Data modeling method, device and modeling equipment

Abstract

The present invention provides a data modeling method, device and modeling equipment, the method comprising: establishing a data model of an extended pico base station; wherein the data model records the management parameters of the management object by taking the device-level object of the extended pico base station as the root node and the management object of the management device under the device-level object as the child node; wherein the management device under the device-level object includes an extension unit, a host unit and a remote unit. With this method, by expanding the management device under the device-level Device, an extension unit, a host unit and a remote unit are added, and the established data model records the management parameters of the corresponding management objects of the extension unit, the host unit and the remote unit respectively, so that the established data model can meet the data modeling of the management objects of each unit of the extended pico base station and form an overall wave base station management object.

Description

Technical Field

[0001] The present invention relates to the field of network management technology, and in particular to a data modeling method, device and modeling equipment. Background Art

[0002] In the communication network, in addition to the macro base stations of the main equipment manufacturers, there are also a large number of integrated skin base stations to meet the indoor coverage and capacity improvement. The management of integrated skin base stations complies with the Customer Premises Equipment WAN Management Protocol (CWMP).

[0003] The data model of the integrated pico base station consists of a set of data objects, including basic device information, time configuration, network interface and protocol stack configuration, routing and bridging management, throughput statistics, and diagnostic tests. The basis of the data model is the interface stack mechanism, where the network interface and protocol layers are modeled as independent data objects (also called interface objects) that can be stacked together into any configuration that the device may support.

[0004] With the application scenario requirements, the device form of Pico Base Stations is also constantly evolving, forming two device forms: integrated and extended (distributed), among which:

[0005] Integrated pico base station: mainly refers to equipment containing baseband and remote unit, with the main functions of base station, and can be directly connected to the core network;

[0006] Distributed pico base station: includes a host unit, an extension unit and a radio frequency remote unit, and the host unit is connected to the core network.

[0007] The management model of existing pico base stations in the network management system can support integrated pico base station management. The data management model is formed into a typical model tree structure, using the device as the root node. Any management of the device is completed by the branches under the root node, and each branch contains more leaf nodes.

[0008] As for the extended (distributed) pico base stations, the above tree structure under one device obviously cannot support the management of multiple separate devices. In addition, when each management unit has complete management parameters, if independent models are established for the host unit, the extension unit and the radio frequency remote unit respectively, the three units of the extended (distributed) pico base station cannot be associated into one pico base station, which can only meet the management of a single unit and cannot form an overall logical pico base station management object. Summary of the invention

[0009] The purpose of the technical solution of the present invention is to provide a data modeling method, device and equipment for realizing data object modeling of an extended (distributed) pico base station, for meeting the data management requirements of the host unit, extension unit and remote unit under the extended pico base station, and forming an overall logical pico base station management object.

[0010] An embodiment of the present invention provides a data modeling method, which includes:

[0011] Establish data model of extended pico base station;

[0012] The data model records the management parameters of the management object by taking the device-level object of the extended pico base station as the root node and the management object of the management device under the device-level object as the child node; wherein the management device under the device-level object includes an extension unit, a host unit and a remote unit.

[0013] Optionally, in the data modeling method, in the data model, corresponding management objects are respectively established for the extension unit, the host unit and the remote unit.

[0014] Optionally, in the data modeling method, the data model includes:

[0015] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0016] The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and

[0017] The management device is a third data model of a remote unit; the third data model is included in the second data model, and the device information parameter in the third data model is recorded as the host unit includes the extension unit, and the extension unit includes the remote unit.

[0018] Optionally, in the data modeling method, the data model includes:

[0019] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0020] The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and

[0021] The management device is a third data model of a remote unit; the third data model is included in the first data model, and the device information parameter in the third data model is recorded as a host unit including a remote unit.

[0022] Optionally, in the data modeling method, the data model includes:

[0023] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0024] The management device is a second data model of an extension unit; the device information parameter record in the second data model is an extension unit; and

[0025] The management device is a third data model of a remote unit; the device information parameter record in the third data model is a remote unit.

[0026] Optionally, in the data modeling method, the data model is also used to record management parameters of the management object of the target instance under the device-level object.

[0027] Optionally, the data modeling method, wherein the data model also records the management parameters of the business items by taking the device-level object of the extended pico base station as the root node and the business items of the business service objects under the device-level object as child nodes; wherein, in the data model, corresponding business items are established for the extension unit, host unit and remote unit, respectively, and the management parameters of the business items are associated with the corresponding extension unit, host unit and remote unit, respectively.

[0028] The embodiment of the present invention further provides a data modeling device, which includes:

[0029] A model building unit, used for building a data model of an extended pico base station;

[0030] The data model records the management parameters of the management object by taking the device-level object of the extended pico base station as the root node and the management object of the management device under the device-level object as the child node; wherein the management device under the device-level object includes an extension unit, a host unit and a remote unit.

[0031] An embodiment of the present invention also provides a modeling device, which includes: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program implements the data modeling method as described in any one of the above items when executed by the processor.

[0032] At least one of the above technical solutions of the present invention has the following beneficial effects:

[0033] By adopting the data modeling method described in the embodiment of the present invention, the management device under the device level Device is expanded, and the extension unit, the host unit and the remote unit are added. The management parameters of the corresponding management objects of the extension unit, the host unit and the remote unit are recorded respectively through the established data model, so that the established data model can meet the data modeling of the management objects of each unit of the extended pico base station and form an overall pico base station management object. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 A schematic diagram of the network architecture of an extended pico base station using the data modeling method according to an embodiment of the present invention;

[0035] Figure 2 A schematic diagram of a flow chart of a data modeling method according to an embodiment of the present invention;

[0036] Figures 3 to 8 It is a schematic diagram of each model using the method provided in the specific embodiment 1;

[0037] Figures 9 to 13 It is a schematic diagram of each model using the method provided in the specific embodiment 2;

[0038] Figures 14 to 18 It is a schematic diagram of each model using the method provided in the specific embodiment 3;

[0039] Fig.19 A schematic diagram of the structure of a data modeling device according to an embodiment of the present invention;

[0040] Fig. 20 It is a schematic diagram of the structure of the data modeling device described in an embodiment of the present invention. DETAILED DESCRIPTION

[0041] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0042] Figure 1 A schematic diagram of the network architecture of an extended pico base station using the data modeling method described in an embodiment of the present invention.

[0043] Among them, the extended pico base station includes a host unit, an extension unit and a remote unit. The host unit can be connected to multiple extension units, and each extension unit can be connected to multiple remote units; the host unit is connected to the network management system and the core network respectively, and the remote unit is connected to the user terminal.

[0044] In an embodiment of the present invention, the data model of the extended pico base station can adopt the model object defined by CWMP, such as the TR181 data structure model defined by CWMP, including: device information parameters, cell service parameters, software version parameters, neighboring cell parameters, base station network management parameters, RAN protocol stack parameters, mobility parameters, log parameters, etc.

[0045] Based on the above data structure model, for the data model created by the pico base station, the device-level Device object is used as the root node, and the various management objects under the device-level Device object are used as child nodes. Each child node can contain more leaf nodes for recording management parameters. For example, the model node of the device information parameter can be expressed as:

[0046] Device.DeviceInfo.ManufacturerOUI, that is, device.Device information.Manufacturer;

[0047] The management node of a cell can be represented as:

[0048] Device.Services.FAPService.{i}.CellConfig.NR.RAN.Common.gNBId, that is, device.service.cell service {i-th instance}.cell configuration.5G new air interface.radio access network.common parameters.base station gNB identifier.

[0049] In conventional technology, the above data structure model can be applied to an integrated pico base station. For an extended pico base station, since it includes a host unit, an extension unit and a remote unit, the tree-structured data model under the above device-level Device object cannot support the management of multiple separate devices.

[0050] In order to solve the above technical problems, an embodiment of the present invention provides a data modeling method, such as Figure 2 As shown, the data modeling method includes:

[0051] S210, establishing a data model of an extended pico base station;

[0052] The data model records the management parameters of the management object by taking the device-level object of the extended pico base station as the root node and the management object of the management device under the device-level object as the child node; wherein the management device under the device-level object includes an extension unit, a host unit and a remote unit.

[0053] The data modeling method described in this embodiment is used to expand the management device under the device level Device compared to the TR181 data structure model defined by CWMP in the prior art, and add extension units, host units and remote units. The management parameters of the corresponding management objects of the main unit (MU), extension unit (EU) and remote unit (RU) are recorded respectively through the established data model, so that the established data model can meet the data modeling of the management objects of each unit of the extended pico base station and form an overall pico base station management object.

[0054] Therefore, based on the data modeling method described in this embodiment, not only can the extension unit, host unit and remote unit be managed separately to meet the data management requirements of the host unit, extension unit and remote unit under the extended pico base station, but also an overall logical pico base station management object can be formed; in addition, the data modeling method can support the management of a single unit without exposing the management interface.

[0055] The data modeling method described in this embodiment is adopted. On the one hand, the device information Device Info of the management device in the data model becomes multi-instance information, which is used to record the device information parameters corresponding to the management device being the extension unit, the host unit and the remote unit respectively.

[0056] Optionally, the data model is also used to record management parameters of the management object of the target instance under the device-level Device object.

[0057] For example, when the target instance is the i-th instance, the device information parameters of the corresponding host unit can be expressed as MU.{i}; the device information parameters of the corresponding extension unit can be expressed as EU.{i}; and the device information parameters of the corresponding remote unit can be expressed as RU.{i}.

[0058] It should be noted that, in the embodiment of the present invention, the parameter {i} included in each parameter mentioned below represents the corresponding parameter in the i-th instance, and the meaning of the parameter {i} will not be repeated below.

[0059] In one implementation manner, the data model includes:

[0060] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0061] The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and

[0062] The management device is a third data model of a remote unit; the third data model is included in the second data model, and the device information parameter in the third data model is recorded as the host unit includes the extension unit, and the extension unit includes the remote unit.

[0063] In this implementation, compared with the prior art, the device information parameters under the device-level object in the data model are expanded, including device information parameters corresponding to the host unit, the extension unit and the remote unit respectively, and the device information parameters corresponding to the three units adopt a tree structure to form a logical architecture of inclusion relationship; wherein, the host unit MU includes the extension unit EU, and the extension unit EU includes the remote unit RU, that is, the data model of the host unit includes the data model of the extension unit, and the data model of the extension unit includes the data model of the remote unit; the device information parameters of the management device are recorded as follows: For example, under the device-level object, the device information parameters include:

[0064] Record the device information of the host unit, expressed as: Device.DeviceInfo.MU.{i};

[0065] Record the device information of the host unit including the extension unit, expressed as: Device.DeviceInfo.MU.{i}.EU.{i};

[0066] The host unit including the extension unit is recorded, and the extension unit includes the device information of the remote unit, which is expressed as: Device.DeviceInfo.MU.{i}.EU.{i}.RU.{i}.

[0067] In another embodiment, the data model includes:

[0068] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0069] The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and

[0070] The management device is a third data model of a remote unit; the third data model is included in the first data model, and the device information parameter in the third data model is recorded as a host unit including a remote unit.

[0071] In this implementation, compared with the prior art, the device information parameters under the device-level object in the data model are expanded, including device information parameters corresponding to the host unit, the extension unit and the remote unit respectively, and the device information parameters corresponding to the three units adopt a tree structure to form a logical architecture of inclusion relationship; wherein, the host unit MU includes the extension unit EU, and the host unit MU includes the remote unit RU, that is, the data model of the host unit includes the data model of the extension unit, and the data model of the host unit includes the data model of the remote unit; in this implementation, the device information parameters of the management device are recorded as follows: For example, under the device-level object, the device information parameters include:

[0072] Record the device information of the host unit, expressed as: Device.DeviceInfo.MU.{i};

[0073] Record the device information of the host unit including the extension unit, expressed as: Device.DeviceInfo.MU.{i}.EU.{i};

[0074] Records the device information of the host unit including the remote unit, expressed as: Device.DeviceInfo.MU.{i}.RU.{i}.

[0075] In another embodiment, the data model includes:

[0076] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0077] The management device is a second data model of an extension unit; the device information parameter record in the second data model is an extension unit; and

[0078] The management device is a third data model of a remote unit; the device information parameter record in the third data model is a remote unit.

[0079] In this implementation, compared with the prior art, the device information parameters under the device-level object in the data model are expanded, including device information parameters corresponding to the host unit, the extension unit and the remote unit respectively, and the device information parameters corresponding to the three units adopt a tree structure, but compared with the above two implementations, in this implementation, the device information parameters of the three units are in a parallel relationship, that is, the data model of the host unit, the data model of the extension unit and the data model of the remote unit are respectively parallel; in this implementation, the device information parameters of the management device are recorded as follows: For example, under the device-level object, the device information parameters include:

[0080] Record the device information of the host unit, represented as Device.DeviceInfo.MU.{i};

[0081] Record the device information of the extension unit, expressed as Device.DeviceInfo.EU.{i};

[0082] Record the device information of the remote unit, expressed as Device.DeviceInfo.RU.{i}.

[0083] In another implementation manner of the data modeling method described in the embodiment of the present invention, the data model established in step S110 corresponds to the management devices being the extension unit, the host unit and the remote unit, and corresponding management objects are established respectively.

[0084] This implementation method expands the corresponding management objects as needed based on each expanded management device, namely, the extension unit, the host unit and the remote unit, and can expand the specific management objects respectively. For example, the expanded management objects include fault alarm management, software management, log management, cell parameter management, neighboring cell management, mobility management, measurement report management, etc.

[0085] Of course, the management objects extended by the extension unit, the host unit and the remote unit may be different, and are not limited to the above examples.

[0086] The data model also uses the device-level object of the extended pico base station as the root node, and the business items of the business service objects under the device-level object as child nodes, for recording the management parameters of the business items; wherein the corresponding management devices are the extension unit, the host unit and the remote unit, respectively, and corresponding business items are established, and the management parameters of the business items are associated with the corresponding extension unit, the host unit and the remote unit.

[0087] By adopting the data modeling method described in the embodiment of the present invention, wireless business services can be modeled, management parameters under business items can be expanded, and management objects of business service objects associated with corresponding extension units, host units and remote units can be added.

[0088] For example, the cell configuration CellConfig of the service item under the service object can be extended to add the cell configurations associated with the extension unit, the host unit and the remote unit, for example, respectively expressed as:

[0089] Service.CellConfig.MU.{i};

[0090] Service.CellConfig.EU.{i};

[0091] Service.CellConfig.RU.{i}.

[0092] By using the data model established by the data modeling method of the above-mentioned implementation mode, the host unit can send the management operation of the extension unit or the remote unit to the target management unit through the fronthaul management interface.

[0093] According to the requirement that the management interface is uniformly provided by the host unit, the host unit needs to support the management operation of the configuration database. That is, when the network management system needs to operate and manage an extension unit EU or a remote unit RU under the host unit MU, the receiving end of the management command is the host unit, then:

[0094] The host unit MU parses the management command, parses the operation node information carried in the message, and parses the management operation that needs to be processed in the message, such as: add, delete, modify, check, etc.

[0095] The host unit MU parses the message to obtain the operation target and operation method, and organizes these contents into management messages according to the fronthaul interface management interface protocol;

[0096] Optionally, the host unit MU sends the management message to the management target via the fronthaul interface management protocol;

[0097] The management target receives the management message and finally sends the feedback message to the host unit through the fronthaul interface.

[0098] The following is an example of the implementation of the data modeling method described in the present invention in conjunction with specific embodiments. Specific embodiment 1

[0100] In the first embodiment, the data model established by the data modeling method is used to expand the management equipment under the device-level object, and the extension unit, host unit and remote unit are added. Accordingly, the device information under the device-level object is expanded, and the device information DeviceInfo is changed to multiple instances, which can support multiple devices, and the host unit, extension unit and remote unit are distinguished by carrying multiple types of instances. Accordingly, corresponding device information parameters are added to the corresponding host unit, extension unit and remote unit respectively.

[0101] In the first embodiment, the device information parameters corresponding to the host unit, the extension unit and the remote unit adopt a tree structure to form a logical framework containing relationships, such as Figure 3 and Figure 4 The figure shows the relationship diagram of the device information parameters of the device information DeviceInfo under the device level object. The host unit MU includes the extension unit EU, and the extension unit EU includes the remote unit RU. Then the device information parameters under the corresponding device information DeviceInfo include:

[0102] Device information DeviceInfo;

[0103] Device.DeviceInfo.MU.{i};

[0104] Device.DeviceInfo.MU.{i}.EU.{i};

[0105] Device.DeviceInfo.MU.{i}.EU.{i}.RU.{i}.

[0106] Optionally, in the first specific embodiment, based on each management device expanded, that is, the extension unit, the host unit and the remote unit, the interface management is re-regulated. If there is a management requirement for the signaling, data and management plane of the host unit, the extension unit and the remote unit, the corresponding management objects should be added. For example, the data model when the Ethernet interface Ethemet.interface is added to the host unit, the extension unit and the remote unit is as follows: Figure 5 As shown, in the specific embodiment 1, the Ethernet interface models established for the host unit, the extension unit and the remote unit respectively include:

[0107] Device.DeviceInfo.MU.{i}.Ethemet.interface{i};

[0108] Device.DeviceInfo.MU.{i}.EU.{i}.Ethemet.interface{i};

[0109] Device.DeviceInfo.MU.{i}.EU.{i}.RU.{i}.Ethemet.interface{i}.

[0110] Similarly, the data model established based on other types of interfaces (such as Asynchronous Transfer Mode (ATM) interface, etc.) is consistent with this structure type and will not be described in detail here.

[0111] Optionally, in the first specific embodiment, based on each management device that is expanded, that is, the extension unit, the host unit and the remote unit, the device-level management is re-regulated. For example, the host unit, the extension unit and the remote unit all have software management functions, fault alarm functions, performance management, log management, file management, etc. Each function corresponds to a management object, which can be recorded in the management parameters of the corresponding data model of each management device (MU.{i}, EU.{i} and RU.{i}). For example, when the management objects established by the host unit, the extension unit and the remote unit all include software management SoftwareManagement, as shown in FIG. Figure 6 As shown, in the first embodiment, the corresponding data models established include:

[0112] Device.DeviceInfo.MU.{i}.SoftwareManagement;

[0113] Device.DeviceInfo.MU.{i}.EU.{i}.SoftwareManagement;

[0114] Device.DeviceInfo.MU.{i}.EU.{i}.RU.{i}.SoftwareManagement.

[0115] Similarly, the data model established based on other types of management objects (such as fault alarms and log files) is consistent with this structure type and will not be described in detail here.

[0116] Optionally, in the first specific embodiment, the base station service is extended, and the corresponding extension unit, host unit and remote unit respectively extend the corresponding service items, and the management parameters of the established service items are associated with the corresponding extension unit, host unit and remote unit. For example, when the service items established by the host unit, the extension unit and the remote unit all include the cell configuration CellConfig, Figure 7 As shown, in the data model, the service sub-items under the service items, such as the cell configuration, respectively correspond to the relevant parameters of the associated extension unit, the host unit and the remote unit, and the corresponding data models respectively include:

[0117] Device.Services.FAPService.{i}.CellConfig.NR.RAN.MU.{i}.****

[0118] Device.Services.FAPService.{i}.CellConfig.NR.RAN.EU.{i}.****

[0119] Device.Services.FAPService.{i}.CellConfig.NR.RAN.RU.{i}.****

[0120] "****" indicates specific configuration parameters, which are determined according to management requirements.

[0121] Optionally, in the first specific embodiment, the corresponding extension unit, the host unit and the remote unit can respectively extend the corresponding unique management objects, such as extending the bit error rate for the extension unit and extending the transmission power for the remote unit. In the embodiment of the present invention, the structure and method of establishing the data model for the extended unique management objects can refer to Figure 8 As shown, no further detailed description is given here.

[0122] Among them, Figure 8 In the example, ".****.Parameter****" means: the configuration parameters of a certain type of configuration parameters under the i-th management object instance of a certain unit. Furthermore, multiple instances of management parameters can also be defined in the format of ".Some type of management parameter.{m-th instance}.Management parameter.{n-th instance}". Specific embodiment 2

[0124] In the second embodiment, the data model established by the data modeling method is used to expand the management equipment under the device-level object, and the extension unit, host unit and remote unit are added. Accordingly, the device information under the device-level object is expanded, and the device information DeviceInfo is changed to multiple instances, which can support multiple devices, and the host unit, extension unit and remote unit are distinguished by carrying multiple types of instances. Accordingly, corresponding device information parameters are added to the host unit, extension unit and remote unit respectively.

[0125] In the first embodiment, the device information parameters corresponding to the host unit, the extension unit and the remote unit adopt a tree structure to form a logical architecture of inclusion relationship; wherein the host unit MU includes the extension unit EU, the host unit MU includes the remote unit RU, and the extension unit EU and the remote unit RU are in a parallel relationship and are at the same tree level. With this implementation, the decoupling scenario of the extension unit EU and the remote unit RU is considered, that is, the fronthaul interface is open, and the network management can independently manage the remote unit RU.

[0126] like Fig. 9 and Fig.10FIG. 1 shows a relationship diagram of device information parameters of device information DeviceInfo under the device level object in this embodiment. The host unit MU includes the extension unit EU, and the host unit MU includes the remote unit RU. Then, the device information parameters under the corresponding device information DeviceInfo include:

[0127] Device information DeviceInfo;

[0128] Device.DeviceInfo.MU.{i};

[0129] Device.DeviceInfo.MU.{i}.EU.{i};

[0130] Device.DeviceInfo.MU.{i}.RU.{i}.

[0131] In the second embodiment, based on Fig. 9 and Fig.10 The relationship between the data models of the host unit MU, the extension unit EU and the remote unit RU is shown in the figure. The interface management is re-planned. If there is a management requirement for the signaling, data and management plane of the host unit, the extension unit and the remote unit, the corresponding management objects should be added. For example, the data model when the Ethernet interface Ethemet.interface is added to the host unit, the extension unit and the remote unit is as follows Fig.11 As shown, in the specific embodiment 2, the Ethernet interface models established for the host unit, the extension unit and the remote unit respectively include:

[0132] Device.DeviceInfo.MU.{i}.Ethemet.interface{i};

[0133] Device.DeviceInfo.MU.{i}.EU.{i}.Ethemet.interface{i};

[0134] Device.DeviceInfo.MU.{i}.RU.{i}.Ethemet.interface{i}.

[0135] Similarly, the data model established based on other types of interfaces (such as ATM, etc.) is consistent with this structure type and will not be described in detail here.

[0136] Optionally, in the second specific embodiment, based on each management device that is expanded, that is, the expansion unit, the host unit and the remote unit, the device-level management is re-regulated. For example, when the management objects established by the host unit, the expansion unit and the remote unit all include software management SoftwareManagement, Fig.12 As shown, in the second implementation mode, the corresponding data models established include:

[0137] Device.DeviceInfo.MU.{i}.SoftwareManagement;

[0138] Device.DeviceInfo.MU.{i}.EU.{i}.SoftwareManagement;

[0139] Device.DeviceInfo.MU.{i}.RU.{i}.SoftwareManagement.

[0140] Similarly, the data model established based on other types of management objects (such as fault alarms and log files) is consistent with this structure type and will not be described in detail here.

[0141] Optionally, in the second specific embodiment, the corresponding extension unit, the host unit and the remote unit can respectively extend the corresponding unique management objects. In the second specific embodiment, the structure and method of establishing the data model for the extended unique management objects can refer to Fig.13 Compared with the first embodiment, in the second embodiment, the remote unit is parallel to the extension unit and is not included in the extension unit, but is connected to and included in the host unit.

[0142] Furthermore, in the second specific embodiment, the corresponding extension unit, host unit and remote unit respectively extend corresponding service items, and the manner of establishing the data model is the same as that of the first specific embodiment, and no further examples are given here. Specific embodiment three

[0144] In the third embodiment, the data model established by the data modeling method is used to expand the management equipment under the device-level object, and the extension unit, host unit and remote unit are added. Accordingly, the device information under the device-level object is expanded, and the device information DeviceInfo is changed to multiple instances, which can support multiple devices, and the host unit, extension unit and remote unit are distinguished by carrying multiple types of instances. Accordingly, corresponding device information parameters are added to the corresponding host unit, extension unit and remote unit respectively.

[0145] In the third embodiment, the device information parameters corresponding to the host unit, the extension unit and the remote unit adopt a tree structure, and the device information parameters of the three units are in a parallel relationship. Among them, the host unit, the extension unit and the remote unit are at the same tree level. This scenario takes into account the decoupling scenario of the host unit, the extension unit and the remote unit, and the network manager can manage each unit independently.

[0146] like Fig.14 and Fig.15 FIG. 4 shows a relationship diagram of device information parameters of device information DeviceInfo under the device level object in this embodiment. The device information parameters under the corresponding device information DeviceInfo include:

[0147] Device information DeviceInfo;

[0148] Device.DeviceInfo.MU.{i};

[0149] Device.DeviceInfo.EU.{i};

[0150] Device.DeviceInfo.RU.{i}.

[0151] In the third embodiment, based on Fig.14 and Fig.15 The relationship between the data models of the host unit MU, the extension unit EU and the remote unit RU is shown in the figure. The interface management is re-planned. If there is a management requirement for the signaling, data and management plane of the host unit, the extension unit and the remote unit, the corresponding management objects should be added. For example, the data model when the Ethernet interface Ethemet.interface is added to the host unit, the extension unit and the remote unit is as follows Fig.16 As shown, in the specific embodiment 3, the Ethernet interface models established for the host unit, the extension unit and the remote unit respectively include:

[0152] Device.DeviceInfo.MU.{i}.Ethemet.interface{i};

[0153] Device.DeviceInfo.EU.{i}.Ethemet.interface{i};

[0154] Device.DeviceInfo.RU.{i}.Ethemet.interface{i}.

[0155] Similarly, the data model established based on other types of interfaces (such as ATM, etc.) is consistent with this structure type and will not be described in detail here.

[0156] Optionally, in the third embodiment, based on each management device that is expanded, that is, the expansion unit, the host unit and the remote unit, the device-level management is re-regulated. For example, when the management objects established by the host unit, the expansion unit and the remote unit all include software management SoftwareManagement, Fig.17 As shown, the third implementation mode is adopted, and the corresponding data models established include:

[0157] Device.DeviceInfo.MU.{i}.SoftwareManagement;

[0158] Device.DeviceInfo.EU.{i}.SoftwareManagement;

[0159] Device.DeviceInfo.RU.{i}.SoftwareManagement.

[0160] Similarly, the data model established based on other types of management objects (such as fault alarms and log files) is consistent with this structure type and will not be described in detail here.

[0161] Optionally, in the specific embodiment 3, the corresponding extension unit, host unit and remote unit can respectively extend the corresponding unique management object. In the embodiment 3, for the extended unique management object, the structure and method of establishing the data model can refer to Fig.18 Compared with the first and second embodiments, in the third embodiment, the remote unit, the extension unit and the remote unit are relatively independent and parallel.

[0162] Furthermore, in the third specific embodiment, the corresponding extension unit, host unit and remote unit respectively extend corresponding service items, and the manner of establishing the data model is the same as that of the first specific embodiment, and no further examples are given here.

[0163] The data modeling method described in the embodiment of the present invention uses a device-level Device root node to represent a pico base station, and the logic of the established data model is clearer; using this method, a data model of an extended pico base station supporting an extended unit and a remote unit is established on the basis of an integrated device model, so that the established data model can meet the data modeling of the management objects of each unit of the extended pico base station and form an overall wave base station management object. In addition, through the expansion of the service layer, the association between the service and the device is more flexible.

[0164] Another aspect of the present invention is to provide a data modeling device. Fig.19 As shown, including:

[0165] A model building unit 1901 is used to build a data model of an extended pico base station;

[0166] The data model records the management parameters of the management object by taking the device-level object of the extended pico base station as the root node and the management object of the management device under the device-level object as the child node; wherein the management device under the device-level object includes an extension unit, a host unit and a remote unit.

[0167] Optionally, in the data modeling device, corresponding management objects are respectively established for the extension unit, the host unit and the remote unit in the data model.

[0168] Optionally, in the data modeling device, the data model includes:

[0169] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0170] The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and

[0171] The management device is a third data model of a remote unit; the third data model is included in the second data model, and the device information parameter in the third data model is recorded as the host unit includes the extension unit, and the extension unit includes the remote unit.

[0172] Optionally, in the data modeling device, the data model includes:

[0173] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0174] The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and

[0175] The management device is a third data model of a remote unit; the third data model is included in the first data model, and the device information parameter in the third data model is recorded as the host unit including the remote unit. Optionally, the data modeling device, wherein the data model includes:

[0176] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0177] The management device is a second data model of an extension unit; the device information parameter record in the second data model is an extension unit; and

[0178] The management device is a third data model of a remote unit; the device information parameter record in the third data model is a remote unit.

[0179] Optionally, in the data modeling device, the data model is also used to record management parameters of the management object of the target instance under the device-level object.

[0180] Optionally, the data modeling device, wherein the data model also records the management parameters of the business items by taking the device-level object of the extended pico base station as the root node and the business items of the business service objects under the device-level object as child nodes; wherein, in the data model, corresponding business items are established for the extension unit, the host unit and the remote unit, respectively, and the management parameters of the business items are associated with the corresponding extension unit, the host unit and the remote unit, respectively.

[0181] The embodiment of the present invention also provides a modeling device, such as Fig. 20 The system shown includes: a processor 2001; and a memory 2003 connected to the processor 2001 via a bus interface 2002, wherein the memory 2003 is used to store programs and data used by the processor 2001 when performing operations, and the processor 2001 calls and executes the programs and data stored in the memory 2003.

[0182] The transceiver 2004 is connected to the bus interface 2002 and is used to receive and send data under the control of the processor 2001. Specifically, the processor 2001 is used to read the program in the memory 2003 and execute the following process:

[0183] Establish data model of extended pico base station;

[0184] The data model records the management parameters of the management object by taking the device-level object of the extended pico base station as the root node and the management object of the management device under the device-level object as the child node; wherein the management device under the device-level object includes an extension unit, a host unit and a remote unit.

[0185] Optionally, in the modeling device, corresponding management objects are respectively established for the extension unit, the host unit and the remote unit in the data model.

[0186] Optionally, in the modeling device, the data model includes:

[0187] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0188] The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and

[0189] The management device is a third data model of a remote unit; the third data model is included in the second data model, and the device information parameter in the third data model is recorded as the host unit includes the extension unit, and the extension unit includes the remote unit. Optionally, the modeling device, wherein the data model includes:

[0190] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0191] The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and

[0192] The management device is a third data model of a remote unit; the third data model is included in the first data model, and the device information parameter in the third data model is recorded as a host unit including a remote unit.

[0193] Optionally, in the modeling device, the data model includes:

[0194] A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and;

[0195] The management device is a second data model of an extension unit; the device information parameter record in the second data model is an extension unit; and

[0196] The management device is a third data model of a remote unit; the device information parameter record in the third data model is a remote unit.

[0197] Optionally, in the modeling device, the data model is also used to record management parameters of the management object of the target instance under the device-level object.

[0198] Optionally, the modeling device, wherein the data model also records the management parameters of the business items by taking the device-level object of the extended pico base station as the root node and the business items of the business service objects under the device-level object as child nodes; wherein, in the data model, corresponding business items are established for the extension unit, host unit and remote unit respectively, and the management parameters of the business items are respectively associated with the corresponding extension unit, host unit and remote unit.

[0199] In addition, a specific embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the steps in the data modeling method as described in any one of the above.

[0200] Specifically, the computer-readable storage medium is applied to the above-mentioned data modeling device. When applied to the data modeling device, the execution steps in the corresponding data modeling method are as described in detail above and will not be repeated here.

[0201] In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0202] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0203] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform some steps of the sending and receiving methods described in various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0204] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary personnel in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A data modeling method, characterized in that: include: Establish data model of extended pico base station; The data model records the management parameters of the management object by taking the device-level object of the extended pico base station as the root node and the management object of the management device under the device-level object as the child node; wherein the management device under the device-level object includes the extension unit, the host unit and the remote unit; Wherein, the data model includes: A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and The management device is a third data model of a remote unit; the third data model is included in the second data model, and the device information parameter in the third data model is recorded as the host unit includes the extension unit, and the extension unit includes the remote unit; or The data model includes: A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and The management device is a third data model of a remote unit; the third data model is included in the first data model, and the device information parameter record in the third data model is that the host unit includes the remote unit; or The data model includes: A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and The management device is a second data model of an extension unit; the device information parameter record in the second data model is an extension unit; and The management device is a third data model of a remote unit; the device information parameter record in the third data model is a remote unit.

2. The data modeling method according to claim 1, characterized in that: In the data model, corresponding management objects are established for the extension unit, the host unit and the remote unit respectively.

3. The data modeling method according to claim 1, characterized in that: The data model is also used to record management parameters of the management object of the target instance under the device-level object.

4. The data modeling method according to claim 1, characterized in that: The data model also records the management parameters of the business items by taking the device-level object of the extended pico base station as the root node and the business items of the business service objects under the device-level object as child nodes; wherein, in the data model, corresponding business items are established for the extension unit, host unit and remote unit respectively, and the management parameters of the business items are associated with the corresponding extension unit, host unit and remote unit respectively.

5. A data modeling device, characterized in that: include: A model building unit, used for building a data model of an extended pico base station; The data model records the management parameters of the management object by taking the device-level object of the extended pico base station as the root node and the management object of the management device under the device-level object as the child node; wherein the management device under the device-level object includes the extension unit, the host unit and the remote unit; Wherein, the data model includes: A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and The management device is a third data model of a remote unit; the third data model is included in the second data model, and the device information parameter in the third data model is recorded as the host unit includes the extension unit, and the extension unit includes the remote unit; or The data model includes: A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and The management device is a second data model of an extension unit; the second data model is included in the first data model, and the device information parameter in the second data model is recorded as a host unit including an extension unit; and The management device is a third data model of a remote unit; the third data model is included in the first data model, and the device information parameter record in the third data model is that the host unit includes the remote unit; or The data model includes: A first data model in which the management device is a host unit; the device information parameter in the first data model is recorded as a host unit; and The management device is a second data model of an extension unit; the device information parameter record in the second data model is an extension unit; and The management device is a third data model of a remote unit; the device information parameter record in the third data model is a remote unit.

6. A modeling device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the data modeling method according to any one of claims 1 to 4.

7. A readable storage medium, characterized in that: The readable storage medium stores a program, and when the program is executed by a processor, the steps in the data modeling method according to any one of claims 1 to 4 are implemented.

Images