Rolling update of network function

The rolling update method for network functions in wireless communication systems allows for sequential updates of execution environments based on terminal connections, enabling continuous service and efficient updates by managing pod updates through a core NW control server and GC servers.

WO2024247169A1PCT designated stage expired Publication Date: 2024-12-05RAKUTEN SYMPHONY INC +1
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2023/020300
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-31
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Existing network function updates in wireless communication systems, such as 5G, are challenging due to the difficulty in stopping network functions for updating while maintaining continuous service, requiring advance user notifications and limiting immediate updates.

Method used

A rolling update method that determines the number of execution environments to be stopped based on the number of connected communication terminals, allowing for sequential software updates in these environments without disrupting service, using a core NW control server and GC servers to manage and instruct VNF updates across multiple pods.

Benefits of technology

Enables network function updates while continuing to provide services by sequentially stopping and updating pods, reducing the period of coexistence between updated and non-updated pods, thus improving update efficiency and minimizing service disruption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023020300_05122024_PF_FP_ABST
    Figure JP2023020300_05122024_PF_FP_ABST
Patent Text Reader

Abstract

This update control device has one or more processors. The one or more processors execute processing comprising: determining the number of execution environments to be stopped among a plurality of execution environments for executing processing relating to communication terminals being connected to an update cell corresponding to software to be updated by executing the software, on the basis of the number of the communication terminals being connected to the update cell; and issuing an instruction to update the software to be executed in each execution environment for each of the determined number of execution environments.
Need to check novelty before this filing date? Find Prior Art

Description

Rolling updates for network functions

[0001] The present disclosure relates to rolling updates of network features.

[0002] In recent years, in wireless communication systems such as 5G, network functions are sometimes virtualized, and the virtualized network functions are also referred to as VNFs (Virtual Network Functions). VNFs can be deployed in various locations in the network, enabling flexible network configurations. For example, when it is desired to reduce the latency of network services, VNFs that provide services to end users are deployed in medium- or small-scale facilities such as RDCs (Regional Data Centers) or GCs (Group Centers) that are located closer to the end users, rather than in large-scale facilities such as CDCs (Central Data Centers) built in the center of the network.

[0003] Special table 2022-530580 publication Special table 2019-519180 publication

[0004] In general, from the viewpoints of security, resource utilization efficiency, and the like, it is preferable that software be updated as needed. However, for software related to network functions such as the VNF described above, it is difficult to stop the function for an update because the network must be continuously operated. In other words, updating the network function requires prior preparation, such as notifying users that the service will be stopped, and immediate updates are not easy.

[0005] The present disclosure has been made in consideration of the above, and aims to provide a rolling update of network functions that can update network functions while continuing to provide services.

[0006] According to one aspect of the present disclosure, the update control device has one or more processors, and the one or more processors perform processing including determining the number of execution environments to stop, among multiple execution environments that execute processing related to communication terminals connected to an update cell corresponding to the software by executing the software to be updated, based on the number of communication terminals connected to the update cell, and instructing an update of the software executed in each execution environment for each of the determined number of execution environments.

[0007] According to another aspect of the present disclosure, the communication control device has one or more processors, and the one or more processors perform processing including: constructing multiple execution environments that execute processing related to communication terminals connected to a cell by executing software; and, when an instruction to update the software is obtained, updating software executed in other execution environments among the multiple execution environments, excluding at least an execution environment that is compatible with the communication terminals connected to the cell.

[0008] According to another aspect of the present disclosure, the update control method includes determining the number of execution environments to be stopped from among a plurality of execution environments that execute processes related to communication terminals connected to an update cell corresponding to the software by executing the software to be updated, based on the number of communication terminals connected to the update cell, and instructing an update of the software executed in each of the determined number of execution environments.

[0009] According to another aspect of the present disclosure, a software update method includes constructing a plurality of execution environments that execute software to perform processing related to a communication terminal connected to a cell, and when obtaining an instruction to update the software, updating software executed in other execution environments among the plurality of execution environments, excluding at least an execution environment that is compatible with the communication terminal connected to the cell.

[0010] FIG. 1 is a diagram illustrating an example of a communication system according to an embodiment. FIG. 2 is a block diagram illustrating a configuration of a core NW control server according to an embodiment. FIG. 3 is a block diagram illustrating a configuration of a GC server according to an embodiment. FIG. 4 is a diagram illustrating a VNF update method according to an embodiment. FIG. 5 is a diagram illustrating a specific example of VNF update. FIG. 6 is a block diagram illustrating an example of the hardware configuration of a core NW control server. FIG. 7 is a block diagram illustrating an example of the hardware configuration of a GC server.

[0011] Hereinafter, an embodiment according to the present disclosure will be described with reference to the accompanying drawings. The embodiment described below is an example and should not be construed as being limited by this description.

[0012] Fig. 1 is a diagram illustrating an example of a communication system according to an embodiment. In the communication system illustrated in Fig. 1, a CDC 10, which is a large-scale facility, is connected to a plurality of GCs 20, which are small-scale facilities. Although not illustrated in Fig. 1, the plurality of GCs 20 may be connected in a ring configuration, and an RDC may be connected between the CDC 10 and the GC 20.

[0013] The CDC 10 has a core network control server (hereinafter abbreviated as "core NW control server") 100, and each GC 20 has a GC server 200. Each GC server 200 is connected to an RU (Radio Unit) 30, which is a wireless base station, and each RU 30 forms a cell 35 indicating a radio wave coverage area.

[0014] The core NW control server 100 is accommodated in the CDC 10 located at the center of the network constituting the communication system and has a core network function in the communication system. That is, the core NW control server 100 deploys software including VNFs to the GC servers 200 of the GC 20 and controls updates of the software deployed to each GC server 200. For example, the core NW control server 100 instructs the GC server 200 to update the VNFs in units of pods (Pods), which are execution environments for executing the VNFs. That is, the core NW control server 100 calculates the number of pods that can be stopped while maintaining service provision to users in the cell 35 in the GC server 200 that controls the cell 35, determines the number of pods to be stopped to be equal to or less than the number of pods that can be stopped, and instructs the GC server 200 to update the VNFs by the determined number of pods to be stopped. It is preferable to update all pods as quickly as possible to shorten the period during which updated and unupdated pods coexist. Therefore, it is preferable to increase the number of stopped pods to reduce the total number of updates. The configuration and operation of the core NW control server 100 will be described in detail later.

[0015] The GC server 200 deploys various VNFs in accordance with instructions from the core NW control server 100 and controls communications in the communication system by executing the VNFs in a virtual environment. For example, the GC server 200 executes VNFs that function as a CU (Central Unit) or a DU (Distributed Unit) to control the RUs 30 that form each cell 35. At this time, the GC server 200 generates multiple pods as VNF execution environments and executes the VNFs in each pod. For example, the GC server 200 may generate multiple pods corresponding to one cell 35 and execute VNFs in each pod to perform processing related to users connected to the cell 35.

[0016] When the GC server 200 is instructed by the core NW control server 100 to update the VNFs, it sequentially updates the VNFs in the pods for the specified number of update pods at a time. That is, the GC server 200 sequentially updates the VNFs in some stoppable pods that are not being used in processing for providing services. This makes it possible to update the VNFs without simultaneously stopping all the VNFs running on the GC server 200, and to update the network functions while continuing to provide services.

[0017] 2 is a block diagram showing a configuration of a core NW control server 100 according to an embodiment. The core NW control server 100 shown in FIG. 2 includes a network function management unit (hereinafter abbreviated as “NW function management unit”) 110, a cell management unit 120, a cell selection unit 130, an update target number determination unit 140, and an update instruction unit 150.

[0018] The NW function management unit 110 manages network functions running in each GC server 200. That is, the NW function management unit 110 stores information on VNFs deployed in each GC server 200 in association with identification information of the GC server 200. When the time comes for a VNF to be updated, the NW function management unit 110 notifies the cell selection unit 130 that a VNF update is required for the GC server 200 on which the VNF is deployed.

[0019] The cell management unit 120 manages the cells 35 under the jurisdiction of each GC server 200. That is, the cell management unit 120 stores information on the cells 35 formed by the RUs 30 connected to each GC server 200, in association with the identification information of the GC server 200. The information on the cells 35 stored by the cell management unit 120 includes location information on the cells 35, the number of pods that execute the VNFs corresponding to the cells 35, information on user terminals (UE: User Equipment, also referred to as communication terminals) present in the cell 35, and the like.

[0020] When the cell selection unit 130 is notified by the NW function management unit 110 that a VNF needs to be updated, the cell selection unit 130 refers to the information stored in the cell management unit 120 and selects the cell 35 in which the VNF to be updated operates. That is, the cell selection unit 130 selects the cell 35 (hereinafter referred to as the "update cell") under the jurisdiction of the GC server 200 in which the VNF to be updated operates.

[0021] Furthermore, the cell selection unit 130 refers to the information stored in the cell management unit 120 and selects cells 35 located in the vicinity of the updated cell (hereinafter referred to as "neighboring cells"). Here, the cell selection unit 130 may select multiple neighboring cells for one updated cell. Then, based on information on UEs present in the updated cell and neighboring cells, the cell selection unit 130 identifies UEs that can be handed over from the updated cell to the neighboring cells. Specifically, the cell selection unit 130 identifies UEs that are connected to the updated cell and are located in an area where the updated cell and the neighboring cells overlap as UEs that can be handed over.

[0022] At this time, the cell selection unit 130 may expand the neighboring cells so that more UEs can be handed over. That is, the cell selection unit 130 may decide to expand the neighboring cells by increasing the transmission power of the RUs 30 forming the neighboring cells. Furthermore, the cell selection unit 130 may decide to increase the number of pods corresponding to the neighboring cells when it is determined that the capacity of the pods executing the VNF corresponding to the neighboring cells will be insufficient if the UE of the updated cell is handed over to the neighboring cells. When the cell selection unit 130 determines adjustments related to the neighboring cells, such as expanding the neighboring cells or increasing the number of pods corresponding to the neighboring cells, it requests the GC server 200 that manages the neighboring cells to make adjustments related to the neighboring cells.

[0023] The update target number determination unit 140 determines the number of pods to be updated by VNF in the GC server 200 that manages the update cell, based on the number of UEs connected to the update cell. When the number of UEs connected to the update cell is reduced by handing over to a neighboring cell, the update target number determination unit 140 determines the number of pods to be updated by VNF in the GC server 200 that manages the update cell, based on the number of pods that execute VNF in the GC servers 200 that manage the update cell and the neighboring cell, and the number of UEs that can be handed over from the update cell to the neighboring cell. For example, when handing over UEs from the update cell to a neighboring cell, the update target number determination unit 140 determines the number of pods to be stopped in the GC server 200 that manages the update cell, based on the number of UEs to be handed over to the neighboring cell and the number of UEs that maintain connection to the update cell, and determines the number of stopped pods as the number of pods to be updated. That is, the update target number determination unit 140 determines the number of pods that do not need to be operated in the GC server 200 that manages the update cell as the number of pods to be updated.

[0024] The update instruction unit 150 generates an update instruction to instruct an update of the VNF and transmits the generated update instruction to the GC server 200 that manages the update cell. That is, the update instruction unit 150 specifies the number of pods to be stopped in the update cell and instructs the GC server 200 that manages the update cell to update the VNF. When the number of UEs connected to the update cell is reduced by handing over them to neighboring cells, the update instruction unit 150 also specifies the number of UEs to be handed over from the update cell to neighboring cells. In this way, by handing over UEs to neighboring cells, the number of pods to be stopped in the update cell can be increased.

[0025] 3 is a block diagram showing the configuration of a GC server 200 according to an embodiment of the present invention. The GC server 200 shown in FIG.

[0026] The cell control unit 210 controls the cell 35 under the jurisdiction of the GC server 200 by executing the VNF. Here, the cell control unit 210 builds a pod for executing the VNF in the control area of ​​each cell 35 formed by the RUs 30 connected to the GC server 200, and executes a VNF having, for example, a virtualized DU (vDU) function in each pod. In this case, one or more pods are built in the control area of ​​each cell 35, and each pod executes processing related to a number of UEs according to its processing capacity. Note that there are various types of VNFs executed, and it is possible that pods are not divided for each cell 35.

[0027] When the cell control unit 210 receives a VNF update instruction from the core NW control server 100, it instructs the UEs present in each cell 35 to measure radio wave intensity for handover, and determines whether or not to handover each UE based on the measurement results obtained from the UEs. Then, the cell control unit 210 instructs the UEs determined to be handed over to specify a handover destination cell and to perform the handover. Such a handover initiated by the network side is also called a network initiated handover. This embodiment may use a general network initiated handover method.

[0028] The update execution unit 220 stops some of the pods in the control area of ​​the update cell based on the number of pods to be updated in VNF determined by the update target number determination unit 140, and performs a VNF update. When UEs connected to the update cell are handed over to a neighboring cell, the update execution unit 220, upon receiving a VNF update instruction from the core NW control server 100, determines whether the number of UEs specified in the update instruction have handed over from the update cell to a neighboring cell. Then, when the specified number of UEs have handed over, the update execution unit 220 stops some of the pods in the control area of ​​the update cell based on the number of pods to be updated in VNF, and performs a VNF update for the stopped pods. Furthermore, the update execution unit 220 sequentially changes the pods to be stopped and sequentially updates all pods in the control area of ​​the update cell. In other words, the update execution unit 220 stops pods by the number of pods to be updated specified in the update instruction, and performs a VNF update.

[0029] Next, a method for updating a VNF in a communication system configured as described above will be described with reference to the sequence diagram shown in Fig. 4. Here, a case where a UE connected to an updated cell is handed over to a neighboring cell will be described.

[0030] When the timing for updating the VNF deployed in the GC server 200 arrives, the NW function management unit 110 of the core NW control server 100 notifies the cell selection unit 130 that the VNF needs to be updated for this GC server 200. Here, the explanation will be continued assuming that the VNF needs to be updated for the GC server 200 that manages cell #1, which is one of the cells 35.

[0031] When it is notified that a VNF needs to be updated, the cell selection unit 130 selects an update cell managed by the GC server 200 on which the VNF to be updated runs (step S101). Here, the explanation will be continued assuming that cell #1 managed by the GC server 200 is selected as the update cell.

[0032] Furthermore, by referring to the information stored in the cell management unit 120, the cell selection unit 130 selects neighboring cells located around the updated cell (step S102). Here, the explanation will be continued assuming that cell #2, which is one of the cells 35, is selected as the neighboring cell. Note that multiple neighboring cells may be selected for one updated cell, and the GC server 200 responsible for the updated cell and the GC server 200 responsible for the neighboring cells may be the same GC server 200 or different GC servers 200.

[0033] Then, by referring to the information stored in the cell management unit 120, the cell selection unit 130 identifies UEs that can be handed over from the updated cell to a neighboring cell. That is, among UEs connected to the updated cell, UEs located in an area where the updated cell and the neighboring cell overlap are identified as UEs that can be handed over. At this time, adjustment of the neighboring cells may be performed, such as expanding the neighboring cell by increasing the transmission power of RU #2 that forms the neighboring cell or increasing the pod corresponding to the neighboring cell (step S103). When adjusting the neighboring cell, an instruction to increase the transmission power of RU #2 or increase the pod is issued to the cell #2 control area of ​​the GC server 200 that manages cell #2 (step S104).

[0034] The cell #2 control area increases the transmission power of RU #2 in accordance with the instruction to expand the neighboring cells or increase the pod corresponding to cell #2. In this way, by expanding the neighboring cells or increasing the pod, the number of UEs that are handed over from the updated cell to the neighboring cells increases. In other words, the minimum number of UEs that maintain connection with the updated cell is made smaller than before the neighboring cells were expanded or the pod was increased. This allows the number of pods that can be stopped in the cell #1 control area of ​​the GC server 200 that manages cell #1 to be increased.

[0035] When a UE that can be handed over from the update cell to a neighboring cell is identified, the number of pods to be updated in the cell #1 control area of ​​the GC server 200 that manages the cell #1 is determined by the update target number determination unit 140 (step S105). Specifically, the number of stopped pods that is equal to or less than the number of pods that can be stopped in the cell #1 control area when the UE is handed over from the update cell to the neighboring cell is determined as the number of pods to be updated.

[0036] Then, an update instruction specifying the number of UEs to be handed over from the updated cell to a neighboring cell and the number of pods to be updated is transmitted to the cell #1 control area of ​​the GC server 200 that manages cell #1 (step S106).

[0037] When the GC server 200 that manages the updated cell receives the update instruction, the cell #1 control area transmits a signal strength measurement instruction to the UE connected to cell #1 via RU #1 (step S107). Upon receiving the measurement instruction, the UE measures the signal strength from nearby RUs 30, including RU #1 and RU #2. The UE then transmits the signal strength measurement results to the GC server 200 via RU #1 (step S108).

[0038] When the GC server 200 receives the measurement result of the radio wave strength, the cell #1 control area determines whether it is possible to hand over the UE from the updated cell to a neighboring cell (step S109). That is, the cell #1 control area determines whether the radio wave strength from the RU #2 forming the neighboring cell is equal to or greater than a predetermined threshold, and if the radio wave strength is equal to or greater than the predetermined threshold, determines to hand over the UE to the neighboring cell, cell #2. Then, the cell #1 control area transmits a handover instruction to cell #2 via RU #1 to the UE that has been determined to be handed over (step S110).

[0039] When the UE receives the handover instruction, it executes handover to the instructed cell #2 and starts communication with the cell #2 control area via RU #2 that forms cell #2 (step S111). When the UE hands over to cell #2, the amount of processing related to the UE is reduced in the cell #1 control area, so it becomes possible to stop part of the pod.

[0040] When a UE executes handover to a neighboring cell, the update execution unit 220 determines whether or not the number of UEs specified by the update instruction or more has handed over from the updated cell to the neighboring cell. If the result of this determination is that the number of UEs specified or more has handed over to the neighboring cell, it is determined that the processing amount of the cell #1 control region has been sufficiently reduced, and an update of the VNF executed in the pod of the cell #1 control region is executed (step S112).

[0041] Specifically, some of the pods are stopped in the cell #1 control area, and the VNFs of the stopped pods are updated. At this time, the pods are stopped sequentially by the number of pods to be updated specified by the update instruction, and the VNFs of the stopped pods are updated. A specific example of such a VNF update will be described with reference to FIG. 5.

[0042] As shown in the upper diagram of Figure 5, the pods established in the cell #1 control area each execute VNF to perform processing related to UEs located in cell #1. Similarly, the pods established in the cell #2 control area each execute VNF to perform processing related to UEs located in cell #2. Because cell #1 is an update cell, the UEs located in cell #1 perform handover to cell #2, a neighboring cell.

[0043] As a result, as shown in the middle diagram of Figure 5, some UEs in cell #1 are handed over to cell #2, and processing related to the handed-over UEs is performed by the pod established in the cell #2 control area. As a result, in the cell #1 control area, two pods 310 are no longer in operation and can be stopped. Therefore, the VNFs of these two pods 310 are updated, and the pods are stopped two by two, and the VNFs are updated. During this time, the three pods that are not the target of the update remain in operation in the cell #1 control area, so service provision to UEs in cell #1 can continue.

[0044] When updating of the VNFs of all pods in the cell #1 control area is completed, the UEs that have been handed over to cell #2 are handed over again to cell #1, and processing for each UE is performed using the updated VNFs, as shown in the lower diagram in Fig. 5. Although omitted in Fig. 5, after updating the VNFs of all pods in the cell #1 control area, the VNFs of all pods in the cell #2 control area may be updated in the same manner.

[0045] 4, when the VNF update of all pods in the cell #1 control area is completed, the cell #1 control area notifies the core NW control server 100 that the VNF update has been completed (step S113). The core NW control server 100 notifies the cell #2 control area that the VNF update of the cell #1 control area has been completed (step S114), and if the transmission power of RU #2 has been increased or the number of pods has been increased, the core NW control server 100 completes the adjustment of these neighboring cells.

[0046] When the completion of the VNF update is notified, the cell #2 control area transmits a signal strength measurement instruction to the UE connected to cell #2 via RU #2 (step S115). Upon receiving the measurement instruction, the UE measures the signal strength from RUs 30, including RU #1 and RU #2, located nearby. The UE then transmits the signal strength measurement results to the GC server 200 via RU #2 (step S116).

[0047] When the GC server 200 receives the measurement result of the radio wave strength, the cell #2 control area determines whether it is possible to hand over the UE from the neighboring cell to the updated cell (step S117). That is, the cell #2 control area determines whether the radio wave strength from the RU #1 forming the updated cell is equal to or greater than a predetermined threshold, and if the radio wave strength is equal to or greater than the predetermined threshold, determines to hand over the UE to cell #1, which is the updated cell to which the UE was originally connected. Then, the cell #2 control area transmits a handover instruction to cell #1 via RU #2 to the UE that has been determined to be handed over (step S118).

[0048] When the UE receives the handover instruction, it executes handover to the instructed cell #1 and starts communication with the cell #1 control area via the RU #1 that forms the cell #1 (step S119). After that, similar to the VNF update in the cell #1 control area, the VNF update may also be executed in the cell #2 control area.

[0049] As described above, according to this embodiment, when updating VNFs deployed on a GC server, some of the pods are stopped based on the number of UEs connected to the cell under the GC server's jurisdiction, and the VNFs are updated. Also, the UEs connected to the cell under the GC server's jurisdiction are handed over to reduce the amount of processing required to control the cell, and the VNFs in the pods can be updated in order, one by one, for each inactive pod. In this way, VNFs can be updated without simultaneously stopping all VNFs running on the GC server, and network functions can be updated while continuing to provide services.

[0050] The core NW control server 100 according to the embodiment can be configured using a processor and a memory. Fig. 6 is a block diagram showing an example of a hardware configuration of the core NW control server 100 according to the embodiment. As shown in Fig. 6, the core NW control server 100 includes a processor 101, a memory 102, a storage 103, and a communication unit 104.

[0051] The processor 101 has, for example, a central processing unit (CPU), a field programmable gate array (FPGA), or a digital signal processor (DSP), and controls the entire core NW control server 100 and executes various types of information processing.

[0052] The memory 102 includes, for example, a random access memory (RAM) or a read only memory (ROM), and stores information used in the information processing executed by the processor 101 .

[0053] The storage 103 includes, for example, a hard disk drive (HDD) or a solid state drive (SSD), and stores various types of data.

[0054] The communication unit 104 has an interface for performing wired or wireless communication, and communicates with the GC server 200 .

[0055] The core NW control server 100 may have other components (not shown), such as a display and an operation switch.

[0056] Similarly, the GC server 200 according to the embodiment can be configured using a processor and a memory. Fig. 7 is a block diagram showing an example of the hardware configuration of the GC server 200 according to the embodiment. As shown in Fig. 7, the GC server 200 includes a processor 201, a memory 202, a storage 203, and a communication unit 204.

[0057] The processor 201 includes, for example, a CPU, an FPGA, or a DSP, and controls the entire GC server 200 and executes various types of information processing.

[0058] The memory 202 includes, for example, a RAM or a ROM, and stores information used in the information processing executed by the processor 201 .

[0059] The storage 203 includes, for example, an HDD or an SSD, and stores various types of data.

[0060] The communication unit 204 has an interface for performing wired or wireless communication, and communicates with the core NW control server 100 and other GC servers 200 .

[0061] The GC server 200 may have other components not shown, such as a display and an operation switch.

[0062] The processes performed by the core NW control server 100 and the GC server 200 described in the above embodiments can also be written as computer-executable programs. In this case, these programs can be stored on a computer-readable, non-transitory recording medium and installed on the computer. Examples of such recording media include portable recording media such as CD-ROMs, DVDs, and USB memory, and semiconductor memories such as flash memories.

[0063] It should be noted that the present disclosure is not limited to the above-described embodiments, but also includes various modified examples in which components are added, deleted, or converted from the above-described configurations.

[0064] Furthermore, the term "connection" used in this disclosure refers to a logical connection for communication. For example, "B connected to A" means that A and B are logically connected so that they can communicate. Therefore, A and B do not necessarily need to be directly physically connected by a physical cable or the like, and multiple devices or wireless communication may be present between A and B.

[0065] The present disclosure described above includes the following [1] to

[10] .

[0066] [1] An update control device having one or more processors, wherein the one or more processors execute processes including: determining the number of execution environments to be stopped from among a plurality of execution environments that execute processes related to communication terminals connected to an update cell corresponding to the software by executing the software to be updated, based on the number of communication terminals connected to the update cell; and instructing an update of the software executed in each execution environment for each of the determined number of execution environments.

[0067] [2] The update control device described in [1] above, wherein the processing further includes determining the number of communication terminals to be connected to neighboring cells located around the update cell among the communication terminals currently connected to the update cell, and the number of communication terminals to remain connected to the update cell, and the number of execution environments to be stopped is determined based on the number of communication terminals to remain connected to the update cell.

[0068] [3] The update control device according to [1] or [2] above, wherein the processing further includes increasing transmission power of a radio base station forming the neighboring cell and expanding the neighboring cell, thereby reducing the minimum number of communication terminals that remain connected to the update cell compared to before the neighboring cell was expanded.

[0069] [4] The update control device according to [1] or [2] above, wherein the processing further includes increasing the execution environment for executing processing related to communication terminals currently connected to the neighboring cell, thereby reducing the minimum number of communication terminals that remain connected to the update cell compared to before the execution environment was increased.

[0070] [5] A communication control device having one or more processors, wherein the one or more processors execute a process including: constructing a plurality of execution environments for executing processes related to communication terminals connected to a cell by executing software; and, when an instruction to update the software is obtained, updating software executed in other execution environments among the plurality of execution environments, excluding at least an execution environment compatible with the communication terminals connected to the cell.

[0071] [6] The communication control device according to [5], wherein the processing further includes, when the software update instruction is acquired, connecting the communication terminal currently connected to the cell to another cell.

[0072] [7] The communication control device according to [6], wherein the connecting includes: causing a communication terminal connected to the cell to measure radio wave strength for the cell and the other cell; and connecting a communication terminal whose measured radio wave strength for the other cell is equal to or greater than a predetermined threshold to the other cell.

[0073] [8] The communication control device according to [6] or [7] above, wherein the updating includes updating the software when the number of communication terminals to be connected to the other cell is equal to or greater than the number of communication terminals specified by the update instruction.

[0074] [9] An update control method comprising: determining the number of execution environments to be stopped from among a plurality of execution environments that execute processes related to communication terminals connected to an update cell corresponding to the software by executing the software to be updated, based on the number of communication terminals connected to the update cell; and instructing an update of the software executed in each of the determined number of execution environments.

[0075]

[10] A software update method comprising: constructing a plurality of execution environments that execute software to execute processes related to communication terminals connected to a cell; and, when an instruction to update the software is obtained, updating software executed in other execution environments among the plurality of execution environments, excluding at least an execution environment that is compatible with the communication terminals connected to the cell.

[0076] REFERENCE SIGNS LIST 100 Core NW control server 101, 201 Processor 102, 202 Memory 103, 203 Storage 104, 204 Communication unit 110 NW function management unit 120 Cell management unit 130 Cell selection unit 140 Update target number determination unit 150 Update instruction unit 200 GC server 210 Cell control unit 220 Update execution unit

Claims

1. An update control device having one or more processors, which executes processes including: determining the number of execution environments to be stopped among multiple execution environments that execute processes related to communication terminals connected to an update cell corresponding to the software by executing software to be updated, based on the number of communication terminals connected to the update cell; and instructing an update of the software executed in each execution environment for each of the determined number of execution environments.

2. The update control device according to claim 1, wherein the processing further includes determining the number of communication terminals to be connected to neighboring cells located around the update cell, among the communication terminals currently connected to the update cell, and the number of communication terminals to remain connected to the update cell, and the number of execution environments to be stopped is determined based on the number of communication terminals to remain connected to the update cell.

3. The update control device according to claim 2, wherein the processing further includes increasing the transmission power of a radio base station forming the neighboring cell and expanding the neighboring cell, thereby making the minimum number of communication terminals that remain connected to the update cell smaller than before the neighboring cell was expanded.

4. The update control device according to claim 2, wherein the processing further includes: increasing an execution environment for executing processing related to communication terminals currently connected to the neighboring cell, thereby reducing the minimum number of communication terminals to remain connected to the update cell to a value smaller than that before the execution environment was increased.

5. A communication control device having one or more processors, which executes processes including: constructing multiple execution environments for executing processes related to communication terminals connected to a cell by executing software; and when an instruction to update the software is obtained, updating software executed in other execution environments among the multiple execution environments, excluding at least an execution environment compatible with the communication terminals connected to the cell.

6. The communication control device according to claim 5, wherein the process further includes: when the software update instruction is obtained, connecting a communication terminal currently connected to the cell to another cell.

7. The communication control device according to claim 6, wherein the connecting includes: causing a communication terminal connected to the cell to measure radio wave strength for the cell and the other cell; and connecting a communication terminal whose measured radio wave strength for the other cell is equal to or greater than a predetermined threshold to the other cell.

8. The communication control device according to claim 6, wherein the updating includes updating the software when the number of communication terminals to be connected to the other cell is equal to or greater than the number of communication terminals specified by the update instruction.

9. An update control method comprising: determining the number of execution environments to be stopped among a plurality of execution environments that execute processes related to communication terminals connected to an update cell corresponding to the software by executing the software to be updated, based on the number of communication terminals connected to the update cell; and instructing an update of the software executed in each execution environment for each of the determined number of execution environments.

10. A software update method comprising: constructing a plurality of execution environments that execute processes related to a communication terminal connected to a cell by executing software; and when an instruction to update the software is obtained, updating software executed in other execution environments among the plurality of execution environments, excluding at least an execution environment that is compatible with the communication terminal connected to the cell.

Citation Information

Patent Citations

  • Method, Apparatus, and System for Deploying Virtualized Network Functions Using Network Edge Computing

    JP2019519180A

  • Multi-entity Resource, Security, and Service Management in Edge Computing Deployments

    JP2022530580A

  • Wireless communication apparatus, wireless communication network, and software upgrading method

    JP2006074683A

  • Managing software changes to virtual network functions

    US20180165084A1

  • Method and apparatus for non-orthogonal multiple access communication

    US20200186189A1