Computer system and configuration method

Abstract

A reading device 28 reads, from a communication device delivered to a GC 16, identification information of the device, and transmits the read identification information of the communication device to an OSS 42. The OSS 42 confirms whether the communication device at the GC 16 is correctly connected to a predetermined counter device, on the basis of the identification information of the communication device transmitted from the reading device 28. The OSS 42 automatically reflects, when the communication device at the GC 16 is correctly connected to the predetermined counter device, configuration information for the communication device at the GC 16 in the communication device.

Description

[Technical field]

[0001] The present disclosure relates to a data processing technology, and more particularly to a computer system and a setting method for setting a Group Center (GC). [Background technology]

[0002] In mobile communications, communication devices located at base stations, GCs, and data centers (hereafter also referred to as "CDCs" (Central Data Centers)) work together to transmit user data. In a GC, for example, a large number of communication devices including a CU (Central Unit) and a DU (Distributed Unit) that provide the function of a RAN (Radio Access Network) are located (for example, see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-136788 A Summary of the Invention [Problem to be solved by the invention]

[0004] Conventionally, it has taken 2 to 3 days or more to set up the communications equipment for one GC, and there is a demand to shorten this setup time.

[0005] The present disclosure has been made in consideration of these problems, and one objective thereof is to provide a technique for making it more efficient to configure communication devices arranged in a GC. [Means for solving the problem]

[0006] In order to solve the above problems, a computer system according to an embodiment of the present disclosure includes a reading device disposed in a GC (Group Center) and an operation support system disposed in a location different from the GC. The reading device reads identification information of a communication device delivered to the GC from the device and transmits the identification information of the communication device to the operation support system. The operation support system checks whether the communication device is correctly connected to a specified counterpart device based on the identification information of the communication device transmitted from the reading device, and when the communication device is correctly connected to the specified counterpart device, the operation support system automatically reflects the setting information of the communication device in the communication device.

[0007] Another aspect of the present disclosure is a setting method in a computer system including a reading device disposed in a GC (Group Center) and an operation support system disposed in a location different from the GC, the setting method including the steps of: the reading device reading identification information of a communication device delivered to the GC from the communication device and transmitting the identification information of the communication device to the operation support system, the operation support system checking whether the communication device is correctly connected to a predetermined opposite device based on the identification information of the communication device transmitted from the reading device, and the operation support system automatically reflecting the setting information of the communication device in the communication device when the communication device is correctly connected to the predetermined opposite device.

[0008] In addition, any combination of the above components, and any conversion of the expressions of the present disclosure between an apparatus, a computer program, a recording medium on which a computer program is readably recorded, etc. are also valid as aspects of the present disclosure. Effect of the Invention

[0009] According to the present disclosure, it is possible to efficiently configure communication devices arranged in a GC. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing the configuration of a communication system according to an embodiment of the present invention.

[0011] [Diagram 2] FIG. 2 is a sequence diagram showing the operation of the communication system according to the embodiment.

[0012] [Diagram 3] FIG. 3 is a sequence diagram showing the operation of the communication system, following FIG.

[0013] [Figure 4] FIG. 4 is a sequence diagram showing the operation of the communication system, following FIG.

[0014] [Diagram 5] FIG. 5 is a sequence diagram showing the operation of the communication system following FIG.

[0015] [Figure 6] FIG. 6 is a sequence diagram showing the operation of the communication system, following FIG.

[0016] [Figure 7] FIG. 7 is a sequence diagram showing the operation of the communication system, following FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] In the embodiment, a computer system (communication system 10 described below) is proposed that realizes efficient configuration (so-called ZTP (Zero Touch Provisioning)) of communication devices arranged in a GC of a mobile network operator (MNO) network. A GC is a station that accommodates subscriber lines, that is, a subscriber exchange that aggregates lines from subscriber telephones within a specified area. A GC is a data center that is physically located close to subscribers, and can also be called an "edge data center."

[0018] The computer system of the embodiment (communication system 10 described below) automates the commissioning process in the GC from end to end. Specifically, the computer system of the embodiment (communication system 10 described below) automates the setup and verification of multiple types of communication devices and network functions (TOR 20, server 22, OOB 24, vDU 36, vCU 38, etc. described below) arranged in the GC. Note that the communication devices refer to data processing devices equipped with communication functions, and include relay devices such as switches and routers, as well as information processing devices such as servers.

[0019] FIG. 1 shows a configuration of a communication system 10 according to an embodiment. The communication system 10 includes a UE (User Equipment) 12, a base station 14, a SW (SWitch) 18, a TOR (Top Of Rack) 20, a server 22, an OOB (Out Of Band) 24, an installation team 26, a reader 28, an OSS (Operation Support System) 42, an orchestration server 48, a network management server 50, a TFTP (Trivial File Transfer Protocol) server 52, a core network system 54, and a shipping team 62. The installation team 26 and the shipping team 62 are groups of people. Each device, except for these groups of people, is connected via a wireless or wired communication network. Although one GC 16 is illustrated in FIG. 1, the actual communication system 10 includes multiple GCs 16.

[0020] The UE 12 is a mobile communication terminal, such as a smartphone or a tablet terminal, operated by a user (subscriber) who has signed a contract with a mobile communication operator. The base station 14 is wirelessly connected to the UE 12 to perform wireless communication.

[0021] The SW18, the TOR 20, the server 22, the OOB 24, the introduction team 26, and the reader 28 are arranged in the GC 16. A plurality of each of the SW18, the TOR 20, the server 22, the OOB 24, and the reader 28 may be arranged in the GC 16. The SW18 is, for example, a layer 2 switch connected to an external network of the GC 16. The TOR 20 is, for example, a layer 2 switch provided in a rack in which a plurality of servers 22 are stored.

[0022] The OOB 24 is a layer 2 switch connected to a management and / or monitoring network. The installation team 26 includes workers who install and configure communication devices in the GC 16. The installation team 26 may carry information processing devices (such as PCs and tablet terminals) operated by the workers. These information processing devices are connected to the SW 18 via a wireless or wired communication network. The reader 28 is an information processing device equipped with a scanner function and a communication function.

[0023] The server 22 is an information processing device that executes various data processing in the GC, and is also called a stock keeping unit (SKU). The server 22 includes a management node 30, a virtualized infrastructure manager (VIM) 32, an OpenStack 34, a virtual distributed unit (vDU) 36, and a virtual central unit (vCU) 38 as a plurality of functional blocks.

[0024] The above-mentioned multiple functional blocks can be configured in terms of hardware using circuit blocks, memory, and other LSIs, and in terms of software, they are realized by a CPU executing a program loaded into memory, etc. Therefore, it will be understood by those skilled in the art that these functional blocks can be realized in various forms using only hardware, only software, or a combination of both, and are not limited to any one of them.

[0025] In the embodiment, a computer program in which modules corresponding to each of the plurality of functional blocks are implemented is installed in the storage of the server 22 via a network. The CPU of the server 22 loads the computer program corresponding to each functional block into a main memory and executes it to fulfill the function corresponding to each functional block. The computer program may be stored in a predetermined recording medium, or may be installed in the storage of the server 22 via the recording medium.

[0026] The management node 30, which can also be called a VIM management node, is installed in one of the multiple servers 22 arranged in the GC 16. The management node 30 manages and controls the operation of the VIM in the multiple servers 22 arranged in the GC 16. The VIM 32 is a system that manages physical machines and virtual machines as network resources. OpenStack 34 is software for building a cloud computing infrastructure, and performs integrated management of virtual machines, storage, networks, etc.

[0027] The vDU36 and vCU38 are software that provides the functionality of a virtualized RAN (i.e., vRAN (virtual RAN)). The vDU36 is software that provides the functionality of a DU (remote station). The vCU38 is software that provides the functionality of a CU (aggregation base station).

[0028] The OSS 42, the orchestration server 48, the network management server 50, the TFTP server 52, and the core network system 54 are arranged in the CDC 40. The CDC 40 is a data center that is connected to a plurality of GCs 16 via a communication network and processes data related to the plurality of GCs. For example, the CDC 40 is a data center that aggregates and processes communication data received by a plurality of GCs. The functions of the systems and servers arranged in the CDC 40 may be virtualized, and there is no restriction on the physical hardware configuration in the CDC 40.

[0029] The OSS 42 is an information processing system that supports the operation of the entire communication system 10. The OSS 42 includes an OSS-SF (Siteforge) 44 and an OSS-FS (Foresight) 46. "Siteforge" and "Foresight" are product names and are also trademarks or registered trademarks. In the embodiment, the OSS-SF 44 and the OSS-FS 46 are implemented as different software modules, but may be implemented as a single software module.

[0030] The orchestration server 48 is an information processing device that provides an orchestration function related to the setup of communication devices of the GC 16. The network management server 50 is an information processing device that manages network information in the GC 16. The network management server 50 includes a function of a DHCP (Dynamic Host Configuration Protocol) server. The TFTP server 52 is an information processing device that functions as a file server.

[0031] The core network system 54 is a computer system that provides a core network function of LTE (Long Term Ecolition) or a fifth generation mobile communication system (hereinafter referred to as "5G"). For example, the core network system 54 may include functions such as UDM (Unified Data Management), AMF (Access and Mobility Management Function), and SMF (Session Management Function).

[0032] In the communication system 10, communication data transmitted from the UE 12 is transmitted via the base station 14, the vDU 36 and vCU 38 of the GC 16, and the core network system 54 of the CDC 40 to an external network (such as the Internet).

[0033] The warehouse 60 is a warehouse where communication devices (TOR 20, server 22, etc.) are stored before shipping. A shipping team 62 is placed in the warehouse 60. The shipping team 62 includes workers who perform work related to the shipping of communication devices to the GC 16. The shipping team 62 may carry information terminals (PCs, tablet terminals, etc.) operated by the workers. These information processing devices are connected to the OSS 42 via a wireless or wired communication network.

[0034] The operation of the GC 16 regarding the setting of the communication device will be described below. 2 is a sequence diagram showing the operation of the communication system 10 of the embodiment. The OSS-SF44 accepts login from a person in charge of GC setting work (S10). In response to an operation by the person in charge, the OSS-SF44 generates GC detailed data for the GC to be constructed (hereinafter referred to as "GC16") (S12). The OSS-SF44 stores the GC detailed data in a storage unit (such as a database) of the OSS42. The storage unit may be a storage device provided outside the OSS42.

[0035] The GC detailed data includes the name, type, ID, and location information of the GC 16. The GC detailed data also includes the IDs of one or more PODs (Points Of Delivery) placed in the GC 16. A POD is a group of communication devices placed in the GC 16. For example, a POD may be a set of one TOR 20 and multiple servers 22. The GC type of the GC detailed data is associated in advance with (1) the type and number of communication devices to be installed in the GC, (2) the connection mode of the multiple communication devices in the GC (e.g., which communication devices are connected to which other communication devices, etc.), and (3) the mode of one or more PODs placed in the GC. In other words, the GC type is information that can uniquely identify the above (1) to (3).

[0036] The OSS-SF44 notifies the OSS-FS46 that the GC detailed data has been created (S14). The OSS-FS46 notifies the shipping team 62 of instructions to ship the communications equipment (S16). For example, the OSS-FS46 may send an email including instructions to ship the communications equipment to the information terminal of the shipping team 62. The shipping team 62 identifies the type and number of each of the multiple communications equipment to be placed in the GC16 based on the GC detailed data (GC type, etc.) of the GC16 stored in the OSS42. The shipping team 62 ships the multiple communications equipment to be placed in the GC16 to the GC16 (S18). The shipping team 62 (the information terminal of the shipping team 62) notifies the OSS-SF44 of the completion of shipment of the communications equipment.

[0037] Fig. 3 is a sequence diagram showing the operation of the communication system 10 following Fig. 2. When the OSS-SF 44 receives the shipping completion notification, it transmits an instruction to the OSS-FS 46 to create GC plan data (S22). The OSS-FS 46 identifies the type and number of each of the multiple communication devices to be placed in the GC 16 based on the pre-stored GC detailed data (GC type, etc.) of the GC 16. The OSS-FS 46 generates GC plan data including attribute information on each communication device to be placed in the GC 16 (S24). This attribute information includes the IP address and host name to be assigned to each communication device.

[0038] The storage unit of OSS42 stores IP addresses and host names already assigned to existing communication devices arranged in existing GCs. When creating GC plan data, OSS-FS46 refers to the storage unit and automatically assigns, to each communication device to be arranged in GC16, an IP address and host name that have not been assigned to existing communication devices (i.e., unique). This makes it possible to reliably prevent duplication (in other words, conflict) of IP addresses and host names within the communication system 10. OSS-FS46 notifies the introduction team 26 of the instructions for network construction work in GC16 to the introduction team 26 of GC16 (S26). OSS-FS46 may send an email including the instructions for the work to the information processing device of the introduction team 26.

[0039] The introduction team 26 operates the reading device 28 to have the reading device 28 read information on each communication device delivered to the GC 16 (S28). The information to be read here is physical identification information assigned to the physical entity / individual of each communication device, and includes a product code and a MAC address. Specifically, the reading device 28 uses a scanner function to read the physical identification information (product code, MAC address, etc.) of each communication device from a label attached to each communication device (TOR 20, server 22, etc.) (S30). The information to be read is, for example, a barcode or a two-dimensional code. The information to be read may be electronic information (electronic data) obtained from a number mark or an RF tag. The reading device 28 transmits the physical identification information of each communication device read from each communication device to the OSS-SF 44 (S32). The OSS-SF 44 stores the physical identification information of each communication device to be placed in the GC 16 transmitted from the reading device 28 in the memory unit of the OSS 42 (S34).

[0040] The introduction team 26 of GC 16 references the GC detailed data of GC 16 stored in OSS-SF 44, and based on the GC detailed data (GC type, etc.), connects the multiple communication devices delivered to GC 16 with communication cables to construct a network for GC 16 (S36). The introduction team 26 turns on the power of the multiple communication devices arranged in GC 16 (S38). The introduction team 26 manually performs a GC acceptance test (S40).

[0041] The manual GC acceptance test is a task in which a person checks whether the physical configuration of multiple communication devices arranged in the GC 16 is correct. For example, the manual GC acceptance test includes checking whether (1) the communication cables are correctly connected to the communication devices, (2) each communication device is correctly labeled, and (3) indicator lamps (LEDs, etc.) provided on each communication device are operating normally (illuminated, etc.). The introduction team 26 (information terminal of the introduction team 26) transmits the results of the manual GC acceptance test to the OSS-SF 44 (S42).

[0042] Fig. 4 is a sequence diagram showing the operation of the communication system 10, following Fig. 3. The OSS-SF 44 stores the results of the manual GC acceptance test notified by the installation team 26 in the memory of the OSS 42 (S44). The OSS-SF 44 instructs the OSS-FS 46 to perform a cable matrix check (S46). The OSS-FS 46 checks whether each communication device in the GC 16 is correctly connected to a predetermined counterpart device as a cable matrix check, based on the physical identification information of the multiple communication devices arranged in the GC 16 transmitted from the reader 28 (S48).

[0043] Specifically, the OSS-FS 46 uses CDP (Cisco Discovery Protocol) to map which device (MAC address) is connected to which port for each of the multiple communication devices (TOR 20, server 22, etc.) arranged in GC 16. Furthermore, based on the product code and MAC address of each of the multiple communication devices arranged in GC 16 and the result of the above mapping, the OSS-FS 46 checks whether each communication device of GC 16 is correctly connected to a predetermined opposite device, i.e., whether the connection mode is suitable for the GC type of GC 16.

[0044] If an error is detected in the cable matrix check, i.e., if an incorrect connection of the communication devices in GC16 is detected, OSS-FS46 notifies OSS-SF44 of the error (S50). OSS-SF44 assigns a correction task to a team in charge of correcting the error (S52). The team to which the correction task is assigned corrects, for example, the connection state of the communication devices in GC16. OSS-SF44 notifies OSS-FS46 that the error correction has been completed (S54).

[0045] As described below, when the cable matrix check is successful (including when errors are corrected), in other words, when each communication device of GC16 is correctly connected to a predetermined counterpart device, OSS-FS46 executes an automatic commissioning process that automatically reflects the setting information of each communication device of GC16 in each communication device. In this way, by executing the automatic commissioning process on the condition that the connection mode of the communication devices arranged in GC16 is correct, it is possible to suppress the occurrence of errors after the start of the automatic commissioning process and the occurrence of rework involved in correcting the error.

[0046] Returning to the explanation of FIG. 4, if the cable matrix check is successful or if the OSS-FS 46 is notified that the error has been corrected, it executes an automatic health check process for the server 22 (S56). The automatic health check process includes checking the normality of memory, disk size, and power supply status. If an abnormality is detected in the automatic health check process, the OSS-FS 46 notifies the OSS-SF 44 of the detected abnormality, in the same way as when an abnormality is detected in the cable matrix check. The OSS-SF 44 requests a specified team to deal with the abnormality and transitions the server 22 to a normal state.

[0047] The OSS-FS 46 assigns the IP address and host name indicated by the GC planning data generated in S24 to each of the multiple servers 22 arranged in the GC 16 (S58). The OSS-FS 46 generates setting information for the TOR 20 based on the GC type of the GC 16, the IP address and host name of each communication device of the GC 16, and the result of the cable matrix check (e.g., data indicating which device is connected to which port) (S60). The setting information for the TOR 20 may include, for example, the host name of the TOR 20, data of the MAC address table, data of the ARP table, data related to VLANs, and data related to priority control. The OSS-FS 46 automatically approves the execution of the automatic commissioning process for the TOR (S62). By performing automatic approval, it is possible to avoid the erroneous input of "reject" due to manual intervention and the waste of time involved in inputting "reject".

[0048] FIG. 5 is a sequence diagram showing the operation of the communication system 10, following FIG. 4. The diagram shows the flow of the automatic commissioning process of one TOR 20. When multiple TORs 20 are arranged in the GC 16, the generation of setting information, automatic approval, and the automatic commissioning process of FIG. 5 may be executed in parallel for each TOR 20. Similarly, the generation of setting information, automatic approval, and automatic commissioning process may be executed (or executed in parallel) for the server 22 (or multiple servers 22) arranged in the GC 16. Similarly, the generation of setting information, automatic approval, and automatic commissioning process may be executed (or executed in parallel) for the OOB 24 (or multiple OOBs 24) arranged in the GC 16. This automatic commissioning process allows multiple GCs scattered throughout the country to be set up and verified simultaneously without regional restrictions.

[0049] The OSS-FS 46 transmits data of the DHCP pool, including the IP address assigned to the TOR 20, the IP address of the TFTP server 52, and the file name of a TOR setting file (described later), to the orchestration server 48 (S64). The orchestration server 48 instructs the network management server 50 to generate the DHCP pool (S66). The network management server 50 generates the DHCP pool and notifies the orchestration server 48 of the completion of generation of the DHCP pool (S68). The orchestration server 48 notifies the OSS-FS 46 of the completion of generation of the DHCP pool (S69).

[0050] The OSS-FS 46 uploads the file (also called the "TOR setting file") containing the setting information for the TOR 20 (such as the host name of the TOR 20) generated in S60 to the TFTP server 52 (S70). The OSS-FS 46 sends a TOR registration request to the orchestration server 48 (S72). Upon receiving the TOR registration request, the orchestration server 48 sends a ping request specifying the host name of the TOR 20 to the TOR 20 (the network of the GC 16) (S74). The orchestration server 48 repeats this ping request periodically (for example, every 15 minutes) (S76).

[0051] The TOR 20 sends a DHCP discover / request to the network management server 50 (S78). The network management server 50 sends a DHCP offer / ACK to the TOR 20, including the IP address assigned to the TOR 20, the IP address of the TFTP server 52, and the file name of the TOR setting file (S80). The TOR 20 sends a TOR setting file download request specifying the file name of the TOR setting file included in the DHCP offer / ACK to the TFTP server 52 (S82). The TFTP server 52 sends the TOR setting file identified by the file name specified in the download request to the TOR 20 (S84).

[0052] The TOR 20 reflects the setting information indicated by the TOR setting file provided by the TFTP server 52 in its own device. For example, the TOR 20 may set the host name included in the setting information in the environment data of its own device, and may also store various table data included in the setting information in the storage unit of its own device. The TOR 20 autonomously restarts (S88). After the restart, the TOR 20 executes operations that reflect the setting information indicated by the TOR setting file.

[0053] The orchestration server 48 sends a ping request specifying the host name of the TOR 20 to the TOR 20 (the network of the GC 16) (S90). The TOR 20 sends a ping response to the orchestration server 48 (S92). When the orchestration server 48 receives the ping response from the TOR 20, it notifies the OSS-FS 46 of the completion of the setting of the TOR 20 (S94).

[0054] In this way, the orchestration server 48 periodically checks the reachability of communication to the communication device of GC16 (TOR 20 in FIG. 5), thereby detecting when the setting information of the communication device has been reflected in the communication device, and notifying OSS 42 that the setting information of the communication device has been reflected in the communication device. As described later, when notified that the setting information of the communication device has been reflected in the communication device, OSS 42 automatically executes a GC acceptance test including a check of the reachability of communication to the communication device. This allows remote automatic testing of the communication device arranged in GC16 to be executed at an appropriate time.

[0055] Fig. 6 is a sequence diagram showing the operation of the communication system 10, following Fig. 5. When the OSS-FS 46 is notified of the completion of the setting of the TOR 20 (completion of the automatic commissioning process), the OSS-FS 46 automatically executes a GC acceptance test (S96). When executing the automatic commissioning process for multiple communication devices arranged in the GC 16, the OSS-FS 46 may execute the GC acceptance test on the condition that it has been notified of the completion of the automatic commissioning process for all communication devices that have been the target of the automatic commissioning process.

[0056] The GC acceptance test includes an OOB 24 acceptance test performed by remotely logging in to the OOB 24, and a TOR 20 acceptance test performed by remotely logging in to the TOR 20. The OOB 24 acceptance test includes (1) verification of the OOB 24 software version (whether it is the latest version or a version that matches the GC type, etc.), (2) confirmation of whether the port is in a connected state, and (3) a ping test to an external device. The TOR 20 acceptance test includes (1) verification of the TOR 20 software version (whether it is the latest version or a version that matches the GC type, etc.), (2) confirmation of the temperature state, (3) confirmation of whether the port is in a connected state, (4) a ping test to an external device, and (5) verification of alarms.

[0057] The OSS-FS46 transmits the result of the GC acceptance test to the OSS-SF44 (S98). The OSS-SF44 stores the result of the GC acceptance test in the storage unit of the OSS42 (S100). The OSS-FS46 generates setup data for the VIM32 and OpenStack34 based on the GC detailed data created in S10, the GC plan data generated in S24, the physical identification information of each communication device stored in S34, and the like (S102). For example, the OSS-FS46 may generate the setup data for the VIM32 and OpenStack34 by setting the IP address indicated by the GC plan data, the MAC address of each communication device, and the like as parameters for a template of the setup data corresponding to the GC type indicated by the GC detailed data.

[0058] The OSS-FS 46 automatically approves the setup of the VIM 32 (S104). The OSS-FS 46 remotely logs in to the server 22 and updates the firmware of the server 22 (S106). The firmware update includes updates of a field programmable gate array (FPGA), a solid state drive (SSD), a network interface card (NIC), a basic input / output system (BIOS), and a firewall.

[0059] The OSS-FS 46 transmits an instruction to install the management node 30 (VIM management node) to the server 22 (S108). The server 22 installs the management node 30. The OSS-FS 46 installs the management node 30 in one of the servers 22 arranged in the GC 16. The management node 30 installed in one server 22 in the GC 16 installs VIM 32 in the multiple servers 22 in the GC 16 (S112).

[0060] When each of the multiple servers 22 arranged in GC 16 successfully installs VIM32, it notifies OSS-FS 46 of the successful installation of VIM32 (S114). When successful installation of VIM32 is notified from all of the servers 22 arranged in GC 16, OSS-FS 46 executes GC acceptance processing (S116). OSS-FS 46 notifies OSS-SF 44 of the completion of GC acceptance (S118). OSS-SF 44 stores information indicating the completion of GC acceptance in the memory unit of OSS 42 (S120).

[0061] Fig. 7 is a sequence diagram showing the operation of the communication system 10 following Fig. 6. When the GC acceptance process of S116 is completed, the OSS-FS 46 automatically approves the start of the setup of OpenStack 34 (S122). The OSS-FS 46 transmits data instructing the installation of OpenStack 34 to the orchestration server 48 (S124). The orchestration server 48 instructs the server 22 to install OpenStack 34 (S126). The process of S126 may include transmitting a virtual machine image file to the server 22. The OpenStack 34 of the server 22 may generate a virtual machine instance based on the virtual machine image file.

[0062] The orchestration server 48 repeatedly queries the server 22 about the installation status of OpenStack 34 (including the virtual machine instance generation status) at predetermined time intervals (e.g., 15 minutes) (S128) (S130). When the installation of OpenStack 34 (including the generation of virtual machine instances) is completed, the server 22 notifies the orchestration server 48 of the success of the installation of OpenStack 34 (S132). The orchestration server 48 notifies the OSS-FS 46 of the success of the installation of OpenStack 34 (S134).

[0063] The OSS-FS 46 cooperates with the orchestration server 48 to set an alert when an abnormality occurs in the GC 16, and also sets periodic jobs (cron jobs, etc.) for backups and the like in the GC 16 (S136). The OSS-FS 46 executes tests on the VIM 32 installed in the multiple servers 22 of the GC 16 (S138). This test includes checking the installation status of the VIM 32 in each server 22.

[0064] The OSS-FS 46 generates data of a DHCP pool (IP address pool) indicating a range of IP addresses that can be assigned to communication devices of the GC 16 (S140). The OSS-FS 46 transmits the data of the DHCP pool to the orchestration server 48 (S142). The OSS-FS 46 registers the DHCP pool in the network management server 50 (S144). The orchestration server 48 notifies the OSS-FS 46 of the completion of setting the DHCP pool (S146). The OSS-FS 46 installs the vRAN function (i.e., the vDU 36 and the vCU 38) in the server 22 (S148). For example, the OSS-FS 46 may transmit a program of the vDU 36 and a program of the vCU 38 to the server 22 and install these programs in the server 22.

[0065] According to the communication system 10 of the embodiment, manual intervention in the setting of the communication devices in the GC 16 is reduced, the setting of the communication devices in the GC 16 is made more efficient, the time required for the setting is significantly shortened, and multiple GCs scattered throughout the country can be simultaneously set up and verified without regional restrictions. For example, according to the communication system 10 of the embodiment, the setting of the communication devices in one GC 16 can be completed in about 9 to 10 hours, and this can be performed simultaneously throughout the country.

[0066] Furthermore, the communication system 10 of the embodiment may be configured to execute the settings of communication devices in multiple GCs 16 in parallel. For example, the OSS 42 may execute in parallel a process to check whether the communication devices of each GC 16 are correctly connected to a predetermined counterpart device based on physical identification information (such as a MAC address) of the communication devices of each GC 16 transmitted from multiple readers 28 arranged in the multiple GCs 16. That is, the OSS-SF 44 and the OSS-FS 46 may execute a cable matrix check (S48 in FIG. 4) for multiple GCs 16 in parallel.

[0067] Furthermore, the OSS 42 may execute in parallel a process of automatically reflecting the setting information of the communication device of each GC 16 in the communication device of each GC 16 when the communication device of each GC 16 is correctly connected to a predetermined counterpart device. That is, the OSS-SF 44 and the OSS-FS 46 may execute in parallel an automatic commissioning process (FIG. 5) for the communication devices arranged in multiple GCs 16. By executing the setting of the communication devices in multiple GCs 16 in parallel, it is possible to simultaneously proceed with the setting process for, for example, 30 to 40 GCs 16.

[0068] The present disclosure has been described above based on examples. These examples are merely illustrative, and it will be understood by those skilled in the art that various modifications are possible in the combination of each component or each treatment process, and that such modifications are also within the scope of the technology of the present disclosure.

[0069] Any combination of the above-mentioned examples and modifications is also useful as an embodiment of the present disclosure. A new embodiment resulting from the combination has the effects of each of the combined examples and modifications. In addition, it will be understood by those skilled in the art that the functions to be performed by each component described in the claims can be realized by each component shown in the examples and modifications alone or in cooperation with each other. [Industrial Applicability]

[0070] The technology of the present disclosure can be applied to an apparatus or system relating to the setting of communication devices arranged in a GC (Group Center). [Explanation of symbols]

[0071] 10 Communication System, 16 GC, 20 TOR, 22 Server, 24 OOB, 28 Reader, 40 CDC, 42 OSS, 48 Orchestration Server.

Claims

1. A reading device, A setting system including one or more computers that are communicatively connected to the reading device via a communication network; Equipped with The reader reads the identification information of the communication device and transmits the identification information of the communication device to the communication network; the setting system receives the identification information via the communication network, and confirms whether or not the communication device is correctly connected to a predetermined opposite device based on the identification information; when it is confirmed that the communication device is correctly connected to a predetermined opposite device, the setting system causes the communication device to reflect setting information of the communication device; the setting system detects that the setting information of the communication device has been reflected in the communication device by confirming communication reachability to the communication device; the setting system executes a test on the communication device when it is detected that the setting information of the communication device has been reflected in the communication device. Computer system.

2. The setting system includes at least a first computer and a second computer communicatively connected to the first computer via a communication network; the first computer detects that the setting information of the communication device has been reflected in the communication device; the second computer executes the test; 2. The computer system of claim 1.

3. A setting method for a communication device by a computer system including a reading device and a setting system including one or more computers communicatively connected to the reading device via a communication network, comprising: the reading device reading identification information of the communication device from the communication device and transmitting the identification information of the communication device to the communication network; a step of the setting system receiving the identification information via the communication network and confirming whether or not the communication device is correctly connected to a predetermined opposite device based on the identification information; a step of causing the setting system to reflect setting information of the communication device in the communication device when it is confirmed that the communication device is correctly connected to a predetermined opposite device; a step of detecting, by the setting system confirming communication reachability to the communication device, that setting information of the communication device has been reflected in the communication device; a step of the setting system executing a test on the communication device when it is detected that the setting information of the communication device has been reflected in the communication device; A setting method comprising:

Images