CN109586939B

CN109586939B - Network adjustment conflict resolution method, equipment and system

Info

Publication number: CN109586939B
Application number: CN201710909699.7A
Authority: CN
Inventors: 方海鹏
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-09-29
Filing date: 2017-09-29
Publication date: 2021-03-05
Anticipated expiration: 2037-09-29
Also published as: CN109586939A; WO2019062591A1

Abstract

The embodiment of the application provides a method, a device and a system for solving network adjustment conflict, which can solve the conflict problem when an NSMF entity performs closed-loop adjustment on NSI and an NSSMF entity performs closed-loop adjustment on NSSI. The method comprises the following steps: the network slice management function NSMF entity determines that a first closed-loop adjustment conflicts with a second closed-loop adjustment, wherein the first closed-loop adjustment is a closed-loop adjustment performed by the first sub-network slice management function NSSMF entity on a first sub-network slice instance NSSI in the network slice instance NSI; the second closed-loop adjustment is a closed-loop adjustment of the NSI by the NSMF entity; the NSMF entity rejects the first closed-loop adjustment or the second closed-loop adjustment.

Description

Network adjustment conflict resolution method, equipment and system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, a device, and a system for solving a network adjustment conflict.

Background

A network slice (network slice) is a logically isolated network for supporting specific network capabilities and network characteristics, and may be an end-to-end (E2E) network including the entire network, or a part of network functions may be shared among multiple network slices, which is a key technology for meeting the requirements of the fifth generation (5G) mobile communication technology for network differentiation proposed by the third generation partnership project (3 GPP). Generally, the network characteristics of different network slices are different, and the network slices are required to be isolated from each other and not influenced by each other. Network slices such as Augmented Reality (AR) or Virtual Reality (VR) traffic require large bandwidth, low latency traffic; the network slice of the internet of things (IOT) service requires to support mass terminal access, but has a small bandwidth and no requirement for delay.

As shown in fig. 1, the management architecture for network slices defined in the current 3GPP standard includes a Network Slice Management Function (NSMF) entity, a directory (catalog), a repository (repository), and a sub-network slice management function (NSSMF) entity. The NSMF entity is mainly responsible for creating a Network Slice Instance (NSI) and managing a life cycle, and in the operation process of the NSI, the NSMF entity can also monitor the operation state of the NSI, and when the NSI cannot meet a Service Level Agreement (SLA) of a user in the operation process, the NSMF entity can also perform closed-loop adjustment on the NSI according to input information of the user or strategy information configured in advance, such as configuration modification, slice Topology (TOPO) change and the like, so as to meet the SLA requirement of the user. The NSSMF entity is mainly responsible for creating and managing a subnet slice instance (NSSI) according to a subnet slice requirement issued by the NSMF entity. In addition, the NSSMF entity may also monitor the operation state of the NSSI, and when the NSSI cannot meet the SLA of the user during the operation process, the NSSMF entity may also perform closed-loop adjustment on the NSSI according to the input information of the user or a policy configured in advance. The directory is mainly used for storing a Network Slice Template (NST) and a sub-network slice template (NSST); the repository is primarily used to store instantiation information for NSIs and NSSIs. As shown in fig. 1, a slice template + a slice order of a customer may be deployed through a network slice management system to a set of slice instances available to the customer.

However, since the NSI is composed of one or more NSSIs, that is, the NSMF entity performs the closed-loop adjustment on the NSI actually performs the closed-loop adjustment on one or more NSSIs in the NSI, the closed-loop adjustment on the NSI by the NSMF entity and the closed-loop adjustment on the NSSI by the NSSMF entity may occur simultaneously, thereby causing the closed-loop adjustment conflict. How to solve the closed-loop adjustment conflict problem is not a relevant solution at present.

Disclosure of Invention

The embodiment of the application provides a method, a device and a system for solving network adjustment conflict, which can solve the conflict problem when an NSMF entity performs closed-loop adjustment on NSI and an NSSMF entity performs closed-loop adjustment on NSSI.

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 network adjustment conflict resolution is provided, where the method includes: the network slice management function NSMF entity determines that a first closed-loop adjustment conflicts with a second closed-loop adjustment, wherein the first closed-loop adjustment is a closed-loop adjustment performed by the first sub-network slice management function NSSMF entity on a first sub-network slice instance NSSI in the network slice instance NSI; the second closed-loop adjustment is a closed-loop adjustment of the NSI by the NSMF entity; the NSMF entity rejects the first closed-loop adjustment or the second closed-loop adjustment. Based on the network adjustment conflict solution method provided by the embodiment of the application, after determining that the closed-loop adjustment performed on the NSI by the NSMF entity conflicts with the closed-loop adjustment performed on the NSSI by the NSSMF entity, the NSMF entity can refuse one of the closed-loop adjustments, so that the conflict problem when the NSMF entity performs the closed-loop adjustment on the NSI and the NSSMF entity performs the closed-loop adjustment on the NSSI can be solved.

Optionally, before the NSMF entity determines that the first closed-loop adjustment conflicts with the second closed-loop adjustment, the method further includes: the NSMF entity determines that the first closed-loop adjustment is required; the NSMF entity refuses to perform the first closed-loop adjustment or the second closed-loop adjustment, including: the NSMF entity refuses to make this first closed loop adjustment.

Optionally, the NSMF entity determines that the first closed-loop adjustment is required, including: the NSMF entity receives an adjustment request message from the first NSSMF entity, the adjustment request message requesting that the first closed-loop adjustment be performed. Based on this scheme, the NSMF entity may determine that a first closed-loop adjustment is needed.

Optionally, the NSMF entity refuses to perform the first closed-loop adjustment, including: the NSMF entity sends an adjustment reject message to the first NSSMF entity, the adjustment reject message instructing the first NSSMF entity to forgo closed-loop adjustment of the first NSSI. Based on this scheme, the NSMF entity may refuse to make this first closed-loop adjustment.

Optionally, the method further includes: the NSMF entity determines that the first closed-loop adjustment is not in conflict with the second closed-loop adjustment; the NSMF entity sends an adjustment allowing message to the first NSSMF entity, wherein the adjustment allowing message is used for indicating that the first NSSMF entity is allowed to carry out closed-loop adjustment on the first NSSI; the NSMF entity receiving an adjustment proceed message from the first NSSMF entity, the adjustment proceed message indicating that the first closed loop adjustment is in progress; the NSMF entity receives an adjustment end message from the first NSSMF entity, the adjustment end message indicating that the first closed loop adjustment is ended. Based on the scheme, the first closed-loop adjustment can be completed when the first closed-loop adjustment is not in conflict with the second closed-loop adjustment.

Optionally, before the NSMF entity determines that the first closed-loop adjustment conflicts with the second closed-loop adjustment, the method further includes: the NSMF entity determines that the second closed-loop adjustment is required; the NSMF entity refuses to perform the first closed-loop adjustment or the second closed-loop adjustment, including: the NSMF entity refuses to make this second closed loop adjustment.

Optionally, the NSMF entity determines that the second closed-loop adjustment is required, including: the NSMF entity receives an adjustment request message from the client equipment, wherein the adjustment request message is used for requesting to carry out the second closed loop adjustment; or, the NSMF entity determines that the second closed-loop adjustment is required according to a preset policy. Based on this scheme, the NSMF entity may determine that this second closed-loop adjustment needs to be made.

Optionally, the NSMF entity refuses to perform the second closed-loop adjustment, including: the NSMF entity foregoes closed-loop tuning of the NSI. Based on this scheme, the NSMF entity may refuse to make this second closed-loop adjustment.

Optionally, the method further includes: the NSMF entity determines that the second closed-loop adjustment does not conflict with the closed-loop adjustments of all NSSIs in the NSI; the NSMF entity decomposes the adjustment requirement of the second closed-loop adjustment to obtain at least one adjustment requirement, wherein the at least one adjustment requirement comprises the requirement that the first NSSI in the NSI needs to be subjected to closed-loop adjustment; the NSMF entity sends an adjustment request message to the first NSSMF entity, wherein the adjustment request message is used for requesting the first NSSMF entity to perform the first closed-loop adjustment on the first NSSI; the NSMF entity receiving a first adjustment proceed message from the first NSSMF entity, the first adjustment proceed message indicating that the first closed loop adjustment is in progress; the NSMF entity receives a first adjustment end message from the first NSSMF entity, the first adjustment end message indicating that the first closed-loop adjustment is ended. Based on the scheme, the first closed-loop adjustment can be completed when the second closed-loop adjustment does not conflict with the closed-loop adjustment of all NSSIs in the NSI.

Optionally, the at least one adjustment requirement further includes an adjustment requirement that the second NSSI in the NSI does not need to perform closed-loop adjustment; the method further comprises the following steps: the NSMF entity sends a second adjustment proceeding message to a second NSSMF entity, wherein the second adjustment proceeding message is used for indicating that the second closed loop adjustment is in progress; after the NSSI that needs to perform the closed-loop adjustment in the NSI completes all closed-loop adjustments, the NSMF entity sends a second adjustment completion message to the second NSSMF entity, where the second adjustment completion message is used to indicate that the second closed-loop adjustment is completed. Based on this scheme, the second NSSMF entity may learn the status of the second closed loop adjustment.

Optionally, before the NSMF entity determines that the first closed-loop adjustment conflicts with the second closed-loop adjustment, the method further includes: the NSMF entity determines that the first closed-loop adjustment and the second closed-loop adjustment are required; the NSMF entity refuses to perform the first closed-loop adjustment or the second closed-loop adjustment, including: the NSMF entity refuses to perform the second closed-loop adjustment if the priority of the first closed-loop adjustment is higher than that of the second closed-loop adjustment; the NSMF entity rejects the first closed-loop adjustment if the priority of the first closed-loop adjustment is lower than the priority of the second closed-loop adjustment.

In a second aspect, a method for network adjustment conflict resolution is provided, the method comprising: a first sub-network slice management function NSSMF entity determines that a first closed loop adjustment needs to be performed on a first sub-network slice instance NSSI in a network slice instance NSI; a first NSSMF entity acquires the current closed-loop adjustment state of the NSI; if the current closed-loop adjustment state of the NSI is the closed-loop adjustment, the first NSSMF entity refuses to perform the first closed-loop adjustment; if the current closed-loop adjustment status of the NSI is not closed-loop adjustment, the first NSSMF entity performs the first closed-loop adjustment. Based on the network adjustment conflict solution method provided by the embodiment of the application, after the NSSMF entity determines that the NSSI needs to be closed-loop adjusted, if it is known that the current closed-loop adjustment state of the NSI is performing closed-loop adjustment, the NSSI is rejected from being closed-loop adjusted, and if it is known that the current closed-loop adjustment state of the NSI is not performing closed-loop adjustment, the NSSI is closed-loop adjusted, so that the conflict problem when the NSMF entity performs closed-loop adjustment on the NSI and when the NSSMF entity performs closed-loop adjustment on the NSSI can be solved.

Optionally, the acquiring, by the first NSSMF entity, the current closed-loop adjustment state of the NSI includes: a first NSSMF entity subscribes a closed-loop adjustment state change event of the NSI to a database entity; in the event that the closed-loop adjustment status of the NSI changes, the first NSSMF entity receives a first change notification from the database entity, the first change notification indicating a current closed-loop adjustment status of the NSI. Based on this scheme, the first NSSMF entity may obtain the current closed-loop adjustment state for the NSI.

Optionally, after the first NSSMF entity performs the first closed-loop adjustment, the method further includes: the first NSSMF entity sends a second change notification to the database entity, the second change notification indicating that the current closed-loop adjustment status of the first NSSI is closed-loop adjustment in progress. Based on this scheme, the database entity may obtain the status of the first closed loop adjustment.

Optionally, the method further includes: during the first closed-loop adjustment by the first NSSMF entity, the first NSSMF entity receiving a third change notification from the database entity, the third change notification indicating that the current closed-loop adjustment status of the NSI is performing closed-loop adjustment; if the priority of the first closed-loop adjustment is higher than the priority of a second closed-loop adjustment, the first NSSMF entity continues to perform the first closed-loop adjustment, wherein the second closed-loop adjustment is the closed-loop adjustment performed by the NSMF entity on the NSI; if the priority of the first closed-loop adjustment is lower than the priority of the second closed-loop adjustment, the first NSSMF entity abstains from performing the first closed-loop adjustment. That is, when the first closed-loop adjustment conflicts with the second closed-loop adjustment, the first NSSMF entity may select to continue the first closed-loop adjustment or to abandon the first closed-loop adjustment according to the priority of the closed-loop adjustment, so that the conflict problem between the NSMF entity performing the closed-loop adjustment on the NSI and the NSSMF entity performing the closed-loop adjustment on the NSSI may be solved.

In a third aspect, a method for network adjustment conflict resolution is provided, where the method includes: a network slice management function NSMF entity determines that a second closed-loop adjustment needs to be carried out on a network slice instance NSI; the NSMF entity acquires the current closed-loop adjustment states of all sub-network slice instances NSSI in the NSI; if the current closed-loop adjustment state of the NSSI exists in the current closed-loop adjustment states of all the NSSIs, the NSMF entity refuses to perform the second closed-loop adjustment; if the current closed-loop adjustment states of all the NSSIs are not closed-loop adjusted, the NSMF entity performs the second closed-loop adjustment. Based on the network adjustment conflict solution method provided by the embodiment of the application, after the NSMF entity determines that the NSI needs to be subjected to closed-loop adjustment, if it is known that the current closed-loop adjustment state of the NSSI in the current closed-loop adjustment states of all the NSSIs in the NSI is the closed-loop adjustment, the NSI is rejected from being subjected to closed-loop adjustment, and if it is known that the current closed-loop adjustment states of all the NSSIs in the NSI are not subjected to closed-loop adjustment, the NSI is subjected to closed-loop adjustment, so that the conflict problem between closed-loop adjustment of the NSI by the NSMF entity and closed-loop adjustment of the NSSI by the NSSMF entity can be solved.

Optionally, the first NSSI is included in the all NSSIs; the NSMF entity obtains the current closed-loop adjustment status of all NSSIs in the NSI, including: the NSMF entity subscribes the closed-loop adjustment state change event of the first NSSI to the database entity; in the event that the closed-loop adjustment status of the first NSSI changes, the NSMF entity receives a first change notification from the database entity, the first change notification indicating a current closed-loop adjustment status of the first NSSI. Based on this scheme, the NSMF entity can obtain the current closed-loop adjustment status of all NSSIs in the NSI.

Optionally, after the NSMF entity performs the second closed-loop adjustment, the method further includes: the NSMF entity sends a second change notification to the database entity, the second change notification indicating that the current closed-loop adjustment state of the NSI is in closed-loop adjustment. Based on this scheme, the database entity may obtain the status of the second closed loop adjustment.

Optionally, the method further includes: during the NSMF performing the second closed-loop adjustment, the NSMF receiving a third change notification from the database entity, the third change notification indicating that the current closed-loop adjustment status of the first NSSI is performing closed-loop adjustment; if the priority of the second closed-loop adjustment is higher than the priority of the first closed-loop adjustment, the NSMF entity continues to perform the second closed-loop adjustment, wherein the first closed-loop adjustment is the closed-loop adjustment of the first NSSMF entity to the first NSSI; if the priority of the second closed-loop adjustment is lower than the priority of the first closed-loop adjustment, the NSMF entity abandons the second closed-loop adjustment. That is, when the first closed-loop adjustment conflicts with the second closed-loop adjustment, the NSMF entity may select to continue the second closed-loop adjustment or abandon the second closed-loop adjustment according to the priority of the closed-loop adjustment, so that the problem of conflict between the NSMF entity performing the closed-loop adjustment on the NSI and the NSSMF entity performing the closed-loop adjustment on the NSSI may be solved.

In a fourth aspect, there is provided an NSMF entity having the functionality to implement the method of the first or third 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 modules corresponding to the functions described above.

In a fifth aspect, there is provided a NSMF entity comprising: a processor and a memory; the memory is configured to store computer executable instructions, and when the NSMF entity runs, the processor executes the computer executable instructions stored in the memory, so that the NSMF entity performs the network adjustment conflict resolution method according to any one of the first aspect or the third aspect.

A sixth aspect provides a computer-readable storage medium having stored therein instructions, which when run on a computer, cause the computer to perform the network adjustment conflict solution method of any one of the first or third aspects.

In a seventh aspect, there is provided a computer program product containing instructions which, when run on a computer, enable the computer to perform the network adjustment conflict resolution method of any one of the first or third aspects.

In an eighth aspect, a system on a chip is provided that includes a processor configured to enable a NSMF entity to implement the functions recited in the above aspects, such as determining that a first closed-loop adjustment conflicts with a second closed-loop adjustment. In one possible design, the system-on-chip further includes a memory for storing necessary program instructions and data for the NSMF entity. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

For technical effects brought by any one of the design manners in the fourth aspect to the eighth aspect, reference may be made to technical effects brought by different design manners in the first aspect or the third aspect, and details are not described here.

In a ninth aspect, there is provided a first NSSMF entity having the functionality to implement the method of the second aspect described above. 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 modules corresponding to the functions described above.

In a tenth aspect, there is provided a first NSSMF entity comprising: a processor and a memory; the memory is configured to store computer-executable instructions, and when the first NSSMF entity is running, the processor executes the computer-executable instructions stored in the memory, so as to enable the first NSSMF entity to perform the network adjustment conflict resolution method according to any of the second aspects.

In an eleventh aspect, there is provided a computer-readable storage medium having stored therein instructions, which when run on a computer, enable the computer to execute the network adjustment conflict resolution method of any one of the second aspects.

In a twelfth aspect, there is provided a computer program product containing instructions which, when run on a computer, make the computer perform the network adjustment conflict solution method of any one of the second aspects.

In a thirteenth aspect, a chip system is provided that includes a processor configured to enable a first NSSMF entity to perform the functions recited in the preceding aspects, such as determining that a first closed loop adjustment is required for a first NSSI in an NSI. In one possible design, the system-on-chip further includes a memory for storing necessary program instructions and data for the first NSSMF entity. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

The technical effects brought by any one of the design manners of the ninth aspect to the thirteenth aspect can be referred to the technical effects brought by different design manners of the second aspect, and are not described herein again.

In a fourteenth aspect, a network adjustment conflict resolution system is provided, which includes the above NSMF entity and the first NSSMF entity.

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

Drawings

Fig. 1 is a schematic diagram of a management architecture of a network slice defined in the existing 3GPP standard;

fig. 2 is a schematic diagram illustrating an architecture of a network adjustment conflict resolution system according to an embodiment of the present application;

fig. 3 is a schematic hardware structure diagram of a communication device according to an embodiment of the present application;

fig. 4 is a first flowchart illustrating a network adjustment conflict resolution method according to an embodiment of the present application;

fig. 5 is a second flowchart illustrating a network adjustment conflict resolution method according to an embodiment of the present application;

fig. 6 is a third schematic flowchart of a network adjustment conflict resolution method according to an embodiment of the present application;

fig. 7 is a fourth flowchart illustrating a network adjustment conflict resolution method according to an embodiment of the present application;

fig. 8 is a fifth flowchart illustrating a network adjustment conflict resolution method according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an NSMF entity according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a first NSSMF entity according to an embodiment of the present application.

Detailed Description

To facilitate understanding of the technical solutions of the embodiments of the present application, a brief description of the related art of the present application is first given as follows.

Network slicing: a network slice is a complete, logically isolated network and may consist of 1 or more sub-network slices.

NSI: an NSI consists of one or more NSSIs. Wherein one NSI may support one or more communication services.

NSSI: an NSSI is composed of one or more Network Function (NF) entities.

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. Also, in the description of the present application, "a plurality" means two or more than two unless otherwise specified. In addition, in order to facilitate clear description of technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items having substantially the same functions and actions. Those skilled in the art will appreciate that the words "first," "second," and the like do not limit the number or order of execution.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

Fig. 2 is a schematic structural diagram of a network adjustment conflict resolution system 20 according to an embodiment of the present application. The network adjustment conflict resolution system 20 includes an NSMF entity 201 and at least one NSSMF entity 202. The at least one NSSMF entity 202 may include a first NSSMF entity 202a, a second NSSMF entity 202b, a third NSSMF entity 202c, … …, and so on. The interaction between the NSMF entity 201 and the first NSSMF entity 202a is described as an example.

The NSMF entity 201 is configured to determine that a first closed-loop adjustment conflicts with a second closed-loop adjustment, where the first closed-loop adjustment is performed by the first NSSMF entity 202a on a first NSSI in the NSI; this second closed-loop adjustment is a closed-loop adjustment of the NSI by the NSMF entity.

The NSMF entity 201 is further configured to reject the first closed-loop adjustment or the second closed-loop adjustment.

Based on the network adjustment conflict solution system provided by the embodiment of the application, after determining that the closed-loop adjustment performed on the NSI by the NSMF entity conflicts with the closed-loop adjustment performed on the NSSI by the NSSMF entity, the NSMF entity may refuse one of the closed-loop adjustments, so that the conflict problem when the NSMF entity performs the closed-loop adjustment on the NSI and the NSSMF entity performs the closed-loop adjustment on the NSSI can be solved.

Or, optionally, the first NSSMF entity 202a, is configured to determine that a first closed loop adjustment needs to be performed on a first NSSI in the NSI.

The first NSSMF entity 202a is also configured to obtain a current closed-loop adjustment status of the NSI.

The first NSSMF entity 202a is further configured to refuse to perform the first closed-loop adjustment if the current closed-loop adjustment state of the NSI is the ongoing closed-loop adjustment; and if the current closed-loop adjustment state of the NSI is that closed-loop adjustment is not performed, performing first closed-loop adjustment.

Based on the network adjustment conflict solution system provided by the embodiment of the application, after the NSSMF entity determines that the NSSI needs to be closed-loop adjusted, if it is known that the current closed-loop adjustment state of the NSI is performing closed-loop adjustment, the NSSI is rejected from being closed-loop adjusted, and if it is known that the current closed-loop adjustment state of the NSI is not performing closed-loop adjustment, the NSSI is closed-loop adjusted, so that the conflict problem when the NSMF entity performs closed-loop adjustment on the NSI and when the NSSMF entity performs closed-loop adjustment on the NSSI can be solved.

Or, optionally, the NSMF entity 201, configured to determine that a second closed-loop adjustment of the NSI is required.

The NSMF entity 201 is further configured to obtain the current closed-loop adjustment status of all NSSIs in the NSI.

The NSMF entity 201 is further configured to, if the current closed-loop adjustment state of the NSSI in the current closed-loop adjustment states of all the NSSIs is the ongoing closed-loop adjustment, refuse to perform the second closed-loop adjustment; and if the current closed-loop adjustment states of all the NSSIs are not subjected to closed-loop adjustment, performing second closed-loop adjustment.

Based on the network adjustment conflict solution system provided by the embodiment of the application, after the NSMF entity determines that the NSI needs to be subjected to closed-loop adjustment, if it is known that the current closed-loop adjustment state of the NSSI in the current closed-loop adjustment states of all the NSSIs in the NSI is the closed-loop adjustment, the NSI is rejected from being subjected to closed-loop adjustment, and if it is known that the current closed-loop adjustment states of all the NSSIs in the NSI are not subjected to closed-loop adjustment, the NSI is subjected to closed-loop adjustment, so that the conflict problem between the closed-loop adjustment of the NSI by the NSMF entity and the closed-loop adjustment of the NSSI by the NSSMF entity can be solved.

Optionally, as shown in fig. 2, the network adjustment conflict resolution system 20 may further include a database entity 203. The database entity 203 may store a directory and a warehouse in the management architecture of the network slice shown in fig. 1, which is not particularly limited in this embodiment of the present application.

Optionally, the entities in fig. 2 may communicate directly with each other, or communicate through forwarding of other devices, which is not specifically limited in this embodiment of the present application.

Alternatively, the network adjustment conflict resolution system 20 shown in fig. 2 may be applied to the currently discussed 5G network or other networks in the future, and the embodiment of the present application is not particularly limited thereto.

Optionally, the NSMF entity, the NSSMF entity, the database entity, and the like in the embodiment of the present application are only names, and the names do not limit the entities themselves. In the 5G network and other networks in the future, the network elements or entities corresponding to the NSMF entity, the NSSMF entity and the database entity may also be other names, which is not specifically limited in this embodiment of the present application. For example, the database entity may be replaced by a Home Subscriber Server (HSS), a User Subscription Database (USD), a Unified Data Management (UDM) entity, or the like, which is described herein in a unified manner and will not be described in detail below.

Optionally, the NSMF entity and the NSSMF entity in fig. 2 may be implemented by one entity device, may also be implemented by multiple entity devices together, and may also be a logic function module in one entity device, which is not specifically limited in this embodiment of the present application.

For example, the NSMF entity and the NSSMF entity in fig. 2 may be implemented by the communication device in fig. 3. Fig. 3 is a schematic diagram illustrating a hardware structure of a communication device according to an embodiment of the present application. The communication device 300 includes at least one processor 301, communication lines 302, memory 303, and at least one communication interface 304.

The processor 301 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure.

The communication link 302 may include a path for transmitting information between the aforementioned components.

The communication interface 304 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.

The memory 303 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk 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. The memory may be separate and coupled to the processor via a communication line 302. The memory may also be integral to the processor.

The memory 303 is used for storing computer-executable instructions for executing the present invention, and is controlled by the processor 301. The processor 301 is configured to execute computer-executable instructions stored in the memory 303, so as to implement the network adjustment conflict resolution method provided by the following embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In particular implementations, processor 301 may include one or more CPUs such as CPU0 and CPU1 in fig. 3, for example, as an example.

In particular implementations, communication device 300 may include multiple processors, such as processor 301 and processor 308 in fig. 3, for example, as an example. 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 particular implementations, communication device 300 may also include an output device 305 and an input device 306, as one embodiment. The output device 305 is in communication with the processor 301 and may display information in a variety of ways. For example, the output device 305 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 306 is in communication with the processor 301 and may receive user input in a variety of ways. For example, the input device 306 may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.

The communication device 300 may be a general purpose device or a special purpose device. In a specific implementation, the communication device 300 may be a desktop, a laptop, a web server, a Personal Digital Assistant (PDA), a mobile phone, a tablet, a wireless terminal device, an embedded device, or a device with a similar structure as in fig. 3. The embodiment of the present application does not limit the type of the communication device 300.

The network adjustment conflict resolution method provided by the embodiment of the present application will be specifically described below with reference to fig. 2 and fig. 3.

Taking the example that the network adjustment conflict solution system 20 shown in fig. 2 is applied to a 5G network, and fig. 4 is a network adjustment conflict solution method provided in the embodiment of the present application, where the network adjustment conflict solution method takes an example that a first NSSMF entity sends an adjustment request to an NSMF entity when determining that closed-loop adjustment needs to be performed on a first NSSI, and the NSMF entity performs conflict resolution. Specifically, the method comprises the following steps:

s401, the first NSSMF entity monitors the operation data of the first NSSI in the NSI.

The operation data of the first NSSI may be, for example, performance data, alarm data, fault data, or the like.

S402, when a Key Performance Indicator (KPI) of the operation data of the first NSSI does not meet the requirements of the client SLA, the first NSSMF entity determines that first closed-loop adjustment is required.

Wherein the first closed-loop adjustment is a closed-loop adjustment of the first NSSI by the first NSSMF entity.

Optionally, the first NSSMF entity may determine that the first closed loop adjustment is required according to an adjustment policy set by the NSST. The adjustment policy set by the NSST may be stored in an NSST file, which is not specifically limited in this embodiment of the present application.

For example, the adjustment policy set by NSST may be to start a capacity expansion operation when the CPU resource occupancy of a slice is far greater than a certain preset value.

S403, the first NSSMF entity sends an adjustment message to the NSMF entity. Accordingly, the NSMF entity receives an adjustment request message from the first NSSMF entity. Wherein the adjustment request message is for requesting a first closed loop adjustment.

S404, the NSMF entity determines whether the first closed-loop adjustment and the second closed-loop adjustment conflict.

Wherein the second closed-loop adjustment is a closed-loop adjustment of the NSI by the NSMF entity.

For example, the NSMF entity may determine whether the first closed-loop adjustment and the second closed-loop adjustment conflict based on the following principle.

For example, if the NSMF entity does not currently initiate closed-loop adjustment of the NSI, the NSMF entity may determine that the first closed-loop adjustment and the second closed-loop adjustment do not conflict; if the NSMF entity currently initiates a closed-loop adjustment of the NSI, the NSMF entity may determine that the first closed-loop adjustment and the second closed-loop adjustment conflict.

Alternatively, for example, if the NSMF entity determines that the first closed-loop adjustment is within the time period allowed by the NSMF, the NSMF entity may determine that the first closed-loop adjustment and the second closed-loop adjustment are not in conflict; if the NSMF entity determines that the first closed-loop adjustment is not within the time period allowed by the NSMF, the NSMF entity may determine that the first closed-loop adjustment and the second closed-loop adjustment conflict.

Of course, the above is merely an exemplary list of two specific implementations of the NSMF entity determining the conflict between the first closed-loop adjustment and the second closed-loop adjustment. Of course, the NSMF entity may also determine whether the first closed-loop adjustment and the second closed-loop adjustment conflict based on other manners, which is not specifically limited in this embodiment of the present application.

If the NSMF entity determines that the first closed-loop adjustment and the second closed-loop adjustment conflict, continuing to execute step S405;

if the NSMF entity determines that the first closed-loop adjustment and the second closed-loop adjustment do not conflict, the steps S406 to S409 are continuously performed.

S405, if the NSMF entity determines that the first closed loop adjustment conflicts with the second closed loop adjustment, the NSMF entity sends an adjustment rejection message to the first NSSMF entity. Accordingly, the NSMF entity receives an adjustment reject message from the NSMF entity. Wherein the adjustment reject message is used to instruct the first NSSMF entity to forgo closed-loop adjustment of the first NSSI.

S406, if the NSMF entity determines that the first closed-loop adjustment and the second closed-loop adjustment do not conflict, the NSMF entity sends an adjustment permission message to the first NSSMF entity. Accordingly, the first NSSMF entity receives an adjustment permission message from the NSMF entity. The adjustment permission message indicates that the first NSSMF entity is permitted to perform closed-loop adjustment on the first NSSI.

S407, the first NSSMF entity performs a closed loop adjustment on the first NSSI, that is, the first NSSMF entity performs a first closed loop adjustment.

S408, the first NSSMF entity sends an adjustment progress message to the NSMF entity. Accordingly, the NSMF entity receives an adjustment proceed message from the first NSSMF entity. The adjustment proceeding message is used to indicate that a first closed loop adjustment is in progress.

Optionally, the adjustment proceeding message in this embodiment of the application may carry an identifier of the first NSSI, where the identifier of the first NSSI is used to indicate that the ongoing closed-loop adjustment is the first closed-loop adjustment, and this is not specifically limited in this embodiment of the application.

S409, after the first NSSMF entity completes the adjustment of the first NSSI, the first NSSMF entity sends an adjustment end message to the NSMF entity. Accordingly, the NSMF entity receives an adjustment end message from the first NSSMF entity, the adjustment end message indicating that the first closed-loop adjustment is ended.

Optionally, the adjustment end message in this embodiment of the application may carry an identifier of the first NSSI, where the identifier of the first NSSI is used to indicate that the first closed loop adjustment is ended, and this is not specifically limited in this embodiment of the application.

In the method for resolving a network adjustment conflict provided in the embodiment of the present application, after the NSMF entity receives an adjustment request message for requesting a first closed-loop adjustment from the first NSSMF entity, if the NSMF entity determines that the first closed-loop adjustment and the second closed-loop adjustment conflict, the first closed-loop adjustment is rejected; if the NSMF entity determines that the first closed-loop adjustment and the second closed-loop adjustment do not conflict, the first NSSMF entity is notified to perform the first closed-loop adjustment. Therefore, based on the scheme, the conflict problem between the NSMF entity performing closed-loop adjustment on the NSI and the NSSMF entity performing closed-loop adjustment on the NSSI can be solved.

The actions of the NSMF entity or the first NSSMF entity in steps S401 to S409 may be executed by the processor 301 in the communication device 300 shown in fig. 3 calling the application program code stored in the memory 303, which is not limited in this embodiment of the present invention.

Optionally, taking the example that the network adjustment conflict solution system 20 shown in fig. 2 is applied to a 5G network, and fig. 5 is a network adjustment conflict solution method provided in the embodiment of the present application, where the network adjustment conflict solution method takes the example that an NSMF entity performs conflict solution when the NSMF entity determines that closed-loop adjustment needs to be performed on an NSI. Assuming that the NSI includes a first NSSI and a second NSSI, the first NSSI corresponds to a first NSSMF entity, and the second NSSI corresponds to a second NSSMF entity, the method includes the following steps:

s501, the NSMF entity acquires NSI operation data.

Optionally, in this embodiment of the present application, the NSMF entity may monitor the operation data of the NSI, so as to obtain the operation data of the NSI; the NSMF entity may also obtain the operation data of the NSI after acquiring the operation data of the first NSSI in the NSI from the first NSSMF entity, and after acquiring the operation data of the second NSSI in the NSI from the second NSSMF entity, and integrating and analyzing the operation data of the first NSSI and the operation data of the second NSSI, the operation data of the NSI is obtained, which is not specifically limited in this embodiment of the application.

The operation data in the embodiment of the present application may be, for example, performance data, alarm data, fault data, or the like.

And S502, when the KPI of the operation data of the NSI does not meet the requirement of the client SLA, the NSMF entity determines that a second closed-loop adjustment is required.

Optionally, in this embodiment of the application, the determining, by the NSMF entity, that the second closed-loop adjustment needs to be performed may include:

the NSMF entity receives an adjustment request message from the client device, the adjustment request message requesting that a second closed-loop adjustment be made. The adjustment request message may be initiated by a client through an Uportal interface, which is not specifically limited in this embodiment of the application.

Or, optionally, in this embodiment of the application, the determining, by the NSMF entity, that the second closed-loop adjustment needs to be performed may include:

and the NSMF entity determines that the second closed loop adjustment is required according to a preset strategy. For example, the NSMF entity may determine that the second closed-loop adjustment is required according to an adjustment policy set by the NST. The adjustment policy set by the NST may be stored in the NSMF entity, or may be stored in the database entity, which is not specifically limited in this embodiment of the present application. If the adjustment policy set by the NST is stored in the database entity, the NSMF entity needs to obtain the adjustment policy set by the NST from the database entity, which is not specifically limited in this application.

S503, the NSMF entity obtains the current closed-loop adjustment status of all NSSIs in the NSI.

Optionally, the NSMF entity may locally query the current closed-loop adjustment status of all NSSIs in the NSI; the current closed-loop adjustment state of the first NSSI may also be queried by sending a first query request message to the first NSSMF entity, and the current closed-loop adjustment state of the second NSSI may be queried by sending a second query request message to the second NSSMF entity, which is not specifically limited in this embodiment of the present application.

S504, the NSMF entity determines whether the second closed-loop adjustment conflicts with the closed-loop adjustments of all NSSIs in the NSI.

For example, in the embodiment of the present application, the NSMF entity may determine whether the second closed-loop adjustment conflicts with the closed-loop adjustment of the first NSSI; and the NSMF entity may determine whether the second closed-loop adjustment conflicts with a closed-loop adjustment of the second NSSI.

Assuming that the second closed-loop adjustment conflicts with the first closed-loop adjustment, the NSMF entity performs step S505, wherein the first closed-loop adjustment is a closed-loop adjustment performed by the first NSSMF entity on the first NSSI.

Alternatively, assuming that the second closed-loop adjustment does not conflict with the closed-loop adjustments of all NSSIs in the NSI, the NSMF entity performs steps S506-S512.

For example, assuming that the closed-loop adjustment status of the first NSSI is performing closed-loop adjustment, the NSMF entity may determine that the first closed-loop adjustment and the second closed-loop adjustment conflict; otherwise, the NSMF entity may determine that the first closed-loop adjustment and the second closed-loop adjustment are not in conflict.

S505, if the NSMF entity determines that the second closed-loop adjustment conflicts with the first closed-loop adjustment, the NSMF entity abandons the closed-loop adjustment of the NSI, that is, the NSMF entity abandons the second closed-loop adjustment.

S506, if the second closed-loop adjustment is not in conflict with the closed-loop adjustments of all NSSIs in the NSI, the NSMF entity decomposes the adjustment requirements of the second closed-loop adjustment to obtain at least one adjustment requirement.

Assuming that the at least one adjustment requirement includes a requirement that a first NSSI in the NSI requires closed-loop adjustment and a requirement that a second NSSI in the NSI does not require closed-loop adjustment, the network adjustment conflict solution further includes the following steps:

s507, the NSMF entity sends an adjustment request message to the first NSSMF entity. Accordingly, the first NSSMF entity receives an adjustment request message from the NSMF entity. Wherein the adjustment request message is for requesting the first NSSMF entity to perform a first closed loop adjustment on the first NSSI.

S508, the first NSSMF entity performs a closed loop adjustment on the first NSSI, that is, the first NSSMF entity performs a first closed loop adjustment.

S509, the first NSSMF entity sends a first adjustment proceeding message to the NSMF entity. Accordingly, the NSMF entity receives a first adjustment proceed message from the first NSSMF entity. The first adjustment proceeding message is used to indicate that a first closed loop adjustment is in progress.

S510, the NSMF entity sends a second adjustment proceeding message to the second NSSMF entity. Accordingly, the second NSSMF entity receives the second adjustment proceed message from the NSMF entity. The second adjustment proceeding message is used to indicate that a second closed loop adjustment is in progress.

S511, after the first NSSMF entity completes the adjustment of the first NSSI, the first NSSMF entity sends a first adjustment complete message to the NSMF entity. Accordingly, the NSMF entity receives a first adjustment end message from the first NSSMF entity, the first adjustment end message indicating that the first closed-loop adjustment is ended.

Optionally, the first adjustment end message in this embodiment of the application may carry an identifier of the first NSSI, where the identifier of the first NSSI is used to indicate that the first closed-loop adjustment is ended, and this is not specifically limited in this embodiment of the application.

S512, after the NSSI that needs to perform the closed-loop adjustment in the NSI completes all closed-loop adjustment, the NSMF entity sends a second adjustment completion message to the second NSSMF entity. Accordingly, the second NSSMF entity receives a second adjustment end message from the NSMF entity. Wherein the second adjustment end message is used to indicate that the second closed-loop adjustment is ended.

Optionally, the second adjustment end message in the embodiment of the present application may carry an identifier of an NSI, where the identifier of the NSI is used to indicate that the second closed-loop adjustment is ended, and this is not specifically limited in the embodiment of the present application.

In the network adjustment conflict solution method provided by the embodiment of the application, after the NSMF entity determines that the first closed-loop adjustment conflicts with the second closed-loop adjustment, the first closed-loop adjustment is rejected; if the NSMF entity determines that the second closed-loop adjustment is not in conflict with the closed-loop adjustments of all NSSIs in the NSI, the second closed-loop adjustment is performed. Therefore, based on the scheme, the conflict problem between the NSMF entity performing closed-loop adjustment on the NSI and the NSSMF entity performing closed-loop adjustment on the NSSI can be solved.

The actions of the NSMF entity or the first NSSMF entity or the second NSSMF entity in steps S501 to S512 may be executed by the processor 301 in the communication device 300 shown in fig. 3 calling the application program code stored in the memory 303, which is not limited in this embodiment of the present invention.

Optionally, taking the example that the network adjustment conflict solution system 20 shown in fig. 2 is applied to a 5G network, and fig. 6 is a network adjustment conflict solution method provided in the embodiment of the present application, where the network adjustment conflict solution method takes an example that an NSMF entity determines that the NSI needs to be closed-loop adjusted, and when the first NSSMF entity determines that the first NSSI needs to be closed-loop adjusted, the NSMF entity performs conflict solution. Specifically, the method comprises the following steps:

S601-S603, like S401-S403, refer to the embodiment shown in fig. 4, and are not described herein again.

S604-S605, like S501-S502, may refer to the embodiment shown in fig. 5, and will not be described herein again.

S606, the NSMF entity determines that the first closed loop adjustment conflicts with the second closed loop adjustment.

If the priority of the first closed-loop adjustment is higher than the priority of the second closed-loop adjustment, the NSMF entity continues to perform step S607;

if the priority of the first closed-loop adjustment is lower than the priority of the second closed-loop adjustment, the NSMF entity continues to perform step S607;

s607, if the priority of the first closed-loop adjustment is higher than the priority of the second closed-loop adjustment, the NSMF entity refuses to perform the second closed-loop adjustment.

Meanwhile, the NSMF entity may instruct the first NSSMF entity to perform the first closed-loop adjustment, and the corresponding scheme may refer to the embodiment shown in fig. 4, which is not described herein again.

S608, if the priority of the first closed loop adjustment is lower than the priority of the second closed loop adjustment, the NSMF entity sends an adjustment reject message to the first NSSMF entity. Accordingly, the NSMF entity receives an adjustment reject message from the NSMF entity. Wherein the adjustment reject message is used to instruct the first NSSMF entity to forgo closed-loop adjustment of the first NSSI.

Meanwhile, the NSMF entity may perform the second closed-loop adjustment, and the corresponding scheme may refer to the embodiment shown in fig. 5, which is not described herein again.

In the method for resolving a network adjustment conflict provided in the embodiment of the present application, after the NSMF entity receives an adjustment request message for requesting a first closed-loop adjustment from the first NSSMF entity and determines that a second closed-loop adjustment is required at the same time, the NSMF entity determines that the first closed-loop adjustment and the second closed-loop adjustment conflict. At this time, the NSMF entity abandons the closed-loop adjustment with the lower priority of the closed-loop adjustment according to the priority of the closed-loop adjustment. Therefore, based on the scheme, the conflict problem between the NSMF entity performing closed-loop adjustment on the NSI and the NSSMF entity performing closed-loop adjustment on the NSSI can be solved.

The actions of the NSMF entity or the first NSSMF entity in steps S601 to S608 may be executed by the processor 301 in the communication device 300 shown in fig. 3 calling the application program code stored in the memory 303, which is not limited in this embodiment of the present invention.

Taking the example that the network adjustment conflict solution system 20 shown in fig. 2 is applied to a 5G network, and fig. 7 is a network adjustment conflict solution method provided in the embodiment of the present application, in which after a first NSSMF entity subscribes a closed-loop adjustment state change event of an NSI to a database entity, and an NSMF entity subscribes a closed-loop adjustment state change event of an NSSI in the NSI to the database entity, the first NSSMF entity determines that the closed-loop adjustment of the first NSSI is required. Specifically, the method comprises the following steps:

s701, in the network slice instantiation process, a first NSSMF entity subscribes a closed-loop adjustment state change event of NSI to a database entity.

S702, in the network slice instantiation process, the NSMF entity subscribes closed-loop adjustment state change events of all NSSIs in the NSI to the database entity.

S703 and S501, which may refer to the embodiment shown in fig. 5 specifically, and are not described herein again.

S704-S705, like S401-S402, may refer to the embodiment shown in fig. 4, and will not be described herein again.

S706, the first NSSMF entity obtains the current closed-loop adjustment status of the NSI.

Optionally, the current closed-loop adjustment state of the NSI may be notified to the first NSSMF entity by the database entity through a first change notification when the closed-loop adjustment state of the NSI changes, where the first change notification is used to indicate the current closed-loop adjustment state of the NSI; of course, the current closed-loop adjustment state of the NSI may also be obtained after the first NSSMF entity queries the database entity, which is not specifically limited in this embodiment of the present application.

If the current closed-loop adjustment state of the NSI is the closed-loop adjustment, executing step S707;

alternatively, if the current closed-loop adjustment status of the NSI is that closed-loop adjustment is not performed, steps S708 to S712 are executed.

And S707, if the current closed-loop adjustment state of the NSI is the closed-loop adjustment, the first NSSMF entity abandons the first closed-loop adjustment.

S708, if the current closed-loop adjustment status of the NSI is that closed-loop adjustment is not performed, the first NSSMF entity performs the first closed-loop adjustment.

S709, the first NSSMF entity sends a second change notification to the database entity. Accordingly, the database entity receives a second change notification from the first NSSMF entity. The second change notification is to indicate that the current closed-loop adjustment state of the first NSSI is in closed-loop adjustment.

S710, the database entity sends a second change notification to the NSMF entity. Accordingly, the NSMF entity receives a second change notification from the database entity. The second change notification is to indicate that the current closed-loop adjustment state of the first NSSI is in closed-loop adjustment.

And S711, after the first NSSMF entity completes the closed-loop adjustment of the first NSSI, the first NSSMF entity sends a third change notification to the database entity. Accordingly, the database entity receives a third change notification from the first NSSMF entity. The third change notification is used to indicate that the current closed-loop adjustment status of the first NSSI is closed-loop adjusted.

S712, the database entity sends a third change notification to the NSMF entity. Accordingly, the NSMF entity receives a third change notification from the database entity. The third change notification is used to indicate that the current closed-loop adjustment status of the first NSSI is closed-loop adjusted.

In the method for solving the network adjustment conflict provided in the embodiment of the present application, a first NSSMF entity subscribes to a closed-loop adjustment state change event of an NSI from a database entity, and an NSMF entity subscribes to a closed-loop adjustment state change event of an NSSI in the NSI from the database entity, when the first NSSMF entity determines that a first closed-loop adjustment needs to be performed on the first NSSI, the first NSSMF entity obtains the closed-loop adjustment state of the NSI, and if the closed-loop adjustment state of the NSI is the closed-loop adjustment in progress, the first NSSMF entity rejects the first closed-loop adjustment; otherwise, the first NSSMF entity performs a first closed loop adjustment. Therefore, based on the scheme, the conflict problem between the NSMF entity performing closed-loop adjustment on the NSI and the NSSMF entity performing closed-loop adjustment on the NSSI can be solved.

The actions of the NSMF entity or the first NSSMF entity in steps S701 to S712 may be executed by the processor 301 in the communication device 300 shown in fig. 3 calling the application program code stored in the memory 303, which is not limited in this embodiment of the present invention.

Taking the example that the network adjustment conflict solution system 20 shown in fig. 2 is applied to a 5G network, and fig. 8 is a network adjustment conflict solution method provided in the embodiment of the present application, the network adjustment conflict solution method takes an example that a first NSSMF entity subscribes a closed-loop adjustment state change event of an NSI to a database entity, and after an NSMF entity subscribes the closed-loop adjustment state change event of an NSSI in the NSI to the database entity, the first NSSMF entity and the NSMF entity initiate closed-loop adjustment at the same time. Specifically, the method comprises the following steps:

s801, the NSMF entity sets closed-loop adjustment priority.

S802, the first NSSMF entity sets the closed loop adjustment priority.

In this embodiment of the present application, the NSMF entity and the first NSSMF entity set a unified closed-loop adjustment priority, for example, the unified closed-loop adjustment priority may be a priority of a second closed-loop adjustment that is lower than a priority of a first closed-loop adjustment, where the second closed-loop adjustment is a closed-loop adjustment performed by the NSMF entity on NSI, and the first closed-loop adjustment is a closed-loop adjustment performed by the first NSSMF entity on first NSSI.

S803-S804, like S701-S702, may refer to the embodiment shown in fig. 7, and are not described herein again.

S805 to S809, similar to S501 to S505, may refer to the embodiment shown in fig. 5, and are not described herein again.

S810-S813, like S704-S707, may refer to the embodiment shown in fig. 7, and are not described herein again.

S814-S816, like S708-S710, refer to the embodiment shown in fig. 7, and are not described herein again.

And S817, if the NSMF entity determines that the second closed-loop adjustment is not in conflict with the closed-loop adjustments of all NSSIs in the NSI, the MSMF entity performs the second closed-loop adjustment.

S818, the NSMF entity sends a third change notification to the database entity. Accordingly, the database entity receives a third change notification from the NSMF entity. The third change notification is used to indicate that the current closed-loop adjustment state of the NSI is closed-loop adjustment in progress.

S819, the database entity sends a third change notification to the first NSSMF entity. Accordingly, the first NSSMF entity receives a third change notification from the database entity. The third change notification is used to indicate that the current closed-loop adjustment state of the NSI is closed-loop adjustment in progress.

At this time, the first closed-loop adjustment conflicts with the second closed-loop adjustment. Assuming that the priority of the first closed-loop adjustment is higher than the priority of the second closed-loop adjustment in the embodiment of the present application, the method for resolving the network adjustment conflict further includes the following steps:

s820, the first NSSMF entity determines that the priority of the first closed-loop adjustment is higher than that of the second closed-loop adjustment according to the preset closed-loop adjustment priority, and continues to perform the first closed-loop adjustment.

And S821, the NSMF entity determines that the priority of the first closed-loop adjustment is higher than that of the second closed-loop adjustment according to the preset closed-loop adjustment priority, and abandons the second closed-loop adjustment.

S822, the NSMF entity sends a fourth change notification to the database entity. Accordingly, the database entity receives a fourth change notification from the NSMF entity. The fourth change notification is used to indicate that the current closed-loop adjustment status of the NSI is closed-loop adjustment end.

In the method for solving the network adjustment conflict provided in the embodiment of the present application, a first NSSMF entity subscribes to a closed-loop adjustment state change event of an NSI from a database entity, and an NSMF entity subscribes to a closed-loop adjustment state change event of an NSSI in the NSI from the database entity, when the first NSSMF entity determines that a first closed-loop adjustment needs to be performed on the first NSSI, the first NSSMF entity obtains the closed-loop adjustment state of the NSI, and if the closed-loop adjustment state of the NSI is the closed-loop adjustment in progress, the first NSSMF entity rejects the first closed-loop adjustment; otherwise, the first NSSMF entity performs a first closed loop adjustment. When the NSMF entity determines that the NSI needs to be subjected to second closed-loop adjustment, the NSMF entity acquires closed-loop adjustment states of all NSSIs in the NSI, and if the current closed-loop adjustment state of the NSSI in the current closed-loop adjustment states of all NSSIs is the closed-loop adjustment, the NSMF entity refuses to carry out the second closed-loop adjustment; otherwise, the NSMF entity performs a second closed-loop adjustment. After the NSMF entity and the first NSSMF entity initiate the closed-loop adjustment process simultaneously, the NSMF entity or the first NSSMF entity abandons the closed-loop adjustment with lower priority. Therefore, based on the scheme, the conflict problem between the NSMF entity performing closed-loop adjustment on the NSI and the NSSMF entity performing closed-loop adjustment on the NSSI can be solved.

The actions of the NSMF entity or the first NSSMF entity in steps S801 to S822 above may be executed by the processor 301 in the communication device 300 shown in fig. 3 calling the application program code stored in the memory 303, which is not limited in this embodiment of the present application.

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 to be understood that the NSMF entity and the first NSSMF entity include hardware structures and/or software modules corresponding to perform the respective functions in order to implement 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 NSMF entity and the first NSSMF entity may be divided into functional modules 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.

For example, in a case where the functional modules are divided in an integrated manner, fig. 9 shows a schematic structural diagram of the NSMF entity 90 involved in the above embodiment. The NSMF entity 90 includes a processing module 902. A processing module 902, configured to determine that a first closed-loop adjustment conflicts with a second closed-loop adjustment, where the first closed-loop adjustment is a closed-loop adjustment performed by a first NSSMF entity on a first NSSI in an NSI; the second closed-loop adjustment is a closed-loop adjustment of the NSI by the NSMF entity 90; the processing module 902 is further configured to reject the first closed-loop adjustment or the second closed-loop adjustment.

Optionally, the processing module 902 is further configured to determine that the first closed-loop adjustment needs to be performed before determining that the first closed-loop adjustment conflicts with the second closed-loop adjustment; the processing module 902 is further configured to reject the first closed-loop adjustment or the second closed-loop adjustment, and includes: the first closed loop adjustment is rejected.

Optionally, the processing module 902 determines that the first closed-loop adjustment is required, including: an adjustment request message is received from a first NSSMF entity requesting the first closed loop adjustment.

Optionally, the processing module 902 refuses to perform the first closed-loop adjustment, including: sending an adjustment reject message to the first NSSMF entity, the adjustment reject message instructing the first NSSMF entity to forgo closed-loop adjustment of the first NSSI.

Optionally, as shown in fig. 9, the NSMF entity 90 further includes: a transceiver module 901; a processing module 902 further configured to determine that the first closed-loop adjustment does not conflict with the second closed-loop adjustment; a processing module 902, further configured to send an adjustment allowing message to the first NSSMF entity, where the adjustment allowing message is used to indicate that the first NSSMF entity is allowed to perform closed-loop adjustment on the first NSSI; a transceiver module 901, configured to receive an adjustment proceeding message from the first NSSMF entity, where the adjustment proceeding message is used to indicate that the first closed-loop adjustment is in progress; the transceiver module 901 is further configured to receive an adjustment end message from the first NSSMF entity, where the adjustment end message is used to indicate that the first closed-loop adjustment is ended.

Optionally, the processing module 902 is further configured to determine that the second closed-loop adjustment needs to be performed before determining that the first closed-loop adjustment conflicts with the second closed-loop adjustment; the processing module 902 rejects the first closed-loop adjustment or the second closed-loop adjustment, including: the second closed loop adjustment is rejected.

Optionally, the processing module 902 determines that the second closed-loop adjustment is required, including: receiving an adjustment request message from a client device, the adjustment request message requesting the second closed-loop adjustment; or determining that the second closed loop adjustment is required according to a preset strategy.

Optionally, the processing module 902 refuses to perform the second closed-loop adjustment, including: the closed loop adjustment of the NSI is abandoned.

Optionally, the processing module 902 is further configured to determine that the second closed-loop adjustment does not conflict with closed-loop adjustments of all NSSIs in the NSI; a processing module 902, further configured to decompose an adjustment requirement of the second closed-loop adjustment to obtain at least one adjustment requirement, where the at least one adjustment requirement includes a requirement that the first NSSI in the NSI needs to perform closed-loop adjustment; a transceiver module 901, configured to send an adjustment request message to the first NSSMF entity, where the adjustment request message is used to request the first NSSMF entity to perform the first closed-loop adjustment on the first NSSI; a transceiver module 901, further configured to receive a first adjustment proceeding message from the first NSSMF entity, where the first adjustment proceeding message is used to indicate that the first closed-loop adjustment is in progress; the transceiver module 901 is further configured to receive a first adjustment end message from the first NSSMF entity, where the first adjustment end message is used to indicate that the first closed-loop adjustment is ended.

Optionally, the at least one adjustment requirement further includes an adjustment requirement that the second NSSI in the NSI does not need to perform closed-loop adjustment; a transceiver module 901, further configured to send a second adjustment performing message to the second NSSMF entity, where the second adjustment performing message is used to indicate that the second closed-loop adjustment is in progress; the transceiver module 901 is further configured to send a second adjustment end message to the second NSSMF entity after all the NSSIs that need to perform the closed-loop adjustment in the NSI complete the closed-loop adjustment, where the second adjustment end message is used to indicate that the second closed-loop adjustment is ended.

Optionally, the processing module 902 is further configured to determine that the first closed-loop adjustment and the second closed-loop adjustment are required to be performed before determining that the first closed-loop adjustment conflicts with the second closed-loop adjustment; the processing module 902 rejects the first closed-loop adjustment or the second closed-loop adjustment, including: the priority of the first closed-loop adjustment is higher than that of the second closed-loop adjustment, and the second closed-loop adjustment is refused to be carried out; and if the priority of the first closed-loop adjustment is lower than that of the second closed-loop adjustment, refusing to perform the first closed-loop adjustment.

Optionally, the processing module 902 is configured to determine that a second closed-loop adjustment needs to be performed on the NSI; the processing module 902 is further configured to obtain current closed-loop adjustment states of all NSSIs in the NSI; the processing module 902 is further configured to, if the current closed-loop adjustment state of the NSSI in the current closed-loop adjustment states of all the NSSIs is the ongoing closed-loop adjustment, refuse to perform the second closed-loop adjustment; the processing module 902 is further configured to perform a second closed-loop adjustment if the current closed-loop adjustment states of all the NSSIs are not closed-loop adjustments.

Optionally, the first NSSI is included in all NSSIs; the processing module 902 obtains the current closed-loop adjustment status of all NSSIs in the NSI, including: subscribing to a closed loop adjustment state change event of a first NSSI to a database entity; in the event that the closed-loop adjustment state of the first NSSI changes, a first change notification is received from the database entity, the first change notification indicating a current closed-loop adjustment state of the first NSSI.

Optionally, the transceiver module 901 is configured to send a second change notification to the database entity after the processing module 902 performs the second closed-loop adjustment, where the second change notification is used to indicate that the current closed-loop adjustment state of the NSI is the ongoing closed-loop adjustment.

Optionally, the transceiver module 901 is configured to receive a third change notification from the database entity during the second closed-loop adjustment performed by the NSMF entity 90, where the third change notification is used to indicate that the current closed-loop adjustment state of the first NSSI is the closed-loop adjustment being performed; the processing module 902 is further configured to continue the second closed-loop adjustment if the priority of the second closed-loop adjustment is higher than the priority of the first closed-loop adjustment, where the first closed-loop adjustment is the closed-loop adjustment performed by the first NSSMF entity on the first NSSI; the processing module 902 is further configured to abort performing the second closed-loop adjustment if the priority of the second closed-loop adjustment is lower than the priority of the first closed-loop adjustment.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In the present embodiment, the NSMF entity 90 is represented in a form of dividing each functional module in an integrated manner. A "module" as used herein may refer to an application-specific integrated circuit (ASIC), an electronic circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that provide the described functionality. In a simple embodiment, one skilled in the art will recognize that the NSMF entity 90 may take the form shown in FIG. 3.

For example, processor 301 in fig. 3 may cause NSMF entity 90 to perform the network adjustment conflict resolution method in the above-described method embodiments by calling a computer-executable instruction stored in memory 303.

In particular, the functions/implementation procedures of the transceiver module 901 and the processing module 902 in fig. 9 can be implemented by the processor 301 in fig. 3 calling a computer executing instruction stored in the memory 303. Alternatively, the function/implementation procedure of the processing module 902 in fig. 9 may be implemented by the processor 301 in fig. 3 calling a computer executing instruction stored in the memory 303, and the function/implementation procedure of the transceiver module 901 in fig. 9 may be implemented by the communication interface 304 in fig. 3.

Since the NSMF entity provided in the embodiment of the present application may be used to execute the method for resolving a network adjustment conflict, the technical effect obtained by the NSMF entity may refer to the method embodiment described above, and will not be described herein again.

For example, in a case where the functional modules are divided in an integrated manner, fig. 10 shows a schematic structural diagram of the first NSSMF entity 100 involved in the above embodiment. The first NSSMF entity 100 comprises a processing module 1002. A processing module 1002, configured to determine that a first closed-loop adjustment needs to be performed on a first NSSI in an NSI; the processing module 1002 is further configured to obtain a current closed-loop adjustment state of the NSI; the processing module 1002 is further configured to refuse to perform the first closed-loop adjustment if the current closed-loop adjustment state of the NSI is the ongoing closed-loop adjustment; the processing module 1002 is further configured to perform a first closed-loop adjustment if the current closed-loop adjustment status of the NSI is that the closed-loop adjustment is not performed.

Optionally, the processing module 1002 obtains the current closed-loop adjustment state of the NSI, including: the database entity subscribes a closed loop adjustment state change event of NSI; in the event that the closed-loop adjustment state of the NSI changes, a first change notification is received from the database entity, the first change notification indicating a current closed-loop adjustment state of the NSI.

Optionally, as shown in fig. 10, the first NSSMF entity 100 further includes: a transceiver module 1001; the transceiver module 1001 is configured to send a second change notification to the database entity after the first closed-loop adjustment is performed, where the second change notification is used to indicate that the current closed-loop adjustment status of the first NSSI is the ongoing closed-loop adjustment.

Optionally, the transceiver module 1001 is configured to receive a third change notification from the database entity during the first closed-loop adjustment performed by the first NSSMF entity 100, where the third change notification is used to indicate that the current closed-loop adjustment state of the NSI is the ongoing closed-loop adjustment; the processing module 1002 is further configured to continue the first closed-loop adjustment if the priority of the first closed-loop adjustment is higher than the priority of a second closed-loop adjustment, where the second closed-loop adjustment is a closed-loop adjustment performed on the NSI by the NSMF entity; the processing module 1002 is further configured to abort performing the first closed-loop adjustment if the priority of the first closed-loop adjustment is lower than the priority of the second closed-loop adjustment.

In the present embodiment, the first NSSMF entity 100 is presented in a form of dividing each functional module in an integrated manner. A "module" as used herein may refer to an application-specific integrated circuit (ASIC), an electronic circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that provide the described functionality. In a simple embodiment, one skilled in the art may recognize that the first NSSMF entity 100 may take the form shown in fig. 3.

For example, the processor 301 in fig. 3 may cause the first NSSMF entity 100 to perform the network adjustment conflict resolution method in the above-described method embodiment by calling a computer-executable instruction stored in the memory 303.

Specifically, the functions/implementation procedures of the transceiver module 1001 and the processing module 1002 in fig. 10 can be implemented by the processor 301 in fig. 3 calling a computer executing instruction stored in the memory 303. Alternatively, the function/implementation process of the processing module 1002 in fig. 10 may be implemented by the processor 301 in fig. 3 calling a computer executing instruction stored in the memory 303, and the function/implementation process of the transceiver module 1001 in fig. 10 may be implemented by the communication interface 304 in fig. 3.

Since the first NSSMF entity provided in the embodiment of the present application may be used to execute the method for solving the network adjustment conflict, the technical effect obtained by the NSSMF entity may refer to the method embodiment described above, and will not be described herein again.

In the above embodiment, the NSMF entity 90 and the first NSSMF entity 100 are presented in the form of dividing each functional module in an integrated manner. Of course, in the embodiment of the present application, each function module of the NSMF entity and the first NSSMF entity may also be divided corresponding to each function, which is not specifically limited in the embodiment of the present application.

Optionally, an embodiment of the present application provides a chip system, where the chip system includes a processor, and is configured to support the NSMF entity to implement the network adjustment conflict solution method, for example, determine that the first closed-loop adjustment conflicts with the second closed-loop adjustment. In one possible design, the system-on-chip further includes a memory. The memory is used for storing program instructions and data necessary for the NSMF entity. The chip system may be formed by a chip, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

Optionally, an embodiment of the present application provides a chip system, where the chip system includes a processor, configured to support a first NSSMF entity to implement the above network adjustment conflict solution method, for example, determine that a first closed-loop adjustment needs to be performed on a first NSSI in an NSI. In one possible design, the system-on-chip further includes a memory. The memory is used for storing necessary program instructions and data of the first NSSMF entity. The chip system may be formed by a chip, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

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 for network adjustment conflict resolution, the method comprising:

the network slice management function NSMF entity determines that a first closed-loop adjustment conflicts with a second closed-loop adjustment, wherein the first closed-loop adjustment is a closed-loop adjustment performed by a first sub-network slice management function NSSMF entity on a first sub-network slice instance NSSI in a network slice instance NSI; the second closed-loop adjustment is a closed-loop adjustment of the NSI by the NSMF entity;

the NSMF entity determines that the first closed-loop adjustment and the second closed-loop adjustment are required;

the NSMF entity refusing to make the first closed-loop adjustment or the second closed-loop adjustment includes:

if the priority of the first closed-loop adjustment is higher than the priority of the second closed-loop adjustment, the NSMF entity refuses to perform the second closed-loop adjustment;

if the priority of the first closed-loop adjustment is lower than the priority of the second closed-loop adjustment, the NSMF entity refuses to perform the first closed-loop adjustment;

the NSMF entity refuses to make the first closed-loop adjustment or the second closed-loop adjustment.

2. The method according to claim 1, before the NSMF entity determines that the first closed-loop adjustment conflicts with the second closed-loop adjustment, further comprising:

the NSMF entity determines that the first closed-loop adjustment is required;

the NSMF entity refuses to make the first closed-loop adjustment.

3. The method according to claim 2, wherein the NSMF entity determines that the first closed-loop adjustment is required, and comprises:

the NSMF entity receives an adjustment request message from the first NSSMF entity, wherein the adjustment request message is used for requesting the first closed loop adjustment.

4. The method according to claim 3, wherein the NSMF entity refuses to make the first closed-loop adjustment, comprising:

the NSMF entity sends an adjustment reject message to the first NSSMF entity, where the adjustment reject message is used to instruct the first NSSMF entity to forgo closed-loop adjustment of the first NSSI.

5. The method according to any one of claims 2-4, further comprising:

the NSMF entity determining that the first closed-loop adjustment does not conflict with the second closed-loop adjustment;

the NSMF entity sending an adjustment allowing message to the first NSSMF entity, wherein the adjustment allowing message is used for indicating that the first NSSMF entity is allowed to perform closed-loop adjustment on the first NSSI;

the NSMF entity receiving an adjustment proceed message from the first NSSMF entity, the adjustment proceed message indicating that the first closed loop adjustment is in progress;

the NSMF entity receives an adjustment end message from the first NSSMF entity, wherein the adjustment end message is used for indicating that the first closed loop adjustment is ended.

6. The method according to claim 1, before the NSMF entity determines that the first closed-loop adjustment conflicts with the second closed-loop adjustment, further comprising:

the NSMF entity determines that the second closed-loop adjustment is required;

the NSMF entity refuses to make the second closed-loop adjustment.

7. The method according to claim 6, wherein the NSMF entity determines that the second closed-loop adjustment is required, and includes:

the NSMF entity receives an adjustment request message from a client device, wherein the adjustment request message is used for requesting to perform the second closed-loop adjustment;

or, the NSMF entity determines that the second closed-loop adjustment needs to be performed according to a preset strategy.

8. The method according to claim 7, wherein the NSMF entity refuses to make the second closed-loop adjustment, comprising:

the NSMF entity forgoes closed-loop tuning of the NSI.

9. The method according to any one of claims 6-8, further comprising:

the NSMF entity determining that the second closed-loop adjustment is not in conflict with closed-loop adjustments of all NSSIs in the NSI;

the NSMF entity decomposes the adjustment requirement of the second closed-loop adjustment to obtain at least one adjustment requirement, wherein the at least one adjustment requirement comprises the requirement that the first NSSI in the NSI needs to be subjected to closed-loop adjustment;

the NSMF entity sending an adjustment request message to the first NSSMF entity, the adjustment request message requesting the first NSSMF entity to perform the first closed-loop adjustment on the first NSSI;

the NSMF entity receiving a first adjustment progress message from the first NSSMF entity, the first adjustment progress message indicating that the first closed loop adjustment is in progress;

the NSMF entity receives a first adjustment end message from the first NSSMF entity, wherein the first adjustment end message is used for indicating the end of the first closed loop adjustment.

10. The method according to claim 9, wherein the at least one adjustment requirement further comprises an adjustment requirement that a second NSSI of the NSI does not require closed loop adjustment; the method further comprises the following steps:

the NSMF entity sends a second adjustment proceeding message to a second NSSMF entity, wherein the second adjustment proceeding message is used for indicating that the second closed loop adjustment is in progress;

after all the NSSI closed-loop adjustments that need to be performed in the NSI are completed, the NSMF entity sends a second adjustment completion message to the second NSSMF entity, where the second adjustment completion message is used to indicate that the second closed-loop adjustments are completed.

11. A method for network adjustment conflict resolution, the method comprising:

a first sub-network slice management function NSSMF entity determines that a first closed loop adjustment needs to be performed on a first sub-network slice instance NSSI in a network slice instance NSI;

the first NSSMF entity acquires the current closed-loop adjustment state of the NSI;

if the current closed-loop adjustment state of the NSI is the closed-loop adjustment, the first NSSMF entity refuses to perform the first closed-loop adjustment;

if the current closed-loop adjustment state of the NSI is that closed-loop adjustment is not performed, performing the first closed-loop adjustment by the first NSSMF entity;

during the first closed-loop adjustment by the first NSSMF entity, the first NSSMF entity receiving a third change notification from a database entity, where the third change notification is used to indicate that the current closed-loop adjustment status of the NSI is closed-loop adjustment in progress;

if the priority of the first closed-loop adjustment is higher than the priority of a second closed-loop adjustment, the first NSSMF entity continues to perform the first closed-loop adjustment, wherein the second closed-loop adjustment is performed on the NSI by an NSMF entity;

if the priority of the first closed-loop adjustment is lower than the priority of the second closed-loop adjustment, the first NSSMF entity abandons the first closed-loop adjustment.

12. The method of claim 11, wherein the obtaining, by the first NSSMF entity, the current closed-loop adjustment status of the NSI comprises:

the first NSSMF entity subscribes to the database entity for a closed-loop adjustment state change event of the NSI;

in the event that the closed-loop adjustment status of the NSI changes, the first NSSMF entity receives a first change notification from the database entity, the first change notification indicating a current closed-loop adjustment status of the NSI.

13. The method of claim 12, wherein after the first closed loop adjustment by the first NSSMF entity, further comprising:

the first NSSMF entity sends a second change notification to the database entity, where the second change notification is used to indicate that the current closed-loop adjustment status of the first NSSI is performing closed-loop adjustment.

14. A method for network adjustment conflict resolution, the method comprising:

a network slice management function NSMF entity determines that a second closed-loop adjustment needs to be carried out on a network slice instance NSI;

the NSMF entity acquires the current closed-loop adjustment states of all sub-network slice instances NSSI in the NSI;

if the current closed-loop adjustment state of the NSSI exists in the current closed-loop adjustment states of all the NSSIs, the NSMF entity refuses to perform the second closed-loop adjustment;

if the current closed-loop adjustment states of all the NSSIs are not closed-loop adjustment, the NSMF entity performs the second closed-loop adjustment;

during the second closed-loop adjustment by the NSMF entity, the NSMF entity receives a third change notification from the database entity, where the third change notification is used to indicate that the current closed-loop adjustment status of the first NSSI is the closed-loop adjustment being performed;

if the priority of the second closed-loop adjustment is higher than the priority of the first closed-loop adjustment, the NSMF entity continues to perform the second closed-loop adjustment, where the first closed-loop adjustment is the closed-loop adjustment performed by the first NSSMF entity on the first NSSI;

if the priority of the second closed-loop adjustment is lower than the priority of the first closed-loop adjustment, the NSMF entity abandons the second closed-loop adjustment.

15. The method according to claim 14, wherein the first NSSI is included in the all NSSIs;

the NSMF entity acquires the current closed-loop adjustment states of all NSSIs in the NSI, including:

the NSMF entity subscribes to a closed-loop adjustment state change event of the first NSSI from the database entity;

the NSMF entity receives a first change notification from the database entity indicating a current closed-loop adjustment state of the first NSSI when the closed-loop adjustment state of the first NSSI changes.

16. The method according to claim 15, further comprising, after the NSMF entity performs the second closed-loop adjustment:

and the NSMF entity sends a second change notice to the database entity, wherein the second change notice is used for indicating that the current closed-loop adjustment state of the NSI is closed-loop adjustment.

17. A network slice management function, NSMF, entity, the NSMF entity comprising: a processing module;

the processing module is configured to determine that a first closed-loop adjustment conflicts with a second closed-loop adjustment, where the first closed-loop adjustment is performed by a first sub-network slice management function NSSMF entity on a first sub-network slice instance NSSI in a network slice instance NSI; the second closed-loop adjustment is a closed-loop adjustment of the NSI by the NSMF entity;

the processing module is further configured to refuse to perform the first closed-loop adjustment or the second closed-loop adjustment;

the processing module is further configured to determine that a first closed-loop adjustment and a second closed-loop adjustment are required before determining that the first closed-loop adjustment conflicts with the second closed-loop adjustment;

the processing module refusing to make the first closed-loop adjustment or the second closed-loop adjustment includes:

if the priority of the first closed-loop adjustment is higher than that of the second closed-loop adjustment, refusing to perform the second closed-loop adjustment;

and if the priority of the first closed-loop adjustment is lower than that of the second closed-loop adjustment, refusing to perform the first closed-loop adjustment.

18. The NSMF entity of claim 17, wherein the processing module is further configured to determine that a first closed-loop adjustment is required before determining that the first closed-loop adjustment conflicts with a second closed-loop adjustment;

the processing module is further configured to reject the first closed-loop adjustment or the second closed-loop adjustment, and includes:

rejecting the first closed loop adjustment.

19. The NSMF entity of claim 18, wherein the processing module determines that the first closed-loop adjustment is required, and comprises:

receiving an adjustment request message from the first NSSMF entity, the adjustment request message requesting the first closed loop adjustment.

20. The NSMF entity of claim 19, wherein the processing module refuses to perform the first closed-loop adjustment comprises:

sending an adjustment reject message to the first NSSMF entity, the adjustment reject message being used to instruct the first NSSMF entity to forgo closed-loop adjustment of the first NSSI.

21. The NSMF entity according to any one of claims 18 to 20, further comprising: a transceiver module;

the processing module is further configured to determine that the first closed-loop adjustment does not conflict with the second closed-loop adjustment;

the processing module is further configured to send an adjustment permission message to the first NSSMF entity, where the adjustment permission message is used to indicate that the first NSSMF entity is allowed to perform closed-loop adjustment on the first NSSI;

the transceiver module is configured to receive an adjustment progress message from the first NSSMF entity, where the adjustment progress message is used to indicate that the first closed-loop adjustment is in progress;

the transceiver module is further configured to receive an adjustment end message from the first NSSMF entity, where the adjustment end message is used to indicate that the first closed-loop adjustment is ended.

22. NSMF entity according to claim 17,

the processing module is further configured to determine that a second closed-loop adjustment is required before determining that the first closed-loop adjustment conflicts with the second closed-loop adjustment;

refusing to make the second closed-loop adjustment.

23. The NSMF entity of claim 22, wherein the processing module determines that the second closed-loop adjustment is required, comprising:

receiving an adjustment request message from a client device, the adjustment request message requesting the second closed-loop adjustment; or determining that the second closed loop adjustment is required according to a preset strategy.

24. The NSMF entity of claim 23, wherein the processing module refuses to perform the second closed-loop adjustment, comprising:

forgoing closed loop adjustment of the NSI.

25. The NSMF entity according to any one of claims 22 to 24, further comprising: a transceiver module;

the processing module is further configured to determine that the second closed-loop adjustment does not conflict with closed-loop adjustments of all NSSIs in the NSI;

the processing module is further configured to decompose an adjustment requirement of the second closed-loop adjustment to obtain at least one adjustment requirement, where the at least one adjustment requirement includes a requirement that a first NSSI in the NSI needs to perform closed-loop adjustment;

the transceiver module is configured to send an adjustment request message to the first NSSMF entity, where the adjustment request message is used to request the first NSSMF entity to perform the first closed-loop adjustment on the first NSSI;

the transceiver module is further configured to receive a first adjustment proceeding message from the first NSSMF entity, where the first adjustment proceeding message is used to indicate that the first closed-loop adjustment is in progress;

the transceiver module is further configured to receive a first adjustment end message from the first NSSMF entity, where the first adjustment end message is used to indicate that the first closed-loop adjustment is ended.

26. The NSMF entity of claim 25, wherein the at least one adjustment requirement further comprises an adjustment requirement that a second NSSI in the NSI does not require closed-loop adjustment;

the transceiver module is further configured to send a second adjustment performing message to a second NSSMF entity, where the second adjustment performing message is used to indicate that the second closed-loop adjustment is in progress;

the transceiver module is further configured to send a second adjustment end message to the second NSSMF entity after all closed-loop adjustments of NSSIs that need to be closed-loop adjusted in the NSI are ended, where the second adjustment end message is used to indicate that the second closed-loop adjustments are ended.

27. A first sub-network slice management function, NSSMF, entity, the first NSSMF entity comprising: a processing module;

the processing module is configured to determine that a first closed-loop adjustment needs to be performed on a first sub-network slice instance NSSI in a network slice instance NSI;

the processing module is further configured to obtain a current closed-loop adjustment state of the NSI;

the processing module is further configured to refuse to perform the first closed-loop adjustment if the current closed-loop adjustment state of the NSI is the ongoing closed-loop adjustment;

the processing module is further configured to perform the first closed-loop adjustment if the current closed-loop adjustment state of the NSI is that closed-loop adjustment is not performed;

the first NSSMF entity further comprises: a transceiver module;

the transceiver module is configured to receive a third change notification from a database entity during the first closed-loop adjustment performed by the first NSSMF entity, where the third change notification is used to indicate that a current closed-loop adjustment state of the NSI is performing closed-loop adjustment;

the processing module is further configured to continue performing the first closed-loop adjustment if the priority of the first closed-loop adjustment is higher than the priority of a second closed-loop adjustment, where the second closed-loop adjustment is performed on the NSI by an NSMF entity;

the processing module is further configured to abandon the first closed-loop adjustment if the priority of the first closed-loop adjustment is lower than the priority of the second closed-loop adjustment.

28. The first NSSMF entity of claim 27, wherein the processing module obtains a current closed-loop adjustment status for the NSI, comprising:

subscribing to the database entity for closed-loop regulatory state change events for the NSI;

receiving a first change notification from the database entity in the event that the closed-loop adjustment status of the NSI changes, the first change notification indicating a current closed-loop adjustment status of the NSI.

29. The first NSSMF entity of claim 28, wherein the first NSSMF entity further comprises: a transceiver module;

the transceiver module is configured to send a second change notification to the database entity after the first closed-loop adjustment is performed, where the second change notification is used to indicate that the current closed-loop adjustment state of the first NSSI is the ongoing closed-loop adjustment.

30. A network slice management function, NSMF, entity, the NSMF entity comprising: a processing module;

the processing module is used for determining that a second closed-loop adjustment needs to be performed on the network slice instance NSI;

the processing module is further configured to acquire current closed-loop adjustment states of all sub-network slice instances NSSI in the NSI;

the processing module is further configured to refuse to perform the second closed-loop adjustment if the current closed-loop adjustment state of the NSSI in the current closed-loop adjustment states of all the NSSIs is the ongoing closed-loop adjustment;

the processing module is further configured to perform the second closed-loop adjustment if the current closed-loop adjustment states of all the NSSIs are not closed-loop adjustment;

the NSMF entity further includes: a transceiver module;

the transceiver module is configured to receive a third change notification from the database entity during the second closed-loop adjustment performed by the NSMF entity, where the third change notification is used to indicate that the current closed-loop adjustment state of the first NSSI is the ongoing closed-loop adjustment;

the processing module is further configured to continue performing the second closed-loop adjustment if the priority of the second closed-loop adjustment is higher than the priority of the first closed-loop adjustment, where the first closed-loop adjustment is performed on the first NSSI by the first NSSMF entity;

the processing module is further configured to abandon the second closed-loop adjustment if the priority of the second closed-loop adjustment is lower than the priority of the first closed-loop adjustment.

31. The NSMF entity of claim 30, wherein the first NSSI is included in the all NSSIs;

the processing module acquires the current closed-loop adjustment states of all NSSIs in the NSI, including:

subscribing to the database entity for a closed-loop adjustment state change event for the first NSSI;

receiving a first change notification from the database entity indicating a current closed-loop adjustment state of the first NSSI in the event of a change in the closed-loop adjustment state of the first NSSI.

32. The NSMF entity according to claim 31, further comprising: a transceiver module;

the transceiver module is configured to send a second change notification to the database entity after the processing module performs the second closed-loop adjustment, where the second change notification is used to indicate that the current closed-loop adjustment state of the NSI is performing the closed-loop adjustment.