IP Library Granted Patent US 12,299,481
Granted Patent B2
US 12,299,481 · App. 16/822,534 · Granted May 13, 2025

Conflict resolution method for a remotely controlled device and conflict resolution system

Inventors: Roman Schlegel (Wettingen, CH); Thomas Locher (Zurich, CH)
Assignee: ABB SCHWEIZ AG
G06F9/4881G06F9/4818G06F9/524G06F11/3006
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,299,481
App. No.
16/822,534
Granted
May 13, 2025
Kind
B2
Abstract

A conflict resolution method for a remotely controlled device is provided. The method includes: issuing a command for the device by a remote control center or by the device; determining a criticality level of the command; depending on the criticality level of the command, sending the command to the other one of the device and the control center for acknowledgment or refusal of the command; and executing or disregarding the command by the device depending on the criticality level of the command and, if applicable, on the acknowledgment or refusal of the command.

Claims (51)

1. A conflict resolution method for a device comprising:

issuing a command for the device by the device,

wherein the device can issue the command on its own;

determining, by the device in response to the command issued by the device, a criticality level of the command;

depending on the criticality level of the command, sending the command to a remote control center for acknowledgment or refusal of the command; and

executing or disregarding the command by the device depending on the criticality level of the command and based on the acknowledgment or refusal of the command;

wherein the criticality level determines whether any acknowledgment by the remote control center is necessary before the command is executed;

wherein issuing the command for the device by the device comprises:

determining a control mode of the device by the device,

wherein sending the command to the remote control center by the device further depends on the control mode of the device,

wherein executing or disregarding the command by the device further depends on the control mode of the device,

wherein, in a normal control mode, the device is configured to send the command to the remote control center by the device based on the determined criticality level of the command, wherein, in a priority mode of the device, the device is configured to directly execute the commands irrespective of the criticality level of the command, and wherein, in a lockout mode of the device, the command needs to be acknowledged by the remote control center irrespective of the criticality level of the command;

in response to determining that the control mode of the device is in the normal mode and the criticality level of the command is high,

the command from the device is executed by the device before the device receives an acknowledgment or refusal of the command from the remote control center in response to determining the acknowledgment or the refusal cannot be obtained within a specified time frame, and

wherein, in response to the acknowledgment or refusal of the command not being received from the remote control center within the specified time frame, the command is reversed by reverting parameters of the device to the parameters before the command was executed by the device; and

changing the control mode of the device by the remote control center.

2. The method according to claim 1 , further comprising:

changing the criticality level of the command.

3. The method according to claim 1 , wherein the command is sent to the remote control center for acknowledgment or refusal of the command if the criticality level is high.

4. The method according to claim 1 , wherein the command is not sent to the remote control center for acknowledgment or refusal of the command if the criticality level is low.

5. The method according to claim 1 , wherein the command is sent to the remote control center for acknowledgment or refusal of the command irrespective of the criticality level when the control mode is set to a priority mode for the remote control center.

6. The method according to claim 1 , wherein the command is given priority over commands issued by the remote control center for the device when the control mode is set to a priority mode for the device.

7. The method according to claim 1 , wherein the command needs to be acknowledged by the other one of the device and the control center irrespective of the criticality level when the control mode is set to a lockout mode for the one of the device and the control center issuing the command.

8. A conflict resolution system, comprising:

a device to be remotely controlled; and

a remote control center,

wherein the device is configured to:

issue a command for the device on its own;

determine a criticality level of the command, by the device issuing the command in response to the command issued by the device; and

depending on the criticality level of the command, send the command to the remote control center for acknowledgment or refusal of the command,

wherein the device is configured to:

execute or disregard the command depending on the criticality level of the command and, if applicable, on the acknowledgment or refusal of the command;

wherein issuing the command for the device comprises:

determine a control mode of the device by the device,

wherein sending the command by the device for acknowledgment or refusal of the command from the device to the remote control center further depends on the control mode of the device,

wherein executing or disregarding the command by the device further depends on the control mode of the device,

wherein, in a normal control mode, the device is configured to send the command to the remote control center by the device based on the determined criticality level of the command, wherein, in a priority mode of the device, the device is configured to directly execute the commands irrespective of the criticality level of the command, and wherein, in a lockout mode of the device, the command needs to be acknowledged by the remote control center irrespective of the criticality level of the command;

in response to determining that the control mode of the device is in the normal mode and the criticality level of the command is high,

the command from the device is executed by the device before the device receives an acknowledgment or refusal of the command from the remote control center in response to determining the acknowledgment or the refusal cannot be obtained within a specified time frame, and

wherein, in response to the acknowledgment or refusal of the command not being received from the remote control center within the specified time frame, the command is reversed by reverting parameters of the device to the parameters before the command was executed by the device; and

changing the control mode of the device by the remote control center.

9. The conflict resolution system of claim 8 , wherein the device is a moveable vessel and the remote control center is stationary.

10. The conflict resolution system of claim 8 , wherein the device, and the remote control center are remote from each other.

11. The conflict resolution system of claim 8 , wherein at least one of the device, and the remote control center comprises a network interface for connecting the device to a data network, in particular a global data network.

12. The method according to claim 1 , further comprising changing the criticality level of the command.

13. The method according to claim 1 , wherein the command is sent to the remote control center for acknowledgment or refusal of the command if the criticality is high.

14. The method according to claim 1 , wherein the command is not sent to the remote control center for acknowledgment or refusal of the command if the criticality level is low.

15. The conflict resolution system of claim 9 , wherein the device and the remote control center are remote from each other.

16. The conflict resolution system of claim 10 , wherein at least one of the device, and the remote control center comprises a network interface for connecting the device to a data network.

17. The conflict resolution system of claim 8 , wherein the command is sent to the remote control center for acknowledgment or refusal of the command irrespective of the criticality level when the control mode is set to a priority mode for the remote control center.

18. The conflict resolution system of claim 8 , wherein the command is given priority over commands issued by the remote control center for the device when the control mode is set to a priority mode for the device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 19, 2020
From: SCHLEGEL, ROMAN; LOCHER, THOMAS
To: ABB SCHWEIZ AG
Reel/Frame 053537/0273 →
Priority Claims (1)
EP 17191639 · Sep 18, 2017 · regional
Continuity (2)
Continuation PCTEP2018074762 · Sep 13, 2018
Related Publication 20200218570A1 · Jul 9, 2020
References Cited (44)
US 5471253A · Nguyen · 1995 [cited by examiner]
US 5519709A · Albrecht et al. · 1996 [cited by applicant]
US 6133867A · Eberwine · 2000 [cited by examiner]
US 6633800B1 · Ward · 2003 [cited by examiner]
US 9871772B1 · Weinstein · 2018 [cited by examiner]
US 10924582B2 · Redmann · 2021 [cited by examiner]
US 20010047213A1 · Sepe, Jr. · 2001 [cited by examiner]
US 20030058135A1 · Kimmet · 2003 [cited by examiner]
US 20070064147A1 · Kondo · 2007 [cited by examiner]
US 20080229084A1 · Wei · 2008 [cited by examiner]
US 20090043941A1 · Brahmaroutu · 2009 [cited by examiner]
US 20090174362A1 · Richardson · 2009 [cited by examiner]
US 20100029117A1 · Underwood · 2010 [cited by examiner]
US 20100114404A1 · Donnelly · 2010 [cited by examiner]
US 20100161868A1 · Ueno · 2010 [cited by examiner]
US 20100195503A1 · Raleigh · 2010 [cited by applicant]
US 20100216509A1 · Riemer · 2010 [cited by examiner]
US 20110006880A1 · Long · 2011 [cited by examiner]
US 20120047291A1 · Davis · 2012 [cited by examiner]
US 20120185862A1 · Arcese · 2012 [cited by examiner]
US 20120317132A1 · Brady et al. · 2012 [cited by applicant]
US 20130103973A1 · Werth · 2013 [cited by examiner]
US 20130131837A1 · Washington · 2013 [cited by examiner]
US 20130318720A1 · Connell · 2013 [cited by examiner]
US 20140156030A1 · Okamoto · 2014 [cited by examiner]
US 20140277846A1 · Melster · 2014 [cited by examiner]
US 20150052308A1 · Ray · 2015 [cited by examiner]
US 20150220710A1 · Cherubini · 2015 [cited by examiner]
US 20160194014A1 · Rajendran · 2016 [cited by examiner]
US 20160212851A1 · Hu · 2016 [cited by examiner]
US 20170308080A1 · Brooks · 2017 [cited by examiner]
US 20180210440A1 · Matsuzaki · 2018 [cited by examiner]
US 20190036141A1 · Yamane · 2019 [cited by examiner]
US 20190093433A1 · Aguirre · 2019 [cited by examiner]
US 20200149204A1 · Xu · 2020 [cited by examiner]
JP 2003120984A · 2003 [cited by applicant]
JP 2007131275A · 2007 [cited by applicant]
JP 2009260712A · 2009 [cited by applicant]
JP 2014064256A · 2014 [cited by applicant]
European Patent Office, International Search Report & Written Opinion issued in corresponding Application No. PCT/EP2018/074762, mailed Nov. 13, 2018, 14 pp. [cited by applicant]
European Patent Office, Extended Search Report issued in corresponding Application No. 17191639.8, mailed Sep. 21, 2018, 10 pp. [cited by applicant]
Intellectual Property Office of Singapore, Invitation to Respond to Written Opinion and Written Opinion issued in corresponding Singaporean application No. 11202002054Q, dated Jun. 28, 2021, 7 pp. [cited by applicant]
Office Action, dated Nov. 12, 2021, from related European Patent App. No. 17191639.8. [cited by applicant]
Japan Office Action, issued by the Japanese Patent Office, mailed Aug. 3, 2021, regarding corresponding patent application Serial No. JP 2020-515921; 6 pages with translation. [cited by applicant]