CN111447077B

CN111447077B - Network element configuration method, device and storage medium

Info

Publication number: CN111447077B
Application number: CN201910044392.4A
Authority: CN
Inventors: 李响; 孙军帅
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2019-01-17
Filing date: 2019-01-17
Publication date: 2023-05-09
Anticipated expiration: 2039-01-17
Also published as: CN111447077A

Abstract

The invention discloses a network element configuration method, a device and a storage medium, which are used for realizing CU/DU management across factories aiming at an application scene of 5G CU/DU separation deployment and improving CU/DU management efficiency and accuracy. The network element configuration method implemented by the network management system side comprises the following steps: receiving a network element registration request, wherein the network element registration request carries a network element identifier of a network element to be registered; aiming at the network element registration request, distributing network management identification for the network element to be registered; and sending the network management identification distributed for the network element to be registered to a requester.

Description

Network element configuration method, device and storage medium

Technical Field

The present invention relates to the field of wireless communications technologies, and in particular, to a network element configuration method, a device, and a storage medium.

Background

According to 3GPP (3 rd Generation Partnership Project, third generation partnership project), the BBU (Building Baseband Unit, baseband processing Unit) function of 5G (fifth generation mobile communication) NR (New Radio) is reconfigured into two functional entities, CU (Centralized Unit) and DU (Distributed Unit), to meet different wireless service requirements. CU and DU function cut-off to distinguish in order to handle the real-time of the content, CU apparatus mainly includes the wireless high-level protocol stack function of non-real time, support some core network function subsidence and MEC (multiple access edge computing) edge application business deployment at the same time, and DU apparatus mainly processes the layer 2 function of physical layer function and real-time demand. Considering saving transmission resources between RRU (Remote Radio Unit, remote radio module) and DU, part of the physical layer functions may also be moved down to RRU implementation.

In terms of management of 5G NR, the existing 3GPP standard defines three deployment modes of CU and DU separation, CU-CP (Control Plane)/CU-UP (User Plane) and DU separation, and CU and DU integration. However, 3GPP currently defines only the gNB (5G base station) resource model (Network Resource Model, NRM), and has not defined the management model of the network management system (Network Management System, NMS) and the device management system (Element Management System, EMS). In practical application, the same EMS can be adopted to manage both CUs and DUs, but the method is not suitable for CU/DU management across factories, because each manufacturer has own private management model, the management model is not exposed to other manufacturers, and the efficiency and accuracy of CU/DU management across factories cannot be ensured. As shown in fig. 1, when an operator needs to control the DU-1 and DU-2 of vendor 1 by the CU of vendor 2, EMS2 cannot recognize DU-1 and DU-2 without a DU management Identification (ID), and if an existing gNB DU ID is used, there is a problem as follows: modifying the gNBDUID of DU-1 of gNB1 to gNBDUID of gNB2 by EMS1, but after modification, configuration will not be effective because the gNB DUID does not belong to gNB 1; the EMS2 cannot identify the DU device of gNB1, so that the gNB DU ID of the DU-1 of gNB1 cannot be modified; because CU and DU deployment positions are different, time delay constraint is provided, and the interface between CU and DU is a control signaling channel, and the network management channel function is not provided, multiplexing the control channel to transmit network management instructions will have an influence on bandwidth and control signaling time delay.

Disclosure of Invention

The embodiment of the invention provides a network element configuration method, a device and a storage medium, which are used for realizing CU/DU management across factories aiming at an application scene of 5GCU/DU separation deployment and improving CU/DU management efficiency and accuracy.

In a first aspect, a network element configuration method implemented by a network management system side is provided, including:

receiving a network element registration request, wherein the network element registration request carries a network element identifier of a network element to be registered;

aiming at the network element registration request, distributing network management identification for the network element to be registered;

and sending the network management identification distributed for the network element to be registered to a requester.

Optionally, the network element to be registered includes a distributed unit DU or a centralized unit CU to be registered; and

receiving a network element registration request, including:

and receiving a network element registration request sent by the CU or the DU through an Equipment Management System (EMS) to which the CU or the DU belongs.

Optionally, sending a network management identifier allocated to the network element to be registered to a requester, which specifically includes:

and sending the network management identification allocated to the CU or the DU to the EMS, wherein the network management identification allocated to the CU or the DU is configured by the EMS.

Optionally, the network element identifier includes an operation administration maintenance OAM internet protocol IP address of the registered network element.

In a second aspect, a network element configuration method implemented at a network element side is provided, including:

sending a network element registration request to a Network Management System (NMS), wherein the network element registration request carries a network element identifier of a network element to be registered;

and receiving and storing a network management identifier allocated by the NMS for the network element registration request.

the method for sending the network element registration request to the network management system NMS specifically comprises the following steps:

and sending the network element registration request to a Network Management System (NMS) through an attributive Equipment Management System (EMS).

Optionally, the network management identifier is configured by the EMS according to the network management identifier sent by the NMS.

In a third aspect, a network element configuration apparatus is provided, including:

a receiving unit, configured to receive a network element registration request, where the network element registration request carries a network element identifier of a network element to be registered;

an allocation unit, configured to allocate a network management identifier to the network element to be registered with respect to the network element registration request;

and the sending unit is used for sending the network management identifier distributed for the network element to be registered to the requester.

the receiving unit is specifically configured to receive a network element registration request sent by the CU or the DU through an EMS to which the CU or the DU belongs.

Optionally, the sending unit is specifically configured to send, to the EMS, a network management identifier allocated to the CU or the DU, where the network management identifier allocated to the CU or the DU is configured by the EMS.

In a fourth aspect, a network element configuration device implemented at a network management system side is provided, including:

a sending unit, configured to send a network element registration request to a network management system NMS, where the network element registration request carries a network element identifier of a network element to be registered;

a receiving unit, configured to receive a network management identifier allocated by the NMS for the network element registration request;

and the storage unit is used for storing the network management identification.

the sending unit is specifically configured to send the network element registration request to a network management system NMS through an attributed device management system EMS.

In a fifth aspect, a computing device is provided, comprising at least one processor, and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of any of the network element configuration methods described above.

In a sixth aspect, there is provided a computer readable medium storing a computer program executable by a computing device, the program when run on the computing device causing the computing device to perform the steps of any one of the network element configuration methods described above.

In the network element configuration method, the device and the storage medium provided by the embodiment of the invention, the network element to be registered sends the registration request to the network management system, the network management system distributes the network management identification for the network element to be registered, and the network element to be registered is managed through the network management identification, so that the network element management across manufacturers can be realized, and the network element management efficiency and accuracy are improved.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:

FIG. 1 is a diagram of a prior art network management architecture;

fig. 2 is a schematic flow chart of an implementation of a network element configuration method implemented by a network management system side in an embodiment of the present invention;

FIG. 3 is a flowchart of an NMS allocating network management identifiers to CUs or DUs according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of CU and DU management models according to an embodiment of the present invention;

fig. 5 is a schematic flow chart of an implementation of a network element configuration method implemented at a network element side in an embodiment of the present invention;

fig. 6 is a schematic structural diagram of a first network element configuration device according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of a second network element configuration device according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of a computing device according to an embodiment of the invention.

Detailed Description

In order to realize CU/DU management across manufacturers aiming at an application scene of 5G CU/DU separation deployment, the embodiment of the invention provides a network element configuration method, a device and a storage medium, and the efficiency and accuracy of CU/DU management are improved.

Reference herein to "a plurality of" or "a number" means two or more than two. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

The embodiment of the invention provides a 5G CU and DU distributed NMS/EMS management method, enhances gNG CU NRM and gNG DU NRM parameters, defines a distribution method of network management identifiers, enables EMS to independently manage CU and DU, and better supports management of manufacturer CU and DU.

The preferred embodiments of the present invention will be described below with reference to the accompanying drawings of the specification, it being understood that the preferred embodiments described herein are for illustration and explanation only, and not for limitation of the present invention, and embodiments of the present invention and features of the embodiments may be combined with each other without conflict.

As shown in fig. 2, a flow chart of an implementation of a network element configuration method implemented by a network management system side according to an embodiment of the present invention includes the following steps:

s21, receiving a network element registration request.

In the implementation, a network element registration request is sent to a Network Management System (NMS) through a network element to be registered, a network management identifier is distributed to the network element by the NMS, the network management identifier is unique in the network management system, and the NMS manages the network element through the network management identifier. And carrying the network element identification of the network element to be registered in the received network element registration request. In practice, the network element identification may be, but is not limited to, an OAM (operation administration maintenance) IP (internet protocol) address for the network element to be registered.

S22, distributing network management identification for the network element to be registered according to the received network element registration request.

After receiving the network element registration request, the NMS distributes network management identification for the network element to be registered.

S23, sending the network management identification distributed for the network element to be registered to the requester.

In a specific implementation, the network element to be registered may be a CU and a DU in the 5G network communication system, based on which, in step S21, the NMS receives a network element registration request sent by the CU or the DU through the EMS to which the NMS belongs. In step S23, the NMS sends the network management identifier allocated for the CU or the DU to the EMS, the network management identifier allocated for the CU or the DU by the EMS is configured for the CU or the DU, and the CU or the DU stores the network management identifier configured for the EMS by the EMS, as shown in fig. 3, which is a schematic flow chart of the NMS allocating the network management identifier for the CU or the DU. As shown in fig. 4, a schematic diagram of a CU and DU management model provided by an embodiment of the present invention is shown, where in the CU or DU management model provided by the embodiment of the present invention, the gNB CU (including CU-CP and CU-UP) and the gNB DU have independent network management identities for managing systems, and respectively expose OAM IP, and the gNB CU and the gNB DU are respectively managed by independent device management systems (EMS), so that the NMS can perform FCAPS (Fault Configuration Accounting Performance and Security, error, configuration, accounting, performance and security) management on the CU and the DU in a finer granularity.

In order to further enhance management on CUs and DUs, in the embodiment of the present invention, an OAM IP address and a network management identifier of a network element are added to NRM (network resource model) of CUs and DUs. And carrying the OAM IP address as a network element identifier in a message interacted between the network element and the NMS and EMS.

As shown in table 1, the parameters of the gNB DU Function (base station distributed unit Function) provided by the embodiment of the present invention are shown in the table:

TABLE 1

Parameter name	Whether or not it is necessary
		gNB DU ID	Must be
gNB DU Name	Optionally, a
		gNB ID	Must be
DU OAM ID	Must choose
		OAM IP Address	Must choose

Wherein, gNB DU ID represents DU identification, gNB DU Name represents DU Name, gNB ID represents base station identification, DU OAM ID represents network management identification allocated for DU, OAM IP Address represents operation management maintenance IP Address corresponding to DU.

As shown in table 2, the parameters are shown in gNB CU CP Function (base station centralized unit control plane function) provided in the embodiment of the present invention:

TABLE 2

Parameter name	Whether or not it is necessary
		gNB ID	Must be
gNB CU Name	Optionally, a
		PLMN IDList	Must be
CU CP OAM ID	Must choose
		OAM IP Address	Must choose

Wherein, gNB ID represents a base station identifier, gNB CUName represents a CU Name, PLMN IDList represents a public land mobile network identifier list, CUCP OAM ID represents a network management identifier distributed to CUCP, OAM IP Address represents an operation management maintenance IP Address of the CUCP.

As shown in table 3, the parameters are shown in gNB CU UP Function (base station centralized unit user plane function) provided in the embodiment of the present invention:

TABLE 3 Table 3

Parameter name	Whether or not it is necessary
		PLMN ID List	Must be
gNB ID	Must be
		CU UP OAM ID	Must be
OAM ID Address	Must choose

Wherein, PLMN ID List represents public land mobile network identifier List, gNB ID represents base station identifier, CU UP OAM ID represents network management identifier allocated for CU UP, OAM IP Address represents operation management maintenance IP Address of CU UP.

In the network element configuration method provided by the embodiment of the invention, through defining the management models of the NMS, EMS, gNB CU and gNB DU, FCAPS management of gNB CU and DU of a cross manufacturer can be realized, and management efficiency and accuracy of CU and DU of different manufacturers are improved.

Based on the same inventive concept, the embodiment of the invention also provides a network element configuration method implemented by a network element side and a corresponding network element configuration device, and because the principle of the device and the method for solving the problem is similar to that of the network element configuration method implemented by the network management system side, the implementation of the device and the method can refer to the implementation of the network element configuration method implemented by the management system side, and the repetition is omitted.

As shown in fig. 5, which is a schematic diagram of an implementation flow of a network element configuration method implemented on the far side of the network, the method includes the following steps:

s51, sending a network element registration request to the NMS.

Wherein, the network element registration request carries the network element identification of the network element to be registered.

S52, receiving the network management identification allocated by the NMS for the network element registration request and storing the network management identification.

Fig. 6 is a schematic structural diagram of a first network element configuration device according to an embodiment of the present invention, including:

a receiving unit 61, configured to receive a network element registration request, where the network element registration request carries a network element identifier of a network element to be registered;

an allocation unit 62, configured to allocate a network management identifier to the network element to be registered for the network element registration request;

a sending unit 63, configured to send, to a requester, a network management identifier allocated to the network element to be registered.

Fig. 7 is a schematic structural diagram of a second network element configuration device according to an embodiment of the present invention, where the second network element configuration device includes:

a sending unit 71, configured to send a network element registration request to a network management system NMS, where the network element registration request carries a network element identifier of a network element to be registered;

a receiving unit 72, configured to receive a network management identifier allocated by the NMS for the network element registration request;

a storage unit 73, configured to store the network management identifier.

For convenience of description, the above parts are described as being functionally divided into modules (or units) respectively. Of course, the functions of each module (or unit) may be implemented in the same piece or pieces of software or hardware when implementing the present invention.

Having described the network element configuration method and apparatus of an exemplary embodiment of the present invention, next, a computing apparatus according to another exemplary embodiment of the present invention is described.

Those skilled in the art will appreciate that the various aspects of the invention may be implemented as a system, method, or program product. Accordingly, aspects of the invention may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.

In some possible implementations, a computing device according to the invention may include at least one processor, and at least one memory. Wherein the memory stores program code which, when executed by the processor, causes the processor to perform the steps in the network element configuration method according to various exemplary embodiments of the invention described in the present specification. For example, the processor may perform step S21 shown in fig. 2, receive a network element registration request, and step S22, allocate a network management identifier to the network element to be registered for the received network element registration request; step S23, sending a network management identifier distributed for the network element to be registered to a requester; or performs step S51 as shown in fig. 5, sending a network element registration request to the NMS; and step S52, receiving the network management identification allocated by NMS for the network element registration request and storing.

A computing device 80 according to such an embodiment of the invention is described below with reference to fig. 8. The computing device 80 shown in fig. 8 is merely an example and should not be taken as limiting the functionality and scope of use of embodiments of the present invention.

As shown in fig. 8, the computing device 80 is in the form of a general purpose computing device. Components of computing device 80 may include, but are not limited to: the at least one processor 81, the at least one memory 82, a bus 83 connecting the various system components, including the memory 82 and the processor 81.

Bus 83 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, and a local bus using any of a variety of bus architectures.

The memory 82 may include readable media in the form of volatile memory, such as Random Access Memory (RAM) 821 and/or cache memory 822, and may further include Read Only Memory (ROM) 823.

Memory 82 may also include a program/utility 825 having a set (at least one) of program modules 824, such program modules 824 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

The computing device 80 may also communicate with one or more external devices 84 (e.g., keyboard, pointing device, etc.), one or more devices that enable a user to interact with the computing device 80, and/or any devices (e.g., routers, modems, etc.) that enable the computing device 80 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 85. Moreover, computing device 80 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through a network adapter 86. As shown, network adapter 86 communicates with other modules for computing device 80 over bus 83. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with computing device 80, including, but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

In some possible embodiments, aspects of the network element configuration method provided by the present invention may also be implemented in the form of a program product, which includes program code for causing a computer device to perform the steps in the network element configuration method according to the various exemplary embodiments of the present invention described above when the program product is run on the computer device, for example, the computer device may perform step S21 as shown in fig. 2, receive a network element registration request, and step S22, allocate a network management identifier for a network element to be registered for the received network element registration request; step S23, sending a network management identifier distributed for the network element to be registered to a requester; or performs step S51 as shown in fig. 5, sending a network element registration request to the NMS; and step S52, receiving the network management identification allocated by NMS for the network element registration request and storing.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The program product for network element configuration of embodiments of the present invention may employ a portable compact disc read only memory (CD-ROM) and include program code and may run on a computing device. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functions of two or more of the elements described above may be embodied in one element in accordance with embodiments of the present invention. Conversely, the features and functions of one unit described above may be further divided into a plurality of units to be embodied.

Furthermore, although the operations of the methods of the present invention are depicted in the drawings in a particular order, this is not required to either imply that the operations must be performed in that particular order or that all of the illustrated operations be performed to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. A network element configuration method, comprising:

receiving a network element registration request, wherein the network element registration request carries a network element identifier of a network element to be registered; wherein, the network element to be registered comprises a distributed unit DU to be registered or a centralized unit CU; and receiving a network element registration request, comprising: receiving a network element registration request sent by the CU or DU through an equipment management system EMS to which the CU or DU belongs;

2. The method according to claim 1, wherein sending the network management identity allocated for the network element to be registered to the requesting party comprises:

3. The method according to claim 1 or 2, wherein the network element identification comprises an operation administration maintenance, OAM, internet protocol, IP, address of the registered network element.

4. A network element configuration method, comprising:

sending a network element registration request to a Network Management System (NMS), wherein the network element registration request carries a network element identifier of a network element to be registered; wherein, the network element to be registered comprises a distributed unit DU to be registered or a centralized unit CU; and sending a network element registration request to a network management system NMS, specifically including: transmitting the network element registration request to a Network Management System (NMS) through an attributed Equipment Management System (EMS);

5. The method of claim 4, wherein the network management identity is configured by the EMS based on a network management identity sent by the NMS.

6. The method of claim 4 or 5, wherein the network element identification comprises an operations administration maintenance, OAM, internet protocol, IP, address of the registered network element.

7. A network element configuration apparatus, comprising:

a receiving unit, configured to receive a network element registration request, where the network element registration request carries a network element identifier of a network element to be registered; wherein, the network element to be registered comprises a distributed unit DU to be registered or a centralized unit CU; the receiving unit is specifically configured to receive a network element registration request sent by the CU or the DU through an EMS to which the CU or the DU belongs;

8. The apparatus of claim 7, wherein,

the sending unit is specifically configured to send, to the EMS, a network management identifier allocated to the CU or the DU, where the network management identifier allocated to the CU or the DU is configured by the EMS.

9. The apparatus of claim 7 or 8, wherein the network element identification comprises an operations administration maintenance, OAM, internet protocol, IP, address of the registered network element.

10. A network element configuration apparatus, comprising:

a sending unit, configured to send a network element registration request to a network management system NMS, where the network element registration request carries a network element identifier of a network element to be registered; wherein, the network element to be registered comprises a distributed unit DU to be registered or a centralized unit CU; the sending unit is specifically configured to send the network element registration request to a network management system NMS through an attributed device management system EMS;

and the storage unit is used for storing the network management identification.

11. The apparatus of claim 10, wherein the network management identity is configured by the EMS based on a network management identity sent by the NMS.

12. The apparatus according to claim 10 or 11, wherein the network element identification comprises an operation administration maintenance, OAM, internet protocol, IP, address of the registered network element.

13. A computing device comprising at least one processor, and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1-6.

14. A computer readable medium, characterized in that it stores a computer program executable by a computing device, which when run on the computing device causes the computing device to perform the steps of the method of any of claims 1-6.