IMS Service Routing Nodes for Dual-Slice Session Dispatch
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies lack a mechanism to dispatch terminating IMS service sessions, such as VoLTE and RCS, to the appropriate IMS slice in a communications network with dual IMS slices, leading to routing challenges in scenarios where IMS functions are separated and/or sliced.
Innovation Solution
A method involving nodes in a communications network that obtain routing service instances for specific IMS services, enabling them to route requests to the appropriate IMS slice based on obtained indications, utilizing the 3GPP Service Based Architecture (SBA) framework to simplify the architecture and processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IMS functions are separated into dual IMS slices, then service specialization and operational flexibility are improved, but routing complexity and configuration complexity increase
Solution Approach 1:
The patent introduces a Service Route Selection Application Server (S-RS-AS) as an intermediary component that receives service route selection requests from P-CSCF, determines the appropriate IMS slice based on service type, and returns routing information. This intermediary handles the complex routing logic centrally, preventing routing complexity from propagating throughout the entire IMS network while maintaining service specialization benefits
2Stability of the object's composition
If static configuration of diameter links is used, then routing stability is improved, but adaptability to service changes and deployment flexibility deteriorate
Solution Approach 1:
The patent implements dynamic routing where the S-RS-AS receives service route selection requests and determines routing information based on current service type and network state. Instead of static diameter link configuration, the system dynamically selects IMS slice instances through service route selection requests and responses, allowing routing to adapt to service changes while maintaining stability through structured interaction protocols
Solution Approach 2:
The system changes routing parameters dynamically by modifying service route selection requests to include service type information and changing routing responses based on determined IMS slice instances. This allows the routing configuration to adapt to different services (VoLTE, RCS, etc.) without requiring static pre-configuration, enabling both stability through consistent parameter structures and adaptability through parameter variations
3Manufacturing precision
If manual configuration and management of IMS slices is performed, then configuration precision is improved, but operational efficiency and time consumption deteriorate
Solution Approach 1:
The system implements self-service through automated service route selection where the S-RS-AS automatically determines appropriate IMS slice instances based on service type without requiring manual configuration. The P-CSCF automatically sends service route selection requests and processes responses, eliminating manual intervention while maintaining configuration precision through structured automated decision-making processes
4Reliability
If dual IMS networks are deployed for different services, then service isolation and reliability are improved, but network complexity and resource requirements increase
Solution Approach 1:
The S-RS-AS serves multiple functions: receiving service route selection requests, determining appropriate IMS slice instances, and returning routing information. This universal component handles routing for multiple services (VoLTE, RCS, etc.) through a single structured interface, reducing network complexity while maintaining service isolation and reliability through functionally separated IMS slices
Data Source
Figure 1a~1b
Figure 2~3
Figure 4
AI summary
A method, by a first node (111), for handling provision of an IMS service. A communications network (10) comprises a first slice handling a first IMS service, and a 5second slice handling a second IMS service. The first node (111) obtains (202), from a second node (112) at least one of a first and a second indication. The first indication is of a first routing service instance for a third node (113) handling the first service in the first slice. The second indication is of a second routing service instance for a fourth node (114) handling the second service in the second slice. The first node (111) then routes 10(204) a request, to one of the nodes. With the proviso that the request is for the first service, the routing (204) is based on the first indication. With the proviso that the request is for the second service, the routing (204) is based on the second indication.