QoS resource establishment method based on terminal registration information matching under multi-core network

Abstract

The application provides a QoS resource establishment method based on terminal registration information matching under a multi-core network, which comprises the following steps: a mapping relationship table of a heterogeneous core network, a policy control entity, an interaction interface and a core network characteristic identifier is constructed in advance; a network access attribute is collected when a terminal accesses a network; a terminal service identifier, a network address and the network access attribute are associated through registration signaling, and a terminal dynamic binding relationship is generated; when QoS resources are established, a target policy control entity is accurately matched by relying on a network address segment and a network access attribute two-dimensional matching rule and a configurable policy, and a corresponding network standard and an interface are adapted to initiate a QoS resource establishment request. The application solves the problems of poor adaptability of single IP matching and easy matching failure in a cross-network scene, and improves the accuracy and automation level of QoS control in a multi-core network scene.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method for establishing QoS resources based on terminal registration information matching in a multi-core network. Background Technology

[0002] With the iterative evolution of mobile communication technology, the hybrid deployment architecture of LTE and 5G heterogeneous core networks has been widely used in critical communication scenarios of private network MCPTT (Multi-Channel PTT). The same network system often needs to connect to multiple heterogeneous core networks simultaneously to meet the needs of large-scale, multi-standard terminal access and group communication. In multi-core network convergence scenarios, different core networks correspond to independent policy control entities, interaction interfaces, and resource scheduling systems. The complex network topology and frequent cross-network roaming of terminals place higher demands on the precise QoS resource management capabilities of critical services such as MCPTT group calls and emergency calls. Currently, most mainstream solutions in the industry use a single network IP address for matching and selecting the core network and policy control entity, which has a relatively limited range of applicable scenarios and can only meet the stable-state scenarios where the terminal network address and core network are fixedly bound.

[0003] Existing single-IP matching technologies cannot identify the actual core network status of a terminal in complex scenarios such as terminal roaming across core networks and session keep-alive resulting in unchanged IP addresses. This easily leads to problems such as incorrect selection of policy control entities, abnormal QoS parameter adaptation, and failure to establish dedicated bearers. Furthermore, they cannot adapt to the differentiated scheduling requirements of heterogeneous hybrid networks using multiple standards, such as LTE and 5G. Simultaneously, traditional management methods lack standardized terminal network access information binding mechanisms and multi-mode fault-tolerant matching strategies, resulting in weak automated adaptation capabilities, high operation and maintenance costs, and difficulty in ensuring stable QoS quality for critical services such as MCPTT emergency calls and group calls. Especially for heterogeneous core networks where MCX systems connect to multiple PLMNs with the same interface but different access cell base stations, the traditional matching method relying solely on IP and PLMN has a single-dimensional limitation, failing to accurately distinguish between multiple core networks with the same PLMN. This easily leads to technical problems such as confusion in matching multiple core networks with the same identifier and service scheduling errors. Therefore, there is an urgent need for a QoS resource establishment solution that is adaptable to multi-core network scenarios, has high matching accuracy, and a high degree of automation. Summary of the Invention

[0004] In view of this, the embodiments of this application provide a QoS resource establishment method based on terminal registration information matching in a multi-core network, which can solve the problems of poor adaptability of single IP matching and easy matching failure in cross-network scenarios, and improve the accuracy and automation level of QoS control in multi-core network scenarios.

[0005] The technical solution of this application embodiment is implemented as follows: In a first aspect, embodiments of this application provide a method for establishing QoS resources based on terminal registration information matching in a multi-core network, comprising the following steps: A mapping table is pre-built and stored, which records the policy control entity addresses, interaction interfaces and core network feature identifiers corresponding to multiple sets of heterogeneous core networks. The core network feature identifiers include network address ranges and network access attributes, which are used to provide benchmark data for subsequent entity matching. When a terminal accesses the core network, the network access attributes corresponding to the current network are automatically collected through native network signaling. The network access attributes are used to characterize the core network identity that the terminal is actually accessing. When a terminal initiates service registration, it receives a registration signaling message carrying the network access attribute. The server parses the registration signaling message, associates the terminal service identifier, the terminal network address, and the network access attribute, and generates and stores the terminal dynamic binding relationship. When it is necessary to establish service QoS resources, the dynamic binding relationship of the terminal is queried. Based on the two-dimensional matching rules composed of the network address range and the network access attributes, the target policy control entity corresponding to the current access core network of the terminal is obtained through the configurable matching strategy. Based on the interaction interface and network standard corresponding to the target policy control entity, a QoS resource establishment request is initiated in a targeted manner, carrying standardized QoS parameters and service priority identifiers.

[0006] Secondly, embodiments of this application also provide a QoS resource establishment apparatus based on terminal registration information matching under a multi-core network, the apparatus comprising: The pre-configuration module is used to pre-build and store a mapping relationship table. The mapping relationship table records the policy control entity addresses, interaction interfaces and core network feature identifiers corresponding to multiple sets of heterogeneous core networks. The core network feature identifiers include network address ranges and network access attributes, which are used to provide benchmark data for subsequent entity matching. The attribute collection module is used to automatically collect the network access attributes corresponding to the current network through native network signaling when the terminal accesses the core network. The network access attributes are used to characterize the identity of the core network that the terminal actually accesses. The signaling processing module is used to receive the registration signaling carrying the network access attribute when the terminal initiates service registration, parse the registration signaling through the server, associate the terminal service identifier, the terminal network address and the network access attribute, and generate and store the terminal dynamic binding relationship. The entity matching module is used to query the dynamic binding relationship of the terminal when it is necessary to establish service QoS resources. Based on the two-dimensional matching rules composed of the network address range and the network access attributes, the module matches the target policy control entity corresponding to the current access core network of the terminal through a configurable matching strategy. The QoS request module is used to initiate a QoS resource establishment request in a targeted manner, carrying standardized QoS parameters and service priority identifiers, based on the interaction interface and network standard corresponding to the target policy control entity.

[0007] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the QoS resource establishment method based on terminal registration information matching under a multi-core network as described in any of the first aspects.

[0008] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, performs the QoS resource establishment method based on terminal registration information matching in a multi-core network as described in any one of the first aspects.

[0009] The embodiments of this application have the following beneficial effects: By pre-constructing a mapping table that records the addresses, interaction interfaces, and core network feature identifiers of policy control entities corresponding to multiple heterogeneous core networks, and combining the dynamic binding relationship of terminals formed by the automatic collection of network access attributes after terminal access and the parsing of registration signaling, the target policy control entity is obtained through adaptive matching based on the two-dimensional matching rules and configurable matching strategies composed of network address ranges and network access attributes. It then adapts to the corresponding interaction interface and network standard to initiate QoS resource establishment requests, forming a complete closed-loop automatic QoS resource management process in multi-core network scenarios. This solution overcomes the shortcomings of single IP address matching, which is limited in its adaptability to a single scenario and prone to failure, through a two-dimensional matching mechanism. It can accurately reflect the actual core network status accessed by the terminal, adapting to complex real-world scenarios such as hybrid networking of LTE and 5G heterogeneous core networks, and terminal cross-network roaming with unchanged IP addresses. Data collection and signaling interaction are achieved entirely based on native network signaling, without requiring modification to the existing network architecture. It can automatically complete the accurate selection of policy control entities and the establishment of QoS resource adaptation in multi-core networks, effectively improving the universality, accuracy, and automation of QoS management for MCPTT services in multi-standard converged networking environments. Attached Figure Description

[0010] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 This is a flowchart illustrating steps S101-S105 provided in the embodiments of this application; Figure 2 This is a flowchart illustrating steps S201-S202 provided in the embodiments of this application; Figure 3 This is a flowchart illustrating steps S301-S303 provided in the embodiments of this application; Figure 4 This is a flowchart illustrating steps S401-S403 provided in the embodiments of this application; Figure 5 This is a flowchart illustrating steps S501-S503 provided in the embodiments of this application; Figure 6 This is a flowchart illustrating steps S601-S602 provided in the embodiments of this application; Figure 7 This is a flowchart illustrating steps S701-S702 provided in the embodiments of this application; Figure 8 This is a schematic diagram of the QoS resource establishment device based on terminal registration information matching in a multi-core network provided in this application embodiment; Figure 9 This is a schematic diagram of the composition structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0012] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0013] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0014] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0015] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0016] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0017] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application and is not intended to limit this application.

[0018] See Figure 1 , Figure 1 This is a flowchart illustrating steps S101-S103 of the QoS resource establishment method based on terminal registration information matching in a multi-core network provided in this application embodiment. It will be combined with... Figure 1 Steps S101-S103 shown will be explained.

[0019] In step S101, a mapping relationship table is pre-built and stored. The mapping relationship table records the policy control entity addresses, interaction interfaces, and core network feature identifiers corresponding to multiple sets of heterogeneous core networks. The core network feature identifiers include network address ranges and network access attributes, which are used to provide benchmark data for subsequent entity matching. In step S102, when the terminal accesses the core network, the network access attributes corresponding to the current network are automatically collected through network native signaling. The network access attributes are used to characterize the core network identity that the terminal actually accesses. In step S103, when the terminal initiates service registration, it receives a registration signaling message carrying the network access attribute, parses the registration signaling message through the server, associates the terminal service identifier, the terminal network address and the network access attribute, and generates and stores the terminal dynamic binding relationship. In step S104, when it is necessary to establish service QoS resources, the terminal dynamic binding relationship is queried, and the target policy control entity corresponding to the current access core network of the terminal is obtained through a configurable matching strategy based on the two-dimensional matching rules composed of the network address range and the network access attributes. In step S105, based on the interaction interface and network standard corresponding to the target policy control entity, a QoS resource establishment request is initiated in a targeted manner, carrying standardized QoS parameters and service priority identifiers.

[0020] This embodiment pre-builds and stores a globally unified mapping table, which serves as the core benchmark data for cross-core network adaptation and matching. This table records the communication addresses, dedicated interaction interfaces, and core network feature identifiers of the policy control entities corresponding to each heterogeneous core network. The core network feature identifiers are divided into two core dimensions: network address ranges and network access attributes. Core network identity is determined from two levels: network address ranges and the actual network access attributes of the terminal. This provides a complete and authoritative benchmark data source for the subsequent implementation of the two-dimensional matching rules, ensuring the standardization and uniformity of matching in multi-core network scenarios.

[0021] During the terminal network access phase, after a terminal connects to any heterogeneous core network, the network access attributes corresponding to the currently accessed network are automatically collected based on the native signaling mechanism of the communication network. This collection process does not require additional signaling interaction procedures or modifications to the existing network architecture and is compatible with existing communication protocols. The collected network access attributes uniquely identify the core network identity that the terminal is currently actually accessing, distinguishing it from a static network address. This accurately reflects the terminal's true network access status and provides a core basis for resolving matching discrepancies in scenarios involving cross-network mobility and unchanged addresses.

[0022] During the terminal service registration phase, the server receives registration signaling initiated by the terminal, carrying network access attributes, and completes signaling parsing. As the sole executor, the server extracts three core data types: terminal service identifier, terminal network address, and network access attributes. These three types of data are then associated and bound to generate and store a dynamic binding relationship specific to the terminal. This dynamic binding relationship is a real-time data set at the terminal level, establishing a link between terminal identity, terminal network address, and actual access to the core network. It serves as the sole data source for entity matching during subsequent QoS resource establishment, ensuring a strong correlation between data and terminal access status.

[0023] During the QoS resource establishment triggering phase, the system queries the dynamic binding relationship corresponding to the terminal based on business requirements. Relying on a two-dimensional matching rule composed of pre-configured network address ranges and network access attributes, and combined with configurable and diverse matching strategies, it adaptively filters and matches the target policy control entity corresponding to the core network currently accessed by the terminal. The two-dimensional matching rule combines the advantages of static address matching and dynamic attribute matching, and can adapt to various networking scenarios such as complex cross-network mobility, address ambiguity, and network switching, significantly improving the accuracy and adaptability of entity matching.

[0024] Ultimately, the system controls the network standard and interaction interface specifications corresponding to the target policy entity based on the matched target policy, carries standardized QoS parameters and differentiated service priority identifiers, and initiates a QoS resource establishment request to the target entity to complete the network service quality resource configuration of the terminal service, thereby realizing intelligent and precise QoS resource scheduling and management in multi-core network convergence scenarios.

[0025] In some embodiments, this embodiment retains the existing two basic matching dimensions: terminal IP address range and network standard (LTE / 5G) access attributes. It adds an ECGI / NCGI cell global identifier as a core distinguishing dimension. A unique, non-overlapping ECGI / NCGI identifier range is pre-configured for each heterogeneous core network within the network. A standardized mapping table containing three types of matching parameters, corresponding core network policy control entities, and adaptation interfaces is established. Data from the three dimensions is collected in real-time and dynamically bound based on the terminal's native network access signaling. Multi-mode matching strategies are adaptively switched according to the network scenario, prioritizing the cell global identifier as the core judgment criterion to complete accurate multi-core network matching and QoS resource adaptation.

[0026] Specifically, traditional solutions rely solely on IP addresses and PLMN identifiers for matching, which has inherent technical flaws and cannot adapt to the complex heterogeneous networking scenarios of MCX private networks. Firstly, private networks often employ deployment methods where multiple core networks share the same PLMN identifier. The PLMN can only identify the network operator type and cannot distinguish between multiple heterogeneous core networks under the same operator. Secondly, in scenarios involving terminal roaming across core networks and persistent session activity, the terminal's IP address remains unchanged. Static IP parameters cannot reflect the real-time status of the core network and cell base station accessed by the terminal, directly causing traditional matching rules to fail and leading to problems such as policy entity mismatch, QoS parameter mismatch, and failure to establish emergency call service bearers. This embodiment adds an ECGI / NCGI cell global identifier as a unique global identifier at the base station cell level, possessing three major characteristics: uniqueness, real-time performance, and independence. It is not constrained by PLMN identifiers or terminal IP addresses and can accurately identify the network cell and corresponding core network currently accessed by the terminal. By linking and matching three-dimensional parameters, especially for the pain point scenario of cross-network roaming with the same PLMN, different base stations, and unchanged IP, it can achieve confusion-free differentiation of multiple heterogeneous core networks. With the adaptive matching strategy, it can significantly improve the accuracy and stability of QoS scheduling of critical services in MCPTT in multi-core network scenarios. It does not require modification of the existing network architecture and has strong compatibility and practicality.

[0027] In some embodiments, see Figure 2 , Figure 2 This is a flowchart illustrating steps S201-S202 provided in the embodiments of this application. The method of constructing the mapping relationship table can be implemented through steps S201-S202, which will be explained in conjunction with each step.

[0028] In step S201, for the LTE standard core network, a mapping and binding relationship is established between the core network and the policy charging rule function entity and the Rx interaction interface; and for the 5G standard core network, a mapping and binding relationship is established between the core network and the policy control function entity, the Rx and / or N5 interaction interface. In step S202, the policy control entity types and their corresponding interaction interfaces under different systems are uniformly entered into the mapping table.

[0029] In the specific construction process, the system performs dedicated mapping configurations for the LTE and 5G core networks respectively. For the LTE evolved core network, a fixed mapping binding relationship is established between the core network and the policy charging rule function entity and the Rx interaction interface, adapting to the QoS policy management specifications and signaling interaction system of the LTE network. For the next-generation 5G core network, a binding relationship is established between the core network and the policy control function entity, while being compatible with the interaction modes of the Rx interface and / or N5 interface, adapting to the flexible interaction characteristics of multiple interfaces in the 5G network, and improving interface adaptation and compatibility in 5G scenarios.

[0030] After completing the single-system mapping and binding, the system integrates all policy control entity types and dedicated adaptation interaction interfaces corresponding to different systems into the mapping relationship table, completing the construction of the global mapping database. This refined configuration method gives the mapping relationship table clear system-distinguishing characteristics. After the core network system determination is completed through dual-dimensional matching, the entity and interface information of the corresponding system can be directly retrieved, providing accurate pre-data support for interface adaptation and system matching in the QoS request stage, and ensuring the continuity of system adaptation throughout the entire process.

[0031] In some embodiments, see Figure 3 , Figure 3 This is a flowchart illustrating steps S301-S303 provided in the embodiments of this application. The step of receiving the registration signaling carrying the network access attribute, parsing the registration signaling by the server, associating the terminal service identifier, the terminal network address and the network access attribute, and generating and storing the terminal dynamic binding relationship can be achieved through steps S301-S303, which will be explained in conjunction with each step.

[0032] In step S301, a service registration signaling initiated by a terminal is received. The registration signaling carries network access attributes collected by the terminal. The network access attributes are encapsulated by the terminal through any one or more combinations of standard signaling header fields, custom extended signaling header fields, and structured message bodies. In step S302, the received registration signaling is parsed to extract the terminal service identifier, terminal network address, and network access attributes. In step S303, the extracted terminal service identifier, terminal network address and network access attributes are associated and bound to generate and store the terminal dynamic binding relationship.

[0033] In this embodiment, after the terminal collects the network access attributes, it can encapsulate and carry the network access attributes in the service registration signaling through any one or more combinations of three methods: standard signaling header field, custom extended signaling header field, and structured message body. Multiple encapsulation methods are compatible with existing standard signaling and custom extended signaling scenarios, adapt to the signaling transmission specifications of different devices and networks, ensure that the network access attributes can be stably and reliably reported to the server, and avoid matching failures caused by data loss.

[0034] After receiving the service registration signaling initiated by the terminal, the server performs a complete parsing of the signaling message to accurately extract three core parameters: terminal service identifier, terminal network address, and network access attributes. The terminal service identifier uniquely distinguishes different terminal devices, the terminal network address represents the terminal's current network addressing information, and the network access attributes represent the terminal's actual core network access status. These three parameters together constitute the complete characteristic data for the terminal's network access.

[0035] The server will strongly associate and bind the three types of parameters extracted from the parsing, generating and storing a dynamic binding relationship specific to the terminal. This binding relationship is not static fixed data, but dynamic data generated based on the terminal's real-time registration signaling. It can accurately correspond to the terminal's current network access status, providing real, effective, and real-time data support for the two-dimensional matching in the subsequent QoS resource establishment process, and ensuring the accuracy of subsequent entity matching results from the data source level.

[0036] In some embodiments, the configurable matching strategy includes: The address-first matching mode includes prioritizing matching based on the terminal network address and the network address range in the mapping table. If the match is successful, the target policy control entity is directly determined. If the match fails or there is address ambiguity, network access attribute matching is switched to be enabled. The network attribute priority matching mode includes matching based on the terminal's network access attributes, which is suitable for scenarios where the terminal moves across core networks and the network address remains unchanged, causing the address range matching to fail. The hybrid verification matching mode includes simultaneous network address range matching and network access attribute matching. If the matching results of the two dimensions are consistent, the result is considered valid. If the results conflict, the matching result of the network access attribute that can truly reflect the current access status of the terminal shall prevail.

[0037] Here, the address-first matching mode is the system's default basic matching mode. It relies on the terminal's network address and pre-defined network address ranges in the mapping table for interval matching. The matching logic is simple, efficient, and fast, suitable for typical network access scenarios where the terminal's network status is stable and the address is unambiguous. When address matching fails due to no results, address overlap or ambiguity, or when the network address remains unchanged after a terminal switches networks, causing address matching to fail, the system automatically switches to the network access attribute matching mode. This achieves efficient matching in typical scenarios and accurate fallback in abnormal scenarios.

[0038] The network attribute-first matching mode uses the terminal's network access attributes as the sole core matching criterion, prioritizing adaptation to special scenarios where the terminal moves across core networks while maintaining the same network address. In this scenario, static network addresses cannot distinguish between the old and new core networks accessed by the terminal. By relying on network access attributes that can characterize the actual access status for matching, the limitations of static address matching can be effectively avoided, accurately locating the target core network currently accessed by the terminal and the corresponding policy control entity.

[0039] The hybrid verification matching mode is a high-precision matching mode that simultaneously performs network address segment matching and network access attribute matching in parallel, and cross-verifies the two sets of matching results. When the two-dimensional matching results are consistent, the matching result is deemed valid and the target entity is output; when the two sets of results conflict, the network access attribute matching result, which can truly reflect the real-time access status of the terminal, is used as the final judgment basis. This effectively solves the matching error problems caused by address information lag, address spoofing, and cross-network handover, and ensures the authenticity and accuracy of matching results in complex scenarios.

[0040] In some embodiments, see Figure 4 , Figure 4 This is a flowchart illustrating steps S401-S403 provided in the embodiments of this application. The matching step can be implemented through steps S401-S403, and will be explained in conjunction with each step.

[0041] In step S401, based on the core network feature identifiers preset in the mapping table, the core network type matching, network operation identifier matching, and radio access type matching are completed sequentially, and the candidate core network range is narrowed down layer by layer. In step S402, the area location identifiers are overlaid as needed to narrow down the matching range; In step S403, the target core network to which the terminal currently belongs is determined by multi-layer feature comparison and the corresponding target policy control entity is matched.

[0042] When the system triggers the network access attribute matching logic, it executes a coarse-to-fine convergence matching process based on the core network feature identifiers pre-stored in the mapping table. First, it sequentially completes core network type matching, network operation identifier matching, and radio access type matching. It filters layer by layer from three macro dimensions: core network standard, operating entity, and access radio standard, which greatly narrows down the number of candidate core networks, quickly eliminates mismatched heterogeneous core networks, and improves matching efficiency.

[0043] After the initial screening, the system can overlay regional location identifiers for matching as needed, based on the network scenario and accuracy requirements. This further refines the matching range by geographical region and network deployment area, adapting to large-scale network scenarios with multiple regions and nodes, and avoiding confusion in node matching across networks of the same standard and operation. This overlay matching method balances efficiency in conventional scenarios with accuracy in complex ones, adapting to network environments of different sizes.

[0044] After multi-layer feature comparison and layer-by-layer convergence screening, the system finally accurately determines the target core network to which the terminal currently belongs, and at the same time matches the unique target policy control entity corresponding to the core network, providing an accurate interaction object for subsequent QoS resource establishment requests, and solving the problem of entity mismatch and omission in the scenario of overlapping deployment of multiple core networks.

[0045] In some embodiments, see Figure 5 , Figure 5 This is a flowchart illustrating steps S501-S503 provided in the embodiments of this application. The targeted initiation of the QoS resource establishment request can be achieved through steps S501-S503, which will be explained in conjunction with each step.

[0046] In step S501, the standardized QoS parameters adapted to the network standard are called according to the core network standard corresponding to the target policy control entity obtained by matching. In step S502, a differentiated service priority identifier is configured according to the terminal service type to distinguish between ordinary services and critical services; In step S503, QoS resources are established based on standardized QoS parameters and service priority identifiers, wherein high-priority critical services are configured with network resource preemption permissions.

[0047] When initiating a QoS resource establishment request, the system first retrieves standardized QoS parameters adapted to the core network standard corresponding to the target policy control entity based on the matched target network standard. Since the QoS parameter systems and service quality standards of different LTE and 5G heterogeneous core networks differ, this solution ensures that the QoS parameters are fully matched with the current access network through standard adaptation, avoiding resource establishment failures and substandard service quality caused by parameter incompatibility, and guaranteeing the standardization of cross-standard QoS scheduling.

[0048] The system configures differentiated service priority identifiers based on the actual service type of the terminal, clearly distinguishing between ordinary and critical services to achieve hierarchical management of services. Through differentiated priority identifier configuration, the system can accurately identify the service quality requirements of different services, providing a basis for subsequent resource allocation and scheduling priorities, and preventing critical services from being overwhelmed by resources during massive concurrent service requests.

[0049] Finally, relying on the adapted standardized QoS parameters and differentiated service priority identifiers, the system completes the QoS resource establishment and configuration for terminal services. This embodiment configures dedicated network resource preemption permissions for high-priority critical services. In scenarios with limited network resources and bandwidth congestion, high-priority critical services can proactively preempt network resources from low-priority ordinary services, prioritizing core service quality indicators such as transmission bandwidth, latency, and packet loss rate for critical services. This achieves a differentiated QoS management effect, prioritizing critical services while ensuring the smooth operation of ordinary services.

[0050] In some embodiments, see Figure 6 , Figure 6This is a flowchart illustrating steps S601-S602 provided in the embodiments of this application. After the target policy control entity is matched and before the QoS resource establishment request is initiated, the method further includes steps S601-S602, which will be explained in conjunction with each step.

[0051] In step S601, it is verified whether the execution result of the two-dimensional matching rule generates a valid target policy control entity; In step S602, if there is no valid matching result, the system's preset default policy control entity is invoked to execute the subsequent QoS resource establishment request process.

[0052] After the two-dimensional matching strategy is executed and the matching results are output, the system first verifies the validity of the matching results to determine whether a legal and valid target policy control entity has been generated. This verification step is a fallback pre-judgment logic that can accurately identify various abnormal scenarios that cause matching failure, such as configuration errors, network matching failures, and missing data, thus avoiding process errors and business failures caused by requests based on invalid entities.

[0053] When the verification determines that no valid match has been found, the system automatically invokes the preset default policy control entity to replace the failed target entity, and then proceeds with the subsequent QoS resource establishment request process normally. This fallback mechanism requires no manual intervention and can automatically complete anomaly repair and process continuation. Even in abnormal scenarios such as abnormal mapping configuration, network feature matching failure, or temporary data loss, it can still ensure the normal establishment of QoS resources for terminal services, guaranteeing uninterrupted terminal services and significantly improving the fault tolerance and reliability of the multi-core network management and control system.

[0054] In some embodiments, see Figure 7 , Figure 7 This is a flowchart illustrating steps S701-S702 provided in the embodiments of this application. The method further includes steps S701-S702, which will be explained in conjunction with each step.

[0055] In step S701, the terminal's re-registration, active deregistration, and registration timeout status are monitored in real time. In step S702, the corresponding terminal dynamic binding relationship is dynamically updated or deleted based on the real-time registration status of the terminal.

[0056] Here, we monitor the changes in the terminal's registration status in real time, focusing on capturing three core status events: terminal re-registration, active deregistration, and registration timeout. These status changes are triggered when a terminal moves across networks, reconnects to the network, goes offline, or experiences session timeout. Consequently, the terminal's network access attributes, network address, and access core network information may change, and statically bound data may become outdated, invalid, or incorrect. Therefore, real-time monitoring of the terminal's registration status is necessary.

[0057] The system dynamically updates or deletes the corresponding dynamic binding relationships of terminals based on the real-time registration status of the terminals. When a terminal triggers re-registration, the system re-collects and parses the terminal's network access information, and updates the network parameters and access attributes in the binding relationship; when a terminal actively cancels or its registration times out, the system determines that the terminal is offline or invalid, promptly deletes the corresponding dynamic binding relationship, and cleans up invalid and redundant data.

[0058] The above method can always ensure that the dynamic binding relationship of the terminal is completely synchronized with the real-time network access status of the terminal, so that each subsequent two-dimensional matching of QoS resource establishment is based on the latest and effective terminal data, completely avoiding problems such as entity matching errors and abnormal QoS resource configuration caused by data lag, expiration, and redundancy, and ensuring the accuracy and stability of the entire matching mechanism in the long term.

[0059] The embodiments of this application will now be described in full and in detail in conjunction with practical applications.

[0060] Example 1: This embodiment is applied to the MCPTT group call service scenario where multiple LTE core networks coexist. Specifically, the MCX system simultaneously interfaces with two heterogeneous LTE core networks, EPC-1 and EPC-2. Through a pre-set mapping table and network address range matching mechanism, it realizes automatic dedicated load establishment and QoS guarantee for group call member terminals under different core networks. In this embodiment, the policy control entity corresponding to the EPC-1 core network is PCRF, with an access address of 10.15.99.10, adapted to the Rx interaction interface, and allocated a terminal IP address range of 10.15.0.0 / 16, with a corresponding PLMN identifier of 460-01. The policy control entity corresponding to the EPC-2 core network is also PCRF, with an access address of 10.100.131.10, adapted to the Rx interaction interface, and allocated a terminal IP address range of 10.100.0.0 / 16, with a corresponding PLMN identifier of 460-07. The MCX system pre-enters the correspondence between the core network, policy control entity, interface type, IP address range and PLMN identifier into the mapping table, completes the pre-configuration of baseline data, and provides data support for subsequent terminal matching.

[0061] During the terminal registration and binding phase, after terminal A, belonging to EPC-1, accesses the network, it initiates a service registration request. Its registration signaling carries P-Access-Network-Info access network information, indicating that the terminal is currently using the 3GPP-E-UTRAN access type and belongs to PLMN 460-01. The MCX system extracts the terminal's IP address (10.15.99.41) from the Contact header field of the registration signaling, associates it with the terminal's unique MCPTT service identifier, IP address, and network access attributes, and generates and stores the terminal's dynamic binding relationship. Similarly, when terminal B, belonging to EPC-2, completes its network registration, the MCX system extracts its IP address (10.100.131.33) and PLMN 460-07 access attributes to generate the corresponding terminal dynamic binding relationship, achieving accurate binding and storage of network access data for two sets of terminals from different core networks.

[0062] During the group call service triggering phase, terminal A initiates an MCPTT group call service. The MCX system needs to establish a dedicated voice bearer for all member terminals within the group. The system queries the pre-stored dynamic binding relationship through the terminal service identifier to obtain the IP address information of terminal A. Based on the address priority matching mode, it compares the terminal IP with the preset IP range in the mapping relationship table, determines that 10.15.99.41 belongs to the 10.15.0.0 / 16 address range, accurately matches it to the PCRF entity corresponding to EPC-1, and initiates an AAR request to address 10.15.99.10 through the Rx interface, carrying the MCPTT service-specific QCI=65, service application identifier, and ARP priority parameters, completing the establishment of the dedicated bearer for terminal A. Simultaneously, the system executes the matching process for terminal B within the group, locates the PCRF entity corresponding to EPC-2 through IP range matching, and independently initiates a QoS resource establishment request.

[0063] This embodiment enables terminal members accessing different LTE core networks under the same group call service to independently establish dedicated QoS loaders. The MCX system, relying on pre-set mapping relationships and two-dimensional matching rules, can automatically identify the core network to which the terminal belongs and match the corresponding policy control entity. No manual configuration intervention is required throughout the process, and no additional network elements are needed. It effectively adapts to the unified QoS management requirements of MCPTT group call services under the parallel deployment of multiple LTE core networks, ensuring stable and reliable communication service quality for all terminals in the group call service.

[0064] Example 2: This embodiment addresses a typical complex networking environment where two heterogeneous LTE core networks are deployed within the system, sharing the same PLMN identifier, and only the access cell base stations differ from the corresponding network segments. This scenario is also a high-risk service scenario that traditional IP and PLMN matching mechanisms cannot fully adapt to. The overall network architecture of this embodiment is configured as two independent LTE core networks, uniformly configured with the same PLMN parameters, to simulate the confusion problem of multiple core networks with the same identifier in the current network. One core network is responsible for covering urban base station areas, and the other core network is responsible for covering suburban base station areas. The two core networks operate independently, respectively carrying critical services such as MCPTT group calls and emergency calls for terminals in different areas. To achieve accurate differentiation between the two core networks sharing the same PLMN, this solution pre-divides non-overlapping dedicated ECGI cell global identifier ranges for the two core networks and matches them with independent IP address ranges, dedicated PCRF policy control entity addresses, and standardized LTE Rx interaction interfaces. All network characteristic parameters, corresponding policy entity information, and interface adaptation relationships are uniformly entered into a pre-set mapping table in the system, completing the standardized configuration of the entire network core network characteristic baseline and providing an accurate basis for subsequent terminal network access matching.

[0065] During the terminal network access phase, terminals within urban coverage areas access the corresponding core network base stations. During service registration, they proactively report real-time information such as their actual network access attributes, the ECGI global identifier of their cell, and their network access IP address via native network signaling. The system server parses the registration signaling and dynamically associates and binds the terminal's unique service identifier with the aforementioned multi-dimensional network parameters, forming a terminal-specific real-time network access binding relationship, which is then persistently stored. Similarly, terminals within suburban coverage areas access suburban base stations to complete network registration and simultaneously bind the corresponding ECGI identifier, network segment, and network attribute parameters. Since the two sets of core network PLMN identifiers are completely identical, traditional matching methods cannot effectively distinguish the access core networks of the two types of terminals, easily leading to policy matching errors. However, this solution, relying on unique and non-overlapping ECGI cell identifiers, can accurately distinguish the actual core network accessed by the terminal from the base station perspective, completely avoiding the matching confusion caused by networking with the same PLMN.

[0066] When a terminal initiates high-priority critical services such as an emergency MCPTT call, the system retrieves the terminal's real-time network access binding data and activates a three-dimensional hybrid verification and matching mechanism. This mechanism comprehensively compares three core dimensions: the terminal's network access IP address range, network access standard attributes, and the ECGI cell global identifier. The ECGI identifier serves as the core judgment benchmark for accurate matching. Based on the matched target cell identifier range, the system accurately locates the heterogeneous core network currently accessed by the terminal and invokes the dedicated PCRF policy control entity corresponding to that core network. It loads the MCPTT standard QoS configuration parameters adapted to the LTE standard and initiates a dedicated bearer establishment process through the corresponding standardized interface. This dynamically allocates service resources matching the current network environment to the terminal, ensuring the transmission quality and scheduling priority of critical services. Even if the terminal roams across core networks between urban and suburban areas, the terminal session keep-alive mechanism ensures its IP address remains unchanged. The system can update the terminal binding relationship in real time through the new ECGI identifier carried in the terminal re-registration signaling, dynamically refreshing the matching benchmark and adapting to the terminal's latest access network status. Meanwhile, the system is equipped with a matching fallback mechanism, which can automatically enable the default policy configuration in rare scenarios of signaling anomalies or parameter parsing failures, ensuring that MCPTT's core business is uninterrupted and scheduling is normal throughout the process.

[0067] Example 3: This embodiment is applied to a multi-5G core network scenario to achieve automated QoS Flow establishment and policy management for 5G network MCPTT group call services. In this embodiment, the MCX system simultaneously interfaces with two heterogeneous 5G core networks, 5GC-1 and 5GC-2. The policy control entity corresponding to the 5GC-1 core network is PCF, with a service address of 10.200.1.5, adapted to the 5G dedicated N5 interaction interface, allocated a terminal IP address range of 10.200.0.0 / 16, a corresponding PLMN identifier of 460-01, and an access type of 3GPP-NR. The PCF entity address corresponding to the 5GC-2 core network is 10.201.1.5, adapted to the N5 interface, allocated an IP address range of 10.201.0.0 / 16, and a corresponding PLMN identifier of 460-07. The MCX system pre-builds and stores a mapping table containing the above parameters to complete the association and binding of the 5G core network with the policy control entity, interaction interface, and network feature identifier.

[0068] During the terminal network registration phase, terminal C accesses the 5GC-1 core network and initiates a registration request. The registration signaling carries the 3GPP-NR access type and PLMN 460-01 identifier. The MCX system extracts the terminal IP address 10.200.10.50 and generates and stores a dynamic binding relationship by combining the terminal service identifier and network access attributes. Terminal D accesses the 5GC-2 core network and completes registration. The system simultaneously extracts its IP address, PLMN identifier, and other information to generate independent terminal dynamic binding data, recording the complete characteristic information of the terminal's 5G network access, and providing real-time data basis for subsequent QoS matching.

[0069] When terminal C initiates an MCPTT group call, the MCX system queries the terminal's dynamic binding relationship to obtain the terminal's IP information. By comparing the pre-set IP segments in the mapping table using an address-first matching mode, it determines the terminal's affiliation to the 5GC-1 core network and matches the corresponding PCF policy control entity. Based on the 5G network standard adaptation N5 interaction interface, the system initiates an N5 policy authorization request to the target PCF entity, carrying the 5G-specific 5QI=65 parameter and the MCPTT service application identifier. Upon receiving the request, the target PCF entity issues standardized PCC policy rules to the SMF network element through its internal N7 interface. The SMF then triggers the establishment process of the terminal-specific QoS Flow, completing the QoS resource configuration for the MCPTT service under the 5G network.

[0070] This embodiment relies on the dual-dimensional matching mechanism and standard adaptation logic of the present invention to realize the automatic selection of PCF entities and the adaptation and calling of N5 interfaces in multi-5G core network scenarios. It can accurately transmit 5G-specific QoS parameters, perfectly adapt to the 5G network QoSFlow management and control specifications, and solve the problems of traditional solutions being unable to adapt to 5G heterogeneous core networks and unable to be compatible with N5 interfaces and 5QI parameters, effectively ensuring the communication service quality of 5G network MCPTT key services.

[0071] Example 4: This embodiment addresses a special networking scenario where the terminal roams across core networks while maintaining a constant IP address. It leverages a network access attribute matching mechanism to resolve the issue of static IP segment matching failures, enabling precise selection of policy control entities. The network architecture in this embodiment utilizes dual LTE core networks, EPC-1 and EPC-2. EPC-1 corresponds to PLMN 460-01 and PCRF address 10.15.99.10, while EPC-2 corresponds to PLMN 460-07 and PCRF address 10.100.131.10. To ensure session continuity during cross-network roaming, the terminal's network IP address remains constant, with only the network access attribute changing.

[0072] When a terminal initially accesses the EPC-1 core network, it completes network registration using IP address 10.15.99.41. The registration signaling carries the network access attribute of PLMN 460-01. The MCX system completes terminal information binding, generating a dynamic binding relationship containing the terminal service identifier, fixed IP address, and initial PLMN attributes. When the terminal moves from the EPC-1 coverage area to the EPC-2 coverage area and triggers re-registration, to maintain uninterrupted service sessions, the terminal retains the original IP address 10.15.99.41, but the network access attribute in the re-registration signaling is updated to PLMN 460-07. The MCX system detects the re-registration behavior of the same terminal identifier, recognizes that the terminal IP address has not changed, but the core network access attribute has been updated, and updates the terminal's dynamic binding relationship in real time, completing the dynamic iteration of the network access attribute.

[0073] When a terminal needs to establish a dedicated MCPTT service carrier, the system queries the latest dynamic binding data of the terminal and performs a two-dimensional matching verification: Based on static IP segment matching, the terminal's IP belongs to the EPC-1 address segment, matching the PCRF entity pointing to EPC-1; based on real-time network access attribute matching, the terminal's current PLMN identifier is 460-07, matching the PCRF entity pointing to EPC-2, resulting in a conflict in the two-dimensional matching results. The system, according to a preset hybrid verification matching strategy, uses the network access attribute results that accurately reflect the terminal's real-time access status as the final judgment criterion, discarding the lagging static IP matching results, and ultimately selecting the policy control entity corresponding to EPC-2.

[0074] After identifying the target entity, the MCX system initiates an AAR request to the PCRF entity of EPC-2, successfully establishing a dedicated service bearer for the terminal roaming across networks. This embodiment effectively solves the problem of IP-unchanged cross-network handover scenarios that traditional pure IP matching schemes cannot adapt to. Through a dual-dimensional matching complementary mechanism, it corrects the lag defect of static address matching, accurately identifies the core network actually accessed by the terminal, and completely avoids the problem of incorrect selection of policy control entities in cross-network scenarios.

[0075] Example 5: This embodiment is applied to a complex scenario where LTE and 5G heterogeneous core networks are deployed in a hybrid manner by the same operator. Through a two-dimensional matching and standard adaptation mechanism, it achieves adaptive selection of policy control entities and interaction interfaces under LTE and 5G heterogeneous networks, and completes the establishment of differentiated QoS resources. The network architecture of this embodiment includes an EPC LTE core network and a 5GC 5G core network of the same operator. The two core networks share the PLMN identifier 460-01. The EPC core network adapts to the Rx interface, PCRF entity and 10.15.0.0 / 16 IP segment, and the 5GC core network adapts to the N5 interface, PCF entity and 10.200.0.0 / 16 IP segment. The MCX system pre-configures the mapping relationship between the two heterogeneous core networks.

[0076] During the terminal network access phase, terminal F accesses the EPC core network via the LTE 3GPP-E-UTRAN standard, with a network access IP of 10.15.88.20. The registration signaling carries LTE access attributes and the corresponding PLMN identifier. The MCX system collects the terminal network access characteristics and generates a dynamic binding relationship. Terminal G accesses the 5GC core network via the 5G 3GPP-NR standard, with a network access IP of 10.200.10.30. The system synchronously collects 5G access attributes and network identification information, generates independent terminal dynamic binding data, and distinguishes the differences in network access characteristics between LTE and 5G terminals.

[0077] During the QoS resource establishment phase, the system performs matching and resource establishment procedures for two types of terminals respectively. For terminal F with LTE access, the system determines its EPC core network affiliation through IP segment matching, confirms the LTE access standard by combining network access attribute verification, selects the corresponding PCRF entity and Rx interaction interface, and initiates an AAR request carrying the QCI=65 parameter to complete the establishment of the dedicated LTE network bearer. For terminal G with 5G access, the system locates the 5GC core network through dual verification of IP segment and NR access attributes, selects the PCF entity and N5 interaction interface, and initiates a policy authorization request carrying the 5QI=65 parameter to complete the establishment of the 5G network QoS Flow.

[0078] This embodiment achieves unified management and control of LTE and 5G heterogeneous hybrid networking scenarios through multi-dimensional convergence matching of core network type, access standard, and IP segment. The system can automatically identify the network standard accessed by the terminal, adaptively switch policy control entities and interaction interfaces, and is compatible with LTE-specific QCI parameters and 5G-specific 5QI parameter system. It does not require the deployment of independent management and control systems for different networks, which greatly improves the universality and adaptability of QoS management for MCPTT services under multi-standard converged networking.

[0079] Example 6: This embodiment focuses on differentiated QoS assurance scenarios for mission-critical services such as MCPTT emergency calls. Through service priority configuration and resource preemption mechanisms, it achieves the highest level of network resource assurance for emergency call services, adapting to the stringent service quality requirements of emergency communication and mission-critical communication. This embodiment is based on the LTE EPC-1 core network architecture. Terminals access the EPC-1 core network to complete network registration, generating a dynamic binding relationship containing terminal IP, PLMN identifier, and access attributes. The MCX system can correctly match the corresponding PCRF policy control entity based on the mapping relationship table.

[0080] When a terminal initiates an MCPTT emergency call, the MCX system first queries the terminal's dynamic binding relationship. Using a two-dimensional matching rule, it accurately matches the terminal's EPC-1 core network and corresponding PCRF entity address. When initiating a QoS resource establishment request, the system configures unique, differentiated parameters for the emergency call service. Compared to a regular MCPTT group call, the emergency call service carries a unique Application-ID=MCPTT-emergency service identifier, is configured with the highest ARP priority level, and enables network resource preemption capabilities, granting the emergency call service priority access to network resources.

[0081] After receiving the QoS establishment request, the target PCRF entity identifies the high-priority parameters and resource preemption rights of the emergency call, and sends a dedicated PCC policy rule to the network side, triggering the PGW network element to establish a dedicated bearer with the highest priority for the terminal. In scenarios with network bandwidth congestion and limited resources, this dedicated bearer for emergency calls can proactively preempt network resources of low-priority ordinary services, prioritizing the transmission bandwidth, latency, and packet loss rate of the emergency call media stream, and avoiding the problem of critical emergency communication services being squeezed out by ordinary service resources.

[0082] This embodiment, based on the differentiated QoS configuration and priority control mechanism of the present invention, achieves absolute priority protection for critical emergency services, can accurately distinguish the service levels of ordinary group call services and emergency call services, and constructs a hierarchical QoS protection system through configurable resource preemption permissions, which greatly improves the reliability and security of MCPTT critical task communication and is suitable for special communication scenarios such as emergency command and emergency dispatch.

[0083] In summary, the embodiments of this application have the following beneficial effects: For MCPTT service networking scenarios with multiple heterogeneous core networks, this solution effectively overcomes the shortcomings of traditional single IP matching methods, such as matching lag, cross-network handover identification failure, and core network selection errors, by constructing a two-dimensional matching rule composed of network address ranges and network access attributes, and a configurable multi-mode matching strategy. It can automatically adapt to the policy control entities and interaction interfaces corresponding to different core network standards in LTE, 5G standalone networking, and LTE / 5G hybrid heterogeneous networking environments, accurately completing the dynamic selection of PCRF / PCF entities and the establishment of QoS resources. It not only supports standardized QoS management for concurrent group call services across multiple terminals and multiple core networks under normal stable networking conditions, but also enables specific scenarios where terminals roam across core networks while maintaining the same IP address. By accurately identifying the actual network access status of terminals through network access attributes such as PLMN, this application ensures the authenticity and reliability of matching results. Simultaneously, by introducing a differentiated service priority mechanism and resource preemption capabilities, it achieves layered QoS guarantees for ordinary group call services and critical emergency call services, greatly improving service reliability in emergency communication scenarios. Furthermore, through a match anomaly fallback mechanism and dynamic maintenance of terminal binding relationships throughout the entire lifecycle, it effectively avoids service anomalies caused by configuration anomalies, data lag, and changes in registration status. The entire process requires no manual intervention or the addition of dedicated network elements, significantly improving the universality, accuracy, stability, and fault tolerance of MCPTT service QoS scheduling under a multi-standard converged core network, and substantially reducing the deployment and maintenance costs of multi-core network integration.

[0084] Based on the same inventive concept, this application also provides a QoS resource establishment device for multi-core network based on terminal registration information matching, which corresponds to the QoS resource establishment method for multi-core network based on terminal registration information matching in the first embodiment. Since the principle of the device in this application is similar to the QoS resource establishment method for multi-core network based on terminal registration information matching, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0085] like Figure 8 As shown, Figure 8 This is a schematic diagram of the QoS resource establishment device 800 based on terminal registration information matching in a multi-core network provided in this application embodiment. The QoS resource establishment device 800 based on terminal registration information matching in a multi-core network includes: The pre-configuration module 801 is used to pre-build and store a mapping relationship table. The mapping relationship table records the policy control entity addresses, interaction interfaces and core network feature identifiers corresponding to multiple sets of heterogeneous core networks. The core network feature identifiers include network address ranges and network access attributes, which are used to provide benchmark data for subsequent entity matching. The attribute acquisition module 802 is used to automatically collect the network access attributes corresponding to the current network through network native signaling when the terminal accesses the core network. The network access attributes are used to characterize the core network identity that the terminal actually accesses. The signaling processing module 803 is used to receive the registration signaling carrying the network access attribute when the terminal initiates service registration, parse the registration signaling through the server, associate the terminal service identifier, the terminal network address and the network access attribute, and generate and store the terminal dynamic binding relationship. The entity matching module 804 is used to query the dynamic binding relationship of the terminal when it is necessary to establish service QoS resources. Based on the two-dimensional matching rules composed of the network address range and the network access attributes, the target policy control entity corresponding to the current access core network of the terminal is matched through a configurable matching strategy. The QoS request module 805 is used to initiate a QoS resource establishment request in a targeted manner, carrying standardized QoS parameters and service priority identifiers, based on the interaction interface and network standard corresponding to the target policy control entity.

[0086] Those skilled in the art should understand that Figure 8 The functions of each unit in the QoS resource establishment device 800 based on terminal registration information matching under a multi-core network can be understood by referring to the relevant description of the aforementioned QoS resource establishment method based on terminal registration information matching under a multi-core network. Figure 8 The functions of each unit in the QoS resource establishment device 800 based on terminal registration information matching in a multi-core network shown can be implemented by a program running on a processor or by specific logic circuits.

[0087] In one possible implementation, the mapping table is constructed in the following ways: For the LTE core network, establish a mapping and binding relationship between the core network and the policy charging rule function entity and the Rx interaction interface; and for the 5G core network, establish a mapping and binding relationship between the core network and the policy control function entity, the Rx and / or N5 interaction interface. The strategy control entity types and their corresponding interaction interfaces under different systems are uniformly entered into the mapping table.

[0088] In one possible implementation, the signaling processing module 803 is specifically used for: The terminal receives a service registration signaling message, which carries network access attributes collected by the terminal. The network access attributes are encapsulated by the terminal using any one or more combinations of standard signaling header fields, custom extended signaling header fields, and structured message bodies. The received registration signaling is parsed to extract the terminal service identifier, terminal network address, and network access attributes; The extracted terminal service identifier, terminal network address, and network access attributes are associated and bound to generate and store the dynamic binding relationship of the terminal.

[0089] In one possible implementation, the configurable matching strategy includes: The address-first matching mode includes prioritizing matching based on the terminal network address and the network address range in the mapping table. If the match is successful, the target policy control entity is directly determined. If the match fails or there is address ambiguity, network access attribute matching is switched to be enabled. The network attribute priority matching mode includes matching based on the terminal's network access attributes, which is suitable for scenarios where the terminal moves across core networks and the network address remains unchanged, causing the address range matching to fail. The hybrid verification matching mode includes simultaneous network address range matching and network access attribute matching. If the matching results of the two dimensions are consistent, the result is considered valid. If the results conflict, the matching result of the network access attribute that can truly reflect the current access status of the terminal shall prevail.

[0090] In one possible implementation, when network access attribute matching is enabled, the entity matching module is specifically used for: Based on the core network feature identifiers pre-set in the mapping table, core network type matching, network operation identifier matching, and wireless access type matching are completed sequentially, and the candidate core network range is narrowed down layer by layer. Overlay region location identifiers as needed to narrow down the matching range; The target core network to which the terminal currently belongs is determined by multi-layer feature comparison, and the corresponding target policy control entity is matched.

[0091] In one possible implementation, the QoS request module is specifically used for: Based on the core network standard corresponding to the target policy control entity obtained by matching, call the standardized QoS parameters adapted to the network standard. Configure differentiated service priority identifiers based on terminal service type to distinguish between ordinary services and critical services; QoS resources are established based on standardized QoS parameters and service priority identifiers, among which high-priority critical services are configured with network resource preemption rights.

[0092] In one possible implementation, the apparatus further includes a result verification module 806, which, after matching the target policy control entity and before initiating a QoS resource establishment request, is specifically used for: Verify whether the execution result of the two-dimensional matching rule generates a valid target policy control entity; If no valid match is found, the system's default policy control entity is invoked to execute the subsequent QoS resource establishment request process.

[0093] In one possible implementation, the device further includes a monitoring and update module 807, which is specifically used for: Real-time monitoring of terminal re-registration, active deregistration, and registration timeout status; Based on the real-time registration status of the terminal, the corresponding dynamic binding relationship of the terminal is dynamically updated or deleted.

[0094] The aforementioned QoS resource establishment device based on terminal registration information matching in a multi-core network is designed for MCPTT service networking scenarios with multiple heterogeneous core networks. By constructing a two-dimensional matching rule composed of network address ranges and network access attributes, and a configurable multi-mode matching strategy, it effectively overcomes the shortcomings of traditional single-IP matching methods, such as matching lag, cross-network handover identification failure, and incorrect core network selection. It can automatically adapt to the policy control entities and interaction interfaces corresponding to different core network standards in LTE, 5G standalone networking, and LTE / 5G hybrid heterogeneous networking environments, accurately completing the dynamic selection of PCRF / PCF entities and QoS resource establishment. It not only supports standardized QoS management for concurrent group calls of multiple terminals and multiple core networks under conventional stable networking, but also enables QoS management when terminals roam across core networks and IP addresses are not used. In special scenarios where the address remains unchanged, the system accurately identifies the actual network access status of the terminal by relying on network access attributes such as PLMN, ensuring the authenticity and reliability of the matching results. At the same time, this application introduces a differentiated service priority mechanism and resource preemption capability to achieve layered QoS protection for ordinary group call services and emergency call key services, which greatly improves the service reliability in emergency communication scenarios. Furthermore, through the matching anomaly fallback mechanism and dynamic maintenance of terminal binding relationships throughout the entire lifecycle, it effectively avoids service anomalies caused by configuration anomalies, data lag, and changes in registration status. The entire process requires no manual intervention and no additional dedicated network elements, significantly improving the universality, accuracy, stability, and fault tolerance of MCPTT service QoS scheduling under multi-standard converged core networks, and greatly reducing the deployment and maintenance costs of multi-core network interconnection.

[0095] like Figure 9 As shown, Figure 9 This is a schematic diagram of the composition structure of the electronic device 900 provided in the embodiments of this application. The electronic device 900 includes: The device 900 comprises a processor 901, a storage medium 902, and a bus 903. The storage medium 902 stores machine-readable instructions executable by the processor 901. When the electronic device 900 is running, the processor 901 communicates with the storage medium 902 via the bus 903. The processor 901 executes the machine-readable instructions to perform the steps of the QoS resource establishment method based on terminal registration information matching under a multi-core network as described in the embodiments of this application.

[0096] In practical applications, the various components in the electronic device 900 are coupled together via a bus 903. It is understood that the bus 903 is used to achieve communication between these components. In addition to a data bus, the bus 903 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 9 The general designated all buses as Bus 903.

[0097] The aforementioned electronic equipment, designed for MCPTT service networking scenarios with multiple heterogeneous core networks, effectively overcomes the shortcomings of traditional single IP matching methods, such as matching lag, cross-network handover identification failure, and core network selection errors, by constructing a two-dimensional matching rule composed of network address ranges and network access attributes, and a configurable multi-mode matching strategy. It can automatically adapt to the policy control entities and interaction interfaces corresponding to different core network standards in LTE, 5G standalone networking, and LTE / 5G hybrid heterogeneous networking environments, accurately completing the dynamic selection of PCRF / PCF entities and the establishment of QoS resources. It not only supports standardized QoS management for concurrent group call services across multiple terminals and core networks under normal stable networking conditions, but also enables special scenarios where terminals roam across core networks while maintaining the same IP address. In this application, the actual network access status of the terminal is accurately identified by relying on network access attributes such as PLMN, ensuring the authenticity and reliability of the matching results. At the same time, by introducing a differentiated service priority mechanism and resource preemption capability, this application realizes layered QoS guarantee for ordinary group call services and emergency call key services, which greatly improves the service reliability in emergency communication scenarios. Furthermore, through the matching anomaly fallback mechanism and dynamic maintenance of terminal binding relationships throughout the entire lifecycle, it effectively avoids service anomalies caused by configuration anomalies, data lag, and changes in registration status. The entire process requires no manual intervention and no additional dedicated network elements, which significantly improves the universality, accuracy, stability, and fault tolerance of MCPTT service QoS scheduling under multi-standard converged core networks, and greatly reduces the deployment and maintenance costs of multi-core network interconnection.

[0098] This application also provides a computer-readable storage medium storing executable instructions. When the executable instructions are executed by at least one processor 901, the QoS resource establishment method based on terminal registration information matching in a multi-core network as described in this application embodiment is implemented.

[0099] In some embodiments, the storage medium may be a magnetic random access memory (FRAM), a read-only memory (ROM), or a programmable read-only memory (PROM). Erasable Programmable Read-Only Memory (EPROM) Electrically Erasable Programmable Read-Only Memory (EEPROM) Read-only memory, flash memory, magnetic surface storage, optical disc, or CD-ROM ROM, Compact Disc Read It can be a memory such as a memory only; or it can be a device that includes one or any combination of the above-mentioned memories.

[0100] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0101] As an example, executable instructions may, but do not necessarily, correspond to files in the file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborating files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0102] As an example, executable instructions can be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.

[0103] The aforementioned computer-readable storage medium, designed for MCPTT service networking scenarios with multiple heterogeneous core networks, effectively overcomes the shortcomings of traditional single IP matching methods, such as matching lag, cross-network handover identification failure, and core network selection errors, by constructing a two-dimensional matching rule composed of network address ranges and network access attributes, and a configurable multi-mode matching strategy. It can automatically adapt to the policy control entities and interaction interfaces corresponding to different core network standards in LTE, 5G standalone networking, and LTE / 5G hybrid heterogeneous networking environments, accurately completing the dynamic selection of PCRF / PCF entities and the establishment of QoS resources. It not only supports standardized QoS management for concurrent group call services across multiple terminals and core networks under normal stable networking conditions, but also enables services where terminals roam across core networks while maintaining the same IP address. In special scenarios, relying on network access attributes such as PLMN, the actual network access status of the terminal is accurately identified, ensuring the authenticity and reliability of the matching results. At the same time, by introducing a differentiated service priority mechanism and resource preemption capability, this application realizes layered QoS guarantee for ordinary group call services and emergency call key services, which greatly improves the service reliability in emergency communication scenarios. Moreover, through the matching anomaly fallback mechanism and dynamic maintenance of terminal binding relationships throughout the entire lifecycle, it effectively avoids service anomalies caused by configuration anomalies, data lag, and changes in registration status. The entire process requires no manual intervention and no additional dedicated network elements, which significantly improves the universality, accuracy, stability, and fault tolerance of MCPTT service QoS scheduling under multi-standard converged core networks, and greatly reduces the deployment and maintenance costs of multi-core network interconnection.

[0104] In the several embodiments provided in this application, it should be understood that the disclosed methods and electronic devices can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components may be combined, or integrated into another system, or some features may be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0105] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0106] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0107] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a platform server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0108] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for establishing QoS resources based on terminal registration information matching in a multi-core network, characterized in that, Includes the following steps: A mapping table is pre-built and stored, which records the policy control entity addresses, interaction interfaces and core network feature identifiers corresponding to multiple sets of heterogeneous core networks. The core network feature identifiers include network address ranges and network access attributes, which are used to provide benchmark data for subsequent entity matching. When a terminal accesses the core network, the network access attributes corresponding to the current network are automatically collected through native network signaling. The network access attributes are used to characterize the core network identity that the terminal is actually accessing. When a terminal initiates service registration, it receives a registration signaling message carrying the network access attributes. The server parses the registration signaling message, associates the terminal service identifier, the terminal network address, and the network access attributes, and generates and stores the terminal dynamic binding relationship. When it is necessary to establish service QoS resources, the dynamic binding relationship of the terminal is queried. Based on the two-dimensional matching rules composed of the network address range and the network access attributes, the target policy control entity corresponding to the current access core network of the terminal is obtained through the configurable matching strategy. Based on the interaction interface and network standard corresponding to the target policy control entity, a QoS resource establishment request is initiated in a targeted manner, carrying standardized QoS parameters and service priority identifiers.

2. The method according to claim 1, characterized in that, The mapping relationship table is constructed in the following ways: For the LTE core network, establish a mapping and binding relationship between the core network and the policy charging rule function entity and the Rx interaction interface; and for the 5G core network, establish a mapping and binding relationship between the core network and the policy control function entity, the Rx and / or N5 interaction interface. The strategy control entity types and their corresponding interaction interfaces under different systems are uniformly entered into the mapping table.

3. The method according to claim 1, characterized in that, The process of receiving registration signaling carrying the network access attributes, parsing the registration signaling by the server, associating the terminal service identifier, terminal network address, and the network access attributes, and generating and storing the terminal dynamic binding relationship includes: The terminal receives a service registration signaling message, which carries network access attributes collected by the terminal. The network access attributes are encapsulated by the terminal using any one or more combinations of standard signaling header fields, custom extended signaling header fields, and structured message bodies. The received registration signaling is parsed to extract the terminal service identifier, terminal network address, and network access attributes; The extracted terminal service identifier, terminal network address, and network access attributes are associated and bound to generate and store the dynamic binding relationship of the terminal.

4. The method according to claim 1, characterized in that, The configurable matching strategy includes: The address-first matching mode includes prioritizing matching based on the terminal network address and the network address range in the mapping table. If the match is successful, the target policy control entity is directly determined. If the match fails or there is address ambiguity, network access attribute matching is switched to be enabled. The network attribute priority matching mode includes matching based on the terminal's network access attributes, which is suitable for scenarios where the terminal moves across core networks and the network address remains unchanged, causing the address range matching to fail. The hybrid verification matching mode includes simultaneous network address range matching and network access attribute matching. If the matching results of the two dimensions are consistent, the result is considered valid. If the results conflict, the matching result of the network access attribute that can truly reflect the current access status of the terminal shall prevail.

5. The method according to claim 4, characterized in that, When network access attribute matching is enabled, the matching steps include: Based on the core network feature identifiers pre-set in the mapping table, core network type matching, network operation identifier matching, and wireless access type matching are completed sequentially, and the candidate core network range is narrowed down layer by layer. Overlay region location identifiers as needed to narrow down the matching range; The target core network to which the terminal currently belongs is determined by multi-layer feature comparison, and the corresponding target policy control entity is matched.

6. The method according to claim 1, characterized in that, The targeted initiation of the QoS resource establishment request includes: Based on the core network standard corresponding to the target policy control entity obtained by matching, call the standardized QoS parameters adapted to the network standard. Configure differentiated service priority identifiers based on terminal service type to distinguish between ordinary services and critical services; QoS resources are established based on standardized QoS parameters and service priority identifiers, among which high-priority critical services are configured with network resource preemption rights.

7. The method according to claim 1, characterized in that, After the target policy control entity is matched and before the QoS resource establishment request is initiated, the method further includes: Verify whether the execution result of the two-dimensional matching rule generates a valid target policy control entity; If no valid match is found, the system's default policy control entity is invoked to execute the subsequent QoS resource establishment request process.

8. The method according to claim 1, characterized in that, The method further includes: Real-time monitoring of terminal re-registration, active deregistration, and registration timeout status; Based on the real-time registration status of the terminal, the corresponding dynamic binding relationship of the terminal is dynamically updated or deleted.

9. A QoS resource establishment device based on terminal registration information matching in a multi-core network, characterized in that, The device includes: The pre-configuration module is used to pre-build and store a mapping relationship table. The mapping relationship table records the policy control entity addresses, interaction interfaces and core network feature identifiers corresponding to multiple sets of heterogeneous core networks. The core network feature identifiers include network address ranges and network access attributes, which are used to provide benchmark data for subsequent entity matching. The attribute collection module is used to automatically collect the network access attributes corresponding to the current network through native network signaling when the terminal accesses the core network. The network access attributes are used to characterize the identity of the core network that the terminal actually accesses. The signaling processing module is used to receive the registration signaling carrying the network access attribute when the terminal initiates service registration, parse the registration signaling through the server, associate the terminal service identifier, the terminal network address and the network access attribute, and generate and store the terminal dynamic binding relationship. The entity matching module is used to query the dynamic binding relationship of the terminal when it is necessary to establish service QoS resources. Based on the two-dimensional matching rules composed of the network address range and the network access attributes, the module matches the target policy control entity corresponding to the current access core network of the terminal through a configurable matching strategy. The QoS request module is used to initiate a QoS resource establishment request in a targeted manner, carrying standardized QoS parameters and service priority identifiers, based on the interaction interface and network standard corresponding to the target policy control entity.

10. An electronic device, characterized in that, include: The device includes a processor, a storage medium, and a bus. The storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the QoS resource establishment method based on terminal registration information matching in a multi-core network as described in any one of claims 1 to 7.

Images