A multi-protocol network preference control method and system for roaming scenarios

Abstract

This invention relates to a multi-protocol network optimization control method and system for roaming scenarios, belonging to the field of mobile communication network control technology. The method includes: receiving user roaming signaling; identifying protocol types and extracting country / operator identifiers based on GT, MCC / MNC, or network element addresses; normalizing multi-protocol scenarios such as MAP, Diameter, and HTTP2 into a unified decision input structure; sequentially performing multi-dimensional priority arbitration of the non-intervention list, control list, optimized network policy, user group, and historical statistical indicators; if interference is required, obtaining interference codes at the country, operator, and system levels and filtering them in conjunction with protocol types; executing allowance or interference based on the arbitration result and generating logs; and simultaneously achieving hot policy updates through incremental refresh. This invention achieves unified multi-protocol decision-making and dynamic policy adjustment, significantly reducing the probability of false interference and improving the refinement and intelligence level of roaming network optimization control.

Description

Technical Field

[0001] This invention relates to the field of mobile communication network control technology, and in particular to a multi-protocol network optimization control method and system for roaming scenarios. Background Technology

[0002] In international roaming scenarios, user terminals may access multiple available operator networks. Existing systems typically control access based on single-dimensional rules, such as processing only by operator list, only by country configuration, only by a single signaling result, or only by a fixed interference code. Such solutions struggle to balance real-time performance, accuracy, and maintainability, and cannot make differentiated decisions based on user history and terminal characteristics.

[0003] With the coexistence of 2G / 3G, 4G, and 5G protocols, network signaling formats differ significantly. In 2G / 3G scenarios, visited networks are often identified using information such as the GT (Global Title) and VLR number. In 4G / 5G scenarios, however, the identification of operators and countries relies more heavily on MCC / MNC (Mobile Country Code / Mobile Network Code), MME (Mobility Management Entity) identifiers, AMF (Access and Mobility Management Function) identifiers, and HTTP2 or Diameter-related fields. Meanwhile, operators desire joint control across multiple dimensions, including users, operators, network elements, terminals, user groups, countries, and historical statistical indicators. They also require policies to be dynamically adjusted and take effect quickly without affecting real-time decisions. Furthermore, the hierarchical relationship between the non-intervention list and the control list in existing solutions is unclear, and the proportional guidance lacks a dynamic adjustment mechanism, making it impossible to achieve proportional traffic distribution in scenarios requiring fine-grained control.

[0004] The existing technology has at least the following problems: 1. Limited strategy dimensions: Processing based solely on operators or a single list fails to consider user type, terminal type, network element type, and historical access performance, leading to miscontrol or missed control.

[0005] 2. Lack of a unified decision-making process: Different protocols, lists, and thresholds are often implemented separately, lacking a unified priority arbitration mechanism, making it difficult to form stable and interpretable processing results. There is a lack of clear priority levels between the various lists, and the order of judgment between the non-intervention lists and the control lists is inconsistent, easily leading to conflicting decisions.

[0006] 3. Inefficient update process: Policy changes typically require a full reload or service restart, which cannot meet the minute-level or even second-level effectiveness requirements of roaming network optimization. Operations personnel must wait a considerable amount of time for policy modifications to take effect, impacting operational efficiency.

[0007] 4. Crude selection of interference codes: The lack of a hierarchical interference code matching mechanism at the national, operator, and system levels results in the use of the same interference code for different roaming destinations, leading to poor compatibility.

[0008] 5. Lack of historical statistical loop: The system fails to incorporate user behavior characteristics such as historical rejection counts, duration, and changes in VLR / MME / AMF, making it impossible to strike a fine-grained balance between "whether to continue intervention" and "whether to allow passage." The lack of an automatic passage mechanism based on statistical feedback leads to continuous and abrupt interference with users, negatively impacting the roaming experience. Summary of the Invention

[0009] Based on the above analysis, this invention aims to disclose a multi-protocol network optimization control method and system for roaming scenarios. By unifying multi-protocol normalization identification, multi-dimensional policy priority arbitration, historical statistical threshold decision, and hierarchical interference code matching into the same decision engine, and supported by a hot update mechanism that does not interrupt services, a closed loop of "policy configuration - real-time decision - statistical feedback - dynamic adjustment" is formed, realizing refined, dynamic, and intelligent control of roaming terminal network selection, and significantly reducing the probability of false interference.

[0010] This invention discloses a multi-protocol network optimization control method for roaming scenarios, comprising: S1. Receive roaming signaling from the user to be processed; S2. Identify the current scenario based on the protocol type of the roaming signaling, and extract the country identifier, operator identifier and visited network element information based on at least one of the following: global title GT, mobile country code / mobile network code MCC / MNC or network element address, and normalize different protocol scenarios into a unified decision input structure. S3. Based on the unified decision input structure, perform priority arbitration by matching the non-intervention list, the control list, the preferred network strategy, the user group, and comparing historical statistical indicators in sequence according to the preset priority level; wherein, the comparison of historical statistical indicators includes comparing the user's historical interference count, interference duration, and number of visits to network elements with the corresponding threshold. S4. When the arbitration result indicates that interference needs to be implemented, obtain the set of interference codes in the order of national level, operator level, and system level, and filter the available interference codes in combination with the current protocol type. S5. Based on the arbitration result, execute the release or interference, and generate logs simultaneously.

[0011] Furthermore, in S3, the priority arbitration is performed in the following hierarchical order: S3-1. First, determine the user, operator, and network element level's no-intervention list. If a match is found, allow passage directly. S3-2. Next, check the control lists at the user, operator, and network element levels. If a match is found, proceed to the corresponding processing branch according to the configured control method. S3-3. If a special terminal configuration exists, the Type Assignment Code (TAC) is extracted from the IMEI and matched against the special terminal whitelist; if the special terminal whitelist is matched, the passage is directly allowed. S3-4. Query the national or operator-level preferred network policy. If it is a no-intervention policy, allow the passage directly. If it is another policy, continue to the subsequent judgment. S3-5. Perform interoperability judgment on users. When it is detected that a user has the behavior characteristics of accessing other generations of networks in the current protocol scenario, combine historical statistical thresholds to determine whether the interoperability release conditions are met. S3-6. Match user groups based on at least one of the following dimensions: IMSI, IMSI prefix, TAC, and brand model. Take the strategy with the highest priority among the dimensions as the final strategy for the user group and arbitrate its priority with the basic strategy. S3-7. For users who require further judgment, introduce threshold decisions based on historical behavior. If any one of them reaches the preset threshold, the user is allowed to proceed; if none of them are reached, interference control continues.

[0012] Further in S3-5, the interoperability judgment includes: Detect VLR or AMF changes in Diameter scenarios, or MME or AMF changes in MAP scenarios; When the change is detected, the number of changes in VLR, MME, or AMF is compared with the corresponding threshold, and if the condition is met, the passage is directly allowed.

[0013] Further in S3-6, user group matching includes: First, match the terminal user group by TAC, then match the service user group and user level group by IMSI; The strategy with the highest priority among all dimensions is taken as the final strategy for the user group, and the final strategy for the user group is arbitrated with the basic strategy. The basic strategy is the strategy determined in the previous steps. During the arbitration, the strategy priority is ranked from high to low as follows: no intervention, prohibition of network access, forced selection, and proportional guidance. The higher priority strategy is taken as the final decision strategy.

[0014] Further, in S3-7, threshold decisions based on historical behavior include: 1) The system obtains the user's historical interference statistics; the user-level statistics maintained by the system include, but are not limited to: the most recent interference code for each protocol, the cumulative number of interferences for each protocol, the cumulative interference duration for each protocol, the number of changes in VLR / MME / AMF (i.e., network element hop count), and the time of the last interference occurrence; 2) The system retrieves interference threshold configurations according to a priority hierarchy from fine to coarse. The retrieval process attempts the following steps sequentially: first, query the threshold configuration based on the most recent interference code, protocol type, and operator identifier; if not found, query the threshold configuration based on the most recent interference code and protocol type; if still not found, query the threshold configuration based on the protocol type and operator identifier; if still not found, retrieve the threshold configuration based only on the protocol type; if no threshold configuration is found after the above hierarchical queries, the system directly outputs the interference result; if a threshold is found, proceed to the next step. 3) The system judges the network element hop count threshold, interference count threshold, and interference duration threshold in sequence. If any one of them reaches the preset threshold, it is determined that the user has met the conditions for release and the system outputs a no-intervention result. If none of the three conditions are met, the interference control continues.

[0015] Further threshold determination process includes: (1) Compare the number of hops of network elements and determine whether the number of changes of VLR / MME / AMF is less than the corresponding threshold; if not, it is determined that the release condition is met and the release result is output without intervention; if yes, continue to the next comparison.

[0016] (2) Compare the number of interferences thresholds and determine whether the cumulative number of interferences is less than the corresponding threshold. If not, output the result of not interfering and allowing passage. If yes, continue to the next comparison.

[0017] (3) Compare the interference duration threshold and determine whether the cumulative interference duration is less than the corresponding threshold; if not, output the result of not intervening and allowing passage; if yes, continue to maintain interference control.

[0018] Further, S4 includes: The system first queries the national-level jamming code policy. If a match is found, the corresponding jamming code list is obtained. If no match is found, the system queries the operator-level jamming code policy. If no match is found, the system-level default jamming code is used. After obtaining the list of interference codes, the system further filters interference codes that match the protocol and are in an enabled state based on the current protocol type and specific signaling type, and obtains the final rejection code and message type.

[0019] Furthermore, it also includes S6, configuring hot update steps: obtaining policy change events by periodically scanning the update log table, and incrementally refreshing the corresponding memory data structure to achieve policy hot update and ensure that the decision engine continues to run online.

[0020] Further configuration steps for hot updates include: After system startup, it first reads the configuration file and loads the entire policy. Then, it starts two processing threads in parallel, one responsible for hot updates of policy configuration and the other for synchronous updates of user historical information. This ensures that policy changes and statistical information take effect within seconds without affecting ongoing real-time decision-making. The strategy hot update thread periodically scans the strategy change log table to obtain add, modify, delete or import events, and loads the corresponding change strategy records. For different table names, the system distributes the changes to the corresponding processing modules to complete the partial refresh of the memory hash table, tree index or list cache. The user history information synchronization thread is responsible for receiving changed user information, reading the changed user history statistical records, and updating the cached user information. The thread ensures that when the decision engine compares historical statistical indicators, the data such as the number of interferences, interference duration, and network element hops used are always synchronized with the backend storage.

[0021] Another aspect of the present invention discloses a multi-protocol network optimization control system for roaming scenarios, comprising: The protocol identification module is used to receive roaming signaling from users to be processed, identify the current scenario according to the protocol type, and extract the country identifier, operator identifier and visited network element information based on at least one of the following: global title GT, mobile country code / mobile network code MCC / MNC or network element address, and normalize different protocol scenarios into a unified decision input structure. The decision engine module is used to perform priority arbitration based on the unified decision input structure, according to a preset priority hierarchy, by matching the non-intervention list, the control list, the preferred network strategy, the user group, and comparing historical statistical indicators. The historical statistical indicator comparison includes comparing the user's historical interference counts, interference durations, and the number of times the visited network element changes with the corresponding thresholds. The interference code matching module is used to obtain the set of interference codes according to the priority order of national level, operator level and system level when the arbitration result is that interference needs to be performed, and to filter the available interference codes in combination with the current protocol type. The execution output module is used to either release or interfere based on the arbitration result, and to generate logs synchronously. Configure a hot update module to obtain policy change events by periodically scanning the update log table and incrementally refreshing the corresponding memory data structure to achieve hot policy updates.

[0022] Compared with the prior art, the present invention has at least the following beneficial effects: 1. Through multi-protocol normalization processing, the optimal roaming logic for 2G / 3G, 4G, and 5G is unified.

[0023] 2. By guiding joint decision-making through lists, user groups, terminals, thresholds, and proportions, the probability of false control is significantly reduced.

[0024] 3. Through an incremental refresh mechanism driven by update logs, configurations can be dynamically applied during runtime without requiring a full load or program restart.

[0025] 4. By using historical statistical thresholds, the criteria for "when to stop interference and allow access to the preferred network" can be interpreted and quantified.

[0026] 5. Improve compatibility with different roaming destinations by performing layered interference code matching at the national, operator, and system levels.

[0027] 6. Through the forced access mechanism, precise control can be exercised over key countries, key operators, or key network elements.

[0028] 7. The dual-channel output of logs and notifications facilitates operational closure, problem identification, and effect evaluation. Attached Figure Description

[0029] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Throughout the drawings, the same reference numerals denote the same parts.

[0030] Figure 1 This is a flowchart of a multi-protocol network optimization control method for roaming scenarios in an embodiment of the present invention; Figure 2 This is a flowchart illustrating the implementation of the decision mechanism in this embodiment of the invention. Figure 3 This is a flowchart of a threshold decision based on historical behavior in an embodiment of the present invention; Figure 4 This is a flowchart of the interference code acquisition process in an embodiment of the present invention; Figure 5 This is a flowchart illustrating the configuration hot update process in an embodiment of the present invention; Figure 6 This is a schematic diagram of the components and connections of the multi-protocol network optimization control system for roaming scenarios in an embodiment of the present invention; Figure 7 This is a diagram of the multi-protocol network preferred control system architecture in an embodiment of the present invention. Detailed Implementation

[0031] Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings, which form part of this application and, together with the embodiments of the present invention, serve to illustrate the principles of the present invention.

[0032] Example 1 One embodiment of the present invention discloses a multi-protocol network optimization control method for roaming scenarios, such as... Figure 1 As shown, it includes: S1. Receive roaming signaling from the user to be processed; The system receives network access request signaling generated by users in international roaming scenarios through the signaling interface. Depending on the network deployment, the signaling comes from network elements including ISTP (Signaling Transfer Point), DRA (Diameter Routing Proxy), or SEPP (Security Edge Protection Proxy).

[0033] S2. Identify the current scenario based on the protocol type of the roaming signaling, and extract the country identifier, operator identifier and visited network element information based on at least one of the following: global title GT, mobile country code / mobile network code MCC / MNC or network element address, and normalize different protocol scenarios into a unified decision input structure. The system first identifies the protocol type of the current signaling. In one implementation, the protocol type includes MAP, Diameter, and HTTP2;

[0034] For 2G / 3G scenarios, the system parses country identifiers, operator identifiers, MCCs, MNCs, and country codes through global header GT information. For 4G / 5G scenarios, the system combines MCC / MNC with network element addresses to map target countries and operators. When the subsystem number SSN is 149, the system further breaks down and identifies MAP traffic, accurately determining it as GPRS-related signaling, achieving fine-grained differentiation of various signaling types under the same protocol family.

[0035] Through the above processing, different protocol scenarios are uniformly transformed into the same decision input structure. The structure includes at least the country identifier, operator identifier, and visited network element information, so that the subsequent policy engine does not need to implement the entire set of logic according to the protocol, but only needs to retain the protocol differences in the threshold comparison and interference code distribution stages.

[0036] S3. Based on the unified decision input structure, perform priority arbitration by matching the non-intervention list, the control list, the preferred network strategy, the user group, and comparing historical statistical indicators in sequence according to the preset priority level; wherein, the comparison of historical statistical indicators includes comparing the user's historical interference count, interference duration, and number of visits to network elements with the corresponding threshold. In this step, a multi-dimensional joint judgment mechanism is introduced to ensure that high-priority rules take effect first through a hierarchical matching order.

[0037] like Figure 2 As shown, the implementation process of the judgment mechanism includes: S3-1. First, determine the user, operator, and network element level's no-intervention list. If a match is found, allow passage directly. The system first determines the user, operator, and network element-level no-intervention lists; if a user is on the no-intervention list, it directly outputs a "no-intervention, allow" result and does not proceed to the subsequent decision process, ensuring that no-intervention users are not disturbed in any way.

[0038] S3-2. Next, check the control lists at the user, operator, and network element levels. If a match is found, proceed to the corresponding processing branch according to the configured control method. If the no-intervention list is not matched, the control lists at the user, operator, and network element levels will be checked. These control lists can be configured with control methods such as blocking network access or forcing access. If a match is found, the corresponding processing branch will be initiated based on the configured control method.

[0039] S3-3. If a special terminal configuration exists, the Type Assignment Code (TAC) is extracted through the IMEI and matched against the special terminal whitelist. If the special terminal whitelist is matched, the device is allowed to pass directly to avoid accidental intervention on key terminals or special models. S3-4. Query the national or operator-level preferred network policy. If it is a no-intervention policy, allow the passage directly. If it is another policy, continue to the subsequent judgment. If a final result is not obtained directly, the national or carrier-level preferred network policy is queried. If the policy is a non-intervention policy, the application is allowed directly; if it is another policy (such as prohibiting network access, forced selection, or proportional guidance), the application will proceed to the next stage of the decision.

[0040] In one implementation, the policy priorities are set from high to low as follows: no intervention, prohibit network access, forced selection, and proportional guidance. This priority design ensures that stronger constraints override weaker constraints, avoiding uncertainty in results caused by multiple policy conflicts.

[0041] For the proportional guidance strategy, the system first determines whether the current operator is in a proportional control state; if control has not been initiated, it will be allowed directly; if control has been initiated, it will proceed to the subsequent threshold comparison process.

[0042] S3-5. Perform interoperability judgment on users. When it is detected that a user has the behavior characteristics of accessing other generations of networks in the current protocol scenario, combine historical statistical thresholds to determine whether the interoperability release conditions are met. The system performs interoperability checks on users. When a user exhibits behavior characteristics of accessing other generations of networks under the current protocol scenario, it determines whether the interoperability permission conditions are met by combining historical statistical thresholds. If the conditions are met, interoperability is granted directly.

[0043] Specifically, interoperability checks include: Detect VLR or AMF changes in Diameter scenarios, or MME or AMF changes in MAP scenarios; When the change is detected, the number of changes in VLR, MME, or AMF is compared with the corresponding threshold, and if the condition is met, the passage is directly allowed.

[0044] S3-6. Match user groups based on at least one of the following dimensions: IMSI, IMSI prefix, TAC, and brand model. Take the strategy with the highest priority among the dimensions as the final strategy for the user group and arbitrate its priority with the basic strategy. When user group configuration exists, the system matches user groups based on dimensions such as IMSI, IMSI prefix, TAC, brand and model.

[0045] Specifically, user group matching includes: First, match the terminal user group by TAC, then match the service user group and user level group by IMSI; The strategy with the highest priority among all dimensions is taken as the final strategy for the user group, and the final strategy for the user group is arbitrated with the basic strategy in terms of priority. The basic strategy refers to the strategy determined through the preceding steps (intervention-free list matching, control list matching, preferred network strategy query and interoperability judgment); the priority arbitration refers to comparing the user group's final strategy with the basic strategy according to the preset strategy priority, and taking the one with the higher priority as the user's final judgment strategy. In one implementation, the policy priorities, from highest to lowest, are: no intervention, prohibition of access, forced selection, and proportional guidance. For example, if the basic policy is "forced selection" and the user group's final policy is "no intervention," then after arbitration, "no intervention" will be adopted as the final decision policy, and the user will be allowed to access the platform directly.

[0046] S3-7. For users who require further judgment, introduce threshold judgment based on historical behavior. If any one of them reaches the preset threshold, the user is allowed to pass; if none of them are reached, the interference control continues. Based on historical statistical information, the thresholds are compared in the following order: number of hops, number of interferences, and duration of interference. If any one of these thresholds is reached, the release condition is deemed met. This invention does not immediately interfere with all users who hit the control policy, but instead introduces a threshold decision based on historical behavior. The system maintains user-level statistical information, including but not limited to: the most recent interference code for each protocol, the cumulative number of interferences for each protocol, the cumulative interference duration for each protocol, the number of changes in VLR / MME / AMF, and the time of the last interference occurrence.

[0047] When a user hits a forced selection or proportional guidance (not meeting the set proportion) strategy, the system selects the corresponding statistical item based on the protocol type and enters the threshold decision process.

[0048] like Figure 3As shown, threshold decisions based on historical behavior include: 1) The system obtains the user's historical interference statistics; the user-level statistics maintained by the system include, but are not limited to: the most recent interference code for each protocol, the cumulative number of interferences for each protocol, the cumulative interference duration for each protocol, the number of changes in VLR / MME / AMF (i.e., network element hop count), and the time of the last interference occurrence; 2) The system retrieves interference threshold configurations according to a priority hierarchy from fine to coarse. The retrieval process attempts the following steps sequentially: first, query the threshold configuration based on the most recent interference code, protocol type, and operator identifier; if not found, query the threshold configuration based on the most recent interference code and protocol type; if still not found, query the threshold configuration based on the protocol type and operator identifier; if still not found, retrieve the threshold configuration based only on the protocol type; if no threshold configuration is found after the hierarchical query (i.e., the threshold does not exist), the system directly outputs the interference result; if the threshold is found, proceed to the next step. 3) The system judges the network element hop count threshold, interference count threshold, and interference duration threshold in that order. If any one of them reaches the preset threshold, the system determines that the user has met the conditions for passage and outputs a no-intervention result. If none of the three are reached, the interference control continues. Specifically, the threshold determination process includes: (1) Compare the number of hops of network elements and determine whether the number of changes of VLR / MME / AMF is less than the corresponding threshold; if not (i.e., the threshold is reached or exceeded), it is determined that the release condition is met and the release result is output without intervention; if yes (i.e. the threshold is not reached), the next comparison is continued.

[0049] (2) Compare the number of interferences thresholds and determine whether the cumulative number of interferences is less than the corresponding threshold. If not (i.e., the threshold is reached or exceeded), output the result of not interfering and allowing passage. If yes, continue to the next comparison.

[0050] (3) Compare the interference duration threshold and determine whether the cumulative interference duration is less than the corresponding threshold. If not (i.e., the threshold is reached or exceeded), output the result of not intervening and allowing passage. If yes (i.e., none of the three thresholds are reached), continue to maintain interference control.

[0051] 4) When calculating the duration of interference, the system adds the difference between the current time and the time of the last interference to ensure the continuity and accuracy of the duration statistics; the mechanism can avoid continuous and brutal interference, improve the stability of the preferred transfer and the user experience.

[0052] S4. When the arbitration result indicates that interference needs to be implemented, obtain the set of interference codes in the order of national level, operator level, and system level, and filter the available interference codes in combination with the current protocol type. like Figure 4As shown, the system first queries the national-level jamming code policy. If a match is found, the corresponding jamming code list is obtained. If no match is found, the system queries the operator-level jamming code policy. If no match is found, the system-level default jamming code is used. After obtaining the list of interference codes, the system further filters interference codes that match the protocol and are in an enabled state based on the current protocol type and specific signaling type (MAP, MAP for GPRS, Diameter, HTTP2) to obtain the final rejection code and message type, ensuring that different countries and different operators use the most suitable interference information under different protocols.

[0053] S5. Based on the arbitration result, execute the release or interference, and generate logs simultaneously.

[0054] If the decision is to allow access, the system outputs an optimal log; if the decision is to interfere, the system outputs an interference log and simultaneously assembles a rejection message (using the interference code obtained from S4) and sends it to ISTP / DRA / SEPP to reject the user's login request.

[0055] Through the above steps, the present invention realizes unified network optimization processing in multi-protocol roaming scenarios, which reduces the probability of false interference while ensuring the optimization effect, and forms a complete closed loop of "strategy configuration - real-time decision - statistical feedback - dynamic adjustment".

[0056] Preferably, it also includes S6, configuring a hot update step; by periodically scanning the update log table to obtain policy change events, and incrementally refreshing the corresponding memory data structure, policy hot updates are achieved, ensuring that the decision engine runs online for a long time.

[0057] This invention does not reload all data every time the strategy changes, but instead sets up an update log scanning mechanism.

[0058] like Figure 5 As shown, the configuration hot update steps include: After system startup, it first reads the configuration file and loads the entire policy. Then, it starts two processing threads in parallel, one responsible for hot updates of policy configuration and the other for synchronous updates of user historical information. This ensures that policy changes and statistical information take effect within seconds without affecting ongoing real-time decision-making. The strategy hot update thread periodically scans the strategy change log table to obtain add, modify, delete or import events, and loads the corresponding change strategy records. For different table names, the system distributes the changes to the corresponding processing modules to complete the partial refresh of the memory hash table, tree index or list cache. The user history information synchronization thread is responsible for receiving changed user information, reading the changed user history statistical records, and updating the cached user information. The thread ensures that when the decision engine compares historical statistical indicators, the data such as the number of interferences, interference duration, and network element hops used are always synchronized with the backend storage.

[0059] In one implementation, the hot update scope includes at least: user control lists and user non-intervention lists, operator control lists and operator non-intervention lists, network element control lists and network element non-intervention lists, user group basic information and member relationships, preferred network policies, system-level and operator-level network access thresholds, interference code information and interference code policies, country and operator basic mapping information, and proportional guidance related configurations.

[0060] By adopting the above method, the update only affects the memory structure of the corresponding module, avoiding the pauses and jitters caused by a full refresh, and enabling the decision engine to run online for a long time.

[0061] Through the complete execution process of S1 to S6 described above, the solution of this embodiment of the invention integrates protocol identification, country / operator mapping, non-intervention list, control list, user group policy, terminal policy, historical statistical threshold, proportional guidance, interference code matching, and execution output into the same decision engine, so as to achieve hot policy updates without interrupting services and realize refined, dynamic, and intelligent control of mobile terminal network selection.

[0062] In summary, this embodiment has at least the following beneficial effects: 1. Through multi-protocol normalization processing, the optimal roaming logic for 2G / 3G, 4G, and 5G is unified.

[0063] 2. By guiding joint decision-making through lists, user groups, terminals, thresholds, and proportions, the probability of false control is significantly reduced.

[0064] 3. Through an incremental refresh mechanism driven by update logs, configurations can be dynamically applied during runtime without requiring a full load or program restart.

[0065] 4. By using historical statistical thresholds, the criteria for "when to stop interference and allow access to the preferred network" can be interpreted and quantified.

[0066] 5. Improve compatibility with different roaming destinations by performing layered interference code matching at the national, operator, and system levels.

[0067] 6. Through the forced access mechanism, precise control can be exercised over key countries, key operators, or key network elements.

[0068] 7. The dual-channel output of logs and notifications facilitates operational closure, problem identification, and effect evaluation.

[0069] Example 2 This embodiment provides a multi-protocol network optimization control system for roaming scenarios, such as... Figure 6 As shown, it includes: The protocol identification module is used to receive roaming signaling from users to be processed, identify the current scenario according to the protocol type, and extract the country identifier, operator identifier and visited network element information based on at least one of the following: global title GT, mobile country code / mobile network code MCC / MNC or network element address, and normalize different protocol scenarios into a unified decision input structure. The decision engine module is used to perform priority arbitration based on the unified decision input structure, according to a preset priority hierarchy, by matching the non-intervention list, the control list, the preferred network strategy, the user group, and comparing historical statistical indicators. The historical statistical indicator comparison includes comparing the user's historical interference counts, interference durations, and the number of times the visited network element changes with the corresponding thresholds. The interference code matching module is used to obtain the set of interference codes according to the priority order of national level, operator level and system level when the arbitration result is that interference needs to be performed, and to filter the available interference codes in combination with the current protocol type. The execution output module is used to either release or interfere based on the arbitration result, and to generate logs synchronously. Configure a hot update module to obtain policy change events by periodically scanning the update log table and incrementally refreshing the corresponding memory data structure to achieve hot policy updates.

[0070] The specific technical details and beneficial effects of this embodiment are the same as those in Embodiment 1. Please refer to them for details, and they will not be repeated here.

[0071] Example 3 This embodiment provides a multi-protocol network optimization control system architecture for roaming scenarios, such as Figure 7 As shown, a layered architecture is adopted, including a data access layer, a network optimization logic layer, an execution output layer, and a data management layer. Each layer works collaboratively to complete the entire processing flow from signaling parsing and multi-dimensional decision-making to interference code matching and execution output.

[0072] The data access layer is used to capture, parse, and structure multi-protocol signaling. This layer connects to network elements such as ISTP, DRA, or SEPP through standard signaling interfaces to receive network access request signaling generated by users in international roaming scenarios. It parses different protocols such as MAP, Diameter, and HTTP2, captures key signaling such as location updates, authentication, and routing requests, and extracts country identifiers, operator identifiers, and visited network element information based on at least one of the following: global header (GT), mobile country code / mobile network code (MCC / MNC), or network element address. It then normalizes different protocol scenarios into a unified decision input structure and outputs it to the network optimization logic layer.

[0073] The network optimization logic layer is used to perform multi-dimensional strategy matching and arbitration according to a preset priority hierarchy based on the unified decision input structure. The layer includes the following sub-modules:

[0074] The no-intervention list matching module is used to determine whether a user, operator, or network element is on the no-intervention list. If it is, a pass instruction is directly output. The control list matching module is used to determine whether a user, operator, or network element is on the control list. If it is, it will proceed to the corresponding processing branch according to the configured method of prohibiting network access or forcing access. The special terminal matching module is used to extract the TAC through the IMEI, match it with the special terminal whitelist, and allow passage directly if a match is found; The preferred network matching module is used to query national or operator-level preferred network policies. If it is a no-intervention policy, it will be allowed directly; otherwise, it will continue to make subsequent judgments. The interoperability judgment module is used to detect whether a user has behavioral characteristics of accessing other generations of networks under the current protocol scenario, including detecting VLR / AMF changes in the Diameter scenario or MME / AMF changes in the MAP scenario, and combining historical statistical thresholds to determine whether the interoperability release conditions are met. The user group matching module is used to match user groups based on at least one of the following dimensions: IMSI, IMSI prefix, TAC, and brand model. First, it matches the terminal user group according to TAC, and then matches the business user group and user level group according to IMSI. The strategy with the highest priority among all dimensions is taken as the final strategy of the user group, and priority arbitration is performed with the basic strategy. The threshold comparison module is used to compare historical statistical information in the order of hop count threshold, interference count threshold, and interference duration threshold. If any one of them reaches the preset threshold, it is determined that the release condition is met. When calculating the interference duration, the difference between the current time and the time of the last interference is added. The proportional guidance module is used to determine whether the current operator is in a proportional control state. If control has not been activated, it will be allowed directly; if control has been activated, it will enter the threshold comparison. The strategy priority arbitration module is used to coordinate the judgment results of the above modules, and conduct arbitration in the order of priority: non-interference, prohibition of network access, forced selection, and proportional guidance, and output the final judgment result. The interference code selection module is used to obtain the set of interference codes according to the priority order of national level, operator level and system level when the judgment result is interference, and to filter the interference codes that match the protocol and are in the enabled state in combination with the current protocol type and specific signaling type.

[0075] The output layer is used to perform corresponding operations and output the results based on the final decision of the network optimization logic layer. The layer includes:

[0076] The interference signaling assembly module is used to assemble a rejection message using the interference code obtained by the interference code selection module when the judgment result is interference, and send it to ISTP / DRA / SEPP to reject the user's login request. The log output module is used to synchronously generate and output preferred or interfering logs to the database.

[0077] The data management layer provides data support and dynamic update capabilities for the network optimization logic layer. This layer includes:

[0078] The user historical data module is used to maintain user-level statistical information, including the most recent interference code, cumulative number of interferences, cumulative interference duration, number of changes in VLR / MME / AMF, and the time of the last interference occurrence for each protocol. The static configuration data module is used to store basic mapping information of the country and operators, and system-level default interference codes; The strategy configuration data module is used to store the list of users exempt from intervention, the control list, the preferred network strategy, user group information, threshold configuration, proportional guidance configuration, and interference code strategy. The strategy dynamic update module is used to obtain strategy change events by periodically scanning the update log table, and distribute the changes to the corresponding modules to complete the partial refresh of the memory hash table, tree index or list cache, so as to realize hot update of strategy.

[0079] Through the collaborative work of the above layers and modules, the system in this embodiment realizes unified network optimization processing in multi-protocol roaming scenarios, achieves hot policy updates without interrupting services, reduces the probability of false interference while ensuring the optimization effect, and forms a complete closed loop of "policy configuration - real-time judgment - statistical feedback - dynamic adjustment".

[0080] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention.

Claims

1. A multi-protocol network optimization control method for roaming scenarios, characterized in that, include: S1. Receive roaming signaling from the user to be processed; S2. Identify the current scenario based on the protocol type of the roaming signaling, and extract the country identifier, operator identifier and visited network element information based on at least one of the following: global title GT, mobile country code / mobile network code MCC / MNC or network element address, and normalize different protocol scenarios into a unified decision input structure. S3. Based on the unified decision input structure, perform priority arbitration by matching the non-intervention list, the control list, the preferred network strategy, the user group, and comparing historical statistical indicators in sequence according to the preset priority level; wherein, the comparison of historical statistical indicators includes comparing the user's historical interference count, interference duration, and number of visits to network elements with the corresponding threshold. S4. When the arbitration result indicates that interference needs to be implemented, obtain the set of interference codes in the order of national level, operator level, and system level, and filter the available interference codes in combination with the current protocol type. S5. Based on the arbitration result, execute the release or interference, and generate logs simultaneously.

2. The multi-protocol network optimization control method for roaming scenarios according to claim 1, characterized in that, In S3, the priority arbitration is performed in the following hierarchical order: S3-1. First, determine the user, operator, and network element level's no-intervention list. If a match is found, allow passage directly. S3-2. Next, check the control lists at the user, operator, and network element levels. If a match is found, proceed to the corresponding processing branch according to the configured control method. S3-3. If a special terminal configuration exists, the Type Assignment Code (TAC) is extracted from the IMEI and matched against the special terminal whitelist; if the special terminal whitelist is matched, the passage is directly allowed. S3-4. Query the national or operator-level preferred network policy. If it is a no-intervention policy, allow the passage directly. If it is another policy, continue to the subsequent judgment. S3-5. Perform interoperability judgment on users. When it is detected that a user has the behavior characteristics of accessing other generations of networks in the current protocol scenario, combine historical statistical thresholds to determine whether the interoperability release conditions are met. S3-6. Match user groups based on at least one of the following dimensions: IMSI, IMSI prefix, TAC, and brand model. Take the strategy with the highest priority among the dimensions as the final strategy for the user group and arbitrate its priority with the basic strategy. S3-7. For users who require further judgment, introduce threshold decisions based on historical behavior. If any one of them reaches the preset threshold, the user is allowed to proceed; if none of them are reached, interference control continues.

3. The multi-protocol network optimization control method for roaming scenarios according to claim 2, characterized in that, In S3-5, the interoperability judgment includes: Detect VLR or AMF changes in Diameter scenarios, or MME or AMF changes in MAP scenarios; When the change is detected, the number of changes in VLR, MME, or AMF is compared with the corresponding threshold, and if the condition is met, the passage is directly allowed.

4. The multi-protocol network optimization control method for roaming scenarios according to claim 2, characterized in that, In S3-6, user group matching includes: First, match the terminal user group by TAC, then match the service user group and user level group by IMSI; The strategy with the highest priority among all dimensions is taken as the final strategy for the user group, and the final strategy for the user group is arbitrated with the basic strategy. The basic strategy is the strategy determined in the previous steps. During the arbitration, the strategy priority is ranked from high to low as follows: no intervention, prohibition of network access, forced selection, and proportional guidance. The higher priority strategy is taken as the final decision strategy.

5. The multi-protocol network optimization control method for roaming scenarios according to claim 2, characterized in that, In S3-7, threshold decisions based on historical behavior include: 1) The system obtains the user's historical interference statistics; the user-level statistics maintained by the system include, but are not limited to: the most recent interference code for each protocol, the cumulative number of interferences for each protocol, the cumulative interference duration for each protocol, the number of changes in VLR / MME / AMF, and the time of the last interference occurrence; 2) The system retrieves interference threshold configurations according to a priority hierarchy from fine to coarse. The retrieval process attempts the following steps sequentially: first, query the threshold configuration based on the most recent interference code, protocol type, and operator identifier; if not found, query the threshold configuration based on the most recent interference code and protocol type; if still not found, query the threshold configuration based on the protocol type and operator identifier; if still not found, retrieve the threshold configuration based only on the protocol type; if no threshold configuration is found after the hierarchical query, the system directly outputs the interference result; if a threshold is found, proceed to the next step. 3) The system judges the network element hop count threshold, interference count threshold, and interference duration threshold in sequence. If any one of them reaches the preset threshold, it is determined that the user has met the conditions for release and the system outputs a no-intervention result. If none of the three conditions are met, the interference control continues.

6. The multi-protocol network optimization control method for roaming scenarios according to claim 5, characterized in that, The threshold determination process includes: (1) Compare the hop count threshold of the network element and determine whether the number of changes in VLR / MME / AMF is less than the corresponding threshold; if not, it is determined that the release condition is met and the release result is output without intervention; if yes, continue to the next comparison. (2) Compare the number of interferences to the threshold and determine whether the cumulative number of interferences is less than the corresponding threshold; if not, output the result of not interfering and allowing passage; if yes, continue to the next comparison. (3) Compare the interference duration threshold and determine whether the cumulative interference duration is less than the corresponding threshold; if not, output the result of not intervening and allowing passage; if yes, continue to maintain interference control.

7. The multi-protocol network optimization control method for roaming scenarios according to claim 1, characterized in that, S4 includes: The system first queries the national-level jamming code policy. If a match is found, the corresponding jamming code list is obtained. If no match is found, the system queries the operator-level jamming code policy. If no match is found, the system-level default jamming code is used. After obtaining the list of interference codes, the system further filters interference codes that match the protocol and are in an enabled state based on the current protocol type and specific signaling type, and obtains the final rejection code and message type.

8. The multi-protocol network optimization control method for roaming scenarios according to claim 1, characterized in that, It also includes S6 and configuration hot update steps: obtain policy change events by periodically scanning the update log table, and incrementally refresh the corresponding memory data structure to realize policy hot update and ensure that the decision engine continues to run online.

9. The multi-protocol network optimization control method for roaming scenarios according to claim 8, characterized in that, The steps for configuring hot updates include: After system startup, it first reads the configuration file and loads the entire policy. Then, it starts two processing threads in parallel, one responsible for hot updates of policy configuration and the other for synchronous updates of user historical information. This ensures that policy changes and statistical information take effect within seconds without affecting ongoing real-time decision-making. The strategy hot update thread periodically scans the strategy change log table to obtain add, modify, delete or import events, and loads the corresponding change strategy records. For different table names, the system distributes the changes to the corresponding processing modules to complete the partial refresh of the memory hash table, tree index or list cache. The user history information synchronization thread is responsible for receiving changed user information, reading the changed user history statistical records, and updating the cached user information. The thread ensures that when the decision engine compares historical statistical indicators, the data such as the number of interferences, interference duration, and network element hops used are always synchronized with the backend storage.

10. A multi-protocol network optimization control system for roaming scenarios, characterized in that, include: The protocol identification module is used to receive roaming signaling from users to be processed, identify the current scenario according to the protocol type, and extract the country identifier, operator identifier and visited network element information based on at least one of the following: global title GT, mobile country code / mobile network code MCC / MNC or network element address, and normalize different protocol scenarios into a unified decision input structure. The decision engine module is used to perform priority arbitration based on the unified decision input structure, according to a preset priority hierarchy, by matching the non-intervention list, the control list, the preferred network strategy, the user group, and comparing historical statistical indicators. The historical statistical indicator comparison includes comparing the user's historical interference counts, interference durations, and the number of times the visited network element changes with the corresponding thresholds. The interference code matching module is used to obtain the set of interference codes according to the priority order of national level, operator level and system level when the arbitration result is that interference needs to be performed, and to filter the available interference codes in combination with the current protocol type. The execution output module is used to either release or interfere based on the arbitration result, and to generate logs synchronously. Configure a hot update module to obtain policy change events by periodically scanning the update log table and incrementally refreshing the corresponding memory data structure to achieve hot policy updates.

Images