System migration support device and system migration support method

Abstract

The present invention aims to provide a technology for reliably and efficiently transitioning control systems. [Solution] The system migration support device includes a message communication unit that receives and duplicates control messages; a network communication unit that transmits the duplicated control messages to a first service of a first system and a second service corresponding to the first service of a second system, and receives a first response message from the first service and a second response message from the second service in response to the control messages; and a message comparison unit that compares and analyzes the first response message and the second response message to determine whether to migrate the first service in place of the second service, or whether to revert the second service in place of the first service.

Description

Technical Field

[0001] The present invention relates to a system migration support device and a system migration support method.

Background Art

[0002] Migration of a large-scale control system involves numerous difficulties. Generally, a large-scale control system includes a large number of services, and an enormous amount of time and cost are required to stably operate all these services after migration. In particular, at the time of migration, it is important to ensure data synchronization between services of the same function in the control systems before and after migration. However, depending on the operation field of the control system, there is also a problem that it is difficult to stop the control system for migration, which further makes the reliable and efficient migration of the control system more difficult.

[0003] On the other hand, in recent years, the demand for migrating on-premises control systems to the cloud environment has been increasing, and it is expected that the migration of large-scale control systems will further increase in the future.

[0004] In contrast, Patent Document 1 aims to provide a plant monitoring and control system migration device that enables a gradual migration of a monitoring and control system in which some facilities are controlled by an existing monitoring and control device and other facilities are controlled by a newly installed monitoring and control device. It discloses a technology "comprising a state signal transceiver that receives state signals transmitted from each of a plurality of facilities and transmits the state signals to an existing control device and a newly installed control device different from the existing control device; a control signal receiver that receives an old control signal generated by the existing control device for each of the plurality of facilities based on the state signal and a new control signal generated by the newly installed control device for each of the plurality of facilities based on the state signal; and a control signal selector that selects, for each of the plurality of facilities, a control signal to be transmitted from among the old control signal and the new control signal under predetermined conditions for each of the plurality of facilities."

[0005] Furthermore, Patent Document 2 discloses a cloud service control device that offers high availability and information security, and enables rapid and flexible system migration. The device comprises: a first communication unit that controls communication with a cloud service that provides plant control functions for controlling a plant; a second communication unit that controls communication with a user device that utilizes service information related to the cloud service; a verification unit that verifies the operating status of the cloud service; a selection unit that selects the cloud service based on the verified operating status; and an information transmission unit that transmits the service information between the selected cloud service and the user device. [Prior art documents] [Patent Documents]

[0006] [Patent Document 1] Japanese Patent Publication No. 2010-205163 [Patent Document 2] Patent No. 6673227 [Overview of the Initiative] [Problems that the invention aims to solve]

[0007] However, generally speaking, large-scale control system migrations are not successful on the first try, and there is a transitional period with a mix of partial successes and failures. Patent documents 1 and 2 do not address how to handle such transitional periods. Addressing these transitional periods is necessary to ensure that large-scale control system migrations are carried out reliably and efficiently. Therefore, the present invention aims to provide a technology that ensures a reliable and efficient transition of control systems by addressing the aforementioned transitional period. [Means for solving the problem]

[0008] To solve the above problems, one representative system migration support device of the present invention supports migration from a first system to a second system, and includes: a message communication unit that receives and duplicates control messages; a network communication unit that transmits the duplicated control messages to a first service of the first system and a second service corresponding to the first service of the second system, and receives a first response message from the first service and a second response message from the second service in response to the control messages; and a message comparison unit that compares and analyzes the first response message and the second response message to determine whether to migrate the first service of the first system in place of the second service of the second system, or whether to return the second service of the second system in place of the first service of the first system. [Effects of the Invention]

[0009] According to the present invention, the transition of the control system can be carried out reliably and efficiently. Other issues, configurations, and effects not mentioned above will be clarified by the description of the embodiments for carrying out the invention below. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 shows an example of a common hardware configuration for the system according to this embodiment. [Figure 2] Figure 2 shows an example of a control system that is assisted in the transition by the system transition support device of Example 1. [Figure 3] Figure 3 shows an example of the basic operation of the system migration support device of Example 1. [Figure 4] Figure 4 shows an example of the system migration support device of Example 1. [Figure 5] Figure 5 shows an example of the message flow during the transition / revert process in Example 1. [Figure 6]FIG. 6 is a diagram showing an example of the migration process for the master-slave control system of the system migration support device according to Embodiment 1. [Figure 7] FIG. 7 is a diagram showing an example of the rollback process for the master-slave control system of the system migration support device according to Embodiment 1. [Figure 8] FIG. 8 is a diagram showing an example of the means related to the message comparison unit of the system migration support device according to Embodiment 1. [Figure 9] FIG. 9 is a diagram showing an example of the analysis report according to Embodiment 1. [Figure 10] FIG. 10 is a diagram showing an example of the operation policy (guidelines) according to Embodiment 1. [Figure 11] FIG. 11 is a diagram showing an example of the operation policy (standards) according to Embodiment 1. [Figure 12] FIG. 12 is a diagram showing an example of the enhancement and reduction of the operation policy according to Embodiment 2. [Figure 13] FIG. 13 is a diagram showing an example of the control LAN simulator to which the system migration support device according to Embodiment 3 is connected. [Figure 14] FIG. 14 is a diagram showing an example of the connection configuration when migrating the pre-migration system migration support device to the post-migration system migration support device using the system migration support device.

MODE FOR CARRYING OUT THE INVENTION

[0011] Hereinafter, this embodiment will be described with reference to the drawings. Note that the present invention is not limited by this embodiment. Also, in the description of the drawings, the same parts are denoted by the same reference numerals.

[0012] When there are a plurality of components having the same or similar functions, they may be described with different subscripts attached to the same reference numeral. Also, when it is not necessary to distinguish these plurality of components, the subscripts may be omitted in the description. Also, terms such as "first", "second", etc. may be used to describe various elements or components, but these elements or components should not be limited by these terms. These terms are only used to distinguish one element or component from another.

[0013] In this embodiment, as the control systems that the system migration support device supports migration for, the pre-migration control system (main system), the pre-migration control system (slave system), the post-migration control system (main system), and the post-migration control system (slave system) are taken up. Sometimes, the four control systems are collectively referred to as the control system. Also, when there is no need to distinguish between the pre-migration control system (main system) and the pre-migration control system (slave system), it may be referred to as the pre-migration control system. The same applies to the post-migration control system (main system) and the post-migration control system (slave system).

[0014] Next, the terms commonly used in this embodiment will be described. (Service) In this embodiment, a service refers to a service application (including those referred to as microservices) that constitutes a control system, which is not tightly coupled with other service applications and can be handled independently as a system component. (Operation Policy) In this embodiment, an operation policy refers to the regulations regarding the migration and rollback of services by the system migration support device. For example, it includes the guidelines for migration processing and rollback processing, the criteria for obtaining migration decisions and rollback decisions, and the conditions for enhancing or reducing the resources of the new system associated with the migration process.

[0015] (Overview of this Embodiment) Generally, in the migration of a large-scale control system, since system failures after migration can be fatal, in order to overcome the above-mentioned transitional period, it is desirable to migrate the control system step by step. However, depending on the control system, it may be difficult to shut down the current system during the migration, making a phased migration impossible. Even if a phased migration is performed, there may be limitations on recovery in case of malfunctions, making it impossible to guarantee the reliable operation of the system after the migration. Therefore, in this embodiment, the unit of migration is a service, and this service is actually run on both the pre-migration control system (current system) and the post-migration control system (new system) to determine whether migration is possible for each service. Furthermore, if a problem occurs with a post-migration service, that service is reverted to the pre-migration service, thereby enabling a safe and reliable migration without stopping the current system.

[0016] <Common Hardware Configuration> First, with reference to Figure 1, the hardware configuration common to each system of this embodiment, such as the pre-migration control system, the post-migration control system, and the system migration support device, will be described.

[0017] Figure 1 shows an example of a common hardware configuration for a system according to this embodiment. Each system includes, as its main components, an input / output controller 1, a CPU 2, an HDD 3, a monitor controller 4, memory 5, a network interface 6, and a display 7. Each component will be described below.

[0018] The input / output controller 1 is a device that manages the interface with external devices in each system. It controls the exchange of data with input devices (keyboard, mouse, etc.) and output devices (printer, storage device, etc.) to the system, and has the function of ensuring the overall operability and expandability of the system.

[0019] CPU2 is the central processing unit used commonly throughout the entire system. It oversees overall control within the system and has the capability to perform real-time processing within the system.

[0020] HDD3 is a data storage device used commonly throughout the entire system. It has the function of long-term storage of important system data and logs. Any data storage device, such as an SSD, can be used.

[0021] The monitor controller 4 is a device that connects data from the system to the display 7. It has the function of controlling the display on the display 7.

[0022] Memory 5 is a storage device used commonly throughout the entire system. It works in conjunction with the system's CPU 2 and has the function of temporarily holding data and programs necessary while the system is running.

[0023] Network interface 6 is a communication interface for connecting systems. It has the function of sending and receiving data between systems.

[0024] Display 7 is a device that visually displays the system status and operating conditions. It functions as a user interface.

[0025] (Example 1) <Overview of the control system> Referring to Figure 2, an overview of the control system that the system migration support device of Embodiment 1 assists in the migration will be described. In this embodiment, the control system that assists in the migration is, for example, a control system for the integrated management of a mobile object (bus, transport truck, train, etc.) moving on a fixed track, but it is not limited to this.

[0026] Figure 2 shows an example of a control system that is assisted in the transition by the system transition support device of Example 1. As shown in Figure 2, the pre-transition control system (main system) 20 and the pre-transition control system (subordinate system) 21, and the post-transition control system (subordinate system) 31 are each connected to the control LAN 40 via the system transition support device 10.

[0027] Here, the pre-migration control system is the current system before the migration, and the post-migration control system is the new system after the migration. The post-migration control system (main system) 30 corresponds to the new system of the pre-migration control system (main system) 20, and the post-migration control system (secondary system) 31 corresponds to the new system of the pre-migration control system (secondary system) 21.

[0028] The control LAN 40 is connected to the controlled devices (control devices, such as video devices, signal devices, and operation management devices) that the control system controls.

[0029] In this embodiment, the control systems are all master-slave systems. A master-slave system is a method of achieving a highly reliable system by preparing two identical systems, a master and a slave, for a single process. Normally, the master system (active machine) performs the processing, and when a failure occurs or an error is detected in the master system, it switches to the standby slave system (backup machine). In this embodiment as well, the master and slave systems have basically the same system configuration.

[0030] The control system in this embodiment provides various services for integrated management of mobile objects. The post-transition control system basically provides services corresponding to each service provided by the pre-transition control system. Below, each service will be described using the pre-transition control system (main system) in Figure 2 as an example.

[0031] (Real-time location display service) This service provides a function to display the real-time location of controlled moving objects (e.g., buses, transport trucks, trains, etc.). This allows for a visual understanding of the current location of moving objects managed by the control system, enabling efficient operational management.

[0032] (Incident Management Service) This service provides functions for managing incidents (failures and problems) that occur in the control system and recording the responses to them. This enables the rapid resolution of various problems that occur during the operation of the control system, and ensures the stable operation of the control system.

[0033] (Crew support services) This service provides functions that enable vehicle crews to efficiently support vehicle users. This makes it possible to provide a comfortable service that responds immediately to user needs.

[0034] (Operation status monitoring service) This service provides functions for real-time monitoring of the status of transportation systems and facilities. This makes it possible to accurately understand the operating status of moving vehicles.

[0035] (Communication Services) This service provides functions for communication between internal devices of a control system and between the control system and external systems. This enables rapid and accurate data exchange and information transmission between devices and systems, maintaining the integrity of the entire system.

[0036] (Map display service) This service displays map information used within the control system and provides functions to support navigation. This allows for the visual display of the route and location information of moving objects, enabling operations managers and crew members to make appropriate decisions.

[0037] (Schedule management service) This service provides functions for managing regulations and schedules for transportation and transport facilities. This enables the efficient formulation and modification of operational plans, and ensures the smooth operation of the entire system.

[0038] (Data collection and analysis services) This function provides the ability to collect and analyze data generated within the control system. This makes it possible to obtain basic data for evaluating and optimizing the operational status and performance of the control system.

[0039] (Mobile tracking service) This service provides functions for determining the current location and tracking the movement history of mobile objects. This makes it possible to understand the operational status of mobile objects in detail and modify the operational plan as needed.

[0040] (Infrastructure management services) This service provides functions for managing the infrastructure of transportation and transport facilities. This makes it possible to ensure safety and reliability in operations.

[0041] (Event notification service) This service provides a function to notify system administrators when critical events occur in the control system. This allows system administrators to respond quickly to important events.

[0042] (Device control service) This service provides functions for managing and controlling devices such as sensors and recording devices connected to the control system. This makes it possible to understand the operating status of each device and make adjustments or controls as needed.

[0043] (User authentication and access control service) This service provides functions for user authentication and access control. This ensures that only users with appropriate privileges can participate in the migration of the control system, thereby guaranteeing system security.

[0044] (Network communication services) This service provides functions to facilitate smooth communication with external systems. This ensures reliable data synchronization and information transfer between systems before and after migration, thereby supporting the migration process.

[0045] <Basic Operation of System Migration Support Device> Next, referring to Figure 3, the basic operation of the system migration support device in this embodiment will be described. Figure 3 shows an example of the basic operation of the system migration support device in Embodiment 1. The basic operation of the system migration support device in this embodiment is migration and rollback. Migration is the operation of replacing the services of the pre-migration control system with the services of the post-migration control system, and rollback is the operation of replacing the services of the post-migration control system, which have been migrated, with the services of the pre-migration control system. Migration and rollback are performed on a service-by-service basis.

[0046] Figure 3 shows that the crew support services and data collection / analysis services of the pre-transition control system (main system) 20 meet the transition criteria and are therefore transferred to the corresponding services of the post-transition control system (main system) 30, and that the operational status monitoring service of the post-transition control system (main system) 30 no longer meets the transition criteria after the transition and is therefore reverted to the corresponding services of the pre-transition control system.

[0047] Service migration / reverting can be performed automatically or as a suggestion to the system administrator. Furthermore, service migrations can be prioritized, starting with the least critical services to minimize the impact of migration-related problems. Details of these transitions / reverts can be specified in Operational Policy 14, which will be described later.

[0048] Note that migration and rollback are relatively similar processes, so the following explanation may use migration as an example, but the same applies to rollback.

[0049] <Overview of System Migration Support Device> Referring to Figure 4, an overview of the system migration support device according to Example 1 will be described. Figure 4 shows an example of the system transition support device of Embodiment 1. First, the overview of the processing of the system transition support device 10 will be explained with reference to Figure 4(a). The dashed arrows in the figure represent the flow of messages.

[0050] The system migration support device 10, upon receiving a control message from the controlled device via the control LAN 40, sequentially performs three processes: duplicating the control message and sending it to the control system; comparing and analyzing the response messages; and sending the response messages back to the controlled device. Each of these processes is described below.

[0051] (Duplicating and sending control messages) When the system migration support device 10 receives a control message from the control LAN 40, it duplicates it and sends it to both the pre-migration control system (main system) 20 and the post-migration control system (main system) 30.

[0052] In this embodiment, since the control system is a master-slave system, master-slave switching devices 50 and 60 are provided between the system transition support device and the pre-transition control system and the post-transition control system, respectively, to manage the flow of control messages between the master and slave systems. In this example, control messages transmitted from the system transition support device 10 are distributed to the master system by the master-slave switching devices 50 and 60, respectively. Note that the master-slave switching devices 50 and 60 can also distribute control messages to both the master and slave systems.

[0053] The pre-migration control system (main system) 20 and the post-migration control system (main system) 30 analyze the received control messages, perform predetermined processing in the corresponding services, create response messages, and transmit them to the system migration support device 10. The response message may consist of multiple messages (a group of response messages, so to speak) for controlling the controlled device.

[0054] (Comparison and analysis of response messages) When the system migration support device 10 receives response messages from both the pre-migration control system (main system) 20 and the post-migration control system (main system) 30, it compares and analyzes both response messages based on the operation policy 14 (described later), makes a decision regarding the migration of the relevant services, and executes the necessary processing. Details of this comparison and analysis will be described later.

[0055] (Reply to the response message) The system migration support device 10, based on its judgment regarding the migration, sends one of the response messages to the controlled device via the control LAN 40 if the migration is possible, and sends only the response message from the pre-migration control system (main system) 20 to the controlled device via the control LAN 40 if the migration is not possible. In this example, only the response message from the pre-migration control system (main system) is sent.

[0056] Next, with reference to Figure 4(b), an overview of each part of the system migration support device 10 will be described. As shown in Figure 4(b), the system migration support device 10 has various components (A) to (M), but the three parts that are primarily responsible for the three processes mentioned above are the following (A) message communication unit, (B) message comparison unit, and (M) network communication unit. Each of these parts will be described below.

[0057] (A) Message Communication Unit The message communication unit has the function of facilitating communication between the control system and the controlled devices (e.g., video equipment, signaling equipment, operation management equipment) via the control LAN 40. This includes functions such as duplicating control messages received via the control LAN and transmitting them to the pre-transition control system and the post-transition control system, receiving response messages to control messages from the pre-transition control system and the post-transition control system, respectively, and selectively sending response messages back to the controlled devices via the control LAN.

[0058] (B) Message comparison section The message comparison unit includes functions to compare and analyze response messages from the pre-migration control system and the post-migration control system, to make decisions regarding migration or rollback, and to output instructions necessary to execute the processes related to migration or rollback. Details of the message comparison unit will be described later.

[0059] (C) Message filtering unit The message filtering unit includes a function to eliminate unnecessary messages based on their content and allow only appropriate messages to pass through.

[0060] (D) Data logging unit The data logging unit includes a function to record the transmission and reception history of each message and save it as data so that it can be analyzed later.

[0061] (E) Synchronization Processing Unit The synchronization processing unit includes a function to synchronize the pre-transition control system and the post-transition control system, ensuring that both systems operate at the same time.

[0062] (F) Error Handling Section The error handling unit includes functions for detecting errors and performing recovery processing.

[0063] (G) Status Monitoring Unit The status monitoring unit includes a function to monitor the operating status of the pre-migration control system and the post-migration control system in real time and to respond if an abnormality is detected.

[0064] (H) Failover section The failover unit includes a function that automatically switches to the other system when either the pre-transition control system or the post-transition control system experiences a system failure.

[0065] (I) Access Control Unit The access control unit includes a function to authenticate users and ensure that only users with the appropriate permissions can perform operations.

[0066] (J) Notification Department The notification section includes a function to notify administrators when important events or errors occur.

[0067] (K) Settings management section The configuration management unit includes functions for managing various system settings and optimizing system operation.

[0068] (L) Interface section The interface section includes functions that provide interfaces for connecting to other systems and devices.

[0069] (M) Network Communications Department The network communication unit includes functions for sending and receiving messages between the pre-migration control system (main system) and the post-migration control system (main system).

[0070] <Message flow> Refer to Figure 5 to explain the message flow during migration / revert. Figure 5 shows an example of the message flow during the transition / revert process in Example 1. This example shows a case where control messages are sent to the pre-transition control system (main system) and the post-transition control system (main system), but the same applies to cases where messages are sent to other control systems. The following explains each step, S1 to S7.

[0071] (S1) A control message is sent to the system migration support device 10 via the control LAN 40.

[0072] (S2) The control message is duplicated by the system migration support device 10, and a first control message and a second control message are created.

[0073] (S3-1) The first control message is sent to the master-slave switching device (before transition) 50.

[0074] (S3-2) A second control message is sent to the master-slave switching device (after transition) 60.

[0075] (S4-1) The first control message is distributed and transmitted to the pre-transition control system (main system) 20 by the master-slave switching device (pre-transition) 50.

[0076] (S4-2) The second control message is distributed and transmitted to the post-transition control system (main system) 30 by the master-slave switching device (post-transition) 60.

[0077] (S5-1) The first control message is processed by the pre-migration control system (main system) 20 service, and the first response message is created.

[0078] (S5-2) The second control message is processed by the service of the post-transition control system (main system) 30, and a second response message is created.

[0079] (S6-1) The first response message is transmitted to the system transition support device 10 via the master-slave switching device (before transition) 50.

[0080] (S6-2) A second response message is sent to the system transition support device 10 via the master-slave switching device (after transition) 60.

[0081] (S7) The first response message and the second response message are compared and analyzed by the system migration support device 10. If there are no problems, only the first response message is allowed to pass through the control LAN, and the second response message is not allowed to pass through.

[0082] These messages are processed for all migrated services in the pre-migration control system (main system) 20, and after the migration is complete, the post-migration control system (main system) 30 will be operated as the main control system.

[0083] As a result, the system migration support device 10 can support a reliable and efficient migration between systems without stopping the current system.

[0084] <Processing for master-slave control systems> Referring to Figures 6 and 7, the processing when the system transition support device 10 of this embodiment is applied to a master-slave control system will be described. Figure 6 shows an example of the transition process for the master-slave control system of the system transition support device of Example 1. In this example, the response message from the pre-transition control system (master system) 20 is used as a reference, and the response messages are compared for the following four cases to make a decision on whether to proceed with the transition.

[0085] In comparison case 1, the response message from the pre-migration control system (main system) 20 and the response message from the post-migration control system (main system) 30 are compared. In this case, the response message from the pre-migration control system (main system) 20 is sent back to the controlled device via the control LAN 40, while the response message from the post-migration control system (main system) 30 is not sent back. By comparing and analyzing both response messages, it is confirmed whether the service satisfies operational policy 14 (described later).

[0086] In comparison case 2, the response message from the pre-migration control system (primary system) 20 and the response message from the pre-migration control system (secondary system) 21 are compared. In this case, the response message from the primary system is sent back to the controlled device via the control LAN 40, while the response message from the secondary system is not sent back. This is done to confirm the consistency between the primary and secondary systems in the pre-migration control system. This may be done when the secondary system is in a hot standby state.

[0087] In comparison case 3, the response message from the pre-transition control system (slave system) 21 and the response message from the post-transition control system (slave system) 31 are compared. In this case, no response messages from either slave system are sent back to the controlled device. This is done to confirm the consistency between the slave systems.

[0088] In comparison case 4, the response message from the post-transition control system (master system) 30 and the response message from the post-transition control system (slave system) 31 are compared. In this case, no response message is sent back to the controlled device from either the master system or the slave system. This is done to confirm the consistency between the master and slave systems in the post-transition control system.

[0089] Normally, if operational policy 14 (described later) is met for all of comparison cases 1 to 4, migration is considered possible. However, for some services, it is not necessary to meet all of comparison cases 1 to 4, and this criterion can also be defined in operational policy 14.

[0090] Figure 7 shows an example of the rollback process for the master-slave control system of the system migration support device in Example 1. In this example, the response message from the post-migration control system (master system) 30 is used as a reference, and the response messages are compared for the following four cases to determine whether to roll back.

[0091] In comparison case 5, the response message from the post-migration control system (main system) 30 and the response message from the pre-migration control system (main system) 20 are compared. In this case, the response message from the post-migration control system (main system) 30 is sent back to the controlled device via the control LAN 40, while the response message from the pre-migration control system (main system) is not sent back. By comparing and analyzing both response messages, it is confirmed whether the service satisfies operational policy 14 (described later).

[0092] In comparison case 6, the response message from the post-migration control system (primary system) 30 and the response message from the post-migration control system (secondary system) 31 are compared. In this case, the response message from the primary system is sent back to the controlled device via the control LAN 40, while the response message from the secondary system is not sent back. This is done to confirm the consistency between the primary and secondary systems in the post-migration control system. This may also be done when the secondary system is in a hot standby state.

[0093] In comparison case 7, the response message from the post-transition control system (slave system) 31 is compared with the response message from the pre-transition control system (slave system) 21. In this case, no response messages from either slave system are sent back to the controlled device. This is done to confirm the consistency between the slave systems.

[0094] In comparison case 8, the response message from the pre-transition control system (primary system) 20 and the response message from the pre-transition control system (secondary system) 21 are compared. In this case, no response message is sent back to the controlled device from either the primary or secondary system. This is done to confirm the consistency between the primary and secondary systems in the pre-transition control system.

[0095] Normally, if any one of comparison cases 5-8 does not meet operational policy 14 (described later), it is considered possible to roll back the project. However, depending on the service, it is not necessarily required that only one of comparison cases 5-8 is met, and this criterion can also be defined in operational policy 14.

[0096] <Comparison and Analysis of Response Messages> Next, with reference to Figure 8, a comparison and analysis of response messages in the system migration support device 10 of this embodiment will be described. Figure 8 shows an example of the means related to the message comparison unit of the system migration support device of Embodiment 1. As shown in Figure 8, the message comparison unit of the system migration support device 10 uses means such as a message comparison buffer 11, a message comparison and analysis unit 12, an analysis report 13, and an operation policy 14 to compare and analyze, for example, a response message from the pre-migration control system (first response message) and a response message from the post-migration control system (second response message). Each means will be described below.

[0097] (Message comparison buffer 11) The message comparison buffer 11 is a memory area configured for each service, and for example, it records on the fly control messages sent to the pre-migration control system (main system) 20 and the post-migration control system (main system) 30, as well as the first response message sent from the pre-migration control system (main system) 20 and the second response message sent from the post-migration control system (main system) 30. The information recorded by the message comparison buffer 11 includes the exact time each message was sent and received, and the content of each message.

[0098] (Message Comparison and Analysis Section 12) The message comparison and analysis unit 12 refers to the information recorded in the message comparison buffer 11, creates the analysis report 13 described below, and makes decisions on migration or rollback based on the operational policy 14.

[0099] (Analysis Report 13) Analysis Report 13 organizes the results of the Message Comparison and Analysis Unit 12 based on the specifications set for each service. Details of Analysis Report 13 will be described later.

[0100] (Operational Policy 14) The operational policy 14 in this embodiment defines the policies and criteria for migration / reverting, which are set for each service. The operational policy 14 may be provided outside the system migration support device 10. Details of the operational policy 14 will be described later.

[0101] Referring to Figure 9, the analysis report 13 for Example 1 will be described. Figure 9 shows an example of the analysis report for Example 1. As shown in Figure 9, the analysis report 13 has specifications for comparison items, targets, and analysis results. In this example, the first response message and the second response message are compared and analyzed using six comparison items: message content, message format, message arrival time, message ID, message arrival order, and message timestamp. Each comparison item will be explained below. As mentioned above, each response message may consist of multiple messages (a group of response messages), so the analysis results in this example are also the result of comparing multiple messages between the two response messages.

[0102] The message content is analyzed by comparing the degree of similarity between the message bodies of both response messages. A higher degree of similarity indicates that there will be no problems with the operation of the service after the migration. In this example, the analysis results show that the degree of similarity between the message bodies was 98%.

[0103] The message format is the subject of comparison and analysis, focusing on the degree of formatting agreement between the two response messages. Only when this agreement is 100% will the service function correctly after the migration. In this example, the analysis results show that the formatting agreement was 100%.

[0104] The message arrival time is calculated by comparing the arrival time difference between the two response messages. A smaller time difference indicates a higher degree of real-time performance after the transition. In this example, the analysis results show that the average arrival time difference was 5ms.

[0105] The message ID is used for comparison and analysis, specifically the number of matching message IDs between both response messages. A higher percentage of matches indicates that the message is being correctly recognized by the migrated service. In this example, the analysis results show that the match rate was 99%.

[0106] Message delivery order is the subject of comparison and analysis of the degree of agreement in the delivery order between both response messages. A higher degree of agreement indicates that the messages are being processed in the correct order in the migrated service. In this example, the analysis results show that the degree of agreement was 99%.

[0107] The message timestamping time is analyzed by comparing the time difference between the timestamps assigned to each response message. A smaller time difference indicates that the message was processed appropriately in the migrated service. In this example, the analysis results show that the time difference was within 50ms.

[0108] If the post-migration control system service is functioning correctly, the analysis results will typically show no difference between the two response messages in terms of comparison items such as message content, message format, message ID, and message arrival order. However, if the post-migration control system service is not exactly the same as the pre-migration control system service, for example, if it is an extension of the pre-migration control system service, the increase in response messages from the post-migration control system service may cause differences in message IDs between pre- and post-migration response messages, or discrepancies in message arrival times.

[0109] Various situations related to the migration, including whether to judge the analysis results as a service malfunction in the post-migration control system or as a result of service enhancements, will be handled flexibly according to Operation Policy 14 described below.

[0110] <Contents of the operational policy> Referring to Figures 10 and 11, the details of the operational policy 14 in Example 1 will be explained. The operational policy 14 in this example includes two types: operational policy (policy) 14-1, which defines the conditions and policies for migration / return, and operational policy (criteria) 14-2, which defines the criteria for migration / return.

[0111] Figure 10 shows an example of Operation Policy 14-1 for this embodiment. Operation Policy 14-1 is set for each service, but in this example it is shown in a list format for explanatory purposes. As shown in Figure 10, Operation Policy 14-1 specifies policies that enable safe and efficient migration and rollback. The following describes each policy included in Operation Policy 14-1.

[0112] The nighttime switching policy stipulates that migrations and rollbacks should be performed during nighttime hours (22:00 to 5:00) when the operational load is relatively low. This allows for low-load, low-risk migrations and rollbacks, minimizing the impact on normal operations. Migrations and rollbacks are performed automatically based on a time schedule.

[0113] The weekend switching policy stipulates that migration / reverting operations should be performed on weekends (Saturdays, Sundays, and public holidays) when the operational load differs from that of weekdays. This allows for verification of migration / reverting operations under different conditions than those of weekdays. Migration / reverting operations are performed automatically based on a time schedule.

[0114] The phased service migration policy stipulates that migration / reverting will be carried out gradually and sequentially during a predetermined migration period. This diversifies the risks of the migration and makes it easier to revert if problems occur. Migration / reverting will be carried out according to a pre-determined schedule.

[0115] The function-based switching policy stipulates that migration / reverting should be performed on a function-by-function basis. This allows for detailed verification of the operation of each function and identification of inter-service interactions. Migration / reverting is carried out according to a pre-determined schedule.

[0116] The artificial load testing policy stipulates that migration / reverting should be tested in advance under artificial load in a simulated environment. This allows for verification of operation under loads close to actual operating conditions. Migration / reverting is performed automatically through simulation.

[0117] The random switching test policy specifies that migrations and rollbacks will be performed randomly. This allows for verification of operation under actual operational conditions and allows for testing of unexpected problems. Migrations and rollbacks are performed automatically in real time.

[0118] A regionally limited transition policy stipulates that migration / reverting procedures are limited to specific regions or departments. This allows for verification within a limited scope, minimizing risk. Migration / reverting is performed automatically on a regional / departmental basis, selecting the relevant regions and services.

[0119] The pre-migration testing policy stipulates that the new system be tested by a limited number of users before the full migration. By obtaining feedback from users, it is possible to predict problems related to the new system.

[0120] The network load comparison policy defines migration / revert in relation to a network load threshold. This allows for operational verification based on actual load, minimizing risks due to load fluctuations. For example, migration is performed automatically when the network load exceeds the threshold.

[0121] The response delay time comparison policy defines migration / revert in relation to a response delay time threshold. Because it allows for responses based on fluctuations in response delay, it helps maintain overall system performance. For example, migration is performed automatically when the response delay time exceeds the threshold.

[0122] As a result, the system migration support device of this embodiment enables the safe and efficient migration of the control system and allows for rapid rollback as needed.

[0123] Next, Figure 11 shows an example of the operational policy (criteria) 14-2 for Example 1. The operational policy (criteria) 14-2 determines the analysis results for each comparison item in the analysis report 13. As shown in Figure 11, the operational policy (criteria) 14-2 sets a target and judgment criteria for each comparison item.

[0124] The evaluation criteria may include those that directly assess the analysis results, such as the message format, those that evaluate based on the average value of the analysis results, such as the message content, and those that evaluate based on the worst-case value of the analysis results, such as the message arrival time. Furthermore, a comprehensive provision may be included to determine the final decision on whether or not to proceed with the transition based on the pass / fail status of each comparison item.

[0125] Taking item 1 of operational policy (standard) 14-2 as an example, this is the item that determines the message content among the comparison items. If the analysis result "98%" in analysis report 13 in Figure 9 is evaluated using the judgment criterion "Pass if average 95% / hour or more", it will be judged as "Pass". In this example, the final decision on the migration of the relevant service is made according to item 7, which is the provision for overall judgment, based on the results of judgments made in items 1 to 6 of operational policy (standard) 14-2 for each comparison item in analysis report 13.

[0126] Regarding remands, the reverse is also true; if any one of items 1 through 6 is not passed, it may be decided to remand the work. Alternatively, separate provisions may be established for the overall judgment regarding remands.

[0127] (Example 2) Generally, when migrating a control system, it is necessary to consider whether the resources of the new system after the migration are sufficient or insufficient. Even if the decision to migrate is negative, if this is due to a lack of resources rather than a malfunction in the service itself, it is desirable to address the issue by increasing resources without changing the service itself. On the other hand, if the resources of the new system are excessive for the services after the migration, even if there are no problems with the operation of the new system, it cannot be said that the migration is without problems in terms of over-specification.

[0128] To address these issues, operational policy 14 can also be used to increase or decrease the resources of the post-migration control system.

[0129] Referring to Figure 12, the resource enhancement / reduction of the post-migration control system by the system migration support device of Example 2 will be described. Figure 12 shows an example of operational policy (enhancement) 14-3 and operational policy (reduction) 14-4 of Example 2. The system migration support device of this example uses operational policy (enhancement) 14-3 shown in Figure 12(a) or operational policy (reduction) 14-4 shown in Figure 12(b), in addition to or instead of operational policy (guideline) 14-1 and operational policy (criteria) 14-2 of Example 1.

[0130] The following describes the flow of resource enhancement, using the network load comparison policy from Operation Policy (Enhancement) 14-3 as an example. In this example, when migrating the services of the pre-migration control system to the services of the post-migration control system, if the network load exceeds a threshold, an attempt will be made to enhance resources. The enhancement process will be carried out in the following order and will continue until an effect is achieved, at which point it will terminate.

[0131] (1. Perform vertical scaling) The CPU or memory will be doubled to enhance the service's processing power. If the network load falls below the threshold after the increase, the enhancement process will end; otherwise, the process will proceed to the next step if the network load still exceeds the threshold.

[0132] (2. Replacing the storage device) The system will be upgraded by replacing the HDD with an SSD or an NVMe (Non-Volatile Memory Express) SSD to improve I / O performance. If the network load falls below the threshold as a result of the upgrade, the process will end; otherwise, it will proceed to the next step.

[0133] (3. Introduction of caching) Caching is implemented for frequently used data to reduce access times. If the network load falls below a threshold as a result of the implementation, the enhancement process will end; if the network load still exceeds the threshold, the process will proceed to the next step.

[0134] (4. Increasing network bandwidth) The bandwidth is doubled to improve latency. If the network load falls below the threshold after the increase, the enhancement process ends; if the network load still exceeds the threshold, the process proceeds to the next step.

[0135] (5. Optimizing Storage and Memory) The system optimizes disk I / O by improving cache and memory efficiency. If the network load falls below a threshold as a result of these improvements, the upgrade process will terminate. If the network load still exceeds the threshold, the migration of the service will be stopped or rolled back.

[0136] These enhancement processes 1-5 can be executed automatically, or they can be proposed to the system administrator. The above explanation of augmentation processing used a network load comparison policy as an example, but augmentation flows can also be prepared and implemented appropriately using a response delay time comparison policy.

[0137] Next, we will explain the resource reduction flow using the response delay time comparison policy from Operation Policy (Reduction) 14-4 in Figure 12(b) as an example. When migrating the services of the pre-migration control system to the services of the post-migration control system, if the response delay time does not exceed the threshold, an attempt is made to reduce resources. The reduction process is carried out in the following order and continues until an abnormality is detected, at which point it is returned to the previous point and terminated.

[0138] (1. Reduction of network bandwidth) Reduce the bandwidth by half. If the response delay time exceeds the threshold as a result of the reduction, revert to the original value and terminate the reduction process. If the response delay time remains below the threshold, proceed to the next step.

[0139] (2. Stopping the introduction of caching) Switch from caching enabled to disabled. If the response delay time exceeds the threshold as a result of the switch, revert to the previous setting and end the reduction process. If the response delay time remains below the threshold, proceed to the next step.

[0140] (3. Replacing the storage device) Replace an NVMe (Non-Volatile Memory Express) SSD with another SSD or HDD. If the response delay time exceeds the threshold after the replacement, revert to the original drive and the reduction process ends. If the response delay time remains below the threshold, proceed to the next step.

[0141] (4. Implementing vertical scaling) Either reduce the CPU processing performance by half or reduce the amount of memory by half. If the response delay time exceeds a threshold as a result of the reduction, revert to the original settings and terminate the reduction process. If the response delay time remains below the threshold, terminate the reduction process there.

[0142] These reduction processes 1-4 can be executed automatically, or they can be proposed to the system administrator. The above explanation of reduction processing used the response delay time comparison policy as an example, but reduction can also be performed using a network load comparison policy by preparing an appropriate reduction flow.

[0143] This makes it possible to continue the migration without changing the service entity and to avoid over-specifying the post-migration control system.

[0144] (Example 3) When migrating a control system, it is necessary to verify that the system after the migration will always operate properly. As shown in Example 1, the operation of the service is usually monitored based on the operational policy 14 for a predetermined period after the migration to confirm that no problems occur. However, it is also necessary to verify in advance that the post-migration control system will operate properly even in the event of events that are not likely to occur within the predetermined period (e.g., accidents or failures).

[0145] The control LAN simulator 41 in this embodiment simulates various anticipated situations, including these events, and generates virtual control messages, thereby making the migration support provided by the system migration support device safer and more reliable.

[0146] Referring to Figure 13, the system migration support device of Example 3 will be described. Figure 13 shows an example of a control LAN simulator to which the system migration support device of Embodiment 3 is connected. As shown in Figure 13, the system migration support device 10 of this embodiment differs from the system migration support device 10 of Embodiment 1 in that it is connected to the control LAN simulator 41. Hereafter, the same reference numerals are used for the components described in Embodiment 1, and their descriptions will be omitted. The explanation will focus on the relationship with the control LAN simulator 41.

[0147] The control LAN simulator 41 includes virtual control target devices, such as a virtual video device, a virtual signaling device, and a virtual operation management device. It transmits virtual scenarios (e.g., accident scenarios) to these virtual control target devices and generates virtual control messages. Next, each of these devices will be described.

[0148] The virtual video device is a virtual device for real-time monitoring in the control system and simulates virtual video data (such as virtual accident footage). The control LAN simulator 41 sends virtual control messages corresponding to the virtual video data to the system transition support device 10. The virtual video device may be implemented as software.

[0149] The virtual signaling device is a virtual device for managing signal data in the control system and simulates virtual signals (e.g., virtual traffic signals or fault signals). The control LAN simulator 41 transmits virtual control messages corresponding to the virtual signals to the system transition support device 10. The virtual signaling device may also be implemented as software.

[0150] The virtual operation management device is a virtual device for operation management in the control system, and it simulates virtual operation conditions (such as virtual accident situations). The control LAN simulator 41 sends virtual control messages corresponding to the virtual operation conditions to the system transition support device 10. The virtual operation management device may also be implemented as software.

[0151] The processing of the system migration support device 10 will now be described. The system migration support device 10 uses the control LAN simulator 41 to evaluate the operation of the post-migration control system, for example, in the following procedure.

[0152] (1. Sending and receiving virtual control messages) The system migration support device 10 receives virtual control messages corresponding to the virtual scenario from the control LAN simulator 41, duplicates them, and transmits them to the pre-migration control system and the post-migration control system.

[0153] (2. Analysis of Simulation Results) The system migration support device 10 receives response messages to virtual control messages from the pre-migration control system and the post-migration control system, respectively, and compares and analyzes both response messages.

[0154] (3. Evaluation of Simulation Results) The system migration support device 10 evaluates whether there are any problems with the operation of the post-migration control system based on the analysis results. If problems are found, the system configuration and settings are reviewed. Such evaluations and reviews may be specified in the operational policy 14.

[0155] As a result, the system migration support device 10 of this embodiment can consider countermeasures in advance for accidents and failures that may occur in the post-migration control system, thereby ensuring the stability and reliability of the post-migration control system.

[0156] <Variation> Although embodiments of the present invention have been described above, the present invention is not limited to the embodiments described above, and various modifications are possible without departing from the spirit of the present invention.

[0157] For example, in this embodiment, the target of the migration support is a control system for the integrated management of mobile objects, but it is not limited to this, and it is possible to support the migration of various control systems.

[0158] Referring to Figure 14, we will now explain the case where the system migration support device targets both the old and new system migration support devices. Figure 14 shows an example of a connection configuration when migrating from a pre-migration system migration support device to a post-migration system migration support device using a system migration support device.

[0159] To verify the operation of the system migration support device (pre-migration) 10-1 and the system migration support device (post-migration) 10-2, a hub 70 with port mirroring functionality and a system migration support device (for verification) 10-3 are used. As shown in Figure 14, the four systems, the pre-migration control system (main system) 20 and (subordinate system) 21 and the post-migration control system (main system) 30 and (subordinate system) 31, are connected to the system migration support device (pre-migration) 10-1 and also to the system migration support device (post-migration) 10-2 via the hub 70.

[0160] System migration support device (pre-migration) 10-1 and system migration support device (post-migration) 10-2 operate under the same operational policy while maintaining time synchronization, and are expected to behave identically. In other words, if both devices behave identically, they will send the same message to system migration support device (verification) 10-3.

[0161] The system migration support device (for verification) 10-3 compares these messages to verify whether the system migration support device (before migration) 10-1 and the system migration support device (after migration) 10-2 are behaving the same way. This allows for a determination of whether the migration of the system migration support device is appropriate or whether it should be reverted to the state before the migration.

[0162] In addition, while this embodiment uses operational policies for migration / reverting, it is not limited to this. When the control system's services are simple, for example, it is also possible to determine migration / reverting by simply comparing response messages as needed.

[0163] Furthermore, while this embodiment demonstrates an example of reducing the resources of the post-migration control system through operational policies, it is also possible to reflect the excessive resource specifications of the post-migration control system in the migration priority.

[0164] The above describes some variations, but the present invention also includes the following embodiments.

[0165] (Aspect 1) In a system migration support device that assists in the transition from the first system to the second system, A message communication unit that receives and duplicates control messages, A network communication unit transmits the replicated control message to the first service of the first system and the second service of the second system corresponding to the first service, and receives a first response message from the first service and a second response message from the second service in response to the control message. The system includes a message comparison unit that compares and analyzes the first response message and the second response message to determine whether to migrate the first service of the first system to the second service of the second system, or whether to return the second service of the second system to the first service of the first system. A system migration support device characterized by the following features.

[0166] (Aspect 2) A system migration support device according to Embodiment 1, The message comparison unit performs the transition process or the rollback process based on the policy specified in the operational policy. A system migration support device characterized by the following features.

[0167] (Aspect 3) A system migration support device according to embodiment 1 or 2, The message comparison unit makes a decision on whether to proceed with the transition or whether to roll back the message based on the criteria specified in the operational policy. A system migration support device characterized by the following features.

[0168] (Aspect 4) A system transition support device according to embodiment 2 or 3, The message comparison unit further performs processing to enhance or reduce the second system based on the conditions specified in the operational policy. A system migration support device characterized by the following features.

[0169] (Appendix 5) A system migration support device according to Embodiment 4, The message comparison unit either outputs the contents of the enhancement or reduction process to the display, or automatically executes the process. A system migration support device characterized by the following features.

[0170] (Aspect 6) A system migration support device according to any one of embodiments 1 to 5, The message communication unit receives control messages from the controlled device via the control LAN, duplicates them, and sends back only one of the first response message and the second response message to the controlled device via the control LAN. A system migration support device characterized by the following features.

[0171] (Aspect 7) A system migration support device according to any one of embodiments 1 to 6, The message communication unit receives a control message from a control LAN simulator that simulates the controlled device, duplicates it, and sends back only one of the first response message and the second response message to the control LAN simulator. A system migration support device characterized by the following features.

[0172] (Pattern 8) In a system migration support method that assists in the transition from the first system to the second system, The message communication unit receives and duplicates the control message. The network communication unit transmits the replicated control message to the first service of the first system and the second service of the second system corresponding to the first service, and receives a first response message from the first service and a second response message from the second service in response to the control message. The message comparison unit compares and analyzes the first response message and the second response message to determine whether to migrate the first service of the first system to the second service of the second system, or whether to revert the second service of the second system back to the first service of the first system. A system migration support method characterized by the following features.

[0173] (Aspect 9) A system migration support method described in aspect 9, The message comparison unit performs the migration process or the rollback process based on the policy specified in the operational policy. A system migration support method characterized by the following features.

[0174] (Aspect 10) A system migration support method according to aspect 8 or 9, The message comparison unit makes a decision on whether to proceed with the migration or whether to roll back the changes, based on the criteria specified in the operational policy. A system migration support method characterized by the following features.

[0175] (Aspect 11) A system migration support method according to aspect 9 or 10, The message comparison unit then performs further processing to enhance or reduce the second system based on the conditions specified in the operational policy. A system migration support method characterized by the following features.

[0176] (Aspect 12) A system migration support method described in Embodiment 11, The message comparison unit either outputs the details of the enhancement or reduction process to the display or automatically executes the process. A system migration support method characterized by the following features.

[0177] (Aspect 13) A system migration support method according to any one of claims 8 to 12, The message communication unit receives control messages from the controlled device via the control LAN, duplicates them, and sends back only one of the first response message and the second response message to the controlled device via the control LAN. A system migration support method characterized by the following features.

[0178] (Aspect 14) A system migration support method described in any of the embodiments 8 to 13, The message communication unit receives control messages from a control LAN simulator that simulates the controlled device, duplicates them, and sends back only one of the first response message and the second response message to the control LAN simulator. A system migration support method characterized by the following features. [Explanation of Symbols]

[0179] 1 Input / Output Controller, 2 CPU, 3 HDD, 4 Monitor Controller, 5 Memory, 6 Network Interface, 7 Display, 10 System Migration Support Device, 10-1 System Migration Support Device (Pre-migration), 10-2 System Migration Support Device (Post-migration), 10-3 System Migration Support Device (Verification), 11 Message Comparison Buffer, 12 Message Comparison / Analysis Unit, 13 Analysis Report, 14 Operational Policy, 14-1 Operational Policy (Guidelines), 14-2 Operational Policy (Standards), 14-3 Operational Policy (Enhancement), 14-4 Operational Policy (Reduction), 20 Pre-migration Control System (Primary), 21 Pre-migration Control System (Secondary), 30 Post-migration Control System (Primary), 31 Post-migration Control System (Secondary), 40 Control LAN, 41 Control LAN Simulator, 50 Master / Slave Switching Device (Pre-migration), 60 Master / Slave Switching Device (Post-migration), 70 Hub

Claims

1. In a system migration support device that assists in the transition from the first system to the second system, A message communication unit that receives and duplicates control messages, A network communication unit transmits the replicated control message to the first service of the first system and the second service of the second system corresponding to the first service, and receives a first response message from the first service and a second response message from the second service in response to the control message. The system includes a message comparison unit that compares and analyzes the first response message and the second response message to determine whether to migrate the first service of the first system to the second service of the second system, or whether to return the second service of the second system to the first service of the first system. A system migration support device characterized by the following features.

2. A system migration support device according to claim 1, The message comparison unit performs the transition process or the rollback process based on the policy specified in the operational policy. A system migration support device characterized by the following features.

3. A system migration support device according to claim 1, The message comparison unit makes a decision on whether to proceed with the transition or whether to roll back the message based on the criteria specified in the operational policy. A system migration support device characterized by the following features.

4. A system migration support device according to claim 2 or 3, The message comparison unit further performs processing to enhance or reduce the second system based on the conditions specified in the operational policy. A system migration support device characterized by the following features.

5. A system migration support device according to claim 4, The message comparison unit either outputs the contents of the enhancement or reduction process to the display, or automatically executes the process. A system migration support device characterized by the following features.

6. A system migration support device according to claim 1, The message communication unit receives control messages from the controlled device via the control LAN, duplicates them, and sends back only one of the first response message and the second response message to the controlled device via the control LAN. A system migration support device characterized by the following features.

7. A system migration support device according to claim 1, The message communication unit receives a control message from a control LAN simulator that simulates the controlled device, duplicates it, and sends back only one of the first response message and the second response message to the control LAN simulator. A system migration support device characterized by the following features.

8. In a system migration support method that assists in the transition from the first system to the second system, The message communication unit receives and duplicates the control message. The network communication unit transmits the replicated control message to the first service of the first system and the second service of the second system corresponding to the first service, and receives a first response message from the first service and a second response message from the second service in response to the control message. The message comparison unit compares and analyzes the first response message and the second response message to determine whether to migrate the first service of the first system to the second service of the second system, or whether to revert the second service of the second system back to the first service of the first system. A system migration support method characterized by the following features.

9. A system migration support method according to claim 8, The message comparison unit performs the migration process or the rollback process based on the operational policy. A system migration support method characterized by the following features.

10. A system migration support method according to claim 8, The message comparison unit makes a decision on whether to proceed with the migration or whether to roll back the changes, based on the criteria specified in the operational policy. A system migration support method characterized by the following features.

11. A system migration support method according to claim 9 or 10, The message comparison unit then performs further processing to enhance or reduce the second system based on the conditions specified in the operational policy. A system migration support method characterized by the following features.

12. A system migration support method according to claim 11, The message comparison unit causes the contents of the enhancement or reduction process to be output to the display, or causes the process to be executed automatically. A system migration support method characterized by the following features.

13. A system migration support method according to claim 8, The message communication unit receives control messages from the controlled device via the control LAN, duplicates them, and sends back only one of the first response message and the second response message to the controlled device via the control LAN. A system migration support method characterized by the following features.

14. A system migration support method according to claim 8, The message communication unit receives control messages from a control LAN simulator that simulates the controlled device, duplicates them, and sends back only one of the first response message and the second response message to the control LAN simulator. A system migration support method characterized by the following features.

Images