WO2021249146A1 - 小区管理模型和小区管理方法 - Google Patents

小区管理模型和小区管理方法 Download PDF

Info

Publication number
WO2021249146A1
WO2021249146A1 PCT/CN2021/094755 CN2021094755W WO2021249146A1 WO 2021249146 A1 WO2021249146 A1 WO 2021249146A1 CN 2021094755 W CN2021094755 W CN 2021094755W WO 2021249146 A1 WO2021249146 A1 WO 2021249146A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
cell
logical
base station
carrier
Prior art date
Application number
PCT/CN2021/094755
Other languages
English (en)
French (fr)
Inventor
李静岚
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021249146A1 publication Critical patent/WO2021249146A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/18—Network planning tools

Definitions

  • This application relates to communication technology, for example, to a cell management model and cell management method.
  • the base station that is, the new wireless node B (gNB) is divided into two parts: a centralized unit (CU) and a distributed unit (DU).
  • the base station centralized unit gNB-CU
  • the base station distribution unit gNB-DU
  • the gNB-CU is deployed on the CU device
  • the gNB-DU is deployed on the DU device
  • the gNB-CU and gNB-DU can also be deployed on one device.
  • a segment of carrier resource can only correspond to one cell, and a cell can only have one cell identifier, one tracking area code (TAC), and one wireless notification area code (RAN-based Notification Area Code, RAC).
  • TAC tracking area code
  • RAN-based Notification Area Code RAC
  • multiple synchronization/physical broadcast channel block Multiple Synchronization Signal/PBCH Block, Multi-SSB
  • Multi-SSB Multiple Synchronization Signal/PBCH Block
  • new network sharing concepts are introduced, between carrier and cell, between cell and cell identity, between cell and TAC, The relationship between the community and the RAC has changed dramatically.
  • a cell can have multiple cell identities (cellIdentity, composed of gNB ID (gNB ID) and cell ID (Cell ID)), TAC, RAC.
  • gNB ID gNB ID
  • Cell ID cell ID
  • the cell management model in the related technology can no longer meet the management requirements, and it is urgent to provide a method for managing a new cell.
  • the present application provides a cell management model and cell management method, so that the realization and configuration of cell management are clear and clear, and the configuration management situation of consistency and configuration conflicts caused by repeated air interface resource configuration is improved.
  • the embodiments of the present application provide a cell management model, which is applied to a three-layer network architecture composed of carriers, physical cells, and logical cells;
  • one carrier of one distribution unit device corresponds to multiple physical cells
  • each physical cell corresponds to different logical cells according to different operators
  • the distribution unit side of each logical cell corresponds to one base station distribution unit of one distribution unit device
  • Different logical cell distribution unit sides of the same physical cell correspond to different base station distribution units.
  • the centralized unit side of each logical cell corresponds to a base station centralized unit of the centralized unit device
  • each base station distribution unit corresponds to a base station centralized unit.
  • the base station centralized unit corresponds to one or more base station distribution units, and the base station centralized units, base station distribution units, and logical cells corresponding to the same operator form a wireless logical network;
  • the cell management model includes a network management unit, a centralized management network element, and a distributed management network element.
  • the network management unit is configured to manage the wireless logical network through the centralized management network element and the distributed management network element.
  • the centralized management network element is set to manage the wireless logical network through a base station centralized unit, and the distributed management network element is set to manage the wireless logical network through a base station distribution unit.
  • the embodiments of the present application provide a cell management method for managing a three-layer network architecture composed of carriers, physical cells, and logical cells;
  • one carrier of one distribution unit device corresponds to multiple physical cells
  • each physical cell corresponds to different logical cells according to different operators
  • the distribution unit side of each logical cell corresponds to one base station distribution unit of one distribution unit device
  • Different logical cell distribution unit sides of the same physical cell correspond to different base station distribution units.
  • the centralized unit side of each logical cell corresponds to a base station centralized unit of the centralized unit device
  • each base station distribution unit corresponds to a base station centralized unit.
  • the base station centralized unit corresponds to one or more base station distribution units, and the base station centralized units, base station distribution units, and logical cells corresponding to the same operator form a wireless logical network;
  • the cell management method includes: managing the wireless logical network through a base station centralizing unit and the base station distributing unit.
  • Figure 1 is a schematic diagram of a carrier in a Multi-SSB scenario
  • Figure 2 is a schematic structural diagram of a three-tier cell management architecture provided by an embodiment of the application.
  • Figure 3 is a schematic structural diagram of a cell management model provided by an embodiment of the application.
  • FIG. 4 is a schematic diagram of management of a cell management model provided by an embodiment of the application.
  • FIG. 5 is a schematic diagram of the correspondence and reference relationship of management objects based on the cell management model shown in FIG. 4;
  • FIG. 6 is a flowchart of a cell management method provided by an embodiment
  • Fig. 7 is a schematic diagram of a cell management model provided in the first embodiment
  • FIG. 8 is a schematic diagram of a cell management configuration provided in the first embodiment
  • Fig. 9 is a schematic diagram of a cell management model provided in the second embodiment.
  • FIG. 10 is a schematic diagram of the cell management configuration provided in the second embodiment.
  • Fig. 11 is a schematic diagram of a cell management model provided in the third embodiment.
  • FIG. 12 is a schematic diagram of the cell management configuration provided in the third embodiment.
  • FIG. 13 is a schematic diagram of a cell management model provided in the fourth embodiment.
  • FIG. 14 is a schematic diagram of a cell management configuration provided in the fourth embodiment.
  • FIG. 15 is a schematic diagram of a cell management model provided in Embodiment 5.
  • FIG. 16 is a schematic diagram of a cell management configuration provided in the fifth embodiment.
  • FIG. 17 is a schematic diagram of a cell management model provided in the sixth embodiment.
  • Fig. 18 is a schematic diagram of a cell management configuration provided in the sixth embodiment.
  • FIG 1 is a schematic diagram of a carrier in a Multi-SSB scenario.
  • one carrier corresponds to multiple synchronization/physical broadcast channel blocks (Synchronization Signal/PBCH Block, SSB), which are SSB1, SSB2, SSB3, and SSB4.
  • the NR Cell Global Identifier (NCGI) of SSB1 is 5, and the NCGI of SSB1 is 6.
  • UE1 and UE2 access the cell of NCGI 5, and UE3 accesses the cell of NCGI 6.
  • the initial (Initial) Band Width Part (BWP) of UE1 occupies SSB1, the dedicated BWP1 occupies SSB1, SSB2, and SSB3, and the dedicated BWP2 occupies SSB4.
  • BWP Band Width Part
  • the initial BWP of UE2 occupies SSB1, and the dedicated BWP1 occupies SSB1 and SSB2.
  • the initial BWP of UE3 occupies SSB3, the dedicated BWP1 occupies SSB1, SSB2, and SSB3, and the dedicated BWP2 occupies SSB4.
  • the embodiments of the present application provide a cell management model and a cell management method, which are used to perform cell management on a network with the foregoing conditions.
  • the cell management model and cell management method provided in the embodiments of this application are described based on 5G cells, but the cell management models and cell management methods provided in the embodiments of this application are not limited to 5G communication systems.
  • the cell management model and cell management method provided in the embodiments of the present application can also be used.
  • Figure 2 is a schematic structural diagram of a three-layer cell management architecture provided by an embodiment of the application. As shown in Figure 2, the cell management model provided in this embodiment is applied to a three-layer network architecture composed of carriers, physical cells, and logical cells.
  • this embodiment divides cells in related technologies into three layers: carrier, physical cell, and logical cell, and the logical cell extends from the logical base station and the wireless logical network.
  • the logical base station includes a base station distribution unit (gNB-DU) and a base station centralized unit (gNB-CU), and each logical cell is divided into a logical cell centralized unit side and a logical cell distribution unit side.
  • gNB-DU base station distribution unit
  • gNB-CU base station centralized unit
  • each logical cell is divided into a logical cell centralized unit side and a logical cell distribution unit side.
  • One carrier resource (Carrier) on a centralized unit (Distrubbed Unit, DU) device corresponds to one or more physical cells.
  • DU Distributed Unit
  • FIG 2 there are two DU devices, and each DU device corresponds to three physical cells, PhysicalCell1, PhysicalCell2, and PhysicalCell3. Take for example.
  • Each physical cell is divided into different logical cells according to different operators.
  • Each logical cell is divided into a logical cell centralization unit side and a logical cell distribution unit side.
  • Each logical cell distribution unit side on the DU device side corresponds to a gNB-DU, and different logical cells corresponding to the same physical cell correspond to different gNB-DUs.
  • One CU device includes one or more gNB-CUs, and each gNB-CU belongs to a different operator, and is uniquely identified and distinguished by a gNB global ID (Global gNB ID).
  • the multiple physical cells corresponding to each DU device correspond to SSB (Cell Defining SSB, CD-SSB) defined by different cells on the carrier of the DU device, and each DU device corresponds to multiple physical cells. Each physical cell shares the entire bandwidth resource of the carrier of the DU device.
  • each gNB-DU corresponds to one gNB-CU
  • one gNB-CU corresponds to one or more gNB-DUs
  • the gNB-DU and gNB-CU correspond to each other according to the gNB global identity.
  • the base station centralized unit, base station distribution unit, and logical cells corresponding to the same operator form a wireless logical network.
  • Figure 2 includes four operators. Among them, PLMN A, PLMN B, and PLMN C in the Public Land Mobile Network (Public Land Mobile Network Identification, PLMN ID) belong to the first operator, and PLMN D, PLMN E, and PLMN F belong to the first operator. The second operator, PLMN G and PLMN H belong to the third operator, and PLMN M belongs to the fourth operator.
  • the two CU devices include two gNB-CUs respectively.
  • the CU device 21 includes gNB-CU A (gNB ID-A) and gNB-CU D (gNB ID-D), and the CU device 22 includes gNB-CU G( gNB ID-G) and gNB-CU M (gNB ID-M), gNB-CU A corresponds to the three PLMN ID networks of the first operator, and gNB-CU D corresponds to the three PLMN ID networks of the second operator
  • gNB-CU G corresponds to two PLMN ID network locks of the third operator
  • gNB-CU M corresponds to one PLMN ID network lock of the first operator.
  • the DU device 23 includes three gNB-DUs, namely gNB-DU A1 (gNB ID-A), gNB-DU D1 (gNB ID-D), and gNB-DU G1 (gNB ID-G).
  • the carrier Carrier1 of the DU device 23 includes 5 SSBs SS1-SSB5, SSB1 corresponds to the physical cell PhysicalCell1, SSB3 corresponds to the physical cell PhysicalCell3, and SSB5 corresponds to the physical cell PhysicalCell5.
  • the physical cell PhysicalCell1 includes logical cell 1 and logical cell 2.
  • Logical cell 1 is the logical cell corresponding to the first operator, that is, the PLMN ID is PLMN A, PLMN B, PLMN C, and logical cell 1 has the following identifiers (gNBID-A +CellID1, TAC-A1, RANAC-A1).
  • Logical cell 2 is the logical cell corresponding to the second operator, that is, the PLMN ID is PLMN D, PLMN E, PLMN F, and logical cell 2 has the following identifiers (gNBID-D+CellID2, TAC-D1, RANAC-D1).
  • the physical cell PhysicalCell3 includes the logical cell 3 and the logical cell 4.
  • the logical cell 3 is the logical cell corresponding to the first operator, that is, the PLMN ID is PLMN A, PLMN B, PLMN C, and the logical cell 3 has the following identification (gNBID-A+ CellID3, TAC-A1, RANAC-A1).
  • the logical cell 4 is the logical cell corresponding to the second operator, that is, the PLMN ID is PLMN D, PLMN E, PLMN F, and the logical cell 4 has the following identifiers (gNBID-D+CellID4, TAC-D1, RANAC-D1).
  • the physical cell PhysicalCell5 includes the logical cell 5 and the logical cell 6.
  • the logical cell 5 is the logical cell corresponding to the second operator, that is, the PLMN ID is PLMN D, PLMN E, PLMN F, and the logical cell 4 has the following identification (gNBID-D+ CellID5, TAC-D1, RANAC-D1).
  • the logical cell 6 is the logical cell corresponding to the third operator, that is, the PLMN ID is PLMN G, PLMN H, and the logical cell 6 has the following identifiers (gNBID-G+CellID6, TAC-G1, RANAC-G1).
  • the DU device 24 includes three gNB-DUs, namely gNB-DU D2 (gNB ID-D), gNB-DU G2 (gNB ID-G), and gNB-DU M1 (gNB ID-M).
  • the carrier Carrier2 of the DU device 24 includes 5 SSBs SS1-SSB5, SSB1 corresponds to the physical cell PhysicalCell1, SSB3 corresponds to the physical cell PhysicalCell3, and SSB5 corresponds to the physical cell PhysicalCell5.
  • the physical cell PhysicalCell1 includes the logical cell 7 and the logical cell 8.
  • the logical cell 7 is the logical cell corresponding to the second operator, that is, the PLMN ID is PLMN D, PLMN E, PLMN F, and the logical cell 7 has the following identification (gNBID-D +CellID1, TAC-D2, RANAC-D2).
  • the logical cell 8 is the logical cell corresponding to the third operator, that is, the PLMN ID is PLMN G, PLMN H, and the logical cell 8 has the following identifiers (gNBID-G+CellID2, TAC-G2, RANAC-G2).
  • the physical cell PhysicalCell3 includes the logical cell 9 and the logical cell 10.
  • the logical cell 9 is the logical cell corresponding to the second operator, that is, the PLMN ID is PLMN D, PLMN E, PLMN F, and the logical cell 7 has the following identification (gNBID-D+ CellID3, TAC-D2, RANAC-D2).
  • the logical cell 10 is a logical cell corresponding to the third operator, that is, the PLMN ID is PLMN G, PLMN H, and the logical cell 10 has the following identifiers (gNBID-G+CellID4, TAC-G2, RANAC-G2).
  • the physical cell PhysicalCell5 includes the logical cell 11 and the logical cell 12.
  • the logical cell 11 is the logical cell corresponding to the third operator, that is, the PLMN ID is PLMN G, PLMN H, and the logical cell 11 has the following identification (gNBID-G+CellID5, TAC -G2, RANAC-G2).
  • the logical cell 12 is a logical cell corresponding to the fourth operator, that is, the PLMN ID is PLMN M, and the logical cell 12 has the following identifiers (gNBID-M+CellID12, TAC-M1, RANAC-M1).
  • an embodiment of the application provides a cell management model, as shown in FIG. 3
  • FIG. 3 This is a schematic structural diagram of the cell management model provided by the embodiments of this application.
  • the cell management model includes a network management unit 31, a centralized management network element 32, and a distributed management network element 33.
  • the network management unit 31 is set to pass through the The centralized management network element 32 and the distributed management network element 33 manage the wireless logical network
  • the centralized management network element 32 is configured to manage the wireless logical network through a base station centralized unit
  • the distributed management network element 33 is configured to manage the wireless logical network through the base station distribution unit.
  • the cell management model shown in Figure 3 is used to manage the three-tier cell architecture shown in Figure 2, which solves the complexity of air interface resources in the 5G Multi-SSB+ network sharing scenario.
  • the complex situation of base station system implementation and 5G cell management caused by the non-one-to-one single relationship.
  • the implementation and configuration of cell management are clear and clear, and the network in related technologies is improved.
  • Configuration management situations such as configuration consistency conflicts and configuration conflicts caused by repeated configurations of the physical source of the air interface in the Network Resource Model (NRM) protocol.
  • NAM Network Resource Model
  • the cell management model proposed in this application is simple to implement and easy to operate, and is suitable for other systems with similar situations.
  • FIG 4 is a schematic diagram of the management of the cell management model provided by an embodiment of the application.
  • the management network element objects are independently generated for different devices, and the management network element objects are the root node objects of the 5G cell management model.
  • the DU device manages the carrier, physical cell, logical cell, and logical base station DU side (gNB-DU), and the CU device only manages the logical cell and logical base station CU side ( gNB-CU).
  • the device When the DU side and the CU side of the base station are deployed in one device, the device manages the carrier, the physical cell, the logical cell DU side, the logical base station DU side, the logical cell CU side, and the logical base station CU side.
  • the centralized management network element in the cell management model manages the wireless logical network through the logical base station CU side
  • the distributed management network element in the cell management model manages the wireless logical network through the logical base station DU side.
  • Figure 4 does not show centralized management network elements and distributed management network elements.
  • the carrier and physical cells are extracted from independent management objects-carrier management objects and physical cell management objects, and together with BWP management objects and carrier fan management objects, they are used as 5G air interface wireless basic resources and aggregated in 5G NR air interface wireless basic resources Under the management object.
  • the distributed unit side of the logical cell (logical cell DU side) as an independent management object—the logical cell distribution unit side management object (DU logical cell management object), and the DU side of the logical base station (gNB-DU) as an independent management object— -Base station distributed unit management object (gNB-DU management object), and DU logical cell management objects of the same operator are aggregated under the operator's gNB-DU management object.
  • One DU logical cell management object can only correspond to one physical cell management object, and different DU logical cell management objects correspond to different physical cell management objects; one physical cell management object can correspond to one or more DU logical cell management objects.
  • One physical cell management object can correspond to one or more carrier management objects, and one carrier management object can correspond to one or more physical cell management objects; one physical cell management object can correspond to one or more BWP management objects, and one BWP management object can Correspond to one or more physical cell management objects.
  • One carrier management object can correspond to one or more carrier management objects, and one carrier management object can only correspond to one carrier management object.
  • the management network element manages the carrier fan management objects through the carrier fan device.
  • the centralized unit side of the logical cell (logical cell CU side) as an independent management object—the logical cell centralized unit side management object (CU logical cell management object), and the CU side of the logical base station (gNB-CU) as an independent management object— -Base station centralized unit management object (gNB-CU management object), and CU logical cell management objects of the same operator are aggregated under the operator's gNB-CU management object.
  • the CU logical cell and the DU logical cell have a one-to-one correspondence according to the NR Cell Global Identifier (NCGI).
  • Figure 5 is a schematic diagram of the correspondence and reference relationship of each management object based on the cell management model shown in Figure 4, in which the DU logical cell management object refers to the physical cell management object; the physical cell management object refers to the carrier management object and the BWP management object; The carrier management object refers to the carrier management object.
  • the centralized management network element in the cell management model is set to manage the management object on the centralized unit side of the logical cell through the centralized unit management object of the base station, and the management object on the centralized unit side of the logical cell corresponding to the wireless logical network Aggregated under the management object of the base station centralized unit corresponding to the wireless logical network.
  • the network management manages the community through centralized management of network elements and distributed management of network elements.
  • the centralized management network element corresponds to the gNB-CU
  • the distributed management network element corresponds to the gNB-DU.
  • the centralized management network element and the distributed management network element are two independent management network elements.
  • the centralized management network element and the distributed management network element become an integrated management network element.
  • the network manager manages the gNB-CU and the management objects corresponding to the gNB-CU through the centralized management of network elements.
  • the network manager manages the gNB-DU and the management objects corresponding to the gNB-DU through distributed management network elements.
  • the network manager manages the management objects on the logical cell centralized unit side (CU logical cell) through the gNB-CU management object, and the logical cell centralized unit side management objects corresponding to a wireless logical network are aggregated in the gNB-CU management object corresponding to the wireless logical network.
  • CU logical cell logical cell
  • the network manager manages the management objects on the logical cell centralized unit side (CU logical cell) through the gNB-CU management object, and the logical cell centralized unit side management objects corresponding to a wireless logical network are aggregated in the gNB-CU management object corresponding to the wireless logical network.
  • the distributed management network element in the cell management model is set to manage the logical cell distribution unit side management object through the base station distribution unit management object, and the logical cell distribution unit side management object corresponding to the wireless logical network Aggregate under the management object of the base station distribution unit corresponding to the wireless logical network to manage the air interface wireless basic resource management objects corresponding to the wireless logical network.
  • the air interface wireless basic resource management objects include carrier management objects and physical cell management objects , Part of bandwidth management objects, load fan management objects.
  • the network manager manages the management objects on the logical cell distribution unit side (DU logical cell) through the gNB-DU management object.
  • the logical cell centralized unit side management objects corresponding to a wireless logical network are aggregated under the gNB-CU management object corresponding to the wireless logical network. That is, for an operator, there is only one corresponding gNB-CU, and the logical cell centralized unit sides of the same operator are aggregated and managed by the corresponding gNB-DU of the operator.
  • the network manager manages the management objects on the logical cell distribution unit side through the base station distribution unit management objects, and the logical cell distribution unit side management objects refer to the physical cell management objects, where one logical cell distribution unit side management object corresponds to a physical Cell management objects, different logical cell distribution unit side management objects correspond to different physical cell management objects, and one physical cell management object corresponds to one or more logical cell distribution unit management objects.
  • Various air interface wireless basic resources in the wireless logical network are also managed by the network manager through the gNB-DU management object.
  • basic radio resources include carrier, physical cell, partial bandwidth, and carrier sector.
  • Various air interface wireless basic resource management objects in the wireless logical network are aggregated to become air interface wireless basic resource management objects.
  • the network manager manages physical cell management objects through air interface wireless basic resource management objects.
  • the physical cell management objects refer to carrier management objects and part of bandwidth management objects.
  • One physical cell management object corresponds to one or more carrier management objects.
  • a carrier management object forms one or more physical cell management objects
  • a physical cell management object corresponds to one or more partial bandwidth management objects
  • a partial bandwidth management object corresponds to one or more physical cell management objects; wireless via air interface
  • the basic resource management object manages the carrier management object
  • the carrier management object refers to the carrier management object.
  • one carrier management object corresponds to one or more carrier management objects
  • one carrier management object corresponds to one carrier management object.
  • the logical cell distributed unit side management object and the logical cell centralized unit side management object of a logical cell correspond one-to-one according to the global identity of the cell.
  • the embodiment of the present application also provides a cell management method for managing a three-layer network architecture composed of carriers, physical cells, and logical cells; wherein, one carrier of a distributed unit device corresponds to multiple physical cells, and each physical cell is Cells correspond to different logical cells according to different operators.
  • the distribution unit side of each logical cell corresponds to one base station distribution unit of one distribution unit device, and different logical cell distribution unit sides of the same physical cell correspond to different base station distribution units.
  • each logical cell corresponds to a base station centralized unit of the centralized unit equipment
  • each base station distribution unit corresponds to a base station centralized unit
  • a base station centralized unit corresponds to one or more base station distribution units, corresponding to the same operator
  • the base station centralized unit, the base station distribution unit, and the logical cells form a wireless logical network;
  • the cell management method includes: the base station centralized unit and the base station distribution unit manage the wireless logical network through the base station centralized unit and the base station distribution The unit manages the wireless logical network.
  • a distribution unit device can have at least one carrier, and the carrier number is unique within a distribution unit device.
  • a distributed centralized unit device and a centralized unit device respectively correspond to a management network element; when CU equipment and DU equipment are deployed in one, a distributed centralized unit device and a centralized unit device jointly correspond to one management Network element.
  • One management network element takes one device as the granularity.
  • Fig. 6 is a flowchart of a cell management method provided in an embodiment. As shown in Fig. 6, the method provided in this embodiment includes the following steps:
  • Step S6010 Manage the logical cell centralized unit side management objects through the base station centralized unit management object, and the logical cell centralized unit side management objects corresponding to the wireless logical network are aggregated under the base station centralized unit management objects corresponding to the wireless logical network.
  • Step S6020 Manage the logical cell distribution unit side management objects through the base station distribution unit management object, and the logical cell distribution unit side management objects corresponding to the wireless logical network are aggregated under the base station distribution unit management objects corresponding to the wireless logical network.
  • Step S6030 Manage the air interface wireless basic resource management objects corresponding to the wireless logical network through the base station distribution unit management object.
  • the air interface wireless basic resource management objects include carrier management objects, physical cell management objects, partial bandwidth management objects, and carrier fan management objects.
  • step S6020 includes: managing the logical cell distribution unit side management object through the base station distribution unit management object, and the logical cell distribution unit side management object refers to the physical cell management object, where One logical cell distribution unit side management object corresponds to one physical cell management object, different logical cell distribution unit side management objects correspond to different physical cell management objects, and one physical cell management object corresponds to one or more logical cell distribution unit management objects.
  • step S6030 includes: managing a physical cell management object through the air interface wireless basic resource management object, and the physical cell management object references the carrier management object and part of the bandwidth management object, where: One physical cell management object corresponds to one or more carrier management objects, one carrier management object forms one or more physical cell management objects, one physical cell management object corresponds to one or more partial bandwidth management objects, and one partial bandwidth management object corresponds to One or more physical cell management objects; the carrier management objects are managed through the air interface wireless basic resource management objects, the carrier management objects refer to the carrier sector management objects, wherein one carrier management object corresponds to one or more carrier sector management objects, One carrier management object corresponds to one carrier management object.
  • the management objects on the logical cell distribution unit side of a logical cell and the management objects on the logical cell centralized unit side correspond one-to-one according to the global identity of the cell.
  • the distributed unit device and the centralized unit device are deployed on the same device.
  • FIG. 7 is a schematic diagram of a cell management model provided in the first embodiment
  • FIG. 8 is a schematic diagram of a cell management configuration provided in the first embodiment.
  • the CU equipment and the DU equipment are deployed separately, the carrier and the physical cell, and the physical cell and the logical cell are in a one-to-one relationship, that is, each physical cell corresponds to a carrier, and each physical cell corresponds to a logical cell. Corresponding to the cell.
  • the logical base station CU side (GNBCUCPFunction) and the logical base station DU side (GNBDUFunction) belong to different management network elements (management network element 1 and management network element 2).
  • GNBCUCPFunction[1] There is only one logical base station CU side (GNBCUCPFunction[1]) under the management network element 1, and there may be multiple logical cell CU sides (NRCellCU) under the logical base station CU side (GNBCUCPFunction[1]).
  • GNBDUFunction[1] There is only one logical base station DU side (GNBDUFunction[1]) under the management network element 2, and there can be multiple logical cell DU sides (NRCellDU) under the logical base station DU side (GNBDUFunction[1]), and it is connected to the logical base station CU side (GNBCUCPFunction). [1]) The logical cell CU side under the one-to-one correspondence.
  • the management network element 2 may have multiple sector equipment (SectorEquipmentFunction).
  • NRCellDU references one NRPhysicalCellDU
  • one NRPhysicalCellDU is referenced by only one NRCellDU
  • There is a one-to-one relationship between physical cells and carriers (NRPhysicalCellDU references one NRCarrier, and one NRCarrier is only referenced by one NRPhysicalCellDU).
  • One carrier can correspond to multiple carrier sectors, but one carrier sector can only correspond to one carrier (NRCarrier can reference one or more NRSectorCarriers, and one NRSectorCarrier can only be referenced by one NRCarrier).
  • One carrier fan corresponds to only one carrier fan device, and one carrier fan device can correspond to multiple carrier fans (NRSectorCarrier references one SectorEquipmentFunction, and one SectorEquipmentFunction can be referenced by multiple NRSectorCarriers).
  • FIG. 9 is a schematic diagram of a cell management model provided in the second embodiment
  • FIG. 10 is a schematic diagram of a cell management configuration provided in the second embodiment.
  • the CU equipment and the DU equipment are deployed separately, and the relationship between the carrier and the physical cell and the logical cell is one-to-one, that is, each physical cell corresponds to one carrier, and each physical cell corresponds to two logical cells. correspond.
  • the logical base station CU side (GNBCUCPFunction) and the logical base station DU side (GNBDUFunction) belong to different management network elements (management network element 1 and management network element 2). There are two logical base station CU sides (GNBCUCPFunction[1] and GNBCUCPFunction[2]) under the management network element 1, and each logical base station CU side (GNBCUCPFunction) can have multiple logical cell CU sides (NRCellCU);
  • each logical base station DU side can have multiple logical cell DU sides (NRCellDU), which are connected to the logical base station.
  • the logical cell CU side under the CU side (GNBCUCPFunction) has a one-to-one correspondence.
  • the management network element 2 can have multiple sector equipment (SectorEquipmentFunction).
  • the logical cell and the physical cell have a two-to-one relationship (NRCellDU under GNBDUFunction[1] refers to NRPhysicalCellDU[1], and NRCellDU under GNBDUFunction[2] also refers to NRPhysicalCellDU[1]).
  • NRCellDU under GNBDUFunction[2] also refers to NRPhysicalCellDU[1]).
  • There is a one-to-one relationship between physical cells and carriers (NRPhysicalCellDU references one NRCarrier, and one NRCarrier is only referenced by one NRPhysicalCellDU).
  • One carrier can correspond to multiple carrier sectors, but one carrier sector can only correspond to one carrier (NRCarrier can reference one or more NRSectorCarriers, and one NRSectorCarrier can only be referenced by one NRCarrier); one carrier sector corresponds to only one carrier sector device, and one The carrier device can correspond to multiple carriers (NRSectorCarrier references one SectorEquipmentFunction, and one SectorEquipmentFunction can be referenced by multiple NRSectorCarriers).
  • FIG. 11 is a schematic diagram of a cell management model provided in the third embodiment
  • FIG. 12 is a schematic diagram of a cell management configuration provided in the third embodiment.
  • the CU equipment and the DU equipment are deployed separately, the carrier and the physical cell are in a one-to-two relationship, and the physical cell and the logical cell are in a one-to-two relationship, that is, each carrier corresponds to two physical cells, and each carrier corresponds to two physical cells.
  • One physical cell corresponds to two logical cells.
  • the logical base station CU side (GNBCUCPFunction) and the logical base station DU side (GNBDUFunction) belong to different management network elements (management network element 1 and management network element 2). There are two logical base station CU sides (GNBCUCPFunction[1] and GNBCUCPFunction[2]) under the management network element 1, and each logical base station CU side (GNBCUCPFunction) can have multiple logical cell CU sides (NRCellCU);
  • each logical base station DU side can have multiple logical cell DU sides (NRCellDU), which are connected to the logical base station.
  • the logical cell CU side under the CU side (GNBCUCPFunction) has a one-to-one correspondence.
  • the management network element 2 can have multiple sector equipment (SectorEquipmentFunction).
  • NRCellDU[1] under GNBDUFunction[1] refers to NRPhysicalCellDU[1]
  • NRCellDU[1] under GNBDUFunction[2] also refers to NRPhysicalCellDU[1]
  • NRCellDU[2] refers to NRPhysicalCellDU[2]
  • NRCellDU[2] under GNBDUFunction[2] also refers to NRPhysicalCellDU[2]
  • the relationship between physical cell and carrier is two-to-one (NRPhysicalCellDU[1] and NRPhysicalCellDU[2] are both Refer to the same NRCarrier[1]).
  • One carrier can correspond to multiple carrier sectors, but one carrier sector can only correspond to one carrier (NRCarrier can reference one or more NRSectorCarriers, and one NRSectorCarrier can only be referenced by one NRCarrier); one carrier sector corresponds to only one carrier sector device, and one The carrier device can correspond to multiple carriers (NRSectorCarrier references one SectorEquipmentFunction, and one SectorEquipmentFunction can be referenced by multiple NRSectorCarriers).
  • FIG. 13 is a schematic diagram of a cell management model provided in the fourth embodiment
  • FIG. 14 is a schematic diagram of a cell management configuration provided in the fourth embodiment.
  • the CU device and the DU device are deployed in one, the carrier and the physical cell are in a one-to-one relationship, and the physical cell and the logical cell are in a one-to-one relationship, that is, each physical cell corresponds to a carrier, and each physical cell corresponds to a carrier.
  • One physical cell corresponds to one logical cell.
  • the logical base station CU side (GNBCUCPFunction) and the logical base station DU side (GNBDUFunction) belong to the same management network element; there is only one logical base station CU side (GNBCUCPFunction[1]) under the management network element, and the logical base station CU side (GNBCUCPFunction[1] ) May have multiple logical cell CU sides (NRCellCU).
  • GNBDUFunction[1] There is only one logical base station DU side (GNBDUFunction[1]) under the management network element, and the logical base station DU side (GNBDUFunction[1]) can have multiple logical cell DU sides (NRCellDU), and it is connected to the logical base station CU side (GNBCUCPFunction[ 1]) The logical cell CU side under one-to-one correspondence.
  • NRRadioInfrastructure[1] There is only one 5G NR air interface radio basic resource (NRRadioInfrastructure[1]) under the management network element, and there can be multiple physical cells (NRPhysicalCellDU), multiple BWP (BWP), multiple carriers (NRCarrier), and multiple carrier sectors ( NRSectorCarrier); There can be multiple sector equipment (SectorEquipmentFunction) under the management network element.
  • NRCellDU refers to one NRPhysicalCellDU
  • one NRPhysicalCellDU is referred to by only one NRCellDU
  • physical cell and carrier are in one-to-one relationship
  • NRPhysicalCellDU refers to one NRCarrier
  • one NRCarrier is referred to by only one NRPhysicalCellDU
  • One carrier can correspond to multiple carrier sectors, but one carrier sector can only correspond to one carrier (NRCarrier can reference one or more NRSectorCarriers, and one NRSectorCarrier can only be referenced by one NRCarrier); one carrier sector corresponds to only one carrier sector device, and one The carrier device can correspond to multiple carriers (NRSectorCarrier references one SectorEquipmentFunction, and one SectorEquipmentFunction can be referenced by multiple NRSectorCarriers).
  • FIG. 15 is a schematic diagram of a cell management model provided in the fifth embodiment
  • FIG. 16 is a schematic diagram of a cell management configuration provided in the fifth embodiment.
  • the CU device and the DU device are deployed in one, the carrier and the physical cell are in a one-to-one relationship, and the physical cell and the logical cell are in a one-to-two relationship, that is, each physical cell corresponds to a carrier, and each physical cell corresponds to a carrier.
  • One physical cell corresponds to two logical cells.
  • the logical base station CU side (GNBCUCPFunction) and the logical base station DU side (GNBDUFunction) belong to the same management network element; there are two logical base station CU sides (GNBCUCPFunction[1] and GNBCUCPFunction[2]) under the management network element, and each logical base station CU There may be multiple logical cell CU sides (NRCellCU) under the side (GNBCUCPFunction).
  • each logical base station DU side can have multiple logical cell DU sides (NRCellDU), which are connected to the logical base station CU
  • NRCellDU logical cell DU sides
  • the logical cell CU side under the side has a one-to-one correspondence.
  • NRRadioInfrastructure[1] There is only one 5G NR air interface radio basic resource (NRRadioInfrastructure[1]) under the management network element, and there can be multiple physical cells (NRPhysicalCellDU), multiple BWP (BWP), multiple carriers (NRCarrier), and multiple carrier sectors ( NRSectorCarrier); There can be multiple sector equipment (SectorEquipmentFunction) under the management network element.
  • NRCellDU under GNBDUFunction[1] refers to NRPhysicalCellDU[1]
  • NRCellDU under GNBDUFunction[2] also refers to NRPhysicalCellDU[1]
  • physical cell and carrier have a one-to-one relationship (NRPhysicalCellDU references one NRCarrier, and one NRCarrier is only referenced by one NRPhysicalCellDU).
  • One carrier can correspond to multiple carrier sectors, but one carrier sector can only correspond to one carrier (NRCarrier can reference one or more NRSectorCarriers, and one NRSectorCarrier can only be referenced by one NRCarrier); one carrier sector corresponds to only one carrier sector device, and one The carrier device can correspond to multiple carriers (NRSectorCarrier references one SectorEquipmentFunction, and one SectorEquipmentFunction can be referenced by multiple NRSectorCarriers).
  • FIG. 17 is a schematic diagram of a cell management model provided in the sixth embodiment
  • FIG. 18 is a schematic diagram of a cell management configuration provided in the sixth embodiment.
  • the CU device and the DU device are deployed in one, the carrier and the physical cell are in a one-to-two relationship, and the physical cell and the logical cell are in a one-to-two relationship, that is, each carrier corresponds to two physical cells.
  • Each physical cell corresponds to two logical cells.
  • the logical base station CU side (GNBCUCPFunction) and the logical base station DU side (GNBDUFunction) belong to different management network elements; there are two logical base station CU sides (GNBCUCPFunction[1] and GNBCUCPFunction[2]) under the management network element, and each logical base station CU There may be multiple logical cell CU sides (NRCellCU) under the side (GNBCUCPFunction).
  • each logical base station DU side can have multiple logical cell DU sides (NRCellDU), which are connected to the logical base station CU
  • NRCellDU logical cell DU sides
  • the logical cell CU side under the side has a one-to-one correspondence.
  • NRRadioInfrastructure[1] There is only one 5G NR air interface radio basic resource (NRRadioInfrastructure[1]) under the management network element, and there can be multiple physical cells (NRPhysicalCellDU), multiple BWP (BWP), multiple carriers (NRCarrier), and multiple carrier sectors ( NRSectorCarrier); There can be multiple sector equipment (SectorEquipmentFunction) under the management network element.
  • NRCellDU[1] under GNBDUFunction[1] refers to NRPhysicalCellDU[1]
  • NRCellDU[1] under GNBDUFunction[2] also refers to NRPhysicalCellDU[1]
  • NRCellDU[2] refers to NRPhysicalCellDU[2]
  • NRCellDU[2] under GNBDUFunction[2] also refers to NRPhysicalCellDU[2]
  • the relationship between physical cell and carrier is two-to-one (NRPhysicalCellDU[1] and NRPhysicalCellDU[2] are both Refer to the same NRCarrier[1]).
  • One carrier can correspond to multiple carrier sectors, but one carrier sector can only correspond to one carrier (NRCarrier can reference one or more NRSectorCarriers, and one NRSectorCarrier can only be referenced by one NRCarrier); one carrier sector corresponds to only one carrier sector device, and one The carrier device can correspond to multiple carriers (NRSectorCarrier references one SectorEquipmentFunction, and one SectorEquipmentFunction can be referenced by multiple NRSectorCarriers).
  • Embodiment 1 to Embodiment 6 that the cell management model and cell management counter provided by the embodiments of the present application are applicable to cells of any architecture, so that the implementation and configuration of cell management are clear.
  • user terminal encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser, or a vehicle-mounted mobile station.
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the application is not limited thereto.
  • the embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions can be assembly instructions, (Instruction Set Architecture, ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or any combination of one or more programming languages Source code or object code written.
  • ISA Instruction Set Architecture
  • the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disc (CD), etc..
  • Computer-readable media can include non-transitory storage media.
  • the data processor can be any suitable for the local technical environment.
  • Types such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs), programmable logic devices (Field-Programmable Gate Array) , FGPA) and processors based on multi-core processor architecture.
  • DSP Digital Signal Processing
  • ASICs application specific integrated circuits
  • FGPA programmable logic devices
  • processors based on multi-core processor architecture.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提出一种小区管理模型和小区管理方法，一种小区管理模型应用于由载波、物理小区和逻辑小区组成的三层网络架构；小区管理模型包括网管单元、集中管理网元和分布管理网元，网管单元设置为通过集中管理网元和分布管理网元对无线逻辑网络进行管理，集中管理网元设置为通过基站集中单元对无线逻辑网络进行管理，分布管理网元设置为通过基站分布单元对无线逻辑网络进行管理。

Description

小区管理模型和小区管理方法 技术领域
本申请涉及通信技术，例如涉及一种小区管理模型和小区管理方法。
背景技术
第五代移动通信(5th Generation，5G)空口技术中，将基站，即新无线节点B(gNB)分为集中单元(Centralized Unit，CU)和分布单元(Distrbuted Unit，DU)两部分。其中基站集中单元(gNB-CU)主要包括非实时的无线高层协议栈功能，处理小区和用户设备(User Equipment，UE)高层相关的功能；基站分布单元(gNB-DU)主要处理小区和UE物理层功能和对实时性要求较高的层2协议栈功能。gNB-CU部署在CU设备上，gNB-DU部署在DU设备上，gNB-CU和gNB-DU也可以合一部署在一个设备上。
相关移动通信技术中，一段载波资源只会对应一个小区，一个小区也只会有一个小区标识、一个跟踪区域码(Tracking Area Code，TAC)、一个无线通知区域码(RAN-based Notification Area Code，RAC)。而5G空口技术中，引入了多同步/物理广播信道块(Multiple Synchronization Signal/PBCH Block，Multi-SSB)和新的网络共享概念，载波和小区间、小区与小区标识间、小区与TAC间、小区与RAC间的关系发生了巨大变化。对于Multi-SSB场景，一个载波上可以有多个小区，对于网络共享场景，一个小区可以有多个小区标识(cellIdentity，由gNB标识(gNB ID)和小区标识(Cell ID)组成)、TAC、RAC。
综上两种场景，相关技术中的小区管理模型已无法满足管理需求，亟待提供一种对新的小区进行管理的方法。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请提供一种小区管理模型和小区管理方法，使小区管理的实现和配置都清晰明了，改善了空口资源配置重复带来的一致性和配置冲突的配置管理情况。
第一方面，本申请实施例提供一种小区管理模型，应用于由载波、物理小区和逻辑小区组成的三层网络架构；
其中，一个分布单元设备的一个载波对应多个物理小区，每个物理小区根据不同运营商对应不同逻辑小区，每个逻辑小区的分布单元侧与一个所述分布单元设备的一个基站分布单元对应，同一物理小区的不同逻辑小区分布单元侧分别对应不同的基站分布单元，每个逻辑小区的集中单元侧与集中单元设备的一个基站集中单元对应，每个基站分布单元与一个基站集中单元对应，一个基站集中单元与一个或多个基站分布单元对应，同一运营商对应的基站集中单元、基站分布单元、逻辑小区组成一个无线逻辑网络；
所述小区管理模型包括网管单元、集中管理网元和分布管理网元，所述网管单元设置为通过所述集中管理网元和所述分布管理网元对所述无线逻辑网络进行管理，所述集中管理网元设置为通过基站集中单元对所述无线逻辑网络进行管理，所述分布管理网元设置为通过基站分布单元对所述无线逻辑网络进行管理。
第二方面，本申请实施例提供一种小区管理方法，用于对由载波、物理小区和逻辑小区组成的三层网络架构进行管理；
其中，一个分布单元设备的一个载波对应多个物理小区，每个物理小区根据不同运营商对应不同逻辑小区，每个逻辑小区的分布单元侧与一个所述分布单元设备的一个基站分布单元对应，同一物理小区的不同逻辑小区分布单元侧分别对应不同的基站分布单元，每个逻辑小区的集中单元侧与集中单元设备的一个基站集中单元对应，每个基站分布单元与一个基站集中单元对应，一个基站集中单元与一个或多个基站分布单元对应，同一运营商对应的基站集中单元、基站分布单元、逻辑小区组成一个无线逻辑网络；
所述小区管理方法包括：通过基站集中单元和所述基站分布单元对所述无线逻辑网络进行管理。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
图1为Multi-SSB场景下的载波示意图；
图2为本申请实施例提供的三层小区管理架构的结构示意图；
图3为本申请实施例提供的小区管理模型的结构示意图；
图4为本申请实施例提供的小区管理模型的管理示意图；
图5为基于图4所示的小区管理模型的各管理对象的对应和引用关系示意图；
图6为一实施例提供的一种小区管理方法的流程图；
图7为实施例一提供的小区管理模型示意图；
图8为实施例一提供的小区管理配置示意图；
图9为实施例二提供的小区管理模型示意图；
图10为实施例二提供的小区管理配置示意图；
图11为实施例三提供的小区管理模型示意图；
图12为实施例三提供的小区管理配置示意图；
图13为实施例四提供的小区管理模型示意图；
图14为实施例四提供的小区管理配置示意图；
图15为实施例五提供的小区管理模型示意图；
图16为实施例五提供的小区管理配置示意图；
图17为实施例六提供的小区管理模型示意图；
图18为实施例六提供的小区管理配置示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。
图1为Multi-SSB场景下的载波示意图，如图1所示，一个载波对应多个同步/物理广播信道块(Synchronization Signal/PBCH Block，SSB)，分别为SSB1、SSB2、SSB3和SSB4。其中SSB1的小区全局标识(NR Cell Global Identifier，NCGI)为5，SSB1的NCGI为6。UE1和UE2接入NCGI 5的小区，UE3接入NCGI 6的小区。UE1的初始(Initial)部分带宽(BandWidth Part，BWP)占用SSB1，专用(Dedicated)BWP1占用SSB1、SSB2和SSB3，专用BWP2占用SSB4。UE2的初始BWP占用SSB1，专用BWP1占用SSB1和SSB2。UE3的初始BWP占用SSB3，专用BWP1占用SSB1、SSB2和SSB3，专用BWP2占用SSB4。
从图1中可以看出，在Multi-SSB场景下，载波和小区间、小区与小区标识间的关系发生了变化。另外在网络共享场景下，一个小区可以有多个小区标识、TAC、RAC，小区与TAC间、小区与RAC间的关系也发生了巨大变化。因此 相关技术中的小区管理模型已无法满足小区管理需求。
针对上述情况，本申请实施例提供一种小区管理模型和小区管理方法，用于对存在上述情况的网络进行小区管理。本申请实施例提供的小区管理模型和小区管理方法基于5G小区进行说明，但本申请实施例提供的小区管理模型和小区管理方法不限于5G通信系统，对于其他存在上述情况的类似无线通信系统，也可以采用本申请实施例提供的小区管理模型和小区管理方法。
图2为本申请实施例提供的三层小区管理架构的结构示意图，如图2所示，本实施例提供的小区管理模型应用于由载波、物理小区和逻辑小区组成的三层网络架构。
根据5G协议中定义的Multi-SSB和网络共享场景，本实施例将相关技术中的小区分为三层：载波、物理小区和逻辑小区，并由逻辑小区延伸出逻辑基站和无线逻辑网络。其中，逻辑基站包括基站分布单元(gNB-DU)和基站集中单元(gNB-CU)，每个逻辑小区分为逻辑小区集中单元侧和逻辑小区分布单元侧。三层小区的对应关系，以及逻辑基站和无线逻辑网络的对应关系如图2所示。
一个集中单元(Distrbuted Unit，DU)设备上的一个载波资源(Carrier)对应一个或多个物理小区，图2中以两个DU设备，每个DU设备分别对应三个物理小区PhysicalCell1、PhysicalCell2、PhysicalCell3为例。每个物理小区按照不同的运营商分为不同的逻辑小区。每个逻辑小区分为逻辑小区集中单元侧和逻辑小区分布单元侧，DU设备侧的每个逻辑小区分布单元侧对应一个gNB-DU，对应同一物理小区的不同逻辑小区对应不同的gNB-DU。一个CU设备上包括一个或多个gNB-CU，每个gNB-CU属于不同运营商，以gNB全局标识(Global gNB ID)唯一标识和区分。在一种可能的实现方式中，每个DU设备对应的多个物理小区分别对应DU设备的载波上的不同小区定义的SSB(Cell Defining SSB，CD-SSB)，并且每个DU设备对应的多个物理小区共享DU设备的载波的整个带宽资源。
DU设备和CU设备之间，每个gNB-DU对应一个gNB-CU，一个gNB-CU对应一个或多个gNB-DU，gNB-DU和gNB-CU间根据gNB全局标识对应。同一运营商对应的基站集中单元、基站分布单元、逻辑小区组成一个无线逻辑网络。
图2中包括四个运营商，其中公共陆地移动网(Public Land Mobile Network Identification，PLMN ID)中的PLMN A、PLMN B、PLMN C属于第一运营商， PLMN D、PLMN E、PLMN F属于第二运营商，PLMN G、PLMN H属于第三运营商，PLMN M属于第四运营商。两个CU设备中分别包括两个gNB-CU，CU设备21中包括gNB-CU A(gNB ID-A)和gNB-CU D(gNB ID-D)，CU设备22中包括gNB-CU G(gNB ID-G)和gNB-CU M(gNB ID-M)，gNB-CU A与第一运营商的三个PLMN ID网络锁定对应，gNB-CU D与第二运营商的三个PLMN ID网络锁定对应，gNB-CU G与第三运营商的两个PLMN ID网络锁定对应，gNB-CU M与第一运营商的一个PLMN ID网络锁定对应。
DU设备23包括三个gNB-DU，分别为gNB-DU A1(gNB ID-A)、gNB-DU D1(gNB ID-D)、gNB-DU G1(gNB ID-G)。DU设备23的载波Carrier1包括SS1-SSB5共5个SSB，SSB1对应物理小区PhysicalCell1，SSB3对应物理小区PhysicalCell3，SSB5对应物理小区PhysicalCell5。物理小区PhysicalCell1包括逻辑小区1和逻辑小区2，其中逻辑小区1为第一运营商对应的逻辑小区，也就是PLMN ID为PLMN A、PLMN B、PLMN C，逻辑小区1具有如下标识(gNBID-A+CellID1，TAC-A1，RANAC-A1)。逻辑小区2为第二运营商对应的逻辑小区，也就是PLMN ID为PLMN D、PLMN E、PLMN F，逻辑小区2具有如下标识(gNBID-D+CellID2，TAC-D1，RANAC-D1)。
物理小区PhysicalCell3包括逻辑小区3和逻辑小区4，逻辑小区3为第一运营商对应的逻辑小区，也就是PLMN ID为PLMN A、PLMN B、PLMN C，逻辑小区3具有如下标识(gNBID-A+CellID3，TAC-A1，RANAC-A1)。逻辑小区4为第二运营商对应的逻辑小区，也就是PLMN ID为PLMN D、PLMN E、PLMN F，逻辑小区4具有如下标识(gNBID-D+CellID4，TAC-D1，RANAC-D1)。
物理小区PhysicalCell5包括逻辑小区5和逻辑小区6，逻辑小区5为第二运营商对应的逻辑小区，也就是PLMN ID为PLMN D、PLMN E、PLMN F，逻辑小区4具有如下标识(gNBID-D+CellID5，TAC-D1，RANAC-D1)。逻辑小区6为第三运营商对应的逻辑小区，也就是PLMN ID为PLMN G、PLMN H，逻辑小区6具有如下标识(gNBID-G+CellID6，TAC-G1，RANAC-G1)。
DU设备24包括三个gNB-DU，分别为gNB-DU D2(gNB ID-D)、gNB-DU G2(gNB ID-G)、gNB-DU M1(gNB ID-M)。DU设备24的载波Carrier2包括SS1-SSB5共5个SSB，SSB1对应物理小区PhysicalCell1，SSB3对应物理小区PhysicalCell3，SSB5对应物理小区PhysicalCell5。物理小区PhysicalCell1包括逻辑小区7和逻辑小区8，其中逻辑小区7为第二运营商对应的逻辑小区，也就 是PLMN ID为PLMN D、PLMN E、PLMN F，逻辑小区7具有如下标识(gNBID-D+CellID1，TAC-D2，RANAC-D2)。逻辑小区8为第三运营商对应的逻辑小区，也就是PLMN ID为PLMN G、PLMN H，逻辑小区8具有如下标识(gNBID-G+CellID2，TAC-G2，RANAC-G2)。
物理小区PhysicalCell3包括逻辑小区9和逻辑小区10，逻辑小区9为第二运营商对应的逻辑小区，也就是PLMN ID为PLMN D、PLMN E、PLMN F，逻辑小区7具有如下标识(gNBID-D+CellID3，TAC-D2，RANAC-D2)。逻辑小区10为第三运营商对应的逻辑小区，也就是PLMN ID为PLMN G、PLMN H，逻辑小区10具有如下标识(gNBID-G+CellID4，TAC-G2，RANAC-G2)。
物理小区PhysicalCell5包括逻辑小区11和逻辑小区12，逻辑小区11为第三运营商对应的逻辑小区，也就是PLMN ID为PLMN G、PLMN H，逻辑小区11具有如下标识(gNBID-G+CellID5，TAC-G2，RANAC-G2)。逻辑小区12为第四运营商对应的逻辑小区，也就是PLMN ID为PLMN M，逻辑小区12具有如下标识(gNBID-M+CellID12，TAC-M1，RANAC-M1)。
基于图2所示载波、物理小区、逻辑小区、逻辑基站(分为gNB-CU和gNB-DU)和无线逻辑网络的关系，以及部署位置，本申请实施例提供一种小区管理模型，图3为本申请实施例提供的小区管理模型的结构示意图，如图3所示，小区管理模型包括网管单元31、集中管理网元32和分布管理网元33，所述网管单元31设置为通过所述集中管理网元32和所述分布管理网元33对所述无线逻辑网络进行管理，所述集中管理网元32设置为通过基站集中单元对所述无线逻辑网络进行管理，所述分布管理网元33设置为通过基站分布单元对所述无线逻辑网络进行管理。
采用本申请实施例提供的小区管理模型，对基于图2所示的三层小区架构采用图3所示的小区管理模型进行管理，解决了5G Multi-SSB+网络共享场景下，空口资源之间复杂的非一对一的单一关系所带来的基站系统实现复杂、5G小区管理复杂的情况，通过合理的分层和抽象，使小区管理的实现和配置都清晰明了，并改善了相关技术中网络资源模型(Network Resource Model，NRM)协议中空口物理源相关配置重复所带来的配置一致性冲突和配置冲突等配置管理情况。本申请提出的小区管理模型实现简单易操作，且适用于存在类似情况的其它系统。
图4为本申请实施例提供的小区管理模型的管理示意图，如图4所示，首 先，按不同的设备独立出管理网元对象，管理网元对象为5G小区管理模型的根节点对象。当基站的DU侧和CU侧分开部署在不同设备上时，DU设备上管理载波、物理小区、逻辑小区、逻辑基站DU侧(gNB-DU)，CU设备只管理逻辑小区、逻辑基站CU侧(gNB-CU)。当基站的DU侧和CU侧合一部署在一个设备上时，该设备上管理载波、物理小区、逻辑小区DU侧、逻辑基站DU侧、逻辑小区CU侧、逻辑基站CU侧。小区管理模型中的集中管理网元通过逻辑基站CU侧对无线逻辑网络进行管理，小区管理模型中的分布管理网元通过逻辑基站DU侧对无线逻辑网络进行管理。图4中未示出集中管理网元和分布管理网元。
将载波和物理小区抽取出独立的管理对象——载波管理对象和物理小区管理对象，并和BWP管理对象、载扇管理对象一起作为5G的空口无线基础资源放在下聚合在5G NR空口无线基础资源管理对象下。逻辑小区的分布单元侧(逻辑小区DU侧)作为独立的管理对象——逻辑小区分布单元侧管理对象(DU逻辑小区管理对象)，逻辑基站的DU侧(gNB-DU)作为独立的管理对象——基站分布单元管理对象(gNB-DU管理对象)，并且同一运营商的DU逻辑小区管理对象聚合在该运营商的gNB-DU管理对象下。一个DU逻辑小区管理对象只能对应一个物理小区管理对象，不同的DU逻辑小区管理对象对应不同的物理小区管理对象；一个物理小区管理对象可以对应一个或多个DU逻辑小区管理对象。
一个物理小区管理对象可以对应一个或多个载波管理对象，一个载波管理对象可以对应一个或多个物理小区管理对象；一个物理小区管理对象可以对应一个或多个BWP管理对象，一个BWP管理对象可以对应一个或多个物理小区管理对象。
一个载波管理对象可以对应一个或多个载扇管理对象，一个载扇管理对象只能对应一个载波管理对象。管理网元通过载扇设备对载扇管理对象进行管理。
逻辑小区的集中单元侧(逻辑小区CU侧)作为独立的管理对象——逻辑小区集中单元侧管理对象(CU逻辑小区管理对象)，逻辑基站的CU侧(gNB-CU)作为独立的管理对象——基站集中单元管理对象(gNB-CU管理对象)，并且同一运营商的CU逻辑小区管理对象聚合在该运营商的gNB-CU管理对象下。CU逻辑小区与DU逻辑小区根据小区全局标识(NR Cell Global Identifier，NCGI)一一对应。
图5为基于图4所示的小区管理模型的各管理对象的对应和引用关系示意 图，其中由DU逻辑小区管理对象引用物理小区管理对象；由物理小区管理对象引用载波管理对象和BWP管理对象；由载波管理对象引用载扇管理对象。
在一实施例中，小区管理模型中的所述集中管理网元设置为通过基站集中单元管理对象对逻辑小区集中单元侧管理对象进行管理，所述无线逻辑网络对应的逻辑小区集中单元侧管理对象聚合在所述无线逻辑网络对应的基站集中单元管理对象下。
网管通过集中管理网元和分布管理网元进行小区管理。集中管理网元与gNB-CU对应，分布管理网元与gNB-DU对应。当DU设备和CU设备分离部署时，集中管理网元和分布管理网元为独立的两个管理网元。当DU设备和CU设备集中部署，那么集中管理网元和分布管理网元为一个集成的管理网元。网管通过集中管理网元对gNB-CU，以及gNB-CU对应的管理对象进行管理。网管通过分布管理网元对gNB-DU，以及gNB-DU对应的管理对象进行管理。其中，网管通过gNB-CU管理对象对逻辑小区集中单元侧(CU逻辑小区)管理对象进行管理，一个无线逻辑网络对应的逻辑小区集中单元侧管理对象聚合在无线逻辑网络对应的gNB-CU管理对象下，也就是对于一个运营商，仅有一个对应的gNB-CU，同一运营商的逻辑小区集中单元侧聚合在一起由该运营商对应的gNB-DU管理。
在一实施例中，小区管理模型中的所述分布管理网元设置为通过基站分布单元管理对象对逻辑小区分布单元侧管理对象进行管理，所述无线逻辑网络对应的逻辑小区分布单元侧管理对象聚合在所述无线逻辑网络对应的基站分布单元管理对象下，对所述无线逻辑网络对应的空口无线基础资源管理对象进行管理，所述空口无线基础资源管理对象包括载波管理对象、物理小区管理对象、部分带宽管理对象、载扇管理对象。
网管通过gNB-DU管理对象对逻辑小区分布单元侧(DU逻辑小区)管理对象进行管理，一个无线逻辑网络对应的逻辑小区集中单元侧管理对象聚合在无线逻辑网络对应的gNB-CU管理对象下，也就是对于一个运营商，仅有一个对应的gNB-CU，同一运营商的逻辑小区集中单元侧聚合在一起由该运营商对应的gNB-DU管理。
在一实施例中，网管通过基站分布单元管理对象对逻辑小区分布单元侧管理对象进行管理，逻辑小区分布单元侧管理对象引用物理小区管理对象，其中，一个逻辑小区分布单元侧管理对象对应一个物理小区管理对象，不同逻辑小区 分布单元侧管理对象对应不同物理小区管理对象，一个物理小区管理对象对应一个或多个逻辑小区分布单元管理对象。
无线逻辑网络中的各种空口无线基础资源也由网管通过gNB-DU管理对象进行管理。其中口无线基础资源包括载波、物理小区、部分带宽、载扇。无线逻辑网络中的各种空口无线基础资源管理对象聚合在一起成为空口无线基础资源管理对象。
在一实施例中，网管通过空口无线基础资源管理对象对物理小区管理对象进行管理，物理小区管理对象引用载波管理对象和部分带宽管理对象，其中，一个物理小区管理对象对应一个或多个载波管理对象，一个载波管理对象队形一个或多个物理小区管理对象，一个物理小区管理对象对应一个或多个部分带宽管理对象，一个部分带宽管理对象对应一个或多个物理小区管理对象；通过空口无线基础资源管理对象对载波管理对象进行管理，载波管理对象引用载扇管理对象，其中，一个载波管理对象对应一个或多个载扇管理对象，一个载扇管理对象对应一个载波管理对象。
为了确定一个逻辑小区中对应的分布单元侧和集中单元侧，一个逻辑小区的逻辑小区分布单元侧管理对象和逻辑小区集中单元侧管理对象根据小区全局标识一一对应。
本申请实施例还提供一种小区管理方法，用于对由载波、物理小区和逻辑小区组成的三层网络架构进行管理；其中，一个分布单元设备的一个载波对应多个物理小区，每个物理小区根据不同运营商对应不同逻辑小区，每个逻辑小区的分布单元侧与一个所述分布单元设备的一个基站分布单元对应，同一物理小区的不同逻辑小区分布单元侧分别对应不同的基站分布单元，每个逻辑小区的集中单元侧与集中单元设备的一个基站集中单元对应，每个基站分布单元与一个基站集中单元对应，一个基站集中单元与一个或多个基站分布单元对应，同一运营商对应的基站集中单元、基站分布单元、逻辑小区组成一个无线逻辑网络；所述小区管理方法包括：通过基站集中单元和所述基站分布单元对所述无线逻辑网络进行管理通过基站集中单元和所述基站分布单元对所述无线逻辑网络进行管理。
一个分布单元设备可以有至少一个载波，载波编号在一个分布单元设备内是唯一的。
CU设备和DU设备分离部署时，一个分布集中单元设备和一个集中单元设 备分别对应一个管理网元；CU设备和DU设备合一部署时，一个分布集中单元设备和一个集中单元设备共同对应一个管理网元。一个管理网元以一个设备为粒度。
图6为一实施例提供的一种小区管理方法的流程图，如图6所示，本实施例提供的方法包括如下步骤：
步骤S6010，通过基站集中单元管理对象对逻辑小区集中单元侧管理对象进行管理，无线逻辑网络对应的逻辑小区集中单元侧管理对象聚合在无线逻辑网络对应的基站集中单元管理对象下。
步骤S6020，通过基站分布单元管理对象对逻辑小区分布单元侧管理对象进行管理，无线逻辑网络对应的逻辑小区分布单元侧管理对象聚合在无线逻辑网络对应的基站分布单元管理对象下。
步骤S6030，通过基站分布单元管理对象对无线逻辑网络对应的空口无线基础资源管理对象进行管理，空口无线基础资源管理对象包括载波管理对象、物理小区管理对象、部分带宽管理对象、载扇管理对象。
在图6所示实施例的基础上，步骤S6020包括：通过所述基站分布单元管理对象对逻辑小区分布单元侧管理对象进行管理，所述逻辑小区分布单元侧管理对象引用物理小区管理对象，其中，一个逻辑小区分布单元侧管理对象对应一个物理小区管理对象，不同逻辑小区分布单元侧管理对象对应不同物理小区管理对象，一个物理小区管理对象对应一个或多个逻辑小区分布单元管理对象。
在图6所示实施例的基础上，步骤S6030包括：通过所述空口无线基础资源管理对象对物理小区管理对象进行管理，所述物理小区管理对象引用载波管理对象和部分带宽管理对象，其中，一个物理小区管理对象对应一个或多个载波管理对象，一个载波管理对象队形一个或多个物理小区管理对象，一个物理小区管理对象对应一个或多个部分带宽管理对象，一个部分带宽管理对象对应一个或多个物理小区管理对象；通过空口无线基础资源管理对象对载波管理对象进行管理，所述载波管理对象引用载扇管理对象，其中，一个载波管理对象对应一个或多个载扇管理对象，一个载扇管理对象对应一个载波管理对象。
在图6所示实施例的基础上，一个逻辑小区的逻辑小区分布单元侧管理对象和逻辑小区集中单元侧管理对象根据小区全局标识一一对应。
在图6所示实施例的基础上，所述分布单元设备和所述集中单元设备部署于同一设备上。
下面以几个不同部署场景为例，对本申请实施例提供的小区管理方法和小区管理模型进行详细说明。
图7为实施例一提供的小区管理模型示意图，图8为实施例一提供的小区管理配置示意图。
在实施例一中，CU设备和DU设备分离部署，载波与物理小区，物理小区与逻辑小区分别是一对一的关系，也即每个物理小区与一个载波对应，每个物理小区与一个逻辑小区对应。
逻辑基站CU侧(GNBCUCPFunction)和逻辑基站DU侧(GNBDUFunction)分属不同的管理网元(管理网元1和管理网元2)。
管理网元1下只有一个逻辑基站CU侧(GNBCUCPFunction[1])，该逻辑基站CU侧(GNBCUCPFunction[1])下可以有多个逻辑小区CU侧(NRCellCU)。
管理网元2下只有一个逻辑基站DU侧(GNBDUFunction[1])、该逻辑基站DU侧(GNBDUFunction[1])下可以有多个逻辑小区DU侧(NRCellDU)，且与逻辑基站CU侧(GNBCUCPFunction[1])下的逻辑小区CU侧一一对应。
管理网元2下只有一个5G NR空口无线基础资源(NRRadioInfrastructure[1])，其下可以有多个物理小区(NRPhysicalCellDU)、多个BWP(BWP)、多个载波(NRCarrier)、多个载扇(NRSectorCarrier)。管理网元2可以有多个载扇设备(SectorEquipmentFunction)。
逻辑小区与物理小区是一对一的关系(NRCellDU引用一个NRPhysicalCellDU，一个NRPhysicalCellDU只被一个NRCellDU引用)。物理小区与载波是一对一的关系(NRPhysicalCellDU引用一个NRCarrier、一个NRCarrier只被一个NRPhysicalCellDU引用)。一个载波可以与多个载扇对应、但一个载扇只能对应一个载波(NRCarrier可以引用一个或多个NRSectorCarrier，一个NRSectorCarrier只被一个NRCarrier引用)。一个载扇只与一个载扇设备对应、一个载扇设备可以对应多个载扇(NRSectorCarrier引用一个SectorEquipmentFunction，一个SectorEquipmentFunction可以被多个NRSectorCarrier引用)。
图9为实施例二提供的小区管理模型示意图，图10为实施例二提供的小区管理配置示意图。
在实施例二中，CU设备和DU设备分离部署，载波与物理小区与逻辑小区是1对1对2的关系，也即每个物理小区与一个载波对应，每个物理小区与两 个逻辑小区对应。
逻辑基站CU侧(GNBCUCPFunction)和逻辑基站DU侧(GNBDUFunction)分属不同的管理网元(管理网元1和管理网元2)。管理网元1下有两个逻辑基站CU侧(GNBCUCPFunction[1]和GNBCUCPFunction[2])，每个逻辑基站CU侧(GNBCUCPFunction)下可以有多个逻辑小区CU侧(NRCellCU)；
管理网元2下有两个逻辑基站DU侧(GNBDUFunction[1]和GNBDUFunction[2])、每个逻辑基站DU侧(GNBDUFunction)下可以有多个逻辑小区DU侧(NRCellDU)，且与逻辑基站CU侧(GNBCUCPFunction)下的逻辑小区CU侧一一对应。
管理网元2下只有一个5G NR空口无线基础资源(NRRadioInfrastructure[1])，其下可以有多个物理小区(NRPhysicalCellDU)、多个BWP(BWP)、多个载波(NRCarrier)、多个载扇(NRSectorCarrier)；管理网元2可以有多个载扇设备(SectorEquipmentFunction)。
逻辑小区与物理小区是二对一的关系(GNBDUFunction[1]下的NRCellDU引用NRPhysicalCellDU[1]，GNBDUFunction[2]下的NRCellDU也引用NRPhysicalCellDU[1])。物理小区与载波是一对一的关系(NRPhysicalCellDU引用一个NRCarrier、一个NRCarrier只被一个NRPhysicalCellDU引用)。
一个载波可以与多个载扇对应、但一个载扇只能对应一个载波(NRCarrier可以引用一个或多个NRSectorCarrier，一个NRSectorCarrier只被一个NRCarrier引用)；一个载扇只与一个载扇设备对应、一个载扇设备可以对应多个载扇(NRSectorCarrier引用一个SectorEquipmentFunction，一个SectorEquipmentFunction可以被多个NRSectorCarrier引用)。
图11为实施例三提供的小区管理模型示意图，图12为实施例三提供的小区管理配置示意图。
在实施例三中，CU设备和DU设备分离部署，载波与物理小区是一对二的关系，物理小区与逻辑小区是一对二的关系，也即每个载波与两个物理小区对应，每个物理小区与两个逻辑小区对应。
逻辑基站CU侧(GNBCUCPFunction)和逻辑基站DU侧(GNBDUFunction)分属不同的管理网元(管理网元1和管理网元2)。管理网元1下有两个逻辑基站CU侧(GNBCUCPFunction[1]和GNBCUCPFunction[2])，每个逻辑基站CU侧(GNBCUCPFunction)下可以有多个逻辑小区CU侧(NRCellCU)；
管理网元2下有两个逻辑基站DU侧(GNBDUFunction[1]和GNBDUFunction[2])、每个逻辑基站DU侧(GNBDUFunction)下可以有多个逻辑小区DU侧(NRCellDU)，且与逻辑基站CU侧(GNBCUCPFunction)下的逻辑小区CU侧一一对应。
管理网元2下只有一个5G NR空口无线基础资源(NRRadioInfrastructure[1])，其下可以有多个物理小区(NRPhysicalCellDU)、多个BWP(BWP)、多个载波(NRCarrier)、多个载扇(NRSectorCarrier)；管理网元2可以有多个载扇设备(SectorEquipmentFunction)。
逻辑小区与物理小区是二对一的关系(GNBDUFunction[1]下的NRCellDU[1]引用NRPhysicalCellDU[1]，GNBDUFunction[2]下的NRCellDU[1]也引用NRPhysicalCellDU[1]；GNBDUFunction[1]下的NRCellDU[2]引用NRPhysicalCellDU[2]，GNBDUFunction[2]下的NRCellDU[2]也引用NRPhysicalCellDU[2])；物理小区与载波是二对一的关系(NRPhysicalCellDU[1]和NRPhysicalCellDU[2]都引用同一个NRCarrier[1])。
一个载波可以与多个载扇对应、但一个载扇只能对应一个载波(NRCarrier可以引用一个或多个NRSectorCarrier，一个NRSectorCarrier只被一个NRCarrier引用)；一个载扇只与一个载扇设备对应、一个载扇设备可以对应多个载扇(NRSectorCarrier引用一个SectorEquipmentFunction，一个SectorEquipmentFunction可以被多个NRSectorCarrier引用)。
图13为实施例四提供的小区管理模型示意图，图14为实施例四提供的小区管理配置示意图。
在实施例四中，CU设备和DU设备合一部署，载波与物理小区是一对一的关系，物理小区与逻辑小区是一对一的关系，也即每个物理小区与一个载波对应，每个物理小区与一个逻辑小区对应。
逻辑基站CU侧(GNBCUCPFunction)和逻辑基站DU侧(GNBDUFunction)属于同一个的管理网元；管理网元下只有一个逻辑基站CU侧(GNBCUCPFunction[1])，该逻辑基站CU侧(GNBCUCPFunction[1])下可以有多个逻辑小区CU侧(NRCellCU)。
管理网元下只有一个逻辑基站DU侧(GNBDUFunction[1])、该逻辑基站DU侧(GNBDUFunction[1])下可以有多个逻辑小区DU侧(NRCellDU)，且与逻辑基站CU侧(GNBCUCPFunction[1])下的逻辑小区CU侧一一对应。
管理网元下只有一个5G NR空口无线基础资源(NRRadioInfrastructure[1])，其下可以有多个物理小区(NRPhysicalCellDU)、多个BWP(BWP)、多个载波(NRCarrier)、多个载扇(NRSectorCarrier)；管理网元下可以有多个载扇设备(SectorEquipmentFunction)。
逻辑小区与物理小区是一对一的关系(NRCellDU引用一个NRPhysicalCellDU，一个NRPhysicalCellDU只被一个NRCellDU引用)；物理小区与载波是一对一的关系(NRPhysicalCellDU引用一个NRCarrier、一个NRCarrier只被一个NRPhysicalCellDU引用)。
一个载波可以与多个载扇对应、但一个载扇只能对应一个载波(NRCarrier可以引用一个或多个NRSectorCarrier，一个NRSectorCarrier只被一个NRCarrier引用)；一个载扇只与一个载扇设备对应、一个载扇设备可以对应多个载扇(NRSectorCarrier引用一个SectorEquipmentFunction，一个SectorEquipmentFunction可以被多个NRSectorCarrier引用)。
图15为实施例五提供的小区管理模型示意图，图16为实施例五提供的小区管理配置示意图。
在实施例五中，CU设备和DU设备合一部署，载波与物理小区是一对一的关系，物理小区与逻辑小区是一对二的关系，也即每个物理小区与一个载波对应，每个物理小区与两个逻辑小区对应。
逻辑基站CU侧(GNBCUCPFunction)和逻辑基站DU侧(GNBDUFunction)属于相同的管理网元；管理网元下有两个逻辑基站CU侧(GNBCUCPFunction[1]和GNBCUCPFunction[2])，每个逻辑基站CU侧(GNBCUCPFunction)下可以有多个逻辑小区CU侧(NRCellCU)。
管理网元下有两个逻辑基站DU侧(GNBDUFunction[1]和GNBDUFunction[2])、每个逻辑基站DU侧(GNBDUFunction)下可以有多个逻辑小区DU侧(NRCellDU)，且与逻辑基站CU侧(GNBCUCPFunction)下的逻辑小区CU侧一一对应。
管理网元下只有一个5G NR空口无线基础资源(NRRadioInfrastructure[1])，其下可以有多个物理小区(NRPhysicalCellDU)、多个BWP(BWP)、多个载波(NRCarrier)、多个载扇(NRSectorCarrier)；管理网元下可以有多个载扇设备(SectorEquipmentFunction)。
逻辑小区与物理小区是二对一的关系(GNBDUFunction[1]下的NRCellDU 引用NRPhysicalCellDU[1]，GNBDUFunction[2]下的NRCellDU也引用NRPhysicalCellDU[1])；物理小区与载波是一对一的关系(NRPhysicalCellDU引用一个NRCarrier、一个NRCarrier只被一个NRPhysicalCellDU引用)。
一个载波可以与多个载扇对应、但一个载扇只能对应一个载波(NRCarrier可以引用一个或多个NRSectorCarrier，一个NRSectorCarrier只被一个NRCarrier引用)；一个载扇只与一个载扇设备对应、一个载扇设备可以对应多个载扇(NRSectorCarrier引用一个SectorEquipmentFunction，一个SectorEquipmentFunction可以被多个NRSectorCarrier引用)。
图17为实施例六提供的小区管理模型示意图，图18为实施例六提供的小区管理配置示意图。
在实施例六中，CU设备和DU设备合一部署，载波与物理小区是一对二的关系，物理小区与逻辑小区是一对二的关系，也即每个载波与两个物理小区对应，每个物理小区与两个逻辑小区对应。
逻辑基站CU侧(GNBCUCPFunction)和逻辑基站DU侧(GNBDUFunction)属于不同的管理网元；管理网元下有两个逻辑基站CU侧(GNBCUCPFunction[1]和GNBCUCPFunction[2])，每个逻辑基站CU侧(GNBCUCPFunction)下可以有多个逻辑小区CU侧(NRCellCU)。
管理网元下有两个逻辑基站DU侧(GNBDUFunction[1]和GNBDUFunction[2])、每个逻辑基站DU侧(GNBDUFunction)下可以有多个逻辑小区DU侧(NRCellDU)，且与逻辑基站CU侧(GNBCUCPFunction)下的逻辑小区CU侧一一对应。
管理网元下只有一个5G NR空口无线基础资源(NRRadioInfrastructure[1])，其下可以有多个物理小区(NRPhysicalCellDU)、多个BWP(BWP)、多个载波(NRCarrier)、多个载扇(NRSectorCarrier)；管理网元下可以有多个载扇设备(SectorEquipmentFunction)。
逻辑小区与物理小区是二对一的关系(GNBDUFunction[1]下的NRCellDU[1]引用NRPhysicalCellDU[1]，GNBDUFunction[2]下的NRCellDU[1]也引用NRPhysicalCellDU[1]；GNBDUFunction[1]下的NRCellDU[2]引用NRPhysicalCellDU[2]，GNBDUFunction[2]下的NRCellDU[2]也引用NRPhysicalCellDU[2])；物理小区与载波是二对一的关系(NRPhysicalCellDU[1]和NRPhysicalCellDU[2]都引用同一个NRCarrier[1])。
一个载波可以与多个载扇对应、但一个载扇只能对应一个载波(NRCarrier可以引用一个或多个NRSectorCarrier，一个NRSectorCarrier只被一个NRCarrier引用)；一个载扇只与一个载扇设备对应、一个载扇设备可以对应多个载扇(NRSectorCarrier引用一个SectorEquipmentFunction，一个SectorEquipmentFunction可以被多个NRSectorCarrier引用)。
从上述实施例一至实施例六可以看出，本申请实施例提供的小区管理模型和小区管理反方，适用于任一种架构的小区，使得小区管理的实现和配置都清晰明了。
以上仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构((Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disc，CD)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FGPA)以及基于多核处理器架构的处 理器。

Claims (13)

  1. 一种小区管理模型，应用于由至少一个载波、多个物理小区和多个逻辑小区组成的三层网络架构；
    其中，一个分布单元设备的一个载波对应多个物理小区，每个物理小区根据不同运营商对应不同逻辑小区，每个逻辑小区的分布单元侧与一个所述分布单元设备的一个基站分布单元对应，同一物理小区的不同逻辑小区分布单元侧分别对应不同的基站分布单元，每个逻辑小区的集中单元侧与集中单元设备的一个基站集中单元对应，每个基站分布单元与一个基站集中单元对应，一个基站集中单元与至少一个基站分布单元对应，同一运营商对应的基站集中单元、基站分布单元、逻辑小区组成一个无线逻辑网络；
    所述小区管理模型包括网管单元、集中管理网元和分布管理网元，所述网管单元设置为通过所述集中管理网元和所述分布管理网元对所述无线逻辑网络进行管理，所述集中管理网元设置为通过基站集中单元对所述无线逻辑网络进行管理，所述分布管理网元设置为通过基站分布单元对所述无线逻辑网络进行管理。
  2. 根据权利要求1所述的小区管理模型，其中，一个载波对应的多个物理小区对应所述一个载波上的不同的小区定义的同步/物理广播信道块CD-SSB，所述一个载波对应的多个物理小区共享所述一个载波的整个带宽资源。
  3. 根据权利要求2所述的小区管理模型，其中，所述集中管理网元设置为通过基站集中单元管理对象对逻辑小区集中单元侧管理对象进行管理，所述无线逻辑网络对应的逻辑小区集中单元侧管理对象聚合在所述无线逻辑网络对应的基站集中单元管理对象下；
    所述分布管理网元设置为通过基站分布单元管理对象对逻辑小区分布单元侧管理对象和所述无线逻辑网络对应的空口无线基础资源管理对象进行管理，所述无线逻辑网络对应的逻辑小区分布单元侧管理对象聚合在所述无线逻辑网络对应的基站分布单元管理对象下，所述空口无线基础资源管理对象包括载波管理对象、物理小区管理对象、部分带宽管理对象、载扇管理对象。
  4. 根据权利要求3所述的小区管理模型，其中，所述分布管理网元，设置为通过所述基站分布单元管理对象对逻辑小区分布单元侧管理对象进行管理，所述逻辑小区分布单元侧管理对象引用物理小区管理对象，其中，一个逻辑小区分布单元侧管理对象对应一个物理小区管理对象，不同逻辑小区分布单元侧 管理对象对应不同物理小区管理对象，一个物理小区管理对象对应至少一个逻辑小区分布单元管理对象。
  5. 根据权利要求3所述的小区管理模型，其中，所述分布管理网元，设置为通过所述空口无线基础资源管理对象对物理小区管理对象进行管理，所述物理小区管理对象引用载波管理对象和部分带宽管理对象，其中，一个物理小区管理对象对应至少一个载波管理对象，一个载波管理对象对应至少一个物理小区管理对象，一个物理小区管理对象对应至少一个部分带宽管理对象，一个部分带宽管理对象对应至少一个物理小区管理对象；通过空口无线基础资源管理对象对载波管理对象进行管理，所述载波管理对象引用载扇管理对象，其中，一个载波管理对象对应至少一个载扇管理对象，一个载扇管理对象对应一个载波管理对象。
  6. 根据权利要求3-5任一项所述的小区管理模型，其中，一个逻辑小区的逻辑小区分布单元侧管理对象和逻辑小区集中单元侧管理对象根据小区全局标识一一对应。
  7. 根据权利要求3-5任一项所述的小区管理模型，其中，所述分布单元设备和所述集中单元设备部署于同一设备上。
  8. 一种小区管理方法，用于对由载波、物理小区和逻辑小区组成的三层网络架构进行管理；
    其中，一个载波对应多个物理小区，每个物理小区根据不同运营商对应不同逻辑小区，每个逻辑小区的分布单元侧与一个基站分布单元对应，同一物理小区的不同逻辑小区分布单元侧分别对应不同的基站分布单元，每个逻辑小区的集中单元侧与一个基站集中单元对应，每个基站分布单元与一个基站集中单元对应，一个基站集中单元与至少一个基站分布单元对应，同一运营商对应的基站集中单元、基站分布单元、逻辑小区组成一个无线逻辑网络，一个分布单元设备包括多个基站分布单元，一个集中单元设备包括多个基站集中单元；
    所述小区管理方法包括：通过基站集中单元和所述基站分布单元对所述无线逻辑网络进行管理。
  9. 根据权利要求8所述的方法，其中，所述通过基站集中单元和所述基站分布单元对所述无线逻辑网络进行管理，包括：
    通过基站集中单元管理对象对逻辑小区集中单元侧管理对象进行管理，所述无线逻辑网络对应的逻辑小区集中单元侧管理对象聚合在所述无线逻辑网络 对应的基站集中单元管理对象下；
    通过基站分布单元管理对象对逻辑小区分布单元侧管理对象进行管理，所述无线逻辑网络对应的逻辑小区分布单元侧管理对象聚合在所述无线逻辑网络对应的基站分布单元管理对象下；
    通过基站分布单元管理对象对所述无线逻辑网络对应的空口无线基础资源管理对象进行管理，所述空口无线基础资源管理对象包括载波管理对象、物理小区管理对象、部分带宽管理对象、载扇管理对象。
  10. 根据权利要求9所述的方法，其中，所述通过基站分布单元管理对象对逻辑小区分布单元侧管理对象进行管理，包括：
    通过所述基站分布单元管理对象对逻辑小区分布单元侧管理对象进行管理，所述逻辑小区分布单元侧管理对象引用物理小区管理对象，其中，一个逻辑小区分布单元侧管理对象对应一个物理小区管理对象，不同逻辑小区分布单元侧管理对象对应不同物理小区管理对象，一个物理小区管理对象对应至少一个逻辑小区分布单元管理对象。
  11. 根据权利要求9所述的方法，其中，所述对所述无线逻辑网络对应的空口无线基础资源管理对象进行管理，包括：
    通过所述空口无线基础资源管理对象对物理小区管理对象进行管理，所述物理小区管理对象引用载波管理对象和部分带宽管理对象，其中，一个物理小区管理对象对应至少一个载波管理对象，一个载波管理对象对应至少一个物理小区管理对象，一个物理小区管理对象对应至少一个部分带宽管理对象，一个部分带宽管理对象对应至少一个物理小区管理对象；通过空口无线基础资源管理对象对载波管理对象进行管理，所述载波管理对象引用载扇管理对象，其中，一个载波管理对象对应至少一个载扇管理对象，一个载扇管理对象对应一个载波管理对象。
  12. 根据权利要求9-11任一项所述的方法，其中，一个逻辑小区的逻辑小区分布单元侧管理对象和逻辑小区集中单元侧管理对象根据小区全局标识一一对应。
  13. 根据权利要求9-11任一项所述的方法，其中，所述分布单元设备和所述集中单元设备部署于同一设备上。
PCT/CN2021/094755 2020-06-10 2021-05-20 小区管理模型和小区管理方法 WO2021249146A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010525345.4A CN113556749B (zh) 2020-06-10 2020-06-10 小区管理模型和小区管理方法
CN202010525345.4 2020-06-10

Publications (1)

Publication Number Publication Date
WO2021249146A1 true WO2021249146A1 (zh) 2021-12-16

Family

ID=78101594

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/094755 WO2021249146A1 (zh) 2020-06-10 2021-05-20 小区管理模型和小区管理方法

Country Status (2)

Country Link
CN (1) CN113556749B (zh)
WO (1) WO2021249146A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116321461A (zh) * 2021-12-08 2023-06-23 中兴通讯股份有限公司 基站资源调度方法、通信设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296391A (zh) * 2007-04-29 2008-10-29 中兴通讯股份有限公司 网元设备控制方法及系统
US20190215726A1 (en) * 2018-01-11 2019-07-11 Comcast Cable Communications, Llc Cell Configuration For Packet Duplication
CN110460456A (zh) * 2018-05-08 2019-11-15 大唐移动通信设备有限公司 一种管理信息库mib同步生成网络拓扑的方法及装置
CN111181745A (zh) * 2018-11-09 2020-05-19 中国移动通信有限公司研究院 一种集中化单元功能实体、基站和网络管理方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010099832A1 (en) * 2009-03-06 2010-09-10 Telefonaktiebolaget Lm Ericsson (Publ) Managing network elements
CN109756906A (zh) * 2017-11-03 2019-05-14 中兴通讯股份有限公司 一种网元管理方法和装置
CN110958623B (zh) * 2018-09-27 2023-05-09 华为技术有限公司 一种小区的配置方法和装置
EP3857357A4 (en) * 2018-09-28 2022-04-27 Nokia Technologies OY IDENTIFICATION OF INSTITUTIONS OF MANAGED OBJECTS FOR OBJECT MANAGEMENT

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296391A (zh) * 2007-04-29 2008-10-29 中兴通讯股份有限公司 网元设备控制方法及系统
US20190215726A1 (en) * 2018-01-11 2019-07-11 Comcast Cable Communications, Llc Cell Configuration For Packet Duplication
CN110460456A (zh) * 2018-05-08 2019-11-15 大唐移动通信设备有限公司 一种管理信息库mib同步生成网络拓扑的方法及装置
CN111181745A (zh) * 2018-11-09 2020-05-19 中国移动通信有限公司研究院 一种集中化单元功能实体、基站和网络管理方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Add NRPhysicalCellDU and NRCarrier NRM to support Multi-SSB and network", SHARING 3GPP TSG-SA5 MEETING #129E S5-201199, 14 February 2020 (2020-02-14), XP051855805 *

Also Published As

Publication number Publication date
CN113556749A (zh) 2021-10-26
CN113556749B (zh) 2022-09-13

Similar Documents

Publication Publication Date Title
US11228947B2 (en) Network slice deployment method and related device
CN108322937B (zh) 无线接入网中用于网络切片的资源分配方法和编排器
CN110012437B (zh) 一种组播报文的发送方法、装置及系统
CN108566289B (zh) 基于5g移动通信网络切片架构设计管理方法
WO2016161677A1 (zh) 一种业务卸载方法及系统
US20230041039A1 (en) Method, device, and system for deploying network slice
US11088924B2 (en) Network management method, device, and system
US20190166001A1 (en) Network function nf management method and nf management device
WO2019105057A1 (zh) 一种网络优化方法及装置
WO2021062740A1 (zh) 一种确定设备信息的方法、装置以及系统
CN107104824A (zh) 一种网络拓扑确定方法和装置
WO2021249146A1 (zh) 小区管理模型和小区管理方法
WO2023103506A1 (zh) 用于设备的内存管理方法、内存管理设备和计算系统
WO2019085999A1 (zh) 网元管理方法和装置
TWI744611B (zh) 接取控制資訊的傳輸方法、裝置及網路側設備
CN112805679B (zh) 用于对象管理的被管理对象实例标识
Mharsi et al. Scalable and cost-efficient algorithms for baseband unit (BBU) function split placement
TWI693839B (zh) 一種確定ｒｒｍ測量配置的方法及設備
CN114630359B (zh) 确定网络覆盖的方法、装置、电子设备、计算机存储介质
WO2016086686A1 (zh) 基带资源管理方法和装置
CN113630792B (zh) 一种流量负载均衡广度优先搜索优化方法、系统、设备
WO2017128625A1 (zh) 业务配置方法及装置、管理网元
WO2022135373A1 (zh) 一种网络资源的请求方法及其相关设备
WO2024032328A1 (zh) 配置信息处理方法及装置
WO2021259279A1 (zh) 配置网元数据的方法和装置、电子设备，及计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21821125

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21821125

Country of ref document: EP

Kind code of ref document: A1