Network function system, network function unit registration method and computer program

Abstract

To smoothly realize scale-out of a network function unit having the same network function.SOLUTION: A network function system includes one or more own network function units having the same network function in a control plane of a wireless communication system, and a network function unit registration unit for centrally registering the one or more own network function units, to a comprehensive network function management unit for managing the network function units each having various network functions in the control plane in the wireless communication system.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a network function system, a network function unit registration method, and a computer program. [Background technology]

[0002] Technical specifications for the fifth-generation mobile communication system (5G system) are described in Non-Patent Documents 1 and 2, etc. In the 5G system, the core network (5G Core Network: 5GC) adopts a "service-based architecture" and is a cloud-native architecture. This allows each function of the 5GC to be built as a CNF (Cloud-native Network Function). In the 5GC, CNF instances are dynamically launched in response to changes in user demand or changes in the state of the communication infrastructure (e.g., communication node failures). CNFs can be realized using a platform such as "Kubernetes (registered trademark)." "Kubernetes" is known as an open-source container platform for automating the deployment, scaling, and management of containerized applications.

[0003] In the 5G system, the processes required for implementing the 5GC control plane (5GC Control-Plane (C-Plane)) functions, such as user authentication, handover, and billing, are converted into microservices called Network Functions (NFs), and each NF publishes an Application Programming Interface (API) within the 5GC to enable it to use its own functions. In 5GC, a Network Repository Function (NRF) is defined as a function that enables an NF to select an NF that provides an API in order to use that API. When an NF that provides an API is started, information about the NF (NF), such as its Internet Protocol (IP) address, the services it provides, and the amount of resources, is registered with the NRF. A Consumer NF (NF) that wants to use an API queries the NRF to learn about the Producer NF (NF) that provides the API, and can then communicate with the Producer NF by obtaining the Producer NF's information (NF Profile) from the NRF. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP, “TS 23.501”, v17.5.0 [Non-patent document 2] 3GPP, “TS 29.510”, v17.6.0 Summary of the Invention [Problem to be solved by the invention]

[0005] To improve fault tolerance in 5GC, it is possible to scale out the NFs by providing multiple NFs that provide the same API and distributing the processing of API requests among the multiple NFs. However, when multiple NFs that provide the same API are launched, the number of NFs registered in the NRF increases, which may lead to problems such as an increase in the NRF equipment cost due to an increase in the NRF database size, a deterioration in the fault tolerance of the NRF, and an increase in the response delay of the NRF.

[0006] The present invention has been made in consideration of the above circumstances, and its object is to smoothly realize the scale-out of network function units having the same network functions. [Means for solving the problem]

[0007] One aspect of the present invention is a network function system comprising: one or more own network function units having the same network function of a control plane of a wireless communication system; and a network function unit registration unit that centrally registers the one or more own network function units with an integrated network function unit management unit that manages network function units each having various network functions of the control plane in the wireless communication system. and further comprising a local network function unit management unit that acquires a local network function unit activation count, which is the number of local network function units that are activated in the network function system, and the network function unit registration unit controls the centralized registration of the one or more local network function units with the comprehensive network function unit management unit based on the local network function unit activation count and an activation count lower limit value. It is a network function system. One aspect of the present invention is a network function system as described above, further comprising a distribution unit that distributes requests for network functions of its own network function unit from outside the network function system to the one or more of its own network function units, and the network function unit registration unit includes a communication address by which the distribution unit can be reached from outside the network function system in network function unit registration information that centrally registers the one or more own network function units with the comprehensive network function unit management unit. One aspect of the present invention is a network function system in which, in the above-mentioned network function system, the network function unit registration unit centrally registers the one or more local network function units with the comprehensive network function unit management unit when the number of activations of the local network function unit meets a lower limit value for the number of activations. One aspect of the present invention is a network function system in which, in the above-mentioned network function system, the network function unit registration unit causes the comprehensive network function unit management unit to delete the centralized registration of one or more of the local network function units when the number of activations of the local network function unit does not satisfy a lower limit value for the number of activations. One aspect of the present invention is a network function system in which the local network function unit management unit measures the request processing capacity of each local network function unit activated in the network function system, and dynamically determines the lower limit of the number of activations based on the measured value and the request processing capacity requirements of the network function system. One aspect of the present invention is a network function system further comprising a local network function unit management unit that acquires a local network function unit activation count, which is the number of local network function units that are activated in the network function system, and the network function unit registration unit includes the local network function unit activation count in the network function unit registration information. One aspect of the present invention is a network function system in which, in the above-mentioned network function system, the local network function unit management unit further acquires the resource amount of the local network function unit that is running in the network function system, and the network function unit registration unit further includes the resource amount in the network function unit registration information.

[0008] One aspect of the present invention is a network function unit registration method executed by a network function system having one or more own network function units having the same network functions of a control plane of a wireless communication system, the method comprising: a network function unit registration step of centrally registering the one or more own network function units with an integrated network function unit management unit that manages network function units each having various network functions of a control plane in the wireless communication system; a local network function unit management step of acquiring a local network function unit activation count, which is the number of local network function units activated in the network function system, wherein the network function unit registration step controls the centralized registration of the one or more local network function units with the comprehensive network function unit management unit based on the local network function unit activation count and an activation count lower limit value. A network function unit registration method.

[0009] One aspect of the present invention is a network function unit registration step in which a computer of a network function system including one or more own network function units having the same network function of a control plane of a wireless communication system centrally registers the one or more own network function units with an integrated network function unit management unit that manages network function units each having various network functions of a control plane in the wireless communication system. and a local network function unit management step of acquiring a local network function unit activation count, which is the number of local network function units activated in the network function system, wherein the network function unit registration step controls the centralized registration of the one or more local network function units with the comprehensive network function unit management unit based on the local network function unit activation count and an activation count lower limit value. It is a computer program. [Effects of the Invention]

[0010] According to the present invention, it is possible to obtain an effect that it is possible to smoothly realize the scale-out of network function units having the same network functions. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram illustrating an example configuration of an NF cluster (network function system) according to an embodiment. [Figure 2] FIG. 10 is a sequence diagram illustrating an example of a procedure for a network function unit registration method according to an embodiment. [Figure 3] FIG. 10 is a sequence diagram illustrating an example of a procedure for a network function unit registration method according to an embodiment. [Figure 4] FIG. 10 is a sequence diagram illustrating an example of a procedure for a network function unit registration method according to an embodiment. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of a procedure for a network function unit registration method according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. 1 is a block diagram showing an example of the configuration of an NF cluster 100 as a network function system according to one embodiment. In this embodiment, a 5G system is used as an example of a wireless communication system, and a system related to NFs of the 5GC control plane (5GC C-Plane) of the 5G system is used as an example of a network function system.

[0013] 1, the NRF 10 manages information (NF Profile) of the NFs that provide various APIs. The NRF 10 is defined in Non-Patent Document 1. The NRF 10 corresponds to an integrated network function management unit.

[0014] The NF cluster 100 includes a master node 110 and a worker node 130. The NF cluster 100 may include only one worker node 130, or multiple worker nodes 130. The NF cluster 100 corresponds to a network function system.

[0015] The NF cluster 100 provides an API of a certain type of NF (for example, an SMF (Session Management Function)) among various NFs of the 5GC control plane to the outside. The NF cluster 100 is configured to perform scale-out for the same API.

[0016] The master node 110 includes an API providing unit 111, an instance management unit 112, and an NF registration unit 113. The worker node 130 includes a gateway 131 and NF instances 132 (132-1, . . . , 132-m, where m is a positive integer greater than or equal to 1).

[0017] The master node 110 is a node that manages the NF cluster 100. The master node 110 does not execute instances that actually process APIs. The worker node 130 is a node that executes NF instances 132, which are instances that actually process APIs.

[0018] The API providing unit 111 provides various statistical information in the NF cluster 100. The instance management unit 112 generates instances required for the worker node 130. The instance management unit 112 corresponds to its own network function management unit.

[0019] The NF registration unit 113 manages the overall status of the NF cluster 100, and centrally registers information (NF profile) of the NF instances 132 running in the NF cluster 100 to the NRF 10. The NF registration unit 113 corresponds to a network function registration unit.

[0020] The gateway 131 distributes API requests arriving at the NF cluster 100 from outside the NF cluster 100 to one or more NF instances 132 running in the NF cluster 100. As a method of this distribution, for example, the API requests may be distributed uniformly to all the NF instances 132. The gateway 131 corresponds to a distribution unit.

[0021] The NF instance 132 processes the API in response to the API request, thereby providing the function of a specific NF (for example, SMF) to the NF (Consumer) that is the source of the API request. The NF instance 132 corresponds to its own network function unit.

[0022] The NRF 10 has a global IP address "10.1.0.100". The master node 110 has a global IP address "10.1.0.101". The worker node 130 has a global IP address "10.1.0.102". As a result, the NRF 10, the master node 110, and the worker node 130 send and receive data by IP communication via the communication network NW. The global IP address "10.1.0.102" of the worker node 130 is a communication address that allows the gateway 131 to be reached from outside the NF cluster 100.

[0023] The worker node 130 is separated from the external communication network NW by a gateway 131. The gateway 131 has a private IP address "10.0.0.1". The NF instances 132-1, ..., 132-m have private IP addresses "10.0.0.2", ..., "10.0.0.m+1". As a result, within the worker node 130, data is sent and received between the gateway 131 and each NF instance 132 by IP communication using the private IP addresses.

[0024] Next, a method for registering an NF instance (network function unit) according to this embodiment will be described.

[0025] (Procedure for building a new NF cluster) The procedure for newly establishing the NF instance 132 in the NF cluster 100 will be described with reference to Fig. 2. Fig. 2 is a sequence diagram showing an example of the procedure for the network function unit registration method according to this embodiment.

[0026] (Step S1) The operator of the 5G system performs a new NF cluster setting on the instance management unit 112. The new NF cluster setting has detailed information about the NF instance 132 to be newly constructed (new NF instance 132). The detailed information includes information used to construct the new NF instance 132, such as an OS (Operating System) image and build version, and the number of new NF instances 132 to be constructed.

[0027] (Step S2) The instance management unit 112 constructs new NF instances 132 in the worker node 130 according to the new NF cluster setting. As a result, the number of new NF instances 132 specified in the new NF cluster setting is started in the worker node 130.

[0028] (Step S3) The instance management unit 112 registers, in the NF registration unit 113, information required for the registration process of the "NF profile" to the NRF 10 ("NF profile" registration process information). The "NF profile" registration process information includes the following "NF profile" registration process information (1), (2), and (3).

[0029] "NF profile" registration processing information (1): Information related to the NRF 10 as the registration destination. The information related to the NRF 10 as the registration destination is, for example, the IP address or FQDN (Fully Qualified Domain Name) of the NRF 10, an NRF identifier (NRF ID), an identifier indicating whether the NF to be registered is an instance or a cluster, etc. The "NF profile" registration processing information (1) is set in the instance management unit 112 by the 5G system operator when setting up a new NF cluster (step S1).

[0030] "NF profile" registration processing information (2): network information of the NF cluster 100. The network information of the NF cluster 100 is, for example, an IP address (in the example of this embodiment, the global IP address "10.1.0.102" of the worker node 130) or an FQDN that can reach the gateway 131 from outside the NF cluster 100. When the instance management unit 112 constructs a new NF instance 132 (step S2), the instance management unit 112 acquires the "NF profile" registration processing information (2), which is an IP address or an FQDN that is made public to the outside by the worker node 130 on which the new NF instance 132 is constructed.

[0031] "NF profile" registration processing information (3): resource amount information of the NF cluster 100. The resource amount information of the NF cluster 100 is, for example, a lower limit (lower limit value of the number of NF instance startups) of the number of NF instances 132 started in the NF cluster 100 (number of NF instance startups), the number of CPU (Central Processing Unit) cores, memory capacity, communication bandwidth, etc. The "NF profile" registration processing information (3) is set in the instance management unit 112 by the 5G system operator when setting up a new NF cluster (step S1).

[0032] (NF cluster internal update procedure) The procedure for updating the NF instance 132 in the NF cluster 100 will be described with reference to Fig. 3. Fig. 3 is a sequence diagram showing an example of the procedure of the network function unit registration method according to this embodiment.

[0033] (Step S11) The operator of the 5G system performs an existing NF cluster update on the instance management unit 112. The existing NF cluster update has detailed information about the existing NF instance 132 (existing NF instance 132). The detailed information includes information used to update the existing NF instance 132, such as the OS image and build version, and the number of existing NF instances 132 to be updated.

[0034] (Step S12) In accordance with the existing NF cluster update, the instance management unit 112 updates the existing NF instances 132 in the worker node 130. As a result, in the worker node 130, the number of existing NF instances 132 specified in the existing NF cluster update is updated.

[0035] (Step S13) The instance management unit 112 updates the information ("NF profile" registration processing information) required for the registration processing of the "NF profile" to the NRF 10 in the NF registration unit 113. The "NF profile" registration processing information is the same as the above-mentioned "NF profile" registration processing information (1), (2), and (3).

[0036] (NRF registration procedure) The procedure for registering an "NF profile" in an NRF will be described with reference to Figures 4 and 5. Figures 4 and 5 are sequence diagrams showing an example of the procedure for a network function unit registration method according to this embodiment.

[0037] (Step S21) The NF registration unit 113 repeats the procedure for registering the "NF profile" to the NRF (steps S21-S29 in FIG. 4) at a fixed cycle (NRF registration cycle). The NF registration unit 113 has a timer that measures the NRF registration cycle. When the measurement period of the timer expires, the NF registration unit 113 proceeds to step S22.

[0038] (Step S22) The NF registration unit 113 makes an NF cluster statistical information request to the API provision unit 111. The NF cluster statistical information request is a request to acquire statistical information (NF cluster statistical information) of the NF cluster 100. The NF cluster statistical information is information including the number of activated NF instances 132 (NF instance activation count) and the usage status of the NF instances 132. The usage status of the NF instances 132 is, for example, the CPU usage rate and the memory usage rate.

[0039] (Step S23) The API providing unit 111 sends an NF cluster statistical information request to the instance management unit 112. The NF cluster statistical information request is a request to acquire NF cluster statistical information.

[0040] (Step S24) The instance management unit 112 acquires the NF cluster statistical information in response to the NF cluster statistical information request from the API providing unit 111. Specifically, the instance management unit 112 acquires the number of NF instances 132 running in the NF cluster 100 (number of running NF instances) and their usage status as the NF cluster statistical information. For the CPU usage rate and memory usage rate, which are the usage status of the NF instances 132, the instance management unit 112 acquires the average value of the CPU usage rate and the average value of the memory usage rate in the NF cluster 100 as the CPU usage rate and memory usage rate of the entire NF cluster 100.

[0041] (Step S25) The instance management unit 112 returns the acquired NF cluster statistical information to the API provision unit 111.

[0042] (Step S26 ) The API providing unit 111 provides the NF cluster statistical information received from the instance managing unit 112 to the NF registering unit 113 .

[0043] (Step S27) The NF registration unit 113 determines the operation for the NRF 10 based on the NF cluster statistical information provided by the API provision unit 111.

[0044] An example of the processing procedure of step S27 is shown in Fig. 5. Here, step S27 will be described with reference to Fig. 5.

[0045] In FIG. 5, the NF registration unit 113 determines the operation for the NRF 10 based on the number of NF instance activations in the NF cluster statistical information, the lower limit value of the number of NF instance activations, the registration status of the “NF profile” to the NRF 10, and the number of NF instance activations currently registered in the NRF 10.

[0046] (Step S271) The NF registration unit 113 determines whether the number of activated NF instances in the NF cluster statistical information is equal to or greater than the lower limit value of the number of activated NF instances. If the result of this determination is that the number of activated NF instances is equal to or greater than the lower limit value, the process proceeds to step S272. On the other hand, if the number of activated NF instances is less than the lower limit value, the process proceeds to step S276.

[0047] (Step S272) The NF registration unit 113 determines whether or not the "NF profile" has been registered in the NRF 10 in the past, based on the registration status of the "NF profile" in the NRF 10. If the result of this determination is that the "NF profile" has been registered in the NRF 10 in the past, the process proceeds to step S274. On the other hand, if the "NF profile" has not been registered in the NRF 10 in the past, the process proceeds to step S273.

[0048] (Step S273) The NF registration unit 113 determines a new registration (NF Register) of an "NF profile" to the NRF 10. After this, the process proceeds to step S28 in FIG. 4, where the NF registration unit 113 performs a new registration (NF Register) of an "NF profile" to the NRF 10. The "NF profile" for this new registration includes network information and resource information of the NF cluster 100. As a result, one or more NF instances 132 running in the NF cluster 100 are centrally registered in the NRF 10. In other words, a single "NF profile" for the entire NF cluster 100 is registered in the NRF 10, rather than individual "NF profiles" of one or more NF instances 132 running in the NF cluster 100.

[0049] (Step S274) The NF registration unit 113 determines whether the number of activated NF instances in the NF cluster statistical information is the same as the number of activated NF instances currently registered in the NRF 10. If the result of this determination is that the two are the same (step S27 in FIG. 4, NO), the process proceeds to step S29 in FIG. 4. On the other hand, if the two are not the same, the process proceeds to step S275.

[0050] (Step S275) The NF registration unit 113 determines to update (NF Update) the "NF profile" already registered in the NRF 10. After that, the process proceeds to step S28 in FIG. 4, and the NF registration unit 113 updates (NF Update) the registered "NF profile" in the NRF 10. The "NF profile" for this update includes network information and resource information of the NF cluster 100.

[0051] (Step S276) The NF registration unit 113 determines whether or not the "NF profile" has been registered in the NRF 10 in the past, based on the registration status of the "NF profile" in the NRF 10. If the result of this determination is that the "NF profile" has been registered in the NRF 10 in the past, the process proceeds to step S277. On the other hand, if the "NF profile" has not been registered in the NRF 10 in the past (step S27 in FIG. 4, NO), the process proceeds to step S29 in FIG. 4.

[0052] (Step S277) The NF registration unit 113 decides to delete the "NF profile" from the NRF 10 (NF Deregister). After this, the process proceeds to step S28 in FIG. 4, where the NF registration unit 113 deletes the registered "NF profile" from the NRF 10 (NF Deregister). As a result, if the number of NF instances 132 currently running in the NF cluster 100 (the number of running NF instances in the NF cluster statistical information) is less than the lower limit value of the number of running NF instances, the registration of the registered "NF profile" of the NF cluster 100 is deleted from the NRF 10. This is because, if the number of NF instances 132 currently running in the NF cluster 100 is less than the lower limit value of the number of running NF instances, the processing capacity of the API request required of the NF cluster 100 cannot be satisfied, and therefore, the NRF 10 does not select the NF cluster 100 (NF (Producer)) for the NF (Consumer). As a result, the NRF 10 selects another NF cluster 100 (NF (Producer)) that provides the same API registered with the NRF 10 for the NF (Consumer).

[0053] In the above example, the lower limit of the number of activated NF instances is set by the operator of the 5G system, but is not limited to this. For example, the operator of the 5G system may set the API request processing capacity required for the NF cluster 100, and dynamically determine the lower limit of the number of activated NF instances in the NF cluster 100 based on the set value of the API request processing capacity. For example, if the API request processing capacity requirement is set as "capable of processing API requests for 10 million people," the instance management unit 112 measures the API request processing capacity of each NF instance 132 activated in the NF cluster 100, and dynamically determines the lower limit Z of the number of activated NF instances (Z = 1000 ÷ X) based on the measured value of "API requests for X million people" and the API request processing capacity requirement of "API requests for 10 million people."

[0054] Returning to the explanation in Figure 4. (Step S28) The NF registration unit 113 performs the operation "new registration of 'NF profile' (NF Register)," "update of registered 'NF profile' (NF Update)," or "deletion of registered 'NF profile' (NF Deregister)" for the NRF 10 determined in step S27. After that, the process proceeds to step S29.

[0055] (Step S29) The NF registration unit 113 restarts the timer that measures the NRF registration period. After that, the NF registration unit 113 waits for the timer's measurement period to expire, and when the timer's measurement period expires (step S21), the process proceeds to step S22.

[0056] According to this embodiment, the NF cluster 100 is provided with an NF registration unit 113, which centrally registers one or more NF instances 132 running in the NF cluster 100 with the NRF 10. This prevents an increase in the number of "NF profiles" registered in the NRF 10 even if a large number of NF instances 132 are started due to scale-out in the NF cluster 100, thereby suppressing an increase in the database size of the NRF 10. This solves issues such as an increase in NRF equipment costs, a deterioration in the fault tolerance of the NRF 10, and an increase in response delays of the NRF 10. This contributes to smoothly achieving scale-out of NF instances 132 that provide the same API.

[0057] Furthermore, since multiple NF instances 132 in the NF cluster 100 are centrally registered with the NRF 10, an NF (Consumer) outside the NF cluster 100 cannot individually specify an NF instance 132 for the NF cluster 100. This allows the gateway 131 to smoothly distribute the load of API requests to multiple NF instances 132.

[0058] Furthermore, the network information of the NF cluster 100 included in the "NF profile" registered in the NRF 10 includes an IP address (in the example of this embodiment, the global IP address of the worker node 130) that allows the gateway 131 to be reached from outside the NF cluster 100. As a result, even if the inside of the worker node 130 is separated from the external communication network NW by the gateway 131, an NF (Consumer) outside the NF cluster 100 can obtain an IP address that allows the gateway 131 to be reached from the NRF 10, thereby allowing an API request to reach the NF instance 132 via the gateway 131.

[0059] Furthermore, the resource amount information of the NF cluster 100 included in the "NF profile" registered in the NRF 10 includes a lower limit value for the number of NF instances activated. This allows the NRF 10 to select an NF cluster 100 that satisfies the required number of NF instances activated from among multiple NF clusters 100 that provide the same API.

[0060] Furthermore, the resource amount information of the NF cluster 100 included in the "NF profile" registered in the NRF 10 includes the resource amount (e.g., the number of CPU cores, the amount of memory, the communication bandwidth, etc.) of the NF instance 132 running in the NF cluster 100. This allows the NRF 10 to select an NF cluster 100 that meets the required API request processing capacity from among multiple NF clusters 100 that provide the same API.

[0061] This will enable, for example, improvements to the overall quality of services in wireless networks, thereby contributing to Goal 9 of the United Nations-led Sustainable Development Goals (SDGs), which is to "Build resilient infrastructure, promote sustainable industrialization and foster innovation."

[0062] Although an embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are also included within the scope that does not deviate from the gist of the present invention.

[0063] In addition, a computer program for realizing the functions of each of the above-described devices may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read and executed by a computer system. Note that the "computer system" here may also include hardware such as an OS and peripheral devices. In addition, "computer-readable recording medium" refers to writable non-volatile memory such as a flexible disk, optical magnetic disk, ROM, or flash memory, portable media such as a DVD (Digital Versatile Disc), or a storage device such as a hard disk built into a computer system.

[0064] Furthermore, the term "computer-readable recording medium" also includes those that retain a program for a certain period of time, such as volatile memory (e.g., DRAM (Dynamic Random Access Memory)) within a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has the function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may also be a program for implementing some of the functions described above, or may be a so-called differential file (differential program) that can implement the functions described above in combination with a program already stored in the computer system. [Explanation of symbols]

[0065] 10...NRF, 100...NF cluster, 110...master node, 111...API provider, 112...instance manager, 113...NF registration unit, 130...worker node, 131...gateway, 132...NF instance, NW...communication network

Claims

1. one or more own network function units having the same network function of a control plane of a wireless communication system; a network function registration unit that centrally registers the one or more own network function units with an integrated network function management unit that manages network function units each having various network functions of a control plane in the wireless communication system, a local network function unit management unit that acquires a local network function unit activation count, which is the number of local network function units that are activated in the network function system, and the network function unit registration unit controls the centralized registration of the one or more local network function units with the comprehensive network function unit management unit based on the local network function unit activation count and an activation count lower limit value. Network function system.

2. a distribution unit that distributes requests relating to the network functions of the network function unit from outside the network function system to the one or more network function units, the network function unit registration unit includes a communication address by which the distribution unit can be reached from outside the network function system in network function unit registration information that centrally registers the one or more own network function units with the integrated network function unit management unit. The network function system according to claim 1 .

3. the network function unit registration unit performs centralized registration of the one or more own network function units with the integrated network function unit management unit when the number of activations of the own network function units satisfies a lower limit value of the number of activations.

3. The network function system according to claim 1 or 2.

4. the network function unit registration unit causes the integrated network function unit management unit to delete the centralized registration of the one or more of its own network function units when the number of activations of the own network function units does not satisfy a lower limit value of the number of activations. The network function system according to claim 3 .

5. the local network function unit management unit measures a request processing capacity for each local network function unit activated in the network function system, and dynamically determines the activation number lower limit based on the measured value and a request processing capacity requirement required for the network function system.

3. The network function system according to claim 1 or 2.

6. a local network function unit management unit that acquires a local network function unit activation count, which is the number of local network function units that are activated in the network function system; the network function unit registration unit includes the number of activations of its own network function unit in the network function unit registration information; The network function system according to claim 2 .

7. the local network function unit management unit further acquires the amount of resources of the local network function unit activated in the network function system; the network function registration unit further includes the resource amount in the network function registration information. The network function system according to claim 6 .

8. A network function unit registration method executed by a network function system including one or more own network function units having the same network function of a control plane of a wireless communication system, comprising: a network function unit registration step of centrally registering the one or more own network function units with an integrated network function unit management unit that manages network function units each having various network functions of a control plane in the wireless communication system; a local network function unit management step of acquiring a local network function unit activation count, which is the number of local network function units that are activated in the network function system; the network function unit registration step controls centralized registration of the one or more own network function units with the integrated network function unit manager based on the own network function unit activation count and an activation count lower limit value. Network function unit registration method.

9. A computer of a network function system having one or more own network function units having the same network function of a control plane of a wireless communication system, a network function unit registration step of centrally registering the one or more own network function units with an integrated network function unit management unit that manages network function units each having various network functions of a control plane in the wireless communication system; a local network function unit management step of acquiring a local network function unit activation count, which is the number of local network function units that are activated in the network function system; the network function unit registration step controls centralized registration of the one or more own network function units with the integrated network function unit manager based on the own network function unit activation count and an activation count lower limit value. Computer program.

Images