The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.

The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.

Date of Patent:
Jul. 26, 2022

Filed:

Dec. 04, 2018
Applicant:

Microsoft Technology Licensing, Llc, Redmond, WA (US);

Inventors:

Karthik Raman, Sammamish, WA (US);

Momin Mahmoud Al-Ghosien, Sammamish, WA (US);

Bhalakumaaran Erode Ranganathan, Bellevue, WA (US);

Madhan Gajendran, Bengaluru, IN;

Ji Huang, Bothell, WA (US);

Atul Katiyar, Sammamish, WA (US);

Mikhail Mikhailovich Koltachev, Redmond, WA (US);

Sujit Vattathil Kuruvilla, Redmond, WA (US);

Digvijaysinh Govindbhai Makwana, Seattle, WA (US);

Subramanyam Pattipaka, Bellevue, WA (US);

Ovidiu Constantin Platon, Redmond, WA (US);

Ankur Savailal Shah, Redmond, WA (US);

Pankaj Sharma, Kirkland, WA (US);

Dharma Shukla, Bellevue, WA (US);

Shreshth Singhal, Seattle, WA (US);

Shireesh Kumar Thota, Redmond, WA (US);

Assignee:
Attorneys:
Primary Examiner:
Int. Cl.
CPC ...
G06F 17/00 (2019.01); G06F 16/23 (2019.01); G06F 16/27 (2019.01); G06F 11/20 (2006.01); G06F 16/22 (2019.01); G06F 16/2452 (2019.01); G06F 16/28 (2019.01); G06F 16/25 (2019.01); G06F 16/21 (2019.01); H04L 67/1008 (2022.01); G06F 9/50 (2006.01); H04L 41/0896 (2022.01); H04L 41/5009 (2022.01); H04L 47/72 (2022.01); H04L 47/762 (2022.01); G06F 16/182 (2019.01); G06F 16/903 (2019.01); H04L 41/5019 (2022.01); H04L 67/1012 (2022.01); H04L 67/1034 (2022.01); H04L 41/0803 (2022.01); H04L 41/5022 (2022.01); H04L 41/50 (2022.01); H04L 69/24 (2022.01); H04L 67/1029 (2022.01);
U.S. Cl.
CPC ...
G06F 16/2365 (2019.01); G06F 9/5077 (2013.01); G06F 11/2007 (2013.01); G06F 11/2023 (2013.01); G06F 11/2056 (2013.01); G06F 16/184 (2019.01); G06F 16/211 (2019.01); G06F 16/219 (2019.01); G06F 16/2246 (2019.01); G06F 16/2255 (2019.01); G06F 16/2272 (2019.01); G06F 16/2315 (2019.01); G06F 16/2322 (2019.01); G06F 16/2329 (2019.01); G06F 16/2336 (2019.01); G06F 16/2452 (2019.01); G06F 16/252 (2019.01); G06F 16/258 (2019.01); G06F 16/27 (2019.01); G06F 16/28 (2019.01); G06F 16/903 (2019.01); H04L 41/0803 (2013.01); H04L 41/0896 (2013.01); H04L 41/5009 (2013.01); H04L 41/5019 (2013.01); H04L 41/5022 (2013.01); H04L 41/5032 (2013.01); H04L 47/72 (2013.01); H04L 47/762 (2013.01); H04L 67/1008 (2013.01); H04L 67/1012 (2013.01); H04L 67/1034 (2013.01); H04L 69/24 (2013.01); G06F 2201/80 (2013.01); H04L 67/1029 (2013.01);
Abstract

A server set for a data set may designate a subset of 'master' servers that update the data set in order to reduce data version conflicts involving mutually exclusive updates of the data set. Multi-master configurations may fulfill the performance constraints, and the subset of masters may detect and resolve data version conflicts. However, if multiple masters perform conflict resolution for a particular data version conflict, the resolution may produce inefficiency and redundancy (if the masters reach the same outcome) or additional data version conflicts (if the masters reach different outcomes). Instead, among the masters, a merge master may be identified that applies conflict resolution techniques to data version conflicts and forwards the conflict resolution outcome to the other masters for application to the data set to resolve the data version conflict. The other masters may temporarily store updates in a tentative update set until data version conflicts are resolved.


Find Patent Forward Citations

Loading…