EP2916488A1 - Method and system for upgrading software of distributed communication device - Google Patents

Method and system for upgrading software of distributed communication device Download PDF

Info

Publication number
EP2916488A1
EP2916488A1 EP13851276.9A EP13851276A EP2916488A1 EP 2916488 A1 EP2916488 A1 EP 2916488A1 EP 13851276 A EP13851276 A EP 13851276A EP 2916488 A1 EP2916488 A1 EP 2916488A1
Authority
EP
European Patent Office
Prior art keywords
software
main control
data
control unit
active
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP13851276.9A
Other languages
German (de)
French (fr)
Other versions
EP2916488B1 (en
EP2916488A4 (en
Inventor
Zhenfu Zhao
Wei Chen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of EP2916488A1 publication Critical patent/EP2916488A1/en
Publication of EP2916488A4 publication Critical patent/EP2916488A4/en
Application granted granted Critical
Publication of EP2916488B1 publication Critical patent/EP2916488B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • G06F8/656Updates while running
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/085Retrieval of network configuration; Tracking network configuration history
    • H04L41/0859Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions

Definitions

  • the disclosure relates to the technical field of communications, and in particular to a software upgrading method and system for a distributed communication device.
  • a communication device In network communication devices operating on a network, for performance and expandability consideration, many of the devices are distributed communication devices implemented on the basis of a multiprocessing operation system.
  • multiple service processes are used to cooperatively implement functions of the communication device such as routing learning and data forwarding.
  • the communication device interacts with external devices, learns network route, and calculates and generates an optimum route table for use in a forwarding plane. Then the optimum route table is issued to the forwarding plane, which performs routing and forwarding of data according to the optimum route table.
  • embodiments of the disclosure are intended to provide a software upgrading method and system for a distributed communication device, which can avoid unnecessary service interruption arisen during a software upgrading, thus improving reliability and availability of services and improving user experiences.
  • a software upgrading method for a distributed communication device applied to a software upgrading system for the distributed communication device that includes an active main control unit, a standby main control unit and a line card, the method including:
  • the step that the active main control unit notifies the standby main control unit to launch a new version of a software and run said new version of the software in a standby state, and performs data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit may include:
  • the step that the line card launches a new version of a software of a control plane and of a management plane and runs said new version of the software in a standby state, and performs data and data state recovery on said new version of the software on the line card through a current active main control unit, or performs data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card may include:
  • the method may further include:
  • the method may further include:
  • a software upgrading system for a distributed communication device including an active main control unit, a standby main control unit and a line card, wherein the active main control unit is configured to notify the standby main control unit to launch a new version of a software, to perform data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit, and to change a running state of the active main control unit to a standby state after the data and data state recovery is finished; the standby main control unit is configured to launch said new version of the software and run the said new version of the software in a standby state, to cooperate with the active main control unit to perform the data and data state recovery on said new version of the software, and to change a running state of the standby main control unit to an active state after the data and data state recovery is finished; and the line card is configured to, after active/standby state inversion between the active main control unit and the standby main control unit is finished, launch a new version of a software of a control plane and of
  • the active main control unit may include a first version manager and a first active standby manager
  • the standby main control unit may include a second version manager and a second active standby manager
  • each software on the active and standby main control units may include a data recovery assembly
  • the first version manager is configured to notify the second version manager to launch the new version of the software on the standby main control unit, and to, after the data and data state recovery is finished, notify the first active standby manager to change the running state of the active main control unit to a standby state
  • the second version manager is configured to launch the new version of the software on the standby main control unit, and to, after the data and data state recovery is finished, notify the second active standby manager to change the running state of the standby main control unit to the active state
  • the first active standby manager is configured to perform the active/standby state inversion on the running state of the active main control unit
  • the second active standby manager is configured to perform the active/standby state inversion on the running state of the standby main control unit
  • the data and data state recovery is performed on said new version of the software on the standby main control unit through the old version of the software on the active main control unit based on the data recovery assembly of the active main control unit.
  • the line card may include a third version manager, and each software on the active and standby main control units and the line card may include a data recovery assembly; specifically, the third version manager is configured to, after the active/standby state inversion between the active main control unit and the standby main control unit is finished, launch said new version of the software of the control plane and of the management plane on the line card and run said new version of the software in a standby state; and to, after the data and data state recovery performed on the line card is finished, cancel said old version of the software of the control plane and of the management plane, run said new version of the software of the control plane and of the management plane in the active state, and refresh the data of and the data state of the software of the forwarding plane; the data and data state recovery is performed on said new version of the software on the line card through the current active main control unit based on the data recovery assembly of the current active main control unit, or the data and data state recovery is performed on said new version of the software on the line card through the old version of the software of the control plane
  • the line card may be further configured to, after the data and data state recovery performed on the line card is finished and before the data of and the data state of the software of the forwarding plane are refreshed, upgrade the software of the forwarding plane on the line card.
  • the active main control unit may be further configured to, after the active/standby state inversion between the active main control unit and the standby main control unit is finished, upgrade said old version of the software on an original active main control unit to the new version of the software and run the new version of the software in the standby state.
  • softwares are upgraded in sequence in the main control units and the line card, since the main control units include the active main control unit and the standby main control unit based on physical redundancy, the software is enabled to run in an active state or a standby state in the line card, thus the embodiments according to the disclosure enable new and old versions of a software to run simultaneously, and the new version of the software is enabled to replace seamlessly the old version of the software so as to enter a running state through active/standby state inversion between the active main control unit and the standby main control unit as well as control of an active/standby running state of the new and old versions of the software on the line card.
  • the software of the control plane and of the management plane is upgraded on the line card, and the software of the forwarding plane of the line card is upgraded as required so as to avoid unnecessary service interruption arisen from the software upgrading, thus improving reliability and availability of services, avoiding severe economic loss resulted from the service interruption, and improving user experiences.
  • An embodiment of the disclosure discloses a software upgrading method for a distributed communication device, which is applied to a software upgrading system for the distributed communication device that includes an active main control unit, a standby main control unit and a line card, and the method includes two stages: a first stage of a software upgrading process for main control units, and a second stage of a software upgrading process for a line card.
  • the active main control unit and the standby main control unit together are referred to as main control units and also as main processing units which take charge of system management, route calculation and the like in a communication device.
  • the active main control unit refers to a main processor on which softwares run in an active state and provide services to the outside.
  • the active main control unit refers to a main processor on which softwares run in a standby state and do not provide services to the outside, and the softwares can provide services to the outside only after being changed to the active state.
  • the line card takes charge of implementing services such as management of forwarded data and data forwarding.
  • the active main control unit and the standby main control unit each can be implemented by a Central Processing Unit (CPU), a Digital Signal Processor (DSP) or a Field Programmable Gate Array (FPGA).
  • CPU Central Processing Unit
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • the active main control unit may include a first version manager and a first active standby manager; the standby main control unit may include a second version manager and a second active standby manager, and each software on main control units may include a data recovery assembly; the line card may include a third version manager, and each software on the main control units and the line card may include a data recovery assembly.
  • step S101 may include:
  • Step A1 specifically includes: the first version manager notifies the second version manager to launch the new version of the software on the standby main control unit.
  • step A2 may include:
  • Step S102 active/standby state inversion between the active main control unit and the standby main control unit is performed.
  • the standby main control unit having finished the software upgrading is enabled to enter an active running state, and the original active main control unit is enabled to enter a standby running state, on which the software is waiting to be upgraded.
  • the first version manager after the data and data state recovery is finished, notifies the first active standby manager to change the running state of the active main control unit to the standby state, and the second version manager notifies the second active standby manager to change the running state of the standby main control unit to the active state.
  • Step S103 a current active main control unit notifies the line card to launch a new version of a software of a control plane and of a management plane and runs said new version of the software in a standby state, and performs the data and data state recovery on said new version of the software on the line card through the current active main control unit, or performs the data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card.
  • the third version manager launches said new version of the software of the control plane and of the management plane on the line card and run said new version of the software in a standby state; and after the data and data state recovery performed on the line card is finished, cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, and refreshes data of and a data state of a software of a forwarding plane; the data and data state recovery is performed on said new version of the software on the line card through the new version of the software of the current active main control unit based on a data recovery assembly, or the data and data state recovery is performed on said new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card based on the data recovery assembly.
  • step S103 the processing that the data and data state recovery is performed on the new version of the software of the control plane and of the management plane on the line card through the current active main control unit includes:
  • the data and data state synchronized from the active main control unit are received through the new version of the software of the control plane and of the management plane on the line card based on the data recovery assembly.
  • step S103 the processing that the data and data state recovery is performed on the new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card includes:
  • the data and data state synchronized from the old version of the software of the control plane and of the management plane on the line card are received through the new version of the software of the control plane and of the management plane on the line card based on the data recovery assembly.
  • Step S104 after the data and data state recovery performed on the line card is finished, the line card cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, and refreshes the data of and the data state of the software of the forwarding plane.
  • the third version manager cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, and refreshes the data of and the data state of the software of the forwarding plane.
  • the method may further include:
  • the main control unit herein refers to a main control unit in the active state, i.e., the active main control unit, since the standby main control unit does not provide services to the system.
  • An embodiment of the disclosure discloses a software upgrading method for a distributed communication device, which is applied to a software upgrading system for the distributed communication device that includes an active main control unit, a standby main control unit and a line card, and the method includes two stages: a first stage of a software upgrading process for main control units and a second stage of a software upgrading process for a line card, as shown in Fig. 2 , the method includes below steps:
  • step S201 may include:
  • Step A1 specifically includes: the first version manager notifies the second version manager to launch the new version of the software on the standby main control unit.
  • step A2 may include:
  • Step S202 active/standby state inversion between the active main control unit and the standby main control unit is performed.
  • the standby main control unit having finished the software upgrading is enabled to enter an active running state, and the original active main control unit is enabled to enter a standby running state, on which the software is waiting to be upgraded.
  • the first version manager after the data and data state recovery is finished, notifies the first active standby manager to change the running state of the active main control unit to the standby state, and the second version manager notifies the second active standby manager to change the running state of the standby main control unit to the active state.
  • Step S203 after the active/standby state inversion between the active main control unit and the standby main control unit, said old version of the software on an original active main control unit is upgraded to the new version of the software and the new version of the software is run in the standby state.
  • Step S204 a current active main control unit notifies the line card to launch a new version of a software of a control plane and of a management plane and runs said new version of the software in a standby state, and performs the data and data state recovery on said new version of the software on the line card through the current active main control unit, or performs the data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card.
  • the third version manager launches said new version of the software of the control plane and of the management plane on the line card and run said new version of the software in a standby state; and after the data and data state recovery performed on the line card is finished, cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, and refreshes data of and a data state of a software of a forwarding plane; the data and data state recovery is performed on said new version of the software on the line card through the new version of the software of the current active main control unit based on a data recovery assembly, or the data and data state recovery is performed on said new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card based on the data recovery assembly.
  • Step S205 after the data and data state recovery performed on the line card is finished, the line card cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, upgrades the software of the forwarding plane on the line card, and refreshes the data of and the data state of the software of the forwarding plane.
  • the third version manager cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, upgrades the software of the forwarding plane on the line card, and refreshes the data of and the data state of the software of the forwarding plane.
  • the process of upgrading a software of the forwarding plane by the third version manager on the line card is similar to the process of upgrading the software of the control plane and of the management plane on the line card, the reason why the upgrading of the software of the forwarding plane comes last lies in that the function of the forwarding plane affects directly service operation of the communication device, upgrading firstly the software of the control plane and of the management plane on the line card will not result in interruption of the service; the process of upgrading the software of the forwarding plane also needs to follow the below procedures: an old version of the software of the forwarding plane is cancelled and a new version of the software of the forwarding plane is launched, a data and data state recovery is performed on the new version of the software of the forwarding plane on the line card through the new version of the software on the current active main control unit, the data of and the data state of the new version of the software of the forwarding plane are refreshed, so as to validate the entries of the forwarding table of the new version of the software of the forwarding plane. Time taken by upgrading the software of the forwarding plane is very short
  • the method may further include:
  • the main control unit herein refers to a main control unit in the active state, i.e., the active main control unit, since the standby main control unit does not provide services to the system.
  • Embodiments of the disclosure further disclose a software upgrading system for a distributed communication device, as shown in Fig. 3 , the system includes an active main control unit 10 including a standby main control unit 20 and a line card 30 based on physical redundancy; the active main control unit 20 is configured to notify the standby main control unit to launch a new version of a software, to perform data and data state recovery on said new version of the software on the standby main control unit 30 through an old version of the software on the active main control unit 20, and to change a running state of the active main control unit to a standby state after the data and data state recovery is finished.
  • an active main control unit 10 including a standby main control unit 20 and a line card 30 based on physical redundancy
  • the active main control unit 20 is configured to notify the standby main control unit to launch a new version of a software, to perform data and data state recovery on said new version of the software on the standby main control unit 30 through an old version of the software on the active main control unit 20, and to change a
  • the standby main control unit 30 is configured to launch said new version of the software and run the said new version of the software in a standby state, to cooperate with the active main control unit 20 to perform the data and data state recovery on said new version of the software, and to change a running state of the standby main control unit to an active state after the data and data state recovery is finished.
  • the active main control unit 20 may include a first version manager 21 and a first active standby manager 22, the standby main control unit 30 may include a second version manager 31 and a second active standby manager 32, and each software on the active and standby main control units may include a data recovery assembly 11;
  • the first version manager 21 is configured to notify the second version manager 31 to launch the new version of the software on the standby main control unit 30, and to, after the data and data state recovery is finished, notify the first active standby manager 22 to change the running state of the active main control unit 22 to a standby state so that the old version of the software enters a standby running state and waits to be upgraded;
  • the data recovery assembly 11 is configured to perform, in the old version of the software on the active main control unit 20, the data and data state recovery on said new version of the software on the standby main control unit 30;
  • the second version manager 31 is configured to launch the new version of the software on the standby main control unit 30, and to, after the data and data state recovery is finished, notify the second active stand
  • the line card 40 is configured to, after active/standby state inversion between the active main control unit 20 and the standby main control unit 30 is finished, launch a new version of a software of a control plane and of a management plane on the line card and run said new version of the software in a standby state, and to perform data and data state recovery on said new version of the software on the line card through a current active main control unit, or to perform data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card, and to, after the data and data state recovery performed on the line card is finished, cancel said old version of the software of the control plane and of the management plane, run said new version of the software of the control plane and of the management plane in the active state, and refresh data of and a data state of a software of a forwarding plane.
  • the line card 40 may include a third version manager 41, and each software on the active and standby main control units and the line card may include a data recovery assembly.
  • the third version manager 41 is configured to, after the active/standby state inversion between the active main control unit 20 and the standby main control unit 30 is finished, launch said new version of the software of the control plane and of the management plane on the line card and run said new version of the software in a standby state; and to, after the data and data state recovery performed on the line card 40 is finished, cancel said old version of the software of the control plane and of the management plane, run said new version of the software of the control plane and of the management plane in the active state, and refresh the data of and the data state of the software of the forwarding plane;
  • the data recovery assembly 11 is configured to perform, in the old version of the software on the active main control unit 20, the data and data state recovery i on said new version of the software on the line card 40, or the data and data state recovery is performed on said new version of the software on the line card 40 through the old version of the software of the control plane and of the management plane on the line card 40 based on the data recovery assembly 11.
  • An embodiment of the disclosure further discloses a software upgrading system for a distributed communication device
  • the software upgrading system for a distributed communication device is roughly the same as the software upgrading system for a distributed communication device shown in Fig. 3 , and the difference lies in that in the system according to the embodiment, the active main control unit 20 is further configured to, after the active/standby state inversion between the active main control unit 20 and the standby main control unit 30 is finished, upgrade said old version of the software on an original active main control unit 20 to the new version of the software and run the new version of the software in the standby state.
  • the line card 40 is further configured to, after the data and data state recovery performed on the line card 40 is finished and before the data of and the data state of the software of the forwarding plane are refreshed, upgrade the software of the forwarding plane on the line card 40.
  • the process of upgrading a software of the forwarding plane by the third version manager 41 on the line card 40 is similar to the process of upgrading the software of the control plane and of the management plane on the line card 40, the reason why the upgrading of the software of the forwarding plane comes last lies in that the function of the forwarding plane affects directly service operation of the communication device, upgrading firstly the software of the control plane and of the management plane on the line card 40 will not result in interruption of the service; the process of upgrading the software of the forwarding plane also needs to follow the below procedures: an old version of the software of the forwarding plane is cancelled and a new version of the software of the forwarding plane is launched, a data and data state recovery is performed on the new version of the software of the forwarding plane on the line card 40 through the new version of the software on the current active main control unit 20, the data of and the data state of the new version of the software of the forwarding plane are refreshed, so as to validate the entries of the forwarding table of the new version of the software of the forwarding plane. Time taken by upgrading the software
  • Application scenario upgrading of a software of an access gateway.
  • Fig. 4 is a sequence diagram showing interaction during software upgrading of a distributed access gateway
  • Fig. 5 to Fig. 10 show various states during the software upgrading of the distributed access gateway
  • the access gateway in the drawings is a distributed communication device for implementing access of users to a network, and for high reliability and high availability consideration, the access gateway is configured with active/standby main control panels
  • Fig. 5 shows a state before upgrading of the software of the distributed access gateway, a processing unit on the active control panel is a main controller 1 while a processing unit on the standby main control panel is a main controller 2.
  • 4 line cards are configured in order to implement access of users and forwarding processing.
  • a subsidiary process There are 80 processes running on the main control unit, such as a supportive process, a Border Gateway Protocol (BGP) process, a Routing Information Protocol (RIP) process, an Open Shortest Path First (OSPF) process, a Forward Information Base (FIB) process and the like.
  • BGP Border Gateway Protocol
  • RIP Routing Information Protocol
  • OSPF Open Shortest Path First
  • FIB Forward Information Base
  • the four line cards of the access gateway are upgraded in a line card by line card way. That is to say, each line card is upgraded in sequence, line card 1 is upgraded first, then line card 2 is upgraded, and then line card 3 is upgraded, finally line card 4 is upgraded.
  • the upgrading of the version of the software of the access gateway relates to below assemblies: an old version of the software, a new version of the software, a version manager, and an active standby manager.
  • the old version of the software and the new version of the software implement a same function
  • the version manager takes charge of upgrading of the version of a software, failure rollback and the like
  • the active standby manager takes charge of active/standby management of new/old versions of a software
  • Processing steps for implementing, on a network, a software upgrading method for a distributed access gateway are as follows.
  • Stage 1 upgrading of a software of a main controller.
  • a new version of a software to which an old version of the software is to be upgraded needs to be copied to an active main controller of an access gateway (the device automatically copies it to a standby main controller); a new version of a software of the line card is acquired by request from the main controller;
  • the VM on the main controller 1 after receiving the main controller software upgrading instruction, the VM on the main controller 1 sends a command to a VM on the main controller 2, the old version of the software is upgraded to a new version of the software and the new version of the software is launched on the main controller 2, as shown in Fig. 6 ;
  • data and data state recovery is performed on the new version of the software on the main controller 2 through the old version of the software on the main controller 1, so that after entering a running state, the new version of the software can take over seamlessly the old version of the software to provide services to the outside; preferably, there may be one or more communication links for the data and data state recovery;
  • the new version of the software on the main controller 2 sends, through the VM on the main controller 2, a standby main controller new version launch completion notification to the VM on the main controller 1;
  • the VM on the main controller 1 triggers active/standby state inversion of the active main controller on an Active Standby Manager (ASM) on the main controller 1, as shown in Fig. 7 .
  • the VM on the main controller 2 triggers active/standby state inversion of the standby main controller on an ASM on the main controller 2;
  • the main controller 1 is changed to a new standby main controller, and the main controller 2 is changed to a new active main controller.
  • a new version of the software on the new active main controller replaces the old version of the software and enters an active running state so as to provide service to the outside.
  • the old version of the software on the new standby main controller does not provide services to the outside;
  • the VM on the main controller 1 feeds a result of upgrading success back to the user, and indicates that subsequent upgrading of a software of the line card can be implemented.
  • Stage 2 upgrading of a software of a line card (upgrading is performed line card by line card, line card 1 is taken as an example to elaborate, other line cards have a same upgrading process).
  • the VM on the main controller 2 after receiving the software upgrading instruction for the line card 1, the VM on the main controller 2 sends a line card software upgrading instruction to a VM on the line card 1;
  • the VM on the line card 1 acquires the new version of the software from the main controller 2, launches the new version of the software of the control plane and of the management plane on the line card and runs it in the standby state, and before being changed to the active state, the new version of the software of the control plane and of the management plane does not provide services to the outside;
  • the new version of the software of the control plane and of the management plane on the line card 1 needs to recover data and data state required for providing services.
  • the data and data state recovery is implemented through multiple communication links;
  • the VM on the line card 1 after receiving the new version software recovery completion notification, the VM on the line card 1 sends a cancellation instruction to the old version of the software of the control plane and of the management plane on the line card 1. And the VM on the line card 1 sends an active/standby state inversion instruction to the new version of the software of the control plane and of the management plane on the line card 1;
  • active/standby state inversion is performed on the new version of the software of the control plane and of the management plane on the line card 1 so that the new version of the software replaces the old version of the software of the control plane and of the management plane and enters the running state;
  • the VM on the line card 1 feeds a result of the upgrading of the software on the line card back to the main controller 2.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)
  • Hardware Redundancy (AREA)

Abstract

Provided is a software upgrading method for a distributed communication device, and the method includes: softwares are upgraded in sequence in the main control units and the line card, new and old versions of a software are enabled to run simultaneously, and the new version of the software is enabled to replace seamlessly the old version of the software so as to enter a running state through active/standby state inversion of the active main control unit and the standby main control unit as well as control of an active/standby running state of the new and old versions of the software on the line card. Further disclosed is a software upgrading system for a distributed communication device. By means of the technical solutions according to the disclosure, the software of the forwarding plane of the line card is upgraded as required so as to avoid unnecessary service interruption arisen from the software upgrading, thus improving reliability and availability of services, avoiding severe economic loss resulted from the service interruption and improving user experiences.

Description

    TECHNICAL FIELD
  • The disclosure relates to the technical field of communications, and in particular to a software upgrading method and system for a distributed communication device.
  • BACKGROUND
  • With an increasing demand for accessing a network to acquire information at any time in any places, various wired and wireless terminals spring up and are connected to the network. In order to improve user experiences, network devices for bearing user network services in a network become increasingly important; if an anomaly arises in a network device, it may affect user access experiences, resulting in user churn, and may even affect operation of an enterprise's electronic commerce network, resulting in severe economic losses.
  • In network communication devices operating on a network, for performance and expandability consideration, many of the devices are distributed communication devices implemented on the basis of a multiprocessing operation system. In a communication device using a multiprocessing operation system, multiple service processes are used to cooperatively implement functions of the communication device such as routing learning and data forwarding. The communication device interacts with external devices, learns network route, and calculates and generates an optimum route table for use in a forwarding plane. Then the optimum route table is issued to the forwarding plane, which performs routing and forwarding of data according to the optimum route table.
  • During operation of the network device, since there may be malfunctions or newly-added functional features in the software, it is inevitable to encounter various software upgradings for the network device. However, there are so far no effective methods that can avoid service interruption arisen during a software upgrading of the network device.
  • SUMMARY
  • In view of the above, embodiments of the disclosure are intended to provide a software upgrading method and system for a distributed communication device, which can avoid unnecessary service interruption arisen during a software upgrading, thus improving reliability and availability of services and improving user experiences.
  • To this end, the technical solutions of embodiments of the disclosure are implemented as follows.
  • A software upgrading method for a distributed communication device, applied to a software upgrading system for the distributed communication device that includes an active main control unit, a standby main control unit and a line card, the method including:
    • the active main control unit notifies the standby main control unit to launch a new version of a software and run said new version of the software in a standby state, and performs data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit;
    • active/standby state inversion between the active main control unit and the standby main control unit is performed;
    • the line card launches a new version of a software of a control plane and of a management plane and runs said new version of the software in a standby state, and performs data and data state recovery on said new version of the software on the line card through a current active main control unit, or performs data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card;
    • the line card cancels said old version of the software of the control plane and of the management plane, and runs said new version of the software of the control plane and of the management plane in an active state; and
    • the line card refreshes data of and a data state of a software of a forwarding plane.
  • In an embodiment, the step that the active main control unit notifies the standby main control unit to launch a new version of a software and run said new version of the software in a standby state, and performs data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit may include:
    • the active main control unit notifies the standby main control unit to launch the new version of the software on the standby main control unit; and
    • the data and data state recovery is performed on said new version of the software on the standby main control unit through the old version of the software on the active main control unit based on a data recovery assembly;
  • In an embodiment, the step that the line card launches a new version of a software of a control plane and of a management plane and runs said new version of the software in a standby state, and performs data and data state recovery on said new version of the software on the line card through a current active main control unit, or performs data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card may include:
    • after the active/standby state inversion between the active main control unit and the standby main control unit is finished, the line card launches said new version of the software of the control plane and of the management plane on the line card and runs said new version of the software in the standby state;
    • the data and data state recovery is performed on said new version of the software on the line card through the current active main control unit based on a data recovery assembly, or the data and data state recovery is performed on said new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card based on a data recovery assembly; and
    • after the data and data state recovery performed on the line card is finished, the line card cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, and refreshes the data of and the data state of the software of the forwarding plane.
  • In an embodiment, the method may further include:
    • after the data and data state recovery performed on the line card is finished and before the data of and the data state of the software of the forwarding plane are refreshed, the software of the forwarding plane on the line card is upgraded.
  • In an embodiment, the method may further include:
    • after the active/standby state inversion between the active main control unit and the standby main control unit is finished, said old version of the software on an original active main control unit is upgraded to the new version of the software and the new version of the software is run in the standby state.
  • A software upgrading system for a distributed communication device, including an active main control unit, a standby main control unit and a line card, wherein
    the active main control unit is configured to notify the standby main control unit to launch a new version of a software, to perform data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit, and to change a running state of the active main control unit to a standby state after the data and data state recovery is finished;
    the standby main control unit is configured to launch said new version of the software and run the said new version of the software in a standby state, to cooperate with the active main control unit to perform the data and data state recovery on said new version of the software, and to change a running state of the standby main control unit to an active state after the data and data state recovery is finished; and
    the line card is configured to, after active/standby state inversion between the active main control unit and the standby main control unit is finished, launch a new version of a software of a control plane and of a management plane on the line card and run said new version of the software in a standby state, and to perform data and data state recovery on said new version of the software on the line card through a current active main control unit, or to perform data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card, and to, after the data and data state recovery performed on the line card is finished, cancel said old version of the software of the control plane and of the management plane, run said new version of the software of the control plane and of the management plane in the active state, and refresh data of and a data state of a software of a forwarding plane.
  • In an embodiment, the active main control unit may include a first version manager and a first active standby manager, the standby main control unit may include a second version manager and a second active standby manager, and each software on the active and standby main control units may include a data recovery assembly;
  • Specifically, the first version manager is configured to notify the second version manager to launch the new version of the software on the standby main control unit, and to, after the data and data state recovery is finished, notify the first active standby manager to change the running state of the active main control unit to a standby state;
    the second version manager is configured to launch the new version of the software on the standby main control unit, and to, after the data and data state recovery is finished, notify the second active standby manager to change the running state of the standby main control unit to the active state;
    the first active standby manager is configured to perform the active/standby state inversion on the running state of the active main control unit; and
    the second active standby manager is configured to perform the active/standby state inversion on the running state of the standby main control unit;
    the data and data state recovery is performed on said new version of the software on the standby main control unit through the old version of the software on the active main control unit based on the data recovery assembly of the active main control unit.
  • In an embodiment, the line card may include a third version manager, and each software on the active and standby main control units and the line card may include a data recovery assembly;
    specifically, the third version manager is configured to, after the active/standby state inversion between the active main control unit and the standby main control unit is finished, launch said new version of the software of the control plane and of the management plane on the line card and run said new version of the software in a standby state; and to, after the data and data state recovery performed on the line card is finished, cancel said old version of the software of the control plane and of the management plane, run said new version of the software of the control plane and of the management plane in the active state, and refresh the data of and the data state of the software of the forwarding plane;
    the data and data state recovery is performed on said new version of the software on the line card through the current active main control unit based on the data recovery assembly of the current active main control unit, or the data and data state recovery is performed on said new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card based on the data recovery assembly of the line card.
  • In an embodiment, the line card may be further configured to, after the data and data state recovery performed on the line card is finished and before the data of and the data state of the software of the forwarding plane are refreshed, upgrade the software of the forwarding plane on the line card.
  • In an embodiment, the active main control unit may be further configured to, after the active/standby state inversion between the active main control unit and the standby main control unit is finished, upgrade said old version of the software on an original active main control unit to the new version of the software and run the new version of the software in the standby state.
  • In the software upgrading method and system for a distributed communication device according to embodiments of the disclosure, softwares are upgraded in sequence in the main control units and the line card, since the main control units include the active main control unit and the standby main control unit based on physical redundancy, the software is enabled to run in an active state or a standby state in the line card, thus the embodiments according to the disclosure enable new and old versions of a software to run simultaneously, and the new version of the software is enabled to replace seamlessly the old version of the software so as to enter a running state through active/standby state inversion between the active main control unit and the standby main control unit as well as control of an active/standby running state of the new and old versions of the software on the line card. In addition, in embodiments of the disclosure, the software of the control plane and of the management plane is upgraded on the line card, and the software of the forwarding plane of the line card is upgraded as required so as to avoid unnecessary service interruption arisen from the software upgrading, thus improving reliability and availability of services, avoiding severe economic loss resulted from the service interruption, and improving user experiences.
  • BRIEF DESCRIPTION OF THE DRAWINGS
    • Fig. 1 is a flow chart of a software upgrading method for a distributed communication device according to a first embodiment of the disclosure;
    • Fig. 2 is a flow chart of a software upgrading method for a distributed communication device according to a second embodiment of the disclosure;
    • Fig. 3 is a schematic structural diagram of a software upgrading system for a distributed communication device according to a second embodiment of the disclosure;
    • Fig. 4 is a sequence diagram showing interaction during software upgrading of a distributed access gateway according to an embodiment of the disclosure;
    • Fig. 5 is a schematic diagram showing a state before software upgrading of a distributed access gateway according to an embodiment of the disclosure;
    • Fig. 6 is a schematic diagram showing that a main controller 2 of a distributed access gateway launches a new version of a software and performs data and data state recovery according to an embodiment of the disclosure;
    • Fig. 7 is a schematic diagram showing that a running state of the main controller 2 of the distributed access gateway is changed to an active state, and a new version of a software on the line card is launched to perform data and data state recovery according to an embodiment of the disclosure;
    • Fig. 8 is a schematic diagram showing that a line card of a distributed access gateway cancels an old version of a software according to an embodiment of the disclosure;
    • Fig. 9 is a schematic diagram showing that a new version of a software of a line card of a distributed access gateway enters a running state according to an embodiment of the disclosure; and
    • Fig. 10 is a schematic diagram showing that an old version of a software of a main controller 1 of a distributed access gateway is upgraded to a new version of the software according to an embodiment of the disclosure.
    DETAILED DESCRIPTION
  • In order to learn features and technical contents of embodiments of the disclosure in greater detail, the embodiments of the disclosure are elaborated below with reference to accompanying drawings which are for reference purposes only and not intended to limit the embodiments of the disclosure.
  • An embodiment of the disclosure discloses a software upgrading method for a distributed communication device, which is applied to a software upgrading system for the distributed communication device that includes an active main control unit, a standby main control unit and a line card, and the method includes two stages: a first stage of a software upgrading process for main control units, and a second stage of a software upgrading process for a line card.
  • In order to more clearly understand embodiments of the disclosure, concepts associated with embodiments of the disclosure are described as follows.
  • The active main control unit and the standby main control unit together are referred to as main control units and also as main processing units which take charge of system management, route calculation and the like in a communication device.
  • The active main control unit refers to a main processor on which softwares run in an active state and provide services to the outside.
  • The active main control unit refers to a main processor on which softwares run in a standby state and do not provide services to the outside, and the softwares can provide services to the outside only after being changed to the active state.
  • The line card takes charge of implementing services such as management of forwarded data and data forwarding.
  • Specifically, in practical applications, the active main control unit and the standby main control unit each can be implemented by a Central Processing Unit (CPU), a Digital Signal Processor (DSP) or a Field Programmable Gate Array (FPGA).
  • In an embodiment, the active main control unit may include a first version manager and a first active standby manager; the standby main control unit may include a second version manager and a second active standby manager, and each software on main control units may include a data recovery assembly; the line card may include a third version manager, and each software on the main control units and the line card may include a data recovery assembly.
  • The two stages included in the software upgrading method for a distributed communication device will be described as follows respectively, as shown in Fig. 1, the method includes below steps:
    • step S101, an active main control unit notifies a standby main control unit to launch a new version of a software and run said new version of the software in a standby state, and performs data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit.
  • Preferably, step S101 may include:
    • step A1, the active main control unit notifies the standby main control unit to launch the new version of the software on the standby main control unit; and
    • step A2, the data and data state recovery is performed on said new version of the software on the standby main control unit through the old version of the software on the active main control unit based on a data recovery assembly.
  • Step A1 specifically includes: the first version manager notifies the second version manager to launch the new version of the software on the standby main control unit.
  • Preferably, step A2 may include:
    • step A21, one or more communication links are established between the active main control unit and the standby main control unit through respective data recovery assemblies; and
    • step A22, the data and data state are synchronized to the new version of the software on the standby main control unit through the old version of the software on the active main control unit based on the data recovery assembly.
  • In this way, the data and data state synchronized from said new version of the software on the active main control unit are received through the new version of the software on the standby main control unit also based on the data recovery assembly.
  • Step S102, active/standby state inversion between the active main control unit and the standby main control unit is performed.
  • In this way, the standby main control unit having finished the software upgrading is enabled to enter an active running state, and the original active main control unit is enabled to enter a standby running state, on which the software is waiting to be upgraded.
  • Specifically, after the data and data state recovery is finished, the first version manager notifies the first active standby manager to change the running state of the active main control unit to the standby state, and the second version manager notifies the second active standby manager to change the running state of the standby main control unit to the active state.
  • Step S103, a current active main control unit notifies the line card to launch a new version of a software of a control plane and of a management plane and runs said new version of the software in a standby state, and performs the data and data state recovery on said new version of the software on the line card through the current active main control unit, or performs the data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card.
  • Specifically, after the active/standby state inversion between the active main control unit and the standby main control unit is finished, the third version manager launches said new version of the software of the control plane and of the management plane on the line card and run said new version of the software in a standby state; and after the data and data state recovery performed on the line card is finished, cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, and refreshes data of and a data state of a software of a forwarding plane;
    the data and data state recovery is performed on said new version of the software on the line card through the new version of the software of the current active main control unit based on a data recovery assembly, or the data and data state recovery is performed on said new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card based on the data recovery assembly.
  • In step S103, the processing that the data and data state recovery is performed on the new version of the software of the control plane and of the management plane on the line card through the current active main control unit includes:
    • step B1, one or more communication links are established between the current active main control unit and the line card based on the data recovery assembly; and
    • step B2, the data and data state are synchronized to the new version of the software of the control plane and of the management plane on the line card through the new version of the software on the current active main control unit based on the data recovery assembly.
  • Accordingly, the data and data state synchronized from the active main control unit are received through the new version of the software of the control plane and of the management plane on the line card based on the data recovery assembly.
  • In step S103, the processing that the data and data state recovery is performed on the new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card includes:
    • step C1, one or more communication links are established between the old version of the software of the control plane and of the management plane on the line card and the new version of the software on the line card; and
    • step C2, the data and data state are synchronized to the new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card.
  • Accordingly, the data and data state synchronized from the old version of the software of the control plane and of the management plane on the line card are received through the new version of the software of the control plane and of the management plane on the line card based on the data recovery assembly.
  • Step S104, after the data and data state recovery performed on the line card is finished, the line card cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, and refreshes the data of and the data state of the software of the forwarding plane.
  • Specifically, after the data and data state recovery performed on the line card is finished, the third version manager cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, and refreshes the data of and the data state of the software of the forwarding plane.
  • Preferably, before step S101, the method may further include:
    • the new version of the software is copied to a main control unit and the line card of the communication device; or the new version of the software is copied to the main control unit of the communication device, then the line card requests the main control unit for the new version of the software and upgrades it.
  • The main control unit herein refers to a main control unit in the active state, i.e., the active main control unit, since the standby main control unit does not provide services to the system.
  • An embodiment of the disclosure discloses a software upgrading method for a distributed communication device, which is applied to a software upgrading system for the distributed communication device that includes an active main control unit, a standby main control unit and a line card, and the method includes two stages: a first stage of a software upgrading process for main control units and a second stage of a software upgrading process for a line card, as shown in Fig. 2, the method includes below steps:
    • step S201, an active main control unit notifies a standby main control unit to launch a new version of a software and run said new version of the software in a standby state, and performs data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit.
  • Preferably, step S201 may include:
    • step A1: the active main control unit notifies the standby main control unit to launch the new version of the software on the standby main control unit; and
    • step A2, the data and data state recovery is performed on said new version of the software on the standby main control unit through the old version of the software on the active main control unit based on a data recovery assembly.
  • Step A1 specifically includes: the first version manager notifies the second version manager to launch the new version of the software on the standby main control unit.
  • Preferably, step A2 may include:
    • step A21, one or more communication links are established between the active main control unit and the standby main control unit through respective data recovery assemblies; and
    • step A22, the data and data state are synchronized to the new version of the software on the standby main control unit through the old version of the software on the active main control unit based on the data recovery assembly.
  • Step S202, active/standby state inversion between the active main control unit and the standby main control unit is performed.
  • In this way, the standby main control unit having finished the software upgrading is enabled to enter an active running state, and the original active main control unit is enabled to enter a standby running state, on which the software is waiting to be upgraded.
  • Specifically, after the data and data state recovery is finished, the first version manager notifies the first active standby manager to change the running state of the active main control unit to the standby state, and the second version manager notifies the second active standby manager to change the running state of the standby main control unit to the active state.
  • Step S203, after the active/standby state inversion between the active main control unit and the standby main control unit, said old version of the software on an original active main control unit is upgraded to the new version of the software and the new version of the software is run in the standby state.
  • Step S204, a current active main control unit notifies the line card to launch a new version of a software of a control plane and of a management plane and runs said new version of the software in a standby state, and performs the data and data state recovery on said new version of the software on the line card through the current active main control unit, or performs the data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card.
  • Specifically, after the active/standby state inversion between the active main control unit and the standby main control unit is finished, the third version manager launches said new version of the software of the control plane and of the management plane on the line card and run said new version of the software in a standby state; and after the data and data state recovery performed on the line card is finished, cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, and refreshes data of and a data state of a software of a forwarding plane;
    the data and data state recovery is performed on said new version of the software on the line card through the new version of the software of the current active main control unit based on a data recovery assembly, or the data and data state recovery is performed on said new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card based on the data recovery assembly.
  • Step S205, after the data and data state recovery performed on the line card is finished, the line card cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, upgrades the software of the forwarding plane on the line card, and refreshes the data of and the data state of the software of the forwarding plane.
  • Specifically, after the data and data state recovery performed on the line card is finished, the third version manager cancels said old version of the software of the control plane and of the management plane, runs said new version of the software of the control plane and of the management plane in the active state, upgrades the software of the forwarding plane on the line card, and refreshes the data of and the data state of the software of the forwarding plane.
  • The process of upgrading a software of the forwarding plane by the third version manager on the line card is similar to the process of upgrading the software of the control plane and of the management plane on the line card, the reason why the upgrading of the software of the forwarding plane comes last lies in that the function of the forwarding plane affects directly service operation of the communication device, upgrading firstly the software of the control plane and of the management plane on the line card will not result in interruption of the service; the process of upgrading the software of the forwarding plane also needs to follow the below procedures: an old version of the software of the forwarding plane is cancelled and a new version of the software of the forwarding plane is launched, a data and data state recovery is performed on the new version of the software of the forwarding plane on the line card through the new version of the software on the current active main control unit, the data of and the data state of the new version of the software of the forwarding plane are refreshed, so as to validate the entries of the forwarding table of the new version of the software of the forwarding plane. Time taken by upgrading the software of the forwarding plane is very short, which has little effect on service operation.
  • Preferably, before the step S201, the method may further include:
    • the new version of the software is copied to a main control unit and the line card of the communication device; or the new version of the software is copied to the main control unit of the communication device, then the line card requests the main control unit for the new version of the software.
  • The main control unit herein refers to a main control unit in the active state, i.e., the active main control unit, since the standby main control unit does not provide services to the system.
  • Embodiments of the disclosure further disclose a software upgrading system for a distributed communication device, as shown in Fig. 3, the system includes an active main control unit 10 including a standby main control unit 20 and a line card 30 based on physical redundancy;
    the active main control unit 20 is configured to notify the standby main control unit to launch a new version of a software, to perform data and data state recovery on said new version of the software on the standby main control unit 30 through an old version of the software on the active main control unit 20, and to change a running state of the active main control unit to a standby state after the data and data state recovery is finished.
  • The standby main control unit 30 is configured to launch said new version of the software and run the said new version of the software in a standby state, to cooperate with the active main control unit 20 to perform the data and data state recovery on said new version of the software, and to change a running state of the standby main control unit to an active state after the data and data state recovery is finished.
  • Preferably, the active main control unit 20 may include a first version manager 21 and a first active standby manager 22, the standby main control unit 30 may include a second version manager 31 and a second active standby manager 32, and each software on the active and standby main control units may include a data recovery assembly 11;
    the first version manager 21 is configured to notify the second version manager 31 to launch the new version of the software on the standby main control unit 30, and to, after the data and data state recovery is finished, notify the first active standby manager 22 to change the running state of the active main control unit 22 to a standby state so that the old version of the software enters a standby running state and waits to be upgraded;
    the data recovery assembly 11 is configured to perform, in the old version of the software on the active main control unit 20, the data and data state recovery on said new version of the software on the standby main control unit 30;
    the second version manager 31 is configured to launch the new version of the software on the standby main control unit 30, and to, after the data and data state recovery is finished, notify the second active standby manager 32 to change the running state of the standby main control unit 30 to the active state;
    the first active standby manager 22 is configured to perform the active/standby state inversion on the running state of the active main control unit 20; and
    the second active standby manager 32 is configured to perform the active/standby state inversion on the running state of the standby main control unit 30.
  • The line card 40 is configured to, after active/standby state inversion between the active main control unit 20 and the standby main control unit 30 is finished, launch a new version of a software of a control plane and of a management plane on the line card and run said new version of the software in a standby state, and to perform data and data state recovery on said new version of the software on the line card through a current active main control unit, or to perform data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card, and to, after the data and data state recovery performed on the line card is finished, cancel said old version of the software of the control plane and of the management plane, run said new version of the software of the control plane and of the management plane in the active state, and refresh data of and a data state of a software of a forwarding plane.
  • Preferably, the line card 40 may include a third version manager 41, and each software on the active and standby main control units and the line card may include a data recovery assembly.
  • The third version manager 41 is configured to, after the active/standby state inversion between the active main control unit 20 and the standby main control unit 30 is finished, launch said new version of the software of the control plane and of the management plane on the line card and run said new version of the software in a standby state; and to, after the data and data state recovery performed on the line card 40 is finished, cancel said old version of the software of the control plane and of the management plane, run said new version of the software of the control plane and of the management plane in the active state, and refresh the data of and the data state of the software of the forwarding plane;
    the data recovery assembly 11 is configured to perform, in the old version of the software on the active main control unit 20, the data and data state recovery i on said new version of the software on the line card 40, or the data and data state recovery is performed on said new version of the software on the line card 40 through the old version of the software of the control plane and of the management plane on the line card 40 based on the data recovery assembly 11.
  • An embodiment of the disclosure further discloses a software upgrading system for a distributed communication device, the software upgrading system for a distributed communication device is roughly the same as the software upgrading system for a distributed communication device shown in Fig. 3, and the difference lies in that in the system according to the embodiment,
    the active main control unit 20 is further configured to, after the active/standby state inversion between the active main control unit 20 and the standby main control unit 30 is finished, upgrade said old version of the software on an original active main control unit 20 to the new version of the software and run the new version of the software in the standby state.
  • In addition, the line card 40 is further configured to, after the data and data state recovery performed on the line card 40 is finished and before the data of and the data state of the software of the forwarding plane are refreshed, upgrade the software of the forwarding plane on the line card 40.
  • Preferably, the process of upgrading a software of the forwarding plane by the third version manager 41 on the line card 40 is similar to the process of upgrading the software of the control plane and of the management plane on the line card 40, the reason why the upgrading of the software of the forwarding plane comes last lies in that the function of the forwarding plane affects directly service operation of the communication device, upgrading firstly the software of the control plane and of the management plane on the line card 40 will not result in interruption of the service; the process of upgrading the software of the forwarding plane also needs to follow the below procedures: an old version of the software of the forwarding plane is cancelled and a new version of the software of the forwarding plane is launched, a data and data state recovery is performed on the new version of the software of the forwarding plane on the line card 40 through the new version of the software on the current active main control unit 20, the data of and the data state of the new version of the software of the forwarding plane are refreshed, so as to validate the entries of the forwarding table of the new version of the software of the forwarding plane. Time taken by upgrading the software of the forwarding plane is very short, which has little effect on service operation.
  • Based on the above embodiments, an application example of the disclosure is now described, the application scenario and implementation process of the application example are as follows.
  • Application scenario: upgrading of a software of an access gateway.
  • Fig. 4 is a sequence diagram showing interaction during software upgrading of a distributed access gateway, Fig. 5 to Fig. 10 show various states during the software upgrading of the distributed access gateway; the access gateway in the drawings is a distributed communication device for implementing access of users to a network, and for high reliability and high availability consideration, the access gateway is configured with active/standby main control panels; Fig. 5 shows a state before upgrading of the software of the distributed access gateway, a processing unit on the active control panel is a main controller 1 while a processing unit on the standby main control panel is a main controller 2. Furthermore, 4 line cards are configured in order to implement access of users and forwarding processing. There are 80 processes running on the main control unit, such as a supportive process, a Border Gateway Protocol (BGP) process, a Routing Information Protocol (RIP) process, an Open Shortest Path First (OSPF) process, a Forward Information Base (FIB) process and the like. There are 30 processes running on the line card, such as a packet transmission/reception process, a routing forwarding process, a user access process and the like. Since running software versions may have malfunctions, services may be interrupted randomly. Thus it is required to consider upgrading the version of a software so as to overcome device malfunctions. The four line cards of the access gateway are upgraded in a line card by line card way. That is to say, each line card is upgraded in sequence, line card 1 is upgraded first, then line card 2 is upgraded, and then line card 3 is upgraded, finally line card 4 is upgraded.
  • The upgrading of the version of the software of the access gateway relates to below assemblies: an old version of the software, a new version of the software, a version manager, and an active standby manager. Specifically, the old version of the software and the new version of the software implement a same function, the version manager takes charge of upgrading of the version of a software, failure rollback and the like, the active standby manager takes charge of active/standby management of new/old versions of a software, and triggering active/standby state inversion of the new version of the software after data and data state recovery from the old version to the new version of the software, so that the new version of the software can replace seamlessly the old version of the software, thereby implementing software upgrading without service interruption.
  • Processing steps for implementing, on a network, a software upgrading method for a distributed access gateway are as follows.
  • Stage 1, upgrading of a software of a main controller.
  • S1, before software upgrading, a new version of a software to which an old version of the software is to be upgraded needs to be copied to an active main controller of an access gateway (the device automatically copies it to a standby main controller); a new version of a software of the line card is acquired by request from the main controller;
  • S2, an old version of the software on a main controller 1 runs in an active state, a user sends a main controller software upgrading instruction to a Version Manager (VM) on the main controller 1;
  • S3, after receiving the main controller software upgrading instruction, the VM on the main controller 1 sends a command to a VM on the main controller 2, the old version of the software is upgraded to a new version of the software and the new version of the software is launched on the main controller 2, as shown in Fig. 6;
  • S4, after being launched, the new version of the software on the main controller 2 runs in a standby state; before running in the active state, the new version of the software on the main controller 2 does not provide service to the outside of the system;
  • S5, data and data state recovery is performed on the new version of the software on the main controller 2 through the old version of the software on the main controller 1, so that after entering a running state, the new version of the software can take over seamlessly the old version of the software to provide services to the outside; preferably, there may be one or more communication links for the data and data state recovery;
  • S6, after the data and data state recovery is finished, the new version of the software on the main controller 2 sends, through the VM on the main controller 2, a standby main controller new version launch completion notification to the VM on the main controller 1;
  • S7, after receiving the standby main controller new version launch completion notification, the VM on the main controller 1 triggers active/standby state inversion of the active main controller on an Active Standby Manager (ASM) on the main controller 1, as shown in Fig. 7. And the VM on the main controller 2 triggers active/standby state inversion of the standby main controller on an ASM on the main controller 2;
  • S8, the main controller 1 is changed to a new standby main controller, and the main controller 2 is changed to a new active main controller. A new version of the software on the new active main controller replaces the old version of the software and enters an active running state so as to provide service to the outside. The old version of the software on the new standby main controller does not provide services to the outside;
  • S9, preferably, as shown in Fig. 10, when the main controller 1 is changed to the new standby main controller, the old version of the software on the main controller 1 can be upgraded to a new version of the software and launched in the standby state; and
  • S10, the VM on the main controller 1 feeds a result of upgrading success back to the user, and indicates that subsequent upgrading of a software of the line card can be implemented.
  • Stage 2, upgrading of a software of a line card (upgrading is performed line card by line card, line card 1 is taken as an example to elaborate, other line cards have a same upgrading process).
  • S11, after the upgrading of the software of the main controller succeeds, the user sends a software upgrading instruction for the line card 1 to the VM of the main controller 2;
  • S12, after receiving the software upgrading instruction for the line card 1, the VM on the main controller 2 sends a line card software upgrading instruction to a VM on the line card 1;
  • S13, as shown in Fig. 7, after receiving the line card software upgrading instruction, the VM on the line card 1 acquires the new version of the software from the main controller 2, launches the new version of the software of the control plane and of the management plane on the line card and runs it in the standby state, and before being changed to the active state, the new version of the software of the control plane and of the management plane does not provide services to the outside;
  • S14, in order to avoid service interruption, before entering a running state, the new version of the software of the control plane and of the management plane on the line card 1 needs to recover data and data state required for providing services. For the new version of the software on the line card 1 of the access gateway, the data and data state recovery is implemented through multiple communication links;
  • S15, the data and data state recovery of the new version of software of the control plane and of the management plane on the line card 1 is performed by the main controller 2;
  • S16, after the data and data state recovery of the new version of software of the control plane and of the management plane on the line card 1 is finished, a data and data state synchronization completion notification is sent to the VM on the line card;
  • S17, after receiving the new version software recovery completion notification, the VM on the line card 1 sends a cancellation instruction to the old version of the software of the control plane and of the management plane on the line card 1. And the VM on the line card 1 sends an active/standby state inversion instruction to the new version of the software of the control plane and of the management plane on the line card 1;
  • S18, as shown in Fig. 8, after the reception of the cancellation instruction from the VM, the old version of the software of the control plane and of the management plane on the line card 1 is cancelled;
  • S19, as shown in Fig. 9, after the reception of the active/standby inversion instruction from the VM, active/standby state inversion is performed on the new version of the software of the control plane and of the management plane on the line card 1 so that the new version of the software replaces the old version of the software of the control plane and of the management plane and enters the running state;
  • S20, after the new version of the software of the control plane and of the management plane on the line card 1 enters the running state, a software of the forwarding plane is upgraded as required, and refreshing of a forwarding table is triggered so as to validate the entries of the forwarding table of a new version of the software.
  • S21, the VM on the line card 1 feeds a result of the upgrading of the software on the line card back to the main controller 2.
  • By description based on specific embodiments, technical means adopted by the disclosure for achieving predetermined objectives and beneficial effects should be understood more thoroughly and specifically, however, the drawings are designed solely for purposes of illustration and not as a definition of the limits of the invention.

Claims (10)

  1. A software upgrading method for a distributed communication device, applied to a software upgrading system for the distributed communication device that comprises an active main control unit, a standby main control unit and a line card, the method comprising:
    notifying, by the active main control unit, the standby main control unit to launch a new version of a software and run said new version of the software in a standby state, and performing data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit;
    performing active/standby state inversion between the active main control unit and the standby main control unit;
    launching, by the line card, a new version of a software of a control plane and of a management plane and running said new version of the software in a standby state, and performing data and data state recovery on said new version of the software on the line card through a current active main control unit, or performing data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card;
    cancelling, by the line card, said old version of the software of the control plane and of the management plane, and running said new version of the software of the control plane and of the management plane in an active state; and
    refreshing, by the line card, data of and a data state of a software of a forwarding plane.
  2. The software upgrading method for a distributed communication device according to claim 1, wherein the notifying, by the active main control unit, the standby main control unit to launch a new version of a software and run said new version of the software in a standby state, and performing data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit comprise:
    notifying, by the active main control unit, the standby main control unit to launch the new version of the software on the standby main control unit; and
    performing the data and data state recovery on said new version of the software on the standby main control unit through the old version of the software on the active main control unit based on a data recovery assembly.
  3. The software upgrading method for a distributed communication system according to claim 1, wherein the launching, by the line card, a new version of a software of a control plane and of a management plane and running said new version of the software in a standby state, and performing data and data state recovery on said new version of the software on the line card through a current active main control unit, or performing data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card comprise:
    after the active/standby state inversion between the active main control unit and the standby main control unit is finished, launching, by the line card, said new version of the software of the control plane and of the management plane on the line card and running said new version of the software in the standby state;
    performing the data and data state recovery on said new version of the software on the line card through a new version of a software of the current active main control unit based on a data recovery assembly, or performing the data and data state recovery on said new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card based on a data recovery assembly; and
    after the data and data state recovery performed on the line card is finished, cancelling, by the line card, said old version of the software of the control plane and of the management plane, running said new version of the software of the control plane and of the management plane in the active state, and refreshing the data of and the data state of the software of the forwarding plane.
  4. The software upgrading method for a distributed communication device according to claim 1, further comprising:
    after the data and data state recovery performed on the line card is finished and before the data of and the data state of the software of the forwarding plane are refreshed, upgrading the software of the forwarding plane on the line card.
  5. The software upgrading method for a distributed communication device according to any one of claims 1 to 4, further comprising:
    after the active/standby state inversion between the active main control unit and the standby main control unit is finished, upgrading said old version of the software on an original active main control unit to the new version of the software and running the new version of the software in the standby state.
  6. A software upgrading system for a distributed communication device, comprising an active main control unit, a standby main control unit and a line card, wherein
    the active main control unit is configured to notify the standby main control unit to launch a new version of a software, to perform data and data state recovery on said new version of the software on the standby main control unit through an old version of the software on the active main control unit, and to change a running state of the active main control unit to a standby state after the data and data state recovery is finished;
    the standby main control unit is configured to launch said new version of the software and run the said new version of the software in a standby state, to cooperate with the active main control unit to perform the data and data state recovery on said new version of the software, and to change a running state of the standby main control unit to an active state after the data and data state recovery is finished; and
    the line card is configured to, after active/standby state inversion between the active main control unit and the standby main control unit is finished, launch a new version of a software of a control plane and of a management plane on the line card and run said new version of the software in a standby state, and to perform data and data state recovery on said new version of the software on the line card through a current active main control unit, or to perform data and data state recovery on said new version of the software on the line card through an old version of the software of the control plane and of the management plane on the line card, and to, after the data and data state recovery performed on the line card is finished, cancel said old version of the software of the control plane and of the management plane, run said new version of the software of the control plane and of the management plane in the active state, and refresh data of and a data state of a software of a forwarding plane.
  7. The software upgrading system for a distributed communication device according to claim 6, wherein the active main control unit comprises a first version manager and a first active standby manager, the standby main control unit comprises a second version manager and a second active standby manager, and each software on the active and standby main control units comprises a data recovery assembly;
    wherein the first version manager is configured to notify the second version manager to launch the new version of the software on the standby main control unit, and to, after the data and data state recovery is finished, notify the first active standby manager to change the running state of the active main control unit to a standby state;
    the second version manager is configured to launch the new version of the software on the standby main control unit, and to, after the data and data state recovery is finished, notify the second active standby manager to change the running state of the standby main control unit to the active state;
    the first active standby manager is configured to perform the active/standby state inversion on the running state of the active main control unit; and
    the second active standby manager is configured to perform the active/standby state inversion on the running state of the standby main control unit;
    wherein the data and data state recovery is performed on said new version of the software on the standby main control unit through the old version of the software on the active main control unit based on the data recovery assembly of the active main control unit.
  8. The software upgrading system for a distributed communication device according to claim 6, wherein the line card comprises a third version manager, and each software on the active and standby main control units and the line card comprises a data recovery assembly;
    wherein the third version manager is configured to, after the active/standby state inversion between the active main control unit and the standby main control unit is finished, launch said new version of the software of the control plane and of the management plane on the line card and run said new version of the software in a standby state; and to, after the data and data state recovery performed on the line card is finished, cancel said old version of the software of the control plane and of the management plane, run said new version of the software of the control plane and of the management plane in the active state, and refresh the data of and the data state of the software of the forwarding plane;
    wherein the data and data state recovery is performed on said new version of the software on the line card through the current active main control unit based on the data recovery assembly of the current active main control unit, or the data and data state recovery is performed on said new version of the software on the line card through the old version of the software of the control plane and of the management plane on the line card based on the data recovery assembly of the line card.
  9. The software upgrading system for a distributed communication device according to claim 6, wherein the line card is further configured to, after the data and data state recovery performed on the line card is finished and before the data of and the data state of the software of the forwarding plane are refreshed, upgrade the software of the forwarding plane on the line card.
  10. The software upgrading system for a distributed communication device according to any one of claims 6 to 9, wherein the active main control unit is further configured to, after the active/standby state inversion between the active main control unit and the standby main control unit is finished, upgrade said old version of the software on an original active main control unit to the new version of the software and run the new version of the software in the standby state.
EP13851276.9A 2012-11-01 2013-08-27 Method and system for upgrading software of distributed communication device Active EP2916488B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210428526.0A CN102937925B (en) 2012-11-01 2012-11-01 A kind of distributed communication equipment method for upgrading software and system
PCT/CN2013/082411 WO2014067330A1 (en) 2012-11-01 2013-08-27 Method and system for upgrading software of distributed communication device

Publications (3)

Publication Number Publication Date
EP2916488A1 true EP2916488A1 (en) 2015-09-09
EP2916488A4 EP2916488A4 (en) 2015-11-25
EP2916488B1 EP2916488B1 (en) 2019-04-10

Family

ID=47696824

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13851276.9A Active EP2916488B1 (en) 2012-11-01 2013-08-27 Method and system for upgrading software of distributed communication device

Country Status (3)

Country Link
EP (1) EP2916488B1 (en)
CN (1) CN102937925B (en)
WO (1) WO2014067330A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3304282A4 (en) * 2015-06-05 2019-02-27 Shell International Research Maatschappij B.V. System and method for replacing a live control/estimation application with a staged application
US10326653B2 (en) 2014-11-12 2019-06-18 Huawei Technologies Co., Ltd. Method for upgrading network functions virtualization application, service forwarding method, and apparatus
KR20210034648A (en) * 2018-09-05 2021-03-30 지티이 코포레이션 Cross-version upgrade method, apparatus and device, computer-readable storage medium
EP4198712A1 (en) * 2022-12-16 2023-06-21 Pfeiffer Vacuum Technology AG Vacuum system and method for operating same

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102937925B (en) * 2012-11-01 2015-08-12 中兴通讯股份有限公司 A kind of distributed communication equipment method for upgrading software and system
CN104486394B (en) * 2014-12-10 2018-01-12 新华三技术有限公司 In-service Software Upgrade method and device
CN107580322A (en) * 2017-08-28 2018-01-12 驭势科技(北京)有限公司 Upgrade method, device and the automatic driving vehicle of automatic driving vehicle software systems
CN109728886A (en) * 2017-10-27 2019-05-07 中兴通讯股份有限公司 A kind of method of data synchronization, device, equipment and storage medium suitable for cross-version upgrading
CN108170464A (en) * 2017-12-27 2018-06-15 联想(北京)有限公司 A kind of version upgrading method, service platform and electronic equipment
US11706162B2 (en) * 2019-10-21 2023-07-18 Sap Se Dynamic, distributed, and scalable single endpoint solution for a service in cloud platform
CN111490935B (en) * 2020-03-31 2022-05-27 新华三信息安全技术有限公司 Information synchronization method, forwarding unit and control unit in distributed architecture
CN114553860B (en) * 2022-02-18 2024-07-23 深圳海星智驾科技有限公司 OTA upgrading method and device and electronic equipment

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6898189B1 (en) * 2000-08-23 2005-05-24 Cisco Technology, Inc. Restartable spanning tree for high availability network systems
US7177919B1 (en) * 2000-11-28 2007-02-13 Cisco Technology, Inc. Method and system for controlling tasks on network cards
US8806472B2 (en) * 2007-09-27 2014-08-12 Ericsson Ab In-service software upgrade utilizing metadata-driven state translation
CN101383724B (en) * 2008-08-29 2011-04-13 上海华为技术有限公司 Network updating method and operation maintaining element, and network element updating system
CN102195845B (en) * 2010-03-03 2015-01-14 杭州华三通信技术有限公司 Method, device and equipment for realizing active-standby switching of main control board
US8495418B2 (en) * 2010-07-23 2013-07-23 Brocade Communications Systems, Inc. Achieving ultra-high availability using a single CPU
US8402454B2 (en) * 2010-09-22 2013-03-19 Telefonaktiebolaget L M Ericsson (Publ) In-service software upgrade on cards of virtual partition of network element that includes directing traffic away from cards of virtual partition
CN102081540B (en) * 2011-01-18 2014-04-16 杭州华三通信技术有限公司 Distributed dual-master control network equipment software updating method and device
CN102937925B (en) * 2012-11-01 2015-08-12 中兴通讯股份有限公司 A kind of distributed communication equipment method for upgrading software and system

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10326653B2 (en) 2014-11-12 2019-06-18 Huawei Technologies Co., Ltd. Method for upgrading network functions virtualization application, service forwarding method, and apparatus
EP3304282A4 (en) * 2015-06-05 2019-02-27 Shell International Research Maatschappij B.V. System and method for replacing a live control/estimation application with a staged application
KR20210034648A (en) * 2018-09-05 2021-03-30 지티이 코포레이션 Cross-version upgrade method, apparatus and device, computer-readable storage medium
EP4198712A1 (en) * 2022-12-16 2023-06-21 Pfeiffer Vacuum Technology AG Vacuum system and method for operating same

Also Published As

Publication number Publication date
CN102937925B (en) 2015-08-12
WO2014067330A1 (en) 2014-05-08
EP2916488B1 (en) 2019-04-10
CN102937925A (en) 2013-02-20
EP2916488A4 (en) 2015-11-25

Similar Documents

Publication Publication Date Title
EP2916488B1 (en) Method and system for upgrading software of distributed communication device
EP2916228A1 (en) Method and system for upgrading software of distributed communication device
US10545750B2 (en) Distributed upgrade in virtualized computing environments
US10404579B1 (en) Virtual machine instance migration using a hypervisor
US9954725B2 (en) Redundant storage solution
US10983880B2 (en) Role designation in a high availability node
US9992058B2 (en) Redundant storage solution
US9141502B2 (en) Method and system for providing high availability to computer applications
EP2816467B1 (en) Method and device for checkpoint and restart of container state
EP2619662B1 (en) In-service software upgrade of control and line cards of network element
CN108075971B (en) Main/standby switching method and device
EP2916487B1 (en) Method and system for upgrading patching software
JP6431197B2 (en) Snapshot processing methods and associated devices
US20200145284A1 (en) Validating Network Configuration Using Shadow Databases
US20080183878A1 (en) System And Method For Dynamic Patching Of Network Applications
CN108984334B (en) Method and apparatus for managing sessions
US20150288612A1 (en) Socket state transfer
US9706440B2 (en) Mobile communication system, call processing node, and communication control method
US10021171B2 (en) Zero-downtime cloud connector upgrades
JP2015032301A (en) Version update method for virtual host and network equipment
US9647881B2 (en) Managing a network connection of a switch
US20200236059A1 (en) Systems and methods for acquiring server resources at schedule time
CN111698142B (en) Message forwarding method and device, electronic equipment and storage medium
CN105939205B (en) A kind of configuration rollback method and device
WO2016001772A1 (en) Synchronizing operations between regions when a network connection fails

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20150601

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20151027

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/24 20060101AFI20151021BHEP

Ipc: G06F 9/445 20060101ALI20151021BHEP

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 9/445 20060101ALI20181031BHEP

Ipc: H04L 12/24 20060101AFI20181031BHEP

Ipc: G06F 8/656 20150909ALI20181031BHEP

INTG Intention to grant announced

Effective date: 20181121

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 9/445 20180101ALI20181031BHEP

Ipc: H04L 12/24 20060101AFI20181031BHEP

Ipc: G06F 8/656 20180101ALI20181031BHEP

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 8/656 20180101ALI20181031BHEP

Ipc: G06F 9/445 20180101ALI20181031BHEP

Ipc: H04L 12/24 20060101AFI20181031BHEP

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1120184

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190415

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602013053844

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20190410

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1120184

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190910

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190710

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190711

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190710

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190810

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602013053844

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

26N No opposition filed

Effective date: 20200113

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20190827

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190831

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190831

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190827

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20190831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190827

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190831

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190827

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20130827

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602013053844

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012240000

Ipc: H04L0041000000

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230703

Year of fee payment: 11