+

WO2018127068A1 - Procédé et appareil de gestion de réseau - Google Patents

Procédé et appareil de gestion de réseau Download PDF

Info

Publication number
WO2018127068A1
WO2018127068A1 PCT/CN2018/071275 CN2018071275W WO2018127068A1 WO 2018127068 A1 WO2018127068 A1 WO 2018127068A1 CN 2018071275 W CN2018071275 W CN 2018071275W WO 2018127068 A1 WO2018127068 A1 WO 2018127068A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
slice instance
function
request message
network function
Prior art date
Application number
PCT/CN2018/071275
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 华为技术有限公司
Publication of WO2018127068A1 publication Critical patent/WO2018127068A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/28—Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/126—Applying verification of the received information the source of the received data

Definitions

  • Embodiments of the present invention relate to the field of communications, and in particular, to a network management method and apparatus in the field of communications.
  • 5G fifth generation wireless communication technology
  • 5G will support diverse application needs, including support for higher speed experiences and greater bandwidth access, lower latency and highly reliable information interaction, and the connection of larger and lower cost machine-like communication devices. Entry and management, etc.
  • 5G will support a variety of vertical industry applications for vehicle networking, emergency communications, and industrial Internet. Faced with these performance requirements and application scenarios of 5G, 5G networks need to be closer to the specific needs of users, and their customization capabilities need to be further improved.
  • the 3GPP carrier network may include Critical Machine Type Communication (Critical MTC) network slicing, Massive Machine Type Communication (Massive MTC) network slicing and Mobile Broad Band (MBB for short). Network slicing, where each network slicing service communicates with different use cases.
  • Critical Machine Type Communication Critical MTC
  • Massive Machine Type Communication Massive MTC
  • MBB Mobile Broad Band
  • a logical network formed by a network slice is implemented by the network slice instance, that is, a network slice is formed by instantiating each network function of the network slice and corresponding resources.
  • 5G networks need to manage network slicing instances. How to manage network slicing instances, there is currently no suitable solution.
  • the embodiment of the invention provides a network management method and device, so as to implement management of a network slice instance.
  • the first aspect provides a network management method, including the following steps: a first network device sends a configuration request message to a second network device, where the configuration request message is used to request to configure a first network in the first network slice instance.
  • the first network device receives a configuration response message sent by the second network device, where the configuration response message is used to indicate that the first network function is configured in the first network slice instance.
  • the configuring the first network function in the first network slice instance includes: adding a first network function on the first network slice instance or the first one in the first network slice instance A network function is removed.
  • the network management method in the embodiment of the present invention can implement management of a network slice instance. Further, the network function that provides the network slice instance can be added or deleted to implement the update of the network slice instance, so that the network slice instance can better support the change of the service feature, thereby improving the user experience.
  • the method before the first network device sends a configuration request message to the second network device, the method further includes: the first network device receiving an update request message sent by the sender, An update request message is used to request to add the first network function to the first network slice instance or to delete the first network function in the first network slice instance.
  • the method further includes: the first network device sending an update response message to the sending end, where the update response message is used Indicates that the first network function has been added to the first network slice instance, or the first network function in the first network slice instance has been deleted.
  • the first network device receives the update request message sent by the sending end, and triggers the first network device to send a configuration request message to the second network device, which is beneficial for the first network device to obtain the latest network slice instance composition information.
  • the configuration request message is further configured to request to configure the first network function for all or part of the second network slice instance that is allowed to add or delete the first network function.
  • the second network slice instance sharing the first network function may be updated by the foregoing solution, so that it is not affected by the first network slice instance adding or deleting the first network function.
  • the method before the first network device sends the configuration request message to the second network device, the method further includes: the first network device sending a query request message to the storage device, where The query request message is used to query the validity of the update request message; the first network device receives a query response message sent by the storage device, and the query response message is used to indicate whether the update request message is legal; The first network device sends the configuration request message to the second network device, where the first network device sends the configuration request to the second network device if the update request message is legal Message.
  • the method before the first network device sends the configuration request message to the second network device, the method further includes: the first network device sending a notification request message to the fourth network device, The notification request message is used to notify that the first network function is to be configured; the first network device receives a notification response message sent by the fourth network device.
  • the method further includes: in the first network slice instance and/or all or part
  • the first network device sends a modification to at least one of the second network device and the third network device.
  • a request message the modification request message being used to request modification of the second network function.
  • the method further includes: the first network device sending an update notification message to the storage device,
  • the update notification message carries the updated information of the first network slice instance; the first network device receives the storage success message sent by the storage device.
  • the method further includes: the first network device sending the fourth network device to the fourth network device Network function configuration information, where the network function configuration information carries configuration parameters of the first network function.
  • a second aspect provides a network management method, including the following steps: a second network device receives a configuration request message sent by a first network device, where the configuration request message is used to request to add a first network to the network segment instance. Deleting the first network function in the first network slice instance; the second network device configuring the first network function; the second network device sending the first network device A configuration response message is used to indicate that the configuration of the first network function has been completed.
  • the configuration request message is further configured to request to configure the first network function for all or part of the second network slice instance that is allowed to add or delete the first network function.
  • a third aspect provides a network management method, including the following steps: a sending end sends an update request message to a first network device, where the update request message is used to request to add the first network function to a first network slice instance. Or deleting the first network function in the first network slice instance; the sending end receiving a sending update response message of the first network device, where the update response message is used to indicate the first A network function has been added to the first network slice instance, or the first network function in the first network slice instance has been deleted.
  • a fourth aspect provides a network management method, including the following steps: a fourth network device receives a notification request message sent by a first network device, where the notification request message is used to notify that a first configuration is to be configured in the first network slice instance. a network function; the fourth network device determines, according to the notification request message, that the first network device is allowed to configure the first network function; and the fourth network device sends a notification response message to the first network device; The fourth network device receives network function configuration information sent by the first network device, where the network function configuration information carries configuration parameters of the first network function.
  • a network management apparatus comprising: a transceiver, a memory for storing instructions, and a processor.
  • the processor is coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the step of transmitting a configuration request to the second network device by the transceiver when the instruction is executed a message, the configuration request message is used to request to configure a first network function in the first network slice instance; the first network device receives a configuration response message sent by the second network device, where the configuration response message is used Representing that the first network function is configured in the first network slice instance, where the configuring the first network function in the first network slice instance includes: on the first network slice instance Adding a first network function or deleting the first network function in the first network slice instance.
  • the processor further performs the following steps: receiving, by the transceiver, an update request message sent by a sender, where the update request message is used to request the first network Adding a function to the first network slice instance, or deleting the first network function in the first network slice instance; sending, by the transceiver, an update response message to the sender, the update response The message is used to indicate that the first network function has been added to the first network slice instance, or the first network function in the first network slice instance has been deleted.
  • the configuration request message is further configured to request to configure the first network function for all or part of the second network slice instance that is allowed to add or delete the first network function.
  • the processor when executing the instruction, further performs the step of: sending, by the transceiver, a query request message to a storage device, where the query request message is used to query the legality of the update request message.
  • the processor when executing the instruction, further performing the step of: sending, by the transceiver, a notification request message to a fourth network device, where the notification request message is used to notify that the first a network function; receiving, by the transceiver, a notification response message sent by the fourth network device.
  • the process The processor further performs the following steps: transmitting, by the transceiver, a modification request message to at least one of the second network device and the third network device, the modification request message being used to request to modify the Two network functions.
  • the processor when executing the instruction, further performing the step of: sending, by the transceiver, an update notification message to the storage device, where the update notification message carries the first network slice instance after updating Information; receiving, by the transceiver, a storage success message sent by the storage device.
  • the processor further performs the following steps: sending, by the transceiver, network function configuration information to the fourth network device by using the transceiver, where the network function configuration information carries the A configuration parameter of a network function.
  • a network management apparatus comprising: a transceiver, a memory for storing instructions, and a processor.
  • the processor is coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the step of: receiving, by the transceiver, a configuration sent by the first network device when the instruction is executed a request message, the configuration request message is used to request to add a first network function on the network slice instance or delete the first network function in the first network slice instance; perform the first network function Configuring, by the transceiver, sending a configuration response message to the first network device, where the configuration response message is used to indicate that the first network function is configured in the first network slice instance.
  • the configuration request message is further configured to request to configure the first network function for all or part of the second network slice instance that is allowed to add or delete the first network function.
  • a network management apparatus comprising: a transceiver, a memory for storing instructions, and a processor.
  • the processor is coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the step of transmitting an update request to the first network device by the transceiver when the instruction is executed a message, the update request message being used to request to add the first network function to a first network slice instance, or to delete the first network function in the first network slice instance; through the transceiver Receiving a sending update response message of the first network device, where the update response message is used to indicate that the first network function has been added to the first network slice instance, or the first network slice instance The first network function has been removed.
  • a network management apparatus comprising: a transceiver, a memory for storing instructions, and a processor.
  • the processor is coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the step of: receiving, by the transceiver, a notification sent by the first network device when the instruction is executed a request message for notifying that the first network function is to be configured in the first network slice instance; determining that the first network device is allowed to configure the first network function; A network device sends a notification response message, and the network function configuration information sent by the first network device is received by the transceiver, where the network function configuration information carries configuration parameters of the first network function.
  • the ninth aspect provides a network management apparatus, including: a sending unit, configured to send a configuration request message to a second network device, where the configuration request message is used to request to configure a first network function in the first network slice instance a receiving unit, configured to receive a configuration response message sent by the second network device, where the configuration response message is used to indicate that the first network function is configured in the first network slice instance, where the The first network fragment instance configuring the first network function includes: adding a first network function on the first network slice instance or deleting the first network function in the first network slice instance.
  • the receiving unit is further configured to receive an update request message sent by the sending end, where the update request message is used to request to add the first network function to the first network slice instance, or Deleting the first network function in the first network slice instance;
  • the sending unit is further configured to send an update response message to the sending end, where the update response message is used to indicate that the first network function has been Adding to the first network slice instance, or the first network function in the first network slice instance has been deleted.
  • the configuration request message is further configured to request to configure the first network function for all or part of the second network slice instance that is allowed to add or delete the first network function.
  • the sending unit is further configured to send a notification request message to the fourth network device, where the notification request message is used to notify that the first network function is to be configured; and the receiving unit is further configured to receive the The notification response message sent by the fourth network device.
  • the sending The unit is further configured to send a modification request message to at least one of the second network device and the third network device, where the modification request message is used to request to modify the second network function.
  • the sending unit is further configured to send an update notification message, where the update notification message carries information that is updated by the first network slice instance, and the receiving unit is further configured to receive, by the storage device, Storage success message.
  • the sending unit is further configured to send network function configuration information to the fourth network device, where the network function configuration information carries configuration parameters of the first network function.
  • a network management apparatus includes: a receiving unit, configured to receive a configuration request message sent by a first network device, where the configuration request message is used to request to add a first network function to the network segment instance. Or deleting the first network function in the first network slice instance; the processing unit is configured to configure the first network function; and the sending unit is configured to send a configuration response message to the first network device The configuration response message is used to indicate that the configuration of the first network function has been completed.
  • a network management apparatus including: a sending unit, configured to send an update request message to a first network device, where the update request message is used to request to add the first network function to a first network In the slice instance, the first network function in the first network slice instance is deleted, and the receiving unit is configured to receive a sending update response message of the first network device, where the update response message is used to indicate The first network function has been added to the first network slice instance, or the first network function in the first network slice instance has been deleted.
  • a network management apparatus includes: a receiving unit, configured to receive a notification request message sent by a first network device, where the notification request message is used to notify that a first configuration is to be configured in a first network slice instance a network function, a processing unit, configured to determine that the first network device is configured to configure the first network function, and a sending unit, configured to send a notification response message to the first network device, where the receiving unit is further configured to receive the The network function configuration information sent by the first network device, where the network function configuration information carries configuration parameters of the first network function.
  • a network system comprising at least two network management devices of the above fifth to eighth aspects, or at least two network management devices of the above ninth to twelfth aspects.
  • a fourteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any possible implementation of the first aspect; or the computer program An instruction comprising the method of the second aspect or any of the possible implementations of the second aspect; or the computer program comprising instructions for performing the method of the third aspect or any of the possible implementations of the third aspect; Or the computer program comprises instructions for performing the method of any of the third aspect or any of the possible implementations of the third aspect.
  • FIG. 1 is a schematic diagram of a prior art network management architecture.
  • FIG. 2 is a structural diagram of an NSM&O according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a network management architecture applied according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of another network management architecture applied according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of another network management architecture applied according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of another network management architecture applied according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a network management method according to an embodiment of the present invention.
  • FIG. 8 is a hierarchical structure diagram of an NSM&O according to an embodiment of the present invention.
  • FIG. 9 is a schematic flowchart of another network management method according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart of another network management method according to an embodiment of the present invention.
  • FIG. 11 is a schematic flowchart of another network management method according to an embodiment of the present invention.
  • FIG. 12 is a schematic flowchart of another network management method according to an embodiment of the present invention.
  • FIG. 13 is a schematic block diagram of an apparatus for managing a network slice instance according to an embodiment of the present invention.
  • FIG. 14 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present invention.
  • FIG. 15 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present invention.
  • FIG. 16 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present invention.
  • FIG. 17 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present invention.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • Embodiments of the present invention relate to network slicing techniques.
  • the network slicing technology logically abstracts the network into one or more network slices, where each network slice contains a series of logical network functions to specifically meet the differentiated requirements of different service types.
  • network slicing is an on-demand networking, which enables operators to adjust according to changing user requirements and quickly New services that meet the needs of new applications.
  • the network slicing technology abstracts the 5G network physical infrastructure resources into a plurality of independent parallel network slice instances according to the scene requirements. Each network segment instance performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario and the business model.
  • a network slice instance can be thought of as an instantiated 5G network.
  • Such a network structure allows operators to provide the network as a service to users, and can freely combine physical networks according to indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet different users. Claim.
  • Network slice lifecycle management includes the creation, composition, update, and deletion of network slice instances.
  • the available network resources should be determined for each network slice instance and configured with specific network functions and parameters.
  • those specific network functions and network resources should be released.
  • Network slice refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure.
  • the network slice can be a complete network including the access network and the core network, capable of providing telecommunication services and having certain network capabilities.
  • a network slice may have one or more of the following characteristics: the access network may or may not slice.
  • the access network may be shared by multiple network slices. The characteristics and composition of different network slices may be different for their network functions.
  • Network Slice Instance A real-world logical network that meets certain network characteristics or service requirements.
  • a network slice instance may provide one or more services.
  • a network slicing instance can be created by a network management system.
  • a network management system may create one or more network slicing instances and manage them at the same time, including performance monitoring and fault management during the running of the network slicing instance.
  • Some network resources and network functions may be shared between network slice instances.
  • a network tile instance may or may not be created from a network tile template.
  • a complete network slicing instance can provide complete end-to-end network services.
  • Network segment instances may include network functionality.
  • Network functions may include physical network functions and/or virtual network functions. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.
  • Network Slice Template A method of generating a network slice instance to provide a reference for generating a network slice instance.
  • the network slice template specifies how the network slice instance should be generated.
  • the network slicing module can indicate which network functions are included in the network slice, and Key Performance Indicators (KPIs) that should be achieved.
  • KPIs Key Performance Indicators
  • Network function It is a processing function in the network, which defines functional behaviors and interfaces.
  • the network functions can be implemented by dedicated hardware, or by running software on dedicated hardware, or by virtualizing on a common hardware platform. The form of the function is implemented. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of use, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple network slice instances, different network functions can be used independently. This network function is called a dedicated network function. It is also possible to share the same network function, which is called a shared network function.
  • FIG. 1 illustrates a network management architecture 100.
  • the network management architecture 100 of FIG. 1 may be a 3GPP public land mobile that incorporates a network function virtualized (NFV) management and orchestration (MANO) module.
  • NFV network function virtualized
  • MANO network management and orchestration
  • Network Public Land Mobile Network, referred to as "PLMN”
  • the network management architecture 100 includes modules for managing physical network functions and virtual network functions. The modules in the network management architecture 100 are described in turn below.
  • PNF Physical network function
  • the physical network function module may be a network element (NE) in a traditional 3GPP network management architecture, that is, a physical network element.
  • the NE may be a base station, a Mobility Management Entity (MME), or a Serving Gateway (SGW).
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • VNF Virtualized network function
  • the VNF module can create virtual network functions and perform some parameter configuration on the basis of NFVI to implement a certain network function.
  • Element manager A network module for managing network elements. EM can be used to manage physical network functions (ie PNF modules) or to manage virtual network functions (ie VNF modules).
  • DM Domain manager
  • the DM can manage one or more EMs, for example, the DM can be a vendor's management system.
  • EM and DM are different in definition. EM directly manages the same type of network equipment. For example, EM manages a series of base stations, and DM manages network equipment belonging to equipment vendors (English: vendor), providing domain management. Functional, DM is more manageable than EM. Typically, EM devices are used to perform configuration of network functions. However, in the embodiment of the present invention, the DM may also manage the PNF and/or the VNF. Accordingly, the DM may also perform the steps performed by the EM.
  • Network manager A network-level management module that provides network management functions and management equipment exchanges.
  • NM can be responsible for the distribution, configuration, control, and monitoring of network resources, and NM is supported by EM or DM.
  • Network function virtualized infrastructure (NFVI) module used to deploy virtual network functions (VNF), which can be a set of operating environments consisting of software and hardware, including virtual layers and Abstract hardware resources, etc.
  • VNF virtual network functions
  • NFV-MANO system module It has an interface with NFVI module, VNF module, EM module and NM module for managing virtual network functions at the network level, including the following three modules:
  • NFVO Network function virtualization orchestrator
  • VNFM Virtualized network function manager
  • VIM Virtualized Infrastructure Manager
  • the network management architecture 100 of FIG. 1 can manage physical network functions and virtual network functions. However, it does not enable network slice instances to be managed. Therefore, the network management architecture 100 in FIG. 1 cannot meet the requirements of network slicing technology applications in future communication systems.
  • the embodiment of the present invention introduces a network slice manager and orchestrator (NSM&O) in the network management architecture 100, and manages the process of creating a network slice instance through NSM&O to implement a network slice instance. Automated creation to improve the efficiency of managing network slicing instances.
  • NSM&O network slice manager and orchestrator
  • the network management architecture of the embodiment of the present invention is described below.
  • the embodiment of the present invention introduces an NSM&O module based on the existing network management architecture 100.
  • the structure diagram of the NSM&O module is shown in Figure 2. Its main functions include any of the following:
  • Service conversion The service description information sent by the sender device is received through an interface (for example, an Application Programming Interface (API)), and the service description information is converted into a requirement for the network.
  • API Application Programming Interface
  • Network Slice Design Describes the composition of the network slice based on the results of the service transformation. For example, you can design a network slice template.
  • Network Slice Management Manage the lifecycle of network slicing instances according to a well-designed strategy. For example, it may be network slice instantiation, network slice instance creation, network slice instance scaling, network slice instance update, network slice instance termination, network slice instance deletion, and the like. The details of all network slice instances are available in NSM&O. For example, which network features serve which network tile instances.
  • Network slice orchestration used to specifically determine the network functions and resources used by the network slice instance, including but not limited to computing resources, storage resources, network resources, and the like.
  • KPI Key Performance Indicators
  • the above-mentioned sender device is a device that sends a request to the NSM&O module.
  • the sender device may be an operator, a third party client, an application involved in the communication service, or any other physical device that may send a request to the NSM&O module.
  • the network management architecture in the embodiment of the present invention may further include a storage device, where the storage device is connected to the NSM&O module, and may be used to record information of the generated network slice instance.
  • NSM&O module can be changed as long as the above functions can be implemented.
  • FIG. 3 to FIG. 6 respectively illustrate four network management architectures applied by embodiments of the present invention.
  • the NSM&O modules are included in all four network management architectures.
  • the network management architectures of FIGS. 3 through 6 are hereinafter referred to as network management architecture 300, network management architecture 400, network management architecture 500, and network management architecture 600, respectively.
  • FIG. 3 shows a network management architecture 300 to which an embodiment of the present invention is applied.
  • the network management architecture 300 is a network management architecture that is enhanced and modified based on the network management architecture 100.
  • the network management architecture 300 does not include an NM module, but the NSM&O module performs the functions performed by the NM module in the network management architecture 100.
  • the NSM&O module can include all the functions of the NM module in addition to the functions shown in FIG. 2.
  • the NSM&O module can interact with the EM and/or DM through a communication interface to implement management of network functions corresponding to the network slice instance.
  • the management of the network function includes the management of the PNF module and the VNF module.
  • the NSM&O module can also receive status information of the VNF module from the NFVO module via the communication interface and send commands to the NFVO via the communication interface.
  • the NSM&O module can manage physical network functions, and can utilize the NFVO module to implement resource scheduling management of the NFVI module and implement VNF generation.
  • FIG. 4 illustrates another network management architecture 400 to which an embodiment of the present invention is applied.
  • the network management architecture 400 is also a network management architecture that is enhanced and modified based on the network management architecture 100.
  • the network management architecture 400 is different from the network management architecture 300 in that the network management architecture 300 does not include an NFVO module.
  • the functionality of the NFVO module is implemented by the NSM&O module.
  • the NSM&O module's capabilities include the management of virtual network resources and VNF lifecycle management.
  • the interface can be referred to as an NG2 interface.
  • the NSM&O module and the VNFM module can perform the following interactions through the NG1 interface: support authorization, reservation, allocation, and release of NFVI resources by the VNF; query running status information, such as VNF instance query; VNF initialization update, scaling, Ending, etc.; transmitting VNF related events, status information, etc.
  • the NSM&O module and the VIM module can perform any of the following interactions through the NG2 interface: NFVI resource reservation, allocation, release, etc.; VNF software image (image) addition, deletion, update, etc.; transmission of NFVI-related configuration information, events, measurements Results, upgrade records, etc.
  • the NSM&O module can also manage virtual network functions and the VNF life cycle. Therefore, it is possible to uniformly manage and orchestrate physical and virtual network resources and functions, and optimize resources from a global perspective.
  • FIG. 5 illustrates another network management architecture 500 to which an embodiment of the present invention is applied.
  • the NM module is reserved in the network management architecture 500, and the NSM&O module and the NM module are independent of each other.
  • the communication interface can be referred to as an NG3 interface.
  • the communication interface can be referred to as an NG4 interface.
  • the communication interface can be referred to as an NG4 interface.
  • the communication interface can be referred to as an NG5 interface.
  • the NSM&O module and the NM module can perform the following interactions through the NG3 interface: transmitting the negotiation information between the NSM&O module and the NM module, for example, the NSM&O module queries the VNF that has been generated by the NM module; and the NM module feeds back the generated VNF information to the NSM&O module. And confirm that the NSM&O module is allowed to modify the VNF information; the NSM&O module notifies the NM module which PNF/VNF will be modified; the NSM&O module notifies the NM module of the specific modification of the PNF/VNF.
  • the NSM&O module and the NFVO module can perform the following interactions through the NG4 interface: the NSM&O module participates in VNF lifecycle management through the NG4 interface, for example, notifying the NFVO module to generate, update, and delete a VNF; the NSM&O module queries the NFVO module for VNF and NFVI. Operation information; NFVO module feeds back NNF&O module feedback information about VNF and NFVI; policy management, NSM&O module can send policy to NFVO module, indicating the need for VNF deployment; NSM&O module performs VNF package management through NG4 interface.
  • the NSM&O module and the EM module can communicate with each other through the NG5 interface: the NSM&O module communicates with the EM module through the NG5 interface to manage the PNF and VNF (if the EM supports the management of the VNF).
  • the NSM&O module uses a communication interface to interact with each module.
  • NSM&O modules can be used to orchestrate and manage virtual resources through NFVO modules and participate in VNF lifecycle management.
  • NSM&O modules and NM modules can directly manage PNF.
  • NSM&O modules and NM modules can manage VNF through NFVO modules or EM modules. Therefore, for the management of PNF and VNF, the NSM&O module and the NM module can be coordinated through communication.
  • FIG. 6 illustrates another network management architecture 600 to which an embodiment of the present invention is applied.
  • the NM module is also retained in the network management architecture 600.
  • the NSM&O module and the NM module are also independent of each other.
  • the network management architecture 600 differs from the network management architecture 500 in that the entity of the NFVO module is not included in the network management architecture 600.
  • the functionality of the NFVO module is implemented by the NSM&O module.
  • the NSM&O module's capabilities include the management of virtual network resources and VNF lifecycle management.
  • the communication interface can be referred to as an NG1 interface.
  • the communication interface can be referred to as an NG2 interface.
  • the communication interface can be referred to as an NG5 interface.
  • the NG1 interface, the NG2 interface, and the NG5 interface the same or similar contents in FIG. 4 and FIG. 5 can be referred to. For the sake of brevity, it will not be repeated here.
  • the NSM&O module uses a communication interface to interact with various entity modules.
  • NSM&O modules can be used to orchestrate and manage virtual resources through NFVO modules and participate in VNF lifecycle management.
  • NSM&O modules and NM modules can directly manage PNF. Therefore, for the management of the PNF, the NSM&O module and the NM module can be coordinated by communication.
  • the NSM&O module incorporates the functionality of the NSFO module, the NSM&O module can also directly manage virtual network resources and participate in VNF lifecycle management.
  • the NM module does not manage virtual network resources and VNFs.
  • FIG. 3 to FIG. 6 are only for facilitating the understanding of the embodiments of the present invention, and the embodiments of the present invention are not limited to the specific scenarios illustrated. It will be obvious to those skilled in the art that various modifications and changes can be made without departing from the scope of the embodiments of the present invention.
  • the first network device mentioned herein may be a device including an NSM&O module (hereinafter referred to as "NSM&O")
  • the second network device may be a device including an EM module (hereinafter referred to as "EM") or included
  • EM EM
  • the third network device may be a device including a VNFM module (hereinafter referred to as "VNFM”) or a device including an NFVO module (hereinafter referred to as "NFVO”) or a device including a VIM module (hereinafter referred to as "VIM”
  • the fourth network device may be a device including an NM module (hereinafter referred to as "NM”).
  • the system can implement respective functions by using the first network device, the second network device, the third network device, and the fourth network device, thereby achieving flexible network segmentation instances. management.
  • first network device, the second network device, the third network device, and the fourth network device may be specifically network management devices, which are used for monitoring, managing, and maintaining network elements in network operation and maintenance, but the embodiment of the present invention Not limited to this.
  • FIG. 7 shows a network management method 700 according to an embodiment of the present invention.
  • the method 700 can be applied to the network management architecture 300 shown in FIG. 3, which can be applied to the network management architecture 400 shown in FIG.
  • the network management architecture 500 shown in FIG. 6 can also be applied to the network management architecture 600 shown in FIG.
  • the sending end sends an update request message to the NSM&O, where the update request message is used to request to add the first network function to the first network slice instance, or the foregoing in the first network slice instance.
  • the first network function is deleted; the NSM&O receives the update request message.
  • the NSM&O sends a configuration request message to the EM, where the configuration request message is used to request to configure the first network function in the first network slice instance; the EM receives the configuration request message.
  • Configuring the first network function in the first network slice instance including: adding a first network function on the first network slice instance or deleting the first network function in the first network slice instance .
  • the EM configures the first network function in the first network slice instance according to the configuration request message.
  • Configuring the first network function in the first network slice instance may include: adding a first network function on the first network slice instance or deleting the first network function in the first network slice instance.
  • the EM sends a configuration response message to the NSM&O, where the configuration response message is used to indicate that the first network function is configured in the first network slice instance, and the NSM&O receives the configuration response message.
  • the NSM&O sends an update response message to the sending end according to the configuration response message, where the update response message is used to indicate that the first network function has been added to the first network slice instance, or The first network function in the first network slice instance is deleted.
  • the sending end may send the update request message to the NSM&O through an Application Programming Interface (API), where the update request message is used to request to increase the first network function.
  • API Application Programming Interface
  • the update request message may carry information indicating the network function that needs to be added or deleted, that is, the information of the first network function, which may specifically be the name of the first network function or other identification information.
  • the update request message may also carry information indicating that the network slice instance needs to be added or deleted, that is, the information of the first network slice instance, which may be the identification information of the first network slice instance.
  • the NSM&O after receiving the update request message, the NSM&O sends a configuration request message to the EM, requesting the EM to configure the first network function, so that the first network function starts or stops providing services for the first network slice instance.
  • the configuration request message may include the following configuration parameters: (1) an application specific parameter, such as information of the first network slice instance and information of the first network function.
  • the application parameters may also include a type of the first network slice instance, a monitoring parameter that the first network function needs to detect and report, and the like.
  • Deployment parameters such as network function dependency parameters related to the first network function in the first network slice instance (for example: IP address of the source network function, IP address of the destination network function, etc.).
  • the EM configures the application parameters and deployment parameters of the first network function according to the configuration request message, so that the first network function starts or stops providing services for the first network slice instance. .
  • the network management method in the embodiment of the present invention can add or delete a network function that provides a service for a network sharding instance, and implement the update of the network sharding instance, so that the network sharding instance can better support the change of the service characteristic, thereby improving the user.
  • the original network slice instance does not include the mobility management function.
  • the mobility management function needs to be added to the network slice instance.
  • the original network slice instance includes mobility management function. If all the terminals using the network slice instance have no mobility requirements, the mobility management function can be deleted from the network slice instance.
  • the sender may be an operator, a third-party client, an application involved in the service, or any entity in the service provider domain that may send a request to the NSM&O, which is not limited by the embodiment of the present invention.
  • the sending end may be an NSM&O management device.
  • the NSM&O management device may manage the first NSM&O, the second NSM&O, and the third NSM&O.
  • the NSM&O may be at least one of the first NSM&O, the second NSM&O, and the third NSM&O, that is, the NSM&O management device may separately manage each NSM&O, and send an update request to each NSM&O.
  • the process of updating the network slice instance managed by the first NSM&O, the second NSM&O, and the third NSM&O respectively is the foregoing method 700, and the three NSM&Os may be updated separately in order, or may be updated in parallel.
  • This embodiment of the present invention does not limit this.
  • the NSM&O management device is a total control orchestrator that manages the NSM&O for each domain.
  • a network slice instance may include a core network sub-slice instance and an access network sub-slice instance.
  • a network slice instance can be divided into sub-slice instances provided by multiple different device vendors.
  • a network slice instance can be divided into sub-slice instances provided by multiple different device vendors. This embodiment of the present invention does not limit this.
  • Each subnet slice instance is managed by NSM&O for each domain. After receiving the update request message, the NSM&O management device can determine which sub-network slice instances need to be updated, and then directly notify the corresponding NSM&O to update.
  • the method before the NSM&O sends the configuration request message to the EM, the method further includes: the NSM&O determining whether the first network function is a shared network function. If the first network function is a shared network function, the NSM&O determines to share at least one second network slice instance of the first network function with the first network slice instance. The NSM&O determines whether the second network slice instance is allowed to add or delete the first network function.
  • the NSM&O sends a configuration request message to the EM, including: if the all or part of the second network slice instance allows the first network function to be added or deleted, the NSM&O sends the configuration request message to the EM, and the configuration request message is further
  • the first network function is configured to request the all or part of the second network slice instance that is allowed to add or delete the first network function.
  • configuring the first network function refers to adding or deleting the first network function in the second network slice instance.
  • the NSM&O can also first determine whether the first network function is a shared network function or a dedicated network function. If the first network function is a dedicated network function, that is, only the first network slice instance is served, the NSM&O can directly determine the configuration that needs to perform the first network function. If the first network function is a shared network function, the NSM&O needs to consider whether other network slice instances sharing the network function with the first network slice instance are allowed to add or delete the first network function. Therefore, in the case that the first network function is determined to be a shared network function, the NSM&O may first determine at least one second network slice instance that shares the network function with the first network slice instance, and determine the second network slice instance. Whether the first network function is allowed to be added or deleted, and the configuration of the first network function is performed according to actual conditions.
  • the first network function is a shared network function, and all the second network slice instances allow the first network function to be added, and the NSM&O can directly configure the first network function for all the second network slice instances.
  • the first network function is a shared network function, and a part of the network slice instance of the second network slice instance is allowed to increase the first network function, and another part of the network slice instance is not allowed, the NSM&O may only allow the first network function to be added. This portion of the second network slice instance configures the first network function.
  • the first network function is a dedicated network function, or the first network function is a shared network function, but all the second network slice instances are not allowed to increase the first network function. In both cases, the NSM&O may only The first network function is configured for the first network slice instance.
  • the first network function is a shared network function, and all the second network slice instances are allowed to delete the first network function, and the NSM&O can directly configure the first network function for all the second network slice instances.
  • the first network function is a shared network function, and a part of the network slice instance of the second network slice instance is allowed to delete the first network function, and another part of the network slice instance is not allowed, the NSM&O may only allow deletion of the first network function.
  • the second network slice instance of the portion configures the first network function, and the part of the network slice instance that is not allowed to delete the first network function is still served by the first network function.
  • the first network function is a dedicated network function, or the first network function is a shared network function, but all the second network slice instances are not allowed to delete the first network function. In both cases, the NSM&O may only The first network function is configured for the first network slice instance.
  • the NSM&O may directly The sending end returns an update response message, which is used to indicate that the update fails.
  • the update response message is returned to the sender to indicate that the update fails. This is not limited.
  • the method before the NSM&O sends the configuration request message to the EM, the method further includes: determining, by the NSM&O, whether the first network slice instance and/or all or part of the second network slice instance are dependent on the a second network function of the first network function; if the second network function exists, the NSM&O sends a modification request message to at least one of the EM, the NFVO, and the VIM, the modification request message being used to request to modify the second network function.
  • the source network function and the target network function can be defined.
  • the target network function depends on the source network function, that is, when the target network function is deployed, the source network function must exist. After adding or deleting the first network function, you need to determine whether the corresponding network functions that you depend on need to be modified accordingly.
  • the NSM&O may first determine whether there is a second network function that depends on the first network function in the first network slice instance and/or all or part of the second network slice instance, if yes, The NSM&O can modify the second network function to prevent the addition or deletion of the first network function from affecting the second network function.
  • the NSM&O sends the modification request message to at least one of the EM, NFVO, and VIM.
  • the method further includes: the NSM&O sending a query request message to the storage device, where the query request message is used to query the validity of the update request message.
  • the query request message may carry the identifier of the sending end.
  • the storage device receives the query request message.
  • the storage device performs an inquiry and sends a query response message to the NSM&O, where the query response message is used to indicate whether the update request message is legal.
  • the NSM&O receives the query response message.
  • the NSM&O sends a configuration request message to the EM, including: when the update request message is valid, the NSM&O sends the configuration request message to the EM.
  • the storage device stores the related subscription information of the user and the correspondence between the network slice instance and the user, when the network slice instance is created, or when the user initializes. Therefore, before receiving the update request message sent by the sender, the NSM&O may first send a query request message to the storage device to check whether the update request message is legal. If the update request message is legal, the NSM&O redirects to the EM. Send a configuration request message.
  • the method further includes: the NSM&O sending an update notification message to the storage device, where the update notification message carries the first network
  • the updated information of the first network slice instance may include which network functions the first network slice instance specifically includes and the dependencies between the network functions.
  • the update notification message may also carry all or part of the updated information of the second network slice instance.
  • the storage device receives the update notification message.
  • the storage device stores the update information of the first network slice instance and/or all or part of the second network slice instance, and sends a storage success message to the NSM&O.
  • the NSM&O receives the storage success message.
  • the method before the NSM&O sends the configuration request message to the EM, the method further includes: the NSM&O sending a notification request message to the NM, where the notification request message is used to notify that the first network function is to be configured;
  • the NM receives the notification request message, and sends a notification response message to the NSM&O according to the notification request message; correspondingly, the NSM&O receives the notification response message.
  • the NSM&O and the NM can manage physical network functions and virtual network functions. Therefore, in order to avoid configuration conflicts, coordination between NSM&O and NM is required.
  • the NSM&O may send a notification request message to the NM to notify the network function to be configured, and then perform configuration after receiving the notification response message fed back by the NM.
  • the method further includes: the NSM&O sending network function configuration information to the NM, where the network function configuration information carries the first Configuration parameters for the network function.
  • the NSM&O may send network function configuration information that carries the configuration parameters of the first network function to the NM, so that the NM knows which modifications are made by the NSM&O.
  • FIG. 9 illustrates another network management method provided by an embodiment of the present invention. The method may be applied to the network management architecture 300 shown in FIG. 3, but the embodiment of the present invention is not limited thereto.
  • the sending end sends an update request message to the NSM&O, where the update request message carries the identifier information of the first network slice instance and the identifier information of the first network function, where the update request message is used to request to add the first network function to In the first network slice instance, the first network function in the first network slice instance is deleted.
  • the NSM&O receives the update request message.
  • the NSM&O determines whether the first network function is a shared network function, and if the first network function is a shared network function, determining that the network function is shared with the first network slice instance except the first network slice instance. At least one second network slice instance. The NSM&O may also determine whether there is a second network function in the first network slice instance and/or all or part of the second network slice instance that is dependent on the first network function.
  • the NSM&O sends a query request message to the storage device, where the query request message is used to request whether the update request message is legal.
  • the storage device receives the query request message.
  • the storage device queries and returns a query response message to the NSM&O.
  • the NSM&O receives the query response message.
  • the NSM&O sends an update response message to the sender, where the update response message is used to indicate that the update fails; further, the update response message may also be carried.
  • the reason for the update failure that is, no permission. It should be understood that if the process proceeds to S905, the entire process ends.
  • the NSM&O sends a configuration request message to the EM requesting to configure the first network function.
  • the EM receives the configuration request message accordingly.
  • the specific content of the configuration request message reference may be made to the above description about S702.
  • the EM returns a configuration response message to the NSM&O.
  • NSM&O receives the configuration response message accordingly.
  • the NSM&O sends a modification request message to the EM and/or NFVO, the modification request message is used to request modification of a second network function that depends on the first network function, including but not limited to a connection relationship between network functions and the like.
  • the EM and/or NFVO receives the modification request message and modifies the configuration of the associated network function.
  • the S908 is optional.
  • the NSM&O sends an update notification message to the storage device, where the update notification message carries the updated information of the first network slice instance.
  • the update notification message may also carry updated information of all or part of the second network slice instance.
  • the storage device receives the update notification message.
  • the storage device stores according to the update notification message.
  • the storage device sends a storage success message to the NSM&O, and the NSM&O receives the storage success message.
  • the NSM&O sends an update response message to the sender, where the update response message is used to indicate that the update is successful.
  • the sender receives the update response message.
  • FIG. 10 illustrates another network management method provided by an embodiment of the present invention. The method may be applied to the network management architecture 400 shown in FIG. 4, but the embodiment of the present invention is not limited thereto.
  • S1001-S1007 are the same as S901-S907 in the method 900, and are not described herein again.
  • the NSM&O sends a modification request message to the EM and/or VIM, where the modification request message is used to request to modify other network functions that depend on the first network function, including but not limited to a connection relationship between network functions, etc.;
  • the EM and/or VIM receives the modification request message and modifies the configuration of the associated network function.
  • the S1009-S1010 is the same as the S909-S910 in the method 1100, and details are not described herein again.
  • FIG. 11 illustrates another network management method provided by an embodiment of the present invention. The method may be applied to the network management architecture 500 shown in FIG. 5, but the embodiment of the present invention is not limited thereto.
  • S1101-S1104 are the same as S901-S904, and are not described here.
  • the NSM&O sends a notification request message to the NM to notify that the first network function is to be configured.
  • the NM receives the notification request message.
  • the NM sends a notification response message to the NSM&O according to the notification request message.
  • the NSM&O receives the notification response message.
  • S1107-S1114 is the same as S905-S912 and will not be described here.
  • the NSM&O sends network function configuration information to the NM, where the network function configuration information carries configuration parameters of the first network function; and the NM receives the network function configuration information.
  • FIG. 12 illustrates another network management method provided by an embodiment of the present invention. The method may be applied to the network management architecture 600 shown in FIG. 6, but the embodiment of the present invention is not limited thereto.
  • S1201-S1209 is the same as S1101-S1109, and is not described here.
  • S1210 is the same as S1008, and is not described here.
  • S1211-S1215 is the same as S1111-S1115, and is not described here.
  • a method for managing a network slice instance according to an embodiment of the present invention is described in detail above with reference to FIG. 1 to FIG. 12, and a network slice instance for managing a network according to an embodiment of the present invention will be described in detail below with reference to FIG. 13 to FIG. s installation.
  • FIG. 13 shows an apparatus 1300 for managing a network slice instance provided by an embodiment of the present invention.
  • the apparatus 1300 includes: a receiving unit 1301 and a transmitting unit 1303 that are connected to each other.
  • the sending unit 1303 is configured to send a configuration request message to the second network device.
  • the configuration request message is used to request that the first network function be configured in the first network slice instance.
  • the receiving unit 1301 is configured to receive a configuration response message sent by the second network device.
  • the configuration response message is used to indicate that the first network function is configured in the first network slice instance.
  • the configuring the first network function in the first network slice instance includes: adding a first network function on the first network slice instance or the first one in the first network slice instance A network function is removed.
  • the receiving unit 1301 is further configured to receive an update request message sent by the sending end.
  • the update request message is configured to request to add the first network function to the first network slice instance, or delete the first network function in the first network slice instance.
  • the sending unit 1303 is further configured to send an update response message to the sending end.
  • the update response message is configured to indicate that the first network function has been added to the first network slice instance, or the first network function in the first network slice instance has been deleted.
  • the configuration request message is further configured to request to configure the first network function for all or part of the second network slice instance that is allowed to add or delete the first network function.
  • the sending unit 1303 is further configured to send a query request message to the storage device, where the query request message is used to query the validity of the update request message.
  • the receiving unit 1301 is further configured to receive a query response message sent by the storage device, where the query response message is used to indicate whether the update request message is legal.
  • the sending unit 1303 is further configured to send the configuration request message to the second network device if the update request message is legal.
  • the sending unit 1303 is further configured to send a notification request message to the fourth network device, where the notification request message is used to notify that the first network function is to be configured.
  • the receiving unit 1301 is further configured to receive a notification response message sent by the fourth network device.
  • the sending The unit 1303 is further configured to send, to the at least one of the second network device and the third network device, a modification request message, where the modification request message is used to request to modify the second network function.
  • the sending unit 1303 is further configured to send an update notification message, where the update notification message carries the updated information of the first network slice instance.
  • the receiving unit 1301 is further configured to receive a storage success message sent by the storage device.
  • the sending unit 1303 is further configured to send network function configuration information to the fourth network device, where the network function configuration information carries configuration parameters of the first network function.
  • apparatus 1300 is capable of performing the various steps performed by the NSM&O in the methods of FIGS. 7 and 9-12, and with respect to these steps, to avoid repetition, details are not described herein, and reference may be made to the above description.
  • FIG. 14 shows an apparatus 1400 for managing a network slice instance provided by an embodiment of the present invention.
  • the apparatus 1400 includes a receiving unit 1401, a processing unit 1402, and a transmitting unit 1403.
  • the processing unit 1402 is connected to the receiving unit 1401 and the transmitting unit 1403, respectively.
  • the receiving unit 1401 is configured to receive a configuration request message sent by the first network device.
  • the configuration request message is configured to request to add a first network function on the network slice instance or delete the first network function in the first network slice instance.
  • the processing unit 1402 is configured to configure the first network function.
  • the sending unit 1403 is configured to send a configuration response message to the first network device. The configuration response message is used to indicate that the configuration of the first network function has been completed.
  • the apparatus 1400 is capable of performing the various steps performed by the EM in the methods of FIGS. 7 and 9-12, with respect to which steps are not described herein in order to avoid repetition, reference may be made to the above description.
  • FIG. 15 shows an apparatus 1500 for managing a network slice instance provided by an embodiment of the present invention.
  • the apparatus 1500 includes: a receiving unit 1501 and a transmitting unit 1503 that are connected to each other.
  • the sending unit 1503 is configured to send, to the first network device, an update request message, where the update request message is used to request to add the first network function to the first network slice instance, or the first network The first network function in the slice instance is deleted.
  • the receiving unit 1501 is configured to receive a sending update response message of the first network device, where the update response message is used to indicate that the first network function has been added to the first network slice instance, or the first The first network function in the network slice instance has been deleted.
  • the apparatus 1500 is capable of performing the various steps performed by the transmitting end in the methods of FIGS. 7 and 9-12, and with respect to these steps, to avoid repetition, details are not described herein, and reference may be made to the above description.
  • FIG. 16 shows an apparatus 1600 for managing a network slice instance provided by an embodiment of the present invention.
  • the apparatus 1600 includes a receiving unit 1601, a processing unit 1602, and a transmitting unit 1603.
  • the processing unit 1602 is connected to the receiving unit 1601 and the transmitting unit 1603, respectively.
  • the receiving unit 1601 is configured to receive a notification request message sent by the first network device.
  • the notification request message is used to notify that the first network function is to be configured in the first network slice instance.
  • the processing unit 1602 is configured to determine that the first network device is allowed to configure the first network function.
  • the sending unit 1603 is configured to send a notification response message to the first network device.
  • the receiving unit 1601 is further configured to receive network function configuration information sent by the first network device.
  • the network function configuration information carries configuration parameters of the first network function.
  • the apparatus 1600 is capable of performing the various steps performed by the NM in the methods of FIGS. 11 and 12, with respect to these steps in order to avoid repetition, which will not be described in detail herein, reference may be made to the above description.
  • FIG. 17 shows another apparatus 1700 for managing a network slice instance according to an embodiment of the present invention.
  • the apparatus 1700 includes a processor 1710, a transceiver 1720, and a memory 1730.
  • the processor 1710 is connected to the transceiver 1720 and the memory 1730 for storing instructions.
  • the processor 1710 is configured to execute the instructions stored by the memory 1730 to control the transceiver 1720 to send signals and/or receive signals. .
  • the device 1700 may be specifically the NSM&O in the above embodiment, and may be used to perform the steps corresponding to the NSM&O in the method embodiment shown in FIG. 7, FIG. 9 to FIG.
  • the memory 1730 can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the processor 1710 can be configured to execute instructions stored in the memory, and when the processor 1710 executes the instructions stored in the memory, the processor 1710 is configured to perform the method embodiment shown in FIG. 7, FIG. 9-12 Each step of the NSM&O corresponds to each step of the method embodiment corresponding to the first network device.
  • the device 1700 may be specifically the EM in the above embodiment, and may be used to perform the steps corresponding to the EM in the method embodiment shown in FIG. 7, FIG. 9 to FIG.
  • the memory 1730 can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the processor 1710 can be configured to execute instructions stored in the memory, and when the processor 1710 executes the instructions stored in the memory, the processor 1710 is configured to perform the method embodiment shown in FIG. 7, FIG. 9-12 The steps of the method embodiment corresponding to the EM corresponding to the first network device.
  • the device 1700 may be specifically the transmitting end in the foregoing embodiment, and may be used to perform the steps corresponding to the sending end in the method embodiment shown in FIG. 7 and FIG. 9 to FIG.
  • the memory 1730 can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the processor 1710 can be configured to execute instructions stored in the memory, and when the processor 1710 executes the instructions stored in the memory, the processor 1710 is configured to perform the method embodiment shown in FIG. 7, FIG. 9-12 Each step of the method embodiment corresponding to the first network device corresponding to the first network device.
  • the device 1700 may be specifically the NM in the above embodiment, and may be used to perform various steps corresponding to the NM in the method embodiments shown in FIG. 11 and FIG.
  • the memory 1730 can include read only memory and random access memory and provides instructions and data to the processor.
  • a portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the processor 1710 can be configured to execute instructions stored in the memory, and when the processor 1710 executes the instructions stored in the memory, the processor 1710 is configured to perform the method embodiment shown in FIG. 7, FIG. 9-12
  • Each step of the NM corresponds to each step of the method embodiment corresponding to the first network device.
  • the processor of the foregoing device may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as hardware processor execution completion, or performed by a combination of hardware and software units in the processor.
  • the software unit can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in a memory, and the processor executes instructions in the memory, in combination with hardware to perform the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention contributes in essence or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a USB flash drive, a mobile hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a disk or a CD.
  • ROM Read-Only Memory
  • RAM Random Access Memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Les modes de réalisation de la présente invention concernent un procédé et un appareil de gestion de réseau. Le procédé comprend les étapes suivantes : un premier dispositif de réseau envoie un message de demande de configuration à un second dispositif de réseau, le message de demande de configuration étant utilisé pour demander de configurer une première fonction de réseau au niveau d'une première instance de tranche de réseau ; et le premier dispositif de réseau reçoit un message de réponse de configuration envoyé par le second dispositif de réseau, le message de réponse de configuration étant utilisé pour indiquer que la configuration de la première fonction de réseau sur la première instance de tranche de réseau a été achevée, et la configuration de la première fonction de réseau sur la première instance de tranche de réseau consistant : à ajouter la première fonction de réseau à la première instance de tranche de réseau ou à supprimer la première fonction de réseau dans la première instance de tranche de réseau. Le procédé et l'appareil de gestion de réseau selon les modes de réalisation de la présente invention peuvent ajouter ou supprimer une fonction de réseau pour fournir un service pour une instance de tranche de réseau, pour réaliser une mise à jour de l'instance de tranche de réseau, améliorant ainsi l'expérience utilisateur.
PCT/CN2018/071275 2017-01-05 2018-01-04 Procédé et appareil de gestion de réseau WO2018127068A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710008486.7 2017-01-05
CN201710008486.7A CN108282350A (zh) 2017-01-05 2017-01-05 网络管理方法和装置

Publications (1)

Publication Number Publication Date
WO2018127068A1 true WO2018127068A1 (fr) 2018-07-12

Family

ID=62789165

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/071275 WO2018127068A1 (fr) 2017-01-05 2018-01-04 Procédé et appareil de gestion de réseau

Country Status (2)

Country Link
CN (1) CN108282350A (fr)
WO (1) WO2018127068A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110740477B (zh) * 2018-07-18 2024-02-09 中国移动通信集团重庆有限公司 网络切片信息的管理方法、管理器、设备及介质
CN110972193B (zh) * 2018-09-28 2021-12-03 华为技术有限公司 一种切片信息处理方法及装置
CN113825149B (zh) * 2020-06-18 2024-03-12 中国移动通信集团浙江有限公司 5g切片网元功能自动裁剪方法、装置及计算设备
CN114091679A (zh) * 2020-08-24 2022-02-25 华为技术有限公司 一种更新机器学习模型的方法及通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器
US20160353367A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. System and Method for Virtualized Functions in Control and Data Planes

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160353367A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. System and Method for Virtualized Functions in Control and Data Planes
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on management and orchestration of network slicing for next generation network (Release 14)", 3GPP TR 28.801 V0.3.0, 1 November 2016 (2016-11-01), pages 1 - 24, XP055511272 *

Also Published As

Publication number Publication date
CN108282350A (zh) 2018-07-13

Similar Documents

Publication Publication Date Title
US11032214B2 (en) Method, apparatus, and system for managing network slice instance
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
US11063831B2 (en) Network slice management method and apparatus
JP6463509B2 (ja) 動的仮想化ネットワーク機能記述子管理のためのシステムおよび方法
US20190260636A1 (en) Method and apparatus for managing network slice instance
WO2018127144A1 (fr) Procédé, dispositif et système de gestion d'instance de tranche de réseau
CN115119331A (zh) 用于多接入通信量管理的强化学习
CN106134141B (zh) 一种更新网络服务描述器nsd的方法及装置
WO2018121672A1 (fr) Procédé, dispositif et système de fourniture de service
CN108259193B (zh) 一种网络管理方法、网络管理系统和网元管理系统
WO2018082491A1 (fr) Procédé d'extension d'instance de tranche de réseau, dispositifs de réseau, et architecture de réseau
WO2018058579A1 (fr) Procédé de gestion de tranche de réseau et unité de gestion
US10848366B2 (en) Network function management method, management unit, and system
WO2019056954A1 (fr) Procédé et dispositif de gestion de tranche de réseau
WO2018082487A1 (fr) Procédé, dispositif et système de gestion de tranches de réseau
WO2018127068A1 (fr) Procédé et appareil de gestion de réseau
WO2018090993A1 (fr) Procédé et dispositif de gestion de modèle de tranche de réseau
WO2018000389A1 (fr) Procédé et dispositif de gestion de tranche de réseau
CN109818772A (zh) 一种网络性能保障方法及装置
WO2016058409A1 (fr) Procédé et appareil pour commander une transmission de message, et système de virtualisation de fonction de réseau
CN116614824A (zh) 请求应用功能的方法、装置和系统
WO2020220937A1 (fr) Procédé et dispositif de gestion de politique de sécurité

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18736618

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载