Method for realizing MCPTT service multi-service deployment and capacity expansion based on IFC rule
By configuring differentiated IFC rules for the MCX system and dynamically routing user requests to the sipserver service, the problems of wasted resources and complexity during MCX system expansion are solved, achieving efficient and low-cost load balancing and expansion, and improving system stability.
Patent Information
- Application Number
- CN202511681665.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-17
- Publication Date
- 2026-02-13
AI Technical Summary
Existing MCX systems lack fine-grained traffic scheduling capabilities when facing capacity bottlenecks, leading to wasteful resource expansion and complex architecture, high investment costs, and difficult maintenance.
By configuring differentiated IFC rules for different user groups, user service requests are dynamically routed to different sipserver services, enabling precise scaling and load balancing of the MCX system. This leverages the routing and distribution capabilities of the IMS core network to avoid redundant deployment of the complete MCX system.
It achieves precise system expansion and efficient resource utilization, reduces hardware costs, increases system capacity and business load capacity, simplifies operation and maintenance processes, and has flexibility and adaptability.
Smart Images
Figure CN121530951A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of wireless communication network management technology, and relates to a method for deploying and expanding MCPTT services based on IFC rules. Background Technology
[0002] The MCX system, or critical communication system, is a core application built on the IMS network (IP Multimedia Subsystem network). Its service triggering and routing fully comply with the existing service control mechanisms of IMS. In the IMS architecture, the IFC rule (Initial Filtering rule) is the core policy rule for implementing service triggering. It is executed by the SSCCF (Service-Call Session Control Function) when processing SIP sessions such as user registration and calls to determine whether and how to route signaling to a specific AS (Application Server).
[0003] Currently, in standard MCX system deployments, all users are typically configured to subscribe to the same IFC rule template, which treats the entire MCX system as a unified AS for triggering. While this system-level IFC configuration scheme can meet basic business triggering requirements, its design is only intended to differentiate between different business systems, without considering the load balancing issue among multiple instances of the same service within a single business system.
[0004] When an MCX system faces capacity bottlenecks, existing technologies lack the ability to finely utilize IFC rules. Because all user service requests are routed to a single MCX system entry point through the same IFC rule, the system cannot leverage the inherent routing and distribution capabilities of the IMS core network to direct service traffic to different service instances. This limitation prevents the potential value of IFC rules in system expansion scenarios from being effectively realized. The system is forced to adopt a crude expansion approach, deploying multiple complete MCX systems and configuring different IFC rules for each, resulting in resource waste and architectural complexity. This leads to a series of subsequent problems, including high investment costs, long investment cycles, and significant maintenance difficulties.
[0005] Therefore, there is an urgent need in this field for an innovative solution that can break through the rigid application mode of existing IFC rules, and achieve fine-grained traffic scheduling and elastic scaling of specific service modules within the MCX system through in-depth exploration and reconstruction of its policy mechanism, thereby giving full play to the basic service capabilities of the IMS core network. Summary of the Invention
[0006] The purpose of this invention is to overcome the technical shortcomings of existing MCX systems, which can only adopt a system stacking-based extensive expansion method when expanding services. This invention provides a method for multi-service deployment and expansion of MCPTT services based on IMS IFC rules. The method of this invention achieves precise expansion and load balancing of bottleneck service modules in the MCX system by configuring differentiated IFC rules for different user groups and dynamically routing user service requests to different sipserver services. This achieves the technical goal of effectively improving system capacity and service load capacity without significantly increasing hardware costs or changing the system architecture, fundamentally solving problems such as resource waste, high investment costs, and complex operation and maintenance.
[0007] The technical solution adopted in this invention is a method for multi-service deployment and expansion of MCPTT services based on IFC rules. The key is that, in a network based on the IMS core network and MCX service system, the above method is implemented by configuring initial filtering rules on the IMS core network side, including the following steps: S1. Deploy two or more sipserver services in the MCX business system and configure unique addressing information for each sipserver service; S2. When a user opens an account, different IFC templates are configured for different user groups in the user data of the IMS network. Each IFC template triggers the business requests of its associated user group to a specified sipserver service. Based on the aforementioned IFC template, the S3 and IMS core networks route received user service requests to the corresponding sipserver services for processing.
[0008] Furthermore, the deployment of two or more sipserver services in the MCX business system is achieved by using the same deployment procedure and configuring different addressing information for each sipserver service; each sipserver service shares the same Group Management Service (GMS), Conference Management Service (CMS), and Identity Management Service (IDMS) in the MCX business system.
[0009] Furthermore, the aforementioned sipserver services also share the same dispatch service Dispatch, in-memory database service Redis, presentation service Presence, and Web to SIP gateway service W2S in the MCX business system.
[0010] Specifically, the aforementioned user service requests include user registration requests and user call requests.
[0011] More specifically, when the aforementioned user service request is a user registration request, the IMS core network triggers the SIP registration message to the corresponding sipserver service based on the IFC template signed by the user.
[0012] More specifically, when the aforementioned user service request is a user call request, the IMS core network routes the SIP call initiation message to the sipserver service corresponding to the calling user to handle the calling side service, based on the IFC template signed by the calling user.
[0013] Furthermore, once the calling party's service processing is complete, the IMS core network routes the aforementioned SIP call initiation message to the called party's corresponding sipserver service to process the called party's service, based on the IFC template signed by the called party.
[0014] Furthermore, the above-mentioned multi-service deployment and expansion method achieves system expansion by adding a sipserver service and configuring an IFC template pointing to the new service for the new user group.
[0015] Preferably, the aforementioned unique addressing information includes any one or more of the hostname, IP address, and port number.
[0016] It should be noted that the above-mentioned different user groups are divided according to the numerical range of user identifiers.
[0017] Compared with the prior art, the present invention has the following advantages: This invention proposes a method for multi-service deployment and expansion of MCPTT services based on IMS IFC rules. By innovatively utilizing the existing service triggering mechanism of the IMS core network, service requests from user groups are dynamically routed to different sipserver services based on differentiated IFC templates, thereby achieving precise expansion and load balancing of bottleneck services in the MCX system.
[0018] Specifically, the technical solution of the present invention has the following advantages: First, this invention achieves precise system expansion and efficient resource utilization. Addressing the resource waste caused by deploying multiple complete MCX systems due to performance bottlenecks in the sipserver service in existing technologies, this invention achieves individual expansion of the performance bottleneck component by deploying multiple sipserver services and sharing the backend GMS, CMS, and IDMS services. This invention allows expansion investment to be precisely focused on the performance bottleneck, avoiding redundant deployment of non-bottleneck services, significantly improving hardware resource utilization, and fundamentally solving the cost problem caused by extensive expansion.
[0019] Secondly, this invention endows the system architecture with a high degree of flexibility and scalability. Facing the differentiated needs of various customers in terms of business scale and the uncertainty of future business growth, the multi-service deployment method provided by this invention demonstrates excellent adaptability. The system can be initially deployed according to the minimum business requirements, and subsequent linear and smooth capacity expansion can be achieved simply by adding a sipserver service and configuring the corresponding IFC template for new users. This modular expansion method allows the system capacity to be precisely matched with business growth, effectively avoiding the dilemma of excessive initial investment or rigid expansion in the later stages.
[0020] Third, this invention ensures the non-intrusiveness of the capacity expansion process and the simplicity of operation and maintenance. The core of this invention lies in fully utilizing and configuring the standard IFC rules of the IMS network, without requiring any functional modifications or code development to the existing MCX system or IMS core network. The capacity expansion operation only involves configuring a new IFC template on the IMS side, without affecting existing business logic and system architecture, greatly reducing the complexity and risk of the implementation plan. Simultaneously, the routing rules based on the mapping between user identifier ranges and IFC templates make the traffic distribution logic clear and simple, greatly simplifying the daily maintenance and fault location process of the system.
[0021] In summary, by creatively applying the IMS standard mechanism to the internal service distribution scenario, this invention successfully constructs a low-cost, high-efficiency, and easy-to-maintain elastic expansion solution, providing reliable technical support for the stable operation of the MCX system in large-scale user scenarios. Attached Figure Description
[0022] Figure 1 This is a diagram of a multi-instance architecture based on SSCCF distribution, which is the method of this invention. Detailed Implementation
[0023] Various exemplary embodiments of the present invention will now be described in detail. This detailed description should not be considered as a limitation of the present invention, but rather as a more detailed description of certain aspects, features, and embodiments of the present invention.
[0024] It should be understood that the terminology used in this invention is merely for describing particular embodiments and is not intended to limit the invention. Furthermore, with respect to numerical ranges in this invention, it should be understood that each intermediate value between the upper and lower limits of the range is also specifically disclosed. Any stated value or intermediate value within a stated range, as well as each smaller range between any other stated value or intermediate value within said range, is also included in this invention. The upper and lower limits of these smaller ranges may be independently included or excluded from the range.
[0025] Unless otherwise stated, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art. While only preferred methods and materials have been described herein, any methods and materials similar or equivalent to those described herein may be used in the implementation or testing of this invention. All references to this specification are incorporated by way of citation to disclose and describe methods and / or materials associated with those references. In the event of any conflict with any incorporated reference, the content of this specification shall prevail.
[0026] Various modifications and variations can be made to the specific embodiments described in this specification without departing from the scope or spirit of the invention, as will be apparent to those skilled in the art. Other embodiments derived from this specification will also be readily apparent to those skilled in the art. This specification and embodiments are merely exemplary.
[0027] The terms “include,” “including,” “have,” “contain,” etc., used in this article are all open-ended terms, meaning that they include but are not limited to. Example
[0028] This embodiment provides a method for deploying and expanding MCPTT services across multiple services based on IFC rules. In a network based on the IMS core network and the MCX service system, this method is implemented by configuring IFC rules on the IMS core network side, without requiring modification to the MCX service system. See the architecture diagram below. Figure 1 Specifically, it includes the following steps: S1. Deploy two or more sipserver services in the MCX business system, and configure unique addressing information for each sipserver service. The unique addressing information in this invention includes any one or more of the hostname, IP address and port number. Deploying two or more sipserver services in the MCX business system is achieved by using the same deployment procedure and configuring different addressing information for each sipserver service; each sipserver service shares the same Group Management Service (GMS), Conference Management Service (CMS), and Identity Management Service (IDMS) in the MCX business system.
[0029] The multiple SIP server services of this invention share services such as GMS (Group Management Service), CMS (Conference Management Service), idms (Identity Management Service), dispatch (Scheduling Service), redis (Redis In-Memory Database Service), presense (Presense Service), and w2s (Web to SIP Gateway Service) in the MCX business system.
[0030] S2. When a user opens an account through the UE (User Equipment), different IFC templates are configured for different user groups in the user data of the IMS network. Each IFC template triggers the service requests of its associated user group to a specified sipserver service. The different user groups are divided according to the numerical range of the user identifier.
[0031] S3. The user service request is first sent by the UE to the PCSCF (Proxy Call Session Control Function), and then forwarded to the SCSCF (Service-Call Session Control Function) that provides services to the user; The SCSCF routes the received user service request to the corresponding SIPServer service for processing according to the IFC template configured in step S2. The user service requests in this invention include user registration requests and user call requests, wherein: When the user service request is a user registration request: The IMS core network triggers the SIP registration message to the corresponding sipserver service based on the IFC template signed by the user. When the user service request is a user call request: The IMS core network routes the SIP call initiation message to the sipserver service corresponding to the calling user based on the IFC template signed by the calling user to process the calling side service; after the calling side service is processed, the IMS core network routes the SIP call initiation message to the sipserver service corresponding to the called user based on the IFC template signed by the called user to process the called side service.
[0032] The method of the present invention achieves system expansion by adding a new sipserver service and configuring an IFC template pointing to the new user group. Example
[0033] This embodiment provides a specific application scenario of the multi-service deployment and expansion method based on Embodiment 1, in order to explain in detail the implementation process and technical effects of the present invention.
[0034] Specifically: S1. Deploy two or more sipserver services in the MCX business system, and configure unique addressing information for each sipserver service: Deploying two or more sipserver services in the MCX business system is achieved by using the same deployment procedure and configuring different addressing information for each sipserver service; each sipserver service shares the same Group Management Service (GMS), Conference Management Service (CMS), and Identity Management Service (IDMS) in the MCX business system.
[0035] The address information for the first sipserver service is: sipserver1.mcx.com; The address information for the second sipserver service is: sipserver2.mcx.com; These two sipserver services share GMS, CMS, idms, dispatch, redis, presense, and w2s in the MCX business system.
[0036] S2. When a user opens an account, different IFC templates are configured for different user groups in the user data of the IMS network: User groups with IDs 1 to 10000 sign up for the IFC1 template, which triggers their service requests to sipserver1.mcx.com; The user group with user IDs 10001 to 20000 signed up for the IFC2 template, which triggered their business requests to sipserver2.mcx.com.
[0037] S3 and the IMS core network, based on the IFC template, route the received user service requests to the corresponding sipserver service for processing. When the user's business request is a user registration request: SIP registration messages from users 1 to 10000 trigger sipserver1, and SIP registration messages from users 10001 to 20000 trigger sipserver2. When a user's service request is a user call request, taking user 10000 calling user 20000 as an example: The IMS core network routes the INVITE message to sipserver1 to process the calling party's business based on the IFC1 template signed by the calling user 10000. After the calling party's service is processed, the IMS core network routes the same INVITE message to sipserver2 to process the called party's service based on the IFC2 template signed by the called user 20000.
[0038] In this embodiment, system expansion is achieved by adding a new sipserver service and configuring an IFC template pointing to the new user group for the new service: When it is necessary to support 30,000 users, add a new sipserver3 (address information: sipserver3.mcx.com), configure IFC3 templates for users 20001 to 30000 pointing to sipserver3.mcx.com, and the business requests of the new users will be routed to sipserver3 for processing through the IFC3 templates.
[0039] The embodiments described above are merely preferred embodiments of the present invention and are not intended to limit the scope of the present invention. Various modifications and improvements made by those skilled in the art to the technical solutions of the present invention without departing from the spirit of the present invention should fall within the protection scope defined by the claims of the present invention.
Claims
1. A method for deploying and expanding MCPTT services based on IFC rules, characterized in that, In a network based on the IMS core network and MCX service system, the method is implemented by configuring initial filtering rules on the IMS core network side, including the following steps: S1. Deploy two or more sipserver services in the MCX business system and configure unique addressing information for each sipserver service; S2. When a user opens an account, different IFC templates are configured for different user groups in the user data of the IMS network. Each IFC template triggers the business requests of its associated user group to a specified sipserver service. S3 and the IMS core network route the received user service requests to the corresponding sipserver service for processing according to the IFC template.
2. The method for multi-service deployment and expansion according to claim 1, wherein the deployment of two or more sipserver services in the MCX business system is achieved by using the same deployment program and configuring different addressing information for each sipserver service; each sipserver service shares the same Group Management Service (GMS), Conference Management Service (CMS), and Identity Management Service (IDMS) in the MCX business system.
3. The method according to claim 2, characterized in that, The various SIP server services also share the same dispatch service Dispatch, in-memory database service Redis, presentation service Presence, and Web to SIP gateway service W2S in the MCX business system.
4. The method for multi-service deployment and expansion according to claim 1, wherein the user service request includes user registration request and user call request.
5. In the method for multi-service deployment and expansion according to claim 4, when the user service request is a user registration request, the IMS core network triggers the SIP registration message to the corresponding sipserver service according to the IFC template signed by the user.
6. In the multi-service deployment and expansion method according to claim 4, when the user service request is a user call request, the IMS core network routes the SIP call initiation message to the sipserver service corresponding to the calling user to process the calling side service according to the IFC template signed by the calling user.
7. According to the method for multi-service deployment and expansion as described in claim 6, after the calling side service is processed, the IMS core network routes the SIP call initiation message to the sipserver service corresponding to the called user to process the called side service based on the IFC template signed by the called user.
8. The method for multi-service deployment and expansion according to claim 1, characterized in that, The method for deploying and expanding multiple services achieves system expansion by adding a new sipserver service and configuring an IFC template pointing to the new service for the new user group.
9. The method for multi-service deployment and expansion according to claim 1, characterized in that, The unique addressing information includes any one or more of the hostname, IP address, and port number.
10. The method for multi-service deployment and expansion according to claim 1, characterized in that, The different user groups are divided according to the numerical range of user identifiers.