Tag-Based Application Selection for Reliable Network Connections
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity and resource consumption of establishing network connections between different service networks with varying environments are high, and scalability is limited due to the need for complex and differentiated implementation logic of external service interfaces, leading to instability and unreliable network services.
Innovation Solution
A method and apparatus that select and delete application instances based on tags and exclusion information, determining target instances with real-time running status to establish network connections, ensuring high reliability and reduced resource consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If external service interfaces are used to establish network connections between different service networks, then network connectivity is achieved, but implementation logic becomes complicated and resource consumption increases
Solution Approach 1:
The patent applies homogeneity by using a unified tag-based selection mechanism for application instances across different network environments. Instead of implementing different logic for different network scenarios, the system uses consistent tag matching and exclusion rules to select target application instances, simplifying the implementation while maintaining reliability across diverse service networks.
Solution Approach 2:
The patent changes parameters by introducing tag-based identification and exclusion criteria for application instances. Rather than complex conditional logic, the system uses configurable tags and exclusion rules that can be adjusted without changing the underlying connection establishment mechanism, reducing implementation complexity while maintaining connection reliability.
2Adaptability or versatility
If external service interfaces are invoked for each network connection, then different network environments are supported, but resource consumption becomes too high
Solution Approach 1:
The patent applies preliminary action by pre-configuring tags and exclusion rules for application instances before network connection establishment. The system prepares the selection criteria in advance, allowing the connection process to simply match tags and apply exclusion rules rather than performing complex evaluations, thereby reducing resource consumption while maintaining adaptability to different network environments.
Solution Approach 2:
The patent implements universality by creating a multi-functional tag-based selection mechanism that works across all network environments. The same tag matching and exclusion logic serves multiple purposes: selecting application instances, filtering inappropriate targets, and adapting to different service networks, thereby reducing resource consumption while maintaining broad adaptability.
3Reliability
If complex implementation logic is used to handle different network environments, then connection establishment is possible, but scalability is limited
Solution Approach 1:
The patent applies dynamics by making the system configurable through tags and exclusion rules that can be dynamically adjusted without changing the underlying architecture. New service networks and application instances can be integrated by simply assigning appropriate tags and exclusion criteria, enabling the system to scale while maintaining reliable connection establishment through the same dynamic mechanism.
Data Source
AI summary
A method includes selecting, based on selectable tag(s) carried by a network connection object, selectable application instance(s) corresponding to the selectable tag(s), respectively, from original application instance(s); selecting excludable application instance(s) from the original application instance(s) based on exclusion indication information carried by the network connection object; deleting one or more of the selectable application instance(s) based on the excludable application instance(s), to obtain candidate application instance(s) associated with a first service network and a second service network; selecting, based on a running status corresponding to each of the candidate application instance(s), target application instance(s) that meet a running condition, from the candidate application instance(s); and establishing, by the controller, a network connection between the first service network and the second service network based on the target application instance(s).


