WO2019062830A1

WO2019062830A1 - Method and device for generating example service topology

Info

Publication number: WO2019062830A1
Application number: PCT/CN2018/108233
Authority: WO
Inventors: 李卓明
Original assignee: 华为技术有限公司
Priority date: 2017-09-29
Filing date: 2018-09-28
Publication date: 2019-04-04
Also published as: CN109586938A; CN109586938B

Abstract

The embodiments of the present application provide a method for generating an example service topology, a device and a system, being able to improve the flexibility and simplicity of slice service deployment. Said method comprises: a device for generating an example service topology acquiring a network topology and a logical service topology of a slice, and a generation policy of the example service topology, the network topology being used for characterizing a network layout composed of N network function examples and the physical connection relationship of the N network function examples, the logical service topology being used for characterizing a network layout composed of M network functions and the service connection relationship of the M network functions, and the generation policy being used for characterizing whether a service connection is allowed to be established between any two network function examples of the N network function examples; and generating the example service topology of the slice according to the network topology, the logical service topology and the generation policy, the example service topology being used for characterizing a network layout composed of the N network function examples and the service connection relationship of the N network function examples.

Description

Method and device for generating instance business topology

This application claims the priority of the Chinese Patent Application filed on Sep. 29, 2017, the Chinese National Intellectual Property Office, the application number is 201710909314.7, and the invention is entitled "Method and Apparatus for Generating the Topology Business Topology", the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for generating an instance service topology.

Background technique

Currently, in the 3rd generation partnership project (3GPP) standard, the process of the slice management function entity creating a slice instance for the customer on the infrastructure according to the slice template according to the customer order is called slice instantiation.

Specifically, slice instantiation usually includes two processes of network deployment and service deployment. In the prior art, during the service deployment process of the slice, the service configuration script of the network function entity in the slice template needs to be configured. The service configuration script is written according to the service topology designed for the slice instance in advance (since the service topology is designed for the slice instance, so it can also be called the slice instance service topology). That is to say, each time a slice instance is deployed, the carrier needs to ask the vendor to design the sliced instance service topology and write the corresponding service configuration script. The service configuration script can complete the service deployment of the slice. However, this has the following problems:

First, since the network function in the slice may be the operator's or the customer's, and the network environment of each operator and customer is different, the slice instantiation needs to plan and design various slices in advance according to various situations. The instance business topology, and the corresponding business configuration scripts are written in advance, which makes the slicing instantiation work very complicated. In addition, if you deploy a slice in a different location, there are more or less differences in the network environment. In this case, the operator needs to find the vendor's instance service topology and write the corresponding service configuration script, which is very inflexible.

Second, because the instance service topology of the slice is designed according to the operation and maintenance strategy and service requirements proposed by the operator and the customer in advance, if the operation and maintenance strategy and service requirements change, the operator needs to find the manufacturer to redesign the slice. The instance service topology and the corresponding service configuration scripts are very inflexible, which limits the large-scale commercialization of the carrier slicing service.

In summary, the existing service topology of the existing slice designing process makes the service deployment process very complicated and inflexible. Therefore, how to obtain the instance service topology to improve the flexibility and simplicity of the slice service deployment is an urgent problem to be solved.

Summary of the invention

The embodiment of the present application provides a method and a device for generating an instance service topology corresponding to a slice, which can improve the flexibility and simplicity of the slice service deployment.

To achieve the above objective, the embodiment of the present application provides the following technical solutions:

The first aspect provides a method for generating an instance service topology, where the method includes: generating, by a device for generating an instance service topology, a network topology of a slice, a logical service topology of the slice, and a generation policy of an instance service topology of the slice; The network topology is used to represent a network layout consisting of N network function instances and physical connection relationships between the N network function instances, the N network function instances corresponding to M different network functions. The logical service topology is used to represent a network layout formed by the M network functions and a service connection relationship between the M network functions, where the generation strategy is used to represent any two network function instances of the N network function instances. Whether the service connection is allowed to be established, and M and N are positive integers. The device for generating the service topology generates the instance service topology of the slice according to the network topology, the logical service topology and the generation policy, where the instance service topology is generated. A network layout for characterizing the N network function instances and the service connection relationship between the N network function instances. That is to say, in the embodiment of the present application, the instance service topology of the slice is automatically generated by the device for generating the instance service topology, and the service deployment of the slice can be further completed according to the service topology of the instance. You can re-generate the changed network topology or logical service topology or generate a policy and regenerate the instance service topology in the case of a network topology or a logical service topology or a policy change. As long as the network topology or the logical service topology or the generation policy is changed, the vendor needs to redesign the sliced instance service topology and write the corresponding service configuration script according to the sliced instance service topology. The service deployment of the slice is completed, so that the embodiment of the present application can improve the flexibility and simplicity of the slice service deployment.

In a possible design, the generating device of the instance service topology acquires the network topology of the slice, the logical service topology of the slice, and the generation policy of the instance service topology of the slice, including: the device for generating the instance service topology from the slice template Obtaining the network topology information corresponding to the network topology, the logical service topology information corresponding to the logical service topology, and the generation policy; the device for generating the service topology acquires the network topology according to the network topology information; The generating device acquires the logical service topology according to the logical service topology information. That is, the embodiment of the present application sets the information of the network topology of the slice, the information of the logical service topology of the slice, and the generation policy of the instance service topology of the slice in a slice template, because the slice template is by a vendor or The slice operation and maintenance personnel are set in advance, so based on this solution, the versatility and portability of the slice service deployment can be improved.

In a possible design, the generating device of the instance service topology acquires the network topology of the slice, the logical service topology of the slice, and the generation policy of the instance service topology of the slice, including: the device for generating the instance service topology from the slice template Obtaining the network topology information corresponding to the network topology, the logical service topology information corresponding to the logical service topology, and the default generation policy of the service topology of the instance; and the generating device of the instance service topology acquiring the external generation strategy of the service topology of the instance The generation policy of the instance service topology is determined by a default generation policy and an external generation policy: for example, the external generation policy may be set to a high priority policy by a priority manner, so that when the instance service topology generation device obtains When the external generation policy is generated, the external generation policy is set as the generation strategy of the instance business topology; or the default generation policy and the external generation policy may be combined to form an instance business topology generation policy. The generating device of the example service topology acquires the network topology according to the network topology information. The device for generating the service topology acquires the logical service topology according to the logical service topology information. In one aspect, the embodiment of the present application sets the information of the network topology of the slice, the information of the logical service topology of the slice, and the default generation policy of the instance service topology of the slice in a slice template, because the slice template is by a vendor or The slice operation and maintenance personnel are set in advance, so based on this solution, the versatility and portability of the slice service deployment can be improved. On the other hand, since the generation strategy of the instance service topology is determined by the default generation policy and the external generation policy, not only is the user more selective; and the external policy can be customized according to the customer's needs and is easy to implement. Therefore, it is convenient to realize the user's personalized requirement for the slice without increasing the difficulty of implementation, without the intervention of the manufacturer.

In a possible design, the generating device of the instance service topology acquires the network topology of the slice, the logical service topology of the slice, and the generation policy of the instance service topology of the slice, including: the device for generating the instance service topology from the slice template Obtaining the network topology information corresponding to the network topology and the logical service topology information corresponding to the logical service topology; and the generating device of the instance service topology acquiring the external generation policy of the service topology of the instance, wherein the generation strategy of the instance service topology The generating device generates the policy; the generating device of the instance service topology acquires the network topology according to the network topology information; and the generating device of the instance service topology obtains the logical service topology according to the logical service topology information. In one aspect, the embodiment of the present application sets the information of the network topology of the slice and the information of the logical service topology of the slice in a slice template, and the slice template is preset by the vendor personnel or the slice operation and maintenance personnel, so This solution can improve the versatility and portability of the slicing business deployment. On the other hand, since the generation strategy of the instance service topology is an external generation policy, and the external policy can be formulated according to the needs of the customer, and is easy to implement, based on the solution, the user can be easily implemented without increasing the difficulty of implementation. There is no need for vendor intervention for the personalized needs of the slice.

In a possible design, the network topology information includes a network service descriptor NSD, and the generating device of the instance service topology acquires the network topology according to the network topology information, and the device includes: the service topology generating device generates the NSD according to the slice template. The network topology of the slice. This scenario is more commonly used in the scenario where the network topology processing entity and the instance service topology generating device are deployed together, which can save device resources.

In one possible design, the network topology information includes a network service descriptor NSD.

In the network deployment phase, the instance service topology generating device sends a network deployment request to the network topology processing entity, where the network deployment request carries the NSD in the slice template, and the network topology processing entity performs the NFV network deployment according to the NFV network deployment. An NFV network serves the NS instance, and sends a network deployment response to the instance service topology generating device, where the network deployment response carries the network topology of the NS instance. After receiving the network deployment response from the network topology processing entity, the device for generating the instance service topology may save the correspondence between the NSD (or the slice template or the slice template ID) and the network topology of the NS instance. In the subsequent instance service topology generation phase, the device for generating the instance service topology obtains the network topology according to the network topology information, and the device for generating the instance service topology determines the network topology of the network service instance corresponding to the NSD as the network topology of the slice. Alternatively, for a case where a slice template corresponds to multiple slice orders, after the instance service topology generating device receives the network deployment response from the network topology processing entity, the network topology of the NS instance and the slice order (or the slice order number) may be further saved. Correspondence relationship between the NSD (or slice template or slice template ID), the slice order (or the number of the slice order) and the network topology of the NS instance. In the subsequent instance service topology generation phase, the device for generating the instance service topology obtains the network topology according to the network topology information, and the device for generating the instance service topology determines the network service corresponding to the NSD and the slice order of the slice (or the number of the slice order). The network topology of the instance is the network topology of the slice. This scenario is more commonly used in scenarios where the network topology processing entity is deployed separately from the instance service topology generation device, and the reliability is high.

Alternatively, after generating an NFV NS instance, the network topology processing entity allocates an NS instance ID to the generated NS instance, and sends a network deployment response to the instance service topology generating device, where the network deployment response carries the NS instance ID. After receiving the network deployment response from the network topology processing entity, the device for generating the instance service topology may store the correspondence between the NSD (or the slice template or the slice template ID) and the NS instance ID. In the subsequent instance service topology generation phase, the device for generating the instance service topology obtains the network topology according to the network topology information, and the device for generating the instance service topology determines the network service instance ID corresponding to the slice according to the NSD, and processes the entity to the network topology. And sending a network topology request message, where the network topology request message carries the network service instance ID; and further, the instance service topology generating device receives the network topology of the slice from the network topology processing entity. Alternatively, in the case that one slice template corresponds to multiple slice orders, the instance service topology generating device further needs to save the correspondence between the slice order (or the slice order number) and the NS instance ID, and the NSD is established (in this case). Or the slice template or slice template ID), the correspondence between the slice order and the NS instance ID. In the subsequent instance service topology generation phase, the device for generating the instance service topology obtains the network topology according to the network topology information, and the device for generating the instance service topology determines the network service instance ID corresponding to the slice according to the slice order of the slice and the NSD. And sending a network topology request message to the network topology processing entity, where the network topology request message carries the network service instance ID; and further, the instance service topology generating device receives the network topology of the slice from the network topology processing entity. This scenario is more commonly used in scenarios where the network topology processing entity is deployed separately from the instance service topology generation device, and the reliability is high.

In a possible design, the network topology information includes a network service descriptor NSD ID, and the generating device of the instance service topology acquires the network topology according to the network topology information, including: the service topology generating device is configured according to the NSD ID in the slice template. The corresponding NSD is loaded, and the network topology of the slice is generated according to the NSD. On the one hand, this situation is more commonly used in the scenario where the network topology processing entity and the instance service topology generating device are deployed together, which can save device resources. On the other hand, since the NSD can be loaded from the outside and does not need to be written in the slice template, the resources of the slice template can be saved.

In one possible design, the network topology information includes a network service descriptor NSD ID.

In the network deployment phase, the instance service topology generating device sends a network deployment request to the network topology processing entity, where the network deployment request carries the NSD ID in the slice template, and the network topology processing entity loads the corresponding NSD according to the NSD ID. After the NFV network is deployed, an NFV network service NS instance is generated, and a network deployment response is sent to the instance service topology generating device, where the network deployment response carries the network topology of the NS instance. After receiving the network deployment response from the network topology processing entity, the device for generating the instance service topology may save the correspondence between the NSD ID (or the slice template or the slice template ID) and the network topology of the NS instance. In the subsequent instance service topology generation phase, the device for generating the instance service topology obtains the network topology according to the network topology information, and the device for generating the instance service topology determines that the network topology of the network service instance corresponding to the NSD ID is the network topology of the slice. Alternatively, for a case where a slice template corresponds to multiple slice orders, after the instance service topology generating device receives the network deployment response from the network topology processing entity, the network topology of the NS instance and the slice order (or the slice order number) may be further saved. Correspondence relationship between the NSD ID (or slice template or slice template ID), the slice order (or the number of the slice order) and the network topology of the NS instance. In the subsequent instance service topology generation phase, the device for generating the instance service topology obtains the network topology according to the network topology information, and the device for generating the instance service topology determines the network corresponding to the NSD ID and the slice order (or the number of the slice order) of the slice. The network topology of the service instance is the network topology of the slice. On the one hand, the situation is more frequently used to deploy the network topology processing entity and the instance service topology generating device separately, and the reliability is high. On the other hand, since the NSD can be loaded from the outside and does not need to be written in the slice template, the resources of the slice template can be saved.

Alternatively, after generating an NFV NS instance, the network topology processing entity allocates an NS instance ID to the generated NS instance, and sends a network deployment response to the instance service topology generating device, where the network deployment response carries the NS instance ID. After receiving the network deployment response from the network topology processing entity, the device for generating the instance service topology may store the correspondence between the NSD ID (or the slice template or the slice template ID) and the NS instance ID. In the subsequent instance service topology generation phase, the device for generating the instance service topology obtains the network topology according to the network topology information, and the device for generating the instance service topology determines the network service instance ID corresponding to the slice according to the NSD ID, and processes the network topology The entity sends a network topology request message, where the network topology request message carries the network service instance ID; and further, the instance service topology generating device receives the network topology of the slice from the network topology processing entity. Alternatively, in the case that one slice template corresponds to multiple slice orders, the instance service topology generating device further needs to save the correspondence between the slice order (or the slice order number) and the NS instance ID, and the NSD ID is established relative to the NSD ID. (or slice template or slice template ID), the correspondence between the slice order and the NS instance ID. In the subsequent instance service topology generation phase, the device for generating the instance service topology obtains the network topology according to the network topology information, and the device for generating the instance service topology determines the network service instance ID corresponding to the slice according to the slice order of the slice and the NSD ID. And sending a network topology request message to the network topology processing entity, where the network topology request message carries the network service instance ID; and further, the instance service topology generating device receives the network topology of the slice from the network topology processing entity. On the one hand, the situation is more frequently used to deploy the network topology processing entity and the instance service topology generating device separately, and the reliability is high. On the other hand, since the NSD can be loaded from the outside and does not need to be written in the slice template, the resources of the slice template can be saved.

In a possible design, the logical service topology information is used to describe the logical service topology; the device for generating the service topology acquires the logical service topology according to the logical service topology information, including: the device for generating the instance service topology The logical service topology is determined according to the logical service topology information. The device for generating the instance service topology may generate a logical service topology of the slice according to the logical service topology information in the slice template, and the slice template is preset by the vendor personnel or the slice operation and maintenance personnel, so that the device may be upgraded based on the solution. The versatility and portability of slicing business deployments.

In a possible design, the logical topology information includes an identifier of the logical service topology, and the generating device of the instance service topology acquires the logical service topology according to the logical service topology information, including: generating device topology of the instance service topology The logical service topology processing entity sends a logical service topology request message, where the logical service topology request message carries an identifier of the logical service topology, where the identifier of the logical service topology is used to obtain the logical service topology; and the instance service topology generating device receives the The logical business topology processes the logical business topology of the entity. On the one hand, the device for generating the instance service topology may generate a logical service topology of the slice according to the logical service topology information in the slice template, and the slice template is preset by the vendor personnel or the slice operation and maintenance personnel, so based on the solution Can improve the versatility and portability of the slice business deployment. On the other hand, since it is not necessary to write specific information for describing the logical service topology in the slice template, the resources of the slice template can be saved.

In a possible design, the generating device of the instance service topology generates an instance service topology of the slice according to the network topology, the logical service topology and the generating policy, including: generating device of the instance service topology according to the network topology The logical service topology and the generation policy determine whether there is a service connection relationship between any two network function instances in the network topology; the device service topology generation device generates an instance service topology of the slice according to the determination result. Since the instance service topology of the slice is used to represent the network layout formed by the N network function instances and the service connection relationship between the N network function instances, when generating the instance service topology of the slice, by determining any two of the network topologies If there is a service connection relationship between the network function instances, and then the method of generating the instance service topology is generated according to the determination result, the accuracy of the generated instance service topology can be improved, and the accuracy of the service deployment can be improved.

In a possible design, the generating device of the example service topology determines, according to the network topology, the logical service topology and the generating policy, whether there is a service connection relationship between any two network function instances in the network topology, including: When the following three conditions are met, the generating device of the instance service topology determines that there is a service connection relationship between the first network function instance and the second network function instance; if any one of the following three conditions is not met, determining the There is no service connection relationship between the first network function instance and the second network function instance; wherein the first network function instance and the second network function instance are any two network function instances in the network topology; condition 1 The generating device of the instance service topology determines that there is a physical connection relationship between the first network function instance and the second network function instance according to the network topology; condition 2: the instance service topology generating device according to the logical service topology, Determining a first network function corresponding to the first network function instance and the second network function Examples of the relationship between the presence of a service connection corresponding to a second network function; Condition 3: The service instance based on the topology generating means generates policy, determines to allow the first establishes a service connection between a network and a function example of the second example of network functionality. Since the above condition 1 is considered from the viewpoint of network conditions, the above condition 2 is considered from the viewpoint of business demand, and the above condition 3 is considered from the viewpoint of customer demand. That is to say, the method for determining whether there is a service connection relationship between any two network function instances in the network topology provided by the embodiment of the present application considers network conditions, service requirements, and customer requirements, and thus determines any two of the network topologies. The method of whether the service connection relationship exists between the network function instances is more comprehensive and complete, so that the accuracy of the generated instance service topology can be further improved, and the accuracy of the service deployment can be further improved.

Optionally, after the generating device of the example service topology generates the instance service topology of the slice according to the network topology, the logical service topology, and the generating policy, the generating device of the instance service topology acquires the N networks. The standard interface information of the function instance; the device for generating the service topology generates the service configuration information of the slice according to the service topology of the instance and the standard interface information. Because the solution does not need to manually write a corresponding service configuration script for the instance service topology of the slice, the service configuration information of the slice can be automatically generated according to the instance service topology and the standard interface information, that is, the automatic service deployment can be implemented, so Improve the flexibility and simplicity of the slicing business deployment.

Optionally, the generating device of the instance service topology generates service configuration information of the slice according to the service topology of the instance and the standard interface information, including: a service connection relationship of any non-serving architecture interface in the service topology of the instance, The device for generating the service topology of the instance is processed according to the service connection relationship of the non-serving architecture interface between the third network function instance and the fourth network function instance: according to the third network function instance in the standard interface information The interface information is used to generate the first service configuration information for the third network function instance; and the second service configuration information is generated for the fourth network function instance according to the interface information of the fourth network function instance in the standard interface information; or For the service connection relationship of any service architecture interface in the service topology of the instance, the device for generating the service topology is in accordance with the service connection relationship between the service architecture interface between the fifth network function instance and the sixth network function instance. Way of handling: according to the standard interface information, the fifth The interface information of the network function instance generates third service configuration information for the service discovery node; and generates fourth service configuration information for the service discovery node according to the interface information of the sixth network function instance in the standard interface information, where The third service configuration information is used by the fifth network function instance to discover the sixth network function instance by using the service discovery node, where the fourth service configuration information is used by the sixth network function instance to discover the fifth through the service discovery node. Network function instance. The non-serving architecture interface between the third network function instance and the fourth network function instance is configured as the service connection relationship between the network function instance and the fourth network function instance. When the service connection relationship is processed, the corresponding service configuration information may be generated for the third network function instance and the fourth network function instance, respectively, so that the corresponding service configuration may be completed; the service connection relationship of the serviced architecture interface refers to the service discovery. The service connection of the service call can be dynamically established, so when the service connection relationship of the service architecture interface between the fifth network function instance and the sixth network function instance is processed, the corresponding service configuration information is generated for the service discovery node. The service configuration information is used for mutual discovery between the fifth network function instance and the sixth network function instance, so that the corresponding service configuration can be completed.

In a second aspect, an apparatus for generating an instance service topology is provided, the apparatus for generating a service topology having the function of implementing the method described in the above first aspect. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

A third aspect provides an apparatus for generating an instance service topology, including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the generating device of the instance service topology is running, the processor executes the memory storage The computer executes instructions to cause the instance service topology generation device to perform the instance service topology generation method of any of the above first aspects.

A fourth aspect, a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the example service of any of the above first aspects Topology generation method.

In a fifth aspect, a computer program product comprising instructions, when run on a computer, causes the computer to perform the method of generating an instance service topology as described in any of the above first aspects.

In a sixth aspect, a chip system is provided, the chip system including a processor, and a generating device for supporting an instance service topology implements functions involved in the foregoing aspects, such as acquiring a network topology of a slice, a logical service topology of a slice, and The generation strategy of the sliced instance business topology. In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the generating device of the instance service topology. The chip system can be composed of chips, and can also include chips and other discrete devices.

For the technical effects brought by any one of the second aspect to the sixth aspect, refer to the technical effects brought by different design modes in the first aspect, and details are not described herein again.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

DRAWINGS

1 is a schematic diagram of a network topology, a logical service topology, an instance service topology, and standard interface information of a slice according to an embodiment of the present disclosure;

2 is a schematic diagram of a prior art slice instantiation system;

FIG. 3 is a schematic structural diagram of an example service topology generation system according to an embodiment of the present disclosure;

4 is a schematic diagram of a change of a network topology of a slice according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a network topology and a change of a logical service topology of a slice according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of hardware of an example service topology generating apparatus according to an embodiment of the present disclosure;

FIG. 7 is a schematic flowchart of a method for generating an example service topology according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of generating an example service topology according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of an apparatus for generating an example service topology according to an embodiment of the present disclosure.

Detailed ways

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, a brief introduction of the related art of the present application is first given as follows.

Network slice:

A network slice is a network that is used to support logical isolation of specific network capabilities and network characteristics. It can be end-to-end (E2E) including the entire network, or part of the network function in multiple network slices. Sharing is a key technology to meet the 5th generation (5G) mobile communication technology proposed by 3GPP for network differentiation requirements. Generally, network characteristics of different network slices are not the same, and network slices are required to be isolated from each other without affecting each other. For example, network slicing of augmented reality (AR) or virtual reality (VR) services requires large bandwidth and low latency; network segmentation of Internet of Things (IOT) services requires massive terminal access. However, the bandwidth is small and there is no requirement for delay.

In addition, a network slice may be composed of one or more sub-network slices. The slice involved in the embodiment of the present application may be a network slice or a sub-network slice, which is uniformly described herein, and details are not described herein again.

Slice instantiation:

In the 3GPP standard, the process of creating a slice instance for a client on a infrastructure (such as a physical machine or a virtual machine, etc.) according to a customer order, according to a customer order, is called slice instantiation. The process of creating a network slice instance for the client on the infrastructure according to the network slice template according to the customer order, the network slice management function (NSMF) entity is called network slice instantiation; the sub-network slice management function ( Network slice subnet management function (NSSMF) The process of creating a sub-network slice instance for a customer on the infrastructure according to the sub-network slice template according to the customer order is called sub-network slice instantiation. In the embodiment of the present application, the instantiation of the slice includes the network slice instantiation and the sub-network slice instantiation, which are collectively described herein, and are not further described below.

Network function and network function example:

A network function is equivalent to providing a network service. For example, in a 5G network, the network function may include a session management function (SMF), a policy control function (PCF), a user plane function (UPF), and an evolved base station (evolved node B, eNB) or 5G base station (new radio (NR) nodeB, gNB), access and mobility management function (AMF) and network storage function (NRF), and so on. The SMF is used to provide session management services, the PCF is used to provide policy control services, the UPF is used to provide user plane services, and the AMF is used to provide access and mobility management services, eNB or gNB (hereinafter, eNB is taken as an example) Used to provide wireless access services, NRF is used to provide service discovery.

Based on considerations such as load balancing and service coverage area, in one slice, one network function may deploy multiple network function instances, that is, multiple network function instances provide the same network function service. The virtualized network function (VNF) descriptor (VNFD) of the network function is generated once, and a corresponding network instance is generated. For example, assume that the network functions required by the user include eNB, AMF, SMF, UPF, and NRF. If the nearest service based on a consideration of the regions A and D require a UPF instance (also referred to herein may UPF entity), it is possible according to the UPF VNF descriptor (VNFD_ _UPF), in the region of the infrastructure A Perform a deployment operation on the first to generate the UPF entity 1; perform a deployment operation on the infrastructure in the area D to generate the UPF entity 2, that is, perform two deployment operations according to the UPF VNF descriptor, and then Two UPF entities, namely UPF entity 1 and UPF entity 2, are generated, as shown in Figure 1a. Similarly, if an AMF instance (also referred to herein as an AMF entity) is required in both region C and region D based on factors such as load balancing and service coverage, then the VNF descriptor (VNFD_ _AMF ) of the AMF can be used. Performing a deployment operation on the infrastructure in the area C to generate the AMF entity 1; performing a deployment operation on the infrastructure in the area D to generate the AMF entity 2, that is, according to the AMF's VNF descriptor, After performing two deployment operations, two AMF entities, AMF entity 1 and AMF entity 2, can be generated, as shown in Figure 1a. Alternatively, if based on load balancing considerations, an SMF instance (also referred to herein as an SMF entity) is required in both Region C and Region D, the basis of Region V can be based on the VNF Descriptor (VNFD_SMF) of the _SMF . Performing a deployment operation on the facility to generate the SMF entity 1; performing a deployment operation on the infrastructure in the area D to generate the SMF entity 2, that is, performing two deployment operations according to the VMF descriptor of the SMF, Two SMF entities, namely SMF entity 1 and SMF entity 2, may be generated, as shown in Figure 1a; in addition, according to the VNF descriptor of the _NRF (VNFD_NRF), in area A, area B, area C and area D A deployment operation is performed on the infrastructure to generate an NRF entity, as shown in Figure 1a. The network function instance may also be an instance of a physical network function (PNF) described in a network service descriptor (NSD). For example, based on factors such as the service coverage area, an eNB entity is required in both the area A and the area B. One eNB1 may be deployed in the area A according to the NSD, and one eNB2 may be deployed in the area B, as shown in FIG. 1a.

It should be noted that the NSD in the embodiment of the present application includes the network topology description information of the slice, for example, how to deploy the VNF, and how to establish a physical connection between the VNF and the PNF if there is a pre-deployed PNF. Of course, the NSD may include other information. For details, refer to related descriptions of the related art, and details are not described herein again.

It should be noted that, in the embodiment of the present application, a network function instance may be deployed according to multiple network functions. For example, in FIG. 2, the VNF of the SMF is deployed once on a virtual machine in the area D. descriptor (VNFD_ _SMF) and the AMF VNF descriptor (VNFD_ _AMF), thereby generating a core network control function (core network-control function, CN -CF) example (here also referred entity CN-CF), this application The embodiment does not specifically limit this.

Physical connection:

A physical connection is used to characterize the physical connectivity between two network function instances.

Exemplarily, as shown in FIG. 1a, the eNB1 in the area A is connected to the UPF entity 1 in the area A through the network, so there is a physical connection between the eNB1 in the area A and the UPF entity 1 in the area A; or eNB1 in area A is connected to eNB2 in area B through the network, so there is a physical connection between eNB1 in area A and eNB2 in area B; or eNB1 in area A passes through SMF entity 1 in network and area C Connected with the AMF entity 1, so there is a physical connection between the eNB1 in the area A and the SMF entity 1 and the AMF entity 1 in the area C; or, the eNB1 in the area A passes through the network and the SMF entity 2 in the area D, AMF The entity 2 is connected to the UPF entity 2, so there is a physical connection between the eNB1 in the area A and the SMF entity 2, the AMF entity 2 and the UPF entity 2 in the area D, and so on, and details are not described herein.

Business connection:

A service connection is used to characterize whether two network function instances or two network functions can transmit service packets.

Exemplarily, as shown in FIG. 1b, there is a service connection relationship between the AMF and the SMF. Therefore, the service packet can be transmitted between the AMF and the SMF; or, there is a service connection relationship between the UPF and the SMF, and therefore, the service The message can be transmitted between the UPF and the SMF; or, there is a service connection between the AMF and the AMF. Therefore, the service message can be transmitted between the AMF and the AMF, and so on, and will not be repeated here.

Or, exemplarily, as shown in FIG. 1c, there is a service connection relationship between the UPF entity 1 in the area A and the eNB1 in the area A, and therefore, the service packet can be in the UPF entity 1 and the area A in the area A. There is a service connection between the eNB1 in the area A; or the eNB2 in the area A and the eNB2 in the area B. Therefore, the service packet can be in the UPF entity 1 in the area A and the eNB2 in the area B. Or, there is a service connection relationship between the UPF entity 1 in the area A and the SMF entity 1 in the area C. Therefore, the service packet can be in the UPF entity 1 in the area A and the SMF entity 1 in the area C. Or, there is a service connection relationship between the UPF entity 1 in the area A and the SMF entity 2 in the area D. Therefore, the service packet can be in the UPF entity 1 in the area A and the SMF entity 2 in the area D. Inter-transmission, etc., will not be repeated here.

The service connection relationship between the UPF and the SMF, or the UPF instance and the SMF instance (such as the UPF entity 1 in the area A and the SMF entity 1 in the area C) may be a service connection for transmitting bearer control signaling. Therefore, the transmitted service message may be a bearer control signaling message; between AMF and SMF, or between AMF instance and SMF instance (such as AMF entity 2 in area D and SMF entity 2 in area D) The connection relationship may be a service connection for transmitting session control signaling, so the transmitted service message may be a session control signaling message; between the AMF and the AMF, or between the AMF instance and the AMF instance (such as the AMF entity 1 in the area C) The service connection relationship with the AMF entity 2) in the area D may be a service connection for transmitting mobility management signaling, so the transmitted service message may be a mobility management signaling message; between the AMF and the eNB, or AMF The service connection relationship between the instance and the eNB instance (such as eNB1 in the area A and the AMF entity 1 in the area C) may be a service connection for transmitting the registration request of the user and the service request signaling, so the transmitted service message may be User registration And summing the service request signaling message; the service connection relationship between the eNB and the UPF, or between the eNB instance and the UPF instance (UPF entity 1 in area A and eNB1 in area A) may be used for session bearer Service connection, so the transmitted service message can be a user data message; a service connection between the AMF and the NRF, or between the AMF instance and the NRF instance (the AMF entity 2 in the area D and the NRF entity in the area) The relationship may be a service connection for service discovery, so the transmitted service message may be a service discovery request message; between the SMF and the NRF, or between the SMF instance and the NRF instance (the SMF entity 2 and the area in the area D) The service connection relationship between the NRF entities may be a service connection for service discovery. Therefore, the service packet transmitted may be a service discovery request packet, which is uniformly described herein, and is not described here.

Network topology:

The network topology in the embodiment of the present application is used to represent a network layout composed of N network function instances and physical connection relationships between the N network function instances.

Illustratively, as shown in FIG. 1a, a schematic diagram of a network topology of a slice provided by an embodiment of the present application. The network topology of the slice is composed of eNB1, eNB2, UPF entity 1, UPF entity 2, SMF entity 1, SMF entity 2, AMF entity 1, AMF entity 2, NRF entity, and physical connection relationship between the above network function instances. For a description of related examples of the physical connection relationship between the network function instances, refer to the description of the foregoing physical connection part, and details are not described herein again.

Logical business topology:

The logical service topology in the embodiment of the present application is used to represent a network layout composed of M network functions and service connection relationships between M network functions. In the logical service topology, each type of network function acts as a node, and the service connection relationship between different types of network functions is described as a connection between different nodes, and a description of the service connection relationship between network functions of the same type. Self-join for the node.

Illustratively, as shown in FIG. 1b, a schematic diagram of a logical business topology of a slice provided by an embodiment of the present application. The logical service topology of the slice is composed of an eNB, UPF, SMF, AMF, NRF, and a service connection relationship between the above network functions. For a description of related examples of the service connection relationship between the network functions, reference may be made to the description of the foregoing service connection part, and details are not described herein again.

It should be noted that the network topology and the logical service topology in the embodiment of the present application are related, and the specific performance is as follows: in the slice design stage, the slice designer (such as a slice service provider) determines according to the service to be provided by the slice. What types of network functions need to be included in the slice, and then according to the 3GPP standard, determine how these types of network functions should be connected in order to support the corresponding services, that is, design the logical business topology of the slice, and determine the various network functions between Business interface. The slice designer then designs or selects the existing NSD as the NSD required for the slice deployment based on the network capabilities in the logical business topology of the slice. When the slice is deployed, the corresponding network topology can be generated according to the NSD and the needs of the user (such as the number of users sliced, etc.).

Instance business topology:

The example service topology in the embodiment of the present application is used to represent a network layout formed by N network function instances and service connection relationships between N network function instances. In the instance service topology, each type of network function may have multiple network function instances according to network deployment conditions, and each network function instance acts as a node in the instance service topology. The business connection relationship between the same type and different types of network function instances is described as the connection between the nodes.

Illustratively, as shown in FIG. 1c, a schematic diagram of an example service topology of a slice provided by an embodiment of the present application. The example service topology of the slice is composed of an eNB1, an eNB2, a UPF entity 1, a UPF entity 2, an SMF entity 1, an SMF entity 2, an AMF entity 1 and an AMF entity 2, an NRF entity, and a service connection relationship between the network function instances. For a description of related examples of the service connection relationship between the network function instances, reference may be made to the description of the service connection part, and details are not described herein again.

Instance business topology generation strategy:

In the embodiment of the present application, the instance service topology generation policy is used to identify whether any two network function instances in the N network function instances are allowed to establish a service connection.

Optionally, the foregoing generation policy may be an external generation policy, or may be a default generation policy, and may also include an external generation policy and a default generation policy, which are not specifically limited in this embodiment of the present application. The external generation policy specifically refers to a generation strategy of an instance service topology provided by an external processing entity when the slice is instantiated; or a generation policy determined according to externally input policy description information when the slice is instantiated. The default generation policy specifically refers to the generation strategy of the instance business topology described in the slice template during the slice design. If the external instantiation policy and the default generation policy are used in the instantiation of the slice, the operator will be assigned the priority of the externally generated policy. This is not specifically limited.

Optionally, the generation policy in the embodiment of the present application may be described by using an E (event event)-C (condition condition)-A (action action) in the industry, that is, the event triggers a certain judgment logic, and the condition is met. In the case of a certain action.

Illustratively, a description using the E-C-A (event-condition-action) form can be:

E: CREATE_INSTANCE_SERVICE_TOPO; / / event is: the creation of the instance business topology

C1: ((NE1.type==eNB&&NE2.type==AMF)&&(NE1.position==NE2.position)); / / Condition C1 is: the type of network element 1 is eNB, and the type of network element 2 is AMF And the two are in the same position

A1: Add_Connection_in_Service_Topo(NE1, NE2); //Action A1 is: Allow service connection between NE 1 and NE 2.

C2: ((NE1.type==SMF&&NE2.type==UPF)&&(NE1.position==NE2.position)); / / Condition C2 is: the type of network element 1 is SMF, and the type of network element 2 is UPF And the two are in the same position

A2: Add_Connection_in_Service_Topo(NE1, NE2)); / / Action A2 is: Allow network connection between network element 1 and network element 2

C3: (NE1.type==AMF&&NE2.type==AMF); // Condition C3 is: the type of network element 1 is AMF, and the type of network element 2 is AMF.

A3: Add_Connection_in_Service_Topo(NE1, NE2)); / / Action A3 is: Allow network connection between network element 1 and network element 2

C4:default;//condition C4 is: default condition

A4: Do_nothing(); // Action A4 is: no service connection is allowed.

Service connection relationship between the service architecture interface and the service connection relationship of the non-service architecture interface:

In the embodiment of the present application, the service connection relationship of the service architecture interface refers to a service connection that can dynamically establish a service call through the service discovery. The service connection relationship of the non-serviced architecture interface is that the network function instance at both ends of the interface can be established through static configuration. Business connection.

In the embodiment of the present application, the service discovery specifically refers to that when the network function instance A provides some services, the service provided by the network function instance A is registered with the service discovery node, so that subsequent network function instances can dynamically be discovered through the service discovery node. Discover this network function instance A and be able to use the services provided by this network function instance A. For example, the second network function instance can provide the service corresponding to the second network function, so the service corresponding to the second network function can be registered with the service discovery node. When the first network function instance needs to use the service provided by the second network function, firstly, a service discovery request is made to the service discovery node, and then the service discovery node responds to the address of the second network function instance that can provide the required service, and then The first network function instance can initiate a service call to the second network function instance corresponding to the address.

Exemplarily, as shown in FIG. 1d, since AMF and SMF perform dynamic service discovery and service invocation through a network repository function (NRF), a service connection relationship between the AMF and the SMF is a service architecture interface. NRF is a service discovery node in a serviced architecture network. Among them, when AMF calls the service provided by SMF, it uses the standard interface Nsmf of SMF; when SMF calls the service provided by AMF, it uses the standard interface Namf of AMF. Between AMF and NRF is the standard interface Nnrf for NRF for service discovery; the same interface between NMF and NRF is also the standard interface Nnrf for NRF for service discovery.

Or, exemplarily, as shown in FIG. 1d, during the session bearer connection establishment process of the eNB and the UPF, the SMF that processes the session establishment request selects the UPF, notifies the selected UPF of the eNB's bearer address, and then the UPF. The bearer address tells the eNB that the UPF and the eNB can obtain the address information of the peer through the SMF and dynamically establish the service connection of the session bearer. In this process, the SMF acts as the service discovery node that carries the service, and the eNB and the UPF are also equivalent. The service connection relationship of the service architecture interface. In contrast, SMF and UPF establish a service connection through static configuration. The eNB and AMF establish a service connection through static configuration, so they are the service connection relationship of the non-serving interface. As shown in FIG. 1d, the standard interface used by the eNB to establish a service connection with the UPF is the N3 interface of the eNB, and the standard interface used by the eNB to establish a service connection with the AMF is the N2 interface of the eNB, and the AMF is used to establish a service connection with the eNB. The standard interface is the N2 interface of the AMF. The standard interface used by the UPF to establish a service connection with the SMF is the N4 interface of the UPF. The standard interface used by the SMF to establish a service connection with the UPF is the N4 interface of the SMF. No longer.

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the present application, unless otherwise stated, "/" means the meaning of or, for example, A/B may represent A or B; "and/or" herein is merely an association describing the associated object. The relationship indicates that there may be three kinds of relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately. Also, in the description of the present application, "a plurality" means two or more than two unless otherwise stated. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", and the like are used to distinguish the same items or similar items whose functions and functions are substantially the same. Those skilled in the art can understand that the words "first", "second" and the like do not limit the number and execution order, and the words "first", "second" and the like are not necessarily limited.

The network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application. The technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

First, an application scenario of the embodiment of the present application is given:

It is assumed that the operator designs a slice template for each type of service in order to support a certain type of service of the customer, such as a car network service, a VR service or an emergency communication service, and the slice template contains a series of description information, and the description information can be Used to create a specific slice instance. After the design of the slice template is completed, the operator can publish the slice type defined by the slice template as a slice product on the network and order it for the user. Optionally, the user can also provide some customized functions, for example, the user can select The business capacity that suits your business needs (such as the number of users using the service, etc.), you can also choose the location or scope of the service, and so on. When a user orders a sliced product, a slice order is generated. The slice order describes what kind of slice is ordered, what are the optional business functions, what is the scope of the service offering, and how much size the business supports. The operator then creates a slice instance for the user based on the slice order, which is to create a logical isolation for the customer using techniques such as network function virtualization (NFV) and software defined network (SDN). Network, and open the corresponding business for users.

Specifically, the network slice is taken as an example. As shown in FIG. 2, in the prior art, before the network slice is instantiated, the operator needs to load the network slice template in advance on the network slice management function (NSMF) entity. . The network slice template includes an NSD or NSD identity (ID) required for the NFV deployment, and a service configuration script of the network function entity. The service configuration script includes a service configuration command of the network function entity. The related description of the NSD can be referred to the preamble of the specific implementation manner, and details are not described herein again.

During the network deployment phase in which the network slice is instantiated, the operator's NSMF entity performs network deployment according to the network slice order. In the NFV scenario, network deployment is mainly through NFV deployment on infrastructure resources through management and orchestration (MANO) entities, creating VNFs and creating physical connections between different VNFs (or PNFs). Specifically, the NSMF entity sends the NSD or NSD ID to the MANO entity, and the MANO entity allocates resources according to the NSD on the NFV Infrastructure (NFVI) and deploys the VNF entity in the network slice, and creates different VNFs (or PNFs). The physical connection between the two; or, after the MANO entity loads the NSD from the outside according to the NSD ID, allocates resources on the NFVI according to the NSD and deploys the VNF entity in the network slice, and creates a physical connection between different VNFs (or PNFs).

During the service deployment phase of the network segment instantiation, the NSMF entity sends the service configuration script to the element management system (EMS) entity, and the EMS entity performs related services on the VNF and PNF included in the network slice according to the service configuration script. Configuration commands, such as the protocol (IP) address, the service routing, the configuration of the signaling interface parameters, the configuration of the service function switch, etc., which are configured on the VNF and/or PNF. The services required in the normal operation can be run on the network slice. The device for generating the instance service topology, such as the VNF and/or the PNF, is configured to enable the network function to forward the service that the client needs to carry on the network slice. This step is often referred to as network-level service configuration. No longer.

However, as described in the background art, the existing service configuration script is written according to an example service topology of a pre-designed slice. Each time a slice is deployed, the operator needs to ask the device manufacturer to design a sliced instance service topology and write a corresponding The service configuration script can be used to complete the service deployment of the service based on the service configuration script. In this way, the service topology of the instance is designed to be very complicated and inflexible. Therefore, how to obtain the instance service topology to improve the flexibility of service deployment. Sex and simplicity are the problems that need to be solved.

To solve the problem, the embodiment of the present application provides a method for generating an instance service topology, so that the flexibility and simplicity of the slice service deployment can be improved. The main idea is that the instance service topology generating device acquires the network topology of the slice, the logical business topology of the slice, and the generation strategy of the sliced instance service topology; wherein the network topology is used to represent the N network function instances and the N network functions. The network layout formed by the physical connection relationship between the instances, the logical service topology is used to represent the network layout composed of the M network functions and the service connection relationship between the M network functions, and the generation strategy is used to represent the N network function instances. Whether a service connection is allowed to be established between any two network function instances, and M and N are positive integers; the instance service topology generating device generates a sliced instance service topology according to the network topology, the logical service topology, and the generation policy, where the instance service is generated. The topology is used to characterize the network layout of the N network function instances and the service connection relationships between the N network function instances.

The network topology of the slice may be a network topology designed during the slice design phase, or may be a network topology obtained by the device for generating the instance service topology after the network instance of the slice instance is completed, and the instance service may be executed during the running process of the slice instance. The network topology of the network that is dynamically acquired by the topology generating device for the network topology change scenario is not specifically limited in this embodiment of the present application. Similarly, the logical service topology of the above-mentioned slice may be a logical service topology designed in the slice design phase, or may be redesigned for the scenario of the logical service topology change dynamically acquired by the instance service topology generation device during the execution of the slice instance. The logical service topology is not specifically limited in this embodiment of the present application.

Exemplarily, assume that the network topology of the current slice is as shown in Figure 3a. Among them, the network function instances such as eNB1, AMF entity 1, SMF entity 1, UPF entity 2, and UPF entity 1 are deployed in city A; network functions such as eNB2, AMF entity 2, SMF entity 2, and UPF entity 3 are deployed in city B. For example, the NRF entity is a service discovery node, and is located in the overlapping area of the city A and the city B. The physical connection relationship between the network function instances is shown in FIG. 3a, and is not described here.

Assume that during the operation phase of the slice instance, the traffic of the slice is drastically increased due to the grand performance of City B, and the result is shown in Figure 3b. The dotted line in FIG. 3b indicates a new network function instance or physical connection relationship. At this time, the device for generating the instance service topology needs to obtain the network topology shown in FIG. 3b, and automatically generate the instance service topology of the slice according to the foregoing solution, and the service deployment of the slice can be re-completed according to the service topology of the instance.

Or, for example, assume that the logical service topology of the current slice is as shown in FIG. 4b, including five network functions of eNB, AMF, SMF, UPF, and NRF, and a service connection relationship between network functions. The network topology of the current slice is shown in Figure 4a. Among them, the network function instances such as eNB1, AMF entity 1, SMF entity 1, UPF entity 2, and UPF entity 1 are deployed in city A; network functions such as eNB2, AMF entity 2, SMF entity 2, and UPF entity 3 are deployed in city B. For example, the NRF entity 1 is a service discovery node, and is located in an overlapping area of the city A and the city B. The physical connection relationship between the network function instances is shown in FIG. 4a, and is not described here.

It is assumed that after the slicing operation, the customer requests to increase the service function of performing dynamic quality of service (QoS) control. At this time, the operator finds that it needs to increase the PCF network function to meet the new requirements of the customer, and thus re-modifies the logical business topology of the slice. The logical service topology of the modified slice is shown in Figure 4d. Of course, as described in the preamble of the specific implementation, the network topology and the logical service topology have certain correlations at the time of design. Therefore, in the case where the logical business topology of the slice is changed, the design of the NSD may need to be changed, and then the MANO entity The network topology of the slice is changed according to the changed NSD. Therefore, the network topology of the slice is changed. For example, as shown in FIG. 4c, the PCF entity 1 can be deployed in the city B, and the PCF entity 1 and the SMF entity 2 are deployed. Physical connection, which in turn can result in a network topology as shown in Figure 4c. The dotted line in FIG. 4c indicates a new network function instance or physical connection relationship. At this time, the device for generating the instance service topology needs to acquire the network topology of the slice shown in FIG. 4c and the logical service topology of the slice shown in FIG. 4d, and automatically generate an instance service topology of the slice according to the foregoing solution, according to the service topology of the instance. Re-complete the business deployment of the slice.

In addition, the generation policy of the instance service topology of the foregoing slice may be a default generation policy, or may be an external generation policy, or may be determined by a default generation policy and an external generation policy, which are not specifically limited in this embodiment of the present application. The external generation policy may be obtained in real time, which is not specifically limited in this embodiment of the present application.

That is to say, in the embodiment of the present application, the instance service topology of the slice is automatically generated by the device for generating the instance service topology, and the service deployment of the slice can be further completed according to the service topology of the instance. You can re-generate the changed network topology or logical service topology or generate a policy and regenerate the instance service topology in the case of a network topology or a logical service topology or a policy change. As required by the prior art, each time the network topology or the logical service topology or the generation policy is changed, the vendor needs to redesign the sliced instance service topology, and write a corresponding service configuration script according to the sliced instance service topology, according to The service configuration script can complete the service deployment of the slice, so that the embodiment of the present application can improve the flexibility and simplicity of the slice service deployment.

Optionally, the method for generating the foregoing service topology may be independently performed by the generating device of the instance service topology. If the slice is a network slice, the device for generating the instance service topology may be, for example, an NSMF entity; if the slice is a sub-network slice, the device for generating the instance service topology may be, for example, a network slice subnet management function. Function, NSSMF) entity, hereby unified description, the details are not described below.

Alternatively, as shown in FIG. 5, an example service topology generation system 50 is provided in the embodiment of the present application. The instance service topology generation system 50 includes an instance service topology generation device 501, and network topology processing. At least one of an entity 502, a logical service topology processing entity 503, and an external policy entity 504. For example, the instance service topology generation system 50 includes an instance service topology generation device 501 and a network topology processing entity 502; or the instance service topology generation system 50 includes an instance service topology generation device 501, a network topology processing entity 502, and a logical service. The topology processing entity 503; or the instance service topology generation system 50 includes an instance service topology generation device 501, a network topology processing entity 502, a logical service topology processing entity 503, and an external policy entity 504; No specific limitation.

The network topology processing entity 502 is configured to send a network topology to the instance service topology generating device 501 after receiving the network topology request message from the generating device 501 of the instance service topology; the logical service topology processing entity 503 is configured to receive After the logical service topology request message from the generating device 501 of the instance service topology, the logical service topology is sent to the generating device 501 of the instance service topology; the external policy entity 504 is configured to receive the policy request message from the generating device 501 of the instance service topology. Then, the external service generation policy is sent to the instance service topology generating device 501. The instance service topology generating device 501 is configured to generate a sliced instance service topology according to the network topology, the logical service topology, and the generation policy. The specific solution will be described in detail in the following method embodiments, and details are not described herein again.

Optionally, in the embodiment of the present application, the network topology processing entity 502 may be, for example, a MANO entity, and the logical service topology processing entity 503 may be, for example, a slice controller, and the external policy entity 504 may be, for example, an operator's operation and maintenance support system. The support system, the OSS, and the like are not specifically limited in the embodiment of the present application.

Optionally, each network element in FIG. 5 may be deployed independently or in any combination of network elements. For example, the logical service topology processing entity 503 and the external policy entity 504 are deployed in a unified manner, and the instance service topology generating apparatus 501 is configured. The network topology processing entity 502 is deployed in a unified manner, or all the network elements are deployed in a unified manner, and the like, which is not specifically limited in this embodiment.

FIG. 6 is a schematic diagram showing the hardware structure of an apparatus for generating an instance service topology according to an embodiment of the present application. The instance service topology generating device 600 includes at least one processor 601, a communication line 602, a memory 603, and at least one communication interface 604.

The processor 601 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.

Communication line 602 can include a path for communicating information between the components described above.

Communication interface 604, using any type of transceiver, for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .

The memory 603 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this. The memory may be stand-alone and connected to the processor via communication line 602. The memory can also be integrated with the processor.

The memory 603 is used to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 601 for execution. The processor 601 is configured to execute the computer execution instructions stored in the memory 603, so as to implement the method for generating the example service topology provided by the following embodiments of the present application.

Optionally, the computer-executed instructions in the embodiment of the present application may also be referred to as an application code, which is not specifically limited in this embodiment of the present application.

In a specific implementation, as an embodiment, the processor 601 may include one or more CPUs, such as CPU0 and CPU1 in FIG.

In a specific implementation, as an embodiment, the instance service topology generating apparatus 600 may include multiple processors, such as the processor 601 and the processor 608 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.

In a specific implementation, as an embodiment, the instance service topology generating apparatus 600 may further include an output device 605 and an input device 606. Output device 605 is in communication with processor 601 and can display information in a variety of ways. For example, the output device 605 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait. Input device 606 is in communication with processor 601 and can receive user input in a variety of ways. For example, input device 606 can be a mouse, keyboard, touch screen device, or sensing device, and the like.

The above-described instance service topology generating device 600 can be a general purpose device or a dedicated device. In a specific implementation, the instance service topology generating device 600 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or have FIG. 6 A device of similar structure. The embodiment of the present application does not limit the type of the generating device 600 of the example service topology.

The method for generating an example service topology provided by the embodiment of the present application is described below.

The method for generating an instance service topology is applied to the system for generating an instance service topology shown in FIG. 5 as an example. As shown in FIG. 7 , the method for generating an instance service topology provided by the embodiment of the present application includes the following steps:

S701. The device for generating an instance service topology obtains network topology information of the slice and logical service topology information of the slice from the slice template.

Optionally, the slice template in the embodiment of the present application may be pre-loaded into the generating device of the instance service topology after the operator designs the slice template, or may be pre-loaded into other devices after the operator designs the slice template. The method for generating the instance service topology is obtained by using the device for generating the instance service topology provided by the embodiment of the present application.

The slice template in the embodiment of the present application may include network topology information of the slice and logical service topology information of the slice.

Optionally, the slice template in the embodiment of the present application may further include a default generation policy of the instance service topology of the slice, and the default generation policy may be, for example, allowing a service connection between any two network function instances to be established.

Optionally, the slice template in the embodiment of the present application may further include standard interface information of the network function, which is not specifically limited in this embodiment of the present application. For a description of the standard interface information of the network function, reference may be made to the preamble of the specific implementation manner, and details are not described herein again.

Optionally, the network topology information in the embodiment of the present application may be description information that can generate a network topology. The device for generating the service topology may obtain the network topology of the slice according to the description information that can generate the network topology.

For example, in the slice design phase, the slice designer determines which types of network functions the slice needs to include based on the services to be provided by the slice, and then determines according to the 3GPP standard how these types of network functions should be connected in order to support the corresponding services. That is, the logical business topology of the slice is designed, and the service interface between various network functions is determined. The slice designer then designs or selects the existing NSD as the NSD required for the slice deployment according to the network function in the logical service topology, and writes the NSD into the slice template as the description information capable of generating the network topology. The following two scenarios are met when the method for generating the service topology of the instance is executed:

Scenario 1: The device for generating an instance service topology may generate a network topology of the slice according to the NSD in the slice template. This scenario is more commonly used in the scenario where the network topology processing entity and the instance service topology generating device are deployed together, which can save device resources, and is uniformly described herein, and details are not described herein.

Scenario 2: The device for generating an instance service topology may send a network deployment request to the network topology processing entity, where the network deployment request carries the NSD, and the network topology processing entity performs NFV network deployment according to the NSD, thereby generating an NFV network service (network After the NS instance is assigned an NS instance ID, the network deployment response is sent to the instance service topology generating device, and the network deployment response may carry the NS instance ID, or the network deployment response may also be The network topology of the NS instance may be carried, which is not specifically limited in this embodiment of the present application. When the network deployment response carries the network topology of the NS instance, the device for generating the instance service topology further needs to save the correspondence between the NSD (or the slice template or the slice template ID) in the slice template and the network topology of the NS instance. . When the instance service topology is generated, the network topology of the slice can be directly obtained according to the NSD (or the slice template or the slice template ID) in the slice template. Optionally, if a slice template corresponds to multiple slice orders, that is, multiple NS instances may be deployed according to one NSD, after the instance service topology generating device receives the network deployment response from the network topology processing entity, The generating device of the instance service topology further needs to save the correspondence between the network topology of the NS instance and the slice order (or the number of the slice order), and the NSD (or slice template or slice template ID) is established relative to the slice order ( Or the corresponding number of the slice order) and the network topology of the NS instance. When the instance service topology is generated, the network topology of the slice can be directly obtained according to the NSD (or slice template or slice template ID) and the slice order (or the number of the slice order) in the slice template. No longer. This scenario is more commonly used in the scenario where the network topology processing entity is deployed separately from the instance service topology generation device. The reliability is high.

Alternatively, optionally, the network topology information in the embodiment of the present application may be an identifier that can generate a network topology; and the generating device of the instance service topology may obtain the network topology of the slice according to the identifier that can generate the network topology.

For example, in the slice design phase, the slice designer determines which types of network functions the slice needs to include based on the services to be provided by the slice, and then determines according to the 3GPP standard how these types of network functions should be connected in order to support the corresponding services. That is, the logical business topology of the slice is designed, and the service interface between various network functions is determined. The slice designer then designs or selects the existing NSD as the NSD required for the slice deployment based on the network functions in the logical service topology, and writes the NSD ID into the slice template as the identifier that can generate the network topology. The following two scenarios are met when the method for generating the service topology of the instance is executed:

Scenario 3: The device for generating an instance service topology may load a corresponding NSD according to the NSD ID in the slice template, and generate a network topology of the slice according to the NSD. This scenario is more commonly used in the scenario where the network topology processing entity and the instance service topology generating device are deployed together, which can save device resources, and is uniformly described herein, and details are not described herein.

For the fourth scenario, refer to the following steps S702-S705, and details are not described herein again. This scenario is more commonly used in the scenario where the network topology processing entity is deployed separately from the instance service topology generation device. The reliability is high.

Optionally, the logical service topology information in the embodiment of the present application may be the description information of the logical service topology; and the generating device of the instance service topology may directly determine the logical service topology of the slice according to the description information of the logical service topology. This scenario may be considered as a scenario in which the generating device of the instance service topology is integrated with the logical service topology processing entity, which is not specifically limited in this embodiment of the present application.

Alternatively, the logical service topology information in the embodiment of the present application may be an identifier of the logical service topology; and the device for generating the service topology may obtain the information from the logical service topology processing entity according to the identifier of the logical service topology. The logical business topology of the slice. This scenario can be considered as a scenario in which the instance service generation device and the logical service topology processing entity are deployed independently. The specific scenarios are as follows:

The logical service topology processing entity can be loaded with various logical service topologies in advance, and the logical service topology processing entity saves the correspondence between the various logical service topologies and the corresponding logical service topology identifiers. In the slice design phase, the slice template can carry the identifier of the corresponding logical service topology.

In this way, when the logical service topology of the slice is obtained, the generating device of the instance service topology sends a logical service topology request message to the logical service topology processing entity, where the logical service topology request message carries the identifier of the logical service topology carried in the slice template. The logical service topology processing entity may determine the logical service topology corresponding to the identifier of the logical service topology according to the identifier of the logical service topology, and the corresponding relationship between the saved logical service topology and the corresponding logical service topology identifier, and then may The generating device of the instance service topology sends the logical service topology, so that the generating device of the instance service topology can acquire the logical service topology of the slice.

The network topology information is the NSD ID, the logical service topology information is the identifier of the logical service topology, and the instance service topology generation policy is the external generation policy obtained from the external policy entity.

S702. The generating device of the instance service topology sends a network deployment request to the network topology processing entity, where the network deployment request carries the NSD ID, so that the network topology processing entity receives the network deployment request from the generating device of the instance service topology.

S703: The network topology processing entity loads the corresponding NSD according to the NSD ID, and then performs NFV network deployment, thereby generating an NFV NS instance.

Specifically, the network topology of the NFV NS instance is the network topology of the slice. The NSD may be pre-stored on the network topology processing entity, or may be loaded from a device other than the network topology processing entity, which is not specifically limited in this embodiment.

Optionally, in the embodiment of the present application, the network topology processing entity may allocate an NS instance ID to the generated NS instance. The network topology processing entity performs the network deployment according to the NSD. The specific process of generating an NS instance may refer to the prior art, and details are not described herein.

S704. The network topology processing entity sends a network deployment response to the generating device of the instance service topology, so that the generating device of the instance service topology receives the network deployment response from the network topology processing entity.

The network deployment response carries the NS instance ID, or the network deployment response may also carry the network topology of the NS instance, which is not specifically limited in this embodiment of the present application.

It should be noted that the above steps S702-704 are used for the network deployment phase of the slice instantiation.

When the network deployment response carries the network topology of the NS instance, the device for generating the instance service topology further needs to save the NSD ID (or the slice template or the slice template ID) in the slice template and the network topology of the NS instance. Correspondence. Optionally, if a slice template corresponds to multiple slice orders, that is, multiple NS instances may be deployed according to an NSD ID, after the instance service topology generating device receives the network deployment response from the network topology processing entity, The device for generating the instance service topology further needs to save the correspondence between the network topology of the NS instance and the slice order (or the number of the slice order), and the NSD ID (or slice template or slice template ID) is set relative to the slice. The corresponding relationship between the order (or the number of the sliced order) and the network topology of the NS instance is described here, and is not described here.

Alternatively, when the network deployment response carries the NS instance ID, the instance service topology generating device further needs to save the corresponding relationship between the NSD ID (or the slice template or the slice template ID) in the slice template and the NS instance ID. Alternatively, in the case that the one slice template corresponds to multiple slice orders, the instance service topology generating device further needs to save the correspondence between the slice order (or the slice order number) and the NS instance ID, and the NSD is established relative to the NSD. The corresponding relationship between the ID (or the slice template or the slice template ID), the slice order, and the NS instance ID is uniformly described herein, and details are not described herein again.

The following steps are the process of generating a sliced instance of the business topology:

S705. The device for generating an instance service topology acquires a network topology of the slice.

Specifically, when the network deployment phase of the instance service topology generating device from the network topology processing entity carries the network topology of the NS instance, the instance service topology generating device obtains the network topology of the slice. The device includes: an NSM ID (or a slice template or a slice template ID) in the slice template, and an NSD ID (or a slice template or a slice template ID) in the pre-stored slice template and a network topology of the NS instance. The network topology of the NS instance corresponding to the NSD ID (or the slice template or the slice template ID) in the slice template is the network topology of the slice. Or, for the case that the one slice template corresponds to multiple slice orders, the instance service topology generating device acquires the network topology of the slice, and the method may include: the instance service topology generating device according to the NSD ID (or the slice template or Slice template ID) and the slice order of the slice (or the number of the slice order), and the correspondence between the NSD ID (or slice template or slice template ID), the slice order (or the number of the slice order), and the network topology of the NS instance, Determining the NSD ID (or slice template or slice template ID) in the slice template and the network topology of the NS instance corresponding to the slice order of the slice is the network topology of the slice.

In the network deployment phase, the instance service topology generating device obtains the NS instance ID from the network topology processing entity, and the instance service topology generating device obtains the network topology of the slice, which may include: the instance service topology. The generating device determines the corresponding relationship between the NSD ID (or the slice template or the slice template ID) in the slice template and the NSD ID (or the slice template or the slice template ID) in the pre-stored slice template and the NS instance ID. The NS instance ID corresponding to the NSD ID (or the slice template or the slice template ID) in the slice template; the instance service generating device sends a network topology request message to the network topology processing entity, where the network topology request message carries the NS instance ID; The service generating device receives the network topology response message from the network topology processing entity, where the network topology response message carries the network topology corresponding to the NS instance ID. Or, for the case that the one slice template corresponds to multiple slice orders, the instance service topology generating device acquires the network topology of the slice, and the method may include: the instance service topology generating device according to the NSD ID (or the slice template or Slice template ID) and the slice order of the slice (or the number of the slice order), and the pre-stored NSD ID (or slice template or slice template ID), the slice order (or the number of the slice order) and the corresponding NS instance ID a relationship, determining an NSD ID (or a slice template or a slice template ID) in the slice template and an NS instance ID corresponding to the slice order of the slice; the instance service generating device sends a network topology request message to the network topology processing entity, the network topology The request message carries the NS instance ID. The generating device of the instance service receives the network topology response message from the network topology processing entity, where the network topology response message carries the network topology corresponding to the NS instance ID.

S706. The generating device of the instance service topology sends an identifier of the logical service topology to the logical service topology processing entity, so that the logical service topology processing entity receives the identifier of the logical service topology of the generating device from the instance service topology.

S707. The logical service topology processing entity determines a logical service topology of the slice according to the identifier of the logical service topology.

S708. The logical service topology processing entity sends the logical service topology of the slice to the generating device of the instance service topology, so that the generating device of the instance service topology receives the logical service topology from the logical service topology processing entity.

S709. The instance service topology generating device extracts any two network function instances from the network topology, and assumes that any two network function instances are the first network function instance and the second network function entity.

S710. The device for generating an instance service topology determines, according to the logical service topology, whether a service connection relationship exists between the first network function corresponding to the first network function instance and the second network function corresponding to the second network function instance.

If yes, proceed to step S711; if not, go to step S715.

S711: The device for generating an instance service topology determines, according to the network topology, whether a physical connection relationship exists between the first network function instance and the second network function instance.

If yes, proceed to step S712; if not, go to step S715.

S712. The generating device of the instance service topology sends a policy request message to the external policy entity, so that the external policy entity receives the policy request message from the generating device of the instance service topology. The policy request message carries at least one of attribute information of the first network function instance, attribute information of the second network function instance, and attribute information of a physical connection between the first network function instance and the second network function instance. A policy of requesting whether a service connection is allowed to be established between the first network function instance and the second network function instance.

Optionally, in the embodiment of the present application, the attribute information of the first network function instance or the attribute information of the second network function instance may specifically include information such as location and size; physical between the first network function instance and the second network function instance. The attribute information of the connection may specifically include information such as the network connection bandwidth, which is not specifically limited in this embodiment of the present application.

S713. The external policy entity sends a policy response message to the generating device of the instance service topology, so that the generating device of the instance service topology receives the policy response message from the external policy entity. The policy response message carries indication information about whether a service connection is allowed to be established between the first network function instance and the second network function instance.

S714. The device for generating an instance service topology determines, according to the policy response message, whether a service connection relationship exists between the first network function instance and the second network function instance in the instance service topology of the slice.

For example, if the policy response message carries a policy that allows a service connection to be established between the first network function instance and the second network function instance, the instance service topology generating device may determine the first network in the sliced instance service topology. A service connection relationship exists between the function instance and the second network function instance; otherwise, the instance service topology generating device may determine that there is no service connection between the first network function instance and the second network function instance in the sliced instance service topology. relationship.

That is, when the following three conditions are met at the same time, the generating device of the instance service topology determines that there is a service connection relationship between the first network function instance and the second network function instance in the instance service topology of the slice; If any one of the conditions is not met, the generating device of the instance service topology determines that there is no service connection relationship between the first network function instance and the second network function instance:

Condition 1: The generating device of the instance service topology determines, according to the network topology, that there is a physical connection relationship between the first network function instance and the second network function instance;

Condition 2: The generating device of the instance service topology determines, according to the logical service topology, that there is a service connection relationship between the first network function corresponding to the first network function instance and the second network function corresponding to the second network function instance;

Condition 3: The generating device of the instance service topology determines, according to the generating policy, that a service connection is allowed to be established between the first network function instance and the second network function instance.

It should be noted that the above steps S710-S714 are merely exemplary to determine whether the condition 2 is satisfied first, and then determine whether the condition 1 is satisfied, and finally determine whether the condition 3 is satisfied, thereby determining the generating device of the example service topology. A specific implementation of the service connection relationship exists between the first network function instance and the second network function instance in the example service topology of the slice, but the embodiment of the present application does not limit whether the conditions of the foregoing condition 1, condition 2, and condition 3 are satisfied. For example, it may be determined whether the condition 1 is satisfied first, whether it is determined whether the condition 2 is satisfied, and finally whether the condition 3 is satisfied, etc., and will not be repeated here.

S715. The generating device of the instance service topology continues from step S709 to cycle through all network function instances in the network topology.

After traversing all the network function instances in the network topology, you can get the sliced instance service topology.

After the network topology of the slice, the logical business topology of the slice, and the generation policy of the sliced instance service topology are acquired, the instance service topology generation device generates the instance service topology of the slice according to the network topology, the logical service topology, and the generation policy. The pseudo code can be expressed as follows:

It should be noted that the above pseudo code of the instance business topology of the generated slice is:

The generating device of the instance service topology identifies how many network function instances exist in the network topology, and numbers the network function instances in the network topology in any order, such as the first network function instance, the second network function instance, and the like.

Then, starting from the first network function instance, determining whether the first network function corresponding to the first network function instance and the network function corresponding to the other network function instance have a service connection relationship according to the logical service topology; determining the first according to the network topology Whether there is a service connection relationship between the network function instance and the other network function instance; determining whether the service is allowed to be established between the first network function instance and the second network function instance according to the generation policy.

Then, from the second network function instance, the above operation for the first network function instance is performed until all network function instance traversal in the network topology is completed.

Based on the method for generating an example service topology provided by the embodiment of the present application, on the one hand, the embodiment of the application may automatically generate an instance service topology of the slice by using the instance service topology generating device, and further complete the service deployment of the slice according to the service topology of the instance. . You can re-generate the changed network topology or logical service topology or generate a policy and regenerate the instance service topology in the case of a network topology or a logical service topology or a policy change. As long as the network topology or the logical service topology or the generation policy is changed, the vendor needs to redesign the sliced instance service topology and write the corresponding service configuration script according to the sliced instance service topology. The service deployment of the slice is completed, so that the embodiment of the present application can improve the flexibility and simplicity of the slice service deployment. On the other hand, the embodiment of the present application sets the information of the network topology of the slice and the information of the logical service topology of the slice in a slice template, because the slice template is preset by the vendor personnel or the slice operation and maintenance personnel. Therefore, based on the scheme, the versatility and portability of the slicing service deployment can be improved. On the other hand, since the generation strategy of the instance service topology in the embodiment of the present application is an external generation strategy, and the external policy may be formulated according to the needs of the customer, and is easy to implement, based on the solution, the implementation difficulty may not be increased. Under the premise, it is convenient to realize the user's personalized demand for the slice, without the intervention of the manufacturer. On the other hand, when determining whether there is a service connection relationship between any two network function instances in the network topology, the foregoing condition 1 is considered from the perspective of network conditions, and the above condition 2 is considered from the perspective of service requirements, and the foregoing conditions are considered. 3 is considered from the perspective of customer needs. That is to say, the method for determining whether there is a service connection relationship between any two network function instances in the network topology provided by the embodiment of the present application considers network conditions, service requirements, and customer requirements, and thus determines any two of the network topologies. The method of whether the service connection relationship exists between the network function instances is more comprehensive and complete, so that the accuracy of the generated instance service topology can be further improved, and the accuracy of the service deployment can be further improved.

The action of the generating device of the example service topology in the foregoing steps S701 to S715 can be performed by the processor 601 in the generating device 600 of the example service topology shown in FIG. 6 to call the application code stored in the memory 603. There are no restrictions on this.

Optionally, the embodiment shown in FIG. 7 is an example of an external generation policy obtained from an external policy entity by using a generation policy of the instance service topology of the slice as an example. Of course, the generation strategy of the sliced instance service topology may also be as follows:

Case 1: The instance of the sliced business topology generation strategy is the default generation policy in the slice template. Because the slice template is set by the manufacturer or the slice operation and maintenance personnel in advance, based on the solution, the versatility and portability of the slice service deployment can be improved.

Case 2: The instance of the sliced service topology generation policy is determined by the default generation policy and the external generation policy: for example, the external generation policy can be set to a high priority policy by priority, so that the instance service topology generation device When the external generation policy is obtained, the external generation policy is set as the generation strategy of the instance business topology; or the default generation policy and the external generation policy may be combined to form an instance business topology generation policy. Since the generation policy of the instance service topology is determined by the default generation policy and the external generation policy, not only is the user more selective; and since the external policy can be customized according to the customer's needs and is easy to implement, Under the premise of not increasing the difficulty of implementation, it is convenient to realize the user's personalized requirement for the slice without the intervention of the manufacturer.

Optionally, the external generation policy in the embodiment of the present application may be an external generation policy obtained from an external policy entity. Alternatively, the external generation policy in the embodiment of the present application may also be an externally input policy generated by the instance service topology. The external generation policy for determining the information is not specifically limited in this embodiment of the present application.

Optionally, when the external generation policy is obtained, the embodiment shown in FIG. 7 is configured to obtain the generation strategy corresponding to the two network function instances when the two network function instances in the network topology are processed. . Of course, the device for generating the instance service topology may also be an external generation policy for acquiring the service topology of the entire instance at one time, which is not specifically limited in this embodiment of the present application.

Optionally, in the embodiment of the present application, after the instance service topology of the slice is generated, the method further includes: the instance service topology generating device acquires standard interface information of the N network function instances; and according to the instance service topology and the standard interface information, Generate business configuration information for the slice.

Because the solution does not need to manually write a corresponding service configuration script for the instance service topology of the slice, the service configuration information of the slice can be automatically generated according to the instance service topology and the standard interface information, that is, the automatic service deployment can be implemented, so Improve the flexibility and simplicity of the slicing business deployment.

Optionally, in the embodiment of the present application, the instance service topology generating device generates the service configuration information of the slice according to the instance service topology and the standard interface information, and specifically includes: performing services on any non-serving architecture interface in the instance service topology. The connection relationship, the instance service topology generating device is processed according to the service connection relationship of the non-serving architecture interface between the third network function instance and the fourth network function instance:

Generating first service configuration information for the third network function instance according to the interface information of the third network function instance in the standard interface information; and generating the fourth network function instance according to the interface information of the fourth network function instance in the standard interface information Second service configuration information;

Or, for the service connection relationship of any service architecture interface in the instance service topology, the device for generating the instance service topology is in accordance with the service connection relationship of the service architecture interface between the fifth network function instance and the sixth network function instance. Mode processing:

Generating third service configuration information for the service discovery node according to the interface information of the fifth network function instance in the standard interface information; and generating a fourth service configuration for the service discovery node according to the interface information of the sixth network function instance in the standard interface information The information, wherein the third service configuration information is used by the fifth network function instance to discover the sixth network function instance by using the service discovery node, and the fourth service configuration information is used by the sixth network function instance to discover the fifth network function instance by using the service discovery node.

The non-serving architecture interface between the third network function instance and the fourth network function instance is configured as the service connection relationship between the network function instance and the fourth network function instance. When the service connection relationship is processed, the corresponding service configuration information may be generated for the third network function instance and the fourth network function instance, respectively, so that the corresponding service configuration may be completed; the service connection relationship of the serviced architecture interface refers to the service discovery. The service connection of the service call can be dynamically established, so when the service connection relationship of the service architecture interface between the fifth network function instance and the sixth network function instance is processed, the corresponding service configuration information is generated for the service discovery node. The service configuration information is used for mutual discovery between the fifth network function instance and the sixth network function instance, so that the corresponding service configuration can be completed.

Exemplarily, according to FIG. 1d, the service connection relationship between the eNB and the AMF is a service connection relationship of the non-serving architecture interface, so the service connection relationship between the eNB2 and the AMF entity 2 in FIG. 1c is a non-serving architecture. The service connection relationship of the interface, the device for generating the instance service topology may generate service configuration information for the eNB2 according to the N2 interface information of the eNB2; and the device for generating the instance service topology may generate the AMF entity 2 according to the N2 interface information of the AMF entity 2 Business configuration information.

Or, exemplarily, according to FIG. 1d, the service connection relationship between the SMF and the AMF is a service connection relationship of the service architecture interface, so the service connection relationship between the SMF entity 1 and the AMF entity 1 in FIG. 1c is non- The device for generating the service architecture interface may generate the service configuration information 1 for the NRF entity according to the Nsmf interface information of the SMF entity 1; and the device for generating the instance service topology may be based on the Namf interface of the AMF entity 1 Information, generating service configuration information 2 for the NRF entity. The service configuration information 1 is used by the SMF entity 1 to discover the AMF entity 1 through the NRF entity, and the service configuration information 2 is used by the AMF entity 1 to discover the SMF entity 1 through the NRF entity. In addition, when processing the service discovery request of each network function instance, the NRF entity can implement the control of the service topology according to the service configuration information on the NRF entity. For example, when the AMF entity 1 requests the SMF service discovery to the NRF entity, the NRF entity according to the service The configuration information only provides the service address of the SMF entity 1 to the AMF entity 1 in the response message, and does not provide the service address of the SMF entity 2.

A method for generating an example service topology provided by an embodiment of the present application will be described below with reference to a specific example.

Exemplarily, first, assume that the network topology of the slice acquired by the generating device of the instance service topology is as shown in FIG. 8a:

In FIG. 8a, the network topology of the slice includes an access network (AN) device 1, an AMF entity 1, an SMF entity 1, a UPF entity 1, an NRF entity, an AN device 2, an AMF entity 2, and an SMF entity 2 The physical connection relationship between the UPF entity 1 and the above network function instances. For example, since the urban A metropolitan area network and the urban B metropolitan area network are physically connected by long-distance transmission trunk lines, the AN equipment 1, the AMF entity 1, the SMF entity 1 and the UPF entity 1 can be physically connected through the city A metropolitan area network. The AN device 2, the AMF entity 2, the SMF entity 2, and the UPF entity 2 can all be connected through the city B metropolitan area network, so the AN device 1, the AMF entity 1, the SMF entity 1, the UPF entity 1, the NRF entity, and the AN device 2. There is a physical connection between any two network function instances between AMF entity 2, SMF entity 2, and UPF entity 1.

Second, assume that the logical service topology of the slice obtained by the instance service topology generating device is as shown in Figure 8b:

In FIG. 8b, the logical service topology of the slice includes an AN, an AMF, an SMF, a UPF, an NRF, and a service connection relationship between the foregoing network functions. For example, there is a service connection relationship between the AN and the UPF for the service session; a service for transmitting control signaling exists between the AN and the AMF, between the AMF and the AMF, between the AMF and the SMF, and between the SMF and the UPF. Connection relationship; NRF and AMF, and NRF and SMF have a service connection relationship for service discovery.

And, the generation strategy of the instance service topology of the slice obtained by the generating device of the instance service topology is: the AN device establishes a service connection with the local AMF, the AMF only requests the local SMF to provide the service session, and the UPF is controlled by the local SMF.

Then, the generating device of the instance service topology may generate an instance service topology of the slice based on the following method:

Step 1: The device for generating the instance service topology takes out any two network function instances from the network topology. Here, the AN device 1 and the UPF entity 1 are taken as an example.

Step 2: The device for generating the instance service topology determines whether there is a service connection relationship between the AN device 1 and the UPF entity 1.

The embodiment of the present application can determine whether there is a service connection relationship between the AN device 1 and the UPF entity 1 according to the conditions 1, the condition 2, and the condition 3 in the foregoing embodiment.

For the condition 1, according to the network topology of the slice shown in FIG. 8a, there is a physical connection relationship between the AN device 1 and the UPF entity 1.

For condition 2, according to the logical service topology of the slice shown in FIG. 8b, there is a service connection relationship between the AN and the UPF for the service session.

For condition 3, according to the generation policy of the instance service topology of the above slice, it can be known that the service connection is allowed between the AN device 1 and the UPF entity 1.

The device for generating the instance service topology can determine that there is a service connection relationship between the AN device 1 and the UPF entity 1, and the device for generating the instance service topology can add the AN device 1 and the UPF, because the condition 1, the condition 2, and the condition 3 are satisfied. The business connection relationship between entities 1 is as shown in Figure 8c.

Step 3: For any two network function instances in the network topology of the slice shown in FIG. 8a, similar processing is performed according to the foregoing step 2, until all network function instances in the network topology of the slice shown in FIG. 8a are traversed. carry out.

For example, taking AMF entity 1 and SMF entity 2 as an example, whether there is a service connection relationship between AMF entity 1 and SMF entity 2 can be determined according to conditions 1, condition 2 and condition 3 in the above embodiment.

For the condition 1, according to the network topology of the slice shown in FIG. 8a, there is a physical connection relationship between the AMF entity 1 and the SMF entity 2.

For condition 2, according to the logical service topology of the slice shown in FIG. 8b, there is a service connection relationship between the AMF and the SMF for the service session.

For condition 3, according to the generation policy of the instance service topology of the above slice, it can be known that the service connection is not allowed between the AMF entity 1 and the SMF entity 2.

Since the foregoing condition 1, condition 2, and condition 3 are not satisfied at the same time, the generating device of the instance service topology may determine that there is no service connection relationship between the AMF entity 1 and the SMF entity 2, and the generating device of the instance service topology does not add the AMF entity 1 The service connection relationship with the SMF entity 2 is as shown in Figure 8c.

At this point, the process of generating the instance service topology of the slice ends, and the service configuration information of the slice can be further generated according to the service topology of the instance, thereby completing the service deployment of the slice, and improving the flexibility and simplicity of the slice service deployment. For the process of generating the service configuration information of the slice according to the example service topology, reference may be made to the example in the foregoing embodiment, and details are not described herein again.

The solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements. It can be understood that, in order to implement the above functions, the generating device of the above-mentioned example service topology includes corresponding hardware structures and/or software modules for performing respective functions. Those skilled in the art will readily appreciate that the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

The embodiment of the present application may divide the function module of the instance service topology generating device according to the foregoing method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one processing module. . The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.

For example, in the case of dividing each functional module by using corresponding functions, FIG. 9 shows a possible structural diagram of the generating device 90 of the example service topology involved in the above embodiment. The instance service topology generating device 90 includes a processing module 901. The processing module 901 is configured to acquire a network topology of the slice, a logical service topology of the slice, and a generation policy of the sliced instance service topology, where the network topology is used to represent between the N network function instances and the N network function instances. The network layout formed by the physical connection relationship, the logical service topology is used to represent the network layout composed of the M network functions and the service connection relationship between the M network functions, and the generation strategy is used to represent any two of the N network function instances. Whether a service connection is allowed to be established between the function instances, and M and N are positive integers. The processing module 901 is further configured to generate a service instance of the slice according to the network topology, the logical service topology, and the generation policy, where the instance service topology is used. A network layout constituting a network connection instance between N network function instances and N network function instances.

Optionally, as shown in FIG. 9, the device for generating the service topology of the example may further include a storage module 902 and a transceiver module 903. The storage module 902 is configured to store a pre-loaded slice module. The transceiver module 903 is configured to communicate with an external device, such as an external device such as a network topology processing entity or a logical service topology processing entity or an external policy entity in FIG. 5.

The processing module 901 acquires the network topology of the slice, the logical service topology of the slice, and the generation policy of the instance service topology of the slice, including: obtaining the network topology information corresponding to the network topology from the slice template, and the logical service topology information corresponding to the logical service topology, and Generate a policy; obtain a network topology based on the network topology information; and obtain a logical service topology according to the logical service topology information.

Alternatively, the processing module 901 obtains the network topology of the slice, the logical service topology of the slice, and the generation policy of the instance service topology of the slice, including: obtaining the network topology information corresponding to the network topology from the slice template, and corresponding to the logical service topology. The logical service topology information, and the default generation policy of the instance service topology; and the external generation policy of the instance service topology, wherein the instance service topology generation policy is determined by the default generation policy and the external generation policy; and the network is obtained according to the network topology information. Topology; obtains a logical service topology based on logical service topology information.

Alternatively, the processing module 901 obtains the network topology of the slice, the logical service topology of the slice, and the generation policy of the instance service topology of the slice, including: obtaining the network topology information corresponding to the network topology and the logical service topology corresponding to the slice template. The logical service topology information; and the external generation policy of the instance service topology, wherein the generation strategy of the instance service topology is an external generation policy; the network topology is obtained according to the network topology information; and the logical service topology is obtained according to the logical service topology information.

In a possible implementation, the network topology information includes an NSD ID, and the processing module 901 obtains the network topology according to the network topology information, including: determining a network topology of the network service instance corresponding to the NSD ID as a slice network topology; or determining The network topology of the sliced slice order and the network service instance corresponding to the NSD ID is the network topology of the slice.

In a possible implementation, the network topology information includes an NSD ID, and the processing module 901 obtains the network topology according to the network topology information, including: determining, according to the NSD ID, a network service instance ID corresponding to the slice; or, according to the sliced slice order And determining, by the NSD ID, a network service instance ID corresponding to the slice; the network topology processing entity sends a network topology request message, where the network topology request message carries the network service instance ID; and receives a network topology of the slice from the network topology processing entity.

In a possible implementation, the logical service topology information is used to describe the logical service topology; the processing module 901 obtains the logical service topology according to the logical service topology information, including: determining the logical service topology according to the logical service topology information;

In another possible implementation, the logical topology information includes an identifier of the logical service topology, and the processing module 901 obtains the logical service topology according to the logical service topology information, including: sending a logical service topology request message to the logical service topology processing entity, and logic The service topology request message carries an identifier of a logical service topology, the identifier of the logical service topology is used to obtain a logical service topology, and the logical service topology from the logical service topology processing entity is received.

Optionally, the processing module 901 generates an instance service topology of the slice according to the network topology, the logical service topology, and the generation policy, including: determining, according to the network topology, the logical service topology, and the generation policy, between the two network function instances in the network topology. Whether there is a service connection relationship; according to the determination result, an instance service topology of the slice is generated.

Optionally, the processing module 901 determines, according to the network topology, the logical service topology, and the generation policy, whether there is a service connection relationship between any two network function instances in the network topology, including: determining the first when the following three conditions are met simultaneously A service connection relationship exists between the network function instance and the second network function instance; if any one of the following three conditions is not met, determining that there is no service connection relationship between the first network function instance and the second network function instance; The first network function instance and the second network function instance are any two network function instances in the network topology; condition 1: determining, according to the network topology, a physical connection relationship between the first network function instance and the second network function instance; Condition 2: determining, according to the logical service topology, a service connection relationship between the first network function corresponding to the first network function instance and the second network function corresponding to the second network function instance; condition 3: determining the first network according to the generation policy A service connection is allowed between the function instance and the second network function instance.

Optionally, the processing module 901 is further configured to acquire standard interface information of the N network function instances after the instance service topology of the slice is generated according to the network topology, the logical service topology, and the generation policy. The processing module 901 is further configured to: The instance service topology and standard interface information are generated, and the service configuration information of the slice is generated.

Optionally, the processing module 901 generates the service configuration information of the slice according to the instance service topology and the standard interface information, including: the service connection relationship of any non-serving architecture interface in the instance service topology, according to the third network function instance. And processing the service connection relationship of the non-serving architecture interface between the fourth network function instance: generating the first service configuration information for the third network function instance according to the interface information of the third network function instance in the standard interface information; Generating second service configuration information for the fourth network function instance according to the interface information of the fourth network function instance in the standard interface information; or, for the service connection relationship of any service architecture interface in the instance service topology, according to the And processing the service connection relationship of the service architecture interface between the network function instance and the sixth network function instance: generating third service configuration information for the service discovery node according to the interface information of the fifth network function instance in the standard interface information; And, according to the standard interface information, the sixth The interface information of the network function instance generates a fourth service configuration information for the service discovery node, where the third service configuration information is used by the fifth network function instance to discover the sixth network function instance by using the service discovery node, and the fourth service configuration information is used for The sixth network function instance discovers the fifth network function instance through the service discovery node.

All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

In the present embodiment, the instance service topology generating means 90 is presented in the form of dividing the functional modules in an integrated manner. A "module" herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device. In a simple embodiment, those skilled in the art will appreciate that the instance service topology generation device 90 can take the form shown in FIG.

For example, the processor 601 in FIG. 6 can execute the instruction executed by the computer stored in the memory 603, so that the instance service topology generating device 90 executes the method for generating the instance service topology in the foregoing method embodiment.

Specifically, the function/implementation process of the processing module 901 and the transceiver module 903 in FIG. 9 can be implemented by the processor 601 in FIG. 6 calling the computer execution instruction stored in the memory 603; the function of the storage module 902 in FIG. The implementation process can be implemented by the memory 603 in FIG. Alternatively, the function/implementation process of the processing module 901 in FIG. 9 can be implemented by the processor 601 in FIG. 6 calling the computer execution instruction stored in the memory 603, and the function/implementation process of the transceiver module 903 in FIG. The communication interface 604 in 6 is implemented; the function/implementation process of the storage module 902 in FIG. 9 can be implemented by the memory 603 in FIG.

In the above embodiment, the instance service topology generating means 90 is presented in the form of dividing the functional modules in an integrated manner. Certainly, the embodiments of the present application may also be used to divide each function module of the device for generating an instance service topology according to each function, which is not specifically limited in this embodiment of the present application.

The device for generating the instance service topology provided by the embodiment of the present application may automatically generate an instance service topology of the slice, and the service deployment of the slice may be further completed according to the service topology of the instance. You can re-generate the changed network topology or logical service topology or generate a policy and regenerate the instance service topology in the case of a network topology or a logical service topology or a policy change. As long as the network topology or the logical service topology or the generation policy is changed, the vendor needs to redesign the sliced instance service topology and write the corresponding service configuration script according to the sliced instance service topology. The service deployment of the slice service is completed, so that the device for generating the instance service topology provided by the embodiment of the present application can improve the flexibility and simplicity of the slice service deployment.

Optionally, the embodiment of the present application provides a chip system, where the chip system includes a processor, and a generating device for supporting an instance service topology, to implement the foregoing method for generating an instance service topology, such as acquiring a network topology of a slice, The logical business topology of the slice, and the generation strategy of the instance business topology of the slice. In one possible design, the chip system also includes a memory. The memory is used to store necessary program instructions and data for the generating device of the instance service topology. The chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

Although the present application has been described herein in connection with the various embodiments, those skilled in the art can Other variations of the disclosed embodiments are achieved. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill several of the functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that the measures are not combined to produce a good effect.

While the present invention has been described in connection with the specific embodiments and embodiments thereof, various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the description and drawings are to be regarded as It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

A method for generating an example service topology, where the method includes:

The generating device of the instance service topology acquires a network topology of the slice, a logical service topology of the slice, and a generation policy of the instance service topology of the slice; wherein the network topology is used to represent the N network function instances and the a network layout formed by a physical connection relationship between N network function instances, the logical service topology being used to represent a network layout composed of M network functions and service connection relationships between the M network functions, the generating The policy is used to identify whether a service connection is allowed to be established between any two network function instances of the N network function instances, where M and N are positive integers;

The generating device of the example service topology generates an instance service topology of the slice according to the network topology, the logical service topology and the generating policy, where the instance service topology is used to represent the N network functions A network layout formed by an instance and a service connection relationship between the N network function instances.
The method according to claim 1, wherein the generating device of the instance service topology acquires a network topology of the slice, a logical service topology of the slice, and a generation policy of the instance service topology of the slice, including:

The generating device of the example service topology acquires network topology information corresponding to the network topology from the slice template, logical service topology information corresponding to the logical service topology, and the generating policy;

The generating device of the instance service topology acquires the network topology according to the network topology information;

The generating device of the instance service topology acquires the logical service topology according to the logical service topology information.
The method according to claim 1, wherein the generating device of the instance service topology acquires a network topology of the slice, a logical service topology of the slice, and a generation policy of the instance service topology of the slice, including:

The generating device of the instance service topology acquires network topology information corresponding to the network topology from the slice template, logical service topology information corresponding to the logical service topology, and a default generation policy of the instance service topology;

And the generating device of the instance service topology acquires an external generation policy of the instance service topology, where the generation policy of the instance service topology is determined by the default generation policy and the external generation policy;

The generating device of the instance service topology acquires the network topology according to the network topology information;

The generating device of the instance service topology acquires the logical service topology according to the logical service topology information.
The method according to claim 1, wherein the generating device of the instance service topology acquires a network topology of the slice, a logical service topology of the slice, and a generation policy of the instance service topology of the slice, including:

The generating device of the example service topology acquires network topology information corresponding to the network topology and logical service topology information corresponding to the logical service topology from a slice template;

And the generating device of the instance service topology acquires an external generation policy of the instance service topology, where the generation policy of the instance service topology is the external generation policy;

The generating device of the instance service topology acquires the network topology according to the network topology information;

The generating device of the instance service topology acquires the logical service topology according to the logical service topology information.
The method according to any one of claims 2 to 4, wherein the network topology information comprises a network service descriptor NSD identifier ID; and the generating device of the instance service topology acquires the information according to the network topology information. Network topology, including:

The generating device of the instance service topology determines that the network topology of the network service instance corresponding to the NSD ID is the network topology of the slice;

Alternatively, the generating device of the instance service topology determines, according to the slice order of the slice and the NSD ID, that the network topology of the corresponding network service instance is the network topology of the slice.
The method according to any one of claims 2 to 4, wherein the network topology information comprises a network service descriptor NSD identifier ID; and the generating device of the instance service topology acquires the information according to the network topology information. Network topology, including:

The generating device of the instance service topology determines the network service instance ID corresponding to the slice according to the NSD ID; or the generating device of the instance service topology determines the location according to the slice order and the NSD ID of the slice Describe the network service instance ID corresponding to the slice;

The generating device of the example service topology sends a network topology request message to the network topology processing entity, where the network topology request message carries the network service instance ID;

The generating device of the instance service topology receives a network topology of the slice from the network topology processing entity.
The method according to any one of claims 2-6, wherein the logical service topology information is used to describe the logical service topology; and the generating device of the instance service topology is obtained according to the logical service topology information. The logical service topology includes:

The generating device of the instance service topology determines the logical service topology according to the logical service topology information;

Or the logical topology information includes the identifier of the logical service topology; the generating device of the instance service topology acquires the logical service topology according to the logical service topology information, including:

The generating device of the example service topology sends a logical service topology request message to the logical service topology processing entity, where the logical service topology request message carries an identifier of the logical service topology, and the identifier of the logical service topology is used to obtain the logic Business topology

The generating device of the instance service topology receives the logical service topology from the logical service topology processing entity.
The method according to any one of claims 1 to 7, wherein the generating device of the instance service topology generates an instance service of the slice according to the network topology, the logical service topology and the generating policy Topology, including:

The generating device of the example service topology determines, according to the network topology, the logical service topology and the generating policy, whether there is a service connection relationship between any two network function instances in the network topology;

The generating device of the instance service topology generates an instance service topology of the slice according to the determination result.
The method according to claim 8, wherein the generating device of the instance service topology determines any two network function instances in the network topology according to the network topology, the logical service topology and the generating policy Whether there is a business connection relationship between:

When the following three conditions are met, the generating device of the instance service topology determines that a service connection relationship exists between the first network function instance and the second network function instance; if any one of the following three conditions is not satisfied, determining There is no service connection relationship between the first network function instance and the second network function instance; wherein the first network function instance and the second network function instance are any two of the network topologies. Network function instance;

Condition 1: The device for generating the instance service topology determines, according to the network topology, that there is a physical connection relationship between the first network function instance and the second network function instance;

Condition 2: The generating device of the instance service topology determines, according to the logical service topology, that there is a service between the first network function corresponding to the first network function instance and the second network function corresponding to the second network function instance Connection relationship

Condition 3: The generating device of the instance service topology determines, according to the generating policy, that a service connection is allowed to be established between the first network function instance and the second network function instance.
The method according to any one of claims 1 to 9, wherein the generating device of the instance service topology generates an instance of the slice according to the network topology, the logical service topology and the generating policy After the business topology, it also includes:

The generating device of the instance service topology acquires standard interface information of the N network function instances;

The generating device of the instance service topology generates service configuration information of the slice according to the instance service topology and the standard interface information.
The method according to claim 10, wherein the generating device of the instance service topology generates the service configuration information of the slice according to the instance service topology and the standard interface information, including:

For the service connection relationship of any non-serving architecture interface in the instance service topology, the generating device of the instance service topology is configured according to the non-serving architecture interface between the third network function instance and the fourth network function instance. The way the business connection relationship is handled:

Generating first service configuration information for the third network function instance according to the interface information of the third network function instance in the standard interface information; and, according to the fourth network function instance in the standard interface information The interface information generates second service configuration information for the fourth network function instance;

Or, for the service connection relationship of any serviced architecture interface in the instance service topology, the generating device of the instance service topology is configured according to a service architecture interface between the fifth network function instance and the sixth network function instance. The way the business connection relationship is handled:

And generating third service configuration information for the service discovery node according to the interface information of the fifth network function instance in the standard interface information; and, according to the interface information of the sixth network function instance in the standard interface information, The service discovery node generates fourth service configuration information, where the third service configuration information is used by the fifth network function instance to discover the sixth network function instance by using the service discovery node, and the fourth service The configuration information is used by the sixth network function instance to discover the fifth network function instance by using the service discovery node.
An apparatus for generating an instance service topology, where the device for generating an instance service topology includes: a processing module;

The processing module is configured to acquire a network topology of a slice, a logical service topology of the slice, and a generation policy of an instance service topology of the slice, where the network topology is used to represent an instance of the N network function and the a network layout formed by a physical connection relationship between N network function instances, the logical service topology being used to represent a network layout composed of M network functions and service connection relationships between the M network functions, The generating policy is used to identify whether a service connection is allowed to be established between any two network function instances of the N network function instances, where M and N are positive integers;

The processing module is further configured to generate an instance service topology of the slice according to the network topology, the logical service topology, and the generation policy, where the instance service topology is used to represent the N network functions A network layout formed by an instance and a service connection relationship between the N network function instances.
The device for generating an example service topology according to claim 12, wherein the processing module acquires a network topology of the slice, a logical service topology of the slice, and a generation policy of the instance service topology of the slice, including:

Obtaining network topology information corresponding to the network topology from the slice template, logical service topology information corresponding to the logical service topology, and the generation policy;

Obtaining the network topology according to the network topology information;

Obtaining the logical service topology according to the logical service topology information.
The device for generating an example service topology according to claim 12, wherein the processing module acquires a network topology of the slice, a logical service topology of the slice, and a generation policy of the instance service topology of the slice, including:

Obtaining the network topology information corresponding to the network topology, the logical service topology information corresponding to the logical service topology, and the default generation policy of the instance service topology;

And obtaining an external generation policy of the instance service topology, where the generation policy of the instance service topology is determined by the default generation policy and the external generation policy;

Obtaining the network topology according to the network topology information;

Obtaining the logical service topology according to the logical service topology information.
The device for generating an example service topology according to claim 12, wherein the processing module acquires a network topology of the slice, a logical service topology of the slice, and a generation policy of the instance service topology of the slice, including:

Obtaining, by using a slice template, network topology information corresponding to the network topology and logical service topology information corresponding to the logical service topology;

And acquiring an external generation policy of the instance service topology, where the generation policy of the instance service topology is the external generation policy;

Obtaining the network topology according to the network topology information;

Obtaining the logical service topology according to the logical service topology information.
The device for generating an example service topology according to any one of claims 13 to 15, wherein the network topology information includes a network service descriptor NSD identifier ID, and the processing module acquires the network topology information according to the network topology information. The network topology, including:

Determining, by using a network topology of the network service instance corresponding to the NSD ID, a network topology of the slice;

Or determining that the slice order of the slice and the network topology of the network service instance corresponding to the NSD ID are the network topology of the slice.
The apparatus for generating an example service topology according to claim 16, wherein the network topology information comprises a network service descriptor NSD identifier ID, and the processing module acquires the network topology according to the network topology information, including :

Determining, according to the NSD ID, a network service instance ID corresponding to the slice; or determining a network service instance ID corresponding to the slice according to the sliced order of the slice and the NSD ID;

Sending a network topology request message to the network topology processing entity, where the network topology request message carries the network service instance ID;

A network topology of the slice from the network topology processing entity is received.
The device for generating an example service topology according to any one of claims 13-17, wherein the logical service topology information is used to describe the logical service topology; and the processing module is configured according to the logical service topology information. Obtaining the logical service topology, including:

Determining the logical service topology according to the logical service topology information;

Or the logical topology information includes an identifier of the logical service topology; the processing module acquires the logical service topology according to the logical service topology information, including:

Sending a logical service topology request message to the logical service topology processing entity, where the logical service topology request message carries an identifier of the logical service topology, where the identifier of the logical service topology is used to acquire the logical service topology;

Receiving the logical service topology from the logical service topology processing entity.
The device for generating an example service topology according to any one of claims 12 to 18, wherein the processing module generates an instance of the slice according to the network topology, the logical service topology, and the generation policy. Business topology, including:

Determining, according to the network topology, the logical service topology and the generating policy, whether there is a service connection relationship between any two network function instances in the network topology;

Based on the determination result, an instance service topology of the slice is generated.
The device for generating an example service topology according to claim 19, wherein the processing module determines any two network functions in the network topology according to the network topology, the logical service topology, and the generation policy. Whether there is a business connection relationship between the instances, including:

When the following three conditions are met, determining that there is a service connection relationship between the first network function instance and the second network function instance; if any one of the following three conditions is not met, determining the first network function instance and There is no service connection relationship between the second network function instances; wherein the first network function instance and the second network function instance are any two network function instances in the network topology;

Condition 1: determining, according to the network topology, that there is a physical connection relationship between the first network function instance and the second network function instance;

Condition 2: determining, according to the logical service topology, a service connection relationship between the first network function corresponding to the first network function instance and the second network function corresponding to the second network function instance;

Condition 3: According to the generating policy, determining that a service connection is allowed to be established between the first network function instance and the second network function instance.
An apparatus for generating an example service topology according to any one of claims 12 to 20, characterized in that

The processing module is further configured to acquire standard interface information of the N network function instances after the instance service topology of the slice is generated according to the network topology, the logical service topology, and the generation policy. ;

The processing module is further configured to generate service configuration information of the slice according to the instance service topology and the standard interface information.
The device for generating an example service topology according to claim 21, wherein the processing module generates the service configuration information of the slice according to the instance service topology and the standard interface information, including:

The service connection relationship of any non-serving architecture interface in the instance service topology is processed according to the service connection relationship of the non-serving architecture interface between the third network function instance and the fourth network function instance:

Generating first service configuration information for the third network function instance according to the interface information of the third network function instance in the standard interface information; and, according to the fourth network function instance in the standard interface information The interface information generates second service configuration information for the fourth network function instance;

Or, the service connection relationship of any serviced architecture interface in the instance service topology is processed according to the service connection relationship of the service architecture interface between the fifth network function instance and the sixth network function instance:

And generating third service configuration information for the service discovery node according to the interface information of the fifth network function instance in the standard interface information; and, according to the interface information of the sixth network function instance in the standard interface information, The service discovery node generates fourth service configuration information, where the third service configuration information is used by the fifth network function instance to discover the sixth network function instance by using the service discovery node, and the fourth service The configuration information is used by the sixth network function instance to discover the fifth network function instance by using the service discovery node.
An apparatus for generating an instance service topology, wherein the apparatus for generating an instance service topology includes a processor and a memory;

The memory is configured to store computer execution instructions that, when the generating device of the instance service topology is running, execute the computer-executed instructions stored by the memory to cause the generating device of the instance service topology to execute A method of generating an example service topology as claimed in any of claims 1-11.