Control device, communication system and control method

Abstract

To provide a control device capable of supporting dynamic arrangement change of an NF.SOLUTION: A control device includes: an NF management part for managing an NF in distributed mobile core network; a condition management part for detecting that a predetermined condition relating to the NF is not satisfied at present or in future; and a scheduling part for performing scheduling of arrangement change of the NF so that the predetermined condition is satisfied, when it has been detected by the condition management part that the predetermined condition is not satisfied.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a control device, a communication system, and a control method. [Background technology]

[0002] <Examples of distributed mobile network configurations> 10 is a diagram showing examples of the topology of a distributed mobile network. These topology are described in Non-Patent Document 1. In the Local Offload option, a User Plane Function (UPF) for data communication is located at the edge site, and a Control Plane (C-Plane) NF for processing control information is located at the central site. The UPF can either offload data traffic to a local Application Function (AF) or forward the data traffic to the central site. In both cases, the C-Plane signals are exchanged via the backhaul. This option is suitable for environments where edge nodes are less reliable or for use cases where there is no latency or capacity impact on the end-to-end service (e.g., aerial communications or live content acquisition using nomadic networks).

[0003] In the Locally Administered Edge option, AMF (Access and Mobility Management Function) and SMF (Session Management Function) are deployed at the edge site, and authentication, authorization, and session management are performed at the edge. This reduces certain C-Plane signaling between the edge and the central (e.g., Service Request Procedure) because it is completed at the edge site. This option is suitable when you want to apply specific local policies to the edge or when there is a backhaul with significant latency characteristics.

[0004] The Autonomous Edge option places all C-Plane NF functions on the edge network and provides connectivity to devices within a specific region. However, this model is limited to a certain area and it is difficult to provide continuous mobility for devices. To provide connectivity across edge networks, subscriber profile synchronization is required. This option is best suited for deployments where ultra-low latency is required or where backhaul availability and capacity are very limited and there is a high degree of trust in the edge infrastructure.

[0005] Figure 10 also shows the Authentication User Service Function (AUSF), Unified Data Management (UDM), Policy Control Function (PCF), User Equipment (UE) which is a 5G terminal, and a gNB which is a 5G base station.

[0006] <corba> Non-patent document 2 describes CORBA (Common Object Request Broker Architecture). CORBA is an open architecture that was defined in 1989 and aims to standardize distributed object systems. CORBA is a collection of specifications and protocols that enable remote calls between clients and servers and achieve interoperability between different programming languages ​​or different platforms.

[0007] ORB (Object Request Broker) is the core function of CORBA and plays the role of mediating communication between clients and servers. ORB handles communication between objects such as creating and deleting objects, invoking methods, and transferring data. ORB interacts with applications that comply with the CORBA specifications and manages the exchange of requests and responses. The combination of client / server and ORB allows objects developed in different programming languages ​​or on different platforms to communicate transparently. CORBA provides a means to increase the freedom of choice of programming language and platform, and to improve the extensibility and flexibility of the system. In addition, as described in Non-Patent Document 3, the ORB supports communication using a shared memory.

[0008] The C-Plane of the current 5G CORE network adopts SBA (Service Based Architecture). In SBA, service-based modules called NFs (Network Functions) have SBIs (Service Based Interfaces) and use HTTP (Hyper Text Transfer Protocol) to perform signaling for information exchange. In 5G or 6G, connections from many UEs or UE mobility are expected, so a large amount of signaling between NFs to complete procedures such as registration and handover (HO) may occur, which may cause congestion in the C-Plane called signaling storms (Non-Patent Document 4).

[0009] Therefore, in order to reduce the processing load caused by HTTP signaling, a method called componentization was proposed (Non-Patent Document 5). The componentized NFs are deployed on the same server, and a communication method via hardware / software resources such as shared memory (for example, POSIX shared memory communication method) is used as the communication method between NFs. In this way, by replacing it with a different communication method other than HTTP, it is expected that in addition to reducing the communication cost due to HTTP signaling (for example, the load on the communication path between NFs), the overhead of the processing required for HTTP signaling will also be reduced. The processing in question is, for example, parsing (analysis of packets) and deparsing (reconstruction of packets).

[0010] FIG. 11 is a diagram showing an example of componentization using NF to which CORBA is applied. An example of an SBA configuration and a componentized configuration are shown in Fig. 11. It is expected that components can be implemented by applying CORBA to NF. In the example of Fig. 11, three NFs are shown as NF#1 to NF#3. In CORBA, an ORB is placed in each NF. Here, assume that communication is performed from NF#3 to NF#1 via NF#2. In this case, in SBA, a total of four HTTP signalings and eight HTTP parse / deparses occur. On the other hand, in a configuration where NF#1 and NF#2 are componentized, POSIX shared memory communication is applied to the communication between NF#1 and NF#2, so a total of two HTTP signalings and four HTTP parse / deparses occur, and the load due to HTTP signaling is halved. [Prior art documents] [Non-patent literature]

[0011] [Non-Patent Document 1] Marius Corici, et al. "A Study of 5G Edge-Central Core Network Split Options," Network 1.3 (2021): 354-368. https: / / www.mdpi.com / 2673-8732 / 1 / 3 / 20 [Non-Patent Document 2] "Let's start by reviewing the basics of CORBA," https: / / atmarkit.itmedia.co.jp / ait / articles / 0103 / 08 / news002.html [Non-Patent Document 3] "CORBA with Shared Memory", https: / / cmsdoc.cern.ch / ~gutleber / drthesis / node54.html [Non-Patent Document 4] Ahmad, Ijaz, et al. "5G security: Analysis of threats and solutions." 2017 IEEE Conference on Standards for Communications and Networking (CSCN). IEEE, 2017. [Non-Patent Document 5] Masayuki Kurata et al., "A Study on Distributed Mobile Core Networks Focusing on NWDAF," Research Report Multimedia Communications and Distributed Processing (DPS), 2023-DPS-195. Summary of the Invention [Problem to be solved by the invention]

[0012] However, since the number and volume of procedures (e.g., Registration, HO, Service Request) that the 5G C-Plane, including the CU (Central Unit)-CP, which is an NF of the RAN (Radio Access Networks), must process varies depending on time or location, it is expected that the number or volume of signaling between each NF will change in real time. In this case, when each option is statically (fixedly) adopted in a distributed mobile network, the following (Problem 1) to (Problem 3) can be considered.

[0013] (Problem 1) In the morning or evening, when there is a lot of movement, it is expected that there will be many group HOs. In this case, if the Locally Administered Edge option or the Autonomous Edge option is adopted, HO will occur frequently every time the NF moves to a different edge site, which will lead to an increase in the processing load on the NF. (Problem 2) When access to an edge application server is concentrated and the number of service requests increases, adopting the Local Offload option will result in increased signaling at both the edge site and the central site. (Problem 3) If the Autonomous Edge option is not adopted, it will not be possible to meet the SLA (Service Level Agreement) for latency-critical applications.

[0014] These issues can be addressed by dynamically placing NFs in appropriate locations, but in the current distributed mobile core network environment, there is a problem in that NFs cannot be dynamically changed because there is no decision-making function or device for dynamically changing the placement of NFs, and no device, interface, or procedure for executing instructions.

[0015] The present disclosure has been made in consideration of the above circumstances, and has an objective of providing a control device, a communication system, and a control method that can support dynamic relocation of NFs. [Means for solving the problem]

[0016] As one configuration example, the control device includes an NF management unit that manages NFs in a distributed mobile core network, a condition management unit that detects that a specified condition related to the NF is not satisfied currently or in the future, and a scheduling unit that schedules a change in the placement of the NF so that the specified condition is satisfied when the condition management unit detects that the specified condition is not satisfied.

[0017] As one configuration example, a communications system having an NF in a distributed mobile core network and a control device, wherein the control device comprises an NF management unit that manages the NF, a condition management unit that detects that a specified condition related to the NF is not satisfied currently or in the future, and a scheduling unit that schedules a change in the placement of the NF so that the specified condition is satisfied when the condition management unit detects that the specified condition is not satisfied, and the NF performs a process of changing its own placement in accordance with the scheduling.

[0018] As one configuration example, a control method in which an NF management unit manages NFs in a distributed mobile core network, a condition management unit detects that a specified condition related to the NF is not satisfied currently or in the future, and a scheduling unit schedules a change in the placement of the NF so that the specified condition is satisfied when the condition management unit detects that the specified condition is not satisfied. Effect of the Invention

[0019] The control device, communication system, and control method according to the present disclosure can support dynamic relocation of NFs. [Brief description of the drawings]

[0020] [Figure 1] 1 is a diagram illustrating a schematic configuration example of a control device compatible with CORBA according to an embodiment. [Figure 2A] FIG. 1 is a diagram illustrating an example of an NF management function according to an embodiment. [Figure 2B] FIG. 2 is a diagram illustrating an example of a metrics / alert management function according to an embodiment. [Figure 2C] FIG. 2 is a diagram illustrating an example of a scheduling function according to the embodiment. [Figure 2D] FIG. 10 is a diagram illustrating an example of a component list management function according to an embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of a procedure of a process performed in a communication system according to an embodiment. [Figure 4] FIG. 2 is a diagram illustrating a process performed in a communication system according to an embodiment. [Diagram 5] FIG. 1 is a diagram illustrating an example of an initial state arrangement of C-Plane NFs in a distributed mobile network according to an embodiment. [Figure 6] A figure showing an example of a post-change state arrangement of a C-Plane NF in a distributed mobile network according to an embodiment. [Figure 7] FIG. 1 is a diagram illustrating a schematic configuration example of a control device that supports normal NF according to an embodiment. [Figure 8] FIG. 2 is a diagram showing an example of a procedure of a process performed in a communication system according to an embodiment. [Figure 9] FIG. 2 is a diagram illustrating a process performed in a communication system according to an embodiment. [Figure 10] FIG. 1 illustrates an example of a distributed mobile network topology. [Figure 11] FIG. 1 is a diagram showing an example of componentization using NF to which CORBA is applied. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0022] A first embodiment will be described. (Example of configuration when CORBA is applied) [Control device] FIG. 1 is a diagram showing an example of a schematic configuration of a control device 11 compatible with CORBA according to an embodiment. The control device 11 includes a processing unit 111 and a communication unit 112 . The processing unit 111 includes an NF management unit 131 having an NF management function, a metrics / alert management unit 132 having a metrics / alert management function, a scheduling unit 133 having a scheduling function, and a component list management unit 134 having a component management function. The communication unit 112 includes an interface 151 .

[0023] In this embodiment, the control device 11 may be provided, for example, inside or outside any of the distributed mobile networks shown in FIG. 9 or other networks. The control device 11 including the processing unit 111 realizes a decision function and a decision device for dynamically changing the placement of the NFs, and also realizes a device for executing instructions. The function of the control device 11 (for example, the function of the processing unit 111) may be configured as the function of a new NF. In this embodiment, CORBA NF is used, and NF componentization (NF components) is applied. Therefore, in this embodiment, the NF manager 131 may be called a component manager. The communication unit 112 corresponds to an ORB. Each NF may exist, for example, on the same server or on a different server. When NFs on the same network are componentized, communication is replaced with shared memory communication.

[0024] The control device 11, through the processing unit 111 (e.g., the metrics / alert management unit 132), obtains metrics such as the NF load, the number or amount of signaling between NFs, or the computing resource capacity of each server from an NF called OAM (Operations Administration and Maintenance) or NRF (Network Repository Function).

[0025] FIG. 2A is a diagram illustrating an example of an NF management function according to an embodiment. FIG. 2B is a diagram illustrating an example of a metrics / alert management function according to an embodiment. FIG. 2C is a diagram illustrating an example of a scheduling function according to an embodiment. FIG. 2D is a diagram illustrating an example of a component list management function according to an embodiment.

[0026] The component list management function has information indicating which NFs should be components. 2D, an example of the relationship between five NFs, NF#1 to NF#5, is shown. Note that this relationship is an example for the purpose of explanation, and is not limited to this. In the example of FIG. 2D, NFs of the same type (for example, NF#1s) can be componentized. Also, NFs to be processed subsequently (for example, NF#1 and NF#2, NF#2 and NF#3, NF#1 and NF#4, NF#4 and NF#5) can be componentized. On the other hand, for example, NF#1 and NF#3, or NF#1 and NF#5 do not require componentization. Here, NFs that have been componentized can communicate via shared memory, and NFs that have not been componentized do not communicate with each other.

[0027] The NF management function (in this embodiment, the component management function) grasps, based on the ServerID (for example, "XXX", "YYY"), which is a server-specific ID, the components deployed on that ServerID, the types of NFs included in the corresponding components, and the InstanceID, which is the ID of the NF (for example, the ID "α" of NF#1, the ID "β" of NF#2, etc.). In addition, the NF management function also grasps the CR capacity (computing resource capacity) of the server. The computing resources are, for example, a CPU (Central Processing Unit) or memory. Here, in this embodiment, the content (management table) managed by the NF management function is updated when the NFs included in the components change.

[0028] The metrics / alert management function periodically acquires metrics from OAM and NRF. When the metrics / alert management function observes (or predicts), for example, that the value of each metric becomes equal to or greater than a predetermined threshold X, it issues a scheduling request (alert notification) to the scheduling function to schedule how the components can be reconfigured so that the value of the corresponding metric becomes equal to or less than a threshold Y (in this embodiment, Y < X). Note that threshold value X and threshold value Y may be, for example, one threshold value for one metric, or may be a combination of threshold values ​​for two or more metrics (collectively, multiple threshold values).

[0029] As the metrics, various indicators may be used, such as the processing load of an NF, the amount of signaling between NFs, or the delay associated with a certain process. In the example of Figure 2B, it is managed that the processing load of NF#1 (ID: α) is 70%, the processing load of NF#2 (ID: β) is 30%, the signaling amount between NF#1 (ID: α) is 0, the signaling amount between NF#2 (ID: α) is 0, and the signaling amount between NF#1 (ID: α) and NF#2 (ID: β) is 1000 [kB / s].

[0030] In this way, the metrics / alert management function has a function (condition management function) of detecting when a predetermined condition regarding an NF is no longer satisfied. In this embodiment, an example of a case where the specified condition is no longer satisfied is a case where the value of each metric becomes equal to or greater than a specified threshold value X, but various other conditions may be used as the specified condition. For example, the predetermined condition may be a condition related to the value of one metric, or a condition related to a combination of values ​​of two or more metrics.

[0031] Furthermore, in this embodiment, a configuration example is shown in which, when a specified condition is no longer satisfied (for example, when the value of each metric becomes equal to or greater than a specified threshold X), scheduling is performed to satisfy a possibly different condition (for example, a condition in which the value of the corresponding metric is equal to or less than a threshold Y) in order to satisfy the specified condition. However, as an example, when a specified condition is no longer satisfied (for example, when the value of each metric becomes equal to or greater than a specified threshold X), scheduling may be performed to satisfy the same condition (for example, a condition in which the value of the corresponding metric is less than the threshold X) in order to satisfy the specified condition.

[0032] When the scheduling function receives an alert notification from the metrics / alert management function, it schedules how to rearrange the NFs contained in each component (i.e., changing the placement of NFs) so that the value of the corresponding metric becomes equal to or less than the threshold Y. In this embodiment, the scheduling function refers to the contents managed by the component list management function to ascertain which NFs are available for components. The scheduling function also ensures that the CR capacity of each server is not exceeded during scheduling. In the example of Figure 2C, the scheduling function is notified that by componentizing the area between NF#1 and NF#4, the value of the corresponding metric will be below threshold Y, and performs such scheduling.

[0033] FIG. 3 is a diagram showing an example of a procedure of processing performed in the communication system P1 according to the embodiment. FIG. 4 is a diagram showing a schematic view of the processing performed in the communication system P1 according to the embodiment.

[0034] In this embodiment, the communication system P1 includes a control device 11 and NF#1 to NF#5. It should be noted that such a configuration of the communication system P1 is an example for the purpose of explanation, and any configuration may be used as the configuration of the communication system P1.

[0035] In this embodiment, the control device 11 and NF#1 to NF#5 are CORBA NFs, each having an ORB. Each ORB has an interface for interacting with other ORBs. This realizes an interface and a procedure for executing componentization instructions.

[0036] In the examples of Figures 3 and 4, the initial state is assumed to be such that NF#1, NF#2, and NF#3 exist on a server with Server ID XXX, and NF#1 and NF#2 can communicate via shared memory Q1 and NF#2 and NF#3 can communicate via shared memory Q2, and that NF#4 and NF#5 exist on a server with Server ID YYY, and NF#4 and NF#5 can communicate via shared memory Q4. Assume that a problem occurs when components are configured in such an initial state, and the control device 11 determines that the problem can be solved by migrating NF#1 on a server whose Server ID is XXX to a server whose Server ID is YYY. In this case, the scheduling unit 133 of the control device 11 schedules such a migration.

[0037] In the example of FIG. 3, only the control device 11, NF#1, NF#2, and NF#4 involved in (processing T1) to (processing T4) of this example are shown. In the example of Fig. 4, the control device 11 and NF#1 to NF#5 are illustrated with a processing unit and a communication unit (ORB) separated, and an interface is shown in the communication unit (ORB). In the example of Fig. 4, NF#1 exists on a server with Server ID XXX in the initial state, but after migration, NF#1 moves to a server with Server ID YYY, and a state is shown in which NF#1 and NF#4 can communicate with each other via shared memory Q3.

[0038] (Process T1) In the initial state, the control device 11 instructs the ORB of NF#1 to provide a component with NF#4 on a server whose Server ID is YYY. (Process T2) The ORB of NF#1 releases (decomponent) the shared memory communication with the ORB of NF#2. (Process T3) After NF#1 is migrated to the server with Server ID YYY, the ORB of NF#1 performs setup (recomponent) for shared memory communication with the ORB of NF#4. (Process T3) Finally, NF#1 notifies the control device 11 that componentization on the server with Server ID YYY has been completed. In the control device 11, the NF management unit 131 that has received this notification updates the NF management table (in this embodiment, the component management table).

[0039] <Example> 5 and 6, a specific example will be described in which the placement of C-Plane NFs in a distributed mobile network changes. FIG. 5 is a diagram illustrating an example of an initial state arrangement of C-Plane NFs in a distributed mobile network according to an embodiment. FIG. 6 is a diagram illustrating an example of a post-change state arrangement of C-Plane NFs in a distributed mobile network according to an embodiment.

[0040] An example of the behavior of the control device 11 and componentized NFs in the communication system P11 will be described with reference to Fig. 5 and Fig. 6. Note that the control device 11 may be disposed in any component (for example, on any server) in the communication system P11. In the examples of Figures 5 and 6, AMF, SMF, CU-CP, and Any are shown as NFs. Here, Any represents a C-Plane NF other than AMF and SMF, and may be, for example, the control device 11 or OAM. In this example, one Any corresponds to the control device 11.

[0041] The initial state shown in FIG. 5 will be described. There are a total of 9 servers. Central site #1 is equipped with five servers (servers with Server IDs 1 to 5) with a unit computing resource capacity (e.g., CPU or memory) of 4. Edge site #1 is equipped with two servers (servers with Server IDs 6 to 7) with a unit computing resource capacity of 3. Edge site #2 is equipped with two servers (servers with Server IDs 8 to 9) with a unit computing resource capacity of 3. In this example, each NF requires only one unit computing resource capacity, so the server at the central site can accommodate four NFs, and the server at the edge site can accommodate three NFs. In this example, it is assumed that it is possible to componentize CU-CPs, AMFs, SMFs, CU-CPs and AMFs, and AMFs and SMFs on the same server.

[0042] The post-change state shown in FIG. 6 will now be described. Assume that the control device 11 observes (or predicts) via the metrics / alert management unit 132 that the amount of inter-site signaling between the AMF and SMF on the server with Server ID 7 in edge site #1 and the AMF on the server with Server ID 1 and the SMF on the server with Server ID 2 in central site #1 will be equal to or greater than threshold value X. As a result, the control device 11 starts scheduling via the scheduling unit 133 to reduce the amount of signaling spanning between central site #1 and edge site #1 to be equal to or less than threshold value Y.

[0043] Then, the scheduling unit 133 determines that the signaling volume will be below threshold Y by migrating and recomponenting the CU-CP on the server with Server ID 1 at central site #1 and the CU-CP on the server with Server ID 2 at edge site #1, and the AMF and SMF on the server with Server ID 7 at edge site #1.

[0044] In this case, in the control device 11, the scheduling unit 133 instructs the ORB of each NF to decomponentize the corresponding NF from an existing component. As a result, each NF releases the component with the NF that is the current component destination, and then moves to the server where the NF is to be placed. After that, each NF performs recomponenting to re-form the component. After completing the recomponenting, each NF sends a completion notification to the control device 11.

[0045] In this example, (Problem 1) can be solved by the control device 11 moving the AMF from the edge site to the central site. Regarding (Problem 2), the control device 11 can place the C-Plane NF at an edge site, thereby confining C-Plane signaling within the edge site, thereby reducing signaling between sites and solving the problem. Problem 3 can be solved by placing NFs at edge sites to accommodate applications that have latency requirements.

[0046] As described above, the communication system according to this embodiment includes NFs in a distributed mobile core network and the control device 11. The control device 11 includes an NF management unit 131, a condition management unit (in this embodiment, a metrics / alert management unit 132), a scheduling unit 133, and a component list management unit . The NF management unit 131 manages the NFs. In this embodiment, the NF management unit 131 manages a component which is a collection of multiple NFs. The condition management unit detects when a predetermined condition regarding the NF is not satisfied currently or in the future. When the condition management unit detects that the predetermined condition is not satisfied, the scheduling unit 133 performs scheduling for changing the placement of the NFs (determining dynamic placement of the NFs) so that the predetermined condition is satisfied. The component list management unit 134 manages the list of components.

[0047] In this embodiment, the NF is separated into a communication unit having an interface and a processing unit. The NF performs processing to change its own placement according to the scheduling. In this embodiment, each NF communicates with the control device 11 via a communication unit (interface) and performs processing to change the location of itself (the NF) in response to an instruction from the control device 11.

[0048] As described above, in this embodiment, each NF has a function of receiving an instruction related to dynamic NF placement from the control device 11 and performing processing according to the instruction. In this embodiment, in a componentized NF, a communication unit (in this embodiment, an ORB) is provided with an interface with the control device 11. The interface receives instructions related to components, instructions related to recomponents, or instructions related to decomponents from the control device 11.

[0049] In addition, the NF has, for example, a function to receive a predetermined instruction from an external device, and a function to perform a process to change its own placement in response to the instruction when the instruction is received. The external device is not limited to the control device 11 according to the present embodiment, and may be any device. In this case, the interface of the communication unit is not limited to the control device 11 according to the present embodiment, and may be capable of communicating with such an external device. Here, in this embodiment, a case has been described in which componentization using CORBA is used, but componentization using other techniques may also be used.

[0050] In the communication system according to this embodiment, in a distributed mobile core network, the control device 11 can assist in dynamically changing the arrangement of NFs, thereby satisfying evaluation indicators such as SLAs related to, for example, processing load, signaling volume, or delay.

[0051] The second embodiment will be described. (Configuration example when applying a normal NF) With reference to FIGS. 7 to 9, the case of applying a normal NF will be described. In this example, differences from the case of applying CORBA according to FIGS. 1 to 6 will be described in detail, and detailed descriptions of the same points will be omitted.

[0052] FIG. 7 is a diagram showing a schematic configuration example of a control device 511 corresponding to a normal NF according to the embodiment. The control device 511 includes an NF management unit 531 having an NF management function, a metrics / alert management unit 532 having a metrics / alert management function, and a scheduling unit 533 having a scheduling function. Here, in this example, the control device 511 does not have a component list management function.

[0053] The NF management function manages normal NFs. When the metrics / alert management function observes (or predicts) that the value of each metric becomes equal to or greater than a predetermined threshold X, it issues a scheduling request (alert notification) to the scheduling function to schedule whether moving the normal NF to any location will make the value of the corresponding metric become equal to or less than a threshold Y (Y < X). When the scheduling function receives an alert notification from the metrics / alert management function, it schedules how to reorganize the NFs (which NF should be moved to which server) so that the value of the corresponding metric becomes equal to or less than the threshold Y.

[0054] FIG. 8 is a diagram showing an example of a procedure of a process performed in the communication system P51 according to the embodiment. FIG. 9 is a diagram showing a schematic diagram of the processing performed in the communication system P51 according to the embodiment. In this embodiment, a communication system P51 includes a control device 511 and NF#1 to NF#5. It should be noted that such a configuration of the communication system P51 is merely an example for the purpose of explanation, and any configuration may be used as the configuration of the communication system P51. Here, in this embodiment, in control device 511 and NF#1 to NF#5, the function of the processing unit and the function of the communication unit are integrated.

[0055] In the examples of Figures 8 and 9, it is assumed that, as an initial state, NF#1, NF#2, and NF#3 exist on a server with Server ID XXX, and NF#4 and NF#5 exist on a server with Server ID YYY. Assume that a problem occurs in such an initial state, and the control device 11 determines that the problem can be solved by migrating NF#1 on a server whose Server ID is XXX to a server whose Server ID is YYY. In this case, the scheduling unit 533 of the control device 511 schedules such a migration.

[0056] In the example of FIG. 8, only the control device 511, NF#1, NF#2, and NF#4 are shown. Moreover, the example of Fig. 9 illustrates the control device 511 and NF#1 to NF#5. Moreover, the example of Fig. 9 illustrates a state in which NF#1 exists on a server with a server ID of XXX in the initial state, but after migration, NF#1 has moved to a server with a server ID of YYY. In this embodiment, NFs communicate with each other using HTTP.

[0057] (Process T11) In the initial state, the control device 511 instructs NF#1 to perform migration to a server whose Server ID is YYY. (Process T12) After NF #1 has been migrated to the server with the server ID YYY, NF #1 notifies the control device 511 that the movement (migration) has been completed. In the control device 511, the NF management unit 531 that has received this notification updates the NF management table.

[0058] Here, these interactions (instructions and notification of completion) are performed using SBI, which is standard in NF. These notifications may be made directly from the control device 511, for example, or may be made via a Network Exposure Function (NEF).

[0059] <Example> Even in the case of a normal NF, (Problem 1), (Problem 2), and (Problem 3) can be solved by performing migration of the NF in a manner generally similar to that shown in, for example, Figures 5 and 6.

[0060] That is, in this example, the scheduling unit 533 determines that the signaling volume will be below threshold Y by migrating the CU-CP on the server with Server ID 1 at central site #1 and the CU-CP on the server with Server ID 2, and the AMF and SMF on the server with Server ID 7 at edge site #1.

[0061] In this case, the control device 511 instructs each of the relevant NFs to migrate to the server to which it should be placed, via the scheduling unit 533. After that, each of the relevant NFs sends a completion notification to the control device 511 after completing the migration.

[0062] As described above, in the communication system according to this embodiment, in a distributed mobile core network, the control device 511 can support dynamic relocation of NFs, thereby making it possible to satisfy evaluation indicators such as SLAs relating to processing load, signaling volume, or delay.

[0063] [About the above embodiment] As a result, it will be possible to improve the overall service quality in wireless networks, for example, and thereby contribute to Goal 9 of the United Nations-led Sustainable Development Goals (SDGs), which is to "build resilient infrastructure, promote sustainable industrialization and foster innovation."

[0064] A program for implementing the functions of any of the components of any of the above-described devices may be recorded in a computer-readable recording medium, and the program may be read into a computer system and executed. The term "computer system" as used herein includes hardware such as an operating system or peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CDs (Compact Discs)-ROMs (Read Only Memory), and storage devices such as hard disks built into computer systems. The term "computer-readable recording medium" also refers to storage devices that hold a program for a certain period of time, such as volatile memory inside a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. The volatile memory may be, for example, a RAM (Random Access Memory). The recording medium may be, for example, a non-transitory recording medium.

[0065] The above-mentioned program may be transmitted from a computer system in which the program is stored 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 a function of transmitting information, such as a network such as the Internet or a communication line such as a telephone line. The above program may be for implementing some of the above functions. Furthermore, the above program may be a so-called differential file that can implement the above functions in combination with a program already recorded in the computer system. The differential file may be called a differential program.

[0066] In addition, the function of any of the components in any of the above-described devices may be realized by a processor. For example, each process in the embodiment may be realized by a processor that operates based on information such as a program and a computer-readable recording medium that stores information such as a program. Here, the functions of each part of the processor may be realized by individual hardware, or the functions of each part may be realized by integrated hardware. For example, the processor may include hardware, and the hardware may include at least one of a circuit that processes digital signals and a circuit that processes analog signals. For example, the processor may be configured using one or more circuit devices mounted on a circuit board, or one or both of one or more circuit elements. An IC (Integrated Circuit) or the like may be used as the circuit device, and a resistor or a capacitor or the like may be used as the circuit element.

[0067] Here, the processor may be, for example, a CPU. However, the processor is not limited to a CPU, and various processors such as a GPU (Graphics Processing Unit) or a DSP (Digital Signal Processor) may be used. The processor may be, for example, a hardware circuit using an ASIC (Application Specific Integrated Circuit). The processor may be, for example, a plurality of CPUs, or a hardware circuit using a plurality of ASICs. The processor may be, for example, a combination of a plurality of CPUs and a hardware circuit using a plurality of ASICs. The processor may include, for example, one or more of an amplifier circuit or a filter circuit that processes an analog signal.

[0068] Although the embodiments of this disclosure have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and designs that do not deviate from the gist of this disclosure are also included. [Explanation of symbols]

[0069] 11, 511...control device, 111...processing unit, 112...communication unit, 131, 531...NF management unit, 132, 532...metrics / alert management unit (condition management unit), 133, 533...scheduling unit, 134...component list management unit, 151...interface, P1, P11, P51...communication system, Q1 to Q4...shared memory< / corba>

Claims

1. An NF management unit that manages NFs in a distributed mobile core network; a condition management unit for detecting whether a predetermined condition regarding the NF is not satisfied currently or in the future; a scheduling unit that schedules a change in the placement of the NFs so that the predetermined condition is satisfied when the condition management unit detects that the predetermined condition is not satisfied; A control device comprising:

2. The NF is separated into a communication unit having an interface and a processing unit, The NF management unit manages a component which is a collection of a plurality of the NFs, The control device further includes a component list management unit that manages a list of the components. The control device according to claim 1 .

3. A communication system having an NF in a distributed mobile core network and a control device, The control device includes: An NF management unit that manages the NF; a condition management unit for detecting whether a predetermined condition regarding the NF is not satisfied currently or in the future; a scheduling unit that schedules a change in the placement of the NFs so that the predetermined condition is satisfied when the condition management unit detects that the predetermined condition is not satisfied; Equipped with The NF performs a process of changing its own placement in accordance with the scheduling. Communication systems.

4. The NF management unit manages the NFs in the distributed mobile core network; A condition management unit detects that a predetermined condition regarding the NF is not satisfied currently or in the future; a scheduling unit, when the condition management unit detects that the predetermined condition is not satisfied, scheduling a change in the placement of the NFs so that the predetermined condition is satisfied; Control methods.

Images