WO2019062456A1 - 网络的部署信息确定方法及设备 - Google Patents

网络的部署信息确定方法及设备 Download PDF

Info

Publication number
WO2019062456A1
WO2019062456A1 PCT/CN2018/103081 CN2018103081W WO2019062456A1 WO 2019062456 A1 WO2019062456 A1 WO 2019062456A1 CN 2018103081 W CN2018103081 W CN 2018103081W WO 2019062456 A1 WO2019062456 A1 WO 2019062456A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
information
deployment information
deployment
template
Prior art date
Application number
PCT/CN2018/103081
Other languages
English (en)
French (fr)
Inventor
许瑞岳
张凯
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019062456A1 publication Critical patent/WO2019062456A1/zh
Priority to US16/831,293 priority Critical patent/US11356939B2/en
Priority to US17/831,725 priority patent/US11844017B2/en

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/085—Retrieval of network configuration; Tracking network configuration history
    • 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/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • 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
    • 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/0893—Assignment of logical groups to network elements
    • 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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • 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/5048—Automatic or semi-automatic definitions, e.g. definition templates
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/04—Traffic adaptive resource partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • 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/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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/0894—Policy-based network configuration management
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a network deployment information determining method and device.
  • a network slice is a communication resource that ensures that a bearer service can meet a service level agreement (SLA) requirement. These resources can be hard isolated (that is, physically isolated) or logically isolated (that is, soft isolated).
  • SLA service level agreement
  • a network slice can be thought of as a combination of network functions and resources required to complete a certain service or services, and is a complete logical network.
  • the network management device can calculate the deployment information of the network slice according to the network slice requirement information when receiving the network slice requirement information.
  • a network service descriptor is a template used by vendors to deploy network services.
  • An NSD can contain different deployment flavors.
  • the deployment information of the network slice may include information such as an identifier of the network slice template NSD, an identity of the NSD deployment specification, and an instantiation level.
  • the network management device may send an instantiation request carrying the deployment information of the network slice to the management and orchestration device, and the management and orchestration device instantiates according to the deployment information of the network slice.
  • the network slice template may include multiple network slice subnets.
  • the algorithm for calculating the network slice deployment information according to the network slice requirement information in different network slice subnets is different, the network management device cannot be based on the received network slice requirement. The information is accurately calculated to obtain the deployment information of the network slice, thereby reducing the accuracy of determining the deployment information of the network.
  • the embodiment of the present application provides a network deployment information determining method and device.
  • the deployment information sent to the management and orchestration device includes more comprehensive deployment information, thereby It can improve the accuracy of the network deployment information determination.
  • the embodiment of the present application provides a method for determining deployment information of a network, where the first network entity receives a first message sent by a second network entity, where the first message carries first deployment information, where a deployment information is deployment information of the network component; the first network entity determines second deployment information according to the first deployment information, the second deployment information is deployment information of the network, and the network includes at least one of the networks Component.
  • the first network entity may receive deployment information of multiple network components, and obtain complete network deployment information according to the deployment information of the multiple network components.
  • the deployment information includes the association relationship between the various network components, and includes more comprehensive deployment information in the deployment information sent to the management and orchestration device, which can improve the accuracy of the network deployment information determination.
  • the determining, by the first network entity, the second deployment information, according to the first deployment information includes: determining, by the first network entity, the second deployment from a network template according to the first deployment information.
  • the network template includes deployment information of at least one network.
  • the network template containing the deployment information of the network may be pre-stored in the database for the first network entity to invoke.
  • the deployment information of the network acquired by the first network entity includes more comprehensive deployment information, which can improve the accuracy of the network deployment information. Sex.
  • the method before the first network entity receives the first message sent by the second network entity, the method further includes: the first network entity sending a second message to the second network entity, The second message carries the requirement information of the network component and the identifier of the network component template, and the requirement information of the network component and the identifier of the network component template are used to determine the first deployment information.
  • the method before the first network entity sends the second message to the second network entity, the method further includes: the first network entity acquiring the identifier of the network component template according to the network template; The first network entity will obtain the demand information of the network component according to the demand information of the network.
  • the first deployment information includes at least one of the following: a virtual resource descriptor identifier corresponding to the network component, a virtual resource deployment specification corresponding to the network component, and a virtual resource instance corresponding to the network component.
  • the second deployment information includes at least one of the following: a virtual resource descriptor corresponding to the network, a virtual resource deployment specification corresponding to the network, a virtual resource instantiation level corresponding to the network, and affinity and anti-affinity of the virtual resource deployment corresponding to the network, The deployment location constraint information of the virtual resource corresponding to the network.
  • the network component is a network slice subnet
  • the network component template is a network slice subnet template
  • the network is a network slice.
  • the network management device can receive the deployment information of multiple network slice subnets or the deployment information of the network function, and obtain the complete network slice deployment information according to the deployment information of the multiple network slice subnets or the deployment information of the network function.
  • the deployment information of the slice includes the deployment information of each network slice subnet or the association relationship between the network functions.
  • the deployment information sent to the management and orchestration device includes more comprehensive deployment information, which can improve the deployment information of the network slice. accuracy.
  • the network component is a network function
  • the network component template is a network function template
  • the network is a network slice or a network slice subnet.
  • the network management device or the domain management device can receive the deployment information of the multiple network functions, and obtain the complete network slice deployment information or the network slice subnet deployment information and the network slice deployment information according to the deployment information of the multiple network functions.
  • the deployment information of the network slice subnet includes the association relationship between the network functions, and the deployment information sent to the management and orchestration device includes more comprehensive deployment information, which can improve the accuracy of the network deployment information determination.
  • the method further includes: the first network entity sending, by the first network entity, the second deployment The third message of the message.
  • the embodiment of the present application provides another method for determining deployment information of a network, where the second network entity receives a second message sent by a first network entity, where the second message carries network component demand information and a network.
  • An identifier of the component template where the second network entity determines the first deployment information according to the network component template corresponding to the network component template and the identifier of the network component template, where the first deployment information is the deployment information of the network component.
  • the second network entity sends a first message to the first network entity, where the first message carries the first deployment information.
  • the first network entity may receive deployment information of multiple network components, and obtain complete network deployment information according to the deployment information of the multiple network components.
  • the deployment information includes the association relationship between the various network components, and includes more comprehensive deployment information in the deployment information sent to the management and orchestration device, which can improve the accuracy of the network deployment information determination.
  • the network component template includes deployment information of at least one network component; the second network entity determines the first according to the network component template corresponding to the network component's requirement information and the identifier of the network component template.
  • the deployment information includes: the second network entity determining the first deployment information from the deployment information of the at least one network component according to the requirement information of the network component.
  • the first deployment information includes at least one of the following: a virtual resource descriptor identifier corresponding to the network component, a virtual resource deployment specification corresponding to the network component, and a virtual resource instance corresponding to the network component.
  • the network component is a network slice subnet
  • the network component template is a network slice subnet template
  • the network is a network slice.
  • the network component is a network function
  • the network component template is a network function template
  • the network is a network slice or a network slice subnet.
  • the method further includes: when the second network entity detects that the network component meets a preset condition, the second network entity determines third deployment information according to the preset condition, where The third deployment information is the deployment information of the network component; the preset condition includes at least one of the following: the number of users carried on the network component is greater than a preset threshold, or the second network entity is detected to be faulty.
  • the second network entity sends a fourth message carrying the third deployment information to the first network entity. For example, when the second network entity fails, the second network entity may generate third deployment information according to the related fault information, and then send the information to the first network entity. At this time, the first network entity deploys the network according to the third deployment information.
  • the embodiment of the present application provides a network entity, where the network entity includes a module or a unit for performing a deployment information determining method of a network provided by the first aspect or any possible implementation manner of the first aspect.
  • the embodiment of the present application provides another network entity, where the network entity includes a module or unit for performing a deployment information determining method of a network provided by the second aspect or any possible implementation manner of the second aspect. .
  • the embodiment of the present application provides another network entity, including: a processor, a memory, a transceiver, and a bus; a processor, a transceiver, and a memory communicate with each other through a bus; and a transceiver for receiving and transmitting data;
  • the memory is used to store instructions; the processor is configured to invoke instructions in the memory, and execute the deployment information determining method of the network provided by the first aspect or any possible implementation manner of the first aspect.
  • the embodiment of the present application provides another network entity, including: a processor, a memory, a transceiver, and a bus; a processor, a transceiver, and a memory communicate with each other through a bus; and a transceiver for receiving and transmitting data;
  • the memory is used to store instructions; the processor is configured to invoke instructions in the memory, and execute the deployment information determining method of the network provided by any one of the possible implementations of the second aspect or the second aspect.
  • the embodiment of the present application provides a computer readable storage medium, where the storage medium includes instructions, when the instruction is run on a network entity, causing the network entity to perform any of the first aspect or the first aspect The method for determining the deployment information of the network provided by the implementation.
  • the embodiment of the present application provides another computer readable storage medium, where the storage medium includes instructions, when the instruction is run on a network entity, causing the network entity to perform any one of the second aspect or the second aspect A method of determining the deployment information of the network provided by the possible implementation.
  • the embodiment of the present application provides a computer program, where the computer program includes instructions, when the instruction is run on a network entity, causing the network entity to perform the first aspect or any possible implementation manner of the first aspect.
  • the method of determining the deployment information of the provided network is not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to the instruction.
  • the embodiment of the present application provides another computer program, where the computer program includes instructions, when the instruction is run on a network entity, causing the network entity to perform any of the possible implementations of the second aspect or the second aspect.
  • a method of determining deployment information for the provided network is provided.
  • the embodiment of the present application provides a chip product of a network entity, to perform the method in the first aspect or any possible implementation manner of the first aspect.
  • the embodiment of the present application provides a chip product of another network entity to perform the method in the second aspect or any possible implementation manner of the second aspect.
  • the first network entity associated with the network template decomposes the network requirement information into the network component requirement information, and the network component template identifier and the network component are The demand information is sent to the second network entity associated with the network component.
  • the second network entity obtains the deployment information of the network component according to the received network component template identifier and the network component's requirement information, and sends the deployment information of the network component to the first network entity.
  • the first network entity may receive deployment information of multiple network components, and obtain complete network deployment information according to the deployment information of the multiple network components.
  • the deployment information includes the association relationship between the various network components, and includes more comprehensive deployment information in the deployment information sent to the management and orchestration device, which can improve the accuracy of the network deployment information determination.
  • FIG. 1 is a schematic structural diagram of a network system according to an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of an NST and an NSST according to an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a method for determining deployment information of a network provided by the prior art
  • FIG. 4 is a schematic flowchart of a method for determining deployment information of a network according to an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of another NST and NSST provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of an NSST and an NFT according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of an NST and an NFT according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a network entity 10 according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a network entity 20 according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of another network entity 10 according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of another network entity 20 according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a device according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of another apparatus according to an embodiment of the present invention.
  • a network slice refers to a different logical network that is customized according to different service requirements.
  • a network slice can be thought of as a combination of network functions and resources required to complete a certain service or services, and is a complete logical network.
  • the network slice can be an end-to-end network including a terminal, an access network (AN), a transport network (TN), a core network (CN), and an application server, and can provide complete telecommunications. Service, with certain network capabilities.
  • the network slice may also be any combination of the above terminal, access network, transport network, core network, and application server.
  • Different network slices can be hard-isolated according to different requirements, that is, physical isolation, or soft isolation, that is, logical isolation.
  • the network slice can be a generalized concept.
  • the traditional network or the dedicated network can be used as a network slice.
  • the network slice subnet can also be considered as a network slice.
  • the network service can be implemented by multiple virtualized network functions (VNFs).
  • VNFs virtualized network functions
  • the network service can be considered as the underlying virtual resource corresponding to the network slice. Therefore, when the network slice is deployed, the corresponding network needs to be instantiated.
  • Internet service A network service descriptor (NSD) is a template used by vendors to deploy network services. An NSD can contain different deployment flavors.
  • Different network service descriptors can be distinguished by the NSD identifier (such as the NSD ID), and the NSD deployment specification identifier (such as the deployment specification ID) can be used to distinguish different specifications of the network service in the same network service description, the NSD identifier and The identification of the deployment specification of the NSD
  • the uniquely determined network service may be referred to as a virtual resource of a network slice template or a virtual resource of a network slice subnet template.
  • the network slice template (NST) is generated when the network is designed and planned offline. You can select the corresponding features based on the characteristics of the specific services that are expected to run on the network slice, including the required functions, performance, security, reliability, service experience, and operation and maintenance features. After the design is complete, the slice template is generated. The network slice template after the offline design is completed can be instantiated online as a network slice instance. Designing multiple deployments at a time is the principle of a network slice template.
  • a network slice template (NSST) and/or a network function template (NFT) can be nested in the network slice template.
  • Nested means that a network slice template can be composed of one or more
  • a network slice subnet template or a network function template may also be a network slice template that includes an identifier of one or more network slice subnet templates or an identifier of a network function template, where the identifier indicates a network slice subnet template or network function. template.
  • network function templates can also be nested in the network slice subnet template.
  • a network slice subnet template or a network function template nested in a network slice template may be collectively referred to as a network component template, and a corresponding network slice template composed of a network slice subnet template and/or a network function template may be referred to as a network. template.
  • a network function template that is nested in a network slice subnet template or a network slice template may be referred to as a network component template, and a corresponding network slice subnet template or network slice template composed of network function templates is called a network template.
  • the network slice template may include two or more nested relationships.
  • a network slice template and/or a network function template are nested in the network slice template, and a network function template is nested in the network slice subnet template.
  • the above relationship between the network and the network component is for a nested relationship of any two levels.
  • This application uses two levels of nesting as an example to illustrate, and the nesting relationship of more layers can also be analogized without further elaboration.
  • the network slice template, network slice subnet template, and network function template are named according to functions, and no restrictions are imposed on the name.
  • Each of the above templates may have other names, such as a network slice descriptor and a network slice subnet description. And network function descriptors.
  • a network slice instance is obtained by instantiating a network-based slice template, that is, a real-running logical network that satisfies certain network characteristics or service requirements.
  • a network slice instance can provide one or more services.
  • Network slicing instances can be created by management and orchestration devices.
  • a management and orchestration device can create multiple network slicing instances and manage them simultaneously, including performance monitoring and fault management during network slicing instance operations.
  • a complete network sharding instance can provide complete end-to-end network services, and the network sharding instances can be network slice subnet instances (NSSIs) and/or network function instances.
  • NSSIs network slice subnet instances
  • a network slice instance can be divided into several network slice subnet instances to facilitate management and orchestration device management.
  • the network slicing subnet instance may not need to provide a complete network service end-to-end.
  • the network slicing subnet instance may be a set of network function instances of the same device vendor in the network slicing instance, or may be a network function instance divided by domain.
  • a collection such as a core network network slice subnet instance, an access network network slice subnet instance, or a collection of other ways, such as a deployment location.
  • a network sliced subnet instance can be shared by multiple network slice instances.
  • a network slice instance can consist of several network slice subnet instances and network function instances that are not partitioned into network slice subnet instances.
  • a network slice instance can also consist of only a few network function instances.
  • a network slice subnet instance can also consist of several network function instances.
  • Network function is a processing function in the network that defines functional behavior and interfaces.
  • Network functions can be implemented by dedicated hardware, by running software on dedicated hardware, or as virtual functions on a common hardware platform. The following are collectively referred to as physical network functions and/or virtualized network functions as network functions.
  • a virtual resource is a logical resource built on a physical resource by means of a virtualization platform to support a network.
  • a virtual computing resource vCPU
  • the virtual resources required to implement the network slicing or network slicing subnet in this document may be referred to as a network service NS, and the virtual resources required to implement the network function may be referred to as a VNF.
  • the network or network component requirements information may include latency requirements, bandwidth requirements, coverage requirements, number of users requirements (capacity requirements), mobility requirements, throughput requirements, reliability requirements, deployment location requirements, affinity One or more of anti-affinity requirements, success rate requirements, and network slice type requirements.
  • the delay requirement refers to a response time requirement of a network or a network component
  • the delay requirement may be that the maximum delay does not exceed a preset threshold, where the maximum delay refers to the maximum response time of the network or the network component.
  • the maximum delay of the network or network component is required to be 10ms, that is, the maximum response time of the network or network component is expected to be 10ms.
  • Bandwidth requirements can be used to describe the bandwidth required by a network or network component, for example, requiring a minimum bandwidth of 10M for a network or network component. Coverage requirements are used to describe the network coverage area used by a network or network component, such as the Shanghai area.
  • the number of users is required to describe the maximum number of users that are required to be carried by this network or network component. For example, if the network or network component is expected to be accessed by 1 million users before deployment, the number of users is required to be greater than or equal to 1 million.
  • Mobility requirements are used to describe the movement of a terminal device that accesses the network or network component, such as moving or fixed. Mobility requirements may further describe the rate of movement of a terminal device that accesses the network or network component.
  • Affinity anti-affinity requirements refer to deployment location requirements between a network or network component and other network or network components.
  • the success rate is used to describe the success rate of the terminal device using the network or network component, and may include the reported success rate and the success rate of the delivery.
  • the throughput requirement describes the data forwarding capability of the network or network component, such as 100 Mbit/s, indicating that the network or network component supports transmission of 100 Mbits of data in one second.
  • Reliability requirements are used to indicate the ability of a network or network component to perform its function or to continue to work.
  • the network slice type requirement may be divided according to functions.
  • the network slice type may be one of the following: enhanced mobile broadband (eMBB), ultra reliable and low latency communications (URLLC) ) and mass machine type communications (mMTC).
  • a network slice subnet or network function may be nested in the network slice, the network slice may be a network, the network slice subnet or the network function may be a network component.
  • the network function can be nested in the network slicing subnet, the network slicing subnet can be a network, and the network function can be a network component.
  • the network slice requirement information may be obtained by the service management device according to the received service requirements of the operator and/or the third party client, and sent to the network management device.
  • an algorithm or a policy that can locally store the service requirement to the network requirement in the network slice template is used to implement the requirement information for converting the service requirement into the network slice.
  • the service requirement is that the service type is a vehicle-to-vehicle (V2X) service. Because the V2X service requires high reliability and low latency, the mapping policy can be pre-established to map the V2X service to the demand information: the network slice type requirement is URLLC. .
  • the requirement information of the network slicing subnet may be that the network management device decomposes the demand information of the network slice according to the pre-stored policy or algorithm into the requirement information of each network component, and sends the information to the domain management device.
  • the pre-stored policy or algorithm may be to perform demand information distribution through a policy identifier or an algorithm identifier.
  • the policy identifier or the algorithm identifier may indicate that the demand information of the network slice is allocated according to a preset ratio according to different network domains.
  • the policy identifier or the algorithm identifier may also be used to indicate that the demand information is decomposed according to a preset ratio according to different network slice subnet templates.
  • the demand information of the network function may be that the network management device and/or the domain management device decompose the network slice and/or the network slice subnet requirement information according to the pre-stored policy or algorithm as the requirement information of each network function, and deliver the information to the network function management. equipment.
  • the deployment information of the network or network component may include a virtual resource descriptor identifier corresponding to the network or the network component and/or a virtual resource deployment specification identifier corresponding to the network or the network component.
  • the deployment information of the network or the network component may further include one or more of the following: an instantiation level of the virtual resource corresponding to the network or network component, location constraint information of the virtual resource corresponding to the network or the network component, and a network or network component corresponding to the network Affinity and anti-affinity information for virtual resource deployment.
  • Some of the information in the deployment information may also be calculated according to a locally pre-stored algorithm. For example, the affinity and anti-affinity information may be calculated according to a locally pre-stored algorithm. If the delay requirement is high, that is, the delay requirement in the network or network component requirement information is high, the parameters corresponding to the affinity and anti-affinity information may be set to deploy the network or network component near the base station. Reduce the communication delay with the base station.
  • the deployment information of the network or network component may be an NSD profile calculated according to the demand information of the network or network component.
  • the virtual resource descriptor identifier corresponding to the network or network component may be a network service descriptor identifier (ie, NSD ID) or a virtual network function descriptor (VNFD) identifier (VNFD ID).
  • the virtual resource deployment specification identifier corresponding to the network or network component may be a network service deployment specification identifier (ie, an NS Flavor ID) or a virtual network function deployment specification identifier (ie, a VNF Flavor ID).
  • the virtual resource instantiation level corresponding to the network or network component may be a network service instantiation level (NSInstantiation level) or a virtual network function instantiation level (VNFInstantiation level).
  • the affinity and anti-affinity of the virtual resource deployment corresponding to the network or network component may also include the affinity and anti-affinity of the network service or the affinity and anti-affinity of the VNF.
  • the deployment location constraint information of the virtual resource corresponding to the network or network component may also include constraint information of the deployment location of the network service or constraint information of the deployment location of the VNF.
  • the virtual resource instantiation level corresponding to the network or network component is used to represent the capacity of the virtual resource instance, and the capacity of different virtual resource instantiation levels is different.
  • the capacity can characterize the carrying capacity of the network or network component, for example the number of users that can be carried.
  • the affinity and anti-affinity information of the virtual resource deployment corresponding to the network or network component refers to whether the virtual resource corresponding to the network or network component can be deployed in the same area as the network or network component of another function. For example, a network or network component can be deployed with a data center, a server, or the like.
  • the virtual resource location constraint information corresponding to the network or network component refers to the geographic location of the virtual resource deployment corresponding to the network or network component according to the functional requirements of the network or the network component.
  • a virtual resource corresponding to a network or a network component needs to exchange information with a data center.
  • a virtual resource corresponding to the network or network component can be deployed in the data center.
  • the network or network component has a higher communication delay requirement, and the corresponding virtual resource can be deployed in a location close to the base station to reduce the communication delay and the like.
  • the deployment information of the network or the network component may further include at least one of the following information: description information of the deployed physical network function, and existing VNF instance information.
  • the description information of the deployed physical network function is used to inform the management and orchestration device how to connect the virtual resource to the physical network function, such as connection information of the physical network function, such as an IP address.
  • the existing VNF instance information is used to indicate that the VNF instance can be reused and the reused VNF instance information, such as the identifier of the existing VNF instance, the specifications of the existing VNF instance, and the like.
  • FIG. 1 is a schematic structural diagram of a network system according to an embodiment of the present application.
  • the network system 100 includes: a service management function (SMF) device 101, a network management (NM) device 102, a domain management (DM) device 103, and a virtual network function management. (virtualized network function manager, VNFM) device and management and orchestration (MANO) device 105.
  • SMF service management function
  • NM network management
  • DM domain management
  • VNFM virtualized network function manager
  • MANO management and orchestration
  • the service management device 101 is mainly used to implement service management, such as service lifecycle management, service monitoring, service charging, etc., and translates service requirements of operators and/or third-party customers into network demand information.
  • the network demand information is transmitted to the network management device 102 through an interface with the network management device 102.
  • the network management device 102 is configured to receive a network management request sent by the service management device 101, where the request may carry the network requirement information.
  • the network management device 102 can also have one or more of the following functions: managing the network, including managing the lifecycle, performance, faults, and configuration of the network and/or network subnet; also for network templates and/or network sub-networks Web template management.
  • the network management device 102 is further configured to: when receiving the network request, obtain the network template according to the network request, and may be a network template obtained according to the network template indication information (such as the identifier of the network template) included in the network request, or may be a network according to the network
  • the demand information of the network carried in the request and the local pre-stored decomposition algorithm of the network management device 102 calculate the matching network template.
  • the network deployment information is obtained from the matched network template according to the network requirement information.
  • the network management device 102 can transmit the deployed information of the acquired network to the management and orchestration device 105 through an interface with the management and orchestration device 105.
  • the network management device 102 may perform the foregoing method for acquiring network deployment information; when the network slice template is embedded with the network slice subnet template or the network function template
  • the network management device 102 performs the following operations: the network management device 102 is further configured to parse the network template to obtain one or more network subnet template identifiers and/or identifiers of one or more network function templates, and decompose the network requirement information into Demand information for network subnets and/or demand information for network functions.
  • Each network subnet template identifies the requirement information of one network subnet; the identifier of each network function template corresponds to a network function requirement information.
  • the identifier of each network subnet template and the corresponding network subnet requirement information are sent to the domain management device 103 through an interface with the domain management device 103.
  • the network management device 102 also transmits network function template identification and network function requirement information to each network function management device 104 through an interface with the network function management device 104.
  • the network management device 102 also orchestrate the various network subnets and/or network functions such that different network subnets and/or network functions can satisfy the target service or network demand information. Specifically, it may be at least one of the following service or network requirement information: a service level agreement (SLA) requirement, a key performance indicator (KPI) requirement, and a quality of service (quality of Service, QoS) requirements.
  • SLA service level agreement
  • KPI key performance indicator
  • QoS quality of service
  • the domain management device 103 may have one or all of the network subnet management function or the network subnet scheduling function, and may have some or all of the following functions: lifecycle management of the network subnet, such as creation, update, deletion, and failure of the network subnet. Management, performance management, configuration management, etc.; network service management, including network service lifecycle management, network service fault management, network service performance management, network service configuration management; network function coordination.
  • the domain management device 103 is further configured to receive the identifier of the network subnet template and the corresponding network subnet requirement information sent by the network management device 102 through an interface with the network management device 102.
  • the domain management device 103 can associate one or more network subnet templates. The association here can be understood as management.
  • the domain management device 103 can be divided into a CN management device, an AN management device, and a TN management device according to the network type of the managed network slice subnet.
  • the domain management device 103 searches for the network subnet template corresponding to the identifier by using the identifier of the received network subnet template, and calculates a matching according to the received network slice requirement information and a decomposition algorithm locally saved by the domain management device 103 to obtain the identifier.
  • Target deployment information in the network subnet template Each network subnet template can contain deployment information of at least one network subnet.
  • the domain management device 103 can also send the target deployment information to the management and orchestration device 105 through an interface with the management and orchestration device 105.
  • the network management device 102 may perform the foregoing method for acquiring deployment information of the network subnet; when the network function template is nested in the network subnet template, the domain management device 103 The following operations are performed: the domain management device 103 is further configured to parse the network subnet template to obtain the identifier of one or more network function templates, and decompose the network subnet requirement information into the network function requirement information.
  • the identifier of each network function template corresponds to the demand information of one network function.
  • the identification of each network function template and the required information of the corresponding network function are transmitted to the network function management device 104 through an interface with the network function management device 104.
  • the network function management device 104 may have some or all of the following functions: lifecycle management of network functions, such as creation, update, deletion, fault management, performance management, configuration management, etc. of network functions; management of network services, including network service life Cycle management, network service fault management, network service performance management, network service configuration management, etc.; network function coordination.
  • the network function management device 104 is further configured to receive the identifier of the network function template and the corresponding network function requirement information sent by the network management device 102 through an interface with the network management device 102.
  • the network function management device 104 can associate one or more network function templates.
  • the network function management device 104 searches for the network function template corresponding to the identifier of the received network function template, and calculates and matches the received network function according to the received network function and the network function management device 104.
  • Target deployment information in the network function template Each network function template can contain deployment information of at least one network function.
  • the network function management device 104 is further configured to receive the identifier of the network function template and the corresponding network function requirement information sent by the domain management device 103 through an interface with the domain management device 103.
  • the network function management device 104 searches for the network function template corresponding to the identifier of the received network function template, and calculates and matches the received network function according to the received network function and the network function management device 104.
  • Target deployment information in the network function template The network function management device 104 can also transmit the target deployment information to the management and orchestration device 105 through an interface with the management and orchestration device 105.
  • the management and orchestration device 105 can receive an instantiation request of the network-carrying deployment information sent by the network management device 102, and deploy the virtual resource of the network according to the instantiation request of the deployment information of the portable network.
  • the management and orchestration unit 105 can also directly receive the instantiation request of the deployment information of the network subnet sent by the domain management device 103, and instantiate according to the instantiation request of the deployment information of the network subnet.
  • the management and orchestration device 105 can also directly receive the instantiation request of the deployment information carrying the network function sent by the network function management device 104, and instantiate according to the instantiation request of the deployment information carrying the network function.
  • management and orchestration device 105 may also have some or all of the following functions: network function and/or lifecycle management of network services, failure management of network functions and/or network services, performance management of network functions and/or network services, Configuration management of network functions and/or network services, allocation of virtual resources, reservation of virtual resources, and the like.
  • the above network may be a network slice, which is also called an end to end (E2E) network slice.
  • the network may include at least one of a core network portion, an access network portion, and a transport network portion.
  • the network subnet described above may be a network slice subnet, or may include at least one of a core network part, an access network part, and a transport network part. Logically, networks and network subnets are a collection of network functions.
  • the service management device 101, the network management device 102, the domain management device 103, and the management and orchestration device 104 are all named according to functions. For each of the above devices, there is no restriction on the name of the device. A device can have other names as well. Each of the above devices can be a standalone device.
  • the service management device 101 may be one or more of the following: a communication service management function (CSMF), a service orchestration device, a service management, and an orchestration device.
  • the network management device 102 can be one or more of the following: a network slice management function (NSMF) device, a cross-domain management device, a cross-domain network slice management device, or other device that performs the above functions.
  • CSMF communication service management function
  • NSMF network slice management function
  • the domain management device 103 may be one or more of the following: a domain slice management device, a network slice subnet management function (NSSMF) device, or other device that performs the above functions.
  • the management and orchestration device 104 can be one or more of the following: a network function virtualization orchestration (NFVO), a virtualized network function manager (VNFM), and a virtual infrastructure manager ( Virtualized infrastructure manager (VIM) or other device that performs the above functions.
  • NFVO network function virtualization orchestration
  • VNFM virtualized network function manager
  • VIP Virtualized infrastructure manager
  • Each of the above devices can also be a function in a management device.
  • each device may be one or more of the following devices: network orchestration device, network management and orchestration device, network element management device, service orchestration device, service management and orchestration device, or NFVO.
  • Each network device may be included in the office of strategic services (OSS) or may not be included in the OSS, and is not limited herein.
  • OSS strategic services
  • the network system shown in FIG. 1 is only for the purpose of more clearly explaining the technical solutions of the present application, and does not constitute a limitation of the present application. Those skilled in the art may know that with the evolution of the network system and the emergence of new business scenarios, the present application The technical solutions provided are equally applicable to similar technical issues.
  • FIG. 2 provides a schematic structural diagram of NST and NSST.
  • the network slice template is nested with a network slice subnet template.
  • the network slice template can also be nested with a network function template.
  • the network slice template is nested with a network slice subnet template as an example.
  • the case where a network function template is nested in a slice template is similar to the case where a network function template is nested in a network slice subnet template, and can be analogized.
  • the NST may include deployment information of different network slices.
  • the deployment information of the network slice may include the identifier of the deployment information of the network slice subnet, that is, the identifier of the deployment specification of the NSD of the NSST.
  • NST1 can contain four network slice deployment information according to different NST-NSD identifiers: (1) NST1-NSD specification 1: NSST1-NSD specification 1+NSST2-NSD specification 1, (2) NST1-NSD Specification 2: NSST1-NSD Specification 1+NSST2-NSD Specification 2, (3) NST1-NSD Specification 3: NSST1-NSD Specification 2+NSST2-NSD Specification 1, (4) NST1-NSD Specification 4: NSST1 -NSD specification 2+NSST2-NSD specification 2.
  • the deployment information of each network slice includes the identifier of the deployment information of the network slice subnet 1 and the identifier of the deployment information of the network slice subnet 2.
  • NSST1 is a template of network slice subnet 1
  • NSST2 is a template of network slice subnet 2.
  • the identifier of the deployment information of the network slicing subnet 1 and the identifier of the deployment information of the network slicing subnet 2 may be used to determine the deployment information of the corresponding network slicing subnet 1 and the deployment information of the network slicing subnet 2.
  • FIG. 3 provides a schematic flowchart of a method for determining deployment information of a network. Specifically, the process of determining deployment information of a virtual resource of a network slice according to the NST structure is as follows:
  • the network management device matches the network slice template according to the requirement information of the network slice and/or the identifier of the network slice template.
  • the network management device may calculate the matched network slice identifier as NST1 according to the network slice requirement information and the locally saved decomposition algorithm, or obtain the network slice identifier as NST1 according to the network slice indication information, and the NST1 is different according to the NST1.
  • the NSD deployment specification identifier can contain deployment information for four network slices.
  • the network management device parses the network slice template, and decomposes the network slice requirement information into network slice subnet requirement information.
  • the network management device resolves the above NST1 to obtain NSST1 and NSST2. That is, NSST1 and NSST2 are included in the deployment information of each NST1. Or the NST1 deployment information includes all the network slice subnet templates identified as NSST1 and NSST2. At the same time, the network management device can decompose the network slice requirement information for the NSST1 and the NSST2 into the network slice subnet requirement information. For example, it is decomposed into the demand information of network slice subnet 1 and the demand information of network slice subnet 2.
  • the network management device sends the network slice subnet template and the network slice subnet requirement information to the domain management device.
  • the network management device sends the requirement information of the network slice subnet 1 and the NSST1 identifier to the domain management device 1 associated with the NSST1, and sends the requirement information of the network slice subnet 2 and the NSST2 identifier to Domain management device 2 associated with NSST2.
  • the domain management device determines the deployment information of the network slice subnet according to the network slice subnet template and the network slice subnet requirement information.
  • the domain management device 1 determines the deployment information of the network slice subnet 1 from the deployment information (NSST1-NSD Flavor1 and NSST1-NSD Flavor2) of the two network slice subnets corresponding to the NSST1 according to the requirement information of the network slice subnet 1.
  • the domain management device 2 determines the deployment information of the network slice subnet 2 from the deployment information (NSST2-NSD Flavor1 and NSST2-NSD Flavor2) of the two network slice subnets corresponding to the NSST2 according to the requirement information of the network slice subnet 2.
  • the domain management device sends the deployment information of the network slice subnet to the management and orchestration device.
  • the domain management device 1 transmits the deployment information of the network slice subnet 1 to the management and orchestration device.
  • the domain management device 2 transmits the deployment information of the network slice subnet 2 to the management and orchestration device.
  • the management and orchestration device can deploy the virtual resources according to the deployment information of the network slicing subnet 1 and the deployment information of the network slicing subnet 2.
  • the domain management device 1 may send the deployment information of the network slice subnet 1 to the management and orchestration device through an interface with the management and orchestration device, and the domain management device 2 may also The deployment information of the network slice subnet 2 is sent to the management and orchestration device through an interface with the management and orchestration device, and the management and orchestration device is deployed according to the deployment information of the received network slice subnet 1 and the network slice subnet 2 Information for virtual resource deployment.
  • the management and orchestration device performs two virtual resource deployments independently according to the deployment information of the network slicing subnet 1 and the deployment information of the network slicing subnet 2.
  • the deployment information associated with the network slice subnet 1 and the network slice subnet 2 is lost, such as the connection relationship between the network slice subnet 1 and the network slice subnet 2, and the network slice subnet 1 and the network slice subnet 1
  • the loss of affinity and anti-affinity information which reduces the accuracy of the network deployment information.
  • the embodiment of the present application provides a method for determining deployment information of a network, which can improve the accuracy of deployment information of the network.
  • the main inventive principle of the present application may include: when a network component template is nested in the network template, the first network entity associated with the network template decomposes the network requirement information into the network component requirement information, and identifies the network component template.
  • the demand information with the network component is sent to the second network entity associated with the network component.
  • the second network entity obtains the deployment information of the network component according to the received network component template identifier and the network component's requirement information, and sends the deployment information of the network component to the first network entity.
  • the first network entity may receive deployment information of multiple network components, and obtain complete network deployment information according to the deployment information of the multiple network components.
  • the deployment information includes the association relationship between the various network components, and includes more comprehensive deployment information in the deployment information sent to the management and orchestration device, which can improve the accuracy of the network deployment information determination.
  • the domain management device 1 determines the network slice subnet 1 from the deployment information of the two network slice subnets corresponding to the NSST1 according to the requirement information of the network slice subnet 1.
  • the domain management device 2 determines the deployment information of the network slice subnet 2 from the deployment information of the two network slice subnets corresponding to the NSST2 according to the requirement information of the network slice subnet 2.
  • the domain management device 1 transmits the deployment information of the network slice subnet 1 to the network management device, and the domain management device 2 transmits the deployment information of the network slice subnet 2 to the network management device.
  • the network management device can be included in the network slice template according to the association between the deployment information of the network slice subnet 1 and the deployment information of the network slice, and the association between the deployment information of the network slice subnet 2 and the deployment information of the network slice.
  • the deployment information of the network slice determines the deployment information of the network. Specifically, as shown in FIG. 2, if the deployment information of the network slicing subnet 1 is the deployment information identified by the NSST1-NSD specification 1, the deployment information of the network slicing subnet 2 is the deployment information identified by the NSST2-NSD specification 2.
  • the network management device After receiving the deployment information of the NSST1-NSD specification 1 and the deployment information of the NSST2-NSD specification 2, the network management device selects the deployment information of the four NST1-NSD specification identifiers included in the NST1.
  • the NSD specification 1 association (that is, the NSST1-NSD specification 1 identifier) is associated with the NSST2-NSD specification 2 (that is, the NSST2-NSD specification 2 identifier) is the deployment information identifier, which is the deployment information of the NST1-NSD specification 2 identifier. .
  • the deployment information identified by the NST1-NSD specification 2 includes the association between the network slice subnet 1 and the network slice subnet 2, such as the affinity and anti-affinity of the network slice subnet 1 and the network slice subnet 2 deployment.
  • Sexuality including more comprehensive deployment information in the deployment information sent to the management and orchestration equipment, can improve the accuracy of the network deployment information determination.
  • FIG. 4 is a schematic flowchart of a method for determining deployment information of a network according to an embodiment of the present application.
  • the deployment information determining method of the network includes, but is not limited to, the following steps S401-S404.
  • the first network entity sends a second message to the second network entity.
  • the second message carries the demand information of the network component and the identifier of the network component template.
  • the embodiments of the present application can be applied to at least the following two scenarios.
  • Scenario 1 The first network entity is a network management device, the second network device is a domain management device, and the third network device is a management and orchestration device.
  • the network component is a network slice subnet
  • the network component template is a network slice subnet template
  • the network is a network slice
  • the network template is a network slice template.
  • Scenario 2 The first network device is a network management device or a domain management device
  • the second network device is a network function management device
  • the third network device is a management and orchestration device.
  • the network component is a network function
  • the network component template is a network function template
  • the network is a network slice or a network slice subnet
  • the network template is a network slice template or a network slice subnet template.
  • the network management device before the network management device sends the first message to the domain management device, the network management device is further configured to perform the following steps:
  • Step 1 The network management device receives the network slice request sent by the service management device.
  • the service management device may receive the network slice request or the service request, where the network slice request or the service request carries the network slice request information and the network slice template indication information.
  • the service management device may also calculate the network slice requirement information and the network slice template indication information according to the received service requirements sent by the operator and/or the third-party client, and the network slice requirement information and/or the network slice template.
  • the indication information is carried in the network slice request and sent to the network management device.
  • the network slice request may also directly carry the indication information of the network slice template, and is used to determine the network slice template corresponding to the indication information.
  • the demand information of the network slice reflects the requirement of the network slice function of the operator and/or the third party customer.
  • the network slice requirement information may include delay requirements, bandwidth requirements, coverage requirements, user quantity requirements (capacity requirements), mobility requirements, throughput requirements, reliability requirements, deployment location requirements, affinity anti-affinity requirements. One or more of the success rate requirements and network slice type requirements.
  • Step 2 The network management device acquires a network slice template according to the network slice request.
  • the pre-stored network slice template may be obtained according to the network slice template indication information.
  • the corresponding network slice template may be matched according to the network slice requirement information. The matching process may be calculated by the network management device according to a pre-stored network slice template vendor decomposition algorithm.
  • Step 3 The network management device parses the network slice template to obtain the network slice subnet template identifier, and decomposes the network slice requirement information into the network slice subnet requirement information.
  • the network management device may parse the identifier of the network slice subnet template included in the deployment information of the network slice in the network slice template, so as to obtain the identifier of the network slice subnet template.
  • the demand information of the network slice may be carried in the network slice request.
  • the requirement information for decomposing the network slice is that the network slice subnet requirement information may be decomposed according to a policy or an algorithm indicated by a policy identifier or an algorithm identifier preset in the network slice template.
  • the demand information may be allocated according to a preset ratio according to different network domains; or the demand information may be decomposed according to a preset ratio according to different network slice subnet templates.
  • the requirement information of the network slice is a delay
  • the network slice template includes a network slice subnet template 1, a network slice subnet template 2, and a network slice subnet template 3.
  • the network slice subnet template 1 is an AN part template
  • the network slice subnet template 2 is a CN part template
  • the network slice subnet template 3 is a TN part template.
  • the network slice requirement information is 10 ms
  • the network slice requirement information is decomposed according to the allocation ratio corresponding to the foregoing policy identifier: the delay requirement information of the network slice subnet 1 is 2 ms, and the network delay subnet 2 delay requirement information For 3ms, the delay requirement information of network slice subnet 3 is 5ms.
  • the network slice requirement information is the number of users and the distribution area
  • the network slice is composed of the network slice subnet 1 provided by the vendor 1 and the network slice subnet 2 provided by the vendor 2.
  • the network slice subnet 1 network slice subnet 2 includes an AN part, a CN part, and a TN part.
  • the network slice template is pre-stored with a policy indicating that the network slice subnet template of area 1 is provided by vendor 1, and the area 2 network slice subnet template is provided by vendor 2.
  • Region 1 and Region 2 are two regions in Shanghai.
  • the demand information for network slicing is 1 million users in Shanghai, including 400,000 users in Region 1 and 600,000 users in Region 2.
  • the network slice subnet 1 demand information is the number of users 400,000
  • the network slice subnet 2 demand information The number of users is 600,000.
  • the above examples are only used to explain the embodiments of the present invention, and should not be limited.
  • Other strategies or algorithms may be preset in the network slice template to perform network slice requirement information decomposition. It can be understood that the required information of the network slice subnet obtained by the decomposition is respectively corresponding to the identifier of the parsed network slice template.
  • the network management device may parse the network slice template to obtain one or more network slice subnet template identifiers, and allocate corresponding network slice subnet requirement information for the network slice subnet corresponding to each network slice subnet template. If multiple network slice subnet template identifiers are obtained by parsing, multiple network slice subnet template identifiers and corresponding network slice subnet requirement information may be sent to multiple domain management devices respectively, or may be sent to the same
  • the domain management device is not limited here.
  • scenario 2 is specifically subdivided into two scenarios, that is, scenario 2a, the first network entity is a domain management device, and the second network entity is a network function management device.
  • the network is a network slicing subnet
  • the network component is a network function
  • the network component template is a network function template.
  • scenario 2b the first network entity is a network management device
  • the second network entity is a network function management device.
  • the network is a network slice
  • the network component is a network function
  • the network component template is a network function template.
  • the domain management device may slice according to the network.
  • the subnet template identifier obtains a pre-stored network slice subnet template. If the message sent by the network management device does not include the identifier of the network slice subnet template, the corresponding network slice subnet template can be matched according to the network slice subnet requirement information.
  • the matching process may be calculated by the domain management device according to the pre-stored network slice subnet template vendor decomposition algorithm.
  • the decomposition algorithm and the decomposition algorithm in scenario 1 are preset by the manufacturer, and may be pre-defined according to different functions in a specific situation. Assume.
  • the domain management device parses the network slice subnet template to obtain the network function template identifier, and decomposes the requirement information of the network slice subnet as the network function requirement information.
  • the network segmentation subnet requirement information may be carried in the message sent by the network management device. When the message sent by the network management device does not carry the network slice subnet requirement information, it may be carried in the obtained network slice subnet template. .
  • Decomposing the network segmentation subnet requirement information as the network function requirement information may be decomposed according to a policy or an algorithm indicated by a policy identifier or an algorithm identifier preset in the network slice subnet template. Specifically, the demand information may be allocated according to a preset ratio according to different network functions; or the demand information may be decomposed according to a preset ratio according to different network function templates.
  • the network management device parses the network slice template to obtain the network function template identifier, and decomposes the network slice requirement information into network function requirement information.
  • the network management device may parse the identifier of the network function template included in the deployment information of the network slice in the network slice template, so as to obtain the identifier of the network function template.
  • the network slice request information may be carried in the network slice request. When the network slice request does not carry the network slice request information, it may be carried in the acquired network slice template.
  • Decomposing the network slice requirement information as the network function requirement information may be decomposed according to a policy or an algorithm indicated by a policy identifier or an algorithm identifier preset in the network slice template.
  • the demand information may be allocated according to a preset ratio according to different network functions; or the demand information may be decomposed according to a preset ratio according to different network function templates.
  • the second network entity determines the first deployment information according to the network component template corresponding to the requirement information of the network component and the identifier of the network component template.
  • the first deployment information is deployment information of network components.
  • the domain management device may associate a plurality of network slice subnet templates, and determine a network slice subnet template corresponding to the identifier according to the identifier of the network slice subnet template.
  • the network slice subnet template can contain deployment information of at least one network slice subnet.
  • the domain management device determines the deployment information of the network slice subnet according to the network slice subnet template corresponding to the network slice subnet requirement information and the network slice subnet template identifier, including: the domain management device according to the network slice subnet requirement information from at least
  • the deployment information of the network slice subnet is determined in the deployment information of a network slice subnet.
  • the determined process may be calculated according to a local pre-stored decomposition algorithm of the network slice subnet template, or may be obtained by other methods.
  • the mapping between the required information of the network slicing subnet and the deployment information of the network slicing subnet is not limited in this embodiment.
  • the above method describes a scenario in which the deployment information of the network slice subnet is completely included in the network slice subnet template.
  • part of the information in the deployment information of the network slice subnet may also be calculated by the domain management device by calling a local policy or an algorithm. For example, according to the delay requirement, the position constraint information is calculated.
  • the deployment information of the network slice subnet may include: a virtual resource descriptor identifier corresponding to the network slice subnet, and/or a virtual resource deployment specification identifier corresponding to the network slice subnet.
  • the deployment information of the virtual resource corresponding to the network slice subnet may also include one or more of the following: the instantiation level of the virtual resource corresponding to the network slice subnet, the affinity of the network slice subnet virtual resource deployment, and the anti-affinity Sex, network slice subnet virtual resource deployment location constraint information, etc.
  • the network function management device may associate a plurality of network function templates, and determine a network function template corresponding to the identifier according to the identifier of the network function template.
  • the network function template may include deployment information of at least one network function; the network function management device determines network deployment information according to the network function template corresponding to the network function requirement information and the network function template identifier, including: the network function management device according to the network
  • the demand information of the function determines the deployment information of the network function from the deployment information of the at least one network function.
  • the determined process may be calculated according to a local pre-stored decomposition algorithm of the network function template, or may be obtained by other methods, for example, according to the mapping relationship between the preset network function requirement information and the network function deployment information, The embodiment is not limited.
  • the above method describes a scenario in which the deployment information of the network function is completely included in the network function template. In fact, part of the information in the deployment information of the network function may also be calculated by the network function management device calling algorithm.
  • the deployment information of the network function may include: a virtual resource descriptor identifier corresponding to the network function, and/or a virtual resource deployment specification identifier corresponding to the network function.
  • the virtual resource descriptor identifier corresponding to the network function may be an NFD ID
  • the virtual resource deployment specification identifier corresponding to the network function may be an NFD Flavor ID.
  • the deployment information of the network function may also include one or more of the following: a virtual resource instantiation level corresponding to the network function, an affinity and anti-affinity of the network function virtual resource deployment, and location constraint information of the network function virtual resource deployment. .
  • the second network entity sends a first message to the first network entity, where the first message carries the first deployment information.
  • the deployment information of the network slice subnet sent by the domain management device to the network management device may be one or multiple.
  • the deployment information of the network slicing subnet is multiple
  • the deployment information of the multiple network slicing subnets may be sent by the same domain management device, or may be sent by different domain management devices, and is not limited herein.
  • the number of deployment information of the network slice subnet is equal to the number of identifiers of the network slice subnet template obtained by the network management device in step S401.
  • the number of deployment information of the network slicing subnet is also equal to the number of required information of the network slicing subnet obtained by the network management device decomposing the network slice requirement information.
  • the process of determining the deployment information of the network slice subnet according to the requirement information of the network slice and the identifier of the network slice may refer to the embodiment described in FIG.
  • the deployment information of the network slice subnet and the deployment information of the network slice may also be pre-stored.
  • FIG. 5 is a schematic structural diagram of another NST and NSST provided by an embodiment of the present application.
  • the deployment information contained in each of NSST1, NSST2, and NST1 may be stored in a database for calling. Only the identification of the deployment information may be stored to indicate the deployment information.
  • the network management device parses the network slice template NST1, and obtains the network slice template NST1 containing the network slice subnet templates NSST1 and NSST2.
  • the network management device sends the identifier information of the network slice subnet template NSST1 and the network slice subnet template NSST1 to the corresponding domain management device, and identifies the network sniper template identifier NSST2 and the network slice subnet template NSST2.
  • the information is sent to the corresponding domain management device.
  • the domain management device here can be the same domain management device or a different domain management device.
  • the domain management device obtains the deployment information of the network slice subnet 1 according to the identifier information of the network slice subnet template NSST1 and the network slice subnet template NSST1.
  • the domain management device obtains the deployment information of the network slice subnet 2 according to the identifier information of the network slice subnet template NSST2 and the network slice subnet template NSST2.
  • the domain management device directly obtains the deployment information 1 of the NSST1 from the deployment information of the pre-stored network slice subnet 1 according to the network slice subnet 1 requirement information.
  • the domain management device directly obtains the deployment information 1 of the NSST2 from the deployment information (NSST2) of the pre-stored network slice subnet 2 according to the network slice subnet 2 requirement information.
  • the deployment information of the network function sent by the network function management device to the domain management device or the network management device may be one or multiple.
  • the deployment information of the network function is multiple, the deployment information of the multiple network functions may be sent by the same network function management device, or may be sent by different network function management devices, and is not limited herein.
  • the number of deployment information of the network function is equal to the number of identifiers of the network function template parsed in step S401.
  • the number of deployment information of the network function is also equal to the number of required information of the network function obtained by decomposing the demand information of the network slice subnet or the network slice requirement information.
  • the deployment information of the network function may be pre-stored, and is directly matched from the deployment information of the pre-stored network function according to the network function requirement information.
  • FIG. 6 is a schematic structural diagram of an NSST and an NFT according to an embodiment of the present application.
  • the deployment information contained in each of NFT1, NFT2, and NSST1 may be stored in a database for calling. Only the identifier of the deployment information may be stored to indicate the corresponding deployment information.
  • the domain management device parses the network slice subnet template NSST1, and obtains the network slice subnet template NSST1 containing the network function templates NFT1 and NFT2.
  • the domain management device sends the identifier information of the network function template identifier NFT1 and the network function template NFT1 to the corresponding network function management device, and sends the identifier information of the network function template identifier NFT2 and the network function template NFT2 to the corresponding network function.
  • the management device where the network function management device can be the same network function management device, or can be a different network function management device.
  • the network function management device obtains the deployment information of the network function 1 according to the identifier NFT1 of the network function template and the requirement information of the network function template NFT1.
  • the network function management device obtains the deployment information of the network function 2 according to the identifier information of the network function template NFT2 and the network function template NFT2. As shown in FIG.
  • the network function management device directly obtains the deployment information 1 of the NFT1 from the deployment information of the pre-stored network function 1 according to the requirement information of the network function 1.
  • the network function management device directly obtains the deployment information 1 of the NFT 2 from the deployment information (NFT2) of the pre-stored network function 2 according to the demand information of the network function 2.
  • the deployment information of the network function sent by the network function management device to the network management device may be one or multiple.
  • the deployment information of the network function is multiple, the deployment information of the multiple network functions may be sent by the same network function management device, or may be sent by different network function management devices, and is not limited herein.
  • the number of deployment information of the network function is equal to the number of identifiers of the network function template parsed in step S401.
  • the number of deployment information of the network function is also equal to the number of required information of the network function obtained by decomposing the demand information of the network slice subnet or the network slice requirement information.
  • the deployment information of the network function may be pre-stored, and is directly matched from the deployment information of the pre-stored network function according to the network function requirement information.
  • FIG. 7 is a schematic structural diagram of an NST and an NFT provided by an embodiment of the present application.
  • the deployment information contained in each of NFT1, NFT2, and NST1 may be stored in a database for invocation. Only the identification of the deployment information may be stored to indicate the corresponding deployment information.
  • the network management device parses the network slice template NST1, and the network slice template NST1 includes the network function templates NFT1 and NFT2.
  • the network management device sends the identifier information of the network function template NFT1 and the network function 1 to the corresponding network function management device, and sends the identifier information of the network function template NFT2 and the network function 2 to the corresponding network function management device.
  • the network function management device here may be the same network function management device or different network function management device.
  • the network function management device obtains the deployment information of the network function 1 according to the identifier NFT1 of the network function template and the requirement information of the network function template NFT1.
  • the network function management device obtains the deployment information of the network function 2 according to the identifier information of the network function template NFT2 and the network function template NFT2. As shown in FIG.
  • the network function management device directly obtains the deployment information 1 of the NFT1 from the deployment information of the pre-stored network function 1 according to the requirement information of the network function 1.
  • the network function management device directly obtains the deployment information 1 of the NFT 2 from the deployment information (NFT2) of the pre-stored network function 2 according to the demand information of the network function 2.
  • the first network entity determines second deployment information according to the first deployment information, where the second deployment information is deployment information of the network.
  • the network management device may obtain the deployment information of the network slice according to the received deployment information of the at least one network slice subnet.
  • the network management device may determine the deployment information of the network from the deployment information of the network slice included in the network slice template according to the association between the deployment information of the at least one network slice subnet and the deployment information of the network slice.
  • the ID of the NSST-NSD specification included in the deployment information of one of the network slicing subnets is NSST1-NSD specification 1, another network.
  • the ID of the NSST-NSD specification included in the deployment information of the sniped subnet is NSST2-NSD specification 2.
  • the network management device can calculate the deployment information of the network slice according to the deployment information of the two network tiling subnets as the NST1-NSD specification. 2.
  • the deployment information of the pre-stored network slice may be pre-stored in the network template or locally pre-stored by the network management device.
  • the deployment information of the network slice includes: NST1-NSD deployment information 1, NST1-NSD deployment information 2, NST1-NSD deployment information 3, and NST1-NSD deployment information 4.
  • the deployment information of these network slices can be pre-stored in the database.
  • the NSST1-NSD specification 1 and the NSST2-NSD specification 1 and the NSST2-NSD specification 2 are selected from the deployment information of the above four network slices, including the foregoing NSST1-NSD specification 1 and NSST2- Network slice deployment information for NSD Specification 2.
  • the deployment information of the network slice indicated by the NST1-NSD specification ID being NST1-NSD specification 2 includes the above-mentioned NSST1-NSD specification 1 and NSST2-NSD specification 2.
  • the NST1-NSD deployment information 2 includes the NST1-NSD specification 2. Therefore, it can be determined that the network slice deployment information is NST1-NSD deployment information 2.
  • the network slice deployment information may also include information other than the NST1-NSD specification ID in the NST1-NSD deployment information 2. For example, it may be one or more of the following information, and the following information may be not included in the NST1, but
  • the network slice requirement information is calculated: the instantiation level of the virtual resource corresponding to the network slice 1, the affinity and reverse affinity of the virtual resource deployment of the network slice 1, and the location constraint information of the virtual resource deployment of the network slice 1.
  • the deployment information of the network slice subnet may include a virtual resource descriptor identifier corresponding to the network slice subnet, and/or a virtual resource deployment specification identifier corresponding to the network slice subnet.
  • the deployment information of the network slice subnet may also include at least one of the following information.
  • the following information may be not included in the NSST, but is calculated according to the network slice subnet requirement information: the virtual resource instance corresponding to the network slice subnet.
  • the deployment information of the network slice may include a virtual resource descriptor identifier corresponding to the network slice, and/or an identifier of the virtual resource deployment specification corresponding to the network slice.
  • the deployment information of the network slice subnet may further include at least one of the following information. The following information may be not included in the NST, but is calculated according to the network slice subnet requirement information: the virtual resource instantiation level corresponding to the network slice. The affinity and anti-affinity of the virtual resource deployment corresponding to the network slice, and the deployment location constraint information of the virtual resource corresponding to the network slice.
  • the domain management device detects that the network slice subnet meets the preset condition, the deployment information is determined according to the preset condition; the domain management device sends the deployment information of the network slice subnet to the network management device.
  • the foregoing preset condition may be that the number of users carried on the network slice subnet is greater than a preset threshold.
  • the network slice subnet is an instance of the network slice subnet that has been instantiated.
  • the foregoing preset threshold may be a requirement for the number of users in the required information of the received network slice subnet when acquiring the deployment information of the network slice subnet, or may be preset in the network slice subnet.
  • the number of users in the required information of the received network segment subnet is required to be 1 million users, and the number of users carried on the network slice subnet deployed according to the requirement information of the network slice subnet exceeds 1 million.
  • the network slicing subnet may not be able to load.
  • a setting threshold of 1 million may be set.
  • the triggering domain management device When the number of users exceeds 1 million, the triggering domain management device performs deployment information of sending a network slice subnet to the network management device, and sends the deployment information of the network slice subnet to the network.
  • the management device the network management device acquires the fourth deployment information of the network slice according to the deployment information of the network slice subnet, and sends the fourth deployment information of the network slice to the management and orchestration device, requesting management and scheduling the device according to the network slice.
  • Four deployment information is instantiated.
  • the network slice instance obtained after instantiation can be used to carry the number of users.
  • the domain management device may send the deployment information of the network slice subnet to the management and orchestration device for instantiation.
  • the network slicing subnet when the network slicing subnet is expected to exceed 800,000 users according to the capacity of the number of users, the number of users carried on the network slice subnet deployed according to the required information of the network slicing subnet exceeds, and the preset threshold is set to 800,000.
  • the network slicing subnet may not be able to load.
  • the preset threshold can be set to 800,000.
  • the triggering domain management device performs the deployment information of sending the network slice subnet to the network management device, and sends the deployment information of the network slice subnet to the network.
  • the management device acquires the fourth deployment information of the network slice according to the deployment information of the network slice subnet, and sends the fourth deployment information of the network slice to the management and orchestration device, requesting management and scheduling the device according to the network slice.
  • Four deployment information is instantiated.
  • the network slice instance obtained after instantiation can be used to carry the number of users.
  • the preset condition may also be that the domain management device managing a network slice subnet fails.
  • the failed domain management device loses control of the network slicing subnet and needs to redeploy the network slicing subnet instance.
  • the domain management device updates the network slice subnet triggered according to other policies set up internally. It can be understood that, during the operation of the network slice or the network slice subnet, as long as an abnormal situation occurs, the network slice or the network slice subnet needs to be redeployed or updated, which is included in the embodiment of the present application.
  • the problem of network slicing or network slicing subnet operation may be solved by redeploying or updating the network slice or the network slicing subnet.
  • the network management device determines the deployment information of the network slice according to the deployment information of the network slice subnet
  • the network management device sends a request for the deployment information of the network slice to the management and orchestration device, and the management and orchestration device receives the request.
  • the request for the deployment information of the network slice is carried, the virtual resource of the network slice is deployed according to the deployment information of the network slice.
  • the domain management device does not directly send the deployment information of the network slice subnet to the network slice subnet deployment information.
  • the management orchestration device that manages the network virtual resource is instantiated, and the deployment information of the network slice subnet is sent to the network management device, and the network management device acquires the network including the at least one according to the deployment information of the at least one network slice subnet.
  • the deployment information of the complete network slice corresponding to the network slice requirement information is obtained, and the relationship between the deployment information of the network slice subnet is included, and the deployment information sent to the network management device includes more comprehensive deployment information. Improve the accuracy of the network slice's deployment information.
  • the domain management device or the network management device may acquire deployment information of the network slice according to the received deployment information of the at least one network function.
  • the ID of the NFT-NSD specification included in the deployment information of one of the network functions is NFT1-NSD specification 1
  • the ID of the NFT-NSD specification included in the deployment information of the other NF is NFT2-NSD specification 2.
  • the domain management device can calculate the deployment information of the network slice subnet according to the deployment information of the two NFs. In addition, it may also be deployment information of a pre-stored network slice subnet. As shown in FIG.
  • the deployment information of the network segment subnet includes: NSST1-NSD deployment information 1, NSST1-NSD deployment information 2, NSST1-NSD deployment information 3, and NSST1-NSD deployment information 4.
  • the deployment information of these network slice subnets can be pre-stored in the database.
  • the domain management device receives the deployment information of the two NFs, according to the association relationship between the NFT1-NSD specification 1 and the NFT2-NSD specification 2 and the deployment information of the above four network slice subnets, the NFT1-NSD specification 1 is selected and selected. And network segmentation subnet deployment information of NFT2-NSD specification 2. As shown in FIG.
  • the deployment information of the network slice subnet indicated by the NSST1-NSD specification ID NSST1-NSD specification 2 includes the above NFT1-NSD specification 1 and NFT2-NSD specification 2.
  • the NSST1-NSD deployment information 2 includes the NSST1-NSD specification 2. Therefore, it can be determined that the deployment information of the network slice subnet is NSST1-NSD deployment information 2.
  • the deployment information of the network slice subnet NSST1-NSD deployment information 2 may further include information other than the NSST1-NSD specification ID. For example, it may be one or more of the following information, and the following information may not be included in the NSST1, and the following information may be included in the NSST1.
  • the network slice subnet requirement information the instantiation level of the virtual resource of the network slice subnet 1, the affinity and reverse affinity of the network slice subnet 1 virtual resource deployment, and the network slice subnet 1 virtual resource Location constraint information for deployment, etc.
  • the above examples are only used to explain the embodiments of the present application and should not be construed as limiting.
  • the deployment information of the network function may include a virtual resource descriptor identifier corresponding to the network function, and a virtual resource deployment specification identifier corresponding to the network function.
  • the deployment information of the network function may further include at least one of the following information, where the following information may be not included in the NFT, but calculated according to the network function requirement information: a virtual resource instantiation level corresponding to the network function, and the network function corresponds to The affinity and anti-affinity of the virtual resource deployment, and the deployment location constraint information of the virtual resource corresponding to the network function.
  • the deployment information of the virtual resource corresponding to the network slice subnet may include the virtual resource descriptor identifier corresponding to the network slice subnet and/or the virtual resource deployment specification identifier corresponding to the network slice subnet.
  • the deployment information of the network slice subnet may also include at least one of the following information.
  • the following information may be not included in the NSST, but is calculated according to the network slice subnet requirement information: the virtual resource instance corresponding to the network slice subnet.
  • the domain management device After the domain management device calculates the deployment information of the network slice subnet according to the deployment information of the network function, the deployment information of the network slice subnet is nested in the deployment information of the network slice. Therefore, the domain management device needs to slice the network afterwards.
  • the deployment information of the network is sent to the network management device, and the process of the scenario 1 and the subsequent process in step S404 are performed.
  • the domain management device associated with the network slice subnet template decomposes the network slice subnet requirement information into network function requirements.
  • the information is sent to the network function management device associated with the network function by the network function template identifier and the network function demand information.
  • the network function management device acquires the deployment information of the network function according to the received network function template identifier and the network function requirement information, and sends the deployment information of the network function to the domain management device.
  • the domain management device can receive deployment information of multiple network functions, and obtain a complete network slice subnet according to the deployment information of the multiple network functions.
  • the deployment information of the network slice subnet includes the association relationship between the network functions, and the deployment information sent to the network management device includes more comprehensive deployment information, which can improve the accuracy of the network slice deployment information determination. .
  • the network management device receives the deployment information of the two network functions
  • the ID of the NFT-NSD specification included in the deployment information of one of the network functions is NFT1-NSD specification 1
  • the ID of the NFT-NSD specification included in the deployment information of the other NF is NFT2-NSD specification 2
  • the network management device can calculate the deployment information of the network slice according to the deployment information of the two NFs.
  • it may also be deployment information of pre-stored network slices.
  • the deployment information of the network slice subnet includes: NST1-NSD deployment information 1, NST1-NSD deployment information 2, NST1-NSD deployment information 3, and NST1-NSD deployment information 4.
  • the deployment information of these network slices can be pre-stored in the database.
  • the network management device receives the deployment information of the two NFs, according to the association relationship between the NFT1-NSD specification 1 and the NFT2-NSD specification 2 and the deployment information of the above four network slices, the NFT1-NSD specification 1 and the NFT2 are selected and selected.
  • - NSD specification 2 network slice deployment information.
  • the deployment information of the network slice indicated by the NST1-NSD specification ID being NST1-NSD specification 2 includes the above-mentioned NFT1-NSD specification 1 and NFT2-NSD specification 2.
  • the NST1-NSD deployment information 2 includes the NST1-NSD specification 2.
  • the deployment information of the network slice subnet is NST1-NSD deployment information 2.
  • the deployment information of the network slice subnet may further include information other than the NST1-NSD specification ID, for example, may be one or more of the following information, and the following information may not be included in the NST1, and It is calculated according to the network slice requirement information: the instantiation level of the virtual resource of the network slice 1, the affinity and anti-affinity of the network slice 1 virtual resource deployment, and the location constraint information of the network slice 1 virtual resource deployment.
  • the deployment information of the network function may include a virtual resource descriptor identifier corresponding to the network function, and a virtual resource deployment specification identifier corresponding to the network function.
  • the deployment information of the network function may further include at least one of the following information, where the following information may be not included in the NFT, but calculated according to the network function requirement information: a virtual resource instantiation level corresponding to the network function, and the network function corresponds to The affinity and anti-affinity of the virtual resource deployment, and the deployment location constraint information of the virtual resource corresponding to the network function.
  • the deployment information of the network slice subnet may include a virtual resource descriptor identifier corresponding to the network slice subnet, and/or a virtual resource deployment specification identifier corresponding to the network slice subnet.
  • the deployment information of the network slice subnet may also include at least one of the following information.
  • the following information may be not included in the NSST, but is calculated according to the network slice subnet requirement information: the virtual resource instance corresponding to the network slice subnet.
  • the deployment information of the network slice may be sent to the management and orchestration device, and the management and orchestration device deploys the virtual resource of the network slice according to the deployment information of the network slice.
  • the network management device associated with the network slice template decomposes the network slice requirement information into the network function requirement information, and the network function template is The demand information of the identification and network function is sent to the network function management device associated with the network function.
  • the network function management device acquires the deployment information of the network function according to the received network function template identifier and the network function requirement information, and sends the deployment information of the network function to the network management device.
  • the network management device can receive the deployment information of multiple network functions, and obtain the complete network slice deployment information according to the deployment information of the multiple network functions.
  • the deployment information of the network slice includes the association relationship between the network functions.
  • the deployment information sent to the management and orchestration device includes more comprehensive deployment information, which can improve the accuracy of the network slice deployment information determination.
  • FIG. 8 is a schematic structural diagram of a network entity 10 according to an embodiment of the present disclosure.
  • the first network entity 10 may include a processing unit 801 and a receiving unit 802, where:
  • the receiving unit 802 is configured to receive the first message sent by the second network entity 20, where the first message carries the first deployment information, where the first deployment information is deployment information of the network component.
  • the processing unit 801 is configured to determine second deployment information according to the first deployment information, where the second deployment information is deployment information of the network, where the network includes at least one network component.
  • the processing unit 801 determines the second deployment information according to the first deployment information, including:
  • the processing unit 801 determines second deployment information from the network template according to the first deployment information, where the network template includes deployment information of the at least one network.
  • the first network entity 10 further includes a sending unit 803. Before the processing unit 801 calls the receiving unit 802 to receive the first message sent by the second network entity, the processing unit 801 is further configured to invoke the sending unit 803. And sending a second message to the second network entity, where the second message carries the requirement information of the network component and the identifier of the network component template, and the requirement information of the network component and the identifier of the network component template are used to determine the first deployment information.
  • the first deployment information includes at least one of the following: a virtual resource descriptor identifier corresponding to the network component, a virtual resource deployment specification corresponding to the network component, a virtual resource instantiation level corresponding to the network component, and a network component corresponding Affinity and anti-affinity of the virtual resource deployment, deployment location constraint information of the virtual resource corresponding to the network component;
  • the second deployment information includes at least one of the following: the virtual resource descriptor identifier corresponding to the network, and the network corresponding The virtual resource deployment specification, the virtual resource instantiation level corresponding to the network, the affinity and anti-affinity of the virtual resource deployment corresponding to the network, and the deployment location constraint information of the virtual resource corresponding to the network.
  • the network component is a network slice subnet
  • the network component template is a network slice subnet template
  • the network is a network slice.
  • the first network entity 10 is a network management device.
  • the network component is a network function
  • the network component template is a network function template
  • the network is a network slice or a network slice subnet.
  • the first network entity 10 is a network management device or a domain management device.
  • the sending unit 803 is further configured to send, to the third network entity, a third message that carries the second deployment information.
  • the functions of the processing unit 801, the receiving unit 802, and the transmitting unit 803 may correspond to the corresponding description of the method for determining the deployment information of the network shown in FIG.
  • FIG. 9 is a schematic structural diagram of a network entity 20 according to an embodiment of the present disclosure.
  • the second network entity 20 may include a processing unit 901, a receiving unit 902, and a sending unit. 903, where:
  • the receiving unit 902 is configured to receive a second message sent by the first network entity, where the second message carries the requirement information of the network component and the identifier of the network component template.
  • the processing unit 901 is configured to determine, according to the network component template corresponding to the requirement information of the network component and the identifier of the network component template, the first deployment information, where the first deployment information is deployment information of the network component;
  • the sending unit 903 is configured to send a first message to the first network entity 10, where the first message carries the first deployment information.
  • the network component template includes deployment information of the at least one network component; the processing unit 901 determines the first deployment information according to the network component template corresponding to the network component's requirement information and the network component template identifier, including: the processing unit The first deployment information is determined from the deployment information of the at least one network component according to the requirement information of the network component.
  • the first deployment information includes at least one of the following: a virtual resource descriptor identifier corresponding to the network component, a virtual resource deployment specification corresponding to the network component, a virtual resource instantiation level corresponding to the network component, and a network component corresponding The affinity and anti-affinity of the virtual resource deployment, and the deployment location constraint information of the virtual resource corresponding to the network component.
  • the network component is a network slice subnet
  • the network component template is a network slice subnet template
  • the network is a network slice.
  • the network component is a network function
  • the network component template is a network function template
  • the network is a network slice or a network slice subnet.
  • the processing unit 901 is further configured to: when detecting that the network component meets the preset condition, determine third deployment information according to the preset condition, where the third deployment information is deployment information of the network component;
  • the method includes at least one of the following: the number of users carried on the network component is greater than a preset threshold, or the second network entity is detected to be faulty;
  • the sending unit 903 is further configured to send, to the first network entity 10, a fourth message that carries the third deployment information.
  • the functions of the processing unit 901, the receiving unit 902, and the sending unit 903 may be corresponding to the corresponding description in the method for determining the deployment information of the network shown in FIG. 4, and details are not described herein again.
  • FIG. 10 is a schematic structural diagram of another network entity 10 according to the embodiment of the present disclosure.
  • the first network entity 10 includes: one or more network processors 1001.
  • a memory 1002 a communication interface 1003, a transmitter 1005, a receiver 1006, a coupler 1007, and an antenna 1008.
  • These components can be connected by bus 1004 or other means, and FIG. 10 is exemplified by a bus connection. among them:
  • Communication interface 1003 can be used by first network entity 10 to communicate with other communication devices, such as second network entity 20.
  • the first network entity 10 may be the network management device 102 in the network system architecture shown in FIG. 1.
  • the network management device 102 may communicate with the service management device, the domain management device, and the network function shown in FIG. 1 through the communication interface 1003.
  • the first network entity 10 can also be a domain management device 103 in the network system architecture shown in FIG. 1, and the domain management device 103 can communicate with the network function management device shown in FIG. 1 through the communication interface 1003.
  • the communication interface 1003 may be a long term evolution (LTE) system communication interface, or may be a communication interface of 5G or a future new air interface.
  • LTE long term evolution
  • the first network entity 10 may also be configured with a wired communication interface 1003 to support wired communication.
  • a backhaul link between a first network entity 10 and other network devices may be a wired communication connection.
  • the transmitter 1005 can be used to perform transmission processing on messages or data output by the network processor 1001.
  • transmitter 1005 and receiver 1006 can be viewed as a wireless modem.
  • the number of the transmitter 1005 and the receiver 1006 may each be one or more.
  • Transmitter 1005 and receiver 1006 may also be implemented by one or more transceivers.
  • the antenna 1008 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • the coupler 1007 can be used to divide the mobile pass signal into multiple channels and distribute it to a plurality of receivers 1006.
  • Memory 1002 is coupled to network processor 1001 for storing various software programs and/or sets of instructions.
  • the memory 1002 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as uCOS, VxWorks, or RTLinux.
  • the memory 1002 can also store a program determined by the deployment information of the network, the program determined by the deployment information of the network can be used to communicate with one or more additional devices, one or more network devices.
  • the network processor 1001 can be used to perform wireless channel management, implement call and communication link establishment and teardown, and determine network deployment information and the like.
  • the network processor 1001 can be used to read and execute computer readable instructions. Specifically, the network processor 1001 can be used to invoke a deployment information determination program of a network stored in the memory 1002.
  • the memory 1002 can be used to store an implementation program of the deployment information determining method of the network provided by one or more embodiments of the present application on the side of the first network entity 10.
  • the receiver 1006 is configured to receive a first message sent by the second network entity, where the first message carries the first deployment information, where the first deployment information is deployment information of the network component.
  • the network processor 1001 is configured to call program instructions and data stored in the memory 1002, and performs the following operations:
  • the network processor 1001 determines the second deployment information according to the first deployment information, including:
  • the network processor 1001 is configured to invoke program instructions and data execution stored in the memory 1002 to determine the second deployment information from the network template according to the first deployment information, where the network template includes deployment information of at least one network.
  • the transmitter 1005 further sends a second message to the second network entity, where the second message carries the network component requirement information and the network component template.
  • the identifier of the network component and the identifier of the network component template are used to determine the first deployment information.
  • the first deployment information includes at least one of the following: a virtual resource descriptor identifier corresponding to the network component, a virtual resource deployment specification corresponding to the network component, and a virtual resource instantiation level corresponding to the network component.
  • the second deployment information includes at least one of the following: a virtual resource descriptor identifier corresponding to the network, a virtual resource deployment specification corresponding to the network, a virtual resource instantiation level corresponding to the network, and affinity and anti-affinity of the virtual resource deployment corresponding to the network, The deployment location constraint information of the virtual resource corresponding to the network.
  • the network component is a network slice subnet
  • the network component template is a network slice subnet template
  • the network is a network slice.
  • the network component is a network function
  • the network component template is a network function template
  • the network is a network slice or a network slice subnet.
  • the transmitter 1006 sends a third message that carries the second deployment information to the third network entity.
  • network entity 10 shown in FIG. 10 is only one implementation of the embodiment of the present application. In an actual application, the network entity 10 may further include more or fewer components, which are not limited herein.
  • FIG. 11 is a schematic structural diagram of another network entity 20 according to the embodiment of the present application.
  • the first network entity 20 includes: one or more network processors 1101. Memory 1102, communication interface 1103, transmitter 1105, receiver 1106, coupler 1107, and antenna 1108. These components may be connected by bus 1104 or other means, and FIG. 11 is exemplified by a bus connection. among them:
  • Communication interface 1103 can be used by first network entity 20 to communicate with other communication devices, such as first network entity 10.
  • the second network entity 20 may be the domain management device 103 in the network system architecture shown in FIG. 1, and the domain management device 103 may communicate with the network management device shown in FIG. 1 through the communication interface 1103.
  • the second network entity 20 can also be the network function management device 104 in the network system architecture shown in FIG. 1, and the network function management device 104 can communicate with the domain management device and the network management device shown in FIG. 1 through the communication interface 1003.
  • the communication interface 1103 may be a long term evolution (LTE) system communication interface, or may be a 5G or a future communication interface of a new air interface.
  • LTE long term evolution
  • the second network entity 20 may also be configured with a wired communication interface 1103 to support wired communication.
  • a backhaul link between a second network entity 20 and other network devices may be a wired communication connection.
  • the transmitter 1105 can be used to perform transmission processing on messages or data output by the network processor 1101.
  • transmitter 1105 and receiver 1106 can be viewed as a wireless modem.
  • the number of the transmitter 1105 and the receiver 1106 may each be one or more.
  • Transmitter 1105 and receiver 1106 may also be implemented by one or more transceivers.
  • the antenna 1108 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • Coupler 1007 can be used to divide the mobile pass signal into multiple channels and distribute it to multiple receivers 1106.
  • Memory 1102 is coupled to network processor 1101 for storing various software programs and/or sets of instructions.
  • the memory 1102 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as uCOS, VxWorks, or RTLinux.
  • the memory 1002 can also store a program determined by the deployment information of the network, the program determined by the deployment information of the network can be used to communicate with one or more additional devices, one or more network devices.
  • the network processor 1101 can be used to perform wireless channel management, implement call and communication link establishment and teardown, and determine network deployment information and the like.
  • the network processor 1101 can be used to read and execute computer readable instructions. Specifically, the network processor 1101 can be used to invoke a deployment information determination program of a network stored in the memory 1102.
  • the memory 1102 can be used to store an implementation program of the deployment information determining method of the network provided by one or more embodiments of the present application on the second network entity 20 side.
  • the receiver 1106 is configured to receive a second message sent by the first network entity, where the second message carries the requirement information of the network component and the identifier of the network component template.
  • the network processor 1101 can be used to invoke a program stored in the memory 1102 to perform the following operations:
  • the transmitter 1105 is configured to send a first message to the first network entity, where the first message carries the first deployment information.
  • the network component template includes deployment information of the at least one network component; the network processor 1101 determines the first deployment information according to the network component template corresponding to the requirement information of the network component and the identifier of the network component template, including The network processor 1101 determines the first deployment information from the deployment information of the at least one network component according to the requirement information of the network component.
  • the first deployment information includes at least one of the following: a virtual resource descriptor identifier corresponding to the network component, a virtual resource deployment specification corresponding to the network component, and a virtual resource instantiation level corresponding to the network component. Affinity and anti-affinity of the virtual resource deployment corresponding to the network component, and deployment location constraint information of the virtual resource corresponding to the network component.
  • the network component is a network slice subnet
  • the network component template is a network slice subnet template
  • the network is a network slice.
  • the network component is a network function
  • the network component template is a network function template
  • the network is a network slice or a network slice subnet.
  • the network processor 1101 is further configured to: when the second network entity detects that the network component meets a preset condition, determine third deployment information according to the preset condition, where the third deployment information is The configuration information of the network component; the preset condition includes at least one of the following: the number of users carried on the network component is greater than a preset threshold, or the second network entity is detected to be faulty;
  • the transmitter 1105 sends the fourth information carrying the third deployment information to the first network entity.
  • the network entity 20 shown in FIG. 11 is only one implementation of the embodiment of the present application. In actual applications, the network entity 20 may further include more or fewer components, which are not limited herein.
  • FIG. 12 is a schematic structural diagram of a device according to an embodiment of the present invention.
  • apparatus 120 can include a processor 1201 and one or more interfaces 1202 coupled to processor 1201. among them:
  • the processor 1201 can be used to read and execute computer readable instructions.
  • the processor 1201 may mainly include a controller, an operator, and a register.
  • the controller is mainly responsible for instruction decoding, and sends a control signal for the operation corresponding to the instruction.
  • the operator is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logic operations, as well as performing address operations and conversions.
  • the register is mainly responsible for saving the register operands and intermediate operation results temporarily stored during the execution of the instruction.
  • the hardware architecture of the processor 1201 may be an Application Specific Integrated Circuits (ASIC) architecture or the like.
  • the processor 1201 may be single core or multi-core.
  • the interface 1202 can be used to input data to be processed to the processor 1201, and can output the processing result of the processor 1201 to the outside.
  • the processor 1201 may be configured to invoke, from the memory, an implementation program of the deployment information determining method of the network provided by one or more embodiments of the present application on the first network entity side, and execute the instructions included in the program.
  • the interface 1202 can be used to output the execution result of the processor 1201.
  • processor 1201 and the interface 1202 can be implemented by using a hardware design or a software design, and can also be implemented by a combination of software and hardware, which is not limited herein.
  • FIG. 13 is a schematic structural diagram of another apparatus according to an embodiment of the present invention.
  • apparatus 130 can include a processor 1301 and one or more interfaces 1302 coupled to processor 1301. among them:
  • the processor 1301 can be used to read and execute computer readable instructions.
  • the processor 1301 may mainly include a controller, an operator, and a register.
  • the controller is mainly responsible for instruction decoding, and sends a control signal for the operation corresponding to the instruction.
  • the operator is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logic operations, as well as performing address operations and conversions.
  • the register is mainly responsible for saving the register operands and intermediate operation results temporarily stored during the execution of the instruction.
  • the hardware architecture of the processor 1301 may be a dedicated ASIC architecture or the like.
  • the processor 1301 may be single core or multi-core.
  • the interface 1302 can be used to input data to be processed to the processor 1301, and can output the processing result of the processor 1301 to the outside.
  • the processor 1301 may be configured to invoke, from the memory, an implementation program of the deployment information determining method of the network provided by one or more embodiments of the present application on the second network entity side, and execute the instructions included in the program.
  • the interface 1302 can be used to output the execution result of the processor 1301.
  • processor 1301 and the interface 1302 can be implemented by using a hardware design or a software design, and can also be implemented by a combination of software and hardware, which is not limited herein.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software program instructions.
  • the software program instructions may be composed of corresponding software modules, which may be stored in RAM, flash memory, ROM, Erasable Programmable ROM (EPROM), and electrically erasable programmable read only memory (Electrically EPROM). , EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a transceiver or relay device.
  • the processor and the storage medium may also reside as a discrete component in either the first network entity or the second network entity.
  • processors in the embodiment of the present application may be a central processing unit (CPU), and may be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof.
  • a general purpose processor can be a microprocessor or any conventional processor.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Transfer from a computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)) or the like.

Landscapes

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

Abstract

本申请公开了一种网络的部署信息确定方法及设备，该网络的部署信息确定方法包括：第一网络实体接收第二网络实体发送的第一消息；第一消息携带第一部署信息，第一部署信息为网络组件的部署信息；第一网络实体根据第一部署信息确定第二部署信息，第二部署信息为网络的部署信息，网络包含至少一个网络组件。上述方案可以提高网络的部署信息确定的准确性。

Description

网络的部署信息确定方法及设备 技术领域
本发明实施例涉及通信技术领域，尤其涉及一种网络的部署信息确定方法及设备。
背景技术
网络切片(network slice，NS)是保证承载的业务能达成服务水平协议(service level agreement，SLA)要求的通信资源。这些资源可以按照需求进行硬隔离(即物理隔离)，也可以进行逻辑隔离(即软隔离)。可以认为一个网络切片是完成某个或某些服务所需的网络功能及资源的组合，是一个完整的逻辑网络。网络切片在自动部署时，需要预先设计和规划生成网络切片模板，之后对网络切片模板进行实例化。生成网络切片实例是线下设计的网络切片模板上线的过程。
目前，在生成网络切片实例过程中，网络管理设备在接收到网络切片需求信息时，可以根据网络切片需求信息计算得到网络切片的部署信息。网络服务描述符(network service descriptor，NSD)是厂商用来部署网络服务的模板，一个NSD中可以包含不同的部署规格(deployment flavor)。网络切片的部署信息中可以包含网络切片模板NSD的身份标识、NSD部署规格的身份标识和实例化等级等信息。网络管理设备可以将携带网络切片的部署信息的实例化请求发送给管理和编排设备，管理和编排设备根据该网络切片的部署信息进行实例化。
然而，网络切片模板可以包含多个网络切片子网，当不同的网络切片子网中根据网络切片需求信息计算网络切片的部署信息的算法不相同时，网络管理设备无法根据接收到的网络切片需求信息准确计算得到网络切片的部署信息，从而降低了网络的部署信息确定的准确性。
发明内容
本申请实施例提供一种网络的部署信息确定方法及设备，在网络模板中嵌套有网络组件模板的情况下，在发送给管理与编排设备的部署信息中包含了更全面的部署信息，从而可以提高网络的部署信息确定的准确性。
第一方面，本申请实施例提供了一种网络的部署信息确定方法，包括：第一网络实体接收第二网络实体发送的第一消息；所述第一消息携带第一部署信息，所述第一部署信息为网络组件的部署信息；所述第一网络实体根据所述第一部署信息确定第二部署信息，所述第二部署信息为网络的部署信息，所述网络包含至少一个所述网络组件。在网络模板中嵌套有多个网络组件模板的情况下，第一网络实体可以接收到多个网络组件的部署信息，并根据这多个网络组件的部署信息获取完整的网络的部署信息，网络的部署信息包含各个网络组件之间的关联关系，在发送给管理与编排设备的部署信息中包含了更全面的部署信息，可以提高网络的部署信息确定的准确性。
在一个实施例中，所述第一网络实体根据所述第一部署信息确定第二部署信息，包括：所述第一网络实体根据所述第一部署信息从网络模板中确定所述第二部署信息，所述网络 模板包括至少一个网络的部署信息。可以将包含网络的部署信息的网络模板预存在数据库中，供第一网络实体调用，第一网络实体获取的网络的部署信息中包含了更全面的部署信息，可以提高网络的部署信息确定的准确性。
在一个实施例中，所述第一网络实体接收第二网络实体发送的第一消息之前，所述方法还包括：所述第一网络实体向所述第二网络实体发送第二消息，所述第二消息携带网络组件的需求信息和网络组件模板的标识，所述网络组件的需求信息和所述网络组件模板的标识用于确定所述第一部署信息。
在一个实施例中，所述第一网络实体向所述第二网络实体发送第二消息之前，所述方法还包括：所述第一网络实体根据网络模板获取所述网络组件模板的标识；所述第一网络实体将根据所述网络的需求信息获取所述网络组件的需求信息。
在一个实施例中，所述第一部署信息包括以下至少一种：所述网络组件对应的虚拟资源描述符标识，所述网络组件对应的虚拟资源部署规格，所述网络组件对应的虚拟资源实例化等级，所述网络组件对应的虚拟资源部署的亲和性和反亲和性，所述网络组件对应的虚拟资源的部署位置约束信息；所述第二部署信息包括以下中的至少一种：所述网络对应的虚拟资源描述符标识，所述网络对应的虚拟资源部署规格，所述网络对应的虚拟资源实例化等级，所述网络对应的虚拟资源部署的亲和性和反亲和性，所述网络对应的虚拟资源的部署位置约束信息。
在一个实施例中，所述网络组件为网络切片子网，所述网络组件模板为网络切片子网模板，所述网络为网络切片。网络管理设备可以接收到多个网络切片子网的部署信息或者网络功能的部署信息，并根据这多个网络切片子网的部署信息或者网络功能的部署信息获取完整的网络切片的部署信息，网络切片的部署信息包含各个网络切片子网的部署信息或者网络功能之间的关联关系，在发送给管理与编排设备的部署信息中包含了更全面的部署信息，可以提高网络切片的部署信息确定的准确性。
在一个实施例中，所述网络组件为网络功能，所述网络组件模板为网络功能模板，所述网络为网络切片或者网络切片子网。网络管理设备或者域管理设备可以接收到多个网络功能的部署信息，并根据这多个网络功能的部署信息获取完整的网络切片的部署信息或者网络切片子网的部署信息，网络切片的部署信息或者网络切片子网的部署信息包含各个网络功能之间的关联关系，在发送给管理与编排设备的部署信息中包含了更全面的部署信息，可以提高网络的部署信息确定的准确性。
在一个实施例中，所述第一网络实体根据所述第一部署信息确定第二部署信息之后，所述方法还包括：所述第一网络实体向第三网络实体发送携带所述第二部署信息的第三消息。
第二方面，本申请实施例提供了另一种网络的部署信息确定方法，包括：第二网络实体接收第一网络实体发送的第二消息，所述第二消息携带网络组件的需求信息和网络组件模板的标识；所述第二网络实体根据所述网络组件的需求信息和所述网络组件模板的标识对应的网络组件模板确定第一部署信息，所述第一部署信息为网络组件的部署信息；所述第二网络实体向所述第一网络实体发送第一消息，所述第一消息携带所述第一部署信息。在网络模板中嵌套有多个网络组件模板的情况下，第一网络实体可以接收到多个网络组件 的部署信息，并根据这多个网络组件的部署信息获取完整的网络的部署信息，网络的部署信息包含各个网络组件之间的关联关系，在发送给管理与编排设备的部署信息中包含了更全面的部署信息，可以提高网络的部署信息确定的准确性。
在一个实施例中，所述网络组件模板包含至少一个网络组件的部署信息；所述第二网络实体根据所述网络组件的需求信息和所述网络组件模板的标识对应的网络组件模板确定第一部署信息，包括：所述第二网络实体根据所述网络组件的需求信息从所述至少一个网络组件的部署信息中确定所述第一部署信息。
在一个实施例中，所述第一部署信息包括以下至少一种：所述网络组件对应的虚拟资源描述符标识，所述网络组件对应的虚拟资源部署规格，所述网络组件对应的虚拟资源实例化等级，所述网对应的虚拟资源络组件部署的亲和性和反亲和性，所述网络组件对应的虚拟资源的部署位置约束信息。
在一个实施例中，所述网络组件为网络切片子网，所述网络组件模板为网络切片子网模板，所述网络为网络切片。
在一个实施例中，所述网络组件为网络功能，所述网络组件模板为网络功能模板，所述网络为网络切片或者网络切片子网。
在一个实施例中，所述方法还包括：当所述第二网络实体检测到所述网络组件满足预设条件时，所述第二网络实体根据所述预设条件确定第三部署信息，所述第三部署信息为所述网络组件的部署信息；所述预设条件包含以下至少一种：所述网络组件上承载的用户数量大于预设阈值，或者检测到所述第二网络实体发生故障；所述第二网络实体向所述第一网络实体发送携带所述第三部署信息的第四消息。例如，当第二网络实体发生故障时，第二网络实体可以根据相关故障信息生成第三部署信息，然后发送给第一网络实体。此时，第一网络实体根据第三部署信息来部署网络。
第三方面，本申请实施例提供了一种网络实体，该网络实体包括用于执行第一方面或第一方面的任一种可能实现方式所提供的网络的部署信息确定方法的模块或单元。
第四方面，本申请实施例提供了另一种网络实体，该网络实体包括用于执行第二方面或第二方面的任一种可能实现方式所提供的网络的部署信息确定方法的模块或单元。
第五方面，本申请实施例提供了又一种网络实体，包括：处理器，存储器，收发器和总线；处理器、收发器、存储器通过总线相互通信；收发器，用于接收和发送数据；存储器，用于存储指令；处理器，用于调用存储器中的指令，执行第一方面或第一方面的任一种可能实现方式所提供的网络的部署信息确定方法。
第六方面，本申请实施例提供了再一种网络实体，包括：处理器，存储器，收发器和总线；处理器、收发器、存储器通过总线相互通信；收发器，用于接收和发送数据；存储器，用于存储指令；处理器，用于调用存储器中的指令，执行第二方面或第二方面的任一种可能实现方式所提供的网络的部署信息确定方法。
第七方面，本申请实施例提供了一种计算机可读存储介质，该存储介质包括指令，当该指令在网络实体上运行时，使得网络实体执行第一方面或第一方面的任一种可能实现方式所提供的网络的部署信息确定方法。
第八方面，本申请实施例提供了另一种计算机可读存储介质，该存储介质包括指令， 当该指令在网络实体上运行时，使得网络实体执行第二方面或第二方面的任一种可能实现方式所提供的网络的部署信息确定方法。
第九方面，本申请实施例提供了一种计算机程序，该计算机程序包括指令，当该指令在网络实体上运行时，使得网络实体执行第一方面或第一方面的任一种可能实现方式所提供的网络的部署信息确定方法。
第十方面，本申请实施例提供了另一种计算机程序，该计算机程序包括指令，当该指令在网络实体上运行时，使得网络实体执行第二方面或第二方面的任一种可能实现方式所提供的网络的部署信息确定方法。
第十一方面，本申请实施例提供了一种网络实体的芯片产品，以执行第一方面或第一方面的任意可能的实现方式中的方法。
第十二方面，本申请实施例提供了另一种网络实体的芯片产品，以执行第二方面或第二方面的任意可能的实现方式中的方法。
本申请实施例中，在网络模板中嵌套有网络组件模板的情况下，与网络模板关联的第一网络实体将网络的需求信息分解为网络组件的需求信息，将网络组件模板标识和网络组件的需求信息发送给网络组件关联的第二网络实体。第二网络实体根据接收到的网络组件模板标识和网络组件的需求信息获取网络组件的部署信息，将该网络组件的部署信息发送给第一网络实体。在网络模板中嵌套有多个网络组件模板的情况下，第一网络实体可以接收到多个网络组件的部署信息，并根据这多个网络组件的部署信息获取完整的网络的部署信息，网络的部署信息包含各个网络组件之间的关联关系，在发送给管理与编排设备的部署信息中包含了更全面的部署信息，可以提高网络的部署信息确定的准确性。
附图说明
图1是本申请实施例涉及的一种网络系统的架构示意图；
图2是本申请实施例提供的一种NST和NSST的结构示意图；
图3是现有技术提供的一种网络的部署信息确定方法的流程示意图；
图4是本申请实施例提供的一种网络的部署信息确定方法的流程示意图；
图5是本申请实施例提供的另一种NST和NSST的结构示意图；
图6是本申请实施例提供的一种NSST和NFT的结构示意图；
图7是本申请实施例提供的一种NST和NFT的结构示意图；
图8是本申请实施例提供的一种网络实体10的结构示意图；
图9是本申请实施例提供的一种网络实体20的结构示意图；
图10是本申请实施例提供的另一种网络实体10的结构示意图；
图11是本申请实施例提供的另一种网络实体20的结构示意图；
图12是本发明实施例提供的一种装置的结构示意图；
图13是本发明实施例提供的另一种装置的结构示意图。
具体实施方式
首先，为了便于理解本申请实施例，对本申请实施例涉及的一些概念或术语进行解释。
(1)网络切片
网络切片(network slice，NS)是指根据不同的服务需求定制化的、不同的逻辑网络。可以认为一个网络切片是完成某个或者某些业务所需的网络功能及资源的组合，是一个完整的逻辑网络。网络切片可以是一个包括了终端、接入网(access network，AN)、传输网(transport network，TN)、核心网(core network，CN)和应用服务器的端到端网络，能够提供完整的电信服务，具有一定网络能力。网络切片也可以是上述终端、接入网、传输网、核心网和应用服务器的任意组合。不同的网络切片之间可以按不同需求，进行硬隔离，即物理隔离，也可以进行软隔离，即逻辑隔离。这里网络切片可以是一个广义的概念，可以把传统的网络或者专用的网络均作为一个网络切片，也可以认为网络切片子网也是一种网络切片。
(2)网络服务
网络服务(network service，NS)可以由多个虚拟网络功能(virtualized network function，VNF)来实现，可以认为网络服务是网络切片对应的底层虚拟资源，所以在部署网络切片的时候需要实例化相应的网络服务。网络服务描述符(network service descriptor，NSD)是厂商用来部署网络服务的模板，一个NSD中可以包含不同的部署规格(deployment flavor)。可以通过NSD的标识(如NSD ID)来区分不同的网络服务描述符，用NSD的部署规格的标识(如部署规格ID)来区分同一个网络服务描述中不同规格的网络服务，NSD的标识和NSD的部署规格的标识唯一确定的网络服务可以称为一个网络切片模板的虚拟资源或者一个网络切片子网模板的虚拟资源。
(3)网络切片模板
网络切片模板(network slice template，NST)是在线下设计和规划网络时生成的。可以根据网络切片上预期运行的特定业务的特点选择相应的特性，包括所需要的功能、性能、安全、可靠性、业务体验、运维特征等，设计完成后生成切片模板。线下设计完成后的网络切片模板可以在线实例化为网络切片实例。一次设计多次部署是网络切片模板的原则。网络切片模板中可以嵌套网络切片子网模板(network slice subnet template，NSST)和/或网络功能模板(network function template，NFT)，嵌套的意思是指一个网络切片模板可以由一个或多个网络切片子网模板或网络功能模板组成，也可以是指一个网络切片模板包含一个或者多个网络切片子网模板的标识或者网络功能模板的标识，该标识指示一个网络切片子网模板或者网络功能模板。另外，网络切片子网模板中也可以嵌套有网络功能模板。本文中，嵌套在网络切片模板的网络切片子网模板或者网络功能模板可以统一称为网络组件模板，相应的由网络切片子网模板和/或网络功能模板组成的网络切片模板可以称为网络模板。嵌套在网络切片子网模板或者网络切片模板的网络功能模板可以称为网络组件模板，相应的由网络功能模板组成的网络切片子网模板或者网络切片模板称为网络模板。
本申请中，网络切片模板可以包含两层或两层以上的嵌套关系。例如网络切片模板中嵌套网络切片子网模板和/或网络功能模板，其中的网络切片子网模板中又嵌套有网络功能模板。可以理解的是，上述的网络和网络组件的关系是针对任两级的嵌套关系而言的。本申请以两层嵌套为例进行阐述，更多层的嵌套关系也可以类推，不加赘述。本申请中网络切片模板、网络切片子网模板和网络功能模板均是依据功能命名的，不对名称作任何限制， 上述每一个模板还可以有其他名称，例如网络切片描述符、网络切片子网描述符和网络功能描述符。
(4)网络切片实例
网络切片实例(network slice instance，NSI)是对基于网络切片模板实例化得到的，即是一个真实运行的逻辑网络，能满足一定网络特性或服务需求。一个网络切片实例可以提供一种或多种服务。网络切片实例可以由管理与编排设备创建，一个管理与编排设备可以创建多个网络切片实例并同时对它们进行管理，包括在网络切片实例运行过程中的性能监视和故障管理等。当多个网络切片实例共存时，网络切片实例之间可以共享部分网络资源和网络功能。一个完整的网络切片实例是能够提供完整的端到端的网络服务的，而组成网络切片实例的可以是网络切片子网实例(network slice subnet instance，NSSI)和/或网络功能实例。
一个网络切片实例可以划分为若干个网络切片子网实例，以方便管理与编排设备管理。网络切片子网实例可以不需要提供端到端的完整的网络服务，网络切片子网实例可以是网络切片实例中同一个设备商的网络功能实例组成集合，也可以是按域划分的网络功能实例的集合，例如核心网网络切片子网实例、接入网网络切片子网实例，或由部署位置等其他方式组成集合。网络切片子网实例可以被多个网络切片实例共享。一个网络切片实例可以由若干网络切片子网实例和没有被划分为网络切片子网实例的网络功能实例组成。一个网络切片实例也可以仅由若干网络功能实例组成。一个网络切片子网实例也可以由若干网络功能实例组成。
(5)网络功能
网络功能(network function，NF)是网络中的一种处理功能，定义了功能性的行为和接口。网络功能可以通过专用硬件实现，也可以通过在专用硬件上运行软件实现，也可以在通用的硬件平台上以虚拟功能的形式实现。以下统称物理网络功能和/或虚拟化的网络功能为网络功能。
(6)虚拟资源
虚拟资源是借助虚拟化平台在物理资源上构建出来的逻辑资源，用于支持网络。例如，虚拟计算资源(virtual CPU，vCPU)，用于实现网络中的计算和处理功能。本文中实现网络切片或者网络切片子网所需的虚拟资源可以称为网络服务NS，实现网络功能所需的虚拟资源可以称为VNF。
(7)网络或者网络组件的需求信息
网络或者网络组件的需求信息可以包括时延(latency)要求、带宽要求、覆盖范围要求、用户数量要求(容量要求)、移动性要求、吞吐率要求、可靠性要求、部署位置要求、亲和性反亲和性要求、成功率要求和网络切片类型要求等中的一个或多个。
具体地，时延要求是指对网络或网络组件的响应时间的要求，时延要求可以是最大时延不超过预设阈值，其中最大时延是指网络或网络组件的最大响应时间。例如要求网络或网络组件的最大时延为10ms，即希望网络或网络组件的最大响应时间为10ms。带宽要求可以用于描述要求网络或网络组件提供的带宽，例如，要求网络或网络组件的最小带宽为10M。覆盖范围要求用于描述网络或网络组件使用的网络覆盖区域，例如上海地区。用户 数量要求用于描述要求该网络或网络组件承载的最大的用户数量。例如网络或网络组件在部署前预计为100万用户会接入，则用户数量要求为大于等于100万。移动性要求用于描述接入该网络或网络组件的终端设备的移动情况，比如移动或者固定。移动性要求还可以进一步描述接入该网络或网络组件的终端设备的移动速率。亲和性反亲和性要求是指网络或网络组件与其他的网络或网络组件之间的部署位置要求。成功率用于描述终端设备使用该网络或网络组件的成功率，可以包括上报成功率和下发成功率。吞吐率要求描述网络或者网路组件的数据转发能力，比如100Mbit/s,表示该网络或者网络组件在一秒内支持传输100Mbit的数据。可靠性要求用于表示网络或者网络组件的完成其功能的能力或者持续工作的程度。网络切片类型要求可以是按照功能进行划分，例如网络切片类型可以是以下中的一种：增强型移动宽带(enhanced mobile broadband，eMBB)、高可靠低时延通信(ultra reliable and low latency communications，URLLC)以及海量机器类通信(massive machine type communications，mMTC)。
在一种可能的场景下，网络切片中可以嵌套网络切片子网或者网络功能，网络切片可以是网络，网络切片子网或者网络功能可以是网络组件。在另一种可能的场景下，网络切片子网中可以嵌套网络功能，网络切片子网可以是网络，网络功能可以是网络组件。
在以上两种场景下，网络切片的需求信息可以是业务管理设备根据接收到的运营商和/或第三方客户的业务需求获取得到的，并发送给网络管理设备的。可选地，可以在网络切片模板本地存储业务需求到网络需求的算法或者策略用于实现将业务需求转化为网络切片的需求信息。比如业务需求为业务类型是车联网(vehicle to vehicle，V2X)的业务，由于V2X业务要求高可靠性低时延，可以预先建立映射策略将V2X的业务映射为需求信息：网络切片类型要求是URLLC。
网络切片子网的需求信息可以是网络管理设备根据预存的策略或算法分解网络切片的需求信息为各网络组件的需求信息，并下发给域管理设备的。预存的策略或算法可以是通过一个策略标识或者算法标识指示进行需求信息分配的。例如，该策略标识或者算法标识可以指示将网络切片的需求信息根据不同的网络域按照预设比例进行需求信息分配的。再例如，该策略标识或者算法标识也可以是指示根据不同的网络切片子网模板在某一地理位置按照预设比例进行需求信息分解等等。
网络功能的需求信息可以是网络管理设备和/或域管理设备根据预存的策略或算法分解网络切片和/或网络切片子网的需求信息为各网络功能的需求信息，并下发给网络功能管理设备的。
(8)网络或者网络组件的部署信息
网络或者网络组件的部署信息可以包括网络或者网络组件对应的虚拟资源描述符标识和/或网络或者网络组件对应的虚拟资源部署规格标识。网络或者网络组件的部署信息还可以包括以下中的一个或多个：网络或网络组件对应的虚拟资源的实例化等级、网络或网络组件对应的虚拟资源的位置约束信息、网络或网络组件对应的虚拟资源部署的亲和性和反亲和性信息。该部署信息中的某些信息还可以是根据本地预存的算法计算得到的，例如，亲和性和反亲和性信息可以是根据本地预存的算法计算得到的。如果对时延要求高，即网络或网络组件需求信息中的时延要求高，就可以设置亲和性和反亲和性信息对应的参数用 来将网络或网路组件部署在基站附近，来降低与基站的通信时延。
网络或者网络组件的部署信息可以是根据网络或网络组件的需求信息计算得到的NSD profile。则网络或者网络组件对应的虚拟资源描述符标识可以是网络服务描述符标识(即NSD ID)或者虚拟网络功能描述符(VNF descriptor，VNFD)标识(VNFD ID)。网络或者网络组件对应的虚拟资源部署规格标识可以是网络服务部署规格标识(即NS Flavor ID)或者虚拟网络功能部署规格标识(即VNF Flavor ID)。网络或者网络组件对应的虚拟资源实例化等级可以是网络服务实例化等级(NSInstantiationlevel)或者虚拟网络功能实例化等级(VNFInstantiationlevel)。网络或者网络组件对应的虚拟资源部署的亲和性和反亲和性也可以包括网络服务的亲和性和反亲和性或者VNF的亲和性和反亲和性。网络或者网络组件对应的虚拟资源的部署位置约束信息也可以包括网络服务的部署位置的约束信息或VNF的部署位置的约束信息。
其中，网络或者网络组件对应的虚拟资源实例化等级是用于表示虚拟资源实例的容量，不同的虚拟资源实例化等级的容量不同。这里的容量可以表征网络或网络组件的承载能力，例如可以是承载用户的数量。网络或者网络组件对应的虚拟资源部署的亲和性和反亲和性信息是指网络或者网络组件对应的虚拟资源是否可以与另一功能的网络或者网络组件部署在同一区域。例如网络或者网络组件可以与数据中心(DataCenter)、服务器等部署在一起。网络或者网络组件对应的虚拟资源位置约束信息是指根据该网络或者网络组件的功能需求对该网络或者网络组件对应的虚拟资源部署的地理位置的限定。例如，网络或者网络组件对应的虚拟资源需要与某个数据中心交互信息，为方便与该数据中心交互，该网络或者网络组件对应的虚拟资源可以部署在该数据中心。再例如，该网络或者网络组件对通信时延要求较高，对应的虚拟资源可以部署在靠近基站的位置来降低通信时延等等。
可选地，网络或者网络组件的部署信息还可能包含以下信息中的至少一个：已部署物理网络功能的描述信息、现有VNF实例信息。已部署物理网络功能的描述信息用于告知管理与编排设备如何连接虚拟资源到该物理网络功能，比如该物理网络功能的连接信息等，具体如IP地址。现有VNF实例信息，用于指示存在VNF实例可以重用以及该重用的VNF实例信息，比如现有VNF实例的标识，现有VNF实例的规格等。
请参见图1，是本申请实施例涉及的一种网络系统的架构示意图。如图1所示，该网络系统100包括：业务管理(service management function，SMF)设备101、网络管理(network management，NM)设备102、域管理(domain management，DM)设备103、虚拟网络功能管理(virtualized network function manager，VNFM)设备和管理与编排(management and orchestration，MANO)设备105。
业务管理设备101，主要用于实现业务的管理，比如业务的生命周期管理，业务的监控，业务的计费等，并将运营商和/或第三方客户的业务需求转化为网络的需求信息，并通过和网络管理设备102之间的接口向网络管理设备102发送网络的需求信息。
网络管理设备102，用于接收业务管理设备101发送的网络管理请求，该请求可以携带网络的需求信息。网络管理设备102也可以具有以下一个或多个功能：对网络进行管理，包括对网络和/或网络子网的生命周期、性能、故障和配置等进行管理；还对网络模板和/ 或网络子网模板进行管理。网络管理设备102还用于在接收到网络请求时，根据网络请求获取网络模板，可以是根据网络请求中包含的网络模板指示信息(如网络模板的标识)获取的网络模板，也可以是根据网络请求中携带的网络的需求信息和网络管理设备102本地预存的分解算法计算匹配得到的网络模板。并根据网络的需求信息从匹配到的网络模板中获取网络的部署信息。网络管理设备102可以将获取的网络的部署信息通过与管理与编排设备105之间的接口发送给管理与编排设备105。
当网络模板中未嵌套网络子网模板和网络功能模板时，网络管理设备102可以进行上述的获取网络的部署信息的方法；当网络切片模板中嵌套有网络片子网模板或者网络功能模板时，网络管理设备102执行以下操作：网络管理设备102还用于解析网络模板来获取一个或多个网络子网模板标识和/或一个或多个网络功能模板的标识，并分解网络的需求信息为网络子网的需求信息和/或网络功能的需求信息。每个网络子网模板标识对应一个网络子网的需求信息；每个网络功能模板的标识对应一个网络功能的需求信息。将每个网络子网模板的标识和对应的网络子网需求信息通过与域管理设备103之间的接口发送给域管理设备103。网络管理设备102还通过与网络功能管理设备104之间的接口向各网络功能管理设备104发送网络功能模板标识和网络功能需求信息。
网络管理设备102还对各网络子网和/或网络功能统一编排，以使得不同网络子网和/或网络功能可以满足目标业务或者网络的需求信息。具体地，可以是以下业务或者网络的需求信息中的至少一种：服务等级协议(service-level agreement，SLA)的要求、关键性能指标(key performance indicator，KPI)的要求和服务质量(quality of service，QoS)的要求。
域管理设备103可以具有网络子网管理功能或者网络子网编排功能之一或者全部，可以具备以下部分或者全部功能：网络子网的生命周期管理，例如网络子网的创建、更新、删除、故障管理、性能管理、配置管理等；网络服务的管理，包括网络服务生命周期管理、网络服务故障管理、网络服务性能管理、网络服务配置管理；网络功能的协调等。域管理设备103还用于通过与网络管理设备102之间的接口接收网络管理设备102发送的网络子网模板的标识和对应的网络子网需求信息。域管理设备103可以关联一个或多个的网络子网模板。这里的关联可以理解为管理。域管理设备103可以根据管理的网络切片子网的网络类型划分为CN管理设备、AN管理设备和TN管理设备。域管理设备103通过接收到的网络子网模板的标识查找该标识对应的网络子网模板，并根据接收到的网络切片需求信息和域管理设备103本地保存的分解算法计算匹配得到该标识对应的网络子网模板中的目标部署信息。每个网络子网模板中可以包含至少一条的网络子网的部署信息。域管理设备103还可以通过与管理与编排设备105之间的接口将该目标部署信息发送给管理与编排设备105。
当网络子网模板中未嵌套网络功能模板时，网络管理设备102可以进行上述的获取网络子网的部署信息的方法；当网络子网模板中嵌套有网络功能模板时，域管理设备103执行以下操作：域管理设备103还用于解析网络子网模板来获取一个或多个网络功能模板的标识，并分解网络子网的需求信息为网络功能的需求信息。每个网络功能模板的标识对应一个网络功能的需求信息。将每个网络功能模板的标识和对应的网络功能的需求信息通过 与网络功能管理设备104之间的接口发送给网络功能管理设备104。
网络功能管理设备104，可以具备以下部分或者全部功能：网络功能的生命周期管理，例如网络功能的创建、更新、删除、故障管理、性能管理、配置管理等；网络服务的管理，包括网络服务生命周期管理、网络服务故障管理、网络服务性能管理、网络服务配置管理等；网络功能的协调等。网络功能管理设备104还用于通过与网络管理设备102之间的接口接收网络管理设备102发送的网络功能模板的标识和对应的网络功能需求信息。网络功能管理设备104可以关联一个或多个的网络功能模板。网络功能管理设备104通过接收到的网络功能模板的标识查找该标识对应的网络功能模板，并根据接收到的网络功能的需求信息和网络功能管理设备104本地保存的分解算法计算匹配得到该标识对应的网络功能模板中的目标部署信息。每个网络功能模板中可以包含至少一条的网络功能的部署信息。类似的，网络功能管理设备104还用于通过与域管理设备103之间的接口接收域管理设备103发送的网络功能模板的标识和对应的网络功能需求信息。网络功能管理设备104通过接收到的网络功能模板的标识查找该标识对应的网络功能模板，并根据接收到的网络功能的需求信息和网络功能管理设备104本地保存的分解算法计算匹配得到该标识对应的网络功能模板中的目标部署信息。网络功能管理设备104还可以通过与管理与编排设备105之间的接口将目标部署信息发送给管理与编排设备105。
管理与编排设备105可以接收网络管理设备102发送的携带网络的部署信息的实例化请求，并根据该携带网络的部署信息的实例化请求进行网络的虚拟资源的部署。管理与编排单元105还可以直接接收域管理设备103发送的携带网络子网的部署信息的实例化请求，并根据该携带网络子网的部署信息的实例化请求进行实例化。管理与编排设备105还可以直接接收网络功能管理设备104发送的携带网络功能的部署信息的实例化请求，并根据该携带网络功能的部署信息的实例化请求进行实例化。另外，管理与编排设备105还可以具备以下部分或者全部功能：网络功能和/或网络服务的生命周期管理，网络功能和/或网络服务的故障管理，网络功能和/或网络服务的性能管理，网络功能和/或网络服务的配置管理，虚拟资源的分配，虚拟资源的预留等。
其中，上述的网络可以是网络切片，也称为端到端(end to end，E2E)网络切片。上述网络可以包括核心网部分、接入网部分和传输网部分中的至少一个。上述的网络子网可以是网络切片子网，也可以包括核心网部分、接入网部分和传输网部分中的至少一个。从逻辑上看，网络和网络子网是一组网络功能的集合。
需要进行说明的，业务管理设备101、网络管理设备102、域管理设备103和管理与编排设备104均是依据功能命名的，对上述每一个设备来说，不对设备的名称作任何限制，上述每一个设备还可以有其他名称。上述的每一个设备可以是独立的设备。具体地，业务管理设备101可以是以下中的一个或者多个：通信业务管理功能(communication service management function，CSMF)、业务编排设备、业务管理和编排设备。网络管理设备102可以是以下中的一个或者多个：网络切片管理功能(network slice management function，NSMF)设备、跨域管理设备、跨域网络切片管理设备或者其他执行以上功能的设备。域管理设备103可以是以下中的一个或者多个：域切片管理设备、网络切片子网管理(network slice subnet management function，NSSMF)设备或者其他执行以上功能的设备。管理与编 排设备104可以是以下中的一个或者多个：网络功能虚拟化编排器(network function virtualization orchestration，NFVO)、虚拟网络功能编排器(virtualized network function manager，VNFM)和虚拟基础设施管理器(virtualized infrastructure manager，VIM)或者其他执行以上功能的设备。上述的每一个设备也可以是一个管理设备中的一个功能。具体地，每一个设备可以是以下设备中的一个或多个功能：网络编排设备、网络管理和编排设备、网元管理设备、业务编排设备、业务管理和编排设备或者NFVO。每一个网络设备可以包括在运营支撑系统(the office of strategic services，OSS)内，也可以不包括在OSS内，这里不作限制。
图1示出的网络系统仅仅是为了更加清楚的说明本申请的技术方案，并不构成对本申请的限定，本领域普通技术人员可知，随着网络系统的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
请参阅图2，图2提供了一种NST和NSST的结构示意图。如图2所示，该网络切片模板中嵌套有网络切片子网模板，网络切片模板中也可以嵌套有网络功能模板，以网络切片模板中嵌套有网络切片子网模板为例，网络切片模板中嵌套有网络功能模板的情况和网络切片子网模板中嵌套有网络功能模板的情况类似，可以类推。具体地，如图2所示，NST可以包含不同的网络切片的部署信息。每个网络切片的部署信息中可以包含网络切片子网的部署信息的标识，即NSST的NSD的部署规格的标识。如图2所示，NST1中根据不同的NST-NSD标识可以包含四条网络切片的部署信息，分别为：(1)NST1-NSD规格1:NSST1-NSD规格1+NSST2-NSD规格1，(2)NST1-NSD规格2:NSST1-NSD规格1+NSST2-NSD规格2，(3)NST1-NSD规格3:NSST1-NSD规格2+NSST2-NSD规格1，(4)NST1-NSD规格4:NSST1-NSD规格2+NSST2-NSD规格2。每条网络切片的部署信息中均包含网络切片子网1的部署信息的标识和网络切片子网2的部署信息的标识。其中，NSST1为网络切片子网1的模板，NSST2为网络切片子网2的模板。该网络切片子网1的部署信息的标识和网络切片子网2的部署信息的标识可以用于确定各自对应的网络切片子网1的部署信息和网络切片子网2的部署信息。
请参阅图3，现有技术中，基于图2提供NST的结构示意图，图3提供一种网络的部署信息确定方法的流程示意图。具体地，根据该NST结构确定网络切片的虚拟资源的部署信息的过程如下：
S301、网络管理设备根据网络切片的需求信息和/或网络切片模板的标识匹配网络切片模板。
网络管理设备可以根据网络切片的需求信息和本地保存的分解算法计算匹配到的网络切片标识为NST1，也可以直接根据网络切片的指示信息获取网络切片标识为NST1，该NST1中根据不同的NST1-NSD部署规格标识可以包含四条网络切片的部署信息。
S302、网络管理设备解析网络切片模板，分解网络切片需求信息为网络切片子网需求信息。
网络管理设备解析上述的NST1，可以得到NSST1和NSST2。即每条NST1的部署信息中均包含NSST1和NSST2。或者说NST1的部署信息包含的全部的网络切片子网模板的 标识为NSST1和NSST2。同时，网络管理设备可以针对NSST1和NSST2分解网络切片的需求信息为网络切片子网的需求信息。如分解为网络切片子网1的需求信息和网络切片子网2的需求信息。
S303、网络管理设备将网络切片子网模板和网络切片子网需求信息发送给域管理设备。
为确定网络切片子网的部署信息，网络管理设备将网络切片子网1的需求信息和NSST1标识发送给和NSST1关联的域管理设备1，将网络切片子网2的需求信息和NSST2标识发送给和NSST2关联的域管理设备2。
S304、域管理设备根据网络切片子网模板和网络切片子网需求信息确定网络切片子网的部署信息。
域管理设备1根据网络切片子网1的需求信息从NSST1对应的两个网络切片子网的部署信息(NSST1-NSD Flavor1和NSST1-NSD Flavor2)中确定网络切片子网1的部署信息。域管理设备2根据网络切片子网2的需求信息从NSST2对应的两个网络切片子网的部署信息(NSST2-NSD Flavor1和NSST2-NSD Flavor2)中确定网络切片子网2的部署信息。
S305、域管理设备将网络切片子网的部署信息发送给管理和编排设备。
域管理设备1将网络切片子网1的部署信息发送给管理和编排设备。域管理设备2将网络切片子网2的部署信息发送给管理和编排设备。管理和编排设备可以根据网络切片子网1的部署信息和网络切片子网2的部署信息进行虚拟资源的部署。
图3所描述的网络的部署信息确定方法中，域管理设备1可以通过与管理和编排设备之间的接口将网络切片子网1的部署信息发送给管理和编排设备，域管理设备2也可以通过与管理和编排设备之间的接口将网络切片子网2的部署信息发送给管理和编排设备，管理和编排设备根据接收到的网络切片子网1的部署信息和网络切片子网2的部署信息进行虚拟资源部署。然而，上述的虚拟资源部署方法中，管理和编排设备分别根据网络切片子网1的部署信息和网络切片子网2的部署信息独立的进行两次虚拟资源部署。网络切片子网1的和网络切片子网2之间关联的部署信息丢失，比如网络切片子网1和网络切片子网2之间的连接关系，以及网络切片子网1和网络切片子网1之间的亲和性和反亲和性信息丢失，从而降低了网络的部署信息的准确性。
基于上述图1的网络系统结构示意图，本申请实施例提供了一种网络的部署信息确定方法，可以提高网络的部署信息的准确性。
本申请的主要发明原理可包括：在网络模板中嵌套有网络组件模板的情况下，与网络模板关联的第一网络实体将网络的需求信息分解为网络组件的需求信息，将网络组件模板标识和网络组件的需求信息发送给网络组件关联的第二网络实体。第二网络实体根据接收到的网络组件模板标识和网络组件的需求信息获取网络组件的部署信息，将该网络组件的部署信息发送给第一网络实体。在网络模板中嵌套有多个网络组件模板的情况下，第一网络实体可以接收到多个网络组件的部署信息，并根据这多个网络组件的部署信息获取完整的网络的部署信息，网络的部署信息包含各个网络组件之间的关联关系，在发送给管理与编排设备的部署信息中包含了更全面的部署信息，可以提高网络的部署信息确定的准确性。
举例来说，图2所描述的网络切片结构中，首先，域管理设备1根据网络切片子网1 的需求信息从NSST1对应的两个网络切片子网的部署信息中确定网络切片子网1的部署信息，域管理设备2根据网络切片子网2的需求信息从NSST2对应的两个网络切片子网的部署信息中确定网络切片子网2的部署信息。其次，域管理设备1将网络切片子网1的部署信息发送给网络管理设备，域管理设备2将网络切片子网2的部署信息发送给网络管理设备。再次，网络管理设备可以根据网络切片子网1的部署信息和网络切片的部署信息的关联关系，以及网络切片子网2的部署信息和网络切片的部署信息的关联关系，从网络切片模板中包含的网络切片的部署信息中确定出网络的部署信息。具体地，如图2所示，如果网络切片子网1的部署信息为NSST1-NSD规格1标识的部署信息，网络切片子网2的部署信息为NSST2-NSD规格2标识的部署信息。则网络管理设备在接收到NSST1-NSD规格1标识的部署信息和NSST2-NSD规格2标识的部署信息后，从NST1中包含的四种NST1-NSD规格标识的部署信息中，选取既与NSST1-NSD规格1关联(即包含NSST1-NSD规格1标识)，又与NSST2-NSD规格2关联(即包含NSST2-NSD规格2标识)的部署信息的标识，即为NST1-NSD规格2标识的部署信息。该NST1-NSD规格2标识的部署信息中包含网络切片子网1和网络切片子网2之间的关联关系，例如网络切片子网1和网络切片子网2部署的亲和性和反亲和性，在发送给管理与编排设备的部署信息中包含了更全面的部署信息，能够提高网络的部署信息确定的准确性。
基于上述主要发明原理，下面说明本申请提供的网络的部署信息确定方法的具体流程。图4是本申请实施例提供的一种网络的部署信息确定方法的流程示意图。该网络的部署信息确定方法包括但不限于如下步骤S401-S404。
S401、第一网络实体向第二网络实体发送第二消息。第二消息携带网络组件的需求信息和网络组件模板的标识。
本申请实施例可以应用于至少如下两种场景。场景一、第一网络实体为网络管理设备，第二网络设备为域管理设备，第三网络设备为管理与编排设备。在这种场景中，网络组件为网络切片子网，网络组件模板为网络切片子网模板，网络为网络切片，网络模板为网络切片模板。场景二、第一网络设备为网络管理设备或者域管理设备，第二网络设备为网络功能管理设备，第三网络设备为管理与编排设备。在这种场景中，网络组件为网络功能，网络组件模板为网络功能模板，网络为网络切片或者网络切片子网，网络模板为网络切片模板或者网络切片子网模板。以下针对这两种场景分别进行详细描述。可以理解的，本申请中提供的网络的部署信息确定方法可以适用于网络模板嵌套有网络切片子网模板时确定网络的部署信息的情形，同样适用于网络模板没有嵌套网络切片子网模板时确定网络的部署信息的情形。
针对场景一来说，网络管理设备在向域管理设备发送第一消息之前，网络管理设备还用于执行以下步骤：
步骤一、网络管理设备接收业务管理设备发送的网络切片请求。
业务管理设备向网络管理设备发送的网络切片请求之前，业务管理设备可以接收网络切片请求或者业务请求，该网络切片请求或者业务请求携带网络切片需求信息和网络切片模板指示信息。业务管理设备也可以根据接收到的运营商和/或第三方客户发送的业务需求计算得到网络切片的需求信息和网络切片模板的指示信息，并将该网络切片需求信息和/或 网络切片模板的指示信息携带在网络切片请求中发送给网络管理设备。网络切片请求中也可以直接携带网络切片模板的指示信息，用于确定指示信息对应的网络切片模板。其中，网络切片的需求信息反映运营商和/或第三方客户对网络切片的功能的需求。网络切片的需求信息可以包含时延要求、带宽要求、覆盖范围要求、用户数量要求(容量要求)、移动性要求、吞吐率要求、可靠性要求、部署位置要求、亲和性反亲和性要求、成功率要求和网络切片类型要求中的一个或多个。
步骤二、网络管理设备根据网络切片请求获取网络切片模板。
当网络切片请求中包含网络切片模板指示信息，例如网络切片模板标识时，可以根据该网络切片模板指示信息获取预存的网络切片模板。当网络切片请求中不包含网络切片模板指示信息时，可以根据网络切片需求信息匹配相应的网络切片模板。匹配的过程可以是网络管理设备根据预存的网络切片模板厂商的分解算法计算得到的。
步骤三、网络管理设备解析网络切片模板获取网络切片子网模板标识，分解网络切片的需求信息为网络切片子网需求信息。
网络管理设备可以解析网络切片模板中的网络切片的部署信息包含的网络切片子网模板的标识，从而获取网络切片子网模板的标识。
网络切片的需求信息可以是网络切片请求中携带的。分解网络切片的需求信息为网络切片子网需求信息可以是根据预设在网络切片模板中的策略标识或者算法标识指示的策略或者算法进行分解的。可以是根据不同的网络域按照预设比例进行需求信息分配的；也可以是根据不同的网络切片子网模板在某一地理位置按照预设比例进行需求信息分解等等。
例如，网络切片的需求信息为时延，网络切片模板中包含网络切片子网模板1、网络切片子网模板2和网络切片子网模板3。网络切片子网模板1为AN部分模板，网络切片子网模板2为CN部分模板，网络切片子网模板3为TN部分模板。在网络切片模板中预存有一个策略标识或者算法标识指示AN latency：CN latency：TN latency＝2:3:5。如果网络切片时延需求信息为10ms，则根据上述策略标识对应的分配比例分解网络切片需求信息结果为：网络切片子网1的时延需求信息为2ms，网络切片子网2的时延需求信息为3ms，网络切片子网3的时延需求信息为5ms。
再例如，网络切片需求信息为用户数和分布地区，网络切片由厂商1提供的网络切片子网1和厂商2提供的网络切片子网2组成。且网络切片子网1网络切片子网2均包含AN部分、CN部分和TN部分。网络切片模板本地预存有一个策略表示地区1的网络切片子网模板由厂商1提供，地区2网络切片子网模板由厂商2提供。地区1和地区2为上海市的两个地区。网络切片的需求信息为上海100万用户，其中地区1有40万用户，地区2有60万用户。则根据上述的地区与网络切片模板的使用绑定关系分解网络切片的需求信息上海100万用户的结果为：网络切片子网1的需求信息为用户数40万，网络切片子网2的需求信息为用户数60万。本申请中，上述例子仅用于解释本发明实施例，不应构成限定，还可以根据需求在网络切片模板中预设其他策略或者算法进行网络切片需求信息分解。可以理解的，分解得到的网络切片子网的需求信息分别和解析得到的网络切片模板的标识一一对应。
网络管理设备可以解析网络切片模板得到一个或多个的网络切片子网模板标识，并为 每个网络切片子网模板对应的网络切片子网分配对应的网络切片子网需求信息。如果解析得到多个的网络切片子网模板标识，多个的网络切片子网模板标识和对应的网络切片子网需求信息可以是分别发送给多个域管理设备的，也可以是发送给同一个域管理设备的，这里不作限定。
针对场景二来说，实际上，场景二又具体细分为两个场景，即场景二a、第一网络实体为域管理设备，第二网络实体为网络功能管理设备。此时网络为网络切片子网，网络组件为网络功能，网络组件模板为网络功能模板。场景二b、第一网络实体为网络管理设备，第二网络实体为网络功能管理设备。此时网络为网络切片，网络组件为网络功能，网络组件模板为网络功能模板。以下具体描述的是场景二a的情形，首先，当域管理设备接收到网络管理设备发送的携带网络切片子网模板标识和网络切片子网需求信息的消息时，域管理设备可以根据该网络切片子网模板标识获取预存的网络切片子网模板。若网络管理设备发送的消息中不包含网络切片子网模板的标识，可以根据网络切片子网需求信息匹配相应的网络切片子网模板。匹配的过程可以是域管理设备根据预存的网络切片子网模板厂商的分解算法计算得到的，该分解算法与场景一中的分解算法均是厂商预设的，可以根据具体情况中不同的功能预设。其次，域管理设备解析网络切片子网模板获取网络功能模板标识，分解网络切片子网的需求信息为网络功能的需求信息。网络切片子网的需求信息可以是网络管理设备发送的消息中携带的，当网络管理设备发送的消息中未携带网络切片子网的需求信息时，可以是获取的网络切片子网模板中携带的。分解网络切片子网的需求信息为网络功能需求信息可以是根据预设在网络切片子网模板中的策略标识或者算法标识指示的策略或者算法进行分解的。具体地，可以是根据不同的网络功能按照预设比例进行需求信息分配的；也可以是根据不同的网络功能模板在某一地理位置按照预设比例进行需求信息分解等等。
针对于场景二b的描述，以下详细提供。网络管理设备在获取到网络切片模板后，解析该网络切片模板获取网络功能模板标识，分解网络切片的需求信息为网络功能需求信息。网络管理设备可以解析网络切片模板中的网络切片的部署信息包含的网络功能模板的标识，从而获取网络功能模板的标识。网络切片的需求信息可以是网络切片请求中携带的，当网络切片请求中未携带网络切片的需求信息时，可以是获取的网络切片模板中携带的。分解网络切片的需求信息为网络功能需求信息可以是根据预设在网络切片模板中的策略标识或者算法标识指示的策略或者算法进行分解的。可以是根据不同的网络功能按照预设比例进行需求信息分配的；也可以是根据不同的网络功能模板在某一地理位置按照预设比例进行需求信息分解等等。
S402、第二网络实体根据网络组件的需求信息和网络组件模板的标识对应的网络组件模板确定第一部署信息。第一部署信息为网络组件的部署信息。
针对于场景一来说，域管理设备可以关联若干个网络切片子网模板，根据网络切片子网模板的标识确定该标识对应的网络切片子网模板。网络切片子网模板中可以包含至少一个网络切片子网的部署信息。域管理设备根据网络切片子网的需求信息和网络切片子网模板的标识对应的网络切片子网模板确定网络切片子网的部署信息，包括：域管理设备根据网络切片子网的需求信息从至少一个网络切片子网的部署信息中确定网络切片子网的部署 信息。确定的过程可以是根据网络切片子网模板本地预存的分解算法计算得到的，也可以是其他方法得到的。例如，根据预设的网络切片子网的需求信息和网络切片子网的部署信息映射关系得到的，本实施例不作限制。
上述方法描述了网络切片子网的部署信息完全包含于网络切片子网模板的场景。实际上网络切片子网的部署信息中的部分信息也可以是域管理设备调用本地策略或者算法计算得到的。比如根据时延要求，计算得到位置约束信息。
网络切片子网的部署信息可以包含：网络切片子网对应的虚拟资源描述符标识，和/或网络切片子网对应的虚拟资源部署规格标识。网络切片子网对应的虚拟资源的部署信息还可以包含以下中的一个或多个：网络切片子网对应的虚拟资源的实例化等级、网络切片子网虚拟资源部署的亲和性和反亲和性、网络切片子网虚拟资源部署的位置约束信息等。
针对于场景二来说，网络功能管理设备可以关联若干个网络功能模板，根据网络功能模板的标识确定该标识对应的网络功能模板。网络功能模板中可以包含至少一个网络功能的部署信息；网络功能管理设备根据网络功能的需求信息和网络功能模板的标识对应的网络功能模板确定网络功能的部署信息，包括：网络功能管理设备根据网络功能的需求信息从至少一个网络功能的部署信息中确定网络功能的部署信息。确定的过程可以是根据网络功能模板本地预存的分解算法计算得到的，也可以是其他方法得到的，例如，根据预设的网络功能的需求信息和网络功能的部署信息的映射关系得到的，本实施例不作限制。
上述方法描述了网络功能的部署信息完全包含于网络功能模板的场景。实际上网络功能的部署信息中的部分信息也可以是网络功能管理设备调用算法计算得到的。
网络功能的部署信息可以包含：网络功能对应的虚拟资源描述符标识，和/或网络功能对应的虚拟资源部署规格标识。其中，网络功能对应的虚拟资源描述符标识可以是NFD ID，网络功能对应的虚拟资源部署规格标识可以是NFD Flavor ID。网络功能的部署信息还可以包含以下中的一个或多个：网络功能对应的虚拟资源实例化等级、网络功能虚拟资源部署的亲和性和反亲和性、网络功能虚拟资源部署的位置约束信息。
S403、第二网络实体向第一网络实体发送第一消息，第一消息携带第一部署信息。
针对场景一来说，域管理设备向网络管理设备发送的网络切片子网的部署信息可以是一个，也可以是多个。在网络切片子网的部署信息为多个的情况下，多个网络切片子网的部署信息可以是同一个域管理设备发送的，也可以是不同的域管理设备发送的，这里不作限制。可以理解的是，网络切片子网的部署信息的数量和步骤S401中网络管理设备解析得到的网络切片子网模板的标识的数量相等。当然网络切片子网的部署信息的数量也与网络管理设备分解网络切片的需求信息得到的网络切片子网的需求信息的数量相等。如图2所示，根据网络切片的需求信息和网络切片的标识确定网络切片子网的部署信息的过程可以参看图3所描述的实施例。
另外，网络切片子网的部署信息和网络切片的部署信息也可以是预存的。请参阅图5，是本申请实施例提供的另一种NST和NSST的结构示意图。如图5所示，可以预先将NSST1、NSST2和NST1各自包含的部署信息存储在数据库中供调用。可以仅仅存储部署信息的标识，用于指示该部署信息。网络管理设备解析网络切片模板NST1，得到网络切片模板NST1包含有网络切片子网模板NSST1和NSST2。则网络管理设备将网络切片子网模板的标识 NSST1和网络切片子网模板NSST1的需求信息发送给对应的域管理设备，并将网络切片子网模板的标识NSST2和网络切片子网模板NSST2的需求信息发送给对应的域管理设备，这里的域管理设备可以是同一个域管理设备，也可以是不同的域管理设备。域管理设备根据网络切片子网模板的标识NSST1和网络切片子网模板NSST1的需求信息得到网络切片子网1的部署信息。域管理设备根据网络切片子网模板的标识NSST2和网络切片子网模板NSST2的需求信息得到网络切片子网2的部署信息。如图5所示，域管理设备根据网络切片子网1需求信息直接从预存的网络切片子网1的部署信息中匹配得到NSST1的部署信息1。域管理设备根据网络切片子网2需求信息直接从预存的网络切片子网2的部署信息(NSST2)中匹配得到NSST2的部署信息1。
针对场景二a来说，网络功能管理设备向域管理设备或者网络管理设备发送的网络功能的部署信息可以是一个，也可以是多个。在网络功能的部署信息为多个的情况下，多个网络功能的部署信息可以是同一个网络功能管理设备发送的，也可以是不同的网络功能管理设备发送的，这里不作限制。可以理解的是，网络功能的部署信息的数量和步骤S401中解析得到的网络功能模板的标识的数量相等。当然网络功能的部署信息的数量也与分解网络切片子网的需求信息或者网络切片的需求信息得到的网络功能的需求信息的数量相等。
网络功能的部署信息可以是预存的，根据网络功能需求信息直接从预存的网络功能的部署信息中匹配得到的。具体的，请参阅图6，是本申请实施例提供的一种NSST和NFT的结构示意图。可以预先将NFT1、NFT2和NSST1各自包含的部署信息存储在数据库中供调用。可以仅仅存储部署信息的标识，用于指示对应的部署信息。域管理设备解析网络切片子网模板NSST1，得到网络切片子网模板NSST1包含有网络功能模板NFT1和NFT2。则域管理设备将网络功能模板的标识NFT1和网络功能模板NFT1的需求信息发送给对应的网络功能管理设备，并将网络功能模板的标识NFT2和网络功能模板NFT2的需求信息发送给对应的网络功能管理设备，这里的网络功能管理设备可以是同一个网络功能管理设备，也可以是不同的网络功能管理设备。网络功能管理设备根据网络功能模板的标识NFT1和网络功能模板NFT1的需求信息得到网络功能1的部署信息。网络功能管理设备根据网络功能模板的标识NFT2和网络功能模板NFT2的需求信息得到网络功能2的部署信息。如图6所示，网络功能管理设备根据网络功能1的需求信息直接从预存的网络功能1的部署信息中匹配得到NFT1的部署信息1。网络功能管理设备根据网络功能2的需求信息直接从预存的网络功能2的部署信息(NFT2)中匹配得到NFT2的部署信息1。
针对于场景二b来说，网络功能管理设备向网络管理设备发送的网络功能的部署信息可以是一个，也可以是多个。在网络功能的部署信息为多个的情况下，多个网络功能的部署信息可以是同一个网络功能管理设备发送的，也可以是不同的网络功能管理设备发送的，这里不作限制。可以理解的是，网络功能的部署信息的数量和步骤S401中解析得到的网络功能模板的标识的数量相等。当然网络功能的部署信息的数量也与分解网络切片子网的需求信息或者网络切片的需求信息得到的网络功能的需求信息的数量相等。网络功能的部署信息可以是预存的，根据网络功能需求信息直接从预存的网络功能的部署信息中匹配得到的。具体的，请参阅图7，是本申请实施例提供的一种NST和NFT的结构示意图。可以预先将NFT1、NFT2和NST1各自包含的部署信息存储在数据库中供调用。可以仅仅存储部 署信息的标识，用于指示对应的部署信息。网络管理设备解析网络切片模板NST1，得到网络切片模板NST1包含有网络功能模板NFT1和NFT2。则网络管理设备将网络功能模板的标识NFT1和网络功能1的需求信息发送给对应的网络功能管理设备，并将网络功能模板的标识NFT2和网络功能2的需求信息发送给对应的网络功能管理设备，这里的网络功能管理设备可以是同一个网络功能管理设备，也可以是不同的网络功能管理设备。网络功能管理设备根据网络功能模板的标识NFT1和网络功能模板NFT1的需求信息得到网络功能1的部署信息。网络功能管理设备根据网络功能模板的标识NFT2和网络功能模板NFT2的需求信息得到网络功能2的部署信息。如图6所示，网络功能管理设备根据网络功能1的需求信息直接从预存的网络功能1的部署信息中匹配得到NFT1的部署信息1。网络功能管理设备根据网络功能2的需求信息直接从预存的网络功能2的部署信息(NFT2)中匹配得到NFT2的部署信息1。
S404、第一网络实体依据第一部署信息确定第二部署信息，第二部署信息为网络的部署信息。
针对场景一来说，网络管理设备可以根据接收到的至少一个的网络切片子网的部署信息获取网络切片的部署信息。网络管理设备可以根据至少一个网络切片子网的部署信息和网络切片的部署信息的关联关系，从网络切片模板中包含的网络切片的部署信息中确定出网络的部署信息。如图2所示，如果网络管理设备接收到两个网络切片子网的部署信息，其中一个网络切片子网的部署信息中包含的NSST-NSD规格的ID为NSST1-NSD规格1，另一个网络切片子网的部署信息中包含的NSST-NSD规格的ID为NSST2-NSD规格2，则网络管理设备可以根据这两个网络切片子网的部署信息计算得到网络切片的部署信息为NST1-NSD规格2。
另外，也可以是预存网络切片的部署信息，可以是网络模板中预存的，也可以是网络管理设备本地预存的。如图5所示，网络切片的部署信息包括：NST1-NSD部署信息1、NST1-NSD部署信息2、NST1-NSD部署信息3和NST1-NSD部署信息4。这些网络切片的部署信息可以预先存储在数据库中。在网络管理设备接收到两个网络切片子网的部署信息时，根据NSST1-NSD规格1和NSST2-NSD规格2从以上四种网络切片的部署信息中选取包含上述NSST1-NSD规格1和NSST2-NSD规格2的网络切片部署信息。如图5所示，NST1-NSD规格ID为NST1-NSD规格2指示的网络切片的部署信息包含上述NSST1-NSD规格1和NSST2-NSD规格2。而NST1-NSD部署信息2中包含该NST1-NSD规格2。因此，可以确定网络切片部署信息为NST1-NSD部署信息2。网络切片部署信息为NST1-NSD部署信息2中还可以包含NST1-NSD规格ID以外的信息，例如，可以是以下中的一个或多个，以下信息可以是不包含在NST1中的，而是根据网络切片需求信息计算得到的：网络切片1对应的虚拟资源的实例化等级、网络切片1的虚拟资源部署的亲和性和反亲和性、网络切片1的虚拟资源部署的位置约束信息等。上述例子仅用于解释本申请实施例，不应构成限定。
网络切片子网的部署信息可以包括网络切片子网对应的虚拟资源描述符标识，和/或网络切片子网对应的虚拟资源部署规格标识。网络切片子网的部署信息还可以包括以下中的至少一种，以下信息可以是不包含在NSST中的，而是根据网络切片子网需求信息计算得 到的：网络切片子网对应的虚拟资源实例化等级，网络切片子网对应的虚拟资源部署的亲和性和反亲和性，网络切片子网的对应的虚拟资源部署位置约束信息。网络切片的部署信息可以包括网络切片对应的虚拟资源描述符标识，和/或网络切片对应的虚拟资源部署规格的标识。网络切片子网的部署信息还可以包括以下中的至少一种，以下信息可以是不包含在NST中的，而是根据网络切片子网需求信息计算得到的：网络切片对应的虚拟资源实例化等级，网络切片对应的虚拟资源部署的亲和性和反亲和性，网络切片对应的虚拟资源的部署位置约束信息。在网络管理设备将上述的网络切片的部署信息发送给管理与编排设备后，管理与编排设备根据该网络切片的部署信息进行虚拟资源部署，并在实例化之后形成网络切片实例。
在网络切片实例运行过程中，当域管理设备检测到网络切片子网满足预设条件时，根据预设条件确定部署信息；域管理设备向网络管理设备发送网络切片子网的部署信息。
上述的预设条件可以是网络切片子网上承载的用户数量大于预设阈值。这里网络切片子网是已经实例化过后的网络切片子网实例。其中，上述的预设阈值可以是获取该网络切片子网的部署信息时，接收到的网络切片子网的需求信息中的用户数要求，也可以是网络切片子网内预设的。例如，接收到的网络切片子网的需求信息中的用户数要求为可以承载100万的用户，根据该网络切片子网的需求信息部署的网络切片子网上承载的用户数量超过100万时，该网络切片子网可能不能负荷。可以设置100万为上述的预设阈值，在用户数超过100万时，触发域管理设备执行向网络管理设备发送网络切片子网的部署信息，并将该网络切片子网的部署信息发送给网络管理设备，网络管理设备根据该网络切片子网的部署信息获取网络切片的第四部署信息，将该网络切片的第四部署信息发送给管理与编排设备，请求管理与编排设备根据网络切片的第四部署信息进行实例化。实例化后得到的网络切片实例可以用于承载多出的用户数。也可以是域管理设备将网络切片子网的部署信息发送给管理与编排设备进行实例化。
再例如，网络切片子网根据承载用户数量的能力预计超过80万用户时，根据该网络切片子网的需求信息部署的网络切片子网上承载的用户数量超过，设定预设阈值为80万，该网络切片子网可能不能负荷。可以设置80万为上述的预设阈值，在用户数超过80万时，触发域管理设备执行向网络管理设备发送网络切片子网的部署信息，并将该网络切片子网的部署信息发送给网络管理设备，网络管理设备根据该网络切片子网的部署信息获取网络切片的第四部署信息，将该网络切片的第四部署信息发送给管理与编排设备，请求管理与编排设备根据网络切片的第四部署信息进行实例化。实例化后得到的网络切片实例可以用于承载多出的用户数。
另外，预设条件也可以是管理某个网络切片子网的域管理设备出现故障。故障的域管理设备失去对该某个网络切片子网的管控，需要重新部署网络切片子网实例。也可以是域管理设备根据内部设立的其他的一些策略触发的更新网络切片子网。可以理解的是，在网络切片或者网络切片子网运行过程中，只要出现异常情况使得需要重新部署或者更新网络切片或者网络切片子网，即包含在本申请实施例中。本申请实施例中，可以通过重新部署或者更新网络切片或者网络切片子网来解决网络切片或者网络切片子网运行中出现的问题。
本申请实施例中，网络管理设备根据网络切片子网的部署信息确定网络切片的部署信息之后，网络管理设备向管理与编排设备发送携带网络切片的部署信息的请求，管理与编排设备在接收到携带网络切片的部署信息的请求时，依据网络切片的部署信息部署网络切片的虚拟资源。
本申请实施例中，在网络切片模板中嵌套有网络切片子网模板的情况下，域管理设备在确定网络切片子网的部署信息之后，不是直接将该网络切片子网的部署信息发送给管理网络虚拟资源的管理编排设备进行实例化，而是将该网络切片子网的部署信息发送给网络管理设备，网络管理设备根据至少一个的网络切片子网的部署信息获取包含这至少一个的网络切片子网的部署信息和至少一个的网络切片子网的部署信息之间的关联关系的完整的网络切片的部署信息。从而获取网络切片需求信息对应的完整的网络切片的部署信息，包含了网络切片子网的部署信息之间的关联关系，在发送给网络管理设备的部署信息中包含了更全面的部署信息，可以提高网络切片的部署信息确定的准确性。
针对场景二来说，域管理设备或者网络管理设备可以根据接收到的至少一个的网络功能的部署信息获取网络切片的部署信息。针对于场景二a来说，如图6所示，如果域管理设备接收到两个网络功能的部署信息，其中一个网络功能的部署信息中包含的NFT-NSD规格的ID为NFT1-NSD规格1，另一个NF的部署信息中包含的NFT-NSD规格的ID为NFT2-NSD规格2，则域管理设备可以根据这两个NF的部署信息计算得到网络切片子网的部署信息。另外，也可以是预存的网络切片子网的部署信息。如图6所示，网络切片子网的部署信息包括：NSST1-NSD部署信息1、NSST1-NSD部署信息2、NSST1-NSD部署信息3和NSST1-NSD部署信息4。这些网络切片子网的部署信息可以预先存储在数据库中。在域管理设备接收到两个NF的部署信息时，根据NFT1-NSD规格1和NFT2-NSD规格2和以上四种网络切片子网的部署信息的关联关系，从中选取包含上述NFT1-NSD规格1和NFT2-NSD规格2的网络切片子网部署信息。如图6所示，NSST1-NSD规格ID为NSST1-NSD规格2指示的网络切片子网的部署信息包含上述NFT1-NSD规格1和NFT2-NSD规格2。而NSST1-NSD部署信息2中包含该NSST1-NSD规格2。因此，可以确定网络切片子网的部署信息为NSST1-NSD部署信息2。网络切片子网的部署信息NSST1-NSD部署信息2中还可以包含NSST1-NSD规格ID以外的信息，例如，可以是以下中的一个或多个，以下信息可以是不包含在NSST1中的，而是根据网络切片子网需求信息计算得到的：网络切片子网1的虚拟资源的实例化等级、网络切片子网1虚拟资源部署的亲和性和反亲和性、网络切片子网1虚拟资源部署的位置约束信息等。上述例子仅用于解释本申请实施例，不应构成限定。
网络功能的部署信息可以包括网络功能对应的虚拟资源描述符标识，网络功能对应的虚拟资源部署规格标识。网络功能的部署信息还可以包括以下中的至少一种，以下信息可以是不包含在NFT中的，而是根据网络功能需求信息计算得到的：网络功能对应的虚拟资源实例化等级，网络功能对应的虚拟资源部署的亲和性和反亲和性，网络功能对应的虚拟资源的部署位置约束信息。网络切片子网对应的虚拟资源的部署信息可以包括网络切片子网对应的虚拟资源描述符标识，和/或网络切片子网对应的虚拟资源部署规格标识。网络切片子网的部署信息还可以包括以下中的至少一种，以下信息可以是不包含在NSST中的， 而是根据网络切片子网需求信息计算得到的：网络切片子网对应的虚拟资源实例化等级，网络切片子网对应的虚拟资源部署的亲和性和反亲和性，网络切片子网对应的虚拟资源的部署位置约束信息。
域管理设备可以根据网络功能的部署信息计算得到网络切片子网的部署信息之后，该网络切片子网的部署信息嵌套于网络切片的部署信息中，因此，之后域管理设备需要将网络切片子网的部署信息发送给网络管理设备，并执行步骤S404中场景一的流程及后续流程。
在上述的场景二a中，在网络切片子网模板中嵌套有网络功能模板的情况下，与网络切片子网模板关联的域管理设备将网络切片子网的需求信息分解为网络功能的需求信息，将网络功能模板标识和网络功能的需求信息发送给网络功能关联的网络功能管理设备。网络功能管理设备根据接收到的网络功能模板标识和网络功能的需求信息获取网络功能的部署信息，将该网络功能的部署信息发送给域管理设备。在网络切片子网模板中嵌套有多个网络功能模板的情况下，域管理设备可以接收到多个网络功能的部署信息，并根据这多个网络功能的部署信息获取完整的网络切片子网的部署信息，网络切片子网的部署信息包含各个网络功能之间的关联关系，在发送给网络管理设备的部署信息中包含了更全面的部署信息，可以提高网络切片的部署信息确定的准确性。
针对于场景二b来说，如图7所示，如果网络管理设备接收到两个网络功能的部署信息，其中一个网络功能的部署信息中包含的NFT-NSD规格的ID为NFT1-NSD规格1，另一个NF的部署信息中包含的NFT-NSD规格的ID为NFT2-NSD规格2，则网络管理设备可以根据这两个NF的部署信息计算得到网络切片的部署信息。另外，也可以是预存的网络切片的部署信息。如图7所示，网络切片子网的部署信息包括：NST1-NSD部署信息1、NST1-NSD部署信息2、NST1-NSD部署信息3和NST1-NSD部署信息4。这些网络切片的部署信息可以预先存储在数据库中。在网络管理设备接收到两个NF的部署信息时，根据NFT1-NSD规格1和NFT2-NSD规格2和以上四种网络切片的部署信息的关联关系，从中选取包含上述NFT1-NSD规格1和NFT2-NSD规格2的网络切片的部署信息。如图7所示，NST1-NSD规格ID为NST1-NSD规格2指示的网络切片的部署信息包含上述NFT1-NSD规格1和NFT2-NSD规格2。而NST1-NSD部署信息2中包含该NST1-NSD规格2。因此，可以确定网络切片子网的部署信息为NST1-NSD部署信息2。网络切片子网的部署信息NST1-NSD部署信息2中还可以包含NST1-NSD规格ID以外的信息，例如，可以是以下中的一个或多个，以下信息可以是不包含在NST1中的，而是根据网络切片需求信息计算得到的：网络切片1的虚拟资源的实例化等级、网络切片1虚拟资源部署的亲和性和反亲和性、网络切片1虚拟资源部署的位置约束信息等。上述例子仅用于解释本申请实施例，不应构成限定。
网络功能的部署信息可以包括网络功能对应的虚拟资源描述符标识，网络功能对应的虚拟资源部署规格标识。网络功能的部署信息还可以包括以下中的至少一种，以下信息可以是不包含在NFT中的，而是根据网络功能需求信息计算得到的：网络功能对应的虚拟资源实例化等级，网络功能对应的虚拟资源部署的亲和性和反亲和性，网络功能对应的虚拟资源的部署位置约束信息。网络切片子网的部署信息可以包括网络切片子网对应的虚拟资 源描述符标识，和/或网络切片子网对应的虚拟资源部署规格标识。网络切片子网的部署信息还可以包括以下中的至少一种，以下信息可以是不包含在NSST中的，而是根据网络切片子网需求信息计算得到的：网络切片子网对应的虚拟资源实例化等级，网络切片子网对应的虚拟资源部署的亲和性和反亲和性，网络切片子网对应的虚拟资源的部署位置约束信息。
网络管理设备根据网络功能的部署信息计算得到网络切片的部署信息之后，可以将该网络切片的部署信息发送给管理与编排设备，管理与编排设备根据该网络切片的部署信息部署网络切片的虚拟资源。
在上述的场景二b中，在网络切片模板中嵌套有网络功能模板的情况下，与网络切片模板关联的网络管理设备将网络切片的需求信息分解为网络功能的需求信息，将网络功能模板标识和网络功能的需求信息发送给网络功能关联的网络功能管理设备。网络功能管理设备根据接收到的网络功能模板标识和网络功能的需求信息获取网络功能的部署信息，将该网络功能的部署信息发送给网络管理设备。在网络切片模板中嵌套有多个网络功能模板的情况下，网络管理设备可以接收到多个网络功能的部署信息，并根据这多个网络功能的部署信息获取完整的网络切片的部署信息，网络切片的部署信息包含各个网络功能之间的关联关系，在发送给管理与编排设备的部署信息中包含了更全面的部署信息，可以提高网络切片的部署信息确定的准确性。
上述详细阐述了本申请实施例的方法，下面提供了本申请实施例的网络实体。
基于图1的网络系统架构，图8是本申请实施例提供的一种网络实体10的结构示意图，如图7所示，该第一网络实体10可以包括处理单元801和接收单元802，其中：
接收单元802，用于接收第二网络实体20发送的第一消息；第一消息携带第一部署信息，第一部署信息为网络组件的部署信息；
处理单元801，用于根据第一部署信息确定第二部署信息，第二部署信息为网络的部署信息，网络包含至少一个网络组件。
作为一种可能的实施方式，处理单元801根据第一部署信息确定第二部署信息，包括：
处理单元801根据第一部署信息从网络模板中确定第二部署信息，所述网络模板包括至少一个网络的部署信息。
作为一种可能的实施方式，第一网络实体10还包括发送单元803，处理单元801调用接收单元802接收第二网络实体发送的第一消息之前，处理单元801还用于调用发送单元803，用于向第二网络实体发送第二消息，第二消息携带网络组件的需求信息和网络组件模板的标识，网络组件的需求信息和网络组件模板的标识用于确定第一部署信息。
作为一种可能的实施方式，第一部署信息包括以下至少一种：网络组件对应的虚拟资源描述符标识，网络组件对应的虚拟资源部署规格，网络组件对应的虚拟资源实例化等级，网络组件对应的虚拟资源部署的亲和性和反亲和性，网络组件对应的虚拟资源的部署位置约束信息；第二部署信息包括以下中的至少一种：网络对应的虚拟资源描述符标识，网络对应的虚拟资源部署规格，网络对应的虚拟资源实例化等级，网络对应的虚拟资源部署的亲和性和反亲和性，网络对应的虚拟资源的部署位置约束信息。
作为一种可能的实施方式，网络组件为网络切片子网，网络组件模板为网络切片子网模板，网络为网络切片。第一网络实体10为网络管理设备。
作为一种可能的实施方式，网络组件为网络功能，网络组件模板为网络功能模板，网络为网络切片或者网络切片子网。第一网络实体10为网络管理设备或者域管理设备。
作为一种可能的实施方式，处理单元801根据第一部署信息确定第二部署信息之后，发送单元803，还用于向第三网络实体发送携带第二部署信息的第三消息。
在该实施例中，处理单元801、接收单元802和发送单元803的功能可以对应参照图4所示的网络的部署信息确定方法实施例的相应描述。
基于图1的网络系统架构，图9是本申请实施例提供的一种网络实体20的结构示意图，如图9所示，该第二网络实体20可以包括处理单元901和接收单元902和发送单元903，其中：
接收单元902，用于接收第一网络实体发送的第二消息，第二消息携带网络组件的需求信息和网络组件模板的标识；
处理单元901，用于根据网络组件的需求信息和网络组件模板的标识对应的网络组件模板确定第一部署信息，第一部署信息为网络组件的部署信息；
发送单元903，用于向第一网络实体10发送第一消息，第一消息携带第一部署信息。
作为一种可能的实施方式，网络组件模板包含至少一个网络组件的部署信息；处理单元901根据网络组件的需求信息和网络组件模板的标识对应的网络组件模板确定第一部署信息，包括：处理单元根据网络组件的需求信息从至少一个网络组件的部署信息中确定第一部署信息。
作为一种可能的实施方式，第一部署信息包括以下至少一种：网络组件对应的虚拟资源描述符标识，网络组件对应的虚拟资源部署规格，网络组件对应的虚拟资源实例化等级，网络组件对应的虚拟资源部署的亲和性和反亲和性，网络组件对应的虚拟资源的部署位置约束信息。
作为一种可能的实施方式，网络组件为网络切片子网，网络组件模板为网络切片子网模板，网络为网络切片。
作为一种可能的实施方式，网络组件为网络功能，网络组件模板为网络功能模板，网络为网络切片或者网络切片子网。
作为一种可能的实施方式，处理单元901，还用于当检测到网络组件满足预设条件时，根据预设条件确定第三部署信息，第三部署信息为网络组件的部署信息；预设条件包含以下至少一种：网络组件上承载的用户数量大于预设阈值，或者检测到第二网络实体发生故障；
发送单元903，还用于向第一网络实体10发送携带第三部署信息的第四消息。
在该实施例中，处理单元901、接收单元902和发送单元903的功能可以对应参照图4所示的网络的部署信息确定方法实施例中的相应描述，这里不再赘述。
基于图1的网络系统架构，图10是本申请实施例提供的另一种网络实体10的结构示 意图，如图10所示，该第一网络实体10包括：一个或多个网络处理器1001、存储器1002、通信接口1003、发射器1005、接收器1006、耦合器1007和天线1008。这些部件可通过总线1004或者其他方式连接，图10以通过总线连接为例。其中：
通信接口1003可用于第一网络实体10与其他通信设备，例如第二网络实体20，进行通信。具体的，第一网络实体10可以是图1所示的网络系统架构中的网络管理设备102，网络管理设备102可以通过通信接口1003与图1所示的业务管理设备、域管理设备和网络功能管理设备进行通信。第一网络实体10还可以是图1所示的网络系统架构中的域管理设备103，域管理设备103可以通过通信接口1003与图1所示的网络功能管理设备进行通信。具体的，通信接口1003可以是长期演进(long term evolution，LTE)系统通信接口，也可以是5G或者未来新空口的通信接口。不限于无线通信接口，第一网络实体10还可以配置有有线的通信接口1003来支持有线通信，例如一个第一网络实体10与其他网络设备之间的回程链接可以是有线通信连接。
发射器1005可用于对网络处理器1001输出的消息或数据进行发射处理。
在本申请的一些实施例中，发射器1005和接收器1006可看作一个无线调制解调器。在第一网络实体10中，发射器1005和接收器1006的数量均可以是一个或者多个。发射器1005和接收器1006也可以是由一个或多个收发器来实现的。天线1008可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器1007可用于将移动通信号分成多路，分配给多个的接收器1006。
存储器1002与网络处理器1001耦合，用于存储各种软件程序和/或多组指令。存储器1002可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作系统。存储器1002还可以存储网络的部署信息确定的程序，该网络的部署信息确定的程序可用于与一个或多个附加设备，一个或多个网络设备进行通信。
网络处理器1001可用于进行无线信道管理、实施呼叫和通信链路的建立和拆除，并确定网络的部署信息等。
本申请实施例中，网络处理器1001可用于读取和执行计算机可读指令。具体的，网络处理器1001可用于调用存储于存储器1002中的网络的部署信息确定程序。存储器1002可用于存储本申请的一个或多个实施例提供的网络的部署信息确定方法在第一网络实体10侧的实现程序。具体地，接收器1006，用于接收第二网络实体发送的第一消息；所述第一消息携带第一部署信息，所述第一部署信息为网络组件的部署信息；
网络处理器1001用于调用存储器1002中存储的程序指令和数据，执行如下操作：
根据所述第一部署信息确定第二部署信息，所述第二部署信息为网络的部署信息，所述网络包含至少一个所述网络组件。
可选的，网络处理器1001根据所述第一部署信息确定第二部署信息，包括：
网络处理器1001用于调用存储器1002中存储的程序指令和数据执行：根据所述第一部署信息从网络模板中确定所述第二部署信息，所述网络模板包括至少一个网络的部署信息。
可选的，接收器1006接收第二网络实体发送的第一消息之前，发射器1005还向所述第二网络实体发送第二消息，所述第二消息携带网络组件的需求信息和网络组件模板的标 识，所述网络组件的需求信息和所述网络组件模板的标识用于确定所述第一部署信息。
可选的，所述第一部署信息包括以下至少一种：所述网络组件对应的虚拟资源描述符标识，所述网络组件对应的虚拟资源部署规格，所述网络组件对应的虚拟资源实例化等级，所述网络组件对应的虚拟资源部署的亲和性和反亲和性，所述网络组件对应的虚拟资源的部署位置约束信息；所述第二部署信息包括以下中的至少一种：所述网络对应的虚拟资源描述符标识，所述网络对应的虚拟资源部署规格，所述网络对应的虚拟资源实例化等级，所述网络对应的虚拟资源部署的亲和性和反亲和性，所述网络对应的虚拟资源的部署位置约束信息。
可选的，所述网络组件为网络切片子网，所述网络组件模板为网络切片子网模板，所述网络为网络切片。
可选的，所述网络组件为网络功能，所述网络组件模板为网络功能模板，所述网络为网络切片或者网络切片子网。
可选的，网络处理器1001根据所述第一部署信息确定第二部署信息之后，发射器1006向第三网络实体发送携带所述第二部署信息的第三消息。,
需要说明的，图10所示的网络实体10仅仅是本申请实施例的一种实现方式，实际应用中，网络实体10还可以包括更多或更少的部件，这里不作限制。
基于图1的网络系统架构，图11是本申请实施例提供的另一种网络实体20的结构示意图，如图11所示，该第一网络实体20包括：一个或多个网络处理器1101、存储器1102、通信接口1103、发射器1105、接收器1106、耦合器1107和天线1108。这些部件可通过总线1104或者其他方式连接，图11以通过总线连接为例。其中：
通信接口1103可用于第一网络实体20与其他通信设备，例如第一网络实体10，进行通信。具体的，第二网络实体20可以是图1所示的网络系统架构中的域管理设备103，域管理设备103可以通过通信接口1103与图1所示的网络管理设备进行通信。第二网络实体20还可以是图1所示的网络系统架构中的网络功能管理设备104，网络功能管理设备104可以通过通信接口1003与图1所示的域管理设备和网络管理设备进行通信。具体的，通信接口1103可以是长期演进(long term evolution，LTE)系统通信接口，也可以是5G或者未来新空口的通信接口。不限于无线通信接口，第二网络实体20还可以配置有有线的通信接口1103来支持有线通信，例如一个第二网络实体20与其他网络设备之间的回程链接可以是有线通信连接。
发射器1105可用于对网络处理器1101输出的消息或数据进行发射处理。
在本申请的一些实施例中，发射器1105和接收器1106可看作一个无线调制解调器。在第二网络实体20中，发射器1105和接收器1106的数量均可以是一个或者多个。发射器1105和接收器1106也可以是由一个或多个收发器来实现的。天线1108可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器1007可用于将移动通信号分成多路，分配给多个的接收器1106。
存储器1102与网络处理器1101耦合，用于存储各种软件程序和/或多组指令。存储器1102可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作 系统。存储器1002还可以存储网络的部署信息确定的程序，该网络的部署信息确定的程序可用于与一个或多个附加设备，一个或多个网络设备进行通信。
网络处理器1101可用于进行无线信道管理、实施呼叫和通信链路的建立和拆除，并确定网络的部署信息等。
本申请实施例中，网络处理器1101可用于读取和执行计算机可读指令。具体的，网络处理器1101可用于调用存储于存储器1102中的网络的部署信息确定程序。存储器1102可用于存储本申请的一个或多个实施例提供的网络的部署信息确定方法在第二网络实体20侧的实现程序。具体地，接收器1106，用于接收第一网络实体发送的第二消息，所述第二消息携带网络组件的需求信息和网络组件模板的标识；
网络处理器1101可用于调用存储于存储器1102中的程序执行如下操作：
根据所述网络组件的需求信息和所述网络组件模板的标识对应的网络组件模板确定第一部署信息，所述第一部署信息为网络组件的部署信息；
发射器1105，用于向所述第一网络实体发送第一消息，所述第一消息携带所述第一部署信息。
可选的，所述网络组件模板包含至少一个网络组件的部署信息；网络处理器1101根据所述网络组件的需求信息和所述网络组件模板的标识对应的网络组件模板确定第一部署信息，包括：网络处理器1101根据所述网络组件的需求信息从所述至少一个网络组件的部署信息中确定所述第一部署信息。
可选的，所述第一部署信息包括以下至少一种：所述网络组件对应的虚拟资源描述符标识，所述网络组件对应的虚拟资源部署规格，所述网络组件对应的虚拟资源实例化等级，所述网络组件对应的虚拟资源部署的亲和性和反亲和性，所述网络组件对应的虚拟资源的部署位置约束信息。
可选的，所述网络组件为网络切片子网，所述网络组件模板为网络切片子网模板，所述网络为网络切片。
可选的，所述网络组件为网络功能，所述网络组件模板为网络功能模板，所述网络为网络切片或者网络切片子网。
可选的，网络处理器1101，还用于当所述第二网络实体检测到所述网络组件满足预设条件时，根据所述预设条件确定第三部署信息，所述第三部署信息为所述网络组件的部署信息；所述预设条件包含以下至少一种：所述网络组件上承载的用户数量大于预设阈值，或者检测到所述第二网络实体发生故障；
发射器1105向所述第一网络实体发送携带所述第三部署信息的第四信息。
需要说明的，图11所示的网络实体20仅仅是本申请实施例的一种实现方式，实际应用中，网络实体20还可以包括更多或更少的部件，这里不作限制。
参见图12，图12是本发明实施例提供的一种装置的结构示意图。如图12所示，装置120可包括：处理器1201，以及耦合于处理器1201的一个或多个接口1202。其中：
处理器1201可用于读取和执行计算机可读指令。具体实现中，处理器1201可主要包括控制器、运算器和寄存器。其中，控制器主要负责指令译码，并为指令对应的操作发出 控制信号。运算器主要负责执行定点或浮点算数运算操作、移位操作以及逻辑操作等，也可以执行地址运算和转换。寄存器主要负责保存指令执行过程中临时存放的寄存器操作数和中间操作结果等。具体实现中，处理器1201的硬件架构可以是专用集成电路(Application Specific Integrated Circuits，ASIC)架构等等。处理器1201可以是单核的，也可以是多核的。
接口1202可用于输入待处理的数据至处理器1201，并且可以向外输出处理器1201的处理结果。
本申请中，处理器1201可用于从存储器中调用本申请的一个或多个实施例提供的网络的部署信息确定方法在第一网络实体侧的实现程序，并执行该程序包含的指令。接口1202可用于输出处理器1201的执行结果。关于本申请的一个或多个实施例提供的网络的部署信息确定方法可参考前述各个实施例，这里不再赘述。
需要说明的，处理器1201、接口1202各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
参见图13，图13是本发明实施例提供的另一种装置的结构示意图。如图13所示，装置130可包括：处理器1301，以及耦合于处理器1301的一个或多个接口1302。其中：
处理器1301可用于读取和执行计算机可读指令。具体实现中，处理器1301可主要包括控制器、运算器和寄存器。其中，控制器主要负责指令译码，并为指令对应的操作发出控制信号。运算器主要负责执行定点或浮点算数运算操作、移位操作以及逻辑操作等，也可以执行地址运算和转换。寄存器主要负责保存指令执行过程中临时存放的寄存器操作数和中间操作结果等。具体实现中，处理器1301的硬件架构可以是专ASIC架构等等。处理器1301可以是单核的，也可以是多核的。
接口1302可用于输入待处理的数据至处理器1301，并且可以向外输出处理器1301的处理结果。
本申请中，处理器1301可用于从存储器中调用本申请的一个或多个实施例提供的网络的部署信息确定方法在第二网络实体侧的实现程序，并执行该程序包含的指令。接口1302可用于输出处理器1301的执行结果。关于本申请的一个或多个实施例提供的网络的部署信息确定方法可参考前述各个实施例，这里不再赘述。
需要说明的，处理器1301、接口1302各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件程序指令的方式来实现。软件程序指令可以由相应的软件模块组成，软件模块可以被存放于RAM、闪存、ROM、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于收发机或中继设备中。当然，处理器和存 储介质也可以作为分立组件存在于第一网络实体或第二网络实体中。
可以理解的是，在本申请中，不同实施例之间的技术术语、技术方案可以依据其内在的逻辑相互参考、相互引用，本申请并不对技术术语和技术方案所适用的实施例进行限定。对不同实施例中的技术方案相互组合，还可以形成新的实施例。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如，固态硬盘(Solid State Disk，SSD))等。

Claims (28)

  1. 一种网络的部署信息确定方法，其特征在于，包括：
    第一网络实体接收第二网络实体发送的第一消息；所述第一消息携带第一部署信息，所述第一部署信息为网络组件的部署信息；
    所述第一网络实体根据所述第一部署信息确定第二部署信息，所述第二部署信息为网络的部署信息，所述网络包含至少一个所述网络组件。
  2. 根据权利要求1所述的网络的部署信息确定方法，其特征在于，所述第一网络实体根据所述第一部署信息确定第二部署信息，包括：
    所述第一网络实体根据所述第一部署信息从网络模板中确定所述第二部署信息，所述网络模板包括至少一个网络的部署信息。
  3. 根据权利要求1或2所述的网络的部署信息确定方法，其特征在于，所述第一网络实体接收第二网络实体发送的第一消息之前，所述方法还包括：
    所述第一网络实体向所述第二网络实体发送第二消息，所述第二消息携带网络组件的需求信息和网络组件模板的标识，所述网络组件的需求信息和所述网络组件模板的标识用于确定所述第一部署信息。
  4. 根据权利要求1至3任一项所述的网络的部署信息确定方法，其特征在于，所述第一部署信息包括以下至少一种：所述网络组件对应的虚拟资源描述符标识，所述网络组件对应的虚拟资源部署规格，所述网络组件对应的虚拟资源实例化等级，所述网络组件对应的虚拟资源部署的亲和性和反亲和性，所述网络组件对应的虚拟资源的部署位置约束信息；
    所述第二部署信息包括以下中的至少一种：所述网络对应的虚拟资源描述符标识，所述网络对应的虚拟资源部署规格，所述网络对应的虚拟资源实例化等级，所述网络对应的虚拟资源部署的亲和性和反亲和性，所述网络对应的虚拟资源的部署位置约束信息。
  5. 根据权利要求1至4任一项所述的网络的部署信息确定方法，其特征在于，所述网络组件为网络切片子网，所述网络组件模板为网络切片子网模板，所述网络为网络切片。
  6. 根据权利要求1至4任一项所述的网络的部署信息确定方法，其特征在于，所述网络组件为网络功能，所述网络组件模板为网络功能模板，所述网络为网络切片或者网络切片子网。
  7. 根据权利要求1至6任一项所述的网络的部署信息确定方法，其特征在于，所述第一网络实体根据所述第一部署信息确定第二部署信息之后，所述方法还包括：
    所述第一网络实体向第三网络实体发送携带所述第二部署信息的第三消息。
  8. 一种网络的部署信息确定方法，其特征在于，包括：
    第二网络实体接收第一网络实体发送的第二消息，所述第二消息携带网络组件的需求信息和网络组件模板的标识；
    所述第二网络实体根据所述网络组件的需求信息和所述网络组件模板的标识对应的网络组件模板确定第一部署信息，所述第一部署信息为网络组件的部署信息；
    所述第二网络实体向所述第一网络实体发送第一消息，所述第一消息携带所述第一部署信息。
  9. 根据权利要求8所述的网络的部署信息确定方法，其特征在于，所述网络组件模板包含至少一个网络组件的部署信息；所述第二网络实体根据所述网络组件的需求信息和所述网络组件模板的标识对应的网络组件模板确定第一部署信息，包括：
    所述第二网络实体根据所述网络组件的需求信息从所述至少一个网络组件的部署信息中确定所述第一部署信息。
  10. 根据权利要求8或9所述的网络的部署信息确定方法，其特征在于，所述第一部署信息包括以下至少一种：所述网络组件对应的虚拟资源描述符标识，所述网络组件对应的虚拟资源部署规格，所述网络组件对应的虚拟资源实例化等级，所述网络组件对应的虚拟资源部署的亲和性和反亲和性，所述网络组件对应的虚拟资源的部署位置约束信息。
  11. 根据权利要求8至10任一项所述的网络的部署信息确定方法，其特征在于，所述网络组件为网络切片子网，所述网络组件模板为网络切片子网模板，所述网络为网络切片。
  12. 根据权利要求8至10任一项所述的网络的部署信息确定方法，其特征在于，所述网络组件为网络功能，所述网络组件模板为网络功能模板，所述网络为网络切片或者网络切片子网。
  13. 根据权利要求8至12任一项所述的网络的部署信息确定方法，其特征在于，所述方法还包括：
    当所述第二网络实体检测到所述网络组件满足预设条件时，所述第二网络实体根据所述预设条件确定第三部署信息，所述第三部署信息为所述网络组件的部署信息；所述预设条件包含以下至少一种：所述网络组件上承载的用户数量大于预设阈值，或者检测到所述第二网络实体发生故障；
    所述第二网络实体向所述第一网络实体发送携带所述第三部署信息的第四信息。
  14. 一种网络实体，其特征在于，包括处理单元和接收单元，其中：
    所述接收单元，用于接收第二网络实体发送的第一消息；所述第一消息携带第一部署信息，所述第一部署信息为网络组件的部署信息；
    所述处理单元，用于根据所述第一部署信息确定第二部署信息，所述第二部署信息为 网络的部署信息，所述网络包含至少一个所述网络组件。
  15. 根据权利要求14述的网络实体，其特征在于，所述处理单元根据所述第一部署信息确定第二部署信息，包括：
    所述处理单元根据所述第一部署信息从网络模板中确定所述第二部署信息，所述网络模板包括至少一个网络的部署信息。
  16. 根据权利要求14或15所述的网络实体，其特征在于，所述网络实体还包括发送单元，所述接收单元接收第二网络实体发送的第一消息之前，所述发送单元，用于向所述第二网络实体发送第二消息，所述第二消息携带网络组件的需求信息和网络组件模板的标识，所述网络组件的需求信息和所述网络组件模板的标识用于确定所述第一部署信息。
  17. 根据权利要求14至16任一项所述的网络实体，其特征在于，所述第一部署信息包括以下至少一种：所述网络组件对应的虚拟资源描述符标识，所述网络组件对应的虚拟资源部署规格，所述网络组件对应的虚拟资源实例化等级，所述网络组件对应的虚拟资源部署的亲和性和反亲和性，所述网络组件对应的虚拟资源的部署位置约束信息；所述第二部署信息包括以下中的至少一种：所述网络对应的虚拟资源描述符标识，所述网络对应的虚拟资源部署规格，所述网络对应的虚拟资源实例化等级，所述网络对应的虚拟资源部署的亲和性和反亲和性，所述网络对应的虚拟资源的部署位置约束信息。
  18. 根据权利要求14至17任一项所述的网络实体，其特征在于，所述网络组件为网络切片子网，所述网络组件模板为网络切片子网模板，所述网络为网络切片。
  19. 根据权利要求14至17任一项所述的网络实体，其特征在于，所述网络组件为网络功能，所述网络组件模板为网络功能模板，所述网络为网络切片或者网络切片子网。
  20. 根据权利要求14至19任一项所述的网络实体，其特征在于，所述处理单元根据所述第一部署信息确定第二部署信息之后，所述发送单元，还用于向第三网络实体发送携带所述第二部署信息的第三消息。
  21. 一种网络实体，其特征在于，包括处理单元、发送单元和接收单元，其中：
    所述接收单元，用于接收第一网络实体发送的第二消息，所述第二消息携带网络组件的需求信息和网络组件模板的标识；
    所述处理单元，用于根据所述网络组件的需求信息和所述网络组件模板的标识对应的网络组件模板确定第一部署信息，所述第一部署信息为网络组件的部署信息；
    所述发送单元，用于向所述第一网络实体发送第一消息，所述第一消息携带所述第一部署信息。
  22. 根据权利要求21所述的网络实体，其特征在于，所述网络组件模板包含至少一个网络组件的部署信息；所述处理单元根据所述网络组件的需求信息和所述网络组件模板的标识对应的网络组件模板确定第一部署信息，包括：
    所述处理单元根据所述网络组件的需求信息从所述至少一个网络组件的部署信息中确定所述第一部署信息。
  23. 根据权利要求21或22所述的网络实体，其特征在于，所述第一部署信息包括以下至少一种：所述网络组件对应的虚拟资源描述符标识，所述网络组件对应的虚拟资源部署规格，所述网络组件对应的虚拟资源实例化等级，所述网络组件对应的虚拟资源部署的亲和性和反亲和性，所述网络组件对应的虚拟资源的部署位置约束信息。
  24. 根据权利要求21至23任一项所述的网络的部署信息确定方法，其特征在于，所述网络组件为网络切片子网，所述网络组件模板为网络切片子网模板，所述网络为网络切片。
  25. 根据权利要求21至23任一项所述的网络实体，其特征在于，所述网络组件为网络功能，所述网络组件模板为网络功能模板，所述网络为网络切片或者网络切片子网。
  26. 根据权利要求21至25任一项所述的网络实体，其特征在于，所述处理单元，还用于当所述第二网络实体检测到所述网络组件满足预设条件时，所述第二网络实体根据所述预设条件确定第三部署信息，所述第三部署信息为所述网络组件的部署信息；所述预设条件包含以下至少一种：所述网络组件上承载的用户数量大于预设阈值，或者检测到所述第二网络实体发生故障；
    所述发送单元，还用于向所述第一网络实体发送携带所述第三部署信息的第四消息。
  27. 一种计算机可读存储介质，其特征在于，所述存储介质用于存储指令，当所述指令运行时，使得计算机执行权利要求1至13任一项所述的方法。
  28. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行权利要求1至13任一项所述的方法。
PCT/CN2018/103081 2017-09-27 2018-08-29 网络的部署信息确定方法及设备 WO2019062456A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/831,293 US11356939B2 (en) 2017-09-27 2020-03-26 Method and device for determining deployment information of network
US17/831,725 US11844017B2 (en) 2017-09-27 2022-06-03 Method and device for determining deployment information of network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710891076.1 2017-09-27
CN201710891076.1A CN109560955B (zh) 2017-09-27 2017-09-27 网络的部署信息确定方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/831,293 Continuation US11356939B2 (en) 2017-09-27 2020-03-26 Method and device for determining deployment information of network

Publications (1)

Publication Number Publication Date
WO2019062456A1 true WO2019062456A1 (zh) 2019-04-04

Family

ID=65863825

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/103081 WO2019062456A1 (zh) 2017-09-27 2018-08-29 网络的部署信息确定方法及设备

Country Status (3)

Country Link
US (2) US11356939B2 (zh)
CN (1) CN109560955B (zh)
WO (1) WO2019062456A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113905401A (zh) * 2021-09-29 2022-01-07 中国联合网络通信集团有限公司 一种子切片对接方法、装置及设备
CN114006818A (zh) * 2020-07-13 2022-02-01 中国电信股份有限公司 端到端网络切片对接的配置方法和系统

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6973300B2 (ja) * 2018-06-04 2021-11-24 日本電信電話株式会社 サービスチェイン設計装置、サービスチェイン設計方法、および、サービスチェイン設計プログラム
CN111443985A (zh) * 2019-01-17 2020-07-24 华为技术有限公司 实例化虚拟网络功能的方法及设备
CN110535679B (zh) * 2019-07-09 2022-11-29 中移（杭州）信息技术有限公司 切片的管理方法、架构、网络切片销售平台和管理系统
US10708368B1 (en) * 2019-10-30 2020-07-07 Verizon Patent And Licensing Inc. System and methods for generating a slice deployment description for a network slice instance
CN112995097B (zh) * 2019-12-13 2023-09-22 中兴通讯股份有限公司 跨域访问系统及方法、装置
US20210224109A1 (en) * 2020-01-16 2021-07-22 Cisco Technology, Inc. Systems and methods for orchestrating cloud resources
CN114051279A (zh) * 2020-07-23 2022-02-15 华为技术有限公司 一种业务处理方法及网络设备
US11888700B2 (en) 2020-08-03 2024-01-30 Nokia Solutions And Networks Oy Method and apparatus for fine-grained isolation in CN NSS domain of E2E network slice
US11190413B1 (en) * 2020-08-14 2021-11-30 Verizon Patent And Licensing Inc. Systems and methods for zero-touch deployment of network slices and network slice assurance services
US11576115B2 (en) * 2020-11-03 2023-02-07 Verizon Patent And Licensing Inc. Systems and methods for designing network slices using extensible components
CN114554504A (zh) * 2020-11-24 2022-05-27 华为技术有限公司 网络切片规划的方法以及相关设备
US11271819B1 (en) * 2021-06-16 2022-03-08 At&T Intellectual Property I, L.P. Generating and utilizing templates and logical paths to deploy network equipment
CN115987795A (zh) * 2021-10-13 2023-04-18 中兴通讯股份有限公司 网络切片资源编排方法、网络设备及存储介质
US11729055B1 (en) * 2022-11-04 2023-08-15 At&T Intellectual Property I, L.P. Utilizing templates with associated naming policies to deploy network equipment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170104688A1 (en) * 2015-10-09 2017-04-13 Huawei Technologies Co., Ltd. Method and apparatus for admission control of virtual networks in a backhaul-limited communication network
CN106713406A (zh) * 2015-11-18 2017-05-24 中国移动通信集团公司 接入切片网络的方法及系统
CN107155187A (zh) * 2016-03-03 2017-09-12 华为技术有限公司 通信方法、终端设备和网络侧设备

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9756361B2 (en) * 2014-07-25 2017-09-05 Verizon Patent And Licensing Inc. On-demand load balancer and virtual live slicer server farm for program ingest
WO2017058067A1 (en) * 2015-09-29 2017-04-06 Telefonaktiebolaget Lm Ericsson (Publ) Securing network slice management
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
CN113810905A (zh) * 2016-04-01 2021-12-17 Idac控股公司 服务切片的选择和分离方法
EP3456090B1 (en) * 2016-05-12 2021-03-31 Convida Wireless, Llc Connecting to virtualized mobile core networks
US10856183B2 (en) * 2016-11-10 2020-12-01 Huawei Technologies Co., Ltd. Systems and methods for network slice service provisioning
CN106792739B (zh) * 2016-11-17 2020-01-21 北京邮电大学 网络切片方法、装置和设备
CN108632068B (zh) * 2017-03-22 2020-09-11 大唐移动通信设备有限公司 一种网络切片模板生成、网络切片模板应用方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170104688A1 (en) * 2015-10-09 2017-04-13 Huawei Technologies Co., Ltd. Method and apparatus for admission control of virtual networks in a backhaul-limited communication network
CN106713406A (zh) * 2015-11-18 2017-05-24 中国移动通信集团公司 接入切片网络的方法及系统
CN107155187A (zh) * 2016-03-03 2017-09-12 华为技术有限公司 通信方法、终端设备和网络侧设备

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006818A (zh) * 2020-07-13 2022-02-01 中国电信股份有限公司 端到端网络切片对接的配置方法和系统
CN114006818B (zh) * 2020-07-13 2023-10-31 中国电信股份有限公司 端到端网络切片对接的配置方法和系统
CN113905401A (zh) * 2021-09-29 2022-01-07 中国联合网络通信集团有限公司 一种子切片对接方法、装置及设备
CN113905401B (zh) * 2021-09-29 2023-07-18 中国联合网络通信集团有限公司 一种子切片对接方法、装置及设备

Also Published As

Publication number Publication date
US20220295391A1 (en) 2022-09-15
US11356939B2 (en) 2022-06-07
CN109560955A (zh) 2019-04-02
US11844017B2 (en) 2023-12-12
US20200229080A1 (en) 2020-07-16
CN109560955B (zh) 2021-10-01

Similar Documents

Publication Publication Date Title
US11356939B2 (en) Method and device for determining deployment information of network
EP3595244B1 (en) Network slice management method, unit and system
US10824454B2 (en) 5G dynamic slice and network identity instantiation, termination, and access management system and method
WO2018006381A1 (zh) 一种网络资源的管理方法、装置及系统
WO2018171459A1 (zh) 网络切片的管理方法和装置
US10848366B2 (en) Network function management method, management unit, and system
CN111971944B (zh) 用于配置网络切片的方法和装置
US20210226902A1 (en) Time-Sensitive Networking Communication Method and Apparatus
US11070989B2 (en) Network slice management method, management unit, and system
US20200177473A1 (en) Network component management method and network device
EP3869855A1 (en) Information transmission method and apparatus thereof
US11057309B2 (en) Management method, management unit, and system
CN109391490B (zh) 网络切片的管理方法和装置
CN109600769B (zh) 通信方法及装置
US20230239343A1 (en) Method for dynamically triggering instantiation of edge application server, and apparatus
CN111371578B (zh) 部署虚拟化网络功能的方法和装置
US11784884B2 (en) Code activation management method for network slicing solutions, and corresponding entity, server and computer program
US20240223447A1 (en) Systems and methods for provisioning network slices
US20230308898A1 (en) Network slices for time sensitive networking
KR20200077943A (ko) 동적 네트워크 확장 방법, 장치 및 시스템

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

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

Country of ref document: EP

Kind code of ref document: A1