A method and apparatus for hierarchical management topology of a HUB based on the NETCONF protocol

Abstract

This invention discloses a method and apparatus for hierarchical management of HUB topology based on the NETCONF protocol. The method includes: a multi-port repeater (HUB) obtains and presets the level of the HUB by parsing control words; after the HUB is connected and synchronized with a remote radio unit (RRU), the HUB matches the port ID synchronized with the RRU with the received MAC address of the RRU and fills it into a YANG model; after multiple HUBs are cascaded and synchronized, the upper-level HUB matches the port ID synchronized with the lower-level HUB with the received MAC address of the lower-level HUB and fills it into a YANG model; the HUB hierarchically reports the YANG model of the HUB management topology relationship for the base station to obtain the topology relationship; this invention reduces the operational load of obtaining the topology and improves the real-time perception and maintenance efficiency of the topology relationship.

Description

Technical Field

[0001] This invention belongs to the field of mobile communication technology, and in particular relates to a method and apparatus for hierarchical management topology of a HUB based on the NETCONF protocol. Background Technology

[0002] A multi-port repeater (HUB) is a fundamental device in a data communication system. It is connected to the baseband processing unit (BBU) via optical fiber and to the radio remote unit (RRU) via network cable or fiber optic composite cable. It serves two purposes: first, it can be used to expand the number of RRUs connected to the BBU and provide power to the RRUs; second, it provides a relay function for data exchange between the BBU and the RRUs.

[0003] With the rapid development of communication technology, society's demand for communication networks is constantly growing. While meeting network performance requirements, high demands are placed on network coverage. This has led to the evolution of base station organizational structures from a configuration where BBUs are connected to a single RRU or a small number of RRUs to a configuration where BBUs are connected to a large number of RRUs through multiple HUBs. This has greatly improved the network coverage area. However, the increase in the number of devices inevitably increases the operational difficulty of device monitoring, management, and maintenance. Therefore, the intervention of topology ensures the expansion of the base station organizational structure on the one hand, and simplifies the centralized monitoring, management, and maintenance of multiple devices within the base station organization on the other hand.

[0004] Currently, topology management operations are mostly performed by the BBU, completely solving the time-consuming and labor-intensive problem of manually adding topology relationships. In non-cascaded scenarios, centralized management of HUB and RRU topologies by the BBU is feasible and effective. However, in cascaded scenarios, centralized management of multiple HUB and RRU topologies by the BBU may lead to problems such as increased operational load, decreased sensing performance, and delayed real-time topology status maintenance. Summary of the Invention

[0005] In response to the problems described in the background art, the present invention provides a method and apparatus for hierarchical management of HUB topology based on the NETCONF protocol, which changes the centralized management of topology to hierarchical management, effectively distributing the operational load and improving the efficiency of real-time perception and maintenance of topology relationships.

[0006] To achieve the above objectives, the present invention provides a method and apparatus for hierarchical management topology of a HUB based on the NETCONF protocol, the method comprising:

[0007] The multi-port repeater HUB obtains and presets the number of levels of the HUB by parsing the control words;

[0008] After the HUB connects and synchronizes with the RRU, the HUB will match the port ID synchronized with the RRU with the received MAC address of the RRU and fill it into the YANG model.

[0009] After multiple hubs are cascaded and synchronized, each hub will fill in its own MAC address in the format string. The upper-level hub will match the port ID synchronized with the lower-level hub with the received MAC address of the lower-level hub and fill it into the YANG model;

[0010] The HUB hierarchical reporting system uses the YANG model to represent the HUB management topology, which is then used by the base station to obtain the topology relationships.

[0011] The multi-port repeater (HUB) obtains and presets the number of levels of the HUB by parsing control words, including:

[0012] The connection between the HUB and BBU can use the Common Public Radio Interface (CPRI) or the Enhanced Common Public Radio Interface (eCPRI). All cascaded HUBs use the Common Public Radio Interface (CPRI) for synchronization based on CPRI or eCPRI. Each HUB can obtain its own level ID by parsing the CPRI or eCPRI control word message corresponding to its level ID. Initially, the content of the CPRI or eCPRI control word message corresponding to the level ID is set to zero by default. That is, all HUBs in the network, from power-on until CPRI or eCPRI synchronization, default to having a level ID of zero, indicating and pre-setting themselves as a level-one HUB. When CPRI or eCPRI synchronization occurs, each HUB will again parse the control word message containing the level ID. Since the BBU does not send the level ID to the HUB, the HUB directly connected to the BBU will still set itself as the actual level-one HUB when the level ID is zero, and will increment the level ID by one and assemble a new message with the CPRI control word before transmitting it to the next-level HUB. The next-level HUB will then perform the same operation after obtaining the level ID.

[0013] For both non-cascaded and cascaded HUBs, ensuring CPRI or eCPRI synchronization is based on two aspects: firstly, ensuring that the physical lines of connected devices, including power lines and fiber optic cables between devices, are normal and intact; and secondly, ensuring that the information exchange standards of the communication links of connected devices are consistent.

[0014] Wherein, after the HUB is connected and synchronized with the Radio Remote Unit (RRU), the HUB will match the port ID synchronized with the RRU with the received RRU MAC address and fill it into the YANG model, including:

[0015] The HUB is designed with 10 CPRI ports, with the first 8 consecutive CPRI ports used for RRU connection. Both the HUB and RRU communicate via the Common Public Radio Interface (CPRI) based on CPRI synchronization. The HUB can obtain the port ID corresponding to the CPRI synchronization and calculate the CPRI control word for that port using the synchronized port ID and offset to obtain the MAC address of the RRU corresponding to that port ID. The HUB then matches the port ID and the RRU's MAC address and fills them into the YANG model for topology management at this level.

[0016] The basis for ensuring CPRI synchronization by the HUB and the RRU connected to the HUB is consistent with the aforementioned basis for ensuring CPRI synchronization by the HUB.

[0017] After the multiple HUBs are cascaded and synchronized, the upper-level HUB will match the port ID synchronized with the lower-level HUB with the received MAC address of the lower-level HUB and fill it into the YANG model, including:

[0018] The hub is designed with 10 CPRI ports and 2 eCPRI ports. The two eCPRI ports are used for connecting the hub to the BBU, while the latter two CPRI ports are used for connecting the hub to the BBU or higher / lower-level hubs. The basis for ensuring CPRI or eCPRI synchronization among cascaded devices is the same as the basis for ensuring CPRI synchronization with the hub.

[0019] In a cascaded configuration, a HUB receives information from or sends information to an upstream device via its uplink port, and receives information from or sends information to a downstream device via its downlink port. The downlink port of the upstream HUB connects to the uplink port of the downstream HUB. Based on CPRI synchronization, the upstream HUB can obtain the port ID corresponding to CPRI synchronization, and can also calculate the CPRI control word of the port based on the offset using the synchronized port ID to obtain the MAC address of the downstream HUB corresponding to the port ID. The port ID and the MAC address of the RRU are matched by the HUB and filled into the YANG model used by the upstream HUB for managing the topology relationship at this level.

[0020] The HUB will match the port ID of the connection between the HUB and the RRU and the MAC address of the RRU and fill them into the YANG model for topology management of the HUB. This behavior is applicable to HUBs of any number of levels in non-cascaded or cascaded cases.

[0021] The HUB hierarchically reports the YANG model of the HUB-managed topology relationship for the base station to obtain the topology relationship, including:

[0022] Based on the premise that all devices within the network have normal and synchronized CPRI or eCPRI port connections, the HUB converts the YANG format topology management model into XML format via the Network Configuration Protocol (NETCONF) and reports it to the BBU. The BBU can then directly obtain the topology relationship or display the topology relationship on the webpage based on the HUB's level and MAC address, the port ID of the HUB for RRU connection and the corresponding RRU's MAC address, and the port ID of the HUB for lower-level HUB connection and the corresponding lower-level HUB's MAC address.

[0023] This invention also discloses an apparatus applicable to the above-mentioned HUB hierarchical management topology method based on the NETCONF protocol, the apparatus comprising: a HUB and an RRU based on the NETCONF network configuration protocol.

[0024] The NETCONF network configuration protocol upon which the HUB or RRU is based primarily leases a communication IP from the BBU via the Dynamic Host Configuration Protocol (DHCP) and configures this IP as the network interface card (NIC) IP for external communication of the HUB or RRU. Simultaneously, it obtains the BBU's communication IP and sets it as the destination IP for implementing the call home mechanism. After both the Server IP and Client IP are configured, the HUB or RRU can establish a session to exchange information with the BBU. Once the HUB or RRU can communicate with the BBU, the HUB will assume the responsibility of managing and reporting the device network. The HUB will match the port ID that has achieved CPRI synchronization with the MAC address of the device connected to that port and report it using the network fronthaul YANG model. If a device on the synchronized port experiences a synchronization failure, the HUB will update the information of the abnormal port in the network fronthaul YANG model and report it again.

[0025] The HUB is designed with 10 CPRI ports and 2 eCPRI ports. The first 8 CPRI ports are for RRU connections, the last 2 CPRI ports are for HUB or BBU connections, and the 2 eCPRI ports are for BBU connections. The built-in message interaction and processing module allows the HUB to obtain the HUB's level ID, port ID, and the MAC address of the HUB or RRU matching the port ID through two methods: first, by using a control word; and second, by using the NETCONF configuration protocol to report the YANG model of the HUB for topology management, which already contains the above ID and MAC information.

[0026] The RRU has a built-in message interaction and processing module, which is used by the RRU to send its MAC address to the HUB connected to the RRU via the CPRI control word.

[0027] Compared with the prior art, the present invention has the following beneficial effects:

[0028] In cascading scenarios involving multiple hubs and RRUs, hierarchical topology management via hubs not only distributes the operational load of centralized topology management by hubs, but also effectively improves the efficiency of real-time topology status awareness and maintenance by leveraging NETCONF's real-time update capabilities for the YANG model, thereby enhancing topology management performance. Attached Figure Description

[0029] Figure 1 This is a schematic diagram of the network topology according to an embodiment of the present invention.

[0030] Figure 2 This is a schematic diagram of the hierarchical management topology device according to an embodiment of the present invention.

[0031] Figure 3 This is a schematic diagram of the hierarchical management topology method described in an embodiment of the present invention. Detailed Implementation

[0032] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0033] The main equipment shown in the example includes a baseband processing unit (BBU), a multi-port repeater (HUB), and a remote radio unit (RRU), and all devices within the network are connected via a common radio interface (CPRI). Figure 1 As shown, Figure 1 The diagram illustrates a network topology used in a hierarchical management system for hubs (HUBs). The topology includes both chain and star topologies: the baseband processing unit (BBU) and multi-port repeaters (HUB_1 through HUB_N) use a chain topology, while each HUB (HUB_1 through HUB_N) and each RRU (RRU_1_1 through RRU_1_8) use a star topology. In this topology, the common public radio interface (CPRI) is used between BBUs and HUBs, between HUBs, and between HUBs and RRUs. Based on CPRI synchronization, a HUB can obtain its own tier ID, the MAC address of the cascaded HUB, and the MAC address of the downstream RRU through CPRI control words.

[0034] The specific device structure and wiring method applied to the HUB hierarchical management topology are as follows: Figure 2As shown. The device structure includes: the BBU is designed with an unlimited number of CPRI and eCPRI ports for connection to the HUB; the HUB is designed with 10 CPRI ports and 2 eCPRI ports, with 8 ports (CPRI_1 to CPRI_8) for connection to the RRU, 2 ports (CPRI_9 to CPRI_10) for connection to the HUB or BBU, and 2 ports (eCPRI_11 to eCPRI_12) for connection to the BBU; the RRU is designed with 1 CPRI port for connection to the HUB or BBU. Based on Figure 2 The implementation plan assumes that all devices in the network use the Common Wireless Interface (CPRI) for connection. It is agreed that CPRI_9 on the HUB is the uplink port, i.e. the port for connecting to the upper-level device, and CPRI_1 to CPRI_8 and CPRI_10 are the downlink ports, i.e. the ports for connecting to the lower-level devices.

[0035] A schematic diagram of the specific method and process applied to the hierarchical management topology of a HUB is shown below. Figure 3 As shown, Figure 3 This only demonstrates the specific method and process of HUB hierarchical management topology based on a two-level cascaded environment, but this method is not limited to two-level cascaded.

[0036] First, after ensuring that the power supply, fiber optic cables and other lines between the BBU, HUB and RRU in the network are properly connected, all devices are powered on and initialized. During this process, HUB_1 and HUB_2 will parse the initial content of the CPRI control word to obtain the default level ID and preset themselves as level 1 HUB.

[0037] Secondly, after BBU and HUB_1 achieve CPRI synchronization, since BBU does not send CPRI control word messages containing the level ID to HUB_1, HUB_1 obtains the real level ID when it parses the CPRI control word content again, thus truly setting HUB_1 as a level 1 HUB.

[0038] Next, after HUB_1 and HUB_2 achieve CPRI synchronization, HUB_1 will add 1 to its own level ID to form a new level ID, assemble it with the CPRI control word, and transmit it to HUB_2. At that time, when HUB_2 receives and parses the new level ID, it will update the default level ID and finally set HUB_2 as a level 2 HUB.

[0039] Once the level IDs of HUB_1 and HUB_2 are updated, NETCONF will synchronously update the YANG models used by HUB_1 and HUB_2 to manage their respective level topologies. HUB_1 will exchange its MAC address with HUB_2 via CPRI control word messages. Based on the MAC address received by HUB_1 from HUB_2, the CPRI_10 port ID of HUB_1 will be bound to the MAC address of HUB_2 and populated into the YANG model of HUB_1.

[0040] Then, after HUB_1 achieves CPRI synchronization with RRU_1_1 and HUB_2 with RRU_2_1, HUB_1 will parse the MAC address reported by RRU_1_1 through the CPRI control word message, bind the CPRI_1 port ID with the MAC address of RRU_1_1, and fill it into the YANG model of HUB_1. Similarly, HUB_2 will parse the MAC address reported by RRU_2_1 through the CPRI control word message, bind the CPRI_1 port ID with the MAC address of RRU_2_1, and fill it into the YANG model of HUB_2.

[0041] Finally, HUB_1 and HUB_2 report topology relationships via NETCONF based on the update status of their respective YANG models managing their respective topologies. The basis for topology reporting is that the YANG model update mechanism is triggered when a new device joins the topology, and a new YANG model report is also triggered once the YANG model is updated.

[0042] After the above operations, all levels of topology will be aggregated at the BBU. The BBU only needs to parse the YANG model of each HUB regarding its own topology level and replace identical HUB nodes with those of lower-level topologies to obtain the complete topology relationship. This hierarchical management method of topology effectively distributes the operational load and improves the efficiency of real-time topology status awareness and maintenance.

[0043] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for hierarchical management topology of a HUB based on the NETCONF protocol, characterized in that, All topology relationships, whether non-cascaded or cascaded, are managed hierarchically by the HUB, including: The HUB obtains and presets the level of the HUB by parsing the control word; After the HUB connects and synchronizes with the RRU, the HUB will match the port ID synchronized with the RRU with the received MAC address of the RRU and fill it into the YANG model. After multiple HUBs are cascaded and synchronized, the upper-level HUB will match the port ID synchronized with the lower-level HUB with the received MAC address of the lower-level HUB and fill it into the YANG model. The HUB hierarchical reporting of the YANG model of the HUB management topology relationship is used by the base station to obtain the topology relationship; The method for obtaining its own level ID is as follows: the level ID corresponding to the CPRI or eCPRI control word is set to zero by default, meaning that any HUB is initialized as a level 1 HUB by default. In the case of cascading, after any HUB synchronizes with the upper-level device, it parses the obtained control word message containing the level ID again to extract the level ID and set its own actual level. That is, after a HUB directly connected to the BBU achieves synchronization with the BBU's CPRI or eCPRI, it will parse the CPRI or eCPRI control word message again to obtain its own actual level and set itself as a level 1 HUB. It will also increment its own level ID by one and assemble it together with the CPRI control word to form a message containing the new level ID and transmit it to the lower-level HUB. After receiving and parsing the CPRI control word message transmitted by the upper-level HUB, the lower-level HUB sets its own level to level 2 according to the level ID and encapsulates the new ID message to transmit it to the lower level. The level ID acquisition and transmission behavior of the level 3 HUB is the same as that of the level 2 HUB, and so on for the lower-level HUB.

2. The method for hierarchical management topology of a HUB based on the NETCONF protocol according to claim 1, characterized in that: The HUB includes non-cascaded HUBs and cascaded HUBs at various levels, connected via CPRI or eCPRI interfaces, and synchronized based on CPRI or eCPRI. In non-cascaded configurations, HUBs and first-level HUBs in cascaded configurations obtain their own level IDs by parsing the CPRI or eCPRI control word messages received on the uplink port. In cascaded configurations, each lower-level HUB obtains its own level ID by parsing the CPRI control word messages received on the uplink port.

3. The method for hierarchical management topology of a HUB based on the NETCONF protocol according to claim 1, characterized in that: The HUB and the RRUs connected to the HUB are connected via CPRI ports and synchronized based on CPRI. The HUB includes 10 CPRI ports, of which the first 8 consecutive CPRI ports are used for RRU connection. When the HUB and one or more RRUs connected to the HUB achieve CPRI synchronization based on a specific CPRI port, the HUB can obtain the port ID of the CPRI synchronization and obtain the MAC address of the RRU corresponding to the port ID through the address transmission control word. The port ID and the MAC address of the RRU will be matched by the HUB and filled into the YANG model for the HUB to implement the topology management of this level.

4. The method for hierarchical management topology of a HUB based on the NETCONF protocol according to claim 2, characterized in that, After the multiple HUBs are cascaded and synchronized, the upper-level HUB will match the port ID synchronized with the lower-level HUB with the received MAC address of the lower-level HUB and fill it into the YANG model, including: In a cascaded configuration, all HUBs are connected via CPRI ports and synchronized based on CPRI. In a cascaded configuration, the parent HUB will match the port ID synchronized with the child HUB with the received MAC address of the child HUB and fill it into the YANG model.

5. The method for hierarchical management topology of a HUB based on the NETCONF protocol according to claim 4, characterized in that: The HUB includes 10 CPRI ports and 2 eCPRI ports, of which the 2 eCPRI ports are used for the HUB to connect to the BBU, and the latter 2 of the 10 CPRI ports are used for the HUB to connect to the BBU or upper / lower level HUBs.

6. The method for hierarchical management topology of a HUB based on the NETCONF protocol according to claim 4, characterized in that, In the cascading scenario, the upper-level hub will match the port ID synchronized with the lower-level hub with the received MAC address of the lower-level hub and fill it into the YANG model, including: In a cascaded configuration, a HUB receives information from an upstream device or sends its own information to an upstream device via an uplink port, and receives information from a downstream device or sends its own information to a downstream device via a downlink port. The downlink port of the upstream HUB is connected to the uplink port of the downstream HUB. CPRI synchronization is achieved based on the directly connected upstream and downstream HUBs. The upstream HUB matches the port ID synchronized with the downstream HUB with the received MAC address of the downstream HUB and fills it into the YANG model used by the upstream HUB to manage the topology relationship of this level.

7. The method for hierarchical management topology of a HUB based on the NETCONF protocol according to claim 6, characterized in that, The HUB hierarchical reporting of the YANG model of the HUB-managed topology relationship is used by the base station to obtain the topology relationship, including: Based on the premise that all devices within the network have normal and synchronized CPRI or eCPRI port connections, the HUB converts the YANG format topology management model into XML format using the NETCONF network configuration protocol and then reports it to the BBU. The BBU can then directly obtain the topology relationship or display the topology relationship on the webpage based on the HUB's level and MAC address, the port ID of the HUB for RRU connection and the corresponding RRU's MAC address, and the port ID of the HUB for lower-level HUB connection and the corresponding lower-level HUB's MAC address.

8. An apparatus for hierarchical management of a HUB topology based on the NETCONF protocol, applicable to the hierarchical management of a HUB topology based on the NETCONF protocol as described in any one of claims 1-7, capable of hierarchical management of the topology, characterized in that, Including HUBs and RRUs based on the NETCONF network configuration protocol: The NETCONF network configuration protocol upon which the HUB or RRU is based primarily leases a communication IP from the BBU via the Dynamic Host Configuration Protocol (DHCP) and configures this IP as the network interface card (NIC) IP for external communication of the HUB or RRU. Simultaneously, it obtains the BBU's communication IP and sets it as the destination IP for implementing the call home mechanism. After both the Server IP and Client IP are configured, the HUB or RRU can establish a session to exchange information with the BBU. Once the HUB or RRU can communicate with the BBU, the HUB will assume the responsibility of managing and reporting the device network. The HUB will match the port ID that has achieved CPRI synchronization with the MAC address of the device connected to that port and report it using the network fronthaul YANG model. If a device on the synchronized port experiences a synchronization failure, the HUB will update the information of the abnormal port in the network fronthaul YANG model and report it again.

9. The device for a hierarchical management topology of a HUB based on the NETCONF protocol according to claim 8, characterized in that: The HUB is designed with 10 CPRI ports and 2 eCPRI ports. The first 8 CPRI ports are for RRU connections, the last 2 CPRI ports are for BBU or HUB connections, and the 2 eCPRI ports are for BBU connections. The built-in message interaction and processing module allows the HUB to: 1) obtain the HUB's level ID, synchronized port ID, and the MAC address of the HUB or RRU matching the port ID based on the CPRI ports; and 2) report the YANG model used by the HUB for topology management at this level and which already contains the above ID and MAC information through the NETCONF network configuration protocol. The RRU has a built-in message interaction and processing module, which is used for the RRU to send its MAC address to the HUB connected to the RRU via the CPRI control word.

Images