WO2018137196A1 - 一种网络切片的管理方法、管理单元和系统 - Google Patents

一种网络切片的管理方法、管理单元和系统 Download PDF

Info

Publication number
WO2018137196A1
WO2018137196A1 PCT/CN2017/072666 CN2017072666W WO2018137196A1 WO 2018137196 A1 WO2018137196 A1 WO 2018137196A1 CN 2017072666 W CN2017072666 W CN 2017072666W WO 2018137196 A1 WO2018137196 A1 WO 2018137196A1
Authority
WO
WIPO (PCT)
Prior art keywords
management unit
subnet
information
request
requirement information
Prior art date
Application number
PCT/CN2017/072666
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 CN201780084728.9A priority Critical patent/CN110226308B/zh
Priority to EP17893769.4A priority patent/EP3565182B1/en
Priority to PCT/CN2017/072666 priority patent/WO2018137196A1/zh
Publication of WO2018137196A1 publication Critical patent/WO2018137196A1/zh
Priority to US16/522,131 priority patent/US11070989B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/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/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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a network slice management method, a management unit, and a system.
  • Network slicing can be understood as an on-demand network.
  • a physical network can be logically divided into multiple network slices, and different network slices can be used to carry different services.
  • power companies need to provide smart metering services that can be implemented by connecting a series of network slices of Machine-to-Machine (M2M) devices.
  • M2M Machine-to-Machine
  • the network management system In the existing network slice management process, the network management system (NMS) generally selects multiple available network function instances according to the network slice requirement information, and sends different network function instance information and corresponding configuration parameters. Deploy and configure to different Element Management System (EMS).
  • EMS Element Management System
  • the NMS and the EMS may be provided by different vendors, or different EMSs may be provided by different vendors, and different vendors may not be able to obtain each other's information. This leads to cross-vendor scenarios where network slicing cannot be effectively managed.
  • the embodiment of the invention describes a method, a management unit and a system for managing a network slice, so as to solve the problem that the network slice cannot be effectively managed in a cross-vendor scenario.
  • the embodiment of the present invention provides a method for managing a network slice, where the method includes: determining, by the first management unit, the requirement information of the subnet according to the requirement information of the network slice, where the network slice includes at least one subnet; The management unit sends a first negotiation request to the second management unit, where the first negotiation request carries the requirement information of the subnet, and the first negotiation request is used to query the support information of the second management unit for the subnet requirement; corresponding, second The management unit determines that the second management unit can support the demand information of the subnet, or the second management unit determines that the second management unit cannot support the demand information of the subnet.
  • the first management unit in the process of managing the network slice, the first management unit, after determining the requirement information of the subnet, can send a first negotiation request to the second management unit to query the second management unit for the sub Corresponding to the demand information of the network, correspondingly, the second management unit can determine whether it can support the demand information of the subnet. Therefore, in the solution of the embodiment of the present invention, the management information of the subnet can be negotiated between different management units, so that the management of the network slice in the cross-vendor scenario is more flexible and effective.
  • the first management unit may further receive a notification from the second management unit, where the notification is used to instruct the first management unit to determine the subnet.
  • the first management unit may also receive a network slice request from the third management unit, the network slice request carries the network slice request information, and the network slice request is used to request to create or modify the network slice.
  • the network performance of the subnet may also be collected before the second management unit sends the notification to the first management unit.
  • the second management unit may send the notification to the first management unit.
  • the first management unit may further receive the capability information of the subnet supported by the second management unit from the second management unit. In this case, the first management unit may determine the requirement information of the subnet according to the requirement information of the network slice and the capability information of the subnet.
  • the first management unit may further send a query request to the second management unit, where the query request is used to request the Subnet capability information.
  • the determining, by the first management unit, the requirement information of the subnet according to the requirement information of the network slice may be implemented by: the first management unit may decompose the demand information of the network slice into the requirement information of the at least one subnet.
  • the first management unit may further receive a negotiation response, where the negotiation response carries the indication information, where the indication information is used to indicate the second management unit.
  • the support information of the subnet is supported by the second management unit to support the subnet requirement information, or the support situation is that the second management unit cannot support the subnet requirement information. That is, the indication information is used to indicate that the second management unit can support the requirement information of the subnet, or the indication information is used to indicate that the second management unit cannot support the requirement information of the subnet.
  • the foregoing support situation is that the second management unit can support the requirement information of the subnet, and after receiving the negotiation response from the second management unit, the first management unit may further send the subnet request to the second management unit.
  • the subnet request is used to request to create a subnet or modify an existing subnet.
  • the subnet request carries the demand information of the above subnet.
  • the foregoing support case is that the second management unit cannot support the requirement information of the subnet, and after receiving the negotiation response from the second management unit, the first management unit may further send a second negotiation request to the second management unit, where the second negotiation request carries The required information of the updated subnet, and the second negotiation request is used to query the support information of the second management unit for the updated subnet.
  • the foregoing negotiation response may further carry the requirement information of the subnet suggested by the second management unit.
  • the first management unit may, after receiving the negotiation response, according to the requirement information of the network slice and the required information of the subnet suggested by the second management unit, Determine the demand information for the updated subnet.
  • an embodiment of the present invention provides a method for managing a network slice, where the method includes: the first management unit sends a query request to the second management unit, and the query request is used to request a subnet supported by the second management unit.
  • the second management unit sends the capability information of the subnet supported by the second management unit to the first management unit; the first management unit determines, according to the requirement information of the network slice and the capability information of the subnet supported by the second management unit, The demand information of the subnet, wherein the network slice includes at least one subnet.
  • the first management unit is configured to acquire the capability information of the subnet supported by the second management unit from the second management unit, and according to the network slice requirement information and the subnet supported by the second management unit. Capability information to determine the demand information of the subnet. Therefore, in the solution of the embodiment of the present invention, the first management unit can obtain the capability information of the subnet before determining the requirement information of the subnet, which is beneficial to determining the requirement information of the appropriate subnet, thereby improving the network slice in the cross-vendor scenario. Management efficiency.
  • the first management unit may further receive a notification from the second management unit, where the notification is used to instruct the first management unit to determine the requirement information of the subnet. ;
  • the first management unit may further receive a network slice request from the third management unit, where the network slice request carries the network slice requirement information, and the network slice request is used to request to create or modify the network slice.
  • the first management unit may also send a subnet request to the second management unit, the subnet request carries the subnet requirement information, and the subnet request is used to request to create a subnet or modify an existing subnet.
  • the second management unit may create a subnet or modify an existing subnet, and send information of the created or modified subnet to the first management unit.
  • the first management unit may be a cross-domain management unit; the second management unit may be a core network domain management unit, an access network domain management unit, or a transport network domain management unit.
  • the demand information of the network slice refers to the necessary information for determining a network slice.
  • the subnet demand information refers to the necessary information for determining a subnet.
  • the capability information of the subnet supported by the second management unit refers to the characteristics of the subnet supported by the second management unit.
  • 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 may further include a communication interface for supporting communication between the second management unit and the first 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 present invention provides a communication system, where the system includes the first management unit and the second management unit, which are described in the foregoing aspects; or the system includes the first management unit and the second management described in the foregoing aspects. Unit and third management unit.
  • an embodiment of the present invention provides a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • embodiments of the present invention provide a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • the first management unit in the process of managing the network slice, after determining the requirement information of the subnet, the first management unit can send the first negotiation request to the second management unit to query
  • the second management unit supports the requirement information of the subnet, and correspondingly, the second management unit can determine whether it can support the demand information of the subnet. Therefore, in the solution of the embodiment of the present invention, the management information of the subnet can be negotiated between different management units, so that the management of the network slice in the cross-vendor scenario is more flexible and effective.
  • FIG. 1 is a schematic diagram of a possible application scenario according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a possible network architecture according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of communication of a method for managing a network slice according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of communication of another method for managing a network slice according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of communication of a method for managing a network slice according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of communication of another method for managing a network slice according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of communication of another method for managing a network slice according to an embodiment of the present invention.
  • FIG. 8A is a schematic diagram of communication of a method for managing a network slice according to an embodiment of the present invention.
  • FIG. 8B is a schematic diagram of communication of another method for managing a network slice according to an embodiment of the present invention.
  • FIG. 9A is a schematic block diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 9B is a schematic structural diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 10A is a schematic block diagram of a second management unit according to an embodiment of the present disclosure.
  • FIG. 10B is a schematic structural diagram of a 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 diagram of a possible application scenario according to an embodiment of the present invention.
  • the application scenario shown in FIG. 1 includes at least an SO unit, an NO unit, an EM unit, and a Network/NF unit.
  • SO unit SO unit
  • NO unit NO unit
  • EM unit EM unit
  • Network/NF unit Network/NF unit
  • a Service Orchestrator (SO) unit which can also be called a business orchestration and management unit or a business management unit, mainly includes: lifecycle management (such as instantiation, update, and deletion) of a service according to a service request message.
  • Service aggregation service management, such as service fault, configuration, billing, performance and security (Fault, Configuration, Accounting, Performance, Security, FCAPS) management; and service and network slice (NSL) Mapping between, etc.
  • the service may be a set of service level agreement (SLA) communication services that the user can enjoy, such as mobile broadband (MBB) services, voice services, and the Internet of Things (IOT).
  • MBB mobile broadband
  • IOT Internet of Things
  • Business for example, smart parking business, smart meter reading business, etc.
  • the SO unit can manage the services carried by the network slice.
  • Network Orchestrator (NO) unit also known as network orchestration and management unit or network management unit, its functions mainly include: network slice management, such as network slice life cycle management, network slice Management of templates, etc.; mapping between network slicing and network functions; coordination of different types of network resources; coordination of network resources provided by different operators and different network providers to enable network resources provided by different network providers Can meet the requirements of the target business, such as the requirements of the SLA, the requirements of the key performance indicators (KPI), the requirements of the quality of service (QoS), etc.; the unified arrangement of the network equipment provided by different vendors; The provision of an external application program interface (API), which is used to provide network functions for third parties to achieve cross-operator deployment.
  • API application program interface
  • the Element Manager (EM) unit also known as the Network Function Manager (NF-M) unit, mainly includes: lifecycle management of network elements or network functions (such as instantiation, update, Delete, etc.; FCAPS management of network elements or network functions.
  • EM Element Manager
  • NF-M Network Function Manager
  • a network unit which may include at least one of a core network unit, an access network unit, or a transport network unit. It should be noted that the foregoing network unit may be replaced by a network function (NF) unit, or the network unit may have the function of a network function unit at the same time.
  • the "Network/NF" unit shown in FIG. 1 represents a unit having a function of a network unit and/or a function of a network function unit.
  • OSS Operations Support System
  • NO unit may be deployed in an Operations Support System (OSS)
  • OSS can be understood as a support system for device and network maintenance, responsible for network management of single vendors and network management of multiple vendors.
  • SO unit may be represented by SO, and the other units are similar, and will not be described again.
  • FIG. 2 illustrates a possible network architecture provided by an embodiment of the present invention.
  • the network architecture includes: a Business Support System (BSS), a Cross Domain Manager (CDM) unit, and a Core Network Domain Manager (CN-DM) unit.
  • BSS Business Support System
  • CDM Cross Domain Manager
  • CN-DM Core Network Domain Manager
  • the CDM is connected to the BSS, and the CDM is also connected to the CN-DM, RAN-DM and TN-DM respectively.
  • the BSS is responsible for business-related management (such as business operations, billing, customer relationship management, etc.) and provides services for terminals.
  • the BSS can also be replaced by a customer (Customer), or the BSS can have the functionality of the Customer at the same time.
  • Customer's functions include: business management, and providing corresponding services for the terminal.
  • BSS/Customer indicates a unit having a function of a BSS and/or a function of a Customer.
  • the CDM may also be referred to as a cross-domain orchestration unit with management functions for network slicing and/or orchestration functions for NSL.
  • the CDM may include some or all of the following functions: management of the NSL, such as lifecycle management of network slices, management of network slice templates, fault management of network slices, performance management of network slices, configuration management of network slices, etc.; NSL and Mapping between subnets, and mapping between NSL and network functions; coordination of network resources or SLA information provided by different subdomains (such as core domain, access domain, or transport domain); provided by each subdomain Uniform orchestration of subnet slices and network functions, which enables subnet slicing or network functions provided by each subdomain to meet the target Business requirements (eg, SLA requirements, KPI requirements, and QoS requirements, etc.).
  • target Business requirements eg, SLA requirements, KPI requirements, and QoS requirements, etc.
  • the network slice may also be referred to as an End to End (E2E) network slice, which may include at least a Core Network (CN) part, a Radio Access Network (RAN) part, and a transmission. a network (Transport Network, TN) portion; or, the network slice may include any one of a CN part, a RAN part, or a TN part; or, the network slice may represent a network slice of the CN part, a network slice of the RAN part, or a TN Part of the network slice. It is to be understood that the network slice according to the embodiment of the present invention may further have other embodiments, which are not limited in the embodiment of the present invention.
  • E2E End to End
  • CN Core Network
  • RAN Radio Access Network
  • TN Transmission Network
  • the CN-DM has a subnet management function of the network slice in the core domain and/or a subnet scheduling function of the network slice in the core domain.
  • the CN-DM may include some or all of the following functions: management of subnets of network slices within the core domain, including, for example, subnet lifecycle management (including creation, update, deletion, etc.), subnet fault management, subnets Performance management, subnet configuration management, etc.; management of services in the core domain, including, for example, service lifecycle management, service fault management, service performance management, service configuration management, etc.; coordination of network resources within the core network domain, Used for unified orchestration.
  • the RAN-DM has a subnet management function for accessing network slices in the network domain and/or a subnet scheduling function for accessing network slices within the network domain.
  • the RAN-DM may include some or all of the following functions: management of subnets of network slices within the access domain, including, for example, subnet lifecycle management (including creation, update, deletion, etc.), subnet fault management, sub- Network performance management, subnet configuration management, etc.; management of services within the access domain, including, for example, service lifecycle management, service fault management, service performance management, service configuration management, etc.; access to network resources within the network domain Coordination for uniform orchestration.
  • the TN-DM has a subnet management function for transporting network slices within the network domain and/or a subnet scheduling function for transporting network slices within the network domain.
  • the TN-DM may include some or all of the following functions: management of subnets of network slices within the transport domain, including, for example, subnet lifecycle management (including creation, update, deletion, etc.), subnet fault management, subnets Performance management, configuration management of subnets, etc.; management of services within the transport domain, including, for example, lifecycle management of services, fault management of services, performance management of services, configuration management of services, etc.; coordination of network resources within the transport domain, Used for unified orchestration.
  • CDM, CN-DM, RAN-DM, and TN-DM may all be deployed in the SO or deployed in the NO; or the CDM may be deployed in the NO, CN-DM, RAN-DM, and TN-DM. They can all be deployed in the EM; alternatively, the above CDM can be deployed in the SO, and the CN-DM, RAN-DM, and TN-DM can all be deployed in the NO.
  • the NMS In the existing network slice management process, the NMS generally selects multiple available network function instances according to the network slice requirement information, and sends different network function instance information and corresponding configuration parameters to different EMSs for deployment and configuration.
  • the NMS and the EMS may be provided by different vendors.
  • different EMSs may be provided by different vendors, and different vendors may not be able to obtain information and configuration parameters of the network function instance of the other party. This leads to cross-vendor scenarios where network slicing cannot be effectively managed.
  • an embodiment of the present invention provides a method for managing a network slice, and a management unit and system based on the method.
  • the method includes: the first management unit determines the requirement information of the subnet according to the requirement information of the network slice, where the network slice includes at least one subnet; the first management unit sends the first negotiation request to the second management unit, the first protocol The requesting information of the subnet is carried by the quotient request, and the first negotiation request is used to query the support information of the second management unit for the subnet demand information; correspondingly, the second management unit determines that the second management unit can support the demand information of the subnet Or, the second management unit determines that the second management unit cannot support the demand information of the subnet.
  • the first management unit in the process of managing the network slice, the first management unit, after determining the requirement information of the subnet, can send a first negotiation request to the second management unit to query the second management unit for the sub Corresponding to the demand information of the network, correspondingly, the second management unit can determine whether it can support the demand information of the subnet. Therefore, in the solution of the embodiment of the present invention, the management information of the subnet can be negotiated between different management units, so that the management of the network slice in the cross-vendor scenario is more flexible and effective.
  • the demand information of the above network slice refers to the necessary information for determining a network slice.
  • the network slice requirement information may include some or all of the following: type of network slice (for example, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), high reliability and low time) Ultra-Reliable and Low Latency Communication (URLLC), the SLA requirements of the service, or the KPI of the network.
  • the SLA requirement of the service or the KPI of the network may include at least one of the following: a latency, a report success ratio, a command success ratio, a coverage, and a capacity. ), reliability or throughput.
  • the reporting success rate may refer to the proportion of successful uplink packet transmission; the delivery success rate may refer to the proportion of successful downlink packet transmission; the coverage may refer to the distribution area of the terminal; and the capacity may refer to the number of terminals that can be accommodated.
  • the demand information of the above subnet refers to the necessary information for determining a subnet.
  • the demand information of the subnet may include some or all of the following: the SLA requirement of the service or the KPI of the network, and the like.
  • the SLA requirement of the service or the KPI of the network may include at least one of the following: a latency, a report success ratio, a command success ratio, a coverage, and a capacity. ), reliability or throughput.
  • the solution provided by the embodiment of the present invention will be described below with reference to FIG.
  • the method shown in FIG. 3 is described by taking the network architecture shown in FIG. 2 as an example.
  • the method shown in FIG. 3 includes: sections 301 to 303.
  • the first management unit determines the demand information of the subnet according to the demand information of the network slice.
  • the network slice includes at least one subnet.
  • a subnet may also be referred to as a subnetwork.
  • the second management unit may further receive a network slice request from the third management unit, where the network slice request carries the network slice request information, and the network slice request Used to request to create or modify this network slice.
  • the third management unit sends a network slice request to the second management unit, where the network slice request carries the initial network slice requirement information, and the network slice request is used to request to create the network slice.
  • the second management unit may determine the requirement information of the subnet according to the initial network slice requirement information during the process of creating the network slice. That is, in the scenario of initially creating a network slice, the network slice request sent by the third management unit triggers the second management unit to determine the requirement information of the subnet.
  • the above creation of a network slice can also be understood as instantiating a network slice.
  • the third management unit may send a network slice request to the second management unit due to the change of the received service requirement, and the network slice request.
  • the demand information of the updated network slice is carried, and the network slice request is used to request to modify the network slice.
  • the second management unit may determine the requirement information of the subnet according to the updated network slice requirement information during the process of modifying the network slice. That is, in the scenario of modifying the network slice, the network slice request sent by the third management unit triggers the second management unit to determine the requirement information of the subnet.
  • the above modified network slice can also be understood as updating the network slice.
  • the second management unit may further receive a notification, where the notification is used to instruct the first management unit to determine the requirement information of the subnet.
  • the network performance of the subnet may also be collected, where the network performance of the subnet cannot satisfy the sub-supported by the second management unit.
  • the second management unit may send the notification to the first management unit when the network needs information.
  • the network slice is already set up and running, and the demand information of the subnet corresponding to the network slice requirement information is the first sub-requirement information.
  • the second management unit may collect the network performance of the subnet.
  • the second management unit may send a notification to the first management unit, where the first management unit is instructed to The first sub-requirement information is adjusted to determine the second sub-requirement information.
  • the second sub-requirement information is requirement information of the subnet determined by the first management unit after receiving the notification.
  • the notification sent by the second management unit triggers the second management unit to determine the requirement information of the subnet.
  • the determination of the requirement information of the subnet can be understood as Adjustment of the subnet's demand information.
  • the first management unit may further receive the capability information of the subnet supported by the second management unit from the second management unit; In this case, the first management unit may determine the requirement information of the subnet according to the requirement information of the network slice and the capability information of the subnet.
  • the first management unit may further send a query request to the second management unit, where the query request is used for the request. Capability information for this subnet.
  • the capability information of the subnet refers to the feature of the subnet supported by the second management unit.
  • the capability information of a subnet may include the type of subnet, the function of the subnet, the area supported by the subnet, the capacity supported by the subnet, the service or network parameters (such as SLA) supported by the subnet, or the subnet.
  • the first management unit may determine the requirement information of the subnet by: the first management unit may decompose the demand information of the network slice into the requirement information of the at least one of the foregoing subnets.
  • the first management unit sends a first negotiation request to the second management unit, where the first negotiation request carries the requirement information of the subnet.
  • the first negotiation request is used to query the support information of the second management unit for the subnet.
  • the first negotiation request may be used to query whether the second management unit supports the requirement information of the subnet.
  • the second management unit determines that the second management unit can support the demand information of the subnet, or the second management unit determines that the second management unit cannot support the demand information of the subnet.
  • the second management unit may further send a negotiation response to the first management unit, where the negotiation response carries indication information, where the indication information is used to indicate that the second management unit supports the requirement information of the subnet, and the support situation is The second management unit can support the requirement information of the subnet, or the support situation is that the second management unit cannot support the requirement information of the subnet.
  • the foregoing negotiation response may be referred to as a first negotiation response.
  • the foregoing support situation is that the second management unit can support the demand information of the subnet.
  • the indication information is used to indicate that the second management unit can support the requirement information of the subnet.
  • the first management unit may further send a subnet request to the second management unit.
  • the subnet request is used to request to create the above subnet or modify an existing subnet, and the subnet request carries the demand information of the above subnet.
  • the foregoing support situation is that the second management unit cannot support the requirement information of the subnet, that is, the indication information is used to indicate that the second management unit cannot support the requirement information of the subnet, the first management After receiving the first negotiation response from the second management unit, the unit may further update the requirement information of the subnet, and send a second negotiation request to the second management unit, where the second negotiation request carries the updated subnet requirement information, and the second The negotiation request is used to query the support information of the second management unit for the updated subnet.
  • the second management unit may further determine whether it can support the updated subnet requirement information, and further, may send the second negotiation response to the first management unit.
  • the specific implementation process is similar to the 303 part, and the above detailed description in section 303 can be referred to.
  • the first negotiation response may further carry the requirement information of the subnet suggested by the second management unit.
  • the second management unit may carry the requirement information of the subnet suggested by the second management unit, in addition to carrying the indication information in the first negotiation response,
  • the first management unit may consider the requirement information of the subnet suggested by the second management unit, thereby facilitating the first management unit and the second management unit to agree on the required information of the subnet.
  • the requirement information of the subnet can be negotiated by continuously sending the negotiation request and the negotiation response, until the second management unit can support the sending by the first management unit.
  • Demand information for the subnet can be negotiated by continuously sending the negotiation request and the negotiation response, until the second management unit can support the sending by the first management unit.
  • the first management unit may be a cross-domain management unit; the second management unit may be a core network domain management unit, an access network domain management unit, or a transport network domain management unit; the third management unit may For BSS/Customer.
  • FIG. 4 is a schematic diagram of a method for managing a network slice in a scenario of creating or modifying a network slice according to an embodiment of the present invention.
  • the method illustrated in Figure 4 includes portions 401 through 412, with portions 406 through 409 being optional.
  • the first management unit receives a network slice request, and the network slice request carries the network slice request information.
  • the network slice request is used to request to create or modify a network slice.
  • the requirement information of the network slice may be the initial network slice requirement information; in the scenario of modifying the network slice, the network slice requirement information may be the updated network slice requirement information.
  • the first management unit determines the demand information of the subnet according to the demand information of the network slice.
  • the first management unit may decompose the demand information of the network slice into the demand information of the at least one subnet.
  • the network slice may include one, two or more subnets, which is not limited in the embodiment of the present invention.
  • the first management unit may decompose the demand information of the network slice into the required information of the subnet of the core domain; of course, if the network slice includes a subnet of the access domain or The subnet of the transport domain, The first management unit may also decompose the demand information of the network slice into the requirement information of the subnet corresponding to the domain.
  • the first management unit may decompose the demand information of the network slice into the subnet of the core domain.
  • the first management unit sends a first negotiation request to the second management unit, where the first negotiation request carries the requirement information of the subnet, and the first negotiation request is used to query the support information of the second management unit for the subnet. .
  • the requirement information of the subnet is the requirement information of the subnet of the core domain
  • the second management unit is the core domain management unit
  • the first management unit may send the core domain to the core domain management unit by using the first negotiation request.
  • the subnet's demand information is used to query the support information of the core domain management unit for the subnet's demand information of the core domain.
  • the second management unit is the access domain management unit; or, if the demand information of the subnet is the subnet of the transmission domain
  • the demand information the second management unit is a transport network domain management unit; the first management unit may also send the demand information of the subnet of the corresponding domain to the second management unit.
  • the requirement information of the network slice is decomposed into the requirement information of the subnet of the core domain, the requirement information of the subnet of the access domain, and the requirement of the subnet of the transmission domain.
  • the first management unit may also send the requirement information of the subnet of the corresponding domain to the core domain management unit, the access domain management unit, and the transport domain management unit. In this case, the first management unit separately negotiates the requirement information of the subnet of the corresponding domain with a different second management unit.
  • the second management unit determines that the second management unit can support the demand information of the subnet, or the second management unit determines that the second management unit cannot support the demand information of the subnet.
  • the second management unit sends a first negotiation response to the first management unit, where the first negotiation response carries the indication information.
  • the indication information is used to indicate that the second management unit can support the requirement information of the subnet, in which case the indication The information may be understood as a positive indication; or, if the second management unit determines in the 404 part that the second management unit cannot support the sub-network requirement information, the indication information is used to indicate that the second management unit cannot support the sub-network requirement information. In this case, the indication information can be understood as a negative indication.
  • the first negotiation response may further carry the requirement information of the subnet suggested by the second management unit.
  • the second management unit sends a positive indication to the first management unit in section 405, then section 410 is performed; if the second management unit sends a negative indication to the first management unit in section 405, then the portion 406 is executed.
  • the first management unit updates the demand information of the subnet.
  • the first management unit may update the requirement information of the subnet according to the requirement information of the network slice and the requirement information of the subnet suggested by the second management unit.
  • the first management unit sends a second negotiation request to the second management unit, where the second negotiation request carries the required information of the updated subnet, and the second negotiation request is used to query the second management unit for the updated subnet.
  • Information support
  • the second management unit determines that the second management unit is capable of supporting the required information of the updated subnet, or the second management unit determines that the second management unit cannot support the updated subnet's demand information.
  • the second management unit sends a second negotiation response to the first management unit, and the second negotiation response carries the finger Show information.
  • the indication information is a positive indication; if the second management unit determines in the 408 part that the second management unit cannot support If the required information of the updated subnet is, the indication information is a negative indication.
  • the portion 410 is executed.
  • the first management unit sends a subnet request to the second management unit for requesting to create a subnet or modify an existing subnet.
  • the subnet request carries the demand information of the subnet.
  • the requirement information of the subnet is the requirement information of the subnet that is negotiated by the first management unit and the second management unit. For example, if the second management unit sends a positive indication to the first management unit in the 405 portion, the demand information of the subnet is the demand information of the subnet determined by the first management unit in section 402. For another example, if the second management unit sends a negative indication to the first management unit in the 405 portion, the demand information of the subnet is the demand information of the subnet updated by the first management unit in the 406 portion.
  • the first management unit may only receive the positive indication sent by the second management unit after the 406 part to the 409 part is executed once, that is, in the 409 part; or, the first management The unit may also perform a positive indication sent by the second management unit when the 409 part is last executed after the 406 part to the 409 part are executed twice or more. In either case, the required information of the updated subnet is the first management unit performs the demand information of the subnet of the most recent update of the 410 part.
  • the second management unit creates a subnet or modifies an existing subnet.
  • the second management unit can create a subnet according to the requirement information of the subnet carried in the subnet request.
  • the second management unit can reuse the existing subnet, wherein the second management unit can modify the existing subnet in the process of reusing to meet the requirement information of the subnet carried in the subnet request.
  • the second management unit transmits information of the created or modified subnet to the first management unit.
  • part 403 to 409 of the method shown in FIG. 4 may be referred to as a negotiation process of requirement information of a subnet. It can be understood that, during the negotiation process, the first management unit and the second management unit may need to negotiate one or two times for the subnet requirement information to reach an agreement.
  • FIG. 5 is a schematic diagram of another network slice management method in a scenario of creating or modifying a network slice according to an embodiment of the present invention.
  • the method illustrated in Figure 5 includes portions 501 through 509, with portions 502 and 503 being optional.
  • the 501 portion, the 505 portion, and the 507 portion to the 509 portion are respectively the same as or similar to the 401 portion, the 402 portion, and the 410 portion to the 412 portion in Fig. 4, and may refer to the 401 portion, the 402 portion, and the 410 portion to the 412 portion.
  • a detailed description of the 506 part is the same as or similar to the negotiation process of the required information of the subnet in FIG. 4 . For details, refer to the detailed description of the negotiation process of the required information of the subnet in FIG. 4;
  • the method shown in FIG. 5 is different from the method shown in FIG. 4 in that the method shown in FIG. 5 further includes a second management unit before the first management unit determines the subnet requirement information according to the network slice requirement information.
  • the acquiring process of the capability information of the supported subnet; further, the first management unit may determine the demand information of the subnet according to the requirement information of the network slice and the capability information of the subnet.
  • the above obtaining process may include part 504, or may include part 503 and part 504, or may include parts 502 to 504.
  • the first management unit sends a query request to the second management unit, the query request is used to query the second Capability information for subnets supported by the snap-in.
  • the second management unit evaluates capability information of the subnet supported by the second management unit.
  • the second management unit transmits capability information of the subnet supported by the second management unit to the first management unit.
  • the second management unit may send a query response to the first management unit, the query response carrying capability information of the subnet supported by the second management unit.
  • FIG. 6 is a schematic diagram of a method for managing a network slice in a scenario of monitoring a subnet according to an embodiment of the present invention.
  • the network slice has been established and is running, and the demand information of the subnet corresponding to the demand information of the network slice at this time is the first sub-requirement information.
  • the method illustrated in Figure 6 includes portions 601 through 608, with portions 601 and 603 being optional.
  • the second management unit collects network performance of the subnet.
  • the second management unit sends an adjustment notification to the first management unit, where the adjustment notification is used to instruct the first management unit to adjust the demand information of the subnet.
  • the requirement information of the subnet herein refers to the first sub-requirement information described above.
  • the second management unit may send an adjustment notification to the second management unit to instruct the first management unit to adjust the first sub-requirement information.
  • the acquisition process of the capability information of the subnet supported by the second management unit is performed between the first management unit and the second management unit.
  • the obtaining process may refer to the detailed description of the process of acquiring the capability information of the subnet supported by the second management unit in the method shown in FIG. 5, and details are not described herein.
  • the first management unit determines the demand information of the subnet according to the demand information of the network slice.
  • the requirement information of the subnet herein refers to the second sub-requirement information.
  • the first management unit may adjust the first sub-requirement information according to the requirement information of the network slice to determine the second sub-requirement information.
  • the first management unit may determine the second sub-requirement information according to the requirement information of the network slice and the capability information of the subnet. That is to say, the determination of the demand information of the subnet in the 604 part can be understood as the adjustment of the demand information of the subnet.
  • the parts 605 to 608 are the same as or similar to the parts 506 to 509 in FIG. 5, and the detailed descriptions of the parts 506 to 509 can be referred to, and are not described herein.
  • the first management unit is a CDM
  • the second management unit is at least one of a CN-DM, a RAN-DM, or a TN-DM
  • the network slice requirement information is a network slice.
  • the SLA of the subnet, the SLA of the subnet is taken as an example, and the solution of the embodiment of the present invention is described.
  • the requirement information of the network slice is described as total-SLA or E2E-SLA
  • the requirement information of the subnet in the core domain is described as CN-SLA
  • the requirement information of the subnet in the access domain is described as RAN-SLA
  • the intranet of the transmission domain is described.
  • the demand information of the network is described as TN-SLA.
  • the SLA includes a latency and a report success ratio as an example.
  • the method illustrated in FIG. 7 may include portions 701 through 703 and portions 706; or may include portions 701, 702, 704, and 707; or may include portions 701, 702, 705, and 708; 701, 704, 706, and 707; or 701, 705, 706, and 708; or 701, 702, 704, 705, Sections 707 and 708; or, may include sections 701 to 708.
  • the illustrated method includes parts 701 to 708 as an example.
  • the CDM receives the network slice request, and the network slice request carries a total-SLA.
  • the CDM can receive a network slice request from the BSS/Customer.
  • the CDM determines at least one of the following based on the total-SLA: CN-SLA, RAN-SLA, or TN-SLA.
  • the CDM can determine CN-SLA, RAN-SLA, and TN-SLA based on the total-SLA.
  • CN-SLA includes CN-latency and CN-ratio
  • RAN-SLA includes RAN-latency and RAN-ratio
  • TN-SLA includes TN-latency and TN-ratio.
  • CN-latency 3ms
  • RAN-latency 2ms
  • TN-latency 5ms
  • CN-ratio ⁇ RAN-ratio ⁇ TN-ratio 96%.
  • the CDM negotiates with the CN-DM for the CN-SLA.
  • Section 703 may include portions 701a through 701c, or portion 703 may include portions 701a through 701g.
  • the specific implementation of the 701a to 701g portions is similar to the 403 to 409 portions of FIG. 4, and reference may be made to the detailed description of the 403 to 409 portions, and details are not described herein.
  • Sections 704 and 705 are similar to Section 703. You can refer to the implementation of Section 703, which is not described here.
  • the CDM needs to comprehensively consider the SLA of the subnet of all the domains to update.
  • CDM needs to re-determine CN-SLA, RAN-SLA and TN-SLA, and The CN-DM sends a new CN-SLA, sends a new RAN-SLA to the RAN-DM, and sends a new TN-SLA to the TN-DM.
  • the CDM does not need to send a new RAN-SLA to the RAN-DM; or if the new TN-SLA is relative to the pre-update TN - The SLA has not changed, and the CDM no longer needs to send a new TN-SLA to the TN-DM.
  • the CDM After performing parts 703 to 705, the CDM has completed the negotiation process with CN-DM, RAN-DM and TN-DM respectively.
  • Section 706 the establishment or modification process of the CN subnet is performed between the CDM and the CN-DM.
  • the CDM can send the negotiated CN-SLA to the CN-DM during the establishment or modification of the CN subnet.
  • the specific implementation of the establishing or modifying process may refer to the implementation process in part 410 to 412 of FIG. 4, and details are not described herein.
  • the 707 part and the 708 part are similar to the 706 part, and the implementation process of the 706 part can be referred to, and no further description is made here.
  • the network slice management method provided by the embodiment of the present invention may be implemented in a manner similar to the method shown in FIG. 7, and details are not described herein.
  • the embodiment of the present invention further provides another network slice management method, and a management unit and system based on the method.
  • the method includes: the first management unit sends a query request to the second management unit, the query request is used to request capability information of a subnet supported by the second management unit; and the second management unit sends the second management unit to the first management unit The capability information of the supported subnet; the first management unit determines the requirement information of the subnet according to the requirement information of the network slice and the capability information of the subnet supported by the second management unit, where the network slice includes at least one Subnet.
  • the method can be as shown in Figure 8A.
  • the same or similar content as the method shown in FIG. 3 can refer to the detailed description in FIG. 3; in addition, if it relates to the demand information about the network slice, the requirement information of the subnet, and the second management unit support
  • the capability information of a subnet refer to the detailed description above, and no further details are provided here.
  • the first management unit may further receive a notification from the second management unit, where the notification is used to instruct the first management unit to determine the demand information of the subnet; or The first management unit may further receive a network slice request from the third management unit, where the network slice request carries the network slice requirement information, and the network slice request is used to request to create or modify the network slice.
  • the first management unit may also send a subnet request to the second management unit, the subnet request carrying the demand information of the subnet requesting to request to create a subnet or modify an existing subnet.
  • the second management unit may create a subnet or modify an existing subnet, and send information of the created or modified subnet to the first management unit.
  • FIG. 8B The solution of the embodiment of the present invention is further described below with reference to FIG. 8B.
  • the method illustrated in Figure 8B includes portions 811 through 818, with portions 811, 812, and 815 being optional. It should be noted that the 811 part and the 812 part are two optional parts that are juxtaposed, and one of them is executed.
  • the 811 portion is the same as or similar to the 401 portion in FIG. 4, and reference may be made to the detailed description of the 401 portion, which is not described herein.
  • the 812 part and the 813 part are the same as or similar to the 602 part and 603 in FIG. 6, respectively, and may be referred to the detailed description of the 602 part and the 603 part, and are not described herein.
  • the first management unit determines the demand information of the subnet according to the requirement information of the network slice and the capability information of the subnet supported by the second management unit.
  • the 814 part is the same as or similar to the 505 part of FIG. 5, and the detailed description of the 505 part can be referred to; if the 812 part is executed, the 814 part is the same as or similar to the 604 part of FIG. 6, and the reference part 604 can be referred to. Detailed description of this, not to repeat here.
  • the parts 815 to 818 are the same as or similar to the parts of 605 to 608 in FIG. 6, and the detailed descriptions of parts 605 to 608 can be referred to, and are not described herein.
  • the determined subnet may be directly executed without executing the 815 part.
  • the demand information is sent to the second management unit in section 816, which facilitates rapid deployment of network slices.
  • the first management unit may also perform the 815 part after performing the 814 part, and send the requirement information of the subnet negotiated by the first management unit and the second management unit to the second management unit in the 816 part.
  • the first management unit may be a cross-domain management unit; the second management unit may be a core network domain management unit, an access network domain management unit, or a transport network domain management unit;
  • the snap-in can be BSS/Customer.
  • the solution provided by the embodiment of the present invention is mainly introduced from the perspective of interaction between different management units.
  • the first management unit and the second management unit include corresponding hardware structures and/or software modules for executing 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. Those skilled in the art can use different methods to implement the described work for each particular application. Yes, but this implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present invention.
  • the embodiment of the present invention may divide the function module by using the first management unit, the second management unit, and the like according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated in the function.
  • a processing module In a 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. 9A shows a possible schematic block diagram of the first management unit involved in the embodiment of the present invention.
  • the first management unit 900 includes a processing module 902 and a communication module 903.
  • the processing module 902 is configured to perform control management on the actions of the first management unit.
  • the processing module 902 is configured to support the first management unit to perform the processes 301 and 302 in FIG. 3, and the processes 401-403, 406, and 407 in FIG. And 410, processes 501, 502 and 505-507 in FIG. 5, processes 603-606 in FIG. 6, processes 701-708 in FIG. 7, processes 801 and 803 in FIG. 8A, process 811 in FIG. 8B and 813-816, and/or other processes for the techniques described herein.
  • the communication module 903 is configured to support communication between the first management unit and the second management unit or the third management unit.
  • the first management unit may further include a storage module 901 for storing program codes and data of the first management unit.
  • the processing module 902 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (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 1303 may be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name.
  • the communication interface may include multiple interfaces, for example, the first management unit and the second management may be included. An interface and/or other interface between the unit or the third management unit.
  • the storage module 901 can be a memory.
  • the first management unit involved in the embodiment of the present invention may be the first management unit shown in FIG. 9B.
  • the first management unit 910 includes a processor 912, a communication interface 913, and a memory 911.
  • the first management unit 910 may further include a bus 914.
  • the communication interface 913, the processor 912, and the memory 911 may be connected to each other through a bus 914.
  • the bus 914 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 914 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 9B, but it does not mean that there is only one bus or one type of bus.
  • the first management unit shown in FIG. 9A and FIG. 9B above may be the cross-domain management unit in FIG. 2.
  • FIG. 10A shows a possible schematic block diagram of a second management unit involved in the embodiment of the present invention.
  • the second 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 action of the second management unit.
  • the processing module 1002 is configured to support the second management unit to perform the process 303 in FIG. 3, the processes 404, 405, 408 in FIG. 409, 411, and 412, processes 503, 504, 506, 508, and 509 in FIG. 5, processes 601 to 603, 605, 607, and 608 in FIG. 6, processes 703 to 708 in FIG. 7, and processes in FIG. 8A 802, processes 813, 815, 817, and 818 in FIG. 8B, and/or other processes for the techniques described herein.
  • the communication module 1003 is configured to support communication between the second management unit and the first management unit.
  • the second management unit may further include a storage module 1001 for storing program codes and data of the second management unit.
  • the processing module 1002 may be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a 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 1303 may be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name. In a specific implementation, the communication interface may include multiple interfaces, for example, the second management unit and the first management unit may be included. Interface between and/or other interfaces.
  • the storage module 1001 may be a memory.
  • the second management unit may be the second management unit shown in FIG. 10B.
  • the second management unit 1010 includes a processor 1012, a communication interface 1013, and a memory 1011.
  • the second 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 PCI bus or an EISA bus or the like.
  • 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 FIG. 10B, but it does not mean that there is only one bus or one type of bus.
  • the second management unit shown in FIG. 10A and FIG. 10B above may be the core network domain management unit, the access network domain management unit or the transport network domain management unit in FIG. 2.
  • 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 can be located in the first management unit or the second management unit.
  • the processor and the storage medium may also exist as discrete components in the first management unit or the second management unit.
  • the functions described in the embodiments of the present invention may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, Use a computer, computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). )Wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a digital video disc (DVD)
  • DVD digital video disc
  • SSD solid state disk

Landscapes

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

Abstract

本发明实施例提供一种网络切片的管理方法，和基于这个方法的管理单元和系统。该方法包括：第一管理单元根据网络切片的需求信息确定子网的需求信息，其中，网络切片包括至少一个子网；第一管理单元向第二管理单元发送第一协商请求，第一协商请求携带子网的需求信息，第一协商请求用于查询第二管理单元对子网的需求信息的支持情况；第二管理单元确定第二管理单元能够支持子网的需求信息，或者，第二管理单元确定第二管理单元不能支持子网的需求信息。本发明实施例的方案中，不同管理单元之间能够对子网的需求信息进行协商，从而使得跨厂商场景下的网络切片的管理更加灵活有效。

Description

一种网络切片的管理方法、管理单元和系统 技术领域
本发明涉及通信技术领域，尤其涉及一种网络切片的管理方法、管理单元和系统。
背景技术
在研究未来的移动通信系统时，网络切片的概念被引入。网络切片可以理解为一种按需网络。一个物理网络可以在逻辑上被划分为多个网络切片，不同的网络切片可以用来承载不同的业务。例如，电力公司需要提供智能电表的业务，这种业务可以通过连接一系列机器对机器(Machine-to-Machine，M2M)设备的网络切片来实现。
现有的网络切片管理过程中，网络管理系统(Network Management System，NMS)一般根据网络切片的需求信息选择多个可用的网络功能实例，并将不同的网络功能实例的信息及相应的配置参数发送到不同的网元管理系统(Element Management System，EMS)进行部署和配置。然而，在跨厂商的场景下，NMS和EMS可能由不同的厂商提供，或者，不同的EMS可能由不同的厂商提供，不同的厂商之间无法获取对方的信息。这导致跨厂商的场景下，网络切片无法得到有效管理。
发明内容
本发明实施例描述了一种网络切片的管理方法、管理单元和系统，以期解决跨厂商的场景下，网络切片无法得到有效管理的问题。
一方面，本发明实施例提供一种网络切片的管理方法，该方法包括：第一管理单元根据网络切片的需求信息确定子网的需求信息，其中，该网络切片包括至少一个子网；第一管理单元向第二管理单元发送第一协商请求，第一协商请求携带子网的需求信息，第一协商请求用于查询第二管理单元对子网的需求信息的支持情况；对应的，第二管理单元确定第二管理单元能够支持该子网的需求信息，或者，第二管理单元确定第二管理单元不能支持该子网的需求信息。
本发明实施例的方案中，在网络切片的管理过程中，第一管理单元在确定子网的需求信息后，能够向第二管理单元发送第一协商请求，以查询第二管理单元对该子网的需求信息的支持情况，对应的，第二管理单元能够确定自身能否支持该子网的需求信息。因此，本发明实施例的方案中不同管理单元之间能够对子网的需求信息进行协商，从而使得跨厂商场景下的网络切片的管理更加灵活有效。
在一个可能的设计中，第一管理单元根据网络切片的需求信息确定子网的需求信息之前，第一管理单元还可以从第二管理单元接收通知，通知用于指示第一管理单元确定子网的需求信息；或者，第一管理单元还可以从第三管理单元接收网络切片请求，网络切片请求携带网络切片的需求信息，网络切片请求用于请求创建或修改网络切片。
在一种可能的实施方式中，第二管理单元向第一管理单元发送通知之前，还可以收集子网的网络性能。这种情况下，当子网的网络性能不能满足第二管理单元所支持的子网的 需求信息时，第二管理单元可以向第一管理单元发送上述通知。
在一个可能的设计中，第一管理单元根据网络切片的需求信息确定子网的需求信息之前，第一管理单元还可以从第二管理单元接收第二管理单元所支持的子网的能力信息。这种情况下，第一管理单元可以根据网络切片的需求信息以及子网的能力信息，确定子网的需求信息。
在一种可能的实施方式中，第一管理单元从第二管理单元接收第二管理单元所支持的子网的能力信息之前，还可以向第二管理单元发送查询请求，查询请求用于请求该子网的能力信息。
在一个可能的设计中，第一管理单元根据网络切片的需求信息确定子网的需求信息可以通过以下方式实现：第一管理单元可以将网络切片的需求信息分解为至少一个子网的需求信息。
在一个可能的设计中，第一管理单元向第二管理单元发送第一协商请求之后，还可以从第二管理单元接收协商响应，协商响应携带指示信息，该指示信息用于指示第二管理单元对子网的需求信息的支持情况，该支持情况为第二管理单元能够支持子网的需求信息，或者，该支持情况为第二管理单元不能支持子网的需求信息。即，该指示信息用于指示第二管理单元能够支持子网的需求信息，或者，该指示信息用于指示第二管理单元不能支持子网的需求信息。
在一种可能的实施方式中，上述支持情况为第二管理单元能够支持子网的需求信息，第一管理单元从第二管理单元接收协商响应后，还可以向第二管理单元发送子网请求，子网请求用于请求创建子网或修改现有的子网，子网请求携带上述子网的需求信息。或者，上述支持情况为第二管理单元不能支持子网的需求信息，第一管理单元从第二管理单元接收协商响应后，还可以向第二管理单元发送第二协商请求，第二协商请求携带更新的子网的需求信息，第二协商请求用于查询第二管理单元对更新的子网的需求信息的支持情况。
在一种可能的实施方式中，上述协商响应还可以携带第二管理单元所建议的子网的需求信息。例如，若上述支持情况为第二管理单元不能支持子网的需求信息，第一管理单元可以在接收协商响应后，根据网络切片的需求信息和第二管理单元所建议的子网的需求信息，确定更新的子网的需求信息。
另一方面，本发明实施例提供一种网络切片的管理方法，该方法包括：第一管理单元向第二管理单元发送查询请求，查询请求用于请求第二管理单元所支持的子网的能力信息；第二管理单元向第一管理单元发送第二管理单元所支持的子网的能力信息；第一管理单元根据网络切片的需求信息以及第二管理单元所支持的子网的能力信息，确定子网的需求信息，其中，上述网络切片包括至少一个子网。
本发明实施例的方案中，第一管理单元能够从第二管理单元获取第二管理单元所支持的子网的能力信息，并根据网络切片的需求信息以及第二管理单元所支持的子网的能力信息，确定子网的需求信息。因此，本发明实施例的方案中第一管理单元在确定子网的需求信息之前能先获取子网的能力信息，有利于确定合适的子网的需求信息，从而提高跨厂商场景下网络切片的管理效率。
在一个可能的设计中，第一管理单元向第二管理单元发送查询请求之前，第一管理单元还可以从第二管理单元接收通知，该通知用于指示第一管理单元确定子网的需求信息； 或者，第一管理单元还可以从第三管理单元接收网络切片请求，网络切片请求携带网络切片的需求信息，网络切片请求用于请求创建或修改该网络切片。
在一个可能的设计中，第一管理单元还可以向第二管理单元发送子网请求，子网请求携带子网的需求信息，子网请求用于请求创建子网或修改现有的子网。对应的，第二管理单元从第一管理单元接收子网请求后，可以创建子网或修改现有的子网，并向第一管理单元发送创建的或修改的子网的信息。
上述两个方面的方案中，第一管理单元可以为跨域管理单元；第二管理单元可以为核心网域管理单元、接入网域管理单元或传输网域管理单元。
上述两个方面的方案中，网络切片的需求信息是指用于确定一个网络切片的必要信息。子网的需求信息是指用于确定一个子网的必要信息。第二管理单元所支持的子网的能力信息是指第二管理单元所支持的子网的特征。
又一方面，本发明实施例提供一种第一管理单元，该第一管理单元具有实现上述方法设计中第一管理单元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，第一管理单元包括处理器，所述处理器被配置为支持第一管理单元执行上述方法中相应的功能。进一步的，第一管理单元还可以包括通信接口，所述通信接口用于支持第一管理单元与第二管理单元、第三管理单元或其他单元之间的通信。进一步的，第一管理单元还可以包括存储器，所述存储器用于与处理器耦合，其保存第一管理单元必要的程序指令和数据。
又一方面，本发明实施例提供一种第二管理单元，该第二管理单元具有实现上述方法设计中第二管理单元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，第二管理单元包括处理器，所述处理器被配置为支持第二管理单元执行上述方法中相应的功能。进一步的，第二管理单元还可以包括通信接口，所述通信接口用于支持第二管理单元与第一管理单元或其他单元之间的通信。进一步的，第二管理单元还可以包括存储器，所述存储器用于与处理器耦合，其保存第二管理单元必要的程序指令和数据。
再一方面，本发明实施例提供一种通信系统，该系统包括上述方面所述的第一管理单元和第二管理单元；或者，该系统包括上述方面所述的第一管理单元、第二管理单元和第三管理单元。
再一方面，本发明实施例提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
再一方面，本发明实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
相较于现有技术，本发明实施例的方案中，在网络切片的管理过程中，第一管理单元在确定子网的需求信息后，能够向第二管理单元发送第一协商请求，以查询第二管理单元对该子网的需求信息的支持情况，对应的，第二管理单元能够确定自身能否支持该子网的需求信息。因此，本发明实施例的方案中不同管理单元之间能够对子网的需求信息进行协商，从而使得跨厂商场景下的网络切片的管理更加灵活有效。
附图说明
图1为本发明实施例提供的一种可能的应用场景的示意图；
图2为本发明实施例提供的一种可能的网络架构的示意图；
图3为本发明实施例提供的一种网络切片的管理方法的通信示意图；
图4为本发明实施例提供的另一种网络切片的管理方法的通信示意图；
图5为本发明实施例提供的又一种网络切片的管理方法的通信示意图；
图6为本发明实施例提供的再一种网络切片的管理方法的通信示意图；
图7为本发明实施例提供的再一种网络切片的管理方法的通信示意图；
图8A为本发明实施例提供的再一种网络切片的管理方法通信示意图；
图8B为本发明实施例提供的再一种网络切片的管理方法通信示意图；
图9A为本发明实施例提供的一种第一管理单元的示意性框图；
图9B为本发明实施例提供的一种第一管理单元的结构示意图；
图10A为本发明实施例提供的一种第二管理单元的示意性框图；
图10B为本发明实施例提供的一种第二管理单元的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对于本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
下面首先结合图1和图2对本发明实施例适用的一些可能的应用场景及网络架构进行介绍。
图1为本发明实施例提供的一种可能的应用场景的示意图。其中，图1所示的应用场景中至少包括SO单元、NO单元、EM单元和Network/NF单元。下面对图1中所涉及的各个单元作简单介绍：
业务编排(Service Orchestrator，SO)单元，也可以称为业务编排和管理单元或业务管理单元，其功能主要包括：根据业务请求消息对业务(service)进行生命周期管理(例如实例化、更新、删除等)；service聚合；service的管理，例如service的故障、配置、计费、性能和安全(Fault,Configuration,Accounting,Performance,Security，FCAPS)管理；以及service和网络切片(Network Slice，NSL)之间的映射等。其中，service可以是一组用户能享有的指定服务水平协议(Service Level Agreement，SLA)的通信业务，例如移动宽带(Mobile Broadband，MBB)业务、语音业务、以及物联网(Internet of Things，IOT)业务(例如，智能停车业务、智能抄表业务等)等。示例性的，SO单元可以对网络切片所承载的业务进行管理。
网络编排(Network Orchestrator，NO)单元，也可以称为网络编排和管理单元或网络管理单元，其功能主要包括：网络切片的管理，例如网络切片的生命周期管理、网络切片 模板的管理等；网络切片和网络功能之间的映射；不同类型的网络资源的协调；不同运营商、不同网络供应商所提供的网络资源的协调，以使得不同网络供应商所提供的网络资源可以满足目标业务的需求，例如SLA的要求、关键性能指标(Key Performance Indicator，KPI)的要求、服务质量(Quality of Service，QoS)的要求等；不同供应商所提供的网络设备的统一编排；对外的应用程序接口(Application Program Interface，API)的提供，其中该API接口用于为第三方提供网络功能，以实现跨运营商的部署。
网元管理(Element Manager，EM)单元，也可以称为网络功能管理(Network Function Manager，NF-M)单元，其功能主要包括：网元或网络功能的生命周期管理(例如实例化、更新、删除等)；网元或网络功能的FCAPS管理等。
网络(Network)单元，其可以包括核心网单元、接入网单元或传输网单元中的至少一种。需要说明的是，上述网络单元可以由网络功能(Network Function，NF)单元所替代，或者，上述网络单元可以同时具有网络功能单元的功能。图1中所示的“Network/NF”单元表示具有网络单元的功能和/或网络功能单元的功能的单元。
需要说明的是，上述SO单元或NO单元可以部署在运营支撑系统(Operations Support System，OSS)中，上述SO单元或NO单元也可以独立于OSS部署。其中，OSS可以理解为面向设备和网络维护的支撑系统，负责单厂商的网络管理和多厂商的网络管理。
可以理解的是，上述对各个单元的功能介绍仅仅是一些举例说明，各个单元还可以具有其他功能，本发明实施例并不限定。
为描述方便，下文中，某一单元可以由其英文缩写所表示，例如，SO单元可以用SO表示，其它单元类似，后续不再赘述。
基于上述应用场景，图2示出了本发明实施例提供的一种可能的网络架构。如图2所示，该网络架构包括：业务支撑系统(Business Support System，BSS)、跨域管理(Cross Domain Manager，CDM)单元、核心网域管理(Core Network Domain Manager，CN-DM)单元、无线接入网域管理(Radio Access Network Domain Manager，RAN-DM)单元和传输网域管理(Transport Network Domain Manager，TN-DM)单元等，其中，无线接入网域管理单元也可以简称为接入网域管理单元。上述CDM与BSS相连，CDM还分别与CN-DM、RAN-DM及TN-DM相连。
下面分别对BSS、CDM、CN-DM和TN-DM作简单介绍。
BSS负责业务相关的管理(例如包括业务的运营、计费、客户关系管理等)，以及为终端提供业务。图2所示的网络架构中，BSS也可以由客户(Customer)所替代，或者，BSS可以同时具有Customer的功能。其中，Customer的功能包括：业务管理，以及为终端提供相应的业务。图2中，“BSS/Customer”表示具有BSS的功能和/或Customer的功能的单元。
CDM也可以称为跨域编排单元，具有网络切片的管理功能和/或NSL的编排功能。例如，CDM可以包括以下部分或全部功能：NSL的管理，例如网络切片的生命周期管理、网络切片模板的管理、网络切片的故障管理、网络切片的性能管理和网络切片的配置管理等；NSL与子网之间的映射，以及NSL与网络功能之间的映射；不同子域(例如核心网域、接入网域或传输网域)提供的网络资源或SLA信息的协调；各子域所提供的子网切片和网络功能的统一编排，该统一编排能使得各子域提供的子网切片或网络功能满足目标 业务的需求(例如，SLA的要求、KPI的要求以及QoS的要求等)。
其中，上述网络切片也可以称为端到端(End to End，E2E)网络切片，其可以至少包括核心网(Core Network，CN)部分、无线接入网(Radio Access Network，RAN)部分和传输网(Transport Network，TN)部分；或者，上述网络切片可以包括CN部分、RAN部分或TN部分中的任意两项；或者，上述网络切片可以表示CN部分的网络切片、RAN部分的网络切片或TN部分的网络切片。可以理解的是，本发明实施例所涉及的网络切片还可能具有其他实施方式，本发明实施例并不限定。
CN-DM具有核心网域内网络切片的子网管理功能和/或核心网域内网络切片的子网编排功能。例如，CN-DM可以包括以下部分或全部功能：核心网域内网络切片的子网的管理，例如包括子网的生命周期管理(包括创建、更新、删除等)、子网的故障管理、子网的性能管理、子网的配置管理等；核心网域内业务的管理，例如包括业务的生命周期管理、业务的故障管理、业务的性能管理、业务的配置管理等；核心网域内网络资源的协调，以用于统一编排。
RAN-DM具有接入网域内网络切片的子网管理功能和/或接入网域内网络切片的子网编排功能。例如，RAN-DM可以包括以下部分或全部功能：接入网域内网络切片的子网的管理，例如包括子网的生命周期管理(包括创建、更新、删除等)、子网的故障管理、子网的性能管理、子网的配置管理等；接入网域内业务的管理，例如包括业务的生命周期管理、业务的故障管理、业务的性能管理、业务的配置管理等；接入网域内网络资源的协调，以用于统一编排。
TN-DM具有传输网域内网络切片的子网管理功能和/或传输网域内网络切片的子网编排功能。例如，TN-DM可以包括以下部分或全部功能：传输网域内网络切片的子网的管理，例如包括子网的生命周期管理(包括创建、更新、删除等)、子网的故障管理、子网的性能管理、子网的配置管理等；传输网域内业务的管理，例如包括业务的生命周期管理、业务的故障管理、业务的性能管理、业务的配置管理等；传输网域内网络资源的协调，以用于统一编排。
其中，上述CDM、CN-DM、RAN-DM和TN-DM可以都部署在SO中或都部署在NO中；或者，上述CDM可以部署在NO中，CN-DM、RAN-DM和TN-DM可以都部署在EM中；或者，上述CDM可以部署在SO中，CN-DM、RAN-DM和TN-DM可以都部署在NO中。
下面将基于上面所述的本发明实施例涉及的共性方面，对本发明实施例进一步详细说明。
现有的网络切片管理过程中，NMS一般根据网络切片的需求信息选择多个可用的网络功能实例，并将不同的网络功能实例的信息及相应的配置参数发送到不同的EMS进行部署和配置。然而，在跨厂商的场景下，NMS和EMS可能由不同的厂商提供，或者，不同的EMS可能由不同的厂商提供，不同的厂商之间无法获取对方的网络功能实例的信息和配置参数。这导致跨厂商的场景下，网络切片无法得到有效管理。
有鉴于此，本发明实施例提供一种网络切片的管理方法，和基于这个方法的管理单元及系统。该方法包括：第一管理单元根据网络切片的需求信息确定子网的需求信息，其中，该网络切片包括至少一个子网；第一管理单元向第二管理单元发送第一协商请求，第一协 商请求携带子网的需求信息，第一协商请求用于查询第二管理单元对子网的需求信息的支持情况；对应的，第二管理单元确定第二管理单元能够支持该子网的需求信息，或者，第二管理单元确定第二管理单元不能支持该子网的需求信息。本发明实施例的方案中，在网络切片的管理过程中，第一管理单元在确定子网的需求信息后，能够向第二管理单元发送第一协商请求，以查询第二管理单元对该子网的需求信息的支持情况，对应的，第二管理单元能够确定自身能否支持该子网的需求信息。因此，本发明实施例的方案中不同管理单元之间能够对子网的需求信息进行协商，从而使得跨厂商场景下的网络切片的管理更加灵活有效。
上述网络切片的需求信息是指用于确定一个网络切片的必要信息。例如，网络切片的需求信息可以包括以下部分或全部内容：网络切片的类型(例如，增强移动宽带(enhanced Mobile Broadband，eMBB)、海量机器类通信(massive Machine Type Communication，mMTC)、高可靠低时延通信(Ultra-Reliable and Low Latency Communication，URLLC)等)、业务的SLA要求或网络的KPI等。其中，业务的SLA要求或网络的KPI可以包括以下至少一项：时延(latency)、上报成功率(report success ratio)、下发成功率(command success ratio)、覆盖(coverage)、容量(capacity)、可靠性(reliability)或吞吐量(throughput)。其中，上报成功率可以指上行包发送成功的比例；下发成功率可以指下行包发送成功的比例；覆盖可以指终端的分布区域；容量可以指可容纳的终端数量。
上述子网的需求信息是指用于确定一个子网的必要信息。例如，子网的需求信息可以包括以下部分或全部内容：业务的SLA要求或网络的KPI等。其中，业务的SLA要求或网络的KPI可以包括以下至少一项：时延(latency)、上报成功率(report success ratio)、下发成功率(command success ratio)、覆盖(coverage)、容量(capacity)、可靠性(reliability)或吞吐量(throughput)。
下面结合附图3，对本发明实施例提供的方案进行说明。其中，图3所示的方法，以应用图2所示的网络架构为例，进行说明。图3所示的方法包括：301部分～303部分。
在301部分，第一管理单元根据网络切片的需求信息确定子网的需求信息。
其中，网络切片包括至少一个子网。可选的，子网(subnet)也可以称为子网络(subnetwork)。
在一个示例中，第二管理单元根据网络切片的需求信息确定子网的需求信息之前，还可以从第三管理单元接收网络切片请求，该网络切片请求携带网络切片的需求信息，该网络切片请求用于请求创建或修改该网络切片。
例如，在初始创建网络切片的场景下，第三管理单元向第二管理单元发送网络切片请求，该网络切片请求携带初始的网络切片的需求信息，且该网络切片请求用于请求创建该网络切片。对应的，第二管理单元可以在创建网络切片的过程中，根据初始的网络切片的需求信息确定子网的需求信息。即，在初始创建网络切片的场景下，第三管理单元所发送的网络切片请求触发第二管理单元确定子网的需求信息。其中，上述创建网络切片也可以理解为实例化网络切片。
又例如，在修改网络切片的场景下，此时，网络切片已经建立，第三管理单元可能由于所接收到的业务需求发生变化等原因，向第二管理单元发送网络切片请求，该网络切片请求携带更新的网络切片的需求信息，且该网络切片请求用于请求修改该网络切片。对应 的，第二管理单元可以在修改网络切片的过程中，根据更新的网络切片的需求信息确定子网的需求信息。即，在修改网络切片的场景下，第三管理单元所发送的网络切片请求触发第二管理单元确定子网的需求信息。其中，上述修改网络切片也可以理解为更新网络切片。
在另一个示例中，第一管理单元根据网络切片的需求信息确定子网的需求信息之前，还可以从第二管理单元接收通知，该通知用于指示第一管理单元确定该子网的需求信息。
在一种可能的实施方式中，第二管理单元向第一管理单元发送该通知之前，还可以收集该子网的网络性能，当该子网的网络性能不能满足第二管理单元所支持的子网的需求信息时，第二管理单元可以向第一管理单元发送该通知。
例如，在第二管理单元对子网进行监测的场景下，此时，网络切片已经建立并运行，且此时与网络切片的需求信息对应的子网的需求信息为第一子需求信息。第二管理单元可以收集子网的网络性能，当该子网的网络性能不能满足上述第一子需求信息时，第二管理单元可以向第一管理单元发送通知，用于指示第一管理单元对第一子需求信息进行调整，以确定第二子需求信息。其中，第二子需求信息为第一管理单元接收上述通知后确定的子网的需求信息。即，在第二管理单元对子网进行监测的场景下，第二管理单元所发送的通知触发第二管理单元确定子网的需求信息，这种场景下子网的需求信息的确定可以理解为对子网的需求信息的调整。
在一个示例中，第一管理单元根据网络切片的需求信息确定子网的需求信息之前，第一管理单元还可以从第二管理单元接收第二管理单元所支持的子网的能力信息；这种情况下，第一管理单元可以根据网络切片的需求信息以及该子网的能力信息，确定上述子网的需求信息。
在一种可能的实施方式中，第一管理单元从第二管理单元接收第二管理单元所支持的子网的能力信息之前，还可以向第二管理单元发送查询请求，该查询请求用于请求该子网的能力信息。
其中，上述子网的能力信息是指第二管理单元所支持的子网的特征。例如，子网的能力信息可以包括子网的类型、子网的功能、子网所支持的区域、子网所支持的容量、子网所支持的业务或网络参数(例如SLA)或子网的需求信息范围等。
在一个示例中，第一管理单元可以通过以下方式确定子网的需求信息：第一管理单元可以将该网络切片的需求信息分解为至少一个上述子网的需求信息。
在302部分，第一管理单元向第二管理单元发送第一协商请求，该第一协商请求携带该子网的需求信息。
其中，该第一协商请求用于查询第二管理单元对该子网的需求信息的支持情况。例如，该第一协商请求可以用于查询第二管理单元是否支持该子网的需求信息。
在303部分，第二管理单元确定第二管理单元能够支持子网的需求信息，或者，第二管理单元确定第二管理单元不能支持子网的需求信息。
在一个示例中，第二管理单元还可以向第一管理单元发送协商响应，协商响应携带指示信息，该指示信息用于指示第二管理单元对该子网的需求信息的支持情况，该支持情况为第二管理单元能够支持该子网的需求信息，或者，该支持情况为第二管理单元不能支持该子网的需求信息。其中，该上述协商响应可以称为第一协商响应。
在一种可能的实施方式中，上述支持情况为第二管理单元能够支持该子网的需求信 息，即该指示信息用于指示第二管理单元能够支持上述子网的需求信息，第一管理单元从第二管理单元接收第一协商响应之后，还可以向第二管理单元发送子网请求，该子网请求用于请求创建上述子网或修改现有的子网，该子网请求携带上述子网的需求信息。
在另一种可能的实施方式中，上述支持情况为第二管理单元不能支持该子网的需求信息，即该指示信息用于指示第二管理单元不能支持上述子网的需求信息，第一管理单元从第二管理单元接收第一协商响应之后，还可以更新上述子网的需求信息，并向第二管理单元发送第二协商请求，第二协商请求携带更新的子网的需求信息，第二协商请求用于查询第二管理单元对该更新的子网的需求信息的支持情况。
对应的，第二管理单元从第一管理单元接收第二协商请求之后，还可以确定自身能否支持该更新的子网的需求信息，进一步的，还可以向第一管理单元发送第二协商响应。具体实施过程与303部分相似，可以参考303部分中上述详细描述。
在一个示例中，上述第一协商响应还可以携带第二管理单元所建议的子网的需求信息。例如，若第二管理单元确定不能支持上述子网的需求信息，第二管理单元除在第一协商响应中携带指示信息外，还可以携带第二管理单元所建议的子网的需求信息，这样第一管理单元在更新上述子网的需求信息时，可以考虑第二管理单元所建议的子网的需求信息，从而有利于第一管理单元和第二管理单元对子网的需求信息达成一致。
需要说明的是，第一管理单元和第二管理单元之间可以通过连续发送协商请求和协商响应的方式，对子网的需求信息进行协商，直到第二管理单元能够支持第一管理单元所发送的子网的需求信息。
上述图3所示的方案中，第一管理单元可以为跨域管理单元；第二管理单元可以为核心网域管理单元、接入网域管理单元或传输网域管理单元；第三管理单元可以为BSS/Customer。
下面结合图4～图6，在图3所示方法的基础上，对本发明实施例提供的方案做进一步说明。图4～图6所示方法中，与图3所示方法相同或相似的内容可以参考图3中的详细描述，此处不做赘述。图4～图6所示的方法中，其中，若涉及到，有关网络切片的需求信息、子网的需求信息和第二管理单元所支持的能力信息的介绍可以参考上文中的详细描述，此处不做赘述。
图4为本发明实施例提供的创建或修改网络切片的场景下的一种网络切片的管理方法。图4所示的方法包括401部分～412部分，其中，406部分～409部分为可选的部分。
在401部分，第一管理单元接收网络切片请求，网络切片请求携带网络切片的需求信息。
其中，网络切片请求用于请求创建或修改网络切片。在创建网络切片的场景下，该网络切片的需求信息可以为初始的网络切片的需求信息；在修改网络切片的场景下，该网络切片的需求信息可以为更新的网络切片的需求信息。
在402部分，第一管理单元根据网络切片的需求信息确定子网的需求信息。
在一个示例中，第一管理单元可以将网络切片的需求信息分解为至少一个子网的需求信息。可以理解的是，网络切片可能包括一个、两个或更多子网，本发明实施例并不限定。例如，若网络切片包括核心网域的子网，第一管理单元可以将网络切片的需求信息分解为核心网域的子网的需求信息；当然，若网络切片包括接入网域的子网或传输网域的子网， 第一管理单元也可以将网络切片的需求信息分解为对应域的子网的需求信息。又例如，若网络切片包括核心网域的子网、接入网域的子网和核心网域的子网，第一管理单元可以将网络切片的需求信息分解为核心网域的子网的需求信息、接入网域的子网的需求信息和传输网域的子网的需求信息。
在403部分，第一管理单元向第二管理单元发送第一协商请求，第一协商请求携带子网的需求信息，第一协商请求用于查询第二管理单元对子网的需求信息的支持情况。
例如，该子网的需求信息为核心网域的子网的需求信息，第二管理单元为核心网域管理单元，第一管理单元可以通过第一协商请求向核心网域管理单元发送核心网域的子网的需求信息，以查询核心网域管理单元对核心网域的子网的需求信息的支持情况。当然，若该子网的需求信息为接入网域的子网的需求信息，第二管理单元为接入网域管理单元；或者，若该子网的需求信息为传输网域的子网的需求信息，第二管理单元为传输网域管理单元；第一管理单元也可以将对应域的子网的需求信息发送给第二管理单元。
又例如，若第一管理单元在402部分中，将网络切片的需求信息分解为核心网域的子网的需求信息、接入网域的子网的需求信息和传输网域的子网的需求信息，第一管理单元也可以将对应域的子网的需求信息分别发送给核心网域管理单元、接入网域管理单元和传输网域管理单元。这种情况下，第一管理单元分别与不同的第二管理单元对对应域的子网的需求信息进行协商。
在404部分，第二管理单元确定第二管理单元能够支持子网的需求信息，或者，第二管理单元确定第二管理单元不能支持子网的需求信息。
在405部分，第二管理单元向第一管理单元发送第一协商响应，第一协商响应携带指示信息。
例如，若第二管理单元在404部分中确定第二管理单元能够支持子网的需求信息，则该指示信息用于指示第二管理单元能够支持子网的需求信息，这种情况下，该指示信息可以理解为肯定指示；或者，若第二管理单元在404部分中确定第二管理单元不能支持子网的需求信息，则该指示信息用于指示第二管理单元不能支持子网的需求信息，这种情况下，该指示信息可以理解为否定指示。
在一个示例中，若上述指示信息为否定指示，则第一协商响应中还可以携带第二管理单元所建议的子网的需求信息。
若第二管理单元在405部分中向第一管理单元发送肯定指示，则接下来执行410部分；若第二管理单元在405部分中向第一管理单元发送否定指示，则接下来执行406部分。
在406部分，第一管理单元更新子网的需求信息。
例如，第一管理单元可以根据网络切片的需求信息以及第二管理单元所建议的子网的需求信息，更新子网的需求信息。
在407部分，第一管理单元向第二管理单元发送第二协商请求，第二协商请求携带更新的子网的需求信息，第二协商请求用于查询第二管理单元对更新的子网的需求信息的支持情况。
在408部分，第二管理单元确定第二管理单元能够支持更新的子网的需求信息，或者，第二管理单元确定第二管理单元不能支持更新的子网的需求信息。
在409部分，第二管理单元向第一管理单元发送第二协商响应，第二协商响应携带指 示信息。
例如，若第二管理单元在408部分中确定第二管理单元能够支持更新的子网的需求信息，则该指示信息为肯定指示；若第二管理单元在408部分中确定第二管理单元不能支持更新的子网的需求信息，则该指示信息为否定指示。
若第二管理单元在409部分中向第一管理单元发送肯定指示，则接下来执行410部分；若第二管理单元在409部分中向第一管理单元发送否定指示，则接下来重复执行406部分～409部分，直到第二管理单元向第一管理单元发送肯定指示后，执行410部分。
在410部分，第一管理单元向第二管理单元发送子网请求，子网请求用于请求创建子网或修改现有的子网。
其中，子网请求携带子网的需求信息。需要说明的是，该子网的需求信息为第一管理单元与第二管理单元协商一致的子网的需求信息。例如，若第二管理单元在405部分中向第一管理单元发送肯定指示，则该子网的需求信息为第一管理单元在402部分中确定的子网的需求信息。又例如，若第二管理单元在405部分中向第一管理单元发送否定指示，则该子网的需求信息为第一管理单元在406部分中更新的子网的需求信息。可以理解的是，在后面这种情况中，第一管理单元可能仅在406部分～409部分被执行一次后，即在409部分中接收到第二管理单元发送的肯定指示；或者，第一管理单元也可能在406部分～409部分被执行两次以上后，才在409部分最后一次执行时接收到第二管理单元发送的肯定指示。不管哪种情况，该更新的子网的需求信息为第一管理单元执行410部分前最近一次更新的子网的需求信息。
在411部分，第二管理单元创建子网或修改现有的子网。
例如，在不存在现有子网的情况下，第二管理单元可以根据子网请求中携带的子网的需求信息创建子网。又例如，第二管理单元可以重用现有的子网，其中，第二管理单元可以在重用的过程中修改现有的子网以满足子网请求中携带的子网的需求信息。
在412部分，第二管理单元向第一管理单元发送创建的或修改的子网的信息。
需要说明的是，图4所示方法中403部分～409部分可以称为子网的需求信息的协商过程。可以理解的是，该协商过程中，第一管理单元和第二管理单元之间可能需要就子网的需求信息进行一次、两次或更多次的协商才能达成一致。
图5为本发明实施例提供的创建或修改网络切片的场景下的另一种网络切片的管理方法。图5所示的方法包括501部分～509部分，其中，502部分和503部分为可选的部分。
图5中，501部分、505部分和507部分～509部分分别与图4中的401部分、402部分和410部分～412部分相同或相似，可以参考401部分、402部分和410部分～412部分的详细描述；506部分与图4中的子网的需求信息的协商过程相同或相似，可以参考图4中子网的需求信息的协商过程的详细描述；此处不做赘述。
图5所示方法与图4所示方法的不同之处在于：图5所示的方法，在第一管理单元根据网络切片的需求信息确定子网的需求信息之前，还包括第二管理单元所支持的子网的能力信息的获取过程；进一步的，第一管理单元可以根据网络切片的需求信息以及上述子网的能力信息确定子网的需求信息。其中，上述获取过程可以包括504部分，或者，可以包括503部分和504部分，或者，可以包括502部分～504部分。
在502部分，第一管理单元向第二管理单元发送查询请求，该查询请求用于查询第二 管理单元所支持的子网的能力信息。
在503部分，第二管理单元评估第二管理单元所支持的子网的能力信息。
在504部分，第二管理单元向第一管理单元发送第二管理单元所支持的子网的能力信息。例如，第二管理单元可以向第一管理单元发送查询响应，该查询响应携带第二管理单元所支持的子网的能力信息。
图6为本发明实施例提供的监测子网的场景下的一种网络切片的管理方法。图6所示的方法中，网络切片已经建立并运行，且此时与网络切片的需求信息对应的子网的需求信息为第一子需求信息。图6所示的方法包括601部分～608部分，其中，601部分和603部分为可选的部分。
在601部分，第二管理单元收集子网的网络性能。
在602部分，第二管理单元向第一管理单元发送调整通知，该调整通知用于指示第一管理单元调整子网的需求信息。
具体的，这里的子网的需求信息是指上述第一子需求信息。当子网的网络性能不能满足上述第一子需求信息时，第二管理单元可以向第二管理单元发送调整通知，以指示第一管理单元对第一子需求信息进行调整。
在603部分，第一管理单元和第二管理单元之间执行第二管理单元所支持的子网的能力信息的获取过程。
具体的，该获取过程可以参考图5所示方法中第二管理单元所支持的子网的能力信息的获取过程的详细描述，此处不做赘述。
在604部分，第一管理单元根据网络切片的需求信息确定子网的需求信息。
具体的，这里的子网的需求信息指第二子需求信息。第一管理单元接收调整通知后，可以根据网络切片的需求信息对第一子需求信息进行调整，以确定第二子需求信息。可选的，在执行603部分的情况下，第一管理单元可以根据网络切片的需求信息和上述子网的能力信息，确定第二子需求信息。也就是说，604部分中子网的需求信息的确定可以理解为子网的需求信息的调整。
605部分～608部分与图5中的506部分～509部分相同或相似，可以参考506部分～509部分的详细描述，此处不做赘述。
下面结合图7，在创建网络切片的场景下，以第一管理单元为CDM，第二管理单元为CN-DM、RAN-DM或TN-DM中的至少一个，网络切片的需求信息为网络切片的SLA，子网的需求信息为子网的SLA为例，对本发明实施例的方案进行说明。
其中，网络切片的需求信息描述为total-SLA或E2E-SLA，核心网域内子网的需求信息描述为CN-SLA，接入网域内子网的需求信息描述为RAN-SLA，传输网域内子网的需求信息描述为TN-SLA。示例性的，下面以SLA包括latency和report success ratio为例进行说明。
图7所示的方法可以包括701部分～703部分和706部分；或者，可以包括701部分、702部分、704部分和707部分；或者，可以包括701部分、702部分、705部分和708部分；或者，可以包括701部分～704部分、706部分和707部分；或者，可以包括701部分～703部分、705部分、706部分和708部分；或者，可以包括701部分、702部分、704部分、705部分、707部分和708部分；或者，可以包括701部分～708部分。下面以图7 所示的方法包括701部分～708部分为例进行说明。
在701部分，CDM接收网络切片请求，网络切片请求携带total-SLA。
例如，CDM可以从BSS/Customer接收网络切片请求。
在一个示例中，total-SLA包括total-latency和total-report success ratio，其中，为描述方便，下文中total-report success ratio表示为total-ratio，其它与report success ratio相关的内容也可以类似表示，后续不在赘述。例如，total latency＝10毫秒(ms)，total-ratio＝96％。
在702部分，CDM根据total-SLA确定以下至少一项：CN-SLA、RAN-SLA或TN-SLA。
例如，CDM可以根据total-SLA确定CN-SLA、RAN-SLA和TN-SLA。
在一个示例中，与701部分中的total相对应，CN-SLA包括CN-latency和CN-ratio，RAN-SLA包括RAN-latency和RAN-ratio，TN-SLA包括TN-latency和TN-ratio。例如，CN-latency＝3ms，RAN-latency＝2ms，TN-latency＝5ms；CN-ratio×RAN-ratio×TN-ratio＝96％。
在703部分中，CDM与CN-DM对CN-SLA进行协商。
703部分可以包括701a部分～701c部分，或者，703部分可以包括701a部分～701g部分。其中，701a部分～701g部分的具体实施与图4的403部分～409部分相似，可以参考403部分～409部分的详细描述，此处不做赘述。
704部分和705部分与703部分相似，可以参考703部分的实施过程，此处不做赘述。
需要说明的是，当某一网域或某两个以上网域的子网的SLA需要更新时，CDM需要综合考虑所有网域的子网的SLA来进行更新。例如，当CN-DM不能支持CN-SLA，而RAN-DM能够支持RAN-SLA且TN-DM能够支持TN-SLA时，CDM需要重新确定CN-SLA、RAN-SLA和TN-SLA，并向CN-DM发送新的CN-SLA，向RAN-DM发送新的RAN-SLA，向TN-DM发送新的TN-SLA。可以理解的是，若新的RAN-SLA相对于更新前的RAN-SLA没有变化，CDM不用再向RAN-DM发送新的RAN-SLA；或者，若新的TN-SLA相对于更新前的TN-SLA没有变化，CDM不用再向TN-DM发送新的TN-SLA。
在执行703部分～705部分后，CDM已分别完成了与CN-DM、RAN-DM和TN-DM的协商过程。
在706部分，CDM与CN-DM之间进行CN子网的建立或修改过程。
CDM可以在CN子网的建立或修改过程中将协商一致的CN-SLA发送给CN-DM。具体的，该建立或修改过程的具体实施可以参考图4中410部分～412部分的实施过程，此处不做赘述。
707部分和708部分与706部分相似，可以参考706部分的实施过程，此处不做赘述。
需要说明的是，在修改网络切片的场景或监测子网的场景下，本发明实施例提供的网络切片的管理方法也可以类似图7所示的方法进行实施，此处不做赘述。
为提高跨厂商场景下网络切片的管理效率，本发明实施例还提供另一种网络切片的管理方法，和基于该方法的管理单元和系统。该方法包括：第一管理单元向第二管理单元发送查询请求，该查询请求用于请求第二管理单元所支持的子网的能力信息；第二管理单元向第一管理单元发送第二管理单元所支持的子网的能力信息；第一管理单元根据网络切片的需求信息以及第二管理单元所支持的子网的能力信息，确定该子网的需求信息，其中，该网络切片包括至少一个该子网。例如，该方法可以如图8A所示。
本方法中，与图3所示方法相同或相似的内容可以参考图3中的详细描述；此外，若涉及到，有关网络切片的需求信息、子网的需求信息和第二管理单元所支持的子网的能力信息的介绍可以参考上文中的详细描述，此处不做赘述。
在一个示例中，第一管理单元向第二管理单元发送查询请求之前，第一管理单元还可以从第二管理单元接收通知，该通知用于指示第一管理单元确定子网的需求信息；或者，第一管理单元还可以从第三管理单元接收网络切片请求，网络切片请求携带网络切片的需求信息，网络切片请求用于请求创建或修改该网络切片。
在一个示例中，第一管理单元还可以向第二管理单元发送子网请求，该子网请求携带子网的需求信息，该子网请求用于请求创建子网或修改现有的子网。对应的，第二管理单元接收子网请求后，可以创建子网或修改现有的子网，并向第一管理单元发送创建的或修改的子网的信息。
下面结合图8B对本发明实施例的方案做进一步说明。图8B所示的方法包括811部分～818部分，其中811部分、812部分和815部分为可选的部分。需要说明的是，811部分和812部分为并列的两个可选部分，择其一进行执行。
811部分与图4中的401部分相同或相似，可以参考401部分的详细描述，此处不做赘述。
812部分和813部分分别与图6中的602部分和603相同或相似，可以参考602部分和603部分的详细描述，此处不做赘述。
在814部分中，第一管理单元根据网络切片的需求信息及第二管理单元所支持的子网的能力信息确定子网的需求信息。
若执行811部分，则814部分与图5中的505部分相同或相似，可以参考505部分的详细描述；若执行812部分，则814部分与图6中的604部分相同或相似，可以参考604部分的详细描述，此处不做赘述。
815部分～818部分与图6中的605部分～608部分相同或相似，可以参考605部分～608部分的详细描述，此处不做赘述。
需要说明的是，由于第一管理单元在执行814部分前，已获取第二管理单元所支持的子网的能力信息，因此在执行814部分后，可以不执行815部分，直接将确定的子网的需求信息在816部分中发送给第二管理单元，有利于网络切片的快速部署。或者，第一管理单元也可以在执行814部分后，执行815部分，将第一管理单元和第二管理单元协商一致的子网的需求信息在816部分中发送给第二管理单元。
上述图8A或图8B所示的方案中，第一管理单元可以为跨域管理单元；第二管理单元可以为核心网域管理单元、接入网域管理单元或传输网域管理单元；第三管理单元可以为BSS/Customer。
上述主要从不同管理单元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是，第一管理单元、第二管理单元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本发明中所公开的实施例描述的各示例的单元及算法步骤，本发明实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功 能，但是这种实现不应认为超出本发明实施例的技术方案的范围。
本发明实施例可以根据上述方法示例对第一管理单元、第二管理单元等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的模块的情况下，图9A示出了本发明实施例中所涉及的第一管理单元的一种可能的示意性框图。第一管理单元900包括：处理模块902和通信模块903。处理模块902用于对第一管理单元的动作进行控制管理，例如，处理模块902用于支持第一管理单元执行图3中的过程301和302，图4中的过程401～403、406、407和410，图5中的过程501、502和505～507，图6中的过程603～606，图7中的过程701～708，图8A中的过程801和803，图8B中的过程811和813～816，和/或用于本文所描述的技术的其它过程。通信模块903用于支持第一管理单元与第二管理单元或第三管理单元的通信。第一管理单元还可以包括存储模块901，用于存储第一管理单元的程序代码和数据。
其中，处理模块902可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块1303可以是通信接口、收发器或收发电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口，例如可以包括：第一管理单元单元和第二管理单元或第三管理单元之间的接口和/或其他接口。存储模块901可以是存储器。
当处理模块902为处理器，通信模块903为通信接口，存储模块901为存储器时，本发明实施例所涉及的第一管理单元可以为图9B所示的第一管理单元。
参阅图9B所示，该第一管理单元910包括：处理器912、通信接口913、存储器911。可选的，第一管理单元910还可以包括总线914。其中，通信接口913、处理器912以及存储器911可以通过总线914相互连接；总线914可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线914可以分为地址总线、数据总线、控制总线等。为便于表示，图9B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图9A和图9B所示的第一管理单元可以是图2中的跨域管理单元。
在采用集成的单元的情况下，图10A示出了本发明实施例中所涉及的第二管理单元的一种可能的示意性框图。第二管理单元1000包括：处理模块1002和通信模块1003。处理模块1002用于对第二管理单元的动作进行控制管理，例如，处理模块1002用于支持第二管理单元执行图3中的过程303，图4中的过程404、405、408、 409、411和412，图5中的过程503、504、506、508和509，图6中的过程601～603、605、607和608，图7中的过程703～708，图8A中的过程802，图8B中的过程813、815、817和818，和/或用于本文所描述的技术的其它过程。通信模块1003用于支持第二管理单元与第一管理单元的通信。第二管理单元还可以包括存储模块1001，用于存储第二管理单元的程序代码和数据。
其中，处理模块1002可以是处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块1303可以是通信接口、收发器或收发电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口，例如可以包括：第二管理单元和第一管理单元之间的接口和/或其他接口。存储模块1001可以是存储器。
当处理模块1002为处理器，通信模块1003为通信接口，存储模块1001为存储器时，本发明实施例所涉及的第二管理单元可以为图10B所示的第二管理单元。
参阅图10B所示，该第二管理单元1010包括：处理器1012、通信接口1013、存储器1011。可选的，第二管理单元1010还可以包括总线1014。其中，通信接口1013、处理器1012以及存储器1011可以通过总线1014相互连接；总线1014可以是PCI总线或EISA总线等。所述总线1014可以分为地址总线、数据总线、控制总线等。为便于表示，图10B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图10A和图10B所示的第二管理单元可以是图2中的核心网域管理单元、接入网域管理单元或传输网域管理单元。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于第一管理单元或第二管理单元中。当然，处理器和存储介质也可以作为分立组件存在于第一管理单元或第二管理单元中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专 用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如，固态硬盘(Solid State Disk，SSD))等。
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (27)

  1. 一种网络切片的管理方法，其特征在于，包括：
    第一管理单元根据网络切片的需求信息确定子网的需求信息，其中，所述网络切片包括至少一个所述子网；
    所述第一管理单元向第二管理单元发送第一协商请求，所述第一协商请求携带所述子网的需求信息，所述第一协商请求用于查询所述第二管理单元对所述子网的需求信息的支持情况。
  2. 根据权利要求1所述的方法，其特征在于，所述第一管理单元根据网络切片的需求信息确定子网的需求信息之前，还包括：
    所述第一管理单元从所述第二管理单元接收通知，所述通知用于指示所述第一管理单元确定所述子网的需求信息；或者，
    所述第一管理单元从第三管理单元接收网络切片请求，所述网络切片请求携带所述网络切片的需求信息，所述网络切片请求用于请求创建或修改所述网络切片。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一管理单元根据网络切片的需求信息确定子网的需求信息之前，还包括：
    所述第一管理单元从所述第二管理单元接收所述第二管理单元所支持的所述子网的能力信息；
    所述第一管理单元根据网络切片的需求信息确定子网的需求信息，包括：
    所述第一管理单元根据所述网络切片的需求信息以及所述子网的能力信息，确定所述子网的需求信息。
  4. 根据权利要求3所述的方法，其特征在于，所述第一管理单元从所述第二管理单元接收所述第二管理单元所支持的所述子网的能力信息之前，还包括：
    所述第一管理单元向所述第二管理单元发送查询请求，所述查询请求用于请求所述子网的能力信息。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一管理单元向第二管理单元发送第一协商请求之后，还包括：
    所述第一管理单元从所述第二管理单元接收协商响应，所述协商响应携带指示信息，所述指示信息用于指示所述第二管理单元对所述子网的需求信息的支持情况，所述支持情况为所述第二管理单元能够支持所述子网的需求信息，或者，所述支持情况为所述第二管理单元不能支持所述子网的需求信息。
  6. 根据权利要求5所述的方法，其特征在于，
    所述支持情况为所述第二管理单元能够支持所述子网的需求信息，所述第一管理单元从所述第二管理单元接收协商响应之后，还包括：
    所述第一管理单元向所述第二管理单元发送子网请求，所述子网请求用于请求创建所述子网或修改现有的子网，所述子网请求携带所述子网的需求信息；或者，
    所述支持情况为所述第二管理单元不能支持所述子网的需求信息，所述第一管理单元从所述第二管理单元接收协商响应之后，还包括：
    所述第一管理单元更新所述子网的需求信息；
    所述第一管理单元向所述第二管理单元发送第二协商请求，所述第二协商请求携 带更新的子网的需求信息，所述第二协商请求用于查询所述第二管理单元对所述更新的子网的需求信息的支持情况。
  7. 一种网络切片的管理方法，其特征在于，包括：
    第二管理单元从第一管理单元接收第一协商请求，所述第一协商请求携带子网的需求信息，所述第一协商请求用于查询所述第二管理单元对所述子网的需求信息的支持情况，其中，所述网络切片包括至少一个所述子网；
    所述第二管理单元确定所述第二管理单元能够支持所述子网的需求信息，或者，所述第二管理单元确定所述第二管理单元不能支持所述子网的需求信息。
  8. 根据权利要求7所述的方法，其特征在于，所述第二管理单元从第一管理单元接收第一协商请求之前，还包括：
    所述第二管理单元向所述第一管理单元发送通知，所述通知用于指示所述第一管理单元确定所述子网的需求信息。
  9. 根据权利要求8所述的方法，其特征在于，所述第二管理单元向所述第一管理单元发送通知之前，还包括：
    所述第二管理单元收集所述子网的网络性能；
    所述第二管理单元向所述第一管理单元发送通知，包括：
    当所述子网的网络性能不能满足所述第二管理单元所支持的子网的需求信息时，所述第二管理单元向所述第一管理单元发送所述通知。
  10. 根据权利要求7至9中任一项所述的方法，其特征在于，所述第二管理单元从第一管理单元接收第一协商请求之前，还包括：
    所述第二管理单元向所述第一管理单元发送所述第二管理单元所支持的所述子网的能力信息。
  11. 根据权利要求10所述的方法，其特征在于，所述第二管理单元向所述第一管理单元发送所述第二管理单元所支持的所述子网的能力信息之前，还包括：
    所述第二管理单元从所述第一管理单元接收查询请求，所述查询请求用于请求所述子网的能力信息。
  12. 根据权利要求7至11中任一项所述的方法，其特征在于，还包括：
    所述第二管理单元向所述第一管理单元发送协商响应，所述协商响应携带指示信息，所述指示信息用于指示所述第二管理单元对所述子网的需求信息的支持情况，所述支持情况为所述第二管理单元能够支持所述子网的需求信息，或者，所述支持情况为所述第二管理单元不能支持所述子网的需求信息。
  13. 根据权利要求12所述的方法，其特征在于，
    所述支持情况为所述第二管理单元能够支持所述子网的需求信息，所述第二管理单元向所述第一管理单元发送协商响应之后，还包括：
    所述第二管理单元从所述第一管理单元接收子网请求，所述子网请求用于请求创建所述子网或修改现有的子网，所述子网请求携带所述子网的需求信息；或者，
    所述支持情况为所述第二管理单元不能支持所述子网的需求信息，所述第二管理单元向所述第一管理单元发送协商响应之后，还包括：
    所述第二管理单元从所述第一管理单元接收第二协商请求，所述第二协商请求携 带更新的子网的需求信息，所述第二协商请求用于查询所述第二管理单元对所述更新的子网的需求信息的支持情况。
  14. 一种第一管理单元，其特征在于，包括处理模块和通信模块，
    所述处理模块用于根据网络切片的需求信息确定子网的需求信息，其中，所述网络切片包括至少一个所述子网；以及用于通过所述通信模块向第二管理单元发送第一协商请求，所述第一协商请求携带所述子网的需求信息，所述第一协商请求用于查询所述第二管理单元对所述子网的需求信息的支持情况。
  15. 根据权利要求14所述的第一管理单元，其特征在于，所述处理模块在根据所述网络切片的需求信息确定所述子网的需求信息之前，还用于通过所述通信模块从所述第二管理单元接收通知，所述通知用于指示所述第一管理单元确定所述子网的需求信息；或者，所述处理模块在根据所述网络切片的需求信息确定所述子网的需求信息之前，还用于通过所述通信模块从第三管理单元接收网络切片请求，所述网络切片请求携带所述网络切片的需求信息，所述网络切片请求用于请求创建或修改所述网络切片。
  16. 根据权利要求14或15所述的第一管理单元，其特征在于，所述处理模块在根据所述网络切片的需求信息确定所述子网的需求信息之前，还用于通过所述通信模块从所述第二管理单元接收所述第二管理单元所支持的所述子网的能力信息；以及所述处理模块具体用于根据所述网络切片的需求信息以及所述子网的能力信息，确定所述子网的需求信息。
  17. 根据权利要求16所述的第一管理单元，其特征在于，所述处理模块在通过所述通信模块从所述第二管理单元接收所述第二管理单元所支持的所述子网的能力信息之前，还用于通过所述通信模块向所述第二管理单元发送查询请求，所述查询请求用于请求所述子网的能力信息。
  18. 根据权利要求14至17中任一项所述的第一管理单元，其特征在于，所述处理模块在通过所述通信模块向所述第二管理单元发送所述第一协商请求之后，还用于通过所述通信模块从所述第二管理单元接收协商响应，所述协商响应携带指示信息，所述指示信息用于指示所述第二管理单元对所述子网的需求信息的支持情况，所述支持情况为所述第二管理单元能够支持所述子网的需求信息，或者，所述支持情况为所述第二管理单元不能支持所述子网的需求信息。
  19. 根据权利要求18所述的第一管理单元，其特征在于，所述支持情况为所述第二管理单元能够支持所述子网的需求信息，所述处理模块通过所述通信模块从所述第二管理单元接收所述协商响应之后，还用于通过所述通信模块向所述第二管理单元发送子网请求，所述子网请求用于请求创建所述子网或修改现有的子网，所述子网请求携带所述子网的需求信息；或者，所述支持情况为所述第二管理单元不能支持所述子网的需求信息，所述处理模块通过所述通信模块从所述第二管理单元接收所述协商响应之后，还用于更新所述子网的需求信息，以及用于通过所述通信模块向所述第二管理单元发送第二协商请求，所述第二协商请求携带更新的子网的需求信息，所述第二协商请求用于查询所述第二管理单元对所述更新的子网的需求信息的支持情况。
  20. 一种第二管理单元，其特征在于，包括处理模块和通信模块，
    所述处理模块用于通过所述通信模块从第一管理单元接收第一协商请求，所述第一协商请求携带子网的需求信息，所述第一协商请求用于查询所述第二管理单元对所述子网的需求信息的支持情况，其中，所述网络切片包括至少一个所述子网；以及用于确定所述第二管理单元能够支持所述子网的需求信息，或者，用于确定所述第二管理单元不能支持所述子网的需求信息。
  21. 根据权利要求20所述的第二管理单元，其特征在于，所述处理模块通过所述通信模块从所述第一管理单元接收所述第一协商请求之前，还用于通过所述通信模块向所述第一管理单元发送通知，所述通知用于指示所述第一管理单元确定所述子网的需求信息。
  22. 根据权利要求21所述的第二管理单元，其特征在于，所述处理模块通过所述通信模块向所述第一管理单元发送通知之前，还用于收集所述子网的网络性能；以及所述处理模块具体用于当所述子网的网络性能不能满足所述第二管理单元所支持的子网的需求信息时，通过所述通信模块向所述第一管理单元发送所述通知。
  23. 根据权利要求20至22中任一项所述的第二管理单元，其特征在于，所述处理模块通过所述通信模块从所述第一管理单元接收第一协商请求之前，还用于通过所述通信模块向所述第一管理单元发送所述第二管理单元所支持的所述子网的能力信息。
  24. 根据权利要求23所述的第二管理单元，其特征在于，所述处理模块通过所述通信模块向所述第一管理单元发送所述第二管理单元所支持的所述子网的能力信息之前，还用于通过所述通信模块从所述第一管理单元接收查询请求，所述查询请求用于请求所述子网的能力信息。
  25. 根据权利要求20至24中任一项所述的第二管理单元，其特征在于，所述处理模块还用于通过所述通信模块向所述第一管理单元发送协商响应，所述协商响应携带指示信息，所述指示信息用于指示所述第二管理单元对所述子网的需求信息的支持情况，所述支持情况为所述第二管理单元能够支持所述子网的需求信息，或者，所述支持情况为所述第二管理单元不能支持所述子网的需求信息。
  26. 根据权利要求25所述的第二管理单元，其特征在于，所述支持情况为所述第二管理单元能够支持所述子网的需求信息，所述处理模块通过所述通信模块向所述第一管理单元发送所述协商请求之后，还用于通过所述通信模块从所述第一管理单元接收子网请求，所述子网请求用于请求创建所述子网或修改现有的子网，所述子网请求携带所述子网的需求信息；或者，所述支持情况为所述第二管理单元不能支持所述子网的需求信息，所述处理模块通过所述通信模块向所述第一管理单元发送所述协商响应之后，还用于通过所述通信模块从所述第一管理单元接收第二协商请求，所述第二协商请求携带更新的子网的需求信息，所述第二协商请求用于查询所述第二管理单元对所述更新的子网的需求信息的支持情况。
  27. 一种通信系统，其特征在于，所述系统包括如权利要求14至19中任一项所述的第一管理单元和如权利要求20至26中任一项所述的第二管理单元；或者，所述系统包括如权利要求14至19中任一项所述的第一管理单元、如权利要求20至26中任一项所述的第二管理单元以及第三管理单元。
PCT/CN2017/072666 2017-01-25 2017-01-25 一种网络切片的管理方法、管理单元和系统 WO2018137196A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201780084728.9A CN110226308B (zh) 2017-01-25 2017-01-25 一种网络切片的管理方法、管理单元和系统
EP17893769.4A EP3565182B1 (en) 2017-01-25 2017-01-25 Network slicing management method, and management unit and system
PCT/CN2017/072666 WO2018137196A1 (zh) 2017-01-25 2017-01-25 一种网络切片的管理方法、管理单元和系统
US16/522,131 US11070989B2 (en) 2017-01-25 2019-07-25 Network slice management method, management unit, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/072666 WO2018137196A1 (zh) 2017-01-25 2017-01-25 一种网络切片的管理方法、管理单元和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/522,131 Continuation US11070989B2 (en) 2017-01-25 2019-07-25 Network slice management method, management unit, and system

Publications (1)

Publication Number Publication Date
WO2018137196A1 true WO2018137196A1 (zh) 2018-08-02

Family

ID=62978899

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/072666 WO2018137196A1 (zh) 2017-01-25 2017-01-25 一种网络切片的管理方法、管理单元和系统

Country Status (4)

Country Link
US (1) US11070989B2 (zh)
EP (1) EP3565182B1 (zh)
CN (1) CN110226308B (zh)
WO (1) WO2018137196A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020233217A1 (zh) * 2019-05-17 2020-11-26 中兴通讯股份有限公司 传送网子切片的创建方法、装置、系统及存储介质
WO2023083259A1 (zh) * 2021-11-11 2023-05-19 中国电信股份有限公司 服务等级协议sla指标分解方法、装置、系统及相关设备

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112737866B (zh) 2016-10-31 2022-12-13 华为技术有限公司 网络切片的管理方法、管理单元及系统
WO2018094667A1 (zh) * 2016-11-24 2018-05-31 华为技术有限公司 一种管理方法、管理单元及系统
EP3576479A4 (en) * 2017-02-27 2020-03-04 Huawei Technologies Co., Ltd. ADMINISTRATIVE PROCEDURE, ADMINISTRATIVE UNIT AND SYSTEM
US11240720B2 (en) * 2017-06-02 2022-02-01 FG Innovation Company Limited Methods, devices, and systems for service-driven mobility management
CN113825149B (zh) * 2020-06-18 2024-03-12 中国移动通信集团浙江有限公司 5g切片网元功能自动裁剪方法、装置及计算设备
US11563652B2 (en) * 2020-07-14 2023-01-24 Wipro Limited Method, system, and device for adaptive determination of network slice configuration and resource requirements
CN114339810A (zh) * 2020-09-30 2022-04-12 华为技术有限公司 网络管理方法、装置及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004003751A1 (en) * 2002-06-28 2004-01-08 Sun Microsystems, Inc. A computer system including a network employing redundant information and slicing
CN104105094A (zh) * 2013-04-09 2014-10-15 华为技术有限公司 请求认证方法、装置及系统
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置
CN106304035A (zh) * 2015-05-22 2017-01-04 中兴通讯股份有限公司 一种能力开放方法及系统、能力开放功能实体

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101777999B (zh) * 2010-01-12 2012-01-04 华为技术有限公司 网元历史性能数据的上传方法、系统及服务器
CN104396192B (zh) * 2010-06-29 2018-03-06 华为技术有限公司 不对称网络地址封装
US9483539B2 (en) * 2012-09-13 2016-11-01 International Business Machines Corporation Updating local data utilizing a distributed storage network
US9363141B1 (en) * 2013-09-30 2016-06-07 Emc Corporation System and method for partitioning a network
US20170093624A1 (en) * 2015-09-25 2017-03-30 Qualcomm Incorporated Router Connectivity for Client Devices
US20200252322A1 (en) * 2015-11-26 2020-08-06 Amine Mohamed Houyou Device And Method For Managing Inter-Domain Communications Of A Network Node Assigned To The Device Within A Software-Defined Production Network System
CN110463139A (zh) * 2017-03-16 2019-11-15 英特尔Ip公司 在网络切片实例上支持son功能
US11115826B2 (en) * 2018-06-18 2021-09-07 Electronics And Telecommunications Research Institute Method for managing network slicing resources in communication system and apparatus for the same

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004003751A1 (en) * 2002-06-28 2004-01-08 Sun Microsystems, Inc. A computer system including a network employing redundant information and slicing
CN104105094A (zh) * 2013-04-09 2014-10-15 华为技术有限公司 请求认证方法、装置及系统
CN106304035A (zh) * 2015-05-22 2017-01-04 中兴通讯股份有限公司 一种能力开放方法及系统、能力开放功能实体
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3565182A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020233217A1 (zh) * 2019-05-17 2020-11-26 中兴通讯股份有限公司 传送网子切片的创建方法、装置、系统及存储介质
US11974221B2 (en) 2019-05-17 2024-04-30 Xi'an Zhongxing New Software Co., Ltd. Method and device for creating transmission network sub-slice, and system and storage medium
WO2023083259A1 (zh) * 2021-11-11 2023-05-19 中国电信股份有限公司 服务等级协议sla指标分解方法、装置、系统及相关设备

Also Published As

Publication number Publication date
EP3565182B1 (en) 2021-03-03
US11070989B2 (en) 2021-07-20
US20190349792A1 (en) 2019-11-14
CN110226308A (zh) 2019-09-10
EP3565182A1 (en) 2019-11-06
EP3565182A4 (en) 2020-01-01
CN110226308B (zh) 2021-02-23

Similar Documents

Publication Publication Date Title
WO2018137196A1 (zh) 一种网络切片的管理方法、管理单元和系统
US11038972B2 (en) Service providing method, apparatus, and system
CN108282352B (zh) 管理网络切片实例的方法、装置和系统
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
WO2018152825A1 (zh) 一种管理方法、管理单元和系统
WO2020103523A1 (zh) 一种网络切片的选择方法、网络设备及终端
CN112449315B (zh) 一种网络切片的管理方法及相关装置
CN109391498B (zh) 网络组件的管理方法和网络设备
WO2019062456A1 (zh) 网络的部署信息确定方法及设备
US20220166664A1 (en) Method and Apparatus for Obtaining Management Data
WO2018090191A1 (zh) 网络功能的管理方法、管理单元及系统
US10050823B2 (en) System and method for providing device management service to electronic device having no broadband communication module
WO2018000389A1 (zh) 管理网络切片的方法及其装置
CN109787793B (zh) 网络切片管理的方法、装置、设备及系统
US11201790B2 (en) System and method for virtual private network connectivity
CN113965938B (zh) 切片业务系统及切片业务处理方法
WO2019052363A1 (zh) 修改网络切片实例的方法及装置
CN113472853A (zh) 应用程序网络分片选择方法、应用服务器及udr
CN105323848B (zh) 数据通道控制方法、装置及服务器
CN114363927B (zh) 管理方法、管理单元、通信系统、存储介质和程序产品
US20240089334A1 (en) Systems and methods for modifying connectivity and cloud services

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017893769

Country of ref document: EP

Effective date: 20190801