CN113300878B - Method and device for realizing data smoothing - Google Patents

Method and device for realizing data smoothing Download PDF

Info

Publication number
CN113300878B
CN113300878B CN202110391877.8A CN202110391877A CN113300878B CN 113300878 B CN113300878 B CN 113300878B CN 202110391877 A CN202110391877 A CN 202110391877A CN 113300878 B CN113300878 B CN 113300878B
Authority
CN
China
Prior art keywords
bras
user data
address
interface
configuration instruction
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.)
Active
Application number
CN202110391877.8A
Other languages
Chinese (zh)
Other versions
CN113300878A (en
Inventor
熊志欢
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.)
Beijing H3C Technologies Co Ltd
Original Assignee
Beijing H3C Technologies Co Ltd
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 Beijing H3C Technologies Co Ltd filed Critical Beijing H3C Technologies Co Ltd
Priority to CN202110391877.8A priority Critical patent/CN113300878B/en
Publication of CN113300878A publication Critical patent/CN113300878A/en
Application granted granted Critical
Publication of CN113300878B publication Critical patent/CN113300878B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality

Abstract

The application provides a method and a device for realizing data smoothing, wherein the method comprises the following steps: when a first BRAS vm is in a MAD state, receiving a first configuration instruction sent by a second BRAS vm; configuring other interfaces except the first interface included in the first BRAS vm into an MAD down state according to a first configuration instruction; sending a user data request message to an RMDB through a first interface; receiving a user data response message sent by the RMDB through a first interface, wherein the user data response message comprises user data required by a first BRAS vm; if the user data is recovered in the first BRAS vm, a first notification message is sent to a second BRAS vm; receiving a second configuration instruction sent by a second BRAS vm; and configuring other interfaces into an up state according to the second configuration instruction, and upgrading the first BRAS vm into the master equipment.

Description

Method and device for realizing data smoothing
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing data smoothing.
Background
The Broadband Access Server (BRAS) is a novel Access gateway for Broadband network application, is located at the edge layer of a backbone network, can complete data Access of an IP/ATM network of a user bandwidth, and can be used for Broadband Internet Access of commercial buildings and residential quarters, establishing an Intranet (Intranet), supporting Internet Service providers (Internet Service Provider, ISP for short) to wholesale services to users, and the like.
The BRAS mainly realizes two service functions, namely a network bearing function and a user connection and convergence flow function; and the second is a control realization function which is matched with an authentication system, a charging system, a client management system and a service strategy control system to realize the authentication, charging and management functions of user access.
The BRAS equipment has the problems of high manufacturing cost, low resource utilization rate, incapability of multiplexing, slow update and the like. With the development of network virtualization technology, virtualization processing is performed on BRAS equipment, and an X86 server is used to implement a BRAS equipment network function, so that a vrbras (or called a BRAS virtual machine (vm for short)) is developed accordingly.
The cost and the operation and maintenance advantages are obvious because a plurality of BRAS vm can be flexibly created and deployed on the X86 server. Gradually, BRAS vm only implements control plane traffic, i.e. authentication, charging, and other service policies, in an access network, and forwarding or user plane traffic is processed by other devices, implementing transfer control separation.
In practical networking, two BRAS vm are generally configured as a stacked system, that is, a master and a slave are formed between each other. As shown in fig. 1, fig. 1 is a schematic diagram of a plurality of BRAS vm installed in a Control Plane (CP) device in the prior art. In fig. 1, a User Plane (UP) device accesses a User network and forwards User traffic. A plurality of BRAS vm are arranged in the CP equipment, each BRAS vm is connected with a switch through a plurality of channels, and the switch is connected with a Remote Management Database (RMDB).
The solid line connection between the BRAS vm and the switch is a control channel, and the dotted line connection between the BRAS vm and the switch is a data channel. The control channel is used for transmitting protocol messages, such as stack messages and the like, so as to ensure the formation of a stack system between the BRAS vm; the data channel is used for transmitting data services and is connected with the RMDB. The BRAS vm backs up the user data in time to the RMDB. If a BRAS vm is abnormal or restarted, another BRAS vm in the same stacking system with the BRAS vm can recover user data from the RMDB, thereby avoiding service interruption and realizing minimum service loss.
In one case, in fig. 1, a stacked Intelligent Resilient Framework (IRF) system is formed between BRAS vm1 and BRAS vm 2. Suppose BRAS vm2 is a master device and BRAS vm1 is a standby device. When incompatible version upgrading, the BRAS vm1 firstly executes version upgrading operation, after the BRAS vm1 finishes the version upgrading, the BRAS vm2 sets all interfaces of the BRAS vm1 to be in a Multi-activity Detection (MAD) closing (down) state, namely all the interfaces of the BRAS vm1 are not communicated with the outside, and therefore the BRAS vm1 cannot recover user data from an RMDB and cannot perform service processing on newly-on-line users. Although the BRAS vm2 can still normally process the service at this time, when the BRAS vm2 performs the version upgrading operation and restarts, the BRAS vm2 releases the MAD down state of the BRAS vm1, and all the interfaces of the BRAS vm1 are updated to the on (up) state. BRAS vm1 may recover the user data from the RMDB and begin to take over BRAS vm2 for traffic handling of the user.
However, the incompatible version upgrade process cannot realize smooth processing of services because of the following points: 1) For a stacking system, a No. 3 interface of a BRAS vm2 and a No. 2 interface of a BRAS vm1 have the same three-layer address, so when the BRAS vm1 is in an MAD down state, the No. 2 interface cannot be updated to an up state, and if the No. 2 interface is in the up state, the three-layer address of the interface is the same as the three-layer address of the No. 3 interface, so that address conflict is caused; 2) The BRAS vm1 needs a large amount of time to recover the user data from the RMDB, the data recovery time is close to the 'minute' level, and the overlong data recovery time affects the service processing of the online user, so that the online user is offline and the user traffic is affected.
To sum up, for the existing incompatible version upgrade, in the MAD down state, the interface No. 2 of the BRAS vm1 cannot be updated to the up state, so that much time is wasted when the BRAS vm1 is in the MAD down state, and meanwhile, time for the BRAS vm1 to recover user data from the RMDB is wasted, which causes the online user to be offline and affects the user traffic.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for implementing data smoothing, so as to solve the problem that the user traffic is affected due to the fact that the user data is recovered from the RMDB by the BRAS vm in incompatible version upgrade, which results in the offline of the on-line user.
In a first aspect, the present application provides a method for implementing data smoothing, where the method is applied to a first BRAS vm, where the first BRAS vm includes a first interface, and is in an MAD state after performing incompatible version upgrade, and the method includes:
when the first BRAS vm is in the MAD state, receiving a first configuration instruction sent by a second BRAS vm;
configuring other interfaces except the first interface included in the first BRAS vm into an MAD down state according to the first configuration instruction;
sending a user data request message to an RMDB through the first interface, wherein the user data request message comprises user data required by the first BRAS vm;
receiving a user data response message sent by the RMDB through the first interface, wherein the user data response message comprises user data required by the first BRAS vm, so that the user data is recovered in the first BRAS vm;
if the user data is recovered in the first BRAS vm, sending a first notification message to the second BRAS vm, so that the second BRAS vm executes incompatible version upgrading and is degraded into standby equipment;
receiving a second configuration instruction sent by the second BRAS vm;
and configuring the other interfaces into an up state according to the second configuration instruction, and upgrading the first BRAS vm into a master device.
In a second aspect, the present application provides an apparatus for implementing data smoothing, where the apparatus is applied to a first BRAS vm, where the first BRAS vm includes a first interface, and is in an MAD state after performing an incompatible version upgrade, and the apparatus includes:
the receiving unit is used for receiving a first configuration instruction sent by a second BRAS vm when the first BRAS vm is in the MAD state;
a configuration unit, configured to configure, according to the first configuration instruction, the other interfaces, except the first interface, included in the first BRAS vm to be in an MAD down state;
a sending unit, configured to send a user data request packet to an RMDB through the first interface, where the user data request packet includes user data required by the first BRAS vm;
the receiving unit is further configured to receive, through the first interface, a user data response packet sent by the RMDB, where the user data response packet includes user data required by the first BRAS vm, so that the user data is recovered in the first BRAS vm;
the sending unit is further configured to send a first notification message to the second BRAS vm if the user data is recovered in the first BRAS vm, so that the second BRAS vm executes incompatible version upgrade and downgrades the second BRAS vm to a standby device;
the receiving unit is further configured to receive a second configuration instruction sent by the second BRAS vm;
and the configuration unit is further used for configuring the other interfaces to an up state according to the second configuration instruction and upgrading the first BRAS vm to a master device.
In a third aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to perform the method provided by the first aspect of the present application.
Therefore, by applying the method and the device for realizing data smoothing provided by the application, when the first BRAS vm is in the MAD state, the first BRAS vm receives the first configuration instruction sent by the second BRAS vm. According to the first configuration instruction, the first BRAS vm configures other interfaces except the first interface included in the first BRAS vm into an MAD down state. Through the first interface, the first BRAS vm sends a user data request message to the RMDB, where the user data request message includes user data required by the first BRAS vm. Through the first interface, the first BRAS vm receives a user data response message sent by the RMDB, wherein the user data response message includes user data required by the first BRAS vm, so that the user data is recovered in the first BRAS vm. If the user data is recovered in the first BRAS vm, the first BRAS vm sends a first notification message to the second BRAS vm, so that the second BRAS vm executes incompatible version upgrading and downgrades the second BRAS vm to a standby device. And the first BRAS vm receives a second configuration instruction sent by the second BRAS vm. And according to the second configuration instruction, the first BRAS vm configures other interfaces to be in an up state, and upgrades the first BRAS vm to the main equipment.
Thus, the first BRAS vm sends a user data request message to the RMDB through the first interface in the up state, and receives user data sent by the RMDB through the first interface. If the user data is recovered in the first BRAS vm, the second BRAS vm executes the incompatible version upgrade and downgrades to the standby equipment at the moment. The first BRAS vm is upgraded as a master. The problem that the BRAS vm wastes time for recovering user data from the RMDB in incompatible version upgrading, so that an online user is offline and user flow is influenced is solved. The method and the device realize the minimum shortening of the time influencing the service under the condition of incompatible version upgrading, and avoid the problems of user offline or user flow loss to the maximum extent.
Drawings
Fig. 1 is a schematic diagram of setting multiple BRAS vm in a CP device in the prior art;
fig. 2 is a flowchart of a method for implementing data smoothing according to an embodiment of the present application;
fig. 3 is a schematic diagram of setting multiple BRAS vm in a CP device according to an embodiment of the present application;
fig. 4 is a structural diagram of an apparatus for implementing data smoothing according to an embodiment of the present application;
fig. 5 is a hardware structure of a network device according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the exemplary embodiments below do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the corresponding listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at" \8230; "or" when 8230; \8230; "or" in response to a determination ", depending on the context.
The following describes in detail a method for implementing data smoothing provided in the embodiments of the present application. Referring to fig. 2, fig. 2 is a flowchart of an implementation method of data smoothing provided in an embodiment of the present application. The method is applied to the first BRAS vm, and the method for implementing data smoothing provided by the embodiment of the application can include the following steps.
Step 210, when the first BRAS vm is in the MAD state, receiving a first configuration instruction sent by a second BRAS vm.
Specifically, as shown in fig. 3, fig. 3 is a schematic diagram of setting a plurality of BRAS vm in the CP device provided in the embodiment of the present application. In fig. 3, the UP device accesses the user network and forwards user traffic. And a plurality of BRAS vm are arranged in the CP equipment, each BRAS vm is connected with the switch through a plurality of channels, and the switch is connected with the RMDB.
The solid line connection between the BRAS vm and the switch is a control channel, the dotted line connection between the BRAS vm and the switch is a data channel, and the point break connection between the BRAS vm and the switch is a backup channel. The control channel is used for transmitting protocol messages, such as stack messages and the like, so as to ensure the formation of a stack system between the BRAS vm; the data channel is used for transmitting data services and is connected with the RMDB, and the BRAS vm backs up user data to the RMDB in time; the backup tunnels are used for BRAS vm in MAD down state to restore user data from RMDB through the switch.
The BRAS vm includes a backup interface (also referred to as a first interface, which is described below as an example) through which the BRAS vm establishes a backup tunnel with the switch.
In the embodiment of the application, BRAS vm1 (also called as a first BRAS vm) and BRAS vm2 (also called as a second BRAS vm) form an IRF system in CP equipment. The BRAS vm2 is a main device, the BRAS vm1 is a standby device, and the main device processes service flow sent by a user side.
When incompatible version upgrading, BRAS vm1 executes version upgrading operation first, and after the BRAS vm1 finishes the version upgrading, the BRAS vm1 sets the BRAS vm1 to be in the MAD state and sends a notification message to the BRAS vm2 to notify the BRAS vm2 that the BRAS vm2 finishes the version upgrading operation.
And the BRAS vm2 generates a first configuration instruction and sends the first configuration instruction to the BRAS vm1, and the BRAS vm1 receives the first configuration instruction.
Step 220, configuring other interfaces except the first interface included in the first BRAS vm into an MAD down state according to the first configuration instruction.
Specifically, according to the description of step 210, after receiving the first configuration instruction, the BRAS vm1 configures the other interfaces, except the first interface, included in itself in the MAD down state according to the first configuration instruction. That is, BRAS vm2 sets all the other interfaces of BRAS vm1 except the first interface to the MAD down state, that is, BRAS vm1 only can communicate with the outside world at present, and all the other interfaces cannot communicate with the outside world.
Step 230, sending a user data request message to the RMDB through the first interface, where the user data request message includes an identifier of the user data required by the first BRAS vm.
Specifically, BRAS vm1 pre-recovers user data from RMDB, as described in step 220. The BRAS vm1 generates a user data request message, wherein the user data request message comprises an identifier of user data required by the first BRAS vm.
Through the first interface, the BRAS vm1 sends a user data request message to the switch. And after receiving the user data request message, the switch sends the user data request message to the RMDB.
Step 240, receiving a user data response message sent by the RMDB through the first interface, where the user data response message includes user data required by the first BRAS vm, so as to recover the user data in the first BRAS vm.
Specifically, according to the description of step 230, after receiving the user data request message, the RMDB obtains the identifier of the user data required by the BRAS vm1 from the user data request message. And according to the identification of the user data, the RMDB acquires the user data matched with the identification from a database.
The RMDB generates a user data response message which comprises the user data required by the BRAS vm1 so that the BRAS vm1 can locally recover the user data.
The RMDB sends a user data response message to the switch. And after receiving the user data response message, the switch sends the user data response message to the BRAS vm1 through the backup channel.
Through the first interface, the BRAS vm1 receives the user data response message.
Step 250, if the user data is recovered in the first BRAS vm, sending a first notification message to the second BRAS vm, so that the second BRAS vm executes incompatible version upgrade, and downgrads the second BRAS vm to a standby device.
Specifically, according to the description of step 240, after receiving the user data response message, BRAS vm1 obtains the user data required by BRAS vm1 from the user data response message. BRAS vm1 locally recovers user data.
BRAS vm1 determines whether the user data is recovered locally successfully. If the user data is recovered in the BRAS vm1, the BRAS vm1 generates a first notification message. BRAS vm1 sends a first notification message to BRAS vm 2.
After receiving the first notification message, the BRAS vm2 determines that the BRAS vm1 has completed the incompatible version upgrade, and the BRAS vm1 has completed the user data recovery. BRAS vm2 performs incompatible version upgrades and downgrades itself to a standby device.
And step 260, receiving a second configuration instruction sent by the second BRAS vm.
Specifically, according to the description of step 250, BRAS vm2 performs incompatible version upgrade, and after downgrading itself to the standby device, BRAS vm2 generates a second configuration instruction.
BRAS vm2 sends a second configuration instruction to BRAS vm 1.
And step 270, configuring the other interfaces to an up state according to the second configuration instruction, and upgrading the first BRAS vm to a master device.
Specifically, according to the description of step 260, after receiving the second configuration instruction, BRAS vm1 configures other interfaces of itself except the first interface into the up state according to the second configuration instruction, and upgrades itself to the master device. BRAS vm1 takes over traffic flow for subscribers in BRAS vm 2.
Therefore, by applying the method and the device for realizing data smoothing provided by the application, when the first BRAS vm is in the MAD state, the first BRAS vm receives the first configuration instruction sent by the second BRAS vm. According to the first configuration instruction, the first BRAS vm configures other interfaces except the first interface included in the first BRAS vm into an MAD down state. Through the first interface, the first BRAS vm sends a user data request message to the RMDB, where the user data request message includes user data required by the first BRAS vm. Through the first interface, the first BRAS vm receives a user data response message sent by the RMDB, wherein the user data response message includes user data required by the first BRAS vm, so that the user data is recovered in the first BRAS vm. If the user data is recovered in the first BRAS vm, the first BRAS vm sends a first notification message to the second BRAS vm, so that the second BRAS vm executes incompatible version upgrading and is degraded into standby equipment. The first BRAS vm receives a second configuration instruction sent by a second BRAS vm. And according to the second configuration instruction, the first BRAS vm configures other interfaces to be in an up state, and upgrades the first BRAS vm to the main equipment.
In this way, the first BRAS vm sends a user data request message to the RMDB through the first interface in the up state, and receives user data sent by the RMDB through the first interface. If the user data is recovered in the first BRAS vm, the second BRAS vm executes the incompatible version upgrade and downgrades to the standby equipment at the moment. The first BRAS vm is upgraded as a master. The problem that BRAS vm wastes time for recovering user data from RMDB in incompatible version upgrading, so that an online user is offline and user traffic is influenced is solved. The method and the device realize the minimum shortening of the time influencing the service under the condition of incompatible version upgrading, and avoid the problems of user offline or user flow loss to the maximum extent.
Optionally, in this embodiment of the application, the address of the first interface included in the BRAS vm1 is a first IP address, the BRAS vm2 includes a second interface having a second IP address, and the first IP address is different from the second IP address.
It can be understood that each BRAS vm includes a backup interface, and through the backup interface, each BRAS vm respectively adds a backup channel with the switch. The IP addresses of the backup interfaces included in each BRAS vm are different, so that when a BRAS vm is in the MAD state, its backup interface is not set to down, and no address conflict with other BRAS vms occurs. The BRAS vm may also recover user data from the RMDB.
Optionally, in this embodiment of the present application, when the first IP address is the same as the second IP address, the first configuration instruction further includes a third IP address, and before the step 230 sends the user data request packet to the RMDB through the first interface, the method further includes the following steps:
according to a third IP address included by the first configuration instruction, the BRAS vm1 updates the first IP address to the third IP address, wherein the third IP address is different from the second IP address.
Optionally, in an embodiment of the present application, the method further includes the following steps:
if the user data is not recovered in the BRAS vm1, the BRAS vm1 judges whether to continue recovering the user data. If the BRAS vm1 continues to recover the user data, the BRAS vm1 sends a second notification message to the BRAS vm2, so that the BRAS vm2 does not execute incompatible version upgrading and continues to process user services.
If the BRAS vm1 does not continue to recover the user data, the BRAS vm1 sends a third notification message to the BRAS vm2, so that the BRAS vm2 executes incompatible version upgrading, and the BRAS vm2 is degraded into standby equipment.
And the BRAS vm2 generates a third configuration instruction and sends the third configuration instruction to the BRAS vm 1. According to the third configuration instruction, the BRAS vm1 configures other interfaces to be in the up state, and upgrades the BRAS vm1 to the main equipment. Thus, BRAS vm1 takes over traffic for the subscriber in BRAS vm 2.
Based on the same inventive concept, the embodiment of the application also provides a device for realizing data smoothing corresponding to the method for realizing data smoothing. Referring to fig. 4, fig. 4 is a structural diagram of an apparatus for implementing data smoothing according to an embodiment of the present application. The apparatus is applied to a first BRAS vm applied to the apparatus, the first BRAS vm includes a first interface, the first BRAS vm is in a MAD state after performing incompatible version upgrade, the apparatus includes:
a receiving unit 410, configured to receive a first configuration instruction sent by a second BRAS vm when the first BRAS vm is in the MAD state;
a configuration unit 420, configured to configure, according to the first configuration instruction, the other interfaces included in the first BRAS vm except the first interface to be in an MAD down state;
a sending unit 430, configured to send a user data request packet to an RMDB through the first interface, where the user data request packet includes an identifier of user data required by the first BRAS vm;
the receiving unit 410 is further configured to receive, through the first interface, a user data response packet sent by the RMDB, where the user data response packet includes user data required by the first BRAS vm, so that the user data is recovered in the first BRAS vm;
the sending unit 430 is further configured to send a first notification message to the second BRAS vm if the user data is recovered in the first BRAS vm, so that the second BRAS vm executes incompatible version upgrade and downgrades the second BRAS vm to a standby device;
the receiving unit 410 is further configured to receive a second configuration instruction sent by the second BRAS vm;
the configuration unit 420 is further configured to configure the other interfaces in an up state according to the second configuration instruction, and upgrade the first BRAS vm to a master device.
Optionally, the address of the first interface is a first IP address, the second BRAS vm includes a second interface with a second IP address, and the first IP address is different from the second IP address.
Optionally, when the first IP address is the same as the second IP address, the first configuration instruction further includes a third IP address, and the apparatus further includes:
an updating unit (not shown in the figure) is configured to update the first IP address to the third IP address, where the third IP address is different from the second IP address.
Optionally, the apparatus further comprises:
a judging unit (not shown in the figure) for judging whether to continue to recover the user data if the user data is not recovered in the first BRAS vm;
the sending unit 430 is further configured to send a second notification message to the second BRAS vm if the user data continues to be recovered, so that the second BRAS vm does not perform incompatible version upgrade, and continues to process a user service.
Optionally, the sending unit 430 is further configured to send a third notification message to the second BRAS vm if the user data is not continuously recovered, so that the second BRAS vm performs incompatible version upgrade and is downgraded to a standby device;
the receiving unit 410 is further configured to receive a third configuration instruction sent by the second BRAS vm;
the configuration unit 420 is further configured to configure the other interfaces to an up state according to the third configuration instruction, and upgrade the first BRAS vm to a master device.
Therefore, by applying the method and the device for realizing data smoothing provided by the application, when the first BRAS vm is in the MAD state, the first BRAS vm receives the first configuration instruction sent by the second BRAS vm. According to the first configuration instruction, the first BRAS vm configures other interfaces except the first interface included in the first BRAS vm into an MAD down state. Through the first interface, the first BRAS vm sends a user data request message to the RMDB, where the user data request message includes user data required by the first BRAS vm. Through the first interface, the first BRAS vm receives a user data response message sent by the RMDB, wherein the user data response message comprises user data required by the first BRAS vm, so that the user data is recovered in the first BRAS vm. If the user data is recovered in the first BRAS vm, the first BRAS vm sends a first notification message to the second BRAS vm, so that the second BRAS vm executes incompatible version upgrading and is degraded into standby equipment. And the first BRAS vm receives a second configuration instruction sent by the second BRAS vm. And according to the second configuration instruction, the first BRAS vm configures other interfaces to be in an up state, and upgrades the first BRAS vm to the main equipment.
In this way, the first BRAS vm sends a user data request message to the RMDB through the first interface in the up state, and receives user data sent by the RMDB through the first interface. If the user data is recovered in the first BRAS vm, the second BRAS vm executes the incompatible version upgrade and downgrades to the standby equipment at this moment. The first BRAS vm is upgraded to the primary device. The problem that BRAS vm wastes time for recovering user data from RMDB in incompatible version upgrading, so that an online user is offline and user traffic is influenced is solved. The method and the device realize that the time influencing the service is shortened to the minimum under the condition of incompatible version upgrading, and the problem of user offline or user flow loss is avoided to the maximum extent.
Based on the same inventive concept, the embodiment of the present application further provides a network device, as shown in fig. 5, which includes a processor 510, a transceiver 520, and a machine-readable storage medium 530, where the machine-readable storage medium 530 stores machine-executable instructions capable of being executed by the processor 510, and the processor 510 is caused by the machine-executable instructions to perform the implementation method of data smoothing provided by the embodiment of the present application. The data smoothing implementation apparatus shown in fig. 4 may be implemented by using a hardware structure of a network device as shown in fig. 5.
The computer-readable storage medium 530 may include a Random Access Memory (RAM) or a Non-volatile Memory (NVM), such as at least one disk Memory. Alternatively, the computer-readable storage medium 530 may also be at least one storage device located remotely from the processor 510.
The Processor 510 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the system can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components.
In the embodiment of the present application, the processor 510 reads the machine executable instructions stored in the machine readable storage medium 530, and the machine executable instructions cause the processor 510 itself and the call transceiver 520 to perform the data smoothing implementation method described in the embodiment of the present application.
In addition, the present application provides a machine-readable storage medium 530, the machine-readable storage medium 530 stores machine executable instructions, and when being invoked and executed by the processor 510, the machine executable instructions cause the processor 510 itself and the invoking transceiver 520 to perform the implementation method of data smoothing described in the present application.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
For the embodiments of the data smoothing implementation apparatus and the machine-readable storage medium, the content of the related method is substantially similar to that of the foregoing method embodiments, so that the description is relatively simple, and for relevant points, reference may be made to the partial description of the method embodiments.
The above description is only a preferred embodiment of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (8)

1. A method for implementing data smoothing, wherein the method is applied to a first BRAS vm, the first BRAS vm includes a first interface, and the first BRAS vm is in a MAD state after performing an incompatible version upgrade, and the method includes:
when the first BRAS vm is in the MAD state, receiving a first configuration instruction sent by a second BRAS vm;
configuring other interfaces except the first interface included in the first BRAS vm into an MAD down state according to the first configuration instruction;
sending a user data request message to an RMDB through the first interface, wherein the user data request message comprises an identifier of user data required by the first BRAS vm;
receiving a user data response message sent by the RMDB through the first interface, wherein the user data response message comprises user data required by the first BRAS vm, so that the user data is recovered in the first BRAS vm;
if the user data is recovered in the first BRAS vm, sending a first notification message to the second BRAS vm, so that the second BRAS vm executes incompatible version upgrading and is degraded into standby equipment;
receiving a second configuration instruction sent by the second BRAS vm;
configuring the other interfaces into an up state according to the second configuration instruction, and upgrading the first BRAS vm into a master device;
the address of the first interface is a first IP address, the second BRAS vm comprises a second interface with a second IP address, and the first IP address is different from the second IP address.
2. The method of claim 1, wherein when the first IP address is the same as the second IP address, the first configuration instruction further comprises a third IP address, and wherein before sending the user data request message to the RMDB via the first interface, the method further comprises:
and updating the first IP address to a third IP address, wherein the third IP address is different from the second IP address.
3. The method of claim 1, further comprising:
if the user data is not recovered in the first BRAS vm, judging whether to continue recovering the user data;
and if the user data is continuously recovered, sending a second notification message to the second BRAS vm, so that the second BRAS vm does not execute incompatible version upgrading, and continuously processing the user service.
4. The method of claim 3, further comprising:
if the user data is not continuously recovered, sending a third notification message to the second BRAS vm, so that the second BRAS vm executes incompatible version upgrading and is degraded into standby equipment;
receiving a third configuration instruction sent by the second BRAS vm;
and configuring the other interfaces into an up state according to the third configuration instruction, and upgrading the first BRAS vm into a main device.
5. An apparatus for implementing data smoothing, the apparatus is applied to a first BRAS vm, the first BRAS vm includes a first interface, and the first BRAS vm is in MAD state after performing incompatible version upgrade, the apparatus includes:
the receiving unit is used for receiving a first configuration instruction sent by a second BRAS vm when the first BRAS vm is in the MAD state;
a configuration unit, configured to configure, according to the first configuration instruction, the other interfaces, except the first interface, included in the first BRAS vm to be in an MAD down state;
a sending unit, configured to send a user data request packet to an RMDB through the first interface, where the user data request packet includes an identifier of user data required by the first BRAS vm;
the receiving unit is further configured to receive, through the first interface, a user data response packet sent by the RMDB, where the user data response packet includes user data required by the first BRAS vm, so that the user data is recovered in the first BRAS vm;
the sending unit is further configured to send a first notification message to the second BRAS vm if the user data is recovered in the first BRAS vm, so that the second BRAS vm executes incompatible version upgrade and downgrades the second BRAS vm to a standby device;
the receiving unit is further configured to receive a second configuration instruction sent by the second BRAS vm;
the configuration unit is further configured to configure the other interfaces to an up state according to the second configuration instruction, and upgrade the first BRAS vm to a master device;
the address of the first interface is a first IP address, the second BRAS vm comprises a second interface with a second IP address, and the first IP address is different from the second IP address.
6. The apparatus of claim 5, wherein the first configuration instruction further comprises a third IP address when the first IP address is the same as the second IP address, the apparatus further comprising:
and the updating unit is used for updating the first IP address into a third IP address, and the third IP address is different from the second IP address.
7. The apparatus of claim 5, further comprising:
a determining unit, configured to determine whether to continue to recover the user data if the user data is not recovered in the first BRAS vm;
the sending unit is further configured to send a second notification message to the second BRAS vm if the user data continues to be recovered, so that the second BRAS vm does not perform incompatible version upgrade and continues to process user traffic.
8. The apparatus of claim 7, wherein the sending unit is further configured to send a third notification message to the second BRAS vm if the user data is not continuously recovered, so that the second BRAS vm performs an incompatible version upgrade and downgrades the second BRAS vm to a standby device;
the receiving unit is further configured to receive a third configuration instruction sent by the second BRAS vm;
and the configuration unit is also used for configuring the other interfaces to an up state according to the third configuration instruction and upgrading the first BRAS vm to a main device.
CN202110391877.8A 2021-04-13 2021-04-13 Method and device for realizing data smoothing Active CN113300878B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110391877.8A CN113300878B (en) 2021-04-13 2021-04-13 Method and device for realizing data smoothing

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110391877.8A CN113300878B (en) 2021-04-13 2021-04-13 Method and device for realizing data smoothing

Publications (2)

Publication Number Publication Date
CN113300878A CN113300878A (en) 2021-08-24
CN113300878B true CN113300878B (en) 2022-10-21

Family

ID=77319717

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110391877.8A Active CN113300878B (en) 2021-04-13 2021-04-13 Method and device for realizing data smoothing

Country Status (1)

Country Link
CN (1) CN113300878B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108616431A (en) * 2018-04-20 2018-10-02 新华三技术有限公司 A kind of message processing method, device, equipment and machine readable storage medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102315975B (en) * 2011-10-17 2014-03-19 杭州华三通信技术有限公司 Fault processing method based on intelligent resilient framework (IRF) system and equipment thereof
CN103220189B (en) * 2013-04-12 2017-02-08 杭州华三通信技术有限公司 Multi-active detection (MAD) backup method and equipment
US9838219B2 (en) * 2014-04-30 2017-12-05 Aruba Networks, Inc. Virtual local area network mismatch detection in networks
CN111953591A (en) * 2020-07-17 2020-11-17 新华三技术有限公司 Fault processing method and device

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108616431A (en) * 2018-04-20 2018-10-02 新华三技术有限公司 A kind of message processing method, device, equipment and machine readable storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Technical principle and application of H3C IRF;Tian-bo Liu等;《Advanced materials Research Vols.1044-1045(2014)》;20140930;全文 *

Also Published As

Publication number Publication date
CN113300878A (en) 2021-08-24

Similar Documents

Publication Publication Date Title
US11429369B2 (en) Distributed upgrade in virtualized computing environments
JP6026705B2 (en) Update management system and update management method
WO2018113692A1 (en) Method for controlling network slices, forwarding device, control device and communication system
CN105743692B (en) Policy-based framework for application management
US9720682B2 (en) Integrated software and hardware system that enables automated provisioning and configuration of a blade based on its physical location
US11941423B2 (en) Data processing method and related device
CN109672619B (en) Method, device and system for processing message
JP6432955B2 (en) Method, apparatus and system for migrating virtual network function instances
WO2014032290A1 (en) Processing method and device for internet of things information and management control system
US11398976B2 (en) Method, device, and system for implementing MUX machine
US9451483B2 (en) Mobile communication system, communication system, control node, call-processing node, and communication control method
CN112583708A (en) Connection relation control method and device and electronic equipment
US9706440B2 (en) Mobile communication system, call processing node, and communication control method
CN109412980B (en) BRAS backup method and device
CN113300878B (en) Method and device for realizing data smoothing
CN116095145B (en) Data control method and system of VPC cluster
WO2020181733A1 (en) Vpc-based multi-data center intercommunication method and related device
EP3197106B1 (en) Switch processing method, controller, switch, and switch processing system
CN114978910B (en) Time sensitivity realization method and system of virtualization core network
WO2010103341A1 (en) System and methods for a managed application server restart
CN107528788A (en) Realize the method and apparatus stacked automatically between the network equipment
CN108768798B (en) Equipment access method and device
CN115396385B (en) Method and device for quickly recovering service of stack switch and computing equipment
CN112003731B (en) Configuration method and device
CN113746902B (en) Communication method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant