CN112637252B - Method and system for selecting TCF module in broadband cluster core network - Google Patents
Method and system for selecting TCF module in broadband cluster core network Download PDFInfo
- Publication number
- CN112637252B CN112637252B CN201910903186.4A CN201910903186A CN112637252B CN 112637252 B CN112637252 B CN 112637252B CN 201910903186 A CN201910903186 A CN 201910903186A CN 112637252 B CN112637252 B CN 112637252B
- Authority
- CN
- China
- Prior art keywords
- emmc
- dcn
- cluster
- terminal
- tcf
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
Abstract
The application discloses a method and a system for selecting a TCF module in a broadband cluster core network, wherein the method comprises the following steps: each TCF module informs the corresponding eMMC of a special core network DCN supported by the TCF module; when a cluster terminal accesses a network, eMMC serving for the cluster terminal acquires a UE use type signed by the cluster terminal from eHSS; when the cluster terminal initiates cluster registration, the eMMC serving for the cluster terminal determines the DCN corresponding to the UE usage type subscribed by the cluster terminal according to the mapping relation between the preset UE usage type and the DCN, selects a TCF module supporting the DCN corresponding to the UE usage type from TCF modules connected with the eMMC serving the cluster terminal as the TCF module serving the cluster terminal, and if the selection fails, uses a preset default TCF module as the TCF module serving the cluster terminal. The method and the device are suitable for a scene that a plurality of TCF modules are deployed in the broadband cluster core network.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and a system for selecting a cluster control function (TCF) module in a broadband cluster core network.
Background
The core network architecture defined in the B-Trunc standard architecture supports a single core network architecture, a multi-core network architecture and an access network sharing architecture. As shown in fig. 1, under the local networking single-core network architecture, the system is composed of a single broadband Trunking Core Network (TCN), an LTE broadband trunking terminal, an LTE data terminal, an LTE broadband trunking base station T-eNB, an LTE base station eNB, a scheduling station DC, and a service management station.
3GPP R13 introduced a Dedicated Core Network (DCN) feature. This feature allows multiple private core networks to be deployed within the same Public Land Mobile Network (PLMN), each serving a designated group of users. To support this feature, the 3GPP introduces an optional subscription information parameter at R13: UE Usage Type (UE Usage Type). One UE Usage Type value identifies one DCN, and one core network may support multiple DCNs. The value range of the UE Usage Type parameter is 0-255, that is to say, a PLMN can support 256 private core networks at most.
At present, the scheme of determining the serving TCF module for the UE is only applicable to a scenario where one PLMN supports a single TCF module. Only five logical entities including the eMME, xGW, eHSS, TCF, and TMF are described in the broadband cluster core network defined in the existing B-TrunC standard, but the number of the logical entities is not clear, and how the eMME selects a TCF module for providing a service for the UE if there are multiple TCF modules is also not clear.
Disclosure of Invention
The application provides a method and a system for selecting a TCF module in a broadband cluster core network, which are suitable for a scene of deploying a plurality of TCF modules in the broadband cluster core network.
A method for selecting a TCF module in a broadband cluster core network comprises the following steps:
each cluster control function TCF module informs a corresponding enhanced mobility management entity eNME of a dedicated core network DCN supported by the cluster control function TCF module;
when a cluster terminal accesses a network, eMMC serving for the cluster terminal acquires a UE Usage Type signed by the cluster terminal from an enhanced home subscriber server eHSS;
when the cluster terminal initiates cluster registration, the eMMC serving for the cluster terminal determines the DCN corresponding to the UE usage type subscribed by the cluster terminal according to the mapping relation between the preset UE usage type and the DCN, selects a TCF module supporting the DCN corresponding to the UE usage type from TCF modules connected with the eMMC serving the cluster terminal as the TCF module serving the cluster terminal, and if the selection fails, uses a preset default TCF module as the TCF module serving the cluster terminal.
Preferably, the notifying the corresponding eMME of the DCN information supported by the eMME includes:
and when the TCF module establishes a Tm1 interface with the corresponding eMMC, the TCF module sends the identification information of the DCN supported by the TCF module to the corresponding eMMC.
Preferably, the obtaining, from an eHSS, the UE usage type subscribed to by the cluster terminal by the eMME serving the cluster terminal includes:
when the cluster terminal accesses the network, eMMC serving for the cluster terminal acquires the subscription data of the cluster terminal from the ULA message returned from eHSS, and analyzes the UE use type from the subscription data and stores the UE use type.
Preferably, the method further comprises:
when at least two broadband cluster core networks are used for networking, each eMMC informs a base station of DCN supported by the eMMC; the eMMC module is connected with the eMMC module, wherein the DCN supported by the eMMC module is a collection of DCNs supported by all TCF modules connected with the eMMC module;
and when the trunking terminal performs attachment and/or tracking area update, the base station determines the eMMC serving the trunking terminal according to whether corresponding request messages sent by the trunking terminal contain identification information of the DCN to which the base station belongs and the DCN supported by the eMMC locally stored.
Preferably, the notifying, by the eMME, the DCN supported by the eMME to the base station includes:
when the base station and the eMMC establish an S1-T link, the eMMC carries identification information of DCN supported by the eMMC in an S1-T link establishment response message.
Preferably, the determining the eMME serving the cluster terminal includes:
if the corresponding request message contains the identification information of the DCN to which the trunking terminal belongs, the base station determines the eMME supporting the DCN to which the trunking terminal belongs as the eMME serving the trunking terminal according to the identification information of the DCN to which the trunking terminal belongs; otherwise, the base station determines the preset default eMMC as the eMMC serving for the trunking terminal.
Preferably, the method further comprises:
if the default eMMC ME is determined as the eMMC ME served by the cluster terminal by the base station, the default eMMC ME judges whether the default eMMC ME supports the DCN corresponding to the UE use type signed by the cluster terminal, if not, the cluster terminal is redirected to other eMMC MEs in the broadband cluster core network by initiating a redirection process, and the other eMMC MEs support the DCN corresponding to the UE use type signed by the cluster terminal.
Preferably, the UE usage types and DCNs in the mapping relationship between the UE usage types and DCNs are in one-to-one correspondence.
Preferably, the method further comprises:
when networked by at least two broadband cluster core networks, different eMME supported DCNs are different.
Preferably, the method further comprises:
when the TCF module changes the supported DCN, sending an update request message to the corresponding eMMC, wherein the update request message carries a list of the changed DCN;
and the eMMC updates the DCN information supported by the corresponding TCF module which is locally stored according to the changed DCN list.
A system for selecting a TCF module in a broadband cluster core network comprises: the system comprises a cluster control function TCF module, an enhanced mobility management entity eNME, a base station and an enhanced home subscriber server eHSS; wherein the content of the first and second substances,
the TCF module notifies a dedicated core network DCN supported by the TCF module to a corresponding eNME;
the eMMC acquires the UE use type signed by the trunking terminal from an eHSS when the served trunking terminal accesses a network; when the cluster terminal initiates cluster registration, determining a DCN corresponding to a UE usage type subscribed by the cluster terminal according to a mapping relation between a preset UE usage type and the DCN, selecting a TCF module supporting the DCN corresponding to the UE usage type from TCF modules connected with the TCF module as a TCF module serving the cluster terminal, and if the selection fails, using a preset default TCF module as the TCF module serving the cluster terminal.
Preferably, the notifying, by the TCF module, the corresponding eMME of the DCN information supported by the TCF module includes:
when the Tm1 interface is established with the corresponding eMMC, the identification information of the DCN supported by the eMMC is sent to the corresponding eMMC.
Preferably, the acquiring, by the eMME, the UE usage type subscribed to by the cluster terminal from the eHSS includes:
when the cluster terminal accesses the network, eMMC serving for the cluster terminal acquires the subscription data of the cluster terminal from the ULA message returned from eHSS, and analyzes the UE use type from the subscription data and stores the UE use type.
Preferably, the eMME is configured to notify a base station of DCNs supported by the eMME when the at least two broadband cluster core networks are networked; wherein, the DCN supported by the eGME is a collection of DCNs supported by all TCF modules connected with the eGME
And the base station is used for determining the eMMC serving the trunking terminal according to whether corresponding request information sent by the trunking terminal contains identification information of the DCN to which the base station belongs and the DCN supported by the eMMC locally stored when the trunking terminal is attached or a tracking area is updated.
Preferably, the eMME is configured to notify the base station of the DCN supported by the eMME, and includes:
when the base station establishes an S1-T link with the eMMC, the identification information of the DCN supported by the base station is carried in an S1-T link establishment response message.
Preferably, the base station is configured to determine an eMME serving the trunking terminal, and includes:
if the corresponding request message contains the identification information of the DCN to which the trunking terminal belongs, the base station determines the eMME supporting the DCN to which the trunking terminal belongs as the eMME serving the trunking terminal according to the identification information of the DCN to which the trunking terminal belongs; otherwise, the base station determines the preset default eMMC as the eMMC serving for the trunking terminal.
Preferably, the default eMME is further to: if the base station determines the default eMMC as the eMMC served by the trunking terminal, whether the base station supports the DCN corresponding to the UE use type signed by the trunking terminal is judged, if not, a redirection process is initiated, the trunking terminal is redirected to other eMMC in a broadband trunking core network, and the other eMMC support the DCN corresponding to the UE use type signed by the trunking terminal.
Preferably, the UE usage types and DCNs in the mapping relationship between the UE usage types and DCNs are in one-to-one correspondence.
Preferably, when networked by at least two broadband cluster core networks, different eMME supported DCNs are different.
Preferably, the TCF module is further configured to send an update request message to the corresponding eMME when the TCF module changes the DCN that is supported by the TCF module, where the update request message carries a list of the DCN that has been changed;
the eNME is further configured to update the DCN information supported by the corresponding TCF module stored locally according to the received modified DCN list.
As can be seen from the foregoing technical solutions, in the method and system for selecting a TCF module in a broadband cluster core network provided in this embodiment of the present application, each TCF module notifies an eMME connected to the TCF module of the TCF module, the eMME acquires a UE Usage Type subscribed by a cluster terminal when the cluster terminal accesses a network, and when the cluster terminal initiates cluster registration, determines a DCN corresponding to the UE Usage Type subscribed by the cluster terminal, and selects the TCF module supporting the DCN as a TCF module serving the cluster terminal, so that a TCF module serving the cluster terminal can be selected for the cluster terminal in a scenario where a plurality of TCF modules are deployed in the broadband cluster core network, and thus, independent scheduling of each DCN can be achieved.
Drawings
Fig. 1 is a schematic diagram of a single core network architecture of a local networking;
FIG. 2 is a schematic flow chart of a method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a single broadband cluster core network;
fig. 4 is a schematic structural diagram of a plurality of broadband cluster core network networks;
fig. 5 is a schematic flow chart of a specific implementation of the method embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is further described in detail below by referring to the accompanying drawings and examples.
Fig. 2 is a schematic method flow diagram of an embodiment of the present invention, and as shown in fig. 2, a method for selecting a TCF module in a broadband cluster core network implemented in the embodiment mainly includes:
step 201, each cluster control function (TCF) module notifies a corresponding enhanced mobility management entity (eMME) of a Dedicated Core Network (DCN) supported by the TCF module.
Preferably, the notifying the corresponding eMME of the DCN information supported by the eMME includes:
and when the TCF module establishes a Tm1 interface with the corresponding eMMC, the TCF module sends the identification information of the DCN supported by the TCF module to the corresponding eMMC.
In this step, in order to facilitate the eMME to configure the TCF module matching with the cluster terminal, each TCF module in the broadband cluster core network needs to notify the corresponding eMME of the DCNs supported by the TCF module, so that after the cluster terminal is accessed, the eMME serving the cluster terminal can select the TCF module supporting the DCN to which the cluster terminal belongs based on the DCNs supported by the connected TCF modules, and use the TCF module as the TCF module serving the cluster terminal, thereby realizing independent scheduling of each DCN.
In this step, the eMME needs to acquire the UE UsageType of the trunking terminal when the trunking terminal accesses the network, so that the DCN to which the trunking terminal belongs can be known based on this in the subsequent steps.
Preferably, the eMME serving the trunking terminal in this step may obtain the UE usage type subscribed by the trunking terminal from the eHSS by using the following method:
when the cluster terminal accesses the network, the eMMC serving for the cluster terminal acquires the subscription data of the cluster terminal from a location update response (ULA) message returned from the eHSS, and analyzes the UE use type from the subscription data and stores the UE use type.
In this step, when a cluster terminal initiates cluster registration, an eMME serving the cluster terminal needs to preferentially select a TCF module supporting a DCN to provide services for the cluster terminal according to the DCN corresponding to the UE usage type subscribed by the cluster terminal. Therefore, the TCF module serving the cluster terminal can be ensured to be consistent with the DCN to which the terminal belongs to the maximum extent, and the reliability of serving the cluster terminal can be increased.
Specifically, the UE usage types and DCNs are in one-to-one correspondence in the mapping relationship between the UE usage types and DCNs, that is, the UE usage types corresponding to different DCNs will be different. In practical application, the trunking terminals of the same department will sign the same DCN, so that the UE usage types signed by the trunking terminals of different departments will be different based on the mapping relationship; the UE usage types subscribed by the trunking terminals in the same department will be the same. Thus, based on the above method, independent scheduling of each department can be realized in a scenario where multiple departments share the same eMME and one or more than one eMME xGW.
The method is not only suitable for a single broadband cluster core network networking scenario (as shown in fig. 3), but also suitable for a multiple broadband cluster core network networking scenario (as shown in fig. 4).
The interfaces S1-T, S6a, TC1 and S11 in the figures 3 and 4 are all standard interfaces defined by B-Trunc and 3 GPP. Other interface functions are described below:
tm1 signaling interface between eMME and TCF for transferring cluster related control signaling.
And the user plane interface between Tm2: xGW and TMF is used for transferring cluster user plane data.
EPC HSS in eHSS is centralized in one deployment, THSS can be centralized in one deployment or can be separated in one deployment (for example, each department is deployed independently).
Preferably, in a scenario where a plurality of broadband cluster core networks are networked, to improve reliability of providing a service for a cluster terminal, a network side may select a suitable eMME from a plurality of emmes for the cluster terminal to serve the eMME by using the following method:
when at least two broadband cluster core networks are used for networking, each eMMC informs a base station of DCN supported by the eMMC; the eMMC module is connected with the eMMC module, wherein the DCN supported by the eMMC module is a collection of DCNs supported by all TCF modules connected with the eMMC module;
and when the trunking terminal performs attachment and/or tracking area update, the base station determines the eMMC serving the trunking terminal according to whether corresponding request messages sent by the trunking terminal contain identification information of the DCN to which the base station belongs and the DCN supported by the eMMC locally stored.
Preferably, in order to improve the operation efficiency, the DCN supported by the eMME may be directly configured in the eMME, but the eMME is not limited to this, and the eMME may also learn the DCN supported by the eMME according to the received DCN supported by each TCF module.
Optionally, in the foregoing method, the eMME may notify the base station of the DCN supported by itself by using the following method:
when the base station and the eMMC establish an S1-T link, the eMMC carries identification information of DCN supported by the eMMC in an S1-T link establishment response message.
Preferably, in the above method, the base station may determine the eMME serving the trunking terminal by using the following method:
if the attachment request message or the tracking area update request message contains the identification information of the DCN to which the trunking terminal belongs, the base station determines the eMME supporting the DCN to which the trunking terminal belongs as the eMME serving the trunking terminal according to the identification information of the DCN to which the trunking terminal belongs; otherwise, the base station determines the preset default eMMC as the eMMC serving for the trunking terminal.
Preferably, when selecting the default eMME as the eMME serving the trunking terminal, if the default eMME is not matched with the trunking terminal, the trunking terminal may select a suitable eMME through a redirection procedure, and the specific method is as follows:
if the default eMMC ME is determined as the eMMC ME served by the cluster terminal by the base station, the default eMMC ME judges whether the default eMMC ME supports the DCN corresponding to the UE use type signed by the cluster terminal, if not, the cluster terminal is redirected to other eMMC MEs in the broadband cluster core network by initiating a redirection process, and the other eMMC MEs support the DCN corresponding to the UE use type signed by the cluster terminal.
In the above method, in order to match the eMME serving the trunking terminal with the UE usage type subscribed to the trunking terminal as much as possible, the default eMME needs to determine whether it supports the DCN corresponding to the UE usage type subscribed to the trunking terminal, if not, it needs to select another eMME capable of supporting the DCN corresponding to the UE usage type subscribed to the trunking terminal by using the redirection procedure, and the specific implementation method of the redirection procedure is the same as the existing protocol, which is not described herein again.
Preferably, in order to improve the independence of DCN scheduling, when networking is performed by at least two broadband cluster core networks, the DCNs supported by different emmes may be made different.
Preferably, in order to enable the eMME to accurately select a matching TCF module for the trunking terminal, when the DCN supported by the TCF module changes, the following method may be used to update the DCN information supported by itself and the DCN information supported by the connected TCF module, which are stored in the eMME, so that when a new user accesses a network, the eMME performs TCF selection according to the latest information:
when the TCF module changes the supported DCN, sending an update request message to the corresponding eMMC, wherein the update request message carries a list of the changed DCN;
and the eMMC updates the DCN information supported by the corresponding TCF module which is locally stored according to the changed DCN list.
According to the technical scheme, the TCF modules serving the cluster terminal can be selected for the cluster terminal under the condition that a plurality of TCF modules are deployed in the broadband cluster core network by using the embodiment, and then the independent scheduling of each DCN can be realized. Fig. 5 is a schematic diagram of a specific implementation flow of the above method embodiment, and as shown in fig. 5, the flow mainly includes the following steps:
1. when one broadband cluster core network comprises one eNME and a plurality of TCFs, each TCF and the eNME establish a Tm1 interface and carry a supported DCN ID list. And if the default TCF supports all DCN IDs, carrying the default TCF identification.
2. And when the T-eNB establishes an S1-T link with the eMMC, the eMMC carries a DCN ID list supported by the eMMC in a response message.
3. When the trunking terminal accesses the network, if the trunking terminal carries the DCN ID, the T-eNB selects the corresponding eMMC; otherwise, the T-eBN selects the default eMME.
4. The eMMC acquires the user subscription data from the ULA message returned by the eHSS and maintains the UE Usage Type signed by the user.
5. When a cluster terminal initiates cluster registration, an eMMC selects a proper TCF to provide cluster service for the eMMC according to a UE Usage Type signed by the eMMC and a DCN ID list supported by the TCF. If no suitable TCFs match, the eMMC selects a default TCF for servicing.
6. And when the DCN ID supported by the TCF is changed, sending a configuration updating request message to the eMMC, and carrying an updated DCN ID list. The eGME holds the updated information and returns a response to the TCF. When a new user accesses the network, the eMMC selects the TCF according to the latest information.
Corresponding to the foregoing method embodiment, the present application further provides an embodiment of a system for selecting a TCF module in a broadband trunking core network, including: the system comprises a TCF module, eNME, a base station and eHSS; wherein the content of the first and second substances,
the TCF module notifies a dedicated core network DCN supported by the TCF module to a corresponding eNME;
the eMMC acquires the UE use type signed by the trunking terminal from an eHSS when the served trunking terminal accesses a network; when the cluster terminal initiates cluster registration, determining a DCN corresponding to a UE usage type subscribed by the cluster terminal according to a mapping relation between a preset UE usage type and the DCN, selecting a TCF module supporting the DCN corresponding to the UE usage type from TCF modules connected with the TCF module as a TCF module serving the cluster terminal, and if the selection fails, using a preset default TCF module as the TCF module serving the cluster terminal.
Preferably, the notifying, by the TCF module, the corresponding eMME of the DCN information supported by the TCF module includes:
when the Tm1 interface is established with the corresponding eMMC, the identification information of the DCN supported by the eMMC is sent to the corresponding eMMC.
Preferably, the acquiring, by the eMME, the UE usage type subscribed to the cluster terminal from the eHSS includes:
when the cluster terminal accesses the network, eMMC serving for the cluster terminal acquires the subscription data of the cluster terminal from the ULA message returned from eHSS, and analyzes the UE use type from the subscription data and stores the UE use type.
Preferably, the eMME is configured to notify, when networking is performed by at least two broadband cluster core networks, a base station of DCNs supported by each eMME; the eMMC module is connected with the eMMC module, wherein the DCN supported by the eMMC module is a collection of DCNs supported by all TCF modules connected with the eMMC module;
and the base station is used for determining the eMMC serving the trunking terminal according to whether corresponding request information sent by the trunking terminal contains identification information of the DCN and the DCN supported by the eMMC locally stored when the trunking terminal carries out attachment or tracking area updating.
Preferably, the eMME is configured to notify the base station of the DCN supported by the eMME, and includes:
when the base station establishes an S1-T link with the eMMC, the identification information of the DCN supported by the base station is carried in an S1-T link establishment response message.
Preferably, the base station is configured to determine an eMME serving the trunking terminal, and includes:
if the corresponding request message contains the identification information of the DCN to which the trunking terminal belongs, the base station determines the eMME supporting the DCN to which the trunking terminal belongs as the eMME serving the trunking terminal according to the identification information of the DCN to which the trunking terminal belongs; otherwise, the base station determines the preset default eMMC as the eMMC serving the trunking terminal.
Preferably, the default eMME is further to: if the base station determines the default eMMC as the eMMC served by the trunking terminal, whether the base station supports the DCN corresponding to the UE use type signed by the trunking terminal is judged, if not, a redirection process is initiated, the trunking terminal is redirected to other eMMC in a broadband trunking core network, and the other eMMC support the DCN corresponding to the UE use type signed by the trunking terminal.
Preferably, the UE usage types and DCNs in the mapping relationship between the UE usage types and DCNs are in one-to-one correspondence.
Preferably, when networked by at least two broadband cluster core networks, different emmes support different DCNs.
Preferably, the TCF module is further configured to send an update request message to a corresponding eMME when the TCF module changes a supported DCN, where the update request message carries a list of the changed DCN;
the eNME is further configured to update the DCN information supported by the corresponding TCF module stored locally according to the received modified DCN list.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (20)
1. A method for selecting a TCF module in a broadband cluster core network is characterized by comprising the following steps:
each cluster control function TCF module informs a corresponding enhanced mobility management entity eNME of a dedicated core network DCN supported by the cluster control function TCF module;
when a cluster terminal accesses a network, eMMC serving for the cluster terminal acquires a UE Usage Type signed by the cluster terminal from an enhanced home subscriber server eHSS;
when the cluster terminal initiates cluster registration, the eMMC serving for the cluster terminal determines the DCN corresponding to the UE usage type subscribed by the cluster terminal according to the mapping relation between the preset UE usage type and the DCN, selects a TCF module supporting the DCN corresponding to the UE usage type from TCF modules connected with the eMMC serving the cluster terminal as the TCF module serving the cluster terminal, and if the selection fails, uses a preset default TCF module as the TCF module serving the cluster terminal.
2. The method of claim 1, wherein: the notifying the corresponding eMMC of the DCN information supported by the eMMC comprises the following steps:
and when the TCF module establishes a Tm1 interface with the corresponding eMMC, the TCF module sends the identification information of the DCN supported by the TCF module to the corresponding eMMC.
3. The method of claim 1, wherein: the acquiring, by the eMME serving the cluster terminal, the UE usage type subscribed to by the cluster terminal from the eHSS includes:
when the cluster terminal accesses the network, the eMMC serving for the cluster terminal acquires the subscription data of the cluster terminal from a location update response ULA message returned from the eHSS, and analyzes the UE use type from the subscription data and stores the UE use type.
4. The method of claim 1, wherein: the method further comprises:
when at least two broadband cluster core networks are used for networking, each eMMC informs a base station of DCN supported by the eMMC; the eMMC module is connected with the eMMC module, wherein the DCN supported by the eMMC module is a collection of DCNs supported by all TCF modules connected with the eMMC module;
and when the trunking terminal performs attachment and/or tracking area update, the base station determines the eMMC serving the trunking terminal according to whether corresponding request messages sent by the trunking terminal contain identification information of the DCN to which the base station belongs and the DCN supported by the eMMC locally stored.
5. The method of claim 4, wherein: the eMMC notifying the base station of the DCN supported by the eMMC comprises the following steps:
when the base station and the eMMC establish an S1-T link, the eMMC carries identification information of DCN supported by the eMMC in an S1-T link establishment response message.
6. The method of claim 4, wherein: the determining the eNME serving the cluster terminal includes:
if the corresponding request message contains the identification information of the DCN to which the trunking terminal belongs, the base station determines the eMME supporting the DCN to which the trunking terminal belongs as the eMME serving the trunking terminal according to the identification information of the DCN to which the trunking terminal belongs; otherwise, the base station determines the preset default eMMC as the eMMC serving for the trunking terminal.
7. The method of claim 6, wherein the method further comprises:
if the base station determines the default eMMC as the eMMC served by the trunking terminal, the default eMMC judges whether the default eMMC supports the DCN corresponding to the UE use type signed by the trunking terminal, if not, the attachment request message of the trunking terminal is redirected to other eMMC in a broadband trunking core network by initiating a redirection process, and the other eMMC support the DCN corresponding to the UE use type signed by the trunking terminal.
8. The method of claim 1, wherein: and the UE use types and the DCNs are in one-to-one correspondence in the mapping relation between the UE use types and the DCNs.
9. The method of claim 1, wherein: the method further comprises:
when networked by at least two broadband cluster core networks, different eMME supported DCNs are different.
10. The method of claim 1, wherein: the method further comprises:
when the TCF module changes the supported DCN, sending an update request message to the corresponding eMMC, wherein the update request message carries a list of the changed DCN;
and the eMMC updates the DCN information supported by the corresponding TCF module which is locally stored according to the changed DCN list.
11. A system for selecting a TCF module in a broadband trunking core network, comprising: the system comprises a cluster control function TCF module, an enhanced mobility management entity eNME, a base station and an enhanced home subscriber server eHSS; wherein the content of the first and second substances,
the TCF module notifies a dedicated core network DCN supported by the TCF module to a corresponding eNME;
the eMMC acquires the UE use type signed by the trunking terminal from an eHSS when the served trunking terminal accesses a network; when the cluster terminal initiates cluster registration, determining a DCN corresponding to a UE usage type subscribed by the cluster terminal according to a mapping relation between a preset UE usage type and the DCN, selecting a TCF module supporting the DCN corresponding to the UE usage type from TCF modules connected with the TCF module as a TCF module serving the cluster terminal, and if the selection fails, using a preset default TCF module as the TCF module serving the cluster terminal.
12. The system of claim 11, wherein: the TCF module notifies the corresponding eMMC with the DCN information supported by the TCF module, and the method comprises the following steps:
when the Tm1 interface is established with the corresponding eMMC, the identification information of the DCN supported by the eMMC is sent to the corresponding eMMC.
13. The system of claim 11, wherein: the eMMC acquires the UE use type signed by the cluster terminal from the eHSS, and the method comprises the following steps:
when the cluster terminal accesses the network, eMMC serving for the cluster terminal acquires the subscription data of the cluster terminal from the ULA message returned from eHSS, and analyzes the UE use type from the subscription data and stores the UE use type.
14. The system of claim 11, wherein: the eMMC is used for notifying a DCN supported by each eMMC to a base station when at least two broadband cluster core networks are used for networking; the eMMC module is connected with the eMMC module, wherein the DCN supported by the eMMC module is a collection of DCNs supported by all TCF modules connected with the eMMC module;
and the base station is used for determining the eMMC serving the trunking terminal according to whether corresponding request information sent by the trunking terminal contains identification information of the DCN to which the base station belongs and the DCN supported by the eMMC locally stored when the trunking terminal is attached or a tracking area is updated.
15. The system of claim 14, wherein: the eMMC is used for notifying the DCN supported by the eMMC to a base station, and comprises the following steps:
when the base station establishes an S1-T link with the eMMC, the identification information of the DCN supported by the base station is carried in an S1-T link establishment response message.
16. The system of claim 15, wherein: the base station, configured to determine an eMME serving the trunking terminal, includes:
if the corresponding request message contains the identification information of the DCN to which the trunking terminal belongs, the base station determines the eMME supporting the DCN to which the trunking terminal belongs as the eMME serving the trunking terminal according to the identification information of the DCN to which the trunking terminal belongs; otherwise, the base station determines the preset default eMMC as the eMMC serving for the trunking terminal.
17. The system of claim 16, wherein the default eMME is further to: if the base station determines the default eMMC as the eMMC served by the trunking terminal, whether the base station supports the DCN corresponding to the UE use type signed by the trunking terminal is judged, if not, a redirection process is initiated, the trunking terminal is redirected to other eMMC in a broadband trunking core network, and the other eMMC support the DCN corresponding to the UE use type signed by the trunking terminal.
18. The system of claim 11, wherein: and the UE use types and the DCNs are in one-to-one correspondence in the mapping relation between the UE use types and the DCNs.
19. The system of claim 11, wherein: when networked by at least two broadband cluster core networks, different eMME supported DCNs are different.
20. The system of claim 11, wherein: the TCF module is further configured to send an update request message to the corresponding eMME when the TCF module changes the DCN that is supported, where the update request message carries a list of the DCN that has been changed;
the eMMC is further configured to update, according to the received modified DCN list, DCN information supported by a corresponding TCF module stored locally.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910903186.4A CN112637252B (en) | 2019-09-24 | 2019-09-24 | Method and system for selecting TCF module in broadband cluster core network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910903186.4A CN112637252B (en) | 2019-09-24 | 2019-09-24 | Method and system for selecting TCF module in broadband cluster core network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112637252A CN112637252A (en) | 2021-04-09 |
| CN112637252B true CN112637252B (en) | 2022-05-13 |
Family
ID=75283203
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910903186.4A Active CN112637252B (en) | 2019-09-24 | 2019-09-24 | Method and system for selecting TCF module in broadband cluster core network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112637252B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN86100698A (en) * | 1986-01-23 | 1987-08-05 | 日本电气株式会社 | Facsimile communication apparatus |
| JP2000151956A (en) * | 1998-11-10 | 2000-05-30 | Ricoh Co Ltd | Method for controlling group 3 facsimile equipment |
| CN109429180A (en) * | 2017-06-26 | 2019-03-05 | 大唐移动通信设备有限公司 | The method and apparatus of data exchange |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009017000A (en) * | 2007-07-02 | 2009-01-22 | Oki Electric Ind Co Ltd | Communication device |
-
2019
- 2019-09-24 CN CN201910903186.4A patent/CN112637252B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN86100698A (en) * | 1986-01-23 | 1987-08-05 | 日本电气株式会社 | Facsimile communication apparatus |
| JP2000151956A (en) * | 1998-11-10 | 2000-05-30 | Ricoh Co Ltd | Method for controlling group 3 facsimile equipment |
| CN109429180A (en) * | 2017-06-26 | 2019-03-05 | 大唐移动通信设备有限公司 | The method and apparatus of data exchange |
Non-Patent Citations (7)
| Title |
|---|
| "[MBMS] R2-152454 - Summary of solution assumptions for SC-PTM";Ericsson;《3GPP tsg_ran\WG2_RL2》;20150515;全文 * |
| "ftp-TdocsByAgenda";佚名;《3GPP tsg_sa\WG2_Arch》;20150424;全文 * |
| "TDoc_List_Meeting_S2-108";佚名;《3GPP tsg_sa\WG2_Arch》;20150612;全文 * |
| P802.11-REVmc/D6.0, Jun 2016 - IEEE Draft Standard for Information technology;佚名;《IEEE》;20161231;全文 * |
| 基于LTE的宽带集群通信系统核心网络设备测试方法研究;刘荣朵等;《信息通信技术与政策》;20181115(第11期);全文 * |
| 基于NiosⅡ传真通信规程的分析与设计实现;支亚军等;《电子技术应用》;20090906(第09期);全文 * |
| 无缓存光分组交换机搭建的平坦数据中心架构;闫付龙等;《北京邮电大学学报》;20160815(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112637252A (en) | 2021-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11570827B2 (en) | Network-initiated PDU session connection update method between terminal and network | |
| EP3509336B1 (en) | Finding an appropriate session management network function in a home plmn through a network function repository function | |
| WO2021194265A1 (en) | Communication method and device for edge computing system | |
| CN110383866B (en) | Method, device and system for directly connecting link resource configuration and readable storage medium | |
| WO2019035637A1 (en) | Method for capability negotiation and slice information mapping between network and terminal in 5g system | |
| TWI629908B (en) | Method, device and base station for switching terminal equipment to target cell | |
| CN104969619B (en) | Backhaul link establishment method, base station, relay node and system | |
| CN105848131A (en) | Method for realizing STA cross-domain roaming through cloud AC | |
| CN114501469A (en) | Method, device and system for configuring network slice | |
| CN110602803B (en) | Method for limiting user terminal to access UPF | |
| WO2022025666A1 (en) | Method and device for simultaneously using network slices | |
| WO2019216663A1 (en) | Method and device for controlling rrc state mismatch issue in next-generation mobile communication system | |
| WO2021235769A1 (en) | Method and device for supporting deterministic communication for terminal in mobile communication network | |
| CN114666859A (en) | Method and apparatus for selecting a session management entity serving a wireless communication device | |
| CN113572864A (en) | Data processing method, network element equipment and readable storage medium | |
| US20190200207A1 (en) | Techniques for providing subscriber-specific routing of a roaming user equipment in a visited communication network | |
| US10455358B2 (en) | Prose information transmission method, terminal, and communications device | |
| CN112637252B (en) | Method and system for selecting TCF module in broadband cluster core network | |
| CN111132256B (en) | User terminal access method, initial mobile management entity and base station | |
| EP2359610B1 (en) | Providing access to a gprs network | |
| CN102857953A (en) | Self-configuration method and device of base station | |
| WO2021235781A1 (en) | Method and apparatus for discovering and selecting network providing connectivity for provisioning user subscription data | |
| CN112867016B (en) | Core network equipment for broadband trunking communication and deployment method and device thereof | |
| CN117793688A (en) | New method for external parameter provisioning for AF sessions | |
| CN108616956B (en) | Method for service isolation in electric power wireless private network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |