Adrian Dragomir, 53416 7Th Ave, Kirkland, WA 98033

2010015, Jun 17, 2010

Dec 12, 2008

12/334314

Juan V. Esteve Balducci - Sammamish WA, US
John Allen Atwood - Duvall WA, US
Samuel Neely - Sammamish WA, US
Kevin Resnick - Olathe KS, US
Adrian Dragomir - Bellevue WA, US
Gregory A. Bolles - Snohomish WA, US
Katy Chia-wen Chen - Kirkland WA, US

Microsoft Corporation - Redmond WA

G06F 12/00
G06F 17/30

707610, 707E17055, 707E17046, 707E17005

The embodiments described herein generally relate to a method and system for synchronizing multiple classes with disparate schemas in a single collection through the use of the same synchronization request and/or synchronization key. A collection of different types of items may be synchronized while using the unique schema for each class. Further, different synchronization options, e.g., filtering, truncation, and body settings, may be applied to each class. In a synchronization request, an option block within a synchronization command notifies the server to synchronize the class specified in the option block. The option block may also specify the options, or settings, if any, to apply to the class. Multiple option blocks may be included in the synchronization command to specify the synchronization of multiple classes. Where multiple classes are specified, the server responds with the synchronized items of all such classes while maintaining each class's unique schema.

2010017, Jul 8, 2010

Jan 8, 2009

12/350892

Jeff West - Seattle WA, US
Mark Sievert Larsen - Redmond WA, US
Adrian Dragomir - Bellevue WA, US
Dennis Kiilerich - Seattle WA, US
Lingeshwaran Palaniappan - Bellevue WA, US
Renata van Diest - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 17/00
H04L 9/32

713183

A synchronization system includes a first account assigned a first unique identifier. Access to the first account is contingent on validation of a shared access credential. The synchronization system also includes a second account assigned a second unique identifier. Access to the second account is contingent on validation of the shared access credential. The synchronization system further includes a library of account operations. One or more account operations are configured to utilize the first unique identifier when addressing the first account, and one or more account operations are configured to utilize the second unique identifier when addressing the second account.

2012020, Aug 16, 2012

Jun 20, 2011

13/164678

Marc David McClure - Seattle WA, US
Abolade Gbadegesin - Seattle WA, US
Chittur Padmanabhan Subbaraman - Carnation WA, US
Jianping Yin - Sammamish WA, US
Jorge I. Raastroem - Issaquah WA, US
Yasser Shaaban - Seattle WA, US
Timothy Daniel Noonan - Cary NC, US
Rachel Jiang - Redmond WA, US
Peter John Torr - Bellevue WA, US
Vishal Ghotge - Seattle WA, US
Gregory Arthur de Souza - Seattle WA, US
Pavan Rajamohan Hullumane - Seattle WA, US
Adrian Dragomir - Bellevue WA, US
Darin Miller - Sammamish WA, US
Megan Galbraith Donahue - Seattle WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 15/173
G06F 15/16

709217, 709224

The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

2012026, Oct 18, 2012

Apr 13, 2011

13/085504

Ashutosh Tewari - Freemont CA, US
Adrian Dragomir - Bellevue WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 15/16

709201, 709230

An application using one version of a schematized XML protocol communicates with another application using a different version of the schematized XML protocol. The different versions may correspond to different deployments or releases of the protocol. Each application generates messages to be sent using two data sets. A first data set is incorporated into the message using elements available in a standard XML protocol schema. A second data set is incorporated into the message using XML annotation elements. The receiving application processes the message using the schematized XML protocol to parse out the first data set. The receiving application further parses the message to identify the second data set that is carried by enhanced XML annotation elements. Extension or annotations are flexibly added to the XML protocol without requiring the client application to request—or the server application to respond to—a pre-negotiated number or type of annotations.

2014007, Mar 13, 2014

Sep 10, 2012

13/608967

Adrian Dragomir - Bellevue WA, US
Anish Desai - Bellevue WA, US
Robert St. Pierre - Redmond WA, US
Marc McClure - Seattle WA, US
Kevin Grey - Bellevue WA, US
Jianping Yin - Sammamish WA, US

Microsoft Corporation - Redmond WA

H04L 29/06

713156

An invalid digital certificate can be saved and subsequently compared to an incoming digital certificate when performing a security check. If a subsequently provided digital certificate does not match the saved digital certificate, an error condition can be generated. Because a digital certificate can be invalid for non-malicious reasons, such technologies can be useful for improving software security.

2018035, Dec 6, 2018

Jun 6, 2018

16/001799

- Redmond WA, US
Abolade GBADEGESIN - Seattle WA, US
Chittur Padmanabhan SUBBARAMAN - Carnation WA, US
Jianping YIN - Sammamish WA, US
Jorge I. RAASTROEM - Issaquah WA, US
Yasser SHAABAN - Seattle WA, US
Timothy Daniel NOONAN - Cary NC, US
Rachel JIANG - Redmond WA, US
Peter John TORR - Bellevue WA, US
Vishal GHOTGE - Seattle WA, US
Gregory Arthur DE SOUZA - Seattle WA, US
Pavan Rajamohan HULLUMANE - Seattle WA, US
Adrian DRAGOMIR - Bellevue WA, US
Darin MILLER - Sammamish WA, US
Megan Galbraith DONAHUE - Seattle WA, US

H04W 52/02
G06F 9/54
H04N 21/61
H04N 21/439
H04N 21/233
H04W 4/60
H04W 4/50
H04L 12/24
H04N 21/41
G06F 9/50

The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

2018013, May 17, 2018

Dec 19, 2016

15/384303

- Redmond WA, US
Abolade Gbadegesin - Seattle WA, US
Chittur Padmanabhan Subbaraman - Carnation WA, US
Jianping Yin - Sammamish WA, US
Jorge I. Raastroem - Issaquah WA, US
Yasser Shaaban - Seattle WA, US
Timothy Daniel Noonan - Cary NC, US
Rachel Jiang - Redmond WA, US
Peter John Torr - Bellevue WA, US
Vishal Ghotge - Seattle WA, US
Gregory Arthur de Souza - Seattle WA, US
Pavan Rajamohan Hullumane - Seattle WA, US
Adrian Dragomir - Bellevue WA, US
Darin Miller - Sammamish WA, US
Megan Galbraith Donahue - Seattle WA, US

H04W 52/02
H04W 4/00
H04L 12/24

The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

2015030, Oct 22, 2015

Jun 30, 2015

14/755617

- Redmond WA, US
John Allen Atwood - Duvall WA, US
Samuel Neely - Sammamish WA, US
Kevin Resnick - Olathe KS, US
Adrian Dragomir - Bellevue WA, US
Gregory A. Bolles - Snohomish WA, US
Katy Chia-wen Chen - Kirkland WA, US

Microsoft Technology Licensing, LLC - Redmond WA

G06F 17/30
H04L 29/08
H04L 12/58

The embodiments described herein generally relate to a method and system for synchronizing multiple classes with disparate schemas in a single collection through the use of the same synchronization request and/or synchronization key. A collection of different types of items may be synchronized while using the unique schema for each class. Further, different synchronization options, e.g., filtering, truncation, and body settings, may be applied to each class. In a synchronization request, an option block within a synchronization command notifies the server to synchronize the class specified in the option block. The option block may also specify the options, or settings, if any, to apply to the class. Multiple option blocks may be included in the synchronization command to specify the synchronization of multiple classes. Where multiple classes are specified, the server responds with the synchronized items of all such classes while maintaining each class's unique schema.