Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
This is responsive to preliminary amendment filed on 10/17/24. Claims 1, 4, 7-8 are pending. Claims 2-3, 5-6 are cancelled.
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 10/17/24 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1, 4, 7-8 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claims 1, 4, 7-8 recites the limitation of “…transmit, to the appliance corresponding to a combination of the dynamic address and the static address not included in the table information, a static address request requesting transmission of the static address information to acquire the static address information, and add the static address information to the table information,…transmits the static address request to the appliance that is a transmission source of the update notification to acquire the static address information from the appliance, and adds the static address information to the table information, transmits the control information to the appliance using the static address information associated with the type information and the appliance identification information corresponding to the generated control information and stored in the appliance information storage, and when the update notification is acquired, causes the appliance information storage to store, in a manner associated with one another, the type information and the appliance identification information included in the acquired update notification and the acquired static address information”. Its unclear from the claim scope if the table storage register the appliance information from the static address, type information, appliance ID and the IP address; why would the claim re-register the appliance device by updating the information of the table. Also, the static address based on the spec. is a MAC address which would not change for the appliance device. Since the claim limitation contradicts and hence for purpose of examination claims limitation are interpreted as registering the appliance.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 1, 4, 7-8 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Maeda et al. (US 2022/0053055 A1), hereinafter “Maeda”.
As to claim 1, Maeda disclose a control device for controlling an appliance by transmitting, to the appliance, control information for controlling the appliance using a static address specific to the appliance in a network including the appliance (An identifier (e.g., a MAC (Media Access Control) address) and a device type as classified by classifier 130 are registered in association with each other in the device list, as illustrated in FIG. 3. Note that information aside from the MAC address and the device type may be registered, or information aside from a MAC address may be registered as the identifier, in the device list. In the device list, for example, an IP address may be registered, and if home gateway 20 has a plurality of communication ports for connecting to communication lines, the communication port to which the device is connected may be registered.) (Maeda, ¶ 0091, 0110, figs. 2-3 & 39), the control device comprising:
a table storage to store table information associating the static address with a dynamic address assigned to the appliance in the network including the appliance (home gateway 20 manages information such as IP (Internet Protocol) addresses needed by PC 30, as well as by electric lock 40, air conditioner 41, lighting 42, and controller 43, to communicate, assigns IP addresses in response to requests from each device, provides notifications of the information necessary for communication, and the like. Additionally, home gateway 20 monitors whether or not improper device control commands are being transmitted to electric lock 40, air conditioner 41, and lighting 42, and blocks the improper device control commands as necessary. Home gateway 20 is an example of a device monitoring apparatus) (Maeda, ¶ 0091-0093, 0101, 0110, figs. 10-11 & 39);
an appliance information storage to store, in a manner associated with static address information indicating the static address and being specific to the appliance, type information indicating a type of the appliance and appliance identification information identifying the appliance in an application layer (Initial device list generator 110 is connected to home network 11. Initial device list generator 110 performs processing for generating a device list when no device list is present in device list holder 200 or the device list has been deleted, such as at the time of the first startup, when an instruction has been made by the user to reset the device list held in device list holder 200, or the like. Initial device list generator 110 searches for devices connected to home network 11 and registers devices which have been found in the device list. Additionally, initial device list generator 110 requests classifier 130 to classify devices registered by initial device list generator 110. Although details will be given later, the device list includes information pertaining to a plurality of devices connected to home network 11.) (Maeda, ¶ 0091-0093, 0101, 0110, figs. 10-11 & 39); and
processing circuitry to
identify the static address of the appliance based on the table information (An identifier (e.g., a MAC (Media Access Control) address) and a device type as classified by classifier 130 are registered in association with each other in the device list, as illustrated in FIG. 3) (Maeda, ¶ 0091-0093, 0101, 0110, figs. 3, 10-11 & 39),
transmit an appliance message to the appliance using the identified static address (transmitting ARP messages and registering devices that respond in device list holder 200 when generating the device list, the configuration is not limited thereto, and for example, ICMP (Internet Control Message Protocol) Echo Messages may be transmitted, and the device list may be generated from response messages responding thereto) (Maeda, ¶ 0091-0093, 0101, 0124, figs. 3, 10-11 & 39),
transmit, to the appliance corresponding to a combination of the dynamic address and the static address not included in the table information, a static address request requesting transmission of the static address information to acquire the static address information, and add the static address information to the table information (e.g., a MAC (Media Access Control) address) and a device type as classified by classifier 130 are registered in association with each other in the device list, as illustrated in FIG. 3. Note that information aside from the MAC address and the device type may be registered, or information aside from a MAC address may be registered as the identifier, in the device list. In the device list, for example, an IP address may be registered, and if home gateway 20 has a plurality of communication ports for connecting to communication lines, the communication port to which the device is connected may be registered…FIG. 4, first, if there are no devices registered in device list holder 200 at the time of startup, home gateway 20 generates the device list (an initial device list) using initial device list generator 110 (S1001). Initial device list generator 110 transmits, for example, an ARP (Address Resolution Protocol) message to all IP addresses in the same subnet in order to extract devices connected to home network 11, and registers devices that respond in device list holder 200) (Maeda, ¶ 0091-0093, 0101, 0120-0124, figs. 3-4, 10-11 & 39),
acquire the appliance message transmitted from the appliance (transmitting ARP messages and registering devices that respond in device list holder 200 when generating the device list, the configuration is not limited thereto, and for example, ICMP (Internet Control Message Protocol) Echo Messages may be transmitted, and the device list may be generated from response messages responding thereto) (Maeda, ¶ 0091-0093, 0101, 0124, figs. 3, 10-11 & 39),
determine whether the acquired appliance message is an update notification indicating assignment of a new dynamic address to the appliance (FIG. 4, first, if there are no devices registered in device list holder 200 at the time of startup, home gateway 20 generates the device list (an initial device list) using initial device list generator 110 (S1001). Initial device list generator 110 transmits, for example, an ARP (Address Resolution Protocol) message to all IP addresses in the same subnet in order to extract devices connected to home network 11, and registers devices that respond in device list holder 200) (Maeda, ¶ 0091-0093, 0101, 0120-0124, figs. 3-4, 10-11 & 39),
generate the control information based on at least one of the type information or the appliance identification information (classifier 130 determines whether or not a device that received the determination message has returned a response message (S2002). If the determination message has been transmitted through broadcast or multicast, classifier 130 waits for the response message until a set amount of time has passed following the transmission of the determination message, determines “response” for a device which has transmitted a response message, and determines “no response” for a device which has not transmitted a response message before the set amount of time has passed. On the other hand, if the determination message has been transmitted to devices individually, classifier 130 determines “response” if a response message is received, and determines “no response” if a response message is not received before a set amount of time has passed.) (Maeda, ¶ 0091-0093, 0101, 0120-0124, figs. 3-4, 10-11 & 39),, and
update the type information, the appliance identification information, and the static address information that are stored in the appliance information storage (FIG. 4, first, if there are no devices registered in device list holder 200 at the time of startup, home gateway 20 generates the device list (an initial device list) using initial device list generator 110 (S1001). Initial device list generator 110 transmits, for example, an ARP (Address Resolution Protocol) message to all IP addresses in the same subnet in order to extract devices connected to home network 11, and registers devices that respond in device list holder 200) (Maeda, ¶ 0091-0093, 0101, 0120-0124, figs. 3-4, 10-11 & 39),
wherein the update notification includes the type information and the appliance identification information (FIG. 4, first, if there are no devices registered in device list holder 200 at the time of startup, home gateway 20 generates the device list (an initial device list) using initial device list generator 110 (S1001). Initial device list generator 110 transmits, for example, an ARP (Address Resolution Protocol) message to all IP addresses in the same subnet in order to extract devices connected to home network 11, and registers devices that respond in device list holder 200) (Maeda, ¶ 0091-0093, 0101, 0120-0124, figs. 3-4, 10-11 & 39), and the processing circuitry
transmits the static address request to the appliance that is a transmission source of the update notification to acquire the static address information from the appliance, and adds the static address information to the table information (e.g., a MAC (Media Access Control) address) and a device type as classified by classifier 130 are registered in association with each other in the device list, as illustrated in FIG. 3. Note that information aside from the MAC address and the device type may be registered, or information aside from a MAC address may be registered as the identifier, in the device list. In the device list, for example, an IP address may be registered, and if home gateway 20 has a plurality of communication ports for connecting to communication lines, the communication port to which the device is connected may be registered…FIG. 4, first, if there are no devices registered in device list holder 200 at the time of startup, home gateway 20 generates the device list (an initial device list) using initial device list generator 110 (S1001). Initial device list generator 110 transmits, for example, an ARP (Address Resolution Protocol) message to all IP addresses in the same subnet in order to extract devices connected to home network 11, and registers devices that respond in device list holder 200) (Maeda, ¶ 0091-0093, 0101, 0120-0124, figs. 3-4, 10-11 & 39),
transmits the control information to the appliance using the static address information associated with the type information and the appliance identification information corresponding to the generated control information and stored in the appliance information storage (e.g., a MAC (Media Access Control) address) and a device type as classified by classifier 130 are registered in association with each other in the device list, as illustrated in FIG. 3. Note that information aside from the MAC address and the device type may be registered, or information aside from a MAC address may be registered as the identifier, in the device list. In the device list, for example, an IP address may be registered, and if home gateway 20 has a plurality of communication ports for connecting to communication lines, the communication port to which the device is connected may be registered…FIG. 4, first, if there are no devices registered in device list holder 200 at the time of startup, home gateway 20 generates the device list (an initial device list) using initial device list generator 110 (S1001). Initial device list generator 110 transmits, for example, an ARP (Address Resolution Protocol) message to all IP addresses in the same subnet in order to extract devices connected to home network 11, and registers devices that respond in device list holder 200) (Maeda, ¶ 0091-0093, 0101, 0120-0124, figs. 3-4, 10-11 & 39), and
when the update notification is acquired, causes the appliance information storage to store, in a manner associated with one another, the type information and the appliance identification information included in the acquired update notification and the acquired static address information (FIG. 4, first, if there are no devices registered in device list holder 200 at the time of startup, home gateway 20 generates the device list (an initial device list) using initial device list generator 110 (S1001). Initial device list generator 110 transmits, for example, an ARP (Address Resolution Protocol) message to all IP addresses in the same subnet in order to extract devices connected to home network 11, and registers devices that respond in device list holder 200) (Maeda, ¶ 0091-0093, 0101, 0120-0124, figs. 3-4, 10-11 & 39).
Claim 4 list all the same elements of claim 1, but in a control system, comprising: a server to generate control information to control an appliance (Maeda, ¶ 0091, 0110, figs. 2-3 & 39); and a control device to control the appliance by transmitting, to the appliance, the control information acquired from the server using a static address specific to the appliance in a network including the appliance, wherein the control device (Maeda, ¶ 0091, 0110, figs. 2-3 & 39) to control system including the control device. Therefore, the supporting rationale of the rejection to claim 1 applies equally as well to claim 4.
Claim 7 list all the same elements of claim 1, but in a control method for controlling an appliance by transmitting, to the appliance, control information for controlling the appliance using a static address specific to the appliance in a network including the appliance (Maeda, ¶ 0091, 0110, figs. 2-3 & 39) to carry out method steps of the device form. Therefore, the supporting rationale of the rejection to claim 1 applies equally as well to claim 7.
Claim 8 list all the same elements of claim 1, but in a non-transitory computer-readable recording medium storing a program, the program causing a computer to function as: (Maeda, ¶ 0091, 0110, figs. 2-3 & 39). Therefore, the supporting rationale of the rejection to claim 1 applies equally as well to claim 8.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. See PTO-892.
Whittle et al. (US 2014/0278248 A1) disclose a method and system for administering enterprise appliances facilitates maintenance, procurement, deployment and security of enterprise appliances by taking targeted administrative actions in response to detected power anomalies experienced by such appliances. By using detected power anomalies as triggers for targeted administrative actions, rather than waiting for administrators to be notified of problems with enterprise appliances by workers or departments to which such appliances are assigned, problems with enterprise appliances are resolved more quickly and costs to the enterprise arising from such problems are reduced.
Arai (US 2023/0308444 A1) disclose a control system includes a cloud server and a terminal device. A checker of the cloud server checks pieces of MAC address data acquired by a machine MAC address acquirer against pieces of MAC address data contained in communicable-machine notification information, and specifies, among the pieces of MAC address data acquired by the machine MAC address acquirer, a piece of MAC address data that matches one of the pieces of MAC address data contained in the communicable-machine notification information. An operation authority setter generates, based on the piece of MAC address data specified by the checker, operation authority information containing a piece of MAC address data on a machine operable via the terminal device.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HITESH R PATEL whose telephone number is (571)270-5442. The examiner can normally be reached Monday-Friday 7am-3pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, James Trammell can be reached at 571-272-6712. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/Hitesh Patel/Supervisory Patent Examiner, Art Unit 3667
2/2/26