CN103152202B - Parameter deployment, communication node and communication network - Google Patents

Abstract

The embodiment of the invention discloses a parameter deployment method, a communication node and a communication network, which can automatically deploy parameters to nodes, thereby improving the efficiency of parameter deployment. The method includes: a communication node receives a message containing MD information and MA information sent by a neighboring node; If the information is the same, the communication node obtains the configuration parameter and deploys the configuration parameter. In this way, by receiving the message containing MD information and MA information sent by the neighboring node, when the MD information and MA information contained in the message are the same as the MD information and MA information of the local device, the configuration parameters are obtained and deployed, so as to realize automatic Deploy configuration parameters, so the efficiency of parameter deployment can be improved.

Description

Parameter deployment method, communication node and communication network

technical field

The present invention relates to the communication field, in particular to a parameter deployment method, a communication node and a communication network.

Background technique

In the communication field, the operation, management, and maintenance of the network are called OAM (Operation Administration Maintenance, the English full name is OperationAdministrationMaintenance).

During the network OAM process, it is often necessary to deploy parameters to nodes in the network. At present, the parameter deployment of nodes is mostly implemented manually by maintenance personnel. When there are many nodes, the workload of parameter deployment is large, and the parameter deployment takes a long time.

It can be seen that manually deploying parameters to nodes is less efficient.

Contents of the invention

Embodiments of the present invention provide a parameter deployment method, a communication node, and a communication network, which can automatically deploy parameters to nodes, thereby improving parameter deployment efficiency.

The embodiment of the present invention adopts following technical scheme:

In the first aspect, a parameter deployment method is provided, including:

The communication node receives the message containing the maintenance domain MD information and the maintenance alliance MA information sent by the neighboring node; and MA information, the communication node acquires configuration parameters and deploys the configuration parameters.

In the first possible implementation manner of the first aspect, when the communication node is maintaining an alliance edge node MEP, the configuration parameter includes an MEP value, and the communication node acquires the configuration parameter, and deploying the configuration parameter includes: The communication node generates the MEP value of the local device, and deploys the MEP value of the local device on the local device.

In combination with the first aspect or in combination with the first possible implementation, in the second possible implementation, when the communication node is an MEP, the configuration parameters include an enable flag for sending and receiving cc messages, and the communication node acquires Configuring parameters, and deploying the configuration parameters includes: the communication node generating the sending and receiving cc message enablement identifier or receiving the sending and receiving cc message sent by a neighboring node having the same MD information and MA information as the communication node An enabling flag; the communication node deploys the enabling flag for sending and receiving cc messages on a local device.

With reference to the first possible implementation manner, in a third possible implementation manner, after the communication node generates the MEP value of the local device, the method further includes: the communication node generating the MEP value of each neighbor in the at least one neighbor node. The MEP value of the node; the communication node sends the MEP value of each neighboring node to each neighboring node, so that each neighboring node deploys the received MEP value to each neighboring node.

In combination with the first aspect or the first possible implementation manner or the second possible implementation manner, in a fourth possible implementation manner, the message is a label distribution protocol LDP message and the communication node uses When the MD information and the MA information are available, the communication node is a MEP; or, the message is a Link Layer Discovery Protocol LLDP message and only one of the neighboring nodes sends the MD information and the message contained in the message When the MA information is the same as the MD information and MA information of the communication node, the communication node is an MEP.

In a fifth possible implementation manner of the first aspect, when the communication node is an internal node MIP of the maintenance alliance, the configuration parameter includes an MIP enablement identifier.

In combination with the first aspect or the fifth possible implementation, in the sixth possible implementation, the message is an LLDP message and the MD information contained in the message sent by at least two of the neighboring nodes and MA information are the same as the MD information and MA information of the communication node, the communication node is a MIP.

In combination with the first aspect or any possible implementation manner of the first aspect, in a sixth possible implementation manner, the MD information and MA information contained in the message sent by the neighboring node are carried in the Type Length Value TLV field.

In a second aspect, a communication node is provided, characterized in that it includes:

The receiving unit is used to receive the message containing the maintenance domain MD information and the maintenance alliance MA information sent by the neighboring node; the deploying unit is used to receive the MD information and the MA information contained in the message sent by at least one of the neighboring nodes If it is the same as the MD information and MA information of the communication node, the configuration parameters are acquired and deployed.

In the first possible implementation manner of the second aspect, when the communication node is maintaining an alliance edge node MEP, the configuration parameters include an MEP value, and the deployment unit is specifically configured to generate the MEP value of the local device, and The local device deploys the MEP value of the local device.

In combination with the second aspect or in combination with the first possible implementation manner, in the second possible implementation manner, when the communication node is an MEP, the configuration parameters include an enable flag for sending and receiving cc messages, and the deployment unit specifically It is used to generate the sending and receiving cc message enabling identifier or receive the sending and receiving cc message enabling identifier sent by a neighboring node having the same MD information and MA information as the communication node; deploy the sending and receiving cc message on the local device Packet enable flag.

With reference to the first possible implementation, in a third possible implementation, the deploying unit is configured to generate the MEP value of each adjacent node in the at least one adjacent node; then the communication node further includes sending A unit, configured to send the MEP value of each neighboring node to each neighboring node, so that each neighboring node deploys the received MEP value to each neighboring node.

In combination with the second aspect or the first aspect or the second aspect, in a fourth possible implementation manner, when the message is a label distribution protocol LDP message and the communication node is enabled with MD information and MA information , the communication node is a MEP; or, the message is a Link Layer Discovery Protocol LLDP message and the MD information and MA information contained in the message sent by only one of the neighboring nodes is the same as that of the communication node When the MD information and the MA information are the same, the communication node is an MEP.

In the fifth pit implementation of the second aspect, when the communication node is an internal node MIP of the maintenance alliance, the configuration parameters include an MIP enabling flag.

In combination with the second aspect or the fifth possible implementation, in the sixth possible implementation, the message is an LLDP message and the MD information contained in the message sent by at least two of the neighboring nodes and MA information are the same as the MD information and MA information of the communication node, the communication node is a MIP.

In a third aspect, a communication network is provided, including: at least one communication node in the second aspect or any possible implementation manner of the second aspect, and at least one neighboring node adjacent to the communication node;

The adjacent node is configured to send a message including MD information and MA information to the communication node.

The parameter deployment method, communication node, and communication network of the embodiment of the present invention receive a message containing MD information and MA information sent by a neighboring node, and the MD information and MA information contained in the message are related to the MD information and MA information of the local device. At the same time, the configuration parameters are acquired and deployed, so as to realize the automatic deployment of the configuration parameters, so that the efficiency of parameter deployment can be improved.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

FIG. 1 is a flowchart of a parameter deployment method provided by an embodiment of the present invention;

FIG. 2 is a schematic diagram of an application scenario provided by an embodiment of the present invention;

FIG. 3 is a flowchart of another parameter deployment method provided by an embodiment of the present invention;

FIG. 4 is a schematic diagram of another application scenario provided by an embodiment of the present invention;

FIG. 5 is a flowchart of another parameter deployment method provided by an embodiment of the present invention;

FIG. 6 is a schematic diagram of another application scenario provided by an embodiment of the present invention;

FIG. 7 is a flowchart of another parameter deployment method provided by an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a communication node provided by an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of another communication node provided by an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of another communication node provided by an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of a communication network provided by an embodiment of the present invention.

detailed description

In order to make the object, technical solution and advantages of the present invention clearer, the implementation manner of the present invention will be further described in detail below in conjunction with the accompanying drawings.

In the embodiment of the present invention, the communication nodes include but are not limited to PE (operator edge, English full name is provideredge), CE (user equipment, English full name is consumerequipment), GW (gateway, English full name is GateWay), AGS (aggregation switch, English full name is aggregation switch), ACS (access switch, English full name is access switch).

The parameter deployment method in the embodiment of the present invention can be applied to various networks, such as VLAN (virtual local area network, English full name is virtuallocalareanetwork) network, E2E (end-to-end, English full name is endtoend) VPN (virtual private network, English full name is VirtualPrivateNetwork) Network (can be deployed based on VLL (virtual leased line, English full name is virtualleasedline)), HVPN (hierarchical virtual private network, English full name is Hierarchyvirtualprivatenetwork) network (can be based on VPLS (virtual private LAN service, English full name is virtualprivateLANservice) business deployment ), MixedVPN network (can be deployed with VLL&VPLS mixed services), etc.

An embodiment of the present invention provides a parameter deployment method, as shown in Figure 1, the method may include:

110. The communication node receives a message including MD (Maintenance Domain, English full name maintenance domain) information and MA (Maintenance Alliance, English full name maintenance alliance) information sent by a neighboring node.

Among them, the adjacent node refers to the communication node connected to the communication node, and there can be one or more adjacent nodes, and the MD information and MA information can be MD identification and MA identification, and the MD identification and MA identification can be carried in the message specific fields. In addition, according to different scenarios, the messages in the embodiments of the present invention can be different types of protocol messages, such as LDP (Label Distribution Protocol, English full name is LabelDistributionProtocol) message, LLDP (Link Layer Discovery Protocol, LinkLayerDiscoveryProtocol) message, etc. .

120. If the MD information and MA information included in the message sent by at least one of the neighboring nodes are the same as the MD information and MA information of the communication node, then the communication node acquires configuration parameters and deploys the configuration parameters.

Wherein, the MD information and MA information of the communication node can be pre-deployed on the communication node. The embodiment of the present invention does not limit the specific deployment method of the MD information and the MA information. The MD information and the MA information can be deployed automatically or manually. MA information.

In the parameter deployment method of the embodiment of the present invention, by receiving a message containing MD information and MA information sent by a neighboring node, when the MD information and MA information contained in the message are the same as the MD information and MA information of the local device, the configuration parameters are obtained and Deploy configuration parameters, so as to realize automatic deployment of configuration parameters, so that the efficiency of parameter deployment can be improved.

In the embodiment of the present invention, according to different application scenarios, the communication node can be MEP (edge node of maintenance alliance, full name in English is maintenanceassociationendpoint) or MIP (internal node of maintenance alliance, full name in English is maintenanceassociationintermediatepoint). When the communication node is an MEP, the configuration parameter may include an MEP value, or the configuration parameter may include an enabling identifier for sending and receiving cc messages (multicast protocol messages of CFM (connectivity fault management, English full name connectivity fault management)), or The configuration parameters may include an MEP value and an enable flag for sending and receiving cc messages. When the communication node is a MIP, the configuration parameter may include a MIP enabling flag. For example, the enabling flag for sending and receiving cc messages may be enabling sending cc messages and/or enabling receiving cc messages, and the enabling flag for MIP may be used for fault location by MIP.

In the embodiment of the present invention, according to different application scenarios, the message sent by the neighboring node in the above step 110 may be an LDP message or an LLDP message. For example, communication nodes in networks such as E2EVPN network (based on VLL service deployment), HVPN network (based on VPLS service deployment), and MixedVPN network (based on VLL&VPLS mixed service deployment) can use LDP packets to communicate. For another example, communication nodes in networks such as E2EVPN network (based on VLL service deployment), HVPN network (based on VPLS service deployment), MixedVPN network (based on VLL&VPLS mixed service deployment) and VLAN network can use LLDP packets for communication.

In the embodiment of the present invention, multiple methods may be used to determine whether the communication node is an MEP or a MIP. For example, when the message is an LDP message and the communication node is enabled with MD information and MA information, the communication node is a MEP. That is, the TLV field of the LDP message received by the communication node contains the same MD information and MA information as the communication node, and the communication node is an MEP, then the MEP value is automatically configured on the communication node.

Or, when the message is an LLDP message and the MD information and MA information contained in the message sent by only one of the neighboring nodes are the same as the MD information and MA information of the communication node, the communication node is an MEP. For another example, when the message is an LLDP message and the MD information and MA information contained in the message sent by at least two of the neighboring nodes are the same as the MD information and MA information of the communication node, the communication node is a MIP.

In the embodiment of the present invention, optionally, the MD information and MA information contained in the message sent by the neighboring node are carried in the TLV (Type Length Value, English full name is TypeLengthValue) field of the message. For example, when the neighbor node sends an LDP message, the MD information and MA information can be carried in the TLV field of the LDP message; for another example, when the neighbor node sends an LLDP message, the MD information can be carried in the TLV field of the LLDP message information and MA information.

In this embodiment of the present invention, optionally, when the communication node is an MEP, the configuration parameter may include an MEP value. When the communication node acquires the configuration parameter in the above step 120 and deploys the configuration parameter, the communication node generates the MEP of the local device value, and deploy the MEP value of the local device. Wherein, the MEP value of the local device of the communication node is the MEP value deployed on the communication node.

Further optionally, after the communication node generates the MEP value of the local device, the communication node generates the MEP value of each adjacent node in the at least one adjacent node; the communication node sends the MEP value of each adjacent node to each adjacent node MEP value, so that each neighboring node performs MEP value deployment according to the received MEP value.

In the embodiment of the present invention, optionally, when the communication node is an MEP, the configuration parameters may include the enable identifier for sending and receiving cc messages. When the communication node obtains the configuration parameters in the above 120 and deploys the configuration parameters, the communication node Generate the cc message enabling flag for sending and receiving or receive the cc message enabling flag sent by a neighboring node with the same MD information and MA information as the communication node; the communication node deploys the cc message enabling flag on the local device logo. Wherein, the enabling identifier for sending and receiving cc messages includes an enabling identifier for receiving cc messages and/or an enabling identifier for sending cc messages.

In this embodiment of the present invention, optionally, when the communication node is an MEP, the configuration parameters may include an MEP value and an enable identifier for sending and receiving cc messages. When the communication node acquires the configuration parameters in the above 120 and deploys the configuration parameters, The communication node generates the MEP value of the local device, and generates the cc message enabling identifier or receives the cc message enabling identifier sent by the neighboring node. The communication node deploys the MEP value of the local device on the local device, and the communication node deploys the sending and receiving cc message enabling flag on the local device.

FIG. 2 shows an application scenario of an embodiment of the present invention. In FIG. 2, communication nodes PE1, PE2, and PE3 automatically deploy configuration parameters based on the LDP extension of BGP (Border Gateway Protocol, English full name is bordergatewayprotocol). In the scenario shown in Figure 2, CE3 is connected to PE3, PE3 is connected to PE1 and PE2 respectively, PE1 is connected to PE2, PE1 is connected to CE1, and PE2 is connected to CE2. It should be understood that the connections in this embodiment of the present invention may be physical connections or for a wireless connection.

The following takes the automatic deployment configuration parameters of communication node PE1 as an example to describe the implementation process of automatic deployment configuration parameters in detail. The specific steps are shown in Figure 3:

301. PE1 deploys MD information and MA information.

For example, when PE1 deploys MD information and MA information, it can automatically deploy the MD information and MA information to PE1, or manually deploy the MD information and MA information to PE1.

302. PE1 receives an LDP packet including MD information and MA information sent by neighboring nodes PE2 and PE3.

Specifically, the LDP packet sent by PE2 includes the MD information and MA information deployed on PE2, and the LDP packet sent by PE3 includes the MD information and MA information deployed on PE3. The MD information and MA information can be carried in the LDP packet TLV field, for example, the interfaceTLV field of PW (pseudowire, English full name is pseudowire) in the LDP message.

In the embodiment of the present invention, when PE2 and PE3 deploy MD information and MA information, they can automatically deploy MD information and MA information to PE2 and PE3 respectively, or manually deploy MD information and MA information to PE2 and PE3 respectively. The embodiment does not limit the deployment manner of the MD information and the MA information.

303. PE1 compares the MD information and MA information in the received LDP message with the MD information and MA information deployed by the local device. If the MD information and MA information in the LDP message sent by PE2 and PE3 are consistent with the local device If the MD information and MA information are the same, generate the MEP value of the local device and generate the MEP value of PE2 and the MEP value of PE3.

Wherein, the MEP value of the local device, the MEP value of PE2, and the MEP value of PE3 are different, the local device refers to PE1, and the MEP value of the local device refers to the MEP value of PE1.

304. PE1 deploys the MEP value of the local device to itself.

305. PE1 sends the MEP value of PE2 to PE2, and sends the MEP value of PE3 to PE3, PE2 deploys the received MEP value to itself, and PE3 deploys the received MEP value to itself.

306. PE1 obtains the enabling flag for sending and receiving cc messages, and deploys the enabling flag for sending and receiving cc messages on the local device.

For example, when PE1 generates the MEP value of the local device, it can generate the cc message enabling identifier, or it can receive the sending and receiving enable identifier sent by the neighbor node (such as PE2 or PE3) that has the same MD information and MA information as PE1. The enabling identifiers of the communication nodes of the MD information and the MA information are the same.

In the embodiment of the present invention, the enabling identifier for sending and receiving cc messages includes an enabling identifier for receiving cc messages and/or an enabling identifier for sending cc messages.

In other embodiments of the present invention, if the MD information and MA information contained in the LDP message sent by only one neighboring node in the above 303 are the same as the MD information and MA information of the local device, then PE1 generates a neighboring node with the same MD information and MA information Correspondingly, in 305 above, PE1 generates the cc message enablement identifier of the neighbor node whose MD information and MA information are the same, or PE1 receives the cc message enablement identifier sent by the neighbor node whose MD information and MA information are the same. For example, the MD information and MA information contained in the LDP packet sent by PE2 are the same as the MD information and MA information of PE1, but the MD information and MA information contained in the LDP packet sent by PE3 are different. The MEP value of PE2 will no longer generate the MEP value of PE3.

In other embodiments of the present invention, if the MD information and MA information contained in the LDP message sent by the neighboring nodes PE2 and PE3 in the above 303 are different from the MD information and MA information of the local device, no parameter configuration is performed.

The parameter deployment method in the embodiment of the present invention can be applied to various networks, such as E2EVPN network (can be deployed based on VLL service), HVPN network (can be based on VPLS service) Deployment), MixedVPN network (can be deployed with VLL&VPLS mixed services), etc. Automatic deployment of configuration parameters for inward-type networks can be realized. In an inward type network, when a communication node sends a protocol message, it sends it inward through the interface where the communication node is located. The inward type network automatically completes the deployment of configuration parameters according to the MD information carried in the TLV field of the LDP packet and the comparison result of the MA information. Specifically, if the MD information and MA information contained in the message sent by at least one of the neighboring nodes are the same as the MD information and MA information of the local device, the local device obtains the configuration parameters and deploys the configuration parameters on the local device.

It should be noted that the steps shown in FIG. 3 are only described by taking PE1 in FIG. 2 as an example, and the same method is also applicable to other PEs in FIG. 2 and PEs or CEs in a network similar to FIG. 2 . In addition, the embodiment of the present invention is not limited to the connection mode shown in FIG. 2 . For example, PE1 in FIG. 2 may also be connected to more PEs or CEs.

In the parameter deployment method of the embodiment of the present invention, by receiving a message containing MD information and MA information sent by a neighboring node, when the MD information and MA information contained in the message are the same as the MD information and MA information of the local device, the configuration parameters are obtained and Deploy configuration parameters, so as to realize automatic deployment of configuration parameters, so that the efficiency of parameter deployment can be improved.

Fig. 4 shows an application scenario of the embodiment of the present invention. In Fig. 4, communication nodes PE, CE, and access devices automatically deploy configuration parameters based on LLDP extensions. In the scenario shown in Figure 4, PE1 is connected to PE2 and PE3, PE2 is connected to CE1 and CE2 respectively, and CE1 is connected to an access device. It should be understood that the connection between communication nodes in this embodiment of the present invention can be a physical connection or a wireless connection .

The following takes the automatic deployment configuration parameters of communication node CE1 as an example to describe the implementation process of automatic deployment configuration parameters in detail. The specific steps are shown in Figure 5:

501. CE1 deploys MD information and MA information.

For example, the MD information and MA information can be automatically deployed to CE1, or the MD information and MA information can be manually deployed to CE1.

502. CE1 receives an LLDP packet including MD information and MA information sent by a neighboring node PE2 and an access device.

Specifically, the LLDP packet sent by PE2 includes MD information and MA information deployed on PE2, and the LLDP packet sent by the access device includes MD information and MA information deployed on the access device. In the embodiment of the present invention, the MD information and the MA information may be automatically deployed to the PE2 and the access device, or the MD information and the MA information may be manually deployed to the PE2 and the access device. Wherein, the MD information and the MA information may be carried in the TLV field of the LLDP message.

503. CE1 compares the MD information and MA information in the received LLDP message with the MD information and MA information deployed by the local device, and judges the number N of target LLDP messages. The target LLDP message contains the MD information and LLDP packets whose MA information is the same as the MD information and MA information of the local device.

Wherein, N (the number of target LLDP packets) is an integer greater than or equal to zero, if N=0, configuration parameter deployment is not performed; if N=1, CE1 is an MEP, and proceeds to 504; if N≥2, CE1 is MIP, go to 508.

504. CE1 generates the MEP value of the local device and generates the MEP value of the neighboring node whose MD information and MA information are the same.

For example, if only the MD and MA information in the LLDP packet sent by PE2 is the same as the MD and MA information of CE1's local device, CE1 can be judged as an MEP, and CE1 generates the MEP value of the local device and the MEP value of PE2. Wherein, the MEP value of the local equipment is different from the MEP value of PE2, the local equipment refers to CE1, and the MEP value of the local equipment refers to the MEP value of CE1.

505. CE1 deploys the MEP value of the local device to itself.

506. CE1 sends the corresponding MEP value to the neighboring node with the same MD information and MA information, so that the neighboring node with the same MD information and MA information deploys the received MEP value to itself.

For example, CE1 sends PE2's MEP value to PE2, and PE2 deploys the received MEP value to itself.

507. CE1 acquires the enabling flag for sending and receiving cc messages, and deploys the enabling flag for sending and receiving cc messages on the local device.

For example, CE1 can generate the sending and receiving cc message enabling identifier when generating the MEP value of the local device, and can also receive the sending and receiving enabling identifier sent by a neighboring node (such as PE2) that has the same MD information and MA information as CE1, where the same The enabling identifiers of the communication nodes of the MD information and the MA information are the same.

In the embodiment of the present invention, the enabling identification of sending and receiving cc messages includes the enabling identification of receiving cc messages, or the enabling identification of sending cc messages, or the enabling identification of receiving cc messages and the enabling of sending cc messages logo. The enabling flag for receiving cc messages and the enabling flag for sending cc messages are used to receive cc messages and send cc messages.

508. CE1 generates the MIP enabled identifier of the local device, and deploys the generated MIP enabled identifier of the local device to the local device.

For example, if the MD information and MA information in the LLDP packets sent by PE2 and the access device are the same as the MD information and MA information of the local device, it can be judged that CE1 is an MIP, and CE1 generates the MIP enablement identifier of the local device.

Wherein, the local device refers to CE1, and the MIP enabled identifier of the local device refers to the MIP enabled identifier of CE1. The MIP enabled flag can be used for MIP fault location.

The parameter deployment method in the embodiment of the present invention can be applied to various networks, such as E2EVPN network (based on VLL service deployment), HVPN network (based on VPLS service deployment), MixedVPN network (VLL&VPLS mixed service deployment) of IPRAN solution, etc. Automatic deployment of configuration parameters for inward-type networks can be realized. In an inward type network, when a communication node sends a protocol message, it sends it inward through the interface where the communication node is located. The inward type network automatically completes the deployment of configuration parameters according to the MD information carried in the TLV field of the LDP packet and the comparison result of the MA information. Specifically, if the MD information and MA information contained in the message sent by at least one of the neighboring nodes are the same as the MD information and MA information of the local device, the local device obtains the configuration parameters and deploys the configuration parameters on the local device.

It should be noted that the steps shown in Figure 5 are only illustrated by taking CE1 in Figure 4 as an example, and the same method is also applicable to other communication nodes (such as PE2, access equipment) in Figure 5 and networks similar to Figure 4 communication nodes (such as CE, PE, etc.). In addition, the embodiment of the present invention is not limited to the connection mode shown in FIG. 5. For example, CE1 in FIG. 5 can be connected to more access devices, and PE2 and PE3 in FIG. 5 can be connected to the Internet.

In the embodiment of the present invention, the access device may be an ATN (Access Transport Network, the full English name is AccessTransportNetwork) or the like.

In the parameter deployment method of the embodiment of the present invention, by receiving a message containing MD information and MA information sent by a neighboring node, when the MD information and MA information contained in the message are the same as the MD information and MA information of the local device, the configuration parameters are obtained and Deploy configuration parameters, so as to realize automatic deployment of configuration parameters, so that the efficiency of parameter deployment can be improved.

FIG. 6 shows an application scenario of the embodiment of the present invention. In FIG. 6 , automatic deployment configuration parameters of communication nodes GW, AGS, and ACS are implemented based on LLDP extension. In the scenario shown in Figure 6, the GW is connected to AGS1 and AGS2, AGS1 is connected to ACS1 and ACS2 respectively, and AGS2 is connected to ACS1 and ACS2 respectively. It should be understood that the connection between communication nodes in the embodiment of the present invention can be physical or wireless connect.

The following takes the automatic deployment configuration parameters of the communication node AGS1 as an example to describe the implementation process of the automatic deployment configuration parameters in detail. The specific steps are shown in Figure 7:

701. AGS1 deploys MD information and MA information.

For example, the MD information and MA information can be automatically deployed to AGS1, or the MD information and MA information can be manually deployed to AGS1.

702. The AGS1 receives the LLDP message including the MD information and the MA information sent by the neighboring nodes ACS1, ACS2, and GW.

Specifically, the LLDP packet sent by ACS1 contains the MD information and MA information deployed on ACS1, the LLDP packet sent by ACS2 contains the MD information and MA information deployed on ACS2, and the LLDP packet sent by GW contains the MD information deployed on GW and MA information. In the embodiment of the present invention, the MD information and MA information may be automatically deployed to ACS1, ACS2 and GW, or the MD information and MA information may be manually deployed to ACS1, ACS2 and GW. Wherein, the MD information and the MA information may be carried in the TLV field of the LLDP message.

703. AGS1 compares the MD information and MA information in the received LLDP message with the MD information and MA information deployed by the local device, and determines the number N of target LLDP messages, and the target LLDP message contains the MD information and An LLDP packet whose MA information is the same as the MD information and MA information of the AGS1 local device.

Wherein, N (the number of target LLDP packets) is an integer greater than or equal to zero, if N=0, configuration parameter deployment is not performed; if N=1, CE1 is an MEP, and proceeds to 704; if N≥2, CE1 is MIP, go to step 708.

704. AGS1 generates the MEP value of the local device and generates the MEP value of the neighbor node whose MD information and MA information are the same.

For example, if only the MD and MA information in the LLDP packet sent by ACS1 is the same as the MD and MA information of the local device, it can be determined that AGS1 is an MEP, and then AGS1 generates the MEP value of the local device and the MEP value of ACS1. Wherein, the MEP value of the local device and the MEP value of the ACS1 are different, the local device refers to the AGS1, and the MEP value of the local device refers to the MEP value of the AGS1.

705. AGS1 deploys the MEP value of the local device to itself.

706. The AGS1 sends the corresponding MEP value to the neighboring node with the same MD information and MA information, and the neighboring node with the same MD information and MA information deploys the received MEP value to itself.

For example, if the MD information and MA information of ACS1 are the same as those of AGS1, AGS1 sends the MEP value of ACS1 to ACS1, and ACS1 deploys the received MEP value to itself.

707. The AGS1 acquires the enabling flag for sending and receiving cc messages, and deploys the enabling flag for sending and receiving cc messages on the local device.

For example, AGS1 can generate the sending and receiving cc packet enabling identifier when generating the MEP value of the local device, and can also receive the sending and receiving enabling identifier sent by the neighboring node (such as ACS1) that has the same MD information and MA information as AGS1, where the same The MD information and the enabling identifier of the MA information communication node are the same.

In the embodiment of the present invention, the enabling identification of sending and receiving cc messages includes the enabling identification of receiving cc messages, or the enabling identification of sending cc messages, or the enabling identification of receiving cc messages and the enabling of sending cc messages logo. The enabling flag for receiving cc messages and the enabling flag for sending cc messages are used to receive cc messages and send cc messages.

708. The AGS1 generates the MIP enabled identifier of the local device, and deploys the generated MIP enabled identifier of the local device to the local device.

For example, if the MD information and MA information in the LLDP packets sent by ACS1, ACS2, and GW are the same as the MD information and MA information of the local device, it can be judged that AGS1 is MIP, and then AGS1 generates the MIP enablement identifier of the local device.

Wherein, the local device refers to AGS1, and the MIP enabling identifier of the local device refers to the MIP enabling identifier of AGS1. The MIP enabled flag can be used for MIP fault location.

The parameter deployment method in the embodiment of the present invention can be applied to a variety of networks, such as VLAN networks, E2EVPN networks of IPRAN solutions (which can be deployed based on VLL services), HVPN networks (which can be deployed based on VPLS services), and MixedVPN networks (which can be based on VLL&VPLS mixed services) deployment), etc. Automatic deployment of configuration parameters for an outward network can be realized. In an outward-facing network, when a communication node sends a protocol message, it sends out through the interface where the communication node is located. Outbound networks automatically deploy configuration parameters based on the MD information carried in the TLV field of the LLDP packet and the comparison result of the MA information. Specifically, if the MD information and MA information contained in the message sent by at least one of the neighboring nodes are the same as the MD information and MA information of the local device, the local device obtains the configuration parameters and deploys the configuration parameters on the local device.

It should be noted that the steps shown in Figure 7 are only illustrated by taking PE1 in Figure 6 as an example, and the same method is also applicable to other communication nodes (such as AGS2, ACS1, ACS2, GW) in Figure 6 and similar to Figure 6 Communication nodes in the network. In addition, the embodiment of the present invention is not limited to the connection manner shown in FIG. 6 , for example, AGS1 in FIG. 6 may be connected to more ACSs.

In the parameter deployment method of the embodiment of the present invention, by receiving a message containing MD information and MA information sent by a neighboring node, when the MD information and MA information contained in the message are the same as the MD information and MA information of the local device, the configuration parameters are obtained and Deploy configuration parameters, so as to realize automatic deployment of configuration parameters, so that the efficiency of parameter deployment can be improved.

As shown in FIG. 8, a communication node provided by an embodiment of the present invention may include: a receiving unit 81 and a deploying unit 82, wherein,

A receiving unit 81, configured to receive a message including MD information and MA information sent by a neighboring node;

Wherein, an adjacent node refers to a communication node connected to a communication node by a line, and there may be one or more adjacent nodes. In addition, according to different scenarios, the packets in the embodiments of the present invention may be different types of protocol packets, such as LDP packets, LLDP packets, and the like.

The deploying unit 82 is configured to obtain configuration parameters and deploy the configuration parameters if the MD information and MA information contained in the message sent by at least one of the neighboring nodes are the same as the MD information and MA information of the communication node.

Among them, the MD information and MA information of the communication node can be pre-deployed on the communication node. The embodiment of the present invention does not limit the specific deployment method of the MD information and the MA information. The MD information and the MA information can be deployed automatically or manually. .

In the embodiment of the present invention, optionally, when the communication node is an MEP maintenance alliance edge node, the configuration parameters include the MEP value, and the deployment unit 82 is specifically used to generate the MEP value of the local device, and deploy the MEP value of the local device on the local device .

In this embodiment of the present invention, optionally, when the communication node is an MEP, the configuration parameters include the enabling identifier of sending and receiving cc messages, and the deployment unit 82 is specifically used to generate an enabling identifier of sending and receiving cc messages or receive the sending and receiving cc messages sent by neighboring nodes. Message enablement flag; the local device is deployed to send and receive cc message enablement flags.

In the embodiment of the present invention, optionally, the deploying unit 82 is configured to generate the MEP value of each neighboring node in at least one neighboring node;

Correspondingly, as shown in FIG. 9, the communication node further includes a sending unit 83, configured to send the MEP value of each neighboring node to each neighboring node, so that each neighboring node deploys the received MEP value to each neighboring node .

In this embodiment of the present invention, optionally, when the message is a label distribution protocol LDP message, the communication node is an MEP; or, the message is a link layer discovery protocol LLDP message and only one of the adjacent nodes sends a message. When the MD information and MA information contained in the document are the same as the MD information and MA information of the communication node, the communication node is an MEP.

In the embodiment of the present invention, optionally, when the communication node is an internal node MIP of the maintenance alliance, the configuration parameters include the MIP enablement identifier.

In this embodiment of the present invention, optionally, when the message is an LLDP message and the MD information and MA information contained in the message sent by at least two neighboring nodes among the neighboring nodes are the same as the MD information and MA information of the communication node, the communication node for MIPs.

The communication node in this embodiment of the present invention may use the foregoing method embodiments, and reference may be made to the foregoing method embodiments for a specific implementation process. In addition, the communication nodes in this embodiment of the present invention may be PEs, CEs, GWs, AGSs, ACSs, and the like.

The communication node in the embodiment of the present invention obtains the configuration parameters and deploys them when the message containing the MD information and MA information sent by the neighboring node is the same as the MD information and MA information of the local device. Configure parameters, so as to realize automatic deployment of configuration parameters, so the efficiency of parameter deployment can be improved.

As shown in FIG. 10, another communication node provided by an embodiment of the present invention may include: a bus 11, an interface 12 connected to the bus 11, and a processor 13, wherein:

The interface 12 is used to receive a message including MD information and MA information sent by a neighboring node;

The processor 13 is configured to obtain configuration parameters and deploy configuration parameters if the MD information and MA information contained in the message sent by at least one of the neighboring nodes are the same as the MD information and MA information of the communication node.

In the embodiment of the present invention, optionally, when the communication node is an MEP maintenance alliance edge node, the configuration parameters include the MEP value, and the processor 13 is specifically configured to generate the MEP value of the local device, and deploy the MEP value of the local device on the local device.

In this embodiment of the present invention, optionally, when the communication node is an MEP, the configuration parameters include an enable flag for sending and receiving cc messages, and the processor 13 is specifically used to generate an enable flag for sending and receiving cc messages or receive a sending and receiving cc message sent by a neighboring node. Message enablement flag; the local device is deployed to send and receive cc message enablement flags.

The processor 13 is used to generate the MEP value of each neighboring node in at least one neighboring node;

Then the interface 12 is used to send the MEP value of each neighboring node to each neighboring node, so that each neighboring node deploys the received MEP value to each neighboring node.

In the embodiment of the present invention, optionally, when the message is a label distribution protocol LDP message and the communication node is enabled with MD information and MA information, the communication node is an MEP. That is, the TLV field of the LDP message received by the communication node contains the same MD information and MA information as the communication node, and the communication node is an MEP, then the MEP value is automatically configured on the communication node. Or, when the message is a link layer discovery protocol LLDP message and the MD information and MA information contained in the message sent by only one of the neighboring nodes are the same as the MD information and MA information of the communication node, the communication node is an MEP.

In the embodiment of the present invention, optionally, when the communication node is an internal node MIP of the maintenance alliance, the configuration parameters include the MIP enablement identifier.

In this embodiment of the present invention, optionally, when the message is an LLDP message and the MD information and MA information contained in the message sent by at least two neighboring nodes among the neighboring nodes are the same as the MD information and MA information of the communication node, the communication node for MIPs.

The communication node in the embodiment of the present invention may use the above-mentioned method embodiment, and refer to the above-mentioned method embodiment for a specific implementation process. In addition, the communication nodes in this embodiment of the present invention may be PEs, CEs, GWs, AGSs, ACSs, and the like.

The communication node in the embodiment of the present invention obtains the configuration parameters and deploys them when the message containing the MD information and MA information sent by the neighboring node is the same as the MD information and MA information of the local device. Configure parameters, so as to realize automatic deployment of configuration parameters, so the efficiency of parameter deployment can be improved.

As shown in FIG. 11, an embodiment of the present invention provides a communication network, including: at least one communication node S1 and at least one neighboring node S2 adjacent to the communication node;

The communication node S1 is configured to receive a message including MD information and MA information sent by the neighboring node S2;

If the MD information and MA information contained in the message sent by at least one of the neighboring nodes S2 are the same as the MD information and MA information of the communication node S1, the communication node S1 obtains the configuration parameters and deploys the configuration parameters.

The neighboring node S2 is configured to send a message including MD information and MA information to the communication node.

Specifically, the constituent units of the communication node S1 and the specific functions of each unit are the same as those of the above communication node implementing the embodiment of the present invention, please refer to.

In the communication network of the embodiment of the present invention, the communication node receives a message containing MD information and MA information sent by a neighboring node, and when the MD information and MA information contained in the message are the same as the MD information and MA information of the local device, the configuration parameters are obtained and Deploy configuration parameters, so as to realize automatic deployment of configuration parameters, so that the efficiency of parameter deployment can be improved.

The embodiments of the present invention are mainly applied to parameter deployment of communication nodes, and can automatically perform parameter deployment on nodes, thereby improving parameter deployment efficiency.

It should be noted that: the data sending device and the data receiving device provided by the above-mentioned embodiments are only described by using the division of the above-mentioned functional modules as examples. In practical applications, the above-mentioned functions can be assigned to different function modules according to needs Module completion means that the internal structure of the device is divided into dial-up functional modules to complete all or part of the above functions. In addition, the device provided by the above embodiment and the corresponding method belong to the same idea, and the specific implementation process thereof is detailed in the method embodiment, and will not be repeated here.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above embodiments can be completed by hardware, and can also be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned The storage medium mentioned may be a read-only memory, a magnetic disk or an optical disk, and the like.

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant parts, please refer to part of the description of the method embodiment. The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without creative effort.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be realized by means of software plus necessary general-purpose hardware. The general-purpose hardware includes general-purpose integrated circuits, general-purpose CPUs, general-purpose memories, general-purpose components, etc. , Of course, it can also be realized by dedicated hardware including application-specific integrated circuits, dedicated CPUs, dedicated memories, dedicated components, etc., but in many cases the former is a better implementation. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, such as a floppy disk of a computer , a hard disk or an optical disk, etc., including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute the methods of various embodiments of the present invention.

The above are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection scope of the present invention Inside.

Claims (12)

1. A parameter deployment method, characterized in that, comprising: The communication node receives the message containing the maintenance domain MD information and the maintenance alliance MA information sent by the neighboring node, and the message is a label distribution protocol LDP message or a link layer discovery protocol LLDP message; If the MD information and MA information contained in the message sent by at least one of the neighboring nodes are the same as the MD information and MA information of the communication node, the communication node acquires configuration parameters and deploys the configuration parameters; When the communication node is maintaining an alliance edge node MEP, the configuration parameters include an MEP value, and the communication node obtains the configuration parameters, and deploying the configuration parameters includes: The communication node generates the MEP value of the local device, and deploys the MEP value of the local device on the local device; When the communication node is an internal node MIP of the maintenance alliance, the configuration parameters include a MIP enablement identifier, the communication node obtains the configuration parameters, and deploying the configuration parameters includes: The communication node generates the MIP enabling identifier of the local device, and deploys the MIP enabling identifier of the local device on the local device. 2. The method according to claim 1, wherein when the communication node is an MEP, the configuration parameters include the multicast protocol cc message enablement identifier for sending and receiving connectivity fault management, and the communication node obtains the configuration Parameters, and deployment The configuration parameters include: The communication node generates the enabling identification of the sending and receiving cc message or receives the sending and receiving cc message enabling identification sent by a neighboring node having the same MD information and MA information as the communication node; The communication node deploys the enabling flag for sending and receiving cc messages on a local device. 3. The method according to claim 1, further comprising: after the communication node generates the MEP value of the local device: generating, by the communication node, a MEP value for each of the at least one neighboring node; The communication node sends the MEP value of each neighboring node to each neighboring node, so that each neighboring node deploys the received MEP value to each neighboring node. 4. The method according to any one of claims 1 to 3, wherein when the message is a Label Distribution Protocol (LDP) message and the communication node enables MD information and MA information, the communication Node is MEP; Or, when the message is a link layer discovery protocol LLDP message and the MD information and MA information contained in the message sent by only one of the neighboring nodes are the same as the MD information and MA information of the communication node, The communication node is an MEP. 5. The method according to claim 1, characterized in that, the message is an LLDP message and the MD information and the MA information contained in the message sent by at least two of the adjacent nodes in the adjacent nodes are the same as those of the communication node When the MD information and the MA information are the same, the communication node is a MIP. 6. The method according to any one of claims 1-3, 5, characterized in that the MD information and MA information contained in the message sent by the neighboring node are carried in the Type Length Value TLV field of the message . 7. A communication node, characterized in that, comprising: The receiving unit is configured to receive a message including maintenance domain MD information and maintenance alliance MA information sent by a neighboring node, where the message is a label distribution protocol LDP message or a link layer discovery protocol LLDP message; A deploying unit, configured to obtain configuration parameters and deploy the configuration parameters if the MD information and MA information contained in the message sent by at least one of the neighboring nodes are the same as the MD information and MA information of the communication node ; When the communication node is an MEP maintenance alliance edge node, the configuration parameters include an MEP value, and the deployment unit is specifically configured to generate an MEP value of a local device, and deploy the MEP value of the local device on the local device; When the communication node is an internal node MIP of the maintenance alliance, the configuration parameters include a MIP enablement identifier, and the deployment unit is specifically used to generate a MIP enablement identifier of a local device, and deploy the MIP of the local device on the local device enable flag. 8. The communication node according to claim 7, wherein when the communication node is an MEP, the configuration parameters include an enable flag for sending and receiving cc messages, and the deployment unit is specifically used to generate the sending and receiving cc message Message enablement identification or receiving the sending and receiving cc message enabling identification sent by a neighboring node having the same MD information and MA information as the communication node; deploying the sending and receiving cc message enabling identification on the local device. 9. The communication node according to claim 7, wherein the deploying unit is used to generate the MEP value of each neighboring node in the at least one neighboring node; Then the communication node further includes a sending unit, configured to send the MEP value of each neighboring node to each neighboring node, so that each neighboring node deploys the received MEP value to each neighboring node node. 10. The communication node according to any one of claims 7 to 9, wherein when the message is a Label Distribution Protocol (LDP) message and the communication node enables MD information and MA information, the The communication node is MEP; Or, when the message is a link layer discovery protocol LLDP message and the MD information and MA information contained in the message sent by only one of the neighboring nodes are the same as the MD information and MA information of the communication node, The communication node is an MEP. 11. The communication node according to claim 7, wherein the message is an LLDP message and the MD information and the MA information contained in the message sent by at least two of the adjacent nodes in the adjacent nodes are related to the communication When the MD information and the MA information of the node are the same, the communication node is a MIP. 12. A communication network, characterized in that, comprising: at least one communication node as claimed in any one of claims 7-11 and at least one adjacent node adjacent to the communication node; The adjacent node is configured to send a message including MD information and MA information to the communication node.