Conversion method, conversion device, and conversion program
The method synchronizes configurations and submits service orders in separate periods to minimize service disruptions during network device replacements, addressing the issue of prolonged outages and restrictions.
Patent Information
- Application Number
- JP2024502301
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-02-22
- Publication Date
- 2025-08-20
- Estimated Expiration
- 2042-02-22
AI Technical Summary
Conventional network device replacement methods result in prolonged service outages due to configuration differences and complex conversion logic, leading to extended service order restrictions.
A method involving a conversion process to synchronize configurations between old and new network devices, followed by service order submission and route switching in separate periods, minimizing service disruptions.
Prevents prolonged service outages by allowing for efficient configuration conversion and service order input before route switching, reducing the duration of service restrictions.
Smart Images

Figure 0007726366000001 
Figure 0007726366000002 
Figure 0007726366000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to a conversion method, a conversion device, and a conversion program. [Background technology]
[0002] When replacing a network device (hereinafter referred to as a NW (Network) device) that makes up a network, it is necessary to transfer the setting information (hereinafter referred to as a config) from the NW device before replacement to the NW device after replacement (hereinafter referred to as a config migration) and switch the path.
[0003] Configuration migration involves the steps of extracting the configuration from the source network device, converting the extracted configuration, and inputting the converted configuration into the destination network device.
[0004] If a difference in configuration occurs between the source network device and the destination network device, the start of service to the user may be delayed or the service may not be provided at all.
[0005] Therefore, in order to prevent the occurrence of configuration differences, a method has been proposed in which SO (Service Order) restrictions are imposed when migrating configurations, and network equipment is replaced all at once during nighttime hours, etc. [Prior art documents] [Patent documents]
[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-222465 Summary of the Invention [Problem to be solved by the invention]
[0007] However, the conventional technology has a problem in that the SO restriction associated with the replacement work of the network equipment may become long.
[0008] For example, if the amount of configuration becomes enormous and the configuration conversion logic becomes complex, the configuration migration may not be completed during nighttime hours alone, which may result in a longer period of SO restrictions and even longer periods when services cannot be provided. [Means for solving the problem]
[0009] In order to solve the above-mentioned problems and achieve the object, the conversion method is a conversion method executed by a computer, and is characterized by including: a configuration conversion process for converting a configuration extracted from a first network device that transfers data in a network and inputting the converted configuration to a second network device that transfers data in a first period; a service order input process for inputting a service order input to the first network device to the second network device in a second period; and a switching process for switching a route on the network that passes through the first network device to a route on the network that passes through the second network device in a third period. [Effects of the Invention]
[0010] According to the present invention, it is possible to prevent the SO restriction caused by the replacement work of the network device from becoming long. [Brief explanation of the drawings]
[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a network system before replacement. [Figure 2] FIG. 2 is a diagram illustrating the conversion process. [Figure 3] FIG. 3 is a diagram illustrating how to submit a service order to the second network device. [Figure 4] FIG. 4 is a diagram illustrating the switching process. [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of a network system after replacement. [Figure 6] FIG. 6 is a diagram illustrating a method for synchronizing SOs. [Figure 7]FIG. 7 is a diagram illustrating a method for synchronizing SOs. [Figure 8] FIG. 8 is a diagram illustrating another example of the configuration of the conversion tool. [Figure 9] FIG. 9 illustrates an example of the configuration of a conversion device. [Figure 10] FIG. 10 is a flowchart showing the flow of processing by the conversion device. [Figure 11] FIG. 11 is a diagram illustrating an example of a computer that executes a conversion program. DETAILED DESCRIPTION OF THE INVENTION
[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The following describes in detail embodiments of a conversion method, a conversion device, and a conversion program according to the present application, with reference to the accompanying drawings. However, the present invention is not limited to the embodiments described below.
[0013] [First embodiment] First, a network system in which a network device to which a configuration is to be migrated is arranged will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the configuration of a network system before replacement.
[0014] 1, the network system 1 includes an SO input device 10, a network device 20, a network device 30, a user-side device 40, and a conversion device 50. The network device 20 is an example of a first network device. The network device 30 is an example of a second network device.
[0015] For example, the NW devices 20 and 30 are core routers arranged in a core network, and the user device 40 is an access switch or a terminal device arranged in the user network.
[0016] For example, an IP packet transmitted from the user device 40 is transferred to another device or network via the NW device 20. The NW device 20 also transfers the IP packet to the user device 40.
[0017] In the embodiment, it is assumed that the network device 20 is replaced with the network device 30. That is, after the replacement, IP packets transmitted from the user-side device 40 are forwarded to other devices or networks via the network device 30. In addition, the network device 30 forwards the IP packets to the user-side device 40.
[0018] The SO insertion device 10 inserts an SO into the NW device 20 or the NW device 30. Here, the SO is data that describes information about the user (contractor) and information about the service used by the user. After the SO is inserted into the NW device 20, the user can use services such as forwarding IP packets.
[0019] Furthermore, SO restriction means that SOs are not input to each network device, and therefore, while SO restriction is in effect, users may not be able to use services.
[0020] Here, there are various differences between the configuration of the network device 20 and the configuration of the network device 30. For example, the configuration of the network device 20 and the configuration of the network device 30 may differ from each other in the size of fixed-length data, units of numerical values, syntax, default setting items and their contents, etc.
[0021] The conversion device 50 converts the configuration of the network device 20 into a format that can be input to the network device 30, and inputs the converted configuration to the network device 30.
[0022] The network system 1 replaces the NW device through a conversion process, a service order submission process, and a switching process.
[0023] As shown in Fig. 2, in the conversion process, the conversion device 50 converts the configuration extracted from the NW device 20 that transfers data during a first period, and inputs the converted configuration into the NW device 30 that transfers data. Fig. 2 is a diagram explaining the conversion process.
[0024] Here, the day when the network replacement is completed is defined as the switching day. For example, the first period is the day shift (for example, 9:00 to 17:00) on the work start day, which is the day before the switching day.
[0025] In addition, in the service order submission process, the conversion device 50 submits, to the NW device 30, an SO to be submitted to the NW device 20 in a second period after the first period. Fig. 3 is a diagram illustrating the submission of a service order to the second NW device.
[0026] As a result, the configurations of the network devices 20 and 30 can be synchronized during the second period.
[0027] For example, the second period is from the end of the day shift (for example, 17:00) to the start of the night shift (for example, 22:00) on the work start date.
[0028] In addition, in the switching step, the NW device 20 switches the route on the network that passes through the NW device 20 to the route on the network that passes through the NW device 30 during the third period (route switching). Figure 4 is a diagram illustrating the switching step.
[0029] In addition, in the switching process, the SO insertion device 10 switches the SO insertion destination from the NW device 20 to the NW device 30.
[0030] For example, the third period is within one hour (for example, about 30 minutes) from the night work start time (for example, 22:00) on the work start date.
[0031] The switching process involves switching routes, reconnecting physical lines, reassigning IP addresses, and so on.
[0032] In addition, SO restrictions are applied in the switching process, but not in the conversion process and service order submission process.
[0033] In this way, by completing the conversion process and the service order submission process before the switching process, the time required for the SO restriction can be minimized. For example, if the switching process can be completed in 30 minutes, the time required for the SO restriction will also be 30 minutes.
[0034] On the other hand, if the conversion process and service order input process are not performed in advance, it is necessary to perform the conversion process and the changeover process consecutively after performing the SO control at night. In that case, for example, it is necessary to perform the SO control from the start of the night work until before the day shift of the next day when the entire process is completed (for example, from 22:00 to 6:00 the next day).
[0035] Fig. 5 is a diagram showing an example of the configuration of a network system after replacement. As shown in Fig. 5, after the NW device 20 is replaced with the NW device 30, the user-side device 40 is connected to the NW device 30 instead of the NW device 20. In addition, the SO insertion device 10 inserts an SO into the NW device 30 instead of the NW device 20.
[0036] Here, a first method, a second method, and a third method will be described as variations of the method for submitting an SO in the service order submission process.
[0037] 3, in the first method, the conversion device 50 inputs an SO to the network device 30 every time an SO is input to the network device 20. At this time, the conversion device 50 sequentially converts the SO input from the SO input device 10 to the network device 20, and inputs the converted SO to the network device 30. This makes it possible to synchronize the SOs between the network devices 20 and 30 in real time.
[0038] Next, in the second method, as shown in Fig. 6, the conversion device 50 collectively inputs multiple SOs stored in the NW device 20 into the NW device 30. Fig. 6 is a diagram illustrating a method for synchronizing SOs.
[0039] At this time, the conversion device 50 converts a plurality of SOs that are input from the SO input device 10 to the network device 20 and stored in the network device 20 in a batch, and inputs the converted plurality of SOs to the network device 30. This reduces the operation frequency of the conversion device 50.
[0040] In the third method, as shown in Fig. 7, the SO insertion device 10 inserts each SO into both the network device 20 and the network device 30. Fig. 7 is a diagram for explaining a method for synchronizing SOs.
[0041] This allows the SO to be input to both the NW device 20 and the NW device 30 without conversion by the conversion device 50.
[0042] The conversion device 50 may be realized as a function of any of the network devices. For example, as shown in Fig. 8, the network device 20 may be provided with a conversion tool 50a, which is a program having the same functions as the conversion device 50. Fig. 8 is a diagram showing another example of the configuration of the conversion tool.
[0043] In this case, the conversion tool 50a converts the SO submitted from the SO submission device 10 and submits the converted SO to the NW device 30.
[0044] The configuration of the conversion device according to the first embodiment will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the configuration of the conversion device.
[0045] As shown in FIG. 9, the conversion device 50 includes a communication unit 51, a storage unit 52, and a control unit 53.
[0046] The communication unit 51 performs data communication with other devices. For example, the communication unit 51 transmits and receives data to and from the NW device 20 and the NW device 30.
[0047] The storage unit 52 is a storage device such as a hard disk drive (HDD), a solid state drive (SSD), an optical disk, etc. The storage unit 52 may be a data-rewritable semiconductor memory such as a random access memory (RAM), a flash memory, or a non-volatile static random access memory (NVSRAM). The storage unit 52 stores an operating system (OS) and various programs executed by the conversion device 50.
[0048] The control unit 53 controls the entire conversion device 50. The control unit 53 is, for example, an electronic circuit such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a GPU (Graphics Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).
[0049] The control unit 53 also has an internal memory for storing programs that define various processing procedures and control data, and executes each process using the internal memory.
[0050] The control unit 53 also functions as various processing units by running various programs. For example, the control unit 53 functions as a conversion unit 531 and an input unit 532.
[0051] The conversion unit 531 executes the above-mentioned conversion process. During the first period, the conversion unit 531 converts the configuration extracted from the NW device 20 that transfers data in the network, and inputs the converted configuration to the NW device 30 that transfers data in the network.
[0052] The input unit 532 executes the above-mentioned service order input process. During a first period, the input unit 532 inputs the configuration converted by the conversion unit 531 to the network device 30, and during a second period after the first period, the input unit 532 inputs the service order to be input to the network device 20 to the network device 30.
[0053] [Processing of the first embodiment] 10 is a flowchart showing the flow of processing by the conversion device 50. As shown in FIG. 10, first, the conversion device 50 receives input of a pre-conversion configuration (step S101).
[0054] The pre-conversion configuration is a configuration extracted from the NW device 20. The configuration is a text file in which a predetermined command is written on each line.
[0055] Next, the conversion device 50 reads one line, multiple lines, or all lines of the pre-conversion configuration at once (step S102).Then, for each line that has been read, the conversion device 50 stores the data (step S103).
[0056] Data storage is a process that converts a single command line and adds the converted command to the converted config (or adds nothing). For example, data storage includes trimming, syntax analysis, and conversion.
[0057] If the read line is not the last line (step S104, No), the conversion device 50 returns to step S102 and reads the next line.
[0058] If the read line is the last line (step S104, Yes), the conversion device 50 generates a post-conversion configuration. For example, the conversion device 50 extracts the data stored in the temporary storage area in the form of a file that can be moved, copied, or otherwise manipulated.
[0059] Furthermore, the conversion device 50 inputs the converted configuration into the NW device 30 (step S105).
[0060] [Effects of the first embodiment] As explained above, in a first period, the conversion device 50 converts the configuration extracted from the NW device 20 that transfers data in the network, and inputs the converted configuration to the NW device 30 that transfers the data (conversion process). In addition, in a second period, the conversion device 50 inputs a service order to be input to the NW device 20 to the NW device 30 (service order input process). In addition, in a third period, the NW device 20 switches the route on the network that passes through the NW device 20 to a route on the network that passes through the NW device 30 (switching process).
[0061] In this way, by completing the conversion process and the service order submission process before the switching process, it is possible to prevent the SO restriction associated with the replacement work of the network equipment from becoming too long.
[0062] Here, the SO input device 10 inputs (applies) SO to the NW device 20 at regular intervals (for example, every hour), thereby realizing replacement of the NW device without SO restrictions.
[0063] For example, the SO insertion device 10 connects to the network device 20 via telnet at time t, finishes inserting the SO within one hour from time t, and waits until one hour has passed from time t. Then, at time t+1, one hour later, the SO insertion device 10 inserts the SO again.
[0064] For example, if the configuration of the network device 20 includes about 100,000 lines of commands and the conversion device 50 can extract the commands in one cycle (for example, one hour), the SO restriction becomes unnecessary.
[0065] Also, for example, the conversion device 50 extracts the difference in the SOs input to the network device 20 in each period, so that the SO restrictions become unnecessary.
[0066] [System configuration, etc.] Furthermore, the components of each device shown in the figure are functional concepts and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of each device is not limited to that shown, and all or part of the devices can be functionally or physically distributed or integrated in any unit depending on various loads, usage conditions, etc. Furthermore, all or any part of the processing functions performed by each device can be realized by a CPU (Central Processing Unit) and a program analyzed and executed by the CPU, or can be realized as hardware using wired logic. Note that the program may be executed not only by the CPU but also by other processors such as a GPU.
[0067] Furthermore, among the processes described in this embodiment, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.In addition, the information including the processing procedures, control procedures, specific names, various data and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified.
[0068] [program] In one embodiment, the conversion device 50 can be implemented by installing a conversion program that executes the above conversion process as package software or online software on a desired computer. For example, by having an information processing device execute the above conversion program, the information processing device can function as the conversion device 50. The information processing device referred to here includes desktop and notebook personal computers. Furthermore, other information processing devices also include mobile communication terminals such as smartphones, mobile phones, and PHS (Personal Handyphone Systems), as well as slate terminals such as PDAs (Personal Digital Assistants).
[0069] The conversion device 50 can also be implemented as a conversion server device that provides services related to the above conversion process to a client terminal device used by a user. For example, the conversion server device is implemented as a server device that receives a pre-conversion configuration as input and outputs a post-conversion configuration as output. In this case, the conversion server device may be implemented as a web server or as a cloud that provides services related to the above conversion process through outsourcing.
[0070] 11 is a diagram showing an example of a computer that executes a conversion program. The computer 1000 includes, for example, a memory 1010 and a CPU 1020. The computer 1000 also includes a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These components are connected by a bus 1080.
[0071] The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM (Random Access Memory) 1012. The ROM 1011 stores a boot program such as a BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to a hard disk drive 1090. The disk drive interface 1040 is connected to a disk drive 1100. A removable storage medium such as a magnetic disk or optical disk is inserted into the disk drive 1100. The serial port interface 1050 is connected to a mouse 1110 and a keyboard 1120, for example. The video adapter 1060 is connected to a display 1130, for example.
[0072] The hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, a program that defines each process of the conversion device 50 is implemented as a program module 1093 in which computer-executable code is written. The program module 1093 is stored, for example, in the hard disk drive 1090. For example, a program module 1093 for executing processes similar to those of the functional configuration of the conversion device 50 is stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced with an SSD (Solid State Drive).
[0073] Furthermore, setting data used in the processing of the above-described embodiment is stored as program data 1094, for example, in the memory 1010 or the hard disk drive 1090. Then, the CPU 1020 reads the program module 1093 or the program data 1094 stored in the memory 1010 or the hard disk drive 1090 into the RAM 1012 as necessary, and executes the processing of the above-described embodiment.
[0074] The program module 1093 and program data 1094 are not limited to being stored in the hard disk drive 1090, but may also be stored in, for example, a removable storage medium and read by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and program data 1094 may be stored in another computer connected via a network (such as a local area network (LAN) or a wide area network (WAN)). The program module 1093 and program data 1094 may then be read by the CPU 1020 from the other computer via the network interface 1070. [Explanation of symbols]
[0075] 1 Network System 10 SO injection device 20, 30 NW equipment 40 User side device 50 Conversion Device 50a Conversion Tool 51 Communications Department 52 Storage section 53 Control Unit 531 Conversion Unit 532 Insertion section
Claims
1. 1. A computer-implemented conversion method comprising: a configuration conversion step of converting a configuration extracted from a first network device that transfers data in a network during a first period and inputting the converted configuration into a second network device that transfers data; a service order input step of inputting a service order, which is input to the first network device at predetermined intervals during a second period after the first period, to the second network device every time the service order is input; a switching step of switching a route on the network that passes through the first network device to a route on the network that passes through the second network device during a third period that is later than the second period; A conversion method comprising:
2. a conversion unit that converts a configuration extracted from a first network device that transfers data in a network during a first period and inputs the converted configuration into a second network device that transfers data in the network; an input unit that inputs the configuration converted by the conversion unit to the second network device during a first period, and inputs a service order, which is input to the first network device at predetermined intervals during a second period after the first period, to the second network device every time the service order is input; A conversion device comprising:
3. a conversion step of converting a configuration extracted from a first network device that transfers data in a network during a first period and inputting the converted configuration into a second network device that transfers data in the network; an input step of inputting the configuration converted by the conversion step to the second network device during a first period, and inputting a service order, which is input to the first network device at a predetermined cycle, to the second network device every time the service order is input during a second period after the first period; A conversion program characterized by causing a computer to execute the above.
Citation Information
Patent Citations
Method for transferring subscriber data between service control nodes
JP2003234822A
Information processor, equipment setup system, and program
JP2008027127A
Data migration method, data migration system, migration source server, migration destination server, and data migration program
JP2015222465A
Communication system, migration method, data processing device, and data processing program
JP2020036264A
Data processing device, data processing method, and data processing program
JP2020046822A