RAN Rules Engine for Custom Radio Resource Strategies
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems lack flexibility and customization in managing radio resources for user equipment, requiring complex and time-consuming processes to adapt operator-defined strategies, and suffer from inflexible software solutions that do not efficiently manage radio resource management, carrier aggregation, dual connectivity, and mobility handovers.
Innovation Solution
A method and system utilizing an open-source expert system with a rules engine programmed via LISP, Python, or Java to implement operator-defined rules for managing radio resources, allowing customizable strategies through a configurable interface, decoupling software logic from the wireless communication system, and enabling rapid adaptation to operator needs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If fixed set of codes (logic) are baked into RAN software to manage UE strategies, then the system provides stable and reliable radio resource management, but the system loses flexibility and customization capability for operator-specific strategies
Solution Approach 1:
The patent segments the radio resource management system into two independent parts: a fixed RAN software layer that provides stable execution, and a separate configurable rule engine layer that enables operator-specific customization. The rule engine is decoupled from the core RAN software, allowing operators to define and modify strategies without affecting the stability of the underlying system.
Solution Approach 2:
The patent introduces a rule engine as an intermediary layer between the operator's strategic requirements and the RAN software execution. This rule engine acts as a mediator that translates operator-defined strategies into executable logic, enabling customization while maintaining the stability of the core RAN system.
2Adaptability or versatility
If multiple nested logics are created to customize operator strategies, then the system can accommodate diverse operator requirements, but the complexity of the system increases significantly
Solution Approach 1:
The patent extracts the customization logic from the core RAN software and places it in a separate rule engine. This extraction eliminates the need for multiple nested logics within the RAN software itself, as operators can define their strategies in the external rule engine using a simplified configuration interface.
Solution Approach 2:
The patent creates a universal rule engine that can handle diverse operator strategies through a single, unified configuration interface. Instead of requiring different nested logic structures for different operators, the rule engine provides a multi-functional platform that accommodates various operator requirements through configurable rules.
3Adaptability or versatility
If custom-defined solutions are implemented within closed RAN architecture, then operator-specific strategies can be deployed, but the solutions become inflexible and difficult to adapt to changing operator needs
Solution Approach 1:
The patent implements a dynamic rule engine that allows operator strategies to be modified and updated without requiring changes to the underlying RAN software. The configurable interface enables operators to dynamically adjust strategies in response to changing requirements, making the system both deployable and adaptable.
4Adaptability or versatility
If decision tree complexity grows to incorporate multiple operator strategies, then comprehensive coverage of operator needs is achieved, but processing logic in RAN software becomes overloaded
Solution Approach 1:
The patent extracts the decision tree logic from the RAN software processing load and relocates it to the external rule engine. This extraction prevents processing logic overload in the RAN software while maintaining comprehensive coverage of operator strategies through the rule engine's configurable decision-making capabilities.
Data Source
AI summary
A method and a system of configuring custom operator defined rules for managing radio resources of user equipment in a wireless communication system. The system includes a plurality of User Equipment (UE), a plurality of wireless base stations configured to host Centralized Unit (CU) and Distributed Unit (DU) software, a rules engine, a first Application Programming Interface (API) wherein the rules engine is programmed with operator defined rules via the first API, and a second API coupled with the CU and DU software and configured to invoke the rules engine upon an occurrence of one or more defined events, wherein one or more of the operator defined rules is invoked via API calls to execute operator defined rules that match one or more inputs provided by at least one of the CU and DU hosted by at least one of the plurality of base stations.