(19)
(11)EP 3 684 010 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
27.07.2022 Bulletin 2022/30

(21)Application number: 18860691.7

(22)Date of filing:  28.09.2018
(51)International Patent Classification (IPC): 
H04L 41/5054(2022.01)
H04L 41/0806(2022.01)
H04L 41/122(2022.01)
H04L 41/0897(2022.01)
H04L 41/5041(2022.01)
H04L 41/0895(2022.01)
H04L 41/12(2022.01)
H04L 41/0893(2022.01)
(52)Cooperative Patent Classification (CPC):
H04L 41/0806; H04L 41/0893; H04L 41/5048; H04L 41/5054; H04L 41/0895; H04L 41/40; H04L 41/0897; H04L 41/122
(86)International application number:
PCT/CN2018/108264
(87)International publication number:
WO 2019/062836 (04.04.2019 Gazette  2019/14)

(54)

NETWORK SLICE MANAGEMENT METHOD, AND DEVICE FOR SAME

VERFAHREN ZUR VERWALTUNG VON NETZWERKSLICES UND VORRICHTUNG DAFÜR

PROCÉDÉ DE GESTION DE TRANCHES DE RÉSEAU, ET DISPOSITIF ASSOCIÉ


(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

(30)Priority: 30.09.2017 CN 201710928212

(43)Date of publication of application:
22.07.2020 Bulletin 2020/30

(73)Proprietor: Huawei Technologies Co., Ltd.
Longgang District Shenzhen, Guangdong 518129 (CN)

(72)Inventor:
  • FANG, Haipeng
    Shenzhen Guangdong 518129 (CN)

(74)Representative: Grünecker Patent- und Rechtsanwälte PartG mbB 
Leopoldstraße 4
80802 München
80802 München (DE)


(56)References cited: : 
WO-A1-2016/192643
CN-A- 106 549 806
CN-A- 107 094 127
US-A1- 2017 070 892
WO-A1-2017/032280
CN-A- 106 921 977
CN-A- 107 113 195
US-A1- 2017 141 973
  
  • HUAWEI: "pCR 28.531 Add use case and requirements of network slice instance creation", 3GPP DRAFT; S5-175119 PCR 28.531 ADDING USE CASE OF NETWORK SLICE INSTANCE CREATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTI , vol. SA WG5, no. Busan, Korea; 20171016 - 20171020 3 October 2017 (2017-10-03), XP051361889, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/tsg_sa/WG5_TM/ TSGS5_115/Docs/ [retrieved on 2017-10-03]
  • HUAWEI: "pCR TS 28.531 Add specification level requirements", 3GPP DRAFT; S5-176124 PCR 28.531 ADD SPECIFICATION LEVEL REQUIREMENTS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; , vol. SA WG5, no. Reno, US; 20171127 - 20171201 17 November 2017 (2017-11-17), XP051381147, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG5%5 FTM/TSGS5%5F116/Docs/ [retrieved on 2017-11-17]
  • HUAWEI: "Editorial change for use case reorganization", 3GPP DRAFT; S5-173143 PCR 28.801 EDITORIAL CHANGE FOR USE CASE REORGANIZATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS , vol. SA WG5, no. West Palm Beach, Florida (US); 20170508 - 20170512 28 April 2017 (2017-04-28), XP051269858, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/tsg_sa/WG5_TM/ TSGS5_113/Docs/ [retrieved on 2017-04-28]
  • "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on management and orchestration of network slicing for next generation network (Release 14)", 3GPP STANDARD ; TECHNICAL REPORT ; 3GPP TR 28.801, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V1.0.0, 9 March 2017 (2017-03-09), pages 1-52, XP051290419, [retrieved on 2017-03-09]
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

TECHNICAL FIELD



[0001] Embodiments of this application relate to the field of communications technologies, and specifically, to a network slice management method and an apparatus.

BACKGROUND



[0002] As various communication services continuously emerge, requirements of different communication services on network performance differ significantly. A concept of a network slice (network slice, NS) is introduced into the 5th generation (the 5th generation, 5G) mobile communications system, to meet different requirements of different communication services on network performance.

[0003] Network slicing refers to customization of different logical networks on a physical or virtual network infrastructure based on different service requirements. A network slice may be a complete end-to-end network including a terminal device, an access network, a transport network, a core network, and an application server. The network slice can provide a complete communication service and has a network capability. The network slice may be alternatively any combination of a terminal device, an access network, a transport network, a core network, and an application server.

[0004] A network slice instance (network slice instance, NSI) is a real logical network that operates, and can meet a network feature or a service requirement. The network slice instance may be obtained through instantiation by using a network slice template (network slice template, NST). A complete network slice instance can provide a complete end-to-end network service, and the network slice instance may include several network slice subnet instances (network slice subnet instance, NSSI) and/or several network functions (network function, NF). The NSSI may be obtained through instantiation by using a network slice subnet template (network slice subnet template, NSST).

[0005] A network slice management process is as follows: A communication service management function (communication service management function, CSMF) receives a service requirement of a customer, converts the service requirement into a network slice requirement, and sends the network slice requirement to a network slice management function (network slice management function, NSMF); the NSMF converts the received network slice requirement into a network slice subnet requirement, and sends the network slice subnet requirement to a network slice subnet management function (network slice subnet management function, NSSMF); the NSSMF converts the network slice subnet requirement into a network function requirement, and sends the network function requirement to a management and orchestration (management and orchestration, MANO); and the MANO performs network service instantiation based on the network function requirement. Based on the management process, how to implement automatic management for a network slice is an urgent problem to be resolved.

[0006] Document US 2017/0141973 A1, discloses a method of generating a network slice.

SUMMARY



[0007] Embodiments of this application provide a network slice management method and an apparatus, so that network slice requirement information is decomposed by using a network slice template, to implement automatic management for a network slice.

[0008] A first aspect of the embodiments of this application provides a network slice management method as claimed in independent Claim 1. Another aspect provides an entity according to independent Claim 7.

BRIEF DESCRIPTION OF DRAWINGS



[0009] To describe technical solutions in embodiments of this application or in the background more clearly, the following briefly describes the accompanying drawings required for describing the embodiments of this application or the background.

FIG. 1 is a schematic diagram of a network architecture to which an embodiment of this application is applied;

FIG. 2A and FIG. 2B are a flowchart of a network slice management method according to an embodiment of this application;

FIG. 3 is a schematic composition diagram of a network slice template according to an embodiment of this application;

FIG. 4 is a schematic diagram of a network connection and a service connection according to an embodiment of this application;

FIG. 5A and FIG. 5B are a schematic flowchart of network slice subnet instantiation according to an embodiment of this application;

FIG. 6 is a schematic composition diagram of a network slice subnet template according to an embodiment of this application;

FIG. 7 is a schematic flowchart of service connection instantiation according to an embodiment of this application;

FIG. 8 is a schematic diagram of a logical structure of a device according to an embodiment of this application; and

FIG. 9 is a simplified schematic diagram of an entity structure of a device according to an embodiment of this application.


DESCRIPTION OF EMBODIMENTS



[0010] In 5G, diversified service requirements have different requirements on a rate, performance, security, reliability, and a latency of a network. For example, in an enhanced mobile broadband (enhanced mobile broadband, eMBB) scenario (for example, a virtual reality scenario or an augmented reality scenario), a bandwidth requirement is relatively high and an xGbps-level bandwidth is required. For another example, in a massive machine type communication (massive machine type communication, mMTC) scenario (for example, a wearable scenario or a smart grid scenario), massive device access needs to be supported, for example, access by hundreds of millions of devices or access by billions of devices needs to be supported. For another example, in an ultra-reliable and low-latency (ultra-reliable and low-latency communications, uRLLC) scenario (for example, a self-driving scenario, a remote surgery scenario, or an industrial control scenario), an ultra-low latency of 1 ms needs to be supported. Network slicing emerges to meet requirements of different scenarios, different requirements, and ultimate experience. Networks with different features can be flexibly constructed based on 5G scenarios and requirements.

[0011] A network slicing technology is to logically abstract a network as one or more network slices isolated from each other, and each network slice includes a series of logical network functions, to pertinently meet differentiated requirements of different service types.

[0012] The network slicing technology is to abstract, based on a scenario requirement, a physical infrastructure resource of a 5G network as a plurality of parallel network slice instances independent of each other. In each network slice instance, based on a service scenario requirement and a service model, a network function is customized and tailored, and a corresponding network function is orchestrated and managed. One network slice instance may be considered as one instantiated 5G network. According to such a network structure, an operator is allowed to provide a network as a service for a user, and can freely combine entity networks based on indicators such as a rate, a capacity, coverage, a latency, reliability, security, and availability, to meet requirements of different users.

[0013] Different network slices may provide different network functions. For example, for a scenario in which a mobile intelligent terminal (for example, a mobile phone) performs communication, an independent network slice may be used. For another example, in an internet of vehicles scenario, because there is an ultra-low latency requirement mainly for a self-driving service, and there is a relatively high requirement on a network processing latency and reliability, an independent network slice may also be used. For another example, in an mMTC scenario, because there is a relatively large quantity of access devices, but a packet sent by the access device is relatively small, and a requirement on a network latency is relatively low, an independent network slice may also be used. Because different network slices need to provide different functions and different service quality requirements, different network functions may be deployed in different network slices.

[0014] Terms or names used in the embodiments of this application are described below.

[0015] A network slice is a logically isolated network that is deployed on a physical or virtual infrastructure and that is used to support a specific network capability and a specific network feature. The network slice may include a complete end-to-end (end to end, E2E) network including an access network, a transport network, a core network, and an application server. Some network functions may also be shared by a plurality of network slices. The network slice is a key technology that meets differentiated network requirements of a 5th generation (5th generation, 5G) mobile communications technology proposed by the 3rd generation partnership project (3rd generation partnership project, 3GPP). Usually, different network slices have different network features, and the network slices are required to be isolated from each other and cause no impact to each other. For example, a network slice for an augmented reality (augmented reality, AR) service or a virtual reality (virtual reality, VR) service requires a high bandwidth and a low latency. A network slice for an internet of things (internet of things, IoT) service requires support of access by massive terminals, but requires a low bandwidth and has no requirement on a latency. The network slice may be alternatively any combination of a terminal device, an access network, a transport network, a core network, and an application server.

[0016] A network slice instance is a real logical network that operates, and can meet a network feature or a service requirement. A network slice instance may provide one or more network services. The network slice instance may be created by a network slice management system. One network slice management system may create a plurality of network slice instances and centrally manage the network slice instances. The network slice instance may be created by using a network slice template.

[0017] A network slice template (network slice template, NST) is used to create a network slice instance.

[0018] A complete network slice instance can provide a complete end-to-end network service, and the network slice instance may include a network slice subnet instance and/or a network function. The network slice subnet instance may not need to provide a complete end-to-end network service. The network slice subnet instance may be a set of network functions of a same equipment vendor in the network slice instance, or may be a set of network functions classified based on domains, for example, a network slice subnet instance of a core network and a network slice subnet instance of an access network. A network slice subnet instance may be shared by a plurality of network slice instances. One network slice instance may include a plurality of network slice subnet instances, and each network slice subnet instance includes a plurality of network functions and/or other network slice subnet instances. One network slice instance may directly include several network slice subnet instances and a network function that is not classified into a network slice subnet instance. One network slice instance may alternatively include only several network functions.

[0019] A network slice subnet template (network slice subnet template, NSST) is used to create a network slice subnet instance.

[0020] A network function means a network service that is provided, and defines functional behavior and an interface. For example, in a 5G network, a network function may include a session management function (session management function, SMF), a policy control function (policy control function, PCF), a user plane function (user plane function, UPF), an evolved NodeB (evolved NodeB, eNB) or a 5G base station (new radio (new radio, NR) NodeB, gNB), an access and mobility management function (access and mobility management function, AMF), a network repository function (network repository function, NRF), or the like. The SMF is configured to provide a session management service. The PCF is configured to provide a policy control service. The UPF is configured to provide a user plane service. The AMF is configured to provide an access and mobility management service. The eNB or the gNB (where the eNB is used as an example for description below) is configured to provide a radio access service. The NRF is configured to provide service discovery. A network function may be implemented by special-purpose hardware, or may be implemented by running software on special-purpose hardware, or may be implemented in a form of a virtual function on a general-purpose hardware platform. Therefore, from a perspective of implementation, network functions may be classified into a physical network function (physical network function, PNF) and a virtualized network function (virtualized network function, VNF). From a perspective of usage, network functions may be classified into a dedicated network function and a shared network function. Specifically, a plurality of (sub) network slice instances may independently use different network functions, and such network functions are referred to as dedicated network functions; or a plurality of (sub) network slice instances may share a same network function, and such a network function is referred to as a shared network function. The physical network function and/or the virtual network function are/is collectively referred to as a network function below.

[0021] A network functions virtualization infrastructure (network functions virtualization infrastructure, NFVI) is a resource pool from a perspective of cloud computing. Mapping an NFVI to a physical infrastructure means connecting of a plurality of geographically dispersed data centers (data center, DC) through a highspeed communications network. The NFVI needs to convert physical computing/storage/switching resources into virtual computing/storage/switching resource pools through virtualization.

[0022] A management and orchestration (management and orchestration, MANO) is responsible for management and orchestration of entire NFVI resources, is responsible for mapping and association between a service network and an NFVI resource, and is responsible for implementing a service resource procedure of an operations support system (Operations Support System, OSS).

[0023] For instantiation and deployment of a network slice and a network slice subnet, the MANO needs to complete instantiation of a network service (network service, NS). The instantiation of the network service is to mainly apply to the NFVI for a virtual resource required for the instantiation of the network slice or the network slice subnet.

[0024] A network service descriptor (network service descriptor, NSD) is used to describe a network topology and required resource information that are used for instantiating a network service. The MANO may instantiate a network service based on the NSD.

[0025] An element management system (element management system, EMS) is an element management system of a network function, and is configured to deliver service configuration of the network function to the network function.

[0026] FIG. 1 is a schematic diagram of a network architecture to which an embodiment of this application is applied. The network architecture includes a communication service management function (communication service management function, CSMF), a network slice management function (network slice management function, NSMF), and a network slice subnet management function (network slice subnet management function, NSSMF). It should be noted that quantities of CSMFs, NSMFs, and NSSMFs included in the network architecture are not limited to those shown in FIG. 1. In actual application, there may be a plurality of CSMFs, a plurality of NSMFs, and a plurality of NSSMFs. It should be noted that the foregoing three management functions may be described by using other names. This is not limited in this embodiment of this application. According to the solution provided in this embodiment of this application, an operator may provide a network slice instance for a user, to provide a specific communication service, for example, a high-definition video, for the user.

[0027] Specifically, the user may determine, through negotiation with the operator, corresponding communication service requirements, for example, a coverage range required by a network service, a user quantity, user distribution, a mobility requirement, a latency requirement, and whether a network slice needs to be isolated from another network slice.

[0028] The CSMF is mainly responsible for converting a communication service requirement of an operator and/or a third-party customer into network slice requirement information, where the network slice requirement information includes a network slice type/slice template identifier ID and network slice deployment requirement information (for example, a network capacity and a quality of service QoS requirement); sending the network slice requirement information to the NSMF through an interface between the CSMF and the NSMF; obtaining management data (for example, performance data and fault data) of a network slice from the NSMF; generating management data of a communication service running on the network slice instance; and receiving a subscription requirement of the operator and/or the third-party customer for the management data of the network slice and/or the management data of the communication service.

[0029] The NSMF is mainly responsible for receiving the network slice requirement information sent by the CSMF; managing a life cycle, performance, a fault, and the like of a network slice instance (where the management of the life cycle, the performance, the fault is referred to as management below); orchestrating composition of the network slice instance; decomposing the network slice requirement information into requirement information of each network slice subnet instance and/or network function, and a transport network (transport network, TN) requirement; and sending a network slice subnet instantiation request to each NSSMF, and sending the transport network requirement to a transport network manager (TN-manager).

[0030] The NSSMF is mainly responsible for receiving the network slice subnet requirement sent by the NSMF; managing a network slice subnet instance; orchestrating composition of the network slice subnet instance; decomposing a requirement of the network slice subnet instance into a requirement of each network function and/or nested network slice subnet instance; and sending a nested network slice subnet instantiation request to another NSSMF, and managing a nested network slice subnet instance and the like.

[0031] It should be noted that a network function management entity, network function management, and an NSMF are interchangeable in the embodiments of this application. The three terms are all used to describe an entity responsible for receiving a network slice requirement sent by the CSMF, and do not constitute any limitation on the embodiments of this application. This is also applied to the NSSMF and the CSMF

[0032] Based on the current network slice management process, how to implement automatic management for a network slice is an urgent problem to be resolved. In view of this, the embodiments of this application provide a network slice management method and an apparatus, so that network slice requirement information is decomposed by using a network slice template, to implement automatic management for a network slice.

[0033] FIG. 2A and FIG. 2B are a schematic flowchart of a network slice management method according to an embodiment of this application. The method is described from a perspective of interaction between an NSMF, an NSSMF, and a TN-manager. The TN-manager is responsible for instantiation management of transport networks between network slice subnet nodes and between different network functions in a network slice subnet node. In the method shown in FIG. 2A and FIG. 2B, an example in which a network slice instance includes two network slice subnet instances, an NSSMF 1 may be instantiated to obtain a network slice subnet instance 1 (NSSI-1), and an NSSMF 2 may be instantiated to obtain a network slice subnet instance 2 (NSSI-2) is used. The method shown in FIG. 2A and FIG. 2B may include but is not limited to the following steps.

[0034] Step S200: Generate a network slice template.

[0035] Before the NSMF receives a network slice instantiation request, a slice designer (for example, a slice provider) designs a network slice template, generates the network slice template, and on-boards (on-boarding) the network slice template to the NSMF. The NSMF may record and store a correspondence between a network slice template and network slice requirement information, where the network slice requirement information includes a network slice subnet template identifier or a network slice type. The network slice type is used to represent a type of a network service provided by a slice, for example, a high-definition video service type or an internet of vehicles type. On-boarding the network slice template to the NSMF is a precondition for implementation of this embodiment of this application.

[0036] For a schematic composition diagram of the network slice template, refer to FIG. 3. The network slice template is used to describe component information required for network slice instantiation, where the information includes node description information of a node included in a network slice and connection description information between nodes. The node may be a network slice subnet node or a network function node.

[0037] When the network slice instance includes a network slice subnet instance, the node description information includes a network slice subnet node descriptor (NSS node descriptor), a network connection point descriptor (network connection point descriptor) of a network slice subnet node, and a service access point descriptor (service access point descriptor) of the network slice subnet node; and the connection description information includes a service connection descriptor (service connection descriptor) between network slice subnet nodes and a network connection descriptor (network connection descriptor) between the network slice subnet nodes.

[0038] When the network slice instance may include a network function, the node description information includes a network function node descriptor (NF node descriptor), a network connection point descriptor of a network function node, and a service access point descriptor of the network function node; and the connection description information includes a network connection descriptor between different network function nodes and a service connection descriptor between the network function nodes. The network function node may be a virtualized network function node (VNF node) or may be a physical network function node (PNF node).

[0039] Assuming that a network slice includes two network slice subnets, nodes corresponding to the two network slice subnets are an access network (access network, AN) node and a core network (core network, CN) node, and there are a network connection and a service connection between the access network node (AN node) and the core network node (CN node). The network connection is used to describe a physical connection between the two nodes, that is, the two nodes are physically connected. If service interaction (for example, mutual service packet transmission) between the two nodes needs to be implemented, the service connection needs to be implemented.

[0040] FIG. 4 is a schematic diagram of the network connection and the service connection based on this assumption. Gray points on the nodes are service access points, and black points are network connection points. A network connection point 1 of the AN node is connected to a network connection point 1 of the CN node by using a solid line, indicating that a network connection exists between the AN node and the CN node. To be specific, the solid line shown in FIG. 4 indicates the network connection between the AN node and the CN node, and the network connection is used to carry network connection information between an AN and a CN. A service access point 1 of the AN node is connected to a service access point 1 of the CN node by using a long dashed line, indicating that a service connection exists between the AN node and the CN node. To be specific, the long dashed line shown in FIG. 4 indicates the service connection between the AN node and the CN node, and the service connection is used to carry service interworking information between the AN and the CN.

[0041] The service access point of the AN node depends on the network connection point of the AN node, and the service access point of the CN node depends on the network connection point of the CN node. It should be noted that there are one network connection point and one service access point on one node shown in FIG. 4, and this does not constitute any limitation on this embodiment of this application. In actual application, there are a plurality of network connection points and a plurality of service access points on one node.

[0042] A network connection point of a node may perform a network connection to a network connection point of another node. In other words, a network connection point of a network slice subnet node may perform a network connection to a network connection point of another network slice subnet node, or may perform a network connection to a network connection point of an application server or application software.

[0043] Optionally, different nodes in a network slice instance may be connected to a connected network by using a network connection point, to implement a network connection between the nodes.

[0044] A service access point of a node may perform a service connection to a service access point of another node. In other words, a service access point of a network slice subnet node may perform a service connection to a service access point of another network slice subnet node, or may perform a service connection to a service access point of an application server or application software.

[0045] The network slice subnet node descriptor includes component information required for network slice subnet instantiation. The component information required for network slice subnet instantiation includes a node descriptor of a network function node included in a network slice subnet, a network connection point descriptor of the network function node, a service access point descriptor of the network function node, a network connection descriptor between network function nodes, and a service connection descriptor between the network function nodes. It may be understood that the network slice subnet node descriptor is used to describe information required for network slice subnet instantiation.

[0046] The service connection descriptor between the network slice subnet nodes is used to describe service connection information between the AN node and the CN node in FIG. 4, that is, used to describe service connection information between the network slice subnet nodes. The service connection information may include information such as a service connection protocol and a service connection-related parameter. It may be understood that the service connection descriptor between the network slice subnet nodes is used to describe information, such as a specific service connection protocol and a specific service connection-related parameter, used for a service connection between the network slice subnet nodes.

[0047] The network connection descriptor between the network slice subnet nodes is used to describe network connection information between the AN node and the CN node in FIG. 4, that is, used to describe network connection information between the network slice subnet nodes. The network connection information may include information such as quality of service (quality of service, QoS) information and an internet protocol (Internet protocol, IP) type that are of a network plane. It may be understood that the network connection descriptor between the network slice subnet nodes is used to describe specific network connection information used for a network connection between the network slice subnet nodes.

[0048] The service access point descriptor of the network slice subnet node is used to describe service access point information of the network slice subnet node. The service access point information may be information about a service access point for performing a service connection between the network slice subnet node and a device outside a network slice, or may be information about a service access point for performing a service connection between the network slice subnet node and an application server or application software. The service access point information may include information such as a service IP address of the service access point. If there are a plurality of service access points on the network slice subnet node, each service access point may correspond to one service access point descriptor.

[0049] The network connection point descriptor of the network slice subnet node is used to describe network connection point information of the network slice subnet node. The network connection point information may be information about a network connection point for a network connection between the network slice subnet node and another network slice subnet node, or may be information about a network connection point for a network connection between the network slice subnet node and a device outside a network slice. The network connection point information may include information such as a physical IP address of the network connection point. If there are a plurality of network connection points on the network slice subnet node, each network connection point may correspond to one network connection point descriptor.

[0050] The network slice subnet node is a node of a network slice subnet included in the network slice.

[0051] The physical IP address may be understood as an IP address of a physical interface, and the service IP address is an IP address for service interaction with another network element. However, a service IP packet needs to be sent from the physical interface.

[0052] It may be understood that in the scenario in which the network slice instance includes a network slice subnet instance, the node description information includes the component information required for network slice subnet instantiation, the network connection point descriptor of the network slice subnet node, and the service access point descriptor of the network slice subnet node; and the connection description information includes the network connection descriptor between the network slice subnet nodes and the service connection descriptor between the network slice subnet nodes.

[0053] In the scenario in which the network slice instance may include a network function, the node description information may include the network function node descriptor shown in a dashed-line block in FIG. 3, the network connection point descriptor of the network function node, and the service access point descriptor of the network function node; and the connection description information may include the network connection descriptor between the network function nodes and a service descriptor between the network function nodes. The network function node descriptor is used to describe information required for network function subnet instantiation. The network connection point descriptor of the network function node, the service access point descriptor of the network function node, the network connection descriptor between the network function nodes, and the service access point descriptor between the network function nodes are respectively similar to the network connection point descriptor of the network slice subnet node, the service access point descriptor of the network slice subnet node, the network connection descriptor between the network slice subnet nodes, and the service access point descriptor between the network slice subnet nodes. Details are not described herein again.

[0054] In the scenario in which the network slice instance may include a network function, the network slice template may include a service configuration file shown in a dashed-line block in FIG. 3, and the service configuration file is used for service configuration of the network function. It may be understood that the service configuration file indicates specific service functions that need to be implemented by the network function.

[0055] If the network slice instance may include a virtualized network function, the network slice template may include a network service descriptor (NSD) index file shown in a dashed-line block in FIG. 3, and may be an NSD ID. The network service descriptor is used for instantiating virtual resource deployment of an associated network function, and the associated network function is a virtual network function included in the network slice. It may be understood that, a MANO may complete the virtual resource deployment of the associated network function based on the NSD file corresponding to a network service descriptor ID index in this case. The virtual resource may include a virtual memory resource, a virtual central processing unit (central processing unit, CPU), and the like.

[0056] Step S201: The NSMF receives a network slice instantiation request, where the network slice instantiation request includes the network slice requirement information, and the network slice requirement information includes a network slice template identifier or the network slice type.

[0057] A network slice subscriber, for example, an operator or a third-party customer, may subscribe to a network slice in an operational interface of a business support system (business support system, BSS), that is, enter a service requirement in the operational interface of the BSS. The service requirement may include a service type, and may further include a service-level agreement (service-level agreement, SLA) requirement. The SLA is a contract between a network service provider and a customer. The SLA requirement may include a user quantity, a bandwidth requirement, a latency assurance requirement, and the like. It may be understood that the service requirement includes the service type and the SLA requirement.

[0058] When receiving the service requirement, a CSMF (or a BSS-CSMF) converts the service requirement into the network slice requirement information, where the conversion specifically includes service type conversion and SLA requirement conversion. The service type conversion means conversion of a service type in a service requirement into a network slice type, for example, conversion of a service type into an eMBB network slice, an uRLLC network slice, or an mMTC network slice. Optionally, in this case, the CSMF may further search for, based on the network slice type, the network slice template identifier (NST ID) corresponding to the network slice type. The SLA requirement conversion means conversion of an SLA requirement into network slice deployment requirement information. The network slice deployment requirement information may include requirements such as a user quantity, a bandwidth, and a latency. In other words, the network slice deployment requirement information is used to describe requirement information such as the user quantity, the bandwidth, and the latency.

[0059] It may be understood that the network slice requirement information includes the network slice type and the network slice deployment requirement information, the network slice type is used to indicate a type of a network slice, and the network slice template identifier may be determined based on the network slice type. Alternatively, the network slice requirement information includes the network slice template identifier and the network slice deployment requirement information, and the network slice template identifier is used to indicate a network slice template.

[0060] It may be understood that the network slice requirement information may provide an input parameter for network slice instantiation.

[0061] The CSMF sends the network slice instantiation request to the NSMF, where the network slice instantiation request includes the network slice requirement information, and the network slice requirement information includes the network slice template identifier or the network slice type, and the network slice deployment requirement information. Correspondingly, the NSMF receives the network slice instantiation request from the CSMF, where the network slice instantiation request may be an initial instantiation request, to be specific, a network slice instance that does not exist in a current system may be requested to be instantiated.

[0062] Step S202: The NSMF obtains the network slice template based on the network slice template identifier or the network slice type.

[0063] In an implementation, the NSMF obtains, based on the network slice template identifier, the network slice template corresponding to the network slice template identifier. One network slice template identifier corresponds to one network slice template.

[0064] In an implementation, the NSMF obtains, based on the network slice type, the network slice template corresponding to the network slice type. One network slice type corresponds to one network slice template. Specifically, the NSMF searches for, based on the network slice type, the network slice template identifier corresponding to the network slice type, and then obtains the network slice template based on the network slice template identifier.

[0065] In this case, the NSMF may further allocate an identifier to the network slice instance corresponding to the network slice template, that is, allocate a network slice instance identifier (NSI ID). One network slice instance can be obtained by instantiating one network slice template once.

[0066] Step S203: The NSMF decomposes the network slice requirement information into network slice subnet requirement information 1, network slice subnet requirement information 2, and transport network requirement information based on the network slice template.

[0067] The NSMF decomposes the network slice requirement information based on content included in the network slice template, to obtain network slice subnet requirement information corresponding to the node description information and transport network requirement information corresponding to the connection description information. The network slice subnet requirement information corresponding to the node description information includes network slice subnet requirement information 1 corresponding to node description information of a network slice subnet node 1 and network slice subnet requirement information 2 corresponding to node description information of a network slice subnet node 2.

[0068] The network slice subnet requirement information 1 includes a network slice subnet template identifier (NSST ID), an input parameter required for instantiation of a network slice subnet 1, network connection point information of the network slice subnet node 1, and service access point information of the network slice subnet node 1. The transport network requirement information includes network connection information between the network slice subnet node 1 and the network slice subnet node 2. The network slice subnet requirement information 2 includes a network slice subnet template identifier (NSST ID), an input parameter required for instantiation of a network slice subnet 2, network connection point information of the network slice subnet node 2, and service access point information of the network slice subnet node 2.

[0069] It may be understood that the network slice subnet requirement information provides the input parameter for the instantiation of the network slice subnet, including providing the input parameter for the instantiation of the network slice subnet, providing the network connection point information for the network connection point of the network slice subnet node, and providing the service access point information for the service access point of the network slice subnet node; and the transport network requirement information provides an input parameter for instantiation of a transport network, including providing a network connection input parameter for the network connection between the network slice subnet nodes.

[0070] It may be understood that the network slice template defines components required for network slice instantiation and input parameters required by the components. The network slice requirement information may provide the input parameters. The NSMF may decompose the network slice requirement information based on the network slice template, to be specific, provide corresponding input parameters for the components based on the input parameters required by the components.

[0071] After the decomposition, the NSMF determines deployment areas of an NSSI-1 and an NSSI-2 based on the network slice requirement information, that is, determines a deployment location of each NSSI. In this way, the MANO can subsequently deploy, in a data center (DC) in a correct area, a network function corresponding to a network slice subnet instance.

[0072] If the network slice instance includes a network function, the NSMF decomposes the network slice requirement information into service configuration requirement information, network service requirement information, and transport network requirement information of a network function in a network slice based on the network slice template. For the three pieces of information, refer to descriptions in the embodiment shown in FIG. 6.

[0073] Step S204a: The NSMF sends a network slice subnet instantiation request 1 to an NSSMF 1, where the network slice subnet instantiation request 1 includes the network slice subnet requirement information 1; and correspondingly the NSSMF 1 receives the network slice subnet instantiation request 1 from the NSMF.

[0074] Step S204b: The NSMF sends a network slice subnet instantiation request 2 to an NSSMF 2, where the network slice subnet instantiation request 2 includes the network slice subnet requirement information 2; and correspondingly the NSSMF 2 receives the network slice subnet instantiation request 2 from the NSMF.

[0075] Specifically, the NSMF sends a network slice subnet instantiation request to each NSSMF, where the network slice subnet instantiation request carries corresponding network slice subnet requirement information. For example, a network slice includes the network slice subnet 1 and the network slice subnet 2; the NSMF sends the network slice subnet instantiation request 1 to the NSSMF 1, where the request 1 carries requirement information of the network slice subnet 1; and the NSMF sends the network slice subnet instantiation request 2 to the NSSMF 2, where the request 2 carries requirement information of the network slice subnet 2.

[0076] The NSSMF 1 decomposes the requirement information of the network slice subnet 1 based on an NSST 1 to obtain network service requirement information 1, service configuration requirement information 1, and transport network requirement information 1; sends the network service requirement information 1 to the MANO; sends the service configuration requirement information 1 to an EMS 1 corresponding to the NSSMF 1; and sends the transport network requirement information 1 to the TN-manager. The NSSMF 2 decomposes the requirement information of the network slice subnet 2 based on an NSST 2 to obtain network service requirement information 2, service configuration requirement information 2, and transport network requirement information 2; sends the network service requirement information 2 to the MANO; sends the service configuration requirement information 2 to an EMS 2 corresponding to the NSSMF 2; and sends the transport network requirement information 2 to the TN-manager.

[0077] The network slice subnet instantiation request further includes a deployment area of a corresponding network slice subnet instance, so that the MANO can subsequently deploy, in a DC in a correct area, a network function corresponding to the network slice subnet instance. For example, the network slice subnet instantiation request 1 further includes the deployment area of the NSSI-1, and the network slice subnet instantiation request further includes the deployment area of the NSSI-2.

[0078] The network slice subnet instance request may further include a network slice instance identifier (NSI ID) corresponding to the network slice.

[0079] The network slice subnet requirement information may further include a corresponding network slice subnet template identifier or network slice type.

[0080] Step S205a: The NSSMF 1 sends a network slice subnet instantiation response 1 to the NSMF, where the network slice subnet instantiation response 1 includes instantiation information 1; and correspondingly the NSMF receives the network slice subnet instantiation response 1 from the NSSMF 1.

[0081] Step S205b: The NSSMF 2 sends a network slice subnet instantiation response 2 to the NSMF, where the network slice subnet instantiation response 2 includes instantiation information 2; and correspondingly the NSMF receives the network slice subnet instantiation response 2 from the NSSMF 2.

[0082] After completing instantiation of a network service 1, the NSSMF 1 sends the instantiation information 1 to the NSMF. After completing instantiation of a network service 2, the NSSMF 2 sends the instantiation information 2 to the NSMF.

[0083] The instantiation information 1 includes a network slice subnet instance 1 identifier (NSSI-1 ID), network connection point instantiation information of a network slice subnet instance 1, and service access point instantiation information of the network slice subnet instance 1.

[0084] The network connection point instantiation information of the NSSI-1 includes information such as a local IP address of a network connection point for interconnection between the NSSI-1 and the NSSI-2, and further includes information such as an IP address of a network connection point for interconnection between the NSSI-1 and an external access device. Similarly, network connection point instantiation information of the NSSI-2 may be defined.

[0085] The service access point instantiation information of the NSSI-1 includes a local IP address of a service access point for interconnection between the NSSI-1 and the NSSI-2, and further includes information such as an IP address of a service access point for interconnection between the NSSI-1 and an external access device. Similarly, service access point instantiation information of the NSSI-2 may be defined.

[0086] Access device information may be information about interconnection between a gateway router in a DC in which a network slice subnet instance is deployed and a transmission switch, and includes an access device identifier, a port identifier, and the like.

[0087] For the NSSI 1, the local IP address is an IP address of the NSSI-1, and a peer IP address is an IP address of the NSSI-2.

[0088] The NSMF may record and store instantiation information sent by each NSSMF

[0089] It should be noted that step S204a and step S205a, and step S204b and step S205b each are a procedure of network slice subnet instantiation. For details, refer to descriptions in FIG. 5A and FIG. 5B.

[0090] Step S206a: The NSMF sends a service access request 1 to the NSSMF 1, and correspondingly the NSSMF 1 receives the service access request 1 from the NSMF

[0091] Step S206b: The NSMF sends a service access request 2 to the NSSMF 2, and correspondingly the NSSMF 2 receives the service access request 2 from the NSMF.

[0092] Step S206a and step S206b are performed after step S205a and step S205b.

[0093] The service access request includes the network slice instance identifier, the network slice subnet template identifier, and the service access point information. The service access point instantiation information includes information such as a local IP address and a peer IP address of a service access point for interconnection between the network slice subnet instance and another network slice subnet instance, and an IP address of a gateway router. The IP address of the gateway router is an IP address of a next-hop router. For example, a service access point of the NSSI-1 is interconnected to a service access point of the NSSI-2. For the NSSI-1, the local IP address is an IP address of the service access point of the NSSI-1, and the peer IP address is an IP address of the service access point of the NSSI-2.

[0094] After receiving the instantiation information 1 and the instantiation information 2, the NSMF sends the service access request 1 to the NSSMF 1. The service access request 1 carries a network slice instance identifier, a network slice subnet template identifier corresponding to the network slice subnet instance 1, and service access point information 1.

[0095] After receiving the instantiation information 1 and the instantiation information 2, the NSMF sends the service access request 2 to the NSSMF 2. The service access request 2 carries a network slice instance identifier, a network slice subnet template identifier corresponding to the network slice subnet instance 2, and service access point information 2.

[0096] Step S207a: The NSSMF 1 sends a service access acknowledgement message 1 to the NSMF, and correspondingly the NSMF receives the service access acknowledgement message 1 from the NSSMF 1.

[0097] Step S207b: The NSSMF 2 sends a service access acknowledgement message 2 to the NSMF, and correspondingly the NSMF receives the service access acknowledgement message 2 from the NSSMF 2.

[0098] After the EMS completes service configuration, the NSSMF sends a service access acknowledgement message to the NSMF, where the service access acknowledgement message carries the network slice subnet instance identifier, to notify the NSMF that a corresponding network slice subnet instance has accessed a service. For example, the service access acknowledgement message 1 is used to notify that the NSSI-1 has accessed the service, and the service access acknowledgement message 2 is used to notify that the NSSI-2 has accessed the service.

[0099] It should be noted that, step S206a and step S207a, and step S206b and step S207b each are a procedure of service access instantiation. For details, refer to descriptions in FIG. 7.

[0100] Step S208: The NSMF sends a transport network instantiation request to the TN-manager, and correspondingly, the TN-manager receives the transport network instantiation request from the NSMF

[0101] It should be noted that step S208 is performed after step S205a and step S205b, and step S208 may be performed simultaneously with step S206a and step S206b.

[0102] The NSMF creates a transport network instantiation request between network slice subnet instances based on the instantiation information sent by each NSSMF, for example, creates a transport network instantiation request between the NSSI-1 and the NSSI-2.

[0103] Two network slice subnet instances are used as an example. The transport network instantiation request includes information such as IP addresses (that is, IP addresses of two ends) for a network connection between the NSSI-1 and the NSSI-2 (that is, information such as network connection IP addresses for interconnection between the network slice subnet node 1 and the network slice subnet node 2), and QoS information for a network connection between the NSSI-1 network slice subnet instance 1 and the NSSI-2 network slice subnet instance 2 (that is, QoS information for a network connection between the network slice subnet node 1 and the network slice subnet node 2). The transport network instantiation request further includes information about an access device for interconnection between the NSSI-1 network slice subnet instance 1 and the NSSI-2 network slice subnet instance 2. The information about the access device may be information about interconnection between a gateway router in a DC in which a network slice subnet instance is deployed and a transmission switch, and includes an access device identifier, a port identifier, and the like.

[0104] The NSMF can search for information about an access device corresponding to a deployment location based on an imported network-wide data center and an imported transport network topology.

[0105] Step S209: The TN-manager performs transport network instantiation based on the transport network instantiation request.

[0106] When receiving the transport network instantiation request, the TN-manager performs the transport network instantiation based on the transport network requirement information, establishes a network connection between network slice subnet instances, and may further establish a network connection between a network slice subnet instance and an access device.

[0107] Step S210: The TN-manager sends an acknowledgement message to the NSMF.

[0108] After completing the transport network instantiation, the TN-manager feeds back the acknowledgement message to the NSMF, to notify the NSMF that the transport network instantiation is completed.

[0109] In this embodiment shown in FIG. 2A and FIG. 2B, the NSMF decomposes the network slice requirement information into the network slice subnet requirement information and the transport network requirement information by using the network slice template, so that the NSSMF performs network service instantiation and service connection instantiation, and the TN-manager performs the transport network instantiation.

[0110] FIG. 5A and FIG. 5B are a schematic flowchart of network slice subnet instantiation according to an embodiment of this application which is not claimed as such.

[0111] The procedure is described from a perspective of interaction between an NSMF, an NSSMF, and a MANO. One NSSMF is used as an example for description. The procedure shown in FIG. 5A and FIG. 5B may include but is not limited to the following steps.

[0112] Step S300: Generate a network slice subnet template.

[0113] A slice-related person (for example, a slice provider) designs the network slice subnet template, generates the network slice subnet template, and on-boards the network slice subnet template to the NSSMF. The NSSMF may record and store a correspondence between a network slice subnet template and network slice subnet requirement information, where the network slice subnet requirement information includes a network slice subnet template identifier or a network slice type. The network slice type is used to represent a type of a network service provided by a slice, for example, a high-definition video service type or an internet of vehicles type.

[0114] For a schematic composition diagram of the network slice subnet template, refer to FIG. 6. The network slice subnet template is used to describe component information required for network slice subnet instantiation, includes node description information of a network function node included in a network slice subnet and connection description information between network function nodes, and specifically includes node description information of each network function node and connection description information between the nodes.

[0115] The node description information of the network function node includes a network function node descriptor, a network connection point descriptor of the network function node, and a service access point descriptor of the network function node. The connection description information includes a service connection descriptor between the network function nodes and a network connection descriptor between the network function nodes.

[0116] The network function node descriptor is used to describe an input parameter required for network function subnet instantiation.

[0117] For the network connection point descriptor of the network function node, the service access point descriptor of the network function node, the service connection descriptor between the network function nodes, the network connection descriptor between the network function nodes, the network connection point descriptor of the network slice subnet node, the service access point descriptor of the network slice subnet node, the service connection descriptor between the network slice subnet nodes, and a type of a network connection descriptor between network slice subnet nodes, refer to the foregoing descriptions. Details are not described herein again.

[0118] The network slice subnet template may include a service configuration file shown in a dashed block in FIG. 6, and the service configuration file is used for service configuration of a network function. It may be understood that the service configuration file indicates service functions that need to be implemented by the network function.

[0119] The network slice subnet template may include a network service descriptor index file shown in a dashed-line block in FIG. 6, and may be an NSD ID. The network service descriptor is used for instantiating virtual resource deployment of a network function, and the network function is a network function included in a network slice subnet. It may be understood that the MANO may complete the virtual resource deployment of the network function based on an NSD file corresponding to a network service descriptor ID index in this case. The virtual resource may include a virtual memory resource, a virtual CPU, and the like.

[0120] If a network slice subnet instance may nest another network slice subnet instance, in addition to the content shown in FIG. 6, the network slice subnet template may further include a network slice subnet template corresponding to the nested network slice subnet instance.

[0121] Step S301: The NSSMF receives a network slice subnet instantiation request, where the network slice subnet instantiation request includes network slice subnet requirement information.

[0122] It may be understood that the network slice subnet requirement information is an input parameter provided by the NSMF for the NSSMF, so that the NSSMF instantiates a network slice subnet.

[0123] The network slice subnet instantiation request further includes a deployment area of the network slice subnet instance, so that in an instantiation process, the MANO can deploy a network function corresponding to the network slice subnet instance in a DC in a correct area.

[0124] The network slice subnet instantiation request further includes a network slice instance identifier, so that the NSSMF manages a network slice instance to which the network slice subnet requirement information belongs.

[0125] It should be noted that step S301 corresponds to step S204a and step S204b in the embodiment shown in FIG. 2A and FIG. 2B.

[0126] Step S302: The NSSMF obtains the network slice subnet template.

[0127] In an implementation, the NSSMF obtains, based on the network slice subnet template identifier, the network slice subnet template corresponding to the network slice subnet template identifier. One network slice subnet template identifier corresponds to one network slice subnet template.

[0128] In an implementation, the NSSMF obtains, based on the network slice type, a network slice template corresponding to the network slice type. One network slice type corresponds to one network slice subnet template. Specifically, the NSSMF searches for, based on the network slice type, the network slice subnet template identifier corresponding to the network slice type, and then obtains the network slice subnet template based on the network slice subnet template identifier.

[0129] In this case, the NSSMF may further allocate an identifier to the network slice subnet instance corresponding to the network slice subnet template, that is, allocate a network slice subnet instance identifier (NSSI ID). One network slice subnet instance can be obtained by using one network slice subnet template through instantiation once.

[0130] Step S303: The NSSMF decomposes the network slice subnet requirement information into network service requirement information, service configuration requirement information, and transport network requirement information in a network slice subnet based on the network slice subnet template.

[0131] The NSSMF obtains, from the network slice subnet requirement information based on the network slice subnet template, an input parameter required for network function subnet instantiation, network connection point information of the network function node, service access point information of the network function node, network connection information between the network function nodes, and service connection information between the network function nodes.

[0132] If the component information required for network slice subnet instantiation further includes index information of a network service descriptor corresponding to a virtualized network function included in the network slice subnet instance, that is, the NSST includes an NSD index file corresponding to VNFs included in the NSSI, the NSSMF generates an instantiation input parameter of the NSD based on the obtained five types of information, that is, generates an input parameter required for NS instantiation. In this case, the network service requirement information is the instantiation input parameter of the NSD.

[0133] If the component information required for network slice subnet instantiation includes no index information of a network service descriptor corresponding to a virtualized network function included in the network slice subnet instance, that is, the NSST includes no an NSD index file corresponding to VNFs included in the NSSI, the NSSMF generates, based on the obtained five types of information, an NSD file corresponding to the VNFs included in the NSSI. In this case, the network service requirement information is the generated NSD file.

[0134] If the component information required for network slice subnet instantiation further includes index information of a first service configuration file, that is, the NSST includes the index information of the first service configuration file, the NSSMF generates an input parameter of the first service configuration file based on the foregoing obtained five types of information. In this case, the service configuration requirement information is the input parameter of the first service configuration file.

[0135] If the component information required for network slice subnet instantiation includes no index information of a first service configuration file, that is, the NSST includes no index information of the first service configuration file, the NSSMF generates the first service configuration file based on the foregoing obtained five types of information, and the service configuration requirement information is the first service configuration file.

[0136] The first service configuration file is a non-service access point configuration file of the network slice subnet instance, that is, includes no service access point configuration file for interconnection between the network slice subnet instance and another network slice subnet instance.

[0137] The transport network requirement information provides an input parameter for transport network instantiation, including providing a network connection input parameter for a network connection between network function nodes.

[0138] Step S304: The NSSMF sends a network service instantiation request to the MANO, where the network service instantiation request includes the network service requirement information.

[0139] The network service instantiation request further includes the network slice subnet template identifier.

[0140] When the network slice subnet instantiation request includes the deployment area of the network slice subnet instance, the network service instantiation request further includes the deployment area of the network slice subnet instance.

[0141] The network service instantiation request further includes a network service descriptor identifier (NSD ID), so that the MANO instantiates an NS corresponding to the NSD ID.

[0142] Step S305: The MANO performs network service instantiation based on the network service requirement information.

[0143] The MANO instantiates the network service based on the network service requirement information, including deploying a detailed location of a network function.

[0144] If the network service requirement information is instantiation requirement information of the NSD, the MANO instantiates the network service based on the instantiation requirement information of the NSD. If the network service requirement information is an NSD file, the MANO instantiates the network service based on the NSD file.

[0145] Step S306: The MANO sends a network service instantiation response to the NSSMF.

[0146] When completing the network service instantiation, the MANO sends the network service instantiation response to the NSSMF, where the network service instantiation response includes the network slice subnet instance identifier (NSSI ID), deployment location information of a network function included in the network slice subnet instance, and network connection point instantiation information of a network connection point corresponding to a VNF. The network connection point instantiation information includes information such as an IP address.

[0147] Step S307: The NSSMF sends a service configuration request to the EMS corresponding to the NSSMF, where the service configuration request includes the service configuration requirement information.

[0148] The service configuration requirement information is the first service configuration file or requirement information of the first service configuration file.

[0149] Step S308: The NSSMF sends a transport network instantiation request to a TN-manager, where the transport network instantiation request includes the transport network requirement information.

[0150] Step S308 is similar to step S208 in the embodiment shown in FIG. 2B, and a difference lies in that step S208 is for a transport network including a network slice subnet node, and step S308 is for a transport network including a network function.

[0151] Step S309: The TN-manager performs transport network instantiation based on the transport network instantiation request.

[0152] When receiving the transport network instantiation request, the TN-manager performs the transport network instantiation based on the transport network instantiation request, to establish a network connection between network functions.

[0153] Step S310: The TN-manager sends an acknowledgement message to the NSSMF

[0154] After completing the transport network instantiation, the TN-manager feeds back the acknowledgement message to the NSSMF, to notify the NSSMF that the transport network instantiation is completed.

[0155] Step S311: The NSSMF obtains, based on the network slice subnet template, network connection point information of the network slice subnet instance and another network slice subnet instance, and service access point information corresponding to the network connection point information of the network slice subnet instance and the another network slice subnet instance.

[0156] A network connection point descriptor of the network slice subnet node describes network connection point information used for a network connection between a network slice subnet node and another network slice subnet node. Therefore, the NSSMF may obtain the network connection point information of the network slice subnet instance and the another network slice subnet instance based on the network connection point descriptor of the network slice subnet node with reference to the network slice subnet requirement information.

[0157] A service access point descriptor of the network slice subnet node describes service access point information used for a service connection between the network slice subnet node and the another network slice subnet node. Therefore, the NSSMF may obtain the service access point information of the network slice subnet instance and the another network slice subnet instance based on the service access point descriptor of the network slice subnet node with reference to the network slice subnet requirement information.

[0158] Step S312: The NSSMF sends instantiation information to the NSMF.

[0159] The instantiation information includes the network slice subnet instance identifier, network connection point instantiation information of the network slice subnet instance, and service access point instantiation information of the network slice subnet instance.

[0160] The network connection point instantiation information of the network slice subnet instance includes a local IP address of a network connection point for interconnection between the network slice subnet instance and the another network slice subnet instance, and further includes information about a network connection point for interconnection between the network slice subnet instance and an application server or an external access device.

[0161] The service access point instantiation information of the network slice subnet instance includes a local IP address of a service access point for interconnection between the network slice subnet instance and the another network slice subnet instance, and further includes service access point information of interconnection between the network slice subnet instance and an application server or an external access device.

[0162] Assuming that an NSSI-1 is interconnected to an NSSI 2, for the NSSI-1, the local IP address is an IP address of the NSSI-1, and a peer IP address is an IP address of the NSSI-2.

[0163] The NSMF may record and store the instantiation information sent by each NSSMF

[0164] It should be noted that step S312 corresponds to step S205a and step S205b in the embodiment shown in FIG. 2A and FIG. 2B.

[0165] It should be noted that an execution sequence of step S304, step S307, and step S308 is not limited to that shown in FIG. 5A and FIG. 5B, and the three steps may be performed simultaneously.

[0166] The NSSMF in the procedure shown in FIG. 5A and FIG. 5B may be any NSSMF. If the network slice instance includes a plurality of network slice subnet instances, there are a plurality of NSSMFs, and a procedure of network slice subnet instantiation for each NSSMF may be performed based on the foregoing procedure.

[0167] FIG. 7 is a schematic flowchart of service connection instantiation according to an embodiment of this application. The procedure is described from a perspective of interaction between an NSMF, an NSSMF, and an EMS. The procedure shown in FIG. 7 may include but is not limited to the following steps.

[0168] Step S400: The NSMF records instantiation information sent by the NSSMF

[0169] Step S401: The NSMF sends a service access request to the NSSMF, where the service access request includes a network slice instance identifier, a network slice subnet template identifier, and service access point information.

[0170] Service access point instantiation information includes local address information and peer address information of a service access point for interconnection between a network slice subnet instance and another network slice subnet instance, and address information of a gateway router. An IP address of the gateway router is an IP address of a next-hop router. For example, a service access point of an NSSI 1 and a service access point of an NSSI 2 are interconnected to each other. For the NSSI 1, a local IP address is an IP address of the service access point of the NSSI 1, and a peer IP address is an IP address of the service access point of the NSSI 2.

[0171] After receiving instantiation information of the network slice subnet instance 1 and the network slice subnet instance 2, the NSMF sends a service access request to the NSSMF 1, where the service access request carries a network slice instance identifier, a network slice subnet template identifier corresponding to the network slice subnet instance 1, and service access point information 1.

[0172] After receiving the instantiation information of the network slice subnet instance 1 and the network slice subnet instance 2, the NSMF sends a service access request to the NSSMF 2, where the service access request carries a network slice instance identifier, a network slice subnet template identifier corresponding to the network slice subnet instance 2, and service access point information 2.

[0173] It should be noted that step S401 corresponds to step S206a and step S206b in the embodiment shown in FIG. 2B.

[0174] Step S402: The NSSMF generates a second service configuration file based on a network slice subnet template and the service access point information, where the second service configuration file is a service configuration file used for interconnection between the network slice subnet instance and the another network slice subnet instance.

[0175] Step S403: The NSSMF sends the second service configuration file to the EMS corresponding to the NSSMF

[0176] Step S404: The EMS completes service configuration based on a first service configuration file and the second service configuration file.

[0177] An EMS 1 corresponding to an NSSMF 1 completes service configuration based on the first service configuration file and the second service configuration file, that is, completes service configuration deployment of the network slice subnet instance, so that the NSSI 1 can access a service to implement a service function.

[0178] For descriptions of the first service configuration file, refer to descriptions of step S303 in the embodiment shown in FIG. 5A.

[0179] Step S405: The NSSMF sends a service access acknowledgement message to the NSMF, where the service access acknowledgement message includes the network slice subnet instance identifier.

[0180] After the EMS completes service configuration, the NSSMF sends the service access acknowledgement message to the NSMF, where the service access acknowledgement message carries the network slice subnet instance identifier, to notify the NSMF that a corresponding network slice subnet instance has accessed a service, for example, the NSSI 1 has accessed the service.

[0181] It should be noted that step S405 corresponds to step S207a and step S207b in the embodiment shown in FIG. 2B.

[0182] The NSSMF in the procedure shown in FIG. 7 may be any NSSMF. If the network slice instance includes a plurality of network slice subnet instances, there are a plurality of NSSMFs, and a procedure of service access instantiation for each NSSMF may be performed based on the foregoing procedure.

[0183] The foregoing describes the methods in the embodiments of this application in detail, and the following provides apparatuses in the embodiments of this application.

[0184] FIG. 8 is a schematic diagram of a logical structure of a device according to an embodiment of this application. The device 40 may include a processing unit 401 and a transceiver unit 402. The device 40 may be the NSMF, the NSSMF, or the TN-manager in the embodiments shown in FIG. 2Aand FIG. 2B, FIG. 5A and FIG. 5B, and FIG. 7.

[0185] If the device 40 is the NSMF in the embodiments shown in FIG. 2A and FIG. 2B, FIG. 5A and FIG. 5B, and FIG. 7, the transceiver unit 402 may be configured to communicate with a CSMF, an NSSMF, and a TN-manager, for example, perform step S201, step S204 (a or b), step S205 (a or b), step S206 (a or b), step S207 (a or b), step S209, and step S210 in the embodiment shown in FIG. 2A and FIG. 2B, perform step S312 in the embodiment shown in FIG. 5B, and perform step S405 in the embodiment shown in FIG. 7. The processing unit 401 may be configured to perform an operation of controlling the NSMF, for example, perform step S202 and step S203 in the embodiment shown in FIG. 2A. For details, refer to corresponding descriptions in the embodiments shown in FIG. 2Aand FIG. 2B, FIG. 5A and FIG. 5B, and FIG. 7. Details are not described herein again.

[0186] If the device 40 is the NSSMF in the embodiments shown in FIG. 2A and FIG. 2B, FIG. 5A and FIG. 5B, and FIG. 7, the transceiver unit 402 may be configured to communicate with an NSMF, a TN-manager, an MANO, and an EMS, for example, perform step S204 (a or b), step S205 (a or b), step S206 (a or b), and step S207 (a or b) in the embodiment shown in FIG. 2Aand FIG. 2B, perform step S301, step S304, step S306, step S307, step S308, and step S310 in the embodiment shown in FIG. 5A and FIG. 5B, and perform step S401, step S403, and step S405 in the embodiment shown in FIG. 7. The processing unit 401 may be configured to perform an operation of controlling the NSSMF, for example, perform step S302, step S303, and step S311 in the embodiment shown in FIG. 5A and FIG. 5B, and perform step S402 in the embodiment shown in FIG. 7. For details, refer to corresponding descriptions in the embodiments shown in FIG. 2A and FIG. 2B, FIG. 5A and FIG. 5B, and FIG. 7. Details are not described herein again.

[0187] If the device 40 is the TN-manager in the embodiments shown in FIG. 2A and FIG. 2B, FIG. 5A and FIG. 5B, and FIG. 7, the transceiver unit 402 may be configured to communicate with an NSMF and an NSSMF, for example, perform step S208 in the embodiment shown in FIG. 2B, and perform step S308 in the embodiment shown in FIG. 5B. The processing unit 401 may be configured to perform an operation of controlling the TN-manager, for example, perform step S209 in the embodiment shown in FIG. 2B and perform step S309 in the embodiment shown in FIG. 5B. For details, refer to corresponding descriptions in the embodiments shown in FIG. 2A and FIG. 2B, FIG. 5A and FIG. 5B, and FIG. 7. Details are not described herein again.

[0188] FIG. 9 is a simplified schematic diagram of an entity structure of a device according to an embodiment of this application. The device 50 may be the NSMF, the NSSMF, or the TN-manager in the embodiments shown in FIG. 2Aand FIG. 2B, FIG. 5Aand FIG. 5B, and FIG. 7. The device 50 includes a transceiver 501, a processor 502, and a memory 503. The transceiver 501, the processor 502, and the memory 503 may be connected to each other by using a bus 504, or may be connected to each other in another manner. A related function implemented by the processing unit 401 shown in FIG. 8 may be implemented by one or more processors 502. A related function implemented by the transceiver unit 402 shown in FIG. 8 may be implemented by the transceiver 501.

[0189] The memory 503 includes but is not limited to a random access memory (random access memory, RAM), a read-only memory (read-only memory, ROM), an erasable programmable read-only memory (erasable programmable read only memory, EPROM), or a portable read-only memory (compact disc read-only memory, CD-ROM). The memory 503 is configured to store a related instruction and related data.

[0190] The transceiver 501 is configured to send data and/or signaling, and receive data and/or signaling.

[0191] The processor 502 may include one or more processors, for example, include one or more central processing units (central processing unit, CPU). When the processor 502 is one CPU, the CPU may be a single-core CPU, or may be a multi-core CPU.

[0192] If the device 50 is the NSMF, the processor 502 is configured to support the NSMF in performing step S202 and step S203 in the embodiment shown in FIG. 2A.

[0193] If the device 50 is the NSSMF, the processor 502 is configured to support the NSSMF in performing step S302, step S303, and step S311 in the embodiment shown in FIG. 5A and FIG. 5B, and performing step S402 in the embodiment shown in FIG. 7.

[0194] If the device 50 is the TN-manager, the processor 502 is configured to support the TN-manager in performing step S206a

S206b in the embodiment shown in FIG. 2B and step S309 in the embodiment shown in FIG. 5B.

[0195] The memory 503 is configured to store program code and data of the device 50.

[0196] The transceiver 501 is configured to communicate with another device. If the device 50 is a CSMF, the transceiver 501 is configured to communicate with an NSMF entity, an operator, or a third-party customer. If the device is an NSMF, the transceiver 501 is configured to communicate with a CSMF, an NSSMF, and a TN-manager. If the device is an NSSMF entity, the transceiver is configured to communicate with an NSMF, a TN-manager, an MANO, and an EMS.

[0197] For details of the steps performed by the processor 502 and the transceiver 501, refer to descriptions in the embodiments shown in FIG. 2A and FIG. 2B, FIG. 5A and FIG. 5B, and FIG. 7. Details are not described herein again.

[0198] It may be understood that FIG. 9 shows merely a simplified design of the device. In actual applications, the device may further include other necessary components, including but not limited to any quantities of transceivers, processors, controllers, memories, and communications units. All devices capable of implementing this application fall within the protection scope of this application.

[0199] An embodiment of this application further provides a network slice management system which is not claimed as such, including the NSMF, the NSSMF, and the CSMF shown in FIG. 1, and further including the TN-manager, the MANO, the EMS in the embodiments shown in FIG. 2A and FIG. 2B, FIG. 5A and FIG. 5B, and FIG. 7, and the like.

[0200] A person of ordinary skill in the art may understand that all or some of the processes of the methods in the embodiments may be completed by a computer program instructing relevant hardware. The program may be stored in a computer-readable storage medium. When the program is executed, the processes of the foregoing methods embodiments are performed. The foregoing storage medium includes any medium that can store program code, such as a ROM, a random access memory RAM, a magnetic disk, or an optical disk. Therefore, another embodiment of this application provides a computer-readable storage medium. The computer-readable storage medium stores an instruction, and when the instruction is run on a computer, the computer is enabled to perform the methods in the foregoing aspects.

[0201] Still another embodiment of this application, which is not claimed as such, further provides a computer program product including an instruction, and when the computer program product is run on a computer, the computer is enabled to perform the methods in the foregoing aspects.

[0202] A person of ordinary skill in the art may be aware that, with reference to the examples described in the embodiments disclosed in this application, units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraint conditions of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application.

[0203] It may be clearly understood by the person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, refer to a corresponding process in the foregoing method embodiments, and details are not described herein again.

[0204] In the several embodiments provided in this application, it should be understood that, the disclosed system, apparatus, and method may be implemented in another manner. For example, division into the units is merely logical function division and may be other division in actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms.

[0205] The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one location, or may be distributed on a plurality of network units. Some or all of the units may be selected depending on actual requirements to achieve the objectives of the solutions in the embodiments.

[0206] In addition, functional units in the embodiments of this application may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit.

[0207] All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof in the foregoing embodiments. When software is used to implement the embodiments, all or some of the embodiments may be implemented in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedure or functions according to the embodiments of the present invention are all or partially generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instruction may be stored in a computer-readable storage medium, or transmitted by using the computer-readable storage medium. The computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (digital subscriber line, DSL)) manner or a wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server and a data center that are integrated by one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid-state disk (Solid State Disk, SSD)), or the like.


Claims

1. A network slice management method, comprising:

receiving (201), by a network slice management function entity, a network slice instantiation request, wherein the network slice instantiation request comprises network slice requirement information, and the network slice requirement information comprises a network slice template identifier or a network slice type, and network slice deployment requirement information;

obtaining (202), by the network slice management function entity, a network slice template based on the network slice template identifier or the network slice type;

decomposing (203), by the network slice management function entity based on the network slice template, the network slice requirement information into network slice subnet requirement information of a network slice subnet comprised in the network slice template and transport network requirement information in the network slice;

for each network slice subnet comprised in the network slice, sending (204a, 204b), by the network slice management function entity, a network slice subnet instantiation request to a network slice subnet management function entity, wherein the network slice subnet instantiation request comprises the network slice subnet requirement information;

receiving (205a, 205b), by the network slice management function entity, a network slice subnet instantiation response sent by the network slice subnet management function entity, wherein the network slice subnet instantiation response comprises network slice subnet instantiation information, and the network slice subnet instantiation information comprises a network slice subnet instance identifier, service access point instantiation information of a network slice subnet instance, and network connection point instantiation information of the network slice subnet instance;

sending (208), by the network slice management function entity, a transport network instantiation request to a transport network manager, wherein the transport network instantiation request comprises the transport network requirement information in the network slice and network connection point information of all network slice subnet instances; and

triggering, by the network slice management function entity, establishment of a service connection of each network slice subnet instance based on service access point information obtained after instantiation of each network slice subnet; and wherein

the network slice template comprises a network slice subnet template identifier, a network connection point descriptor of a network slice subnet node, a service access point descriptor of the network slice subnet node and a network connection descriptor between network slice subnet nodes, and a service connection descriptor between the network slice subnet nodes;

wherein the network connection point descriptor of the network slice subnet node is used to describe network connection point information of the network slice subnet node; the service access point descriptor of the network slice subnet node is used to describe service access point information of the network slice subnet node; the network connection descriptor between the network slice subnet nodes is used to describe network connection information between the network slice subnet nodes; and the service connection descriptor between the network slice subnet nodes is used to describe service connection information between the network slice subnet nodes.


 
2. The method according to claim 1, wherein a network slice subnet template corresponding to the network slice subnet template identifier comprises a node descriptor of a network function node comprised in the network slice subnet, a network connection point descriptor of the network function node, a service access point descriptor of the network function node, a network connection descriptor between the network function nodes, and a service connection descriptor between the network function nodes.
 
3. The method according to any one of claims 1 to 2, wherein component information required for network slice instantiation performed by using the network slice template further comprises a network service descriptor index file corresponding to a virtualized network function comprised in the network slice, and the network service descriptor index file is used for instantiating virtual resource deployment of the virtualized network function.
 
4. The method according to any one of claims 1 to 2, wherein the network slice subnet instantiation request further comprises a deployment area of the network slice subnet instance, and the network slice subnet instance is an instance corresponding to the network slice subnet; and
before the sending, by the network slice management function entity, a network slice subnet instantiation request to a network slice subnet management function entity, the method further comprises:
determining, by the network slice management function entity, the deployment area of the network slice subnet instance based on the network slice requirement information.
 
5. The method according to claim 4, wherein the network slice subnet requirement information further comprises the network slice subnet template identifier or the network slice type.
 
6. The method according to claim 1, wherein the triggering, by the network slice management function entity, establishment of a service connection of each network slice subnet instance based on service access point information obtained after instantiation of each network slice subnet comprises:
sending, by the network slice management function entity, a service access request to a corresponding network slice subnet management function entity based on the service access point information obtained after instantiation of each network slice subnet, wherein the service access request comprises a network slice instance identifier, a corresponding network slice subnet template identifier, and corresponding service access point information, and the service access request is used to trigger a corresponding network slice subnet association function entity to establish a service connection.
 
7. An entity for performing the method according to any one of claims 1-6.
 


Ansprüche

1. Verfahren zur Verwaltung von Netzwerkslices, umfassend:

Empfangen (201) durch eine Netzwerkslice-Verwaltungsfunktionsentität einer Netzwerkslice-Instanziierungsanforderung, wobei die Netzwerkslice-Instanziierungsanforderung Netzwerkslice-Anforderungsinformationen umfasst, und die Netzwerkslice-Anforderungsinformationen eine Netzwerkslice-Vorlagenkennung oder einen Netzwerkslice-Typ, und Netzwerkslice-Einsatzanforderungsinformationen umfassen;

Erhalten (202) durch die Netzwerkslice-Verwaltungsfunktionsentität einer Netzwerkslice-Vorlage basierend auf der Netzwerkslice-Vorlagenkennung oder dem Netzwerkslice-Typ;

Aufgliedern (203) durch die Netzwerkslice-Verwaltungsfunktionsentität basierend auf der Netzwerkslice-Vorlage der Netzwerkslice-Anforderungsinformationen in Netzwerkslice-Subnetz-Anforderungsinformationen eines Netzwerkslice-Subnetzes, das in der Netzwerkslice-Vorlage umfasst ist, und Transport-Netzwerk-Anforderungsinformationen in dem Netzwerkslice;

für jedes Netzwerkslice-Subnetz, das in dem Netzwerkslice umfasst ist, Senden (204a, 204b) durch die Netzwerkslice-Subnetz-Verwaltungsfunktionsentität einer Netzwerkslice-Subnetz-Instanziierungsanforderung an eine Netzwerkslice-Subnetz-Verwaltungsfunktionsentität, wobei die Netzwerkslice-Subnetz-Instanziierungsanforderung Netzwerkslice-Subnetz-Anforderungsinformationen umfasst;

Empfangen (205a, 205b) durch die Netzwerkslice-Verwaltungsfunktionsentität einer Netzwerkslice-Subnetz-Instanziierungsantwort, die von der Netzwerkslice-Subnetz-Verwaltungsfunktionsentität gesendet wird, wobei die Netzwerkslice-Subnetz-Instanziierungsantwort Netzwerkslice-Subnetz-Instanziierungsinformationen umfasst, und die Netzwerkslice-Subnetzslice-Instanziierungsinformationen eine Netzwerkslice-Subnetzinstanzkennung, Dienstzugriffspunkt-Instanziierungsinformationen einer Netzwerkslice-Subnetzinstanz und Netzwerkverbindungspunkt-Instanziierungsinformationen der Netzwerkslice-Subnetzinstanz umfassen;

Senden (208) durch die Netzwerkslice-Verwaltungsfunktionsentität einer Transport-Netzwerk-Instanziierungsanforderung an einen Transportnetzwerkverwalter, wobei die Transport-Netzwerk-Instanziierungsanforderung die Transport-Netzwerk-Anforderungsinformationen in dem Netzwerkslice und Netzwerkverbindungspunkt-Informationen aller Netzwerkslice-Subnetzinstanzen umfasst; und

Auslösen durch die Netzwerkslice-Verwaltungsfunktionsentität des Aufbaus einer Dienstverbindung jeder Netzwerkslice-Subnetzinstanz basierend auf Dienstzugriffspunkt-Informationen, die nach der Instanziierung jedes Netzwerkslice-Subnetzes erhalten wurden; und wobei

die Netzwerkslice-Vorlage eine Netzwerkslice-Subnetz-Vorlagenkennung, einen Netzwerkverbindungspunkt-Deskriptor eines Netzwerkslice-Subnetzknotens, einen Dienstzugriffspunkt-Deskriptor des Netzwerkslice-Subnetzknotens und einen Netzwerkverbindungsdeskriptor zwischen Netzwerkslice-Subnetzknoten und einen Dienstverbindungsdeskriptor zwischen den Netzwerkslice-Subnetzknoten umfasst;

wobei der Netzwerkverbindungspunkt-Deskriptor des Netzwerkslice-Subnetzknotens verwendet wird, um Netzwerkverbindungspunkt-Informationen des Netzwerkslice-Subnetzknotens zu beschreiben; der Dienstzugriffspunkt-Deskriptor des Netzwerkslice-Subnetzkwerknotens verwendet wird, um Dienstzugriffspunkt-Informationen des Netzwerkslice-Subnetzknotens zu beschreiben; der Netzwerkverbindungsdeskriptor zwischen den Netzwerkslice-Subnetzknoten verwendet wird, um Netzwerkverbindungsinformationen zwischen den Netzwerkslice-Subnetzknoten zu beschreiben; und der Dienstverbindungsdeskriptor zwischen den Netzwerkslice-Subnetzknoten verwendet wird, um Dienstverbindungsinformationen zwischen den Netzwerkslice-Subnetzknoten zu beschreiben.


 
2. Verfahren nach Anspruch 1, wobei eine Netzwerkslice-Subnetzvorlage, die der Netzwerkslice-Subnetz-Vorlagenkennung entspricht, einen Knotendeskriptor eines Netzwerkfunktionsknotens, der in dem Netzwerkslice-Subnetz umfasst ist, einen Netzwerkverbindungspunkt-Deskriptor des Netzwerkfunktionsknotens, einen Dienstzugriffspunkt-Deskriptor des Netzwerkfunktionsknotens, einen Netzwerkverbindungsdeskriptor zwischen den Netzwerkfunktionsknoten und einen Dienstverbindungsdeskriptor zwischen den Netzwerkfunktionsknoten umfasst.
 
3. Verfahren nach einem der Ansprüche 1 bis 2, wobei Komponenteninformationen, die für die Netzwerkslice-Instanziierung erforderlich sind, die unter Verwenden der Netzwerkslice-Vorlage durchgeführt wird, ferner eine Netzwerkdienstdeskriptor-Indexdatei umfassen, die einer virtualisierten Netzwerkfunktion entspricht, die in dem Netzwerkslice umfasst ist und die Netzwerkdienstdeskriptor-Indexdatei zum Instanziieren des Einsatzes virtueller Ressourcen der virtualisierten Netzwerkfunktion verwendet wird.
 
4. Verfahren nach einem der Ansprüche 1 bis 2, wobei die Netzwerkslice-Subnetz-Instanziierungsanforderung ferner einen Einsatzbereich der Netzwerkslice-Subnetzinstanz umfasst, und die Netzwerkslice-Subnetzinstanz eine Instanz ist, die dem Netzwerkslice-Subnetz entspricht; und
vor dem Senden durch die Netzwerkslice-Verwaltungsfunktionsentität einer Netzwerkslice-Subnetz-Instanziierungsanforderung an eine Netzwerkslice-Subnetz-Verwaltungsfunktionsentität, das Verfahren ferner Folgendes umfasst:
Bestimmen, durch die Netzwerkslice-Verwaltungsfunktionsentität, des Einsatzbereichs der Netzwerkslice-Subnetzinstanz basierend auf den Netzwerkslice-Anforderungsinformationen.
 
5. Verfahren nach Anspruch 4, wobei die Netzwerkslice-Subnetz-Anforderungsinformationen ferner die Netzwerkslice-Subnetz-Vorlagenkennung oder den Netzwerkslice-Typ umfassen.
 
6. Verfahren nach Anspruch 1, wobei das Auslösen durch die Netzwerkslice-Verwaltungsfunktionsentität des Aufbaus einer Dienstverbindung jeder Netzwerkslice-Subnetzinstanz basierend auf Dienstzugriffspunkt-Informationen, die nach der Instanziierung jedes Netzwerkslice-Subnetzes erhalten werden, Folgendes umfasst:
Senden durch die Netzwerkslice-Verwaltungsfunktionsentität einer Dienstzugriffsanforderung an eine entsprechende Netzwerkslice-Subnetz-Verwaltungsfunktionsentität basierend auf den Dienstzugriffspunkt-Informationen, die nach der Instanziierung jedes Netzwerkslice-Subnetzes erhalten wurden, wobei die Dienstzugriffsanforderung eine Netzwerkslice-Instanzkennung, eine entsprechende Netzwerkslice-Subnetz-Vorlagenkennung und entsprechende Dienstzugriffspunkt-Informationen umfasst, und die Dienstzugriffsanforderung dazu verwendet wird, eine entsprechende Netzwerkslice-Subnetz-Assoziationsfunktionsentität auszulösen, um eine Dienstverbindung aufzubauen.
 
7. Entität zum Durchführen des Verfahrens nach einem der Ansprüche 1-6.
 


Revendications

1. Procédé de gestion de tranches de réseau, comprenant :

la réception (201), par une entité de fonction de gestion de tranches de réseau, d'une demande d'instanciation de tranches de réseau, dans lequel la demande d'instanciation de tranches de réseau comprend des informations d'exigence de tranches de réseau, et les informations d'exigence de tranches de réseau comprennent un identifiant de modèle de tranches de réseau ou un type de tranches de réseau, et des informations d'exigence de déploiement de tranches de réseau ;

l'obtention (202), par l'entité de fonction de gestion de tranches de réseau, d'un modèle de tranches de réseau sur la base de l'identifiant de modèle de tranches de réseau ou du type de tranches de réseau ;

la décomposition (203), par l'entité de fonction de gestion de tranches de réseau sur la base du modèle de tranches de réseau, des informations d'exigence de tranches de réseau en informations d'exigence de sous-réseau de tranches de réseau d'un sous-réseau de tranches de réseau compris dans le modèle de tranches de réseau et en informations d'exigence de réseau de transport dans la tranche de réseau ;

pour chaque sous-réseau de tranches de réseau compris dans la tranche de réseau, l'envoi (204a, 204b), par l'entité de fonction de gestion de tranches de réseau, d'une demande d'instanciation de sous-réseau de tranches de réseau à une entité de fonction de gestion de sous-réseau de tranches de réseau, dans lequel la demande d'instanciation de sous-réseau de tranches de réseau comprend les informations d'exigence de sous-réseau de tranches de réseau ;

la réception (205a, 205b), par l'entité de fonction de gestion de tranches de réseau, d'une réponse d'instanciation de sous-réseau de tranches de réseau envoyée par l'entité de fonction de gestion de sous-réseau de tranches de réseau, dans lequel la réponse d'instanciation de sous-réseau de tranches de réseau comprend des informations d'instanciation de sous-réseau de tranches de réseau, et les informations d'instanciation de sous-réseau de tranches de réseau comprennent un identifiant d'instance de sous-réseau de tranches de réseau, des informations d'instanciation de point d'accès de service d'une instance de sous-réseau de tranches de réseau et des informations d'instanciation de point de connexion de réseau de l'instance de sous-réseau de tranches de réseau ;

l'envoi (208), par l'entité de fonction de gestion de tranches de réseau, d'une demande d'instanciation de réseau de transport à un gestionnaire de réseau de transport, dans lequel la demande d'instanciation de réseau de transport comprend les informations d'exigence de réseau de transport dans la tranche de réseau et des informations de point de connexion de réseau de toutes les instances de sous-réseau de tranches de réseau ; et

le déclenchement, par l'entité de fonction de gestion de tranches de réseau, de l'établissement d'une connexion de service de chaque instance de sous-réseau de tranches de réseau sur la base d'informations de point d'accès de service obtenues après l'instanciation de chaque sous-réseau de tranches de réseau ; et dans lequel

le modèle de tranches de réseau comprend un identifiant de modèle de sous-réseau de tranches de réseau, un descripteur de point de connexion de réseau d'un nœud de sous-réseau de tranches de réseau, un descripteur de point d'accès de service du nœud de sous-réseau de tranches de réseau et un descripteur de connexion de réseau entre des nœuds de sous-réseau de tranches de réseau, et un descripteur de connexion de service entre les nœuds de sous-réseau de tranches de réseau ;

dans lequel le descripteur de point de connexion de réseau du nœud de sous-réseau de tranches de réseau est utilisé pour décrire des informations de point de connexion de réseau du nœud de sous-réseau de tranches de réseau ; le descripteur de point d'accès de service du nœud de sous-réseau de tranches de réseau est utilisé pour décrire des informations de point d'accès de service du nœud de sous-réseau de tranches de réseau ; le descripteur de connexion de réseau entre les nœuds de sous-réseau de tranches de réseau est utilisé pour décrire des informations de connexion de réseau entre les nœuds de sous-réseau de tranches de réseau ; et le descripteur de connexion de service entre les nœuds de sous-réseau de tranches de réseau est utilisé pour décrire des informations de connexion de service entre les nœuds de sous-réseau de tranches de réseau.


 
2. Procédé selon la revendication 1, dans lequel un modèle de sous-réseau de tranches de réseau correspondant à l'identifiant de modèle de sous-réseau de tranches de réseau comprend un descripteur de nœud d'un nœud de fonction de réseau compris dans le sous-réseau de tranches de réseau, un descripteur de point de connexion de réseau du nœud de fonction de réseau, un descripteur de point d'accès de service du nœud de fonction de réseau, un descripteur de connexion de réseau entre les nœuds de fonction de réseau et un descripteur de connexion de service entre les nœuds de fonction de réseau.
 
3. Procédé selon l'une quelconque des revendications 1 et 2, dans lequel des informations de composant requises pour l'instanciation de tranches de réseau effectuée en utilisant le modèle de tranches de réseau comprennent en outre un fichier d'index de descripteur de service de réseau correspondant à une fonction de réseau virtualisée comprise dans la tranche de réseau, et le fichier d'index de descripteur de service de réseau est utilisé pour instancier le déploiement de ressources virtuelles de la fonction de réseau virtualisée.
 
4. Procédé selon l'une quelconque des revendications 1 et 2, dans lequel la demande d'instanciation de sous-réseau de tranches de réseau comprend en outre une zone de déploiement de l'instance de sous-réseau de tranches de réseau, et l'instance de sous-réseau de tranches de réseau est une instance correspondant au sous-réseau de tranches de réseau ; et
avant l'envoi, par l'entité de fonction de gestion de tranches de réseau, d'une demande d'instanciation de sous-réseau de tranches de réseau à une entité de fonction de gestion de sous-réseau de tranches de réseau, le procédé comprend en outre :
la détermination, par l'entité de fonction de gestion de tranches de réseau, de la zone de déploiement de l'instance de sous-réseau de tranches de réseau sur la base des informations d'exigence de tranches de réseau.
 
5. Procédé selon la revendication 4, dans lequel les informations d'exigence de sous-réseau de tranches de réseau comprennent en outre l'identifiant de modèle de sous-réseau de tranches de réseau ou le type de tranches de réseau.
 
6. Procédé selon la revendication 1, dans lequel le déclenchement, par l'entité de fonction de gestion de tranches de réseau, de l'établissement d'une connexion de service de chaque instance de sous-réseau de tranches de réseau sur la base d'informations de point d'accès de service obtenues après l'instanciation de chaque sous-réseau de tranches de réseau comprend :
l'envoi, par l'entité de fonction de gestion de tranches de réseau, d'une demande d'accès de service à une entité de fonction de gestion de sous-réseau de tranches de réseau correspondante sur la base des informations de point d'accès de service obtenues après l'instanciation de chaque sous-réseau de tranches de réseau, dans lequel la demande d'accès de service comprend un identifiant d'instance de tranches de réseau, un identifiant de modèle de sous-réseau de tranches de réseau correspondant et des informations de point d'accès de service correspondantes, et la demande d'accès de service est utilisée pour déclencher une entité de fonction d'association de sous-réseau de tranches de réseau correspondante pour établir une connexion de service.
 
7. Entité pour mettre en œuvre le procédé selon l'une quelconque des revendications 1 à 6.
 




Drawing
































Cited references

REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Patent documents cited in the description