WO2018094667A1 - 一种管理方法、管理单元及系统 - Google Patents

一种管理方法、管理单元及系统 Download PDF

Info

Publication number
WO2018094667A1
WO2018094667A1 PCT/CN2016/107153 CN2016107153W WO2018094667A1 WO 2018094667 A1 WO2018094667 A1 WO 2018094667A1 CN 2016107153 W CN2016107153 W CN 2016107153W WO 2018094667 A1 WO2018094667 A1 WO 2018094667A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
information
management unit
sub
management
Prior art date
Application number
PCT/CN2016/107153
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 PCT/CN2016/107153 priority Critical patent/WO2018094667A1/zh
Publication of WO2018094667A1 publication Critical patent/WO2018094667A1/zh
Priority to US16/422,116 priority patent/US10924966B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • 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/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • 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
    • 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/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a management method, a management unit, and a system.
  • Network slicing is an important technical means for the next generation network system to meet the special needs of different industries and different users.
  • Network slicing is a communication resource that guarantees that the bearer service can meet the service level agreement (SLA) requirements. These resources can be physically isolated according to different requirements, and can also be logically isolated. It can be considered that a network slice is completed. The combination of network functions and resources required by the business is a complete logical network.
  • SLA service level agreement
  • different tenants can deploy their own services by renting the network of the telecom operators. For example, the power company can rent the network of the telecom operator to deploy its meter reading service, and the telecom operator can set up its own network. Divided into different network slices to provide to different tenants.
  • the service designer of the network management needs to manually decompose the service request and convert it into a network resource request, and send it to the network designer of the core network respectively.
  • the network designer of the wireless access network deploys network devices by the network designers of the core network and the wireless access network, and then manages the corresponding network devices through the network element management unit.
  • the embodiment of the invention provides a management method, a management unit and a system, so as to solve the problem that the deployment efficiency of the network slice in the prior art is low.
  • the embodiment of the present invention provides a management method, where the method includes: a first management unit that receives a first management request, where the first management request carries demand information or indication information of a network slice, where the indication information is used to acquire a network.
  • the required information of the slice the first management unit acquires the demand information of the first sub-network according to the requirement information of the network slice, where the network slice includes the first sub-network; and then the first management unit determines the required information of the first sub-network
  • the first network resource requirement information where the first network resource requirement information is used to select, create, configure, activate, or request a first network resource instance that satisfies the first network resource requirement information.
  • the first management unit after receiving the first management request that carries the network slice request information or the indication information, can acquire the requirement information of the first sub-network, and determine the first information according to the requirement information of the first sub-network.
  • the requirement information of the first network resource required by the sub-network, and the first network resource instance may be selected, created, configured, activated, or requested according to the requirement information of the first network resource, so that the network can be automatically performed according to the demand information of the network slice.
  • the deployment of slices improves the efficiency of network slice deployment.
  • the first management unit may be an entity having a management function of a network slice, such as a core network domain orchestration unit, a radio access network domain or a core network element.
  • the identifier of the first sub-network or the identifier of the network slice may also be allocated.
  • the first management unit may further send a third management request to the third management unit, where the third management request carries the requirement information of the first network resource, and the third management request is used to request the first network resource instance.
  • the first management unit may further select the first network resource instance that already exists in the existing network.
  • the network slice further includes a second sub-network
  • the first management unit may further send a second management request to the second management unit, where the second management request carries the network slice requirement information, so that the second management The unit acquires the demand information of the second sub-network according to the requirement information of the network slice.
  • the first management unit may further acquire the requirement information of the second sub-network according to the requirement information of the network slice; and send the second management request to the second management unit, where the second management request carries the demand information of the second sub-network.
  • the second management request may also carry the identifier of the first sub-network or The identifier of the network slice.
  • the first management unit allocates an identifier of the first sub-network, and the first management request further carries an identifier of the network slice.
  • the first management unit may also associate the identifier of the first sub-network with The identifier of the network slice.
  • the embodiment of the present invention provides another method for managing a network slice, where the method includes: the second management unit receives a second management request from the first management unit, where the second management request carries the requirement of the second sub-network. Or the second management unit receives the second management request from the first management unit, where the second management request carries the network slice request information, and the second management unit acquires the second sub-network according to the network slice requirement information. Demand information; then, the second management unit determines demand information of the second network resource that satisfies the demand information of the second sub-network, where the demand information of the second network resource is used to select, create, configure, or activate the second network resource A second network resource instance of the demand information.
  • the second management unit after acquiring the requirement information of the second sub-network, can determine the requirement information of the second network resource and obtain the second network resource instance, so that the management of the second sub-network can be implemented.
  • the second management unit may be an entity such as an access network element or a network function.
  • the second management unit may further send a fourth management request to the fourth management unit, where the fourth management request carries the requirement information of the second network resource, and the fourth management request is used to request the second network The resource instance; or the second management unit may also select the second network resource instance that already exists in the existing network.
  • the second management unit may also assign an identification of the second subnetwork.
  • the second management request further carries the identifier of the first sub-network or the identifier of the network slice allocated by the first management unit.
  • the second management unit may also associate the identifier of the second sub-network.
  • the identifier of the first sub-network; or the second management unit may also associate the identifier of the second sub-network with the identifier of the network slice.
  • the required information of the second sub-network may include at least one of the following: a type of the second sub-network, an SLA information of the second sub-network, and a second sub-network. Deployment information, KPI of the second subnetwork, or functional characteristics of the second subnetwork.
  • the required information of the network slice involved may include at least one of the following types: type of network slice, service level agreement SLA information of the network slice, deployment information of the network slice, network slice Key performance indicator KPIs, network characteristics of network slices, user information of network slices, or service information provided by network slices.
  • the demand information of the first sub-network involved may include at least one of the following: a type of the first sub-network, SLA information of the first sub-network, deployment information of the first sub-network, a KPI of the first sub-network, or the first sub-network Functional characteristics of the network.
  • the required information of the first network resource may include at least one of the following: a type of the first network resource, descriptor information of the first network resource, instance information of the first network resource, a KPI of the first network resource, or the first Functional characteristics of network resources.
  • the first network resource instance involved may include at least one of the following: a network function, a network element, a network service, or a transmission resource.
  • the required information of the second network resource may include at least one of the following: a type of the second network resource, descriptor information of the second network resource, instance information of the second network resource, a KPI of the second network resource, or the second Functional characteristics of network resources.
  • the second network resource instance involved may include at least one of the following: a network function, a network element, a network service, or a transmission resource.
  • an embodiment of the present invention provides a first management unit, where the first management unit has a function of implementing behavior of a first management unit in the foregoing method design.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the first management unit includes a processor configured to support the first management unit to perform a corresponding function in the above method. Further, the first management unit may further include a communication interface for supporting communication between the first management unit and the second management unit, the third management unit, or other units. Further, the first management unit may further include a memory for coupling with the processor, which stores program instructions and data necessary for the first management unit.
  • an embodiment of the present invention provides a second management unit, where the second management unit has a function of implementing a behavior of a second management unit in the foregoing method design.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the second management unit includes a processor configured to support the second management unit to perform a corresponding function in the above method. Further, the second management unit is further A communication interface can be included, the communication interface for supporting communication of the second management unit with the first management unit, the fourth management unit, or other units. Further, the second management unit may further include a memory for coupling with the processor, which stores program instructions and data necessary for the second management unit.
  • the embodiment of the invention provides a communication system, which includes the first management unit described in the above aspect; or the system includes the first management unit and the second management unit described in the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing the computer software instructions used by the first management unit, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing the above-mentioned computer software instructions for the second management unit, which includes a program designed to execute the above aspects.
  • embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform functions performed by a first management unit in the method design described above.
  • embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform functions performed by a second management unit in the method design described above.
  • the first management unit after receiving the first management request that carries the network slice requirement information or the indication information, the first management unit can first determine the first required by the first sub-network.
  • the demand information of the network resource, and the first network resource instance may be selected, created, configured, activated, or requested according to the requirement information of the first network resource, so that the network slice deployment can be automatically performed according to the network slice requirement information, and the network segment is improved. Network slice deployment efficiency.
  • FIG. 1 is a schematic diagram of a possible network architecture according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of communication of a method for managing a network slice according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of communication of another method for managing a network slice according to an embodiment of the present invention.
  • FIG. 4 is a communication example diagram of still another method for managing a network slice according to an embodiment of the present invention.
  • FIG. 5 is a communication example diagram of still another method for managing a network slice according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of another first management unit according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a second management unit according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of another second management unit according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are used to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute a limitation of the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • FIG. 1 is a schematic system architecture diagram of a method for managing a network slice according to an embodiment of the present invention.
  • the system corresponding to the method includes an operation support system and a specific communication network, including:
  • E2E Orchestrator (E2E-O) unit The E2E-O unit can also be called an end-to-end management unit or an end-to-end orchestration and management unit, which can have some or all of the following functions:
  • End-to-end network slices eg, lifecycle management of network slices, management of network slice templates, fault management of network slices, performance management of network slices, and configuration management of network slices
  • management of end-to-end services eg , business lifecycle management, business template management, business fault management, business performance management and business configuration management
  • end-to-end network slicing and Sub-network slicing and mapping of network functions coordination of network resources provided by different sub-domains (such as access network domain, core network domain, and transport domain); unified scheduling of sub-network slices and network functions provided by each sub-domain
  • the sub-network slicing or network functions provided by different sub-domains can meet the requirements of the target service (for example, SLA requirements, Key Performance Indicator (KPI) requirements, and Quality of Service (QoS) requirements) .
  • KPI Key Performance Indicator
  • QoS Quality of Service
  • E2E-O can be composed of E2E Service Orchestrator (E2E-SO) units and E2E Network Orchestrator (E2E-NO) units, or E2E-SO units and E2E NO units.
  • E2E-SO E2E Service Orchestrator
  • E2E-NO E2E Network Orchestrator
  • E2E-O functions may also be implemented by a Cross-Domain Orchestrator (CD-O) unit, a Service Orchestrator (SO) unit, a Network Orchestrator (NO) unit, or a network.
  • CD-O Cross-Domain Orchestrator
  • SO Service Orchestrator
  • NO Network Orchestrator
  • NM Network Manager
  • the CN-Domain-O unit may also be referred to as a core domain management and orchestration unit, which may have some or all of the following functions:
  • Management of network slices in the core domain including network slice lifecycle management (create, update, delete), network slice fault management, network slice performance management, network slice configuration management, etc.); management of services within the core domain (including service life cycle) Management, business fault management, business performance management, business configuration management, etc.; coordination of network resources within the core domain for unified orchestration.
  • the CN-Domain-O may be composed of a core network domain service orchestrator (CN-Domain-SO) unit and a Core Network Domain Network Orchestrator (CN-Domain-NO) unit. It may also consist of only one of the CN-Domain-SO unit and the CN-Domain-NO unit.
  • CN-Domain-SO core network domain service orchestrator
  • CN-Domain-NO Core Network Domain Network Orchestrator
  • CN-Domain-O may also be completed by an entity such as an SO unit, a NO unit, an NM, a network control unit, or a network function virtualization orchestration unit.
  • entity such as an SO unit, a NO unit, an NM, a network control unit, or a network function virtualization orchestration unit.
  • the RAN-Domain-O unit may also be referred to as a radio access network and a scheduling and management unit, which may have the following parts or All features:
  • Management of network slices in the access domain including network slice lifecycle management (create, update, delete), network slice fault management, network slice performance management, network slice configuration management, etc.); management of services within the access domain (including services) Lifecycle management, service fault management, service performance management, service configuration management, etc.; coordination of network resources within the access domain for unified scheduling.
  • the RAN-Domain-O can be configured by the Radio Access Network Domain Service Orchestrator (RAN-Domain-SO) unit and the radio access network domain (Radio Access Network Domain Network Orchestrator, RAN-Domain).
  • the -NO) unit composition may also consist of only one of the RAN-Domain-SO unit and the RAN-Domain-NO unit.
  • RAN-Domain-O function may also be completed by an entity such as an SO unit, a NO unit, an NM, a network control unit, or a network function virtualization orchestration unit.
  • entity such as an SO unit, a NO unit, an NM, a network control unit, or a network function virtualization orchestration unit.
  • CN-NF-CTRL CN Network Function Controller
  • NF-M Network Function Manager
  • VNFM Virtualized Network
  • the Function Manager (VNFM) unit is used for lifecycle management, configuration management, fault management, and performance management of network functions in the core domain.
  • RAN-NF-CTRL RAN Network Function Controller
  • CN The core network element or network function, which can refer to one or more network functions of the core network control plane, or a centralized control network function unit of the core network function.
  • RAN access network element or network function, which may refer to one or more network functions of the access network control plane, or a centralized control network function unit of the access network function.
  • E2E-O, CN-Domain-O, RAN-Domain-O and OSS can be Any of the following cases: The first case: E2E-O is located in the OSS, CN-Domain-O and RAN-Domain-O are not located in the OSS; the second case: E2E-O, CN-Domain-O and RAN -Domain-O is not located in the OSS; the third case: E2E-O, CN-Domain-O, and RAN-Domain-O are all located in the OSS.
  • CN-NF-CTRL and RAN-NF-CTRL may or may not be located in the OSS.
  • the E2E SO has an interface with CN-Domain-O and RAN-Domain-O, and is connected to CN-NF-CTRL and CN in turn through CN-Domain-O, and through RAN.
  • -Domain-O is in turn connected to RAN-NF-CTRL and RAN.
  • the CN and the RAN may or may not have an interface.
  • an embodiment of the present invention provides a management method, and a management unit and system based on the method, to implement automatic deployment of network slices to improve network slice deployment efficiency.
  • FIG. 2 is a schematic diagram of communication of a method for managing a network slice according to an embodiment of the present invention. As shown in FIG. 2, the method includes: S201-S204, where S203 is an optional part.
  • the first management unit receives the first management request.
  • the first management request carries the demand information or the indication information of the network slice, where the indication information is used to obtain the requirement information of the network slice.
  • the first management unit may be CN-Domain-O, RAN-Domain-O or CN in FIG.
  • the E2E-O may send the first management request to the first management unit; or the user may send the first management request to the first management unit through an operable interface provided by the system; or The BSS may send a first management request to the first management unit.
  • the requirement information of the network slice may include at least one of the following: a service type supported by the network slice, a type of the network slice, an SLA information of the network slice, a deployment information of the network slice, a KPI of the network slice, and a network slice.
  • the foregoing SLA information may include at least one of the following: delay, success rate, bandwidth, coverage, traffic model, and the like; the foregoing KPI may include: maximum delay, or maximum bandwidth, and the like.
  • the first management unit acquires the requirement information of the first sub-network according to the requirement information of the network slice, where the network slice includes the first sub-network.
  • the first management unit may obtain the requirement information of the first sub-network according to the preset rule, or the first management unit may determine the demand information of the first sub-network by negotiating with other management units.
  • the different ways of obtaining the demand information of the first sub-network are exemplarily explained below.
  • the first way in this manner, the preset rule has been pre-stored in the first management unit.
  • the first management unit is CN-Domain-O
  • the first sub-network is a CN domain
  • the demand information of the network slice received by the first management unit includes SLA information such as delay, coverage, and dropped call rate
  • the preset rule stored in the first management unit is that the dropped call rate is only related to the CN domain, the coverage rate is only related to the RAN domain, and the ratio of the delay to the CN domain and the RAN domain is 1:2.
  • the call drop rate is equal to the call drop rate in the demand information of the received network slice, and the delay is equal to the required information of the received network slice.
  • the time delay is 1/3, and the coverage information is not included in the demand information of the first sub-network.
  • the second mode is as follows: After the first management unit is the CN-Domain-O, the first management unit may send a negotiation request to the RAN-Domain-O after receiving the network slice request information, where the negotiation request may include the network slice. Information such as the demand information and the allocation suggestion of the first management unit, for example, the allocation proposal of the SLA information including the delay, the call drop rate, and the like. After receiving the negotiation request, the RAN-Domain-O determines a new allocation proposal according to its network operation and returns it to the first management unit. In this step, it may take several rounds of negotiation to finally reach a consensus result.
  • the requirement information of the first sub-network may include at least one of the following: a type of the first sub-network, SLA information of the first sub-network, deployment information of the first sub-network, a KPI of the first sub-network, or a A functional feature of a subnetwork.
  • first sub-network may be a sub-network slice.
  • the first management unit allocates an identifier of the first sub-network or an identifier of the network slice.
  • the identifier of the network slice may include at least one of the following: a Public Land Mobile Network (PLMN) identity, a Tenant identity, a Slice type, a Service type, or a Slice identity.
  • PLMN Public Land Mobile Network
  • the first management request received by the first management unit carries the identifier of the network slice, and the first management unit may further associate the identifier of the first sub-network with the identifier of the network slice.
  • the identifier of the first sub-network may be the identifier of the first sub-network instance
  • the identifier of the network slice may be the identifier of the network shard instance.
  • the first management unit determines requirement information of the first network resource required by the first sub-network.
  • the requirement information of the first network resource is used to select, create, configure, activate, or request a first network resource instance that satisfies the requirement information of the first network resource.
  • the first management unit may determine the requirement information of the first network resource required by the first sub-network according to the preset algorithm and/or the network slice descriptor.
  • the following exemplary illustrations illustrate different ways of determining demand information for a first network resource.
  • the first management unit may obtain the foregoing preset algorithm in advance, and after receiving the requirement information of the network slice, the preset information may be used to obtain the foregoing required information of the first sub-network as the preset.
  • the input of the algorithm may output the corresponding demand information of the first network resource.
  • the first management unit may also use the network segmentation requirement information, for example, the SLA information, as the input of the preset algorithm, and the preset algorithm may output the corresponding first network resource requirement information.
  • the second mode is: if the first management request received by the first management unit carries the indication information of the network slice, the first management unit determines the descriptor information of the network slice according to the indication information of the network slice.
  • the descriptor of the network slice may be a network slice template, a network slice blueprint, or the like.
  • the first management unit may determine the network slice requirement information according to the descriptor of the network slice, and then determine the first network resource requirement information according to the network slice requirement information. .
  • the first management unit may also determine the sub-network descriptor according to the foregoing acquired requirement information of the first sub-network.
  • the sub-network descriptor may be included in the network slice descriptor. Further, the first management unit determines the demand information of the first network resource according to the sub-network descriptor.
  • the demand information of the first network resource may include at least one of the following: first The type of the network resource, the descriptor information of the first network resource, the instance information of the first network resource, the KPI of the first network resource, or the functional characteristic of the first network resource.
  • the first network resource can include at least one of the following: a network function, a network element, a network service, or a transmission resource.
  • the first management unit after receiving the requirement information or the indication information of the network slice, acquires the requirement information of the first sub-network according to the information, and determines the first sub-network according to the requirement information of the first sub-network. Determining the required information of the first network resource, and then selecting, creating, configuring, activating, or requesting the first network resource instance according to the requirement information of the first network resource, thereby automatically performing network slice deployment according to the network slice requirement, thereby Greatly improve the efficiency of network slice deployment.
  • the method shown in FIG. 2 may further include the following steps S205-S206; or the method shown in FIG. 2 may further include the following step S207.
  • the first management unit sends a third management request to the third management unit.
  • the third management request carries the requirement information of the first network resource, and the third management request is used to request the first network resource instance.
  • the third management unit can be CN-NF-CTRL or RAN-NF-CTRL. Specifically, when the first management unit is CN-Domain-O or CN, the third management unit may be CN-NF-CTRL; or, when the first management unit is RAN-Domain-O, the third management unit may Is RAN-NF-CTRL.
  • the third management unit selects, creates, configures, activates, or requests a first network resource instance that meets the requirement information of the first network resource according to the third management request.
  • the third management unit may specifically select, deploy, configure, or activate the following process.
  • a network resource instance First, the third management unit determines the demand information of the first network resource instance; then, the third management unit selects, deploys, configures, or activates the first network resource instance that meets the requirement information of the first network resource instance.
  • the first management unit may request, by the third management unit, the first network resource instance that meets the requirement information of the first network resource, Thereby improving the deployment efficiency of the network slice.
  • the first management unit selects a first network resource instance that already exists in the current network.
  • the first management unit determines, by the current network, whether the first network resource instance that meets the requirement information of the first network resource exists, and if yes, The first management unit directly selects the first network resource instance that already exists in the existing network and satisfies the requirement information of the first network resource.
  • a management unit can directly select the first network resource instance that already exists in the existing network, and no longer needs to request the first network resource instance from the third management unit, thereby further improving the deployment efficiency of the network slice.
  • FIG. 3 is a schematic diagram of communication of another method for managing a network slice according to an embodiment of the present invention.
  • the method may include S301, S302, and S305-S307.
  • the method may include S303-S307.
  • the first management unit acquires the requirement information of the second sub-network according to the requirement information of the network slice.
  • the second sub-network belongs to the network slice, that is, the network slice further includes the second sub-network.
  • the first management unit may acquire the requirement information of the second sub-network according to the preset rule, or the first management unit may determine the demand information of the second sub-network by negotiating with other management units.
  • the following is an exemplary illustration of different ways of obtaining demand information for a second subnetwork.
  • the first way in this manner, the preset rule has been pre-stored in the first management unit.
  • the first management unit is a CN-Domain-O
  • the second sub-network is a RAN domain
  • the demand information of the network slice received by the first management unit includes SLA information such as delay, coverage, and dropped call rate
  • the preset rule stored in the first management unit is that the dropped call rate is only related to the CN domain, the coverage rate is only related to the RAN domain, and the ratio of the delay to the CN domain and the RAN domain is 1:2.
  • the coverage ratio is equal to the coverage rate in the required information of the received network slice
  • the delay is equal to the time in the required information of the received network slice. 2/3 of the delay, and the call rate information is not included in the demand information of the second sub-network.
  • the second way assume that the first management unit is CN-Domain-O, when the first management unit receives After the request information of the network slice is sent, the negotiation request may be sent to the RAN-Domain-O.
  • the negotiation request may include information about the network slice and the first management unit's request for the RAN-Domain-O. Recommendations for the allocation of SLA information such as delay and dropped call rate.
  • the RAN-Domain-O determines a new allocation proposal according to its network operation and returns it to the first management unit. Among them, in this step, it may be necessary to negotiate a plurality of times to finally reach a negotiation result.
  • the first management unit sends a second management request to the second management unit, where the second management request carries the requirement information of the second sub-network.
  • the second management unit can be a RAN or a RAN-Domain-O.
  • the second management unit may be the RAN; or, when the first management unit is the CN-Domain-O, the second management unit may be the RAN-Domain-O.
  • the identifier of the first sub-network or the identifier of the network slice may also be carried in the second management request.
  • the requirement information of the second sub-network may include at least one of the following: a type of the second sub-network, SLA information of the second sub-network, deployment information of the second sub-network, a KPI of the second sub-network, or The functional characteristics of the two sub-networks.
  • the first management unit sends a second management request to the second management unit, where the second management request carries the requirement information of the network slice.
  • the identifier of the first sub-network or the identifier of the network slice may also be carried in the second management request.
  • the second management unit acquires the requirement information of the second sub-network according to the requirement information of the network slice.
  • the second management unit may obtain the requirement information of the second sub-network according to the preset rule, or the second management unit may determine the demand information of the second sub-network by negotiating with other management units.
  • the following is an exemplary illustration of different ways of obtaining demand information for a second subnetwork.
  • the first way In this manner, the preset rule has been pre-stored in the second management unit.
  • the second management unit is RAN-Domain-O
  • the second sub-network is the RAN domain
  • the demand information of the network slice received by the second management unit includes SLA information such as delay, coverage, and dropped call rate
  • the preset rule stored in the second management unit is: the call drop rate is only related to the CN domain, and The coverage rate is only related to the RAN domain, and the ratio of the delay to the CN domain and the RAN domain is 1:2.
  • the coverage ratio is equal to the coverage rate and the delay in the required information of the received network slice, and the time delay is equal to the time in the required information of the received network slice. 2/3 of the delay, and the call rate information is not included in the demand information of the second sub-network.
  • the second mode is as follows: the second management unit is a RAN-Domain-O, and the second sub-network is a RAN domain.
  • the second management unit may send a negotiation request to the CN-Domain-O.
  • the negotiation request may include information such as demand information of the network slice and allocation suggestions of the second management unit, for example, allocation suggestions including SLA information such as delay and call drop rate.
  • the CN-Domain-O determines a new allocation proposal according to its network operation and returns it to the second management unit.
  • the requirement information of the second sub-network may include at least one of the following: a type of the second sub-network, SLA information of the second sub-network, deployment information of the second sub-network, a KPI of the second sub-network, or The functional characteristics of the two sub-networks.
  • the second management unit determines requirement information of the second network resource that meets the requirement information of the second sub-network, where the demand information of the second network resource is used to select, create, configure, or activate the requirement information that meets the second network resource. Two network resource instances.
  • the demand information of the second network resource may include at least one of the following: a type of the second network resource, descriptor information of the second network resource, instance information of the second network resource, a KPI of the second network resource, or Functional characteristics of the second network resource.
  • the second network resource instance can include at least one of the following: a network function, a network element, a network service, or a transmission resource.
  • the second management unit sends a fourth management request to the fourth management unit, where the fourth management request carries the requirement information of the second network resource, where the fourth management request is used to request the second network resource instance.
  • the fourth management unit may be a RAN-NF-CTRL.
  • the second management unit may also select the second network that already exists in the current network according to the determined requirement information of the second network resource.
  • the resource instance is a second network resource instance that selects the demand information of the second network resource in the existing network.
  • the fourth management unit requests the second network resource instance according to the requirement information of the second network resource.
  • the fourth management unit may request the second network resource instance according to the requirement information of the second network resource.
  • the fourth management unit may select, deploy, configure, or activate the second process by using the following process.
  • Network resource instance First, the fourth management unit determines the demand information of the first network resource instance. Then, the fourth management unit selects, deploys, configures, or activates a second network resource instance that meets the demand information of the second network resource instance.
  • the method shown in FIG. 3 may further include S308.
  • the second management unit allocates an identifier of the second subnetwork.
  • the second management unit allocates the first After the identifier of the second sub-network, the identifier of the second sub-network and the identifier of the first sub-network may be associated, or the identifier of the second sub-network and the identifier of the network slice may be associated.
  • the identifier of the second sub-network may be an identifier of the second sub-network instance.
  • the first management unit after receiving the requirement information of the network slice, acquires the demand information of the second sub-network, and obtains the second sub-network, on the basis of determining the demand information of the first network resource.
  • the demand information of the network is sent to the second management unit; or the first management unit may send the demand information of the network slice to the second management unit, and the second management unit may obtain the demand information of the second sub-network according to the demand information of the network slice. Therefore, the second management unit determines the requirement information of the second network resource and completes the creation of the second network resource instance, and the like, thereby implementing management of the first sub-network and the second sub-network.
  • FIG. 4 is a schematic diagram of communication of a method for managing a network slice according to an embodiment of the present invention.
  • the first management unit is the CN-Domain-O
  • the first sub-network is the CN domain
  • the first management unit is the RAN-Domain-O
  • the first sub-network is the RAN domain.
  • the third management unit may be CN-NF-CTRL
  • the third management unit may be RAN-NF- CTRL.
  • the method includes:
  • S401 and E2E-O receive a network slice request.
  • the network slice request carries the requirement information of the network slice.
  • the requirement information of the network slice refer to the detailed description in FIG. 2, and details are not described herein.
  • the E2E-O forwards the network slice request to the CN-Domain-O.
  • the network slice request may be an example of the first management request in step S201 of FIG. 2. For details, refer to the description of the foregoing step S201.
  • the CN-Domain-O obtains the requirement information of the CN domain according to the network slice request.
  • step S202 of FIG. 2 For the specific implementation process of this step, reference may be made to the specific implementation process of step S202 of FIG. 2 .
  • the CN-Domain-O allocates an identifier of the CN domain or an identifier of the network slice.
  • CN-Domain-O determines CN requirement information required by the CN domain.
  • CN-Domain-O sends the above CN requirement information to the CN-NF-CTRL.
  • the CN-NF-CTRL selects, creates, configures, activates, or requests a network resource instance that satisfies the CN requirement information according to the CN requirement information.
  • steps S406 and S407 describe the process in which the CN-Domain-O requests the network resource instance from the CN-NF-CTRL, which is an optional step; if the network resource instance that meets the CN requirement information already exists in the existing network, Instead of performing S406 and S407, the CN-Domain-O directly selects a network resource instance that already exists in the existing network and satisfies the CN requirement information.
  • the E2E-O forwards the network slice request to the RAN-Domain-O.
  • the network slice request may be an example of the first management request in step S201 of FIG. 2. For details, refer to the description of the foregoing step S201.
  • the RAN-Domain-O acquires the requirement information of the RAN domain according to the network slice request.
  • step S202 of FIG. 2 For the specific implementation process of this step, reference may be made to the specific implementation process of step S202 of FIG. 2 .
  • the RAN-Domain-O allocates an identifier of the RAN domain or an identifier of the network slice.
  • RAN-Domain-O determines RAN requirement information required by the RAN domain.
  • the RAN-Domain-O sends the foregoing RAN requirement information to the RAN-NF-CTRL.
  • the RAN-NF-CTRL selects, creates, configures, activates, or requests a network resource instance that satisfies the RAN requirement information according to the RAN requirement information.
  • steps S412 and S413 describe the process in which the RAN-Domain-O requests the network resource instance from the RAN-NF-CTRL, which is an optional step; if the network resource instance that satisfies the RAN requirement information already exists in the existing network, Instead of performing S412 and S413, the RAN-Domain-O directly selects a network resource instance that already exists in the existing network and satisfies the RAN requirement information.
  • the execution sequence of the steps S402-S407 and the steps S408-S413 is not limited, and the steps S402-S407 may be performed first, and then the steps S408-S413 may be performed; or the steps S408-S413 may be performed first. Steps S402 to S407 are performed again; or steps S402 to S407 and steps S408 to S413 may be performed in parallel.
  • the E2E-O sends the network slice requirement information to the CN domain and the RAN domain respectively, the CN domain determines the CN requirement information, and obtains the CN domain network resource instance, and the RAN domain determines the RAN requirement information and obtains Network resource instance of the RAN domain.
  • FIG. 5 is a schematic diagram of communication of another method for managing a network slice according to an embodiment of the present invention.
  • the first management unit is CN
  • the second management unit is RAN
  • the third management unit is CN-NF-CTRL
  • the fourth management unit is RAN-NF-CTRL
  • the first sub-network is CN.
  • the domain and the second sub-network are RAN domains as an example, and the solution of the embodiment of the present invention is described.
  • the method includes:
  • S501, E2E-O receive a network slice request.
  • the network slice request carries the requirement information of the network slice.
  • the requirement information of the network slice refer to the detailed description in FIG. 2, and details are not described herein.
  • the E2E-O forwards the network slice request to the CN.
  • the network slice request may be an example of the first management request in step S201 of FIG. 2. For details, refer to the description of the foregoing step S201.
  • the CN acquires the requirement information of the CN domain according to the network slice request.
  • step S202 of FIG. 2 For the specific implementation process of this step, reference may be made to the specific implementation process of step S202 of FIG. 2 .
  • the CN allocates an identifier of the CN domain or an identifier of the network slice.
  • the CN determines the CN requirement information required by the CN domain.
  • the CN sends the CN requirement information to the CN-NF-CTRL.
  • CN-NF-CTRL select, create, configure, activate or request according to CN demand information
  • CN demand information An example of a network resource that satisfies CN demand information.
  • the steps S506 and S507 are similar to the steps S406 and S407 in FIG. 4 respectively. For details, refer to the detailed description of steps S406 and S407, and details are not described herein.
  • the CN acquires the requirement information of the RAN domain according to the network slice request.
  • the CN sends the requirement information of the RAN domain to the RAN.
  • steps S508 and S509 describe the process of the CN acquiring the RAN domain requirement information and then sending the information to the RAN, which is an optional step.
  • the CN may not acquire the RAN domain requirement information, but The demand information of the network slice is directly sent to the RAN, and the RAN acquires the demand information of the RAN domain according to the requirement information of the network slice.
  • steps S303 and S304 for a specific implementation process of receiving the requirement information of the network slice by the RAN and acquiring the requirement information of the RAN domain.
  • the RAN determines RAN requirement information required for the requirement information of the RAN domain.
  • the RAN may also assign an identifier of the RAN domain. Further, the RAN may also associate the identifier of the RAN domain with the identifier of the foregoing CN domain, or the RAN may also associate the identifier of the RAN domain with the identifier of the network slice.
  • the RAN requirement information is used to select, create, configure, or activate a network resource instance that satisfies the RAN requirement information.
  • the RAN sends the foregoing RAN requirement information to the RAN-NF-CTRL.
  • the RAN-NF-CTRL selects, creates, configures, activates, or requests a network resource instance that satisfies the RAN requirement information according to the RAN requirement information.
  • the steps S511 and S512 are similar to the steps S412 and S413 in FIG. 4 respectively. For details, refer to the detailed description of steps S412 and S413, and details are not described herein.
  • steps S503-507 and S508-S512 are not limited, and steps S503-507 may be performed first, and then steps S508-S512 may be performed; or steps S508-S512 may be performed first. Steps S503 to 507 are performed again; or steps S503 to 507 and steps S508 to S512 may be performed in parallel.
  • the E2E-O sends the network slice request information to the CN, and the CN may determine the CN domain requirement information according to the network slice requirement information and obtain the network resource instance of the CN domain. Further, the CN may further determine the RAN domain requirement information according to the network slice requirement information, and send the RAN domain requirement information to the RAN, or the CN may further send the network slice requirement information to the RAN, and the RAN according to the network slice.
  • the demand information determines the demand information of the RAN domain, so that the RAN domain can acquire the network resource instance of the RAN domain.
  • each unit for example, the first management unit, the second management unit, the third management unit, the fourth management unit, and the like, in order to implement the above functions, includes hardware structures and/or software modules corresponding to the execution of the respective functions.
  • the embodiments of the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function modules of the first management unit, the second management unit, the third management unit, the fourth management unit, and the like according to the foregoing method example.
  • each function module may be divided according to each function, or may be Two or more functions are integrated in one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 6 shows a possible structural diagram of the first management unit involved in the above embodiment.
  • the first management unit 1000 includes a processing module 1002 and a communication module 1003.
  • the processing module 1002 is configured to perform control management on the actions of the first management unit.
  • the processing module 1002 is configured to support the first management unit to perform processes S201 to S205 and S207 in FIG. 2, and processes S301 to S303 in FIG. Processes S403 through S406 or S409 through S412 in 4, processes S503 through S506, S508, and S509 in FIG. 5, and/or other processes for the techniques described herein.
  • the communication module 1003 is configured to support communication between the first management unit and other network entities, such as communication with the second management unit or the third management unit.
  • the first management unit may further include a storage module 1001 for storing program codes and data of the first management unit.
  • the processing module 1002 may be a processor or a controller, such as a central processing unit (CPU), a general-purpose processor, and a digital signal processor (Digital). Signal Processor (DSP), Application-Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 1003 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and may include one or more interfaces, such as an interface between the first management unit and the second management unit or the third management unit.
  • the storage module 1001 may be a memory.
  • the processing module 1002 is a processor
  • the communication module 1003 is a communication interface
  • the storage module 1001 is a memory
  • the first management unit involved in the embodiment of the present invention may be the first management unit shown in FIG.
  • the first management unit 1010 includes a processor 1012, a communication interface 1013, and a memory 1011.
  • the first management unit 1010 may further include a bus 1014.
  • the communication interface 1013, the processor 1012, and the memory 1011 may be connected to each other through a bus 1014; the bus 1014 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA). Bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 1014 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 7, but it does not mean that there is only one bus or one type of bus.
  • the first management unit shown in FIG. 6 or FIG. 7 above may be CN-Domain-O, RAN-Domain-O or CN in FIG.
  • FIG. 8 shows a possible structural diagram of the second management unit involved in the above embodiment.
  • the second management unit 2000 includes a processing module 2002 and a communication module 2003.
  • the processing module 2002 is configured to control and manage the actions of the second management unit.
  • the processing module 2002 is configured to support the second management unit to perform processes S304 to SS06 and S308 in FIG. 3, processes S510 and S511 in FIG. 5, and / or other processes for the techniques described herein.
  • the communication module 2003 is for supporting communication between the second management unit and other network entities, such as communication with the first management unit or the fourth management unit.
  • the second management unit may further include a storage module 2001 for storing program codes and data of the second management unit.
  • the processing module 2002 can be a processor or a controller, for example, can be a CPU, and is universal.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 2003 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces, such as an interface between the second management unit and the first management unit or the fourth management unit.
  • the storage module 2001 can be a memory.
  • the second management unit involved in the embodiment of the present invention may be the second management unit shown in FIG.
  • the second management unit 2010 includes a processor 2012, a communication interface 2013, and a memory 2011.
  • the second management unit 2010 may further include a bus 2014.
  • the communication interface 2013, the processor 2012, and the memory 2011 may be connected to each other through a bus 2014;
  • the bus 2014 may be a PCI bus or an EISA bus or the like.
  • the bus 2014 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the second management unit shown in FIG. 8 or FIG. 9 above may be a RAN or the like.
  • the embodiment of the present invention further provides the third management unit and the fourth management unit involved in the foregoing embodiment, wherein the third management unit or the fourth management unit may have a similar Structure.
  • the third management unit may have a structure similar to that shown in FIG. 6, including a processing module and a communication module, and further, may further include a storage module.
  • the third management unit may have a structure similar to that shown in FIG. 7, including a processor, a communication interface, and a memory, and further, may further include a bus.
  • the third management unit may be CN-NF-CTRL or RAN-NF-CTRL.
  • the fourth management unit may have a structure similar to that shown in FIG. 6, including a processing module and a communication module, and further, may further include a storage module.
  • the fourth management unit may have a structure similar to that shown in FIG. 7, including a processor, a communication interface, and a memory, and further, may further include a bus.
  • the fourth management unit may be a RAN-NF-CTRL.
  • the embodiment of the present invention does not describe the structure of the foregoing third management unit and the fourth management unit.
  • the structure description of the third management unit or the fourth management unit reference may be made to the above.
  • the structure of the first management unit or the second management unit The structure of the first management unit or the second management unit.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC may be located in the first management unit, the second management unit, the third management unit, or the fourth management unit.
  • the processor and the storage medium may also exist as discrete components in the first management unit, the second management unit, the third management unit, or the fourth management unit.
  • the functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本发明实施例提供一种管理方法、管理单元及系统，该方法包括：第一管理单元接收第一管理请求，第一管理请求携带所述网络切片的需求信息或指示信息，所述指示信息用于获取所述网络切片的需求信息；所述第一管理单元根据所述网络切片的需求信息获取第一子网络的需求信息；所述第一管理单元确定所述第一子网络所需的第一网络资源的需求信息，所述第一网络资源的需求信息用于选择、创建、配置、激活或请求满足第一网络资源的需求信息的第一网络资源实例。本发明实施例的方案中，第一管理单元能够根据网络切片的需求信息获取第一子网络的需求信息，并获取第一网络资源实例，提升了网络切片部署效率。

Description

一种管理方法、管理单元及系统 技术领域
本发明实施例涉及通信领域，尤其涉及一种管理方法、管理单元及系统。
背景技术
随着网络需求的不断提升，电信运营商需要提供更多的技术来建立与不同客户的合作，包括共享基础设施、开放特定网络功能、将合作伙伴强大丰富的软件能力集成到下一代网络系统中等。其中，网络切片是下一代网络系统满足不同行业、不同用户对网络具有特殊需求时的重要技术手段。网络切片是保证承载业务能达成服务水平协议(Service level agreement，SLA)要求的通信资源，这些资源可以按不同需求进行物理隔离，也可以进行逻辑隔离，可以认为一个网络切片是完成某个(些)业务所需的网络功能及资源的组合，是一个完整的逻辑网络。在下一代网络系统中，不同的租户可以通过租用电信运营商的网络来部署自己的业务，例如，电力公司可以租用电信运营商的网络来部署其抄表业务，电信运营商通过将自己的网络划分为不同的网络切片来提供给不同的租户使用。
现有技术中，在部署网络切片的过程中，网管的业务设计人员在接收到业务请求之后，需要手动分解业务请求，并将其转化为网络资源请求，分别发送给核心网的网络设计人员和无线接入网的网络设计人员，由核心网和无线接入网的网络设计人员分别部署网络设备，然后通过网元管理单元来管理相应的网络设备。
但是，现有技术需要手工进行网络切片部署，导致网络切片部署的效率低下。
发明内容
本发明实施例提供一种管理方法、管理单元及系统，以期解决现有技术中网络切片的部署效率低下的问题。
一方面，本发明实施例提供一种管理方法，该方法包括：第一管理单元接收第一管理请求，该第一管理请求中携带网络切片的需求信息或指示信息，该指示信息用于获取网络切片的需求信息；第一管理单元根据网络切片的需求信息获取第一子网络的需求信息，其中，上述网络切片包括该第一子网络；然后，第一管理单元确定第一子网络所需的第一网络资源的需求信息，该第一网络资源的需求信息用于选择、创建、配置、激活或请求满足第一网络资源的需求信息的第一网络资源实例。
本发明实施例中，第一管理单元在接收携带网络切片的需求信息或指示信息的第一管理请求后，能够获取第一子网络的需求信息，并根据第一子网络的需求信息确定第一子网络所需的第一网络资源的需求信息，进而可以根据第一网络资源的需求信息选择、创建、配置、激活或请求第一网络资源实例，从而能够实现根据网络切片的需求信息自动进行网络切片的部署，提升了网络切片的部署效率。
其中，上述第一管理单元可以是核心网域编排单元、无线接入网域编排单元或核心网网元等具有网络切片的管理功能的实体。
在一个可能的设计中，第一管理单元根据网络切片的需求信息获取第一子网络的需求信息之后，还可以分配第一子网络的标识或网络切片的标识。
在一个可能的设计中，第一管理单元还可以向第三管理单元发送第三管理请求，该第三管理请求携带第一网络资源的需求信息，第三管理请求用于请求第一网络资源实例。
或者，第一管理单元还可以选择现网中已经存在的所述第一网络资源实例。
在一个可能的设计中，网络切片中还包括第二子网络，第一管理单元还可以向第二管理单元发送第二管理请求，第二管理请求携带网络切片的需求信息，以使得第二管理单元根据网络切片的需求信息获取第二子网络的需求信息。
或者，第一管理单元还可以根据网络切片的需求信息获取第二子网络的需求信息；并向第二管理单元发送第二管理请求，第二管理请求携带第二子网络的需求信息。
在一个可能的设计中，第二管理请求中还可以携带第一子网络的标识或 网络切片的标识。
在一个可能的设计中，第一管理单元分配第一子网络的标识，第一管理请求还携带网络切片的标识，在这种情况下，第一管理单元还可以关联第一子网络的标识与网络切片的标识。
另一方面，本发明实施例提供另一种网络切片的管理方法，该方法包括：第二管理单元从第一管理单元接收第二管理请求，该第二管理请求中携带第二子网络的需求信息；或者，第二管理单元从第一管理单元接收第二管理请求，该第二管理请求中携带网络切片的需求信息，进而，第二管理单元根据网络切片的需求信息获取第二子网络的需求信息；然后，第二管理单元确定满足第二子网络的需求信息的第二网络资源的需求信息，该第二网络资源的需求信息用于选择、创建、配置或激活满足第二网络资源的需求信息的第二网络资源实例。
本发明实施例中，第二管理单元在获取到第二子网络的需求信息后，能够确定第二网络资源的需求信息并获取第二网络资源实例，从而能够实现对第二子网络的管理。
其中，上述第二管理单元可以是接入网网元或者网络功能等实体。
在一个可能的设计中，第二管理单元还可以向第四管理单元发送第四管理请求，该第四管理请求携带第二网络资源的需求信息，第四管理请求用于请求所述第二网络资源实例；或者，第二管理单元还可以选择现网中已经存在的所述第二网络资源实例。
在一个可能的设计中，第二管理单元还可以分配所述第二子网络的标识。
在一个可能的设计中，第二管理请求还携带第一管理单元分配的第一子网络的标识或网络切片的标识，在这种情况下，第二管理单元还可以关联第二子网络的标识与第一子网络的标识；或者，第二管理单元还可以关联第二子网络的标识与网络切片的标识。
上述两个方面所提供的网络切片的管理方法中，所涉及的第二子网络的需求信息可以包括以下至少一项：第二子网络的类型、第二子网络的SLA信息、第二子网络的部署信息、第二子网络的KPI或第二子网络的功能特征。
所涉及的网络切片的需求信息可以包括以下至少一种：网络切片的类型、网络切片的服务水平协议SLA信息、网络切片的部署信息、网络切片的 关键性能指标KPI、网络切片的网络特征、网络切片的用户信息或网络切片提供的业务信息。
所涉及的第一子网络的需求信息可以包括以下至少一项：第一子网络的类型、第一子网络的SLA信息、第一子网络的部署信息、第一子网络的KPI或第一子网络的功能特征。
所涉及的第一网络资源的需求信息可以包括以下至少一种：第一网络资源的类型、第一网络资源的描述符信息、第一网络资源的实例信息、第一网络资源的KPI或第一网络资源的功能特征。
所涉及的第一网络资源实例可以包括以下至少一种：网络功能、网元、网络服务或传输资源。
所涉及的第二网络资源的需求信息可以包括以下至少一种：第二网络资源的类型、第二网络资源的描述符信息、第二网络资源的实例信息、第二网络资源的KPI或第二网络资源的功能特征。
所涉及的第二网络资源实例可以包括以下至少一种：网络功能、网元、网络服务或传输资源。
又一方面，本发明实施例提供一种第一管理单元，该第一管理单元具有实现上述方法设计中第一管理单元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，第一管理单元包括处理器，所述处理器被配置为支持第一管理单元执行上述方法中相应的功能。进一步的，第一管理单元还可以包括通信接口，通信接口用于支持第一管理单元与第二管理单元、第三管理单元或其他单元的通信。进一步的，第一管理单元还可以包括存储器，所述存储器用于与处理器耦合，其保存第一管理单元必要的程序指令和数据。
又一方面，本发明实施例提供一种第二管理单元，该第二管理单元具有实现上述方法设计中第二管理单元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，第二管理单元包括处理器，所述处理器被配置为支持第二管理单元执行上述方法中相应的功能。进一步的，第二管理单元还 可以包括通信接口，所述通信接口用于支持第二管理单元与第一管理单元、第四管理单元或其他单元的通信。进一步的，第二管理单元还可以包括存储器，所述存储器用于与处理器耦合，其保存第二管理单元必要的程序指令和数据。
再一方面，本发明实施例提供一种通信系统，该系统包括上述方面所述的第一管理单元；或者，该系统包括上述方面所述的第一管理单元和第二管理单元。
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述用于第一管理单元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述用于第二管理单元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供了一种计算机程序产品，其包含指令，当所述程序被计算机所执行时，该指令使得计算机执行上述方法设计中第一管理单元所执行的功能。
再一方面，本发明实施例提供了一种计算机程序产品，其包含指令，当所述程序被计算机所执行时，该指令使得计算机执行上述方法设计中第二管理单元所执行的功能。
相较于现有技术，本发明实施例的方案中，第一管理单元在接收到携带网络切片的需求信息或指示信息的第一管理请求后，能够首先确定第一子网络所需的第一网络资源的需求信息，进而，可以根据第一网络资源的需求信息选择、创建、配置、激活或者请求第一网络资源实例，从而能够实现根据网络切片的需求信息自动进行网络切片的部署，提升了网络切片的部署效率。
附图说明
图1为本发明实施例提供的一种可能的网络架构的示意图；
图2为本发明实施例提供的一种网络切片的管理方法的通信示意图；
图3为本发明实施例提供的另一种网络切片的管理方法的通信示意图；
图4为本发明实施例提供的又一种网络切片的管理方法的通信示例图；
图5为本发明实施例提供的再一种网络切片的管理方法的通信示例图；
图6为本发明实施例提供的一种第一管理单元的结构示意图；
图7为本发明实施例提供的另一种第一管理单元的结构示意图；
图8为本发明实施例提供的一种第二管理单元的结构示意图；
图9为本发明实施例提供的另一种第二管理单元的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对于本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
应当理解，本文中使用的术语“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
下面首先结合图1对本发明实施例可能适用的网络架构进行介绍。
图1为本发明实施例提供网络切片的管理方法的一种可能的系统架构图，如图1所示，该方法对应的系统涉及运营支撑系统以及具体的通信网络，包括：
(1)运营支撑系统(Operation Support System，OSS)。
(2)端到端编排(E2E Orchestrator，E2E-O)单元：E2E-O单元也可以称为端到端管理单元或端到端编排和管理单元，其可以具备以下部分或全部功能：
端到端网络切片的管理(例如，网络切片的生命周期管理、网络切片模板的管理、网络切片的故障管理、网络切片的性能管理和网络切片的配置管理)；端到端业务的管理(例如，业务的生命周期管理、业务模板的管理、业务的故障管理、业务的性能管理和业务的配置管理)，端到端网络切片和 子网络切片以及网络功能的映射；不同子域(例如接入网域，核心网域，传输域)提供的网络资源的协调；对各子域提供的子网络切片和网络功能的统一编排，以使得不同子域提供的子网络切片或者网络功能可以满足目标业务的需求(例如，SLA的要求，关键性能指标(Key Performance Indicator，KPI)的要求以及服务质量(Quality of Service，QoS)的要求)。为描述方便，下文中，某一单元可以仅用其英文缩写进行描述，例如，E2E-O单元也可以用E2E-O表示，其他单元类似，后续不再赘述。
E2E-O可以由端到端的业务编排(E2E Service Orchestrator，E2E-SO)单元和端到端的网络编排(E2E Network Orchestrator，E2E-NO)单元组成，也可以只由E2E-SO单元和E2E NO单元的其中一个组成。
需要说明的是，上述E2E-O的功能也可以由跨域编排(Cross-Domain Orchestrator，CD-O)单元、业务编排(Service Orchestrator，SO)单元、网络编排(Network Orchestrator，NO)单元或网络管理(Network Manager，NM)单元等实体完成。本发明实施例以下都以E2E-O为例进行说明，但是，需要理解的是，这不应作为对本发明实施例的限制。
(3)核心网域编排(Core Network Domain Orchestrator，CN-Domain-O)单元：CN-Domain-O单元也可以称为核心网域管理和编排单元，其可以具备以下部分或全部功能：
核心网域内网络切片的管理(包括网络切片生命周期管理(创建、更新、删除)、网络切片故障管理、网络切片性能管理、网络切片配置管理等)；核心网域内业务的管理(包括业务生命周期管理、业务故障管理、业务性能管理、业务配置管理等)；核心网域内的网络资源的协调，用于统一编排。
CN-Domain-O可以由核心网域的业务编排(Core Network Domain Service Orchestrator，CN-Domain-SO)单元和核心网域的网络编排(Core Network Domain Network Orchestrator，CN-Domain-NO)单元组成，也可以只由CN-Domain-SO单元和CN-Domain-NO单元的其中一个组成。
需要说明的是，上述CN-Domain-O的功能也可以由SO单元、NO单元、NM、网络控制单元或网络功能虚拟化编排单元等实体完成。本发明实施例以下都以CN-Domain-O为例进行说明，但是，需要理解的是，这不应作为对本发明实施例的限制。
(4)无线接入网域编排(Radio Access Network Domain Orchestrator，RAN-Domain-O)单元：RAN-Domain-O单元也可以称为无线接入网与编排和管理单元，其可以具备以下部分或全部功能：
接入网域内网络切片的管理(包括网络切片生命周期管理(创建、更新、删除)、网络切片故障管理、网络切片性能管理、网络切片配置管理等)；接入网域内业务的管理(包括业务生命周期管理、业务故障管理、业务性能管理、业务配置管理等)；接入网域内的网络资源的协调，用于统一编排。
RAN-Domain-O可以由无线接入网域的业务编排(Radio Access Network Domain Service Orchestrator，RAN-Domain-SO)单元和无线接入网域的网络编排(Radio Access Network Domain Network Orchestrator，RAN-Domain-NO)单元组成，也可以只由RAN-Domain-SO单元和RAN-Domain-NO单元的其中一个组成。
需要说明的是，上述RAN-Domain-O的功能也可以由SO单元、NO单元、NM、网络控制单元、或网络功能虚拟化编排单元等实体完成。本发明实施例以下都以RAN-Domain-O为例进行说明，但是，需要理解的是，这不应作为对本发明实施例的限制。
(5)核心网网络功能控制(CN Network Function Controller，CN-NF-CTRL)单元：包括核心网域内的网络功能管理(Network Function Manager，NF-M)单元和/或虚拟网络功能管理(Virtualized Network Function Manager，VNFM)单元，用于核心网域内的网络功能的生命周期管理、配置管理、故障管理、性能管理等。
(6)无线接入网网络功能控制(RAN Network Function Controller，RAN-NF-CTRL)单元：包括接入网域内的NF-M单元和/或VNFM单元，用于接入网域内的网络功能的生命周期管理、配置管理、故障管理、性能管理等。
(7)CN：核心网网元或者网络功能，可以指核心网控制面的某个或多个网络功能，或者核心网网络功能的集中控制网络功能单元。
(8)RAN：接入网网元或者网络功能，可以指接入网控制面的某个或多个网络功能，或者接入网网络功能的集中控制网络功能单元。
其中，E2E-O，CN-Domain-O，RAN-Domain-O与OSS的关系可以为以 下任意一种情形：第一种情形：E2E-O位于OSS内，CN-Domain-O和RAN-Domain-O不位于OSS内；第二种情形：E2E-O、CN-Domain-O和RAN-Domain-O都不位于OSS内；第三种情形：E2E-O、CN-Domain-O和RAN-Domain-O都位于OSS内。
另外，CN-NF-CTRL和RAN-NF-CTRL可以位于OSS内，也可以不位于OSS内。
图1所示的网络架构中，E2E SO分别与CN-Domain-O和RAN-Domain-O之间具有接口，并通过CN-Domain-O依次连接到CN-NF-CTRL和CN，以及通过RAN-Domain-O依次连接到RAN-NF-CTRL和RAN。其中，CN和RAN之间可以具有接口，也可以不具有接口。
下面将基于上面所述的本发明实施例涉及的共性方面，对本发明实施例进一步详细说明。
下文以图1所示的网络架构为例对本发明实施例的方案进行说明，但是，需要说明的是，本发明实施例的方案也可以应用于其他的系统。
现有方案中，在部署网络切片时，网管的业务设计人员在接收到业务请求之后，需要手动分解业务请求，并将其转化为网络资源请求，分别发送给核心网的网络设计人员和无线接入网的网络设计人员，由核心网和无线接入网的网络设计人员分别部署网络设备，然后通过网元管理单元来管理相应的网络设备。这种人工部署网络切片的方式效率低下。为此，本发明实施例提供一种管理方法，以及基于这个方法的管理单元和系统，来实现网络切片的自动化部署，以提高网络切片的部署效率。
下面结合图2和图3，对本发明实施例提供的方案进行说明。
图2为本发明实施例提供的一种网络切片的管理方法的通信示意图，如图2所示，该方法包括：S201-S204，其中，S203为可选的部分。
S201、第一管理单元接收第一管理请求。
其中，上述第一管理请求携带网络切片的需求信息或指示信息，该指示信息用于获取网络切片的需求信息。
第一管理单元可以是图1中的CN-Domain-O、RAN-Domain-O或者CN。
在一个示例中，E2E-O可以向第一管理单元发送第一管理请求；或者，用户可以通过系统提供的可操作界面向第一管理单元发送第一管理请求；或 者，BSS可以向第一管理单元发送第一管理请求。
在一个示例中，上述网络切片的需求信息可以包括以下至少一种：网络切片支持的业务类型、网络切片的类型、网络切片的SLA信息、网络切片的部署信息、网络切片的KPI、网络切片的网络特征、网络切片的用户信息或网络切片提供的业务信息。其中，上述SLA信息可以包括以下至少一种：时延、成功率、带宽、覆盖率、话务模型等；上述KPI可以包括：最大时延、或最大带宽等。
S202、第一管理单元根据网络切片的需求信息获取第一子网络的需求信息，其中，网络切片包括该第一子网络。
在一个示例中，第一管理单元可以按照预设规则来获取第一子网络的需求信息，或者，第一管理单元也可以通过与其他管理单元进行协商来确定第一子网络的需求信息。下面示例性地说明获取第一子网络的需求信息的不同方式。
第一种方式：在这种方式中，第一管理单元中已经预先存储了上述预设规则。假设第一管理单元为CN-Domain-O，第一子网络为CN域，第一管理单元所接收的网络切片的需求信息中包括时延、覆盖率、掉话率这几种SLA信息，而第一管理单元中所存储的预设规则为：掉话率仅与CN域相关、覆盖率仅与RAN域相关、时延在CN域和RAN域的比例为1:2。则第一管理单元所确定出的第一子网络的需求信息中，掉话率等于所接收到的网络切片的需求信息中的掉话率、时延等于所接收到的网络切片的需求信息中的时延的1/3，并且，第一子网络的需求信息中不包括覆盖率信息。
第二种方式：假设第一管理单元为CN-Domain-O，当第一管理单元接收到网络切片的需求信息后，可以向RAN-Domain-O发送协商请求，协商请求中可以包括网络切片的需求信息以及第一管理单元的分配建议等信息，例如包括时延、掉话率等SLA信息的分配建议。RAN-Domain-O接收到协商请求之后，根据自身的网络运行情况确定出新的分配建议，并返回给第一管理单元。在该步骤中可能需要经过多次协商，最终达成协商一致结果。
在一个示例中，第一子网络的需求信息可以包括以下至少一项：第一子网络的类型、第一子网络的SLA信息、第一子网络的部署信息、第一子网络的KPI或第一子网络的功能特征。
需要说明的是，上述第一子网络可以是子网络切片。
S203、第一管理单元分配第一子网络的标识或网络切片的标识。
在一个示例中，网络切片的标识可以包括以下至少一种：共用陆地移动网(Public Land Mobile Network，PLMN)标识、Tenant标识、Slice类型、Service类型或Slice标识等信息。
在一个示例中，第一管理单元所接收的第一管理请求中携带网络切片的标识，第一管理单元还可以关联第一子网络的标识以及网络切片的标识。
需要说明的是，上述第一子网络的标识可以是第一子网络实例的标识，上述网络切片的标识可以是网络切片实例的标识。
S204、第一管理单元确定第一子网络所需的第一网络资源的需求信息。
其中，第一网络资源的需求信息用于选择、创建、配置、激活或请求满足第一网络资源的需求信息的第一网络资源实例。
在一个示例中，第一管理单元可以根据预设算法和/或网络切片描述符来确定第一子网络所需的第一网络资源的需求信息。下面示例性的说明确定第一网络资源的需求信息的不同方式。
第一种方式：第一管理单元可以预先获取上述预设算法，当接收到网络切片的需求信息后，可以通过执行该预设算法，将前述获取的第一子网络的需求信息作为上述预设算法的输入，则上述预设算法可以输出对应的第一网络资源的需求信息。或者，第一管理单元也可以将网络切片的需求信息，例如SLA信息作为上述预设算法的输入，则上述预设算法可以输出对应的第一网络资源的需求信息。
第二种方式：如果第一管理单元所接收的第一管理请求中携带网络切片的指示信息，则第一管理单元根据该网络切片的指示信息确定网络切片的描述符信息。网络切片的描述符可以是网络切片模板、网络切片蓝图等，第一管理单元根据网络切片的描述符可以确定出网络切片的需求信息，再根据网络切片的需求信息确定第一网络资源的需求信息。或者，第一管理单元也可以根据前述所获取到的第一子网络的需求信息确定子网络描述符，可选地，子网络描述符可以包含在网络切片描述符中。进而，第一管理单元根据子网络描述符确定第一网络资源的需求信息。
在一个示例中，第一网络资源的需求信息可以包括以下至少一种：第一 网络资源的类型、第一网络资源的描述符信息、第一网络资源的实例信息、第一网络资源的KPI或第一网络资源的功能特征。
在一个示例中，第一网络资源可以包括以下至少一种：网络功能、网元、网络服务或传输资源。
本发明实施例中，第一管理单元在接收到携带网络切片的需求信息或指示信息后，根据这些信息获取第一子网络的需求信息，并根据第一子网络的需求信息确定第一子网络所需的第一网络资源的需求信息，进而可以根据第一网络资源的需求信息选择、创建、配置、激活或请求第一网络资源实例，从而实现了根据网络切片需求自动进行网络切片部署，从而极大地提升了网络切片部署的效率。
可选地，图2所示的方法还可以包括下面的步骤S205～S206；或者，图2所示的方法还可以包括下面的步骤S207。
S205、第一管理单元向第三管理单元发送第三管理请求。
其中，第三管理请求携带上述第一网络资源的需求信息，第三管理请求用于请求上述第一网络资源实例。
第三管理单元可以是CN-NF-CTRL或RAN-NF-CTRL。具体地，当第一管理单元为CN-Domain-O或CN时，第三管理单元可以是CN-NF-CTRL；或者，当第一管理单元为RAN-Domain-O时，第三管理单元可以是RAN-NF-CTRL。
S206、第三管理单元根据第三管理请求选择、创建、配置、激活或请求满足第一网络资源的需求信息的第一网络资源实例。
在一个示例中，当第三管理请求所携带的第一网络资源的需求信息不包括第一网络资源的实例信息时，第三管理单元具体可以通过下述过程来选择、部署、配置或激活第一网络资源实例：首先，第三管理单元确定第一网络资源实例的需求信息；然后，第三管理单元选择、部署、配置或激活符合第一网络资源实例的需求信息的第一网络资源实例。
本发明实施例中，第一管理单元确定出第一子网络所需的第一网络资源的需求信息后，可以向第三管理单元请求满足第一网络资源的需求信息的第一网络资源实例，从而提升网络切片的部署效率。
S207、第一管理单元选择现网中已经存在的第一网络资源实例。
具体地，第一管理单元在确定出第一子网络所需的第一网络资源的需求后，判断现网中是否存在满足第一网络资源的需求信息的第一网络资源实例，如果存在，则第一管理单元直接选择现网中已经存在的满足第一网络资源的需求信息的第一网络资源实例。
本发明实施例中，第一管理单元确定出第一子网络所需的第一网络资源的需求信息后，如果现网中存在满足第一网络资源的需求信息的第一网络资源实例，则第一管理单元可以直接选择现网中已经存在的第一网络资源实例，而不再需要向第三管理单元请求第一网络资源实例，进一步提升了网络切片的部署效率。
本发明实施例的方案，在执行上述图2所示方法的基础上，还可以执行下面图3所示的方法。图3为本发明实施例提供的另一种网络切片的管理方法的通信示意图，如图3所示，该方法可以包括S301、S302和S305～S307；或者，该方法可以包括S303～S307。
S301、第一管理单元根据网络切片的需求信息获取第二子网络的需求信息。
其中，上述第二子网络属于上述网络切片，即上述网络切片还包括上述第二子网络。
在一个示例中，第一管理单元可以按照预设规则来获取第二子网络的需求信息，或者，第一管理单元也可以通过与其他管理单元进行协商来确定第二子网络的需求信息。下面示例性的说明获取第二子网络的需求信息的不同方式。
第一种方式：在这种方式中，第一管理单元中已经预先存储了上述预设规则。假设第一管理单元为CN-Domain-O，第二子网络为RAN域，第一管理单元所接收的网络切片的需求信息中包括时延、覆盖率、掉话率这几种SLA信息，而第一管理单元中所存储的预设规则为：掉话率仅与CN域相关、覆盖率仅与RAN域相关、时延在CN域和RAN域的比例为1:2。则第一管理单元所确定出的第二子网络的需求信息中，覆盖率等于所接收到的网络切片的需求信息中的覆盖率、时延等于所接收到的网络切片的需求信息中的时延的2/3，并且，第二子网络的需求信息中不包括掉话率信息。
第二种方式：假设第一管理单元为CN-Domain-O，当第一管理单元接收 到网络切片的需求信息后，可以向RAN-Domain-O发送协商请求，协商请求中可以包括网络切片的需求信息以及第一管理单元对于RAN-Domain-O的需求分配建议等信息，例如包括时延、掉话率等SLA信息的分配建议。RAN-Domain-O接收到协商请求之后，根据自身的网络运行情况确定出新的分配建议，并返回给第一管理单元。其中，在该步骤中可能需要经过多次协商最终达成协商结果。
S302、第一管理单元向第二管理单元发送第二管理请求，该第二管理请求携带第二子网络的需求信息。
第二管理单元可以是RAN或RAN-Domain-O。具体地，当第一管理单元为CN时，第二管理单元可以是RAN；或者，当第一管理单元为CN-Domain-O时，第二管理单元可以是RAN-Domain-O。
在一个示例中，第二管理请求中还可以携带第一子网络的标识或网络切片的标识。
在一个示例中，第二子网络的需求信息可以包括以下至少一项：第二子网络的类型、第二子网络的SLA信息、第二子网络的部署信息、第二子网络的KPI或第二子网络的功能特征。
S303、第一管理单元向第二管理单元发送第二管理请求，该第二管理请求携带网络切片的需求信息。
在一个示例中，第二管理请求中还可以携带第一子网络的标识或网络切片的标识。
S304、第二管理单元根据网络切片的需求信息获取第二子网络的需求信息。
在一个示例中，第二管理单元可以按照预设规则来获取第二子网络的需求信息，或者，第二管理单元也可以通过与其他管理单元进行协商来确定第二子网络的需求信息。下面示例性的说明获取第二子网络的需求信息的不同方式。
第一种方式：在这种方式中，第二管理单元中已经预先存储了上述预设规则。假设第二管理单元为RAN-Domain-O，第二子网络为RAN域，第二管理单元所接收的网络切片的需求信息中包括时延、覆盖率、掉话率这几种SLA信息，而第二管理单元中所存储的预设规则为：掉话率仅与CN域相关、覆 盖率仅与RAN域相关、时延在CN域和RAN域的比例为1:2。则第二管理单元所确定出的第二子网络的需求信息中，覆盖率等于所接收到的网络切片的需求信息中的覆盖率、时延等于所接收到的网络切片的需求信息中的时延的2/3，并且，第二子网络的需求信息中不包括掉话率信息。
第二种方式：假设第二管理单元为RAN-Domain-O，第二子网络为RAN域，当第二管理单元接收到网络切片的需求信息后，可以向CN-Domain-O发送协商请求，协商请求中可以包括网络切片的需求信息以及第二管理单元的分配建议等信息，例如包括时延、掉话率等SLA信息的分配建议。CN-Domain-O接收到协商请求之后，根据自身的网络运行情况确定出新的分配建议，并返回给第二管理单元。
在一个示例中，第二子网络的需求信息可以包括以下至少一项：第二子网络的类型、第二子网络的SLA信息、第二子网络的部署信息、第二子网络的KPI或第二子网络的功能特征。
S305、第二管理单元确定满足第二子网络的需求信息的第二网络资源的需求信息，第二网络资源的需求信息用于选择、创建、配置或激活满足第二网络资源的需求信息的第二网络资源实例。
在一个示例中，第二网络资源的需求信息可以包括以下至少一种：第二网络资源的类型、第二网络资源的描述符信息、第二网络资源的实例信息、第二网络资源的KPI或第二网络资源的功能特征。
在一个示例中，第二网络资源实例可以包括以下至少一种：网络功能、网元、网络服务或传输资源。
S306、第二管理单元向第四管理单元发送第四管理请求，第四管理请求携带第二网络资源的需求信息，第四管理请求用于请求第二网络资源实例。
其中，当第三管理单元为RAN时，第四管理单元可以是RAN-NF-CTRL。
需要说明的是，第二管理单元除了可以通过第四管理单元来请求第二网络资源实例之外，也可以根据所确定的第二网络资源的需求信息，选择现网中已经存在的第二网络资源实例，即选择现网中满足第二网络资源的需求信息的第二网络资源实例。
S307、第四管理单元根据第二网络资源的需求信息请求第二网络资源实例。
当第四管理单元接收到管理请求之后，可以根据第二网络资源的需求信息来请求第二网络资源实例。
在一个示例中，当第四管理请求所携带的第二网络资源的需求信息不包括第二网络资源的实例信息时，第四管理单元可以通过下述过程来选择、部署、配置或激活第二网络资源实例：首先，第四管理单元确定第一网络资源实例的需求信息。然后，第四管理单元选择、部署、配置或激活符合第二网络资源实例的需求信息的第二网络资源实例。
可选的，图3所示的方法还可以包括S308。
S308、第二管理单元分配第二子网络的标识。
在一个示例中，如果前述步骤S302或S303中第一管理单元向第二管理单元发送的第二管理请求中携带第一子网络的标识或网络切片的标识，则第二管理单元在分配完第二子网络的标识之后，还可以关联第二子网络的标识与第一子网络的标识，或者，关联第二子网络的标识与网络切片的标识。
需要说明的是，上述第二子网络的标识可以是第二子网络实例的标识。
本发明实施例中，第一管理单元在接收到网络切片的需求信息后，在确定出第一网络资源的需求信息的基础上，还会获取第二子网络的需求信息，并将第二子网络的需求信息发送给第二管理单元；或者，第一管理单元可以将网络切片的需求信息发送给第二管理单元，第二管理单元可以根据网络切片的需求信息获取第二子网络的需求信息，从而第二管理单元在此基础上确定第二网络资源的需求信息并完成第二网络资源实例的创建等，从而实现了第一子网络和第二子网络的管理。
下面结合图4和图5，对本发明实施例提供的方案进行详细说明。图4和图5所示方法中，与图2或图3相同或相似的内容，可以参考图2或图3中的详细描述，后续不再赘述。
图4为本发明实施例提供的又一种网络切片的管理方法的通信示意图。图4所示方法中，以第一管理单元为CN-Domain-O，第一子网络为CN域为例，或者，以第一管理单元为RAN-Domain-O，第一子网络为RAN域为例，对本发明实施例的方案进行说明。其中，当第一管理单元为CN-Domain-O时，第三管理单元可以为CN-NF-CTRL；当第一管理单元为RAN-Domain-O时，第三管理单元可以为RAN-NF-CTRL。如图4所示，该方法包括：
S401、E2E-O接收网络切片请求。
其中，网络切片请求携带网络切片的需求信息。有关网络切片的需求信息的介绍可以参考图2中的详细描述，此处不作赘述。
S402、E2E-O将网络切片请求转发到CN-Domain-O。
其中，该网络切片请求可以是图2的步骤S201中的第一管理请求一个示例，具体内容可以参见前述步骤S201的描述。
S403、CN-Domain-O根据网络切片请求获取CN域的需求信息。
本步骤的具体实施过程可以参照图2的步骤S202的具体实施过程。
S404、CN-Domain-O分配CN域的标识或网络切片的标识。
S405、CN-Domain-O确定CN域所需的CN需求信息。
本步骤的具体实施过程可以参照图2的步骤S204的具体实施过程。
S406、CN-Domain-O向CN-NF-CTRL发送上述CN需求信息。
S407、CN-NF-CTRL根据CN需求信息选择、创建、配置、激活或请求满足CN需求信息的网络资源实例。
需要说明的是，上述步骤S406和S407描述了CN-Domain-O向CN-NF-CTRL请求网络资源实例的过程，为可选的步骤；若现网中已经存在满足CN需求信息的网络资源实例，可以不执行S406和S407，而是由CN-Domain-O直接选择现网中已经存在的满足CN需求信息的网络资源实例。
S408、E2E-O将网络切片请求转发到RAN-Domain-O。
其中，该网络切片请求可以是图2的步骤S201中的第一管理请求一个示例，具体内容可以参见前述步骤S201的描述。
S409、RAN-Domain-O根据网络切片请求获取RAN域的需求信息。
本步骤的具体实施过程可以参照图2的步骤S202的具体实施过程。
S410、RAN-Domain-O分配RAN域的标识或网络切片的标识。
S411、RAN-Domain-O确定RAN域所需的RAN需求信息。
本步骤的具体实施过程可以参照图2的步骤S204的具体实施过程。
S412、RAN-Domain-O向RAN-NF-CTRL发送上述RAN需求信息。
S413、RAN-NF-CTRL根据RAN需求信息选择、创建、配置、激活或请求满足RAN需求信息的网络资源实例。
需要说明的是，上述步骤S412和S413描述了RAN-Domain-O向RAN-NF-CTRL请求网络资源实例的过程，为可选的步骤；若现网中已经存在满足RAN需求信息的网络资源实例，可以不执行S412和S413，而是由RAN-Domain-O直接选择现网中已经存在的满足RAN需求信息的网络资源实例。
需要说明的是，本发明实施例不限定上述步骤S402～S407与步骤S408～S413的执行顺序，可以先执行步骤S402～S407，再执行步骤S408～S413；或者，也可以先执行步骤S408～S413，再执行步骤S402～S407；或者，还可以并行执行步骤S402～S407和步骤S408～S413。
本发明实施例中，E2E-O将网络切片的需求信息分别发送到CN域以及RAN域，由CN域确定CN需求信息并获取CN域的网络资源实例，以及由RAN域确定RAN需求信息并获取RAN域的网络资源实例。
图5为本发明实施例提供的再一种网络切片的管理方法的通信示意图。图5所示方法中，以第一管理单元为CN，第二管理单元为RAN，第三管理单元为CN-NF-CTRL，第四管理单元为RAN-NF-CTRL，第一子网络为CN域，第二子网络为RAN域为例，对本发明实施例的方案进行说明。如图5所示，该方法包括：
S501、E2E-O接收网络切片请求。
其中，网络切片请求携带网络切片的需求信息。有关网络切片的需求信息的介绍可以参考图2中的详细描述，此处不作赘述。
S502、E2E-O将网络切片请求转发到CN。
其中，该网络切片请求可以是图2的步骤S201中的第一管理请求一个示例，具体内容可以参见前述步骤S201的描述。
S503、CN根据网络切片请求获取CN域的需求信息。
本步骤的具体实施过程可以参照图2的步骤S202的具体实施过程。
S504、CN分配CN域的标识或网络切片的标识。
S505、CN确定CN域所需的CN需求信息。
本步骤的具体实施过程可以参照图2的步骤S204的具体实施过程。
S506、CN向CN-NF-CTRL发送上述CN需求信息。
S507、CN-NF-CTRL根据CN需求信息选择、创建、配置、激活或请求 满足CN需求信息的网络资源实例。
其中，步骤S506和S507分别与图4中的步骤S406和S407类似，具体实施过程可以参考步骤S406和S407的详细描述，此处不作赘述。
S508、CN根据网络切片请求获取RAN域的需求信息。
本步骤的具体实施过程可以参照图3的步骤S301的具体实施过程。
S509、CN向RAN发送上述RAN域的需求信息。
需要说明的是，上述步骤S508和S509描述了CN获取RAN域的需求信息后发送给RAN的过程，为可选的步骤；在实施过程中，CN也可以不获取RAN域的需求信息，而是直接将网络切片的需求信息发送给RAN，由RAN根据网络切片的需求信息获取RAN域的需求信息。由RAN接收网络切片的需求信息并获取RAN域的需求信息的具体实施过程可以参照图3中的步骤S303和S304的具体实施过程。
S510、RAN确定上述RAN域的需求信息所需的RAN需求信息。
可选的，RAN还可以分配RAN域的标识。进一步的，RAN还可以关联RAN域的标识和上述CN域的标识，或者，RAN还可以关联RAN域的标识和上述网络切片的标识。
其中，RAN需求信息用于选择、创建、配置或激活满足RAN需求信息的网络资源实例。
本步骤的具体实施过程可以参照图3的步骤S305的具体实施过程。
S511、RAN向RAN-NF-CTRL发送上述RAN需求信息。
S512、RAN-NF-CTRL根据RAN需求信息选择、创建、配置、激活或请求满足RAN需求信息的网络资源实例。
其中，步骤S511和S512分别与图4中的步骤S412和S413类似，具体实施过程可以参考步骤S412和S413的详细描述，此处不作赘述。
需要说明的是，本发明实施例不限定上述步骤S503～507和步骤S508～S512的执行顺序，可以先执行步骤S503～507，再执行步骤S508～S512；或者，也可以先执行步骤S508～S512，再执行步骤S503～507；或者，还可以并行执行步骤S503～507和步骤S508～S512。
本发明实施例中，E2E-O将网络切片的需求信息发送到CN，CN可以根据网络切片的需求信息确定CN域的需求信息并获取CN域的网络资源实例； 进一步的，CN还可以根据网络切片的需求信息确定RAN域的需求信息，并将RAN域的需求信息发送到RAN，或者，CN还可以将网络切片的需求信息发送到RAN，由RAN根据网络切片的需求信息确定RAN域的需求信息，从而RAN域可以获取RAN域的网络资源实例。
上述主要从各个单元之间交互的角度对本发明实施例的方案进行了介绍。可以理解的是，各个单元，例如第一管理单元、第二管理单元、第三管理单元、第四管理单元等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对第一管理单元、第二管理单元、第三管理单元和第四管理单元等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的模块的情况下，图6示出了上述实施例中所涉及的第一管理单元的一种可能的结构示意图。第一管理单元1000包括：处理模块1002和通信模块1003。处理模块1002用于对第一管理单元的动作进行控制管理，例如，处理模块1002用于支持第一管理单元执行图2中的过程S201至S205和S207，图3中的过程S301至S303，图4中的过程S403至S406或S409至S412，图5中的过程S503至S506、S508和S509，和/或用于本文所描述的技术的其它过程。通信模块1003用于支持第一管理单元与其他网络实体的通信，例如与第二管理单元或第三管理单元之间的通信。第一管理单元还可以包括存储模块1001，用于存储第一管理单元的程序代码和数据。
其中，处理模块1002可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital  Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块1003可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口，例如第一管理单元与第二管理单元或第三管理单元之间的接口。存储模块1001可以是存储器。
当处理模块1002为处理器，通信模块1003为通信接口，存储模块1001为存储器时，本发明实施例所涉及的第一管理单元可以为图7所示的第一管理单元。
参阅图7所示，该第一管理单元1010包括：处理器1012、通信接口1013、存储器1011。可选的，第一管理单元1010还可以包括总线1014。其中，通信接口1013、处理器1012以及存储器1011可以通过总线1014相互连接；总线1014可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线1014可以分为地址总线、数据总线、控制总线等。为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图6或图7所示的第一管理单元可以是图1中的CN-Domain-O、RAN-Domain-O或者CN等。
在采用集成的模块的情况下，图8示出了上述实施例中所涉及的第二管理单元的一种可能的结构示意图。第二管理单元2000包括：处理模块2002和通信模块2003。处理模块2002用于对第二管理单元的动作进行控制管理，例如，处理模块2002用于支持第二管理单元执行图3中的过程S304至SS06和S308，图5中的过程S510和S511，和/或用于本文所描述的技术的其它过程。通信模块2003用于支持第二管理单元与其他网络实体的通信，例如与第一管理单元或第四管理单元之间的通信。第二管理单元还可以包括存储模块2001，用于存储第二管理单元的程序代码和数据。
其中，处理模块2002可以是处理器或控制器，例如可以是CPU，通用 处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块2003可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口，例如第二管理单元与第一管理单元或第四管理单元之间的接口。存储模块2001可以是存储器。
当处理模块2002为处理器，通信模块2003为通信接口，存储模块2001为存储器时，本发明实施例所涉及的第二管理单元可以为图9所示的第二管理单元。
参阅图9所示，该第二管理单元2010包括：处理器2012、通信接口2013、存储器2011。可选的，第二管理单元2010还可以包括总线2014。其中，通信接口2013、处理器2012以及存储器2011可以通过总线2014相互连接；总线2014可以是PCI总线或EISA总线等。所述总线2014可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图8或图9所示的第二管理单元可以是RAN等。
在采用集成的模块的情况下，本发明实施例还提供上述实施例所涉及的第三管理单元和第四管理单元，其中，第三管理单元或第四管理单元可以具有与第一管理单元类似的结构。
例如，第三管理单元可以具有类似图6所示的结构，包括处理模块和通信模块，进一步的，还可以包括存储模块。或者，第三管理单元也可以具有类似图7所示的结构，包括处理器、通信接口和存储器，进一步的，还可以包括总线。可选的，第三管理单元可以是CN-NF-CTRL或RAN-NF-CTRL。
例如，第四管理单元可以具有类似图6所示的结构，包括处理模块和通信模块，进一步的，还可以包括存储模块。或者，第四管理单元也可以具有类似图7所示的结构，包括处理器、通信接口和存储器，进一步的，还可以包括总线。可选的，第四管理单元可以是RAN-NF-CTRL。
为描述简便，本发明实施例不对上述第三管理单元和第四管理单元的结构展开描述，有关第三管理单元或第四管理单元的结构介绍，可以参照上述 第一管理单元或第二管理单元的结构介绍。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于第一管理单元、第二管理单元、第三管理单元或第四管理单元中。当然，处理器和存储介质也可以作为分立组件存在于第一管理单元、第二管理单元、第三管理单元或第四管理单元中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (22)

  1. 一种管理方法，其特征在于，包括：
    第一管理单元接收第一管理请求，所述第一管理请求携带网络切片的需求信息或指示信息，所述指示信息用于获取所述网络切片的需求信息；
    所述第一管理单元根据所述网络切片的需求信息获取第一子网络的需求信息，其中，所述网络切片包括所述第一子网络；
    所述第一管理单元确定所述第一子网络所需的第一网络资源的需求信息，所述第一网络资源的需求信息用于选择、创建、配置、激活或请求满足所述第一网络资源的需求信息的第一网络资源实例。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    所述第一管理单元向第三管理单元发送第三管理请求，所述第三管理请求携带所述第一网络资源的需求信息，所述第三管理请求用于请求所述第一网络资源实例。
  3. 根据权利要求1所述的方法，其特征在于，还包括：
    所述第一管理单元选择现网中已经存在的所述第一网络资源实例。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述网络切片还包括第二子网络，所述方法还包括：
    所述第一管理单元向第二管理单元发送第二管理请求，所述第二管理请求携带所述网络切片的需求信息，以使得所述第二管理单元根据所述网络切片的需求信息获取所述第二子网络的需求信息；或者，
    所述第一管理单元根据所述网络切片的需求信息获取所述第二子网络的需求信息；
    所述第一管理单元向第二管理单元发送第二管理请求，所述第二管理请求携带所述第二子网络的需求信息。
  5. 根据权利要求4所述的方法，其特征在于，所述第二管理请求还携带所述第一子网络的标识或所述网络切片的标识，所述第一管理单元根据所述网络切片的需求信息获取第一子网络的需求信息之后，所述方法还包括：
    所述第一管理单元分配所述第一子网络的标识或所述网络切片的标识。
  6. 根据权利要求5所述的方法，其特征在于，所述第一管理单元分配所述第一子网络的标识，所述第一管理请求还携带所述网络切片的标识，所述 方法还包括：
    所述第一管理单元关联所述第一子网络的标识与所述网络切片的标识。
  7. 根据权利要求4至6中任一项所述的方法，其特征在于，所述第二子网络的需求信息包括以下至少一项：所述第二子网络的类型、所述第二子网络的SLA信息、所述第二子网络的部署信息、所述第二子网络的KPI或所述第二子网络的功能特征。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述网络切片的需求信息包括以下至少一种：所述网络切片的类型、所述网络切片的服务水平协议SLA信息、所述网络切片的部署信息、所述网络切片的关键性能指标KPI、所述网络切片的网络特征、所述网络切片的用户信息或所述网络切片提供的业务信息。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述第一子网络的需求信息包括以下至少一项：所述第一子网络的类型、所述第一子网络的SLA信息、所述第一子网络的部署信息、所述第一子网络的KPI或所述第一子网络的功能特征。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述第一网络资源的需求信息包括以下至少一种：所述第一网络资源的类型、所述第一网络资源的描述符信息、所述第一网络资源的实例信息、所述第一网络资源的KPI或所述第一网络资源的功能特征。
  11. 根据权利要求1至10中任一项所述的方法，其特征在于，所述第一网络资源实例包括以下至少一种：网络功能、网元、网络服务或传输资源。
  12. 一种第一管理单元，其特征在于，包括：处理模块和通信模块；
    所述处理模块用于通过所述通信模块接收第一管理请求，所述第一管理请求携带网络切片的需求信息或指示信息，所述指示信息用于获取网络切片的需求信息；以及用于根据所述网络切片的需求信息获取第一子网络的需求信息，其中，所述网络切片包括所述第一子网络；以及用于确定所述第一子网络所需的第一网络资源的需求信息，所述第一网络资源的需求信息用于选择、创建、配置、激活或请求满足所述第一网络资源的需求信息的第一网络资源实例。
  13. 根据权利要求12所述的第一管理单元，其特征在于，所述处理模块 还用于通过所述通信模块向第三管理单元发送第三管理请求，所述第三管理请求携带所述第一网络资源的需求信息，所述第三管理请求用于请求所述第一网络资源实例。
  14. 根据权利要求12所述的第一管理单元，其特征在于，所述处理模块还用于选择现网中已经存在的所述第一网络资源实例。
  15. 根据权利要求12至14中任一项所述的第一管理单元，其特征在于，所述网络切片还包括第二子网络，所述处理模块还用于：通过所述通信模块向第二管理单元发送第二管理请求，所述第二管理请求携带所述网络切片的需求信息，以使得所述第二管理单元根据所述网络切片的需求信息获取所述第二子网络的需求信息；或者，所述处理模块还用于：根据所述网络切片的需求信息获取所述第二子网络的需求信息，以及通过所述通信模块向第二管理单元发送第二管理请求，所述第二管理请求携带所述第二子网络的需求信息。
  16. 根据权利要求15所述的第一管理单元，其特征在于，所述第二管理请求还携带所述第一子网络的标识或所述网络切片的标识，所述处理模块还用于分配所述第一子网络的标识或所述网络切片的标识。
  17. 根据权利要求16所述的第一管理单元，其特征在于，所述处理模块分配所述第一子网络的标识，所述第一管理请求还携带所述网络切片的标识，所述处理模块还用于关联所述第一子网络的标识与所述网络切片的标识。
  18. 根据权利要求15至17中任一项所述的第一管理单元，其特征在于，所述第二子网络的需求信息包括以下至少一项：所述第二子网络的类型、所述第二子网络的SLA信息、所述第二子网络的部署信息、所述第二子网络的KPI或所述第二子网络的功能特征。
  19. 根据权利要求12至18中任一项所述的第一管理单元，其特征在于，所述网络切片的需求信息包括以下至少一种：所述网络切片的类型、所述网络切片的服务水平协议SLA信息、所述网络切片的部署信息、所述网络切片的关键性能指标KPI、所述网络切片的网络特征、所述网络切片的用户信息或所述网络切片提供的业务信息。
  20. 根据权利要求12至19中任一项所述的第一管理单元，其特征在于，所述第一子网络的需求信息包括以下至少一项：所述第一子网络的类型、所 述第一子网络的SLA信息、所述第一子网络的部署信息、所述第一子网络的KPI或所述第一子网络的功能特征。
  21. 根据权利要求12至20中任一项所述的第一管理单元，其特征在于，所述第一网络资源的需求信息包括以下至少一种：所述第一网络资源的类型、所述第一网络资源的描述符信息、所述第一网络资源的实例信息、所述第一网络资源的KPI或所述第一网络资源的功能特征。
  22. 根据权利要求12至21中任一项所述的第一管理单元，其特征在于，所述第一网络资源实例包括以下至少一种：网络功能、网元、网络服务或传输资源。
PCT/CN2016/107153 2016-11-24 2016-11-24 一种管理方法、管理单元及系统 WO2018094667A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2016/107153 WO2018094667A1 (zh) 2016-11-24 2016-11-24 一种管理方法、管理单元及系统
US16/422,116 US10924966B2 (en) 2016-11-24 2019-05-24 Management method, management unit, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/107153 WO2018094667A1 (zh) 2016-11-24 2016-11-24 一种管理方法、管理单元及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/422,116 Continuation US10924966B2 (en) 2016-11-24 2019-05-24 Management method, management unit, and system

Publications (1)

Publication Number Publication Date
WO2018094667A1 true WO2018094667A1 (zh) 2018-05-31

Family

ID=62194591

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/107153 WO2018094667A1 (zh) 2016-11-24 2016-11-24 一种管理方法、管理单元及系统

Country Status (2)

Country Link
US (1) US10924966B2 (zh)
WO (1) WO2018094667A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019001421A1 (zh) * 2017-06-26 2019-01-03 中兴通讯股份有限公司 网络切片管理方法、装置及计算机可读存储介质
GB2574247A (en) * 2018-05-31 2019-12-04 Nec Corp Communication system
US11218385B2 (en) 2017-11-16 2022-01-04 Huawei Technologies Co., Ltd. Network entity and method for identifier allocating and/or mapping of network services
CN117544514A (zh) * 2024-01-09 2024-02-09 上海卫星互联网研究院有限公司 网络切片方法、装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11323335B2 (en) * 2016-10-18 2022-05-03 Telefonaktiebolaget Lm Ericsson (Publ) SLA handling in network slices
SG11201907736QA (en) * 2017-03-23 2019-09-27 Sony Corp Device, method, and recording medium
EP3689035B1 (en) * 2017-09-25 2022-09-07 Telefonaktiebolaget LM Ericsson (publ) Adaptive network slice selection
US11166179B2 (en) * 2019-10-11 2021-11-02 Verizon Patent And Licensing Inc. Method and system for network slicing based on virtual routing and forwarding instances
US10708368B1 (en) * 2019-10-30 2020-07-07 Verizon Patent And Licensing Inc. System and methods for generating a slice deployment description for a network slice instance
CN116112987A (zh) * 2021-11-11 2023-05-12 中国电信股份有限公司 服务等级协议sla指标分解方法、装置、系统、设备及介质

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 杭州华三通信技术有限公司 网络配置自动部署方法及装置
WO2015021248A1 (en) * 2013-08-09 2015-02-12 Nec Laboratories America, Inc. Hybrid network management
CN105812217A (zh) * 2014-12-29 2016-07-27 中国移动通信集团公司 一种虚拟网络划分方法及多控制器代理装置
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器

Family Cites Families (66)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8880799B2 (en) 2005-09-30 2014-11-04 Cleversafe, Inc. Rebuilding data on a dispersed storage network
US9537730B2 (en) 2009-09-18 2017-01-03 Nokia Solutions And Networks Gmbh & Co. Kg Virtual network controller
US9172678B2 (en) 2011-06-28 2015-10-27 At&T Intellectual Property I, L.P. Methods and apparatus to improve security of a virtual private mobile network
KR101652928B1 (ko) 2012-01-31 2016-09-01 브이아이디 스케일, 인크. 스케일러블 고효율 비디오 코딩(hevc)을 위한 참조 픽처 세트(rps) 시그널링
EP2901766A2 (en) 2012-09-27 2015-08-05 Interdigital Patent Holdings, Inc. End-to-end architecture, api framework, discovery, and access in a virtualized network
US9515873B2 (en) 2013-03-12 2016-12-06 Dell Products L.P. System and method for management of virtual sub-networks
US9584369B2 (en) 2013-03-13 2017-02-28 Futurewei Technologies, Inc. Methods of representing software defined networking-based multiple layer network topology views
CN104243196B (zh) 2013-06-21 2019-03-12 中兴通讯股份有限公司 一种sdn架构下的虚拟网络映射保护方法及系统
US20160255535A1 (en) 2013-10-30 2016-09-01 Interdigital Patent Holdings, Inc. Enabling information centric networks specialization
CN103905523A (zh) 2013-12-23 2014-07-02 浪潮(北京)电子信息产业有限公司 一种基于sdn的云计算网络虚拟化实现方法及系统
JP6133224B2 (ja) 2014-02-28 2017-05-24 日本電信電話株式会社 仮想ネットワークサービス構築システム
US9338094B2 (en) 2014-03-31 2016-05-10 Dell Products, L.P. System and method for context aware network
US20150358399A1 (en) 2014-06-09 2015-12-10 Cisco Technology, Inc. Provisioning and managing slices of a consumer premises equipment device
CN105391568B (zh) 2014-09-05 2019-07-23 华为技术有限公司 一种软件定义网络sdn的实现方法、装置和系统
CN104639653B (zh) 2015-03-05 2019-04-09 北京掌中经纬技术有限公司 基于云架构的自适应方法及系统
JP6464257B2 (ja) 2015-03-20 2019-02-06 株式会社Ｎｔｔドコモ サービス割当決定装置及びサービス割当決定方法
EP3281454B1 (en) 2015-04-08 2019-03-27 Telefonaktiebolaget LM Ericsson (publ) Methods and network nodes for network partition preservation at inter-access handovers
CN104917809A (zh) 2015-04-13 2015-09-16 南京邮电大学 一种基于计算和通信融合的5g无线网络虚拟化体系架构
US10111163B2 (en) 2015-06-01 2018-10-23 Huawei Technologies Co., Ltd. System and method for virtualized functions in control and data planes
US10506471B2 (en) * 2015-06-11 2019-12-10 Nec Corporation Network management system and method for a shared radio access network, RAN, infrastructure
US10425830B2 (en) * 2015-09-07 2019-09-24 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
US9775045B2 (en) * 2015-09-11 2017-09-26 Intel IP Corporation Slicing architecture for wireless communication
EP3366018B1 (en) 2015-10-22 2020-03-04 Siemens Aktiengesellschaft Device for use in a network, controller, network and method
CN105281955B (zh) 2015-10-27 2018-10-09 上海华为技术有限公司 一种业务和资源编排的系统、方法及装置
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
WO2017113109A1 (en) * 2015-12-29 2017-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for virtualized network service provision
US11044203B2 (en) 2016-01-19 2021-06-22 Cisco Technology, Inc. System and method for hosting mobile packet core and value-added services using a software defined network and service chains
US10506552B2 (en) * 2016-02-05 2019-12-10 Telefonaktiebolaget Lm Ericsson (Publ) Core network node, radio network node, wireless device and methods performed therein
US10979998B2 (en) * 2016-02-05 2021-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Radio network node, communication device and methods performed therein
US10158568B2 (en) 2016-02-12 2018-12-18 Huawei Technologies Co., Ltd. Method and apparatus for service function forwarding in a service domain
US9961713B2 (en) 2016-02-23 2018-05-01 Motorola Mobility Llc Procedures to support network slicing in a wireless communication system
EP3416425B1 (en) 2016-02-29 2021-07-14 Huawei Technologies Co., Ltd. Method, apparatus and wireless communication system for determining control plane node
US20170289791A1 (en) 2016-04-05 2017-10-05 Electronics And Telecommunications Research Institute Communication method and apparatus using network slice
CN116113014A (zh) * 2016-04-23 2023-05-12 华为技术有限公司 一种无线接入网切片的生成方法、无线接入网及切片管理器
EP3468105A4 (en) * 2016-06-30 2019-06-26 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR ARRANGING NETWORK RESOURCES
WO2018006381A1 (zh) * 2016-07-07 2018-01-11 华为技术有限公司 一种网络资源的管理方法、装置及系统
US10757645B2 (en) * 2016-07-15 2020-08-25 Telefonaktiebolaget Lm Ericsson (Publ) Access control in communications network comprising slices
EP3276518B1 (de) 2016-07-29 2018-09-19 Deutsche Telekom AG Mobiles kommunikationsgerät mit mehrzahl über eine pin freischaltbarer anwendungen
CN107770794B (zh) * 2016-08-15 2023-05-09 华为技术有限公司 一种网络切片配置方法及装置
CN108307407B (zh) 2016-09-30 2021-02-12 华为技术有限公司 一种通信方法及装置
KR20180038716A (ko) 2016-10-07 2018-04-17 삼성전자주식회사 단말의 시그널링 메시지를 Network Function 간 전달하는 방안
US11363435B2 (en) * 2016-10-11 2022-06-14 Telefonaktiebolaget Lm Ericsson (Publ) Network slicing-aware access network
US11323335B2 (en) * 2016-10-18 2022-05-03 Telefonaktiebolaget Lm Ericsson (Publ) SLA handling in network slices
BR112019008694A2 (pt) * 2016-10-31 2019-10-08 Huawei Tech Co Ltd método de gerenciamento de fatia de rede, unidade de gerenciamento e sistema
KR102108871B1 (ko) * 2016-11-03 2020-05-12 주식회사 케이티 네트워크 슬라이스 기반 데이터 처리 방법 및 그 장치
CN108023751B (zh) * 2016-11-03 2020-02-14 华为技术有限公司 用于管理网络切片实例的方法和装置
US10856183B2 (en) * 2016-11-10 2020-12-01 Huawei Technologies Co., Ltd. Systems and methods for network slice service provisioning
US11095526B2 (en) * 2016-11-14 2021-08-17 Huawei Technologies Co., Ltd. System and method for accelerated provision of network services
CN108243106B (zh) * 2016-12-23 2020-09-04 华为技术有限公司 控制网络切片的方法、转发设备、控制设备和通信系统
EP3565182B1 (en) * 2017-01-25 2021-03-03 Huawei Technologies Co., Ltd. Network slicing management method, and management unit and system
EP3576479A4 (en) * 2017-02-27 2020-03-04 Huawei Technologies Co., Ltd. ADMINISTRATIVE PROCEDURE, ADMINISTRATIVE UNIT AND SYSTEM
CN108632058B (zh) * 2017-03-18 2020-10-09 华为技术有限公司 网络切片的管理方法和装置
JP6834033B2 (ja) * 2017-03-19 2021-02-24 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． ネットワークスライス管理方法、ユニット、及びシステム
CN110326345B (zh) * 2017-03-24 2021-12-24 华为技术有限公司 一种配置网络切片的方法、装置和系统
US10841184B2 (en) * 2017-03-28 2020-11-17 Huawei Technologies Co., Ltd. Architecture for integrating service, network and domain management subsystems
US11050626B2 (en) * 2017-04-28 2021-06-29 Huawei Technologies Co., Ltd. Service provision for offering network slices to a customer
CN109327319B (zh) * 2017-07-31 2021-06-08 华为技术有限公司 部署网络切片的方法、设备及系统
CN109391490B (zh) * 2017-08-08 2021-12-03 华为技术有限公司 网络切片的管理方法和装置
CN109391504B (zh) * 2017-08-11 2022-04-29 华为技术有限公司 网络切片的部署方法和装置
CN109391669B (zh) * 2017-08-11 2020-12-08 华为技术有限公司 一种业务管理的方法、装置及存储介质
CN109428749B (zh) * 2017-08-28 2022-04-22 华为技术有限公司 网络管理方法及相关设备
CN109474449A (zh) * 2017-09-08 2019-03-15 华为技术有限公司 一种处理网络切片实例的方法及装置
CN114745728A (zh) * 2017-09-30 2022-07-12 华为技术有限公司 网络资源部署及评估的方法、和设备
CN109600768B (zh) * 2017-09-30 2022-06-07 华为技术有限公司 网络切片的管理方法、设备及系统
US20190109768A1 (en) * 2017-10-06 2019-04-11 Huawei Technologies Co., Ltd. Management of network slices and associated services
CN109803281B (zh) * 2017-11-16 2021-11-19 华为技术有限公司 网络业务的管理方法、设备及系统

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 杭州华三通信技术有限公司 网络配置自动部署方法及装置
WO2015021248A1 (en) * 2013-08-09 2015-02-12 Nec Laboratories America, Inc. Hybrid network management
CN105812217A (zh) * 2014-12-29 2016-07-27 中国移动通信集团公司 一种虚拟网络划分方法及多控制器代理装置
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019001421A1 (zh) * 2017-06-26 2019-01-03 中兴通讯股份有限公司 网络切片管理方法、装置及计算机可读存储介质
US11218385B2 (en) 2017-11-16 2022-01-04 Huawei Technologies Co., Ltd. Network entity and method for identifier allocating and/or mapping of network services
GB2574247A (en) * 2018-05-31 2019-12-04 Nec Corp Communication system
US11546806B2 (en) 2018-05-31 2023-01-03 Nec Corporation Communication system
CN117544514A (zh) * 2024-01-09 2024-02-09 上海卫星互联网研究院有限公司 网络切片方法、装置
CN117544514B (zh) * 2024-01-09 2024-05-17 上海卫星互联网研究院有限公司 网络切片方法、装置

Also Published As

Publication number Publication date
US20190281503A1 (en) 2019-09-12
US10924966B2 (en) 2021-02-16

Similar Documents

Publication Publication Date Title
WO2018094667A1 (zh) 一种管理方法、管理单元及系统
WO2018076547A1 (zh) 网络切片的管理方法、管理单元及系统
CN109845303B (zh) 网络切片的管理方法及管理单元
CN109417719B (zh) 一种网络资源的管理方法、装置及系统
CN110896355B (zh) 一种网络切片的选择方法及装置
WO2018171459A1 (zh) 网络切片的管理方法和装置
WO2019029268A1 (zh) 网络切片的部署方法和装置
CN109391490B (zh) 网络切片的管理方法和装置
EP3672314B1 (en) Network management method, device and system
EP3531749B1 (en) Management method, management unit and system for network function
CN109417501B (zh) 网络资源的编排方法和设备
WO2019024671A1 (zh) 部署网络切片的方法、设备及系统
WO2019100924A1 (zh) 一种网络性能保障方法及装置
WO2018082574A1 (zh) 一种信息发送方法、单元和系统
WO2018014351A1 (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: 16922528

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16922528

Country of ref document: EP

Kind code of ref document: A1