MaaP Direct Network Node Interfaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Rich Communication Services (RCS) platforms fail to directly connect Messaging as a Platform (MaaP) to network nodes such as online charging systems, Policy and Charging Rules Function, Equipment Identity Register, Cloud Database, and Home Subscriber Server, leading to inefficiencies and potential security issues.
Innovation Solution
The enhanced MaaP directly interfaces with these network nodes without relying on a middle layer or RCS as an intermediary, allowing for direct communication and configuration through user-friendly interfaces and APIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If RCS is used as an intermediary layer between MaaP and network nodes, then the system architecture is simplified and easier to implement, but the communication efficiency decreases and security risks increase due to additional middle layers
Solution Approach 1:
The patent extracts and removes the RCS intermediary layer from the communication path between MaaP and network nodes. By taking out this middle layer, the system achieves direct communication between MaaP and network nodes (HSS, EIR, OCS, PCRF, CDB), eliminating the inefficiencies and security risks associated with the intermediary while maintaining architectural simplicity through direct connections.
2Device complexity
If RCS intermediary layer is used, then implementation complexity is reduced, but the system becomes more vulnerable to hacking and synchronization failures
Solution Approach 1:
The patent removes the RCS intermediary layer that introduces security vulnerabilities and synchronization issues. By extracting this problematic middle layer, the system establishes direct, secure connections between MaaP and network nodes, eliminating the attack surface and synchronization failures that occurred through the intermediary while keeping the overall implementation straightforward through standardized direct interfaces.
3Productivity
If direct interfaces are added between MaaP and network nodes, then communication efficiency and security are improved, but the device complexity increases
Solution Approach 1:
The patent implements universal, standardized direct interfaces between MaaP and multiple network nodes (HSS, EIR, OCS, PCRF, CDB). These multi-functional interfaces handle various communication tasks efficiently, reducing the need for separate specialized connections. This universality approach improves communication efficiency while controlling system complexity through standardized protocols and reusable interface designs.
4Measurement precision
If direct communication channels are established, then synchronization accuracy between MaaP and network nodes is improved, but the system complexity increases
Solution Approach 1:
The patent removes the RCS intermediary layer that caused synchronization delays and inaccuracies. By establishing direct communication channels between MaaP and network nodes, the system achieves real-time, accurate synchronization. The complexity is managed through standardized direct interfaces that use efficient protocols, eliminating the need for complex synchronization mechanisms that would be required to compensate for intermediary-induced delays.
Data Source
AI summary
Aspects of the invention enhance the capabilities of the Message as a Platform (“MaaP”) by adding interfaces thereto so that the platform directly interfaces with the Online Charging System (“OCS”), the Policy and Charging Rules Function (“PCRF”), the Equipment Identity Register (“EIR”), the Cloud Database (“COB”) and the Home Subscriber Server (“HSS”) without middle layer or without using Rich Communication Services (“RCS”) as an intermediary. Moreover, embodiments of the invention may create a user interface of the MaaP so that users may configure parameters to interact with the network nodes right from the user interface.