Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/zhenxiangba/zhenxiangba.com/public_html/phproxy-improved-master/index.php on line 456
US9270844B2 - Image processing apparatus, control method, and storage medium that complement a domain to an address data item with no domain name - Google Patents
[go: Go Back, main page]

US9270844B2 - Image processing apparatus, control method, and storage medium that complement a domain to an address data item with no domain name - Google Patents

Image processing apparatus, control method, and storage medium that complement a domain to an address data item with no domain name Download PDF

Info

Publication number
US9270844B2
US9270844B2 US12/717,747 US71774710A US9270844B2 US 9270844 B2 US9270844 B2 US 9270844B2 US 71774710 A US71774710 A US 71774710A US 9270844 B2 US9270844 B2 US 9270844B2
Authority
US
United States
Prior art keywords
image processing
processing apparatus
address
domain name
address data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related, expires
Application number
US12/717,747
Other languages
English (en)
Other versions
US20100228820A1 (en
Inventor
Shinichi Takano
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Canon Inc
Original Assignee
Canon Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Canon Inc filed Critical Canon Inc
Assigned to CANON KABUSHIKI KAISHA reassignment CANON KABUSHIKI KAISHA ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TAKANO, SHINICHI
Publication of US20100228820A1 publication Critical patent/US20100228820A1/en
Application granted granted Critical
Publication of US9270844B2 publication Critical patent/US9270844B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
    • H04N1/00127—Connection or combination of a still picture apparatus with another apparatus, e.g. for storage, processing or transmission of still picture signals or of information associated with a still picture
    • H04N1/00204—Connection or combination of a still picture apparatus with another apparatus, e.g. for storage, processing or transmission of still picture signals or of information associated with a still picture with a digital computer or a digital computer system, e.g. an internet server
    • H04L61/15—
    • H04L61/1594—
    • H04L61/303—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4594—Address books, i.e. directories containing contact information about correspondents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
    • H04N1/00127—Connection or combination of a still picture apparatus with another apparatus, e.g. for storage, processing or transmission of still picture signals or of information associated with a still picture
    • H04N1/00204—Connection or combination of a still picture apparatus with another apparatus, e.g. for storage, processing or transmission of still picture signals or of information associated with a still picture with a digital computer or a digital computer system, e.g. an internet server
    • H04N1/00244—Connection or combination of a still picture apparatus with another apparatus, e.g. for storage, processing or transmission of still picture signals or of information associated with a still picture with a digital computer or a digital computer system, e.g. an internet server with a server, e.g. an internet server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
    • H04N1/00127—Connection or combination of a still picture apparatus with another apparatus, e.g. for storage, processing or transmission of still picture signals or of information associated with a still picture
    • H04N1/00347—Connection or combination of a still picture apparatus with another apparatus, e.g. for storage, processing or transmission of still picture signals or of information associated with a still picture with another still picture apparatus, e.g. hybrid still picture apparatus
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names
    • H04L29/12066—
    • H04L61/1511—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N2201/00—Indexing scheme relating to scanning, transmission or reproduction of documents or the like, and to details thereof
    • H04N2201/0008—Connection or combination of a still picture apparatus with another apparatus
    • H04N2201/0015—Control of image communication with the connected apparatus, e.g. signalling capability
    • H04N2201/0031—Control of image communication with the connected apparatus, e.g. signalling capability where the still picture apparatus controls another apparatus
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N2201/00—Indexing scheme relating to scanning, transmission or reproduction of documents or the like, and to details thereof
    • H04N2201/0008—Connection or combination of a still picture apparatus with another apparatus
    • H04N2201/0034—Details of the connection, e.g. connector, interface
    • H04N2201/0037—Topological details of the connection
    • H04N2201/0039—Connection via a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N2201/00—Indexing scheme relating to scanning, transmission or reproduction of documents or the like, and to details thereof
    • H04N2201/32—Circuits or arrangements for control or supervision between transmitter and receiver or between image input and image output device, e.g. between a still-image camera and its memory or between a still-image camera and a printer device
    • H04N2201/3201—Display, printing, storage or transmission of additional information, e.g. ID code, date and time or title
    • H04N2201/3204—Display, printing, storage or transmission of additional information, e.g. ID code, date and time or title of data relating to a user, sender, addressee, machine or electronic recording medium
    • H04N2201/3207—Display, printing, storage or transmission of additional information, e.g. ID code, date and time or title of data relating to a user, sender, addressee, machine or electronic recording medium of an address
    • H04N2201/3208—Display, printing, storage or transmission of additional information, e.g. ID code, date and time or title of data relating to a user, sender, addressee, machine or electronic recording medium of an address of an e-mail or network address
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N2201/00—Indexing scheme relating to scanning, transmission or reproduction of documents or the like, and to details thereof
    • H04N2201/32—Circuits or arrangements for control or supervision between transmitter and receiver or between image input and image output device, e.g. between a still-image camera and its memory or between a still-image camera and a printer device
    • H04N2201/3201—Display, printing, storage or transmission of additional information, e.g. ID code, date and time or title
    • H04N2201/3278—Transmission

Definitions

  • the present invention relates to an image processing apparatus which functions as a server communicable with a client image processing apparatus via a network, and a method of controlling the image processing apparatus.
  • the DNS is a system which associates host names with IP addresses on the Internet. In the DNS, it is possible to look up a host name based on an associated IP address, and vice versa.
  • a name resolution unit e.g. a DNS server
  • the name resolution is performed using the set name resolution units.
  • the address data is configured to store not only a destination address, but also a user account and a password, and authentication is performed based on the user account and the password at a transmission destination (receiving end).
  • FIG. 18 shows parts of a system which uses “reverse DNS” to obtain a host name based on an IP address.
  • the system 100 comprises an MFP 101 , a DNS server 102 and first and second file servers 103 and 104 .
  • the MFP 101 , DNS server 102 and the file servers 103 and 104 are interconnected via a network 105 such as a Local Area Network (LAN).
  • LAN Local Area Network
  • the MFP 101 stores an address book having a plurality of entries corresponding to different respective users of the system. Each entry has a host name, user name and password. For example, the first entry in the address book, “address data 1 ”, has “fileserver1” as the host name, “tanaka” as the user name and “1234” as the password.
  • the host name identifies the name of a host assigned to the first file server 103 .
  • the full host name for the first file server 103 is “fileserver1.aaa.bbb.co.jp” but, as shown in FIG. 18 , the address data 1 only specifies “fileserver1”, i.e. the domain name “aaa.bbb.co.jp” is omitted.
  • the full user name for the user “tanaka” is “tanaka.aaa.bbb.co.jp” but the address data 1 only specifies “tanaka”. It is possible to omit the domain name in this case because the MFP 101 and the file servers 103 and 104 belong to the same network, i.e. they share the same domain name.
  • the image data should be transmitted to a directory corresponding to “tanaka” of the file server 103 having the address “fileserver1.aaa.bbb.co.jp”.
  • the MFP 101 obtains the domain name “aaa.bbb.co.jp” from the DNS server 102 based on the IP address of MFP 101 which is “172.24.10.10” and adds this domain name to “fileserver1” and “tanaka”.
  • the complemented address data “fileserver1.aaa.bbb.co.jp” and “tanaka.aaa.bbb.co.jp” can be used as the destination of the image data.
  • FIG. 19 shows another system having, in addition to the MFP 101 and DNS server 102 of FIG. 18 , a further MFP 201 and a further DNS server 202 .
  • the MFP 101 uses the DNS server 102 to obtain a domain name based on an IP address
  • the further MFP 201 uses the further DNS server 202 to obtain a domain name based on an IP address.
  • the MFP 101 and DNS server 102 are connected to the MFP 201 and DNS server 202 via the Internet.
  • the domain name of the MFP 201 is “ccc.ddd.co.jp”, which is different from the domain name “aaa.bbb.co.jp” of the MFP 101 .
  • a problem occurs when the address book of the MFP 101 is exported to the MFP 201 which uses the DNS server 202 different from the DNS server 102 used by the MFP 101 .
  • This problem arises because the address book of the MFP 101 does not include domain names. If a user of MFP 102 selects the exported address data 1 , in order to transmit image data from the MFP 102 to the user “tanaka”, the domain name “ccc.ddd.co.jp” is added to the host name and the user name for “tanaka”.
  • the present invention provides an image processing apparatus as a server which, when a reference request for referring to address data having no domain name described therein is received from a client or a user's instruction for transmitting such address data to a client, complements the address data with a domain name, and then sends the complemented address data to the client.
  • an image processing apparatus operable as a server to communicate with a client image processing apparatus via a network, comprising a storage unit configured to store an address book containing a plurality of address data items including one or more address data items in which no domain name is described, a determination unit configured to determine whether or not a domain name is described in a designated one of the stored address data items, a complementing unit operable when the determination unit determines that a domain name is not described in the designated address data item, to complement the designated address data item with a domain name, and a transmission unit configured to transmit the address data item, complemented with the domain name by the complementing unit, to the client image processing apparatus.
  • a method of controlling a first image processing apparatus that is operable as a server to communicate with a client image processing apparatus via a network, and that stores an address book containing a plurality of address data items including one or more address data items in which no domain name is described, comprising determining whether or not a domain name is described in a designated one of the address data items stored by the first image processing apparatus, complementing, when it is determined that a domain name is not described in the designated address data item, the designated address data item with a domain name, and transmitting the address data item, complemented with the domain name, to the client image processing apparatus.
  • a computer-readable storage medium storing a computer-readable program for causing a computer to execute a method of controlling a first image processing apparatus that is operable as a server to communicate with a client image processing apparatus via a network, and that stores an address book containing a plurality of address data items including one or more address data items in which no domain name is described, wherein the method comprises determining whether or not a domain name is described in a designated one of the address data items stored by the first image processing apparatus, complementing, when it is determined that a domain name is not described in the designated address data item, the designated address data item with a domain name, and transmitting the address data item, complemented with the domain name, to the client image processing apparatus.
  • the present invention when a reference request for referring to address data having no domain name described therein is received, it is possible to complement the address data with a domain name and then transmit the same. This makes it possible e.g. to send address data correctly to a designated destination, and to reduce failure of authentication.
  • FIG. 1 is a block diagram of a server image processing apparatus according to a first embodiment of the present invention.
  • FIG. 2 is a block diagram of a client image processing apparatus.
  • FIG. 3 is a schematic diagram of a whole image processing system.
  • FIG. 4 is a flowchart of a server process executed by the server image processing apparatus.
  • FIG. 5 is a continuation of FIG. 4 .
  • FIG. 6 is a continuation of FIG. 4 .
  • FIG. 7 is a flowchart of a client process executed by the client image processing apparatus.
  • FIG. 8 is a continuation of FIG. 7 .
  • FIG. 9 is a continuation of FIG. 8 .
  • FIG. 10 is a view of an example of an address book reference screen displayed on a display section of the client image processing apparatus.
  • FIG. 11 is a flowchart of a server process executed by a server image processing apparatus according to a second embodiment of the present invention.
  • FIG. 12 is a continuation of FIG. 11 .
  • FIG. 13 is a continuation of FIG. 12 .
  • FIG. 14 is a continuation of FIG. 11 .
  • FIG. 15 is a flowchart of a client process executed by a client image processing apparatus.
  • FIG. 16 is a continuation of FIG. 15 .
  • FIG. 17 is a continuation of FIG. 15 .
  • FIG. 18 is a schematic diagram showing parts of a conventional image processing system.
  • FIG. 19 is a schematic diagram showing parts of another conventional image processing system.
  • FIG. 1 is a block diagram of a server image processing apparatus (hereinafter simply referred to as “the address book server”) according to a first embodiment of the present invention.
  • the address book server has a function of transmitting address data and a name resolution result to an address book client in response to an address book reference request and a name resolution request respectively sent from the address book client.
  • the address book server is comprised of a CPU 11 , a RAM 12 , a hard disk 13 , a main bus 14 , an input section 15 , a display section 16 , and a communication section 17 .
  • the CPU 11 not only controls the units connected to the main bus 14 , but also executes a server process shown in FIGS. 4 to 6 , based on a program for implementing a control method according to the present invention.
  • the RAM 12 provides a work area and a data storage area for the CPU 11 .
  • the hard disk 13 stores the program for implementing the control method of the present invention, various kinds of data (including an address book storing a plurality of address data items), various settings, and so forth.
  • the hard disk 13 may be replaced by an NVRAM or the like.
  • the communication section 17 communicates with external apparatuses via a network. In the present embodiment, processes in the address book server are executed by the CPU 11 controlling the RAM 12 , the hard disk 13 , and the communication section 17 via the main bus 14 , unless otherwise specified.
  • FIG. 2 is a block diagram of a client image processing apparatus (hereinafter simply referred to as “the address book client”).
  • the address book client comprises a CPU 21 , a RAM 22 , a hard disk 23 , a main bus 24 , an input section 25 , a display section 26 , a communication section 27 , and a reading section 28 .
  • the CPU 21 not only controls the units connected to the main bus 24 , but also executes a client process shown in FIGS. 7 to 9 , according to a program.
  • the RAM 22 provides a work area and a data storage area for the CPU 21 .
  • the hard disk 23 stores the program and various settings.
  • the hard disk 23 may be replaced by an NVRAM or the like.
  • the input section 25 is used by users (including an operator and an installer) for inputting commands.
  • the display section 26 displays various screens.
  • the communication section 27 communicates with external apparatuses via the network.
  • the reading section 28 reads an image as electronic data from an original such as a sheet original.
  • processes in the address book client are executed by the CPU 21 controlling the RAM 22 , the hard disk 23 , the input section 25 , the display section 26 , the communication section 27 , and the reading section 28 via the main bus 24 , unless otherwise specified.
  • FIG. 3 is a schematic diagram of parts of an image processing system.
  • the image processing system is comprised of an address book client C 1 , an address book client C 2 , an address book server SV 1 , a DNS server D 1 , and a DNS server D 2 , which are interconnected by a network N (including the Internet).
  • the DNS server D 1 is set in the address book server SV 1 as the DNS server to be queried for complementary addition of a domain name (i.e. the IP address of the DNS server D 1 is stored in the address book server SV 1 ), where as the DNS server D 2 is set in each of the address book clients C 1 and C 2 as the DNS server to be queried for complementary addition of a domain name (i.e. the IP address of the DNS server D 2 is stored in each of the address book clients C 1 and C 2 ).
  • the DNS (Domain Name System) servers D 1 and D 2 are employed as means for performing name resolution, this is not limitative, and any other means, such as WINS (Windows (registered trademark) Internet Naming Service), for performing name resolution may be employed.
  • WINS Windows (registered trademark) Internet Naming Service
  • FIG. 4 is a flowchart of a server process executed by the address book server SV 1 .
  • FIGS. 5 and 6 are continuations of FIG. 4 .
  • the present server process is executed by the CPU 11 of the address book server SV 1 according to the program stored in the hard disk 13 (or the RAM 12 ).
  • the CPU 11 of the address book server SV 1 starts the present server process (step S 1101 ) and recognizes an input received from an external apparatus via the communication section 17 (step S 1102 ).
  • Inputs from external apparatuses include an address book reference request and a name resolution request from an address book client, for example.
  • the CPU 11 determines whether or not the input is an address book reference request from an address book client (step S 1103 ) or whether or not the input is a name resolution request from an address book client (step S 1104 ).
  • step S 1103 a description will be given of a case where it is determined in the step S 1103 that the input is an address book reference request from an address book client.
  • the CPU 11 of the address book server SV 1 receives the address book reference request from the address book client via the communication section 17 (step S 1201 ). Then, the CPU 11 acquires address data designated by the address book reference request from the hard disk 13 and stores the acquired address data in the RAM 12 (step S 1202 ). Then, the CPU 11 performs the following processing on all the designated address data items (loop starting from a step S 1203 ).
  • the CPU 11 determines whether or not a host name specified by a designated address data item is an IP address (step S 1204 ). If the CPU 11 determines that the host name is an IP address, the process proceeds to a step S 1207 . If the host name is not an IP address, the CPU 11 determines whether or not a domain name is included (described) in the host name (step S 1205 ).
  • the process proceeds to the step S 1207 , whereas if not, the CPU 11 complements the host name with a domain name by querying the DNS server D 1 via the communication section 17 (step S 1206 ), i.e. the address data item is formed into address data in FQDN (Fully Qualified Domain Name) format. Then, the process proceeds to the step 1207 .
  • the CPU 11 determines whether or not a domain name is included in a user account (user name) by the designated address data item (step S 1207 ). If a domain name is included in the user account, the process returns to the step S 1203 to execute the present loop again for the next address data item designated in the address book reference request. Thus the loop is executed a number of times equal to the number of the designated address data items. If a domain name is not included in the user account, the CPU 11 complements the user account with a domain name by querying the DNS server D 1 via the communication section 17 (step S 1208 ), followed by the process returning to the step S 1203 .
  • the CPU 11 sends the designated address data, via the communication section 17 , to the address book client that transmitted the address book reference request (step S 1209 ), followed by the process returning to the step S 1102 .
  • the determination in the step S 1204 as to whether or not the host name is an IP address is performed by determining whether or not the host name is formed by a combination of numerals, a dot, numerals, a dot, numerals, . . . . Further, the determination in the step S 1205 as to whether or not a domain name is written in a host name is performed by determining whether or not the host name is formed by a combination of alphanumeric characters, a dot, alphanumeric characters, a dot, alphanumeric characters, . . . .
  • the determination in the step S 1207 as to whether or not a domain name is written in a user account is performed by determining whether or not the user account is formed by a combination of alphanumeric characters, a dot, alphanumeric characters, a dot, alphanumeric characters, . . . .
  • Each of the steps S 1206 and S 1208 may be executed as follows: After a first query is made to the DNS server D 1 , a domain name is cached in a storage area of the RAM 12 or the like, and from the next execution of the loop, the cached domain name is acquired without making a query to the DNS server D 1 , and used for complementary addition of a domain name. This can be done when one or more address data items, in which a domain name is not described, in the address book of SV 1 have the same domain name. In this case, the cached domain name is deleted after completion of check on all the designated address data items.
  • the following processing method may be employed:
  • the CPU 11 adds information indicative of failure of complementary addition of a domain name in association with the address data, as complementing result information, and sends the address data to the address book client via the communication section 17 .
  • the address book client selectively determines which DNS server (the DNS server D 2 or the address book server SV 1 ) should execute name resolution based on the complementing result information.
  • the complementing result information may be stored e.g. in the storage area of the RAM 12 separately from address data and be transmitted.
  • step S 1104 determines that the input is a name resolution request from the address book client.
  • the CPU 11 of the address book server SV 1 receives the name resolution request from the address book client via the communication section 17 (step S 1301 ).
  • the CPU 11 makes a query to the DNS server D 1 set in the address book server SV 1 via the communication section 17 , whereby the CPU 11 performs, using the DNS server D 1 , name resolution on a host name (a transmission destination to which an image is to be sent from the address book client) received from the address book client (step S 1302 ).
  • the CPU 11 sends a name resolution result to the address book client via the communication section 17 (step S 1303 ), followed by the process returning to the step S 1102 .
  • FIG. 7 is a flowchart of a client process executed by the address book client C 1 .
  • FIG. 8 is a continuation of FIG. 7
  • FIG. 9 is a continuation of FIG. 8 .
  • the present client process is executed by the CPU 21 of the address book client C 1 according to the program stored in the hard disk 23 (or the RAM 22 ).
  • the operation of the address book client C 2 is identical to that of the address book client C 1 , and therefore description thereof is omitted.
  • the CPU 21 of the address book client C 1 starts the present client process (step S 1401 ) and recognizes a user input from the input section 25 (step S 1402 ). If the input is an address book reference request for reference to the address book of the address book server SV 1 (YES to a step S 1403 ), the process proceeds to a step S 1501 in FIG. 8 , wherein the CPU 21 sends a reference request for reference to designated address data to the address book server SV 1 via the communication section 27 .
  • the CPU 21 awaits transmission of the address data from the address book server SV 1 and receives the address data via the communication section 27 (step S 1502 ).
  • the CPU 21 displays an address book reference screen (see FIG. 10 ) for reference to the received address data on the display section 26 (step S 1503 ).
  • On the address book reference screen shown in FIG. 10 are displayed an address book server name (File Server 1 in the illustrated example), a host name, a user name, and a password.
  • the purpose of displaying the address book reference screen is to enable a user to check the host name, user name, and/or password to be used to transmit an image.
  • FIG. 10 illustrates an example in which the host name and the user name are complemented with respective domain names.
  • the CPU 21 recognizes a user input from the input section 25 (step S 1504 ). If the input is not an image transmission instruction for image transmission to a designated destination (NO to a step S 1505 ), the present process is immediately terminated. If the input is an image transmission instruction for image transmission to a designated destination (YES to a step S 1505 ), the process proceeds to a step S 1601 in FIG. 9 , wherein first, the CPU 21 determines whether or not a host name stored in the designated address data is an IP address. If the host name is an IP address, the present process is immediately terminated. If the host name is not an IP address, it is determined whether or not the host name has a domain name written therein (step S 1602 ).
  • the present process is immediately terminated. If the host name has a domain name written therein, the present process is immediately terminated. If the host name does not have a domain name written therein, the CPU 21 sends a name resolution request to the address book server SV 1 via the communication section 27 (step S 1603 ). The CPU 21 awaits transmission of a name resolution result from the address book server SV 1 and receives the name resolution result via the communication section 27 (step S 1604 ), followed by terminating the present process.
  • step S 1501 for sending an address book reference request to an address book server information (IP address or the like) on the DNS server D 2 set in the address book client C 1 may be transmitted along with the address book reference request.
  • information IP address or the like
  • the address book server SV 1 performs complementary addition of a domain name if the DNS server set in the address book client C 1 is different from the DNS server set in the address book server SV 1 .
  • step S 1505 when it is determined in the step S 1505 that the input is an image transmission instruction for image transmission to the designated destination and when the address data received from the address book server contains complementing result information, by consulting the complementing result information, a name resolution request may be sent to the address book server (step S 1603 ) without performing host name check (steps S 1601 and S 1602 ).
  • the address book client C 1 may directly send a name resolution request to the DNS server D 1 set in the address book server in place of sending a name resolution request to the address book server.
  • the complementing result information sent from the address book server contains the IP address of the DNS server D 1 set in the address book server.
  • address data when address data is not fully descriptive, e.g. due to absence of a domain name, the address data is complemented with a domain name to make the same fully descriptive, and is then transmitted. This makes it possible to send (export) address data correctly to a designated destination, and to reduce failure of authentication.
  • the present embodiment is identical in hardware configuration to the above-described first embodiment, and hence while omitting duplicate illustration and description of the hardware configuration, the following description will be given using the same reference numerals denoting the corresponding elements thereof.
  • the present embodiment is basically different from the first embodiment in the following points:
  • a user inputs an address data transmission instruction for sending designated address data to an address book client, from the input section of the address book server, whereby the address book server operates in response to the address data transmission instruction (step S 2103 ).
  • An address book server acquires information on a name resolution unit (DNS server) set in an address book client, to thereby determine whether or not to complementarily add a domain name (steps S 2203 to S 2206 ).
  • DNS server name resolution unit
  • the address book server stores a domain name addition result as domain name addition result information in address data (step S 2305 ).
  • the address book server sends information on the address book server to the address book client (step S 2308 ).
  • the address book client sends the information on the name resolution unit set therein to the address book server (step S 2506 ).
  • the address book client determines a name resolution request destination based on domain name addition result information stored in the address data (step S 2702 ).
  • the address book client receives an IP address of the address book server from the address book server and stores the same (steps S 2601 and S 2602 ).
  • FIG. 11 is a flowchart of a server process executed by the address book server.
  • FIG. 12 is a continuation of FIG. 11 .
  • FIG. 13 is a continuation of FIG. 12 .
  • FIG. 14 is a continuation of FIG. 11 .
  • the present server process is executed by the CPU 11 of the address book server SV 1 according to a program stored in the hard disk 13 (or the RAM 12 ).
  • the CPU 11 of the address book server SV 1 starts the present server process (step S 2101 ) and recognizes a user input from the input section 15 or an input received from an external apparatus via the communication section 17 (step S 2102 ).
  • Inputs from the input section 15 and the communication section 17 include an address data transmission instruction from the input section 15 and a name resolution request received from an address book client via the communication section 17 , for example.
  • the address data transmission instruction is input via the input section 15 that is for example operation panel, by a user of the address book server SV 1 .
  • the CPU 11 determines whether or not the input is an address data transmission instruction from the input section 15 (step S 2103 ) or whether or not the input is a name resolution request from an address book client (S 2104 ).
  • step S 2103 a description will be given of a case where it is determined in the step S 2103 that the input is an address data transmission instruction from the input section 15 .
  • the CPU 11 of the address book server SV 1 receives the address data transmission instruction from the input section 15 (step S 2201 ). Then, the CPU 11 acquires address data designated in the address data transmission instruction from the hard disk 13 and stores the acquired address data in the RAM 12 (step S 2202 ).
  • the CPU 11 sends to an address book client designated in the address data transmission instruction an IP address acquisition request for the IP address of a DNS server set in the address book client (i.e. the DNS server D 2 ) via the communication section 17 (step S 2203 ). Further, the CPU 11 receives the IP address of the DNS server D 2 set in the address book client and sent back therefrom in response to the IP address acquisition request, via the communication section 17 (step S 2204 ).
  • the CPU 11 performs comparison between the received IP address of the DNS server D 2 set in the address book client and the IP address of the DNS server D 1 set in the address book server SV 1 (step S 2205 ). Further, the CPU 11 determines, based on determining conditions, whether or not the DNS server of the address book server SV 1 and the DNS server of the address book client are identical, to thereby determine whether or not to complementarily add a domain name (step S 2206 ).
  • the determining conditions may be “YES if the IP addresses of all the DNS servers are identical” or “YES if at least one of the DNS servers set in the address book client is identical to one set in the address book server SV 1 ”, for example.
  • the process proceeds to a step S 2308 in FIG. 13 , wherein the CPU 11 sends the designated address data and the IP address of the address book server SV 1 to the address book client via the communication section 17 without complementing the designated address data with a domain name, followed by the process returning to the step S 2102 .
  • the process proceeds to a step S 2301 in FIG. 13 , wherein the CPU 11 performs the following processing on all the designated address data items (loop starting from the step S 2301 ).
  • a user of the address book server SV 1 designates at least one address data item to be transmitted (exported).
  • the designated address data items can be one address data item of the address book or all of the address data items of the address book.
  • the CPU 11 determines whether or not a host name included in a designated address data item is an IP address (step S 2302 ). If it is determined that the host name is an IP address, the CPU 11 executes a step S 2306 , referred to hereinafter. If the host name is not an IP address, the CPU 11 determines whether or not a domain name is written in the host name (step S 2303 ). If a domain name is written in the host name, the CPU 11 executes the step S 2306 .
  • the CPU 11 complements the host name with a domain name by querying the DNS server D 1 via the communication section 17 (step S 2304 ), i.e. the address data item is formed into address data in FQDN format. Then, the CPU 11 stores the result of the complementary addition of the domain name as domain name addition result information in the address data (step S 2305 ).
  • the domain name addition result information information indicating “Domain name addition is successful” or “Domain name addition is unsuccessful, and therefore a name resolution request should be sent to the address book server” is stored as a flag or the like.
  • the domain name addition result information may be stored e.g. in the RAM 12 separately from the address data.
  • the CPU 11 determines whether or not a domain name is written in a user account (step S 2306 ). If a domain name is written in the user account, the process returns to the step S 2301 . If a domain name is not written in the user account, the CPU 11 complements the user account with a domain name by querying the DNS server D 1 via the communication section 17 (step S 2307 ), followed by the process returning to the step S 2301 execute the present loop a number of times corresponding to the number of the designated address data items.
  • the CPU 11 sends the address data and the IP address of the address book server SV 1 via the communication section 17 to the address book client that transmitted the IP address of the DNS server D 2 (step S 2308 ), followed by the process returning to the step S 2102 .
  • the steps S 2304 and S 2307 may be executed as follows: After a first query is made to the DNS server D 1 , a domain name is cached in a storage area of the RAM 12 or the like, and from the next execution of the loop, the cached domain name is acquired without making a query to the DNS server D 1 and is used for complementary addition of a domain name. In this case, the cached domain name is deleted after check on all the designated address data items is completed.
  • the CPU 11 receives the name resolution request from the address book client via the communication section 17 (step S 2401 ). Then, the CPU 11 makes a query to the DNS server D 1 set in the address book server SV 1 via the communication section 17 , whereby the CPU 11 performs, using the DNS server D 1 , name resolution on a host name received from the address book client (step S 2402 ). Next, the CPU 11 sends a name resolution result to the address book client via the communication section 17 (step S 2403 ), followed by the process returning to the step S 2102 .
  • FIG. 15 is a flowchart of a client process executed by the address book client C 1 .
  • FIGS. 16 and 17 are continuations of FIG. 15 .
  • the present client process is executed by the CPU 21 of the address book client C 1 according to a program stored in the hard disk 23 (or the RAM 22 ).
  • the operation of the address book client C 2 is identical to that of the address book client C 1 , and therefore description thereof is omitted.
  • the CPU 21 of the address book client C 1 starts the present client process (step S 2501 ) and recognizes an input to the address book client C 1 (step S 2502 ).
  • the input is an address data reception request from the address book server
  • the input is an image transmission instruction from the input section 25
  • the input is a DNS server information acquisition request from the address book server.
  • the CPU 21 receives address data that is designated at the address book server and the IP address of the address book server from the address book server via the communication section 27 (step S 2601 ). Then, the CPU 21 stores the address data and the IP address of the address book server received from the address book server, in the hard disk 23 in association with each other (step S 2602 ), followed by terminating the present process.
  • the CPU 21 receives the image transmission instruction for sending image data to a destination designated in the image transmission instruction (step S 2701 ) from the input section 25 . Then, the CPU 21 performs determination as to the contents of domain name addition result information associated with the address data of the designated destination (step S 2702 ). The domain name addition result information is included in the received address data (step 2305 ).
  • the present process is immediately terminated. If the domain name addition result information designates the transmission of the name resolution request, the CPU 21 sends the name resolution request to the address book server via the communication section 27 (step S 2703 ). Then, the CPU 21 receives a name resolution result from the address book server via the communication section 27 (step S 2704 ), followed by terminating the present process.
  • the input is a DNS server information acquisition request from the address book server (YES to a step S 2505 ).
  • the CPU 21 sends information (including an IP address) on the DNS server D 2 set in the address book client C 1 to the address book server via the communication section 27 (step S 2506 ).
  • Various methods have been conventionally proposed as transmission methods, but they are not directly related to the present invention, and hence, description thereof is omitted.
  • the address data when address data is not fully descriptive e.g. due to absence of a domain name, the address data is complemented with a domain name to make the same fully descriptive, and is then transmitted. This makes it possible to send address data correctly to a designated destination, to reduce failure of authentication, and to check information more correctly at a receiving end.
  • the address book server may store, in advance, identifier information for identifying an address book client in which is set the same DNS server as that set in the address book server.
  • processing for complementarily adding a domain name is not carried out.
  • the address book client may be regarded as having the same DNS server set therein.
  • aspects of the present invention can also be realized by a computer of a system or apparatus (or devices such as a CPU or MPU) that reads out and executes a program recorded on a memory device to perform the functions of the above-described embodiments, and by a method, the steps of which are performed by a computer of a system or apparatus by, for example, reading out and executing a program recorded on a memory device to perform the functions of the above-described embodiments.
  • the program is provided to the computer for example via a network or from a recording medium of various types serving as the memory device (e.g., computer-readable medium).

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Information Transfer Between Computers (AREA)
  • Facsimiles In General (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Accessory Devices And Overall Control Thereof (AREA)
US12/717,747 2009-03-04 2010-03-04 Image processing apparatus, control method, and storage medium that complement a domain to an address data item with no domain name Expired - Fee Related US9270844B2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP2009-050755 2009-03-04
JP2009050755 2009-03-04
JP2010-044499 2010-03-01
JP2010044499A JP5550385B2 (ja) 2009-03-04 2010-03-01 画像処理装置及びその制御方法、並びに記憶媒体

Publications (2)

Publication Number Publication Date
US20100228820A1 US20100228820A1 (en) 2010-09-09
US9270844B2 true US9270844B2 (en) 2016-02-23

Family

ID=42199241

Family Applications (1)

Application Number Title Priority Date Filing Date
US12/717,747 Expired - Fee Related US9270844B2 (en) 2009-03-04 2010-03-04 Image processing apparatus, control method, and storage medium that complement a domain to an address data item with no domain name

Country Status (5)

Country Link
US (1) US9270844B2 (ja)
EP (1) EP2226998A1 (ja)
JP (1) JP5550385B2 (ja)
KR (1) KR101342254B1 (ja)
CN (1) CN101827135B (ja)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180048831A1 (en) * 2015-02-23 2018-02-15 Zuma Beach Ip Pty Ltd Generation of combined videos
US11653072B2 (en) 2018-09-12 2023-05-16 Zuma Beach Ip Pty Ltd Method and system for generating interactive media content

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7987123B1 (en) * 2006-04-03 2011-07-26 The Nielsen Company (Us), Llc Method and system for providing market analysis for wireless data markets
JP6016352B2 (ja) 2011-11-17 2016-10-26 キヤノン株式会社 通信装置、通信装置の制御方法、プログラム
JP6000639B2 (ja) * 2012-05-21 2016-10-05 キヤノン株式会社 画像処理装置、画像処理装置の制御方法、及びプログラム
CN104901870B (zh) * 2015-05-29 2018-07-13 北京北信源软件股份有限公司 一种用于即时通信的用户命名方法
JP6300870B2 (ja) * 2016-08-31 2018-03-28 キヤノン株式会社 画像処理装置、画像処理装置の制御方法、及びプログラム

Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5784560A (en) * 1994-12-15 1998-07-21 Novell, Inc. Method and apparatus to secure distributed digital directory object changes
US20020035624A1 (en) * 2000-09-19 2002-03-21 Samsung Electronics Co., Ltd. Gateway and a method for operating the same
US20020087743A1 (en) * 2000-10-23 2002-07-04 Xacct Technologies, Inc. Data collection system and method for reducing latency
US20020191211A1 (en) * 2001-06-18 2002-12-19 Miller David J. System and method for configuring a printing system
US20030055979A1 (en) * 2001-09-19 2003-03-20 Cooley William Ray Internet domain name resolver
US20030126241A1 (en) * 2001-12-27 2003-07-03 Nec Corporation Registration agent system, network system and program therefor
US20030145089A1 (en) * 2002-01-29 2003-07-31 Xerox Corporation System and method for enabling arbitrary components to transfer data between each other
US20030163737A1 (en) * 2002-02-26 2003-08-28 James Roskind Simple secure login with multiple-authentication providers
US20040047349A1 (en) * 2002-08-20 2004-03-11 Nec Corporation Packet transfer equipment, packet transfer method resolution server, DNS server, network system and program
JP2004165877A (ja) 2002-11-12 2004-06-10 Murata Mach Ltd メールサーバとそのプログラム
US20040153455A1 (en) 2003-01-30 2004-08-05 International Business Machines Corporation Method and apparatus for local IP address translation
US20040220970A1 (en) * 1999-07-26 2004-11-04 Microsoft Corporation Automatic pruning of orphaned objects from directory services and other databases
US20040263898A1 (en) * 2003-06-24 2004-12-30 Ferlitsch Andrew R. Systems and methods for monitoring an imaging job using implicit address discovery
US20040264389A1 (en) * 2002-06-24 2004-12-30 Miguel Abdo Automatic discovery of network node addresses
JP2005094676A (ja) 2003-09-19 2005-04-07 Ricoh Co Ltd 画像処理装置およびユーザ情報取得方法
US20050086377A1 (en) * 2003-09-16 2005-04-21 Takahiro Aso Apparatus and method for proper name resolution
EP1763216A2 (en) 2005-09-12 2007-03-14 Canon Kabushiki Kaisha Data delivery apparatus and data delivery method
US20090182821A1 (en) * 2008-01-15 2009-07-16 Research In Motion Limited Apparatus and associated method for providing network based address book and sharing and synchornizing address book information at multiple communication devices
US20100005146A1 (en) * 2008-07-03 2010-01-07 Barracuda Networks Inc. Facilitating transmission of email by checking email parameters with a database of well behaved senders
US20100005191A1 (en) * 2008-07-03 2010-01-07 Barracuda Networks Inc. Requesting a service or transmitting content as a domain name system resolver
US8045485B2 (en) * 2006-04-03 2011-10-25 Seiko Epson Corporation Monitoring technique of a device connected to a network
US8543107B1 (en) * 2007-09-24 2013-09-24 Sprint Spectrum L.P. Method and system for delivering short message service (SMS) messages using the session initiation protocol (SIP)

Patent Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5784560A (en) * 1994-12-15 1998-07-21 Novell, Inc. Method and apparatus to secure distributed digital directory object changes
US20040220970A1 (en) * 1999-07-26 2004-11-04 Microsoft Corporation Automatic pruning of orphaned objects from directory services and other databases
US20020035624A1 (en) * 2000-09-19 2002-03-21 Samsung Electronics Co., Ltd. Gateway and a method for operating the same
US20020087743A1 (en) * 2000-10-23 2002-07-04 Xacct Technologies, Inc. Data collection system and method for reducing latency
US20020191211A1 (en) * 2001-06-18 2002-12-19 Miller David J. System and method for configuring a printing system
US20030055979A1 (en) * 2001-09-19 2003-03-20 Cooley William Ray Internet domain name resolver
US20030126241A1 (en) * 2001-12-27 2003-07-03 Nec Corporation Registration agent system, network system and program therefor
US20030145089A1 (en) * 2002-01-29 2003-07-31 Xerox Corporation System and method for enabling arbitrary components to transfer data between each other
US20030163737A1 (en) * 2002-02-26 2003-08-28 James Roskind Simple secure login with multiple-authentication providers
US20040264389A1 (en) * 2002-06-24 2004-12-30 Miguel Abdo Automatic discovery of network node addresses
US20040047349A1 (en) * 2002-08-20 2004-03-11 Nec Corporation Packet transfer equipment, packet transfer method resolution server, DNS server, network system and program
JP2004165877A (ja) 2002-11-12 2004-06-10 Murata Mach Ltd メールサーバとそのプログラム
US20040153455A1 (en) 2003-01-30 2004-08-05 International Business Machines Corporation Method and apparatus for local IP address translation
KR20050103192A (ko) 2003-01-30 2005-10-27 인터내셔널 비지네스 머신즈 코포레이션 서버로부터 페이지를 요청하는 방법 및 데이터 프로세싱시스템
US20080301313A1 (en) * 2003-01-30 2008-12-04 International Business Machines Corporation Method and Apparatus for Local IP Address Translation
CN1701587A (zh) 2003-01-30 2005-11-23 国际商业机器公司 用于本地因特网协议地址翻译的方法和设备
US20040263898A1 (en) * 2003-06-24 2004-12-30 Ferlitsch Andrew R. Systems and methods for monitoring an imaging job using implicit address discovery
US20050086377A1 (en) * 2003-09-16 2005-04-21 Takahiro Aso Apparatus and method for proper name resolution
JP2005094676A (ja) 2003-09-19 2005-04-07 Ricoh Co Ltd 画像処理装置およびユーザ情報取得方法
EP1763216A2 (en) 2005-09-12 2007-03-14 Canon Kabushiki Kaisha Data delivery apparatus and data delivery method
US20070081399A1 (en) 2005-09-12 2007-04-12 Canon Kabushiki Kaisha Data delivery apparatus and data delivery method
US8045485B2 (en) * 2006-04-03 2011-10-25 Seiko Epson Corporation Monitoring technique of a device connected to a network
US8543107B1 (en) * 2007-09-24 2013-09-24 Sprint Spectrum L.P. Method and system for delivering short message service (SMS) messages using the session initiation protocol (SIP)
US20090182821A1 (en) * 2008-01-15 2009-07-16 Research In Motion Limited Apparatus and associated method for providing network based address book and sharing and synchornizing address book information at multiple communication devices
US20100005146A1 (en) * 2008-07-03 2010-01-07 Barracuda Networks Inc. Facilitating transmission of email by checking email parameters with a database of well behaved senders
US20100005191A1 (en) * 2008-07-03 2010-01-07 Barracuda Networks Inc. Requesting a service or transmitting content as a domain name system resolver

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
Chinese Office Action issued in counterpart Chinese application No. CN201010126858.4, dated Aug. 16, 2012. English translation provided.
Extended European Search Report issued in European Patent Application No. 10155389.9 dated Jun. 29, 2010.
Korean Office Action. Mail date Sep. 26, 2012.
Mockapetris P. ,ISI, "Domain Names-Implementation and Specification" Network Working Group Request for Comments # 883, IETF Standard, Internet Engineering Task Force, IETF, Nov. 1, 1983, XP015006873, pp. 1-76. Cited in EESR issued in corresponding EP 10155389.9 dated Jun. 29, 2010; see NPL cite No. 1.
Mockapetris. "RFC 883-Domain Names: Implementation Specification." IETF Tools. Nov. 1983. Web. . *
Mockapetris. "RFC 883-Domain Names: Implementation Specification." IETF Tools. Nov. 1983. Web. <http://tools.ietf.org/html/rfc883>. *
QAS: "Address database correction software," Jul. 31, 2008, XP002586763, retrieved from the Internet on Jun. 11, 2010: http://web.archive.org/web/20080731051156/http://www.qas.com/address-correction-software.htm; Sections "Address database correction software" and "QAS Pro Web address validation software" included, pp. 1-3. Cited in EESR issued in corresponding EP 10155389.9 dated Jun. 29, 2010; see NPL cite No. 1.

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180048831A1 (en) * 2015-02-23 2018-02-15 Zuma Beach Ip Pty Ltd Generation of combined videos
US11653072B2 (en) 2018-09-12 2023-05-16 Zuma Beach Ip Pty Ltd Method and system for generating interactive media content

Also Published As

Publication number Publication date
JP5550385B2 (ja) 2014-07-16
US20100228820A1 (en) 2010-09-09
CN101827135A (zh) 2010-09-08
JP2010233213A (ja) 2010-10-14
KR101342254B1 (ko) 2014-01-02
CN101827135B (zh) 2014-05-28
KR20100100670A (ko) 2010-09-15
EP2226998A1 (en) 2010-09-08

Similar Documents

Publication Publication Date Title
US9232107B2 (en) Image processing apparatus that prevents erroneous transmission, method of controlling the same, and storage medium
US10567256B2 (en) Information processing system, portable information terminal, information processing device, and non-transitory computer readable recording medium
US9270844B2 (en) Image processing apparatus, control method, and storage medium that complement a domain to an address data item with no domain name
US9357032B2 (en) Communication apparatus capable of restricting destination of transmission by authenticated user, method of controlling the communication apparatus, and storage medium
US10466943B2 (en) Image processing apparatus, method and non-transitory computer-readable recording medium storing instructions therefor
US10015131B2 (en) Communication device recording input values for subnet mask setting item, IP address setting item, and gateway setting item
JP5014847B2 (ja) 情報処理装置及び情報処理方法
US10630787B2 (en) Mediation server mediating communication between service provider server and first and second communication apparatuses
US11140294B2 (en) Communication device, non-transitory computer-readable recording medium storing computer-readable instructions for communication device, and method executed by communication device
JP2015106815A (ja) 画像処理装置、画像処理方法、及びプログラム
US20110080609A1 (en) Image forming apparatus to support wired and wireless network interfaces and network connection method of the image forming apparatus
US10740044B2 (en) Image processing device, non-transitory computer-readable recording medium storing computer-readable instructions for image processing device, and method
JP6135480B2 (ja) 情報処理プログラムおよび情報処理装置
JP2015069421A (ja) 情報処理システム、情報処理装置、情報処理方法、及びプログラム
JP2014090301A (ja) 情報処理装置及びプログラム
US10560590B2 (en) Information processing apparatus equipped with communication functions, control method therefor, and storage medium
JP2019192088A (ja) 情報処理装置、その制御方法、及びプログラム
JP4203862B2 (ja) データ送信システム、データ送信装置及びプログラム
US11262956B2 (en) Communication system, server system, and terminal apparatus
JP2021149809A (ja) 画像形成装置、印刷システム、制御方法、およびプログラム
JP2019171829A (ja) 画像形成装置、ジョブ取得方法、印刷システム
US8799995B2 (en) Image forming method
US20160117137A1 (en) Image processing apparatus, system, and non-transitory computer readable medium
CN101827185A (zh) 信息处理系统及其控制方法
US10270919B2 (en) Image forming apparatus, image data transmission method, and computer program

Legal Events

Date Code Title Description
AS Assignment

Owner name: CANON KABUSHIKI KAISHA, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TAKANO, SHINICHI;REEL/FRAME:024562/0612

Effective date: 20100318

ZAAA Notice of allowance and fees due

Free format text: ORIGINAL CODE: NOA

ZAAB Notice of allowance mailed

Free format text: ORIGINAL CODE: MN/=.

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20240223