CN113543157A

CN113543157A - Method and equipment for controlling network resources

Info

Publication number: CN113543157A
Application number: CN202010291102.9A
Authority: CN
Inventors: 张春蕾; 陆晓萍
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-04-14
Filing date: 2020-04-14
Publication date: 2021-10-22
Anticipated expiration: 2040-04-14
Also published as: CN113543157B; WO2021208817A1

Abstract

The embodiment of the application provides a method and equipment for controlling network resources. The management system acquires network requirements; the management system executes any one or more of the following operations according to the network requirement: create new network functions NF, delete created NFs. According to the method, the NF in the network is adaptively adjusted according to the network requirements, so that the utilization rate of network resources can be effectively improved on the premise of meeting the user requirements.

Description

Method and equipment for controlling network resources

Technical Field

The present application relates to the field of communications, and in particular, to a method and apparatus for network resource control.

Background

Networks of the fifth Generation (5th Generation, 5G) communication system are composed of Network Functions (NFs), and different types of NFs can provide different network functions to meet different user requirements. With the continuous development of network functions and diversification of user requirements, the types of NFs in the network will be more and more abundant.

If all types of NFs are deployed in the network, the utilization rate of some types of NFs is low, and even no one uses the NF, so that the resource waste is caused. If only a partial type of NF is deployed in the network, this may result in the network not supporting the functionality of the undeployed type of NF.

When NF is deployed in a network, how to improve the utilization rate of network resources on the premise of meeting the user requirements is an urgent problem to be solved.

Disclosure of Invention

The application provides a method and equipment for controlling network resources, which can improve the utilization rate of the network resources on the premise of meeting the requirements of users by adaptively adjusting NF in a network according to the network requirements.

In a first aspect, a method for network resource control is provided, where the method includes: the management system acquires network requirements; the management system executes any one or more of the following operations according to the network requirement: create new network functions NF, delete created NFs.

Based on the technical scheme, the NF in the network is adaptively adjusted according to the network requirements, so that the utilization rate of network resources can be effectively improved on the premise of meeting the user requirements.

With reference to the first aspect, in some implementations of the first aspect, the acquiring, by the management system, a network requirement includes: the management system receives a creation request message sent by a first NF, wherein the creation request message is used for requesting to create a second NF; wherein, the management system executes any one or more of the following operations according to the network requirement: creating a new NF and deleting the created NF, comprising: the second NF is created according to the creation request message.

With reference to the first aspect, in some implementations of the first aspect, the creating the second NF according to the create request message includes: and under the condition that resources required for creating the second NF are configured in the network, creating the second NF according to the creation request message.

With reference to the first aspect, in some implementations of the first aspect, the creating the second NF according to the create request message includes: and under the condition that the type of the second NF which can be dynamically established and system resources required by the second NF are planned in the network, the second NF is established according to the establishing request message.

With reference to the first aspect, in some implementations of the first aspect, before the receiving the create request message sent from the first NF, the method further includes: receiving a subscription message sent by the first NF, wherein the subscription message is used for requesting the information of the NF; and sending NF list information to the first NF, wherein the NF list information is used for indicating the types of the NF which can be created, and the types of the NF which can be created comprise the type of the second NF.

With reference to the first aspect, in some implementations of the first aspect, after the creating the second NF according to the create request message, the method further includes: sending a first message to the first NF, wherein the first message is used for indicating the attribute information of the second NF successfully created by the management system, and the attribute information of the second NF comprises the type of the second NF and the address of the second NF; or sending a second message to the first NF, wherein the second message is used for indicating that the management system fails to create the second NF.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: acquiring the utilization rate of a third NF established in the network; wherein, the management system executes any one or more of the following operations according to the network requirement: creating a new NF and deleting the created NF, comprising: and deleting the third NF under the condition that the utilization rate of the third NF is lower than a threshold value.

With reference to the first aspect, in some implementations of the first aspect, before the obtaining the utilization rate of the third NF, the method further includes: and sending a query message to the third NF, wherein the query message is used for indicating the management system to periodically acquire the use condition of the third NF.

In a second aspect, a method for network resource control is provided, the method comprising: a first network function NF obtains network requirements; and the first NF sends a creation request message to the management system according to the network requirement, wherein the creation request message is used for requesting to create a second NF.

With reference to the second aspect, in some implementations of the second aspect, the sending, by the first network function NF, a create request message to a management system according to the network requirement includes: and under the condition that the second NF is not established in the current network, the first network function NF sends an establishment request message to a management system according to the network requirement.

With reference to the second aspect, in some implementations of the second aspect, before the first network function NF sends the request message to the management system according to the network requirement, the method further includes: sending a subscription message to the management system, wherein the subscription message is used for requesting information of NF; and receiving NF list information sent by the management system, wherein the NF list information is used for indicating the types of NF which can be created and the types of NF which can be created comprise the type of the second NF.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: receiving a first message sent by the management system, wherein the first message is used for indicating the attribute information of the second NF successfully created by the management system, and the attribute information of the second NF comprises the type of the second NF and the address of the second NF; or receiving a second message sent by the management system, wherein the second message is used for indicating that the management system fails to create the second NF.

In a third aspect, a network device is provided, including: the processing unit is used for acquiring network requirements; the processing unit is further configured to perform any one or more of the following operations according to the network requirement: create new network functions NF, delete created NFs.

With reference to the third aspect, in certain implementations of the third aspect, the network device further includes a transceiver unit, configured to receive a create request message sent from the first NF, where the create request message is used to request to create the second NF; the processing unit is further configured to create the second NF according to the creation request message.

With reference to the third aspect, in some implementations of the third aspect, in a case that a resource required for creating the second NF has been configured in the network, the processing unit is further configured to create the second NF according to the creation request message.

With reference to the third aspect, in some implementations of the third aspect, in a case where the type of the second NF that can be dynamically established and system resources required by the second NF have been planned in the network, the second NF is created according to the creation request message.

With reference to the third aspect, in some implementations of the third aspect, the transceiver unit is further configured to receive a subscription message sent by the first NF, where the subscription message is used to request information of an NF; and the transceiver unit is further configured to send NF list information to the first NF, where the NF list information is used to indicate types of NFs that can be created, and the types of NFs that can be created include the type of the second NF.

With reference to the third aspect, in some implementations of the third aspect, the transceiver unit is further configured to send a first message to the first NF, where the first message is used to indicate that the management system successfully creates the attribute information of the second NF, and the attribute information of the second NF includes a type of the second NF and an address of the second NF; or the transceiver unit is further configured to send a second message to the first NF, where the second message is used to indicate that the management system fails to create the second NF.

With reference to the third aspect, in some implementations of the third aspect, the processing unit is further configured to obtain a utilization rate of a third NF that has been created in the network; the processing unit is further configured to delete the third NF when the utilization rate of the third NF is lower than a threshold value.

With reference to the third aspect, in some implementations of the third aspect, the network device further includes a transceiver unit, configured to send a query message to the third NF, where the query message is used to instruct the management system to periodically acquire the usage of the third NF.

In a fourth aspect, a network device is provided, comprising: the processing unit is used for acquiring network requirements; and the transceiver unit is used for sending a creation request message to the management system according to the network requirement, wherein the creation request message is used for requesting to create the second NF.

With reference to the fourth aspect, in some implementations of the fourth aspect, in a case that it is determined that the second NF is not currently created in the network, the transceiver unit is further configured to send a creation request message to a management system according to the network requirement.

With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to send a subscription message to the management system, where the subscription message is used to request information of the NF; and the transceiver unit is further configured to receive NF list information sent from the management system, where the NF list information is used to indicate types of NFs that can be created, and the types of NFs that can be created include the type of the second NF.

With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to receive a first message sent from the management system, where the first message is used to indicate that the management system successfully creates the attribute information of the second NF, and the attribute information of the second NF includes a type of the second NF and an address of the second NF; or the transceiver unit is further configured to receive a second message sent from the management system, where the second message is used to indicate that the management system fails to create the second NF.

In a fifth aspect, there is provided a network device, the device comprising a memory and a processor,

the memory is configured to store instructions, and the processor is configured to read the instructions stored in the memory, so that the apparatus executes the method of the first aspect and any possible implementation manner of the first aspect.

In a sixth aspect, a network device is provided, which includes a memory for storing instructions and a processor for reading the instructions stored in the memory, so that the apparatus performs the method of the second aspect and any possible implementation manner of the second aspect.

Optionally, the number of the processors is one or more, and the number of the memories is one or more.

Optionally, the memory is integrated with the processor or provided separately from the processor.

In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

In a seventh aspect, a computer-readable storage medium is provided for storing a computer program comprising instructions for performing the method of the first and/or second aspect and any possible implementation manner of the first and/or second aspect.

In an eighth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first and/or second aspect described above and any possible implementation of the first and/or second aspect described above.

In a ninth aspect, a chip is provided, comprising at least one processor and an interface; the at least one processor is configured to invoke and run a computer program to cause the chip to execute the method in the first aspect and/or the second aspect and any possible implementation manner of the first aspect and/or the second aspect.

A tenth aspect provides a communication system comprising the network device of the third aspect and the network device of the fourth aspect, or comprising the network device of the fifth aspect and the network device of the sixth aspect.

Drawings

Fig. 1 is a schematic diagram of a network architecture suitable for the method for controlling network resources provided in the embodiment of the present application.

Fig. 2 is a schematic flow chart diagram of a method 200 for network resource control according to an embodiment of the present application.

Fig. 3 is a schematic flow chart diagram of a method 300 for network resource control according to an embodiment of the present application.

Fig. 4 is a schematic flow chart diagram of a method 400 for network resource control according to an embodiment of the present application.

Fig. 5 is a schematic flow chart diagram of a method 500 for network resource control according to an embodiment of the present application.

Fig. 6 is a schematic flow chart diagram of a method 600 for network resource control according to an embodiment of the present application.

Fig. 7 is a schematic flow chart diagram of a method 700 for network resource control according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of a network device 800 provided by an embodiment of the present application.

Fig. 9 is a schematic block diagram of a network device 900 provided in an embodiment of the present application.

Fig. 10 is a schematic block diagram of a network device 1000 provided in an embodiment of the present application.

Fig. 11 is a schematic block diagram of a network device 1100 provided in an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

In the embodiments of the present application, "a plurality" may be understood as "at least two"; "plurality" is to be understood as "at least two".

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, a fifth Generation (5th Generation, 5G) System or a New Radio Network (NR), future communication systems, and the like.

It should be understood that, in the embodiment of the present application, a specific structure of an execution main body of the method provided in the embodiment of the present application is not particularly limited as long as the execution main body can perform communication according to the method provided in the embodiment of the present application by running a program recorded with a code of the method provided in the embodiment of the present application, for example, the execution main body of the method provided in the embodiment of the present application may be a terminal or a network-side device, or a functional module capable of calling a program and executing the program in the UE or the network-side device.

For the understanding of the embodiments of the present application, an application scenario of the embodiments of the present application will be described in detail with reference to fig. 1.

Fig. 1 is a schematic diagram of a network architecture suitable for the method provided by the embodiment of the present application. As shown, the network architecture may be, for example, a non-roaming (non-roaming) architecture. The network architecture may specifically include the following network elements:

1. user Equipment (UE): may be referred to as a terminal device, terminal, access terminal, subscriber unit, subscriber station, mobile, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G Network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, which are not limited in this embodiment.

2. Access Network (AN): the method provides a network access function for authorized users in a preset area, and can use transmission tunnels with different qualities according to the grade of the users, the service requirements and the like. The access network may be an access network employing different access technologies. There are two types of current radio access technologies: third Generation Partnership Project (3 GPP) access technologies such as the radio access technologies employed in 3G, 4G, 5G or 6G systems and non-third Generation Partnership Project (non-3GPP) access technologies. The 3GPP Access technology refers to an Access technology meeting 3GPP standard specifications, and an Access Network adopting the 3GPP Access technology is referred to as a Radio Access Network (RAN), where an Access Network device in a 5G system is referred to as a next generation Base station (gNB). The non-3GPP access technology refers to an access technology that does not conform to the 3GPP standard specification, for example, an air interface technology represented by an Access Point (AP) in wifi.

An access network that implements an access network function based on a wireless communication technology may be referred to as a Radio Access Network (RAN). The radio access network can manage radio resources, provide access service for the terminal, and further complete the forwarding of control signals and user data between the terminal and the core network.

The Radio Access Network may be, for example, a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) System or a Code Division Multiple Access (CDMA) System, a Base Station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) System, an evolved Base Station (eNB, eNodeB) in an LTE System, a Radio controller in a Cloud Radio Access Network (CRAN) scenario, or the Network device may be a relay Station, an Access point, a vehicle-mounted device, a wearable device, a Network device in a future 5G Network, or a Network device in a future evolved PLMN Network, and the embodiments of the present application are not limited.

3. Access and mobility management function (AMF) entity: the method is mainly used for mobility management, access management, and the like, and can be used for implementing functions other than session management in Mobility Management Entity (MME) functions, such as functions of lawful interception, or access authorization (or authentication), and the like. In the embodiment of the present application, the method and the device can be used for implementing the functions of the access and mobility management network element.

4. Session Management Function (SMF) entity: the method is mainly used for session management, Internet Protocol (IP) address allocation and management of the UE, selection of a termination point of an interface capable of managing a user plane function, policy control or charging function, downlink data notification, and the like. In the embodiment of the present application, the method and the device can be used for implementing the function of the session management network element.

5. User Plane Function (UPF) entity: i.e. a data plane gateway. The method can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, and the like. The user data can be accessed to a Data Network (DN) through the network element. In the embodiment of the application, the method can be used for realizing the function of the user plane gateway.

6. Data Network (DN): for providing a network for transmitting data. Such as a network of carrier services, an Internet network, a third party's service network, etc.

7. Authentication service function (AUSF) entity: the method is mainly used for user authentication and the like.

8. Network open function (NEF) entity: for securely opening services and capabilities, etc. provided by the 3GPP network functions to the outside.

9. The network storage function (NF) entity is used to store the network function entity and the description information of the service provided by the network function entity, and support service discovery, network element entity discovery, etc.

10. Policy Control Function (PCF) entity: the unified policy framework is used for guiding network behaviors, providing policy rule information for control plane function network elements (such as AMF and SMF network elements) and the like.

11. Unified Data Management (UDM) entity: the method is used for unified data management, 5G user data management, user identification processing, access authentication, registration, mobility management and the like.

12. Application Function (AF) entity: the method is used for carrying out data routing of application influence, accessing network open function network elements, or carrying out strategy control by interacting with a strategy framework and the like.

In the network architecture, an N1 interface is a reference point between a terminal and an AMF entity; the N2 interface is a reference point of AN and AMF entities, and is used for sending non-access stratum (NAS) messages and the like; the N3 interface is a reference point between (R) AN and UPF entities, for transmitting user plane data, etc.; the N4 interface is a reference point between the SMF entity and the UPF entity, and is used to transmit information such as tunnel identification information, data cache indication information, and downlink data notification message of the N3 connection; the N6 interface is a reference point between the UPF entity and the DN for transmitting user plane data, etc.

It should be understood that the network architecture applied to the embodiments of the present application is only an exemplary network architecture described in terms of a conventional point-to-point architecture and a service architecture, and the network architecture to which the embodiments of the present application are applied is not limited thereto, and any network architecture capable of implementing the functions of the network elements described above is applicable to the embodiments of the present application.

It should also be understood that the AMF entity, SMF entity, UPF entity, NSSF entity, NEF entity, AUSF entity, NRF entity, PCF entity, UDM entity shown in fig. 1 may be understood as network elements in the core network for implementing different functions, e.g. may be combined into network slices as needed. The core network elements may be independent devices, or may be integrated in the same device to implement different functions, which is not limited in this application.

The present application does not limit the specific form of the network element, and for example, the network element may be integrated in the same physical device, or may be different physical devices. Furthermore, the above nomenclature is only used to distinguish between different functions, and should not be construed as limiting the application in any way, and this application does not exclude the possibility of other nomenclature being used in 5G networks and other networks in the future. For example, in a 6G network, some or all of the above network elements may follow the terminology in 5G, and may also adopt other names, etc. The description is unified here, and will not be repeated below.

It should also be understood that the name of the interface between each network element in fig. 1 is only an example, and the name of the interface in the specific implementation may be other names, which is not specifically limited in this application. In addition, the name of the transmitted message (or signaling) between the network elements is only an example, and the function of the message itself is not limited in any way.

In the conventional network resource management, if the user requirements in the network change, a method of manual intervention is required to create a new NF or delete an NF that has been created in the network. That is, an engineer is required to monitor the network condition, and according to the network condition, the engineer may create a new NF in the network or delete an NF that has been created in the network. When the network resource management is carried out by adopting the mode, the problems of inflexible network deployment and long response time exist because manual intervention is needed.

The present application provides a method for controlling network resources, which can effectively improve the utilization rate of network resources on the premise of satisfying the user requirements, and the method provided by the embodiment of the present application is described in detail below with reference to fig. 2.

Fig. 2 shows a schematic flow chart of a method 200 for network resource control provided by the embodiment of the present application. The method 200 includes

steps

210 and 220, which are described in detail below.

Step 210, the management system obtains network requirements.

In this embodiment of the present application, the acquiring, by the management system, the network requirement includes: the management system receives a creation request message sent from the first NF, the creation request message for requesting creation of the second NF. Wherein the creation request message includes a type of the second NF. It should be understood that the first NF is an NF that has been deployed in the network before the network demand changes. The second NF is a newly deployed NF in the network after the network requirements change.

The management system receives a creation request message sent by a first NF, and the creation request message can be realized by the following mode, after the first NF identifies the service requirement of a user in the network (for example, the service requirement of the user needs to be slice selection) according to a cell identifier carried in a user message, the first NF sends the creation request message to the management system. In this case, the management system may receive a create request message transmitted from the first NF.

Optionally, before the management system receives the creation request message sent from the first NF, the method further includes: receiving a subscription message sent by a first NF, wherein the subscription message is used for requesting the information of the NF; and sending NF list information to the first NF, wherein the NF list information is used for indicating the types of the NF which can be created, and the types of the NF which can be created comprise the type of the second NF.

After the first NF receives the NF list information sent from the management system, the first NF may send a creation request message to the management system according to the information in the NF list. It should be noted that, in the case that there is no second NF type that needs to be created in the NF list, the first NF does not send a create request message to the management system.

Step 220, the management system performs any one or more of the following operations according to the network requirements: create new network functions NF, delete created NFs.

The management system executes any one or more of the following operations according to network requirements: creating a new NF and deleting the created NF, comprising: and creating the second NF according to the creation request message.

In one implementation, creating the second NF in accordance with the create request message includes: and under the condition that resources required for creating the second NF are configured in the network, creating the second NF according to the creation request message. Wherein the resources required to create the second NF include hardware resources and software resources required to create the second NF. When the resources required for creating the second NF are not reserved in the network, the management system cannot deploy the second NF according to the creation request message, that is, the creation of the second NF fails.

In another implementable manner, creating the second NF in accordance with the create request message includes: and under the condition that the type of the second NF which can be dynamically established and system resources required by the second NF are planned in the network, the second NF is established according to the establishment request message.

In the embodiment of the present application, the system resource required by the second NF is not particularly limited. For example, the system resources required by the second NF may be hardware resources associated with the second NF. Alternatively, the system resources required by the second NF may also be a software package associated with the second NF.

It should be noted that, after the management system creates the second NF according to the network requirement, the management system further needs to issue the configuration information of the second NF. In this case, the second NF may provide the network service to the user. The configuration information includes system configuration information and network configuration information. The system configuration information includes control parameters, and the network configuration information includes a route, an Internet Protocol (IP), and the like required for the second NF to communicate with the outside of the network.

After creating the second NF according to the creation request message, the method further includes: sending a first message to a first NF, wherein the first message is used for indicating the attribute information of a second NF successfully created by a management system, and the attribute information of the second NF comprises the type of the second NF and the address of the second NF; or sending a second message to the first NF, wherein the second message is used for indicating that the management system fails to create the second NF.

The management system executes any one or more of the following operations according to network requirements: creating a new NF, deleting the created NF, further comprising: and deleting the third NF under the condition that the utilization rate of the third NF is lower than the threshold value. Wherein the third NF is an NF which is already established in the network. For example, the third NF may be an NF that has been deployed in the network before the network demand changes. Alternatively, the third NF may be a newly deployed NF in the network after the network demand changes.

In the embodiment of the application, after the management system obtains the utilization rate of the created third NF in the network, the management system deletes the third NF according to the network requirement under the condition that the utilization rate of the third NF is lower than the threshold value.

Before the management system obtains the utilization rate of the third NF, the method further includes: and sending a query message to the third NF, wherein the query message is used for indicating the management system to periodically acquire the use condition of the third NF.

In one implementation, the third NF may proactively report usage of the third NF to the management system. Specifically, the management system establishes a second NF, and issues related configuration information (e.g., system configuration and network configuration) of the second NF. If a second NF (i.e., an example of a third NF) is already deployed in the network, the second NF (i.e., an example of the third NF) may periodically report the use condition of the second NF (i.e., an example of the third NF) to the management system according to the configuration information issued by the management system.

In another implementable manner, the management system may proactively acquire a usage of the third NF. Specifically, a second NF is established in the management system, and relevant configuration information (e.g., system configuration and network configuration) of the second NF is issued. If a second NF (i.e., an instance of a third NF) is already deployed in the network, the management system may periodically obtain the usage of the second NF (i.e., an instance of the third NF).

In this embodiment, the third NF is deleted when the utilization of the third NF is lower than the threshold. It is understood that when the utilization rate of the third NF is less than or equal to T and no one is used within K hours, the management system deletes the third NF. It should be understood that the sizes of T and K may be set according to the requirements of the network, and the present application is not limited thereto. For example, T may be 0% and K may be 24 hours. That is, when the utilization rate of the third NF is less than or equal to 0% and no user uses the third NF within 24 hours, the management system deletes the third NF.

In the embodiment of the present application, the management system may periodically acquire the usage of the third NF. Wherein, the length of the period can be configured in the configuration information of the management system. The length of the period may be set to range from 1 minute to 24 hours. For example, the period length may be configured to be 1 minute. In this case, the management system acquires the use of the third NF every 1 minute. For example, the cycle length may be set to 30 minutes. In this case, the management system acquires the use of the third NF every 30 minutes. For example, the period length may be configured to be 24 hours. In this case, the management system acquires the use of the third NF every 24 hours.

The management system executes any one or more of the following operations according to network requirements: creating a new network function NF, deleting the created NF, further comprising: and creating the second NF according to the creation request message, and deleting the third NF under the condition that the utilization rate of the third NF is lower than a threshold value. It should be understood that the third NF is an NF that has been created in the network. In other words, the third NF may be an NF that has been deployed in the network before the network demand changes. Alternatively, the third NF may be a newly deployed NF in the network after the network demand changes. For example, the third NF may be the first NF. Alternatively, the third NF may be the second NF.

The method for controlling the network resources provided by the embodiment of the application can automatically sense the network requirements through the established NF in the network, can quickly and timely adjust the NF in the network according to the network requirements, and can effectively improve the utilization rate of the network resources on the premise of meeting the requirements of users.

Hereinafter, the method for controlling network resources according to the present application will be described with reference to fig. 3 to 7.

Fig. 3 shows a schematic flow chart of a method 300 of network resource control according to an embodiment of the application. The method 300 of fig. 3 includes steps 310 through 380, which are described in detail below.

At step 310, the SMF (i.e., an instance of the first NF) obtains network requirements.

In the embodiment of the present application, a manner of acquiring a network requirement by the SMF is not particularly limited. For example, the SMF may obtain the network requirement according to the cell identifier carried in the user message. Alternatively, the SMF may also obtain the network requirements by analyzing the network system.

At step 320, the SMF (i.e., an instance of the first NF) sends a create request message to the management system.

Wherein the creation request message is for requesting creation of a NEW NF (i.e., an instance of the second NF), and the creation request message includes a type of the NEW NF.

In one implementation, the SMF sends a create request message to the management system, including: after the SMF identifies the service requirement of the user in the network according to the cell identifier carried in the user message, and the network element corresponding to the service requirement of the user is NEW NF, the SMF sends a creation request message to the management system. In this case, the management system may receive a create request message from the SMF.

It should be appreciated that when the SMF discovers that a NEW NF does not exist in the current network, the SMF may send a create request message to the management system. When the SMF discovers that a NEW NF exists in the current network, the SMF may not send a create request message to the management system.

Illustratively, the SMF identifies that the service requirement of the user is required to be slice-selected according to the cell identifier carried in the user message, and the network element corresponding to the service requirement is NEW NF # 1. The SMF discovers that NEW NF #1 does not exist in the current network and the SMF sends a create request message to the management system, the request message including the type of the NEW NF # 1.

Optionally, step 320 may be preceded by step 370 and step 380.

Therein, the SMF (i.e., an instance of the first NF) sends a subscribe message to the management system, step 370.

Wherein the subscription message includes information requesting the NF.

Therein, the management system sends a NF list to the SMF (i.e., an example of the first NF), step 380.

The management system sends a list of NFs to the SMF (i.e., an instance of the first NF) based on the subscription message. Wherein the NFs included in the NF list indicate types of NFs that the current management system supports creation.

In another implementable manner, the SMF sends a create request message to the management system, including: after receiving the NF list information sent from the management system, the SMF may send a create request message to the management system according to the information in the NF list. It should be noted that, in the case that there is no NEW NF type to be created in the NF list, the SMF does not send a create request message to the management system.

At step 330, the management system determines whether to create a NEW NF (i.e., an instance of a second NF).

In one implementation, the management system determines whether to create the NEW NF from the create request message of step 320, including the following two cases:

the first condition is as follows:

if the hardware resources and software resources required for creating the NEW NF are reserved in the current network, the management system can create the NEW NF according to the creation request message. In this case, step 340 and step 350 are performed after step 330.

Step 340, the management system issues configuration information to the NEW NF.

After the management system creates the NEW NF according to the network requirement, the NEW NF can provide the network service for the user only after the management system issues the configuration information of the NEW NF. The configuration information includes system configuration information and network configuration information. For example, the system configuration information includes control parameters. For example, the network configuration information includes a route, IP, etc. required for the NEW NF to communicate with outside the network.

In step 350, the management system sends a first message to the SMF.

The first message is used for indicating attribute information of the NEW NF successfully created by the management system, and the attribute information of the NEW NF comprises the type of the NEW NF and the address of the NEW NF.

In the embodiment of the present application, the sequence of steps 340 and 350 is not particularly limited. For example, step 340 may be performed first, followed by step 350. Alternatively, step 350 may be performed first, and then step 340 may be performed.

Case two:

if the hardware resources and the software resources required for creating the NEW NF are not reserved in the current network, the management system cannot create the NEW NF according to the creation request message. In this case, step 360 is performed after step 330.

In another implementable manner, the management system determines whether to create the NEW NF based on the create request message of step 320, including: the NEW NF is created from the create request message, with the type of NEW NF that can be dynamically established and the system resources that the NEW NF needs having been planned in the network. In this case, step 340 and step 350 are performed after step 330. Otherwise, step 360 is performed after step 330.

In step 360, the management system sends a second message to the SMF.

Wherein the second message is used for indicating that the management system fails to create the NEW NF.

According to the method for controlling the network resources, the new NF is adaptively created according to the network requirements, and the utilization rate of the network resources can be effectively improved on the premise of meeting the requirements of users.

Fig. 4 shows a schematic flow chart of a method 400 of network resource control according to an embodiment of the application. The method 400 of fig. 4 includes steps 410 through 490, which are described in detail below.

In the embodiment of the present application, NF is taken as an example for introduction. It should be understood that, when an NF is used as the first NF, the NF needs to acquire information on whether a NEW NF (i.e., an example of the second NF) is included in the current network by querying the NRF.

At step 410, the NF obtains network requirements.

In the embodiment of the present application, the manner in which the NF acquires the network requirement is not particularly limited. For example, the NF may obtain the network requirement according to the cell identifier carried in the user message. Alternatively, the NF may analyze the network system to obtain network requirements.

At step 420, the NF sends a query message to the NRF.

And the NF sends a query message to the NRF, wherein the query message is used for querying whether the NF corresponding to the network requirement exists in the current network.

The NRF sends a create request message to the management system, step 430.

The NRF sends the creation request message to the management system, which can be understood as that the NRF identifies that the user service requirement in the network changes according to the cell identifier carried in the user message, and sends the creation request message to the management system when determining that there is no network element corresponding to the user service requirement in the current network. It should be understood that, if the NRF finds that the network element corresponding to the user service requirement exists in the current network, the NRF does not send the creation request message to the management system.

At step 440, the management system determines whether to create a NEW NF (i.e., an instance of a second NF).

In one implementation, the management system determines whether to create the NEW NF from the create request message of step 430, including the following two cases:

the first condition is as follows:

if the hardware resources and software resources required for creating the NEW NF are reserved in the current network, the management system can create the NEW NF according to the creation request message. In this case, steps 450 to 470 are performed after step 440.

Step 450, the management system issues configuration information to the NEW NF.

After the management system creates the NEW NF according to the network requirement, the NEW NF can provide the network service for the user only after the management system issues the configuration information of the NEW NF. The configuration information includes system configuration information and network configuration information. The system configuration information includes control parameters and the network configuration information includes routing, IP, etc. required for the NEW NF to communicate with outside the network.

Step 460, the management system sends a first message to the NRF.

The NRF sends a first message to the NF, step 470.

It should be appreciated that the NRF sends the first message to the NF, which is the same as the first message in step 460.

In the embodiment of the present application, step 450 may be performed first, and then steps 460 and 470 may be performed. Alternatively, step 460 and step 470 may be performed first, and then step 450 may be performed.

Case two:

and if the hardware resources and the software resources required for creating the NEW NF are not reserved in the current network, the management system cannot create the NEW NF according to the creation request message. In this case, step 440 is followed by step 480 and step 490.

In another implementable manner, the management system determining whether to create the NEW NF from the create request message of step 430 includes: in case the type of dynamically establishable NEW NFs and the system resources required by the NEW NFs have been planned in the network, the NEW NFs are based on the create request message. In this case, steps 450 to 470 are performed after step 440. Otherwise, steps 480 and 490 follow step 440.

Step 480, the management system sends a second message to the NRF.

The NRF sends a second message to the NF, step 490.

It should be appreciated that the NRF sends a second message to the NF that is the same as the second message in step 480.

According to the method for controlling the network resources, the new NF is adaptively established according to the network requirements, and the utilization rate of the network resources can be effectively improved on the premise of meeting the user requirements.

It should be understood that the method for automatically creating NF according to network requirement provided in fig. 3 and 4 is only an example and does not constitute any limitation to the present application.

In the above, an embodiment in which the management system automatically creates NFs according to network requirements is described in detail with reference to fig. 3 and 4. An embodiment in which the management system automatically deletes created NFs in the network according to the network requirements is described in detail below with reference to fig. 5.

Fig. 5 shows a schematic flow chart of a method 500 of network resource control according to an embodiment of the application. The method 500 of fig. 5 includes steps 510 through 530, which are described in detail below.

In step 510, NF #1 (i.e., an example of a third NF) sends the utilization of NF #1 to the management system.

Wherein, NF #1 is the NF which is already established in the current network.

In the embodiment of the present application, the NF #1 may actively report the utilization rate of the NF #1 to the management system. Specifically, the NF #1 may report the utilization rate of the NF #1 to the management system periodically according to the configuration information issued by the management system.

At step 520, the management system determines whether to delete NF #1 (i.e., an instance of a third NF).

The management system determines whether to delete NF #1 according to network requirements, and the method comprises the following steps: in the case where the utilization of NF #1 is below the threshold value, NF #1 is deleted.

When the utilization rate of the NF #1 is lower than the threshold value, the NF #1 is deleted, which is to be understood that when the utilization rate of the NF #1 is less than or equal to T and no one is used within K hours, the management system deletes the NF # 1. It should be understood that the sizes of T and K may be set according to the requirements of the network, and the present application is not limited thereto.

For example, T may be 1% and K may be 5 hours. That is, when the utilization rate of NF #1 is less than or equal to 1%, and no user uses the NF #1 within 5 hours, the management system deletes the NF # 1.

For example, T may be 0% and K may be 24 hours. That is, when the utilization rate of NF #1 is less than or equal to 0%, and no user uses the NF #1 for 24 hours, the management system deletes the NF # 1.

Optionally, step 530 may be further included before step 510.

At step 530, the management system sends a query message to NF #1 (i.e., an example of a third NF).

Wherein, the query message is used for periodically acquiring the utilization rate of NF # 1.

Optionally, in some implementations, the management system may proactively acquire usage of NF # 1. Specifically, the management system periodically obtains the utilization rate of NF #1 through the query message.

According to the method for controlling the network resources, the created NF in the network is deleted in a self-adaptive mode according to the network requirements, and the utilization rate of the network resources can be effectively improved on the premise that the user requirements are met.

It should be understood that the method for automatically deleting NF created in the network according to the network requirement provided in fig. 5 is only an example and does not limit the present application in any way.

In the present application, the method provided in fig. 5 may be combined with the method provided in fig. 3 or the method provided in fig. 4, respectively. The specific implementation is shown in fig. 6 and fig. 7, respectively.

Fig. 6 shows a schematic flow chart of a method 600 of network resource control according to an embodiment of the application. The method 600 of fig. 6 includes steps 610 through 692. The method of steps 610 to 680 is the same as the method of steps 310 to 380, and the method of steps 690 to 692 is the same as the method of steps 510 to 530. For brevity, detailed description is not provided below.

In the embodiment of the present application, SMF is used as the first NF.

At step 610, the SMF (i.e., an instance of the first NF) obtains network requirements.

At step 620, the SMF sends a create request message to the management system.

Optionally, step 670 and step 680 may also be included before step 620.

In step 670, the SMF sends a subscribe message to the management system.

Therein, the management system sends the NF list to the SMF, step 680.

At step 630, the management system determines whether to create a NEW NF (i.e., an instance of a second NF).

The first condition is as follows: the management system determines to create a NEW NF based on the create request message and the resources in the network, and then performs step 640 and step 650 after step 630.

Step 640, the management system issues the configuration information of the NEW NF.

At step 650, the management system sends a first message to the SMF.

Case two: the management system determines that the creation of the NEW NF failed based on the create request message and the resources in the network, then step 660 is performed after step 630.

At step 660, the management system sends a second message to the SMF.

Step 690, the NEW NF sends the utilization of the NEW NF to the management system.

Optionally, step 692 may also be included prior to step 690.

Therein, step 692, the management system sends a query message to the NEW NF.

At step 691, the management system determines whether to delete the NEW NF (i.e., an instance of the third NF).

The method for controlling the network resources, provided by the embodiment of the application, can adaptively create and delete a new NF according to the network requirements. On the premise of meeting the user requirements, the utilization rate of network resources can be effectively improved.

Fig. 7 shows a schematic flow chart of a method 700 of network resource control according to an embodiment of the application. The method 700 of fig. 7 includes steps 710 through 793. The methods of steps 710 to 790 are respectively the same as those of steps 410 to 490, and the methods of steps 791 to 793 are respectively the same as those of steps 510 to 530. For brevity, detailed description is not provided below.

In the embodiment of the present application, NF is used as the first NF.

At step 710, the NF (i.e., an instance of the first NF) obtains network requirements.

At step 720, the NF sends a query request message to the NRF.

At step 730, the NRF sends a create request message to the management system.

At step 740, the management system determines whether to create a NEW NF.

The first condition is as follows: the management system determines to create a NEW NF based on the create request message and the resources in the network, and then performs steps 750 through 770 after step 740.

Step 750, the management system issues the configuration information of the NEW NF.

At step 760, the management system sends a first message to the NRF.

At step 770, the NRF sends a first message to the NF.

Case two: the management system determines that the creation of the NEW NF failed based on the create request message and the resources in the network, and then performs

steps

780 and 790 after step 740.

Step 780, the management system sends a second message to the NRF.

Step 790, the NRF sends a second message to the NF.

Step 791, the NEW NF sends the utilization of the NEW NF to the management system.

Optionally, step 793 may also be included before step 791.

Wherein, step 793, the management system sends a query message to the NEW NF.

At step 792, the management system determines whether to delete the NEW NF (i.e., an instance of the third NF).

The method provided by the embodiment of the present application is described in detail above with reference to fig. 2 to 7. Next, a network device provided in an embodiment of the present application is described in detail with reference to fig. 8 to 11.

Fig. 8 shows a schematic structural diagram of a network device 800 provided in an embodiment of the present application. The network device includes a processing unit 810 and a transceiving unit 820. The processing unit 810 is configured to obtain network requirements; the processing unit 810 is further configured to perform any one or more of the following operations according to the network requirement: create new network functions NF, delete created NFs.

Optionally, in some embodiments, the transceiving unit 820 is configured to receive a create request message sent from a first NF, where the create request message is used to request to create a second NF; the processing unit 810 is further configured to create the second NF according to the creation request message.

Optionally, in some embodiments, in a case that a resource required for creating the second NF is already configured in the network, the processing unit 810 is further configured to create the second NF according to the creation request message.

Optionally, in some embodiments, the transceiving unit 820 is further configured to receive a subscription message sent by the first NF, where the subscription message is used to request information of an NF; and the transceiving unit 820 is further configured to send NF list information to the first NF, where the NF list information is used to indicate types of NFs that can be created, and the types of NFs that can be created include the type of the second NF.

Optionally, in some embodiments, the transceiving unit 820 is further configured to send a first message to the first NF, where the first message is used to indicate that the management system successfully creates the attribute information of the second NF, and the attribute information of the second NF includes a type of the second NF and an address of the second NF; or the transceiving unit 820 is further configured to send a second message to the first NF, where the second message is used to indicate that the management system failed to create the second NF.

Optionally, in some embodiments, the processing unit 810 is further configured to obtain a utilization rate of a third NF that has been created in the network; the processing unit 810 is further configured to delete the third NF if the utilization of the third NF is lower than a threshold value.

Optionally, in some embodiments, the transceiving unit 820 is configured to send a query message to the third NF, where the query message is used to instruct the management system to periodically acquire the usage of the third NF.

Fig. 9 shows a schematic structural diagram of a network device 900 provided in an embodiment of the present application. The network device includes a processing unit 910 and a transceiving unit 920. The processing unit 910 is configured to obtain a network requirement; a transceiving unit 920, configured to send a creation request message to the management system according to the network requirement, where the creation request message is used to request for creating the second NF.

Optionally, in some embodiments, in a case that it is determined that the second NF is not currently created in the network, the transceiver unit is further configured to send a creation request message to the management system according to the network requirement.

Optionally, in some embodiments, the transceiver unit is further configured to send a subscription message to the management system, where the subscription message is used to request information of the NF; and

the transceiver unit is further configured to receive NF list information sent from the management system, where the NF list information is used to indicate types of NFs that can be created, and the types of NFs that can be created include the type of the second NF.

Optionally, in some embodiments, the transceiver unit is further configured to receive a first message sent from the management system, where the first message is used to indicate that the management system successfully creates the attribute information of the second NF, and the attribute information of the second NF includes a type of the second NF and an address of the second NF; or

The transceiver unit is further configured to receive a second message sent from the management system, where the second message is used to indicate that the management system fails to create the second NF.

Fig. 10 shows a schematic block diagram of a network device 1000 provided in an embodiment of the present application.

As shown in fig. 10, the network device 1000 includes: a transceiver 1010, a processor 1020, and a memory 1030. The transceiver 1010, the processor 1020 and the memory 1030 communicate with each other via internal communication paths to transmit control and/or data signals.

A processor 1020 for obtaining network requirements;

the processor 1020 is further configured to perform any one or more of the following operations according to the network requirement: create new network functions NF, delete created NFs.

It is understood that when the processor 1020 invokes and runs the computer program from the memory, the processor 1020 can be used to execute the method embodiments and implement the execution subject of the method embodiments, such as the functions of the network device.

Fig. 11 shows a schematic block diagram of a network device 1100 provided by an embodiment of the present application.

As shown in fig. 11, the network device 1100 includes: a transceiver 1110, a processor 1120, and a memory 1130. The transceiver 1110, the processor 1120, and the memory 1130 communicate with each other via internal communication paths to transmit control and/or data signals.

A transceiver 1110, configured to send a create request message to a management system according to the network requirement, where the create request message is used to request to create a second NF;

a processor 1120 configured to obtain network requirements.

It is understood that when the processor 1120 invokes and runs the computer program from the memory, the processor 1120 can be used to execute the method embodiments and realize the execution subject of the method embodiments, such as the function of the network device.

The embodiment of the application also provides a processing device, which comprises a processor and an interface; the processor is configured to perform the method of any of the above method embodiments.

It is to be understood that the processing means described above may be one or more chips. For example, the processing device may be a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit (DSP), a Microcontroller (MCU), a Programmable Logic Device (PLD), or other integrated chips. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. To avoid repetition, it is not described in detail here.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor described above may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the method performed by the management system, the first NF, of the embodiment shown in fig. 2.

According to the method provided by the embodiment of the present application, the present application further provides a computer-readable medium storing a program code, which when running on a computer, causes the computer to execute the method executed by the management system and the first NF in the embodiment shown in fig. 2

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. 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.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for network resource control, the method comprising:

the management system acquires network requirements;

the management system executes any one or more of the following operations according to the network requirements:

create new network functions NF, delete created NFs.

2. The method of claim 1, wherein the management system obtaining network requirements comprises:

the management system receives a creation request message sent by a first NF, wherein the creation request message is used for requesting to create a second NF;

wherein the management system performs any one or more of the following operations according to the network requirements: creating a new NF and deleting the created NF, comprising:

and creating the second NF according to the creating request message.

3. The method of claim 2, wherein the creating the second NF in accordance with the create request message comprises:

and under the condition that resources required for creating the second NF are configured in the network, creating the second NF according to the creating request message.

4. The method of claim 2 or 3, wherein prior to receiving the create request message from the first NF, the method further comprises:

receiving a subscription message sent by the first NF, wherein the subscription message is used for requesting the information of the NF; and

and sending NF list information to the first NF, wherein the NF list information is used for indicating the types of the NF which can be created, and the types of the NF which can be created comprise the type of the second NF.

5. The method according to any of claims 2-4, wherein after the creating the second NF according to the create request message, the method further comprises:

sending a first message to the first NF, wherein the first message is used for indicating the attribute information of the second NF successfully created by the management system, and the attribute information of the second NF comprises the type of the second NF and the address of the second NF; or

And sending a second message to the first NF, wherein the second message is used for indicating that the management system fails to create the second NF.

6. The method of claim 1, further comprising:

acquiring the utilization rate of a third NF established in the network;

and deleting the third NF under the condition that the utilization rate of the third NF is lower than a threshold value.

7. The method of claim 6, wherein prior to obtaining the utilization of the third NF, the method further comprises:

and sending a query message to the third NF, wherein the query message is used for indicating the management system to periodically acquire the use condition of the third NF.

8. A method for network resource control, the method comprising:

a first network function NF obtains network requirements;

and the first NF sends a creation request message to a management system according to the network requirement, wherein the creation request message is used for requesting to create a second NF.

9. The method of claim 8, wherein the first network function NF sends a create request message to a management system according to the network requirements, comprising:

and under the condition that the second NF is not established in the current network, the first network function NF sends an establishment request message to a management system according to the network requirement.

10. Method according to claim 8 or 9, wherein before the first network function NF sends a request message to a management system according to the network requirements, the method further comprises:

sending a subscription message to the management system, wherein the subscription message is used for requesting information of NF (network connection); and

and receiving NF list information sent by the management system, wherein the NF list information is used for indicating the types of NF which can be created, and the types of NF which can be created comprise the type of the second NF.

11. The method according to any one of claims 8-10, further comprising:

receiving a first message sent by the management system, wherein the first message is used for indicating the attribute information of the second NF successfully created by the management system, and the attribute information of the second NF comprises the type of the second NF and the address of the second NF; or

And receiving a second message sent by the management system, wherein the second message is used for indicating that the management system fails to create the second NF.

12. A network device, comprising:

the processing unit is used for acquiring network requirements;

the processing unit is further configured to perform any one or more of the following operations according to the network requirement:

create new network functions NF, delete created NFs.

13. The network device according to claim 12, wherein the network device further comprises a transceiver unit, configured to receive a create request message sent from a first NF, the create request message being used to request to create a second NF;

the processing unit is further configured to create the second NF according to the creation request message.

14. The network device of claim 13,

and under the condition that resources required for creating the second NF are configured in the network, the processing unit is also used for creating the second NF according to the creation request message.

15. The network device of claim 13 or 14,

the receiving and sending unit is further configured to receive a subscription message sent by the first NF, where the subscription message is used to request information of an NF; and

the transceiver unit is further configured to send NF list information to the first NF, where the NF list information is used to indicate types of NFs that can be created, and the types of NFs that can be created include the type of the second NF.

16. The network device of any one of claims 13-15,

the transceiver unit is further configured to send a first message to the first NF, where the first message is used to indicate that the management system successfully creates the attribute information of the second NF, and the attribute information of the second NF includes a type of the second NF and an address of the second NF; or

The transceiver unit is further configured to send a second message to the first NF, where the second message is used to indicate that the management system fails to create the second NF.

17. The network device of claim 12,

the processing unit is further configured to obtain a utilization rate of a third NF that has been created in the network;

the processing unit is further configured to delete the third NF when the utilization rate of the third NF is lower than a threshold value.

18. The network device according to claim 17, wherein the network device further comprises a transceiver unit, and the transceiver unit is configured to send a query message to the third NF, where the query message is used to instruct the management system to periodically acquire the usage of the third NF.

19. A network device, comprising:

the processing unit is used for acquiring network requirements;

and the receiving and sending unit is used for sending a creation request message to the management system according to the network requirement, wherein the creation request message is used for requesting to create the second NF.

20. The network device of claim 19,

and under the condition that the second NF is not established in the current network, the transceiver unit is also used for sending an establishment request message to a management system according to the network requirement.

21. The network device of claim 19 or 20,

the receiving and sending unit is further configured to send a subscription message to the management system, where the subscription message is used to request information of the NF; and

22. The network device of any one of claims 19-21,

the transceiver unit is further configured to receive a first message sent from the management system, where the first message is used to indicate that the management system successfully creates the attribute information of the second NF, and the attribute information of the second NF includes a type of the second NF and an address of the second NF; or

23. A network device comprising a processor and a memory, the memory for storing instructions, the processor for reading instructions stored in the memory to implement the method of any one of claims 1 to 11.

24. A computer-readable storage medium comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 11.

25. A chip comprising at least one processor and an interface;

the at least one processor is configured to call and run a computer program to cause the chip to perform the method according to any one of claims 1 to 11.