Targeted Release Update Deployment Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud-based service update deployment methods are inflexible and do not account for customers with pre-deployment requirements (PDRs) such as compliance assessments and validation tasks, leading to manual and labor-intensive updates for these customers.

Innovation Solution

A flexible targeted release (TR) deployment framework that segregates subsets of users to complete PDRs before updates are rolled out to the entire userbase, allowing TR customers to be associated with different rings or waves and enabling customizable update sequencing to ensure compliance and user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If ring deployment techniques are used to deploy updates to cloud service customers, then updates can be rolled out in controlled stages to mitigate deployment risk, but customers with pre-deployment requirements cannot complete compliance assessments and validation tasks before update deployment

Engineering Contradiction:
Improvedeployment risk mitigationVSAvoidaccommodation of pre-deployment requirements
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the customer base into two distinct categories: targeted release customers who have pre-deployment requirements and must complete compliance assessments and validation tasks before update deployment, and non-targeted release customers who receive updates through standard ring deployment. This segmentation allows the system to handle different deployment scenarios with appropriate processes for each customer type, resolving the contradiction between maintaining controlled deployment and accommodating special requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary actions by requiring targeted release customers to complete pre-deployment tasks (compliance assessments, validation tasks, documentation requirements) before updates are deployed to their userbases. The system tracks completion status of these preliminary tasks and only permits update deployment after they are satisfied, ensuring that customers with regulatory or quality requirements can perform necessary preparations before receiving updates.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual processes are used to deploy updates to customers with pre-deployment requirements, then compliance and validation tasks can be ensured, but the deployment process becomes labor-intensive and inefficient

Engineering Contradiction:
Improvecompliance assuranceVSAvoiddeployment efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements self-service mechanisms where targeted release customers independently complete their own pre-deployment tasks (compliance assessments, validation tasks, documentation) through automated interfaces provided by the system. The system automatically tracks completion status and manages the deployment process based on this status, eliminating the need for manual intervention while ensuring compliance requirements are met, thus maintaining reliability while improving productivity.

Inventive Principle:
Principle #25Self-service

3Speed

If updates are deployed to all customers simultaneously, then deployment speed is maximized, but the risk of negative user experience impacts increases for customers who have not completed pre-deployment requirements

Engineering Contradiction:
Improvedeployment speedVSAvoiduser experience quality
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent ensures that targeted release customers complete pre-deployment tasks (compliance assessments, validation tasks) before updates are deployed to their userbases. This preliminary action prevents potential user experience issues by verifying that customers are ready for the update, while the system manages this process efficiently to minimize deployment delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies different deployment strategies to different customer segments: targeted release customers receive updates only after completing pre-deployment requirements, while non-targeted release customers receive updates through standard ring deployment. This localized quality approach ensures that each customer group receives updates through the most appropriate process for their specific needs, maintaining both speed and reliability.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12032942B2Targeted release updates for cloud service deployments
Publication Date: 2024.07.09 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12032942B2 patent drawing
  • US12032942B2 patent drawing
  • US12032942B2 patent drawing

AI summary

A data processing system implements scalable, secure, and reliable targeted release (TR) deployments of updates in cloud-based service. The TR deployment framework is provided that solves the technical problem of facilitating deployment of updates to targeted release customers. TR customers are associated with pre-deployment requirements (PDRs) associated with accreditation and/or validation tasks that must be completed before the update may be deployed to the customer base of the TR customers. A subset of the TR customer base is provided with segregated access to complete these accreditation tasks and/or validation tasks before the update is provided to the remainder of the userbase of the TR customer. This approach ensures that the industry standards and/or customer requirements are met before the update is deployed to the entire userbase of the TR customer.