(19)
(11)EP 3 648 401 A1

(12)EUROPEAN PATENT APPLICATION
published in accordance with Art. 153(4) EPC

(43)Date of publication:
06.05.2020 Bulletin 2020/19

(21)Application number: 18824936.1

(22)Date of filing:  26.06.2018
(51)Int. Cl.: 
H04L 12/24  (2006.01)
(86)International application number:
PCT/CN2018/092856
(87)International publication number:
WO 2019/001421 (03.01.2019 Gazette  2019/01)
(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR
Designated Extension States:
BA ME
Designated Validation States:
KH MA MD TN

(30)Priority: 26.06.2017 CN 201710494883

(71)Applicant: ZTE Corporation
Shenzhen, Guangdong 518057 (CN)

(72)Inventors:
  • ZHOU, Junchao
    Shenzhen Guangdong 518057 (CN)
  • TU, Xiaoyong
    Shenzhen Guangdong 518057 (CN)

(74)Representative: Rosenberg, Muriel Sylvie et al
Ipsilon Le Centralis 63, avenue du Général Leclerc
92340 Bourg-la-Reine
92340 Bourg-la-Reine (FR)

  


(54)METHOD, DEVICE, AND COMPUTER READABLE STORAGE MEDIUM FOR MANAGING NETWORK SLICE


(57) The present disclosure provides a network slice management method, device, and a computer-readable storage medium. The network slice management method includes the following steps: receiving communication service subscription information initiated by a user; converting the communication service subscription information into requirement description information of a corresponding network slice; selecting a sub-slice and determining requirement description information of the sub-slice, according to the requirement description information of the network slice; determining a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, and initiating a deployment request for the sub-slice based on the deployment indicator of the network service; and managing the sub-slice based on the network service and the deployment request for the sub-slice.




Description

TECHNICAL FIELD



[0001] The present disclosure relates to the field of communication technology and particularly to a network slice management method, device and a computer-readable storage medium.

BACKGROUND



[0002] Network slicing is a key feature of Network Function Virtualization (NFV) applied to the fifth generation mobile communication technology (5th generation, 5G). A network slice will form an end-to-end logical network and flexibly provide one or more network services as required by a demanding party of the network slice.

[0003] To fulfill orchestration and management of 5G network slices, the 3rd Generation Partnership Project (3GPP) standardization organization has newly added three logical management network elements into the standards, that is, a Communication Service Management Function (CSMF) unit, a Network Slice Management Function (NSMF) unit, and a Network Slice Subnet Management Function (NSSMF) unit. However, the standards have not defined how to orchestrate and deploy the 5G network slices, or how to implement discovery and selection of the 5G network slices in cooperation with the 5G network slices that have been instantiated.

SUMMARY



[0004] In an embodiment of the present disclosure, there is provided a network slice management method, the method including the steps of: receiving communication service subscription information initiated by a user; converting the communication service subscription information into requirement description information of a corresponding network slice; selecting a sub-slice and determining requirement description information of the sub-slice, according to the requirement description information of the network slice; determining a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, and initiating a deployment request for the sub-slice based on the deployment indicator of the network service; and managing the sub-slice based on the deployment request for the sub-slice.

[0005] In an embodiment of the present disclosure, there is further provided a network slice management device, including: an interface module configured to receive communication service subscription information initiated by a user; a conversion module configured to convert the communication service subscription information into requirement description information of a corresponding network slice; a parsing module configured to select a sub-slice and determine requirement description information of the sub-slice, according to the requirement description information of the network slice; and a management module configured to determine a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, initiate a deployment request for the sub-slice based on the deployment indicator of the network service, and manage the sub-slice based on the deployment request for the sub-slice.

[0006] Furthermore, in an embodiment of the present disclosure, there is further provided a computer-readable storage medium having one or more computer programs stored thereon which, when executed by one or more processors, cause the following steps to be performed: receiving communication service subscription information initiated by a user; converting the communication service subscription information into requirement description information of a corresponding network slice; selecting a sub-slice and determining requirement description information of the sub-slice, according to the requirement description information of the network slice; determining a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, and initiating a deployment request for the sub-slice based on the deployment indicator of the network service; and managing the sub-slice based on the deployment request for the sub-slice.

BRIEF DESCRIPTION OF DRAWINGS



[0007] 

Fig. 1 is a flowchart of a network slice management method according to an embodiment of the present disclosure.

Fig. 2 is a schematic diagram of components of a network slice management device according to an embodiment of the present disclosure.

Fig. 3 is a signal flow diagram of managing a network slice according to an embodiment of the present disclosure.

Fig. 4 is a signal flow diagram of discovering and sensing a network slice according to an embodiment of the present disclosure.


DETAILED DESCRIPTION



[0008] Aiming that how to orchestrate and deploy and how to discover and select network slices in a 5G network are not specifically defined in the 5G standard protocol, the present disclosure provides a network slice management method, device and a computer-readable storage medium for 5G network slices.

[0009] Hereinafter, specific embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0010] Referring to Fig. 1, which is a flowchart of a network slice management method according to an embodiment of the present disclosure, the method includes the following steps S101 to S105.

[0011] In step S101, communication service subscription information initiated by a user is received.

[0012] Specifically, the user initiates a subscription to a communication service, i.e. initiates communication service subscription information, when needed. According to different operation modes of the user, the communication service subscription information may be initiated online, by short messages or in a business hall or the like. In an embodiment of the present disclosure, a user may initiate communication service subscription information online through a client provided by a CSMF.

[0013] In step S102, the communication service subscription information is converted into requirement description information of a corresponding network slice.

[0014] Specifically, the requirement description information may include Service Level Agreement (SLA) information. Various information related to the network service is defined in the SLA information, and typical SLA information may include: a minimum bandwidth allocated to the user; user bandwidth limits; data of the simultaneously served users; notifications prior to network changes that may affect user behavior; access availability; applying statistics; minimum network utilization performance supported by a service provider, such as 99.9% effective working time or downtime up to one minute per day; and traffic priorities of various types of users, etc.

[0015] In step S103, a sub-slice is selected and requirement description information of the sub-slice is determined, according to the requirement description information.

[0016] The information contained in the SLA information (requirement description information) as described above may reflect the specific contents of the communication service subscription information initiated by the user, and thus, parameter requirements of a sub-slice may be determined according to the SLA information. Determining the parameter requirements of the sub-slice according to the SLA information may include: determining at least one of sharing information, acceleration information, priority information, and the like of the sub-slice according to the SLA information. The sharing information of a sub-slice refers to whether the sub-slice is dedicated or shared; the acceleration information of a sub-slice refers to network speed information and the like of the sub-slice determined from a user bandwidth and the like; and the priority information refers to a use priority of each user for the traffic provided by the sub-slice. In addition to the sharing information, the acceleration information, and the priority information, the parameter requirements of the sub-slice may also include other parts. There is no clear and definite boundary between a network slice and a sub-slice, and any segmentation meeting the requirements may be carried out on a network slice. The segmentation of the network slice is mainly carried out through an NSMF, and the logic of the segmentation is determined according to the SLA. The sub-slice management after slicing is performed by an NSSMF.

[0017] In step S104, a deployment indicator of a corresponding network service is determined according to the requirement description information of the sub-slice, and a deployment request for the sub-slice is initiated based on the deployment indicator of the network service.

[0018] The deployment indicator may include at least one of a capacity, a traffic model, disaster tolerance characteristics, sharing, acceleration, and a priority; and these indicator descriptions may reflect the requirement description information of the sub-slice as described above. In other words, the requirement description information of the sub-slice may be reflected by these deployment indicators in the sub-slice.

[0019] In an embodiment, the step of determining the deployment indicator of the corresponding network service according to the requirement description information of the sub-slice, and initiating the deployment request for the sub-slice based on the deployment indicator of the network service may include: selecting a preset network service or generating a new network service based on the preset network service, according to the SLA information of the sub-slice; determining a deployment indicator of the selected or generated network service; initiating a reservation request for a resource for the sub-slice based on the deployment indicator; feeding back response message indicating successful reservation of the resource; and initiating a deployment request for the sub-slice.

[0020] The reservation request for the resource for the sub-slice is typically initiated by an NSSMF to a Network Function Virtualization Orchestrator (NFVO) configured to manage and coordinate a Network Service (NS) Life Cycle; coordinate management of a Virtualised Network Function (VNF) Life Cycle, which needs to be supported by a Virtual Network Function Manager (VNFM); and coordinate management of various types of resources of NFV Infrastructure (NFVI), which needs to be supported by a Virtual Infrastructure Manager (VIM). The above configuration of the NFVO may ensure optimal configurations of various types of resources and connections as desired.

[0021] When the reservation request for the resource is initiated, the NFVO interacts with the VNFM to complete computation of the resource required by the sub-slice, which may include a computing resource, a storage resource, a network resource, a resource required by deployed characteristics, and the like. After completing the computation of the resource, the NFVO initiates the reservation request for the resource to the NFVI or VIM based on a computation result.

[0022] After the reservation request for the resource is initiated, an object receiving the request, e.g., the NFVI or VIM, may reply a reservation response to the initiator (i.e., the NFVO) according to a state of managed resources. The reservation response may include a success or failure response, where the success response indicates that the resources managed by the NFVI or VIM are in a spare state, and may be used for deploying the sub-slice; while the failure response indicates that the resources are insufficient and cannot be used for deploying the sub-slice. When the failure response occurs, the deployment of the sub-slice may be delayed as appropriate, and the NFVI or VIM continues to detect the state of the managed resources until a response indicating successful resource reservation can be given.

[0023] Upon receiving the response indicating successful resource reservation, the NSSMF knows that the subsequent deployment of the sub-slice can be performed, and therefore, the NSSMF continues to initiate the deployment request for the sub-slice, which is also sent to the NFVO.

[0024] In step S105, the sub-slice is managed based on the deployment request.

[0025] The sub-slice management may include deployment of the sub-slice which mainly includes data configuration. If there is a demand for network deployment within the deployed sub-slice, the NFVO completes the deployment of network resources through a Software Defined Network Orchestrator (SDNO) or router plug-in.

[0026] While deploying the sub-slice, the NFVO interacts with the VNFM, and employs a European Telecommunications Standards Institute (ETSI) standard procedure to complete the deployment of the sub-slice. The deployment includes two modes: direct deployment and indirect deployment.

[0027] While deploying the sub-slice, the NFVO replies to the NSSMF with a response message indicating successful activation of a network slice, where the response message may carry, but is not limited to, the following information: a network element or service component identifier; network element or service component deployment characteristics, including sharing information, priority information, acceleration information, and the like; network element or service component capability properties, including whether support MTC or URLLC access, and the like; network element or service component reliability, such as whether support load sharing, pool disaster tolerance, whether support migration, and the like; and monitoring index characteristics, including whether support monitoring, a list of supported monitoring indices, and the like.

[0028] Specifically, the sub-slice deployment (management) may include: pushing configuration data through a sub-slice management facility or acquiring the configuration data from the sub-slice management facility through a deployed sub-slice, and performing data configuration within the sub-slice. An Element Management (EM) is notified by the NSSMF to initiate the data configuration process for the sub-slice, and the EM further interacts with Virtual Network Functions (VNFs) to complete the data configuration for the VNFs or service components within the sub-slice. In a specific data configuration process, the EM may deliver the configuration data to the VNFs or service components in corresponding sub-slice, which may be referred to as a PUSH mode; the corresponding configuration data may also be actively acquired from the EM by the VNFs or service components within the sub-slice, which may be referred to as a PULL mode.

[0029] In an embodiment of the present disclosure, the step of managing the sub-slice may further include: sending a response message indicating successful deployment of the sub-slice. The response message may carry instantiation information of the sub-slice and information of network elements/service components composing the sub-slice. The instantiation information of the sub-slice includes but is not limited to: a sub-slice instance identifier; sub-slice deployment characteristics (sharing, priority, acceleration, etc.); sub-slice capability properties (supporting enhanced Mobile Broadband (eMBB), Machine Type Communication (MTC), etc.); sub-slice performance characteristics (maximum supported message capability, capacity, etc.); sub-slice reliability (supporting load sharing, Pool disaster tolerance, supporting migration, etc.); monitoring index characteristics (whether support monitoring, a list of supported monitoring indices) and the like. Information of the network elements/service components composing the sub-slice includes but is not limited to: a network element or service component identifier; network element or service component deployment characteristics (sharing, priority, acceleration, etc.); network element or service component capability properties (supporting MTC access, supporting Ultra Reliable &Low Latency Communication (URLLC) access, etc.); network element or service component reliability (supporting load sharing, Pool disaster tolerance, supporting migration, etc.); monitoring index characteristics (whether support monitoring, a list of supported monitoring indices) and the like.

[0030] Accordingly, the NSMF may generate instantiation information of a slice according to the information carried in the response message, such as the instantiation information of the sub-slice, the information of the network elements/service components composing the sub-slice, and the like. The instantiation information of the slice includes but is not limited to: a slice instance identifier; slice deployment characteristics (sharing, priority, acceleration, etc.); slice capability properties (supporting eMBB, MTC, etc.); slice performance characteristics (maximum supported message capability, capacity, etc.); slice reliability (supporting load sharing, Pool disaster tolerance, supporting migration, etc.); monitoring index characteristics (whether support monitoring, a list of supported monitoring indices) and the like.

[0031] Then, the NSMF may cache the instantiation information of the sub-slice, the information of the network elements/service components composing the sub-slice, and the instantiation information of the slice, and send a notification message indicating successful deployment of the slice to the CSMF.

[0032] Accordingly, after receiving the notification message indicating successful deployment of the slice, the CSMF sends a notification message indicating successful subscription to the communication service by the user to the user to indicate that the operation of the user is completed.

[0033] In an embodiment of the present disclosure, the network slice management method may further include the following steps: receiving a subscription request for operation information of the slice from other network element facilities; and sending a change notification of the operation information of the slice to the other network element facilities when the operation information of the network slice changes. The change notification may include a change type and the latest operation information of the slice.

[0034] In an embodiment, a logic function entity, i.e., a Network Slice Select Function (NSSF) unit, may be added to the network slice, and configured to store the latest operation information of the slice in real time and select a slice when a terminal accesses the 5G network slices.

[0035] Subscribing to the change notification of the operation information of the slice may include: sending, by the NSSF, a subscription request for the change notification of the operation information of the slice to the NS(S)MF, where the request carries information such as an NSSF identifier. The NS(S)MF represents the NSMF or NSSMF.

[0036] Then, the NS(S)MF replies to the NSSF with a subscription response indicating that the NS(S)MF knows that the NSSF has subscribed to the change notification of the operation information of the slice. When the operation information of the slice changes, the NS(S)MF sends the change notification of the operation information of the slice carrying a specific change type and the latest operation information of the slice to the NSSF.

[0037] The change type, i.e., a condition that triggers the change, includes but is not limited to: at least one of addition, modification and deletion of a network slice. The addition of a network slice indicates that information of a new network slice or sub-slice is cached successfully; the modification of a network slice indicates that stored information changes, which may involve a change in parameter information of the corresponding slice, such as a change in priority, a change in sharing information, and the like; and the deletion of a network slice indicates that cached information is deleted, which may indicate that a corresponding slice is deleted, or that relevant contents in a slice/sub-slice are deleted, etc.

[0038] After giving the notification, the NSSF caches the latest operation information of the slice, and makes a response to the NS(S)MF to indicate that the NSSF has received the change notification of the operation information of the slice. Thus, through the process of slice discovery and sensing, the NSSF can always maintain the latest operation information of the slice so that when a user accesses the 5G slices, a suitable network slice may be selected for the user. The specific slice selection process is not described in detail herein.

[0039] According to the network slice management method provided by the embodiment of the disclosure, the complete flow from a user subscribing to the communication service to completion of the slice orchestration and deployment can be effectively completed, which is a supplement and improvement to the standard protocol.

[0040] Referring to Fig. 2, which is a schematic diagram of components of a network slice management device according to an embodiment of the present disclosure, the network slice management device includes a interface module 201, a conversion module 202, a parsing module 203 and a management module 205.

[0041] The interface module 201 is configured to receive communication service subscription information initiated by a user.

[0042] The conversion module 202 is configured to convert the communication service subscription information into requirement description information of a corresponding network slice.

[0043] The parsing module 203 is configured to select a sub-slice and determine requirement description information of the sub-slice, according to the requirement description information.

[0044] The management module 205 is configured to: determine a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, and initiate a deployment request for the sub-slice based on the deployment indicator of the network service; and manage the sub-slice based on the deployment request.

[0045] The management module 205 may be further configured to: select a preset network service or generate a new network service based on the preset network service, according to SLA information of the sub-slice; determine a deployment indicator of the selected or generated network service; initiate a reservation request for a resource for the sub-slice based on the deployment indicator; feed back response message indicating successful reservation of the resource; and initiate the deployment request for the sub-slice.

[0046] Specifically, the management module 205 may be further configured to: push configuration data through a sub-slice management facility or acquire the configuration data from the sub-slice management facility through a deployed sub-slice, and perform data configuration within the sub-slice. The interface module 201 may be further configured to: send a response message indicating successful deployment of the sub-slice, where the response message may carry: instantiation information of the sub-slice and information of network elements/service components composing the sub-slice. In an embodiment of the present disclosure, the network slice management device may further include a notification module 206 configured to receive subscription request for operation information of the slice from other network element facilities; and send a change notification of the operation information of the slice to the other network element facilities when the operation information of the network slice changes. The change notification may include a change type and the latest operation information of the slice.

[0047] It is to be noted that the various modules may perform the steps and operations described above in conjunction with steps S101 to S105 and achieve the same technical effect. For the sake of brevity, the steps and operations described herein are not repeated.

[0048] According to the network slice management device provided by the embodiment of the present disclosure, the complete flow from a user subscribing to the communication service to completion of the slice orchestration and deployment can be effectively completed, which is a supplement and improvement to the standard protocol.

[0049] Referring to Fig. 3, which is a signal flow diagram of a network slice management method according to an embodiment of the present disclosure, the network slice management method includes the following steps S301-S318.

[0050] In step S301, a user initiates communication service subscription information through a client provided by a CSMF.

[0051] In step S302, the communication service subscription information is converted into requirement description information including SLA information.

[0052] In step S303, an NSMF divides a network slice into different sub-slices, determines SLA information of each of the sub-slices, and then passes the SLA information to an NSSMF, where the SLA information includes: capacity, performance, traffic model, disaster tolerance characteristics, sharing, acceleration, priority, and other parameters.

[0053] In step S304, the NSSMF converts the SLA information into specific indicators such as the capacity, QoS characteristics, and performance of a sub-slice network service, and selects a preset network service or generates a new network service based on the preset network service, based on the indicators, and then initiates a reservation request for a resource for the sub-slice to an NFVO based on the selected or generated network service. As described above in conjunction with step S305, the NFVO completes deployment of network resources through a Software Defined Network Orchestrator (SDNO) or router plug-in. Therefore, although the NFVO is not shown in Fig. 3, it should be understood that the NFVO is at substantially the same location as the SDNO or router plug-in.

[0054] In step S305, the NFVO interacts with a VNFM to complete computation of a resource required by the sub-slice (including a computing resource, a storage resource, a network resource, and a resource required for deployment characteristics).

[0055] In step S306, the NFVO initiates a reservation request for the resource to an NFVI or VIM.

[0056] In step S307, the NFVI/VIM replies to the NFVO with a reservation response according to the state of managed resources.

[0057] In step S308, the NFVO replies to NSSMF with a response to the resource reservation.

[0058] In step S309, the NSSMF initiates a sub-slice deployment request to the NFVO according to a response indicating successful resource reservation to deploy the specific sub-slice.

[0059] In step S310, if there is a demand for network deployment within the sub-slice to be deployed, the NFVO completes the deployment of network resources through a Software Defined Network Orchestrator (SDNO) or router plug-in.

[0060] In step S312, the NFVO interacts with a VNFM and completes deployment of the sub-slice through a direct or indirect deployment mode using an ETSI standard procedure.

[0061] In step S313, the NFVO replies to the NSSMF with a response indicating successful activation of a slice. The information carried in the response message includes but is not limited to: a network element or service component identifier, network element or service component deployment characteristics (sharing, priority, acceleration, etc.), network element or service component capability properties (supporting MTC or URLLC access, and the like), network element or service component reliability (supporting load sharing, Pool disaster tolerance, supporting migration, etc.), monitoring index characteristics (whether support monitoring, a list of supported monitoring indices) and the like.

[0062] In step S314, an EM is notified by the NSSMF to initiate the data configuration process for the sub-slice, and the EM further interacts with VNFs to complete the data configuration for the VNFs or service components within the sub-slice.

[0063] During the configuration process, the EM may deliver the configuration data to the VNFs or service components in a corresponding sub-slice, which may be referred to as a PUSH mode; the corresponding configuration data may also be actively acquired from the EM by the VNFs or service components within the sub-slice, which may be referred to as a PULL mode.

[0064] In step S315, after completing the data configuration, the EM replies to the NSSMF with a response indicating completion of data configuration.

[0065] In step S316, the NSSMF replies to the NSMF with a response indicating successful deployment of the sub-slice, where the response message may carry instantiation information of the sub-slice and information of network elements/service components composing the sub-slice.

[0066] The instantiation information of the sub-slice includes but is not limited to: a sub-slice instance identifier, sub-slice deployment characteristics (sharing, priority, acceleration, etc.), sub-slice capability properties (supporting eMBB, MTC, etc.), sub-slice performance characteristics (maximum supported message capability, capacity, etc.), sub-slice reliability (supporting load sharing, Pool disaster tolerance, supporting migration, etc.), monitoring index characteristics (whether support monitoring, a list of supported monitoring indices) and the like.

[0067] The information of the network elements or service components composing the sub-slice includes but is not limited to: a network element or service component identifier, network element or service component deployment characteristics (sharing, priority, acceleration, etc.), network element or service component capability properties (supporting MTC or URLLC access, and the like), network element or service component reliability (supporting load sharing, Pool disaster tolerance, supporting migration, etc.), monitoring index characteristics (whether support monitoring, a list of supported monitoring indices) and the like.

[0068] In step S317, the NSMF generates instantiation information of a slice according to the instantiation information of the sub-slice, the information of the network elements/service components composing the sub-slice in the response message.

[0069] After locally caching the instantiation information of the sub-slice, the information of the network elements/service components composing the sub-slice, and the instantiation information of the slice, the NSMF sends a notification message indicating successful deployment of the slice to the CSMF, and triggers a process of discovering and sensing the slice.

[0070] In step S318, the CSMF sends a notification message indicating successful subscription to the communication service by the user to the user.

[0071] The discovering and sensing process of the network slice is described below with reference to Fig. 4, which includes the following steps S401 to S404.

[0072] In step S401, the NSSF sends a subscription request for a change notification of operation information of the slice to the NS(S)MF, where the request carries information such as an NSSF identifier.

[0073] In step S402, the NS(S)MF replies to the NSSF with a subscription response.

[0074] In step S403, when information of the slice changes, the NS(S)MF sends a change notification carrying a specific operation type (addition/modification/deletion) and the latest operation information of the slice to the NSSF.

[0075] Conditions for triggering the change notification include but are not limited to: 1) successful cache of information such as a new network slice, e.g., a new slice is orchestrated and deployed successfully; 2) changes in cached information, e.g., the NS(S)MF senses that performances or functional characteristics or the like of the running slice is changed; 3) deletion of the cached information, e.g., the running slice is deactivated or deleted, or resources are passively released, or the like.

[0076] In step S404, the NSSF locally caches the latest operation information of the slice, and replies to the NS(S)MF with a response to the change notification.

[0077] According to the network slice management method provided by the embodiment of the disclosure, the network slices can be orchestrated and deployed from a user initiating communication service subscription information, which is a supplement and improvement to the standard protocol.

[0078] In an embodiment of the present disclosure, there is further provided a computer-readable storage medium having one or more computer programs stored thereon which, when executed by one or more processors, cause the following steps to be performed: receiving communication service subscription information initiated by a user; converting the communication service subscription information into requirement description information of a corresponding network slice; selecting a sub-slice and determining requirement description information of the sub-slice, according to the requirement description information; determining a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, and initiating a deployment request for the sub-slice based on the deployment indicator of the network service; and managing the sub-slice based on the deployment request.

[0079] It is to be noted that in the computer-readable medium according to the embodiments of the present disclosure, the computer programs therein, when executed by one or more processors, may cause the steps and operations described above in conjunction with steps S101 to S105 to be performed and achieve the same technical effect. For the sake of brevity, the steps and operations described herein are not repeated.

[0080] Those skilled in the art will appreciate that the above-described modules or steps of the present disclosure may be implemented by a general purpose computing device, and that when implemented, the modules or steps may be concentrated on a single computing device or distributed across a network of computing devices. The various modules or steps may also be implemented by a program code executable by a computing device, and when implemented, the program code stored in a storage medium (a ROM/RAM, a disk, an optical disk) may be executed by a computing device to implement functions of the various modules or perform the various steps. In some cases, the steps shown or described may be performed in an order different than that described herein. The present disclosure is not limited to any specific combination of hardware and software.

[0081] The above specific embodiments are merely illustrative explanation of the present disclosure, and the scope of the present disclosure is not to be construed as being limited to these embodiments. It will be apparent to those ordinary skilled in the art to which the present disclosure pertains that several changes or substitutions can be made without departing from the scope of the disclosure, which changes and substitutions should also be considered as falling within the scope of the disclosure.


Claims

1. A network slice management method, comprising:

receiving communication service subscription information initiated by a user;

converting the communication service subscription information into requirement description information of a corresponding network slice;

selecting a sub-slice and determining requirement description information of the sub-slice, according to the requirement description information of the network slice;

determining a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, and initiating a deployment request for the sub-slice based on the deployment indicator of the network service; and

managing the sub-slice based on the deployment request for the sub-slice.


 
2. The network slice management method according to claim 1, wherein the deployment indicator of the network service comprises at least one of a capacity, a traffic model, disaster tolerance characteristics, sharing, acceleration, and a priority.
 
3. The network slice management method according to claim 1, wherein requirement description information comprises Service Level Agreement, SLA, information;
wherein determining the deployment indicator of the corresponding network service according to the requirement description information of the sub-slice, and initiating the deployment request for the sub-slice based on the deployment indicator of the network service comprises:

selecting a preset network service or generating a new network service based on the preset network service, according to SLA information of the sub-slice;

determining a deployment indicator of the selected or generated network service;

initiating a reservation request for a resource for the sub-slice based on the deployment indicator of the selected or generated network service;

feeding back response message indicating that the resource for the sub-slice are reserved successfully; and

initiating the deployment request for the sub-slice.


 
4. The network slice management method according to claim 1, wherein managing the sub-slice comprises:
sending response message indicating successful deployment of the sub-slice, wherein the response message indicating successful deployment of the sub-slice carries instantiation information of the sub-slice and information of network elements/service components composing the sub-slice.
 
5. The network slice management method according to any one of claims 1 to 4, wherein managing the sub-slice comprises:
pushing configuration data through a sub-slice management facility or acquiring the configuration data from the sub-slice management facility through a deployed sub-slice, and performing data configuration within the sub-slice.
 
6. The network slice management method according to claim 1, comprising:

receiving a subscription request for operation information of the network slice from another network element facility; and

sending a change notification of the operation information of the network slice to the other network element facility when the operation information of the network slice changes.


 
7. The network slice management method according to claim 6, wherein the change notification comprises a change type, and the change type comprises at least one of addition, modification and deletion of the network slice.
 
8. A network slice management device, comprising:

an interface module configured to receive communication service subscription information initiated by a user;

a conversion module configured to convert the communication service subscription information into requirement description information of a corresponding network slice;

a parsing module configured to select a sub-slice and determine requirement description information of the sub-slice, according to the requirement description information of the network slice; and

a management module configured to determine a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, initiate a deployment request for the sub-slice based on the deployment indicator of the network service, and manage the sub-slice based on the deployment request for the sub-slice.


 
9. The network slice management device according to claim 8, wherein requirement description information comprises Service Level Agreement, SLA, information;
wherein the management module is further configured to:

select a preset network service or generate a new network service based on the preset network service, according to the SLA information of the sub-slice;

determine a deployment indicator of the selected or generated network service;

initiate a reservation request for a resource for the sub-slice based on the deployment indicator of the selected or generated network service;

feed back response message indicating that the resource for the sub-slice are reserved successfully; and

initiate the deployment request for the sub-slice.


 
10. The network slice management device according to claim 8, wherein the interface module is further configured to:
send response message indicating successful deployment of the sub-slice, wherein the response message indicating successful deployment of the sub-slice carries instantiation information of the sub-slice and information of network elements/service components composing the sub-slice.
 
11. The network slice management device according to any one of claims 8 to 10, wherein the management module is further configured to:
push configuration data through a sub-slice management facility or acquire the configuration data from the sub-slice management facility through a deployed sub-slice, and perform data configuration within the sub-slice.
 
12. The network slice management device according to claim 8, further comprising a notification module configured to:

receive a subscription request for operation information of the network slice from another network element facility; and

send a change notification of the operation information of the network slice to the other network element facility when the operation information of the network slice changes.


 
13. A computer-readable storage medium having one or more computer programs stored thereon which, when executed by one or more processors, cause the following steps to be performed:

receiving communication service subscription information initiated by a user;

converting the communication service subscription information into requirement description information of a corresponding network slice;

selecting a sub-slice and determining requirement description information of the sub-slice, according to the requirement description information of the network slice;

determining a deployment indicator of a corresponding network service according to the requirement description information of the sub-slice, and initiating a deployment request for the sub-slice based on the deployment indicator of the network service; and

managing the sub-slice based on the deployment request for the sub-slice.


 




Drawing