DETAILED ACTION
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 .
Specification
A new title is required that is clearly indicative of the invention to which the claims are directed. This current title includes a long description of all possible areas where applicant’s invention could be used. The following title is suggested: Automated Elevator Control for Unmanned Devices.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1-19 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter. The claimed invention, claims 1-12, is directed to an abstract idea without significantly more. Claims 1-12 recite “A method for taking an elevator by an unmanned device”; a process that simply automates a human activity using a robot does not render the claims patent eligible. To be eligible, the claims must show a technical improvement (an improvement to the navigation system of the robot or the elevator control system itself), not just an application of a well-known technology in a different field. This judicial exception is not integrated into a practical application because generically programming a machine (unmanned device) to communicate with a virtual server (cloud platform) through remote communication does not represent a technological improvement. The claim(s) do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the series of recited steps only instruct an unmanned device to perform a desired routine that includes conventional computer functions.
In reference to claims 13-19, although the preamble in these claims in different from the preamble in claims 1-12, the body of claims 13-19 is directed to a similar abstract idea as described above in the rejection of claims 1-12. Claims 13-19 also recite a conventional communication between a virtual server (cloud platform) and a robot (unmanned device). Therefore, claims 13-19 are rejected for the same reasons given above with respect to claims 1-12.
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)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1-19 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Vuorenala et al US Publication 2019/0345000).
Claims 1 and 13, Vuorenala et al teaches a method for controlling an elevator by an unmanned device comprising: sending s start floor elevator call request to a cloud platform through a remote communication connection (as described in paragraph 0029, robot 150A/150B communicate with data center 140); receiving a real-time running information of at least one elevator 100 by the data center 140 (the data center communicates with the robots directly or indirectly through the elevator control entity 110 as described in paragraph 0029) by determining a priority associated to the received elevator call request (see paragraph 0035); selecting a target elevator 100 according to the real-time running information and entering said target elevator (see paragraph 0036); and establishing a communication connection with the elevator control entity 110 of the target elevator 100 in order to send the target elevator to the requesting passenger (either a robot or a human), see the description given in paragraph 0036.
Claims 2 and 14, Vuorenala et al further describes receiving real-time running information of a selected target elevator; and determining arrival of the selected elevator 100 to a target floor based on the real-time running information (see fig. 2 and corresponding description).
Claims 3 and 15, as described above in the rejection of claim 1, Vuorenala et al describes a data center 140 communicating directly or indirectly with the unmanned device 150A/150B through elevator control entity 110 which is described in fig. 5.
Claims 4 and 16, Vuorenala et al describes, fig. 1 and paragraph 0029, establishing a remote communication between the unmanned device 150A/150B with the cloud platform (data center) 140; and sending a service call request (fig. 2, step 210) to the cloud platform 140 through remote communication (see fig. 4).
Claim 5, Vuorenala et al describes activating a sub-process of the unmanned device 150A/150B (when the unmanned device communicates to the data server 140 through elevator controlling device 110); connecting to the elevator control device 110 through communication interface 430; and performing a log in step in order to establish a connection with the elevator control device (see for example the description of each of the elements found in the unmanned device, paragraph 0037).
Claims 6, 7, and 18-19, Vuorenala et al describes sending a target elevator request call to the data server 140 either by the unmanned device 150A/150B directly or through the elevator control device 110; and using control device 110 to move the target elevator to the requesting floor where the unmanned device is located based on the target floor request call. Additionally, the elevator control unit 110 and the data center 140 manage service calls to the same target floor by different entities (humans or robots) in order to avoid sending duplicate calls to different elevators (see for example the description given in paragraph 0036).
Claims 8, 9, and 17, Vuorenala et al describes in fig. 2 the steps taken by an elevator system when a service call is requested by a user (human or unmanned device), the elevator system receives the call (fig. 2, step 210) from the user or data center 140, a user (unmanned device) moves to an assigned elevator 100 to perform a given task of going to a desired floor, and an elevator control unit 110 operates the elevator 110 to transport the user to the target or desired floor. It is inherent the elevator will open its door to let the user in, close the door before moving to the target floor, and open its doors again to let the user get out. Fig. 5 describes elements of the elevator control unit which includes a processor 510 and memory 520.
Claim 10, Vuorenala et al describes in fig. 4 the components found in the unmanned device 150A/150B which include sensor unit 450, this unit allows the unmanned device to navigate and position itself within a specified area. The data server 140 and the elevator control unit 110 communicate with the unmanned device through communication interface 430 in order to let the unmanned device know where to go to accomplish its task.
Claim 11, Vuorenala et al describes in paragraph 0036 the real-time running information including the running state of an elevator 100.
Claim 12, Vuorenala et al describes in fig. 1 the elevator controlling communication device 110/120 inside elevator 100; and the elevator controlling device 140 disposed outside the elevator.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. The documents cited in the attached PTO-892, especially US Publication 20120041593, describe elevator control systems and methods for controlling elevator systems using robots.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Rina I Duda whose telephone number is (571)272-2062. The examiner can normally be reached M-F 8-4 PM.
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, Eduardo Colon-Santana can be reached at (571) 272-2060. 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.
/RINA I DUDA/Primary Examiner, Art Unit 2846