Remote Procedure Call Agent for SDN Controller Cross-Language Interaction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing SDN technologies face challenges in enabling direct interaction between applications (APPs) and SDN controllers across different programming languages, as well as across different hosts, due to differences in programming languages and distributed architectures.
Innovation Solution
A method and system for implementing remote procedure calls (RPCs) that include an agent module, conversion modules, and transceiver modules to convert and transmit parameters between APP clients and SDN controllers in a preset protocol format, allowing for cross-language and cross-host communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If applications are developed with different programming languages (e.g., PYTHON) while the SDN controller is developed with JAVA, then application development flexibility is improved, but direct interaction between applications and SDN controller becomes impossible
Solution Approach 1:
The patent introduces an intermediary layer (service interface with conversion modules) between applications and the SDN controller. This intermediary translates requests from different programming languages into a common protocol format, enabling cross-language communication while maintaining the SDN controller's original JAVA implementation. The service interface acts as a mediator that converts application-specific data formats into standardized RPC protocols.
2Adaptability or versatility
If applications and SDN controller are distributed on different hosts, then system scalability and deployment flexibility are improved, but remote interaction across nodes cannot be performed
Solution Approach 1:
The patent replaces direct mechanical/protocol-level communication requirements with a standardized remote procedure call mechanism. By defining service interfaces and using RPC protocols, the system enables remote hosts to interact through standardized message passing rather than requiring direct protocol compatibility. This substitution of communication mechanisms allows distributed deployment while maintaining interaction capability.
3Adaptability or versatility
If a service interface with conversion modules is introduced to enable cross-language communication, then interaction capability between different programming languages is improved, but system complexity increases
Solution Approach 1:
The patent segments the system into distinct functional modules: application layer, service interface layer with conversion modules, and SDN controller layer. This segmentation isolates the complexity of language conversion to a specific intermediate layer, allowing the upper and lower layers to remain simple and language-agnostic. Each segment has a specific responsibility, making the overall system more manageable despite the added conversion capability.
Data Source
Figure 1~3
Figure 4~5
AI summary
The present application discloses a method and device for implementing remote procedure call. The method includes: calling, by a client, a service interface of a Software Defined Networking, SDN, controller and converting a first input parameter of the service interface into a second input parameter in a preset protocol format; and converting, by the client, the second input parameter into request information conforming to a remote procedure call protocol, RPC, and sending the same to the SDN controller.