IBC Framework for Cross-System Business Entity Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in establishing and maintaining communication connections between business entities across different computing systems, as direct logical addressing is not feasible, and routing information needs frequent updates with changes in technical infrastructure.
Innovation Solution
The Identifiable Business Context (IBC) framework identifies routing rules in a database, generates an IBCR with unique identifiers and business data attributes, and establishes communication connections using defined protocols, allowing secure and stable communication between business entities regardless of system boundaries and infrastructure changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If direct logical addressing is used to locate business entities within the same computing system, then addressing is simple and direct, but it becomes infeasible when business entities are located in other computing systems
Solution Approach 1:
The patent introduces routing information as an intermediary mechanism that mediates communication between business entities in different computing systems. The routing information contains sender and recipient business entity identifiers that enable indirect addressing across system boundaries, resolving the contradiction between simple logical addressing within a system and the need for cross-system addressing capability.
2Adaptability or versatility
If routing information is configured to connect to other computing systems, then communication between systems is enabled, but routing information needs frequent updates when technical infrastructure changes
Solution Approach 1:
The patent implements dynamic routing information that can be automatically updated and regenerated. The system determines routing information based on current technical infrastructure state, allowing routing configurations to adapt dynamically when infrastructure changes occur, reducing manual maintenance complexity while preserving cross-system communication capability.
Solution Approach 2:
The patent performs preliminary determination of routing information before actual communication occurs. By pre-configuring routing rules and business entity mappings, the system prepares routing paths in advance, reducing the complexity of real-time routing decisions and minimizing the impact of infrastructure changes through pre-established fallback routes.
3Loss of information
If sender and recipient business entity information is included in the payload message, then business entities can be identified in computing systems, but authentication becomes difficult to implement
Solution Approach 1:
The patent uses routing information as an intermediary layer that separates business entity identification from authentication. Instead of including sensitive authentication data directly in payload messages, the system uses routing information to establish authenticated communication channels, thereby maintaining business entity identification capability while improving authentication security through a dedicated intermediary mechanism.
Data Source
AI summary
Techniques for managing information exchange between business entities include identifying a plurality of routing rules stored in a database of a first business entity computing system; receiving a request for a business transaction through an application of a plurality of applications of the first business entity computing system; determining, based on the identified routing rules, an identifiable business context reference (IBCR) associated with a second business entity computing system, the IBC comprising a unique identifier associated with the second business entity and a first plurality of business data attributes associated with the second business entity; determining, based on the identified IBCR, a communication connection associated with the IBC and an identifiable business context (IBC) associated with the first business entity computing system; and initiating the business transaction between the first business entity computing system and the second business entity computing system through the determined communication connection.