CN109526032B

CN109526032B - Method and device for modifying network slice example

Info

Publication number: CN109526032B
Application number: CN201710841751.XA
Authority: CN
Inventors: 杨水根; 谭巍; 陆伟; 孙文琦; 冯珍妮; 蒋若冰
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-09-18
Filing date: 2017-09-18
Publication date: 2021-02-09
Anticipated expiration: 2037-09-18
Also published as: CN109526032A; WO2019052363A1

Abstract

The application discloses a method and a device for modifying a network slice example, which are used for modifying the network slice example. The method for modifying the network slice example comprises the following steps: the method comprises the steps that a first network device receives a first request from a second network device, wherein the first request comprises identification of a network slice example, identification of a network slice subnet example and indication information; the indication information is used for indicating the first network equipment to add the network slice subnet instance into the network slice instance or indicating the first network equipment to delete the network slice subnet instance from the network slice instance; the first network device adds a network slice subnet instance to the network slice instance according to the first request or deletes the network slice subnet instance from the network slice instance according to the first request. The present application relates to the field of communications.

Description

Method and device for modifying network slice example

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for modifying a network slice instance.

Background

With the rapid development of mobile communication, digital transformation has involved almost all the conventional industries. However, the conventional cellular network architecture can only provide uniform network services, and it is difficult to satisfy the communication requirements with great differences, including functional differences, performance differences, etc., brought by the digitalized transformation surge. In a fifth generation (5G) wireless communication system, a network is abstracted as "network slices," one network slice satisfies a certain type or one use case of connection communication service requirements, and the entire 5G network is composed of a large number of network slices satisfying different connection capabilities. A unified network platform, which supports connection communication services with different functions and quality of service (QoS) by using a dynamic and secure network slice, is one of the basic capabilities of a 5G network.

A network slice instance is created by a network slice management system that may create and manage multiple network slice instances simultaneously, including performance monitoring, fault management, modification, etc. during operation of the network slice instance. However, at present, there is no technical solution how to implement the modification of the network slice example.

Disclosure of Invention

The embodiment of the application provides a method and a device for modifying a network slice example, which are used for modifying the network slice example.

In order to achieve the above purpose, the embodiments of the present application provide the following technical solutions:

in a first aspect, a method for modifying a network slice instance is provided, the method comprising: the method comprises the steps that a first network device receives a first request from a second network device, wherein the first request comprises identification of a network slice example, identification of a network slice subnet example and indication information; the indication information is used for indicating the first network equipment to add the network slice subnet instance into the network slice instance or indicating the first network equipment to delete the network slice subnet instance from the network slice instance; the first network device adds a network slice subnet instance to the network slice instance according to the first request or deletes the network slice subnet instance from the network slice instance according to the first request. In the method provided by the first aspect, the first network device adds or deletes the NSSI in the NSI according to the first request sent by the second network device, the network function provided by the NSI can be changed by adding or deleting the NSSI in the NSI, and the NSI can meet the service requirement or guarantee the network performance under the condition that the NSSI is added or deleted in the NSI according to the service requirement or the network performance.

In one possible design, adding a network slice subnet instance to a service endpoint description of the network slice subnet instance corresponding to configuring an identification of the network slice instance into an identification of the network slice subnet instance, such that the network slice subnet instance provides a service for the network slice instance; deleting a network slice subnet instance from a network slice instance corresponds to deleting the identity of the network slice instance from the service endpoint description of the network slice subnet instance identified by the identity of the network slice subnet instance, such that the network slice subnet instance no longer provides service for the network slice instance.

In one possible design, after the first network device adds a network slice subnet instance to the network slice instance according to the first request or deletes a network slice subnet instance from the network slice instance according to the first request, the method further includes: the first network device sends a first response to the second network device, the first response indicating whether the first network device successfully added or removed the network-slice subnet instance to or from the network-slice instance.

In a second aspect, a method for modifying a network slice instance is provided, the method comprising: the second network equipment determines to modify the network slice instance; the second network equipment sends a first request to the first network equipment, wherein the first request comprises the identification of the network slice instance, the identification of the network slice subnet instance and the indication information; the indication information is used to instruct the first network device to add the network slice subnet instance to the network slice instance or to instruct the first network device to delete the network slice subnet instance from the network slice instance. In the method provided by the second aspect, when it is determined that the NSI needs to be modified, the second network device sends a first request to the first network device, where the first request includes the NSI ID, the NSSI ID, and the indication information, so that the first network device adds or deletes the NSSI in the NSI according to the first request, and the network function provided by the NSI can be changed by adding or deleting the NSSI in the NSI, and in the case that the NSSI is added or deleted in the NSI according to the service requirement or the network performance, the NSI can meet the service requirement or ensure the network performance.

In one possible design, the second network device determines to modify the network slice instance, including: the second network equipment receives a modification request of the network slice instance; or the second network equipment determines to modify the network slice instance according to the current running state of the network slice instance and a preset rule.

In one possible design, after the second network device sends the first request to the first network device, the method further includes: the second network equipment receives the first response from the first network equipment, and determines whether the first network equipment successfully adds the network slice subnet instance to the network slice instance or deletes the network slice subnet instance from the network slice instance according to the first response; the first response is to indicate whether the first network device successfully added or removed the network-slice subnet instance to or from the network-slice instance.

In a third aspect, a method for modifying a network slice instance is provided, the method comprising: the first network equipment receives a second request from second network equipment, wherein the second request is used for requesting the first network equipment to create a network slice subnet instance, and the second request comprises related requirements of the network slice subnet; the first network equipment creates a network slice subnet example according to the related requirements of the network slice subnet; the first network equipment sends the identifier of the network slice subnet instance to the second network equipment; the first network equipment receives a third request from the second network equipment, wherein the third request comprises an identifier of a network slice instance, an identifier of a network slice subnet instance and indication information, and the indication information is used for indicating the first network equipment to add the network slice subnet instance to the network slice instance; the first network device adds the network slice subnet instance to the network slice instance according to the third request. In the method provided in the third aspect, the first network device adds the NSSI in the NSI according to the third request sent by the second network device, and the network function provided by the NSI can be changed by adding the NSSI in the NSI, so that the NSI can meet the service requirement or ensure the network performance under the condition that the NSSI is added in the NSI according to the service requirement or the network performance.

In one possible design, adding the network slice subnet instance to the network slice instance corresponds to configuring an identification of the network slice instance into a service endpoint description of the network slice subnet instance identified by the identification of the network slice subnet instance, such that the network slice subnet instance provides services for the network slice instance.

In one possible design, the network slice subnet related requirements include one or more of the following requirements: the method comprises the following steps of service level agreement of the network slice subnet, network key performance indicators of the network slice subnet, the type of the network slice subnet, the service quality of the network slice subnet, the network topology of the network slice subnet, the resource requirement of the network slice subnet and the related requirement of the network function of the network slice subnet.

In one possible design, after the first network device adds the network-slice subnet instance to the network-slice instance according to the third request, the method further includes: the first network device sends a second response to the second network device, the second response indicating whether the first network device successfully added the network-slice subnet instance to the network-slice instance.

In a fourth aspect, a method of modifying a network slice instance is provided, the method comprising: the second network equipment determines to modify the network slice instance; the second network equipment sends a second request to the first network equipment, wherein the second request is used for requesting the first network equipment to create a network slice subnet example, and the second request comprises the related requirements of the network slice subnet; the second network device receiving an identification of the network slice subnet instance from the first network device; and the second network equipment sends a third request to the first network equipment, wherein the third request comprises the identification of the network slice instance, the identification of the network slice subnet instance and indication information, and the indication information is used for indicating the first network equipment to add the network slice subnet instance to the network slice instance. In the method provided by the fourth aspect, when it is determined that the NSI needs to be modified, the second network device sends a third request to the first network device, where the third request includes the NSI ID, the NSSI ID, and the indication information, so that the first network device adds the NSSI in the NSI according to the third request, and the network function provided by the NSI can be changed by adding the NSSI in the NSI, and in a case where the NSSI is added in the NSI according to a service requirement or a network performance, the NSI can meet a service requirement or ensure the network performance.

In one possible design, after the second network device sends the third request to the first network device, the method further includes: the second network device receives a second response from the first network device and determines whether the first network device successfully adds the network-slice subnet instance to the network-slice instance according to the second response, the second response indicating whether the first network device successfully adds the network-slice subnet instance to the network-slice instance.

In a fifth aspect, a method for modifying a network slice instance is provided, the method comprising: the first network equipment receives a fourth request from the second network equipment, wherein the fourth request comprises the identification of the network slice example and the related requirements of the network slice subnet, and the fourth request is used for requesting the first network equipment to create the network slice subnet example and add the network slice subnet example into the network slice example; the first network equipment creates a network slice subnet example according to the related requirements of the network slice subnet; the first network equipment adds the network slice subnet instance to the network slice instance; the first network device sends the identifier of the network slice subnet instance to the second network device, so that the second network device determines that the first network device successfully adds the network slice subnet instance identified by the identifier of the network slice subnet instance to the network slice instance. In the method provided by the fifth aspect, the first network device creates an NSSI according to the fourth request sent by the second network device and adds the NSSI to the NSI, the network function provided by the NSI can be changed by adding the NSSI to the NSI, and the NSI can meet the service requirement or guarantee the network performance in the case of adding the NSSI to the NSI according to the service requirement or the network performance. Also, in the case that there is no NSSI in the network that meets the requirements related to the network slice subnet, the process of adding NSSI in an NSI provided by this embodiment can save signaling overhead compared to the process of adding NSSI in an NSI shown in fig. 4 above.

In a sixth aspect, a method of modifying a network slice instance is provided, the method comprising: the second network equipment determines to modify the network slice instance; the second network equipment sends a fourth request to the first network equipment, wherein the fourth request comprises the identification of the network slice example and the related requirements of the network slice subnet, and the fourth request is used for requesting the first network equipment to create the network slice subnet example and adding the network slice subnet example into the network slice example; and the second network equipment receives the identifier of the network slice subnet instance sent by the first network equipment, and determines that the first network equipment successfully adds the network slice subnet instance identified by the identifier of the network slice subnet instance to the network slice instance according to the identifier of the network slice subnet instance. In the method provided by the sixth aspect, when it is determined that the NSI needs to be modified, the second network device sends a fourth request to the first network device, where the fourth request includes the NSI ID and the requirement related to the network slice subnet, so that the first network device creates the NSSI according to the fourth request and adds the NSSI to the NSI, and the network function provided by the NSI can be changed by adding the NSSI to the NSI, and in a case where the NSSI is added to the NSI according to a service requirement or a network performance, the NSI can meet the service requirement or ensure the network performance. Also, in the case that there is no NSSI in the network that meets the requirements related to the network slice subnet, the process of adding NSSI in an NSI provided by this embodiment can save signaling overhead compared to the process of adding NSSI in an NSI shown in fig. 4 above.

In a seventh aspect, an apparatus for modifying a network slice instance is provided, where the apparatus has the function of implementing any one of the methods provided in the first aspect, the third aspect, or the fifth aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions.

In an eighth aspect, there is provided an apparatus for modifying a network slice instance, the apparatus having the functionality to implement any one of the methods provided in the second aspect, the fourth aspect, or the sixth aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions.

In a ninth aspect, an apparatus for modifying a network slice instance is provided, the apparatus comprising: a memory and a processor; the memory is used for storing computer-executable instructions, and the processor executes the computer-executable instructions stored by the memory to cause the apparatus to implement any one of the methods provided by the first aspect, the third aspect or the fifth aspect. The device may be in the form of a chip product.

In a tenth aspect, there is provided an apparatus for modifying a network slice instance, the apparatus comprising: a memory and a processor; the memory is used for storing computer-executable instructions, and the processor executes the computer-executable instructions stored by the memory to cause the apparatus to implement any one of the methods provided by the second aspect, the fourth aspect or the sixth aspect. The device may be in the form of a chip product.

In an eleventh aspect, there is provided a computer-readable storage medium comprising instructions which, when run on a computer, cause the computer to perform any one of the methods provided in the first aspect or the third aspect or the fifth aspect.

In a twelfth aspect, there is provided a computer-readable storage medium comprising instructions which, when run on a computer, cause the computer to perform any of the methods provided by the second or fourth aspects or the sixth aspect.

In a thirteenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform any one of the methods provided in the first or third or fifth aspects above.

In a fourteenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform any one of the methods provided in the second or fourth aspects above.

The technical effects brought by any one of the design manners of the seventh aspect to the fourteenth aspect can be seen in the technical effects brought by different design manners of the first aspect to the sixth aspect, and are not described herein again.

Drawings

Fig. 1 is a schematic composition diagram of a network slice management system according to an embodiment of the present application;

fig. 2 is a schematic hardware structure diagram of a network device according to an embodiment of the present disclosure;

fig. 3 is a flow chart of a method for modifying NSI according to an embodiment of the present application;

fig. 4 is a flow chart of another method for modifying NSI provided by an embodiment of the present application;

fig. 5 is a flowchart of another method for modifying NSI provided by an embodiment of the present application;

fig. 6 is a schematic composition diagram of an apparatus according to an embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Where in the description of the present application, "/" indicates an OR meaning, for example, A/B may indicate A or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the present application, "a plurality" means two or more than two.

In order to facilitate understanding of the embodiments of the present application, concepts related to the present application will be briefly described below.

Network slice (network slice): refers to different logical networks customized according to different service requirements. The network slice can be a complete network comprising a terminal, an access network, a transmission network, a core network and an application server, can provide complete telecommunication service and has certain network capability; the network slice may also be a combination of one or more of the above terminals, access networks, transport networks, core networks, and application servers.

Network slice instance (NSI for short): the instantiation of the network slice is realized, namely the network slice is a real running logic network and can meet certain network characteristics or service requirements. An NSI may provide one or more services. An NSI may be created by a network slice management system, which may create multiple NSIs and manage them simultaneously, e.g., modify, terminate, etc. the multiple NSIs. When multiple NSIs coexist, part of the network resources and network functions may be shared between the NSIs. The NSI may or may not be created from a network slice template. A complete NSI is capable of providing a complete end-to-end network service, and what constitutes the NSI may be a Network Slice Subnet Instance (NSSI) and/or a network function. The network functions may include physical network functions and/or virtual network functions. Hereinafter, the physical network function and/or the virtual network function are collectively referred to as a network function.

NSSI: the NSSI may not need to provide complete end-to-end network services, and may be a set of network functions of the same equipment in the NSI, or may be a set of network functions divided by domains, such as a core network NSSI, an access network NSSI, or a set formed by deployment locations and other manners. The NSSI may be shared by multiple NSIs. The NSSI is provided, and the management of a network slice management system can be facilitated.

An NSI is identified by an NSI identifier (NSI ID). Correspondingly, an NSSI is identified by an NSSI identifier (NSSI ID). For example, the NSI ID and the NSSI ID may be in a digital form, a character form, or a combination form of a digital number and a character, which is not limited in this application embodiment

Illustratively, referring to fig. 1, the network slice management system includes a Communication Service Management Function (CSMF), a Network Slice Management Function (NSMF), and a Network Slice Subnet Management Function (NSSMF). The CSMF is mainly responsible for converting the communication service related requirements of the operator and/or the third party customer into the network slice related requirements, sending the network slice requirements (such as creating, terminating, modifying an NSI request, etc.) to the NSMF through an interface between the CSMF and the NSMF, acquiring the network slice management data (such as performance, fault data, etc.) from the NSMF, generating the management data of the communication service running on the NSI, and receiving the subscription requirements of the operator and/or the third party customer on the network slice management data and/or the management data of the communication service. The NSMF is mainly responsible for receiving the related requirements of the network slice sent by the CSMF, managing the life cycle, performance, fault and the like of the NSI, arranging the composition of the NSI, decomposing the requirements of the NSI into the requirements of each NSSI, and sending NSSI management requests to each NSSMF. The NSSMF is mainly responsible for receiving network slice subnet related requirements sent by the NSMF, managing the NSSI, arranging NSSI components, and the like.

As shown in fig. 2, a schematic diagram of a hardware structure of a network device 20 according to an embodiment of the present disclosure is provided, where the network device 20 includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.

The processor 201 may be a general processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs according to the present disclosure.

The communication bus 202 may include a path that conveys information between the aforementioned components.

The communication interface 204 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet network, an Internet Protocol (IP) network, and the like.

The memory 203 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a Random Access Memory (RAM) or other types of dynamic storage devices that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.

The memory 203 is used for storing application program codes for executing the scheme of the application, and the processor 201 controls the execution. The processor 201 is adapted to execute application program code stored in the memory 203 to implement the methods described hereinafter.

In particular implementations, processor 201 may include one or more CPUs such as CPU0 and CPU1 in fig. 2, for example, as one embodiment.

In particular implementations, network device 20 may include multiple processors, such as processor 201 and processor 208 in fig. 2, for example, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In one embodiment, the network device 20 may further include an output device 205 and an input device 206.

An embodiment of the present application provides a method for modifying an NSI, as shown in fig. 3, the method includes:

301. the second network device determines to modify the NSI.

The second network device may be an NSMF or a device having the function of the NSMF (for example, a device loaded with software of the NSMF). The modification to the NSI may include adding or deleting an NSSI in the NSI. Specifically, adding the NSSI to the NSI may be configuring an NSI ID into a service endpoint description of the NSSI identified by the NSSI ID, so that the NSSI can provide a service for the NSI; deleting an NSSI from an NSI may be deleting an NSI ID from the service endpoint description of the NSSI identified by the NSSI ID so that the NSSI no longer provides service for the NSI.

Optionally, step 301 may include, in specific implementation: the second network device receiving a modification request for the NSI; or the second network device determines to modify the NSI according to the current operation state of the NSI and a preset rule.

Wherein the second network device may receive a modification request for the NSI from a third network device or other network device. The third network device may be a CSMF or a CSMF-enabled device (e.g. a device loaded with CSMF software).

The current operation state of the NSI may include a current load of the NSI, a current CPU utilization rate, and the like, and the preset rule may be that the second network device determines to modify the NSI when the current operation state satisfies a certain condition. For example, the second network device determines to modify the NSI when the current CPU utilization of the NSI is greater than a first preset value. For example, the first preset value may be 80%.

302. The second network device sends a first request to the first network device, and the first network device receives the first request from the second network device.

Wherein, the first request comprises NSI ID, NSSI ID and indication information; the indication information is used to instruct the first network device to add the NSSI to the NSI or to instruct the first network device to delete the NSSI from the NSI. The first network device may be a NSSMF or a device having the functionality of a NSSMF (e.g., a device loaded with the software of a NSSMF).

The indication information may correspond to the NSSI ID or the NSI ID, which is not specifically limited in this embodiment of the application.

Optionally, the first request may include one NSI ID, multiple NSSI IDs, and indication information, where the multiple NSSI IDs may correspond to one indication information, and the indication information may be used to indicate that multiple NSSIs identified by the multiple NSSI IDs are added to an NSI identified by an NSI ID or may be used to indicate that multiple NSSIs identified by multiple NSSI IDs are deleted from an NSI identified by an NSI ID, in this case, table 1 exemplarily shows a correspondence relationship between an NSI ID, an NSSI ID, and indication information, and the first indication information may be used to indicate that NSSI 1, NSSI 2, and NSSI 3 are deleted from NSI 1; in this case, table 2 exemplarily shows a correspondence relationship between the NSI ID, and the indication information, the first indication information may be used to indicate that NSI 1 is deleted from NSI 1, the second indication information may be used to indicate that NSSI 2 is added to NSI 1, and the third indication information may be used to indicate that NSSI 3 is deleted from NSI 1.

TABLE 1

TABLE 2

Optionally, the first request may further include a plurality of NSI IDs, one NSI ID, and indication information, the plurality of NSI IDs may correspond to one indication information, for example, the indication information may be used to indicate that the NSI identified by the NSI ID is deleted from the NSI identified by the NSI ID or the indication information may be used to indicate that the NSI identified by the NSI ID is added to the NSI identified by the NSI ID, in this case, table 3 exemplarily shows a correspondence relationship between the NSI ID, and the indication information, and the first indication information may be used to indicate that the NSI 1 is deleted from the NSI 1, the NSI 2, and the NSI 3; in this case, table 4 exemplarily shows a corresponding relationship between an NSI ID, and indication information, where the first indication information may be used to indicate that NSI 1 is deleted from NSI 1, the second indication information may be used to indicate that NSI 1 is added to NSI 2, and the third indication information may be used to indicate that NSI 3 is deleted from NSI 3.

TABLE 3

TABLE 4

Optionally, the first request may further include multiple NSI IDs, multiple NSSI IDs, and indication information, the NSI IDs and the NSSI IDs may correspond to each other, and the first request may include only one indication information, where the indication information may be used to indicate that the NSSI identified by the NSSI ID is added to the NSI identified by the NSI ID, or indicate that the NSSI identified by the NSSI ID is deleted from the NSI identified by the NSI ID, in this case, table 5 exemplarily shows a correspondence relationship between the NSI ID and the NSSI ID and the indication information, and the first indication information may be used to indicate that NSSI 1 is added to NSI 1, NSSI 2 is added to NSI 2, and NSSI 3 is added to NSI 3; the NSI ID, the NSSI ID, and the indication information may also correspond to one another, in this case, one indication information may be used to indicate that the NSSI identified by the NSSI ID corresponding to the indication information is added to the NSI identified by the NSI ID corresponding to the indication information, or may be used to indicate that the NSSI identified by the NSSI ID corresponding to the indication information is deleted from the NSI identified by the NSI ID corresponding to the indication information, in this case, table 6 exemplarily shows a correspondence relationship between the NSI ID, the NSSI ID, and the indication information, the first indication information may be used to indicate that NSSI 1 is added to NSI 1, the second indication information may be used to indicate that NSSI 2 is added to NSI 2, and the third indication information may be used to indicate that NSSI 3 is deleted from NSI 3. Of course, one NSI ID in the first request may also correspond to multiple NSI IDs, or one NSI ID may correspond to multiple NSI IDs, and in this case, the specific function of the indication information may be referred to above, and is not described herein again.

TABLE 5

TABLE 6

NSI ID	NSSI ID	Indicating information
			1	1	First indication information
2	2	Second indication information
			3	3	Third indication information

303. The first network device adds or deletes the NSSI from the NSI according to the first request.

Specifically, when the indication information is used for indicating the first network device to add the NSSI to the NSI, the first network device adds the NSSI to the NSI according to the first request, and when the indication information is used for indicating the first network device to delete the NSSI from the NSI, the first network device deletes the NSSI from the NSI according to the first request.

Optionally, after step 303, the first network device and the second network device may further perform the following steps: the first network device sends a first response to the second network device, the second network device receives the first response from the first network device, and determines whether the first network device successfully adds the network slice subnet instance to the network slice instance or deletes the network slice subnet instance from the network slice instance according to the first response.

The first response is to indicate whether the first network device successfully added or deleted the NSSI in the NSI. Specifically, the first response may carry indication information indicating whether the first network device successfully adds or deletes the NSSI in the NSI. For example, the indication information may be represented by one bit, and exemplarily, "1" may represent success and "0" may represent failure.

In the method provided by the embodiment of the application, when it is determined that the NSI needs to be modified, the second network device sends the first request to the first network device, where the first request includes the NSI ID, the NSSI ID, and the indication information, the first network device adds or deletes the NSSI in the NSI according to the first request, and can change a network function provided by the NSI by adding or deleting the NSSI in the NSI, and in a case where the NSSI is added or deleted in the NSI according to a service requirement or a network performance, the NSI can satisfy the service requirement or ensure the network performance.

Embodiments of the present application also provide a method for modifying NSI, and the explanation of the content related to the above in the method can be referred to above, as shown in fig. 4, the method includes:

401. the second network device determines to modify the NSI.

The method by which the second network device determines the modification to the NSI may be as described above.

402. And the second network equipment sends a second request to the first network equipment, the first network equipment receives the second request from the second network equipment, the second request is used for requesting the first network equipment to create the NSSI, and the second request comprises the network slice subnet related requirements.

Optionally, before step 402, the method may further include: the second network device determines whether NSSI exists in the network that satisfies the requirements associated with the network slice subnet, and if not, performs step 402.

Specifically, each NSSI may correspond to a capability parameter, and the second network device may determine whether an NSSI meeting the requirements related to the network slice subnet exists in the network according to the capability parameter.

For example, referring to table 7, table 7 shows the corresponding capability parameters for a plurality of NSSIs.

TABLE 7

Illustratively, if the time delay of the network slice subnet related requirement is less than or equal to 5us, the reporting success rate (%) is greater than 60, the issuing success rate (%) is greater than 70, and the type is a massive internet of things, the second network device determines that the NSSI 3 is the NSSI meeting the network slice subnet related requirement. If the time delay of the network slice subnet is less than or equal to 1us, the reporting success rate (%) is greater than 60, the issuing success rate (%) is greater than 70, the type is a massive internet of things, and the second network device determines that no NSSI meeting the network slice subnet related requirements exists in the network because no NSSI meeting the conditions exists in the table 7.

For example, the second network device may determine the network slice subnet related requirements according to a modification request of the NSI received from the third network device or other network devices, may also determine the network slice subnet related requirements according to a current operating state of the NSI, and may also determine the network slice subnet related requirements based on a load balancing principle or a functional requirement of the NSI.

Wherein the network slice subnet related requirements may include one or more of the following requirements: (1) a Service Level Agreement (SLA) of a network slice subnet; (2) a Key Performance Indicator (KPI) of a network slice subnet may specifically include one or more of the following information: latency, coverage, capacity, throughput, reliability, reporting success rate, and issuing success rate. The reporting success rate can refer to the successful sending proportion of the uplink data packet; the sending success rate can refer to the successful sending proportion of the downlink data packet; coverage may refer to the distribution area of the terminal; capacity may refer to the number of terminals that can be accommodated; (3) type of network slice subnet. For example, enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), mass internet of things (MIoT), etc.; (4) QoS for network slice subnets; (5) network topology (network topology) of the network slice subnet; (6) resource requirements (resource requirements) of the network slice subnet; (7) the network function related requirements of the network slice subnet may specifically include one or more of the following information: network function type (type), network function capacity (capacity), network function location (location), network function capabilities (capabilities), and the like.

403. The first network device creates an NSSI according to network slice subnet related requirements.

After step 403, the first network device may generate an NSSI ID for the created NSSI to uniquely identify the NSSI.

404. The first network device sends the NSSI ID to the second network device, which receives the NSSI ID from the first network device.

405. The second network device sends a third request to the first network device, the first network device receives the third request from the second network device, the third request comprises the NSI ID, the NSSI ID and indication information, and the indication information is used for indicating the first network device to add the NSSI to the NSI.

Optionally, the third request may include a plurality of NSI IDs, a plurality of NSSI IDs, and a plurality of indication information, in which case, the corresponding relationship between the NSI ID and/or the NSSI ID and the indication information may be referred to above, and is not described herein again.

406. The first network device adds the NSSI to the NSI according to the third request.

Optionally, after step 406, the first network device and the second network device may further perform the following steps: the first network device sends a second response to the second network device, the second network device receives the second response from the first network device, and determines whether the first network device successfully adds the network slice subnet instance to the network slice instance according to the second response.

The second response is to indicate whether the first network device successfully added the NSSI in the NSI. Specifically, the second response may carry indication information indicating whether the first network device successfully adds the NSSI to the NSI. For example, the indication information may be represented by one bit, and exemplarily, "1" may represent success and "0" may represent failure.

In the method provided by the embodiment of the application, when it is determined that the NSI needs to be modified, the second network device sends a third request to the first network device, where the third request includes the NSI ID, the NSSI ID, and the indication information, the first network device adds the NSSI in the NSI according to the third request, and can change a network function provided by the NSI by adding the NSSI in the NSI, and in a case where the NSSI is added in the NSI according to a service requirement or a network performance, the NSI can meet the service requirement or ensure the network performance.

Embodiments of the present application also provide a method for modifying NSI, where the explanation of the content related to the above may be referred to above, and as shown in fig. 5, the method may include:

501. the second network device determines to modify the NSI.

502. The second network device sends a fourth request to the first network device, the first network device receives the fourth request from the second network device, the fourth request includes the NSI ID and the network slice subnet related requirements, and the fourth request is used for requesting the first network device to create the NSSI and add the NSSI to the NSI.

Optionally, before step 502, the second network device may further determine whether there is an NSSI in the network that meets the requirements related to the network slice subnet, and if not, execute step 502. The determination method can be referred to the above related description, and is not repeated herein.

For the content of the related requirements of the network slice subnet, see the above description.

503. The first network device creates an NSSI according to network slice subnet related requirements.

504. The first network device adds the NSSI to the NSI.

Optionally, the fourth request may include a plurality of network slice subnet related requirements and/or a plurality of NSI IDs, and the first network device may create a plurality of NSSIs according to the plurality of network slice subnet related requirements, and add the plurality of NSSIs to one or more NSIs.

It should be noted that the fourth request may further include indication information, where the indication information may be used to indicate that the first network device adds the created NSSI to the NSI.

505. The first network device sends the NSSI ID to the second network device, the second network device receives the NSSI ID sent by the first network device, and the first network device determines that the NSSI identified by the NSSI ID is successfully added to the NSI according to the NSSI ID.

After the second network device receives the NSSI ID sent by the first network device, the second network device maintains the acquired NSSI ID, and performs other actions as necessary, for example, requests the first network device to add the NSSI identified by the NSSI ID to other NSIs.

Prior to step 505, the first network device may generate an NSSI ID for the created NSSI that uniquely identifies the NSSI.

In the method provided by the embodiment of the application, when it is determined that the NSI needs to be modified, the second network device sends a fourth request to the first network device, where the fourth request includes the NSI ID and the requirements related to the network slice subnet, the first network device creates the NSSI according to the fourth request and adds the NSSI to the NSI, and the network function provided by the NSI can be changed by adding the NSSI to the NSI, and the NSI can meet the service requirement or ensure the network performance under the condition that the NSSI is added to the NSI according to the service requirement or the network performance. Also, in the case that there is no NSSI in the network that meets the requirements related to the network slice subnet, the process of adding NSSI in an NSI provided by this embodiment can save signaling overhead compared to the process of adding NSSI in an NSI shown in fig. 4 above.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. It is understood that the apparatus for modifying NSI includes hardware structures and/or software modules for performing the functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the functional modules of the apparatus for modifying NSI may be divided according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

In case of using an integrated unit, fig. 6 shows a schematic diagram of a possible structure of an apparatus 60 according to the above embodiment, where the apparatus 60 may be a first network device or a second network device, and the apparatus 60 includes a processing unit 601 and a communication unit 602, and may further include a storage unit 603.

When the apparatus 60 is a first network device, the processing unit 601 is configured to control and manage actions of the first network device, for example, the processing unit 601 is configured to support the first network device to execute the actions performed by the first network device in the processes 302 and 303 in fig. 3, the process 402 and 406 in fig. 4, the process 502 and 505 in fig. 5, and/or other processes described in this embodiment. The communication unit 602 is configured to support communication between the first network device and other network entities, for example, communication with the second network device in fig. 3, and the storage unit 603 is configured to store program codes and data of the first network device.

When the apparatus 60 is a second network device, the processing unit 601 is configured to control and manage actions of the second network device, for example, the processing unit 601 is configured to support the second network device to execute the actions performed by the second network device in the processes 301 and 302 in fig. 3, the processes 401, 402, 404, and 405 in fig. 4, the processes 501, 502, and 505 in fig. 5, and/or other processes described in this embodiment. The communication unit 602 is configured to support communication between the second network device and other network entities, for example, communication with the first network device in fig. 3, and the storage unit 603 is configured to store program codes and data of the second network device.

The processing unit 601 may be a processor or a controller, and the communication unit 602 may be a communication interface, a transceiver circuit, and the like, where the communication interface is generally referred to and may include one or more interfaces. The storage unit 603 may be a memory. When the processing unit 601 is a processor, the communication unit 602 is a communication interface, and the storage unit 603 is a memory, the network device shown in fig. 2 may be referred to as an apparatus according to an embodiment of the present application. When the first network device is shown in fig. 2, the processor 201 is configured to control and manage the action of the first network device, for example, the processor 201 is configured to support the first network device to execute the actions performed by the first network device in the processes 302 and 303 in fig. 3, the process 402 and 406 in fig. 4, the process 502 and 505 in fig. 5, and/or other processes described in this embodiment. When fig. 2 shows a second network device, the processor 201 is configured to control and manage actions of the second network device, for example, the processor 201 is configured to support the second network device to execute the actions performed by the second network device in the processes 301 and 302 in fig. 3, the processes 401, 402, 404, and 405 in fig. 4, the processes 501, 502, and 505 in fig. 5, and/or other processes described in this embodiment of the present application.

Embodiments of the present application also provide a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the above-mentioned method.

Embodiments of the present application also provide a computer program product containing instructions which, when run on a computer, cause the computer to perform the above method.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated upon loading and execution of computer program instructions on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or can comprise one or more data storage devices, such as a server, a data center, etc., that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method of modifying a network slice instance, the method comprising:

the method comprises the steps that a first network device receives a first request from a second network device, wherein the first request comprises identification of a network slice instance, identification of a network slice subnet instance and indication information; the indication information is used for indicating the first network device to add the network slice subnet instance to the network slice instance or indicating the first network device to delete the network slice subnet instance from the network slice instance; the first network device is a network slice subnet management function NSSMF, and the second network device is a network slice management function NSMF;

the first network device adding the network slice subnet instance to the network slice instance according to the first request or deleting the network slice subnet instance from the network slice instance according to the first request;

adding the network slice subnet instance to the service endpoint description of the network slice subnet instance corresponding to the configuration of the identity of the network slice instance into the network slice subnet instance identified by the identity of the network slice subnet instance, such that the network slice subnet instance provides services for the network slice instance; deleting the network slice subnet instance from the network slice instance corresponds to deleting the identification of the network slice instance from the service endpoint description for the network slice subnet instance identified by the identification of the network slice subnet instance such that the network slice subnet instance no longer provides service for the network slice instance.

2. A method of modifying a network slice instance, the method comprising:

the second network equipment determines to modify the network slice instance;

the second network equipment sends a first request to the first network equipment, wherein the first request comprises the identifier of the network slice instance, the identifier of the network slice subnet instance and indication information; the indication information is used for indicating the first network device to add the network slice subnet instance to the network slice instance or indicating the first network device to delete the network slice subnet instance from the network slice instance; the first network device is a network slice subnet management function NSSMF, and the second network device is a network slice management function NSMF;

3. The method of claim 2, wherein the second network device determining to modify the network slice instance comprises:

the second network device receiving a modification request for the network slice instance; or the second network equipment determines to modify the network slice instance according to the current running state of the network slice instance and a preset rule.

4. An apparatus for modifying a network slice instance, the apparatus comprising:

a transceiving unit, configured to receive a first request from a second network device, where the first request includes an identifier of a network slice instance, an identifier of a network slice subnet instance, and indication information; the indication information is for instructing the apparatus to add the network slice subnet instance to the network slice instance or for instructing the apparatus to delete the network slice subnet instance from the network slice instance; the second network device is a device of a network slice management function NSMF;

a processing unit for adding the network slice subnet instance to the network slice instance according to the first request or deleting the network slice subnet instance from the network slice instance according to the first request;

5. An apparatus for modifying a network slice instance, the apparatus comprising:

a processing unit to determine to modify a network slice instance;

a transceiving unit, configured to send a first request to a first network device, where the first request includes an identifier of the network slice instance, an identifier of a network slice subnet instance, and indication information; the indication information is used for indicating the first network device to add the network slice subnet instance to the network slice instance or indicating the first network device to delete the network slice subnet instance from the network slice instance; the first network equipment is a network slice subnet management function NSSMF;

6. The apparatus according to claim 5, wherein the processing unit is specifically configured to:

receiving, by the transceiver unit, a modification request for the network slice instance; or, determining to modify the network slice instance according to the current running state of the network slice instance and a preset rule.

7. An apparatus for modifying a network slice instance, the apparatus comprising: a memory and a processor;

the memory is for storing computer-executable instructions, the processor executing the computer-executable instructions stored by the memory to cause the apparatus to implement the method of claim 1.

8. An apparatus for modifying a network slice instance, the apparatus comprising: a memory and a processor;

the memory is to store computer-executable instructions, which the processor executes to cause the apparatus to implement the method of any one of claims 2-3.