Converged IP Messaging Server Service Type Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing messaging services, such as SMS, MMS, IM, and PoC, operate in silos due to technical differences, leading to fragmented user experiences and market confusion, with Converged IP Messaging (CPM) aiming to unify these services by enabling multimedia sessions, presence information management, and seamless interconnection across different systems.
Innovation Solution
A method and system for implementing Converged IP Messaging (CPM) that includes a CPM server capable of determining service types and performing corresponding signaling control, configuring media resources, and processing messages to provide unified messaging experiences across various services, including message delivery, session management, and interaction with third-party applications and non-CPM systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple separate messaging services (SMS, MMS, IM, PoC) are deployed to provide different messaging experiences, then each service can be optimized for its specific function, but the system complexity increases and user experience becomes fragmented
Solution Approach 1:
The patent combines multiple separate messaging services (SMS, MMS, IM, PoC) into a single unified messaging service platform. The service management entity consolidates service registration, discovery, and routing functions, while the access entity provides a unified interface for users to access all messaging types through a single service portal, eliminating the need for separate service deployments
Solution Approach 2:
The unified messaging service is designed to handle multiple messaging types (text, multimedia, instant messaging, push-to-talk) through a single service infrastructure. The service management entity and access entity work together to provide universal access to diverse messaging functions, allowing users to switch between different messaging modes without requiring separate service configurations
2Adaptability or versatility
If multiple separate messaging services are deployed to support different media types and communication modes, then service functionality is enhanced, but service integration and interoperability deteriorate
Solution Approach 1:
The service management entity acts as an intermediary between users and multiple messaging services. It receives service requests, determines the appropriate messaging type and target service, and routes requests accordingly. This mediator architecture ensures reliable integration and interoperability by centralizing service discovery, registration, and request routing, eliminating the need for direct integration between separate messaging systems
3Stability of the object's composition
If separate messaging services are maintained to preserve existing service characteristics, then service stability is maintained, but user experience unity deteriorates
Solution Approach 1:
The system architecture is segmented into distinct functional components: the service management entity handles service registration, discovery, and routing, while the access entity provides unified user access. This segmentation allows existing messaging services to maintain their individual characteristics and stability while presenting a unified interface to users through the access entity's service portal
4Ease of manufacture
If messaging services operate independently in silos, then each service can be managed separately, but service interoperability and seamless communication deteriorate
Solution Approach 1:
The service management entity serves as a mediator that enables interoperability between independently deployed messaging services. It maintains separate service registrations and characteristics while providing unified service discovery and request routing, allowing services to operate independently yet communicate seamlessly through the mediator's coordination
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method, a device and a system for converging IP message are disclosed, for overcoming the problems that the crossing of the technique ability, the overlap of the user application experience of the message service other than CPM and the existed interactive gaping between the message service other than CPM; the invention includes the following step: the CPM server that receives a CPM message determines its service type based on the CPM message and performs a corresponding signaling control, and processes the CPM message content based on the process flow corresponding with the service type; forwardly, the invention includes the following step: the CPM server that receives a CPM message determines its service type based on the CPM message, and determines the service server which can process this service based on the service type, and converses the CPM message to the message or / and session request corresponding with the service server, and transmits it to the service server to process, and after the CPM message of the service server is received, transmits the CPM message to the CPM client terminal. The application of the present invention improves the user's service experience.