CN113099465B - B-Trunc cluster networking architecture - Google Patents
B-Trunc cluster networking architecture Download PDFInfo
- Publication number
- CN113099465B CN113099465B CN201911342845.8A CN201911342845A CN113099465B CN 113099465 B CN113099465 B CN 113099465B CN 201911342845 A CN201911342845 A CN 201911342845A CN 113099465 B CN113099465 B CN 113099465B
- Authority
- CN
- China
- Prior art keywords
- tcn
- office
- gateway
- cluster
- offices
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/08—Trunked mobile radio systems
Abstract
The invention provides a B-Trunc cluster networking architecture. The architecture includes: the system comprises a plurality of cluster sub-offices, wherein each cluster sub-office comprises a gateway office and at least one cluster core network TCN, any two TCNs in each cluster sub-office are connected through an intra-office interface, all TCNs are connected with the gateway offices in the corresponding cluster sub-offices through cross-office interfaces, the gateway offices of any two cluster sub-offices are connected through inter-office interfaces, and the gateway offices are used for establishing connection between the TCNs in the corresponding cluster sub-offices and other cluster sub-offices. The B-Trunc cluster networking architecture establishes the connection between the TCN in the corresponding cluster sub-office and other cluster sub-offices by setting the gateway office, thereby realizing that the internal topology and the network parameter change of each cluster sub-office can be shielded outwards by the gateway office, and being beneficial to networking.
Description
Technical Field
The invention relates to a cluster communication technology, in particular to a B-trunk cluster networking architecture.
Background
Broadband Trunking Communication (B-TrunC) is a TD-LTE-based "LTE digital transmission + Trunking voice Communication" private network Broadband Trunking system standard established by Broadband Trunking industry alliance organization.
Currently, a B-TrunC system cross-cluster core network architecture supports 2 architectures: a unified Evolved Home Subscriber Server (eHSS for short) and a distributed eHSS.
However, no matter the B-TrunC unified eHSS networking or the distributed eHSS networking is adopted, the TC2 interfaces between the core networks are all of a full interconnection architecture, but the TC2 interfaces are fully interconnected and coupled between the core networks, which is not beneficial to group national large networks.
Disclosure of Invention
The invention provides a B-Trunc cluster networking architecture, which is used for solving the technical problem that the existing B-Trunc cluster networking architecture is not beneficial to networking due to the fact that interfaces are fully interconnected.
The invention provides a B-trunk cluster networking architecture, which comprises the following components: a plurality of cluster sub-offices;
each cluster sub-office comprises a gateway office and at least one cluster core network TCN;
any two TCNs in each cluster sub-office are connected through an intra-office interface, and all TCNs are connected with gateway offices in the corresponding cluster sub-offices through cross-office interfaces;
the gateway offices of any two cluster sub-offices are connected through an interoffice interface;
the gateway bureau is used for establishing the connection between the TCN in the corresponding cluster sub-bureau and other cluster sub-bureaus.
In this embodiment, a plurality of cluster sub-offices are constructed, where each cluster sub-office includes a gateway office and at least one cluster core network TCN, any two TCNs in each cluster sub-office are connected through an intra-office interface, all the TCNs are connected to the gateway offices in the corresponding cluster sub-office through cross-office interfaces, the gateway offices of any two cluster sub-offices are connected through an inter-office interface, and the gateway offices are used to establish connections between the TCNs in the corresponding cluster sub-offices and other cluster sub-offices, so that internal topology and network parameter changes of each cluster sub-office can be shielded from outside through the gateway offices, and a group large network is facilitated.
In one possible design, TCN administration information is exchanged between any two TCNs in each cluster sub-office through the intra-office interface, the TCN administration information including a TCN administration number segment and TCN address information.
In this embodiment, the TCN administration information is exchanged between any two TCNs in each cluster sub-office through the intra-office interface, so as to implement automatic exchange between TCNs in the cluster sub-offices.
In one possible design, the gateway bureau acquires administration information of the gateway bureau through the cross bureau interface, the administration information of the gateway bureau comprises a number section administered by the gateway bureau and address information of the gateway bureau, and the number section administered by the gateway bureau is determined according to all TCN administration number sections in the corresponding cluster sub-bureau.
In this embodiment, the gateway bureau obtains the TCN administration information of all TCNs in the corresponding cluster sub-bureau through the cross-bureau interface, so as to determine the administration information of the gateway bureau.
In one possible design, the gateway offices of any two cluster sub-offices exchange administration information of the gateway offices through the interoffice interface.
In this embodiment, the gateway offices of each cluster sub-office exchange gateway office administration information through the inter-office interface, so as to realize automatic exchange of gateway office administration information between the gateway offices of each cluster sub-office.
In one possible design, the group affiliation TCN performs control panel signaling replication distribution among TCNs in the cluster sub-office based on the stored TCN administration information.
In a possible design, the gateway office corresponding to the group affiliation TCN performs addressing, copying, and distributing of control panel signaling between cluster sub-offices according to the cluster sub-office where the group subscriber terminal UE resides.
In a possible design, the gateway office corresponding to the TCN where the group member resides receives the control panel signaling of the gateway office corresponding to the TCN to which the group belongs, and duplicates and distributes the control panel signaling between the TCNs of the corresponding cluster sub-offices.
In this embodiment, the group-homed TCN TC2 signaling addressing complexity is reduced by implementing a multi-level replicated distribution of control panel signaling.
In one possible design, the group affiliation TCN performs user plane data copy distribution among TCNs in the cluster sub-office according to the stored TCN administration information.
In a possible design, the gateway corresponding to the group affiliation TCN performs addressing, copying and distributing of user plane data between the cluster sub-offices according to the cluster sub-office where the group subscriber terminal UE resides.
In a possible design, the gateway office corresponding to the TCN where the group member resides receives the control panel signaling of the gateway office corresponding to the TCN to which the group belongs, and copies and distributes the user plane data between the TCNs of the corresponding trunking sub-offices.
In the embodiment, the multi-stage copy distribution of the user plane data is realized, so that the processing complexity of the group attribution TCN TC2 user plane data is reduced.
The B-Trunc cluster networking architecture provided by the invention is characterized in that a plurality of cluster sub-offices are constructed, wherein each cluster sub-office comprises a gateway office and at least one cluster core network TCN, any two TCNs in each cluster sub-office are connected through an intra-office interface, all TCNs are connected with the gateway offices in the corresponding cluster sub-offices through cross-office interfaces, the gateway offices of any two cluster sub-offices are connected through inter-office interfaces, and the gateway offices are used for establishing the connection between the TCNs in the corresponding cluster sub-offices and other cluster sub-offices, so that the internal topology and network parameter change of each cluster sub-office can be shielded through the gateway offices, and the networking is facilitated.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a diagram illustrating a B-TrunC unified eHSS networking architecture in accordance with an exemplary embodiment of the present invention;
FIG. 2 is a schematic diagram of a B-Trunc distributed eHSS networking architecture in accordance with an exemplary embodiment of the present invention;
fig. 3 is a schematic architecture diagram of the fully interconnected form of interfaces between core networks of the B-TrunC shown in fig. 1 or fig. 2;
fig. 4 is an architecture diagram illustrating a B-TrunC cluster networking architecture in accordance with an exemplary embodiment of the present invention;
FIG. 5 is a schematic illustration of jurisdiction number segment exchange, shown in accordance with an exemplary embodiment of the present invention;
FIG. 6 is an interaction diagram illustrating control panel signaling replication distribution in accordance with an exemplary embodiment of the present invention;
FIG. 7 is a user plane data replication distribution interaction diagram that is shown in accordance with an exemplary embodiment of the present invention.
With the above figures, certain embodiments of the invention have been illustrated and described in more detail below. The drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
Broadband Trunking Communication (B-TrunC) is a TD-LTE-based "LTE digital transmission + Trunking voice Communication" private network Broadband Trunking system standard established by Broadband Trunking industry alliance organization. Currently, a B-TrunC system cross-cluster core network architecture supports 2 architectures: a unified Evolved Home Subscriber Server (eHSS for short) and a distributed eHSS. However, no matter the B-TrunC unified eHSS networking or the distributed eHSS networking is adopted, the TC2 interfaces between the core networks are all of a full interconnection architecture, but the TC2 interfaces are coupled between the core networks in a full interconnection manner, which is not beneficial to group of national large networks.
Fig. 1 is a schematic diagram of a B-TrunC unified eHSS networking architecture according to an exemplary embodiment of the present invention. As shown in fig. 1, in the B-TrunC unified eHSS networking architecture provided in this embodiment, a whole Network (e.g., a railway) of a B-TrunC operator/industry field is an eHSS, and a plurality of Trunking Core Networks (TCNs) are provided, where a Public Land Mobile Network (PLMN) is one Public Land Mobile Network (PLMN), and interconnection between TCNs of the Public Land Mobile Networks (PLMN) adopts the unified eHSS architecture.
Fig. 2 is a schematic diagram illustrating a B-TrunC distributed eHSS networking architecture according to an exemplary embodiment of the present invention. As shown in fig. 2, in the B-TrunC distributed eHSS networking architecture provided in this embodiment, a B-TrunC operator network has an eHSS and a TCN and has an independent PLMN, and at this time, the multiple operator networks are interconnected to form the distributed eHSS architecture.
With continuing reference to fig. 1-2, the various parts of the figures are explained: an Evolved Mobility Management Entity (eMME), a Trunking Control Function (TCF), a Trunking Media Function (TMF), and a Trunking Gateway (xGW). Specifically, for the specific description of the unified eHSS and the distributed eHSS, reference may be made to a white paper of LTE wideband trunking communication (B-TrunC) technology, which is not described herein again.
Fig. 3 is a schematic diagram of a fully interconnected interface between core networks of the B-TrunC shown in fig. 1 or fig. 2. As shown in fig. 3, the TC2 interface between the core networks is a full interconnect architecture regardless of whether a B-TrunC centralized eHSS networking or a distributed eHSS networking is adopted. The TC2 interfaces are all interconnected, and specifically have the following risks and constraints:
firstly, a full interconnection architecture is adopted among subnetworks, and core networks which are required by interconnection among systems or terminal roaming need to be directly interconnected by TC 2. Therefore, the system has a full interconnection structure and no topology hiding function in the sub-network.
And secondly, when a nationwide large network is formed, if a B-trunk core network is newly added, other core networks need to be added to the TC2 interface configuration of the new core network. At present, a B-Trunc TC2 interface is a full interconnection architecture and has no TC2 interface proxy node.
And thirdly, the B-Trunc protocol number segment relation table is in static configuration. Each TCF needs to manually configure the administration number table of the TCF of the whole network. The number segment table can only be configured manually and statically, and no number segment managed by each subnet has no automatic exchange mechanism.
Fourthly, each TCF needs to manually configure the domain name table of each subnet and system network element of the whole network so as to search the eHSS, TCF and TMF domain name of the home subnet according to the user number. Only the domain name table of the equipment of a manual static system can be used, and no number administration section of each sub-network has no automatic exchange mechanism.
And fifthly, only the group master control TCF is subjected to primary replication distribution, namely, the cross-core network joint grouping is carried out, and the group master control TCF/TMF performs replication distribution to other core networks where the group members reside. Therefore, a multi-level distribution mechanism of a cluster user plane is not provided, group user plane copy and distribution are primary copy, and a group master control TCF/TMF is loaded.
In view of the above technical problems, an embodiment of the present invention provides a B-TrunC cluster networking architecture, where a plurality of cluster sub-offices are constructed, where each cluster sub-office includes a gateway office and at least one cluster core network TCN, any two TCNs in each cluster sub-office are connected through an intra-office interface, all TCNs are connected with the gateway offices in the corresponding cluster sub-office through a cross-office interface, the gateway offices of any two cluster sub-offices are connected through an inter-office interface, and the gateway office is used to establish connections between the TCNs in the corresponding cluster sub-offices and other cluster sub-offices, so that internal topology and network parameter changes of each cluster sub-office can be shielded from outside through the gateway offices, and a large network can be formed.
The following describes the technical solutions of the present invention and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present invention will be described below with reference to the accompanying drawings.
Fig. 4 is a schematic architecture diagram illustrating a B-TrunC cluster networking architecture according to an exemplary embodiment of the present invention. As shown in fig. 4, the B-TrunC cluster networking architecture provided in this embodiment includes: a plurality of cluster sub-offices. Each cluster sub-office comprises a gateway office and at least one cluster core network TCN, wherein any two TCNs in each cluster sub-office are connected through an intra-office interface, all TCNs are connected with the gateway offices in the corresponding cluster sub-offices through cross-office interfaces, the gateway offices of any two cluster sub-offices are connected through inter-office interfaces, and the gateway offices are used for establishing connection between the TCNs in the corresponding cluster sub-offices and other cluster sub-offices.
Continuing with fig. 4, it may be exemplified that the B-TrunC cluster networking architecture includes two cluster sub-offices (cluster sub-office a and cluster sub-office C), each of which includes x TCNs and one gateway office (cluster sub-office a includes gateway office a and TCN A1-TCN Ax, and cluster sub-office C includes gateway office C and TCN C1-TCN Cx).
In the cluster sub-office A, a TCN A1 is connected with a TCN Ax through an intra-office interface (TC 2), and TCN A1-TCN Ax are respectively connected with a gateway office A through a cross-office interface (TC 2 cross-office). In the cluster sub-office C, the TCN C1 is connected with the TCN Cx through an intra-office interface (TC 2), and the TCN C1-TCN Cx are respectively connected with the gateway office C through a cross-office interface (TC 2 cross-office). The connection between the cluster sub-office a and the cluster sub-office C may be via an inter-office interface (TC 2 inter-office relay).
The TCN in the cluster sub-office A is communicated with the cluster sub-office C through the gateway office A, and the TCN in the cluster sub-office C is communicated with the cluster sub-office A through the gateway office C, so that the internal topology and the network parameter change of each cluster sub-office can be shielded from the outside through the gateway office.
In this embodiment, a plurality of cluster sub-offices are constructed, where each cluster sub-office includes a gateway office and at least one cluster core network TCN, any two TCNs in each cluster sub-office are connected through an intra-office interface, all the TCNs are connected to the gateway offices in the corresponding cluster sub-office through cross-office interfaces, the gateway offices of any two cluster sub-offices are connected through an inter-office interface, and the gateway offices are used to establish connections between the TCNs in the corresponding cluster sub-offices and other cluster sub-offices, so that internal topology and network parameter changes of each cluster sub-office can be shielded from outside through the gateway offices, and a group large network is facilitated.
Fig. 5 is a diagram illustrating jurisdiction number segment exchange in accordance with an exemplary embodiment of the present invention. As shown in fig. 5, in this embodiment, TCN administration information is exchanged between any two TCNs in each cluster sub-office through an intra-office interface, where the TCN administration information includes a TCN administration number segment and TCN address information.
For example, in Cluster Subserve A, TCN jurisdiction for TCN A1 is 010, while TCN A1 IP is 10.10.10.10, TCN jurisdiction for TCN Ax is 011, while TCN Ax IP is 10.10.10.11. In the cluster sub-office a, the TCN A1 and the TCN Ax exchange their TCN administration number segments and TCN address information via an intra-office interface (TC 2). After all the TCNs in the cluster sub-office a complete the TCN administration information exchange, each TCN in the cluster sub-office a includes the TCN administration information that all the TCNs in the cluster sub-office a complete the TCN, and in addition, the TCN administration information of the TCNs outside the cluster sub-office a may also be determined. Specifically, after all TCNs in the cluster sub-office a complete the TCN administration information exchange, the TCN A1 or the TCN Ax stores the following information: the TCN jurisdiction number section of the TCN A1 is 010, and the TCN A1 IP is 10.10.10.10; the TCN jurisdiction number section of TCN Ax is 011, and the TCN Ax IP is 10.10.10.11; the number section of the outgoing TCN in jurisdiction is all number sections except 010-011, and the corresponding IP address is IP10.10.10.1 of gateway A.
Correspondingly, in cluster sub-office C, TCN C1 has a TCN jurisdiction number of 020 and TCN C1 IP of 20.20.20.20, TCN Cx has a TCN jurisdiction number of 021, and TCN Cx IP of 20.20.20.21. In the cluster sub-office C, the TCN C1 and the TCN Cx exchange their TCN administration number segments and TCN address information via the intra-office interface (TC 2). After all the TCNs in the cluster sub-office C complete the TCN administration information exchange, each TCN in the cluster sub-office C includes the TCN administration information that all the TCNs in the cluster sub-office C complete the TCN administration, and in addition, the TCN administration information of the TCNs outside the cluster sub-office C may also be determined. Specifically, after all TCNs in the cluster sub-office C complete the TCN administration information exchange, the TCN C1 or TCN Cx stores the following information: TCN jurisdiction number segment of TCN C1 is 020, TCN C1 IP is 20.20.20.20; TCN administration section of TCN Cx is 021, TCN Cx IP is 20.20.20.21; the number section of the outgoing TCN is controlled to be all the number sections except 020-021, and the corresponding IP address is IP20.20.20.1 of the gateway office C.
In this embodiment, the TCN administration information is exchanged between any two TCNs in each cluster sub-office through the intra-office interface, so as to implement automatic exchange between the TCNs in the cluster sub-offices.
In addition, the gateway bureau of each cluster sub-bureau acquires administration information of the gateway bureau through a cross-bureau interface, wherein the administration information of the gateway bureau comprises a number section administered by the gateway bureau and address information of the gateway bureau, and the number section administered by the gateway bureau is determined according to all TCN administration number sections in the corresponding cluster sub-bureau.
For example, in the cluster sub-office a, the external gateway administration information of the gateway a includes the administration number section of the gateway a and the gateway a IP, specifically, the administration number section of the gateway a is 010-011, and the gateway a IP (or TCN IP) is 10.10.10.1. In addition, the gateway A also stores a TCN jurisdiction number segment of TCN A1 of 010, TCN A1 IP of 10.10.10.10; TCN Ax has a TCN jurisdiction number of 011.
Correspondingly, in the cluster sub-bureau C, the administration information of the external gateway bureau of the gateway bureau a includes the administration number segment of the gateway bureau a and the gateway bureau C IP, specifically, the administration number segment of the gateway bureau C is 020-021, and the gateway bureau C IP (or TCN IP) is 20.20.20.20.1. In addition, the gateway bureau C also stores TCN administration number segment of TCN C1 as 020, TCN C1 IP as 20.20.20.20; TCN administration number of TCN Cx is 021, TCN Cx IP is 20.20.20.21.
In this embodiment, the gateway office obtains the TCN administration information of all TCNs in the corresponding cluster sub-office through the cross-office interface, thereby determining the TCN administration information of the gateway office
In addition, the administration information of the gateway bureaus can be exchanged between the gateway bureaus of any two cluster sub-bureaus through an interoffice interface.
For example, after the cluster sub-office a exchanges gateway administration information with the cluster sub-office C through the inter-office interface, the external gateway administration information of the gateway office a of the cluster sub-office a may include: the jurisdiction number section of the gateway A is 010-011, the IP (or TCN IP) of the gateway A is 10.10.10.1, the jurisdiction number section of the TCN C1 in the gateway C is 020, and the jurisdiction number section of the TCN C1 IP is 20.20.20.20.
Correspondingly, after the cluster sub-office C exchanges gateway administration information with the cluster sub-office a through the inter-office interface, the external gateway administration information of the gateway office C of the cluster sub-office C may include: the administration number section of TCN C1 is 020, the administration number section of TCN C1 IP is 20.20.20.20, the administration number section of the gateway A is 010-011, and the IP (or TCN IP) of the gateway A is 10.10.10.1.
In this embodiment, gateway bureaus administration information is exchanged between the gateway bureaus of each cluster sub-bureau through an interoffice interface, so that automatic exchange of the gateway bureaus administration information between the gateway bureaus of each cluster sub-bureau is realized.
Fig. 6 is an interaction diagram illustrating control panel signaling copy distribution in accordance with an exemplary embodiment of the present invention. As shown in fig. 6, the control panel signaling copy distribution in the present embodiment may be a multi-level copy distribution, so as to reduce the complexity of group home TCN TC2 signaling addressing.
Optionally, the replication distribution may be divided into three levels, specifically as follows:
a first stage: group affiliation TCN: and the TCN of the group affiliation copies and distributes the control panel signaling between the TCNs in the cluster sub-office according to the stored information administered by the TCN.
And a second stage: group affiliation TCN gateway: and the gateway office corresponding to the group attribution TCN performs control panel signaling addressing, copying and distributing among the cluster sub-offices according to the cluster sub-offices where the group subscriber terminal UE resides. The acquisition scheme of the cluster sub-office where the group signed UE resides may be a home cluster sub-network of a pre-stored group signed member, a cluster sub-network gateway office, and a TCN.
And a third stage: TCN gateway where group members reside: and the gateway office corresponding to the TCN where the group member resides receives the control panel signaling of the gateway office corresponding to the TCN to which the group belongs, and copies and distributes the control panel signaling between the TCNs of the corresponding cluster sub-offices.
FIG. 7 is a user plane data replication distribution interaction diagram that is shown in accordance with an exemplary embodiment of the present invention. As shown in fig. 7, the user plane data replication distribution in this embodiment may be multi-level replication distribution, so as to reduce the complexity of processing the group-homed TCN TC2 user plane data.
Optionally, the method may be divided into three levels of replication distribution, which is specifically as follows:
a first stage: group affiliation TCN: and the group attribution TCN copies and distributes user plane data among the TCNs in the cluster sub-office according to the stored TCN administration information.
And a second stage: group affiliation TCN gateway: and the gateway corresponding to the group attribution TCN performs user plane data addressing, copying and distributing among the cluster sub-offices according to the cluster sub-offices where the group subscriber terminal UE resides.
And a third stage: TCN gateway where group members reside: and the gateway corresponding to the TCN where the group member resides receives the control panel signaling of the gateway corresponding to the TCN to which the group belongs, and copies and distributes the user plane data between the TCNs of the corresponding cluster sub-offices.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (7)
1. A B-Trunc cluster networking architecture, comprising: a plurality of cluster sub-offices;
each cluster sub-office comprises a gateway office and at least one cluster core network TCN;
any two TCNs in each cluster sub-office are connected through an intra-office interface, and all TCNs are connected with gateway offices in the corresponding cluster sub-offices through cross-office interfaces;
the gateway offices of any two cluster sub-offices are connected through an interoffice interface;
the gateway bureau is used for establishing the connection between the TCN in the corresponding cluster sub-bureau and other cluster sub-bureaus;
exchanging TCN administration information between any two TCNs in each cluster sub-office through the intra-office interface, wherein the TCN administration information comprises a TCN administration number section and TCN address information;
the gateway bureau acquires the administration information of the gateway bureau through the cross bureau interface, wherein the administration information of the gateway bureau comprises a number section administered by the gateway bureau and address information of the gateway bureau, and the number section administered by the gateway bureau is determined according to all TCN administration number sections in the corresponding cluster sub-bureau;
and exchanging administration information of the gateway offices of any two cluster sub-offices through the interoffice interface.
2. The B-TrunC cluster networking architecture of claim 1, wherein the group affiliation TCNs perform replication and distribution of control panel signaling between TCNs in the cluster sub-office based on the stored TCN administration information.
3. The B-TrunC cluster networking architecture of claim 2, wherein the gateway corresponding to the group-owned TCN performs control panel signaling addressing, replication, and distribution among the cluster sub-offices according to the cluster sub-office where the group subscriber terminal UE resides.
4. The B-TrunC cluster networking architecture of claim 3, wherein the gateway corresponding to the TCN where the group member resides receives the control panel signaling of the gateway corresponding to the TCN to which the group belongs, and copies and distributes the control panel signaling to the control panel signaling between the TCNs of the corresponding cluster sub-offices.
5. The B-Trunc cluster networking architecture of claim 4, wherein the group home TCN performs user plane data replication and distribution among TCNs in the cluster sub-office according to the stored TCN administration information.
6. The B-TrunC cluster networking architecture of claim 5, wherein the gateway corresponding to the group home TCN performs addressing, replication and distribution of user plane data between cluster sub-offices according to the cluster sub-office where the group subscriber terminal UE resides.
7. The B-TrunC cluster networking architecture of claim 6, wherein the gateway corresponding to the TCN where the group member resides receives the control panel signaling of the gateway corresponding to the TCN to which the group belongs, and copies and distributes the user plane data between TCNs of corresponding cluster sub-offices.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911342845.8A CN113099465B (en) | 2019-12-23 | 2019-12-23 | B-Trunc cluster networking architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911342845.8A CN113099465B (en) | 2019-12-23 | 2019-12-23 | B-Trunc cluster networking architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113099465A CN113099465A (en) | 2021-07-09 |
| CN113099465B true CN113099465B (en) | 2023-02-24 |
Family
ID=76663632
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911342845.8A Active CN113099465B (en) | 2019-12-23 | 2019-12-23 | B-Trunc cluster networking architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113099465B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN201869372U (en) * | 2010-08-17 | 2011-06-15 | 师磊 | Triple-play mobile trunking communication system |
| CN106331997A (en) * | 2015-07-03 | 2017-01-11 | 普天信息技术有限公司 | Method for allowing group member to register toward group main control server in case of grading network formation |
| CN106332282A (en) * | 2015-07-03 | 2017-01-11 | 普天信息技术有限公司 | Method for realizing group call in hierarchical networking |
| CN106332010A (en) * | 2015-07-03 | 2017-01-11 | 普天信息技术有限公司 | Hierarchically-networked broadband trunking communication system and point-to-point calling method thereof |
| CN107645713A (en) * | 2016-07-21 | 2018-01-30 | 中国移动通信集团安徽有限公司 | A kind of method of calling, across cluster cornet server and the network equipment |
| CN108990115A (en) * | 2018-07-16 | 2018-12-11 | 鼎桥通信技术有限公司 | A method of in trunked communication system multi-core network group guaranteed qos off the net |
| CN109673004A (en) * | 2017-10-13 | 2019-04-23 | 成都鼎桥通信技术有限公司 | The method and apparatus of terminal acquisition group service server address |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7577431B2 (en) * | 2003-02-18 | 2009-08-18 | Roamware, Inc. | Providing multiple MSISDN numbers in a mobile device with a single IMSI |
| EP2670106A1 (en) * | 2012-05-28 | 2013-12-04 | AinaCom Oy | Mobile SIP proxy integration |
| CA2988254C (en) * | 2015-06-04 | 2023-07-04 | Tata Communications (America) Inc. | System and method for setting up a call to a roaming party through an over-the-top (ott) call service |
| US10033866B2 (en) * | 2016-02-19 | 2018-07-24 | At&T Intellectual Property I, L.P. | Facilitation of an internet protocol multimedia platform |
-
2019
- 2019-12-23 CN CN201911342845.8A patent/CN113099465B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN201869372U (en) * | 2010-08-17 | 2011-06-15 | 师磊 | Triple-play mobile trunking communication system |
| CN106331997A (en) * | 2015-07-03 | 2017-01-11 | 普天信息技术有限公司 | Method for allowing group member to register toward group main control server in case of grading network formation |
| CN106332282A (en) * | 2015-07-03 | 2017-01-11 | 普天信息技术有限公司 | Method for realizing group call in hierarchical networking |
| CN106332010A (en) * | 2015-07-03 | 2017-01-11 | 普天信息技术有限公司 | Hierarchically-networked broadband trunking communication system and point-to-point calling method thereof |
| CN107645713A (en) * | 2016-07-21 | 2018-01-30 | 中国移动通信集团安徽有限公司 | A kind of method of calling, across cluster cornet server and the network equipment |
| CN109673004A (en) * | 2017-10-13 | 2019-04-23 | 成都鼎桥通信技术有限公司 | The method and apparatus of terminal acquisition group service server address |
| CN108990115A (en) * | 2018-07-16 | 2018-12-11 | 鼎桥通信技术有限公司 | A method of in trunked communication system multi-core network group guaranteed qos off the net |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113099465A (en) | 2021-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210111985A1 (en) | Methods, systems, and computer readable media for distributing network function (nf) topology information among proxy nodes and for using the nf topology information for inter-proxy node message routing | |
| DE69733762T2 (en) | TELEVISION TELEVISION WITH PARTICIPANT NUMBER SHIFTABILITY | |
| DE60309426T2 (en) | Automated assignment of voice-over-IP devices to VLAN | |
| US8638764B2 (en) | Mobile telecommunications architecture | |
| JP2007513528A (en) | Serverless and switchless internet protocol telephone systems and methods | |
| WO1998037707A1 (en) | An arrangement, a system and a method relating to management communication | |
| DE69925171T2 (en) | Routing element for routing a signaling message through a communication network | |
| CN109068285B (en) | Method for realizing cluster pool | |
| CN102684969B (en) | VPN (virtual private network) node, VPN node identification analysis agency and method, VPN server | |
| CN105635335B (en) | Social resources cut-in method, apparatus and system | |
| US5701120A (en) | Partitioned point-to-point communications networks | |
| CN115955456A (en) | IPv 6-based enterprise campus network and networking method | |
| CN113099465B (en) | B-Trunc cluster networking architecture | |
| CN108347722B (en) | User roaming control method for distributed EPC core network and EPC core network | |
| DE102013008932A1 (en) | Method and arrangement for setting up a telecommunication connection | |
| CN104883287B (en) | IPSec vpn system control methods | |
| CN117321963A (en) | Method, system and computer readable medium for platform firewall management through Network Function (NF) repository function (NRF) or Service Communication Proxy (SCP) | |
| CN111131366B (en) | Train network topology construction method and computer readable storage medium | |
| CN113472753A (en) | Multi-tenant network isolation method, data center and communication system | |
| CN108028773A (en) | Method, telecommunication network, mobility management entity pond, program and computer program product for the performance for strengthening the telecommunication network for including at least one pond mobility management entity group | |
| JPS63211842A (en) | Path control system | |
| CN104125357B (en) | Cross-domain exchange network-building method and system | |
| CN108769283A (en) | A method of realizing that DHCP is adaptive | |
| CN109302502A (en) | Distribution method, system and the storage medium of base station transport layer IP and terminal local IP | |
| CN100444576C (en) | Group broadcast realization in IP telecommunication network system |
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 |