WO2019085999A1 - Network element management method and apparatus - Google Patents

Abstract

A network element management method and apparatus. The method comprises: respectively setting, in network management information, a management object instance corresponding to a network resource model corresponding to a CU of a base station and a management object instance corresponding to a network resource model corresponding to a DU of the base station; and managing the CU in the base station according to the management object instance corresponding to the CU; and managing the DU in the base station according to the management object instance corresponding to the DU, wherein the base station comprises at least one CU and at least one DU.

Description

Network element management method and device

The present disclosure claims the priority of the Chinese Patent Application, filed on Jan. 03,,,,,,,,,,,,,,,,,,,,,,

Technical field

The present disclosure relates to the field of wireless communication systems, for example, to a network element management method and apparatus.

Background technique

In the field of wireless communication system management, the interface between the Network Management System (NMS) and the Element Management System (EMS) is called the northbound interface (Itf-N). EMS mainly completes the Element Management Layer (EML) function in the International Telecommunication Union (ITU) Telecommunications Management Network (TMN), that is, completes the management functions of one or more mobile communication devices. Usually, EMS between different device vendors cannot be universal. The NMS mainly performs the Network Management Layer (NML) function in the ITU TMN and is responsible for the management of all network elements in a managed network. In the case where there are multiple device vendors in a managed network (called a subnet), the entire subnet can be managed through EMS management of multiple device vendors.

In the entire management system of the operator, the operation support system (OSS) and the business support system (BSS) are generally included. In general, NMS is generally considered to be included in OSS and is part of OSS.

The industry has begun research on fifth generation mobile communication technology (5G), which is a component of 5G. The so-called network slicing mainly refers to a set of network functions and includes support for the network. A functionalized network resource consisting of an instantiated complete logical network with specific network characteristics, which is used to meet the needs of a particular type of network service. Examples of network characteristics here are ultra-low latency or super high Reliability, etc.

The network slice is obtained by instantiating according to the network slice blueprint, so it is also called the network slice instance. The network slice blueprint refers to a complete definition for describing the structure, configuration, and workflow of the network slice instance. The Network Slicing Management Function (NSMF) completes the instantiation of the network slice according to the definition of the network slice blueprint. Control management of the life cycle of network slicing.

When a network slice is relatively complex, the network slice can be decomposed into sub-slices for ease of management. A sub-slice refers to a logical network composed of a group of network functions and network resources supporting the network functions, having specific network characteristics. A network slice can include zero, one, or multiple sub-slices. The management and orchestration of sub-slices is done by the Network Slice Subnet Management Function (NSSMF).

One of the features of 5G networks is the adoption of virtualization technology. The network functions of 5G networks can be provided by software running on a common hardware platform, namely Virtualized Network Function (VNF).

In addition, on the 5G radio access network (RAN) side, the concept of separation between a central unit (CU) and a distributed unit (DU) is proposed, that is, a 5G base station (generation Node B, gNB) can be composed of CU and DU. Based on the separation technology of CU and DU, the function of gNB can also be partially implemented by virtualization technology, that is, CU can be implemented by VNF, and DU is still implemented by physical network function (PNF). However, the technical solution for managing the base station in the case where the CU and the DU are separated is not provided in the related art.

Summary of the invention

The present disclosure proposes a network element management method and apparatus, which can solve the problem that the base station management lacks a corresponding solution under the CU/DU separation technology.

The present disclosure proposes a network element management method, the method comprising:

Configuring at least one management object instance corresponding to the network resource model corresponding to the at least one CU of the base station and at least one management object instance corresponding to the network resource model corresponding to the at least one DU, respectively, in the management information;

And managing at least one CU in the base station according to the at least one management object instance corresponding to the at least one CU;

And managing at least one DU in the base station according to the at least one management object instance corresponding to the at least one DU.

The present disclosure also provides a network element management apparatus, the apparatus comprising:

a model establishing unit, configured to set, in the management information, at least one management object instance corresponding to the network resource model corresponding to the at least one CU of the base station and at least one management object instance corresponding to the network resource model corresponding to the at least one DU;

a management unit, configured to manage at least one CU in the base station according to the at least one management object instance corresponding to the at least one CU; and, according to the at least one management object instance corresponding to the at least one DU, to at least one DU in the base station Manage.

DRAWINGS

FIG. 1 is a flowchart of a network element management method according to an embodiment;

2 is a schematic diagram of inheritance relationship between information object classes GNbCuFunction and GNbDuFunction provided by an embodiment;

FIG. 3 is a schematic diagram of a relationship between an information object class GNbCuFunction and a GNbDuFunction according to an embodiment;

4 is a schematic diagram of relationship between an information object class GNbCuFunction and a GNbDuFunction according to another embodiment;

FIG. 5 is a schematic diagram of relationship between an information object class GNbCuFunction and a GNbDuFunction according to another embodiment;

FIG. 6 is a schematic structural diagram of a network element management apparatus according to an embodiment.

Detailed ways

The disclosure is described below in conjunction with the accompanying drawings and is not intended to limit the scope of the disclosure. FIG. 1 is a flowchart of a network element management method according to an embodiment. Referring to FIG. 1, the method provided in this embodiment includes the following steps.

Step 110: Set at least one management object instance corresponding to the network resource model corresponding to the at least one CU of the base station and at least one management object instance corresponding to the network resource model corresponding to the at least one DU in the management information.

Step 120: Manage at least one CU in the base station according to the at least one management object instance corresponding to the at least one CU, and manage at least one DU in the base station according to at least one management object instance corresponding to the at least one DU.

In an embodiment, the base station comprises at least one CU, the base station comprising at least one DU.

In an embodiment, the at least one management object instance of the network resource model corresponding to the at least one CU of the base station and the at least one management object instance of the network resource model corresponding to the at least one DU are respectively configured to: set the at least one CU An attribute of each CU, the attribute of each CU includes a private attribute of each of the CUs; setting an attribute of each of the at least one DU, the attributes of each of the DUs including each The private property of the DU.

In an embodiment, the attribute of each CU further includes a common attribute of each CU, and the attribute of each DU further includes a common attribute of each DU.

In an embodiment, the network resource model (NRM) corresponding to the CU of the gNB and the NRM corresponding to the DU are added to the management information of the management system (at least one of the NMS, the EMS, the NSMF, and the NSSMF), that is, respectively Establish the following Information Object Class (IOC): (1), GNbCuFunction: used to represent the CU part of a gNB; (2), GNbDuFunction: used to represent the DU part of a gNB; here a gNB can include at least one DU.

In an embodiment, the private attribute of each CU includes a CU identifier (CuId) item for indicating an identifier of each CU itself; and the private attribute of each DU includes a DU identifier (DuId) Item for indicating the identity of each of the DUs themselves.

In an embodiment, the information object class GNbCuFunction is configured to include an attribute identifier ((Identify, Id) or CuId, which is used to represent the identifier of each CU itself; and the information object class GNbDuFunction established above includes attributes. Id or DuId is used to indicate the identity of each of the DUs themselves.

In an embodiment, the private attribute of each CU further includes a DU identifier list dUIDList for storing an identifier of the DU corresponding to each CU.

In an embodiment, the private attribute of the DU further includes a CU identifier list (cUIDList) for storing an identifier of the CU corresponding to each DU.

In an embodiment, the information object class GNbCuFunction is configured to include an attribute DU identifier list (dUIDList) for storing an identifier (ID) of a DU that belongs to the same gNB as each CU.

In an embodiment, the information object class GNbDuFunction is configured to include an attribute CU identifier (cUID) or a CU identifier list (cUIDList) for storing an ID of a CU that belongs to the same aNB as each DU.

In an embodiment, the common attribute corresponding to the base station is set to a network resource model ManagedFunction, that is, an information object class ManagedFunction; the public attribute of the CU is set to an information object class GNbCuFunction; and the public attribute of the DU is set to an information object class. GNbDuFunction.

The above information object class has at least one of the following relationships: the information object classes GNbCuFunction and GNbDuFunction are both inherited from the information object class ManagedFunction; the information object classes GNbCuFunction and GNbDuFunction are both included in the information object class ManagedElement.

In an embodiment, the method further includes setting a correspondence between each CU and a base station by setting a CuId item of each CU. In an embodiment, for a CU corresponding to the base station, a CuId item of the CU corresponding to the base station is set to include a base station identifier (gNBId) of the base station; and the gNBId item is an identifier of the base station itself (for example, including a base station corresponding to Corresponding relationship between each DU and at least one CU is set by setting a DuId item of each DU; wherein, for each DU corresponding to the CU, the DU corresponding to each CU a CuId term is set to include a CuId item of each CU; or, a correspondence relationship between each DU and a base station is set by setting a CuId item of each DU; wherein, for a DU corresponding to the base station, the base station corresponds to The CuId term of the DU is set to include the gNBId entry of the base station.

In an embodiment, the attribute of each CU is a Managed Object Instance (MOI) of each CU, and the attribute of each DU is an MOI of each DU.

In an embodiment, when a gNB including both a CU and a DU is to be managed, it can be implemented by the following operations.

Step 10: Generate a management object instance of the CU of the gNB, such as GNbCuFunction001.

Step 20: Generate a management object instance of the DU of the gNB, such as GNbDuFunction001 and GNbDuFunction002.

Step 30: The dUIDList in the instance of the GNbCuFunction saves an identifier (ID) of the GNbDuFunction corresponding to the instance of the GNbCuFunction; and the instance of the GNbDuFunction directly associates with the GNbCuFunction instance through the inclusion relationship, or the CU identifier included by the GNbDuFunction ( The cUID) or CU identification list (cUIDList) is used to hold the ID of the instance of the GNbCuFunction corresponding to the GNbDuFunction instance to establish a correspondence with the GNbCuFunction instance.

In an embodiment, the instance of the GNbDuFunction directly associates with the GNbCuFunction instance by the inclusion relationship, and when the relationship between the IOC GNbCuFunction and the GNbDuFunction is defined, the GNbCuFunction name is defined as (Names contain) GNbDuFunction.

In an embodiment, there is no specified sequence between step 10 and step 10.

In an embodiment, when the management system is to perform a management operation on a gNB, first find the GNbCuFunction instance corresponding to the gNB by using the identifier of the GNbCuFunction (Id or CU-Id), and then find the dUIDList in the GNbCuFunction instance. An example of the corresponding GNbDuFunction. The gNB is managed through the GNbCuFunction instance and the GNbDuFunction instance.

In an embodiment, in the case that the DU corresponding to the base station changes, the dUIDList list of the CU corresponding to the base station is modified according to the change of the changed DU.

In an embodiment, the identifier of the added DU is added to the dUIDList list of the CU corresponding to the added DU according to the added DU; and the dUIDList list of the CU corresponding to the reduced DU according to the reduced DU. The identifier of the reduced DU is reduced.

For example, when the DU of a gNB is increased or decreased, the related attributes (such as dUIDList) in the GNbCuFunction instance of the CU corresponding to the increased or decreased DU also need to be updated synchronously. For example, when a DU is shared by multiple gNBs (CUs), when the shared gNB (CU) is increased or decreased, the related attributes (such as cUIDList) in the GNbDuFunction instance of the shared DU also need to be updated synchronously.

In an embodiment, both GNbCuFunction and GNbDuFunction are subclasses of ManagedFunction (see 3GPP TS 28.622).

The technical solution provided by the present disclosure will be described below in conjunction with an implementation scenario.

Example 1

This embodiment provides a modeling method for a CU and a DU included in a gNB, where the CU and the DU are in a one-to-many relationship, and the setting includes the following contents:

1. In the management information of the management system (NMS or EMS or NSMF or NSSMF), add the NRM corresponding to the CU of the gNB and the NRM corresponding to the DU, that is, respectively establish the following IOC: a) GNbCuFunction: used to represent the CU part of a gNB; b) GNbDuFunction: used to represent the DU portion of a gNB; here a gNB may include at least one DU.

2. The information object class GNbCuFunction established above includes at least an attribute Id for indicating the identity of the GNbCuFunction itself.

3. The information object class GNbDuFunction established above includes an attribute Id for indicating the identity of the GNbDuFunction itself.

4. The information object class GNbCuFunction established above includes an attribute DU identifier list (dUIDList) for storing the ID of the DU belonging to the same gNB as the CU.

5. The information object class GNbDuFunction established above includes an attribute CU identifier (cUID) for storing an ID of a CU belonging to the same gNB as the DU.

In an embodiment, the information object class ManagedFunction is an information object class corresponding to the base station, and the relationship between the GNbCuFunction and the GNbDuFunction and the ManagedFunction may be one of the following.

Mode 1-1, FIG. 2 is a schematic diagram of the inheritance relationship between the information object classes GNbCuFunction and GNbDuFunction provided by an embodiment. As shown in FIG. 2, the information object classes GNbCuFunction and GNbDuFunction are inherited from the information object class ManagedFunction.

Mode 1-2, FIG. 3 is a schematic diagram of relationship between information object classes GNbCuFunction and GNbDuFunction provided by an embodiment. As shown in FIG. 3, the information object classes GNbCuFunction and GNbDuFunction are both included in the information object class ManagedElement. In an embodiment, the management of the CU and the DU is set to a level relationship.

Example 2

This embodiment provides a modeling method for a CU and a DU included in a gNB. The CU and the DU are in a many-to-many relationship, and the modeling method is as follows.

1. In the management information of the management system (NMS or EMS or NSMF or NSSMF), the NRM corresponding to the CU of the gNB and the NRM corresponding to the DU are added, that is, the following IOCs are respectively established.

a) GNbCuFunction: used to represent the CU part of a gNB; b) GNbDuFunction: used to represent the DU part of a gNB; here a gNB may include at least one DU.

2. The information object class GNbCuFunction established above includes at least an attribute Id for indicating the identity of the GNbCuFunction itself.

3. The information object class GNbDuFunction established above includes an attribute Id for indicating the identity of the GNbDuFunction itself.

4. The information object class GNbCuFunction established above includes an attribute DU identifier list (dUIDList) for storing the ID of the DU belonging to the same gNB as the CU.

5. The information object class GNbDuFunction established above includes an attribute CU identifier list (cUIDList) for storing an ID of a CU belonging to the same gNB as the DU.

Example 3

This embodiment provides a modeling method for a CU and a DU included in a gNB, which is implemented by a name inclusion method, and the modeling method is as follows.

1. In the management information of the management system (NMS or EMS or NSMF or NSSMF), add the NRM corresponding to the CU of the gNB and the NRM corresponding to the DU, that is, respectively establish the following IOC: a) GNbCuFunction: used to represent the CU part of a gNB; b) GNbDuFunction: used to represent the DU portion of a gNB; here a gNB may include at least one DU.

2. The information object class GNbCuFunction established above includes at least an attribute Id for indicating the identity of the GNbCuFunction itself.

3. The information object class GNbCuFunction established above includes an attribute DU identifier list (dUIDList) for storing the ID of the DU belonging to the same gNB as the CU.

4. The information object class GNbDuFunction established above includes an attribute Id for indicating the identity of the GNbDuFunction itself; where GNbDuFunction is the name contained in the GNbCuFunction. As shown in FIG. 4, it is a schematic diagram of the relationship between the information object class GNbCuFunction and GNbDuFunction. In this embodiment, the GNbCuFunction includes a GNbDuFunction, and the CU and the DU are in a one-to-many relationship, that is, the Id of the GNbDuFunction instance includes the Id of the GNbCuFunction instance to which the GNbDuFunction instance belongs.

For example, an instance of GNbCuFunction has an Id of GNbCuFunction001:

"SubNetwork=ABC,MeContext=MEC001,ManagedElement=ME002,GNbCuFunction=GNBCF001",

Then, the id of the GNbCuFunction 001 including the GNbDuFunction instance GNbDuFunction 002 may be: "SubNetwork=ABC, MeContext=MEC001, ManagedElement=ME002, GNbCuFunction=GNBCF001, GNbDuFunction=GNBDF002".

FIG. 5 is a schematic diagram of a relationship between a more managed object class GNbCuFunction and a GNbDuFunction according to another embodiment. In this embodiment, the GNbCuFunction includes a GNbDuFunction, and the CU and the DU are in a many-to-many relationship.

Example 4

This embodiment provides a method for managing a gNB that includes both a CU and a DU, and the operation is as follows:

1) Generate the MOI of the CU of the gNB, such as GNbCuFunction001.

2) Generate the MOI of the DU of the gNB, such as GNbDuFunction001 and GNbDuFunction002.

3) The dUIDList in the GNbCuFunction instance GNbCuFunction001 holds the IDs of the corresponding GNbDuFunction instances GNbDuFunction001 and GNbDuFunction002.

4) The instances of the GNbDuFunction GNbDuFunction001 and the GNbDuFunction002 attribute cUID hold the ID of the corresponding instance of the GNbCuFunction to establish a correspondence with the GNbCuFunction instance.

In this embodiment, the above 1) and 2) do not have a specified sequence.

Example 5

This embodiment provides a method for managing a gNB that includes both a CU and a DU. The CU and the DU are supported in a many-to-many relationship. The operations are as follows:

1) Generate the MOI of the CU of the gNB, such as GNbCuFunction001.

2) Generate the MOI of the DU of the gNB, such as GNbDuFunction001 and GNbDuFunction002.

3) The dUIDList in the GNbCuFunction instance GNbCuFunction001 holds the IDs of the corresponding GNbDuFunction instances GNbDuFunction001 and GNbDuFunction002.

4) The instances of the GNbDuFunction GNbDuFunction001 and the GNbDuFunction002 attribute cUIDList hold the ID of the corresponding instance of the GNbCuFunction to establish a correspondence with the GNbCuFunction instance.

Example 6

This embodiment provides a method for managing a gNB that includes both a CU and a DU. The CU and the DU belong to the same managed entity (ME), and the operations are as follows:

1) Generate a management object instance including the management unit ManagedElement of the gNB, such as ME001; Note: Here, the generation of ME001 may precede the management object instance of the subsequent CU and DU, that is, the management object instance in which the subsequent CU and DU are generated. At the time, the ME001 may already exist.

2) The MOI of the CU of the gNB is generated, such as GNbCuFunction001, and the GNbCuFunction001 is included in ME001.

3) A management object instance of a DU that generates the gNB, such as GNbDuFunction001 and GNbDuFunction002, the GNbDuFunction001 and GNbDuFunction002 are included in ME001.

4) The dUIDList in the GNbCuFunction instance GNbCuFunction001 holds the IDs of the corresponding GNbDuFunction instances GNbDuFunction001 and GNbDuFunction002.

5) The instances of the GNbDuFunction GNbDuFunction001 and the GNbDuFunction002 attribute cUID hold the ID of the corresponding instance of the GNbCuFunction to establish a correspondence with the GNbCuFunction instance.

In this embodiment, there is no specified sequence between the above 2) and 3).

Example 7

This embodiment provides a method for managing a gNB that includes both a CU and a DU. In this embodiment, the CU and the DU belong to different MEs, and the operations are as follows:

1) Generate a management object instance of the management unit ManagedElement including the CU and DU parts of the gNB, such as ME001 and ME002; Note: Here, the generation of ME001 and ME002 may precede the subsequent instances of the CU and the DU, that is, in the subsequent generation When managing instances of CUs and DUs, the ME001 and ME002 may already exist.

2) The MOI of the CU of the gNB is generated, such as GNbCuFunction001, and the GNbCuFunction001 is included in ME001.

3) The MOI of the DU of the gNB is generated, such as GNbDuFunction001 and GNbDuFunction002, and the GNbDuFunction001 and GNbDuFunction002 are included in ME002.

4) The dUIDList in the GNbCuFunction instance GNbCuFunction001 holds the IDs of the corresponding GNbDuFunction instances GNbDuFunction001 and GNbDuFunction002.

5) The instances of the GNbDuFunction GNbDuFunction001 and the GNbDuFunction002 attribute cUID hold the ID of the corresponding instance of the GNbCuFunction to establish a correspondence with the GNbCuFunction instance.

In an embodiment, there is no specified sequence between the above 2) and 3).

The present embodiment further provides a network element management apparatus based on the same or similar concepts as the above embodiments. Referring to FIG. 6, a network element management apparatus according to this embodiment includes: a model establishing unit 10, configured to set at least one management object instance corresponding to at least one network resource model corresponding to at least one CU of the base station and at least one in the management information. At least one management object instance corresponding to the network resource model corresponding to the DU; the management unit 20 is configured to manage at least one CU in the base station according to the at least one management object instance corresponding to the at least one CU; and, according to the at least one At least one management object instance corresponding to the DU manages at least one DU in the base station.

In an embodiment, the base station comprises at least one CU, the base station comprising at least one DU.

In this embodiment, the model establishing unit is further configured to establish a correspondence between at least one management object instance corresponding to at least one CU included in the same base station and at least one management object instance corresponding to at least one DU; the management unit And at least one management object instance corresponding to the at least one CU included in the base station, at least one management object instance corresponding to the at least one DU, and at least one management object instance corresponding to the at least one CU and at least one management corresponding to the at least one DU The correspondence between the object instances is managed by the base station.

In an embodiment, the model establishing unit 10 is configured to set at least one management object instance corresponding to the network resource model corresponding to the at least one CU of the base station and at least one corresponding to the network resource model corresponding to the at least one DU. Management object instance: setting an attribute of each CU in the at least one CU, the attribute of each CU includes a CuId item for indicating an identifier of each CU itself; setting the at least one DU An attribute of each DU, where the attribute of each DU includes a DuId item, which is used to indicate the identity of each DU itself.

In an embodiment, the attribute of each CU further includes a dUIDList list for storing an identifier of the DU corresponding to each CU.

In an embodiment, the attribute of each DU further includes a cUIDList list for storing an identifier of a CU corresponding to each DU.

In an embodiment, the management unit 20 is further configured to modify the dUIDList list of the CU corresponding to the changed DU according to the change of the changed DU when the DU corresponding to the base station changes.

In an embodiment, according to the added DU, adding the identifier of the added DU to the dUIDList list of the CU corresponding to the added DU; according to the reduced DU, in the dUIDList list of the CU corresponding to the reduced DU The identification of the reduced DU is reduced.

In an embodiment, the model establishing unit 10 is further configured to: set a network resource model of the at least one CU as a network resource model GNbCuFunction; and set a network resource model of the at least one DU as a network resource model GNbDuFunction.

The network resource model is set to have at least one of the following relationships: the network resource models GNbCuFunction and GNbDuFunction are both inherited from the network resource model ManagedFunction; the network resource models GNbCuFunction and GNbDuFunction are both included in the network resource model ManagedElement.

In an embodiment, the model establishing unit 10 is further configured to: set a correspondence relationship between each CU and a base station by setting a CuId item of each CU; wherein, for a CU corresponding to the base station, a CU corresponding to the base station a CuId term is set to include an Id item of the managed element corresponding to the base station; the Id item is an identifier of the ManagedElement itself; and a correspondence relationship between each DU and at least one CU is set by setting a CuId item of each DU; wherein, for each a CU corresponding to the CU, the CuId item of the DU corresponding to each CU is set to include a CuId item of each CU; or, by setting a DuId item of each DU, setting a correspondence relationship between each DU and a base station; The CuId item of the DU corresponding to the base station is set to include an Id item of the ManagedElement.

The embodiments described above are only for the convenience of those skilled in the art, and are not intended to limit the scope of the disclosure.

Claims (17)

A network element management method includes: At least one management object instance corresponding to the network resource model corresponding to the at least one centralized unit CU of the base station and at least one management object instance corresponding to the network resource model corresponding to the at least one distribution unit DU are respectively set in the management information; And managing at least one CU in the base station according to at least one management object instance corresponding to the at least one CU; And managing at least one DU in the base station according to at least one management object instance corresponding to the at least one DU. The network element management method according to claim 1, further comprising: Establishing a correspondence between at least one management object instance corresponding to the at least one CU included in the same base station and at least one management object instance corresponding to the at least one DU; At least one management object instance corresponding to at least one CU included in the base station, at least one management object instance corresponding to at least one DU, and at least one management object instance corresponding to at least one CU and at least one management object instance corresponding to at least one DU The corresponding relationship between the base stations is managed. The network element management method according to claim 1, wherein the at least one management object instance corresponding to the network resource model corresponding to the at least one CU of the base station and the at least one management object corresponding to the network resource model corresponding to the at least one DU are respectively set. Examples include: Setting an attribute of each CU in the at least one CU of the base station, where the attribute of each CU includes a CU identifier CuId item, where the CuId item is used to indicate an identifier of each CU itself; Setting an attribute of each of the at least one DU of the base station, where the attribute of each DU includes a DU identifier DuId item, where the DuId item is used to indicate an identifier of each DU itself. The network element management method according to claim 3, wherein The attribute of each CU further includes a DU identifier list dUIDList, where the dUIDList is used to store an identifier of a DU corresponding to each CU. The network element management method according to claim 4, wherein The CU identifier list cUIDList is further included in the attribute of each DU, where the cUIDList is used to store an identifier of a CU corresponding to each DU. The network element management method according to claim 4 or 5, further comprising: In the case that the DU in the base station changes, the dUIDList of the CU corresponding to the transformed DU is modified according to the change of the DU that is transformed; The dUIDList of the CU corresponding to the DU that is transformed is modified according to the change of the DU in which the transformation occurs, including: And increasing, according to the added DU, an identifier of the added DU in a dUIDList of the CU corresponding to the added DU; and reducing, according to the reduced DU, the reduced DU in a dUIDList of the CU corresponding to the reduced DU Logo. The network element management method according to claim 2, further comprising: Setting a network resource model of at least one CU of the base station as a GNbCuFunction; Setting a network resource model of at least one DU of the base station as a GNbDuFunction; The above network resource model is set to have at least one of the following relationships: The GNbCuFunction and the GNbDuFunction are both inherited from a network resource model ManagedFunction; The GNbCuFunction and the GNbDuFunction are both included in the network resource model ManagedElement. The network element management method according to claim 3, further comprising: Setting a corresponding relationship between each CU and the base station by setting a CuId item of each CU; wherein, for a CU corresponding to the base station, a CuId item of a CU corresponding to the base station is set to include the base station corresponding to The identifier of the ManagedElement is an Id item; the Id item is an identifier of the ManagedElement itself; Setting a correspondence relationship between the each DU and the at least one CU by setting a CuId item of each DU; wherein, for a DU corresponding to each CU, a CuId item of the DU corresponding to each CU is set to include The CuId item of each CU; or, Setting a corresponding relationship between each of the DUs and the base station by setting a CuId item of each of the DUs; wherein, for a DU corresponding to the base station, a CuId item of the DU corresponding to the base station is set to include the base station corresponding to The Id item of the ManagedElement. A network element management device includes: a model establishing unit, configured to set, in the management information, at least one management object instance corresponding to the network resource model corresponding to the at least one centralized unit CU of the base station and at least one management object instance corresponding to the network resource model corresponding to the at least one distribution unit DU; a management unit, configured to manage, according to the management object instance corresponding to the at least one CU, at least one CU in the base station; and, according to the management object instance corresponding to the at least one DU, to at least one DU in the base station Manage. The network element management device according to claim 9, wherein The model establishing unit is further configured to establish a correspondence between a management object instance corresponding to at least one CU included in the same base station and a management object instance corresponding to at least one DU; The management unit is further configured to: at least one management object instance corresponding to at least one CU included in the base station, at least one management object instance corresponding to at least one DU, and at least one management object instance corresponding to at least one CU and at least one DU corresponding to at least one DU The corresponding relationship between at least one management object instance is managed by the base station. The network element management device according to claim 9, wherein The model establishing unit is configured to set at least one management object instance corresponding to the network resource model corresponding to the at least one CU of the base station and at least one management object instance corresponding to the network resource model corresponding to the at least one DU by: Setting an attribute of each CU in the at least one CU of the base station, where the attribute of each CU includes a CU identifier CuId item, where the CuId item is used to indicate an identifier of each CU itself; Setting an attribute of each of the at least one DU of the base station, where the attribute of each DU includes a DU identifier DuId item, where the DuId item is used to indicate an identifier of each DU itself. The network element management device according to claim 11, wherein The attribute of each CU further includes a DU identifier list dUIDList, where the dUIDList is used to store an identifier of the DU corresponding to each CU. The network element management device according to claim 11 or 12, wherein The attribute of each DU further includes a CU identifier list cUIDList, where the cUIDList is used to store an identifier of a CU corresponding to each DU. The network element management device according to claim 12, wherein The management unit is further configured to: when the DU in the base station changes, modify a dUIDList of the CU corresponding to the changed DU according to a change of the changed DU; The management unit is configured to modify the dUIDList of the CU corresponding to the changed DU according to the change of the changed DU by: adding, according to the added DU, the dUIDList of the CU corresponding to the added DU The identifier of the added DU; according to the reduced DU, reducing the identifier of the reduced DU in a dUIDList of the CU corresponding to the reduced DU. The network element management apparatus according to claim 10, wherein the model establishing unit is further configured to: Setting a network resource model of at least one CU of the base station as a network resource model GNbCuFunction; Setting a network resource model of at least one DU of the base station as a network resource model GNbDuFunction; The above network resource model setting has at least one of the following relationships: The GNbCuFunction and the GNbDuFunction are both inherited from the network resource model ManagedFunction; The GNbCuFunction and the GNbDuFunction are both included in the network resource model ManagedElement. The network element management apparatus according to claim 11, wherein the model establishing unit is further configured to: Setting a corresponding relationship between each CU and the base station by setting a CuId item of each CU; wherein, for a CU corresponding to the base station, a CuId item of a CU corresponding to the base station is set to include the base station The identifier of the corresponding ManagedElement is an Id item; the Id item is an identifier of the ManagedElement itself; Setting a correspondence relationship between the each DU and the at least one CU by setting a CuId item of each DU; wherein, for a DU corresponding to each CU, a CuId item of the DU corresponding to each CU is set to include The CuId item of each CU; or, Setting a corresponding relationship between each of the DUs and the base station by setting a CuId item of each of the DUs; wherein, for a DU corresponding to the base station, a CuId item of the DU corresponding to the base station is set to include the base station corresponding to The Id item of the ManagedElement. A computer readable storage medium storing computer executable instructions for performing the method of transmitting a reference signal according to any one of claims 1-8.

Images