USPatent applicationPatented

Robot control system and method

Granted 5 Aug 2014 · 1 office action

Assignee: Foxconn Technology Group

Law firm: Law firm · Log in to unlock

Attorney: Attorney · Log in to unlock

Inventors: Shou-Kuo Hsu, Shen-Chun Li · Examiner: Dalena Tran · AU 3664 · TC 3600

Life of the application

8 dated events
⤢ drag to zoom20122014201620182020202220242026202820302032ProsecutionOwnershipTerm & fees
ProsecutionOwnershipTerm & feeshover for detail · click to open

Abstract

A cloud server and method controls one or more robots. The cloud server receives location information of each robot. A robot closest to a task location where a task is taken according to the location information. The cloud server of the data center sends a command to the located robot to move to the task location, where the command defines a task of the located robot to perform.

Description

4 parts
›BACKGROUND

1. Technical Field

The embodiments of the present disclosure relate to cloud computing technology, and particularly to a robot control system and method for controlling robots via cloud computing.

2. Description of Related Art

Automation reduces the need for human labor in the production of goods and services. A robot (e.g., a mobile robot or an industrial robot) is often used in automation. For example, manufacturers may use a plurality of industrial robots to assemble a car. However, at present, each robot is controlled by a control system that installed in a fixed and dedicated computer (e.g., a personal computer, or a server). Therefore, a large number of computers are needed when a plurality of robots need to be controlled.

›BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system view of one embodiment of a robot control system.

FIG. 2 is a block diagram of one embodiment of a cloud server included in FIG. 1 .

FIG. 3 is a flowchart of one embodiment of a robot control method.

›DETAILED DESCRIPTION · 1 of 2

The disclosure is illustrated by way of examples and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean at least one.

In general, the word “module”, as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language, such as, Java, C, or assembly. One or more software instructions in the modules may be embedded in firmware, such as in an EPROM. The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of non-transitory computer-readable medium or other storage device. Some non-limiting examples of non-transitory computer-readable media include CDs, DVDs, BLU-RAY, flash memory, and hard disk drives.

FIG. 1 is a block diagram of one embodiment of a robot control system 1 . In one embodiment, the robot control system 1 may include a data center 10 , a network 40 and one or more clients 50 . The robot control system 1 may be used to control one or more robots 20 .

The data center 10 is located behind a firewall 30 and connected to the network 40 . The network 40 may be, but is not limited to, a wide area network (e.g., the Internet) or a local area network. The firewall 30 is used to protect the data center 10 from unauthorized access and secure information safety of the data center 10 . The data center 10 is designed for cloud computing capability and capacity and includes a plurality of cloud servers 100 . The cloud servers 100 are connected to the one or more robots 20 wirelessly.

Each robot 20 is a mechanical intelligent agent which can perform tasks (e.g., vacuum cleaning.) In one embodiment, each robot 20 may be, but is not limited to, a mobile robot. The mobile robot has the capability to move around and is not fixed to one physical location. Each mobile robot includes one or more wheels or motors to move. Additionally, each robot 20 includes a global positioning system (GPS) device. The GPS device receives GPS signals from one or more satellites, and determines a longitude and a latitude of the robot 20 .

The cloud server 100 is a dynamic host configuration protocol (DHCP) server. In one embodiment, the cloud server 100 assigns IP addresses to the client 50 . The cloud server 100 may provide three modes for allocating IP addresses to the clients 50 . The modes are dynamic allocation, automatic allocation, and static allocation. In one embodiment, the cloud server 100 uses dynamic allocation to assign the IP addresses to the clients 50 . The cloud server 100 further sets a password (e.g., 123456$) and a name (e.g., apple) for enabling the client 50 to access the data center 10 . The cloud server 100 also provides an access privilege for each client 50 according to the assigned IP address and the name. Additionally, the cloud server 100 may be a personal computer (PC), a network server, or any item of other data-processing equipment. Further details of the cloud server 10 will be described below.

The client 50 is electronically connected to the network 40 . Additionally, the client 50 provides a user interface on the display for a user to access the data center 10 to control one or more operations of the cloud server 100 . For example, the user may input a password and name by an input device (e.g., keyboard) into the user interface on the display to access the data center 10 .

FIG. 2 is a block diagram of one embodiment of the cloud server 100 including a robot control unit 110 . The robot control unit 110 may be used to control the robots 20 . In one embodiment, the cloud server 100 includes a storage system 180 , at least one processor 190 , and an electronic map 200 . The electronic map 200 is used to display a location of the robot 20 according to the longitude and the latitude of the robot 20 . In one embodiment, the robot control unit 110 includes a setting module 120 , a receiving module 130 , a determination module 140 , a search module 150 , a sending module 160 , and a denying module 170 . The modules 120 - 170 may include computerized code in the form of one or more programs that are stored in a storage system 180 . The computerized code includes instructions that are executed by the at least one processor 190 to provide functions for the modules 120 - 170 . The storage system 180 may be a cache or a memory, such as an EPROM, HDD, or flash memory.

The setting module 120 sets identification information used in order to access the cloud server 100 of the data center 10 and assigns the identification information to the client 50 . In one embodiment, the identification information includes the name, the password, and the IP address of the client 50 . The identification information of each client 50 is also stored in the storage system 180 .

The receiving module 130 receives a login request to access the cloud server 100 of the data center 10 from the client 50 . In one embodiment, the user inputs a name and a password in the user interface of the client 50 . The client 50 generates the login request and sends the login request to the cloud server 100 of the data center 10 . It is understood that the login request is defined as a command having information of the input name, input password and the IP address of the client 50 .

The determination module 140 determines if the client 50 is permitted to access the cloud server 100 of the data center 10 . In one embodiment, the determination module 140 compares the identification information of the client 50 that is stored in the storage system 180 with information contained in the login request, if the identification information is the same as the information contained in the login request, the client 50 is permitted to access the cloud server 100 of the data center 10 . Otherwise, if the identification information is different from the information contained in the login request, the client 50 is not permitted to the cloud server 100 of the data center 10 .

›DETAILED DESCRIPTION · 2 of 2

The receiving module 130 receives location information of each robot 20 from the GPS device of each robot 20 , and receives location information of a task location from the client 50 , in response to a determination that the client is permitted to the cloud server 100 of the data center 10 . It is understood that the task location is a particular place where a task should be undertaken by the robot 20 . In one embodiment, the location information includes a longitude and a latitude. In one embodiment, the user may input the location information of the task location in the clients 50 .

The search module 150 locates a robot 20 which is closest to the task location according to the location information of all the robots 20 and the location information of the task location. In one embodiment, the search module 150 computes a route from each robot 20 to the task location on the electronic map 200 and determines a shortest route to the task location. For example, assuming that the two robots 20 are labeled as A and B, the search module 150 computes a first route from A to the task location and also computes a second route from B to the task location, the search module 150 finds out a shortest route from the first route and the second route. For example, if the first route is shorter than the second route, then A is determined to be closest to the task location.

The sending module 160 sends a command to the located robot 20 to move to the task location, wherein the command defines a task of the located robot 20 to perform. For example, the tasks may be vacuum cleaning. The sending module 160 sends the command to A to move to the task location to execute the task. For example, if the task is vacuum cleaning, the command includes content of the task and the location information of the task location. The content of the task includes information on how and what to perform the task. If the located robot 20 receives the command, the robot 20 moves to the task location according to the location information and perform vacuum cleaning according to the content of the task.

The denying module 170 denies the client 50 to access the cloud server 100 of the data center 10 , in response to a determination that the client 50 is not permitted to the cloud server 100 of the data center 10 .

FIG. 3 is a flowchart of one embodiment of a robot control method. Depending on the embodiment, additional blocks may be added, others deleted, and the ordering of the blocks may be changed.

In block S 301 , the setting module 120 sets identification information for accessing the cloud server 100 of the data center 10 and assigns the identification information to the client 50 . As mentioned above, the identification information may include the name, the password, and the IP address of the client 50 .

In block S 302 , the receiving module 130 receives a login request to access the cloud server 100 of the data center 10 from the client 50 . As mentioned above, the user may input a name and a password in the user interface of the client 50 which is forwarded to the cloud server 100 of the data center 10 as part of the login request.

In block S 303 , the determination module 140 determines if the client 50 is capable of accessing the cloud server 100 of the data center 10 . In one embodiment, the determination module 140 compares the identification information with the login request, if the identification information is different from the information contained in the login request, the client 50 is permitted to access the cloud server 100 of the data center 10 , the procedure goes to the block S 304 . Otherwise, if the identification information is different from the information contained in the login request, the client 50 is not permitted to the cloud server 100 of the data center 10 , the procedure goes to the block S 307 .

In block S 304 , the receiving module 130 receives location information of each robot 20 from the GPS device of each robot 20 and receives location information of a task location from the client 50 . As mentioned above, the location information includes a longitude and a latitude.

In block S 305 , the search module 150 locates a robot 20 which is closest to the task location according to the location information of each robot 20 . For example, assuming that the two robots 20 are labeled as A and B, the search module 150 computes a first route from A to the task location and also computes a second route from B to the task location, the search module 150 finds out a shortest route from the first route and the second route. For example, if the first route is shorter than the second route, then A is determined as the robot 20 which is closest to the task location.

In block S 306 , the sending module 160 sends a command to the located robot 20 to move to the task location, wherein the command defines a task of the located robot 20 to perform. For example, if the task is vacuum cleaning. The sending module 160 sends the command to A to move to the task location to execute the task.

In block S 307 , the denying module 170 denies the client 50 to access the cloud server 100 of the data center 10 .

Although certain inventive embodiments of the present disclosure have been specifically described, the present disclosure is not to be construed as being limited thereto. Various changes or modifications may be made to the present disclosure without departing from the scope and spirit of the present disclosure.

Claims as granted

15 claims

Log in to read the claims of this application.

Log in to unlock

Classifications

3 codes
IPC · International Patent Classification
Section G — Physics
  • G05D3/00
USPC · US Patent Classification
700/248718/103

Claim changes

Soon
Coming soonHow the claims changed between publication and grant

See which claims were amended, added or cancelled during examination, with every added and removed word marked.

AmendedAddedCancelledUnchanged

The published claims of this application are not paired with the granted ones in what we hold.

File wrapper

⤢ drag to zoomJul 2011Jan 2012Jul 2012Jan 2013Jul 2013Jan 2014Jul 2014USPTOApplicantNon-final rejectionResponse after non-finalNotice of allowance
USPTOApplicanthover for detail · click to open
Pendency
2.9 y
1,076 days filing → grant
Office actions
1
non-final + final
Responses
1
no RCE
Examiner
Dalena Tran
art unit 3664 · TC 3600
Citations: 5 back · 31 forward

See the full prosecution history — every USPTO and applicant action on this file, in order.

Log in to unlock

Documents

Log in to open the documents of this file: the application as filed, every office action and response, the notice of allowance.

Log in to unlock

Chain of title

⤢ drag to zoom20122014201620182020202220242026202820302032Owner 1
Titlehover for detail · click to open

See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.

Log in to unlock