Correlation ID Message Sequencing for Enterprise Service Requests

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Telecommunications service providers face challenges in managing complex service requests across multiple applications and geographic locations, leading to increased costs, human intervention, and potential errors due to the complexity of provisioning services and the need for precise execution sequences.

Innovation Solution

A system and method for synchronizing data through a flow of multiple messages that require a precise execution sequence, using correlation IDs to manage interdependent messages, and employing integration middleware technology to handle service requests generated by external consumers, ensuring related requests follow a defined business logic sequence.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple distinct software applications are implemented to handle service requests across different geographic locations, then the service provider can manage complex provisioning tasks, but the system complexity and implementation cost increase significantly

Engineering Contradiction:

Improveability to manage service requests across multiple applications and geographic locationsVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (correlation ID mechanism and message sequencing system) that mediates between multiple distinct software applications. This intermediary manages the complexity of coordinating service requests across different applications and geographic locations without requiring the applications themselves to be highly complex. The correlation ID acts as a mediator to track and sequence messages across the distributed system.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If human intervention is used to manage service requests, then errors can be identified and corrected, but the cost and time required for service provisioning increase

Engineering Contradiction:

Improveerror detection and correctionVSAvoidservice provisioning time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a feedback mechanism through correlation IDs that allow the system to track service request status and send notifications when messages are processed. This automated feedback loop enables the system to detect and correct errors without requiring continuous human intervention, while maintaining fast service provisioning speeds. The notification system provides feedback to stakeholders when service requests are completed or encounter issues.

Inventive Principle:

Principle #23Feedback

3Productivity

If service requests are processed without a defined execution sequence, then processing speed increases, but errors occur and profits are lost

Engineering Contradiction:

Improveprocessing speedVSAvoidexecution accuracy

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by defining the required execution sequence for service requests before processing begins. The system determines the correct order of operations in advance and enforces this sequence through correlation ID tracking and message sequencing mechanisms. This preliminary sequencing prevents errors during execution while maintaining high processing speeds through automated sequence enforcement.

Inventive Principle:

Principle #10Preliminary action

4Adaptability or versatility

If different software tools and platforms are used across the enterprise, then existing infrastructure can be leveraged, but integration difficulty and training requirements increase

Engineering Contradiction:

Improveuse of existing software tools and platformsVSAvoidintegration ease

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent segments the service request processing into distinct, manageable components that can be handled by different software tools and platforms. Each component processes specific parts of the service request and communicates through standardized correlation ID messages. This segmentation allows the system to leverage existing infrastructure while reducing integration complexity through modular, independent processing units.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS9152937B2Message sequence management of enterprise based correlated events

Publication Date: 2015.10.06 ACCENTURE GLOBAL SERVICES LTD

AI summary

A message sequence management of enterprise based correlated events incorporates the changing and unique business of a telecommunications service provider with minimal configurations. The design identifies and manages related service requests and ensures that related service requests follow a precise execution sequence as defined by the business logic. The design's robust features allows for simplified integration and management to changing business processes and needs.