Cross-Layer Controller Connections Using Boundary Resource Identifiers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current cross-layer and peer-to-peer management and control systems lack clarity in the process and interface for initiating cross-layer connection interactions, leading to weak connection establishment capabilities and challenging system scheduling.

Innovation Solution

A connection interaction method involving a first controller sending a connection creation request with a boundary resource identifier to a second controller, followed by the second controller establishing a connection and sending a success message, clarifying the interaction process and enhancing connection establishment capability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a cross-layer management and control system is implemented with multiple controllers, then comprehensive management and control services can be provided, but the process and interface for initiating cross-layer connection interactions become unclear

Engineering Contradiction:

Improvecomprehensive management and control servicesVSAvoidprocess and interface complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the connection establishment process into distinct phases: connection request initiation, boundary resource identifier generation, connection establishment execution, and confirmation feedback. Each controller has clearly defined responsibilities for specific segments of the process, making the overall complex interaction manageable and understandable.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The boundary resource identifier acts as an intermediary element that facilitates communication between controllers of different layers. This standardized identifier enables clear interface definition and simplifies the interaction process by providing a common language for resource reference across layer boundaries.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If peer-to-peer controller interactions are enabled, then direct control between controllers is achieved, but the connection establishment process becomes ambiguous

Engineering Contradiction:

Improvedirect control capabilityVSAvoidconnection establishment process

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces specific parameters including boundary resource identifiers, connection request messages, and confirmation messages that standardize the peer-to-peer interaction. These parameter changes transform ambiguous direct control into a structured process with defined message exchanges and state transitions.

Inventive Principle:

Principle #35Parameter changes

3Productivity

If connection establishment capability is enhanced across multiple server-layer controllers, then system scheduling is improved, but the interface clarity requirement increases

Engineering Contradiction:

Improvesystem scheduling efficiencyVSAvoidinterface definition

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal interface mechanism that works across all server-layer controllers regardless of their specific functions. The boundary resource identifier and standardized message exchange protocol provide multi-functional capability, enabling the same interface to support various types of cross-layer connections and resource allocations.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250310409A1Connection interaction method, communication device, storage medium, and program product

Publication Date: 2025.10.02 ZTE CORP

AI summary

Embodiments of this application provide a connection interaction method, a communication device, a storage medium, and a program product. The connection interaction method includes: sending, by a first controller, a connection creation request carrying a boundary resource identifier to a second controller; then, establishing, by the second controller, a connection according to the boundary resource identifier; subsequently, generating, by the second controller, a connection establishment success message carrying the boundary resource identifier, and sending the connection establishment success message to the first controller; and finally, determining, by the first controller, a successful connection establishment according to the boundary resource identifier.