18521241. TENANT-CONTROLLED CLOUD UPDATES simplified abstract (MICROSOFT TECHNOLOGY LICENSING, LLC)

TENANT-CONTROLLED CLOUD UPDATES

Organization Name

MICROSOFT TECHNOLOGY LICENSING, LLC

Inventor(s)

Jiaxing Zhang of Beijing (CN)

Thomas Moscibroda of Beijing (CN)

Haoran Wang of Shanghai (CN)

Jurgen Aubrey Willis of Woodinville WA (US)

Yang Chen of Beijing (CN)

Ying Yan of Beijing (CN)

James E. Johnson of Bellevue WA (US)

Ajay Mani of Woodinville WA (US)

TENANT-CONTROLLED CLOUD UPDATES - A simplified explanation of the abstract

This abstract first appeared for US patent application 18521241 titled 'TENANT-CONTROLLED CLOUD UPDATES

Simplified Explanation

The patent application abstract describes systems and methods for allowing customers of a cloud computing service to control when updates affect the services provided to them. Conflicting preferences for update timing among multiple customers are addressed to reduce inconvenience and downtime associated with updates.

• Customers of a cloud computing service can control when updates affect the services provided to them.
• Conflicting preferences for update timing among multiple customers are resolved.
• Customers are provided with input for scheduling planned updates to reduce inconvenience.
• The update schedule is transmitted to customers so they can prepare for associated downtime.

Potential Applications

This technology could be applied in various cloud computing services to improve customer satisfaction and minimize service disruptions during updates.

Problems Solved

1. Conflicting preferences for update timing among multiple customers. 2. Inconvenience and downtime associated with updates.

Benefits

1. Improved customer satisfaction. 2. Reduced service disruptions. 3. Efficient update scheduling.

Potential Commercial Applications

Optimizing update scheduling in cloud computing services for enhanced customer experience and operational efficiency.

Possible Prior Art

There may be existing systems or methods in the field of cloud computing that address update scheduling and customer preferences, but specific prior art is not provided in this context.

How does this technology handle emergency updates that cannot be scheduled in advance?

The patent abstract does not mention how the system deals with urgent updates that cannot be planned in advance. This aspect could be crucial for ensuring service continuity during unforeseen circumstances.

What measures are in place to ensure the security and integrity of customer data during updates?

The abstract does not elaborate on the security protocols or data protection mechanisms implemented during updates. Addressing this aspect is essential to maintain customer trust and compliance with data privacy regulations.

Original Abstract Submitted

Systems and methods are taught for providing customers of a cloud computing service to control when updates affect the services provided to the customers. Because multiple customers share the cloud's infrastructure, each customer may have conflicting preferences for when an update and associated downtime occurs. Preventing and resolving conflicts between the preferences of multiple customers while providing them with input for scheduling a planned update may reduce the inconvenience posed by updates. Additionally, the schedule for the update may be transmitted to customers so that they can prepare for the downtime of services associated with the update.