Communication control device and base station control method
Patent Information
- Application Number
- JP2023132379
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-08-15
- Publication Date
- 2025-02-28
AI Technical Summary
【0008】 一つの側面によれば、実行ファイルの送受信に伴うネットワークの負荷を抑制することが可能になる。
Smart Images

Figure 2025027554000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a communication control device and a base station control method. [Background technology]
[0002] In a communication system (hereinafter also simply referred to as a communication system) compatible with the communication standard of fifth generation mobile communication (hereinafter also simply referred to as 5G), an operation system (OPS) that controls a base station device transmits an executable file (LM: Load Module) to a central unit (CU) or a radio unit (RU) that constitutes the base station device. The CU or RU then executes the executable file received from the OPS, for example, to perform communication (wireless communication) with a terminal device and communication with a core network (CN: Core Network) (see, for example, Patent Documents 1 to 3). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Japanese Patent Application Publication No. 7-319784 [Patent Document 2] JP 2005-070987 A [Patent Document 3] JP 2011-141635 A Summary of the Invention [Problem to be solved by the invention]
[0004] In recent years, for example, multiple virtual base station devices (hereinafter also referred to as virtual base station devices) may be constructed in an MPCS (M Plane Client Server) by using multiple virtual machines (VMs) constructed in the MPCS, which is a single physical machine.
[0005] However, in this case, the OPS needs to transmit an executable file to each of the multiple virtual base station devices, for example. Therefore, in the network between the OPS and the MPCS, for example, the amount of data of the executable file being transmitted and received increases, and transmission and reception of communication data other than the executable file may be restricted.
[0006] Therefore, in one aspect, the present invention has an object to provide a communication control device and a base station control method that can reduce the network load associated with sending and receiving executable files. [Means for solving the problem]
[0007] In one aspect of an embodiment, a communication control device has a receiving unit that receives a transmission notification from a management device indicating that a first file will be sent to a first virtual machine in a physical machine on which multiple virtual machines are generated, a determination unit that determines, in response to receiving the transmission notification, whether a second virtual machine, which is one of the virtual machines different from the first virtual machine generated on the same physical machine as the first virtual machine, has the first file stored therein, and a transmitting unit that transmits the first file stored in the second virtual machine to the first virtual machine when it is determined that the second virtual machine has the first file stored therein. Effect of the Invention
[0008] According to one aspect, it is possible to reduce the load on the network caused by sending and receiving executable files. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram illustrating the configuration of a communication system 10. As shown in FIG. [Diagram 2] FIG. 2 is a diagram for explaining the hardware configuration of the MPCS1. [Diagram 3] FIG. 3 is a diagram illustrating the hardware configuration of the OPS2. [Figure 4]FIG. 4 is a diagram illustrating the function of the MPCS 1 in the first embodiment. [Diagram 5] FIG. 5 is a diagram illustrating the function of the MPCS 1 in the first embodiment. [Figure 6] FIG. 6 is a diagram illustrating the function of the OPS 2 in the first embodiment. [Figure 7] FIG. 7 is a flow chart outlining the file management process in the first embodiment. [Figure 8] FIG. 8 is a sequence chart illustrating details of the file management process in the first embodiment. [Figure 9] FIG. 9 is a sequence chart illustrating details of the file management process in the first embodiment. [Figure 10] FIG. 10 is a sequence chart illustrating details of the file management process in the first embodiment. [Figure 11] FIG. 11 is a sequence chart illustrating details of the file management process in the first embodiment. [Figure 12] FIG. 12 is a sequence chart illustrating details of the file management process in the first embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the transmission notification 131. In FIG. [Figure 14] FIG. 14 is a diagram for explaining a specific example of the deletion etc. prohibition request 132. In FIG. [Figure 15] FIG. 15 is a diagram for explaining a specific example of the presence notification 133. In FIG. [Figure 16] FIG. 16 is a diagram for explaining a specific example of the completion notification 134. In FIG. [Figure 17] FIG. 17 is a diagram for explaining a specific example of the transmission request 135. In FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. However, such descriptions should not be interpreted in a limiting sense and do not limit the subject matter described in the claims. In addition, various changes, substitutions, and modifications can be made without departing from the spirit and scope of the present disclosure. In addition, different embodiments can be appropriately combined.
[0011] [Configuration of the communication system in the first embodiment] First, a description will be given of the configuration of the communication system 10. FIG 1 is a diagram for explaining the configuration of the communication system 10.
[0012] As shown in FIG. 1, the communication system 10 includes, for example, an MPCS 1 (hereinafter also referred to as a communication control device 1) and an OPS 2 (hereinafter also referred to as a management device 2). The communication system 10 also includes, for example, UE (User Equipment) 3a, UE 3b, UE 3c, RU 4a, RU 4b, RU 4c, CU 5a, CU 5b, and CU 5c. Hereinafter, UE 3a, UE 3b, and UE 3c are collectively referred to simply as UE 3. Hereinafter, RU 4a, RU 4b, and RU 4c are collectively referred to simply as RU 4. Hereinafter, CU 5a, CU 5b, and CU 5c are collectively referred to simply as CU 5. Hereinafter, a case where the communication system 10 includes three UEs 3 will be described, but the communication system 10 may include, for example, UEs other than three. Hereinafter, a case where the communication system 10 includes three RUs 4 will be described, but the communication system 10 may include, for example, RUs other than three. Furthermore, although the following description will be given of a case where the communication system 10 has three CUs 5, the communication system 10 may have, for example, a number of CUs 5 other than three.
[0013] The MPCS1 is, for example, a physical machine, and is a device that connects the OPS2 and each CU5. As shown in FIG. 1, for example, a VM (Virtual Machine) 6a connected to the CU5a, a VM 6b connected to the CU5b, and a VM 6c connected to the CU5c are constructed in the MPCS1. Hereinafter, the VMs 6a, 6b, and 6c are collectively referred to simply as VMs 6. For example, the VMs 6 are generated for each customer that operates the system. Note that, although the following description will be given of a case where the communication system 10 has three VMs 6, the communication system 10 may have, for example, a number other than three VMs 6.
[0014] The OPS2 is, for example, a physical machine, and is a device that controls each VM6 constructed in the MPCS1. Specifically, the OPS2 transmits an executable file to each VM6 created in the MPCS1 via, for example, the core network NW. Note that, although the following description will be given of a case in which the communication system 10 has one OPS2, the communication system 10 may have, for example, a plurality of OPS2. In this case, the plurality of OPS2 may each control, for example, each of the VMs 6 constructed in the MPCS1.
[0015] The UE 3 is, for example, a terminal device such as a smartphone or a mobile device used by a user.
[0016] The RU 4 is a device that performs wireless communication with the UE 3, for example, via an antenna (not shown). Specifically, the RU 4 converts radio waves transmitted from the UE 3 into signals and transmits them to the CU 5. The RU 4 also converts signals transmitted from the CU 5 into radio waves and transmits them to the UE 3. Hereinafter, the RU 4 is also referred to as a wireless unit 4.
[0017] The CU 5 is, for example, a device that communicates with the core network NW via the MPCS 1.
[0018] 1, CU5a and VM6a configure, for example, a virtual base station device Sa, CU5b and VM6b configure, for example, a virtual base station device Sb, and CU5c and VM6c configure, for example, a virtual base station device Sc. Hereinafter, the virtual base station devices Sa, Sb, and Sc are collectively referred to simply as virtual base station devices S. Note that, although the following description will be given of a case in which the communication system 10 has three virtual base station devices S, the communication system 10 may have, for example, a number other than three virtual base station devices S.
[0019] Here, OPS2 transmits an executable file to each of a plurality of VMs 6 (three VMs 6 in the example shown in FIG. 1) constructed in MPCS1, for example. There are a plurality of executable files required for each operating customer of VM6 (virtual base station), and OPS2 transmits executable files according to each customer at the required timing for each customer. Therefore, in the network (network including the core network NW) between OPS2 and MPCS1, for example, the amount of data of executable files transmitted and received increases, and there is a possibility that transmission and reception of communication data other than executable files (for example, communication data with UE3 as the source or destination) may be restricted.
[0020] On the other hand, there are cases where an executable file used by a certain customer is common to executable files required by other customers.
[0021] Therefore, the MPCS1 in this embodiment receives, for example, a transmission notification (hereinafter, also simply referred to as a transmission notification) indicating transmission of an executable file (hereinafter, also referred to as a first file) to a VM6 (hereinafter, also referred to as a first virtual machine 6 or a destination VM6) from the OPS2. Specifically, the MPCS1 receives, for example, from the destination VM6, the transmission notification transmitted from the OPS2 to the destination VM6.
[0022] Then, for example, in response to receiving a transmission notification of the executable file, the MPCS1 determines whether or not a VM6 (hereinafter also referred to as a second virtual machine 6 or a search target VM6) different from the destination VM6 stores the executable file. If it is determined that the search target VM6 stores the executable file, the MPCS1 transmits, for example, the executable file stored in the search target VM6 to the destination VM6.
[0023] In other words, for example, when an executable file to be sent to a destination VM6 is stored in a search target VM6 constructed in the same MPCS1 as the destination VM6, the communication system 10 transmits and receives the executable file within the MPCS1 without transmitting the executable file from OPS2 to the MPCS1.
[0024] As a result, the MPCS1 in this embodiment can, for example, reduce the frequency with which executable files are sent and received on the network between the OPS2 and the MPCS1, and can reduce the amount of data sent by executable files. Therefore, the MPCS1 can prevent, for example, the sending and receiving of executable files from restricting the sending and receiving of communication data other than executable files.
[0025] [Hardware configuration of communication system] Next, a description will be given of the hardware configuration of the communication system 10. Fig. 2 is a diagram for explaining the hardware configuration of the MPCS 1. Fig. 3 is a diagram for explaining the hardware configuration of the OPS 2.
[0026] First, a description will be given of the hardware configuration of the MPCS 1. As shown in Fig. 2, the MPCS 1 has, for example, a CPU (Central Processing Unit) 101, which is a processor, a memory 102, a communication device (I / O interface) 103, and a storage device 104. Each part is connected to each other via a bus 105.
[0027] The storage device 104 has, for example, a program storage area (not shown) that stores a program 110 for performing a process (hereinafter also referred to as a file management process) of storing an executable file in each VM 6. The storage device 104 also has, for example, a storage unit 130 (hereinafter also referred to as an information storage area 130) that stores information used when performing the file management process. The storage device 104 may be, for example, a hard disk drive (HDD) or a solid state drive (SSD).
[0028] The CPU 101 executes, for example, a program 110 loaded from the storage device 104 to the memory 102 to perform file management processing.
[0029] The communication device 103 communicates with the OPS 2 via the core network NW, for example. Also, the communication device 103 communicates with each CU 5, for example.
[0030] Next, a description will be given of the hardware configuration of the OPS 2. As shown in Fig. 3, the OPS 2 has, for example, a CPU 201 which is a processor, a memory 202, a communication device 203, and a storage device 204. Each unit is connected to each other via a bus 205.
[0031] The storage device 204 has, for example, a program storage area (not shown) that stores a program 210 for performing file management processing. The storage device 204 also has, for example, a storage unit 230 (hereinafter also referred to as information storage area 230) that stores information used when performing file management processing. The storage device 204 may be, for example, an HDD or SSD.
[0032] The CPU 201 executes, for example, a program 210 loaded from the storage device 204 into the memory 202 to perform file management processing.
[0033] The communication device 203 communicates with the MPCS 1 via, for example, the core network NW.
[0034] [Functions of the communication system in the first embodiment] Next, functions of the communication system 10 in the first embodiment will be described. Figures 4 and 5 are diagrams for explaining the functions of the MPCS 1 in the first embodiment. Also, Figure 6 is a diagram for explaining the functions of the OPS 2 in the first embodiment.
[0035] First, the functions of the MPCS 1 will be described. As shown in Fig. 4, the MPCS 1 realizes various functions including an information receiving unit 111, an information determining unit 112, a file transmitting unit 113, and an information transmitting unit 114 as a function for performing file management processing, by organic cooperation between hardware such as a CPU 101 and a memory 102 and a program 110. Hereinafter, the information receiving unit 111, the information determining unit 112, the file transmitting unit 113, and the information transmitting unit 114 will be collectively referred to simply as the processing unit 1a.
[0036] The information receiving unit 111 receives, for example, a transmission notification transmitted from the OPS 2 to the destination VM 6 from the destination VM 6 .
[0037] For example, when the information receiving unit 111 receives a transmission notification, the information determining unit 112 determines whether or not an executable file corresponding to the received transmission notification is stored in a search target VM 6 different from the destination VM 6 .
[0038] For example, when the information determining unit 112 determines that the executable file is stored in the search target VM 6 , the file transmitting unit 113 transmits the executable file stored in the search target VM 6 to the destination VM 6 .
[0039] Specifically, for example, when the information determination unit 112 determines that an executable file is stored in the search target VM 6, the file transmission unit 113 acquires the executable file stored in the search target VM 6 by duplicating (copying) it. Then, the file transmission unit 113 transmits the acquired executable file to the destination VM 6, for example.
[0040] For example, if the information determination unit 112 determines that the executable file is not stored in the search target VM 6, the information sending unit 114 sends a transmission request (hereinafter simply referred to as a transmission request) to the destination VM 6, requesting the transmission of the executable file corresponding to the transmission notification received by the information receiving unit 111.
[0041] In the following, the processing unit 1a will be described as a function of the MPCS 1, but the processing unit 1a may be, for example, a function of a physical machine other than the MPCS 1. Also, the processing unit 1a may be, for example, a function of a VM (a VM other than the VM 6 functioning as the virtual base station device S) constructed in the MPCS 1.
[0042] Next, a description will be given of the functions of the VM 6 constructed in the MPCS 1. As shown in Fig. 5, the VM 6 realizes various functions including an information receiving unit 121, an information transmitting unit 122, and a file receiving unit 123 by organically cooperating with hardware such as a CPU 101 and a memory 102 and a program (not shown).
[0043] The information receiving unit 121 receives, for example, a transmission notification transmitted from the OPS 2. Also, the information receiving unit 121 receives, for example, a transmission request transmitted from the processing unit 1a.
[0044] The information transmitting unit 122 transmits, for example, a transmission notification received by the information receiving unit 121 to the processing unit 1a.
[0045] The file receiving unit 123 receives, for example, an executable file transmitted from the processing unit 1a (a copy of the executable file stored in the search target VM 6) or an executable file transmitted from the OPS 2. Then, the file receiving unit 123 stores, for example, the received executable file in the information storage area 130.
[0046] In addition, for example, when the file receiving unit 123 receives an executable file transmitted from the processing unit 1a and stores it in the information storage area 130, the information transmitting unit 122 transmits to OPS2 a completion notification (hereinafter also referred to simply as a completion notification) indicating that the executable file corresponding to the transmission notification received by the information receiving unit 121 has been stored in the information storage area 130.
[0047] Furthermore, for example, when the information receiving unit 121 receives a transmission request transmitted from the processing unit 1a (i.e., when the file receiving unit 123 does not receive an executable file transmitted from the processing unit 1a), the information transmitting unit 122 transmits the received transmission request to the OPS2. In this case, the OPS2 transmits, for example, an executable file corresponding to the transmission request received from the MPCS1 to the MPCS1.
[0048] Next, the functions of OPS 2 will be described. As shown in Fig. 6, OPS 2 realizes various functions including an information transmitting unit 211, an information receiving unit 212, and a file transmitting unit 213 as a function for performing file management processing, by organically cooperating with hardware such as a CPU 201 and a memory 202 and a program 210.
[0049] The information transmitting unit 211 transmits, for example, a transmission notification to the destination VM 6. Specifically, the information transmitting unit 211 transmits a transmission notification to the destination VM 6 in response to, for example, information indicating that an executable file (a new executable file) will be transmitted to the destination VM 6 being input by an operator of OPS 2 (hereinafter also simply referred to as an operator).
[0050] The information receiving unit 212 receives, for example, a transmission request from the destination VM 6. In addition, the information receiving unit 212 receives, for example, a completion notification from the destination VM 6.
[0051] For example, when the file transmitting unit 213 receives a transmission request from the information receiving unit 212, it transmits an executable file corresponding to the received transmission request to the destination VM 6. Specifically, the file transmitting unit 213 transmits, for example, an executable file corresponding to the received transmission request from among the executable files stored in the information storage area 230 by the worker to the destination VM 6.
[0052] [Outline of file management process in the first embodiment] Next, an outline of the first embodiment will be described with reference to Fig. 7, which is a flow chart for explaining an outline of file management processing in the first embodiment.
[0053] 7, the MPCS1 (processing unit 1a) receives, for example, a transmission notification to the destination VM6 from the OPS2 (S1). Specifically, the MPCS1 receives, for example, from the destination VM6, the transmission notification transmitted from the OPS2 to the destination VM6.
[0054] Then, for example, in response to receiving a transmission notification in processing S1, MPCS1 determines whether a search target VM6 (VM6 constructed in MPCS1) different from the destination VM6 stores an executable file corresponding to the transmission notification received in processing S1 (S2).
[0055] As a result, when it is determined that the search target VM 6 stores the executable file (YES in S3), the MPCS 1 transmits, for example, the executable file determined to be stored in the search target VM 6 to the destination VM 6 (S4). Specifically, in this case, the MPCS 1, for example, copies and acquires the executable file determined to be stored in the search target VM 6, and transmits the acquired executable file to the destination VM 6.
[0056] On the other hand, if it is determined that the search target VM 6 does not store the executable file (NO in S3), the MPCS 1 does not perform the process of S4, for example.
[0057] As a result, the MPCS1 in this embodiment can, for example, reduce the frequency with which executable files are sent and received on the network between the OPS2 and the MPCS1, and can reduce the amount of data sent by executable files. Therefore, the MPCS1 can prevent, for example, the sending and receiving of executable files from restricting the sending and receiving of communication data other than executable files.
[0058] [Details of file management process in the first embodiment] Next, details of the file management process in the first embodiment will be described. Figures 8 to 12 are sequence charts explaining the details of the file management process in the first embodiment. Figures 13 to 17 are diagrams explaining the details of the file management process in the first embodiment.
[0059] In the following description, it is assumed that the destination VM6 is VM6a (hereinafter also referred to as destination VM6a) described in FIG. 1, and the search target VM6 is at least one of VM6b (hereinafter also referred to as search target VM6b) and VM6c (hereinafter also referred to as search target VM6c) described in FIG. 1.
[0060] [Processing when the executable file is stored in the first search target VM] First, a description will be given of a process performed when an executable file corresponding to a transmission notification transmitted from the OPS 2 is stored in the first VM 6 to be searched. Figures 8 and 9 are sequence charts that explain the process performed when an executable file is stored in the first VM 6 to be searched.
[0061] 8, the OPS2 (information transmitting unit 211) transmits, for example, a transmission notification 131 to the destination VM 6a (S11). Specifically, for example, when an update occurs to an executable file that has already been transmitted to the destination VM 6a, the OPS2 transmits, to the destination VM 6a, a transmission notification 131 indicating that the updated executable file will be transmitted. A specific example of the transmission notification 131 will be described below.
[0062] [Example of sending notification] 13 is a diagram for explaining a specific example of the transmission notification 131. Hereinafter, the destination VM 6a is also referred to simply as "6a."
[0063] The transmission notification 131 shown in FIG. 13 has, for example, items such as “Time” which sets the time when the transmission notification 131 was sent from the sender (OPS2), “File name” which sets the file name of the executable file, and “Destination VM” which sets the identification information of the destination of the executable file (destination VM6).
[0064] Specifically, in the transmission notification 131 shown in FIG. 13, for example, "12:00:00" is set as the "time", "FL013" is set as the "file name", and "6a" is set as the "destination VM".
[0065] Returning to FIG. 8, the destination VM 6a (information transmitting unit 122) transmits, for example, the transmission notification 131 received from the OPS 2 in the process of S11 to the processing unit 1a (S12).
[0066] In this case, the destination VM 6a may send to the processing unit 1a, for example, instead of the transmission notification 131 received from OPS2 in the processing of S11, another notification having at least some information different from the received transmission notification 131.
[0067] Then, the MPCS 1 (information determination unit 112) accesses, for example, the search target VM 6b, and searches for an executable file corresponding to the transmission notification 131 received in the process of S12 (S13).
[0068] Specifically, the MPCS1, for example, accesses the search target VM 6b and determines whether or not the executable file corresponding to the transmission notification 131 received in the processing of S12 (the executable file corresponding to the file name included in the transmission notification 131) is stored in the memory area of the information storage area 130 corresponding to the search target VM 6b.
[0069] As a result, if it is determined that the executable file corresponding to the transmission notification 131 received in the processing of S12 is stored in the search target VM 6b, the MPCS1 (information sending unit 114) sends, for example, a request to prohibit deletion and movement of the executable file corresponding to the transmission notification 131 received in the processing of S12 (hereinafter also referred to as a deletion etc. prohibition request 132) to the search target VM 6b (S14).
[0070] 9, even if the MPCS1 receives a request to delete or move an executable file stored in the search target VM 6b from another OPS (S21) while the executable file is being copied from the search target VM 6b to the MPCS1, the MPCS1 can prevent the deletion or movement of the executable file being copied. A specific example of the deletion etc. prohibition request 132 will be described below.
[0071] [Specific examples of requests to prohibit deletion, etc.] FIG. 14 is a diagram for explaining a specific example of the deletion etc. prohibition request 132. In FIG.
[0072] The deletion etc. prohibition request 132 shown in Figure 14 has, for example, items such as "time", which sets the time when the deletion etc. prohibition request 132 was sent from the sender (MPCS1), and "file name", which sets the file name of the executable file.
[0073] Specifically, in the deletion etc. prohibition request 132 shown in FIG. 14, for example, "12:00:05" is set as the "time" and "FL013" is set as the "file name".
[0074] 8, when a response indicating that the prohibition of deletion and movement of the executable file corresponding to the transmission notification 131 received in the process of S12 has been completed is received from the search target VM 6b, the MPCS1 (information sending unit 114) sends, for example, a presence notification (hereinafter, also simply referred to as the presence notification 133) indicating that the executable file corresponding to the transmission notification 131 received in the process of S12 is stored in another VM 6 (search target VM 6b) in the MPCS1 to the destination VM 6a (S15). A specific example of the presence notification 133 will be described below.
[0075] [Specific examples of presence notification] FIG. 15 is a diagram for explaining a specific example of the presence notification 133. In FIG.
[0076] The presence notification 133 shown in FIG. 15 has, for example, items such as “Time”, which sets the time when the presence notification 133 was sent from the sender (MPCS1), “File name”, which sets the file name of the executable file, and “Destination VM”, which sets the identification information of the destination of the executable file.
[0077] Specifically, in the presence notification 133 shown in FIG. 15, for example, "12:00:10" is set as the "time", "FL013" is set as the "file name", and "6a" is set as the "destination VM".
[0078] Returning to FIG. 8, the destination VM 6a (information transmitting unit 122) transmits, for example, the presence notification 133 received in the process of S15 to the OPS 2 (S16).
[0079] In other words, for example, if MPCS1 determines that an executable file corresponding to the transmission notification 131 received in processing S12 is stored in another VM 6 in MPCS1, it notifies OPS2 that there is no need to send the executable file corresponding to the transmission notification 131 received in processing S12 to the destination VM 6a.
[0080] This allows OPS2 to, for example, stop sending executable files to the destination VM 6a. This allows OPS2 to, for example, reduce the frequency of sending executable files to MPCS1 (VM 6 built in MPCS1).
[0081] Therefore, the communication system 10 can suppress the frequency of transmission of executable files in the network between, for example, the OPS 2 and the MPCS 1, and can suppress the amount of transmission data of the executable files.
[0082] In addition, in the processing of S16, the destination VM 6a may send to OPS2, for example, instead of the presence notification 133 received from MPCS 1 in the processing of S15, another notification having at least some information different from the received presence notification 133.
[0083] Returning to FIG. 8, in this case, the MPCS 1 (file transmission unit 113) copies and acquires the executable file determined to be stored in the search target VM 6b in the process of S13 (S17).
[0084] Then, the MPCS 1 (file transmission unit 113) transmits, for example, the executable file acquired in the process of S17 to the destination VM 6a (S18).
[0085] Thereafter, the destination VM 6a (file receiving unit 123) stores the executable file received in the process of S18, for example, in a storage area of the information storage area 130 corresponding to the destination VM 6a. Then, the destination VM 6 (information transmitting unit 122) transmits to the OPS 2, for example, a completion notification (hereinafter, also simply referred to as a completion notification 134) indicating that the storage (storage) of the executable file corresponding to the transmission notification 131 received in the process of S12 has been completed (S19). A specific example of the completion notification 134 will be described below.
[0086] [Examples of completion notices] FIG. 16 is a diagram for explaining a specific example of the completion notification 134. In FIG.
[0087] The completion notification 134 shown in FIG. 16 has, for example, items such as "Time," which sets the time when the completion notification 134 was sent from the sender (MPCS1), "File name," which sets the file name of the executable file, and "Destination VM," which sets the identification information of the destination of the executable file.
[0088] Specifically, in the completion notification 134 shown in FIG. 16, for example, "12:00:15" is set as the "time", "FL013" is set as the "file name", and "6a" is set as the "destination VM".
[0089] [What to do if the executable file is not stored in the first search target VM] Next, a process will be described for a case where the executable file corresponding to the transmission notification transmitted from OPS2 is not stored in the first VM 6 to be searched (stored in the second VM 6 to be searched). Fig. 10 is a sequence chart diagram for explaining the process for a case where the executable file is not stored in the first VM 6 to be searched. Below, the points different from the case explained in Fig. 8 will be explained.
[0090] As shown in FIG. 10, the MPCS 1 (information determination unit 112) accesses, for example, the search target VM 6b, and searches for an executable file corresponding to the transmission notification 131 received in the process of S12 (S13).
[0091] As a result, if it is determined that the executable file corresponding to the transmission notification 131 received in the processing of S12 is not stored in the search target VM 6b, the MPCS1 (information determination unit 112) accesses, for example, a search target VM 6c which is a search target VM 6 different from the search target VM 6b, and further searches for the executable file corresponding to the transmission notification 131 received in the processing of S12 (S13-2).
[0092] Then, if it is determined that the executable file corresponding to the transmission notification 131 received in the processing of S12 is stored in the search target VM 6c, the MPCS1 (information sending unit 114) sends, for example, a request 132 to prohibit deletion, etc. of the executable file corresponding to the transmission notification 131 received in the processing of S12 to the search target VM 6c (S14).
[0093] Thereafter, when a response is received from the search target VM 6b indicating that the prohibition on deletion and movement of the executable file corresponding to the transmission notification 131 received in the processing of S12 has been completed, the MPCS1 (information sending unit 114) sends, for example, a notification of the existence of the executable file 133 corresponding to the transmission notification 131 received in the processing of S12 to the destination VM 6a (S15).
[0094] Next, the destination VM 6a (information transmitting unit 122) transmits, for example, the presence notification 133 received in the process of S15 to the OPS 2 (S16).
[0095] Furthermore, in this case, the MPCS 1 (file transmission unit 113) copies and acquires the executable file determined to be stored in the search target VM 6c in the process of S13-2 (S17).
[0096] Then, the MPCS 1 (file transmission unit 113) transmits, for example, the executable file acquired in the process of S17 to the destination VM 6a (S18).
[0097] Thereafter, the destination VM 6a (file receiving unit 123) stores the executable file received in the process of S18, for example, in a storage area corresponding to the destination VM 6a in the information storage area 130. Then, the destination VM 6 (information transmitting unit 122) transmits, for example, a completion notification 134 of the executable file corresponding to the transmission notification 131 received in the process of S12 to the OPS 2 (S19).
[0098] [What to do if deletion or moving of executable files cannot be prohibited] Next, a process for a case where the deletion or movement of an executable file stored in the search target VM 6 (search target VM 6b) cannot be prohibited will be described. Fig. 11 is a sequence chart diagram for explaining a process for a case where the deletion or movement of an executable file stored in the search target VM 6 cannot be prohibited. Below, a description will be given of points different from the case described in Fig. 8.
[0099] As shown in FIG. 11, the MPCS 1 (information determination unit 112) accesses, for example, the search target VM 6b, and searches for an executable file corresponding to the transmission notification 131 received in the process of S12 (S13).
[0100] As a result, if it is determined that an executable file corresponding to the transmission notification 131 received in the processing of S12 is stored in the search target VM 6b, the MPCS1 (information sending unit 114) sends, for example, a request to prohibit the deletion, etc. of the executable file corresponding to the transmission notification 131 received in the processing of S12 to the search target VM 6b (S13, S14).
[0101] Thereafter, if no response is received from the search target VM 6b indicating that the prohibition on deletion and movement of the executable file corresponding to the transmission notification 131 received in the processing of S12 has been completed, the MPCS1 (information determination unit 112) accesses, for example, the search target VM 6c, which is a search target VM 6 different from the search target VM 6b, and further searches for the executable file corresponding to the transmission notification 131 received in the processing of S12 (S13-2).
[0102] That is, for example, if the executable file corresponding to the transmission notification 131 received in the process of S12 has already been deleted or moved, the search target VM 6b cannot prohibit the deletion or movement of the executable file corresponding to the transmission notification 131 received in the process of S12 even if the search target VM 6b receives a deletion etc. prohibition request 132 from the MPCS 1. Therefore, in this case, the MPCS 1 further searches for the executable file corresponding to the transmission notification 131 received in the process of S12 by, for example, accessing a search target VM 6 (search target VM 6c) other than the search target VM 6b.
[0103] Then, if it is determined that the executable file corresponding to the transmission notification 131 received in the processing of S12 is stored in the search target VM 6c, the MPCS1 (information sending unit 114) sends, for example, a request 132 to prohibit deletion, etc. of the executable file corresponding to the transmission notification 131 received in the processing of S12 to the search target VM 6c (S14-2).
[0104] Thereafter, when a response is received from the search target VM 6c indicating that the prohibition on deletion and movement of the executable file corresponding to the transmission notification 131 received in the processing of S12 has been completed, the MPCS1 (information sending unit 114) sends, for example, a notification of the existence of the executable file 133 corresponding to the transmission notification 131 received in the processing of S12 to the destination VM 6a (S15).
[0105] Next, the destination VM 6a (information transmitting unit 122) transmits, for example, the presence notification 133 received in the process of S15 to the OPS 2 (S16).
[0106] Furthermore, in this case, the MPCS 1 (file transmission unit 113) copies and acquires the executable file determined to be stored in the search target VM 6c in the process of S13-2 (S17).
[0107] Then, the MPCS 1 (file transmission unit 113) transmits, for example, the executable file acquired in the process of S17 to the destination VM 6a (S18).
[0108] Thereafter, the destination VM 6a (file receiving unit 123) stores the executable file received in the process of S18, for example, in a storage area corresponding to the destination VM 6a in the information storage area 130. Then, the destination VM 6 (information transmitting unit 122) transmits, for example, a completion notification 134 of the executable file corresponding to the transmission notification 131 received in the process of S12 to the OPS 2 (S19).
[0109] [What to do if the executable file is not stored in all target VMs] Next, a process for when the executable file is not stored in any of the search target VMs 6 will be described. Fig. 12 is a sequence chart for explaining the process for when the executable file is not stored in any of the search target VMs 6. Below, the points different from the case explained in Fig. 8 will be explained.
[0110] As shown in FIG. 12, the MPCS 1 (information determination unit 112) accesses, for example, the search target VM 6b, and searches for an executable file corresponding to the transmission notification 131 received in the process of S12 (S13).
[0111] As a result, if it is determined that the executable file corresponding to the transmission notification 131 received in the processing of S12 is not stored in the search target VM 6b, the MPCS1 (information determination unit 112) accesses, for example, a search target VM 6c which is a search target VM 6 different from the search target VM 6b, and further searches for the executable file corresponding to the transmission notification 131 received in the processing of S12 (S13-2).
[0112] Then, when it is determined that the executable file corresponding to the transmission notification 131 received in the process of S12 is not stored in the search target VM 6c, that is, when it is determined that the executable file corresponding to the transmission notification 131 received in the process of S12 is not stored in all the search target VMs 6, the MPCS1 (information transmitting unit 114) transmits, for example, a transmission request (hereinafter also simply referred to as a transmission request 135) for the executable file corresponding to the transmission notification 131 received in the process of S12 to the destination VM 6a (S31). A specific example of the transmission request 135 will be described below.
[0113] [Example of a transmission request] FIG. 17 is a diagram for explaining a specific example of the transmission request 135. In FIG.
[0114] The transmission request 135 shown in FIG. 17 has, for example, items such as "time," which sets the time when the transmission request 135 was sent from the sender (MPCS1), a "file name," which sets the file name of the executable file, and a "destination VM," which sets the identification information of the destination of the executable file.
[0115] Specifically, in the transmission request 135 shown in FIG. 17, for example, "12:00:20" is set as the "time", "FL013" is set as the "file name", and "6a" is set as the "destination VM".
[0116] Returning to FIG. 12, the destination VM 6a (information transmitting unit 122) transmits, for example, the transmission request 135 received in the process of S31 to the OPS 2 (S32).
[0117] In this case, the destination VM 6a may transmit to the OPS 2, for example, instead of the transmission request 135 received in the process of S31, another notification having at least some information different from that of the received transmission request 135.
[0118] Then, the OPS2 (file transmission unit 213) transmits, for example, an executable file corresponding to the transmission request 135 received in the process of S32 to the destination VM 6a (S33).
[0119] Thereafter, the destination VM 6a (file receiving unit 123) stores the executable file received in the process of S33, for example, in a storage area corresponding to the destination VM 6a in the information storage area 130. Then, the destination VM 6 (information transmitting unit 122) transmits, for example, a completion notification 134 of the executable file corresponding to the transmission notification 131 received in the process of S12 to the OPS 2 (S19).
[0120] In this manner, the MPCS1 in this embodiment receives, for example, a transmission notification 131 from the OPS2 indicating that an executable file will be transmitted to the destination VM 6. Then, for example, the MPCS1 determines whether the search target VM 6 stores the executable file in response to the reception of the executable file transmission notification 131. As a result, if it is determined that the search target VM 6 stores the executable file, the MPCS1 transmits, for example, the executable file stored in the search target VM 6 to the destination VM 6.
[0121] In other words, for example, when an executable file to be sent to a destination VM6 is stored in a search target VM6 constructed in the same MPCS1 as the destination VM6, the communication system 10 transmits and receives the executable file within the MPCS1 without transmitting the executable file from OPS2 to the MPCS1.
[0122] As a result, the MPCS1 in this embodiment can, for example, reduce the frequency with which executable files are sent and received on the network between the OPS2 and the MPCS1, and can reduce the amount of data sent by executable files. Therefore, the MPCS1 can prevent, for example, the sending and receiving of executable files from restricting the sending and receiving of communication data other than executable files.
[0123] Furthermore, the MPCS 1 in this embodiment can reduce the time required to transmit an executable file to the destination VM 6 by transmitting and receiving the executable file within the MPCS 1, for example.
[0124] The above embodiment can be summarized as follows:
[0125] (Appendix 1) a receiving unit that receives a transmission notification from the management device, the transmission notification indicating that a first file is to be transmitted to a first virtual machine in a physical machine on which a plurality of virtual machines are generated; a determination unit that, in response to receiving the transmission notification, determines whether or not a second virtual machine, which is any one of virtual machines different from the first virtual machine and generated on the same physical machine as the first virtual machine, stores the first file; a transmission unit that transmits the first file stored in the second virtual machine to the first virtual machine when it is determined that the second virtual machine stores the first file. A communication control device comprising:
[0126] (Appendix 2) In Appendix 1: The receiving unit receives, from the first virtual machine, the transmission notification transmitted from the management device to the first virtual machine. A communication control device comprising:
[0127] (Appendix 3) In Appendix 1: when it is determined that the second virtual machine does not store the first file, the transmission unit transmits a transmission request to the management device to request transmission of the first file. A communication control device comprising:
[0128] (Appendix 4) In Appendix 1: when the transmission unit transmits the first file stored in the second virtual machine to the first virtual machine, the transmission unit transmits a completion notification indicating that the first file has been stored in the first virtual machine to the management device. A communication control device comprising:
[0129] (Appendix 5) In Appendix 4: The transmission unit transmits the completion notification to the first virtual machine; The first virtual machine transmits the received completion notification to the management device. A communication control device comprising:
[0130] (Appendix 6) In Appendix 1: when it is determined that the second virtual machine does not store the first file, the determination unit determines whether or not a third virtual machine different from the first virtual machine and the second virtual machine stores the first file; When it is determined that the third virtual machine stores the first file, the transmission unit transmits the first file stored in the third virtual machine to the first virtual machine. A communication control device comprising:
[0131] (Appendix 7) In Appendix 6: when it is determined that the third virtual machine does not store the first file, the transmission unit transmits a transmission request to the management device to request transmission of the first file. A communication control device comprising:
[0132] (Appendix 8) In Appendix 1: the management device and the physical machine are connected to each other via a network; Each of the plurality of virtual machines in the physical machine forms a virtual base station and is connected to a wireless unit. A communication control device comprising:
[0133] (Appendix 9) receiving a transmission notification from the management device, the transmission notification indicating that a first file is to be transmitted to a first virtual machine in a physical machine on which a plurality of virtual machines have been generated; In response to receiving the transmission notification, determine whether or not a second virtual machine, which is any one of virtual machines different from the first virtual machine generated on the same physical machine as the first virtual machine, stores the first file; When it is determined that the second virtual machine stores the first file, the second virtual machine transmits the first file stored therein to the first virtual machine. A base station control method, the processing of which is executed by a computer.
[0134] (Appendix 10) In Appendix 9: in the transmitting process, when it is determined that the second virtual machine does not store the first file, a transmission request for requesting transmission of the first file is transmitted to the management device; A base station control method comprising: [Explanation of symbols]
[0135] 1: MPCS 2: OPS 3:UE 4:RU 5:CU 6:VM 10: Communication system 101: CPU 102: Memory 103: I / O interface 104: Storage device 105: Bus 130: Information storage area 201: CPU 202: Memory 203: I / O interface 204: Storage device 205: Bus 230: Information storage area NW: Core network
Claims
1. a receiving unit that receives a transmission notification from the management device, the transmission notification indicating that a first file is to be transmitted to a first virtual machine in a physical machine on which a plurality of virtual machines are generated; a determination unit that, in response to receiving the transmission notification, determines whether or not a second virtual machine, which is any one of virtual machines different from the first virtual machine and generated on the same physical machine as the first virtual machine, stores the first file; a transmission unit that transmits the first file stored in the second virtual machine to the first virtual machine when it is determined that the second virtual machine stores the first file. A communication control device comprising:
2. In claim 1, The receiving unit receives, from the first virtual machine, the transmission notification transmitted from the management device to the first virtual machine. A communication control device comprising:
3. In claim 1, When it is determined that the second virtual machine does not store the first file, the transmission unit transmits a transmission request to the management device to request transmission of the first file. A communication control device comprising:
4. In claim 1, when the transmission unit transmits the first file stored in the second virtual machine to the first virtual machine, the transmission unit transmits a completion notification indicating that the first file has been stored in the first virtual machine to the management device. A communication control device comprising:
5. In claim 4, The transmission unit transmits the completion notification to the first virtual machine; The first virtual machine transmits the received completion notification to the management device. A communication control device comprising:
6. In claim 1, When it is determined that the second virtual machine does not store the first file, the determination unit determines whether or not a third virtual machine different from the first virtual machine and the second virtual machine stores the first file; When it is determined that the third virtual machine stores the first file, the transmission unit transmits the first file stored in the third virtual machine to the first virtual machine. A communication control device comprising:
7. In claim 6, When it is determined that the third virtual machine does not store the first file, the transmission unit transmits a transmission request to the management device to request transmission of the first file. A communication control device comprising:
8. In claim 1, the management device and the physical machine are connected to each other via a network; Each of the virtual machines in the physical machine forms a virtual base station and is connected to a wireless unit. A communication control device comprising:
9. receiving a transmission notification from the management device, the transmission notification indicating that a first file is to be transmitted to a first virtual machine in a physical machine in which a plurality of virtual machines have been generated; In response to receiving the transmission notification, determine whether or not a second virtual machine, which is any one of virtual machines different from the first virtual machine generated on the same physical machine as the first virtual machine, stores the first file; When it is determined that the second virtual machine stores the first file, the second virtual machine transmits the first file stored therein to the first virtual machine. A base station control method, the processing of which is executed by a computer.
Citation Information
Patent Citations
Method and device for file transfer between networks
JP1995319784A
Node to be used in file sharing system, file storage method to be used in file sharing system, and file storing program
JP2005070987A
Communication method of data of virtual server using iner-host communication
JP2011141635A