Protocol Interoperability Gateway for Mobile Subscriber Units
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in providing interoperability between different communication protocols, such as Simple Common Air Interface Encapsulation Protocol (SCEP) and Sub-Network Dependent Convergence Protocol (SNDCP), requiring costly infrastructure replacement when migrating from one protocol to another.
Innovation Solution
A method that determines the protocol difference between a mobile subscriber unit and a packet-data subsystem, creates context information, and encapsulates data packets with a header associated with the second protocol, enabling seamless communication across protocols without replacing infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a subscriber unit employs SCEP protocol, then it can communicate with SCEP infrastructure system, but it cannot communicate with SNDCP infrastructure system
Solution Approach 1:
A gateway device is introduced as an intermediary between SCEP subscriber units and SNDCP infrastructure systems. The gateway performs protocol conversion by receiving SCEP packets, translating them to SNDCP format, and forwarding to the SNDCP system. This mediator enables communication between incompatible protocols without requiring changes to the existing subscriber units or core infrastructure.
Solution Approach 2:
The gateway device changes protocol parameters by transforming packet structures, header formats, and data encoding schemes between SCEP and SNDCP. It modifies communication parameters such as address formats, data rates, and protocol handshaking sequences to enable interoperability while maintaining the original functionality of both systems.
2Adaptability or versatility
If the infrastructure system is migrated from SCEP to SNDCP protocol, then newer protocol capabilities are achieved, but all subscriber units must be replaced
Solution Approach 1:
The system is segmented into three independent parts: SCEP subscriber units, the gateway device for protocol conversion, and the SNDCP core network. This segmentation allows each component to evolve independently - subscriber units remain unchanged, the gateway handles protocol translation, and the core network adopts the newer SNDCP protocol, thereby avoiding complete system replacement.
Solution Approach 2:
The gateway acts as a transitional intermediary that enables gradual protocol migration. It allows the infrastructure to adopt SNDCP while maintaining compatibility with existing SCEP subscriber units, thus avoiding the need for simultaneous replacement of all subscriber units and enabling phased migration strategies.
3Adaptability or versatility
If multiple protocols are supported on the same channel, then interoperability is improved, but system complexity increases
Solution Approach 1:
The gateway concentrates multi-protocol handling capability in a single intermediary device rather than requiring each network element to support multiple protocols. This centralizes the complexity in the gateway while keeping subscriber units and core network elements simple and protocol-specific.
Solution Approach 2:
The gateway device is designed with universal functionality to handle multiple protocol types (SCEP, SNDCP, and potentially others). It implements a universal packet processing architecture that can translate between different protocols, making the gateway itself multi-functional while other system components remain specialized and simple.
Data Source
AI summary
The application discloses a method and apparatus for providing interoperability for a mobile subscriber unit (MSU), employing a first protocol e.g., SCEP, with a packet-data subsystem operating at a second protocol e.g., SNDCP. The method includes determining that the first protocol employed by the MSU is different from the second protocol operated by the packet data subsystem. The method then includes creating a context information for the MSU when the determined first protocol is different from the second protocol. Further, the method includes determining a header associated with the second protocol based on the created context information and then receiving at least one data packet associated with the first protocol from the MSU. The method then encapsulates the at least one data packet with the determined header associated with the second protocol. The method then transmits the at least one encapsulated data packet to the communication network through a context manager.