WO2022172331A1 - 設定変更装置、設定変更方法及びプログラム - Google Patents
設定変更装置、設定変更方法及びプログラム Download PDFInfo
- Publication number
- WO2022172331A1 WO2022172331A1 PCT/JP2021/004785 JP2021004785W WO2022172331A1 WO 2022172331 A1 WO2022172331 A1 WO 2022172331A1 JP 2021004785 W JP2021004785 W JP 2021004785W WO 2022172331 A1 WO2022172331 A1 WO 2022172331A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- setting change
- update
- software
- unit
- network device
- Prior art date
Links
- 230000008859 change Effects 0.000 title claims abstract description 68
- 238000000034 method Methods 0.000 title claims abstract description 28
- 230000008569 process Effects 0.000 claims abstract description 10
- 238000012545 processing Methods 0.000 description 24
- 238000012423 maintenance Methods 0.000 description 23
- 238000010586 diagram Methods 0.000 description 22
- 230000004044 response Effects 0.000 description 12
- 238000004891 communication Methods 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 6
- 230000000694 effects Effects 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
Definitions
- the present invention relates to a setting change device, a setting change method, and a program.
- network devices When updating software programs (hereinafter simply referred to as “software”) for routers, switches, etc. (hereinafter referred to as “network devices”), user communication may be interrupted due to software changes and restarts of the network devices themselves. be.
- the settings from the orchestrator cannot be input to the network device whose software is being updated, and the setting process according to the SO is not completed. As a result, the settings are input to only one of the network devices in the redundant configuration, and a state inconsistency occurs in the 0/1 system.
- the present invention has been made in view of the above points, and it is an object of the present invention to avoid the occurrence of inconsistencies between network devices when changing settings during software update for a group of network devices having a redundant configuration.
- a setting change device includes a determination unit that determines whether or not software for a plurality of network devices is being updated when an instruction to change settings for a plurality of network devices related to a redundant configuration is input. and a setting change unit that, if any of the network devices is updating the software, waits until the software update of the network device is completed, and executes the setting change for the network device. have.
- FIG. 1 is a diagram illustrating a configuration example of a communication system according to a first embodiment
- FIG. 2 is a diagram showing a hardware configuration example of a user portal 10 according to the first embodiment
- FIG. 2 is a diagram illustrating functional configuration examples of a maintenance console 20, a user portal 10, and an orchestrator 30 according to the first embodiment
- FIG. 10 is a sequence diagram for explaining an example of a processing procedure of software update processing according to the first embodiment
- FIG. 4 is a sequence diagram for explaining an example of a processing procedure executed according to SO in the first embodiment
- FIG. 10 is a diagram showing functional configuration examples of a maintenance console 20, a user portal 10, and an orchestrator 30 according to a second embodiment
- FIG. 12 is a sequence diagram for explaining an example of a processing procedure of software update processing according to the second embodiment
- FIG. 11 is a sequence diagram for explaining an example of a processing procedure executed according to SO in the second embodiment
- FIG. 11 is a diagram showing an example of functional configurations of a maintenance console 20, a user portal 10, and an orchestrator 30 according to a third embodiment
- FIG. 14 is a sequence diagram for explaining an example of a processing procedure of software update processing according to the third embodiment
- FIG. 14 is a sequence diagram for explaining an example of a processing procedure executed according to SO in the third embodiment
- FIG. 1 is a diagram showing a configuration example of a communication system according to the first embodiment.
- the communication system includes a user portal 10, a maintenance console 20, an orchestrator 30, multiple GWs (gateways) 40, one or more UEs (User Equipment) 50, and the like.
- the orchestrator 30 can communicate with the user portal 10 and each GW 40 .
- the UE 50 is a device that transmits and receives packet communications, and is used by users of services provided by the communication system (hereinafter simply referred to as "services").
- services For example, a PC, a smart phone, an IoT (Internet of Things) device, etc. are examples of the UE 50 .
- the arrow starting from the UE 50 indicates an example of the path of packets sent from the UE 50 .
- a person who uses the service via the UE 50 is called a "user". Note that one user may have multiple UEs 50 .
- the GW 40 is a general device that processes packets flowing on the network, and is an example of network equipment in this embodiment. Traffic of one or more UEs 50 passes through one or more GWs 40 or pairs of GWs 40 (pairs of redundant GWs 40) in multiple stages.
- EPC S-GW40, P-GW40, etc.
- 5GC UPF, etc.
- base stations eNodeB, gNodeB, etc.
- general network equipment such as routers and switches (L2/L3 transfer, firewall, VPN connection equipment, DPI, proxy, etc.) is an example of the GW 40 .
- the GW 40 may be a physical device or a virtual device.
- the GW 40 may have a single configuration like the GW 40a, but preferably has a redundant configuration (for example, 0 system 1 system and 1 set of redundant pairs) like the GW 40b and GW 40c. Redundant configurations are not limited to configurations such as 2N, N+1, and N+M. Also, the combination of states such as Active and Standby is not limited.
- the user portal 10 accepts SO (Service order) input from service users remotely (via a network) via a GUI (Graphical User Interface) (web page, etc.) or a CLI (Command Line Interface).
- SO Service order
- GUI Graphic User Interface
- CLI Common Line Interface
- SO means order information related to service subscription or change.
- the SO serves as a trigger for changing the settings of the GW 40 . Therefore, SO substantially corresponds to an instruction to change the setting of GW 40 .
- a service user is a person who is in a position to input SO on the user side of the service. etc.
- the service user is the system department of the company
- the UE 50 is the company smartphone of each employee (each user)
- the system department uses the company smartphone as the user portal 10. It is assumed that it will be collectively managed from
- the user portal 10 inputs (transmits) the received SO to the orchestrator 30 .
- the maintenance console 20 is a device that functions as a functional unit that receives an update instruction input for the software program of the GW 40 (hereinafter simply referred to as "software") from the system maintenance person and transmits the update instruction to the orchestrator 30.
- a user interface (GUI, etc.) for accepting input of an update instruction may be provided as a web page, or may be realized by a dedicated program installed on the console.
- a system maintenance person is a person who performs operations (input of update instructions, etc.) for updating the software of the GW 40.
- an update instruction is input via the maintenance console 20 is shown, but an update instruction from the system maintenance person may be input via the orchestrator 30, or sent to the GW 40. may be input directly to
- the orchestrator 30 inputs settings (changes settings) to a device (GW 40) that requires a setting change according to the SO from the user portal 10, and according to an update instruction from the maintenance console 20, the GW 40 A computer that functions as a functional unit that controls software update of the GW 40 and includes a device (Openflow Controller, etc.) that can operate the GW 40 .
- the orchestrator 30 may be able to control (change or update settings) the GW 40 via the rest-API.
- other APIs may be used as long as they are APIs (Application Program Interfaces) that can control the GW 40 .
- the orchestrator 30 may be realized using the same computer as the user portal 10, or the GW 40 may also function as the orchestrator 30.
- FIG. 2 is a diagram showing a hardware configuration example of the user portal 10 according to the embodiment of the present invention.
- the user portal 10 of FIG. 2 has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, and the like, which are connected to each other via a bus B, respectively.
- a program that implements processing in the user portal 10 is provided by a recording medium 101 such as a CD-ROM.
- a recording medium 101 such as a CD-ROM.
- the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100 .
- the program does not necessarily need to be installed from the recording medium 101, and may be downloaded from another computer via the network.
- the auxiliary storage device 102 stores installed programs, as well as necessary files and data.
- the memory device 103 reads and stores the program from the auxiliary storage device 102 when a program activation instruction is received.
- the CPU 104 executes functions related to the user portal 10 according to programs stored in the memory device 103 .
- the interface device 105 is used as an interface for connecting to a network.
- the orchestrator 30, maintenance console 20 and GW 40 may also have the hardware configuration shown in FIG.
- FIG. 3 is a diagram showing a functional configuration example of the maintenance console 20, user portal 10, and orchestrator 30 in the first embodiment.
- the maintenance console 20 has an update instruction receiving section 21 .
- the update instruction receiving unit 21 is implemented by a process that causes the CPU of the maintenance console 20 to execute one or more programs installed in the maintenance console 20 .
- the user portal 10 has an order reception unit 11, a determination unit 12, and an order transmission unit 13. Each of these units is implemented by one or more programs installed in the console that cause the CPU 104 to execute. User portal 10 also utilizes update information storage unit 121 .
- the update information storage unit 121 can be implemented using, for example, the auxiliary storage device 102 or a storage device that can be connected to the console via a network.
- the orchestrator 30 has an update control unit 31 , an order reception unit 32 and a setting change unit 33 . These units are implemented by one or more programs installed in the orchestrator 30 causing the CPU of the orchestrator 30 to execute.
- the orchestrator 30 also uses the customer information storage unit 321 .
- the customer information storage unit 321 can be implemented using, for example, an auxiliary storage device that the orchestrator 30 has, or a storage device that can be connected to the orchestrator 30 via a network.
- FIG. 4 is a sequence diagram for explaining an example of the processing procedure of software update processing according to the first embodiment.
- step S110 the update instruction receiving unit 21 of the maintenance console 20 receives a software update instruction from the system maintenance person.
- the update instruction includes information (hereinafter referred to as "GW information") indicating the GW 40 to be updated (hereinafter referred to as "target GW 40").
- GW information information
- target GW 40 information
- the update instruction receiving unit 21 transmits the update instruction to the orchestrator 30 (S120).
- the update control unit 31 of the orchestrator 30 Upon receiving the update instruction, the update control unit 31 of the orchestrator 30 acquires the user information (user ID) of the user accommodated in the target GW 40 (hereinafter referred to as "target user") from the customer information storage unit 321. (S130, S140). That is, the customer information storage unit 321 stores information indicating in which GW 40 each user is accommodated (correspondence information between the user ID and the ID of the GW 40). Therefore, the update control section 31 acquires the user information corresponding to the GW information included in the update instruction from the customer information storage section 321 .
- the update control unit 31 stores update information (user ID, status) indicating that the status of the GW 40 accommodating the target user is that the software is being updated, in association with the user ID of the target user. Recorded in the unit 121 (S150).
- the status is information indicating the update status of software for the GW 40, and its value is "updating” or "update completed”. In step S150, "updating" is recorded as the status.
- the update control unit 31 executes software update control for the target GW 40 (here, the pair of GW 40b and GW 40c).
- the target GW 40 here, the pair of GW 40b and GW 40c.
- the update control unit 31 first starts updating the software from the standby GW 40c (S160).
- the update control unit 31 executes a redundancy switching operation to switch the working system and the standby system (S180, S190). That is, the GW 40b becomes the standby system, and the GW 40c becomes the active system. As a result, user traffic comes to flow to GW40c.
- the update control unit 31 starts controlling software update for the GW 40b that has newly become a standby system (S200).
- the update control unit 31 performs the redundancy switching operation again to return the GW 40b to the active system, and the GW 40c. Return to the standby system (S220, S230).
- the redundancy switching operation is not essential, and the operation may be continued with the GW 40b as the standby system and the GW 40c as the active system. This point is the same for the second and third embodiments.
- the update control unit 31 records update information indicating that the update regarding the target user has been completed in the update information storage unit 121 (S240). That is, the update control unit 31 updates the status associated with the user ID of the target user and stored in the update information storage unit 121 to "update completed". Such a status update corresponds to deletion of information indicating that the target user is being updated.
- the update control unit 31 transmits a response indicating completion of the update to the update instruction reception unit 21 of the maintenance console 20 (S250). Upon receiving the response, the update instruction receiving unit 21 notifies the system maintenance person of the completion of the update (S260).
- FIG. 5 is a sequence diagram for explaining an example of a processing procedure executed according to SO in the first embodiment.
- the order reception unit 11 of the user portal 10 receives an SO input from the service user.
- SO includes the user ID of the user to be changed regarding the service (hereinafter referred to as "target user").
- the determination unit 12 refers to the update information storage unit 121 and determines whether or not the GW 40 accommodating the target user is updating software (S502, S503). That is, if the update information storage unit 121 stores a status indicating "updating" in association with the user ID of the target user, the determination unit 12 determines that the target user is being updated.
- steps S511 to S517 are executed.
- step S ⁇ b>511 the order transmission unit 13 transmits the input SO to the orchestrator 30 .
- the setting change unit 33 sends the SO to the GW 40 (here, the pair of GW 40b and GW 40c) corresponding to the user ID included in the SO. By inputting the corresponding settings, the settings of these GW 40 are changed (S512 to S515). Note that the GW 40 corresponding to the user ID included in the SO can be specified by referring to the customer information storage unit 321.
- FIG. When setting changes are completed for all applicable GWs 40, the setting change unit 33 transmits a response indicating completion of setting changes to the user portal 10 (S516). Upon receiving the response, the order transmission unit 13 of the user portal 10 notifies the service user of the completion of the setting change according to the SO (S517).
- steps S521 to S529 are executed.
- step S521 the determination unit 12 notifies the service user that the setting change according to the SO has been completed, or that "it will take time to reflect because maintenance is in progress". Subsequently, the order transmission unit 13 waits for completion of the update regarding the target user by repeatedly referring to the update information storage unit 121 (for example, at regular time intervals) (S522, S523). When the status for the target user changes to "update completed", the order sending unit 13 detects completion of the update. When the order sending unit 13 detects the completion of the update, the same processes as steps S511 to S516 are executed in steps S524 to S529.
- FIG. 6 is a diagram showing a functional configuration example of the maintenance console 20, user portal 10, and orchestrator 30 in the second embodiment.
- the same parts as those in FIG. 3 are denoted by the same reference numerals, and the description thereof will be omitted.
- the user portal 10 does not have the determination unit 12.
- the user portal 10 also does not use the update information storage unit 121 .
- the orchestrator 30 further has a determination unit 34.
- the determination unit 34 is implemented by a process that causes the CPU of the orchestrator 30 to execute one or more programs installed in the orchestrator 30 .
- the orchestrator 30 also uses the update information storage unit 322 .
- the update information storage unit 322 can be implemented using, for example, an auxiliary storage device that the orchestrator 30 has, or a storage device that can be connected to the orchestrator 30 via a network.
- FIG. 7 is a sequence diagram for explaining an example of the processing procedure of software update processing according to the second embodiment.
- the same step numbers as in FIG. 4 are given to the same steps, and the description thereof is omitted.
- step S150 is replaced with step S150a. Further, steps S191 and S192 are executed between steps S190 and S200. Further, step S240 is replaced with step S240a.
- step S150a the update control unit 31 records in the update information storage unit 322 the ID of the backup GW 40 (here, the GW 40c) among the target GW 40 and the status of the software update for that GW 40 in association with each other.
- step S150a "updating" is recorded as the status.
- the update information storage unit 121 in the first embodiment stores the status for each user (per user), but the update information storage unit 322 in the second embodiment stores the status for each GW 40 (GW 40 unit) is stored. Therefore, in the second embodiment, status management for each GW 40 is possible.
- the update control unit 31 changes the status of the GW 40c to "update completed".
- update information indicating that the status of the GW 40b is "updating” is recorded in the update information storage unit 322 (S192). That is, the information indicating that the software is being updated for the GW 40c is deleted, and the information indicating that the software is being updated for the GW 40b is recorded.
- the update control unit 31 changes the status of the GW 40b to "update completed" ( S240a). That is, the information indicating that the software of the GW 40b is being updated is deleted.
- FIG. 8 is a sequence diagram for explaining an example of a processing procedure executed according to SO in the second embodiment. 8, the same steps as in FIG. 5 are given the same step numbers, and the description thereof will be omitted as appropriate.
- the order transmission unit 13 transmits the SO to the orchestrator 30 (S511).
- the determination unit 34 refers to the update information storage unit 322, and each GW 40 accommodating the target user (hereinafter referred to as "target GW 40") It is determined whether or not updating is in progress (S601, S602). Each target GW 40 can be identified by referring to the customer information storage unit 321 . That is, the determination unit 34 determines that the target GW 40 whose ID is stored in the update information storage unit 322 in association with the status indicating "updating" is being updated.
- steps S512 to S517 are executed.
- steps S611 to S618 are executed.
- the backup GW 40c is being updated and the active GW 40b is not being updated.
- the setting of the GW 40b which is not being updated, is changed, and the setting of the GW 40c is changed after the update is completed.
- the setting change unit 33 first changes the setting of the GW 40b (S611, S612). Subsequently, processing similar to steps S516 and S517 is executed (S613, S614).
- the setting change unit 33 waits for completion of the update regarding the GW 40c by repeatedly referring to the update information storage unit 322 (for example, at regular time intervals) (S615, S616).
- the setting change unit 33 detects completion of the update.
- the setting change unit 33 changes the setting of the GW 40c (S617, S618).
- FIG. 9 is a diagram showing a functional configuration example of the maintenance console 20, user portal 10, and orchestrator 30 in the third embodiment.
- the same parts as those in FIG. 6 are denoted by the same reference numerals, and descriptions thereof are omitted.
- the update information storage unit 322 is not used in the third embodiment.
- FIG. 10 is a sequence diagram for explaining an example of the processing procedure of software update processing according to the third embodiment.
- the same steps as in FIG. 7 are given the same step numbers, and the description thereof is omitted.
- FIG. 10 shows a processing procedure in which the recording processing (S150a, S191, S192, S240a) for the update information storage unit 322 in FIG. 7 is excluded.
- FIG. 11 is a sequence diagram for explaining an example of a processing procedure executed according to SO in the third embodiment.
- the same steps as in FIG. 8 are given the same step numbers, and the description thereof will be omitted as appropriate.
- the setting change unit 33 speculatively tries to change the setting of each target GW 40 (S512-S513). Assume that the GW 40c is updating software at this timing. In this case, from the GW 40c, there is no normal response to the setting change, or a response indicating that updating is in progress is returned.
- the determination unit 34 determines whether or not each target GW 40 is being updated based on the presence or absence of a normal response or a response indicating that updating is in progress. A normal response is a response indicating that the setting change has been completed.
- the setting change unit 33 waits for a certain period of time (S711), and then re-executes the setting change for the GW 40c for which the setting change has not been completed (S712). If there is no response or if a response indicating that updating is in progress is returned (S713), the setting change unit 33 repeats step S711 and subsequent steps. After that, when the update of the GW 40c is completed, the setting change of the GW 40c succeeds (S714, S715). That is, the setting change unit 33 repeats the setting change until the setting change for the GW 40c succeeds.
- the functional configuration can be simplified.
- the user portal 10 and the orchestrator 30 are examples of a setting change device.
- the update information storage unit 121 or the update information storage unit 322 is an example of a storage unit.
- UEs 100 drive device 101 recording medium 102 auxiliary storage device 103 memory device 104 CPU 105 interface device 121 update information storage unit 321 customer information storage unit 322 update information storage unit B bus
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
次に、第2の実施の形態について説明する。第2の実施の形態では第1の実施の形態と異なる点について説明する。第2の実施の形態において特に言及されない点については、第1の実施の形態と同様でもよい。
11 オーダ受付部
12 判定部
13 オーダ送信部
20 保守用コンソール
21 更新指示受付部
30 オーケストレータ
31 更新制御部
32 オーダ受信部
33 設定変更部
34 判定部
40 GW
50 UE
100 ドライブ装置
101 記録媒体
102 補助記憶装置
103 メモリ装置
104 CPU
105 インタフェース装置
121 更新情報記憶部
321 顧客情報記憶部
322 更新情報記憶部
B バス
Claims (7)
- 冗長構成に係る複数のネットワーク機器に対する設定変更の指示が入力されると、前記複数のネットワーク機器に関してソフトウェアの更新中であるかを判定する判定部と、
いずれかの前記ネットワーク機器が前記ソフトウェアの更新中である場合に、当該ネットワーク機器のソフトウェアの更新が完了するまで待機して、当該ネットワーク機器に関して前記設定変更を実行する設定変更部と、
を有することを特徴とする設定変更装置。 - 前記設定変更部は、前記ソフトウェアの更新中でない前記ネットワーク機器については、他の前記ネットワーク機器が前記ソフトウェアの更新中であっても前記設定変更を実行する、
ことを特徴とする請求項1記載の設定変更装置。 - 前記設定変更部は、前記ソフトウェアの更新中の前記ネットワーク機器に対して前記設定変更が成功するまで前記設定変更を繰り返す、
ことを特徴とする請求項1又は2記載の設定変更装置。 - 前記複数のネットワーク機器のうち、予備系の第1のネットワーク機器に対して前記ソフトウェアの更新を行った後で稼働系と予備系とを入れ替えて、新たに予備系となった第2のネットワーク機器に対して前記ソフトウェアの更新を行う更新制御部を有し、
前記更新制御部は、前記第1のネットワーク機器に対する更新の開始に伴って、前記複数のネットワーク機器に収容されるユーザについて更新中であることを示す情報を記憶部に記録し、前記第2のネットワーク機器に対する更新の完了に伴って、当該情報を前記記憶部から削除し、
前記判定部は、前記記憶部に前記情報が記憶されている場合に、前記更新中であると判定し、
前記設定変更部は、前記記憶部から前記情報が削除されるまで、前記設定変更を待機する、
ことを特徴とする請求項1記載の設定変更装置。 - 前記複数のネットワーク機器のうち、予備系の第1のネットワーク機器に対して前記ソフトウェアの更新を行った後で稼働系と予備系とを入れ替えて、新たに予備系となった第2のネットワーク機器に対して前記ソフトウェアの更新を行う更新制御部を有し、
前記更新制御部は、それぞれの前記ネットワーク機器に対する更新の開始に伴って、当該ネットワーク機器について更新中であることを示す情報を記憶部に記録し、当該ネットワーク機器に対する更新の完了に伴って、当該情報を前記記憶部から削除し、
前記設定変更部は、前記記憶部に前記情報が記録されている前記ネットワーク機器について、前記設定変更を待機する、
ことを特徴とする請求項1又は2記載の設定変更装置。 - 冗長構成に係る複数のネットワーク機器に対する設定変更の指示が入力されると、前記複数のネットワーク機器に関してソフトウェアの更新中であるかを判定する判定手順と、
いずれかの前記ネットワーク機器が前記ソフトウェアの更新中である場合に、当該ネットワーク機器のソフトウェアの更新が完了するまで待機して、当該ネットワーク機器に関して前記設定変更を実行する設定変更手順と、
をコンピュータが実行することを特徴とする設定変更方法。 - 請求項1乃至5いずれか一項記載の設定変更装置としてコンピュータを機能させることを特徴とするプログラム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/275,790 US20240129184A1 (en) | 2021-02-09 | 2021-02-09 | Setting changing apparatus, setting changing method and program |
PCT/JP2021/004785 WO2022172331A1 (ja) | 2021-02-09 | 2021-02-09 | 設定変更装置、設定変更方法及びプログラム |
JP2022581053A JPWO2022172331A1 (ja) | 2021-02-09 | 2021-02-09 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/004785 WO2022172331A1 (ja) | 2021-02-09 | 2021-02-09 | 設定変更装置、設定変更方法及びプログラム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022172331A1 true WO2022172331A1 (ja) | 2022-08-18 |
Family
ID=82838464
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/004785 WO2022172331A1 (ja) | 2021-02-09 | 2021-02-09 | 設定変更装置、設定変更方法及びプログラム |
Country Status (3)
Country | Link |
---|---|
US (1) | US20240129184A1 (ja) |
JP (1) | JPWO2022172331A1 (ja) |
WO (1) | WO2022172331A1 (ja) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011128683A (ja) * | 2009-12-15 | 2011-06-30 | Fujitsu Ltd | 情報処理装置、コマンド判定プログラム、およびコマンド判定方法 |
JP2013097515A (ja) * | 2011-10-31 | 2013-05-20 | Canon Inc | 情報処理装置、その制御方法、および制御プログラム |
JP2014078839A (ja) * | 2012-10-10 | 2014-05-01 | O F Networks Co Ltd | 親局通信装置、親局制御プログラム及びネットワークシステム |
JP2015032301A (ja) * | 2013-08-07 | 2015-02-16 | 日本電信電話株式会社 | 仮想ホストのバージョンアップ方法、および、ネットワーク装置 |
JP2017169044A (ja) * | 2016-03-16 | 2017-09-21 | 日本電気株式会社 | 設定装置、通信システム、通信装置の設定更新方法及びプログラム |
JP2019075057A (ja) * | 2017-10-19 | 2019-05-16 | 住友電気工業株式会社 | 通信装置のファームウェア更新方法、通信装置の制御装置および通信装置 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8533316B2 (en) * | 2007-04-27 | 2013-09-10 | Hitachi, Ltd. | Management computer for setting configuration information of node |
TWI386847B (zh) * | 2009-02-04 | 2013-02-21 | Novatek Microelectronics Corp | 可安全復原的韌體更新方法及可安全復原之韌體更新的嵌入式電子裝置 |
US9600263B2 (en) * | 2014-07-21 | 2017-03-21 | Big Switch Networks, Inc. | Systems and methods for performing uninterrupted network upgrades with controllers |
JP6812900B2 (ja) * | 2017-05-17 | 2021-01-13 | 富士通株式会社 | ストレージ装置、ストレージ制御装置、およびストレージ制御プログラム |
JP6562093B2 (ja) * | 2018-01-23 | 2019-08-21 | 日本電気株式会社 | システム管理装置 |
JP7088070B2 (ja) * | 2019-02-18 | 2022-06-21 | 日本電信電話株式会社 | ソフトウェア更新管理装置およびソフトウェア更新管理方法 |
-
2021
- 2021-02-09 US US18/275,790 patent/US20240129184A1/en active Pending
- 2021-02-09 WO PCT/JP2021/004785 patent/WO2022172331A1/ja active Application Filing
- 2021-02-09 JP JP2022581053A patent/JPWO2022172331A1/ja active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011128683A (ja) * | 2009-12-15 | 2011-06-30 | Fujitsu Ltd | 情報処理装置、コマンド判定プログラム、およびコマンド判定方法 |
JP2013097515A (ja) * | 2011-10-31 | 2013-05-20 | Canon Inc | 情報処理装置、その制御方法、および制御プログラム |
JP2014078839A (ja) * | 2012-10-10 | 2014-05-01 | O F Networks Co Ltd | 親局通信装置、親局制御プログラム及びネットワークシステム |
JP2015032301A (ja) * | 2013-08-07 | 2015-02-16 | 日本電信電話株式会社 | 仮想ホストのバージョンアップ方法、および、ネットワーク装置 |
JP2017169044A (ja) * | 2016-03-16 | 2017-09-21 | 日本電気株式会社 | 設定装置、通信システム、通信装置の設定更新方法及びプログラム |
JP2019075057A (ja) * | 2017-10-19 | 2019-05-16 | 住友電気工業株式会社 | 通信装置のファームウェア更新方法、通信装置の制御装置および通信装置 |
Also Published As
Publication number | Publication date |
---|---|
US20240129184A1 (en) | 2024-04-18 |
JPWO2022172331A1 (ja) | 2022-08-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1965541B1 (en) | System, apparatus and method for automated wireless device configuration | |
JP5488980B2 (ja) | コンピュータシステム、及び通信方法 | |
JP5804054B2 (ja) | 通信システム、制御装置、ノード、処理規則の設定方法およびプログラム | |
JP6388955B2 (ja) | OpenFlowスイッチのグレースフル・リスタート処理方法及びOpenFlowコントローラ | |
JP5462252B2 (ja) | 2部ピアオーバレイを用いてp2pモードにおいてピア間でコンテンツデータを伝送する装置及び方法 | |
KR101658824B1 (ko) | 소프트웨어 정의 네트워크에서 플로우 룰을 변경하는 방법, 장치 및 컴퓨터 프로그램 | |
CN107508916B (zh) | 用于智能机器人的服务器链接管理方法 | |
WO2022172331A1 (ja) | 設定変更装置、設定変更方法及びプログラム | |
JP7347525B2 (ja) | システム、方法及び制御装置 | |
EP1901497A1 (en) | Apparatus for low latency communications through an alternate path | |
CN100527693C (zh) | 通信网络以及操作该通信网络以传送数据的方法 | |
JPWO2012132101A1 (ja) | 情報処理装置、および障害対応プログラム | |
JP2011048702A (ja) | 電子機器、通信制御装置、およびプログラム | |
JP2004254039A (ja) | メール通信中継システム、メール通信中継装置、メール通信中継方法及びメール通信中継用プログラム | |
US9847916B2 (en) | Control apparatus, control apparatus control method, and program | |
KR102404112B1 (ko) | 소프트웨어 정의 네트워크 환경에서의 sdn 컨트롤러 서버 장애 발생시 이를 처리하는 네트워크 장비 및 방법 | |
JP5958626B2 (ja) | 通信制御装置およびプログラム | |
KR101783094B1 (ko) | 컨트롤러와 네트워크 장치 간에 번들 능력을 통보하는 방법 및 장치 | |
JP2002261792A (ja) | 通信システムとそのパケット交換方法、及び交換プログラムを記録した記録媒体 | |
JP6975974B2 (ja) | 制御装置、制御方法、及び、プログラム | |
JP3989447B2 (ja) | 通信切替方法およびデータ通信装置 | |
CN113014481B (zh) | 传输链路状态通告的方法、装置、设备及存储介质 | |
KR100372342B1 (ko) | 이동통신 시스템에서의 운용자 명령 처리 방법 | |
JP4485295B2 (ja) | 移動制御システム、移動制御方法及び移動制御装置並びに移動制御プログラム | |
JP6233460B2 (ja) | 通信制御装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21925585 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022581053 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18275790 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21925585 Country of ref document: EP Kind code of ref document: A1 |