Scale-out system, scale-out method, and recording medium

Abstract

In order to perform scale-out of a disaster recovery site before traffic flows into the disaster recovery site in the event of a disaster, a scale-out system according to the present invention comprises: a holding means that holds resource information of a main site acquired in advance; a scale-out means that, upon acquisition of disaster information, requests the disaster recovery site to perform scale-out for resources based on the held resource information; and a provision means that provides, in response to a notification pertaining to the scale-out status acquired from the disaster recovery site, an acceptance instruction for disaster roaming to enable use of a public land mobile network (PLMN) which is for use during a disaster and which corresponds to the disaster recovery site.

Description

Scale-out system, scale-out method, and recording medium

[0001] The present disclosure relates to a scale-out system, a scale-out method, and a recording medium.

[0002] A technology is known in which a disaster recovery site (DR site) is established as an alternative system base to a main site, which is the primary system base. The DR site operates when the main site becomes unavailable due to a disaster. For example, Patent Literature 1 (JP-A-2005-102666) describes a technology for switching from the main site to the DR site.

[0003] JP 2019-47396 A

[0004] Recently, the construction of a 5th Generation Core network (5GC) in a public cloud environment has been promoted. An example of using 5GC in a public cloud environment is a DR site.

[0005] In the event of a disaster, a sudden increase in traffic may require scaling out the DR site. In a 5GC public cloud environment, scaling out the DR site is considered to be performed by increasing the number of Pods or network functions depending on the degree of increase in inflow traffic. However, when a DR site is realized in a 5GC public cloud environment, there is room for further improvement in the scale-out operation of the DR site.

[0006] The present disclosure has been made in consideration of the above improvements, and one exemplary purpose thereof is to provide a technology for scaling out a DR site in advance in the event of a disaster, before traffic flows into the DR site.

[0007] A scale-out system according to an exemplary aspect of the present disclosure is a system for scaling out a DR site (Disaster Recovery site) connected to a mobile communication network, and includes: a storage means for storing resource information of a main site acquired in advance; a scale-out means for requesting the DR site to scale out resources based on the stored resource information upon acquisition of disaster information; and a provision means for providing a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site in response to a notification regarding the scale-out status acquired from the DR site.

[0008] A scale-out method according to an exemplary aspect of the present disclosure is a method executed by a scale-out system that scales out a DR site (Disaster Recovery site) connected to a mobile communication network, and includes: a retaining process in which at least one processor retains resource information of a main site that has been acquired in advance; a scale-out process in which the at least one processor, upon acquisition of disaster information, requests the DR site to scale out resources based on the retained resource information; and a providing process in which the at least one processor, in response to a notification regarding the scale-out status acquired from the DR site, provides a disaster roaming acceptance instruction that enables use of a disaster public land mobile network (PLMN) corresponding to the DR site.

[0009] A scale-out program recorded on a computer-readable recording medium according to an exemplary aspect of the present disclosure is a program that causes at least one processor to function as a scale-out system that scales out a DR site (Disaster Recovery site) connected to a mobile communication network, and causes the at least one processor to function as: a storage means that stores resource information of a main site that has been acquired in advance; a scale-out means that, upon acquisition of disaster information, requests the DR site to scale out resources based on the stored resource information; and a provision means that, in response to a notification regarding the scale-out status acquired from the DR site, provides a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site.

[0010] According to an exemplary aspect of the present disclosure, an exemplary effect is achieved in that a technique can be provided that, in the event of a disaster, scales out a DR site in advance before traffic flows into the DR site.

[0011] FIG. 1 is a block diagram showing the configuration of a scale-out system according to the present disclosure. FIG. 2 is a flow diagram showing the flow of a scale-out method executed by the scale-out system according to the present disclosure. FIG. 3 is a schematic diagram showing an overview of the scale-out system according to the present disclosure. FIG. 4 is a block diagram showing the internal configuration of a controller according to the present disclosure. FIG. 5 is a flow diagram showing the flow of a scale-out method executed by the scale-out system according to the present disclosure. FIG. 6 is a flow diagram showing the flow of a scale-out method executed by the scale-out system according to the present disclosure. FIG. 7 is a schematic diagram showing an overview of the scale-out system according to the present disclosure. FIG. 8 is a block diagram showing the configuration of a computer functioning as a controller provided in the scale-out system according to the present disclosure.

[0012] The following are examples of embodiments of the present invention. However, the present invention is not limited to the exemplary embodiments shown below, and various modifications are possible within the scope of the claims. For example, embodiments obtained by appropriately combining the technologies (part or all of the products or methods) employed in the exemplary embodiments shown below may also be included in the scope of the present invention. Furthermore, embodiments obtained by appropriately omitting some of the technologies employed in the exemplary embodiments shown below may also be included in the scope of the present invention. Furthermore, the effects mentioned in the exemplary embodiments shown below are examples of effects expected in the exemplary embodiments, and do not define the scope of the present invention. In other words, embodiments that do not exhibit the effects mentioned in the exemplary embodiments shown below may also be included in the scope of the present invention.

[0013] [First Exemplary Embodiment] A first exemplary embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. This exemplary embodiment is a basic form for each of the exemplary embodiments described below. Note that the scope of application of each technique employed in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technique employed in this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical obstacles arise. Furthermore, each technique shown in the drawings referenced to explain this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical obstacles arise.

[0014] (Configuration of Scale-Out System 1) The configuration of the scale-out system 1 will be described with reference to FIG. 1. FIG. 1 is a block diagram showing the configuration of the scale-out system 1. As shown in FIG. 1, the scale-out system 1 includes a holding unit 11, a scale-out unit 12, and a providing unit 13. The holding unit 11, the scale-out unit 12, and the providing unit 13 are an example of a configuration that realizes the holding means, the scale-out means, and the providing means. For example, if the scale-out system 1 includes at least one processor, the holding unit 11, the scale-out unit 12, and the providing unit 13 are realized by the at least one processor executing a program.

[0015] The scale-out system 1 scales out a disaster recovery (DR) site connected to a mobile communication network. An example of a mobile communication network is a 5G (5th generation) mobile communication system. The DR site is used as an alternative base for a main site when the main site becomes unavailable due to a disaster. The DR site may also be referred to as a backup site.

[0016] The DR site is operated in a cloud environment in which, for example, a 5th Generation Core network (5GC) is built. The DR site may be operated in a public cloud environment. Examples of public cloud environments include Amazon Web Services (AWS) (registered trademark), Azure (registered trademark), and Google Cloud Platform (registered trademark).

[0017] The storage unit 11 stores resource information of the main site that has been acquired in advance. The storage unit 11 may store resource information that has been acquired by communicating with the main site. The storage unit 11 may also store resource information that has been acquired by input by a worker performing maintenance work.

[0018] Upon receiving disaster information, the scale-out unit 12 requests the DR site to scale out resources based on the resource information it holds. The scale-out unit 12 requests the DR site to scale out based on the resource information held by the holding unit 11. The disaster information may be information acquired via a network. The disaster information may be information input to a controller that controls the DR site by a worker performing maintenance work. The disaster information includes, for example, (i) a disaster notification broadcast to a target area, such as an emergency earthquake alert, and (ii) a notification indicating poor communication between a server operating the main site and a controller that controls the DR site.

[0019] In addition, requesting scale-out in response to the acquisition of disaster information means providing a scale-out request to the DR site after the acquisition of disaster information and before traffic flows into the DR site, and it is not necessary for the scale-out to be completed before traffic flows in.

[0020] The DR site performs scale-out by increasing the number of at least one of Pods, worker nodes, and network functions (NFs) at the DR site based on a request from the scale-out unit 12. That is, the DR site increases the number of at least one of Pods, worker nodes, and network functions (NFs) built in the cloud environment. This improves the information processing capability of the DR site.

[0021] In response to the scale-out status notification received from the DR site, the provider 13 provides a disaster roaming acceptance instruction that enables the use of a disaster public land mobile network (PLMN) corresponding to the DR site. This enables the use of the DR site. The scale-out status notification includes (i) a scale-out completion notification indicating that the scale-out of the DR site has been completed, and (ii) a progress notification indicating that the scale-out of the DR site has been completed in stages. The disaster roaming acceptance instruction is an instruction to start accepting roaming to the disaster PLMN corresponding to the DR site.

[0022] (Flow of Scale-Out Method S1) The flow of the scale-out method S1 executed by the scale-out system 1 will be described with reference to Fig. 2. Fig. 2 is a flow diagram showing the flow of the scale-out method S1 executed by the scale-out system 1. As shown in Fig. 2, the scale-out method S1 includes a retention process S11, a scale-out process S12, and a provision process S13.

[0023] In a holding process S11, at least one processor (for example, the holding unit 11) holds resource information of the main site acquired in advance. In a scale-out process S12, at least one processor (for example, the scale-out unit 12) requests the DR site to scale out resources based on the held resource information before traffic flows into the DR site. In a provision process S13, in response to a notification regarding the scale-out status acquired from the DR site, at least one processor (for example, the provision unit 13) provides an instruction to accept disaster roaming, which enables the DR site to use a disaster PLMN corresponding to the DR site.

[0024] (Effects of Scale-Out System 1 and Scale-Out Method S1) As described above, the scale-out system 1 and scale-out method S1 employ a configuration in which the storage unit 11 stores resource information of the main site acquired in advance, the scale-out unit 12, upon acquiring disaster information, requests the DR site to scale out resources based on the stored resource information, and the providing unit 13 provides an instruction to accept disaster roaming in response to a notification regarding the scale-out status. Because the resource information of the main site is stored in advance, it is possible to scale out the DR site in accordance with the resource information of the main site. This provides the effect that, in the event of a disaster, the DR site can be scaled out in advance before traffic flows into the DR site.

[0025] Furthermore, according to the scale-out system 1 and scale-out method S1 described above, the scale-out of the DR site is performed first. Therefore, in the event of a disaster, it is not necessary to perform scale-out of the DR site every time the traffic flowing into the DR site exceeds a predetermined amount. This reduces the time required for call processing.

[0026] Furthermore, according to the scale-out system 1 and scale-out method S1 described above, in the event of a disaster, the DR site is scaled out before traffic flows into the DR site. In other words, the DR site is not scaled out during normal times when no disaster has occurred. Therefore, the resources of the DR site can be minimized during normal times, thereby reducing the operating costs of the DR site.

[0027] Second Exemplary Embodiment A second exemplary embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. Components having the same functions as those described in the above exemplary embodiment will be denoted by the same reference numerals, and their description will be omitted as appropriate. The scope of application of each technique employed in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technique employed in this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical hindrance occurs. Furthermore, each technique shown in each drawing referenced to describe this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical hindrance occurs.

[0028] (Configuration of Scale-Out System 1A) The configuration of the scale-out system 1A will be described with reference to Fig. 3. Fig. 3 is a schematic diagram showing an overview of the scale-out system 1. The scale-out system 1A includes a UE (User Equipment) 2, a gNB 3, a main site 5, and a DR site 6.

[0029] The UE 2 is a device that can be connected to a network wirelessly or via a wired connection, and examples of the UE 2 include a smartphone, a tablet terminal, a personal computer, and an IoT device.

[0030] The gNB 3 is a base station that constitutes a 5G Radio Access Network (5G-RAN). The gNB 3 is an example of a RAN node. The UE 2 connects to the main site 5 and the DR site 6 via the 5G-RAN.

[0031] The main site 5 is a facility that serves as a main base, and is installed in the on-premises environment 100. The main site 5 is constructed, for example, by a server or the like that is placed in the on-premises environment 100. The main site 5 is equipped with a 5GC 50 that constructs a 5G network. A UE 2 registered with a PLMN provided by a communication carrier with which the communication contract has been concluded connects to the 5GC 50.

[0032] The 5GC 50 includes the following network functions (NFs): an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), and a User Plane Function (UPF). The AMF, SMF, and UDM function as a Control Plane (C-Plane) for communicating control signals. The AMF manages UE2 registration, connection, mobility, etc. The SMF manages UE2 sessions, etc. The UDM holds various data such as subscriber data and PLMN lists. The UPF functions as a User Plane (U-Plane) for communicating user data. The 5GC 50 may also include NFs such as a Unified Data Repository (UDR), an Authentication Server Function (AUSF), and a Network Slice Selection Function (NSSF).

[0033] Each NF included in the 5GC 50 generates various Pods, worker nodes, or container platforms as needed. A Pod includes one or more container platforms and manages the execution of containerized applications using the container platforms. One or more Pods are deployed on a worker node. The worker node starts each deployed Pod (container platform).

[0034] The DR site 6 is installed in the cloud environment 200 as a replacement for the main site 5. The DR site 6 is constructed by a cloud server or the like arranged in the cloud environment 200. The DR site 6 may be constructed in, for example, AWS, which is a public cloud environment. The DR site 6 includes a 5GC 60. The 5GC 60 has the same configuration as the 5GC 50. A UE 2 registered in a disaster PLMN corresponding to the DR site 6, for example, connects to the 5GC 60.

[0035] (Internal Configuration of Controller 10) The scale-out system 1A includes a controller 10. The controller 10 controls each unit included in the main site 5 and the DR site 6. The controller 10 is constructed in a cloud environment 200. The controller 10 includes at least one processor. The controller 10 may further include a memory, a communication interface, etc.

[0036] The internal configuration of the controller 10 will be described with reference to Fig. 4. Fig. 4 is a block diagram showing the internal configuration of the controller 10. The controller 10 includes an acquisition unit 14 and a calculation unit 15 in addition to the storage unit 11, scale-out unit 12, and provision unit 13 included in the first exemplary embodiment.

[0037] The acquisition unit 14 acquires accommodated subscriber number information from the main site 5. The accommodated subscriber number information is an example of resource information of the main site 5. The acquisition unit 14 acquires disaster information. The acquisition unit 14 acquires a scale-out completion notification from the network function (NF) of the 5GC 60 or the container platform that constitutes the 5GC 60. The scale-out completion notification is a notification indicating that the scale-out of the DR site 6 has been completed. The acquisition unit 14 is an example of a configuration that realizes a first acquisition means, a second acquisition means, and a third acquisition means.

[0038] The calculation unit 15 calculates the resources required for scaling out the DR site 6 from the stored information on the number of accommodated subscribers. The calculation unit 15 is an example of a configuration that realizes a calculation means.

[0039] (Flow of scale-out method S1A) The scale-out system 1A configured as described above executes the scale-out method S1A. The flow of the scale-out method S1A will be described with reference to Figs. 5 and 6. Figs. 5 and 6 are flow diagrams showing the flow of the scale-out method S1A. As shown in Figs. 5 and 6, the scale-out method S1A includes steps S100 to S122.

[0040] 5, in step S100, the AMF 61 included in the 5GC 60 provides a disaster availability notification indicating that a disaster PLMN corresponding to the DR site 6 can be used in the event of a disaster to the UDM 52 included in the 5GC 50. In step S102, the UDM 52 holds a disaster PLMN list in which PLMNs that can be used in the event of a disaster are listed. In step S102, the UDM 52 includes the acquired disaster PLMN in the disaster PLMN list.

[0041] In step S103, the acquisition unit 14 acquires information on the number of accommodated subscribers of the main site 5 from the AMF 51 included in the 5GC 50. In step S103, the acquisition unit 14 may periodically acquire information on the number of accommodated subscribers of the main site 5 from the AMF 51. In step S104, the retention unit 11 retains the information on the number of accommodated subscribers acquired by the acquisition unit 14. Step S104 is an example of a retention process. In step S104, the retention unit 11 may retain the information on the number of accommodated subscribers by storing it in a database constructed in the cloud environment 200, memory, etc.

[0042] In step S105, UE2 provides a registration request for the PLMN provided by the communication carrier with which the UE2 has made a communication contract to AMF 51. In step S106, AMF 51 provides a notification indicating that UE2 is present in the PLMN provided by the communication carrier with which the UE2 has made a communication contract to UDM 52. In step S107, AMF 51 provides a request for subscriber data of UE2 to UDM 52.

[0043] In step S108, the UDM 52 provides the subscriber data and the disaster PLMN list of the UE 2 to the AMF 51. In step S109, the AMF 51 provides the acquired disaster PLMN list to the UE 2. In step S110, the 5G-RAN 31 (gNB 3) belonging to the PLMN provided by the communication carrier with which the communication contract has been made provides the disaster PLMN list according to the disaster type to the UE 2.

[0044] 6 , in step S111, a disaster occurs in the area where the main site 5 is installed. In step S112, the AMF 51 provides disaster information to the controller 10. In step S112, the acquisition unit 14 acquires the disaster information provided by the AMF 51.

[0045] In step S113, the calculation unit 15 calculates the resources required for scaling out the DR site 6 from the accommodated subscriber number information held by the holding unit 11. An example of a method for calculating the resources calculated by the calculation unit 15 in step S113 is shown below. 1. Number of accommodated subscribers × Traffic per subscriber = Total traffic 2. Total traffic ÷ Processable traffic per Pod of each NF = Required number of Pods for each NF 3. (Required number of Pods × Resources per Pod) ÷ Resources per worker node = Minimum number of worker nodes 4. Minimum number of worker nodes + Surplus number taking into account resource fragmentation = Required number of worker nodes

[0046] In step S113, the calculation unit 15 may calculate the required number of Pods and / or the required number of worker nodes for each NF by adding a predetermined number to the calculated required number of Pods and / or the required number of worker nodes. This provides a margin for the resources required for scale-out. In step S113, the calculation unit 15 may calculate only the required number of Pods for each NF, or may calculate only the required number of worker nodes. In step S113, the calculation unit 15 may calculate the number of NFs required for scaling out the DR site 6, or may calculate the number of container platforms required for scaling out the DR site 6.

[0047] In step S114, the scale-out unit 12, upon receiving the disaster information, provides the container base 62 with a scale-out request requesting scale-out by the amount of resources calculated by the calculation unit 15. In step S115, the scale-out unit 12, upon receiving the disaster information, provides the AMF 61 with a scale-out request requesting scale-out by the amount of resources calculated by the calculation unit 15. Steps S114 and S115 are an example of scale-out processing. In steps S114 and S115, the scale-out unit 12 includes in the scale-out request (i) the number of pods required for each NF and (ii) the number of worker nodes required, which are calculated by the calculation unit 15.

[0048] In step S116, based on the acquired scale-out request, the AMF 61 and the container base 62 scale out the DR site 6. For example, in step S116, the AMF 61 and the container base 62 increase the number of Pods and the number of worker nodes required for each NF included in the scale-out request.

[0049] In step S117, when the scale-out of the DR site 6 is completed, the container base 62 provides a scale-out completion notification indicating the completion of the scale-out of the DR site 6 to the controller 10. In step S118, when the scale-out of the DR site 6 is completed, the AMF 61 provides a scale-out completion notification indicating the completion of the scale-out of the DR site 6 to the controller 10. In steps S117 and S118, the acquisition unit 14 acquires the scale-out completion notifications from the AMF 61 and the container base 62.

[0050] In step S119, the providing unit 13 provides an instruction to accept disaster roaming to the 5G-RAN 32 (gNB 3) belonging to the disaster PLMN in response to the acquired scale-out completion notification. Step S119 is an example of a providing process.

[0051] In step S120, the 5G-RAN 32 provides the UE 2 with a disaster roaming start notification that notifies the UE 2 of the start of disaster roaming acceptance based on the acquired disaster roaming acceptance instruction. In step S121, the UE 2 provides the AMF 61 with a registration request for a disaster PLMN corresponding to the DR site 6. In step S122, the AMF 61, the container board 62, and the UDM 52 register the location information of the UE 2.

[0052] (Effects of Scale-Out System 1A) As described above, the scale-out system 1A employs a configuration in which the storage unit 11 stores information about the number of subscribers accommodated at the main site 5 that has been acquired in advance, the scale-out unit 12, upon acquisition of disaster information, requests the DR site 6 to scale out resources based on the stored information about the number of subscribers accommodated, and the provision unit 13 provides an instruction to accept disaster roaming in response to a scale-out completion notification. This makes it possible to obtain effects similar to those of the scale-out system 1.

[0053] As described above, the scale-out system 1A employs a configuration in which the acquisition unit 14 acquires information on the number of accommodated subscribers from the main site 5. By acquiring information on the number of accommodated subscribers from the main site 5, it becomes possible to update the information on the number of accommodated subscribers. Therefore, in addition to the effects of the scale-out system 1, the scale-out system 1A has the effect of being able to scale out the DR site 6 in accordance with the updated number of accommodated subscribers.

[0054] Furthermore, the scale-out system 1A employs a configuration in which the acquisition unit 14 acquires disaster information from the main site 5. Therefore, in addition to the effects of the scale-out system 1, the scale-out system 1A has the effect of being able to scale out the DR site 6 in advance when a disaster occurs at the main site 5.

[0055] Furthermore, the scale-out system 1A employs a configuration in which the resources required for scaling out the DR site 6 are calculated from the accommodated subscriber number information held by the calculation unit 15. Therefore, the scale-out of the DR site 6 is performed by the amount of resources calculated based on the accommodated subscriber number information. Therefore, in addition to the effects of the scale-out system 1, the scale-out system 1A provides the effect of being able to scale out the DR site 6 in accordance with the number of accommodated subscribers of the main site 5.

[0056] Furthermore, the scale-out system 1A employs a configuration in which the scale-out unit 12 provides a scale-out request including at least one of the number of Pods and the number of worker nodes required for scale-out to at least one of the AMF 61 and the container base 62. Therefore, at least one of the AMF 61 and the container base 62 generates at least one of the Pods and the worker nodes for the calculated number. Therefore, according to the scale-out system 1A, in addition to the effects achieved by the scale-out system 1, it is possible to scale out multiple Pods and multiple worker nodes required for scale-out in parallel.

[0057] Furthermore, the scale-out system 1A is configured such that the acquisition unit 14 acquires a scale-out completion notification indicating that the scale-out of the DR site 6 has been completed from at least one of the AMF 61 and the container base 62. The acquisition unit 14 acquires the scale-out completion notification, thereby making it possible to confirm that the scale-out has been completed. Therefore, in addition to the effects of the scale-out system 1, the scale-out system 1A can start accepting UEs 2 into the DR site 6 after the scale-out is completed.

[0058] Furthermore, the scale-out system 1A employs a configuration in which the provider 13 provides a disaster roaming acceptance instruction to the gNB 3 in response to a scale-out completion notification. Therefore, according to the scale-out system 1A, in addition to the effects of the scale-out system 1, it is possible to start accepting UEs 2 into the DR site 6 after the scale-out is completed.

[0059] [Variation 1] (Configuration of scale-out method S1B) A scale-out method S1B, which is a variation of the scale-out method S1A executed by the scale-out system 1, will be described with reference to Fig. 7. Fig. 7 is a flow diagram showing the flow of the scale-out method S1B executed by the scale-out system 1. Below, differences from the scale-out method S1A will be described, and similar points will not be described repeatedly.

[0060] In the scale-out method S1B, the acquisition unit 14 acquires progress notifications indicating that the scale-out of the DR site 6 has been completed in stages from the AMF 61 and the container base 62. In the scale-out method S1B, the provision unit 13 provides the gNB 3 with an instruction to gradually accept disaster roaming in response to the progress notification.

[0061] The scale-out method S1B includes steps S100 to S110 included in the scale-out method S1A. Furthermore, the scale-out method S1B includes steps S130 to S154. Note that steps S131 to S136 of the scale-out method S1B are the same as steps S111 to S116 of the scale-out method S1A, and therefore their description will be omitted.

[0062] In steps S137 and S138, the acquisition unit 14 acquires progress notifications indicating the progress of the scale-out from the container board 62 and the AMF 61. For example, in steps S137 and S138, the acquisition unit 14 acquires progress notifications indicating that one-third of the scale-out of the DR site has been completed.

[0063] In step S139, the providing unit 13 provides an instruction to accept disaster roaming to the 5G-RAN 32 (gNB 3) in response to the acquired progress notification. For example, in step S139, when one-third of the scale-out of the DR site is completed, the providing unit 13 provides the 5G-RAN 32 with an instruction to accept disaster roaming for UE 2 whose telephone numbers end with 0 to 2.

[0064] In step S140, based on the acquired disaster roaming acceptance instruction, the 5G-RAN 32 notifies the UE 2 whose telephone number ends with 0 to 2 of a disaster roaming start notification. In step S141, the UE 2 provides the AMF 61 with a registration request for a disaster PLMN corresponding to the DR site 6. In step S142, the AMF 61, the container board 62, and the UDM 52 register the location information of the UE 2 whose registration has been accepted.

[0065] Steps S143 to S148 and steps S149 to S154 of scale-out method S1B are the same as steps S137 to S142, respectively. Steps S143 to S148 are executed when two-thirds of the scale-out of the DR site is complete. In this case, steps S145 and S146 are executed, thereby performing disaster roaming for UE2 whose telephone numbers end with 3 to 5.

[0066] Furthermore, steps S149 to S154 are executed when 3 / 3 of the scale-out of the DR site is completed. That is, steps S149 to S154 are executed when a notification is received indicating that the scale-out of DR site 6 is completed. In this case, steps S151 and S152 are executed, thereby performing disaster roaming for UE2 whose telephone numbers end with 6 to 9. Note that steps S139, S145, and S151 of scale-out method S1B are an example of a provision process.

[0067] (Effects of Scale-Out Method S1B) As described above, in scale-out method S1B, the acquisition unit 14 acquires progress notifications indicating that the scale-out of the DR site 6 has been completed in stages, and the provision unit 13 provides instructions to the gNB 3 to accept disaster roaming in stages in response to the progress notifications. The acquisition unit 14 acquires progress notifications from the AMF 61 or the container base 62, enabling the gradual acceptance of disaster roaming. Therefore, according to scale-out method S1B, in addition to the effects of the scale-out system 1, access by UE 2 according to the resources of the DR site 6 is possible while scaling out the DR site 6.

[0068] [Variation 2] (Configuration of Scale-Out System 1B) The configuration of a scale-out system 1B, which is a variation of the scale-out system 1A, will be described with reference to Fig. 8. Fig. 8 is a schematic diagram showing an overview of the scale-out system 1B. As shown in Fig. 8, the scale-out system 1B includes a UE 2, a gNB 3, a main site 5B, a main site 7, and a DR site 6B. Below, differences from the scale-out system 1A will be described, and similar points will not be described repeatedly.

[0069] The main site 5B is installed in a cloud environment 200. The main site 5B may be installed in, for example, AWS, a public cloud environment. The main site 5B may include a DB (database) 55 that stores various data. The main site 7 includes a 5GC 70 and a DB 75. The 5GC 70 has the same configuration as the 5GC 50. The DB 75 stores various data.

[0070] Main site 5B and main site 7 belong to first region 8. Main site 5B and main site 7 are each an AZ (Availability Zone) of first region 8. By locating main site 5B and main site 7 in first region 8, redundancy is achieved between main sites 5B and 7. Various types of data are synchronized between DB55 and DB75.

[0071] The DR site 6B may include a DB 65 that stores various data. The DR site 6B belongs to a second region 9 that is different from the first region 8. The UPF of the 5GC 60 may communicate with the UPF of the 5GC 70 of the main site 7.

[0072] The main sites 5B and 7 and the DR site 6B are controlled by a controller 10. A storage unit 11 stores information on the number of subscribers accommodated at the main site 5B and the main site 7. A scale-out unit 12 requests the DR site 6B to scale out resources based on the information on the number of subscribers accommodated at the main site 5B and the main site 7.

[0073] (Effects of Scale-Out System 1B) As described above, in the scale-out system 1B, the main sites 5B and 7 are configured to be installed in the cloud environment 200. This makes it possible to reduce the equipment costs and maintenance costs of the main sites 5B and 7. Furthermore, by controlling the main sites 5B and 7 and the DR site 6B by the controller 10, it is possible to achieve the same effects as in the second exemplary embodiment.

[0074] [Other Modifications] In the above-described exemplary embodiment 2 and each modification, the scale-out unit 12 has been described as performing scale-out of the DR sites 6 and 6B based on the information on the number of subscribers accommodated in the main sites 5, 5B, and 7. However, in exemplary embodiment 2 and each modification, the DR sites 6 and 6B may perform scale-out based on resource information other than the information on the number of subscribers accommodated.

[0075] For example, the total traffic (number of accommodated subscribers × traffic per subscriber) and / or the minimum number of worker nodes ((number of required Pods × resources per Pod) ÷ resources per worker node) calculated by the main sites 5, 5B, 7 may be used as resource information for the main sites 5, 5B, 7. In this case, the acquisition unit 14 acquires the total traffic and / or minimum number of worker nodes calculated by the main sites 5, 5B, 7, and the retention unit 11 retains the acquired total traffic and / or minimum number of worker nodes. The scale-out unit 12 requests the DR site 6 to scale out resources based on the retained total traffic and / or minimum number of worker nodes.

[0076] [Example of implementation by software] Some or all of the functions of the scale-out systems 1, 1A, 1B (hereinafter also referred to as "each of the above-mentioned devices") may be implemented by hardware such as an integrated circuit (IC chip), or by software.

[0077] In the latter case, each of the above devices is realized by, for example, a computer that executes instructions of a program, which is software that realizes each function. An example of such a computer (hereinafter referred to as computer C) is shown in Figure 9. Figure 9 is a block diagram showing the hardware configuration of computer C that functions as each of the above devices.

[0078] The computer C includes at least one processor C1 and at least one memory C2. The memory C2 stores a program P for causing the computer C to function as each of the above-mentioned devices. In the computer C, the processor C1 reads and executes the program P from the memory C2, thereby realizing the functions of each of the above-mentioned devices.

[0079] The processor C1 may be, for example, a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a micro processing unit (MPU), a floating point number processing unit (FPU), a physics processing unit (PPU), a tensor processing unit (TPU), a quantum processor, a microcontroller, or a combination thereof. The memory C2 may be, for example, a flash memory, a hard disk drive (HDD), a solid state drive (SSD), or a combination thereof.

[0080] The computer C may further include a RAM (Random Access Memory) for expanding the program P during execution and for temporarily storing various data. The computer C may also include a communication interface for transmitting and receiving data to and from other devices. The computer C may also include an input / output interface for connecting input / output devices such as a keyboard, a mouse, a display, and a printer.

[0081] The program P can also be recorded on a non-transitory, tangible recording medium M that can be read by the computer C. Such a recording medium M can be, for example, a tape, a disk, a card, a semiconductor memory, or a programmable logic circuit. The computer C can acquire the program P via such a recording medium M. The program P can also be transmitted via a transmission medium. Such a transmission medium can be, for example, a communication network or broadcast waves. The computer C can also acquire the program P via such a transmission medium.

[0082] Furthermore, the functions of each of the devices may be realized by a single processor provided in a single computer, by multiple processors provided in a single computer working in cooperation, or by multiple processors provided in each of multiple computers working in cooperation. Furthermore, the programs for causing each of the devices to realize the functions may be stored in a single memory provided in a single computer, or may be distributed and stored in multiple memories provided in a single computer, or may be distributed and stored in multiple memories provided in each of multiple computers.

[0083] [Appendix A] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0084] (Appendix A1) A scale-out system for scaling out a DR site (Disaster Recovery site) connected to a mobile communication network, comprising: a storage means for storing resource information of a main site acquired in advance; a scale-out means for requesting the DR site to scale out resources based on the stored resource information in response to acquisition of disaster information; and a provision means for providing a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site in response to a notification regarding the scale-out status acquired from the DR site.

[0085] (Supplementary Note A2) The scale-out system according to Supplementary Note A1, further comprising a first acquisition unit that acquires the resource information from the main site.

[0086] (Supplementary Note A3) The scale-out system according to Supplementary Note A1 or A2, further comprising a second acquisition unit that acquires the disaster information from the main site.

[0087] (Supplementary Note A4) The scale-out system according to any one of Supplementary Notes A1 to A3, further comprising a calculation unit that calculates resources required for scaling out the DR site from the stored resource information.

[0088] (Appendix A5) The scale-out system according to Appendix A4, wherein the scale-out means provides a scale-out request including at least one of the number of pods and the number of worker nodes required for scale-out to at least one of a network function (NF) of a core network and a container platform generated by the NF.

[0089] (Appendix A6) The scale-out system described in Appendix A5, further comprising a third acquisition means for acquiring a scale-out completion notification indicating that the scale-out of the DR site has been completed as a notification regarding the scale-out status from at least one of the NF and the container platform.

[0090] (Supplementary Note A7) The scale-out system according to Supplementary Note A6, wherein the providing unit provides an instruction to accept the disaster roaming to a radio access network (RAN) node in response to the scale-out completion notification.

[0091] (Appendix A8) The scale-out system described in Appendix A6, wherein the third acquisition means acquires a progress notification from at least one of the NF and the container platform indicating that the scale-out of the DR site has been completed in stages, and the providing means provides a radio access network (RAN) node with an instruction to gradually accept the disaster roaming based on the progress notification.

[0092] [Appendix B] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0093] (Appendix B1) A method executed by a scale-out system that scales out a DR site (Disaster Recovery site) connected to a mobile communication network, comprising: a holding process in which at least one processor holds resource information of a main site acquired in advance; a scale-out process in which the at least one processor, upon acquisition of disaster information, requests the DR site to scale out resources based on the resource information it has held; and a providing process in which, in response to a notification regarding the scale-out status acquired from the DR site, it provides a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site.

[0094] (Supplementary Note B2) The scale-out method according to Supplementary Note B1, further comprising a first acquisition process of acquiring the resource information from the main site.

[0095] (Supplementary Note B3) The scale-out method according to Supplementary Note B1 or B2, further comprising a second acquisition process of acquiring the disaster information from the main site.

[0096] (Supplementary Note B4) The scale-out method according to any one of Supplementary Notes B1 to B3, further comprising a calculation process for calculating resources required for scaling out the DR site from the stored resource information.

[0097] (Appendix B5) The scale-out method described in Appendix B4, in which, in the scale-out process, a scale-out request including at least one of the number of pods and the number of worker nodes required for scale-out is provided to at least one of a network function (NF) of a core network and a container platform generated by the NF.

[0098] (Appendix B6) The scale-out method described in Appendix B5, further including a third acquisition process for acquiring a scale-out completion notification indicating that the scale-out of the DR site has been completed as a notification regarding the scale-out status from at least one of the NF and the container platform.

[0099] (Supplementary Note B7) The scale-out method according to Supplementary Note B6, wherein in the providing process, an instruction to accept the disaster roaming is provided to a radio access network (RAN) node in response to the scale-out completion notification.

[0100] (Appendix B8) A scale-out method as described in Appendix B6, wherein in the third acquisition process, a progress notification indicating that the scale-out of the DR site has been completed in stages is acquired from at least one of the NF and the container platform as a notification regarding the scale-out status, and in the provision process, an instruction to gradually accept the disaster roaming is provided to a radio access network (RAN) node in response to the progress notification.

[0101] [Appendix C] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0102] (Appendix C1) A scale-out program that causes at least one processor to function as a scale-out system that scales out a DR site (Disaster Recovery site) connected to a mobile communication network, the scale-out program causing the at least one processor to function as: a holding means that holds resource information of a main site that has been acquired in advance; a scale-out means that, upon acquisition of disaster information, requests the DR site to scale out resources based on the held resource information; and a providing means that, in response to a notification regarding the scale-out status acquired from the DR site, provides a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site.

[0103] (Supplementary Note C2) The scale-out system according to Supplementary Note C1, wherein the at least one processor further functions as a first acquisition unit that acquires the resource information from the main site.

[0104] (Supplementary Note C3) The scale-out system according to Supplementary Note C1 or C2, wherein the at least one processor further functions as a second acquisition unit that acquires the disaster information from the main site.

[0105] (Supplementary Note C4) The scale-out system according to any one of Supplementary Notes C1 to C3, further causing the at least one processor to function as a calculation means for calculating resources required for scaling out the DR site from the resource information held therein.

[0106] (Appendix C5) The scale-out system according to Appendix C4, wherein the scale-out means provides a scale-out request including at least one of the number of pods and the number of worker nodes required for scale-out to at least one of a network function (NF) of a core network and a container platform generated by the NF.

[0107] (Appendix C6) A scale-out system described in Appendix C5, wherein the at least one processor further functions as a third acquisition means for acquiring a scale-out completion notification indicating that the scale-out of the DR site has been completed from at least one of the NF and the container platform as a notification regarding the scale-out status.

[0108] (Supplementary Note C7) The scale-out system according to Supplementary Note C6, wherein the providing unit provides an instruction to accept the disaster roaming to a radio access network (RAN) node in response to the scale-out completion notification.

[0109] (Appendix C8) The scale-out system described in Appendix C6, wherein the third acquisition means acquires a progress notification indicating that the scale-out of the DR site has been completed in stages as a notification regarding the scale-out status from at least one of the NF and the container platform, and the providing means provides an instruction to a radio access network (RAN) node to accept the disaster roaming in stages in response to the progress notification.

[0110] [Appendix D] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0111] (Appendix D1) A controller included in a system that scales out a DR site (Disaster Recovery site) connected to a mobile communication network, comprising: a storage means for storing previously acquired resource information of a main site; a scale-out means for requesting the DR site to scale out resources based on the stored resource information in response to acquisition of disaster information; and a providing means for providing a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site in response to a notification regarding the scale-out status acquired from the DR site.

[0112] (Supplementary Note D2) The controller according to Supplementary Note D1, further comprising a first acquisition means for acquiring the resource information from the main site.

[0113] (Supplementary Note D3) The controller according to Supplementary Note D1 or D2, further comprising a second acquisition means for acquiring the disaster information from the main site.

[0114] (Supplementary Note D4) The controller according to any one of Supplementary Note D1 to D3, further comprising: a calculation unit that calculates resources required for scaling out the DR site from the stored resource information.

[0115] (Appendix D5) The controller according to appendix D4, wherein the scale-out means provides a scale-out request including at least one of the number of pods and the number of worker nodes required for scale-out to at least one of a network function (NF) of a core network and a container platform generated by the NF.

[0116] (Appendix D6) The controller described in Appendix D5, further comprising a third acquisition means for acquiring a scale-out completion notification indicating that the scale-out of the DR site has been completed as a notification regarding the scale-out status from at least one of the NF and the container platform.

[0117] (Supplementary Note D7) The controller according to Supplementary Note D6, wherein the providing means provides an instruction to accept the disaster roaming to a radio access network (RAN) node in response to the scale-out completion notification.

[0118] (Appendix D8) The controller according to Appendix D6, wherein the third acquisition means acquires a progress notification indicating that the scale-out of the DR site has been completed in stages as a notification regarding the scale-out status from at least one of the NF and the container platform, and the providing means provides an instruction to a radio access network (RAN) node to accept the disaster roaming in stages in response to the progress notification.

[0119] [Appendix E] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0120] (Appendix E1) A scale-out system for scaling out a DR site (Disaster Recovery site) connected to a mobile communication network, comprising at least one processor, the at least one processor performing the following operations: a retention process for retaining resource information of a main site acquired in advance; a scale-out process for requesting the DR site to scale out resources based on the retained resource information, in response to acquisition of disaster information; and a provision process for providing a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site, in response to a notification regarding the scale-out status acquired by the at least one processor from the DR site.

[0121] (Supplementary Note E2) The scale-out system according to Supplementary Note E1, wherein the at least one processor further executes a first acquisition process to acquire the resource information from the main site.

[0122] (Supplementary Note E3) The scale-out system according to Supplementary Note E1 or E2, wherein the at least one processor further executes a second acquisition process of acquiring the disaster information from the main site.

[0123] (Appendix E4) The scale-out system according to any one of appendices E1 to E3, wherein the at least one processor further executes a calculation process to calculate resources required for scaling out the DR site from the resource information held therein.

[0124] (Appendix E5) The scale-out system described in Appendix E4, wherein in the scale-out process, a scale-out request including at least one of the number of pods and the number of worker nodes required for scale-out is provided to at least one of a network function (NF) of a core network and a container platform generated by the NF.

[0125] (Appendix E6) A scale-out system described in Appendix E5, further executing a third acquisition process to acquire a scale-out completion notification indicating that the scale-out of the DR site has been completed as a notification regarding the scale-out status from at least one of the NF and the container platform.

[0126] (Supplementary Note E7) The scale-out system according to Supplementary Note E6, wherein in the providing process, an instruction to accept the disaster roaming is provided to a radio access network (RAN) node in response to the scale-out completion notification.

[0127] (Appendix E8) A scale-out system as described in Appendix E6, wherein in the third acquisition process, a progress notification indicating that the scale-out of the DR site has been completed in stages is acquired from at least one of the NF and the container platform as a notification regarding the scale-out status, and in the provision process, an instruction to gradually accept the disaster roaming is provided to a radio access network (RAN) node in response to the progress notification.

[0128] [Appendix F] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0129] (Appendix F1) A non-transitory recording medium having recorded thereon a scale-out program that causes at least one processor to function as a scale-out system that scales out a DR site (Disaster Recovery site) connected to a mobile communication network, the scale-out program causing the at least one processor to execute the following: a retention process that retains resource information of a main site that has been acquired in advance; a scale-out process that, upon acquisition of disaster information, requests the DR site to scale out resources based on the retained resource information; and a provision process that, in response to a notification regarding the scale-out status acquired from the DR site, provides a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site.

[0130] This application claims priority based on Japanese Patent Application No. 2024-117995, filed on July 23, 2024, the disclosure of which is incorporated herein by reference in its entirety.

[0131] 1, 1A, 1B Scale-out system 10 Controller 11 Storage unit 12 Scale-out unit 13 Provision unit 14 Acquisition unit 15 Calculation unit 5, 5B, 7 Main site 6, 6B DR site

Claims

1. A scale-out system for scaling out a DR site (Disaster Recovery site) connected to a mobile communication network, comprising: a storage means for storing resource information of a main site acquired in advance; a scale-out means for requesting the DR site to scale out resources based on the stored resource information in response to acquisition of disaster information; and a provision means for providing a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site in response to a notification regarding the scale-out status acquired from the DR site.

2. The scale-out system according to claim 1, further comprising a first acquisition means for acquiring the resource information from the main site.

3. A scale-out system according to claim 1 or claim 2, further comprising a second acquisition means for acquiring the disaster information from the main site.

4. The scale-out system according to any one of claims 1 to 3, further comprising a calculation means for calculating resources required for scaling out the DR site from the resource information held therein.

5. The scale-out system described in claim 4, wherein the scale-out means provides a scale-out request including at least one of the number of pods and the number of worker nodes required for scale-out to at least one of a network function (NF) of the core network and a container platform generated by the NF.

6. The scale-out system described in claim 5, further comprising a third acquisition means for acquiring a scale-out completion notification indicating that the scale-out of the DR site has been completed as a notification regarding the scale-out status from at least one of the NF and the container platform.

7. The scale-out system according to claim 6, wherein the providing means provides an instruction to accept the disaster roaming to a radio access network (RAN) node in response to the scale-out completion notification.

8. The scale-out system described in claim 6, wherein the third acquisition means acquires a progress notification indicating that the scale-out of the DR site has been completed in stages as a notification regarding the scale-out status from at least one of the NF and the container platform, and the providing means provides an instruction to a radio access network (RAN) node to gradually accept the disaster roaming in response to the progress notification.

9. A method executed by a scale-out system that scales out a DR site (Disaster Recovery site) connected to a mobile communication network, the method comprising: retaining resource information of a main site acquired in advance; requesting the DR site to scale out resources based on the retained resource information upon acquisition of disaster information; and providing a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site in response to a notification regarding the scale-out status acquired from the DR site.

10. The scale-out method according to claim 9, wherein the resource information is acquired from the main site.

11. The scale-out method according to claim 9 or 10, wherein the disaster information is acquired from the main site.

12. A scale-out method according to any one of claims 9 to 11, further comprising calculating resources required for scaling out the DR site from the stored resource information.

13. The scale-out method described in claim 12, wherein in a scale-out request to the DR site, a scale-out request including at least one of the number of pods and the number of worker nodes required for scale-out is provided to at least one of a network function (NF) of a core network and a container platform generated by the NF.

14. A scale-out method as described in claim 13, wherein a scale-out completion notification indicating that the scale-out of the DR site has been completed is obtained from at least one of the NF and the container platform as a notification regarding the scale-out status.

15. The scale-out method according to claim 14, wherein providing the acceptance instruction comprises providing the disaster roaming acceptance instruction to a radio access network (RAN) node in response to the scale-out completion notification.

16. The scale-out method described in claim 14, wherein, in obtaining the scale-out completion notification, a progress notification indicating that the scale-out of the DR site has been completed in stages is obtained from at least one of the NF and the container platform as a notification regarding the scale-out status, and, in providing the acceptance instruction, a gradual acceptance instruction for the disaster roaming is provided to a radio access network (RAN) node in response to the progress notification.

17. A computer-readable recording medium having recorded thereon a scale-out program that causes at least one processor to function as a scale-out system that scales out a DR site (Disaster Recovery site) connected to a mobile communications network, the scale-out program causing the at least one processor to function as: a storage means that stores previously acquired resource information of the main site; a scale-out means that, upon acquisition of disaster information, requests the DR site to scale out resources based on the stored resource information; and a provision means that, in response to a notification regarding the scale-out status acquired from the DR site, provides a disaster roaming acceptance instruction that enables the DR site to use a disaster public land mobile network (PLMN) corresponding to the DR site.

Images