WO2024004177A1 - Resource sharing within cloud group formed of plurality of clouds - Google Patents

Abstract

The present invention provides a control device comprising one or more processors. The one or more processors select, from among existing applications deployed to a primary cloud within a cloud group formed of a plurality of clouds, a target application to be deployed to a secondary cloud within the cloud group. The one or more processors deploy a part of or all of CNFs for building the target application to the secondary cloud. The one or more processors obtain information about the Radio Resource Control (RRC) state of one or more user terminals having established PDU session with the target application deployed to the primary cloud. The one or more processors issue an instruction to switch a route of the PDU session from a route to the target application deployed to the primary cloud to a route to the target application deployed to the secondary cloud according to the RRC state.

Description

Resource sharing within a cloud group formed by multiple clouds

The present disclosure relates to resource sharing within a cloud group formed by multiple clouds.

With the increase in demand for IoT (Internet of Things), VR (Virtual Reality), AR (Augmented Reality), video distribution applications, etc., edge computing, which is a distributed architecture, has been attracting attention in recent years. Edge computing is a distributed computing system that performs at least some of its processing in an edge cloud built on edge servers installed near user terminals (UEs), instead of a central cloud built on a central data center. It is ing. By using the edge cloud, the processing for providing services to user terminals, which was concentrated in the center cloud, is distributed to the edge cloud, thereby distributing the processing load.

Japanese Patent Application Publication No. 2017-143365

However, due to constraints such as where the edge server is installed, the computing resources allocated to the edge cloud may not be sufficient, and it may be difficult to stably provide services to user terminals.

A control device according to one aspect of the present disclosure includes one or more processors.
The one or more processors select a target application to be deployed to a secondary cloud in the cloud group from existing applications deployed in a primary cloud in a cloud group formed by a plurality of clouds.
Further, the one or more processors deploy all or part of a CNF (Containerized Network Function) that constructs the target application to a secondary cloud in the cloud group.
The one or more processors also monitor the RRC (Radio Resource Control) state of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud. Get information.
The one or more processors may also transmit the PDU from a route to the target application deployed in the primary cloud to a route to the target application deployed in the secondary cloud, depending on the RRC state. Instructs to switch the session route.

A control method according to an aspect of the present disclosure includes a control method that selects a target application to be deployed to a secondary cloud in the cloud group from an existing application deployed in a primary cloud in a cloud group formed by a plurality of clouds, using a processor. Including using and selecting.
Further, the control method includes deploying all or part of a CNF (Containerized Network Function) that constructs the target application to a secondary cloud in the cloud group using a processor.
The control method also includes information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud. , using a processor.
The control method also includes controlling the PDU session from a route to the target application deployed in the primary cloud to a route to the target application deployed in the secondary cloud, depending on the RRC state. This includes instructing the switching of routes using a processor.

A non-transitory computer-readable medium according to one aspect of the present disclosure records a program.
When the program is loaded by a computer, one or more processors of the computer are configured to deploy an existing application deployed in a primary cloud in a cloud group formed by a plurality of clouds to a secondary cloud in the cloud group. Select the target application you want to use.
Further, the one or more processors deploy all or part of a CNF (Containerized Network Function) that constructs the target application to a secondary cloud in the cloud group.
The one or more processors also monitor the RRC (Radio Resource Control) state of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud. Get information.
The one or more processors may also transmit the PDU from a route to the target application deployed in the primary cloud to a route to the target application deployed in the secondary cloud, depending on the RRC state. Instructs to switch the session route.

FIG. 1 is a conceptual diagram showing a cloud group to which a control device according to the present disclosure is applied. FIG. 2 is a diagram showing the relationship between services and applications in a microservice architecture. FIG. 3 is a functional block diagram illustrating a configuration example of a control device according to the present disclosure. FIG. 4A is a diagram for explaining an application example of the control device according to the present disclosure. FIG. 4B is a diagram for explaining an application example of the control device according to the present disclosure. FIG. 5 is a flowchart illustrating an example of the operation of the control device according to the present disclosure. FIG. 6 is a diagram illustrating an example of a processing sequence in the control device according to the present disclosure. FIG. 7 is a block diagram showing a configuration example of the control device shown in FIG. 3.

Embodiments of the present disclosure will be described in detail below with reference to the drawings.
A control device according to the present disclosure controls resource sharing within a cloud group formed by a plurality of clouds. As discussed below, the controller may be an orchestrator.

(One embodiment)
FIG. 1 is a conceptual diagram showing a cloud group to which a control device 100 according to the present disclosure is applied. The cloud group includes a plurality of (L pieces, L is an integer) edge clouds.
FIG. 1 shows an example in which a cloud group includes four (L=4) edge clouds.
Applications for providing various services to user terminals (not shown) within a coverage area formed by one or more Radio Units (RUs) may be deployed in each edge cloud. The user terminal is an ICT (Information and Communication Technology) device that can execute an application for receiving services and can communicate. Examples of user terminals include portable PCs (Personal Computers) such as smartphones and tablet terminals. The user terminal may be a non-portable device such as a desktop PC.

A cloud group is formed from multiple edge clouds. A cloud group is formed, for example, by edge clouds built on edge servers that are geographically close to each other. Note that a cloud group does not necessarily have to be formed only by edge clouds that are geographically close to each other. For example, a cloud group may be formed by edge clouds built on edge servers installed in logically close locations.
Further, the cloud group may include a center cloud built on the central data center.
Further, the cloud group may include a cloud built on a regional data center.
Hereinafter, the edge cloud, center cloud, etc. included in a cloud group will be simply referred to as "cloud".
The control device 100 according to the present disclosure may be installed in a data center where these clouds are constructed, or may be installed in a data center outside the cloud group.

Before describing the control device 100 according to the present disclosure, the relationship between services provided to user terminals and applications deployed in the cloud will be described using FIG. 2. The application is an application for providing a service to a user terminal.
In the present disclosure, services provided to user terminals are constructed using a microservice architecture.

FIG. 2 is a diagram showing the relationship between services and applications (hereinafter also referred to as "APP") in a microservice architecture.
As shown in FIG. 2, a service is constructed from one or more applications. The number of applications that construct one service varies depending on the service.
Each application is built from one or more Containerized Network Functions (CNFs).
CNF operates on "Kubernetes" (registered trademark), for example. Kubernetes is open source software (OSS) that automatically configures and manages containerized services.
The number of CNFs to build one application may vary depending on the application and design.
CNF running on Kubernetes is constructed from one or more Pods. A Pod is the smallest unit of application that can run on Kubernetes. Multiple Pods are operationally managed by Kubernetes. Pods that operate on CNF have a self-repair function; for example, when a certain Pod stops operating, another Pod is activated and the CNF function self-repairs.
Each Pod is constructed from one or more containers.

The use of microservice architecture is also being considered in 5G (fifth generation mobile communication system).
Examples of the above-mentioned services in 5G include a radio access network (RAN) and a core network (CN).
When the service is RAN, the Central Unit (CU) and Distributed Unit (DU) correspond to the application.
Furthermore, if the service is a CN, a Service Network Function (SNF) that constructs the CN, such as an AMF (Access and Mobility Management Function) or a UPF (User Plane Function), corresponds to the application.

When the application indicated by APP#1 is a CU, the CNF indicated by CNF#1 can be set as a CU-CP (Control Plane), and the CNF indicated by CNF#2 can be set as a CU-UP (User Plane).
CU-CP includes radio resource control (RRC). CU-UP includes SDAP (Service Data Adaptation Protocol) and PDCP (Packet Data Convergence Protocol) related to the user plane.
The CU-CP and CU-UP are capable of functionally linked communication via the E1 interface. Both CU-CP and CU-UP can be connected to DU with F1 interface.

Furthermore, examples of services other than the above-mentioned RAN and CN include a web distribution service, a game provision service, a video distribution service, a music distribution service, a monitoring service, a navigation service, an automatic driving service, an email provision service, and a sensor service.
Examples of applications that provide these services include a web distribution application, a game provision application, a video distribution application, a music distribution application, a monitoring execution application, a navigation application, an automatic driving application, a mail provision application, and a sensor execution application.

FIG. 3 is a functional block diagram showing a configuration example of the control device 100 according to the present disclosure.
The control device 100 includes a resource monitoring section 110, a resource determination section 120, an application selection section 130, a secondary cloud determination section 140, a CNF selection section 150, a path switching instruction section 160, and a deployment section 170.

The resource monitoring unit 110 monitors resource usage of clouds within a cloud group. Monitoring may be performed periodically, or may be performed at the timing when a request to create a new application, which will be described later, is notified to one of the clouds.
Note that applications already deployed in the cloud and new applications are built using microservice architecture. That is, these applications are constructed from one or more CNFs.
The resource usage status includes, for example, information on the total number of CNFs that can be placed (deployed) in the cloud and the total number of CNFs of all applications actually deployed on the cloud. The total number of CNFs that can be placed in the cloud may be determined by the cloud's computing resources. The total number of CNFs for all applications actually deployed in the cloud is the total number of CNFs already deployed in the cloud.

The resource determination unit 120 determines whether the cloud has the resources to deploy all the CNFs that construct the new application when requesting the creation of a new application to the cloud in the cloud group. In other words, the resource determination unit 120 determines whether or not the resources of the cloud that has received the request to create a new application are tight. Hereinafter, the cloud that received the request to create a new application will be referred to as the "primary cloud." A method for determining whether or not resources are tight in the resource determination unit 120 will be described later.

The resource determination unit 120 receives, for example, directly from the primary cloud that the primary cloud has been requested to create a new application. The resource determination unit 120 may receive a request to create a new application in the primary cloud from a management device that manages registration of new applications.
The new application creation request includes information about the new application (hereinafter also referred to as "application information"). The application information includes information on the total number of CNFs for constructing new applications.

For example, the resource determination unit 120 can determine whether the primary cloud has resources for deploying all CNFs for building a new application, using the following information (1) and (2). can.
(1) Maximum number of CNFs that can be placed in the primary cloud: f _max
(2) Total number of CNFs requested to be placed in the primary cloud: f _sum
f _max and f _sum are counted in units of one CNF. That is, f _max and f _sum represent how many CNFs they correspond to.

f _max is the maximum number of CNFs that can be placed in the primary cloud. In other words, f _max is the sum of the number of CNFs already placed in the primary cloud and the number of CNFs that can be further placed in the primary cloud. The maximum number of CNFs that can be placed in the primary cloud may be determined by the primary cloud's computing resources.
Furthermore, f _sum is the sum of the number of CNFs that have already been placed in the primary cloud plus the number of CNFs that will construct a new application that has been requested to be placed in the primary cloud. In other words, the total number of CNFs f _sum is the total number of CNFs scheduled to be placed in the primary cloud when all CNFs for building a new application are placed (deployed) in the primary cloud.

For example, the resource determination unit 120 determines whether the primary cloud has resources for deploying all CNFs that construct a new application, based on the resource usage ratio R defined by the ratio f _sum /f _max . judge.

If the resource usage ratio R is less than 1, that is,

In this case, it is determined that the primary cloud has the resources to deploy all the CNFs that build the new application.

On the other hand, if the resource usage ratio R is greater than 1, that is,

In this case, the resource determination unit 120 determines that the primary cloud does not have the resources to deploy all the CNFs that construct the new application.
If the resource usage ratio R>1, the resource determination unit 120 notifies the application selection unit 130 of a request to select an application to be deployed in a cloud different from the primary cloud (hereinafter referred to as “secondary cloud”). In the following explanation, the application that will be deployed to the secondary cloud is also referred to as the "target application."

Note that even if the primary cloud has the resources to deploy all the CNFs for building a new application, some CNFs may be deployed to the secondary cloud. In other words, even if the resources of the primary cloud are not actually in short supply, the resource determining unit 120 may make a hypothetical determination that the resources are in short supply only in a preset situation. As a result, it is possible to deploy a part of the CNF to the secondary cloud in advance before a resource shortage occurs, thereby delaying the timing at which the primary cloud's resources become scarce. For example, the resource determination unit 120 hypothetically determines that resources are tight in a situation where it is expected that new application creation requests will continue. The situations in which it is determined that resources are tight are not limited to this.
As described above, the resource determination unit 120 determines whether or not the resources of the primary cloud are tight, and if the resources are tight, the resource determination unit 120 requests the application selection unit 130 to select an application to be deployed to the secondary cloud. Notice. Note that the method used by the resource determination unit 120 to determine whether or not resources are tight is not particularly limited.

When the application selection unit 130 receives a request to select an application (target application) to be deployed to the secondary cloud from the resource determination unit 120, the application selection unit 130 selects the target application based on the operating status of the existing application deployed to the primary cloud. do.
The operating status includes at least one of the operating time of the application, the number of user terminals connected to the application, the amount of data of the application, and the throughput of the application. The application selection unit 130 can obtain information about the operating time by, for example, inquiring a management device that manages the cloud. The application selection unit 130 can obtain information about the operating time by, for example, inquiring a management device that manages the cloud. Further, the application selection unit 130 can obtain information about the number of user terminals connected to the application, the amount of data of the application, and the throughput of the application by, for example, inquiring the UPF.

When using the operating time of an application as the operating status, the application selection unit 130 selects the application with the shortest operating time as the target application. When using the number of user terminals connected to an application as the operating status, the application selection unit 130 selects the application with the least number of user terminals as the target application. When using the amount of data of an application as the operating status, the application selection unit 130 selects the application with the least amount of data as the target application. When using the throughput of an application as the operating status, the application selection unit 130 selects the application with the lowest throughput as the target application.

As a result, applications with low uptime are relocated to the secondary cloud, while applications with long uptime are maintained in the primary cloud. Further, applications with a small number of connected user terminals are relocated to the secondary cloud, and applications with a large number of connected user terminals are maintained in the primary cloud. In addition, applications with small amounts of data are relocated to the secondary cloud, while applications with large amounts of data are kept in the primary cloud. Additionally, applications with low throughput are relocated to the secondary cloud, while applications with high throughput are kept in the primary cloud. In this way, by determining the target application according to the operating status of the application in the primary cloud, an application that will have a low impact on usability when relocated to the secondary cloud is determined as the target application.

Note that the application selection unit 130 may use the instantaneous operating status in a situation where primary cloud resources are tight, or may use the average operating status within a time span such as one day, several days, or one week. May be used. When the operating status in a situation where primary cloud resources are tight is used, it is possible to suppress the impact on user terminals immediately after existing applications are relocated to the secondary cloud. When the average operating status within a time span such as one day, several days, or one week is used, the influence on the user terminal within the time span can be suppressed.

In addition to the existing applications deployed in the primary cloud, the application selection unit 130 may also use the operating status of existing applications deployed in the clouds in the cloud group. In this case, the application is selected as the target application because the application's operating time, the number of user terminals connected to the application, the amount of data of the application, or the throughput of the application are temporarily low in the primary cloud. This can be prevented.

After determining the target application, the application selection unit 130 notifies the secondary cloud determination unit 140 of information on the total number of CNFs (f _total ) for constructing the target application. Further, the application selection unit 130 notifies the path switching instruction unit 160 of information about the target application.

The secondary cloud determining unit 140 determines a secondary cloud within the cloud group in which at least a portion of the CNF for constructing the target application will be placed. An example of determining the secondary cloud will be described later. Furthermore, the secondary cloud determining unit 140 sets the number (f) of CNFs to be placed in the secondary cloud among all CNFs that construct the target application. For example, the secondary cloud determining unit 140 sets the number of surplus CNFs (f _d ) that cannot be deployed to the primary cloud to the number of CNFs (f) to be placed in the secondary cloud.

The secondary cloud determining unit 140 calculates the number of surplus CNFs (f _d ) using, for example, the following formula.

The number of surplus CNFs (f _d ) calculated using equation (3) is the number of CNFs that cannot be deployed to the primary cloud when attempting to deploy as many CNFs as possible to the primary cloud among the CNFs that construct the target application. The number of pieces.

Note that the method for calculating the number of surplus CNFs (f _d ) is not limited to the above. For example, the number of CNFs that can be placed in the primary cloud is set in advance as a threshold value (f _threshold , f _threshold < f _max ), and the number (f _sum - f _threshold ) exceeding this threshold value (f _threshold ) is set as surplus. It may also be the number of CNFs (f _d ).

In this case, (f _max - f _threshold ) free resources are secured in the primary cloud for each CNF. As a result, when there is an urgent request to create a new application in the primary cloud, there is a high possibility that the primary cloud will be able to respond to the urgent request immediately.
The secondary cloud determining unit 140 sets the thus calculated number of surplus CNFs (f _d pieces) that cannot be deployed to the primary cloud as the number (f) of CNFs to be placed in the secondary cloud. Note that the secondary cloud determining unit 140 may set the number of all CNFs (f _total ) that constructs the target application to the number of CNFs (f). In this case, all CNFs that construct the target application will be deployed to the secondary cloud.

The secondary cloud determining unit 140 determines the secondary cloud based on, for example, the size of free resources when a cloud other than the primary cloud in the cloud group deploys f CNFs. The size of empty resources is counted in units of one CNF. The secondary cloud determining unit 140 can obtain information about the resource usage status of clouds in the cloud group from the resource determining unit 120.

Note that the secondary cloud determining unit 140 may determine the secondary cloud based not only on the size of free resources but also on the geographical (or logical) distance between the primary cloud and a cloud other than the primary cloud. .
For example, if there are multiple clouds with the same size of free resources, the secondary cloud determining unit 140 determines the cloud with the smallest distance from the primary cloud as the secondary cloud among the multiple clouds with the same size of free resources. It's okay.

Additionally, the secondary cloud determining unit 140 may determine the secondary cloud based on the geographical (or logical) distance between the primary cloud and a cloud other than the primary cloud. For example, the secondary cloud determining unit 140 may determine the cloud with the smallest distance from the primary cloud as the secondary cloud, regardless of the size of free resources. When determining the secondary cloud based on distance, it is possible to reduce the delay time caused by PDU session switching, which will be described later.

Additionally, the secondary cloud determining unit 140 may determine the secondary cloud based on a delay time due to switching of a PDU session path, which will be described later. For example, the secondary cloud determining unit 140 estimates the delay time caused by switching the path of the PDU session based on the geographical location of the server where each cloud is installed, the specifications of the computing resources of each cloud, etc. can do. The secondary cloud determining unit 140 may determine the cloud with the minimum delay time as the secondary cloud. Thereby, the influence caused by switching the PDU session path can be minimized.

Further, the secondary cloud determining unit 140 may determine the secondary cloud based on the current free resource size of clouds other than the primary cloud in the cloud group. In this case, the secondary cloud determining unit 140 may determine the secondary cloud and then set the number (f) of CNFs to be placed in the secondary cloud. This also allows the maximum number of CNFs to be placed in the secondary cloud.
Further, the secondary cloud determining unit 140 may always determine a specific cloud within the cloud group as the secondary cloud. In this case, the time it takes for a new application to be deployed and service provision to start can be shortened.

The secondary cloud determination unit 140 notifies the deployment unit 170 of information on the determined secondary cloud. Further, the secondary cloud determining unit 140 notifies the CNF selecting unit 150 of information about the number (f) of CNFs to be placed in the secondary cloud.

The CNF selection unit 150 acquires information about the characteristics of the CNF that constructs the target application, for example, from a management device that manages application registration. The characteristics of the CNF are information representing the role played by the CNF when a service is provided, such as, for example, the CNF is related to user data or control data.
CNFs related to user data are accessed directly from the user terminal. CNFs related to user data are directly connected to user terminals. CNFs associated with control data are typically not directly accessed by user terminals, but may be connected to CNFs associated with user data.

The CNF selection unit 150 also acquires information on the number (f) of CNFs placed in the secondary cloud from the secondary cloud determination unit 140.
The CNF selection unit 150 selects CNFs to be placed in the secondary cloud from among the CNFs that construct the target application, based on the priority order of the CNFs, in descending order of the priority order of the CNFs. In the following, the CNF placed in the secondary cloud will also be referred to as "target CNF."

The CNF priorities may be set in advance. For example, CNF priorities may be set based on CNF characteristics. The characteristics of the CNF are information representing the role played by the CNF when a service is provided, such as whether the CNF is related to user data or control data.
When priorities are set focusing on functions related to user data and functions related to control data, the priority of CNFs related to user data is higher than the priority of CNFs related to control data. Set.

Based on the CNF priorities set in this way, when the CNF selection unit 150 selects CNFs to be placed in the secondary cloud, CNFs that can be directly accessed from user terminals are preferentially placed in the primary cloud. It becomes like this. Therefore, the influence of communication delay when a user terminal receives service provision can be suppressed.

Upon selecting a target CNF, the CNF selection unit 150 notifies the deployment unit 170 of information on the target CNF.
Note that if the number (f) of CNFs arranged in the secondary cloud, which is notified from the secondary cloud determining unit 140, is equal to the total number of CNFs that construct the target application, the CNF selecting unit 150 selects all CNFs of the target application. Select.

The route switching instruction unit 160 acquires information about the selected application from the application selection unit 130. The application selected by the application selection unit 130 is an application (target application) to be deployed to the secondary cloud.
The path switching instruction unit 160 acquires information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud. . The path switching instructing unit 160 can obtain information on the RRC state from, for example, an AMF (Access and Mobility management Function).

As RRC states, 3GPP Release 15 defines RRC_CONNECTED, RRC_IDLE, and RRC_INACTIVE (see 3GPP TS 38.300).
RRC_CONNECTED is a state in which an RRC (Radio Resource Control) connection between the RAN and the user terminal has been set. In RRC_CONNECTED, the location of the user terminal is known by the RAN at cell level. In the RRC_CONNECTED state, the context of the user terminal is saved in the RAN and CN.

RRC_IDLE is a state in which no RRC connection is set. In the RRC_IDLE state, the location of the user terminal is not known by the RAN at the cell level, but the location of the user terminal is known by the CN at the location registration area level. The location registration area level corresponds to the tracking area in LTE (Long Term Evolution). In RRC_IDLE, the context of the user terminal is not held in the RAN, but the context of the user terminal is saved in the CN.

Similar to RRC_IDLE, RRC_INACTIVE is a state in which an RRC connection is not set. In RRC_INACTIVE, the context of the user terminal is saved in the RAN and CN. The state of the user terminal is almost the same as the state of the user terminal in RRC_IDLE. Therefore, the power saving state is maintained in the user terminal. Furthermore, since the context of the user terminal is also held in the RAN, the number of signals required for the procedure for returning to RRC_CONNECTED can be reduced.

The route switching instruction unit 160 instructs switching of the PDU session route from the route to the target application deployed in the primary cloud to the route to the target application deployed in the secondary cloud, according to the RRC state. .
Hereinafter, the path for forming a PDU session from the user terminal to the target application deployed in the primary cloud will also be referred to as a "first path." In addition, a path for forming a PDU session from a user terminal to a target application relocated to a secondary cloud is also referred to as a "second path." The route switching instructing unit 160 instructs to switch the route of the PDU session from the first route to the second route according to the RRC state.
The route switching instructing unit 160 instructs the deploying unit 170 to switch the route, for example, when the number of user terminals whose RRC status is RRC_CONNECTED is equal to or less than a predetermined threshold. Here, the user terminal is a user terminal with which a PDU session has been established with a target application deployed in the primary cloud.

Depending on what value the predetermined threshold is set to, it is possible to control the number of user terminals that are affected by switching the path of the PDU session from the first path to the second path. The larger the predetermined threshold value is, the larger the number of affected user terminals is, and the smaller the predetermined threshold value is, the smaller the number of affected user terminals is.
The predetermined threshold value may be set to a fixed value. In this case, the maximum number of affected user terminals can be made uniform regardless of the type of target application.

Further, the predetermined threshold value may be set depending on the QoS (Quality of service) required of the target application.
Examples of QoS include high-speed bandwidth guarantee, high-speed best effort, low-speed bandwidth guarantee, and low-speed best effort. The higher the QoS of the target application, the smaller the predetermined threshold may be set. QoS is higher in the order of high-speed bandwidth guarantee, high-speed best effort, low-speed bandwidth guarantee, and low-speed best effort.
For example, in a video distribution application, since the amount of data is large, high-speed bandwidth guarantee or high-speed best effort is required as QoS. On the other hand, in mail providing applications, real-time performance is less important, so a low best effort QoS is sufficient.
In such a case, for example, the predetermined threshold value for the video distribution application may be set to "10", and the predetermined threshold value for the mail provision application having a lower QoS than the video distribution application may be set to "100".

The route switching instruction unit 160 compares the number of user terminals that are RRC_CONNECTED among the user terminals for which a PDU session has been established between a predetermined threshold value "10" and the video distribution application. The route switching instruction unit 160 instructs switching of the PDU session route when the number of user terminals that are RRC_CONNECTED among the user terminals that have established a PDU session with the video distribution application is 10 or less. . On the other hand, if the number of user terminals in RRC_CONNECTED among the user terminals for which a PDU session has been established with the video distribution application is 11 or more, the path switching instruction unit 160 does not output a switching instruction. Therefore, the PDU session passing through the first route is maintained until the number of user terminals in RRC_CONNECTED becomes 10 or less.

The route switching instruction unit 160 compares the number of user terminals that are RRC_CONNECTED among the user terminals for which a PDU session has been established between the predetermined threshold value "100" and the mail providing application. The route switching instruction unit 160 instructs switching of the PDU session route when the number of user terminals that are RRC_CONNECTED among the user terminals that have established a PDU session with the email providing application is 100 or less. . Therefore, even if the number of user terminals that have established PDU sessions with the email providing application is 99, the PDU session route will be switched from the first route to the second route. .

In this way, by setting a predetermined threshold according to the QoS required by the application, it is possible to control for each application the number of user terminals whose PDU sessions are temporarily disconnected due to route switching. can. In the route switching instruction unit 160, a predetermined threshold is compared with the number of RRC_CONNECTED, and when the number of RRC_CONNECTED is less than or equal to the predetermined threshold, switching of the route is instructed.

The higher the QoS of an application, the smaller the predetermined threshold value can be set. The lower the QoS of an application, the larger the predetermined threshold value may be set. In this case, even if the number of RRC_CONNECTED is the same, an application with a high QoS will not switch the PDU session route, but an application with a low QoS will switch the PDU session route.

Furthermore, the predetermined threshold value may be set depending on the priority level required of the new application. The predetermined threshold value may be set to a larger value as the priority required for the new application is higher. For example, if the new application has a high degree of urgency, such as an autonomous driving application, and needs to be created in the primary cloud immediately, the predetermined threshold may be set to a very large value. In this case, even if the number of user terminals whose RRC status is RRC_CONNECTED is large, switching of the PDU session path will be instructed.

Furthermore, the predetermined threshold value may be set depending on the time period in which the target application is used. For example, if it is expected that the number of user terminals using the target application is greater during the daytime hours than at nighttime hours, the predetermined threshold value for daytime hours may be set to a larger value than the predetermined threshold value for nighttime hours. may be set.

The deployment unit 170 deploys the f target CNFs selected by the CNF selection unit 150 to the secondary cloud. Further, upon receiving the path switching instruction from the path switching instruction section 160, the deploying section 170 executes processing for establishing a PDU session between the user terminal and the target application deployed in the secondary cloud. Additionally, the deployment unit 170 executes processing for deleting the target CNF deployed in the primary cloud.

Next, switching of PDU session paths by the control device 100 according to the present disclosure will be described using FIGS. 4A and 4B. FIG. 4A shows the path of the PDU session before path switching. FIG. 4B shows the path of the PDU session after path switching.
FIGS. 4A and 4B show an example in which the cloud group includes Edge Cloud #1 and Edge Cloud #2. Furthermore, FIGS. 4A and 4B show five user terminals (UE#1, UE#2, UE#3, UE#4, and UE#5) located within the coverage area formed by the RU. ing. Note that the number of clouds, the number of RUs, and the number of UEs included in a cloud group are not limited.

FIG. 4A shows that DU, CU, UPF, and APP #1, which are indicated by solid lines, are deployed in Edge Cloud #1 before the path switching. UE#1, UE#2, UE#3, UE#4, and UE#5 have established a PDU session through the first route with APP#1.
In this case, assume that Edge Cloud #1 is requested to create APP #2, which is indicated by a dotted line. At this time, it is assumed that the application selection unit 130 selects APP #1 as the target application to be deployed on the secondary cloud, and the secondary cloud determination unit 140 determines Edge Cloud #2 as the secondary cloud. Further, it is assumed that the CNF selection unit 150 selects all CNFs constructing APP #1 as target CNFs.

FIG. 4B shows how APP #1 is relocated from Edge Cloud #1 to Edge Cloud #2. As described above, the route switching instruction unit 160 determines whether the number of user terminals whose RRC state is RRC_CONNECTED and which has established a PDU session with APP #1 on the first route and a predetermined threshold value are determined. be compared. When the number of user terminals that are RRC_CONNECTED is a predetermined threshold, switching of the PDU session path is instructed.
After route switching, the PDU session between the user terminal and the target application (APP #1) connects the DU, CU, UPF deployed on Edge Cloud #1, and APP #1 deployed on the secondary cloud. The second path will be established.
By relocating APP #1 from Edge Cloud #1 to Edge Cloud #2, APP #2 can be deployed to resources available in Edge Cloud #1.

FIG. 5 is a flowchart illustrating an example of the operation of the control device 100 according to the present disclosure.
The resource monitoring unit 110 monitors the resource usage status of the cloud in the cloud group (S11).
When requesting the primary cloud to create a new application, the resource determining unit 120 determines whether or not the resources of the primary cloud are tight (S12). Specifically, the resource determination unit 120 determines that resources are tight if the primary cloud does not have the resources to deploy all CNFs that construct a new application.
The application selection unit 130 selects an application (target application) to be deployed to the secondary cloud from existing applications deployed to the primary cloud, based on the operating status of the application (S13).

The secondary cloud determining unit 140 sets the number (f) of CNFs (target CNFs) to be placed in the secondary cloud among all CNFs that construct the target application (S14). The secondary cloud determining unit 140 determines a secondary cloud (S15). Note that, as described above, the number (f) of CNFs (target CNFs) may be set after determining the secondary cloud.
The CNF selection unit 150 selects CNFs (target CNFs) to be placed in f secondary clouds from the CNFs that construct the target application (S16). In S16, the CNF selection unit 150 may select the target CNF based on a preset CNF priority order.
The deployment unit 170 deploys the selected target CNF to the secondary cloud (S17).
The route switching instruction unit 160 changes the route for forming a PDU session from a first route to a second route according to the RRC status of one or more user terminals with which a PDU session has been established with the target application. An instruction is given to switch (S18). Specifically, when the number of RRC states of one or more user terminals with which a PDU session has been established with the target application is RRC_CONNECTED is equal to or less than a predetermined threshold, the path switching instruction unit 160 Instructs to switch the PDU session route.
Note that in S12, if it is determined that the resources of the primary cloud for which the new application creation request was made are not under strain, the deployment unit 170 creates the new application in the primary cloud. (S19).

Next, the operation of the control device 100 according to the present disclosure will be described using FIG. 6. FIG. 6 is a diagram illustrating an example of a processing sequence in the control device 100 according to the present disclosure.
The control device 100 monitors the resource usage status of the cloud in the cloud group (“resource information management”, T11).

FIG. 6 shows how the resource usage status of the i-th cloud (also referred to as cloud (i)) other than the primary cloud in the cloud group is monitored. Here, i=1 to N-1, and N is the total number of clouds in the cloud group.
Further, the resource usage status may be monitored periodically or triggered by a request to create a new application.

The control device 100 triggers a request to create a new application to the primary cloud in the cloud group (“new application creation request”, T12), and the control device 100 determines that the resources for deploying all CNFs for building the new application are available in the primary cloud. It is determined whether the resource is present (“resource determination”, T13). For example, if the resource usage ratio R defined by the ratio f _sum /f _max is 1 or less, the control device 100 determines that the primary cloud has resources for deploying all CNFs that construct a new application ("resources are tight"). "No"). On the other hand, if the resource usage ratio R is greater than 1, the control device 100 determines that the primary cloud does not have the resources to deploy all the CNFs that construct the new application (“resources are tight”).

If it is determined in the "resource determination" (T13) that "resources are tight", the control device 100 selects an application (target application) to be deployed to the secondary cloud ("application selection", T14). The target application is selected from existing applications deployed in the primary cloud based on the operating status of the application.
When the target application is selected, the control device 100 determines a secondary cloud in which to place at least a portion of the CNF that constructs the target application (“determine secondary cloud”, T15). Furthermore, in "Secondary Cloud Determination" (T15), the control device 100 sets the number of CNFs (target CNFs) to be placed in the secondary cloud.
Furthermore, the control device 100 selects a CNF (target CNF) to be placed in the secondary cloud based on the priority order of the CNFs (“CNF selection”, T16).

The control device 100 deploys the selected target CNF to the secondary cloud (T17).
Note that in the "resource determination" (T13), if it is determined that "there is no resource strain", the control device 100 may decide to deploy all CNFs for constructing a new application in the primary cloud (T14, T15). , T16). In this case, the control device 100 deploys all CNFs for constructing a new application to the primary cloud (T17A).

The control device 100 switches the path of the PDU session established between the user terminal and the target application, depending on the RRC state of one or more user terminals with which a PDU session has been established with the target application (" "Route switching", T18). For example, a process for establishing a PDU session between a user terminal and a target application deployed in a secondary cloud is executed. Furthermore, the control device 100 executes processing for deleting the target CNF deployed in the primary cloud (T19).

As described above, the control device 100 according to the present disclosure includes at least the application selection section 130 and the path switching instruction section 160. The application selection unit 130 selects an application (target application) to be deployed to the secondary cloud based on the operating status of existing applications deployed to the primary cloud. The path switching instruction unit 160 acquires information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud. . The route switching instruction unit 160 instructs switching of the PDU session route from the route to the target application deployed in the primary cloud to the route to the target application deployed in the secondary cloud, according to the RRC state. .

When the control device 100 adopts the above configuration, the path of the PDU session is switched from the first path to the second path. The first path is a path for forming a PDU session from the user terminal to the target application deployed in the primary cloud. The second route is a route for forming a PDU session from the user terminal to the target application relocated to the secondary cloud. To stably provide services to user terminals while suppressing the impact of switching paths for forming PDU sessions even when the primary cloud does not have sufficient resources and it is necessary to change the placement of CNFs that build applications. You will be able to do this.
Furthermore, since CNFs that build applications can be distributed and placed in different clouds, it is possible to level out the consumption of computing resources for the cloud group as a whole.

Further, the application selection unit 130 may select the target application based on the operating status of existing applications deployed in the primary cloud. As a result, applications with high operating status are placed in the primary cloud, and applications with low operating status are placed in the secondary cloud, reducing the impact of placement changes such as temporary disconnection of PDU sessions. be able to.
Note that, before selecting a target application from existing applications deployed in the primary cloud, the application selection unit 130 may compare the priorities of the existing application and the new application. If the priority of the new application is higher than the existing application, the application selection unit 130 may select the target application from the existing applications. If the new application has a lower priority than the existing application, the application selection unit 130 may select the new application as the target application to be deployed to the secondary cloud. The application selection unit 130 may instruct the secondary cloud determination unit 140 and the CNF selection unit 150 to deploy the new application to the secondary cloud. In this case, no instruction for switching the route will be output to the route switching instruction unit 160.

Note that in the above explanation, an example has been explained in which an application for providing services provided to a user terminal has a configuration as shown in FIG. 2, but the present invention is not limited to this. . Even if an application is built from role units that are divided into roles when providing a service, and these role units are deployed to different clouds, an architecture is adopted that allows functional coordination communication between role units. It would be fine if it was.

FIG. 7 is a diagram showing a computer 200 implementing the control device 100 according to the present disclosure. Computer 200 includes a processor 210, a memory 220, and a communication unit 230. The number of processors 210, memories 220, and communication units 230 is not limited, and may be one or more. Further, the processor 210, the memory 220, and the communication unit 230 may be deployed together at each location where each unit that constitutes the control device 100 is arranged. The processor 210 is a program-controlled device such as a microprocessor that operates according to a program installed in the control device 100. The memory 220 is a storage device such as a storage element such as ROM or RAM, a solid state drive (SSD), or a hard disk drive (HDD). The memory 220 stores programs and the like executed by the processor 210. The communication unit 230 is, for example, a communication interface such as a NIC or a wireless LAN module. Note that SDN (Software-Defined Networking) may be implemented in the communication unit 230.
Computer 200 may further include storage 240.
Examples of the application information stored in the storage 240 include information on the total number of CNFs for constructing a new application, information on CNF characteristics, and information on application priorities.
Computer 200 may further include other components not shown.

The control device 100 according to the present disclosure includes one or more processors. One or more processors select a target application to be deployed to a secondary cloud in the cloud group from existing applications deployed in a primary cloud in a cloud group formed by a plurality of clouds. One or more processors deploy all or part of a CNF (Containerized Network Function) that constructs a target application to a secondary cloud within a cloud group. One or more processors acquire information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with a target application deployed in a primary cloud. One or more processors instruct switching of the path of the PDU session from a path to a target application deployed in a primary cloud to a path to a target application deployed in a secondary cloud, depending on the RRC state.

Note that when container-type virtualization technology is applied to the construction of an application, the control device 100 according to the present disclosure may realize resource sharing between clouds using an orchestrator function.

The present disclosure is not limited to the above configuration, and the present disclosure also includes a control program. That is, the present disclosure also includes a program that, when read by a computer, causes one or more processors of the computer to execute each part of the control device 100.
The above-mentioned program may be provided recorded on a computer-readable non-transitory storage medium.

The present disclosure includes the following aspects.

[1] Comprising one or more processors, the one or more processors:
Selecting a target application to be deployed to a secondary cloud in the cloud group from existing applications deployed in a primary cloud in a cloud group formed by a plurality of clouds;
Deploying all or part of a CNF (Containerized Network Function) that constructs the target application to a secondary cloud within the cloud group;
Obtaining information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud;
Instructing to switch the path of the PDU session from a path to the target application deployed in the primary cloud to a path to the target application deployed in the secondary cloud according to the RRC state. and,
A control device that executes.

[2] The one or more processors are:
Instructing the switching when the number of RRC states of RRC_CONNECTED is less than or equal to a predetermined threshold;
The control device according to [1].

[3] The predetermined threshold value is set according to QoS (Quality of service) required of the target application.
The control device according to [2].

[4] The higher the QoS required for the target application, the smaller the predetermined threshold value is.
The control device according to [3].

[5] The one or more processors:
When requesting the creation of a new application to the primary cloud, select the target application,
The predetermined threshold value is set according to the priority required for the new application,
The control device according to [2].

[6] The higher the priority required for the new application, the greater the predetermined threshold value;
The control device according to [5].

[7] The predetermined threshold value is set according to the usage time period,
The control device according to any one of [2] to [6].

[8] The one or more processors are:
selecting the target application based on the operating status of the existing application;
The control device according to any one of [1] to [7].

[9] The operating status includes at least one of the operating time of the application, the number of user terminals connected to the application, the amount of data of the application, and the throughput of the application.
The control device according to [8].

[10] The one or more processors include:
further performing the step of determining the secondary cloud based on a delay time caused by switching the path of the PDU session;
The control device according to any one of [1] to [9].

[11] The one or more processors include:
determining a cloud with the minimum delay time as the secondary cloud;
The control device according to [10].

[12] The one or more processors,
selecting the target application using the fact that the primary cloud is under stress as a trigger when requesting creation of a new application to the primary cloud;
The control device according to any one of [1] to [11].

[13] The one or more processors,
Monitoring resource usage of the primary cloud;
further execute
The control device according to any one of [1] to [12].

[14] The one or more processors include:
Instructing to delete all or part of the CNF that builds the target application deployed in the primary cloud;
further execute
The control device according to any one of [1] to [13].

[15] The target application is constructed using a microservice architecture.
The control device according to any one of [1] to [14].

[16] Selecting, using a processor, a target application to be deployed to a secondary cloud in the cloud group from existing applications deployed in a primary cloud in a cloud group formed by a plurality of clouds;
Deploying all or part of a CNF (Containerized Network Function) that constructs the target application to a secondary cloud within the cloud group using a processor;
Using a processor, acquire information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud. to do and
The processor switches the path of the PDU session from a path to the target application deployed in the primary cloud to a path to the target application deployed in the secondary cloud according to the RRC state. using and instructing;
including control methods.

[17] When read by a computer, one or more processors of said computer:
Selecting a target application to be deployed to a secondary cloud in the cloud group from existing applications deployed in a primary cloud in a cloud group formed by a plurality of clouds;
Deploying all or part of a CNF (Containerized Network Function) that constructs the target application to a secondary cloud within the cloud group;
Obtaining information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud;
Instructing to switch the path of the PDU session from a path to the target application deployed in the primary cloud to a path to the target application deployed in the secondary cloud according to the RRC state. and,
A non-transitory computer-readable medium on which a program for executing is recorded.

Note that the present disclosure is not limited to the above-described embodiments, but also includes various modifications in which components are added, deleted, or converted to the above-described configuration.

100 Control device 110 Resource monitoring unit 120 Resource determination unit 130 Application selection unit 140 Secondary cloud determination unit 150 CNF selection unit 160 Route switching instruction unit 170 Deployment unit 200 Computer 210 Processor 220 Memory 230 Communication unit 240 Storage

Claims (17)

1. comprising one or more processors, the one or more processors comprising:
   Selecting a target application to be deployed to a secondary cloud in the cloud group from existing applications deployed in a primary cloud in a cloud group formed by a plurality of clouds;
   Deploying all or part of a CNF (Containerized Network Function) that constructs the target application to a secondary cloud within the cloud group;
   Obtaining information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud;
   Instructing to switch the path of the PDU session from a path to the target application deployed in the primary cloud to a path to the target application deployed in the secondary cloud according to the RRC state. and,
   A control device that executes.
2. The one or more processors are:
   Instructing the switching when the number of RRC states of RRC_CONNECTED is less than or equal to a predetermined threshold;
   The control device according to claim 1.
3. The predetermined threshold value is set according to QoS (Quality of service) required of the target application.
   The control device according to claim 2.
4. The higher the QoS required for the target application, the smaller the predetermined threshold value is.
   The control device according to claim 3.
5. the one or more processors,
   When requesting the creation of a new application to the primary cloud, select the target application,
   The predetermined threshold value is set according to the priority required for the new application,
   The control device according to claim 2.
6. The higher the priority required for the new application, the greater the predetermined threshold value;
   The control device according to claim 5.
7. The predetermined threshold value is set according to the usage time period,
   The control device according to claim 2.
8. The one or more processors are:
   selecting the target application based on the operating status of the existing application;
   The control device according to claim 1.
9. The operating status includes at least one of the operating time of the application, the number of user terminals connected to the application, the amount of data of the application, and the throughput of the application.
   The control device according to claim 8.
10. The one or more processors are:
    further performing the step of determining the secondary cloud based on a delay time caused by switching the path of the PDU session;
    The control device according to claim 1.
11. The one or more processors are:
    determining a cloud with the minimum delay time as the secondary cloud;
    The control device according to claim 10.
12. the one or more processors,
    selecting the target application using the fact that the primary cloud is under stress as a trigger when requesting creation of a new application to the primary cloud;
    The control device according to claim 1.
13. the one or more processors,
    Monitoring resource usage of the primary cloud;
    further execute
    The control device according to claim 1.
14. The one or more processors are:
    Instructing to delete all or part of the CNF that builds the target application deployed in the primary cloud;
    further execute
    The control device according to claim 1.
15. The target application is constructed using a microservice architecture.
    The control device according to claim 1.
16. Selecting, using a processor, a target application to be deployed to a secondary cloud in the cloud group from existing applications deployed to a primary cloud in a cloud group formed by a plurality of clouds;
    Deploying all or part of a CNF (Containerized Network Function) that constructs the target application to a secondary cloud within the cloud group using a processor;
    Using a processor, acquire information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud. to do and
    The processor switches the path of the PDU session from a path to the target application deployed in the primary cloud to a path to the target application deployed in the secondary cloud according to the RRC state. using and instructing;
    including control methods.
17. When read by a computer, one or more processors of said computer:
    Selecting a target application to be deployed to a secondary cloud in the cloud group from existing applications deployed in a primary cloud in a cloud group formed by a plurality of clouds;
    Deploying all or part of a CNF (Containerized Network Function) that constructs the target application to a secondary cloud within the cloud group;
    Obtaining information on the RRC (Radio Resource Control) status of one or more user terminals that have established a PDU (Packet Protocol Unit) session with the target application deployed in the primary cloud;
    Instructing to switch the path of the PDU session from a path to the target application deployed in the primary cloud to a path to the target application deployed in the secondary cloud according to the RRC state. and,
    A non-transitory computer-readable medium on which a program for executing is recorded.
    
    

Images