WO2018085973A1 - Procédé de gestion de tranche de réseau, et unité et système - Google Patents

Procédé de gestion de tranche de réseau, et unité et système Download PDF

Info

Publication number
WO2018085973A1
WO2018085973A1 PCT/CN2016/105017 CN2016105017W WO2018085973A1 WO 2018085973 A1 WO2018085973 A1 WO 2018085973A1 CN 2016105017 W CN2016105017 W CN 2016105017W WO 2018085973 A1 WO2018085973 A1 WO 2018085973A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
unit
network service
information
network slice
Prior art date
Application number
PCT/CN2016/105017
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 PCT/CN2016/105017 priority Critical patent/WO2018085973A1/fr
Publication of WO2018085973A1 publication Critical patent/WO2018085973A1/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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5077—Network service management, e.g. ensuring proper service fulfilment according to agreements wherein the managed service relates to simple transport services, i.e. providing only network infrastructure
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications

Definitions

  • the structure of the first unit includes a processor and a communication interface, the processor being configured to support the first unit to perform the corresponding function in the above method.
  • the communication interface is for supporting communication between the first unit and the second unit, the third unit, or other units.
  • the first unit may further include a memory for coupling with the processor, which stores program instructions and data necessary for the first unit.
  • the structure of the third unit includes a processor and a communication interface, the processor being configured to support the third unit to perform the corresponding function in the above method.
  • the communication interface is used to support communication between the third unit and the first unit or other units.
  • the third unit may further include a memory for coupling with the processor, which stores program instructions and data necessary for the third unit.
  • FIG. 1A is a schematic diagram of a network architecture of a MANO of an NFV in the prior art
  • FIG. 5 is a schematic diagram of communication of another network slice management method according to an embodiment of the present invention.
  • FIG. 9A is a schematic block diagram of a first unit according to an embodiment of the present disclosure.
  • FIG. 1B shows a possible network architecture provided by an embodiment of the present invention. The following describes the main network elements in the network architecture:
  • Network Orchestrator (NO) unit its functions include: lifecycle management of network slices, including network slice or network creation, deletion, update, etc. Management of network slice templates, including creation, update, and deletion of network slice templates , activation and deactivation; mapping of network slicing and network functions; coordinating different types of network resources; coordinating network resources provided by different operators and different network providers; and unifying the network equipment provided by different vendors to The network resources provided by different network providers can meet the requirements of the target service; an application program interface (API) is provided externally, and the API interface is used to provide network functions for third parties to implement cross-operator deployment.
  • the network slice orchestrator (NSO) unit or the network slice manager (NSM) unit may be a type of NO. In the embodiment of the present invention, only the NO unit is taken as an example for description.
  • VNFM Virtualized Network Function Manager
  • Embodiments of the present invention provide a network slice management method, and a unit and system based on the method.
  • the method includes: the first unit receives a network slice management request, and the network slice management request carries a network slice descriptor identifier or network slice requirement information, a network slice descriptor identifier or a network slice required The information is used to obtain a network slice descriptor, and the network slice descriptor includes network service requirement information; then, the first unit selects or requests to create a network service instance according to the network service demand message.
  • the foregoing method may be as shown in FIG. 2, and the network service instance is a virtual resource part of a network slice. Therefore, the embodiment of the present invention may enable the first unit to acquire the virtual resource part of the network slice in real time during the network slice creation process, and improve the method. The efficiency of network slice deployment.
  • the first unit may also request the second unit: create a network slice management object and configure network service instance information in the network slice management object. Further, the first unit may further request the second unit: create a network function management object and configure virtual network function instance information in the network function management object.
  • the network orchestration unit may select or request to create a network service instance.
  • the network orchestration unit requests to create a network service instance; in the methods shown in FIG. 6 and FIG. 7, the network orchestration unit selects a network service instance.
  • the solution of the embodiment of the present invention will be further described below with reference to FIG. 3 to FIG. 6.
  • the method shown in FIG. 3 is described by taking the network service requirement information as a network service descriptor as an example; the method shown in FIG. 4 takes the network service requirement information as a network service descriptor identifier as an example for description;
  • the method uses the network service requirement information as the network service feature information or the network slice feature information as an example.
  • the method shown in FIG. 6 uses the network service demand information as the network service instance information and the network service feature information. Or network slice feature information is taken as an example for description.
  • the first unit is a network orchestration unit
  • the second unit is a network management unit
  • the third unit is a network function virtualization orchestration unit
  • the solution of the embodiment of the present invention is performed. description.
  • the network orchestration unit receives a network slice management request.
  • the network slice management request carries a network slice descriptor identifier or network slice requirement information, the network slice descriptor identifier or the network slice requirement information is used to obtain a network slice descriptor, and the network slice descriptor is used to deploy the network, including
  • the type information and deployment information of the network slice is the basis of the network slice lifecycle management. It can also be called a network slice template or a network slice blueprint. It is not limited here.
  • At least one network slice descriptor is preset in the network orchestration unit. If the network slice descriptor request carries the network slice descriptor identifier, the network orchestration unit may directly determine the corresponding network according to the network slice descriptor identifier in the preset network slice descriptor. The slice descriptor, if the network slice management request carries the network slice requirement information, the network orchestration unit may match the corresponding network slice descriptor in the preset network slice descriptor according to the network slice requirement information.
  • the network orchestration unit acquires a network service descriptor.
  • the network orchestration unit sends a fifth creation request to the network function virtualization orchestration unit.
  • the fifth creation request is used to request the network function virtualization orchestration unit to create a network service instance, and the fifth creation request carries the network service descriptor, or the network orchestration unit first uploads the network service descriptor to the network function virtualization orchestration.
  • the unit, the fifth creation request carries the network service descriptor identifier, and the network function virtualization orchestration unit obtains the network service descriptor identifier, and then determines the network service descriptor. It can be understood that the network orchestration unit returns after uploading the network service descriptor.
  • Network service descriptor ID is used to request the network function virtualization orchestration unit to create a network service instance, and the fifth creation request carries the network service descriptor, or the network orchestration unit first uploads the network service descriptor to the network function virtualization orchestration.
  • the unit, the fifth creation request carries the network service descriptor identifier, and the network function virtualization orchestration unit obtains the network service descriptor identifier, and then determines the network service descriptor
  • the network function virtualization orchestration unit creates a network service instance.
  • the network function virtualization orchestration unit creates a network service instance according to the network service descriptor, including a corresponding virtual network function (VNF) instance, a virtual connection (VL, virtualized link) instance or a virtual network function forwarding map (VNF Forward Graph). , VNFFG) instance.
  • VNF virtual network function
  • VL virtual connection
  • VNF Forward Graph virtual network function forwarding map
  • the network service instance information includes corresponding virtual network function instance information, virtual connection function instance information or virtual network function forwarding map instance information.
  • the creation of the network slice management object may include one of the following situations:
  • the first case the network orchestration management unit creates a network slice management object, as shown in section 306, wherein the portion 306 can include portions 306a and 306b.
  • a third scenario the network orchestration unit requests the network management unit for another way of creating a network slice management object, as shown in Section 308, wherein the portion 308 can include portions 308a through 308d.
  • the network orchestration unit may also request the other management unit to create a network slice management object, such as a network element management unit.
  • a network management unit as an example. The description will not be repeated.
  • the network orchestration unit creates a network slice management object.
  • the network orchestration unit may also create a network slice management object before receiving the network service instance information, that is, step 306a may be performed between steps 301-306b, which is not limited thereto.
  • the network orchestration unit configures the network service instance information in the network slice management object.
  • the network orchestration unit configures the network service instance information in the network slice management object, including configuring the network service instance identifier.
  • the network orchestration unit may also create at least one network function management object, and configure the virtual network function instance information in the network function management object, including configuring the virtual network function instance identifier. It can be understood that the network orchestration unit creates the network.
  • the step of the function management object may be performed at any position between the network orchestration unit receiving the network slice management request and the network orchestration unit configuring the virtual network function instance information in the network function management object, which is not limited thereto.
  • the network orchestration unit sends a first creation request to the network management unit.
  • the first creation request is used to request the network management unit to create a network slice management object and configure network service instance information in the network slice management object, where the first creation request carries network service instance information, where the network service instance information may include virtual Network function instance information.
  • the network management unit creates a network slice management object.
  • the network management unit creates a network slice management object according to the first creation request, wherein the network slice includes an application part and a virtual resource part.
  • the network management unit configures the network service instance information in the network slice management object.
  • the network management unit configures the network service instance information in the network slice management object, including configuring the network service instance identifier.
  • the network orchestration unit sends a second creation request to the network management unit.
  • the second creation request is used to request the network management unit to create a network slice management object.
  • step 308a and step 308b are associated with each other.
  • steps 308a and 308b may be performed between steps 301-308c, if the step 308a is performed after step 305, and the create network slice management object request may carry network service instance information.
  • the network management unit creates a network slice management object.
  • Step 308b is similar to step 307b and will not be described again.
  • the first configuration request is used to request the network management unit to configure the network service instance information in the network slice management object.
  • the first configuration request carries network service instance information, where the network service instance information includes virtual network function instance information.
  • the network management unit configures the network service instance information in the network slice management object.
  • Step 308d is similar to step 307c and will not be described again.
  • the network orchestration unit after receiving the network slice management request, the network orchestration unit sends a fourth creation request to the network management unit, where the fourth creation is used to request the network management unit to create a network function management object, and then, in the network orchestration unit, requests to create or select a network service.
  • the network orchestration unit sends a second configuration request to the network management unit, where the second configuration request is used to request the network management unit to configure the virtual network function instance information in the network function management object, and the second configuration request carries the virtual network function instance. information.
  • the network service descriptor includes virtual network function information constituting the network service
  • the virtual network function information includes a virtual network function descriptor or virtual network function requirement information (VNFProfile)
  • the network service instance identifier may be a network service instance ID.
  • the network slice descriptor identifier may be a network slice descriptor ID or a network slice descriptor name
  • the network service descriptor identifier may be a network service descriptor ID or a network service descriptor name
  • the network service instance information is used for Instructing the network service instance
  • the network service instance information may be a network service instance identifier
  • the network service instance information may further include virtual network function instance information, where the virtual network function instance information is used to indicate the virtual network function instance, and the virtual network function instance information It can be a virtual network function instance identifier.
  • the network service descriptor may also be directly carried in the network slice management request, and then, in step 302, the network orchestration unit directly obtains the network slice management request.
  • the network service descriptor, the remaining steps are similar, and will not be described again.
  • the network slice descriptor includes a network service descriptor
  • the network orchestration unit creates a network service instance according to the network service descriptor request, which enriches the implementation manner of the embodiment of the present invention.
  • steps 401-408 wherein steps 406, 407, and 408 are optional steps, and one of the three may be performed.
  • steps 401, 404, and 405 are similar to steps 301, 304, and 305 of FIG. 3, respectively, and are not described again.
  • the network orchestration unit acquires a network service descriptor identifier.
  • the network slice descriptor includes a network service descriptor identifier
  • the network slice descriptor may further include a Flavor identifier, where the Flavor identifier includes a Flavor ID or a Flavor name, and the Flavor identifier is used to distinguish different deployments of the network service.
  • the network slice descriptor may further include a virtual network function descriptor identifier or a virtual network function requirement information identifier, where the virtual network function descriptor identifier includes a virtual network function descriptor ID or a virtual network function descriptor name, and the virtual network function
  • the requirement information identifier includes the virtual network function requirement information ID or the virtual network function requirement information name. The following descriptions are used for the Flavor identifier, the virtual network function descriptor identifier, and the virtual network function requirement information identifier, which are not described herein.
  • the network orchestration unit may determine the network service descriptor identifier from the network slice descriptor.
  • the network orchestration unit sends a network service instance creation request to the network function virtualization orchestration unit.
  • the network service instance request carries the network service descriptor identifier
  • the Flavor identifier may be carried
  • the network function virtualization orchestration unit may determine the network service descriptor according to the network service descriptor identifier.
  • the creation of the network slice management object may include one of the following situations:
  • the first case the network orchestration management unit creates a network slice management object, as shown in section 406, where portion 406 can include portions 406a and 406b.
  • the second case the network orchestration unit requests the network management unit to create a network slice management object, as shown in part 407, wherein the 407 part may include the 407a part to the 407c part.
  • a third scenario the network orchestration unit requests the network management unit for another way of creating a network slice management object, as shown in section 408, where portion 408 can include portions 408a through 408d.
  • part 406, part 407 and part 408 are respectively associated with part 306 of Figure 3, Section 307 is similar to Section 308 and will not be repeated.
  • the network orchestration unit may also create at least one network function management object, and configure virtual network function instance information in the network function management object, including configuring the virtual network function instance.
  • Identification it can be understood that the step of creating a network function management object by the network orchestration unit can be performed at any position between the network scheduling unit receiving the network slice management request and the network orchestration unit configuring the virtual network function instance information in the network function management object. There is no limit here.
  • the network orchestration unit may send a third creation request to the network management unit, where the third creation request is used to request the network.
  • the management unit creates a network function management object and configures virtual network function instance information in the network function management object, and the third creation request carries the virtual network function instance information.
  • the network orchestration unit after receiving the network slice management request, sends a fourth creation request to the network management unit, where the fourth creation is used to request the network management unit to create a network function management object, and then, after the network orchestration unit receives the network service instance information, The network scheduling unit sends a second configuration request to the network management unit, where the second configuration request is used to request the network management unit to configure the virtual network function instance information in the network function management object, and the second configuration request carries the virtual network function instance information.
  • the network service descriptor identifier may be directly carried in the network slice management request, and then, in step 402, the network orchestration unit directly obtains the network service descriptor in the network slice management request.
  • the logo, the remaining steps are similar, and will not be described again.
  • the network slice descriptor includes a network service descriptor identifier, which enriches the implementation manner of the embodiment of the present invention.
  • the network orchestration unit acquires network service feature information or network slice feature information.
  • the network slice descriptor includes the network service feature information or the network slice feature information, where the network service feature information includes a type of the network service, a specification of the network service, and the network slice feature information includes a network slice type, a function, and a specification, where The network service feature information and the network slice feature information are the same description, and will not be described again.
  • the network orchestration unit determines the network service feature information or the network slice feature information from the network slice descriptor, and then obtains the network service descriptor identifier according to the network service feature information or the network slice feature information. For example, the network orchestration unit may be based on the type of the network service. Matching the type of the network service in the network service descriptor to determine the network service descriptor identifier, or the network orchestration unit matches the function in the network slice descriptor according to the function of the network slice, thereby determining the network service descriptor identifier In addition, the network orchestration unit may also obtain a Flavor identifier, a virtual network function descriptor identifier, or a virtual network function requirement information identifier.
  • the creation of the network slice management object may include one of the following situations:
  • the first case the network orchestration management unit creates a network slice management object, as shown in section 506, wherein the portion 506 can include portions 506a and 506b.
  • the second case the network orchestration unit requests the network management unit to create a network slice management object, as shown in section 507, wherein the 507 part may include the 507a part to the 507c part.
  • a third scenario the network orchestration unit requests the network management unit for another way of creating a network slice management object, as shown in section 508, wherein portion 508 can include portions 508a through 508d.
  • the 506 part, the 507 part and the 508 part are similar to the 306 part, the 307 part, and the 308 part of FIG. 3, respectively, and are not described again.
  • the network orchestration unit may also create at least one network function management object, and configure virtual network function instance information in the network function management object, including configuring the virtual network function instance.
  • Identification it can be understood that the step of creating a network function management object by the network orchestration unit can be performed at any position between the network scheduling unit receiving the network slice management request and the network orchestration unit configuring the virtual network function instance information in the network function management object. There is no limit here.
  • the network orchestration unit may send a third creation request to the network management unit, where the third creation request is used to request the network.
  • the management unit creates a network function management object and configures virtual network function instance information in the network function management object, and the third creation request carries the virtual network function instance information.
  • the network orchestration unit after receiving the network slice management request, sends a fourth creation request to the network management unit, where the fourth creation is used to request the network management unit to create a network function management object, and then, after the network orchestration unit receives the network service instance information, The network scheduling unit sends a second configuration request to the network management unit, where the second configuration request is used to request the network management unit to configure the virtual network function instance information in the network function management object, and the second configuration request carries the virtual network function instance information.
  • the network service feature information or the network slice feature information may be directly carried in the network slice management request, and correspondingly, in step 502, the network orchestration unit is directly in the network.
  • the network service feature information or the network slice feature information is obtained in the slice management request, and the remaining steps are similar and will not be described again.
  • the network slice descriptor includes the network service feature information or the network slice feature information, which enriches the implementation manner of the embodiment of the present invention.
  • the method shown in FIG. 6 includes:
  • the network orchestration unit receives a network slice management request.
  • Step 601 is similar to step 301 of FIG. 3 and will not be described again.
  • the network orchestration unit acquires network service instance information, network service feature information, or network slice feature information.
  • the network slice descriptor includes network service instance information, network service feature information or network slice feature information.
  • the network orchestration unit determines the network service instance information from the network slice descriptor. It should be noted that the network service instance information may be the network service instance identifier. Similarly, if the network slice descriptor includes the network service feature information or the network slice feature information, the network service feature information or the network slice feature information may be respectively obtained from the network slice descriptor.
  • the network orchestration unit selects a network service instance.
  • the network orchestration unit can obtain the network service instance directly on the live network according to the network service instance information.
  • the network orchestration unit may determine the network service instance information according to the network service feature information or the network slice feature information, for example, the network orchestration unit may be according to the network.
  • the type of service matches the type of network service in the network service instance to determine the network service instance information, or
  • the network programming unit matches the functions of the network slice according to the functions in the network service instance to determine the network service instance information, which is not limited here.
  • the creation of the network slice management object may include one of the following situations:
  • the first case the network orchestration management unit creates a network slice management object, as shown in the 604 portion, wherein the 604 portion can include the 604a portion and the 604b portion.
  • the second case the network orchestration unit requests the network management unit for a way to create a network slice management object, as shown in part 605, wherein the 605 part may include parts 605a to 605c.
  • a third scenario the network orchestration unit requests the network management unit for another way of creating a network slice management object, as shown in section 606, wherein the portion 606 can include portions 606a through 606d.
  • 604 part, 605 part and 606 part are optional parts, and any one of them can be executed.
  • the 604 part, the 605 part and the 606 part are similar to the 306 part, the 307 part, and the 308 part of FIG. 3, respectively, and are not described again.
  • the network orchestration unit may also create at least one network function management object, and configure virtual network function instance information in the network function management object, including configuring the virtual network function instance.
  • Identification it can be understood that the step of creating a network function management object by the network orchestration unit can be performed at any position between the network scheduling unit receiving the network slice management request and the network orchestration unit configuring the virtual network function instance information in the network function management object. There is no limit here.
  • the network orchestration unit may send a third creation request to the network management unit, where the third creation request is used to request the network.
  • the management unit creates a network function management object and configures virtual network function instance information in the network function management object, and the third creation request carries the virtual network function instance information.
  • the network orchestration unit after receiving the network slice management request, the network orchestration unit sends a fourth creation request to the network management unit, where the fourth creation is used to request the network management unit to create a network function management object, and then, after the network orchestration unit receives the network service instance information, The network orchestration unit sends a second configuration request to the network management unit, where the second configuration request is used to request the network management unit to manage the network function object
  • the virtual network function instance information is configured, and the second configuration request carries the virtual network function instance information.
  • the network service instance information, the network service feature information, or the network slice feature information may be directly carried in the network slice management request, and correspondingly, in step 602, the network The orchestration unit obtains the corresponding network service instance information, the network service feature information or the network slice feature information directly in the network slice management request, and the remaining steps are similar and will not be described again.
  • the network slice descriptor includes network service instance information, network service feature information or network slice feature information
  • the network orchestration unit may directly select a network service instance in the live network, thereby improving processing efficiency.
  • the network scheduling unit or the network management unit creates a network slice management object and configures the network service instance information.
  • the network orchestration unit may also be in the network service. Configure the application parameters of the network slice in the instance. This will be described below with reference to FIGS. 7 and 8.
  • the first unit is a network orchestration unit
  • the third unit is a network function virtualization orchestration unit. The solution of the embodiment of the present invention is described.
  • FIG. 7 illustrates an embodiment of an application parameter of a network orchestration unit configuring a network slice in a network service instance.
  • the method shown in Figure 7 includes:
  • the network orchestration unit receives a network slice management request.
  • Step 701 is similar to step 301 of FIG. 3 and will not be described again.
  • the network orchestration unit selects a network service instance according to the network service requirement information in the network slice descriptor.
  • the network slice descriptor includes the network service requirement information, and the network orchestration unit determines the network service requirement information from the network slice descriptor.
  • the network service requirement information is the network service instance information, and the network service feature information is used.
  • the network slice feature information specifically, the step of the network orchestration unit selecting the network service instance according to the network service requirement information is similar to the step 603 of FIG. 6 and will not be described again.
  • the network orchestration unit configures application parameters of the network slice in the network service instance.
  • the application parameters of the network slice may be configured in the network service instance, and the application parameters of the network slice are service-related parameters, including service policies and routing rules, which are not limited herein.
  • the network slice management request may also directly carry the network service.
  • the network orchestration unit can directly obtain the network service requirement information in the network slice management request, and does not need to extract the network service requirement information in the network slice descriptor. The remaining steps are similar and will not be described again.
  • the network orchestration unit selects the network service instance according to the network service requirement information in the network slice descriptor, and configures the network slice application parameter in the network service instance, without relying on other network elements, thereby improving the processing efficiency.
  • FIG. 8 illustrates another embodiment of a network programming unit configuring an application parameter of a network slice in a network service instance.
  • the method shown in FIG. 8 includes:
  • the network orchestration unit receives a network slice management request.
  • Step 801 is similar to step 301 of FIG. 3 and will not be described again.
  • the network orchestration unit requests to create a network service instance according to the network service requirement information in the network slice descriptor.
  • the network slice descriptor includes network service requirement information, and the network orchestration unit determines network service demand information from the network slice descriptor.
  • the network orchestration unit sends a fifth creation request to the network function virtualization orchestration unit, and the fifth creation request is used to request the network function virtualization orchestration unit to create a network service instance,
  • the fifth creation request carries the network service descriptor. This step is similar to step 303 of FIG. 3 .
  • the network orchestration unit receives the network service instance information sent by the network function virtualization orchestration unit. This step is similar to step 305 of FIG. 3 . No longer.
  • the network orchestration unit sends a fifth creation request to the network function virtualization orchestration unit, and the fifth creation request is used to request the network function virtualization orchestration unit to create a network service instance, and the fifth creation is performed.
  • the request carries the network service descriptor identifier.
  • This step is similar to step 403 of FIG. 4, and the network orchestration unit receives the network service instance information sent by the network function virtualization orchestration unit. This step is similar to step 405 of FIG. Let me repeat.
  • the network orchestration unit acquires the network service descriptor identifier according to the network service feature information or the network slice feature information, and the network orchestration unit sends the fifth creation to the network function virtualization orchestration unit.
  • the request, the fifth creation request is used to request the network function virtualization orchestration unit to create a network service instance, and the fifth creation request carries the network service descriptor identifier.
  • the step is similar to step 503 of FIG. 5, and the network orchestration unit receives the network function virtualization orchestration.
  • the network service instance information sent by the unit is similar to the step 505 of FIG. 5 and will not be described again.
  • the network orchestration unit configures application parameters of the network slice in the network service instance.
  • Step 803 is similar to step 703 of FIG. 7 and will not be described again.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Selon certains modes de réalisation, la présente invention concerne un procédé de gestion de tranche de réseau, et une unité et un système basés sur le procédé. Selon un mode de réalisation de la présente invention, le procédé comprend les étapes suivantes : une première unité reçoit une demande de gestion de tranche de réseau, la demande de gestion de tranche de réseau transportant un identifiant de descripteur de tranche de réseau ou des informations de demande de tranche de réseau, l'identifiant de descripteur de tranche de réseau ou les informations de demande de tranche de réseau étant utilisées pour obtenir un descripteur de tranche de réseau, et le descripteur de tranche de réseau comprenant des informations de demande de service de réseau ; et la première unité sélectionne ou crée une instance de service de réseau selon les informations de demande de service de réseau. Au moyen de la solution fournie dans les modes de réalisation de la présente invention, l'efficacité de déploiement de tranche de réseau peut être améliorée.
PCT/CN2016/105017 2016-11-08 2016-11-08 Procédé de gestion de tranche de réseau, et unité et système WO2018085973A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/105017 WO2018085973A1 (fr) 2016-11-08 2016-11-08 Procédé de gestion de tranche de réseau, et unité et système

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/105017 WO2018085973A1 (fr) 2016-11-08 2016-11-08 Procédé de gestion de tranche de réseau, et unité et système

Publications (1)

Publication Number Publication Date
WO2018085973A1 true WO2018085973A1 (fr) 2018-05-17

Family

ID=62109026

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/105017 WO2018085973A1 (fr) 2016-11-08 2016-11-08 Procédé de gestion de tranche de réseau, et unité et système

Country Status (1)

Country Link
WO (1) WO2018085973A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112087780A (zh) * 2019-06-14 2020-12-15 中国电信股份有限公司 Ims服务提供方法、系统和网络侧服务提供系统
CN112838942A (zh) * 2019-11-25 2021-05-25 中兴通讯股份有限公司 网络运维方法、电子设备以及存储介质
CN113300881A (zh) * 2021-04-23 2021-08-24 北京邮电大学 基于5g网络的编排调度方法、装置、设备及存储介质
WO2021219233A1 (fr) * 2020-04-30 2021-11-04 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de réseau
WO2022237255A1 (fr) * 2021-05-14 2022-11-17 华为技术有限公司 Procédé et système de gestion pour nœud de calcul
CN117544514A (zh) * 2024-01-09 2024-02-09 上海卫星互联网研究院有限公司 网络切片方法、装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014205786A1 (fr) * 2013-06-28 2014-12-31 华为技术有限公司 Procédé et appareil d'enregistrement et de mise en œuvre de service d'envoi à la cantonade, et dispositif et système de commutation
CN104639653A (zh) * 2015-03-05 2015-05-20 北京掌中经纬技术有限公司 基于云架构的自适应方法及系统
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014205786A1 (fr) * 2013-06-28 2014-12-31 华为技术有限公司 Procédé et appareil d'enregistrement et de mise en œuvre de service d'envoi à la cantonade, et dispositif et système de commutation
CN104639653A (zh) * 2015-03-05 2015-05-20 北京掌中经纬技术有限公司 基于云架构的自适应方法及系统
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112087780A (zh) * 2019-06-14 2020-12-15 中国电信股份有限公司 Ims服务提供方法、系统和网络侧服务提供系统
CN112087780B (zh) * 2019-06-14 2022-08-30 中国电信股份有限公司 Ims服务提供方法、系统和网络侧服务提供系统
CN112838942A (zh) * 2019-11-25 2021-05-25 中兴通讯股份有限公司 网络运维方法、电子设备以及存储介质
WO2021219233A1 (fr) * 2020-04-30 2021-11-04 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de réseau
US11824708B2 (en) 2020-04-30 2023-11-21 Telefonaktiebolaget Lm Ericsson (Publ) Network management
CN113300881A (zh) * 2021-04-23 2021-08-24 北京邮电大学 基于5g网络的编排调度方法、装置、设备及存储介质
CN113300881B (zh) * 2021-04-23 2022-08-05 北京邮电大学 基于5g网络的编排调度方法、装置、设备及存储介质
WO2022237255A1 (fr) * 2021-05-14 2022-11-17 华为技术有限公司 Procédé et système de gestion pour nœud de calcul
CN117544514A (zh) * 2024-01-09 2024-02-09 上海卫星互联网研究院有限公司 网络切片方法、装置
CN117544514B (zh) * 2024-01-09 2024-05-17 上海卫星互联网研究院有限公司 网络切片方法、装置

Similar Documents

Publication Publication Date Title
WO2018085973A1 (fr) Procédé de gestion de tranche de réseau, et unité et système
EP3595244B1 (fr) Procédé, unité et système de gestion de tranche de réseau
US10999740B2 (en) Network slice management method, management unit, and system
WO2018058579A1 (fr) Procédé de gestion de tranche de réseau et unité de gestion
US10541877B2 (en) Dynamic reservation protocol for 5G network slicing
CN108243106B (zh) 控制网络切片的方法、转发设备、控制设备和通信系统
WO2018171459A1 (fr) Procédé et dispositif de gestion de tranche de réseau
WO2018006381A1 (fr) Procédé, appareil et système de gestion de ressource de réseau
WO2016155394A1 (fr) Procédé et dispositif pour établir une liaison entre des fonctions réseau virtualisées
WO2018001049A1 (fr) Procédé, dispositif et système de déploiement de fonction de réseau virtuelle utilisant le calcul en périphérie de réseau
CN108370368B (zh) 安全策略部署方法与装置
US20160294643A1 (en) System and method for service orchestration in distributed cloud environment
US20190281503A1 (en) Management Method, Management Unit, and System
EP3637687B1 (fr) Procédé d'orchestration de réseau défini par logiciel et contrôleur sdn
EP3163975A1 (fr) Procédé de gestion d'informations de configuration, dispositif, système de gestion d'élément de réseau et support de stockage
WO2017162089A1 (fr) Procédé et dispositif de configuration de service pour service de réseau
WO2019127418A1 (fr) Procédé de gestion de service de réseau, dispositif et système associés
JP2018530214A (ja) ネットワークサービスをデプロイするための方法及び装置
WO2018072503A1 (fr) Procédé d'initiation de modification de logiciel, procédé et dispositif de publication de métadonnées
EP3257212A1 (fr) Mécanisme de sécurité pour réseaux hybrides
WO2019091439A1 (fr) Procédé, dispositif et terminal de génération de tranches de réseau
US20200260288A1 (en) Communication method and communications apparatus
EP3883183A1 (fr) Procédé et dispositif de gestion de virtualisation
US10469402B2 (en) Dynamic endpoint group binding for cross-tenant resource sharing in software defined networks
CN111416732B (zh) 一种sdn中网络设备扩容自动配置业务的方法及装置

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

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

Country of ref document: EP

Kind code of ref document: A1