WO2018000394A1 - Procédé et appareil d'agencement de ressources de réseau - Google Patents

Procédé et appareil d'agencement de ressources de réseau Download PDF

Info

Publication number
WO2018000394A1
WO2018000394A1 PCT/CN2016/088037 CN2016088037W WO2018000394A1 WO 2018000394 A1 WO2018000394 A1 WO 2018000394A1 CN 2016088037 W CN2016088037 W CN 2016088037W WO 2018000394 A1 WO2018000394 A1 WO 2018000394A1
Authority
WO
WIPO (PCT)
Prior art keywords
network resource
management unit
information
request message
capability
Prior art date
Application number
PCT/CN2016/088037
Other languages
English (en)
Chinese (zh)
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 华为技术有限公司
Priority to EP16906794.9A priority Critical patent/EP3468105A4/fr
Priority to CN201680087147.6A priority patent/CN109417501B/zh
Priority to PCT/CN2016/088037 priority patent/WO2018000394A1/fr
Publication of WO2018000394A1 publication Critical patent/WO2018000394A1/fr
Priority to US16/235,190 priority patent/US20190140972A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a method and a device for scheduling network resources.
  • Network Function Virtualization (NFV) technology reduces the expensive equipment cost of the network by using general-purpose hardware and virtualization technology to carry software processing of many functions.
  • An indicator of the NFV system is to implement fast service deployment.
  • the service deployment allocates network resources (also called network functions) that meet the requirements for the service.
  • the network resources include multiple network elements with different network functions.
  • the scheduling of network resources relies on manual participation analysis, and the efficiency is low, which cannot meet the requirements of rapid deployment of services.
  • the embodiments of the present invention provide a method and a device for scheduling network resources, so as to improve the efficiency of network resource scheduling to meet the requirements of rapid service deployment.
  • an embodiment of the present invention provides a method for scheduling network resources.
  • the method includes: the second management unit sends the information of the network resource to the first management unit, for example, the second management unit sends the information of the network resource by using the registration request message, or the second management unit sends the network resource by using the query response message. information.
  • the first management unit receives the information of the network resource from the second management unit, and performs network resource scheduling according to the information of the network resource.
  • the information of the network resource includes capability information of the network resource, where the capability information of the network resource is used to indicate a function or feature of the network resource, for example, the capability information of the network resource may be a capability identifier or network of the network resource. The ability to describe the information of the resource.
  • the information about the network resource further includes at least one of the following information: an identifier of the network resource, status information of the network resource, or usage information of the network resource.
  • the first management unit receives the information of the network resource that includes the capability information of the network resource from the second management unit, and further performs network resource scheduling according to the information of the network resource, thereby implementing the self-network resource. Dynamic programming improves the efficiency of network resource orchestration to meet the needs of rapid business deployment.
  • the second management unit may send a registration request message to the first management unit, where the registration request message is used to register a network resource, and the registration request message includes information about the network resource.
  • the first management unit receives the registration request message, and obtains information about the network resource from the registration request message.
  • the first management unit may send a query request message to the second management unit, where the query request message is used to request information of the network resource, and the second management unit determines the network resource according to the query request message. And sending a query response message to the first management unit, where the query response message includes information about the network resource.
  • the first management unit receives the query response message, and obtains information about the network resource from the query response message.
  • the query request message includes capability information of the network resource, and is used to determine information about the network resource. For example, after receiving the query request message, the second management unit determines information of the network resource that satisfies the condition according to the capability information.
  • the first management unit may determine, according to the service requirement and the information of the network resource, the identifier of the target network resource that meets the service requirement or the capability information of the target network resource; and then, the first management unit goes to the second
  • the management unit sends an instance obtainment request message, where the instance obtains the identifier of the target network resource or the capability information of the target network resource, where the instance obtain request message is used to request the identifier of the target network resource or the target network resource.
  • the capability information corresponds to the target instance.
  • the second management unit receives the instance acquisition request message, and determines a target instance that satisfies the condition according to the identifier of the target network resource or the capability information of the target network resource, for example, the second management unit first determines from the deployed instance. Whether there is a target instance that satisfies the condition, if there is no target instance in the deployed instance that satisfies the condition, the second management unit requests to deploy a new target instance that satisfies the condition. The second management unit sends the information of the target instance to the first management unit in the instance acquisition response message, where the information of the target instance includes, for example, the identifier of the target instance. among them,
  • the first management unit may be set as a single functional entity, the first management unit may be set as a functional module of other functional entities, and the functions of the first management unit may be integrated in other In the functional entity.
  • the second management unit may be set as a single functional entity, or the second management unit may be set as a functional module of other functional entities, and the functions of the second management unit may be integrated into other functional entities.
  • the first management unit and the second management unit may be combined into one combined entity having the functions of the first management unit and the functions of the second management unit.
  • the first management unit may be NO, SO, NM, NFVO or NF Controller.
  • the second management unit can be NO, NM, EM or VNFM.
  • the second management unit when the first management unit is NO or SO, the second management unit is NM, NFVO or EM.
  • the second management unit is an EM, an NF Controller, or a VNFM.
  • the first management unit when the first management unit is NFVO, the second management unit is a VNF, EM or NF Controller.
  • the embodiment of the present invention provides a first management unit, which may implement the functions performed by the first management unit in the foregoing method example, and the functions may be implemented by hardware or by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the first management unit includes a processor and a communication interface configured to support the first management unit to perform a corresponding function in the above method.
  • the communication interface is used to support communication between the first management unit and other network elements.
  • the first management unit can also include a memory for coupling with the processor that holds the program instructions and data necessary for the device.
  • the embodiment of the present invention provides a second management unit, which may implement the functions performed by the second management unit in the foregoing method example, and the functions may be implemented by hardware or by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the second management unit includes a processor and a communication interface configured to support the second management unit to perform a corresponding function in the above method.
  • the communication interface is used to support communication between the second management unit and other network elements.
  • the second management unit can also include a memory for coupling with the processor that holds the program instructions and data necessary for the device.
  • an embodiment of the present invention provides a communication system, where the system includes the first management unit and the second management unit described in the foregoing aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the first management unit, which includes a program designed to execute the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the second management unit, which includes a program designed to execute the above aspects.
  • the first management unit receives the information of the network resource from the second management unit, where the information of the network resource includes the capability information of the network resource, and the first management unit further according to the network.
  • the information of the resources is used to arrange the network resources, thereby realizing the automatic arrangement of the network resources and improving the efficiency of the network resource arrangement.
  • FIG. 1 shows a possible network architecture provided by an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for scheduling a network resource according to Embodiment 1 of the present invention
  • FIG. 3 is a schematic diagram of capability information of a network resource
  • FIG. 4 is a schematic diagram of communication of a method for acquiring information of a network resource according to Embodiment 2 of the present invention.
  • FIG. 5 is a schematic diagram of communication of a method for acquiring information of a network resource according to Embodiment 3 of the present invention.
  • FIG. 6 is a schematic diagram of communication of a network resource scheduling method according to Embodiment 4 of the present invention.
  • FIG. 7 is a schematic structural diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of another first management unit according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a second management unit according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another second management unit according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and are not limited to the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • the technical solution provided by the embodiment of the present invention can be applied to a network management system, and the network management
  • the system may include a Network Function Virtualization (NFV) system or may not include an NFV system.
  • NFV Network Function Virtualization
  • the embodiment of the present invention is described by taking a network management system including an NFV system, that is, an NFV-based network management system as an example.
  • FIG. 1 shows a possible network architecture provided by an embodiment of the present invention, which is an NFV-based network architecture.
  • the traditional network architecture usually adopts independent business network and operation support system.
  • NFV technology deconstructs the network architecture from vertical and horizontal.
  • the network architecture in the NFV environment is divided into three layers from a vertical perspective:
  • NFV Infrastructure layer NFV Infrastructure (NFVI), from a cloud computing perspective, can be understood as a resource pool.
  • NFVI maps to the physical infrastructure by connecting multiple geographically dispersed data centers over a high-speed communications network.
  • NFVI requires virtualization to convert physical compute/storage/swap resources into virtual compute/storage/swap resource pools.
  • Virtual network layer corresponds to the current telecommunication service network. Each physical network element is mapped into a virtualized network function (VNF) unit. The required resources of the VNF unit need to be decomposed into virtual computing/storage/exchange. The resources are carried by the NFVI. The interfaces between the VNF units can use the signaling interfaces defined by the traditional network.
  • VNF virtualized network function
  • the business management layer includes the Operations Support System (OSS)/Business Support System (BSS) and Element Manager (EM) units, which need to be modified and necessary for virtualization. Adjustment.
  • OSS Operations Support System
  • BSS Business Support System
  • EM Element Manager
  • NM Network Manager
  • NM Network Manager
  • the network management unit may be described as an NM unit or an NM.
  • the network architecture in the NFV environment is divided into two domains from the horizontal perspective:
  • Service network domain Corresponding to the current telecommunication service networks.
  • the NFV environment adds a resource management orchestration domain, which is responsible for the management and orchestration of the entire NFVI resources, mapping and association of the business network and NFVI resources.
  • MANO includes three virtual infrastructure management (VIM) units, virtual network function management (VNFM) units, and NFV Orchestrator (NFVO) units. Units, complete network services provided to NFVI, VNF units, and service networks (Network Service, NS) three levels of management.
  • the resource management orchestration domain may further include an NS index, a VNF index, an NFV instance, an NFVI resource, and the like.
  • the solution of the embodiment of the present invention introduces two logical units: a Service Orchestrator (SO) unit and a Network Orchestrator (NO) unit.
  • the service orchestration unit may be described as an SO unit or an SO
  • the network orchestration unit may be described as a NO unit or NO.
  • the SO may be set as a single functional entity, or the SO may be set as a functional module of other functional entities, and the functions of the SO may be integrated into other functional entities.
  • the NO may be set as a single functional entity, or the NO may be set as a functional module of other functional entities, and the function of the NO may be integrated into other functional entities.
  • the SO and the NO may be combined into one combined entity having the function of the SO and the function of the NO.
  • the association entity may be referred to as a service and network orchestration unit. It is to be understood that the association entity may have other names, which are not limited in the embodiment of the present invention.
  • the concatenated entity in the case of a concatenated entity, in the embodiment of the present invention, the concatenated entity may be set as a single functional entity, or the concatenated entity may be set as a functional module of other functional entities, and may also be combined. The functionality of the entity is integrated into other functional entities.
  • the functions of the foregoing SO include, but are not limited to, lifecycle management (eg, instantiation or creation, expansion and expansion, or update) of a service according to a service request message sent by the BSS; service aggregation, service management (eg, failure, Configuration, accounting, performance, security (Fault, Configuration, Accounting, Performance, Security, FCAPS) management) and mapping between service and network slices.
  • the service may be a set of service level agreement (SLA) communication services that the user can enjoy, for example, Mobile Broadband (MBB) services, such as voice and Internet of Things (IOT).
  • MBB Mobile Broadband
  • IOT Internet of Things
  • Business for example, smart parking, smart meter reading, etc.
  • the network slice may be a communication resource that ensures that the bearer service or the service can meet the SLA requirement, and may also be considered as a combination of the network function and the communication resource required to complete a service or a certain service.
  • the functions of the above NO include, but are not limited to, management of network slices (eg, lifecycle management, FCAPS management, management of network slice templates); management of network functions (NF); mapping of network slices and network functions; coordination Different types of network resources; Adjust the network resources provided by different operators and different network providers; unify the network equipment provided by different vendors so that the network resources provided by different network providers can meet the requirements of the target service (for example, SLA requirements, Key Performance Indicator (KPI) requirements and Quality of Service (QoS); external application program interface (API), which is used to provide network functions for third parties.
  • Cross-operator deployment for example, SLA requirements, Key Performance Indicator (KPI) requirements and Quality of Service (QoS); external application program interface (API), which is used to provide network functions for third parties.
  • the lifecycle management of the network slice includes the creation, deletion, and update of the network slice or the network; the management of the network slice template by the NO includes the creation, update, deletion, activation, and Deactivate and so on.
  • SO and NO are set separately, and both SO and NO are set in OSS/BSS.
  • the setting of SO and NO in FIG. 1 is only an example, and SO and NO may have other setting manners: for example, both are set outside the OSS/BSS; for example, SO is set in the OSS/BSS, NO Set outside of NO.
  • the SO and the NO may be combined and set as one set entity, and the set entity may be set inside the OSS/BSS or outside the OSS/BSS.
  • the solution of the embodiment of the present invention may perform network resource scheduling by interaction between the first management unit and the second management unit.
  • the first management unit is mainly used for the arrangement of the network resources
  • the second management unit is mainly used for the management of the network resources.
  • the devices having the scheduling function for the network resources can be referred to as the first management network element;
  • a device having a management function for a network resource may be referred to as a first management network element.
  • the first management unit may be NO, SO, OSS, NM or NFVO.
  • the second management unit may be NO, NM, EM, VNFM or a network function controller (NF controller), and the network function controller may also be referred to as a network function manager.
  • the first management unit is NO or SO
  • the second management unit is NM, NFVO or EM.
  • the second management unit is an EM, an NF Controller, or a VNFM.
  • the first management unit is NFVO
  • the second management unit is VNFM, EM or NF Controller.
  • Embodiment 1 of the present invention provides a method for scheduling network resources
  • FIG. 2 is an embodiment of the present invention.
  • a schematic flowchart of a method for configuring a network resource is provided. As shown in FIG. 2, the method in this embodiment includes the following steps:
  • Step 101 The first management unit receives information of the network resource from the second management unit, where the information of the network resource includes capability information of the network resource, where the capability information of the network resource is used to indicate a function or feature of the network resource.
  • the first management unit may obtain information of the network resource by any one of the following methods:
  • the first management unit may receive a registration request message from the second management unit, where the registration request message carries information about the network resource, where the registration request message is used to register the network resource.
  • the first management unit may send a query request message to the second management unit, where the query request message is used to request information about the network resource; and the second management unit determines the information of the network resource according to the query request message.
  • the information of the network resource is carried in the query response message and sent to the first management unit.
  • the first management unit receives the query response message.
  • the capability information of the network resource is used to indicate the function or feature of the network resource, and the capability information of the network resource is mainly used for the scheduling of the network resource.
  • the capability information of the network resource shields other properties (such as the provider and version of the network resource) of the network resource that the first management unit does not need to perceive as the orchestration unit, and only needs to know that a certain network resource has the first management unit. Some kind of ability can be, no need to pay attention to other properties of the network resources.
  • the network resources in this embodiment and in the following embodiments may be specifically NF, Network Service (NS), network, or Network Element (NE).
  • the network is mainly The resource is described by taking NF as an example.
  • NF is usually expressed in the form of NF class or NF instance.
  • MME NF can provide mobility management capability.
  • the NF class identifies a type of NF instance, which can be an NF template, an NF model, or a descriptor.
  • a network resource can have one or more capabilities, and different network resources can have the same capabilities.
  • Figure 3 is a schematic diagram of the capabilities of network resources. As shown in Figure 3, NF class1, NF class2, and NF class3 all have the same capabilities. NF class4 has two capabilities: capability 1 and capability 2, and NF class 5 has capability 2, NF. Class3 deploys two NF instances: NF Instance1 and instance2, where NF instance1 and instance2 have the same capabilities and the same capabilities as NF class3, that is, multiple NF instances deployed according to the same NF class have the same capabilities.
  • the capability information of the network resource is a capability identifier or capability description information of the network resource
  • the capability identifier of the network resource is used to uniquely identify a network resource
  • the capability description information of the network resource is used to describe the capability of the network resource.
  • the first management unit may allocate an identifier for the capability of the network resource according to the capability description information of the network resource.
  • the information of the network resource includes at least one of the following information in addition to the capability information of the network resource: the identifier of the network resource, the status information, and the usage information.
  • the identifier of the network resource is used to uniquely identify a network resource, and the identifier of the network resource may be an identifier of the NF class or an identifier of the NF instance.
  • the status information of the network resource is used to indicate whether the network resource is available.
  • the status information of the NF class may also include whether the NF class is deployed with the NF instance.
  • the usage information of the network resource is used to indicate whether the network resource is used.
  • Step 102 The first management unit performs network resource scheduling according to the information of the network resource.
  • the first management unit may perform network resource scheduling according to service requirements and network resource information. For example, the first management unit determines the identifier of the target network resource or the capability information of the target network resource that meets the service requirement according to the service requirement and the information of the network resource. Then, the first management unit sends an instance acquisition request message to the second management unit, where the instance acquisition request message is used to request a target instance corresponding to the identifier of the target network resource or the capability information of the target network resource, where the instance obtains The request message includes an identifier of the target network resource or capability information of the target network resource.
  • the service requirement is carried in a service request message or a network slice request message received by the first management unit.
  • the second management unit After receiving the instance obtaining request message, the second management unit determines the target instance that satisfies the condition according to the identifier of the target network resource or the capability information of the target network resource, and returns a target instance to the first management unit, and the target instance that satisfies the condition
  • the number may be one or more.
  • the first management unit receives the information of the network resource from the second management unit, where the information of the network resource includes the capability information of the network resource, and then performs network resource scheduling according to the information of the network resource, thereby implementing the network resource.
  • Automatic programming to improve network resources The efficiency of the orchestration to meet the needs of rapid business deployment.
  • the second embodiment of the present invention provides a method for acquiring information of a network resource
  • FIG. 4 is a schematic diagram of communication of a method for acquiring information of a network resource according to Embodiment 2 of the present invention.
  • the method provided in this embodiment may include the following steps:
  • Step 201 The second management unit sends a registration request message to the first management unit, where the registration request message includes information about a network resource.
  • the registration request message is used to register a network resource, and the registration request message may also be referred to as a notification message or other name.
  • the second management unit adds new network resources, the second management unit sends a registration request message to the first management unit. Specifically, the registration request message is used to register an NF Class or NFinstance.
  • the registered NF Class can be a new NF class or an updated NF class.
  • the network resource information included in the registration request message is specifically the capability information of the registered NF Class, and is registered. At least one of an NF Class identifier, version information, status information, and usage information.
  • the capability information of the registered NF Class is specifically the capability identifier or capability description information of the registered NF Class.
  • the registered NF instance When registering an NF instance, the registered NF instance is a newly deployed NF instance.
  • the network resource information included in the registration request message is specifically the capability information of the registered NF instance, and the registered NF instance identifier and status information. And at least one of the usage information.
  • Step 202 The first management unit checks the validity of the information of the network resource.
  • the first management unit When registering an NF Class, the first management unit verifies the legality of the registered NF class after receiving the registration request message, and records the information of the registered NF class. When registering an NF instance, the first management unit verifies the validity of the registered NF instance after receiving the registration request message, and records the information of the registered NF instance.
  • Step 203 The first management unit sends a registration response message to the second management unit.
  • the first management unit After verifying that the information of the network resource is legal, the first management unit sends a registration response message to the second management unit to notify the second management unit that the network resource registration is successful.
  • step 202 and step 203 are optional steps.
  • the first management unit may not verify the validity of the network resource, and may not return the registration response message to the second management unit. After a certain period of time, the second management unit defaults to the first management order.
  • the first management unit may also return a registration response message to the second management unit after receiving the registration request message.
  • the registration response message may not include any information, and may include identifier information of the network resource and/or a capability identifier of the network resource.
  • the second management unit actively sends the capability information of the network resource and other information to the first management unit, so that the subsequent first management unit performs network resource scheduling according to the capability information of the network resource.
  • the third embodiment of the present invention provides a method for acquiring information of a network resource
  • FIG. 5 is a schematic diagram of communication of a method for acquiring information of a network resource according to Embodiment 3 of the present invention.
  • the method provided in this embodiment may include the following steps:
  • Step 301 The first management unit sends a query request message to the second management unit, where the query request message is used to request information about acquiring network resources.
  • the first management unit sends a query request message to the second management unit to request to obtain the information of the network resource.
  • the query request message does not carry any query condition
  • the second implementation manner The query request message carries the query condition.
  • Step 302 The second management unit determines information about the network resource according to the query request message.
  • the second management unit may determine the information of the network resource by any of the following methods:
  • the second management unit determines, according to the query request message, that the network resource that the first management unit requests to query is all locally saved network resources, and the information of all the network resources saved locally is carried.
  • the information is sent to the first management unit in the query response message, and all network resources saved locally by the second management unit are all NF Class and NF instance registered on the second management unit.
  • the query request message carries the query condition
  • the query condition is a condition that the network resource that the first management unit needs to obtain needs to be satisfied.
  • the second management unit needs to save the local condition according to the query condition.
  • the network resource that meets the condition is determined in the network resource, and the information carrying query response message of the network resource that satisfies the query condition is sent to the first management unit.
  • the query condition may be the capability information of the network resource, and after receiving the query request message, the second management unit determines, according to the capability information, the network resource that meets the capability information from all the locally saved network resources, The information of the network resource that meets the capability requirement is carried in the query response message and sent to the first management unit.
  • the capability information may also be understood as capability requirement information, and may specifically be capability identification or capability description information.
  • the capability requirement information is the capability identifier
  • the first management unit needs to acquire the capability information of the network resource before sending the query request message to the second management unit.
  • the second management unit adds a new network resource
  • the second management unit identifies whether the newly added network resource provides a new capability, where the newly added network resource may be added. NF Class and NF instance.
  • the second management unit sends a capability registration request message to the first management unit, where the capability registration request message is used to request registration of the newly added capability, and the capability registration request message is Carry this new capability information.
  • the new capability information is the identifier of the added capability or the description information of the added capability.
  • the added capability information is the description information of the added capability
  • the second option is optional.
  • the management unit assigns an identifier to the newly added capability according to the newly added capability description information.
  • Step 303 The query response message sent by the second management unit to the first management unit, where the query response message includes information about the network resource.
  • the second management unit verifies the legality of the newly added capability information, and returns a capability registration response message to the first management unit.
  • the capability registration response message is received. This new capability ID is included.
  • the first management unit sends a query request message to the second management unit to obtain the capability information of the network resource and other information, so that the subsequent first management unit performs network resource scheduling according to the capability information of the network resource.
  • FIG. 6 is a schematic diagram of communication of a network resource scheduling method according to Embodiment 4 of the present invention, as shown in FIG.
  • the method provided in this embodiment may include the following steps:
  • Step 401 The first management unit determines, according to the service requirement and the information of the network resource, the identifier or capability information of the target network resource that meets the service requirement.
  • the service requirement is, for example, an SLA, a service type information, or the like
  • the first management unit determines the identity or capability information of the target network resource that meets the service requirement according to the SLA, the service type information, and the like.
  • the target network resource may be an NF Class or an NF Instance
  • the identifier of the target network resource may be an identifier of the NF Class or an identifier of the NF Instance.
  • the first management unit determines, according to the service requirement and the information of the network resource, that the result may be an NF Class, NF Instance or capability that satisfies the requirement.
  • the first management unit determines the NF Class that meets the requirement according to the service requirement and the capability information of the NF Class, and carries the identifier of the NF Class in the instance acquisition request message and sends the identifier to the second management unit.
  • the instance obtaining request message further includes information about a version of the NF Class, a location and a size of the instance to be obtained, and the like.
  • the second management unit determines whether the existing NF Instance satisfies the requirement and is available according to the information of the NF Class included in the instance acquisition request message and the information of the instance to be acquired.
  • the second management unit sends the information of the available NF instance in the instance get response message to the first management unit, and the available NF instance may be one or more. If the existing NF Instance does not have an available NF Instance, the second management unit deploys one or more NF Instances that meet the conditions according to the NF Class identifier, and carries the information of the deployed NF Instance in the instance get response message. The first management unit.
  • the first management unit determines the NF Instance that satisfies the requirement according to the service requirement and the capability information of the NF Instance, and carries the identifier of the NF Instance in the instance acquisition request message and sends the identifier to the second management unit.
  • the instance obtaining request message further includes a size, a location, an access information, and the like of the NF Instance, and the second management unit determines, according to the information of the NF Instance in the instance obtaining request message, the NF Instance that satisfies the condition, and determines the The information of the NF Instance is carried in the instance acquisition response message and sent to the first management unit.
  • the first management unit determines the capability to meet the requirement according to the service requirement and the capability information of the locally stored network resource, and the determined capability information is carried in the instance acquisition request message and sent to the second management unit.
  • the capability information may be capability identification and/or capability description information.
  • the instance obtaining request message further includes the size, the location, the access information, and the like of the NF Instance to be obtained, and the second management unit obtains the capability information carried in the request message and the information of the NF Instance to be acquired according to the instance.
  • the NF Instance is determined to be available in the existing NF Instance. If the NF Instance is available, the second management unit sends the information of the available NF instance to the first management unit in the instance acquisition response message.
  • the second management unit requests to deploy one or more NF Instances that meet the capability according to the capability information carried in the request message, and carries the determined NF Instance information. Instance get response message sent Send to the first management unit.
  • Step 402 The first management unit sends an instance obtaining request message to the second management unit, where the instance obtaining request message includes the identifier of the target network resource or the capability information of the target network resource, where the instance obtaining request message is used to request the acquiring and the target network.
  • the target instance corresponding to the identifier of the resource or the capability information of the target network resource.
  • the instance obtaining request message may specifically be an instance creation request message, an instance update request message, or an instance use request message, the instance creation request message is used to request to create one or more new instances, and the instance update request message is used for the request. Update one or more instances that have already been created, and the instance uses the request message to request that an instance be allowed to be used.
  • Step 403 The second management unit determines, according to the identifier or capability information of the target network resource, a target instance that satisfies the condition.
  • Step 404 The second management unit sends an instance acquisition response message to the first management unit, where the instance obtains information including the target instance in the response message.
  • Step 405 The first management unit sends an instance release request message to the second management unit, where the instance processing request message includes an identifier of the target instance.
  • the first management unit After obtaining the target instance, the first management unit does not need to use the target instance at some time because of deleting the service or deleting the slice.
  • the first management unit sends an instance release request message to the second management unit, where the instance release request message includes an identifier of the target instance, and the instance release request message is used to request to delete or release the target instance.
  • the instance release request message further includes an operation type identifier, where the operation type identifier indicates an operation type used by the second management unit to process the target instance.
  • Step 406 The second management unit processes the target instance according to the instance release request message.
  • the second management unit After the second management unit receives the instance release request message, if the instance release request message does not carry the operation type identifier, the target instance is released, and the state of the target instance is changed to an unavailable state; optionally, the second The management snap-in can also decide to delete the target instance at its discretion. If the instance release request message carries the operation type identifier, the second management unit processes the target instance according to the operation indicated by the operation type identifier.
  • the operation type identifier is a deletion operation identifier or a release operation identifier.
  • the second management unit deletes the target instance according to the deletion operation identifier, and when the operation type identifier is released When the identifier is operated, the second management unit releases the target instance according to the release operation identifier.
  • each network element for example, the first management unit, the second management unit, and the like, in order to implement the above functions, includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function module by using the first management unit, the second management unit, and the like according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated in the function.
  • a processing module In a processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 7 shows a possible structural diagram of the first management unit involved in the above embodiment.
  • the first management unit 100 includes a processing module 11 and a communication module 12.
  • the processing module 11 is configured to perform control management on the actions of the first management unit 100.
  • the processing module 11 is configured to support the first management unit 100 to perform the methods shown in FIG. 2, FIG. 4, FIG. 5, and FIG. 6, and/or Other processes for the techniques described herein.
  • the communication module 11 is for supporting communication between the first management unit and other network entities, for example, with the second management unit shown in FIGS. 2, 4, 5, and 6.
  • the first management unit may further include a storage module 13 for storing program codes and data of the first management unit.
  • the processing module 11 may be a processor or a controller, and may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It may implement or perform various illustrative logical blocks that are described in connection with the present disclosure. Modules and circuits.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 12 can be a transceiver circuit or a communication interface or the like.
  • the storage module 13 can be a memory.
  • the processing module 11 is a processor
  • the communication module 12 is a communication interface
  • the storage module 13 is a memory
  • the first management unit involved in the embodiment of the present invention may be the first management unit shown in FIG.
  • the first management unit 200 includes a processor 21, a communication interface 22, a memory 23, and a bus 24.
  • the communication interface 22, the processor 21, and the memory 23 are connected to each other through a bus 24.
  • the bus 24 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
  • FIG. 9 shows a possible structural diagram of the second management unit involved in the above embodiment.
  • the second management unit 300 includes a processing module 31 and a communication module 32.
  • the processing module 31 is configured to perform control management on the actions of the second management unit 300.
  • the processing module 31 is configured to support the second management unit 300 to perform the methods shown in FIG. 2, FIG. 4, FIG. 5, and FIG. 6, and/or Other processes for the techniques described herein.
  • the communication module 32 is for supporting communication between the second management unit 300 and other network entities, such as communication with the first management unit shown in FIGS. 2, 4, 5, and 6.
  • the second management unit 300 may further include a storage module 33 for storing program codes and data of the second management unit.
  • the processing module 31 can be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, a Field Programmable Gate Array, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 32 can be a transceiver circuit or a communication interface or the like.
  • the storage module 33 can be a memory.
  • the second management unit may be the second embodiment shown in FIG. Management unit.
  • the second management unit 400 includes a processor 41, a communication interface 42, a memory 43, and a bus 44.
  • the communication interface 42, the processor 41, and the memory 43 are connected to each other through a bus 44.
  • the bus 44 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • Wait The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computational Linguistics (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente invention se rapportent au domaine des communications, et concernent un procédé et un appareil d'agencement de ressources de réseau. Le procédé comprend les étapes suivantes : une première unité de gestion reçoit des informations d'une ressource de réseau provenant d'une deuxième unité de gestion, les informations de la ressource de réseau contenant des informations de capacité de la ressource de réseau, et les informations de capacité de la ressource de réseau indiquant une fonction ou une caractéristique de la ressource de réseau ; et la première unité de gestion agence la ressource de réseau selon les informations de la ressource de réseau. Dans la solution des modes de réalisation de la présente invention, la première unité de gestion reçoit de la deuxième unité de gestion les informations de la ressource de réseau contenant les informations de capacité de la ressource de réseau pour agencer ensuite la ressource de réseau selon la ressource de réseau, ce qui crée un agencement automatique de ressources du réseau et améliore l'efficacité d'agencement de ressource du réseau.
PCT/CN2016/088037 2016-06-30 2016-06-30 Procédé et appareil d'agencement de ressources de réseau WO2018000394A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP16906794.9A EP3468105A4 (fr) 2016-06-30 2016-06-30 Procédé et appareil d'agencement de ressources de réseau
CN201680087147.6A CN109417501B (zh) 2016-06-30 2016-06-30 网络资源的编排方法和设备
PCT/CN2016/088037 WO2018000394A1 (fr) 2016-06-30 2016-06-30 Procédé et appareil d'agencement de ressources de réseau
US16/235,190 US20190140972A1 (en) 2016-06-30 2018-12-28 Network resource orchestration method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/088037 WO2018000394A1 (fr) 2016-06-30 2016-06-30 Procédé et appareil d'agencement de ressources de réseau

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/235,190 Continuation US20190140972A1 (en) 2016-06-30 2018-12-28 Network resource orchestration method and device

Publications (1)

Publication Number Publication Date
WO2018000394A1 true WO2018000394A1 (fr) 2018-01-04

Family

ID=60785923

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/088037 WO2018000394A1 (fr) 2016-06-30 2016-06-30 Procédé et appareil d'agencement de ressources de réseau

Country Status (4)

Country Link
US (1) US20190140972A1 (fr)
EP (1) EP3468105A4 (fr)
CN (1) CN109417501B (fr)
WO (1) WO2018000394A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023231713A1 (fr) * 2022-05-31 2023-12-07 华为技术有限公司 Procédé, dispositif et système de communication

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10116732B1 (en) * 2014-12-08 2018-10-30 Amazon Technologies, Inc. Automated management of resource attributes across network-based services
WO2018023338A1 (fr) 2016-08-01 2018-02-08 华为技术有限公司 Procédé de gestion de fonction réseau, et dispositif de gestion de fonction réseau
WO2018094667A1 (fr) * 2016-11-24 2018-05-31 华为技术有限公司 Procédé de gestion, unité de gestion, et système
US10637753B1 (en) * 2019-04-09 2020-04-28 Verizon Patent And Licensing Inc. Managing a 5G network using extension information
US20220345379A1 (en) * 2019-09-12 2022-10-27 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for service management

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
WO2015168834A1 (fr) * 2014-05-04 2015-11-12 华为技术有限公司 Procédé d'attribution de ressources de réseau dans une fonction de réseau virtuel, composeur et gestionnaire
CN105656646A (zh) * 2014-11-10 2016-06-08 中国移动通信集团公司 一种虚拟网元的部署方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9130760B2 (en) * 2011-04-26 2015-09-08 Openet Telecom Ltd Systems, devices and methods of establishing a closed feedback control loop across multiple domains
WO2014091734A1 (fr) * 2012-12-14 2014-06-19 日本電気株式会社 Dispositif de construction de système et procédé de construction de système
WO2015099036A1 (fr) * 2013-12-27 2015-07-02 株式会社Ｎｔｔドコモ Système de gestion, nœud de gestion globale et procédé de gestion
EP3133794B1 (fr) * 2014-05-15 2019-04-03 Huawei Technologies Co., Ltd. Système réseau de virtualisation de fonction réseau
CN105282195A (zh) * 2014-06-27 2016-01-27 中兴通讯股份有限公司 网络服务提供、策略规则评估、服务组件选择方法及装置
CN105282765A (zh) * 2014-06-30 2016-01-27 中兴通讯股份有限公司 一种管理配置信息的方法、设备及网元管理系统
CN104253866B (zh) * 2014-09-20 2018-03-27 华为技术有限公司 虚拟网络功能网元的软件部署方法、系统及相关设备
US10951480B2 (en) * 2014-09-25 2021-03-16 Apple Inc. Network functions virtualization

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
WO2015168834A1 (fr) * 2014-05-04 2015-11-12 华为技术有限公司 Procédé d'attribution de ressources de réseau dans une fonction de réseau virtuel, composeur et gestionnaire
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN105656646A (zh) * 2014-11-10 2016-06-08 中国移动通信集团公司 一种虚拟网元的部署方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3468105A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023231713A1 (fr) * 2022-05-31 2023-12-07 华为技术有限公司 Procédé, dispositif et système de communication

Also Published As

Publication number Publication date
CN109417501B (zh) 2020-11-17
EP3468105A1 (fr) 2019-04-10
CN109417501A (zh) 2019-03-01
EP3468105A4 (fr) 2019-06-26
US20190140972A1 (en) 2019-05-09

Similar Documents

Publication Publication Date Title
WO2018000394A1 (fr) Procédé et appareil d'agencement de ressources de réseau
US11258822B2 (en) Network function service discovery method and device
JP7047113B2 (ja) アプリケーションのサービスレベル合意を保証するための方法、デバイスおよびシステム
US11063831B2 (en) Network slice management method and apparatus
WO2018058579A1 (fr) Procédé de gestion de tranche de réseau et unité de gestion
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
EP3826359A1 (fr) Procédé et dispositif de traitement d'informations de réseau d'accès radio, élément de réseau, et support de stockage
WO2018006381A1 (fr) Procédé, appareil et système de gestion de ressource de réseau
EP2648392A1 (fr) Système de routage d'interface de programmation d'application et son procédé de fonctionnement
KR20200062272A (ko) 모바일 네트워크 상호 작용 프록시
WO2018076547A1 (fr) Procédé de gestion de tranche de réseau, unité de gestion et système
WO2019029268A1 (fr) Procédé et dispositif de déploiement d'une tranche de réseau
CN114025021B (zh) 一种跨Kubernetes集群的通信方法、系统、介质和电子设备
US20190281503A1 (en) Management Method, Management Unit, and System
WO2018089634A1 (fr) Gestion de tranches de réseau
EP3531749B1 (fr) Procédé de gestion, unité et système de gestion destinés à une fonction de réseau
WO2017066931A1 (fr) Procédé et dispositif de gestion de certificat dans une architecture de virtualisation de fonction de réseau
US20200228419A1 (en) Network management method, device, and system
WO2017041562A1 (fr) Procédé et dispositif d'identification d'une identité d'utilisateur d'un dispositif terminal
WO2019057015A1 (fr) Procédé et appareil de gestion de tranche de réseau
CN113630266B (zh) 一种实例化边缘应用服务器的方法和装置
CN112492592A (zh) 一种多个nrf场景下的授权方法
CN111371578B (zh) 部署虚拟化网络功能的方法和装置
WO2018082574A1 (fr) Procédé d'envoi d'informations, unité, et système
WO2020253343A1 (fr) Procédé et dispositif de découverte de service de gestion

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016906794

Country of ref document: EP

Effective date: 20190104