[go: up one dir, main page]

WO2019085999A1 - Procédé et appareil de gestion d'élément de réseau - Google Patents

Procédé et appareil de gestion d'élément de réseau Download PDF

Info

Publication number
WO2019085999A1
WO2019085999A1 PCT/CN2018/113707 CN2018113707W WO2019085999A1 WO 2019085999 A1 WO2019085999 A1 WO 2019085999A1 CN 2018113707 W CN2018113707 W CN 2018113707W WO 2019085999 A1 WO2019085999 A1 WO 2019085999A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
item
identifier
object instance
management
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/113707
Other languages
English (en)
Chinese (zh)
Inventor
祝伟宏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2019085999A1 publication Critical patent/WO2019085999A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/22—Traffic simulation tools or models
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • the present disclosure relates to the field of wireless communication systems, for example, to a network element management method and apparatus.
  • the interface between the Network Management System (NMS) and the Element Management System (EMS) is called the northbound interface (Itf-N).
  • EMS mainly completes the Element Management Layer (EML) function in the International Telecommunication Union (ITU) Telecommunications Management Network (TMN), that is, completes the management functions of one or more mobile communication devices.
  • ITU International Telecommunication Union
  • Telecommunications Management Network Telecommunications Management Network
  • EMS between different device vendors cannot be universal.
  • the NMS mainly performs the Network Management Layer (NML) function in the ITU TMN and is responsible for the management of all network elements in a managed network.
  • NML Network Management Layer
  • the entire subnet can be managed through EMS management of multiple device vendors.
  • OSS operation support system
  • BSS business support system
  • NMS network management system
  • 5G fifth generation mobile communication technology
  • a functionalized network resource consisting of an instantiated complete logical network with specific network characteristics, which is used to meet the needs of a particular type of network service. Examples of network characteristics here are ultra-low latency or super high Reliability, etc.
  • the network slice is obtained by instantiating according to the network slice blueprint, so it is also called the network slice instance.
  • the network slice blueprint refers to a complete definition for describing the structure, configuration, and workflow of the network slice instance.
  • the Network Slicing Management Function (NSMF) completes the instantiation of the network slice according to the definition of the network slice blueprint. Control management of the life cycle of network slicing.
  • a sub-slice refers to a logical network composed of a group of network functions and network resources supporting the network functions, having specific network characteristics.
  • a network slice can include zero, one, or multiple sub-slices.
  • the management and orchestration of sub-slices is done by the Network Slice Subnet Management Function (NSSMF).
  • NSSMF Network Slice Subnet Management Function
  • VNF Virtualized Network Function
  • a 5G base station generation Node B, gNB
  • CU central unit
  • DU distributed unit
  • gNB 5G base station
  • the function of gNB can also be partially implemented by virtualization technology, that is, CU can be implemented by VNF, and DU is still implemented by physical network function (PNF).
  • PNF physical network function
  • the present disclosure proposes a network element management method and apparatus, which can solve the problem that the base station management lacks a corresponding solution under the CU/DU separation technology.
  • the present disclosure proposes a network element management method, the method comprising:
  • the present disclosure also provides a network element management apparatus, the apparatus comprising:
  • a model establishing unit configured to set, in the management information, at least one management object instance corresponding to the network resource model corresponding to the at least one CU of the base station and at least one management object instance corresponding to the network resource model corresponding to the at least one DU;
  • a management unit configured to manage at least one CU in the base station according to the at least one management object instance corresponding to the at least one CU; and, according to the at least one management object instance corresponding to the at least one DU, to at least one DU in the base station Manage.
  • FIG. 1 is a flowchart of a network element management method according to an embodiment
  • FIG. 2 is a schematic diagram of inheritance relationship between information object classes GNbCuFunction and GNbDuFunction provided by an embodiment
  • FIG. 3 is a schematic diagram of a relationship between an information object class GNbCuFunction and a GNbDuFunction according to an embodiment
  • FIG. 4 is a schematic diagram of relationship between an information object class GNbCuFunction and a GNbDuFunction according to another embodiment
  • FIG. 5 is a schematic diagram of relationship between an information object class GNbCuFunction and a GNbDuFunction according to another embodiment
  • FIG. 6 is a schematic structural diagram of a network element management apparatus according to an embodiment.
  • FIG. 1 is a flowchart of a network element management method according to an embodiment. Referring to FIG. 1, the method provided in this embodiment includes the following steps.
  • Step 110 Set at least one management object instance corresponding to the network resource model corresponding to the at least one CU of the base station and at least one management object instance corresponding to the network resource model corresponding to the at least one DU in the management information.
  • Step 120 Manage at least one CU in the base station according to the at least one management object instance corresponding to the at least one CU, and manage at least one DU in the base station according to at least one management object instance corresponding to the at least one DU.
  • the base station comprises at least one CU, the base station comprising at least one DU.
  • the at least one management object instance of the network resource model corresponding to the at least one CU of the base station and the at least one management object instance of the network resource model corresponding to the at least one DU are respectively configured to: set the at least one CU An attribute of each CU, the attribute of each CU includes a private attribute of each of the CUs; setting an attribute of each of the at least one DU, the attributes of each of the DUs including each The private property of the DU.
  • the attribute of each CU further includes a common attribute of each CU
  • the attribute of each DU further includes a common attribute of each DU.
  • the network resource model (NRM) corresponding to the CU of the gNB and the NRM corresponding to the DU are added to the management information of the management system (at least one of the NMS, the EMS, the NSMF, and the NSSMF), that is, respectively Establish the following Information Object Class (IOC): (1), GNbCuFunction: used to represent the CU part of a gNB; (2), GNbDuFunction: used to represent the DU part of a gNB; here a gNB can include at least one DU.
  • IOC Information Object Class
  • the private attribute of each CU includes a CU identifier (CuId) item for indicating an identifier of each CU itself; and the private attribute of each DU includes a DU identifier (DuId) Item for indicating the identity of each of the DUs themselves.
  • CuId CU identifier
  • DuId DU identifier
  • the information object class GNbCuFunction is configured to include an attribute identifier ((Identify, Id) or CuId, which is used to represent the identifier of each CU itself; and the information object class GNbDuFunction established above includes attributes. Id or DuId is used to indicate the identity of each of the DUs themselves.
  • the private attribute of each CU further includes a DU identifier list dUIDList for storing an identifier of the DU corresponding to each CU.
  • the private attribute of the DU further includes a CU identifier list (cUIDList) for storing an identifier of the CU corresponding to each DU.
  • cUIDList CU identifier list
  • the information object class GNbCuFunction is configured to include an attribute DU identifier list (dUIDList) for storing an identifier (ID) of a DU that belongs to the same gNB as each CU.
  • dUIDList attribute DU identifier list
  • ID identifier
  • the information object class GNbDuFunction is configured to include an attribute CU identifier (cUID) or a CU identifier list (cUIDList) for storing an ID of a CU that belongs to the same aNB as each DU.
  • cUID attribute CU identifier
  • cUIDList CU identifier list
  • the common attribute corresponding to the base station is set to a network resource model ManagedFunction, that is, an information object class ManagedFunction; the public attribute of the CU is set to an information object class GNbCuFunction; and the public attribute of the DU is set to an information object class. GNbDuFunction.
  • the above information object class has at least one of the following relationships: the information object classes GNbCuFunction and GNbDuFunction are both inherited from the information object class ManagedFunction; the information object classes GNbCuFunction and GNbDuFunction are both included in the information object class ManagedElement.
  • the method further includes setting a correspondence between each CU and a base station by setting a CuId item of each CU.
  • a CuId item of the CU corresponding to the base station is set to include a base station identifier (gNBId) of the base station; and the gNBId item is an identifier of the base station itself (for example, including a base station corresponding to Corresponding relationship between each DU and at least one CU is set by setting a DuId item of each DU; wherein, for each DU corresponding to the CU, the DU corresponding to each CU a CuId term is set to include a CuId item of each CU; or, a correspondence relationship between each DU and a base station is set by setting a CuId item of each DU; wherein, for a DU corresponding to the base station, the base station corresponds to The CuId term of the DU is set to include
  • the attribute of each CU is a Managed Object Instance (MOI) of each CU
  • the attribute of each DU is an MOI of each DU.
  • MOI Managed Object Instance
  • a gNB including both a CU and a DU when a gNB including both a CU and a DU is to be managed, it can be implemented by the following operations.
  • Step 10 Generate a management object instance of the CU of the gNB, such as GNbCuFunction001.
  • Step 20 Generate a management object instance of the DU of the gNB, such as GNbDuFunction001 and GNbDuFunction002.
  • Step 30 The dUIDList in the instance of the GNbCuFunction saves an identifier (ID) of the GNbDuFunction corresponding to the instance of the GNbCuFunction; and the instance of the GNbDuFunction directly associates with the GNbCuFunction instance through the inclusion relationship, or the CU identifier included by the GNbDuFunction ( The cUID) or CU identification list (cUIDList) is used to hold the ID of the instance of the GNbCuFunction corresponding to the GNbDuFunction instance to establish a correspondence with the GNbCuFunction instance.
  • ID identifier
  • cUID cUID
  • CU identification list cUIDList
  • the instance of the GNbDuFunction directly associates with the GNbCuFunction instance by the inclusion relationship, and when the relationship between the IOC GNbCuFunction and the GNbDuFunction is defined, the GNbCuFunction name is defined as (Names contain) GNbDuFunction.
  • step 10 there is no specified sequence between step 10 and step 10.
  • the management system when the management system is to perform a management operation on a gNB, first find the GNbCuFunction instance corresponding to the gNB by using the identifier of the GNbCuFunction (Id or CU-Id), and then find the dUIDList in the GNbCuFunction instance.
  • Id the identifier of the GNbCuFunction
  • CU-Id the identifier of the GNbCuFunction
  • dUIDList dUIDList in the GNbCuFunction instance.
  • the gNB is managed through the GNbCuFunction instance and the GNbDuFunction instance.
  • the dUIDList list of the CU corresponding to the base station is modified according to the change of the changed DU.
  • the identifier of the added DU is added to the dUIDList list of the CU corresponding to the added DU according to the added DU; and the dUIDList list of the CU corresponding to the reduced DU according to the reduced DU.
  • the identifier of the reduced DU is reduced.
  • the related attributes (such as dUIDList) in the GNbCuFunction instance of the CU corresponding to the increased or decreased DU also need to be updated synchronously.
  • the related attributes (such as cUIDList) in the GNbDuFunction instance of the shared DU also need to be updated synchronously.
  • both GNbCuFunction and GNbDuFunction are subclasses of ManagedFunction (see 3GPP TS 28.622).
  • This embodiment provides a modeling method for a CU and a DU included in a gNB, where the CU and the DU are in a one-to-many relationship, and the setting includes the following contents:
  • NMS management information of the management system
  • EMS management system
  • NSSMF NSSMF
  • the information object class GNbCuFunction established above includes at least an attribute Id for indicating the identity of the GNbCuFunction itself.
  • the information object class GNbDuFunction established above includes an attribute Id for indicating the identity of the GNbDuFunction itself.
  • the information object class GNbCuFunction established above includes an attribute DU identifier list (dUIDList) for storing the ID of the DU belonging to the same gNB as the CU.
  • dUIDList attribute DU identifier list
  • the information object class GNbDuFunction established above includes an attribute CU identifier (cUID) for storing an ID of a CU belonging to the same gNB as the DU.
  • cUID CU identifier
  • the information object class ManagedFunction is an information object class corresponding to the base station, and the relationship between the GNbCuFunction and the GNbDuFunction and the ManagedFunction may be one of the following.
  • FIG. 2 is a schematic diagram of the inheritance relationship between the information object classes GNbCuFunction and GNbDuFunction provided by an embodiment. As shown in FIG. 2, the information object classes GNbCuFunction and GNbDuFunction are inherited from the information object class ManagedFunction.
  • FIG. 3 is a schematic diagram of relationship between information object classes GNbCuFunction and GNbDuFunction provided by an embodiment. As shown in FIG. 3, the information object classes GNbCuFunction and GNbDuFunction are both included in the information object class ManagedElement. In an embodiment, the management of the CU and the DU is set to a level relationship.
  • This embodiment provides a modeling method for a CU and a DU included in a gNB.
  • the CU and the DU are in a many-to-many relationship, and the modeling method is as follows.
  • the NRM corresponding to the CU of the gNB and the NRM corresponding to the DU are added, that is, the following IOCs are respectively established.
  • a gNB may include at least one DU.
  • the information object class GNbCuFunction established above includes at least an attribute Id for indicating the identity of the GNbCuFunction itself.
  • the information object class GNbDuFunction established above includes an attribute Id for indicating the identity of the GNbDuFunction itself.
  • the information object class GNbCuFunction established above includes an attribute DU identifier list (dUIDList) for storing the ID of the DU belonging to the same gNB as the CU.
  • dUIDList attribute DU identifier list
  • the information object class GNbDuFunction established above includes an attribute CU identifier list (cUIDList) for storing an ID of a CU belonging to the same gNB as the DU.
  • cUIDList attribute CU identifier list
  • This embodiment provides a modeling method for a CU and a DU included in a gNB, which is implemented by a name inclusion method, and the modeling method is as follows.
  • NMS management information of the management system
  • EMS management system
  • NSSMF NSSMF
  • the information object class GNbCuFunction established above includes at least an attribute Id for indicating the identity of the GNbCuFunction itself.
  • the information object class GNbCuFunction established above includes an attribute DU identifier list (dUIDList) for storing the ID of the DU belonging to the same gNB as the CU.
  • dUIDList attribute DU identifier list
  • the information object class GNbDuFunction established above includes an attribute Id for indicating the identity of the GNbDuFunction itself; where GNbDuFunction is the name contained in the GNbCuFunction.
  • FIG. 4 it is a schematic diagram of the relationship between the information object class GNbCuFunction and GNbDuFunction.
  • the GNbCuFunction includes a GNbDuFunction, and the CU and the DU are in a one-to-many relationship, that is, the Id of the GNbDuFunction instance includes the Id of the GNbCuFunction instance to which the GNbDuFunction instance belongs.
  • GNbCuFunction001 an instance of GNbCuFunction has an Id of GNbCuFunction001:
  • FIG. 5 is a schematic diagram of a relationship between a more managed object class GNbCuFunction and a GNbDuFunction according to another embodiment.
  • the GNbCuFunction includes a GNbDuFunction
  • the CU and the DU are in a many-to-many relationship.
  • This embodiment provides a method for managing a gNB that includes both a CU and a DU, and the operation is as follows:
  • GNbCuFunction001 holds the IDs of the corresponding GNbDuFunction instances GNbDuFunction001 and GNbDuFunction002.
  • the above 1) and 2) do not have a specified sequence.
  • This embodiment provides a method for managing a gNB that includes both a CU and a DU.
  • the CU and the DU are supported in a many-to-many relationship. The operations are as follows:
  • GNbCuFunction001 holds the IDs of the corresponding GNbDuFunction instances GNbDuFunction001 and GNbDuFunction002.
  • This embodiment provides a method for managing a gNB that includes both a CU and a DU.
  • the CU and the DU belong to the same managed entity (ME), and the operations are as follows:
  • ME001 Generate a management object instance including the management unit ManagedElement of the gNB, such as ME001; Note: Here, the generation of ME001 may precede the management object instance of the subsequent CU and DU, that is, the management object instance in which the subsequent CU and DU are generated. At the time, the ME001 may already exist.
  • the MOI of the CU of the gNB is generated, such as GNbCuFunction001, and the GNbCuFunction001 is included in ME001.
  • a management object instance of a DU that generates the gNB such as GNbDuFunction001 and GNbDuFunction002, the GNbDuFunction001 and GNbDuFunction002 are included in ME001.
  • the dUIDList in the GNbCuFunction instance GNbCuFunction001 holds the IDs of the corresponding GNbDuFunction instances GNbDuFunction001 and GNbDuFunction002.
  • This embodiment provides a method for managing a gNB that includes both a CU and a DU.
  • the CU and the DU belong to different MEs, and the operations are as follows:
  • ME001 and ME002 Generate a management object instance of the management unit ManagedElement including the CU and DU parts of the gNB, such as ME001 and ME002; Note: Here, the generation of ME001 and ME002 may precede the subsequent instances of the CU and the DU, that is, in the subsequent generation When managing instances of CUs and DUs, the ME001 and ME002 may already exist.
  • the MOI of the CU of the gNB is generated, such as GNbCuFunction001, and the GNbCuFunction001 is included in ME001.
  • the MOI of the DU of the gNB is generated, such as GNbDuFunction001 and GNbDuFunction002, and the GNbDuFunction001 and GNbDuFunction002 are included in ME002.
  • the dUIDList in the GNbCuFunction instance GNbCuFunction001 holds the IDs of the corresponding GNbDuFunction instances GNbDuFunction001 and GNbDuFunction002.
  • a network element management apparatus includes: a model establishing unit 10, configured to set at least one management object instance corresponding to at least one network resource model corresponding to at least one CU of the base station and at least one in the management information. At least one management object instance corresponding to the network resource model corresponding to the DU; the management unit 20 is configured to manage at least one CU in the base station according to the at least one management object instance corresponding to the at least one CU; and, according to the at least one At least one management object instance corresponding to the DU manages at least one DU in the base station.
  • the base station comprises at least one CU, the base station comprising at least one DU.
  • the model establishing unit is further configured to establish a correspondence between at least one management object instance corresponding to at least one CU included in the same base station and at least one management object instance corresponding to at least one DU; the management unit And at least one management object instance corresponding to the at least one CU included in the base station, at least one management object instance corresponding to the at least one DU, and at least one management object instance corresponding to the at least one CU and at least one management corresponding to the at least one DU
  • the correspondence between the object instances is managed by the base station.
  • the model establishing unit 10 is configured to set at least one management object instance corresponding to the network resource model corresponding to the at least one CU of the base station and at least one corresponding to the network resource model corresponding to the at least one DU.
  • Management object instance setting an attribute of each CU in the at least one CU, the attribute of each CU includes a CuId item for indicating an identifier of each CU itself; setting the at least one DU An attribute of each DU, where the attribute of each DU includes a DuId item, which is used to indicate the identity of each DU itself.
  • the attribute of each CU further includes a dUIDList list for storing an identifier of the DU corresponding to each CU.
  • the attribute of each DU further includes a cUIDList list for storing an identifier of a CU corresponding to each DU.
  • the management unit 20 is further configured to modify the dUIDList list of the CU corresponding to the changed DU according to the change of the changed DU when the DU corresponding to the base station changes.
  • the model establishing unit 10 is further configured to: set a network resource model of the at least one CU as a network resource model GNbCuFunction; and set a network resource model of the at least one DU as a network resource model GNbDuFunction.
  • the network resource model is set to have at least one of the following relationships: the network resource models GNbCuFunction and GNbDuFunction are both inherited from the network resource model ManagedFunction; the network resource models GNbCuFunction and GNbDuFunction are both included in the network resource model ManagedElement.
  • the model establishing unit 10 is further configured to: set a correspondence relationship between each CU and a base station by setting a CuId item of each CU; wherein, for a CU corresponding to the base station, a CU corresponding to the base station a CuId term is set to include an Id item of the managed element corresponding to the base station; the Id item is an identifier of the ManagedElement itself; and a correspondence relationship between each DU and at least one CU is set by setting a CuId item of each DU; wherein, for each a CU corresponding to the CU, the CuId item of the DU corresponding to each CU is set to include a CuId item of each CU; or, by setting a DuId item of each DU, setting a correspondence relationship between each DU and a base station; The CuId item of the DU corresponding to the base station is set to include an Id item of the ManagedElement.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil de gestion d'élément de réseau. Le procédé consiste à : définir respectivement, dans des informations de gestion de réseau, une instance d'objet de gestion correspondant à un modèle de ressource de réseau correspondant à une CU d'une station de base et une instance d'objet de gestion correspondant à un modèle de ressource de réseau correspondant à une DU de la station de base ; et gérer la CU dans la station de base selon l'instance d'objet de gestion correspondant à la CU ; et gérer la DU dans la station de base selon l'instance d'objet de gestion correspondant à la DU, la station de base comprenant au moins une CU et au moins une DU.
PCT/CN2018/113707 2017-11-03 2018-11-02 Procédé et appareil de gestion d'élément de réseau Ceased WO2019085999A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711072938.4 2017-11-03
CN201711072938.4A CN109756906A (zh) 2017-11-03 2017-11-03 一种网元管理方法和装置

Publications (1)

Publication Number Publication Date
WO2019085999A1 true WO2019085999A1 (fr) 2019-05-09

Family

ID=66332838

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/113707 Ceased WO2019085999A1 (fr) 2017-11-03 2018-11-02 Procédé et appareil de gestion d'élément de réseau

Country Status (2)

Country Link
CN (1) CN109756906A (fr)
WO (1) WO2019085999A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210274366A1 (en) * 2018-08-07 2021-09-02 Apple Inc. End-to-end (e2e) performance measurements in 5g networks

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112584398B (zh) * 2019-09-29 2022-09-16 华为技术有限公司 数据处理方法、装置及存储介质
CN113556749B (zh) * 2020-06-10 2022-09-13 中兴通讯股份有限公司 小区管理模型和小区管理方法
CN113727374B (zh) * 2021-08-26 2023-07-07 中国联合网络通信集团有限公司 一种网络资源管理方法及装置

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
"Telecommunication management; Study on management aspects of next generation network architecture and features", 3GPP GENERATION PARTNERSHIP PROJECT 28.802 V1.1.0, 31 October 2017 (2017-10-31), XP055614669 *
"Telecommunication management; Study on management aspects of virtualized network functions that are part of the New Radio (NR", 3GPP GENERATION PARTNERSHIP PROJECT 32.864 V1.0.0, 30 September 2017 (2017-09-30), XP051336904 *
INTEL.: "Add NRM options for the gNB", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #112 S 5-171575, 31 March 2017 (2017-03-31), XP051248685 *
INTEL.: "Discussion paper for the NRM enhancement to support gNB", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #111BIS S5A-170087, 16 February 2017 (2017-02-16), XP051218527 *
INTEL.: "pCR 32.864 Add the CU and DU modelling options", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #114 S 5-174110, 25 August 2017 (2017-08-25) *
NOKIA: "pCR TR 28.802 Add potential solution for NR management", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #114 S 5-174251, 25 August 2017 (2017-08-25) *
NOKIA: "Rel-15 pCR 28. 802 Add potential NRM solution for gNB with functional split", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #115 S 5-175205, 20 October 2017 (2017-10-20), XP051348974 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210274366A1 (en) * 2018-08-07 2021-09-02 Apple Inc. End-to-end (e2e) performance measurements in 5g networks
US11765608B2 (en) * 2018-08-07 2023-09-19 Apple Inc. End-to-end (E2E) performance measurements in 5G networks

Also Published As

Publication number Publication date
CN109756906A (zh) 2019-05-14

Similar Documents

Publication Publication Date Title
US11277306B2 (en) Sending information of a network repository function instance storing network function instance information
CN110603837B (zh) 将移动无线电通信网络的网络切片实例与网络功能相关联的方法
US12402036B2 (en) Network slice deployment method and apparatus
KR102439559B1 (ko) 경보 방법 및 디바이스
US20210326167A1 (en) Vnf service instantiation method and apparatus
CN105103507B (zh) 网络功能虚拟化的方法及装置
CN106134141B (zh) 一种更新网络服务描述器nsd的方法及装置
CN108011846B (zh) 网络功能虚拟化架构中管理业务的方法及装置
WO2019007345A1 (fr) Procédé, appareil et système de sélection de tranche de réseau, et support d'informations
US20190056975A1 (en) Virtualized network function manager determining method and network functions virtualization orchestrator
CN110351111A (zh) 一种订阅处理方法、网络节点及用户数据库
EP3723325A1 (fr) Procédé de gestion de service de réseau, dispositif et système associés
WO2019085999A1 (fr) Procédé et appareil de gestion d'élément de réseau
CN109862581A (zh) 一种通信方法及装置
CN106664216A (zh) 一种切换vnf的方法和装置
US11284303B2 (en) Network resource model to support next generation node B
WO2019141089A1 (fr) Procédé, dispositif, système et terminal d'alarme de réseau
US20250344076A1 (en) Data delivery automation of a cloud-managed wireless telecommunication network
US20180062946A1 (en) Method and Apparatus for Establishing Network Service Instance
US20250142317A1 (en) Unified data registry (udr) synchronization in a wireless communication network
WO2023137712A1 (fr) Procédé, dispositif et produit-programme informatique pour communication sans fil
US12231306B2 (en) Performance index value calculation system and performance index value calculation method
US20240281754A1 (en) Performance index value calculation system and performance index value calculation method
CN112889247B (zh) Vnf服务实例化方法及装置
JP7764611B2 (ja) 仮想化通信システムをテストするための方法及び管理コンポーネント

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: 18872476

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 15/09/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18872476

Country of ref document: EP

Kind code of ref document: A1