WO2018171459A1 - 网络切片的管理方法和装置 - Google Patents

网络切片的管理方法和装置 Download PDF

Info

Publication number
WO2018171459A1
WO2018171459A1 PCT/CN2018/078730 CN2018078730W WO2018171459A1 WO 2018171459 A1 WO2018171459 A1 WO 2018171459A1 CN 2018078730 W CN2018078730 W CN 2018078730W WO 2018171459 A1 WO2018171459 A1 WO 2018171459A1
Authority
WO
WIPO (PCT)
Prior art keywords
subnet
information
template
instance
network slice
Prior art date
Application number
PCT/CN2018/078730
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 华为技术有限公司
Priority to EP18771593.3A priority Critical patent/EP3584999B1/en
Priority to EP21165924.8A priority patent/EP3907932B1/en
Publication of WO2018171459A1 publication Critical patent/WO2018171459A1/zh
Priority to US16/573,509 priority patent/US11063831B2/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/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • 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/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
    • 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/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • 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/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5006—Creating or negotiating SLA contracts, guarantees or penalties
    • 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/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • 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

Definitions

  • the present application relates to communication technologies, and in particular, to a method and an apparatus for managing network slices.
  • next-generation networks will expand to support new and different types of customers and partners.
  • Business diversity and automated deployment are a feature of next-generation networks that leverage existing network resources to quickly respond to business to business (Business to Business, Short for B2B) and Business-to-Customer (B2C) business needs, timely provisioning and opening of new services, shortening the time to market for new services (Time To Market, referred to as TTM) is the main operator facing Competitive pressure.
  • Network Slice is an important technical means for the next generation network to meet the special needs of different industries and different users.
  • Network slicing is a communication resource that ensures that the bearer service can meet the service level agreement (SLA) requirements. These resources can be hard-isolated (physically isolated) or soft-isolated (logically isolated) according to different requirements. It can also be considered that a network slice is a combination of network functions and resources required to complete a certain service (s), and is a complete logical network.
  • the next-generation network is a cross-vendor network, that is, different components of the network slice may come from different vendors. For example, an operator needs to deploy a low-latency network slice to provide virtual reality services, and adopts A, B, and C vendors. To provide network slicing together, how to automate or integrate different components of different vendors to form a network slice is a major difficulty in quickly and automatically deploying services.
  • the existing service deployment process is as follows: the customer (Customer) proposes the service demand to the operator, the operator determines the network demand according to the service requirement and designs the corresponding network, and proposes the corresponding network or subnet requirement to each equipment manufacturer, and each equipment manufacturer Negotiate the required network resources, and design corresponding services according to the network resources provided by each equipment manufacturer to meet the customer requirements. It can be seen that the existing service deployment is completed by manual negotiation, which takes a long time, and the manually designed network slice cannot be reused. Each new service requires a long negotiation process, resulting in waste of resources.
  • the present invention provides a network slice management method and device, which can generate multiple network slice information according to capability information of multiple subnets to meet various service requirements, and the generated network slice can be reused, thereby improving resource utilization.
  • a first aspect of the present application provides a method for managing a network slice, including: a first management unit acquires capability information of a subnet from a second management unit, where the capability information of the subnet includes at least one of the following information: a subnet The capability information of the template, the capability information of the subnet instance, where the capability information of the subnet template is used to represent the feature of the subnet template, and the capability information of the subnet instance is used to represent the subnet instance.
  • the first management unit generates information of the network slice according to the capability information of the subnet, where the information of the network slice includes information of a network slice template or information of a network slice instance, where the network slice includes at least one of the subnets .
  • the first management unit is capable of generating information of multiple network slices according to capability information of multiple subnets to meet various service requirements, and the generated network slice can be reused, and the physical implementation of the network slice is shielded externally.
  • the method further includes: sending, by the first management unit, the third management unit Information about the network slice template.
  • the information about the network slice instance includes the requirement information of the subnet instance required to instantiate or create the network slice instance, and the first management unit generates the information of the network slice according to the capability information of the subnet.
  • the method further includes: the first management unit receives requirement information of the network slice instance from a third management unit, where the requirement information of the network slice instance is used to instantiate or create a network slice instance.
  • the first management unit generates the information of the network slice according to the capability information of the subnet, where the first management unit determines the instance according to the requirement information of the network slice instance and the capability information of the subnet.
  • the requirement information of the subnet instance required for the network slice instance is created or created.
  • the method further includes: the first management unit sending a query request message to the second management unit, where the query request message is used by Requesting capability information of the subnet.
  • the second aspect of the present application provides a method for managing a network slice, including:
  • the second management unit sends the capability information of the subnet to the first management unit, where the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, and the subnet template.
  • the capability information is used to represent characteristics of the subnet template, and the capability information of the subnet instance is used to represent features of the subnet instance.
  • the method before the sending, by the second management unit, the capability information of the subnet to the first management unit, the method further includes: the second management unit generating capability information of the subnet.
  • the method further includes: the second management unit receiving the query request message sent by the first management unit, the query request message Capability information for requesting the subnet.
  • the third aspect of the present application provides a network slice management apparatus, including:
  • an acquiring module configured to acquire capability information of the subnet from the second management unit, where the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, where The capability information of the subnet template is used to indicate the feature of the subnet template, and the capability information of the subnet instance is used to represent the feature of the subnet instance;
  • a generating module configured to generate information about the network slice according to the capability information of the subnet, where the information of the network slice includes information of a network slice template or information of a network slice instance, where the network slice includes at least one of the subnets.
  • the information about the network slice includes information about a network slice template, and correspondingly, the device further includes:
  • a sending module configured to send information about the network slice template to the third management unit.
  • the information about the network sharding instance includes the requirement information of the subnet instance required to be instantiated or created by the network sharding instance, and the device further includes:
  • a receiving module configured to receive, by the third management unit, requirement information of the network slice instance, where the requirement information of the network slice instance is used to instantiate or create a network slice instance;
  • the generating module is specifically configured to:
  • the device further includes:
  • a sending module configured to send a query request message to the second management unit, where the query request message is used to request capability information of the subnet.
  • the fourth aspect of the present application provides a network slice management apparatus, including:
  • a sending module configured to send capability information of the subnet to the first management unit, where the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, and the subnet
  • the capability information of the template is used to represent characteristics of the subnet template
  • the capability information of the subnet instance is used to represent features of the subnet instance.
  • the device further includes:
  • a generating module configured to generate capability information of the subnet.
  • the device further includes:
  • the receiving module is configured to receive a query request message sent by the first management unit, where the query request message is used to request capability information of the subnet.
  • a fifth aspect of the present application provides a management apparatus for a network slice, including a processor, a memory, and a communication interface, where the memory is used to store an instruction, the communication interface is used to communicate with another device, and the processor is configured to execute the memory.
  • the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, and the capability of the subnet template
  • the information is used to indicate a feature of the subnet template, and the capability information of the subnet instance is used to represent a feature of the subnet instance;
  • the information of the network slice is generated according to the capability information of the subnet, where the information of the network slice includes information of a network slice template or information of a network slice instance, and the network slice includes at least one of the subnets.
  • the information about the network slice includes the information of the network slice template, and the communication interface is configured to send the information about the network slice template to the third management unit.
  • the information about the network slice instance includes requirement information for instantiating or creating a subnet instance required by the network slice instance, where the processor generates information about the network slice according to the capability information of the subnet.
  • the communication interface is further configured to: receive, by the third management unit, requirement information of the network slice instance, where the requirement information of the network slice instance is used to instantiate or create a network slice instance;
  • the processor is specifically configured to: according to the requirement information of the network slice instance and the capability information of the subnet, determine requirement information of a subnet instance required to instantiate or create the network slice instance.
  • the communication interface is further configured to: send a query request message to the second management unit, where the query request message is used to request capability information of the subnet.
  • a sixth aspect of the present application provides a management apparatus for a network slice, including a processor, a memory, and a communication interface, wherein the memory is configured to store an instruction, the communication interface is configured to communicate with another device, and the processor is configured to execute the memory Stored instructions.
  • the communication interface is specifically configured to:
  • the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, and capability information of the subnet template. And indicating the feature of the subnet template, the capability information of the subnet instance is used to represent a feature of the subnet instance.
  • the processor is specifically configured to: generate capability information of the subnet.
  • the communication interface is further configured to: receive a query request message sent by the first management unit, where the query request message is used to request capability information of the subnet.
  • the capability information of the subnet template includes at least one of the following: an identifier of a subnet template, a type of a subnet template, a function of a subnet template, The function of the subnet template, the sharing policy of the subnet template, the connection information of the subnet template, the performance information of the subnet template, the service information of the subnet template, and the configurable parameters of the subnet template.
  • the capability information of the subnet instance includes at least one of the following: an identifier of a subnet instance, a type of a subnet instance, a function of a subnet instance, The function of the subnet instance, the sharing policy of the subnet instance, the performance information of the subnet instance, the connection information of the subnet instance, and the service information of the subnet instance.
  • the information about the network slice template includes capability information of at least one subnet template or capability information of at least one subnet instance
  • the network slice The information of the instance includes capability information of at least one subnet template or capability information of at least one subnet instance.
  • the information about the network slice template further includes at least one of the following information: indication information of the subnet instance, and indication information of the subnet template.
  • a network slice-to-subnet decomposition policy corresponding to the network slice template, where the indication information of the subnet instance is used to indicate a subnet instance included in the network slice template, and the indication information of the subnet template is used for And indicating a subnet template included in the network slice template, where the network slice template is used to deploy a network slice instance.
  • a seventh aspect of the present application provides a computer readable storage medium storing instructions for causing a computer to execute a network slice management method according to the first aspect of the present application when the instructions are executed .
  • An eighth aspect of the present application provides a computer readable storage medium storing instructions for causing a computer to execute a network slice management method according to the second aspect of the present application when the instructions are executed .
  • a ninth aspect of the present application provides a computer program product, comprising: instructions, when executed, causing a computer to perform a method of managing a network slice as described in the first aspect of the present application.
  • a tenth aspect of the present application provides a computer program product, comprising: instructions, when executed, causing a computer to perform a method of managing a network slice as described in the second aspect of the present application.
  • the first management unit acquires capability information of a subnet, and the capability information of the subnet includes at least one of the following information: capability information of the subnet template, and capability information of the subnet instance
  • the capability information of the subnet template is used to represent the characteristics of the subnet template
  • the capability information of the subnet instance is used to represent the characteristics of the subnet instance
  • the network slice information is generated according to the capability information of the subnet
  • the network slice information includes Information of a network slice template or information of a network slice instance, the network slice containing at least one subnet.
  • the first management unit can generate information of multiple network slices according to capability information of multiple subnets to meet various service requirements, and the generated network slice can be reused, and the physical implementation of the network slice is shielded externally.
  • FIG. 1 shows a possible network architecture provided by the present application
  • Figure 2 shows a schematic diagram of an existing network architecture
  • FIG. 3 is a schematic flowchart of a method for managing a network slice according to Embodiment 1;
  • Embodiment 4 is a signaling flowchart of a method for managing a network slice provided by Embodiment 2;
  • Embodiment 5 is a signaling flowchart of a method for managing a network slice provided by Embodiment 3;
  • FIG. 6 is a schematic structural diagram of a network slice management apparatus provided in Embodiment 4.
  • FIG. 7 is a schematic structural diagram of a network slice management apparatus provided in Embodiment 5.
  • FIG. 8 is a schematic structural diagram of a network slice management apparatus according to Embodiment 6.
  • the network architecture and the service scenario described in this application are for the purpose of more clearly explaining the technical solutions of the present application, and do not constitute a limitation of the technical solutions provided by the present application.
  • Those skilled in the art may know that with the evolution of the network architecture and new business scenarios, The technical solution provided by the present application is equally applicable to similar technical problems.
  • FIG. 1 shows a possible network architecture provided by the present application, which includes: a business support system (BSS)/client slice management unit/service management unit (SM), cross-domain A cross-domain slice manager and a plurality of domain slice managers.
  • BSS business support system
  • SM service management unit
  • the network is mainly divided into three domains: an Access Network (AN) domain, a Core Network (CN) domain, and a Transport Network (TN) domain.
  • the plurality of domain slice management units include an AN domain slice management unit, a CN domain slice management unit, and a TN domain slice management unit.
  • the domain slice management unit may also be referred to as a domain subnet management unit.
  • the AN domain slice management unit is also referred to as an AN domain subnet management unit
  • the CN domain slice management unit is also referred to as a CN domain subnet management unit, TN.
  • the domain slice management unit is also known as the TN domain subnet management unit.
  • Multiple domain slice management units may come from different vendors. For example, in the example shown in FIG. 1, two CN domain slice management units are provided by vendor 1 and vendor 2, respectively, and the AN domain slice management unit is supplied by Provided by Vendor 3, the TN Domain Slice Management Unit is provided by Vendor 4.
  • the client slice management unit is configured to manage a network slice leased by a customer or a tenant from a carrier network.
  • a cross-domain slice management unit also called a network slice management unit or a network slice design unit, includes at least one of the following functions: network slice management, network slice and sub-network, and mapping of network functions, network slice orchestration, network resources provided by different domains. Coordination with Sub-SLA.
  • the network slice may be a communication resource that guarantees that the bearer service or service can meet the SLA requirement, and may also be considered as a combination of the network function and the communication resource required to complete a certain service or some services.
  • Network slice management includes network slice design, lifecycle management, network slice template management, network slice fault management, network slice performance management, and network slice configuration management.
  • Network slicing is to arrange the sub-network slicing and network functions provided by each domain in a unified manner to obtain network slicing that meets the service requirements.
  • the service requirements can be SLA requirements, key performance indicators (KPIs) requirements, and services. Quality of Service (QoS) requirements.
  • KPIs key performance indicators
  • QoS Quality of Service
  • the domain slice management unit also known as the subnet management unit or subnet design unit, is mainly used for subnet management, subnet service management, and subnet network resource coordination and orchestration.
  • subnet management includes subnet design, lifecycle management (create, update, delete, etc.), subnet fault management, subnet performance management, and subnet configuration management.
  • Service management of subnets includes service lifecycle management, service fault management, service performance management, and service configuration management.
  • the CN domain slice management unit is mainly used for CN subnet management, CN subnet service management, and network resource coordination and orchestration of the CN subnet.
  • CN subnet management includes CN subnet design, lifecycle management (create, update, delete, etc.), CN subnet fault management, CN subnet performance management, and CN subnet configuration management.
  • the service management of the CN subnet includes service lifecycle management, service fault management, service performance management, and service configuration management.
  • the AN domain slice management unit is mainly used for the management of the AN subnet, the service management of the AN subnet, and the coordination and arrangement of the network resources of the AN subnet.
  • the AN subnet management includes the design of the AN subnet, lifecycle management (creation, update, deletion, etc.), fault management of the AN subnet, performance management of the AN subnet, and configuration management of the AN subnet.
  • the service management of the AN subnet includes service lifecycle management, service fault management, service performance management, and service configuration management.
  • the TN domain slice management unit is mainly used for TN subnet management, TN subnet service management, and TN subnet network resource coordination and orchestration.
  • the TN subnet management includes TN subnet design, lifecycle management (creation, update, deletion, etc.), TN subnet fault management, TN subnet performance management, and TN subnet configuration management.
  • Service management of the TN subnet includes service lifecycle management, service fault management, service performance management, and service configuration management.
  • the cross-domain slice management unit and the domain slice management unit mentioned above may be integrated in an existing network element or may exist as independent network elements.
  • 2 shows a schematic diagram of an existing network architecture, which includes the following network elements: Service Orchestrator (SO), Network Orchestrator (NO) unit, and Element Manager (Element Manager, EM) unit.
  • SO Service Orchestrator
  • NO Network Orchestrator
  • EM Element Manager
  • the service orchestration unit may also be referred to as a Service Manager (SM) unit, and the network orchestration unit is also referred to as a Network Manager (NM) unit.
  • SM Service Manager
  • NM Network Manager
  • the service orchestration unit may be described as an SO unit or an SO
  • the network orchestration unit may be described as a NO unit or NO.
  • the SO can be set as a single functional entity, or the SO can be set as a functional module of other functional entities, and the functions of the SO can be integrated into other functional entities.
  • NO can be set as a single functional entity, NO can be set as a functional module of other functional entities, and the function of NO can be integrated into other functional entities.
  • the SO and the NO may be combined into one combined entity having the function of the SO and the function of the NO.
  • the combined entity may be referred to as a service and network orchestration unit.
  • the associated entity may have other names, which is not limited in this application.
  • the combined entity in this application, may be set as a separate functional entity, or the combined entity may be set as a functional module of other functional entities, and the combined entity may also be The functionality is integrated into other functional entities.
  • the functions of the foregoing SO include, but are not limited to, lifecycle management (eg, instantiation or creation, expansion and expansion, or update) of a service according to a service request message sent by the BSS; service aggregation, service management (eg, failure, Configuration, accounting, performance, security (Fault, Configuration, Accounting, Performance, Security, FCAPS) management) and mapping between service and network slices.
  • the service may be a set of service level agreement (SLA) communication services that the user can enjoy, for example, Mobile Broadband (MBB) services, such as voice and Internet of Things (IOT).
  • MBB Mobile Broadband
  • IOT Internet of Things
  • Business for example, smart parking, smart meter reading, etc.
  • the functions of the above NO include, but are not limited to, management of network slices (eg, lifecycle management, FCAPS management, management of network slice templates); management of network functions (NF); mapping of network slices and network functions; coordination Different types of network resources; coordinating network resources provided by different operators and different network providers; and unifying the network equipment provided by different vendors so that network resources provided by different network providers can meet the needs of target services ( For example, the requirements of the SLA, the requirements of the Key Performance Indicator (KPI) and the Quality of Service (QoS); the external application program interface (API), which is used for the third party.
  • KPI Key Performance Indicator
  • QoS Quality of Service
  • API external application program interface
  • SO and NO can be set in an Operations Support System (OSS)/Business Support System (BSS), and SO and NO can also have other settings: for example, both are set in OSS/BSS external; for example, SO is set in OSS/BSS, and NO is set outside NO.
  • the SO and the NO may be combined and set as one set entity, and the set entity may be set inside the OSS/BSS or outside the OSS/BSS.
  • cross-domain slice management unit may be the foregoing SO, NO, or NM, and each domain slice or subnet management unit may also be SO, NO, EM, DM (Domain Manager) or NM.
  • network slice management can be performed through interaction between the first management unit and the second management unit.
  • the first management unit is mainly used to design a network slice template or a network slice instance according to the capability information of the subnet template or the subnet instance
  • the second management unit is mainly used to report the subnet template to the first management unit or
  • the device that can design the network slice template or the network slice instance according to the capability information of the subnet template or the subnet instance can be referred to as the first management network element;
  • the device that reports the capability information of the subnet template or the subnet instance to the first management unit may be referred to as a second management network element.
  • FIG. 3 is a schematic flowchart of a method for managing a network slice according to the first embodiment. As shown in FIG. 3 , the method in this embodiment includes the following steps:
  • Step 101 The first management unit acquires capability information of the subnet from the second management unit, where the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, where the subnet The capability information of the template is used to represent the characteristics of the subnet template, and the capability information of the subnet instance is used to represent the characteristics of the subnet instance.
  • the first management unit may obtain capability information of one or more subnets, and the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, and a subnet template is used for the descriptor.
  • Network information, subnet templates are used to deploy subnet instances, and subnet instances are used to represent a specific logical network.
  • the feature of the subnet template refers to the feature describing the subnet in the subnet template.
  • a subnet is an abstract concept. When a subnet instance is deployed with a subnet template, the subnet here corresponds to the subnet instance.
  • the characteristics of the subnet are the characteristics of the subnet instance.
  • the capability information of the subnet template includes at least one of the following: an identifier of the subnet template, a type of the subnet template, a function of the subnet template, a function feature of the subnet template, a sharing policy of the subnet template, and a subnet template. Connection information of the network template, performance information of the subnet template, service information of the subnet template, and configurable parameters of the subnet template.
  • the type of the subnet template is used to describe the type of the subnet.
  • the function of the subnet template is used to describe the function of the subnet.
  • the functional features of the subnet template are used to describe the functional characteristics of the subnet.
  • the subnet template connection information is used to describe the subnet connection information.
  • the subnet template performance information is used to describe the subnet performance information and the subnet template service information is used to describe the subnet. Business information.
  • the subnet type is equal to the subnet instance type.
  • the function of the subnet is equal to the function of the subnet instance.
  • the functional characteristics of the subnet are equal to the functional characteristics of the subnet instance.
  • the sharing policy is equal to the sharing policy of the subnet instance.
  • the connection information of the subnet is equal to the connection information of the subnet instance.
  • the performance information of the subnet is equal to the performance information of the subnet instance, and the service information of the subnet is equal to the service information of the subnet instance.
  • the type of the subnet template can be divided into the following ways: In one example, the type of the subnet template can be classified according to the type of the network system.
  • the existing network system mainly includes: Global System of Mobile communication (GSM) System, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, Long Term Evolution (LTE) system and fifth generation Mobile communication (5th-Generation, 5G for short) system.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • 5th-Generation, 5G for short fifth generation Mobile communication
  • the types of subnet templates can be classified into GSM subnet templates, CDMA subnet templates, WCDMA subnet templates, LTE subnet templates, or 5G subnet templates.
  • the type of subnet template can be divided according to the type of network, and each network system usually includes an AN subnet, a CN subnet, and a TN subnet.
  • the type of the subnet template can be AN, CN or TN.
  • the type of the subnet template can be classified according to the application scenario of the network system.
  • the application scenario of the network system there are mainly three application scenarios: Enhanced Mobile Broadband (eMBB), and super Ultra-reliable and Low Latency Communications (URLLC), Massive Machine Type Communication (MMTC).
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra-reliable and Low Latency Communications
  • MMTC Massive Machine Type Communication
  • the subnet template type can be eMBB, URLL or mMTC.
  • the type of the subnet template may be classified according to a protocol structure of the network system.
  • the data is divided into control plane (CP) data and user plane (UP) data according to the protocol architecture.
  • CP control plane
  • UP user plane
  • the subnet template type can be UP or CP.
  • any two or more subnet template types of the network system type, the network type, the application scenario of the network system, and the protocol architecture of the network system may be combined, for example, the protocol architecture and network of the network system may be combined.
  • Type and application scenario subnet template type, the subnet template type can be (eMBB/URLLC/mMTC) AN CP, (eMBB/URLLC/mMTC) AN UP, (eMBB/URLLC/mMTC)CN CP, (eMBB/ URLLC/mMTC) CN UP, (eMBB/URLLC/mMTC) TN CP and (eMBB/URLLC/mMTC) TN UP and the like.
  • the identifier of the subnet template is used to uniquely identify a subnet template. This embodiment does not limit the identifier of the subnet template.
  • the function of the subnet template is related to the type of the subnet template.
  • the subnets described by different types of subnet templates have different functions.
  • the function of the CN subnet may include one or more of the following functions: Database, Domain Name System (DNS), Mobile Management, Session Management, Security Service, Authentication, Packet Process Scheduler, Bearing Service Process, and Network Protocol Process.
  • the functions of the AN subnet include Radio Resource Management (RRM), Packet Data Convergence Protocol-signaling radio bearers (PDCP-SRB) management, and radio link control (Radio).
  • RRM Radio Resource Management
  • PDCP-SRB Packet Data Convergence Protocol-signaling radio bearers
  • Radio link control Radio link control
  • RLC Link Control
  • MAC Medium Access Control
  • IP Internet Protocol
  • L2RLC data link layer radio link control
  • L2MAC data link Layer Media Access Control
  • L1PHY Physical Layer
  • PDCP-DRB PDCP-data radio bearers
  • a function that indicates that the function may or may not be selected.
  • the Mobility Management function of the eMTC CN subnet template is an option.
  • the mMTC CN subnet is selected to instantiate a CN instance (Instance to support the resident meter reading service, the function is not selected.
  • Select mMTC CN subnet instantiation This feature is selected when a CN Instance is supported for wearable device data collection.
  • the function of the subnet template is used to describe the value of the subnet feature described by the subnet template.
  • the mobility management function of the CN subnet may be characterized by low speed movement, normal movement, and high speed movement.
  • the characteristics of the SLA capability supported by the subnet include the range of latency (for example, 1ms-3ms), the minimum value of the report success rate, and the minimum of the Command Success Ratio.
  • the value, the size of the coverage for example, the diameter of the coverage area), the capacity (Capacity), the value of the reliability parameter, the size of the throughput (Throughput), and the like.
  • the subnet template sharing policy is used to describe that the subnet described by the subnet template can only form one network slice or can form multiple network slices, and the subnets described by the subnet template can be used to form which network slices.
  • connection information of the subnet template is used to describe the connection relationship between the subnet described by the subnet template and other subnets, and the interfaces and protocols used when the subnet is connected to other subnets.
  • the performance information of the subnet template includes the SLA of the subnet template, the Quality of Service (QoS), and the Key Performance Indicato (KPI).
  • QoS Quality of Service
  • KPI Key Performance Indicato
  • the service information of the subnet template is the information of the services supported by the subnet described by the subnet template.
  • Each subnet may support one or more services.
  • the services supported by different subnets may be the same or different. For example, some subnets support voice services, some subnets support Virtual Reality (VR) services, some subnets support multimedia services, and some subnets support instant messaging services.
  • VR Virtual Reality
  • the configurable parameters of the subnet template are used to describe which capability information of the subnet described by the subnet template can be configured by the user.
  • the user can set and modify the parameters according to requirements.
  • the capability information of the subnet instance includes at least one of the following: an identifier of the subnet instance, a type of the subnet instance, a function of the subnet instance, a function feature of the subnet instance, and a sharing policy of the subnet instance.
  • Both the subnet template and the subnet instance are used to represent a subnet.
  • the subnet instance is generated by the subnet template. Therefore, for the same subnet, the subnet instance has the same type as the subnet template.
  • the function of the subnet instance is the same as that of the subnet template.
  • the sharing policy of the subnet instance is the same as that of the subnet template.
  • the performance information of the subnet instance is the same as that of the subnet template.
  • the connection information of the subnet instance is the same as the connection information of the subnet template.
  • the service information of the subnet instance is the same as the service information of the subnet template, but the identifier of the subnet instance is different from the identifier of the subnet template.
  • the first management unit may be a cross-sectional slice management unit
  • the second slice management unit may be a domain slice management unit
  • the third management unit may be a client slice management unit.
  • the first management unit acquires the capability information of the subnet from the second management unit, where the first management unit receives the capability information of the subnet from the second management unit.
  • the first management unit may be a client slice management unit
  • the second management unit is a domain slice management unit
  • the first management unit acquires capability information of the subnet from the second management unit, specifically: first management
  • the unit receives capability information of the subnet forwarded by the second management unit by the cross-sectional slice management unit.
  • the second management unit may also be a database, where the capability information of the subnet is stored.
  • Step 102 The first management unit generates information about the network slice according to the capability information of the subnet, where the information of the network slice includes information of a network slice template or information of a network slice instance, where the network slice includes at least one subnet.
  • the first management unit generates the network slice information according to the capability information of the subnet, and the first management unit performs the network slice template design according to the capability information of the subnet, or the first management unit performs the network slice according to the capability information of the subnet.
  • the arrangement of the examples The information of the network slice template includes capability information of at least one subnet template or capability information of at least one subnet instance, and the information of the network slice instance includes capability information of at least one subnet template or capability information of at least one subnet instance.
  • the network slice template is used to deploy the network slice instance.
  • the network slice template information includes at least one of the following information: the indication information of the subnet instance, the indication information of the subnet template, and the network slice corresponding to the network slice template.
  • Decomposition strategy to subnet The indication information of the subnet instance is used to indicate the subnet instance included in the network slice template, and the indication information of the subnet template is used to indicate the subnet template included in the network slice template.
  • the decomposition strategy may specifically be a parameter mapping relationship between the network slice and the subnet. For example, the delay of the CN subnet is one quarter of the network slice, and the delay of the AN subnet is one quarter of the network slice delay. The delay of the TN subnet is one-half of the network slice delay.
  • the first management unit may slice the information of the template according to the capability information of the multiple subnets.
  • Each network slice template can satisfy at least one service requirement, and each network slice template has all or part of the functions of multiple subnet slices that generate the network slice template.
  • the first management unit may generate the information of the network slice template according to the capability information of the subnet template, or generate the information of the network slice template according to the capability information of the subnet instance, and may also be based on the sub
  • the capability information of the network template and the capability information of the subnet instance jointly generate information of the network slice template.
  • the first management unit generates a network slice template according to the subnet template.
  • a network is composed of an AN subnet, a CN subnet, and a TN subnet.
  • the network slice template is also composed of an AN subnet template and a CN subnet.
  • the combination of the template and the capability information of the TN subnet template may select a combination of the capability information of the AN subnet template, the CN subnet template, and the TN subnet template of the same network system to generate a network slice template.
  • the mMTC network slice template is generated according to the capability information of the MNTC's AN subnet template, CN subnet template, and TN subnet template.
  • the URLLC network slice template is generated, the URLLC network slice template is generated according to the capability information of the AN subnet template, the CN subnet template, and the TN subnet template of the URLLC.
  • the first management unit may also select a combination of the capability information of the AN subnet template, the CN subnet template, and the TN subnet template of different network systems to generate a network slice template.
  • the capability information of the subnet received by the first management unit is as follows:
  • the identifier of the CN subnet template and the type of the CN subnet are eMTC and the functions supported by the CN subnet: mobility management, session management, security management, authentication authentication management, etc., SLA supported by the CN subnet (delay: 5- 10ms, covering 10K square, number of users: 100w-300w, success rate 92%), connection point of CN subnet: CP1, CP2 and CP3, geographical location: Shanghai Pudong; template configurable parameters: whether mobility management supports, Number of users, coverage, success rate.
  • the identifier of the RAN subnet template, the type of the RAN subnet is eMTC, and the SLA supported by the RAN subnet (delay: 2-6ms, covering 10K square, number of users: 50w-200w, success rate 93%), CN subnet Connection points: CP4, CP5 and CP6; Geographical location: Shanghai Pudong. Template configurable parameters: number of users, coverage, success rate.
  • the identifier of the TN subnet template, the type of the TN subnet is eMTC, and the SLA supported by the TN subnet (delay: distance-related, covering 10K square, number of users: 500w, success rate 93%), connection point of the TN subnet : CP7, CP8, CP9 and CP10; Geographical location: Shanghai Pudong.
  • Template configurable parameters number of users, coverage, success rate
  • the first management unit may generate a network slice template for supporting the meter reading service according to the capability information of the three subnet templates, and the information of the network slice template includes:
  • the mobility management of the CN subnet template identifier is no;
  • the number of users supported by the network slice is the minimum number of users of the three subnet templates: 50w-200w;
  • the network slice success rate is multiplied by the success rate of the three subnet templates; the priority satisfaction degree is: AN>CN>TN;
  • the delay supported by the network slice is the delay of the three subnet templates.
  • Connection information CP1, CP2 is connected to CP7; CP5 is connected to CP8; CP6, CP7 is connected to CP9;
  • the type of network slice is eMTC.
  • the first management unit may further generate information of the network slice template according to the requirement information of the network slice and the capability information of the subnet, where the capability information of the subnet template refers to the foregoing description.
  • the requirement information of the network slice received by the first management unit may include: no need to support mobility, eMTC type, the number of users supported by the network slice is 50w-200w; the success rate of the network slice is 93% of the success rate of the three subnet templates* 93%*92%; the supported delay of network slicing is 20ms.
  • the first management unit selects the three subnet templates to generate the information of the network slice template, and the generated information of the network slice template includes, in addition to the requirement information of the network slice, the following:
  • the mobility management of the CN subnet template identifier is no;
  • Connection information CP1, CP2 is connected to CP7; CP5 is connected to CP8; CP6, CP7 is connected to CP9;
  • the first management unit generates a network slice template mainly according to the functions of the MMTC's AN subnet template, the CN subnet template, and the TN subnet template delay and mobility management, and of course, according to other functions of the subnet template. Generate network slice templates, which are not listed here.
  • the first management unit performs network according to the capability information of the subnet template or the subnet instance.
  • the design of the slice template may be: the first management unit first generates an AN subnet template according to the capability information of the AN CP subnet template and the capability information of the AN UP subnet template, according to the capability information of the CN UP subnet template and the CN UP sub.
  • the capability information of the network template generates a CN subnet template, and generates a TN subnet template according to the capability information of the TN CP subnet template and the capability information of the TN UP subnet template.
  • the first management unit generates a network slice template according to the generated capability information of the AN subnet template, the CN subnet template, and the TN subnet template.
  • the information about the AN subnet template, the CN subnet template, and the TN subnet template is sent to The third management unit.
  • the third management unit generates a network slice template by the third management unit according to the information of the AN subnet template, the CN subnet template, and the TN subnet template.
  • the third management unit may be a client slice management unit.
  • the above example is mainly described by the first management unit generating the information of the network slice template according to the capability information of the subnet template.
  • the first management unit may use the same method to generate the information of the network slice template according to the capability information of the subnet instance. No longer.
  • the information about the network splicing instance includes the requirement information of the subnet instance required to instantiate or create the network sharding instance, and the first management unit further generates the information of the network sharding instance according to the capability information of the subnet.
  • the demand information of the network slice instance may be received from the third management unit, and the demand information of the network slice instance is used to instantiate or create a network slice instance.
  • the requirement information of the network slice instance may include at least one of the following: a network slice type required by the network slice instance, an identifier of the network slice template required by the network slice instance, a number of users, and an SLA.
  • the first management unit determines, according to the requirement information of the network slice instance and the capability information of the subnet, the requirement information of the subnet instance required to instantiate or create the network slice instance. Specifically, the first management unit determines, according to the requirement information of the network slice instance and the capability information of the subnet, a subnet template or a subnet instance that can meet the requirement information of the network slice instance from the subnet template or the subnet instance, according to the network slice. The requirement information of the instance, and the capability information of the subnet template or the subnet instance that meets the requirement information of the network slice instance, generate the requirement information of the subnet instance required to instantiate or create the network slice instance.
  • the first management unit obtains the capability information of the subnet, and the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, and capability of the subnet template.
  • the information is used to indicate the characteristics of the subnet template.
  • the capability information of the subnet instance is used to represent the characteristics of the subnet instance.
  • the information of the network slice is generated according to the capability information of the subnet, and the information of the network slice includes the information of the network slice template or Information of a network slice instance, the network slice containing at least one subnet.
  • the first management unit can generate information of multiple network slices according to the capability information of multiple subnets to meet various service requirements, and the generated network slice can be reused, and the physical implementation of the network slice is shielded externally.
  • FIG. 4 is a signaling flowchart of a method for managing a network slice according to the second embodiment.
  • the first management unit may be a cross-domain slice management unit and a second slice management unit. It can be a domain slice management unit, and the third management unit can be customer.
  • the method in this embodiment may include the following steps:
  • Step 201 The third management unit sends the requirement information of the network slice to the first management unit.
  • the demand information of the network slice includes the type of the network slice and the functional characteristics of the network slice.
  • Types of network slices include GSM network slices, CDMA network slices, WCDMA network slices, LTE network slices, and 5G network slices.
  • the 5G network slice may be further typed including eMBB network slice, mMTC network slice, and URLLC network slice.
  • Step 202 The first management unit decomposes the requirement information of the network slice to obtain the requirement information of the at least two subnets.
  • the subnet's demand information includes the subnet type and the functional characteristics of the subnet.
  • the first management unit first decomposes the network slice type into at least two subnet types according to the type of the network slice, and then the first management unit decomposes the functional features of each subnet according to the functional features of the network slice.
  • the eMBB network slice type the eMBB network slice is decomposed into an eMBB RAN subnet, an eMBB CN subnet, and a TN CN subnet.
  • the functional features of the eMBB RAN subnet, the eMBB CN subnet, and the TN CN subnet are decomposed.
  • Step 203 The first management unit sends the requirement information of each subnet to the corresponding second management unit.
  • the first management unit sends the requirement information of each subnet to the corresponding second management unit.
  • Step 204 The second management unit generates a subnet template according to the requirement information of the subnet.
  • the second management unit generates a subnet template by using an overlay coverage/capacity planning algorithm, a resource selection algorithm, a parameter mapping decomposition capability, and a model conversion capability according to a network element or a functional model in the subnet.
  • steps 201 to 204 are optional steps, and the steps 201 to 204 can also be completed by manual negotiation, but the subnet template obtained by the final negotiation needs to be loaded into the second management unit.
  • Step 205 The second management unit sends the capability information of the generated subnet template to the first management unit.
  • the capability information of the subnet template includes at least one of the following: an identifier of the subnet template, a type of the subnet template, a function of the subnet template, a function feature of the subnet template, a sharing policy of the subnet template, and a subnet template. Connection information, performance information of the subnet template, service information of the subnet template, and configurable parameters of the subnet template.
  • Step 206 The first management management unit generates information of the network slice template according to the capability information of the subnet template.
  • the information of the network slice template includes capability information of at least one subnet template or capability information of at least one subnet instance, and the network slice template is used to deploy a network slice instance.
  • the steps 205 and 205 refer to the related description of the first embodiment, and details are not described herein again.
  • Step 207 The first management unit sends information of the network slice template to the third management unit.
  • the network slice template information includes at least one of the following information: indication information of the subnet instance, indication information of the subnet template, and network segmentation to subnet decomposition strategy corresponding to the network slice template, and the indication information of the subnet instance is used. Indicates the subnet instance included in the network slice template.
  • the subnet template indicates the subnet template included in the network slice template.
  • the first management unit may send the generated information of the plurality of network slice templates to the third management unit.
  • the third management unit may send a query request of the network slice template to the first management unit.
  • Step 208 The third management unit determines the requirement information of the network slice instance according to the received information of the network slice template.
  • the requirement information of the network slice instance may include at least one of the following: a network slice type required by the network slice instance, an identifier of the network slice template required by the network slice instance, a number of users, and an SLA.
  • Step 209 The third management unit sends a network slice instance request to the first management unit.
  • the network slice instance request includes the requirement information of the network slice instance.
  • Step 210 The first management unit determines the requirement information of the subnet instance according to the network slice instance request and the information of the network slice template.
  • the requirement information of the network slice instance is decomposed into the requirement information of at least two subnet instances, and the requirement information of the subnet instance includes at least one of the following information: the type of the subnet instance, the function of the subnet instance, and the functional characteristics of the subnet instance. And the SLA of the subnet instance.
  • Step 211 The first management unit sends a subnet instance request to the second management unit.
  • the subnet instance request message includes the requirement information of the subnet instance. Since the instance requirement information of the network slice is at least decomposed into the requirement information of the two subnet instances, the first management unit needs to send the subcarrier to the at least two second management units. Web instance request. For example, if the eMBB network slice is decomposed into an eMBB RAN subnet instance, an eMBB CN subnet instance, and an eMBB TN subnet instance, the first management unit sends a subnet instance request to the three second management units to request to acquire the eMBB RAN. Subnet instance, eMBB CN subnet instance, and eMBB TN subnet instance.
  • Step 212 The first management unit generates a subnet instance according to the capability information of the subnet instance request and the subnet template.
  • the first management unit converts the requirement information of the subnet instance into the corresponding network element deployment information and configuration information according to the capability information of the subnet instance request and the subnet template.
  • the first management unit generates the information of the network slice template according to the capability information of the subnet, and sends the information of the network slice template to the second management unit, so that the third management is performed.
  • the unit is based on the information of the network slice template.
  • the first management unit can generate information of multiple network slice templates according to the capability information of multiple subnets to meet various service requirements, and the network slice template can be reused, and the physical implementation of the network slice is externally shielded.
  • the third embodiment provides a method for managing a network slice.
  • the first management unit is a client slice management unit
  • the second The management unit is a domain slice management unit.
  • the cross-domain slice management unit receives the capability information of the subnet and forwards the information to the client slice management unit, and the client slice management unit generates the network slice template according to the capability information of the subnet.
  • 5 is a signaling flowchart of a method for managing a network slice according to the third embodiment. As shown in FIG. 5, the method in this embodiment may include the following steps:
  • Step 301 The client slice management unit sends the requirement information of the network slice to the cross-sectional slice management unit.
  • Step 302 The cross-domain slice management unit decomposes the demand information of the network slice to obtain the demand information of the at least two subnets.
  • Step 303 The cross-domain slice management unit sends the requirement information of each subnet to the corresponding domain slice management unit.
  • Step 304 The domain slice management unit generates capability information of the subnet template according to the requirement information of the subnet.
  • Step 305 The domain slice management unit sends the capability information of the generated subnet template to the cross-domain slice management unit.
  • Step 306 The cross-domain slice management unit sends the capability information of the subnet template to the client slice management unit.
  • Step 307 The client slice management unit generates information of the network slice template according to the capability information of the subnet template.
  • Step 308 The client slice management unit sends a network slice instance request to the cross-domain slice management unit.
  • the network slice instance request includes the requirement information of the network slice instance and the information of the multiple network slice templates generated by the client slice management unit.
  • the client slice management unit may send a query request of the network slice template to the cross-domain slice management unit.
  • the client slice management unit carries the information of the network slice template in the network slice instance request.
  • the client slice management unit may also send the network to the cross-sectional slice management unit before step 308.
  • a slice template load request is used to load information of multiple network slice templates onto the cross-region slice management unit.
  • only the information of multiple network slice templates is not required in the network slice instance request.
  • Step 309 The cross-domain slice management unit determines the requirement information of the subnet instance according to the requirement information of the network slice instance and the information of the network slice template.
  • Step 310 The cross-domain slice management unit sends a subnet instance request to the domain slice management unit.
  • the subnet slice instance request message includes the requirement information of the subnet instance.
  • Step 311 The domain slice management unit generates a subnet slice instance according to the capability information of the subnet instance request and the subnet template.
  • FIG. 6 is a schematic structural diagram of a network slice management apparatus provided in Embodiment 4. As shown in FIG. 6, the network slice management apparatus of this embodiment includes an acquisition module 11 and a generation module 12.
  • the obtaining module 11 is configured to acquire capability information of the subnet from the second management unit, where the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, where The capability information of the subnet template is used to indicate a feature of the subnet template, and the capability information of the subnet instance is used to represent a feature of the subnet instance;
  • the generating module 12 is configured to generate information about the network slice according to the capability information of the subnet, where the information of the network slice includes information of a network slice template or information of a network slice instance, where the network slice includes at least one of the subnets.
  • the capability information of the subnet template includes at least one of the following: an identifier of the subnet template, a type of the subnet template, a function of the subnet template, a function feature of the subnet template, and a sharing of the subnet template.
  • the policy the connection information of the subnet template, the performance information of the subnet template, the service information of the subnet template, and the configurable parameters of the subnet template.
  • the capability information of the subnet instance includes at least one of the following: an identifier of the subnet instance, a type of the subnet instance, a function of the subnet instance, a function feature of the subnet instance, and a sharing of the subnet instance. Policy, performance information of the subnet instance, connection information of the subnet instance, and service information of the subnet instance.
  • the information about the network slice template includes capability information of at least one subnet template or capability information of at least one subnet instance, where the information of the network slice instance includes capability information of at least one subnet template or at least one sub The capability information of the network instance.
  • the information about the network slice template further includes at least one of the following information: indication information of the subnet instance, indication information of the subnet template, and network segmentation to subnet decomposition strategy corresponding to the network slice template.
  • the indication information of the subnet instance is used to indicate a subnet instance included in the network slice template
  • the indication information of the subnet template is used to indicate a subnet template included in the network slice template, where the network A slice template is used to deploy a network slice instance.
  • the information about the network slice includes the information of the network slice template
  • the device further includes a sending module (not shown), and the sending module is configured to send the information of the network slice template to the third management unit.
  • the information of the network slice instance includes requirement information for instantiating or creating a subnet instance required by the network slice instance
  • the device further includes a receiving module (not shown), and the receiving module is configured to:
  • the demand information of the network slice instance is received from a third management unit, and the demand information of the network slice instance is used to instantiate or create a network slice instance.
  • the generating module 12 is specifically configured to: according to the requirement information of the network slice instance and the capability information of the subnet, determine requirement information of a subnet instance required to instantiate or create the network slice instance.
  • the sending module is further configured to send a query request message to the second management unit, where the query request message is used to request capability information of the subnet.
  • the device in this embodiment may be used to perform the steps performed by the first management unit in the methods provided in the foregoing Embodiments 1 to 3.
  • the specific implementation manners and technical effects are similar, and details are not described herein again.
  • FIG. 7 is a schematic structural diagram of a network slice management apparatus according to Embodiment 5. As shown in FIG. 7, the network slice management apparatus of this embodiment includes a generation module 21 and a transmission module 22.
  • the generating module 21 is configured to generate capability information of the subnet, where the capability information of the subnet includes at least one of the following information: capability information of the subnet template, capability information of the subnet instance, and capability information of the subnet template. a feature for indicating the subnet template, where the capability information of the subnet instance is used to represent a feature of the subnet instance;
  • the sending module 22 is configured to send capability information of the subnet to the first management unit.
  • the device further includes a receiving module (not shown), where the receiving module is configured to receive a query request message sent by the first management unit, where the query request message is used to request the capability of the subnet. information.
  • the capability information of the subnet template includes at least one of the following: an identifier of the subnet template, a type of the subnet template, a function of the subnet template, a function feature of the subnet template, and a sharing of the subnet template.
  • the policy the connection information of the subnet template, the performance information of the subnet template, the service information of the subnet template, and the configurable parameters of the subnet template.
  • the capability information of the subnet instance includes at least one of the following: an identifier of the subnet instance, a type of the subnet instance, a function of the subnet instance, a function feature of the subnet instance, and a sharing of the subnet instance. Policy, performance information of the subnet instance, connection information of the subnet instance, and service information of the subnet instance.
  • the device in this embodiment may be used to perform the steps performed by the second management unit in the methods provided in the foregoing Embodiments 1 to 3.
  • the specific implementation manners and technical effects are similar, and details are not described herein again.
  • the receiving module and the sending module may be implemented by one transceiver, or the receiving module is implemented by an independent receiver, and the sending module is implemented by an independent receiver.
  • the processing module in the above embodiment may be implemented by a processor having a data processing function.
  • the network slice management apparatus provided in this embodiment includes a processor 31, a memory 32, and a communication interface 33.
  • the communication interface 33 is configured to communicate with other devices, and the processor 31 is configured to execute the instructions stored in the memory 32, so that the management device of the network slice performs the foregoing methods for providing the first embodiment to the third embodiment.
  • the steps performed by the first management unit are similar in implementation and technical effects, and are not described here.
  • the seventh embodiment provides a management apparatus for the network slice, and the management device of the network slice is the same as the device shown in FIG. 8.
  • the management device of the network slice is used to execute the second method in the first embodiment to the third embodiment.
  • the steps performed by the management unit are similar to the technical effects, and are not described here.
  • Embodiment 8 provides a computer readable storage medium storing instructions that, when executed, cause a computer to execute a first management unit in a method provided in Embodiments 1 through 3 above The steps, specific implementation methods and technical effects are similar, and will not be described here.
  • Embodiment 9 provides a computer readable storage medium storing instructions that, when executed, cause a computer to execute a second management unit in a method as provided in Embodiments 1 through 3 above The steps performed, the specific implementation methods and technical effects are similar, and will not be described here.
  • Embodiment 10 provides a computer program product, the computer program product comprising instructions, when the instructions are executed, causing a computer to perform the steps performed by the first management unit in the methods provided in the foregoing Embodiments 1 to 3, The method and technical effect are similar and will not be described here.
  • Embodiment 11 provides a computer program product, the computer program product comprising instructions, when the instructions are executed, causing a computer to perform the steps performed by the second management unit in the methods provided in the first embodiment to the third embodiment,
  • the specific implementation and technical effects are similar, and are not described here.
  • the processor referred to in this application may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable.
  • Logic device transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the application.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the bus mentioned in this application may be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • the bus in the drawings of the present application is not limited to only one bus or one type of bus.
  • the communication interface mentioned in the present application may include a separate transmitter and a separate receiver, or may be a transmitter and a receiver integrated.
  • the communication interface can operate under the direction of the corresponding processor.
  • the transmitter may correspond to a transmitter in the physical device
  • the receiver may correspond to a receiver in the physical device.
  • each module of the management device of the above network slice is only a division of a logical function, and the actual implementation may have another division manner, for example, multiple units or components may be combined or integrated. Go to another system, or some features can be ignored or not executed.
  • the coupling or direct coupling or communication connection shown or discussed herein may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

Abstract

本申请提供一种网络切片的管理方法和装置，第一管理单元通过获取子网的能力信息，子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，子网模板的能力信息用于表示子网模板的特征，子网实例的能力信息用于表示子网实例的特征，然后，根据子网的能力信息生成网络切片的信息，网络切片的信息包括网络切片模板的信息或网络切片实例的信息，所述网络切片包含至少一个子网。所述方法，第一管理单元能够根据多个子网的能力信息生成多种网络切片的信息，以满足多种业务需求，且生成的网络切片可以重复利用，并且对外屏蔽了网络切片的物理实现。

Description

网络切片的管理方法和装置
本申请要求于2017年3月18日提交中国专利局、申请号为201710162500.9、申请名称为“网络切片的管理方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，尤其涉及一种网络切片的管理方法和装置。
背景技术
当前的网络业务蓬勃发展，包括网络自身的发展和网络应用的发展，而网络的虚拟化进一步加快了发展趋势。下一代网络将扩展为支持新的不同类型的客户和合作伙伴，业务多样性和自动部署是下一代网络的一个特性，如何利用现有的网络资源，快速的响应企业到企业(Business to Business，简称B2B)和企业到客户(Business-to-Customer，简称B2C)的业务需求，及时提供新业务的上线和开通，缩短新业务的上市时间(Time To Market，简称TTM)是运营商面临的主要竞争压力。
网络切片(Network Slice)是下一代网络满足不同行业、不同用户对网络特殊需求的重要技术手段。网络切片是保证承载业务能达成服务水平协议(Service level agreement，简称SLA)要求的通信资源，这些资源可以按不同需求，进行硬隔离(物理隔离)，也可以软隔离(逻辑隔离)。也可以认为网络切片是完成某个(些)业务所需的网络功能及资源的组合，是一个完整的逻辑网络。下一代网络是跨厂商的网络，即网络切片的不同组件可能来自不同的厂商，比如：某个运营商要部署一个低时延的网络切片来提供虚拟现实业务，会采用A、B、C厂商来共同提供网络切片，如何自动编排或者在线集成不同厂商的不同组件来构成网络切片是快速自动部署业务的一大难点。
现有的业务部署过程为：客户(Customer)向运营商提出业务需求，运营商根据业务需求确定网络需求并设计相应的网络，向各设备厂商提出相应的网络或者子网需求，和各设备厂商协商达成所需的网络资源，根据各设备厂商提供的网络资源，设计相应的业务来满足Customer需求。可知，现有的业务部署由人工协商完成，耗时较长，且人工设计的网络切片无法复用，每次新业务都得需要漫长的协商过程，造成资源浪费。
发明内容
本申请提供一种网络切片的管理方法和装置，能够根据多个子网的能力信息生成多种网络切片的信息，以满足多种业务需求，生成的网络切片可以重复利用，提高了资源利用率。
本申请第一方面提供了一种网络切片的管理方法，包括：第一管理单元从第二管理单元获取子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，其中，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征；所述第一管理单元根据子网的能力信息生成网络切片的信息，所述网络切片的信息包括网络切片模板的信息或网络切片实例的信息，所述网络切片包含至少一个所述子网。
第一管理单元能够根据多个子网的能力信息生成多种网络切片的信息，以满足多种业务需求，且生成的网络切片可以重复利用，并且对外屏蔽了网络切片的物理实现。
当所述网络切片的信息包括网络切片模板的信息时，所述第一管理单元根据子网的能力信息生成网络切片的信息之后，还包括：所述第一管理单元向第三管理单元发送所述网切片模板的信息。
可选的，所述网络切片实例的信息包括实例化或者创建所述网络切片实例所需的子网实例的需求信息，所述第一管理单元根据子网的能力信息生成网络切片的信息之前，还包括：所述第一管理单元从第三管理单元接收所述网络切片实例的需求信息，所述网络切片实例的需求信息用于实例化或者创建一个网络切片实例。相应的，所述第一管理单元根据子网的能力信息生成网络切片的信息，具体为：所述第一管理单元根据所述网络切片实例的需求信息和所述子网的能力信息，确定实例化或者创建所述网络切片实例所需的子网实例的需求信息。
可选的，所述第一管理单元从第二管理单元获取子网的能力信息之前，还包括：所述第一管理单元向所述第二管理单元发送查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
本申请第二方面提供一种网络切片的管理方法，包括：
第二管理单元向第一管理单元发送子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征。
可选的，所述第二管理单元向第一管理单元发送子网的能力信息之前，还包括：所述第二管理单元生成所述子网的能力信息。
可选的，所述第二管理单元向第一管理单元发送子网的能力信息之前，还包括：所述第二管理单元接收所述第一管理单元发送的查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
本申请第三方面提供一种网络切片的管理装置，包括：
获取模块，用于从第二管理单元获取子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，其中，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征；
生成模块，用于根据子网的能力信息生成网络切片的信息，所述网络切片的信息包括网络切片模板的信息或网络切片实例的信息，所述网络切片包含至少一个所述子网。
可选的，所述网络切片的信息包括网络切片模板的信息，相应的，所述装置还包括：
发送模块，用于向第三管理单元发送所述网切片模板的信息。
可选的，所述网络切片实例的信息包括实例化或者创建所述网络切片实例所需的子网实例的需求信息，相应的，所述装置还包括：
接收模块，用于从第三管理单元接收所述网络切片实例的需求信息，所述网络切片实例的需求信息用于实例化或者创建一个网络切片实例；
所述生成模块，具体用于：
根据所述网络切片实例的需求信息和所述子网的能力信息，确定实例化或者创建所述网络切片实例所需的子网实例的需求信息。
可选的，所述装置还包括：
发送模块，用于向所述第二管理单元发送查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
本申请第四方面提供一种网络切片的管理装置，包括：
发送模块，用于向第一管理单元发送子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征。
可选的，所述装置还包括：
生成模块，用于生成所述子网的能力信息。
可选的，所述装置还包括：
接收模块，用于接收所述第一管理单元发送的查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
本申请第五方面提供网络切片的管理装置，包括处理器、存储器和通信接口，所述存储器用于存储指令，所述通信接口用于和其他设备通信，所述处理器用于执行所述存储器中存储的指令，以执行如下所述方法：
从第二管理单元获取子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，其中，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征；
根据子网的能力信息生成网络切片的信息，所述网络切片的信息包括网络切片模板的信息或网络切片实例的信息，所述网络切片包含至少一个所述子网。
可选的，所述网络切片的信息包括网络切片模板的信息，相应的，所述通信接口用于：向第三管理单元发送所述网切片模板的信息。
可选的，所述网络切片实例的信息包括实例化或者创建所述网络切片实例所需的子网实例的需求信息，所述处理器根据子网的能力信息生成网络切片的信息之前，所述通信接口还用于：从第三管理单元接收所述网络切片实例的需求信息，所述网络切片实例的需求信息用于实例化或者创建一个网络切片实例；
相应的，所述处理器具体用于：根据所述网络切片实例的需求信息和所述子网的 能力信息，确定实例化或者创建所述网络切片实例所需的子网实例的需求信息。
可选的，所述通信接口还用于：向所述第二管理单元发送查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
本申请第六方面提供网络切片的管理装置，包括处理器、存储器和通信接口，所述存储器用于存储指令，所述通信接口用于和其他设备通信，所述处理器用于执行所述存储器中存储的指令。所述通信接口具体用于：
向第一管理单元发送子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征。
可选的，所述处理器具体用于：生成所述子网的能力信息。
可选的，所述通信接口还用于：接收所述第一管理单元发送的查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
可选的，在本申请第一方面至第六方面中，所述子网模板的能力信息包括以下中的至少一种：子网模板的标识、子网模板的类型、子网模板的功能、子网模板的功能特征、子网模板的共享策略、子网模板的连接信息、子网模板的性能信息、子网模板的业务信息和子网模板的可配置参数。
可选的，在本申请第一方面至第六方面中，所述子网实例的能力信息包括以下中的至少一种：子网实例的标识、子网实例的类型、子网实例的功能、子网实例的功能特征、子网实例的共享策略、子网实例的性能信息、子网实例的连接信息和子网实例的业务信息。
可选的，在本申请第一方面、第三方面、第五方面中，所述网络切片模板的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息，所述网络切片实例的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息。
可选的，在本申请第一方面、第三方面、第五方面中，所述网络切片模板的信息还包括以下信息中的至少一种：子网实例的指示信息、子网模板的指示信息和所述网络切片模板对应的网络切片到子网的分解策略，所述子网实例的指示信息用于指示所述网络切片模板中包含的子网实例，所述子网模板的指示信息用于指示所述网络切片模板中包含的子网模板，所述网络切片模板用于部署网络切片实例。
本申请第七方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如本申请第一方面所述的网络切片的管理方法。
本申请第八方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如本申请第二方面所述的网络切片的管理方法。
本申请第九方面提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行如本申请第一方面所述的网络切片的管理方法。
本申请第十方面提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行如本申请第二方面所述的网络切片的管理方法。
本申请提供的网络切片的管理方法和装置，第一管理单元通过获取子网的能力信息，子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，子网模板的能力信息用于表示子网模板的特征，子网实例的能力信息用于表示子网实例的特征，然后，根据子网的能力信息生成网络切片的信息，网络切片的信息包括网络切片模板的信息或网络切片实例的信息，所述网络切片包含至少一个子网。所述方法，第一管理单元能够根据多个子网的能力信息生成多种网络切片的信息，以满足多种业务需求，且生成的网络切片可以重复利用，并且对外屏蔽了网络切片的物理实现。
附图说明
图1示出了本申请提供的一种可能的网络架构；
图2示出了一种现有的网络架构的示意图；
图3为实施例一提供的网络切片的管理方法的流程示意图；
图4为实施例二提供的网络切片的管理方法的信令流程图；
图5为实施例三提供的网络切片的管理方法的信令流程图；
图6为实施例四提供的网络切片的管理装置的结构示意图；
图7为实施例五提供的网络切片的管理装置的结构示意图；
图8为实施例六提供的网络切片的管理装置的结构示意图。
具体实施方式
本申请描述的网络架构以及业务场景是为了更加清楚的说明本申请的技术方案，并不构成对本申请提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
图1示出了本申请提供的一种可能的网络架构，该网络架构包括：业务支撑系统(Business support system，BSS)/客户端切片管理单元/业务管理单元(Service Manager,SM)、跨域切片管理单元(cross-domain slice manager)和多个域切片管理单元(domain slice manager)。目前网络主要分为三个域：接入网(Access Network，AN)域、核心网(Core Network，CN)域和传输网(Transport Network，TN)域。相应的，多个域切片管理单元包括AN域切片管理单元、CN域切片管理单元和TN域切片管理单元。其中，域切片管理单元也可以称为域子网管理单元，相应的，AN域切片管理单元也称为AN域子网管理单元，CN域切片管理单元也称为CN域子网管理单元，TN域切片管理单元也称为TN域子网管理单元。多个域切片管理单元可能来自不同的供应商(vendor)，例如，图1所示例子中，两个CN域切片管理单元分别由供应商1和供应商2提供，AN域切片管理单元由供应商3提供，TN域切片管理单元由供应商4提供。
其中，客户端切片管理单元用于对客户(customer)或者租户(tenant)从运营商网络租用的网络切片进行管理。
跨域切片管理单元，也称为网络切片管理单元或者网络切片设计单元，包括以下至少一种功能：网络切片管理、网络切片和子网络以及网络功能的映射、网络切片编 排、不同域提供的网络资源和Sub-SLA的协调。下述实施例中网络切片可以是保证承载业务或者服务能达到SLA要求的通信资源，也可以认为是完成某个service或某些service所需的网络功能及通信资源的组合。网络切片管理包括网络切片的设计、生命周期管理、网络切片模板的管理、网络切片的故障管理、网络切片的性能管理和网络切片的配置管理。网络切片编排是指对各域提供的子网络切片和网络功能统一进行编排，得到满足业务需求的网络切片，业务需求可以是SLA的要求、关键性能指标(Key Performance Indicator，KPI)的要求以及服务质量(Quality of Service，QoS)的要求。
域切片管理单元，也称为子网管理单元或者子网设计单元，主要用于对子网的管理、子网的业务管理以及子网的网络资源协调和编排。其中，子网管理包括子网的设计、生命周期管理(创建、更新、删除等)、子网的故障管理、子网的性能管理和子网的配置管理等。子网的业务管理包括业务生命周期管理、业务故障管理、业务性能管理和业务配置管理等。
具体地，CN域切片管理单元主要用于对CN子网管理、CN子网的业务管理以及CN子网的网络资源协调和编排。其中，CN子网管理包括CN子网的设计、生命周期管理(创建、更新、删除等)、CN子网的故障管理、CN子网的性能管理和CN子网的配置管理等。CN子网的业务管理包括业务生命周期管理、业务故障管理、业务性能管理和业务配置管理等。
AN域切片管理单元主要用于对AN子网管理、AN子网的业务管理以及AN子网的网络资源协调和编排。其中，AN子网管理包括AN子网的设计、生命周期管理(创建、更新、删除等)、AN子网的故障管理、AN子网的性能管理和AN子网的配置管理等。AN子网的业务管理包括业务生命周期管理、业务故障管理、业务性能管理和业务配置管理等。
TN域切片管理单元主要用于对TN子网管理、TN子网的业务管理以及TN子网的网络资源协调和编排。其中，TN子网管理包括TN子网的设计、生命周期管理(创建、更新、删除等)、TN子网的故障管理、TN子网的性能管理和TN子网的配置管理等。TN子网的业务管理包括业务生命周期管理、业务故障管理、业务性能管理和业务配置管理等。
上述提到的跨域切片管理单元和各域切片管理单元可以集成在已有的网元中，也可以以独立网元存在。图2示出了一种现有的网络架构的示意图，该网络架构包括以下网元：业务编排单元(Service Orchestrator，SO)、网络编排(Network Orchestrator，NO)单元和网元管理(Element Manager，EM)单元。业务编排单元也可以称为业务管理(Service Manager，SM)单元，网络编排单元也称为网络管理(Network Manager，NM)单元。
为描述方便，下文中，业务编排单元可以描述为SO单元或SO，网络编排单元可以描述为NO单元或NO。本申请中，可以将SO设置为一个单独的功能实体，也可以将SO设置为其它功能实体的功能模块，还可以将SO的功能集成在其他功能实体中。类似的，本申请中，可以将NO设置为一个单独的功能实体，也可以将NO设置为其它功能实体的功能模块，还可以将NO的功能集成在其他功能实体中。进一步地，SO和NO可以合并为一个合设实体，该合设实体具备SO的功能和NO的功能。例如，该 合设实体可以称之为业务与网络编排单元，可以理解的是，该合设实体还可以有其他名称，本申请并不限定。类似的，在合设实体的情况下，本申请中，可以将合设实体设置为一个单独的功能实体，也可以将合设实体设置为其它功能实体的功能模块，还可以将合设实体的功能集成在其他功能实体中。
上述SO的功能包括但不仅限于：根据BSS发送的业务请求消息对业务(service)进行生命周期管理(例如，实例化或创建，扩缩容或更新)；service聚合，service的管理(例如故障、配置、计费、性能、安全(Fault，Configuration，Accounting，Performance，Security，FCAPS)管理)以及service和网络切片(network slice)之间的映射。其中，service可以是一组用户能享有的指定服务水平协议(Service level agreement，SLA)的通信业务，例如，移动宽带(Mobile Broadband，MBB)业务，如语音以及物联网(Internet of Things，IOT)业务(例如，智能停车，智能抄表等)。
上述NO的功能包括但不仅限于：网络切片的管理(例如，生命周期管理、FCAPS管理、网络切片模板的管理)；网络功能(Network Function，NF)的管理；网络切片和网络功能的映射；协调不同类型的网络资源；协调不同的运营商、不同网络供应商提供的网络资源；对不同供应商提供的网络设备的统一编排，以使得不同网络供应商提供的网络资源可以满足目标业务的需求(例如，SLA的要求，关键性能指标(KeyPerformance Indicator，KPI)的要求以及服务质量(Quality of Service，QoS))；对外提供应用程序接口(Application Program Interface，API)，该API接口用于为第三方提供网络功能，实现跨运营商部署。
示例性的，SO和NO可以均设置在运营支撑系统(Operations Support System，OSS)/业务支撑系统(Business support system，BSS)中，SO和NO还可以有其他设置方式：例如二者均设置在OSS/BSS外部；又例如SO设置在OSS/BSS内，NO设置在NO外部。或者，SO和NO可以合并设置为一个合设实体，该合设实体可以设置在OSS/BSS内或OSS/BSS外部。
需要说明的是，跨域切片管理单元可以为上述的SO、NO或NM，各域切片或者子网管理单元也可以为SO、NO、EM、DM(Domain Manager)或NM。
下面将基于上面所述的本申请涉及的共性方面，对本申请中的技术方案进行描述。
在上述网络架构的基础上，本申请的方案中，可以通过第一管理单元、第二管理单元的交互，进行网络切片的管理。其中，第一管理单元主要用于根据子网模板或者子网实例的能力信息进行网络切片模板的设计或网络切片实例的编排，第二管理单元主要用于向第一管理单元上报子网模板或者子网实例的能力信息，可以理解的是，能够根据子网模板或者子网实例的能力信息进行网络切片模板的设计或网络切片实例的编排的设备都可以称为第一管理网元；类似的，向第一管理单元上报子网模板或者子网实例的能力信息的设备都可以称为第二管理网元。
本申请一提供一种网络切片的管理方法，图3为实施例一提供的网络切片的管理方法的流程示意图，如图3所示，本实施例的方法包括以下步骤：
步骤101、第一管理单元从第二管理单元获取子网的能力信息，子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，其中，子 网模板的能力信息用于表示子网模板的特征，子网实例的能力信息用于表示子网实例的特征。
第一管理单元可能获取到一个或多个子网的能力信息，子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，子网模板用于描述子网的信息，子网模板用于部署子网实例，子网实例用于表示一个具体的逻辑网络。其中，子网模板的特征指的是子网模板中描述子网的特征。子网是一个抽象的概念，当用子网模板部署一个子网实例时，这里的子网对应为子网实例，子网的特征为子网实例的特征。
具体的，子网模板的能力信息包括以下中的至少一种：子网模板的标识、子网模板的类型、子网模板的功能、子网模板的功能特征、子网模板的共享策略、子网模板的连接信息、子网模板的性能信息、子网模板的业务信息和子网模板的可配置参数。
其中，子网模板的类型用于描述子网的类型，子网模板的功能用于描述子网的功能，子网模板的功能特征用于描述子网的功能特征，子网模板的共享策略用于描述子网的共享策略，子网模板的连接信息用于描述子网的连接信息，子网模板的性能信息用于描述子网的性能信息、子网模板的业务信息用于描述子网的业务信息。
当基于该子网模板部署一个子网实例时，子网的类型等于子网实例的类型，子网的功能等于子网实例的功能，子网的功能特征等于子网实例的功能特征，子网的共享策略等于子网实例的共享策略，子网的连接信息等于子网实例的连接信息，子网的性能信息等于子网实例的性能信息、子网的业务信息等于子网实例的业务信息。
子网模板的类型可以通过如下几种方式划分：一种示例中，可以根据网络系统类型划分子网模板的类型，现有的网络系统主要包括：全球移动通讯(Global System of Mobile communication，简称GSM)系统、码分多址(Code Division Multiple Access，简称CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，简称WCDMA)系统、长期演进(Long Term Evolution，简称LTE)系统和第五代移动通信(5th-Generation，简称5G)系统。子网模板的类型可以分为GSM子网模板、CDMA子网模板、WCDMA子网模板、LTE子网模板或者5G子网模板。
另一种示例中，可以根据网络类型划分子网模板的类型，每个网络系统通常包含AN子网、CN子网和TN子网。相应的，子网模板的类型可以为AN、CN或者TN等类型。
另一种示例中，可以根据网络系统的应用场景划分子网模板的类型，例如，在5G系统中，主要有以下三种应用场景：增强型行动宽频应用(Enhanced Mobile Broadband，简称eMBB)、超可靠及低延迟通讯(Ultra-reliable and Low Latency Communications，简称URLLC)、大量连结机器型通讯(Massive Machine Type Communication，简称mMTC)。相应的，子网模板类型可以为eMBB、URLL或者mMTC等。
又一种示例中，可以根据网络系统的协议架构划分子网模板的类型，例如，根据协议架构将数据分为控制面(control plane，简称CP)数据和用户面(user plane，简称UP)数据。相应地，子网模板类型可以为UP或者CP。
又一种示例中，可以结合网络系统类型、网络类型、网络系统的应用场景、网络系统的协议架构的任意两个或者多个划分子网模板类型，例如，可以结合网络系统的 协议架构、网络类型和应用场景划分子网模板类型，则子网模板类型可以为(eMBB/URLLC/mMTC)AN CP、(eMBB/URLLC/mMTC)AN UP、(eMBB/URLLC/mMTC)CN CP、(eMBB/URLLC/mMTC)CN UP、(eMBB/URLLC/mMTC)TN CP和(eMBB/URLLC/mMTC)TN UP等类型。
子网模板的标识用于唯一标识一个子网模板即可，本实施例并不对子网模板的标识进行限定。子网模板的功能与子网模板的类型有关，不同类型的子网模板描述的子网的功能不同。例如，CN子网的功能可以包括以下功能中的一种或多种：数据库(Database)、域名管理系统(Domain Name System，DNS)、移动性管理(Mobile Management)、会话管理(Session Management)、安全服务(Security Service安)、鉴权(Authentication)、数据包调度处理(Packet process Scheduler)，承载服务处理(Bearing Service Process)和网络协议处理(Network Protocol Process)等。AN子网的功能包括无线资源管理(Radio Resource Management，简称RRM)、分组数据汇聚协议-信令无线承载(Packet Data Convergence Protocol-signalling radio bearers，简称PDCP-SRB)管理、无线链路控制(Radio Link Control，简称RLC)处理、媒体接入控制(Medium Access Control，简称MAC)处理、网络互联协议(Internet Protocol，简称IP)层处理、数据链路层无线链路控制(L2RLC)、数据链路层媒体接入控制(L2MAC)、物理层(L1PHY)处理、PDCP-数据无线承载(PDCP-data radio bearers，简称PDCP-DRB)管理。
可选地，针对某个功能可能还带有可选项，指示该功能可选择也不可以不选择。例如，eMTC CN子网模板的Mobility Management功能作为一个可选项，在选择mMTC CN子网实例化一个CN实例(Instance来支持居民抄表业务时，就不用选择该功能。选择mMTC CN子网实例化一个CN Instance来支持用于穿戴设备数据采集时，就选择该功能。
子网模板的功能特征用于描述该子网模板描述的子网特征的取值，例如，CN子网的移动性管理功能的特征可以为低速移动、正常移动和高速移动等。又如，子网支持的SLA能力的特征包括时延(latency)的范围(例如1ms-3ms)、上报成功率(Report Success Ratio)的最小取值、下发成功率(Command Success Ratio)的最小取值、覆盖范围(Coverage)的大小(例如，覆盖区域的直径)、容量大小(Capacity)、可靠性(Reliability)参数的取值、吞吐量(Throughput)的大小等。
子网模板的共享策略用于描述子网模板描述的子网只能组成一个网络切片或者可以组成多个网络切片，以及子网模板描述的子网可以用于组成哪些网络切片等。
子网模板的连接信息用于描述该子网模板描述的子网与其他子网的连接关系，以及该子网与其他子网连接时使用的接口、协议等。
子网模板的性能信息包括子网模板描述的子网的SLA、服务质量(Quality of Service，简称QoS)和关键绩效指标(Key Performance Indicato，简称KPI)等。
子网模板的业务信息为子网模板描述的子网支持的业务的信息，每个子网可能支持一个或多个业务，不同子网支持的业务可能相同也可能不同。例如，有些子网支持语音业务，有些子网支持虚实现实(Virtual Reality，简称VR)业务，有些子网支持多媒体业务，有些子网支持即时通讯业务等。
子网模板的可配置参数用于描述子网模板描述的子网的哪些能力信息可以由用户配置，对于可配置参数，用户可以根据需求对参数进行设置和修改。
本实施例中，子网实例的能力信息包括以下中的至少一种：子网实例的标识、子网实例的类型、子网实例的功能、子网实例的功能特征、子网实例的共享策略、子网实例的性能信息、子网实例的连接信息和子网实例的业务信息。
子网模板和子网实例都用于表示一个子网，子网实例由子网模板生成，因此对于同一个子网来说，子网实例的类型与子网模板的类型相同，子网实例的功能与子网模板的功能相同，子网实例的功能特征与子网模板的功能相同，子网实例的共享策略与子网模板的共享策略相同，子网实例的性能信息与子网模板的性能信息相同，子网实例的连接信息与子网模板的连接信息相同，子网实例的业务信息和子网模板的业务信息相同，但是子网实例的标识与子网模板的标识不同，子网实例的标识用于唯一标识一个子网实例，子网模板的标识用于唯一标识一个子网。对于子网实例的其他能力信息参照上述子网模板的能力信息的相关描述，这里不再赘述。
需要说明的是，本实施例中，第一管理单元可以为跨域切片管理单元，第二切片管理单元可以为域切片管理单元，第三管理单元可以为客户端切片管理单元。则第一管理单元从第二管理单元获取子网的能力信息，具体为：第一管理单元从第二管理单元接收子网的能力信息。可选的，第一管理单元还可以为客户端切片管理单元，第二管理单元为域切片管理单元，则第一管理单元从第二管理单元获取子网的能力信息，具体为：第一管理单元接收第二管理单元通过跨域切片管理单元转发的子网的能力信息。可选的，第二管理单元还可以为数据库，数据库上存储有子网的能力信息。
步骤102、第一管理单元根据子网的能力信息生成网络切片的信息，该网络切片的信息包括网络切片模板的信息或网络切片实例的信息，该网络切片包含至少一个子网。
第一管理单元根据子网的能力信息生成网络切片的信息，包括：第一管理单元根据子网的能力信息进行网络切片模板的设计，或者，第一管理单元根据子网的能力信息进行网络切片实例的编排。其中，网络切片模板的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息，网络切片实例的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息。
网络切片模板用于部署网络切片实例，可选的，网络切片模板的信息还包括以下信息中的至少一种：子网实例的指示信息、子网模板的指示信息、网络切片模板对应的网络切片到子网的分解策略。该子网实例的指示信息用于指示网络切片模板中包含的子网实例，该子网模板的指示信息用于指示网络切片模板中包含的子网模板。该分解策略具体可以为网络切片和子网之间的参数映射关系，比如CN子网的时延为网络切片的四分之一，AN子网的时延为网络切片时延的四分之一，TN子网的时延为网络切片时延的二分之一等。
第一管理单元可以根据多个子网的能力信息可以多种网络切片模板的信息。每种网络切片模板能够满足至少一种业务需求，每种网络切片模板具备生成该网络切片模板的多个子网切片的全部或部分功能。在生成网络切片模板的信息时，第一管理单元可以只根据子网模板的能力信息生成网络切片模板的信息，也可以只根据子网实例的 能力信息生成网络切片模板的信息，还可以根据子网模板的能力信息和子网实例的能力信息共同生成网络切片模板的信息。
以第一管理单元根据子网模板生成网络切片模板为例，通常，一个网络由AN子网、CN子网和TN子网组成，相应的，网络切片模板也由AN子网模板、CN子网模板和TN子网模板的能力信息组合组成。需要说明的是，第一管理单元在生成网络切片模板时，可以选取同一种网络系统的AN子网模板、CN子网模板片和TN子网模板的能力信息组合生成网络切片模板。例如，在生成一个mMTC网络切片模板时，根据mMTC的AN子网模板、CN子网模板和TN子网模板的能力信息生成mMTC网络切片模板。在生成URLLC网络切片模板时，根据URLLC的AN子网模板、CN子网模板和TN子网模板的能力信息生成URLLC网络切片模板。第一管理单元也可以选取不同网络系统的AN子网模板、CN子网模板片和TN子网模板的能力信息组合生成网络切片模板。
假设第一管理单元接收到的子网的能力信息如下：
CN子网模板的标识、CN子网的类型为eMTC、CN子网支持的功能：移动性管理、会话管理、安全管理、鉴权认证管理等，CN子网支持的SLA(时延：5-10ms，覆盖10K平方，用户数：100w-300w，成功率92％)，CN子网的连接点：CP1、CP2和CP3，地理位置：上海浦东；模板的可配置参数：移动性管理是否支持，用户数，覆盖，成功率。
RAN子网模板的标识、RAN子网的类型为eMTC，RAN子网支持的SLA(时延：2-6ms，覆盖10K平方，用户数：50w-200w，成功率93％)，CN子网的连接点：CP4、CP5和CP6；地理位置：上海浦东。模板的可配置参数：用户数，覆盖，成功率。
TN子网模板的标识、TN子网的类型为eMTC，TN子网支持的SLA(时延：与距离有关，覆盖10K平方，用户数：500w，成功率93％)，TN子网的连接点:CP7，CP8，CP9和CP10；地理位置：上海浦东。模板的可配置参数：用户数，覆盖，成功率
第一管理单元根据上述三个子网模板的能力信息，可以生成一个用于支持抄表业务的网络切片模板，则该网络切片模板的信息包括：
CN/AN/TN子网模板的标识；
CN子网模板标识的移动性管理为否；
网络切片支持的用户数为三个子网模板用户数的最小值：即50w-200w；
网络切片成功率为三个子网模板的成功率相乘；优先满足度为：AN>CN>TN；
网络切片支持的时延为三个子网模板的时延相加，具体值为CN：AN＝1:2；
连接信息：CP1，CP2连接CP7；CP5连接CP8；CP6，CP7连接CP9；
网络切片的类型为eMTC。
可选的，第一管理单元还可以根据网络切片的需求信息和子网的能力信息生成网络切片模板的信息，其中，子网模板的能力信息参照上述描述。第一管理单元接收到的网络切片的需求信息可以包括：不需要支持移动性，eMTC类型，网络切片支持的用户数为50w-200w；网络切片成功率为三个子网模板的成功率93％*93％*92％；网络切片的支持的时延为20ms。则第一管理单元选择上述的三个子网模板生成网切片模板 的信息，生成的网络切片模板的信息除上述网络切片的需求信息外，还包含：
CN/AN/TN子网模板的标识；
CN子网模板标识的移动性管理为否；
连接信息：CP1，CP2连接CP7；CP5连接CP8；CP6,CP7连接CP9；
时延：AN 7ms，CN 5ms，TN 8ms。
上述例子中第一管理单元主要根据mMTC的AN子网模板、CN子网模板和TN子网模板的时延和移动性管理两个功能生成网络切片模板，当然还可以根据子网模板的其他功能生成网络切片模板，这里不再一一列举。
如果上述多个子网模板的能力信息中包括AN/TN/CN CP子网模板和RAN/TN/CN UP子网模板时，则第一管理单元根据子网模板或者子网实例的能力信息进行网络切片模板的设计，可以为：第一管理单元先根据AN CP子网模板的能力信息和AN UP子网模板的能力信息生成AN子网模板，根据CN UP子网模板的能力信息和CN UP子网模板的能力信息生成CN子网模板，根据TN CP子网模板的能力信息和TN UP子网模板的能力信息生成TN子网模板。然后，第一管理单元根据生成的AN子网模板、CN子网模板和TN子网模板的能力信息生成网络切片模板。在另一种可能的实现方式中，第一管理单元生成AN子网模板、CN子网模板和TN子网模板之后，将AN子网模板、CN子网模板和TN子网模板的信息发送给第三管理单元，由第三管理单元根据AN子网模板、CN子网模板和TN子网模板的信息生成网络切片模板。当第一管理单元为跨域切片管理单元，第二管理单元为域切片管理单元时，第三管理单元可以为客户端切片管理单元。
上述例子主要以第一管理单元根据子网模板的能力信息生成网络切片模板的信息为例进行说明，第一管理单元可以采用同样的方法根据子网实例的能力信息生成网络切片模板的信息，这里不再赘述。
可选的，网络切片实例的信息包括实例化或者创建网络切片实例所需的子网实例的需求信息，第一管理单元根据子网的能力信息生成网络切片实例的信息之前，第一管理单元还可以从第三管理单元接收网络切片实例的需求信息，网络切片实例的需求信息用于实例化或者创建一个网络切片实例。其中，网络切片实例的需求信息可以包括以下信息中的至少一个：网络切片实例需要的网络切片类型、网络切片实例需要的网络切片模板的标识、用户数和SLA等。则第一管理单元根据网络切片实例的需求信息和子网的能力信息，确定实例化或者创建网络切片实例所需的子网实例的需求信息。具体的，第一管理单元根据网络切片实例的需求信息和子网的能力信息，从子网模板或子网实例中确定能够满足网络切片实例的需求信息的子网模板或者子网实例，根据网络切片实例的需求信息，以及满足网络切片实例的需求信息的子网模板或者子网实例的能力信息，生成实例化或者创建网络切片实例所需的子网实例的需求信息。
本实施实例的方法，第一管理单元通过获取子网的能力信息，子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，子网模板的能力信息用于表示子网模板的特征，子网实例的能力信息用于表示子网实例的特征，然后，根据子网的能力信息生成网络切片的信息，网络切片的信息包括网络切片模板的信息或网络切片实例的信息，所述网络切片包含至少一个子网。所述方法，第一管 理单元能够根据多个子网的能力信息生成多种网络切片的信息，以满足多种业务需求，且生成的网络切片可以重复利用，并且对外屏蔽了网络切片的物理实现。
在上述实施例一的基础上，图4为实施例二提供的网络切片的管理方法的信令流程图，本实施例中，第一管理单元可以为跨域切片管理单元，第二切片管理单元可以为域切片管理单元，第三管理单元可以为customer。如图4所示，本实施例的方法可以包括以下步骤：
步骤201、第三管理单元向第一管理单元发送网络切片的需求信息。
网络切片的需求信息包括网络切片的类型和网络切片的功能特征。网络切片的类型包括GSM网络切片、CDMA网络切片、WCDMA网络切片、LTE网络切片和5G网络切片等。5G网络切片由可以进一步包括eMBB网络切片、mMTC网络切片和URLLC网络切片等类型。
步骤202、第一管理单元分解网络切片的需求信息得到至少两个子网的需求信息。
子网的需求信息包括子网类型和子网的功能特征。具体的，第一管理单元先根据网络切片的类型，将网络切片类型分解为至少两个子网类型，然后，第一管理单元根据网络切片的功能特征分解得到各子网的功能特征。例如，对于eMBB网络切片类型，将eMBB网络切片分解为eMBB RAN子网、eMBB CN子网和TN CN子网。然后根据eMBB网络切片的功能特征，分解得到eMBB RAN子网、eMBB CN子网和TN CN子网的功能特征。
步骤203、第一管理单元将各子网的需求信息发送给对应的第二管理单元。
图4中只示出了一个第二管理单元，实际上有多个第二管理单元。第一管理单元将各子网的需求信息发送给对应的第二管理单元。
步骤204、第二管理单元根据子网的需求信息生成子网模板。
具体的，第二管理单元根据子网内的网元或者功能模型，通过叠加覆盖/容量规划算法、资源选择算法、参数映射分解能力、模型转换的能力等生成子网模板。
需要说明的是，步骤201至204为可选步骤，步骤201至204也可以由人工协商完成，但是需要将最终协商得到的子网模板加载到第二管理单元上。
步骤205、第二管理单元向第一管理单元发送生成的子网模板的能力信息。
子网模板的能力信息包括以下中的至少一种：子网模板的标识、子网模板的类型、子网模板的功能、子网模板的功能特征、子网模板的共享策略、子网模板的连接信息、子网模板的性能信息、子网模板的业务信息和子网模板的可配置参数。
步骤206、第一管理管理单元根据子网模板的能力信息生成网络切片模板的信息。
其中，网络切片模板的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息，网络切片模板用于部署网络切片实例。步骤205和步骤205的具体实现方式参照上述实施例一的相关描述，这里不再赘述。
步骤207、第一管理单元向第三管理单元发送网络切片模板的信息。
网络切片模板的信息还包括以下信息中的至少一种：子网实例的指示信息、子网模板的指示信息和网络切片模板对应的网络切片到子网的分解策略，子网实例的指示信息用于指示网络切片模板中包含的子网实例，子网模板的指示信息用于指示网络切 片模板中包含的子网模板。
第一管理单元可以将生成的多个网络切片模板的信息都发送给第三管理单元，可选的，在步骤207之前，第三管理单元可以向第一管理单元发送网络切片模板的查询请求。
步骤208、第三管理单元根据接收到的网络切片模板的信息确定网络切片实例的需求信息。
其中，网络切片实例的需求信息可以包括以下信息中的至少一个：网络切片实例需要的网络切片类型、网络切片实例需要的网络切片模板的标识、用户数和SLA等。
步骤209、第三管理单元向第一管理单元发送网络切片实例请求。
网络切片实例请求中包括网络切片实例的需求信息。
步骤210、第一管理单元根据网络切片实例请求和网络切片模板的信息确定子网实例的需求信息。
网络切片实例的需求信息被分解为至少两个子网实例的需求信息，子网实例的需求信息包括以下信息中的至少一个：子网实例的类型、子网实例的功能、子网实例的功能特征和子网实例的SLA等。
步骤211、第一管理单元向第二管理单元发送子网实例请求。
子网实例请求消息中包括子网实例的需求信息，由于网络切片的实例需求信息至少被分解为两个子网实例的需求信息，因此，第一管理单元需要向至少两个第二管理单元发送子网实例请求。例如，eMBB网络切片被分解为了eMBB RAN子网实例、eMBB CN子网实例和、eMBB TN子网实例，则第一管理单元向三个第二管理单元发送子网实例请求，以请求获取eMBB RAN子网实例、eMBB CN子网实例和、eMBB TN子网实例。
步骤212、第一管理单元根据接收到子网实例请求和子网模板的能力信息生成子网实例。
具体的，第一管理单元根据子网实例请求和子网模板的能力信息，将子网实例的需求信息转换为相应的网元部署信息和配置信息。
本实施实例的方法，第一管理单元通过获取子网的能力信息，根据子网的能力信息生成网络切片模板的信息，并将网络切片模板的信息发送给第二管理单元，以使第三管理单元根据网络切片模板的信息。所述方法，第一管理单元能够根据多个子网的能力信息生成多种网络切片模板的信息，以满足多种业务需求，且网络切片模板可以重复利用，并且对外屏蔽了网络切片的物理实现。
在上述实施例一的基础上，实施例三提供一种网络切片的管理方法，本实施例与实施例二的区别在于，本实施例中，第一管理单元为客户端切片管理单元，第二管理单元为域切片管理单元，本实施例中跨域切片管理单元接收到子网的能力信息后转发给客户端切片管理单元，由客户端切片管理单元根据子网的能力信息生成网络切片模板的信息，图5为实施例三提供的网络切片的管理方法的信令流程图，如图5所示，本实施例的方法可以包括以下步骤：
步骤301、客户端切片管理单元向跨域切片管理单元发送网络切片的需求信息。
步骤302、跨域切片管理单元分解网络切片的需求信息得到至少两个子网的需求信息。
步骤303、跨域切片管理单元将各子网的需求信息发送给对应的域切片管理单元。
步骤304、域切片管理单元根据子网的需求信息生成子网模板的能力信息。
步骤305、域切片管理单元向跨域切片管理单元发送生成的子网模板的能力信息。
步骤306、跨域切片管理单元将子网模板的能力信息发送给客户端切片管理单元。
步骤307、客户端切片管理单元根据子网模板的能力信息生成网络切片模板的信息。
步骤308、客户端切片管理单元向跨域切片管理单元发送网络切片实例请求。
与实施例二不同的是，本实施例中，网络切片实例请求中包括网络切片实例的需求信息和客户端切片管理单元生成的多个网络切片模板的信息。
可选的，在步骤308之前，客户端切片管理单元可以向跨域切片管理单元发送网络切片模板的查询请求。
本实施例中，客户端切片管理单元将网络切片模板的信息携带在网络切片实例请求中，在其他实施例中，客户端切片管理单元也可以在步骤308之前，向跨域切片管理单元发送网络切片模板加载请求，该网络切片模板加载请求用于将多个网络切片模板的信息加载到跨域切片管理单元上。相应的，网络切片实例请求中只不需要包括多个网络切片模板的信息。
步骤309、跨域切片管理单元根据网络切片实例的需求信息和网络切片模板的信息确定子网实例的需求信息。
步骤310、跨域切片管理单元向域切片管理单元发送子网实例请求。
子网切片实例请求消息中包括子网实例的需求信息。
步骤311、域切片管理单元根据接收到子网实例请求和子网模板的能力信息生成子网切片实例。
图6为实施例四提供的网络切片的管理装置的结构示意图，如图6所示，本实施例的网络切片的管理装置包括获取模块11和生成模块12。
获取模块11，用于从第二管理单元获取子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，其中，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征；
生成模块12，用于根据子网的能力信息生成网络切片的信息，所述网络切片的信息包括网络切片模板的信息或网络切片实例的信息，所述网络切片包含至少一个所述子网。
可选的，所述子网模板的能力信息包括以下中的至少一种：子网模板的标识、子网模板的类型、子网模板的功能、子网模板的功能特征、子网模板的共享策略、子网模板的连接信息、子网模板的性能信息、子网模板的业务信息和子网模板的可配置参数。
可选的，所述子网实例的能力信息包括以下中的至少一种：子网实例的标识、子网实例的类型、子网实例的功能、子网实例的功能特征、子网实例的共享策略、子网 实例的性能信息、子网实例的连接信息和子网实例的业务信息。
可选的，所述网络切片模板的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息，所述网络切片实例的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息。
可选的，所述网络切片模板的信息还包括以下信息中的至少一种：子网实例的指示信息、子网模板的指示信息和所述网络切片模板对应的网络切片到子网的分解策略，所述子网实例的指示信息用于指示所述网络切片模板中包含的子网实例，所述子网模板的指示信息用于指示所述网络切片模板中包含的子网模板，所述网络切片模板用于部署网络切片实例。
可选的，所述网络切片的信息包括网络切片模板的信息，所述装置还包括发送模块(图中未示出)，发送模块用于向第三管理单元发送所述网切片模板的信息。
可选的，所述网络切片实例的信息包括实例化或者创建所述网络切片实例所需的子网实例的需求信息，所述装置还包括接收模块(图中未示出)，接收模块用于从第三管理单元接收所述网络切片实例的需求信息，所述网络切片实例的需求信息用于实例化或者创建一个网络切片实例。所述生成模块12具体用于：根据所述网络切片实例的需求信息和所述子网的能力信息，确定实例化或者创建所述网络切片实例所需的子网实例的需求信息。
可选的，发送模块还用于向所述第二管理单元发送查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
本实施例的装置可用于执行上述实施例一至实施例三提供的方法中第一管理单元执行的步骤，具体实现方式和技术效果类似，这里不再赘述。
图7为实施例五提供的网络切片的管理装置的结构示意图，如图7所示，本实施例的网络切片的管理装置包括生成模块21和发送模块22。
生成模块21，用于生成子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征；
发送模块22，用于向第一管理单元发送所述子网的能力信息。
可选的，所述装置还包括接收模块(图中未示出)，接收模块用于接收所述第一管理单元发送的查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
可选的，所述子网模板的能力信息包括以下中的至少一种：子网模板的标识、子网模板的类型、子网模板的功能、子网模板的功能特征、子网模板的共享策略、子网模板的连接信息、子网模板的性能信息、子网模板的业务的信息和子网模板的可配置参数。
可选的，所述子网实例的能力信息包括以下中的至少一种：子网实例的标识、子网实例的类型、子网实例的功能、子网实例的功能特征、子网实例的共享策略、子网实例的性能信息、子网实例的连接信息和子网实例的业务信息。
本实施例的装置可用于执行上述实施例一至实施例三提供的方法中第二管理单元执行的步骤，具体实现方式和技术效果类似，这里不再赘述。
需要说明的是，上述实施例四和实施例五中，接收模块和发送模块可以通过一个 收发器实现，或者，接收模块由独立的接收器实现，发送模块由独立的接收器实现。上述实施例中的处理模块可以由具有数据处理功能的处理器实现。
图8为实施例六提供的网络切片的管理装置的结构示意图，如图8所示，本实施例提供的网络切片的管理装置包括处理器31、存储器32和通信接口33，所述存储器32用于存储指令，所述通信接口33用于和其他设备通信，所述处理器31用于执行所述存储器32中存储的指令，以使网络切片的管理装置执行上述实施例一至实施例三提供方法中第一管理单元执行的步骤，具体实现方式和技术效果类似，这里不再赘述。
实施例七提供一种网络切片的管理装置，该网络切片的管理装置的结构与图8所示装置相同，该网络切片的管理装置用于执行上述实施例一至实施例三提供的方法中第二管理单元执行的步骤，具体实现方式和技术效果类似，这里不再赘述。
实施例八提供一种计算机可读存储介质，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如上述实施例一至实施例三提供方法中第一管理单元执行的步骤，具体实现方式和技术效果类似，这里不再赘述。
实施例九提供一种计算机可读存储介质，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如上述实施例一至实施例三提供的方法中第二管理单元执行的步骤，具体实现方式和技术效果类似，这里不再赘述。
实施例十提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行如上述实施例一至实施例三提供方法中第一管理单元执行的步骤，具体实现方式和技术效果类似，这里不再赘述。
实施例十一提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行如上述实施例一至实施例三提供的方法中第二管理单元执行的步骤，具体实现方式和技术效果类似，这里不再赘述。
可以理解，本申请提到的处理器可以是中央处理器(CPU)，通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)，现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
本申请中提到的总线可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、外部设备互连(Peripheral Component，PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，本申请附图中的总线并不限定仅有一根总线或一种类型的总线。
本申请中提到的通信接口可以包括单独的发送器和单独的接收器，也可以是发送器和接收器集成一体。通信接口可以在相应的处理器的指示下工作。可选的，发送器可以对应物理设备中发射机，接收器可以对应物理设备中的接收机。
另外，需要说明的是，应理解以上网络切片的管理装置的各个模块的划分仅仅是一种逻辑功能的划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示 或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。

Claims (30)

  1. 一种网络切片的管理方法，其特征在于，包括：
    第一管理单元从第二管理单元获取子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，其中，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征；
    所述第一管理单元根据所述子网的能力信息生成网络切片的信息，所述网络切片的信息包括网络切片模板的信息或网络切片实例的信息，所述网络切片包含至少一个所述子网。
  2. 根据权利要求1所述的方法，其特征在于，所述子网模板的能力信息包括以下中的至少一种：子网模板的标识、子网模板的类型、子网模板的功能、子网模板的功能特征、子网模板的共享策略、子网模板的连接信息、子网模板的性能信息、子网模板的业务信息和子网模板的可配置参数。
  3. 根据权利要求1所述的方法，其特征在于，所述子网实例的能力信息包括以下中的至少一种：子网实例的标识、子网实例的类型、子网实例的功能、子网实例的功能特征、子网实例的共享策略、子网实例的性能信息、子网实例的连接信息和子网实例的业务信息。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述网络切片模板的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息，所述网络切片实例的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述网络切片模板的信息还包括以下信息中的至少一种：子网实例的指示信息、子网模板的指示信息和所述网络切片模板对应的网络切片到子网的分解策略，所述子网实例的指示信息用于指示所述网络切片模板中包含的子网实例，所述子网模板的指示信息用于指示所述网络切片模板中包含的子网模板，所述网络切片模板用于部署网络切片实例。
  6. 根据权利要求1所述的方法，其特征在于，所述网络切片的信息包括网络切片模板的信息，所述第一管理单元根据子网的能力信息生成网络切片的信息之后，还包括：
    所述第一管理单元向第三管理单元发送所述网切片模板的信息。
  7. 根据权利要求1-3任一项所述的方法，其特征在于，所述网络切片实例的信息包括实例化或者创建所述网络切片实例所需的子网实例的需求信息，所述第一管理单元根据子网的能力信息生成网络切片的信息之前，还包括：
    所述第一管理单元从第三管理单元接收所述网络切片实例的需求信息，所述网络切片实例的需求信息用于实例化或者创建一个网络切片实例；
    所述第一管理单元根据子网的能力信息生成网络切片的信息，包括：
    所述第一管理单元根据所述网络切片实例的需求信息和所述子网的能力信息，确定实例化或者创建所述网络切片实例所需的子网实例的需求信息。
  8. 根据权利要求1所述的方法，其特征在于，所述第一管理单元从第二管理单元获取子网的能力信息之前，还包括：
    所述第一管理单元向所述第二管理单元发送查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
  9. 一种网络切片的管理方法，其特征在于，包括：
    第二管理单元向第一管理单元发送子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征。
  10. 根据权利要求9所述的方法，其特征在于，所述第二管理单元向第一管理单元发送子网的能力信息之前，还包括：所述第二管理单元生成所述子网的能力信息。
  11. 根据权利要求9所述的方法，其特征在于，所述第二管理单元向第一管理单元发送子网的能力信息之前，还包括：
    所述第二管理单元接收所述第一管理单元发送的查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，所述子网模板的能力信息包括以下中的至少一种：子网模板的标识、子网模板的类型、子网模板的功能、子网模板的功能特征、子网模板的共享策略、子网模板的连接信息、子网模板的性能信息、子网模板的业务的信息和子网模板的可配置参数。
  13. 根据权利要求9-11任一项所述的方法，其特征在于，所述子网实例的能力信息包括以下中的至少一种：子网实例的标识、子网实例的类型、子网实例的功能、子网实例的功能特征、子网实例的共享策略、子网实例的性能信息、子网实例的连接信息和子网实例的业务信息。
  14. 一种网络切片的管理装置，其特征在于，包括：
    获取模块，用于从第二管理单元获取子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，其中，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征；
    生成模块，用于根据子网的能力信息生成网络切片的信息，所述网络切片的信息包括网络切片模板的信息或网络切片实例的信息，所述网络切片包含至少一个所述子网。
  15. 根据权利要求14所述的装置，其特征在于，所述子网模板的能力信息包括以下中的至少一种：子网模板的标识、子网模板的类型、子网模板的功能、子网模板的功能特征、子网模板的共享策略、子网模板的连接信息、子网模板的性能信息、子网模板的业务信息和子网模板的可配置参数。
  16. 根据权利要求14所述的装置，其特征在于，所述子网实例的能力信息包括以下中的至少一种：子网实例的标识、子网实例的类型、子网实例的功能、子网实例的功能特征、子网实例的共享策略、子网实例的性能信息、子网实例的连接信息和子网实例的业务信息。
  17. 根据权利要求14-16任一项所述的装置，其特征在于，所述网络切片模板的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息，所述网络 切片实例的信息包括至少一个子网模板的能力信息或者至少一个子网实例的能力信息。
  18. 根据权利要求14-16任一项所述的装置，其特征在于，所述网络切片模板的信息还包括以下信息中的至少一种：子网实例的指示信息、子网模板的指示信息和所述网络切片模板对应的网络切片到子网的分解策略，所述子网实例的指示信息用于指示所述网络切片模板中包含的子网实例，所述子网模板的指示信息用于指示所述网络切片模板中包含的子网模板，所述网络切片模板用于部署网络切片实例。
  19. 根据权利要求14所述的装置，其特征在于，所述网络切片的信息包括网络切片模板的信息，所述装置还包括：
    发送模块，用于向第三管理单元发送所述网切片模板的信息。
  20. 根据权利要求14-16任一项所述的装置，其特征在于，所述网络切片实例的信息包括实例化或者创建所述网络切片实例所需的子网实例的需求信息，所述装置还包括：
    接收模块，用于从第三管理单元接收所述网络切片实例的需求信息，所述网络切片实例的需求信息用于实例化或者创建一个网络切片实例；
    所述生成模块具体用于：
    根据所述网络切片实例的需求信息和所述子网的能力信息，确定实例化或者创建所述网络切片实例所需的子网实例的需求信息。
  21. 根据权利要求14所述的装置，其特征在于，还包括：
    发送模块，用于向所述第二管理单元发送查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
  22. 一种网络切片的管理装置，其特征在于，包括：
    发送模块，用于向第一管理单元发送子网的能力信息，所述子网的能力信息包括以下信息中的至少一个：子网模板的能力信息、子网实例的能力信息，所述子网模板的能力信息用于表示所述子网模板的特征，所述子网实例的能力信息用于表示所述子网实例的特征。
  23. 根据权利要求22所述的装置，其特征在于，还包括：
    生成模块，用于生成所述子网的能力信息。
  24. 根据权利要求22所述的装置，其特征在于，还包括：
    接收模块，用于接收所述第一管理单元发送的查询请求消息，所述查询请求消息用于请求所述子网的能力信息。
  25. 根据权利要求22-24任一项所述的装置，其特征在于，所述子网模板的能力信息包括以下中的至少一种：子网模板的标识、子网模板的类型、子网模板的功能、子网模板的功能特征、子网模板的共享策略、子网模板的连接信息、子网模板的性能信息、子网模板的业务的信息和子网模板的可配置参数。
  26. 根据权利要求22-23任一项所述的装置，其特征在于，所述子网实例的能力信息包括以下中的至少一种：子网实例的标识、子网实例的类型、子网实例的功能、子网实例的功能特征、子网实例的共享策略、子网实例的性能信息、子网实例的连接信息和子网实例的业务信息。
  27. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有指 令，当所述指令被执行时，使得计算机执行如权利要求1-8任一项所述的网络切片的管理方法。
  28. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如权利要求9-13任一项所述的网络切片的管理方法。
  29. 一种计算机程序产品，其特征在于，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行如权利要求1-8任一项所述的网络切片的管理方法。
  30. 一种计算机程序产品，其特征在于，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行如权利要求9-13任一项所述的网络切片的管理方法。
PCT/CN2018/078730 2017-03-18 2018-03-12 网络切片的管理方法和装置 WO2018171459A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18771593.3A EP3584999B1 (en) 2017-03-18 2018-03-12 Network slice management method and device
EP21165924.8A EP3907932B1 (en) 2017-03-18 2018-03-12 Network slice management method and apparatus
US16/573,509 US11063831B2 (en) 2017-03-18 2019-09-17 Network slice management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710162500.9 2017-03-18
CN201710162500.9A CN108632058B (zh) 2017-03-18 2017-03-18 网络切片的管理方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/573,509 Continuation US11063831B2 (en) 2017-03-18 2019-09-17 Network slice management method and apparatus

Publications (1)

Publication Number Publication Date
WO2018171459A1 true WO2018171459A1 (zh) 2018-09-27

Family

ID=63586216

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/078730 WO2018171459A1 (zh) 2017-03-18 2018-03-12 网络切片的管理方法和装置

Country Status (4)

Country Link
US (1) US11063831B2 (zh)
EP (2) EP3907932B1 (zh)
CN (1) CN108632058B (zh)
WO (1) WO2018171459A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113556784A (zh) * 2021-07-29 2021-10-26 新华三技术有限公司 网络切片实现方法、装置及电子设备
CN114071657A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 网络切片的处理方法、装置和存储介质
CN115211159A (zh) * 2020-03-04 2022-10-18 上海诺基亚贝尔股份有限公司 网络切片的分配资源
WO2023083259A1 (zh) * 2021-11-11 2023-05-19 中国电信股份有限公司 服务等级协议sla指标分解方法、装置、系统及相关设备

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018094667A1 (zh) * 2016-11-24 2018-05-31 华为技术有限公司 一种管理方法、管理单元及系统
CN108632063B (zh) * 2017-03-20 2021-01-05 华为技术有限公司 管理网络切片实例的方法、装置和系统
CN109560952B (zh) * 2017-09-27 2021-04-09 华为技术有限公司 一种网络切片管理方法及设备
CN111130825B (zh) * 2018-10-31 2022-09-23 中兴通讯股份有限公司 网络切片模板生成方法、装置、设备及存储介质
CN112104468B (zh) * 2019-06-17 2021-12-03 华为技术有限公司 一种管理服务的发现方法及装置
TWI714239B (zh) 2019-08-30 2020-12-21 緯創資通股份有限公司 行動通訊裝置及網路切片組態之管理方法
CN112817688B (zh) * 2019-11-15 2023-10-20 大唐移动通信设备有限公司 一种网络切片模板生成方法及装置
CN111065116B (zh) * 2019-12-10 2021-03-16 中盈优创资讯科技有限公司 一种端到端切片自动化部署方法及系统
CN114079958B (zh) * 2020-08-10 2023-09-05 中国移动通信集团浙江有限公司 5g切片实例的容灾池选择方法、装置及计算设备
CN117014315A (zh) * 2022-04-29 2023-11-07 华为技术有限公司 网络管理方法及装置、系统、存储介质
US20240073139A1 (en) * 2022-08-29 2024-02-29 Vmware, Inc. Multipath link optimization for private mobile network

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125091A (zh) * 2013-04-25 2014-10-29 杭州华三通信技术有限公司 网络配置自动部署方法及装置
CN106341832A (zh) * 2015-07-07 2017-01-18 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
US20170054595A1 (en) * 2015-08-21 2017-02-23 Huawei Technologies Co., Ltd. Method and Apparatus for Network Slicing
CN106792692A (zh) * 2016-12-27 2017-05-31 兴唐通信科技有限公司 一种基于sdn技术的物理切片方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8880659B2 (en) * 2008-01-17 2014-11-04 Aerohive Networks, Inc. Configuring network devices using compilations of coherent subsections of configuration settings
US9276816B1 (en) * 2011-01-17 2016-03-01 Cisco Technology, Inc. Resource management tools to create network containers and virtual machine associations
US10425830B2 (en) * 2015-09-07 2019-09-24 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
CN109952741A (zh) * 2016-10-05 2019-06-28 康维达无线有限责任公司 服务实例化的能力暴露
WO2018084975A1 (en) * 2016-11-02 2018-05-11 Intel IP Corporation Lifecycle management parameter modeling for virtual network functions
US10567440B2 (en) * 2016-12-16 2020-02-18 Nicira, Inc. Providing application visibility for micro-segmentation of a network deployment
CN110463139A (zh) * 2017-03-16 2019-11-15 英特尔Ip公司 在网络切片实例上支持son功能
US10973027B2 (en) * 2017-03-17 2021-04-06 At&T Intellectual Property I, L.P. Dynamic carrier management and network slicing for internet of things (IoT)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125091A (zh) * 2013-04-25 2014-10-29 杭州华三通信技术有限公司 网络配置自动部署方法及装置
CN106341832A (zh) * 2015-07-07 2017-01-18 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
US20170054595A1 (en) * 2015-08-21 2017-02-23 Huawei Technologies Co., Ltd. Method and Apparatus for Network Slicing
CN106792692A (zh) * 2016-12-27 2017-05-31 兴唐通信科技有限公司 一种基于sdn技术的物理切片方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
AN, QI ET AL.: "Network Slicing Architecture Based on SDN and NFV", TELECOMMUNICATIONS SCIENCE, no. 11, 30 November 2016 (2016-11-30), pages 119 - 126, XP055625917, ISSN: 1000-0801 *
See also references of EP3584999A4

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115211159A (zh) * 2020-03-04 2022-10-18 上海诺基亚贝尔股份有限公司 网络切片的分配资源
CN114071657A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 网络切片的处理方法、装置和存储介质
CN113556784A (zh) * 2021-07-29 2021-10-26 新华三技术有限公司 网络切片实现方法、装置及电子设备
CN113556784B (zh) * 2021-07-29 2023-05-26 新华三技术有限公司 网络切片实现方法、装置及电子设备
WO2023083259A1 (zh) * 2021-11-11 2023-05-19 中国电信股份有限公司 服务等级协议sla指标分解方法、装置、系统及相关设备

Also Published As

Publication number Publication date
US20200052969A1 (en) 2020-02-13
EP3584999A1 (en) 2019-12-25
EP3907932B1 (en) 2023-08-09
EP3584999B1 (en) 2021-05-05
EP3584999A4 (en) 2019-12-25
CN108632058A (zh) 2018-10-09
US11063831B2 (en) 2021-07-13
CN108632058B (zh) 2020-10-09
EP3907932A1 (en) 2021-11-10

Similar Documents

Publication Publication Date Title
WO2018171459A1 (zh) 网络切片的管理方法和装置
US11146462B2 (en) Network slice management method, device, and system
US11032214B2 (en) Method, apparatus, and system for managing network slice instance
US10958525B2 (en) Network slice management method and apparatus
EP3595244B1 (en) Network slice management method, unit and system
US11051183B2 (en) Service provision steps using slices and associated definitions
US10999740B2 (en) Network slice management method, management unit, and system
CN109417719B (zh) 一种网络资源的管理方法、装置及系统
US10924966B2 (en) Management method, management unit, and system
EP3585114B1 (en) Method, device and system for configuring network slice
US20220116865A1 (en) Information configuration method and management unit
WO2019062584A1 (zh) 一种网络切片管理方法及设备
US20190260636A1 (en) Method and apparatus for managing network slice instance
EP4207820A1 (en) Method and apparatus for dynamically triggering instantiation of edge application server
WO2018000389A1 (zh) 管理网络切片的方法及其装置
US11050638B2 (en) Network performance assurance method and apparatus
US20220224552A1 (en) Network slice charging method and apparatus
CN115767452A (zh) 一种网络切片的计费方法及装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018771593

Country of ref document: EP

Effective date: 20190920