Service Bus for Telecom Infrastructure Microservices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current telecom infrastructure lacks a scalable and flexible architecture that can efficiently manage multiple radio access technologies (RATs) and provide seamless network slicing, leading to limitations in resource allocation and service deployment in 5G networks.

Innovation Solution

A cloud-native Service Bus architecture is introduced, utilizing a messaging protocol and enterprise Service Bus design to coordinate multiple HetNet Gateways (HNGs), enabling multi-RAT coordination, load balancing, and zero-touch configuration across various RATs, including 2G, 3G, 4G, and 5G networks, with stateless and loosely coupled microservices for scalable and resilient operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a traditional monolithic telecom infrastructure architecture is used, then system stability is maintained, but scalability and flexibility are limited

Engineering Contradiction:
ImprovescalabilityVSAvoidarchitecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the monolithic telecom infrastructure into microservices that can be independently deployed, scaled, and managed. Each microservice handles specific network functions (e.g., authentication, routing, billing) as separate units, enabling granular scalability without requiring changes to the entire system architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal service bus architecture that can handle multiple radio access technologies (2G, 3G, 4G, 5G) and various network functions through a common platform. This multi-functional design allows the system to adapt to different technologies and requirements without requiring separate dedicated infrastructure for each.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple radio access technologies are integrated in a traditional architecture, then service coverage is expanded, but resource allocation efficiency decreases

Engineering Contradiction:
Improvemulti-RAT supportVSAvoidresource allocation efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent introduces a service bus as an intermediary layer between different radio access technology modules and the core network functions. This mediator enables efficient resource allocation by centralizing resource management and coordination, allowing dynamic allocation across 2G, 3G, 4G, and 5G networks based on demand without the inefficiencies of traditional point-to-point integrations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements dynamic parameter adjustment capabilities that allow the system to optimize resource allocation based on network conditions, traffic patterns, and service requirements. Parameters such as bandwidth allocation, priority levels, and quality of service thresholds can be changed in real-time to maximize efficiency across multiple RATs.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If network slicing is implemented in legacy infrastructure, then service differentiation is achieved, but deployment complexity increases

Engineering Contradiction:
Improvenetwork slicing capabilityVSAvoiddeployment ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent implements automated self-service capabilities for network slicing deployment through the service bus architecture. The system can automatically provision, configure, and manage network slices based on service level agreements and resource availability, eliminating the need for manual configuration and reducing deployment complexity while maintaining service differentiation.

Inventive Principle:
Principle #25Self-service

4Device complexity

If a centralized coordination approach is used for multiple HetNet Gateways, then control simplicity is maintained, but system resilience decreases

Engineering Contradiction:
Improvecoordination complexityVSAvoidsystem resilience
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the centralized coordination function into distributed coordination capabilities across multiple HetNet Gateways. Each gateway maintains independent coordination abilities and can operate autonomously if needed, while still participating in collective coordination through the service bus. This segmentation enhances resilience by eliminating single points of failure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic coordination modes that can adapt between centralized and distributed operation based on system conditions. The coordination architecture is flexible and can shift control responsibilities dynamically, allowing the system to maintain simplicity under normal conditions while providing resilience during failures or high-load scenarios.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11650862B2Service bus for telecom infrastructure
Publication Date: 2023.05.16 PARALLEL WIRELESS INC
  • US11650862B2 patent drawing
  • US11650862B2 patent drawing
  • US11650862B2 patent drawing

AI summary

Systems, methods and computer software are disclosed for providing a Service Bus for telecommunications infrastructure. The services bus provides a communications system between mutually interacting software applications, including a plurality of microservices, each microservice comprising: an internal bus; a data store in communication with the internal bus; a data access object in communication with the internal bus; a message exchange object in communication with the internal bus; a MAPReduce engine in communication with the internal bus; and a restful Application Programming Interface (API) bus in communication with the data access object, the message exchange object and the MAPReduce engine. The Service Bus provides a messaging service, a synchronization service and a persistence service, and routes messages between services, monitors and controls routing of message exchange between servers, resolves contention between communicating service components, controls deployment and versioning of services, marshals use of redundant services, and provides commodity services.