WO2019128651A1 - 一种anima网络的信息处理方法、设备及系统 - Google Patents

一种anima网络的信息处理方法、设备及系统 Download PDF

Info

Publication number
WO2019128651A1
WO2019128651A1 PCT/CN2018/119269 CN2018119269W WO2019128651A1 WO 2019128651 A1 WO2019128651 A1 WO 2019128651A1 CN 2018119269 W CN2018119269 W CN 2018119269W WO 2019128651 A1 WO2019128651 A1 WO 2019128651A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
objective
saved
message
locally
Prior art date
Application number
PCT/CN2018/119269
Other languages
English (en)
French (fr)
Inventor
耿永生
黄河
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18894504.2A priority Critical patent/EP3720078B1/en
Publication of WO2019128651A1 publication Critical patent/WO2019128651A1/zh
Priority to US16/913,274 priority patent/US11095514B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the present application relates to the field of communications technologies, and in particular, to an information processing method, device, and system for an autonomic networking integrated model and approach (ANIMA) network.
  • ANIMA autonomic networking integrated model and approach
  • the ANIMA network is a self-organizing network.
  • the autonomy of the ANIMA network mainly completes four purposes: self-configuration, self-protection, self-healing, and self-optimization, so as to minimize the autonomic function.
  • the ANIMA network is divided into two layers: an autonomic service agent (ASA) and an autonomic network infrastructure (ANI).
  • ASA autonomic service agent
  • ANI autonomic network infrastructure
  • bootstrap bootstrap
  • ACP Autonomic Control Pannel
  • GRASP generic autonomic signaling protocol
  • Bootstrap is responsible for the secure boot and boot of network devices. Network devices join the authentication of the ANIMA domain and the assignment of domain certificates.
  • the ACP is responsible for establishing a hop-by-hop encrypted Internet Protocol (IP) tunnel between network devices to form a stable virtual private network (VPN), which is based on the internal VPN.
  • IP Internet Protocol
  • VPN virtual private network
  • IGP inter-or gateway protocol
  • GRASP is a standard signaling protocol for interaction between ASAs. It is responsible for enabling the ASA to perform dynamic neighbor discovery, synchronization status, and negotiation parameter settings.
  • objective refers to a set of configurable parameters or configurable parameters that operate in the GRASP discovery, synchronization, negotiation, and flooding mechanisms.
  • the network device as the initiator transmits the Objective to the network device as the receiving end based on GRASP, so that the receiving end configures according to the received Objective.
  • the Objective saved by the receiving end cannot be changed in time.
  • the receiving end can only wait for the Objective aging saved by the receiving end to aging or wait for the initiator to start the discovery, synchronization, and corresponding to the Objective.
  • Negotiation or flooding mechanism when the Objective of the initiator changes, the Objective saved by the receiving end cannot be changed in time.
  • the embodiment of the present application provides an information processing method, device, and system for an ANIMA network.
  • the network device detects that the locally saved Objective changes, the network device automatically peers with the network device.
  • the peer network device notifies the change of the Objective, so that the peer network device changes the locally saved Objective in time, which helps the peer network device to reduce the occupation of a central processing unit (CPU) and a storage resource. .
  • CPU central processing unit
  • an information processing method for an ANIMA network includes the first network device transmitting a first Objective to a second network device, wherein the first network device and the second network device are running an ANIMA protocol. Then, the first network device determines whether the first Objective saved locally is changed. When the first network device determines that the first Objective change is locally saved, the first network device sends a first Objective change message to the second network device to instruct the second network device to change the The first Objective from the first network device saved locally by the second network device.
  • the network device when the network device detects that the locally saved Objective changes, the network device automatically notifies the peer network device of the network device of the change of the Objective, so that The peer network device changes the locally saved Objective in time to help the peer network device reduce the CPU and storage resources.
  • the determining, by the first network device, whether the first saved object is locally changed comprises: determining, by the first network device, whether the first Objective saved locally is delete.
  • the first network device sends a first Objective change message to the second network device to instruct the second network device to change the
  • the first Objective from the first network device saved locally by the second network device includes: when the first network device determines that the first Objective saved locally is deleted, the first network device is The second network device sends a first Objective change message to instruct the second network device to delete the first Objective from the first network device that is saved locally by the second network device.
  • the determining, by the first network device, whether the first saved entity is locally changed comprises: determining, by the first network device, whether the first Objective saved locally is modified.
  • the first network device sends a first Objective change message to the second network device to instruct the second network device to change the
  • the first Objective from the first network device saved locally by the second network device includes: when the first network device determines that the first Objective saved locally is modified, the first network device is The second network device sends a first Objective change message to instruct the second network device to modify the first Objective from the first network device that is locally saved by the second network device.
  • the first network device acquires an ANIMA message, and the de-enable ANIMA message is used to instruct the first network device to disable the ANIMA function of the first port.
  • the first port is a port that the first network device sends the first Objective to the second network device.
  • the first network device sends a second Objective change message to the second network device to indicate the And deleting, by the second network device, the first Objective from the first network device that is locally saved by the second network device according to the second Objective change message.
  • an information processing method for an ANIMA network includes the second network device receiving a first Objective sent by the first network device, the first network device and the second network device running an ANIMA protocol. And, the second network device saves the first Objective.
  • the second network device receives the first Objective change message sent by the first network device, where the first Objective change message is locally saved by the first network device in response to the first network device.
  • the first Objective is generated by a change.
  • the second network device changes the first Objective saved locally by the second network device according to the first Objective change message.
  • the network device when the network device detects that the locally saved Objective changes, the network device automatically notifies the peer network device of the network device of the change of the Objective, so that The peer network device changes the locally saved Objective in time to help the peer network device reduce the CPU and storage resources.
  • the changing, by the second network device, the first Objective that is locally saved by the second network device according to the first Objective change packet includes: the second network The device deletes the first Objective saved by the second network device according to the first Objective change message.
  • the changing, by the second network device, the first Objective that is locally saved by the second network device according to the first Objective change message includes: the second The network device modifies the first Objective saved by the second network device according to the first Objective change message.
  • the second network device forwards the first Objective to the third network device.
  • the second network device determines whether the first communication link is faulty, and the first communication link is that the second network device receives the first Objective communication link sent by the first network device.
  • the second network device sends a second Objective change message to the third network device to instruct the third network device to delete the The first Objective saved locally by the three network devices.
  • the first Objective change message is a GRASP message
  • the GRASP message includes a first identifier
  • the first identifier is used to indicate that the GRASP message is Objective Change the message.
  • the GRASP message further includes a second identifier, where the second identifier is used to indicate a change type of the first Objective from the first network device that is saved locally by the second network device.
  • a first network device having a function of implementing behavior of a first network device in the foregoing method.
  • the functions may be implemented based on hardware, or may be implemented based on hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the first network device includes a processor and an interface configured to support the first network device to perform a corresponding function in the above method.
  • the interface is configured to support communication between the first network device and the second network device, send information or instructions involved in the foregoing method to the second network device, or receive information involved in the foregoing method from the second network device. Or instructions.
  • the first network device can also include a memory for coupling with a processor that retains program instructions and data necessary for the first network device.
  • the first network device includes: a processor, a transmitter, a receiver, a random access memory, a read only memory, and a bus.
  • the processor is respectively coupled to the transmitter, the receiver, the random access memory, and the read-only memory through a bus.
  • the first network device is booted into a normal operating state by booting in a basic input/output system in a read-only memory or a bootloader booting system in an embedded system.
  • the application and operating system are run in a random access memory such that the processor performs the method of the first aspect or any possible implementation of the first aspect.
  • a first network device in a fourth aspect, includes: a main control board and an interface board, and further, a switching network board.
  • the first network device is operative to perform the method of the first aspect or any possible implementation of the first aspect.
  • the first network device comprises means for performing the method of the first aspect or any possible implementation of the first aspect.
  • a first network device comprising a controller and a first forwarding sub-device.
  • the first forwarding sub-device includes: an interface board, and further, may further include a switching network board.
  • the first forwarding sub-device is configured to perform the function of the interface board in the fourth aspect. Further, the function of the switching network board in the fourth aspect may also be performed.
  • the controller includes a receiver, a processor, a transmitter, a random access memory, a read only memory, and a bus.
  • the processor is coupled to the receiver, the transmitter, the random access memory, and the read only memory through a bus.
  • the booting is started by the solid input/output system in the read-only memory or the bootloader booting system in the embedded system, and the controller is put into a normal running state. After the controller enters a normal operating state, the application and the operating system are run in the random access memory, so that the processor performs the functions of the main control board in the fourth aspect.
  • a computer storage medium for storing a program, code or instruction for use in the first network device, and the processor or the hardware device can perform the first of the above aspects when executing the program, code or instruction.
  • the function or step of a network device is provided for storing a program, code or instruction for use in the first network device, and the processor or the hardware device can perform the first of the above aspects when executing the program, code or instruction.
  • a second network device having a function of implementing a behavior of the second network device in the foregoing method.
  • the functions may be implemented based on hardware, or may be implemented based on hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the second network device includes a processor and an interface configured to support the second network device to perform a corresponding function in the above method.
  • the interface is configured to support communication between the second network device and the first network device, send information or instructions involved in the foregoing method to the first network device, or receive information involved in the foregoing method from the first network device. Or instructions.
  • the second network device can also include a memory for coupling with the processor that retains program instructions and data necessary for the second network device.
  • the second network device includes: a processor, a transmitter, a receiver, a random access memory, a read only memory, and a bus.
  • the processor is respectively coupled to the transmitter, the receiver, the random access memory, and the read-only memory through a bus.
  • the booting is performed by the bootloader booting system in the basic input/output system or the embedded system in the read-only memory, and the second network device is booted into a normal running state.
  • the application and operating system are run in a random access memory such that the processor performs the method of any of the second or second aspects of the possible implementation.
  • a second network device in an eighth aspect, includes: a main control board and an interface board, and further, a switching network board.
  • the second network device is operative to perform the method of the second aspect or any possible implementation of the second aspect.
  • the second network device comprises means for performing the method of any of the second aspect or any of the possible implementations of the second aspect.
  • a second network device comprising a controller and a second forwarding sub-device.
  • the second forwarding sub-device includes: an interface board, and further, may further include a switching network board.
  • the second forwarding sub-device is configured to perform the function of the interface board in the eighth aspect. Further, the function of the switching network board in the eighth aspect may also be performed.
  • the controller includes a receiver, a processor, a transmitter, a random access memory, a read only memory, and a bus.
  • the processor is coupled to the receiver, the transmitter, the random access memory, and the read only memory through a bus.
  • the booting is started by the solid input/output system in the read-only memory or the bootloader booting system in the embedded system, and the controller is put into a normal running state. After the controller enters the normal operating state, the application and the operating system are run in the random access memory, so that the processor performs the functions of the main control board in the eighth aspect.
  • a computer storage medium for storing a program, code or instruction used by the second network device, and the processor or the hardware device can perform the second of the above aspects when executing the program, code or instruction.
  • the function or step of a network device is provided for storing a program, code or instruction used by the second network device, and the processor or the hardware device can perform the second of the above aspects when executing the program, code or instruction.
  • an ANIMA network system comprising a first network device and a second network device, the first network device being the third aspect or the fourth or fifth aspect A network device, wherein the second network device is the foregoing seventh aspect or the second network device in the eighth aspect or the ninth aspect.
  • the information processing method, device and system of the ANIMA network provided by the embodiments of the present application are provided by the foregoing solutions.
  • the network device when the network device detects that the locally saved Objective changes, the network device automatically notifies the peer network device of the network device of the change of the Objective, so that the peer network device changes the local time in time.
  • the saved Objective helps the peer network device to reduce the CPU and storage resources.
  • FIG. 1 is a schematic structural diagram of an ANIMA network according to an embodiment of the present application.
  • FIG. 2 is a flowchart of an information processing method of an ANIMA network according to an embodiment of the present application
  • FIG. 3 is a flowchart of a method for generating and sending an Objective change message according to an embodiment of the present application
  • FIG. 4 is a format diagram of a packet of an Objective Change message according to an embodiment of the present application.
  • FIG. 5 is a format diagram of a packet of another Objective change packet according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a packet format of another Objective change packet according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a first network device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of hardware of a first network device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of hardware of another first network device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a second network device according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of hardware of a second network device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of hardware of another second network device according to an embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of an ANIMA network according to an embodiment of the present application.
  • the ANIMA network includes a first network device, a second network device, and a third network device.
  • the first network device is in communication with the second network device, and the second network device is in communication with the third network device.
  • the first network device, the second network device, and the third network device all run the ANIMA protocol. More specifically, the first network device, the second network device, and the third network device all run GRASP.
  • the first network device, the second network device, and the third network device enable the ASA based on the GRASP, and therefore, in the case of running GRASP, the first network device, the second network device, and the third network
  • the devices may be referred to as a first ASA, a second ASA, and a third ASA, respectively.
  • GRASP is a standard signaling protocol for interaction between ASAs to enable discovery, synchronization, negotiation, and flooding mechanisms between ASAs.
  • GRASP implements discovery, synchronization, negotiation, and flooding mechanisms by passing Objective between ASAs. Objective can be distinguished by type: Discover Objective, Synchronize Objective, Negotiate Objective and Flood Objective. Among them, Objective is used in the GRASP discovery mechanism.
  • Synchronous Objective is used in the GRASP synchronization mechanism.
  • Negotiation Objective is used in the GRASP negotiation mechanism.
  • Flooding Objective is used in the GRASP flooding mechanism.
  • the ASA can discover other ASAs by discovering Objective.
  • the ASA can obtain the current parameter values in other ASAs by synchronizing the Objective request.
  • the negotiation mechanism the ASA can initiate negotiations with other ASAs through negotiation Objectives in order to implement an iterative interaction process of parameter settings between ASAs.
  • the ASA can flood the Objectives to other ASAs by flooding Objective.
  • the Objective may include a name and a value, where the name is used to identify the Objective, and the value refers to a configuration parameter for the network device included in the Objective.
  • the first network device in FIG. 1 serves as an initiator of the Objective, and the first network device implements a discovery mechanism with the second network device by using GRASP.
  • the first network device acquires a first Objective
  • the first Objective is a Discovery Objective.
  • the first network device may acquire the first Objective by means of a network administrator, or may acquire the first Objective from another network device (for example, a network management device).
  • the first network device acquires the first Objective
  • the first Objective is saved.
  • the first network device may save the first Objective in a cache.
  • the first network device sends the first Objective to the second network device.
  • the first network device may carry the first Objective in a GRASP message, and send the GRASP message to the second network device.
  • the GRASP message may also be referred to as a discovery message.
  • the second network device After receiving the first Objective, the second network device saves the first Objective, and performs a configuration operation on the second network device by using the first Objective. The second network device also sends a discovery response message to the first network device.
  • the GRASP message may include a loop-count field, the loop-count field is used to indicate the number of hops that the GRASP message is forwarded.
  • the loop-count field ranges from 0 to 255.
  • the loop-count field ensures that the first Objective can be sent not only to the second network device but also to a network device that is greater than one hop from the first network device.
  • the second network device is further connected to the third network device.
  • the second network device After receiving the first Objective from the first network device, the second network device records a port on the second network device for receiving the first Objective.
  • the second network device performs a configuration operation on the second network device by using the first Objective, and forwards the first Objective to the location according to the value of the loop-count field in the GRASP message.
  • Said third network device After receiving the first Objective, the third network device saves the first Objective, and performs a configuration operation on the third network device by using the first Objective.
  • the third network device also sends a discovery response message to the first network device via
  • the first network device may send the first Objective to multiple network devices.
  • the first network device is further connected to a fourth network device.
  • the first network device may send the first Objective to the fourth network device, so that the fourth network device performs a configuration operation on the fourth network device by using the first Objective.
  • the discovery mechanism is taken as an example to describe the transmission process of Objective.
  • the synchronization mechanism, the negotiation mechanism, and the flooding mechanism the implementation process of transmitting the Objective is similar, and is not described here.
  • the Objective may be changed.
  • the change includes the Objective being deleted and a partial or all value in the Objective being modified.
  • the original Objective is deleted due to a user configuration change or the Internet Protocol version 6 (IPv6) address parameter included in the original Objective is modified.
  • IPv6 Internet Protocol version 6
  • the first Objective saved locally by the first network device is changed, for example, the first Objective saved locally by the first network device is deleted, and the second network is deleted.
  • the device or the third network device is not aware.
  • the first Objective is used in a discovery mechanism. Therefore, the second network device or the third network device needs to wait for the aging time of the first Objective to arrive, and the first Objective saved in the second network device or the third network device Cleared. Or the second network device or the third network device needs to wait for the first network device to initiate a discovery mechanism again, and the first Objective saved in the second network device or the third network device Cleared. Therefore, the useless Objective in the second network device or the third network device cannot be cleared in time, and the CPU and storage resources of the second network device or the third network device are occupied.
  • the first network device after the second network device deploys the first Objective, the first network device determines the first Objective saved locally. Whether it has changed. And if the first network device determines that the first Objective changed locally, the first network device sends a first Objective change message to the second network device.
  • the first Objective change message is used to indicate the change of the first Objective
  • the first Objective change message is used to trigger the second network device to change the second according to the first Objective change message.
  • the first Objective saved locally by the second network device is an Objective received by the second network device from the first network device.
  • the second network device deletes the first Objective saved locally by the second network device according to the first Objective change message.
  • the second network device updates the locally saved device of the second network device according to the new Objective carried by the first Objective change message. Said the first Objective.
  • the network device when the network device detects that the locally saved Objective changes, the network device automatically notifies the peer network device of the network device of the change of the Objective, so that the peer network device changes the local save in time.
  • the Objective helps the peer network device to reduce CPU and storage resource usage.
  • any two network devices are a pair of peers.
  • the first network device and the second network device are a pair of peers
  • the second network device and the third network device are a pair of peers.
  • "a pair of peers" can be understood as: one device is the peer of another device.
  • the first network device and the second network device being a pair of peers may be understood to mean that the first network device is a peer of the second network device, or is understood to be the second network device. Is the peer of the first network device.
  • the peer can also be referred to as a neighbor.
  • FIG. 2 is an information processing method of an ANIMA network according to an embodiment of the present application.
  • the method shown in Figure 2 can be applied to the ANIMA network shown in Figure 1.
  • the ANIMA network includes a first network device and a second network device.
  • the method shown in FIG. 2 includes S101 to S107.
  • the first network device sends a first Objective to the second network device, where the first network device and the second network device run an ANIMA protocol.
  • the first network device first acquires the first Objective.
  • the first network device may acquire the first Objective by means of a network administrator, or may acquire the first Objective from another network device (for example, a network management device).
  • the first network device After the first network device acquires the first Objective, the first Objective is saved.
  • the first network device may save the first Objective in a cache.
  • the cache may be a memory that implements temporary storage.
  • the first Objective may be an Objective used by the first network device and the second network device to implement a discovery mechanism, a synchronization mechanism, a negotiation mechanism, or a flooding mechanism.
  • the first Objective includes a name and a vlaue, and the name is used to identify the Objective, and the value refers to a configuration parameter included in the Objective for a network device.
  • the first network device may send the first Objective to the second network device via a first port of the first network device, thereby deploying the first Objective to the second network device.
  • the first port of the first network device is connected to a communication link between the first network device and the second network device.
  • the first network device and the second network device both run an ANIMA protocol, and therefore, the first network device and the second network device can implement a GRASP function.
  • the first Objective may be configured to trigger the second network device to configure the second network device according to the first Objective.
  • the GRASP message may be exchanged between the first network device and the second network device.
  • the first Objective can be carried in a GRASP message.
  • the second network device receives the first Objective sent by the first network device.
  • the second network device saves the first Objective.
  • the second network device may receive the first Objective sent by the first network device via the communication link. For example, the second network device receives a GRASP message sent by the first network device, where the GRASP message carries the first Objective. After receiving the GRASP message, the second network device acquires the first Objective and saves the first Objective in a cache of the second network device.
  • the cache may be a memory that implements temporary storage.
  • the second network device may further determine, according to the information type (message_TYPE) carried in the GRASP message, that the first Objective belongs to the Objective used in any of the mechanisms mentioned above. Then, the second network device configures the second network device according to the value included by the first Objective.
  • the first network device determines whether the first Objective saved locally is changed.
  • the change of the first Objective may include the first Objective being deleted or the value included in the first Objective being modified.
  • the value included in the first Objective may be modified to include that the partial value is modified or all values are modified.
  • the first Objective includes an IPv6 address, and the IPv6 address parameter included in the first Objective is modified due to a user configuration change.
  • the first network device determines that the first Objective change is locally saved, the first network device sends a first Objective change message to the second network device to indicate that the second network device changes.
  • the first Objective from the first network device saved locally by the second network device.
  • the first network device determines that the first Objective changed locally, the first network device generates the first Objective change message according to the change of the first Objective.
  • the first Objective change message is used to indicate the change of the first Objective.
  • the first Objective is deleted, and the first Objective change message is used to indicate that the first Objective is deleted.
  • the value included in the first Objective is modified, and the first Objective change message is used to indicate the modified first Objective.
  • the first network device sends a first Objective change message to the second network device via the first port of the first network device.
  • the first Objective change message is used to trigger the second network device to perform the first Objective from the first network device that is locally saved by the second network device according to the first Objective change message. The corresponding change.
  • the first Objective that is locally saved and saved by the first network device is the same as the first Objective that is locally saved and saved by the second network device. .
  • the following describes an implementation manner in which the first network device determines that the first Objective changes, and generates and sends the first Objective change message, by using FIG. 3 as an example.
  • the first network device may include an ANIMA control component and a GRASP component.
  • the ANIMA control component is configured to manage and schedule other components in the first network device.
  • the GRASP component is configured to implement a GRASP function.
  • the GRASP component is further configured to generate and send the The first Objective change message.
  • the first network device may further include a configurator (CFG) component and/or a command line interface (CLI) component.
  • the CFG component is used to manage and configure a configuration file.
  • the CLI component is for interaction between a user and the first network device.
  • the ANIMA control component, the GRASP component, the CFG component, and the CLI component may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the method shown in FIG. 3 includes S1101 to S1105.
  • the CLI component or the CFG component detects whether the first Objective changes.
  • the first network device may detect, by the CLI component or the CFG component, whether the first Objective has changed. For example, the user changes the value in the first Objective through the CLI component, or the user deletes the first Objective through the CLI component, or the user inputs a new first Objective through the CLI component. In this way, the CLI component can determine that the first Objective has changed. For another example, based on the user's configuration change request, the ANIMA control component invokes the CFG component to reconfigure the first Objective. In this way, the CFG component can determine that the first Objective changes.
  • the CLI component or the CFG component determines that the first Objective changes, generates a first message, and sends the first message to the ANIMA control component.
  • the CLI component or the CFG component may generate a first message, the first message being used to indicate a change of the first Objective.
  • the change is that the first Objective is deleted, and the first message includes a name and an initiator of the first Objective.
  • the initiator is used to indicate the network device that initiates the first Objective, or can be understood as a network device that initiates a discovery mechanism, a synchronization mechanism, a negotiation mechanism, or a flooding mechanism.
  • the first message may not carry any value in the first Objective, indicating that the change indicated by the first message is deleting the first Objective.
  • the first message may further include a change type, and the change type is set to delete.
  • the first message may further include a value in the first Objective. Indicates that the value in the first Objective is deleted.
  • the change is that the value in the first Objective is modified, and the first message includes the modified first Objective and initiator.
  • the first message carries a modified first Objective, indicating that the change indicated by the first message is to modify the first Objective.
  • the first message may further include a change type, and the change type is set to be modified.
  • the change type is set to be modified, the first message does not carry the modified first Objective, but carries a new value of the specifically modified parameter value, and the first message further carries The parameter type of the new value, which is used to indicate the new value.
  • the first message is sent to the ANIMA control component.
  • the format of the first message may use a messaging format internal to the network device, such as a socket message.
  • the ANIMA control component forwards the first message to the GRASP component.
  • the GRASP component generates the first Objective change message according to the first message.
  • the GRASP component sends the first Objective change message.
  • the ANIMA control component is configured to manage and schedule other components in the first network device, and after receiving the first message, the ANIMA control component determines that the first message is used to indicate the first An Objective change sends the first message to the GRASP component. After receiving the first message, the GRASP component may generate the first Objective change message by using information in the first message. Then, the GRASP component sends the first Objective change message to the second network device.
  • the first Objective change packet For a specific implementation manner of the first Objective change packet, refer to the following description of the application.
  • S1101 to S1105 illustrate that the CLI component or the CFG component actively reports the implementation of the first Objective change to the GRASP component by using the ANIMA control component.
  • the GRASP component can actively request the ANIMA control component to query whether the first Objective of the ANIMA control component changes.
  • the ANIMA control component invokes the CLI component or the CFG component for reporting.
  • For the process of reporting the CLI component or the CFG component refer to the descriptions of S1101 to S1105 above, and details are not described herein.
  • the second network device receives the first Objective change message sent by the first network device, where the first Objective change message is that the first network device is local to the first network device.
  • the saved first Objective is generated by a change.
  • the second network device changes, according to the first Objective change message, the first Objective from the first network device that is saved by the second network device, where the first network device locally saves The first Objective that has changed is the same as the first Objective that is locally saved by the second network device.
  • the first network device sends the first Objective change message to the second device via a first port of the first network device.
  • the second network device may receive the first Objective change message via the communication link.
  • the second network device parses the first Objective change message. Determining a change type of the first Objective indicated by the first Objective change message.
  • the second network device determines that the change type is to delete the first Objective
  • the second network device deletes the first Objective from the first network device saved by the second network device.
  • the second network device determines that the change type is to modify the value in the first Objective
  • the second network device modifies the first according to the new first Objective carried by the first Objective change message.
  • the second network device may replace the first Objective saved by the second network device by using a new first Objective carried by the first Objective change message.
  • modifying the value in the first Objective may include modification of a partial value or modification of all values.
  • the first Objective change message does not carry a new first Objective, but carries the A parameter value that is specifically modified in an Objective.
  • the second network device replaces the modified parameter value with the corresponding parameter value in the first Objective saved by the second network device.
  • the first Objective that is locally saved and saved by the first network device is the same as the first Objective that is locally saved and saved by the second network device. .
  • the network device when the network device detects that the locally saved Objective changes, the network device automatically notifies the peer network device of the network device of the change of the Objective, so that the peer network The device can change the locally saved Objective in time to help the peer network device reduce the CPU and storage resources.
  • the foregoing embodiment describes an implementation manner in which the first network device sends a first Objective change message to the second network device. It should be noted that the first network device may send an Objective change message to multiple network devices according to the foregoing implementation manner.
  • the second network device after receiving the Objective change packet sent by the first network device, may continue to forward the Objective change packet to the next hop network device of the second network device according to the foregoing implementation manner.
  • the first network device acquires an ANIMA message, and the de-enable ANIMA message is used to instruct the first network device to disable the ANIMA function of the first port,
  • the first port is a port that the first network device sends the first Objective to the second network device.
  • the first network device sends a second Objective change message to the second network device to indicate the The second network device deletes the first Objective saved locally by the second network device according to the second Objective change message.
  • the first network device when the first network device detects that the first Objective changes, the first network device may send the first Objective change message to the second network device, so as to trigger The second network device changes the first Objective saved locally by the second network device according to the first Objective change message.
  • the first port used by the first network device to send the first Objective may be disabled to enable the ANIMA function. For example, a configuration change causes the first interface to no longer run the ANIMA function. In this way, the first network device can obtain the de-enabled ANIMA message of the first port, and the de-enable ANIMA message is used to instruct the first network device to disable the ANIMA function of the first port.
  • the first network device parses the de-enabled ANIMA message, and sends a second Objective change message to the second network device before performing the ANIMA function of the first port.
  • the second Objective change message of the second network device deletes the first Objective saved locally by the second network device.
  • the network device when the port of the network device exits the ANIMA domain, the network device automatically notifies the peer network device of the network device that the port exits the ANIMA domain, so that the peer network device deletes the local save in time.
  • the Objective helps the peer network device to reduce CPU and storage resource usage.
  • the network device may be globally disabled.
  • the global de-enablement means that the entire network device exits the ANIMA domain.
  • the ANIMA function can be disabled for all ports of the network device that are running the ANIMA function. For each port, refer to the foregoing implementation manner, and details are not described herein.
  • the second network device forwards the first Objective to the third network device.
  • the second network device determines whether a communication link is faulty, and the communication link is that the second network device receives the first Objective communication link sent by the first network device.
  • the second network device sends a second Objective change message to the third network device to indicate that the third network device is configured according to the second Objective
  • the change message deletes the first Objective saved locally by the third network device.
  • the second network device may be connected to a third network device.
  • the second network device may send the third network device to a third network device via a communication link between the second network device and the third network device. Forwarding the first Objective.
  • the third network device can save the first Objective and configure the third network device based on the first Objective.
  • the second network device when the first network device receives the first Objective, not only stores the first Objective but also records that the second network device receives the port information of the first Objective.
  • the first Objective is in a corresponding relationship with the port of the second network device that receives the first Objective.
  • the second network device also determines whether a communication link between the first network device and the second network device has failed.
  • the communication link is for transmitting the first Objective.
  • the second network device closes a port of the second network device that is connected to the communication link.
  • the second network device records the receiving port when receiving the first Objective sent by the first network device, and therefore, the second network device may determine that the second network device is turned off according to the corresponding relationship mentioned above.
  • the port is the port that receives the first Objective.
  • the second network device generates the second Objective change message, where the second Objective change message is used to indicate that the first Objective needs to be deleted.
  • the second network device sends the second Objective change message to the third network device, where the second Objective change message is used to trigger the third network device to delete according to the second Objective change message.
  • the first Objective saved locally by the third network device.
  • the network device when the network device finds that the upstream link receiving the Objective is faulty, the network device automatically notifies the peer network device downstream of the network device to delete the Objective, so that the downstream peer network device Deleting the locally saved Objective in time helps the downstream peer network device reduce the CPU and storage resources.
  • the first Objective change message is a GRASP message
  • the GRASP message includes a first identifier, where the first identifier is used to indicate that the GRASP message is an Objective change message.
  • the GRASP message further includes a second identifier, where the second identifier is used to indicate a change type of the first Objective saved locally by the second network device.
  • the GRASP message may be exchanged between the first network device, the second network device, and the third network device, and the GRASP message may be used to implement the first Objective change message.
  • the first Objective change message may be implemented by multiplexing an existing GRASP message defined by GRASP; in another possible implementation, a new GRASP message implementation may be defined in GRASP. The first Objective change message.
  • FIG. 4 illustrates a message format of the first Objective change message implemented by multiplexing an existing GRASP message defined by GRASP.
  • the GRASP message shown in FIG. 4 is referred to as a first GRASP message.
  • the first GRASP message includes a time-to-live (TTL), and in the GRASP, the TTL is used to indicate that the Objective carried by the first GRASP message survives in a network device. time.
  • the length of the TTL is 32 bits, and the value ranges from 0 ms to 4294967295 ms, and ms represents milliseconds.
  • the present application implements the first identifier by multiplexing the TTL in the first GRASP message, where the first identifier is used to indicate that the first GRASP message is the first Objective change message.
  • the TTL value is defined as the first identifier, that is, when the TTL value is all F, the first GRAPH message is used to indicate that the first GRIPS message is the first Objective change packet, indicating that the TTL is A change that occurred in Objective.
  • the first GRASP message may further include a message type (message_type), a session identifier (session-id), an initiator (initiator), an object name (objective-name), an object-objective (objective-flag), and a loop number (loop). -count).
  • the first GRASP message may further include an objective value.
  • the message_type is used to indicate the type of the first GRASP message, for example, M_DISCOVERY indicates a GRASP message used in the discovery mechanism.
  • Session-id refers to the identity of the GRASP session.
  • the initiator refers to the initiator of the mechanism mentioned in this application, and is also the initiator of the first Objective mentioned in this application, such as the first network device of the present application.
  • the objective-name refers to the name of the Objective defined in the foregoing embodiment of the present application.
  • the objective-value refers to the value included in the Objective defined in the foregoing embodiment of the present application.
  • the objective-flag is used to indicate a discovery session, a negotiation session, a synchronization session, or a dry-run negotiation.
  • the loop-count is used to indicate the range in which the first GRASP message is transmitted. For example, when the value is 1, the first GRASP message may be propagated to the second network device, and when the value is 2, the first GRASP message may be It is propagated to the third network device.
  • the first GRASP message sent by the first network device and received by the second network device includes a first identifier.
  • the first identifier is a TTL, and the value of the TTL is all F, indicating that the first GRASP message is the first Objective change message.
  • the first GRASP message includes an objective-name, but does not include an objective-value
  • the first GRASP message is used to perform an Objective Change message for deleting the first Objective.
  • the first GRASP message includes an objective-name, and further includes an objective-value
  • the first GRASP message is an Objective Change message for performing a modification of the value included in the first Objective.
  • the first GRASP message may carry a second Objective, the second Objective includes a modified value, and the second Objective is used to replace the first Objective.
  • the objective-value in the first GRASP message is a value in the second Objective.
  • FIG. 5 illustrates the implementation of the message format of the first Objective change message by defining a new GRASP message in GRASP.
  • the GRASP message shown in FIG. 5 is referred to as a second GRASP message.
  • the second GRASP message includes a message_type.
  • the message_type is redefined, for example, the value of the message_type is set to 98 (representative: M_DELETE), indicating that the second GRASP message is the first Objective change message. Therefore, the newly defined message_type is equivalent to the aforementioned first identifier.
  • the second GRASP message further includes an objective-flag.
  • the objective-flag is redefined, for example, the value of the objective-flag is set to 5 (representative: F_DEL), indicating that the second GRASP message is used to perform the deletion of the Objective change message of the first Objective;
  • the value of the objective-flag is set to 4 (representative: F_MODIFY), indicating that the second GRASP message is an Objective change message for performing a modification of the value included in the first Objective. Therefore, the newly defined objective-flag is equivalent to the aforementioned second identifier.
  • the second GRASP message may further include a session-id, an initiator, an objective-name, an objective-flag, and a loop-count.
  • the first GRASP message may further include an objective-value.
  • the second GRASP message sent by the first network device and received by the second network device includes a first identifier.
  • the first identifier is a message_type
  • the value of the message_type is 98 (representative: M_DELETE), indicating that the second GRASP message is the first Objective change message. If the second GRASP message includes an objective-name, but does not include an objective-value, the second GRASP message is used to perform an Objective Change message for deleting the first Objective.
  • the second GRASP message includes an objective-name, and further includes an objective-value
  • the second GRASP message is an Objective Change message for performing a modification of the value included in the first Objective.
  • the second GRASP message may carry a second Objective, the second Objective includes a modified value, and the second Objective is used to replace the first Objective.
  • the objective-value in the second GRASP message is a value in the second Objective.
  • the second GRASP message further includes a second identifier on the basis of the foregoing first identifier.
  • the second identifier is an objective-flag. Setting the value of the objective-flag to 5 (representing: F_DEL), indicating that the second GRASP message is for performing an Objective change message for deleting the first Objective; setting the value of the objective-flag to 4 (representing: F_MODIFY), indicating that the second GRASP message is an Objective Change message for performing a modification of the value included in the first Objective.
  • F_DEL presents: F_DEL
  • F_MODIFY indicating that the second GRASP message is an Objective Change message for performing a modification of the value included in the first Objective.
  • FIG. 6 illustrates an embodiment in which Objective is added on the basis of FIG. 5, that is, the second GRASP message may carry multiple Objectives.
  • the network device can implement operations on multiple Objectives according to an Objective change message. Conducive to saving transmission bandwidth and CPU resource consumption.
  • FIG. 6 reference may be made to the foregoing description of FIG. 5, and details are not described herein.
  • FIG. 7 is a schematic structural diagram of a first network device 1000 according to an embodiment of the present application.
  • the first network device 1000 shown in FIG. 7 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the first network device is deployed in an ANIMA network, and the ANIMA network further includes a second network device.
  • the first network device 1000 includes a transmitting unit 1002 and a processing unit 1004.
  • the sending unit 1002 is configured to send a first Objective to the second network device, where the first network device and the second network device run an ANIMA protocol;
  • the processing unit 1004 is configured to determine whether the first Objective saved locally is changed.
  • the sending unit 1002 is further configured to send a first Objective change message to the second network device to instruct the second network device to change the location.
  • the first Objective from the first network device saved locally by the second network device, where the first Objective and the second network device that are locally saved by the first network device are locally saved The first Objective of the change is the same.
  • the processing unit 1004 is configured to determine whether the locally saved first Objective change is performed, where the processing unit 1004 is configured to determine whether the locally saved first Objective is deleted; The processing unit 1004 determines that the first Objective change is locally saved, and the sending unit 1002 is further configured to send, by the second network device, a first Objective change message to instruct the second network device to change the second
  • the first Objective from the first network device saved locally by the network device specifically includes: when the processing unit 1004 determines that the first Objective saved locally is deleted, the sending unit 1002 is further configured to The second network device sends a first Objective change message to instruct the second network device to delete the first Objective from the first network device that is saved locally by the second network device.
  • the processing unit 1004 is configured to determine whether the locally saved first Objective change occurs, where the processing unit 1004 is configured to determine whether the locally saved first Objective is modified; The processing unit 1004 determines that the first Objective change is locally saved, and the sending unit 1002 is further configured to send, by the second network device, a first Objective change message to instruct the second network device to change the second
  • the first Objective from the first network device saved locally by the network device specifically includes: when the processing unit 1004 determines that the first Objective saved locally is modified, the sending unit 1002 is further configured to The second network device sends a first Objective change message to instruct the second network device to modify the first Objective from the first network device that is locally saved by the second network device.
  • the processing unit 1004 is further configured to obtain an ANIMA message, where the ANIMA message is used to instruct the processing unit 1004 to disable the ANIMA function of the first port, where the first port is the
  • the sending unit 1002 sends the port of the first Objective to the second network device; before the processing unit 1004 turns off the ANIMA function of the first port according to the de-enable ANIMA message, the sending unit 1002 further
  • the second network device is configured to send, by the second network device, the second network device to delete, according to the second Objective change message, the second network device locally saved from the first network device.
  • the first Objective is configured to obtain an ANIMA message, where the ANIMA message is used to instruct the processing unit 1004 to disable the ANIMA function of the first port, where the first port is the
  • the sending unit 1002 sends the port of the first Objective to the second network device; before the processing unit 1004 turns off the ANIMA function of the first port according to the de-enable ANIMA message, the sending unit 1002 further
  • the first network device shown in FIG. 7 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the network device detects that the locally saved Objective changes, the network device automatically notifies the peer network device of the network device of the change of the Objective, so that the peer network device changes in time.
  • the locally saved Objective helps the peer network device to reduce the CPU and storage resources.
  • FIG. 8 is a schematic structural diagram of hardware of a first network device 1100 according to an embodiment of the present application.
  • the first network device 1100 shown in FIG. 8 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the first network device 1100 includes a processor 1101, a memory 1102, an interface 1103, and a bus 1104.
  • the interface 1103 can be implemented by using a wireless or wired manner, and specifically can be a network card.
  • the above processor 1101, memory 1102, and interface 1103 are connected by a bus 1104.
  • the interface 1103 may specifically include a transmitter and a receiver, configured to send and receive information between the first network device and the second network device in the foregoing embodiment.
  • the interface 1103 is configured to support sending the first Objective and the first Objective change message to the second network device.
  • the interface 1103 is used to support the processes S101 and S105 of FIG.
  • the processor 1101 is configured to perform processing performed by the first network device in the foregoing embodiment.
  • the processor 1101 is configured to determine whether a locally saved first Objective has changed; and/or other processes for the techniques described herein.
  • the processor 1101 is configured to support the process S104 of FIG.
  • the memory 1102 includes an operating system 11021 and an application 11022 for storing programs, codes, or instructions that can be executed when a processor or a hardware device executes the programs, code, or instructions.
  • the memory 1102 can include a read-only memory (English: Read-only Memory, abbreviated as ROM) and a random access memory (English: Random Access Memory, abbreviation: RAM).
  • ROM Read-only Memory
  • RAM Random Access Memory
  • the first network device 1100 When the first network device 1100 needs to be run, booting is performed by the BIOS in the ROM or the bootloader booting system in the embedded system, and the first network device 1100 is booted into a normal running state. After the first network device 1100 enters the normal running state, the application program and the operating system running in the RAM are executed, thereby completing the processing procedure involving the first network device in the method embodiment.
  • FIG. 8 only shows a simplified design of the first network device 1100.
  • the first network device can contain any number of interfaces, processors or memories.
  • FIG. 9 is a schematic structural diagram of hardware of another first network device 1200 according to an embodiment of the present application.
  • the first network device 1200 shown in FIG. 9 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the first network device 1200 includes: a main control board 1210 , an interface board 1230 , a switching network board 1220 , and an interface board 1240 .
  • the main control board 1210, the interface boards 1230 and 1240, and the switching network board 1220 are connected to each other through the system bus to implement interworking.
  • the main control board 1210 is used to complete functions such as system management, device maintenance, and protocol processing.
  • the switching network board 1220 is used to complete data exchange between each interface board (also referred to as a line card or a service board).
  • the interface boards 1230 and 1240 are configured to provide various service interfaces (for example, a POS interface, a GE interface, an ATM interface, etc.), and implement forwarding of data packets.
  • the interface board 1230 may include a central processing unit 1231, a forwarding entry storage 1234, a physical interface card 1233, and a network processor 1232.
  • the central processing unit 1231 is configured to control and manage the interface board and communicate with the central processing unit on the main control board.
  • the forwarding entry storage 1234 is used to save forwarding entries.
  • the physical interface card 1233 is used to complete the reception and transmission of traffic.
  • the network storage 1232 is configured to control the physical interface card 1233 to send and receive traffic according to the forwarding entry.
  • the physical interface card 1233 is configured to send the first Objective and the first Objective change message to the second network device.
  • the central processing unit 1211 is further configured to determine whether a locally saved first Objective has changed. When the central processing unit 1211 determines that the locally saved first Objective changes, the physical interface card 1233 is triggered to send the first Objective change message to the second network device.
  • the central processing unit 1211 is further configured to generate the first Objective and the first Objective change message.
  • the central processing unit 1211 transmits the first Objective and the first Objective change message to the physical interface card 1233 via the central processing unit 1231.
  • the physical interface card 1233 sends the first Objective and the first Objective change message to the second network device.
  • the central processing unit 1231 is further configured to control the network storage 1232 to obtain the forwarding entry in the forwarding entry storage 1234, and the central processing unit 1231 is further configured to control the network storage 1232 to complete the receiving and transmitting of the traffic via the physical interface card 1233.
  • the operation on the interface board 1240 in the embodiment of the present invention is consistent with the operation of the interface board 1230, and details are not described herein for brevity.
  • the first network device 1200 of the present embodiment may correspond to the functions and/or various steps of the foregoing method embodiments, and details are not described herein again.
  • the main control board may have one or more blocks, and when there are multiple blocks, the main control board and the standby main control board may be included.
  • the interface board may have one or more blocks. The stronger the data processing capability of the first network device, the more interface boards are provided.
  • the physical interface card on the interface board can also have one or more blocks.
  • the switching network board may not exist, and there may be one or more blocks. When there are multiple blocks, the load sharing redundant backup can be implemented together.
  • the first network device does not need to exchange the network board, and the interface board undertakes the processing function of the service data of the entire system.
  • the first network device may have at least one switching network board, and implement data exchange between multiple interface boards through the switching network board to provide large-capacity data exchange and processing capability. Therefore, the data access and processing capabilities of the first network device of the distributed architecture are greater than those of the centralized architecture. Which architecture is used depends on the specific network deployment scenario, and is not limited here.
  • FIG. 10 is a schematic structural diagram of a second network device 2000 according to an embodiment of the present application.
  • the second network device 2000 shown in FIG. 10 can perform the corresponding steps performed by the second network device in the method of the above embodiment.
  • the second network device is deployed in an ANIMA network, and the ANIMA network further includes a first network device.
  • the second network device 2000 includes a receiving unit 2002, a processing unit 2004, and a storage unit 2006.
  • the receiving unit 2002 is configured to receive a first Objective sent by the first network device, where the first network device and the second network device run an ANIMA protocol;
  • the storage unit 2006 is configured to save the first Objective
  • the receiving unit 2002 is further configured to receive a first Objective change message sent by the first network device, where the first Objective change message is locally saved by the first network device in response to the first network device
  • the first Objective is generated by a change
  • the processing unit 2004 is configured to change, according to the first Objective change message, the first Objective saved by the storage unit 2006, where the first Objective that is locally saved by the first network device is changed.
  • the first Objective that is changed by the storage unit 2006 is the same.
  • the processing unit 2004 is configured to: according to the first Objective change message, the first Objective that is saved by the storage unit 2006, specifically: the processing unit 2004 is configured to use, according to the first Objective The change message deletes the first Objective saved by the storage unit 2006.
  • the processing unit 2004 is configured to: according to the first Objective change message, the first Objective that is saved by the storage unit 2006, specifically: the processing unit 2004 is configured to use, according to the first Objective The change message modifies the first Objective saved by the storage unit 2006.
  • the second network device further includes: a sending unit 2008, configured to forward the first Objective to the third network device; the processing unit 2004 is further configured to determine whether the first communication link is faulty, The first communication link is that the receiving unit 2002 receives the first Objective communication link sent by the first network device; when the processing unit 2004 determines that the first communication link is faulty, the sending unit The 2008 is further configured to send a second Objective change message to the third network device to instruct the third network device to delete the first Objective saved locally by the third network device.
  • a sending unit 2008 configured to forward the first Objective to the third network device
  • the processing unit 2004 is further configured to determine whether the first communication link is faulty, The first communication link is that the receiving unit 2002 receives the first Objective communication link sent by the first network device; when the processing unit 2004 determines that the first communication link is faulty, the sending unit The 2008 is further configured to send a second Objective change message to the third network device to instruct the third network device to delete the first Objective saved locally by the third network device.
  • the second network device shown in FIG. 10 can perform the corresponding steps performed by the second network device in the method of the above embodiment.
  • the network device detects that the locally saved Objective changes, the network device automatically notifies the peer network device of the network device of the change of the Objective, so that the peer network device changes in time.
  • the locally saved Objective helps the peer network device to reduce the CPU and storage resources.
  • FIG. 11 is a schematic structural diagram of hardware of a second network device 2100 according to an embodiment of the present application.
  • the second network device 2100 shown in FIG. 11 can perform the corresponding steps performed by the second network device in the method of the above embodiment.
  • the second network device 2100 includes a processor 2101, a memory 2102, an interface 2103, and a bus 2104.
  • the interface 2103 can be implemented by using a wireless or wired manner, and specifically can be a network card.
  • the above processor 2101, memory 2102, and interface 2103 are connected by a bus 2104.
  • the interface 2103 may specifically include a transmitter and a receiver, configured to send and receive information between the second network device and the first network device in the foregoing embodiment, or used in the second network device and the third network in the foregoing embodiment. Send and receive information between devices.
  • the interface 2103 is configured to support receiving the first Objective and the first Objective change message sent by the first network device, or to support sending the first Objective and the second Objective change report to the third network device. Text.
  • the interface 2103 is used to support processes S102 and S106 in FIG.
  • the processor 2101 is configured to perform processing performed by the second network device in the foregoing embodiment.
  • the processor 2101 is configured to change, according to the first Objective change message, a first Objective saved by the memory 2102, and further configured to determine, between the second network device and the first network device, Transmitting whether the first communication link of the first Objective fails; and/or other processes for the techniques described herein.
  • the processor 2101 is configured to support the process S107 of FIG.
  • the memory 2102 includes an operating system 21021 and an application program 21022 for storing programs, codes, or instructions that can be executed when a processor or a hardware device executes the programs, codes, or instructions.
  • the memory 2102 may include a read only memory (English: Read-only Memory, abbreviated as ROM) and a random access memory (English: Random Access Memory, abbreviation: RAM).
  • the ROM includes a basic input/output system (English: Basic Input/Output System, BIOS) or an embedded system;
  • the RAM includes an application and an operating system.
  • BIOS Basic Input/Output System
  • the second network device 2100 needs to be run, booting is performed by the BIOS in the ROM or the bootloader booting system in the embedded system, and the second network device 2100 is booted into a normal running state. After the second network device 2100 enters the normal running state, the application program and the operating system running in the RAM are executed, thereby completing the processing procedure involving the second network device in the method embodiment.
  • FIG. 11 merely shows a simplified design of the second network device 2100.
  • the second network device can include any number of interfaces, processors or memories.
  • FIG. 12 is a schematic structural diagram of hardware of another second network device 2200 according to an embodiment of the present application.
  • the second network device 2200 shown in FIG. 12 can perform the corresponding steps performed by the second network device in the method of the above embodiment.
  • the second network device 2200 includes: a main control board 2210, an interface board 2230, a switching network board 2220, and an interface board 2240.
  • the main control board 2210, the interface boards 2230 and 2240, and the switching network board 2220 are connected to each other through the system bus to implement interworking.
  • the main control board 2210 is used to complete functions such as system management, device maintenance, and protocol processing.
  • the switching network board 2220 is used to complete data exchange between each interface board (also called a line card or a service board).
  • the interface boards 2230 and 2240 are configured to provide various service interfaces (for example, a POS interface, a GE interface, an ATM interface, etc.), and implement forwarding of data packets.
  • the interface board 2230 can include a central processor 2231, a forwarding entry storage 2234, a physical interface card 2233, and a network processor 2232.
  • the central processing unit 2231 is configured to control and manage the interface board and communicate with the central processing unit on the main control board.
  • the forwarding entry storage 2234 is used to save forwarding entries.
  • the physical interface card 2233 is used to complete the reception and transmission of traffic.
  • the network storage 2232 is configured to control the physical interface card 2233 to send and receive traffic according to the forwarding entry.
  • the physical interface card 2233 is configured to receive the first Objective and the first Objective change message sent by the first network device, or to send the first Objective and the second Objective change message to the third network device. .
  • the central processing unit 2211 is further configured to: change the first Objective saved by the second network device according to the first Objective change message; and further to determine, between the second network device and the first network device, Whether the first communication link for transmitting the first Objective fails.
  • the central processing unit 2211 determines that the first communication link is faulty, the physical interface card 2233 is triggered to send the second Objective change message to the third network device.
  • the central processing unit 2211 is further configured to generate the second Objective change message.
  • the central processing unit 2211 transmits the first Objective and the second Objective change message to the physical interface card 2233 via the central processing unit 2231.
  • the physical interface card 2233 sends the first Objective and the second Objective change message to the third network device.
  • the central processing unit 2231 is further configured to control the network storage 2232 to obtain the forwarding entry in the forwarding entry storage 2234, and the central processing unit 2231 is further configured to control the network storage 2232 to complete the receiving and transmitting of the traffic via the physical interface card 2233.
  • the operation on the interface board 2240 in the embodiment of the present invention is consistent with the operation of the interface board 2230, and details are not described herein for brevity.
  • the second network device 2200 of the present embodiment may correspond to the functions and/or various steps of the foregoing method embodiments, and details are not described herein again.
  • the main control board may have one or more blocks, and when there are multiple blocks, the main control board and the standby main control board may be included.
  • the interface board may have one or more blocks. The stronger the data processing capability of the second network device, the more interface boards are provided.
  • the physical interface card on the interface board can also have one or more blocks.
  • the switching network board may not exist, and there may be one or more blocks. When there are multiple blocks, the load sharing redundant backup can be implemented together.
  • the second network device does not need to exchange the network board, and the interface board undertakes the processing function of the service data of the entire system.
  • the second network device may have at least one switching network board, and exchange data between multiple interface boards through the switching network board to provide large-capacity data exchange and processing capability. Therefore, the data access and processing capabilities of the second network device of the distributed architecture are greater than those of the centralized architecture. Which architecture is used depends on the specific network deployment scenario, and is not limited here.
  • the first Objective change message is a GRASP message
  • the GRASP message includes a first identifier.
  • the first identifier is used to indicate that the GRASP message is an Objective change message.
  • the GRASP message further includes a second identifier, where the second identifier is used to indicate a change type of the first Objective from the first network device that is saved locally by the second network device.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the first network device, which includes a program designed to execute the foregoing method embodiments.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the second network device, which includes a program designed to execute the foregoing method embodiments.
  • the embodiment of the present application further includes an ANIMA network system, where the ANIMA network system includes a first network device and a second network device, where the first network device is the first network device in the foregoing FIG. 7 or FIG. 8 or FIG.
  • the second network device is the second network device in the foregoing FIG. 10 or FIG. 11 or FIG.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions.
  • the software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in the user equipment.
  • the processor and the storage medium may also reside as discrete components in the user equipment.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种ANIMA网络的信息处理方法、设备及系统。所述方法包括，第一网络设备向第二网络设备发送第一目标Objective，第一网络设备和第二网络设备运行有ANIMA协议。第一网络设备确定本地保存的第一Objective是否发生变更。当第一网络设备确定本地保存的第一Objective发生变更，第一网络设备向第二网络设备发送第一Objective变更报文以指示第二网络设备变更第二网络设备本地保存的来自第一网络设备的第一Objective。以便第二网络设备及时变更本地保存的Objective，有助于第二网络设备减少CPU和存储资源的占用。

Description

一种ANIMA网络的信息处理方法、设备及系统
本申请要求于2017年12月27日提交中国专利局、申请号为201711449449.6、申请名称为“一种ANIMA网络的信息处理方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种自主网络集成模型和方法(autonomic networking integrated model and approach，ANIMA)网络的信息处理方法、设备及系统。
背景技术
ANIMA网络是一种自组织型网络。ANIMA网络的自主化主要完成自主配置(self-configuration)、自主保护(self-protection)、自主治愈(self-healing)、自主优化(self-optimization)4个目的，以便通过自主功能最大限度的减少对网络管理员或集中管理系统的依赖。ANIMA网络在架构上分为自主业务代理(autonomic service agent，ASA)和自主网络底层架构(autonomic network infrastructure，ANI)两层。其中，ANI又分为引导程序(bootstrap)、自主控制平面(Autonomic Control Pannel，ACP)和通用自主信令协议(generic autonomic signaling protocol，GRASP)三个阶段。Bootstrap负责网络设备的安全启动和引导，网路设备加入ANIMA域的认证和域证书的分配。ACP负责网络设备之间建立逐跳(hop-by-hop)的加密互联网协议(Internet Protocol，IP)隧道，形成一个稳定的管理虚拟专用网络(virtual private network，VPN)，在该VPN中基于内部网关协议(interior gateway protocol，IGP)实现多跳网络设备之间的互通。GRASP是ASA之间交互的标准信令协议，负责使能ASA，完成动态邻居发现、同步状态和协商参数设置等功能。
技术目标(technical objective)，本文简称为目标(objective)，是指在GRASP的发现、同步、协商和洪泛机制中所操作的可配置参数或可配置参数集合。在ANIMA网络中，作为发起端的网络设备基于GRASP向作为接收端的网络设备发送Objective，以便接收端根据接收到的Objective进行配置。
在实际的应用场景中，当发起端的Objective发生变更时，接收端保存的Objective无法进行及时的变更，接收端只能等待接收端保存的Objective老化或者等待发起端再次启动Objective对应的发现、同步、协商或洪泛机制。
发明内容
有鉴于此，本申请实施例提供了一种ANIMA网络的信息处理方法、设备及系统，当网络设备检测到本地保存的Objective发生变更时，所述网络设备自动的向所述网络设备的对等体(peer)网络设备通知所述Objective的变更，以便所述peer网络设备及 时变更本地保存的Objective，有助于所述peer网络设备减少中央处理单元(central processing unit，CPU)和存储资源的占用。
本申请实施例提供的技术方案如下。
第一方面，提供了一种ANIMA网络的信息处理方法。所述方法包括，第一网络设备向第二网络设备发送第一Objective，其中，所述第一网络设备和所述第二网络设备运行有ANIMA协议。然后，所述第一网络设备确定本地保存的所述第一Objective是否发生变更。当所述第一网络设备确定本地保存的所述第一Objective发生变更，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
基于实施例提供的方案，在ANIMA网络场景中，当网络设备检测到本地保存的Objective发生变更时，所述网络设备自动的向所述网络设备的peer网络设备通知所述Objective的变更，以便所述peer网络设备及时变更本地保存的Objective，有助于所述peer网络设备减少CPU和存储资源的占用。
在第一方面的一种可能的实现方式中，所述第一网络设备确定本地保存的所述第一Objective是否发生变更包括：所述第一网络设备确定本地保存的所述第一Objective是否被删除。当所述第一网络设备确定本地保存的所述第一Objective发生变更，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective包括：当所述第一网络设备确定本地保存的所述第一Objective被删除，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备删除所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
在第一方面的又一种可能的实现方式中，所述第一网络设备确定本地保存的所述第一Objective是否发生变更包括：所述第一网络设备确定本地保存的所述第一Objective是否被修改。当所述第一网络设备确定本地保存的所述第一Objective发生变更，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective包括：当所述第一网络设备确定本地保存的所述第一Objective被修改，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备修改所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
在第一方面的再一种可能的实现方式中，所述第一网络设备获取去使能ANIMA消息，所述去使能ANIMA消息用于指示所述第一网络设备关闭第一端口的ANIMA功能，所述第一端口是所述第一网络设备向所述第二网络设备发送所述第一Objective的端口。在所述第一网络设备根据所述去使能ANIMA消息关闭所述第一端口的ANIMA功能前，所述第一网络设备向所述第二网络设备发送第二Objective变更报文以指示所述第二网络设备根据所述第二Objective变更报文删除所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
第二方面，提供了一种ANIMA网络的信息处理方法。所述方法包括，第二网络设备接收第一网络设备发送的第一Objective，所述第一网络设备和所述第二网络设备运行有ANIMA协议。并且，所述第二网络设备保存所述第一Objective。然后，所述 第二网络设备接收所述第一网络设备发送的第一Objective变更报文，所述第一Objective变更报文是所述第一网络设备响应于所述第一网络设备本地保存的所述第一Objective发生了变更而生成的。所述第二网络设备根据所述第一Objective变更报文变更所述第二网络设备本地保存的所述第一Objective。
基于实施例提供的方案，在ANIMA网络场景中，当网络设备检测到本地保存的Objective发生变更时，所述网络设备自动的向所述网络设备的peer网络设备通知所述Objective的变更，以便所述peer网络设备及时变更本地保存的Objective，有助于所述peer网络设备减少CPU和存储资源的占用。
在第二方面的一种可能的实现方式中，所述第二网络设备根据所述第一Objective变更报文变更所述第二网络设备本地保存的所述第一Objective包括：所述第二网络设备根据所述第一Objective变更报文删除所述第二网络设备保存的所述第一Objective。
在第二方面的又一种可能的实现方式中，所述第二网络设备根据所述第一Objective变更报文变更所述第二网络设备本地保存的所述第一Objective包括：所述第二网络设备根据所述第一Objective变更报文修改所述第二网络设备保存的所述第一Objective。
在第二方面的再一种可能的实现方式中，所述第二网络设备向第三网络设备转发所述第一Objective。所述第二网络设备确定第一通信链路是否发生故障，所述第一通信链路是所述第二网络设备接收所述第一网络设备发送的第一Objective的通信链路。当所述第二网络设备确定所述第一通信链路发生故障，所述第二网络设备向所述第三网络设备发送第二Objective变更报文以指示所述第三网络设备删除所述第三网络设备本地保存的所述第一Objective。
在上述第一方面或第二方面中，可选的，所述第一Objective变更报文为GRASP消息，所述GRASP消息包括第一标识，所述第一标识用于指示所述GRASP消息为Objective变更报文。进一步可选的，所述GRASP消息还包括第二标识，所述第二标识用于指示所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective的变更类型。
第三方面，提供了一种第一网络设备，所述第一网络设备具有实现上述方法中第一网络设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，第一网络设备的结构中包括处理器和接口，所述处理器被配置为支持第一网络设备执行上述方法中相应的功能。所述接口用于支持第一网络设备与第二网络设备之间的通信，向第二网络设备发送上述方法中所涉及的信息或者指令，或者从第二网络设备接收上述方法中所涉及的信息或者指令。所述第一网络设备还可以包括存储器，所述存储器用于与处理器耦合，其保存第一网络设备必要的程序指令和数据。
在另一个可能的设计中，所述第一网络设备包括：处理器、发送器、接收器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接发送器、接收器、随机存取存储器以及只读存储器。其中，当需要运行第一网络设备时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启 动，引导第一网络设备进入正常运行状态。在第一网络设备进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第四方面，提供一种第一网络设备，所述第一网络设备包括：主控板和接口板，进一步，还可以包括交换网板。所述第一网络设备用于执行第一方面或第一方面的任意可能的实现方式中的方法。具体地，所述第一网络设备包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的模块。
第五方面，提供一种第一网络设备，所述第一网络设备包括控制器和第一转发子设备。所述第一转发子设备包括：接口板，进一步，还可以包括交换网板。所述第一转发子设备用于执行第四方面中的接口板的功能，进一步，还可以执行第四方面中交换网板的功能。所述控制器包括接收器、处理器、发送器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接接收器、发送器、随机存取存储器以及只读存储器。其中，当需要运行控制器时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导控制器进入正常运行状态。在控制器进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第四方面中主控板的功能。
第六方面，提供了一种计算机存储介质，用于储存为上述第一网络设备所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述方面中第一网络设备的功能或步骤。
第七方面，提供了一种第二网络设备，所述第二网络设备具有实现上述方法中第二网络设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，第二网络设备的结构中包括处理器和接口，所述处理器被配置为支持第二网络设备执行上述方法中相应的功能。所述接口用于支持第二网络设备与第一网络设备之间的通信，向第一网络设备发送上述方法中所涉及的信息或者指令，或者从第一网络设备接收上述方法中所涉及的信息或者指令。所述第二网络设备还可以包括存储器，所述存储器用于与处理器耦合，其保存第二网络设备必要的程序指令和数据。
在另一个可能的设计中，所述第二网络设备包括：处理器、发送器、接收器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接发送器、接收器、随机存取存储器以及只读存储器。其中，当需要运行第二网络设备时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导第二网络设备进入正常运行状态。在第二网络设备进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第八方面，提供一种第二网络设备，所述第二网络设备包括：主控板和接口板，进一步，还可以包括交换网板。所述第二网络设备用于执行第二方面或第二方面的任意可能的实现方式中的方法。具体地，所述第二网络设备包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的模块。
第九方面，提供一种第二网络设备，所述第二网络设备包括控制器和第二转发子设备。所述第二转发子设备包括：接口板，进一步，还可以包括交换网板。所述第二转发子设备用于执行第八方面中的接口板的功能，进一步，还可以执行第八方面中交换网板的功能。所述控制器包括接收器、处理器、发送器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接接收器、发送器、随机存取存储器以及只读存储器。其中，当需要运行控制器时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导控制器进入正常运行状态。在控制器进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第八方面中主控板的功能。
第十方面，提供了一种计算机存储介质，用于储存为上述第二网络设备所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述方面中第二网络设备的功能或步骤。
第十一方面，提供一种ANIMA网络系统，所述ANIMA网络系统包括第一网络设备和第二网络设备，所述第一网络设备为前述第三方面或第四方面或第五方面中的第一网络设备，所述第二网络设备为前述第七方面或第八方面或第九方面中的第二网络设备。
通过上述方案，本申请实施例提供的ANIMA网络的信息处理方法、设备及系统。在ANIMA网络场景中，当网络设备检测到本地保存的Objective发生变更时，所述网络设备自动的向所述网络设备的peer网络设备通知所述Objective的变更，以便所述peer网络设备及时变更本地保存的Objective，有助于所述peer网络设备减少CPU和存储资源的占用。
附图说明
图1为本申请实施例的一种ANIMA网络结构示意图；
图2为本申请实施例的一种ANIMA网络的信息处理方法流程图；
图3为本申请实施例的一种生成和发送Objective变更报文的方法流程图；
图4为本申请实施例的一种Objective变更报文的报文格式图；
图5为本申请实施例的另一种Objective变更报文的报文格式图；
图6为本申请实施例的又一种Objective变更报文的报文格式图；
图7为本申请实施例的第一网络设备的结构示意图；
图8为本申请实施例的第一网络设备的硬件结构示意图；
图9为本申请实施例的另第一网络设备的硬件结构示意图；
图10为本申请实施例的第二网络设备的结构示意图；
图11为本申请实施例的第二网络设备的硬件结构示意图；
图12为本申请实施例的另第二网络设备的硬件结构示意图。
具体实施方式
下面通过具体实施例，分别进行详细的说明。
图1为本申请实施例的一种ANIMA网络结构示意图。如图1所示，所述ANIMA 网络包括第一网络设备、第二网络设备和第三网络设备。所述第一网络设备与所述第二网络设备通信，所述第二网络设备与所述第三网络设备通信。所述第一网络设备、第二网络设备和第三网络设备均运行ANIMA协议，更为具体的，所述第一网络设备、第二网络设备和第三网络设备均运行GRASP。
在ANIMA网络中，所述第一网络设备、第二网络设备和第三网络设备基于GRASP使能ASA，因此，在运行GRASP情况下，所述第一网络设备、第二网络设备和第三网络设备分别可以被称为第一ASA，第二ASA，第三ASA。GRASP是各个ASA之间交互的标准信令协议，以实现ASA之间的发现(discovery)、同步(synchronization)、协商(negotiation)和洪泛(flood)机制。GRASP通过在ASA之间传送Objective实现发现、同步、协商和洪泛机制。Objective按类型区分可以包括：发现Objective，同步Objective，协商Objective和洪泛Objective。其中，发现Objective在GRASP的发现机制中使用，同步Objective在GRASP的同步机制中使用，协商Objective在GRASP的协商机制中使用，洪泛Objective在GRASP的洪泛机制中使用。其中，在发现机制中，ASA可以通过发现Objective发现其他的ASA。在同步机制中，ASA可以通过同步Objective请求获取其他ASA中的当前参数值。在协商机制中，ASA可以通过协商Objective发起与其他ASA的协商，以便实现ASA之间的参数设置的迭代交互过程。在洪泛机制中，ASA可以通过洪泛Objective向其他ASA洪泛Objective中的值。其中，Objective可以包括名称(name)和值(value)，所述name用于标识所述Objective，所述value是指所述Objective中包括的用于网络设备的配置参数。
举例说明，图1中的所述第一网络设备作为Objective的发起端，所述第一网络设备通过GRASP实现与所述第二网络设备的发现机制。首先，所述第一网络设备获取第一Objective，所述第一Objective是发现Objective。所述第一网络设备可以通过网络管理员配置的方式获取所述第一Objective，也可以从其他网络设备(例如网管设备)获取所述第一Objective。所述第一网络设备获取所述第一Objective后，保存所述第一Objective，具体的，所述第一网络设备可以将所述第一Objective保存在缓存中。然后，所述第一网络设备向所述第二网络设备发送所述第一Objective。具体的，所述第一网络设备可以将所述第一Objective携带在GRASP消息(GRASP message)中，向所述第二网络设备发送所述GRASP消息。其中，在发现机制中，所述GRASP消息也可以被称为发现信息(discovery message)。所述第二网络设备接收到所述第一Objective后，将所述第一Objective进行保存，并且利用所述第一Objective对所述第二网络设备进行配置操作。所述第二网络设备还向所述第一网络设备发送发现响应消息(discovery response message)。
所述GRASP消息可以包括循环次数(loop-count)字段，所述loop-count字段用于指示所述GRASP消息转发的跳数。所述loop-count字段的取值范围为0到255。所述loop-count字段确保了所述第一Objective不仅可以发送到所述第二网络设备，还可以发送到与所述第一网络设备间隔大于1跳的网络设备。例如，图1中，所述第二网络设备还连接所述第三网络设备。所述第二网络设备接收到来自所述第一网络设备的所述第一Objective后，记录所述第二网络设备上、用于接收所述第一Objective的端口。所述第二网络设备利用所述第一Objective对所述第二网络设备进行配置操作，并 且根据所述GRASP消息中的所述loop-count字段的取值，将所述第一Objective转发到所述第三网络设备。所述第三网络设备接收到所述第一Objective后，将所述第一Objective进行保存，并且利用所述第一Objective对所述第三网络设备进行配置操作。所述第三网络设备还经由所述第二网络设备向所述第一网络设备发送发现响应消息。
所述第一网络设备在获取所述第一Objective后，可以向多个网络设备发送所述第一Objective。图1中，所述第一网络设备还连接第四网络设备。所述第一网络设备可以向所述第四网络设备发送所述第一Objective，以便所述第四网络设备利用所述第一Objective对所述第四网络设备进行配置操作。
上述实施方式中，以发现机制为例说明书Objective的传输过程。在同步机制、协商机制和洪泛机制中，传输Objective的实现过程类似，此处不进行赘述。
所述第一网络设备在发送Objective后，所述Objective可能发生变更。所述变更包括所述Objective被删除和所述Objective中的部分值或全部值被修改。例如，由于用户配置变更导致原有的Objective被删除或者导致原有的Objective包括的互联网协议第6版(Internet Protocol version 6，IPv6)地址参数被修改。
在实际的应用场景中，例如图1，当所述第一网络设备本地保存的第一Objective发生变更，例如所述第一网络设备本地保存的所述第一Objective被删除，所述第二网络设备或所述第三网络设备无法感知。其中，所述第一Objective使用在发现机制中。因此，所述第二网络设备或所述第三网络设备需要等待所述第一Objective的老化时间到达，所述第二网络设备或所述第三网络设备中保存的所述第一Objective才会被清除。或者所述第二网络设备或所述第三网络设备需要等待所述第一网络设备再次发起发现机制，所述第二网络设备或所述第三网络设备中保存的所述第一Objective才会被清除。因此，所述第二网络设备或所述第三网络设备中的无用Objective不能被及时清除，增加了所述第二网络设备或所述第三网络设备的CPU和存储资源的占用。
在本申请的实施方式中，所述第一网络设备依照本申请前述的实施方式，在所述第二网络设备部署第一Objective后，所述第一网络设备确定本地保存的所述第一Objective是否发生变更。如果所述第一网络设备确定本地保存的所述第一Objective发生变更，所述第一网络设备向所述第二网络设备发送第一Objective变更报文。所述第一Objective变更报文用于指示所述第一Objective的变更，所述第一Objective变更报文用于触发所述第二网络设备根据所述第一Objective变更报文变更所述第二网络设备本地保存的所述第一Objective。其中，所述第二网络设备本地保存的所述第一Objective是所述第二网络设备从所述第一网络设备接收到的Objective。
在一种可能的实现方式中，如果所述第一网络设备确定本地保存的所述第一Objective被删除。所述第二网络设备在接收到所述第一Objective变更报文后，所述第二网络设备根据所述第一Objective变更报文删除所述第二网络设备本地保存的所述第一Objective。
在另一种可能的实现方式中，如果所述第一网络设备确定本地保存的所述第一Objective包括的部分值或全部值被修改。所述第二网络设备在接收到所述第一Objective变更报文后，所述第二网络设备根据所述第一Objective变更报文携带的新的Objective更新所述第二网络设备本地保存的所述第一Objective。
通过上述实施方式，当网络设备检测到本地保存的Objective发生变更时，所述网络设备自动的向所述网络设备的peer网络设备通知所述Objective的变更，以便所述peer网络设备及时变更本地保存的Objective，有助于所述peer网络设备减少CPU和存储资源的占用。其中，通过Objective变更报文实现peer网络设备及时变更本地保存的Objective的具体实现方式可以参见本申请后续实施例的说明。
另外，在ANIMA网络中，任意两台网络设备是一对peer。以图1为例，所述第一网络设备与所述第二网络设备是一对peer，所述第二网络设备与所述第三网络设备是一对peer。其中，“一对peer”可以被理解为：一个设备是另一个设备的peer。例如，所述第一网络设备与所述第二网络设备是一对peer可以被理解为指所述第一网络设备是所述第二网络设备的peer，或者被理解为所述第二网络设备是所述第一网络设备的peer。所述peer也可以被称为邻居。
图2为本申请实施例的一种ANIMA网络的信息处理方法。图2所示的方法可以应用于图1所示的ANIMA网络中。所述ANIMA网络包括第一网络设备和第二网络设备。图2所示的方法包括S101至S107。
S101、所述第一网络设备向所述第二网络设备发送第一Objective，所述第一网络设备和所述第二网络设备运行有ANIMA协议。
根据前述实施方式，所述第一网络设备首先获取所述第一Objective。所述第一网络设备可以通过网络管理员配置的方式获取所述第一Objective，也可以从其他网络设备(例如网管设备)获取所述第一Objective。所述第一网络设备获取所述第一Objective后，保存所述第一Objective，具体的，所述第一网络设备可以将所述第一Objective保存在缓存中。所述缓存可以是一种实现暂时存储的存储器。其中，所述第一Objective可以是所述第一网络设备和所述第二网络设备在实现发现机制、同步机制、协商机制或洪泛机制中使用的Objective。
所述第一Objective包括name和vlaue，所述name用于标识所述Objective，所述value是指所述Objective中包括的用于网络设备的配置参数。所述第一网络设备可以经由所述第一网络设备的第一端口向所述第二网络设备发送所述第一Objective，从而，将所述第一Objective部署到所述第二网络设备。其中，所述第一网络设备的第一端口连接所述第一网络设备与所述第二网络设备之间的通信链路。所述第一网络设备和所述第二网络设备均运行有ANIMA协议，因此，所述第一网络设备和所述第二网络设备可以实现GRASP功能。所述第一Objective可以用于触发所述第二网络设备根据所述第一Objective配置所述第二网络设备。
在一种可能的实现方式中，所述第一网络设备和所述第二网络设备之间可以交互GRASP消息。所述第一Objective可以被携带在GRASP消息中。
S102、所述第二网络设备接收所述第一网络设备发送的所述第一Objective。
S103、所述第二网络设备保存所述第一Objective。
所述第二网络设备可以经由所述通信链路接收所述第一网络设备发送的所述第一Objective。例如，所述第二网络设备接收所述第一网络设备发送的GRASP消息，所述GRASP消息携带有所述第一Objective。所述第二网络设备接收到所述GRASP消息后，获取所述第一Objective，并且将所述第一Objective保存在所述第二网络设备的缓存中。 其中，所述缓存可以是一种实现暂时存储的存储器。所述第二网络设备还可以根据所述GRASP消息携带的信息类型(message_TYPE)确定所述第一Objective属于前述提到的具体哪种机制中使用的Objective。然后，所述第二网络设备根据所述第一Objective包括的值配置所述第二网络设备。
S104、所述第一网络设备确定本地保存的所述第一Objective是否发生变更。
根据前述实施方式，所述第一Objective发生的变更可以包括所述第一Objective被删除或所述第一Objective中包括的值被修改。所述第一Objective中包括的值被修改可以包括部分值被修改或全部值被修改。例如，所述第一Objective中包括IPv6地址，由于用户配置变更导致所述第一Objective中包括的IPv6地址参数被修改。
S105、当所述第一网络设备确定本地保存的所述第一Objective发生变更，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
当所述第一网络设备确定本地保存的所述第一Objective发生变更，所述第一网络设备根据所述第一Objective的变更生成所述第一Objective变更报文。所述第一Objective变更报文用于指示所述第一Objective的变更。在一种可能的实现方式中，所述第一Objective被删除，所述第一Objective变更报文用于指示所述第一Objective被删除。在另一种可能的实现方式中，所述第一Objective包括的值被修改，所述第一Objective变更报文用于指示修改后的第一Objective。所述第一网络设备经由所述第一网络设备的所述第一端口向所述第二网络设备发送第一Objective变更报文。所述第一Objective变更报文用于触发所述第二网络设备根据所述第一Objective变更报文对所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective进行相应的变更。所述第二网络设备在执行变更操作后，所述第一网络设备本地保存的发生变更的所述第一Objective与所述第二网络设备本地保存的发生变更的所述第一Objective是相同的。
下面以图3为例，说明所述第一网络设备确定所述第一Objective发生变更，以及生成和发送所述第一Objective变更报文的实现方式。
如图3所示，所述第一网络设备可以包括ANIMA控制组件和GRASP组件。其中，所述ANIMA控制组件用于管理和调度所述第一网络设备中的其他组件；所述GRASP组件用于实现GRASP功能，在本申请实施例中，GRASP组件还用于生成和发送所述第一Objective变更报文。所述第一网络设备还可以包括配置器(configurator，CFG)组件和/或命令行接口(command line interface，CLI)组件。其中，所述CFG组件用于对配置文件进行管理和配置。所述CLI组件用于用户与所述第一网络设备之间的交互。所述ANIMA控制组件、GRASP组件、CFG组件和CLI组件可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。图3所示的方法包括S1101至S1105。
S1101、所述CLI组件或所述CFG组件检测所述第一Objective是否发生变更。
所述第一网络设备可以通过所述CLI组件或所述CFG组件检测出所述第一Objective是否发生了变更。例如，用户通过所述CLI组件更改了所述第一Objective中的值，或者用户通过所述CLI组件删除所述第一Objective，或者用户通过所述CLI 组件输入了新的第一Objective。这样，所述CLI组件可以确定所述第一Objective发生变更。又例如，基于用户的配置变更请求，所述ANIMA控制组件调用所述CFG组件对所述第一Objective进行重新配置。这样，所述CFG组件可以确定所述第一Objective发生变更。
S1102、所述CLI组件或所述CFG组件确定所述第一Objective发生变更，生成第一消息，并且向所述ANIMA控制组件发送所述第一消息。
当所述第一Objective发生了变更，所述CLI组件或所述CFG组件可以生成第一消息，所述第一消息用于指示所述第一Objective的变更。在一种可能的实现方式中，所述变更是所述第一Objective被删除，所述第一消息包括所述第一Objective的名称和发起端(initiator)。所述initiator用于指示发起所述第一Objective的网络设备，或者可以理解为，发起发现机制、同步机制、协商机制或洪泛机制的网络设备。所述第一消息可以不携带所述第一Objective中的任何值，表示所述第一消息指示的变更是删除所述第一Objective。可选的，所述第一消息还可以包括变更类型，并且变更类型被设置为删除。可选的，所述变更类型被设置为删除的情况下，所述第一消息还可以包括所述第一Objective中的值。表示所述第一Objective中的值被删除。
在另一种可能的实现方式中，所述变更是所述第一Objective中的值被修改，所述第一消息包括修改后的第一Objective和initiator。所述第一消息携带有修改后的第一Objective，表示所述第一消息指示的变更是修改所述第一Objective。可选的，所述第一消息还可以包括变更类型，并且变更类型被设置为修改。可选的，所述变更类型被设置为修改的情况下，所述第一消息不携带修改后的第一Objective，而是携带具体修改的参数值的新值，并且所述第一消息还携带该新值的参数类型，所述参数类型用于指示该新值。
所述CLI组件或所述CFG组件生成所述第一消息后，向所述ANIMA控制组件发送所述第一消息。所述第一消息的格式可以使用网络设备内部的消息传送格式，例如socket消息。
S1103、所述ANIMA控制组件向所述GRASP组件转发所述第一消息。
S1104、所述GRASP组件根据所述第一消息生成所述第一Objective变更报文。
S1105、所述GRASP组件发送所述第一Objective变更报文。
根据前述，所述ANIMA控制组件用于管理和调度所述第一网络设备中的其他组件，所述ANIMA控制组件接收到所述第一消息后，确定所述第一消息用于指示所述第一Objective的变更，将所述第一消息发送到所述GRASP组件。所述GRASP组件在接收到所述第一消息后，可以利用所述第一消息中的信息生成所述第一Objective变更报文。然后，所述GRASP组件向所述第二网络设备发送所述第一Objective变更报文。其中，所述第一Objective变更报文的具体实现方式可以参见本申请后续说明。
上述S1101至S1105说明了所述CLI组件或所述CFG组件通过所述ANIMA控制组件向所述GRASP组件主动上报所述第一Objective变更的实现方式。在另一种实现方式中，所述GRASP组件可以主动的向所述ANIMA控制组件进行请求，询问所述ANIMA控制组件所述第一Objective是否发生变更。所述ANIMA控制组件调用所述CLI组件或所述CFG组件进行上报。所述CLI组件或所述CFG组件进行上报的过程 可以参见上述S1101至S1105的说明，此处不进行赘述。
S106、所述第二网络设备接收所述第一网络设备发送的所述第一Objective变更报文，所述第一Objective变更报文是所述第一网络设备响应于所述第一网络设备本地保存的所述第一Objective发生了变更而生成的。
S107、所述第二网络设备根据所述第一Objective变更报文变更所述第二网络设备保存的来自所述第一网络设备的所述第一Objective，其中，所述第一网络设备本地保存的发生变更的所述第一Objective与所述第二网络设备本地保存的发生变更的所述第一Objective是相同的。
所述第一网络设备经由所述第一网络设备的第一端口向所述第二设备发送所述第一Objective变更报文。所述第二网络设备可以经由所述通信链路接收所述第一Objective变更报文。所述第二网络设备接收到所述第一Objective变更报文后，解析所述第一Objective变更报文。确定所述第一Objective变更报文指示的所述第一Objective的变更类型。当所述第二网络设备确定所述变更类型为删除所述第一Objective时，所述第二网络设备删除所述第二网络设备保存的来自所述第一网络设备的所述第一Objective。当所述第二网络设备确定所述变更类型为修改所述第一Objective中的值时，所述第二网络设备根据所述第一Objective变更报文携带的新的第一Objective修改所述第二网络设备保存的来自所述第一网络设备的所述第一Objective。具体的，所述第二网络设备可以利用所述第一Objective变更报文携带的新的第一Objective替换所述第二网络设备保存的所述第一Objective。其中，修改所述第一Objective中的值可以包括部分值的修改或全部值的修改。在另一种可变换的实现方式中，当所述变更类型为修改所述第一Objective中的值时，所述第一Objective变更报文不携带新的第一Objective，而是携带所述第一Objective中具体被修改的参数值。所述第二网络设备在获取到该被修改的参数值后，将该被修改的参数值替换所述第二网络设备保存的所述第一Objective中的对应参数值。所述第二网络设备在执行变更操作后，所述第一网络设备本地保存的发生变更的所述第一Objective与所述第二网络设备本地保存的发生变更的所述第一Objective是相同的。
通过上述实施方式，在ANIMA网络中，当网络设备检测到本地保存的Objective发生变更时，所述网络设备自动的向所述网络设备的peer网络设备通知所述Objective的变更，以便所述peer网络设备及时变更本地保存的Objective，有助于所述peer网络设备减少CPU和存储资源的占用。上述实施方式说明了所述第一网络设备向所述第二网络设备发送第一Objective变更报文的实现方式。需要说明的是，所述第一网络设备可以按照上述实现方式向多个网络设备发送Objective变更报文。所述第二网络设备在接收到来自所述第一网络设备发送的Objective变更报文，可以按照上述实现方式继续向所述第二网络设备的下一跳网络设备转发Objective变更报文。
根据前述实施方式的描述，可选的，所述第一网络设备获取去使能ANIMA消息，所述去使能ANIMA消息用于指示所述第一网络设备关闭所述第一端口的ANIMA功能，所述第一端口是所述第一网络设备向所述第二网络设备发送所述第一Objective的端口。在所述第一网络设备根据所述去使能ANIMA消息关闭所述第一端口的ANIMA功能前，所述第一网络设备向所述第二网络设备发送第二Objective变更报文以指示所 述第二网络设备根据所述第二Objective变更报文删除所述第二网络设备本地保存的所述第一Objective。
根据本申请前述实施方式，当所述第一网络设备检测到所述第一Objective发生变更，所述第一网络设备可以向所述第二网络设备发送所述第一Objective变更报文，以便触发所述第二网络设备根据所述第一Objective变更报文变更所述第二网络设备本地保存的所述第一Objective。
所述第一网络设备用于发送所述第一Objective的第一端口可能被去使能ANIMA功能。例如，配置变更导致所述第一接口不再运行ANIMA功能。这样，所述第一网络设备可以获取所述第一端口的去使能ANIMA消息，所述去使能ANIMA消息用于指示所述第一网络设备关闭所述第一端口的ANIMA功能。所述第一网络设备解析所述去使能ANIMA消息，在执行关闭所述第一端口的ANIMA功能之前，向所述第二网络设备发送第二Objective变更报文。所述第二网络设备所述第二Objective变更报文删除所述第二网络设备本地保存的所述第一Objective。其中，获取所述去使能ANIMA消息，以及生成和发送所述第二Objective变更报文的实现方式可以参见本申请前述实施方式的说明，例如参见图2和图3的实现方式，此处不进行赘述。
通过上述实现方式，当网络设备的端口退出ANIMA域时，所述网络设备自动的向所述网络设备的peer网络设备通知所述端口退出ANIMA域的情况，以便所述peer网络设备及时删除本地保存的Objective，有助于所述peer网络设备减少CPU和存储资源的占用。需要说明的是，网络设备可能发生全局去使能，所述全局去使能是指整个网络设备退出ANIMA域。这种情况下，可以等同于所述网络设备的所有运行ANIMA功能的端口均关闭ANIMA功能，对于每个端口均可以参照上述实现方式，此处不进行赘述。
根据前述实施方式的描述，可选的，所述第二网络设备向第三网络设备转发所述第一Objective。所述第二网络设备确定通信链路是否发生故障，所述通信链路是所述第二网络设备接收所述第一网络设备发送的第一Objective的通信链路。当所述第二网络设备确定所述通信链路发生故障，所述第二网络设备向所述第三网络设备发送第二Objective变更报文以指示所述第三网络设备根据所述第二Objective变更报文删除所述第三网络设备本地保存的所述第一Objective。
如图1所示，所述第二网络设备可能连接有第三网络设备。根据前述实施方式的描述，所述第二网络设备在接收到所述第一Objective后，可以经由所述第二网络设备和第三网络设备之间的通信链路，向所述第三网络设备转发所述第一Objective。从而，所述第三网络设备可以保存所述第一Objective，并且基于所述第一Objective配置所述第三网络设备。
根据GRASP的规定，所述第二网络设备在接收到所述第一Objective时，不仅存储所述第一Objective，还记录所述第二网络设备接收到所述第一Objective的端口信息。在所述第二网络设备中，所述第一Objective与所述第二网络设备的接收所述第一Objective的端口形成对应关系。
所述第二网络设备还确定所述第一网络设备和所述第二网络设备之间的通信链路是否发生故障。所述通信链路用于传输所述第一Objective。当所述第二网络设备发现 所述通信链路发生故障，所述第二网络设备关闭所述第二网络设备连接所述通信链路的端口。由于所述第二网络设备在接收到所述第一网络设备发送的所述第一Objective时，记录了接收端口，因此，所述第二网络设备可以根据上述提及的对应关系确定该被关闭的端口是接收所述第一Objective的端口。所述第二网络设备生成所述第二Objective变更报文，所述第二Objective变更报文用于指示所述第一Objective需要被删除。所述第二网络设备向所述第三网络设备发送所述第二Objective变更报文，所述第二Objective变更报文用于触发所述第三网络设备根据所述第二Objective变更报文删除所述第三网络设备本地保存的所述第一Objective。
通过上述实现方式，当网络设备发现接收Objective的上游链路发生故障时，所述网络设备自动的向所述网络设备的下游的peer网络设备通知删除所述Objective，以便所述下游的peer网络设备及时删除本地保存的Objective，有助于所述下游的peer网络设备减少CPU和存储资源的占用。
可选的，所述第一Objective变更报文为GRASP消息，所述GRASP消息包括第一标识，所述第一标识用于指示GRASP消息为Objective变更报文。进一步可选的，所述GRASP消息还包括第二标识，所述第二标识用于指示所述第二网络设备本地保存的所述第一Objective的变更类型。
根据前述，所述第一网络设备、第二网络设备和第三网络设备之间可以交互GRASP消息，所述GRASP消息可以用于实现所述第一Objective变更报文。在一种可能的实现方式中，可以通过复用GRASP定义的现有GRASP消息实现所述第一Objective变更报文；在另一种可能的实现方式中，可以在GRASP中定义新的GRASP消息实现所述第一Objective变更报文。
举例说明，图4示出了通过复用GRASP定义的现有GRASP消息实现所述第一Objective变更报文的报文格式。在说明图4的过程中，为了方便说明，将图4所示的GRASP消息成为第一GRASP消息。
如图4所示，所述第一GRASP消息包括生存时间(time-to-live，TTL)，在GRASP中，所述TTL用于指示所述第一GRASP消息携带的Objective在网络设备中的生存时间。所述TTL的长度为32比特，取值范围为0ms到4294967295ms，ms表示毫秒。本申请通过复用所述第一GRASP消息中的TTL实现第一标识，所述第一标识用于指示第一GRASP消息为第一Objective变更报文。具体的，将TTL取值为全F定义为第一标识，即，当所述TTL取值为全F时，用于指示所述第一GRASP消息为第一Objective变更报文，表示所述第一Objective发生的变更。
所述第一GRASP消息还可以包括信息类型(message_type)，会话标识(session-id)，发起端(initiator)，目标名称(objective-name)，目标标志(objective-flag)，和循环次数(loop-count)。可选的，所述第一GRASP消息还可能包括目标值(objective-value)。其中，message_type用于指示所述第一GRASP消息的类型，例如M_DISCOVERY表示发现机制中使用的GRASP消息。session-id是指GRASP会话的标识。initiator是指本申请所提及的机制的发起者，也是本申请提及的第一Objective的发起者，例如本申请的第一网络设备。objective-name是指本申请前述实施例中定义的Objective的名称。objective-value是指本申请前述实施例中定义的Objective包括的值。objective-flag用 于指示发现会话、协商会话、同步会话或协商演练(dry-run negotiation)。loop-count用于指示所述第一GRASP消息传播的范围，例如取值为1时，所述第一GRASP消息可以被传播到第二网络设备，取值为2时所述第一GRASP消息可以被传播到第三网络设备。
例如，结合前述实施例中提及的所述第一Objective被删除的实现方式和所述第一Objective包括的值被修改的实现方式进行说明。所述第一网络设备发送的和第二网络设备接收到的所述第一GRASP消息包括第一标识。所述第一标识是TTL，并且所述TTL的取值为全F，说明所述第一GRASP消息是所述第一Objective变更报文。如果所述第一GRASP消息包括objective-name，但不包括objective-value，则说明所述第一GRASP消息是用于执行删除所述第一Objective的Objective变更报文。如果所述第一GRASP消息包括objective-name，还包括objective-value，则说明所述第一GRASP消息是用于执行修改所述第一Objective包括的值的Objective变更报文。其中，所述第一GRASP消息可以携带第二Objective，所述第二Objective中包括了修改后的值，所述第二Objective用于替换所述第一Objective。所述第一GRASP消息中的objective-value是所述第二Objective中的值。
举例说明，图5示出了通过在GRASP中定义新的GRASP消息实现所述第一Objective变更报文的报文格式。在说明图5的过程中，为了方便说明，将图5所示的GRASP消息成为第二GRASP消息。
如图5所示，所述第二GRASP消息包括message_type。在本申请中message_type被重新定义，例如将message_type的值设置为98(代表：M_DELETE)，表示所述第二GRASP消息为所述第一Objective变更报文。因此，新定义的message_type等同于前述提及的第一标识。可选的，所述第二GRASP消息还包括objective-flag。在本申请中objective-flag被重新定义，例如将objective-flag的值设置为5(代表：F_DEL)，表示所述第二GRASP消息是用于执行删除所述第一Objective的Objective变更报文；例如将objective-flag的值设置为4(代表：F_MODIFY)，表示所述第二GRASP消息是用于执行修改所述第一Objective包括的值的Objective变更报文。因此，新定义的objective-flag等同于前述提及的第二标识。
所述第二GRASP消息还可以包括session-id，initiator，objective-name，objective-flag和loop-count。可选的，所述第一GRASP消息还可能包括objective-value。所述第二GRASP消息包括的上述字段的解释可以参见前述实施例。
例如，结合前述实施例中提及的所述第一Objective被删除的实现方式和所述第一Objective包括的值被修改的实现方式进行说明。所述第一网络设备发送的和第二网络设备接收到的所述第二GRASP消息包括第一标识。所述第一标识是message_type，并且所述message_type的取值为98(代表：M_DELETE)，说明所述第二GRASP消息是所述第一Objective变更报文。如果所述第二GRASP消息包括objective-name，但不包括objective-value，则说明所述第二GRASP消息是用于执行删除所述第一Objective的Objective变更报文。如果所述第二GRASP消息包括objective-name，还包括objective-value，则说明所述第二GRASP消息是用于执行修改所述第一Objective包括的值的Objective变更报文。其中，所述第二GRASP消息可以携带第二Objective，所 述第二Objective中包括了修改后的值，所述第二Objective用于替换所述第一Objective。所述第二GRASP消息中的objective-value是所述第二Objective中的值。
在另一种可能的实现方式中，所述第二GRASP消息在包括上述第一标识的基础上，还包括第二标识。所述第二标识是objective-flag。将objective-flag的值设置为5(代表：F_DEL)，表示所述第二GRASP消息是用于执行删除所述第一Objective的Objective变更报文；将objective-flag的值设置为4(代表：F_MODIFY)，表示所述第二GRASP消息是用于执行修改所述第一Objective包括的值的Objective变更报文。这样，网络设备不需要根据所述第二GRASP消息中是否包括objective-value判断变更类型，而是通过objective-flag判断更改类型。
举例说明，图6示出了在图5的基础上增加Objective的实施方式，即所述第二GRASP消息可以携带多个Objective。这样，网络设备可以根据一条Objective变更报文实现对多个Objective的操作。有利于节省传输带宽和CPU的资源占用。图6的具体实施方式可以参见前述图5的说明，此处不进行赘述。
需要说明的是，本申请中提及的第二Objective变更报文也可以按照上述图4-图6的实现方式实现，此处不进行赘述。
图7为本申请实施例的第一网络设备1000的结构示意图。图7所示的第一网络设备1000可以执行上述实施例的方法中第一网络设备执行的相应步骤。所述第一网络设备被部署在ANIMA网络中，所述ANIMA网络还包括第二网络设备。如图7所示，所述第一网络设备1000包括发送单元1002和处理单元1004。
所述发送单元1002，用于向第二网络设备发送第一Objective，所述第一网络设备和所述第二网络设备运行有ANIMA协议；
所述处理单元1004，用于确定本地保存的所述第一Objective是否发生变更；
当所述处理单元1004确定本地保存的所述第一Objective发生变更，所述发送单元1002还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective，其中，所述第一网络设备本地保存的发生变更的所述第一Objective与所述第二网络设备本地保存的发生变更的所述第一Objective是相同的。
可选的，所述处理单元1004，用于确定本地保存的所述第一Objective是否发生变更具体包括：所述处理单元1004用于确定本地保存的所述第一Objective是否被删除；当所述处理单元1004确定本地保存的所述第一Objective发生变更，所述发送单元1002还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective具体包括：当所述处理单元1004确定本地保存的所述第一Objective被删除，所述发送单元1002还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备删除所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
可选的，所述处理单元1004，用于确定本地保存的所述第一Objective是否发生变更具体包括：所述处理单元1004用于确定本地保存的所述第一Objective是否被修改；当所述处理单元1004确定本地保存的所述第一Objective发生变更，所述发送单 元1002还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective具体包括：当所述处理单元1004确定本地保存的所述第一Objective被修改，所述发送单元1002还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备修改所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
可选的，所述处理单元1004还用于获取去使能ANIMA消息，所述去使能ANIMA消息用于指示所述处理单元1004关闭第一端口的ANIMA功能，所述第一端口是所述发送单元1002向所述第二网络设备发送所述第一Objective的端口；在所述处理单元1004根据所述去使能ANIMA消息关闭所述第一端口的ANIMA功能前，所述发送单元1002还用于向所述第二网络设备发送第二Objective变更报文以指示所述第二网络设备根据所述第二Objective变更报文删除所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
图7所示的第一网络设备可以执行上述实施例的方法中第一网络设备执行的相应步骤。应用在ANIMA网络场景中，当网络设备检测到本地保存的Objective发生变更时，所述网络设备自动的向所述网络设备的peer网络设备通知所述Objective的变更，以便所述peer网络设备及时变更本地保存的Objective，有助于所述peer网络设备减少CPU和存储资源的占用。
图8为本申请实施例的第一网络设备1100的硬件结构示意图。图8所示的第一网络设备1100可以执行上述实施例的方法中第一网络设备执行的相应步骤。
如图8所示，所述第一网络设备1100包括处理器1101、存储器1102、接口1103和总线1104。其中接口1103可以通过无线或有线的方式实现，具体来讲可以是网卡。上述处理器1101、存储器1102和接口1103通过总线1104连接。
所述接口1103具体可以包括发送器和接收器，用于第一网络设备与上述实施例中的第二网络设备之间收发信息。例如，所述接口1103用于支持向所述第二网络设备发送第一Objective和第一Objective变更报文。作为举例，所述接口1103用于支持图2中的过程S101和S105。所述处理器1101用于执行上述实施例中由第一网络设备进行的处理。例如，所述处理器1101用于确定本地保存的第一Objective是否发生变更；和/或用于本文所描述的技术的其他过程。作为举例，所述处理器1101用于支持图2中的过程S104。存储器1102包括操作系统11021和应用程序11022，用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及第一网络设备的处理过程。可选的，所述存储器1102可以包括只读存储器(英文：Read-only Memory，缩写：ROM)和随机存取存储器(英文：Random Access Memory，缩写：RAM)。其中，所述ROM包括基本输入/输出系统(英文：Basic Input/Output System，缩写：BIOS)或嵌入式系统；所述RAM包括应用程序和操作系统。当需要运行第一网络设备1100时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导第一网络设备1100进入正常运行状态。在第一网络设备1100进入正常运行状态后，运行在RAM中的应用程序和操作系统，从而，完成方法实施例中涉及第一网络设备的处理过程。
可以理解的是，图8仅仅示出了第一网络设备1100的简化设计。在实际应用中，第一网络设备可以包含任意数量的接口，处理器或者存储器。
图9为本申请实施例的另第一网络设备1200的硬件结构示意图。图9所示的第一网络设备1200可以执行上述实施例的方法中第一网络设备执行的相应步骤。
如图9所述，第一网络设备1200包括：主控板1210、接口板1230、交换网板1220和接口板1240。主控板1210、接口板1230和1240，以及交换网板1220之间通过系统总线与系统背板相连实现互通。其中，主控板1210用于完成系统管理、设备维护、协议处理等功能。交换网板1220用于完成各接口板(接口板也称为线卡或业务板)之间的数据交换。接口板1230和1240用于提供各种业务接口(例如，POS接口、GE接口、ATM接口等)，并实现数据包的转发
接口板1230可以包括中央处理器1231、转发表项存储器1234、物理接口卡1233和网络处理器1232。其中，中央处理器1231用于对接口板进行控制管理并与主控板上的中央处理器进行通信。转发表项存储器1234用于保存转发表项。物理接口卡1233用于完成流量的接收和发送。网络存储器1232用于根据所述转发表项控制物理接口卡1233收发流量。
具体的，物理接口卡1233用于向所述第二网络设备发送第一Objective和第一Objective变更报文。
中央处理器1211还用于确定本地保存的第一Objective是否发生变更。当所述中央处理器1211确定本地保存的第一Objective发生变更时，触发物理接口卡1233向所述第二网络设备发送所述第一Objective变更报文。
中央处理器1211还用于生成所述第一Objective和所述第一Objective变更报文。中央处理器1211将所述第一Objective和所述第一Objective变更报文经由中央处理器1231向物理接口卡1233发送。物理接口卡1233向所述第二网络设备发送所述第一Objective和所述第一Objective变更报文。
中央处理器1231还用于控制网络存储器1232获取转发表项存储器1234中的转发表项，并且，中央处理器1231还用于控制网络存储器1232经由物理接口卡1233完成流量的接收和发送。
应理解，本发明实施例中接口板1240上的操作与所述接口板1230的操作一致，为了简洁，不再赘述。应理解，本实施例的第一网络设备1200可对应于上述方法实施例所具有的功能和/或所实施的各种步骤，在此不再赘述。
此外，需要说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，第一网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，第一网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，第一网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的第一网络设备的数据接入和处理能力要大于集中式架构的设备。具体采用哪种架构，取决于具体的组网部署场景，此处不做任何限定。
图10为本申请实施例的第二网络设备2000的结构示意图。图10所示的第二网络设备2000可以执行上述实施例的方法中第二网络设备执行的相应步骤。所述第二网络设备被部署在ANIMA网络中，所述ANIMA网络还包括第一网络设备。如图10所示，所述第二网络设备2000包括接收单元2002，处理单元2004和存储单元2006。
所述接收单元2002，用于接收第一网络设备发送的第一Objective，所述第一网络设备和所述第二网络设备运行有ANIMA协议；
所述存储单元2006，用于保存所述第一Objective；
所述接收单元2002还用于接收所述第一网络设备发送的第一Objective变更报文，所述第一Objective变更报文是所述第一网络设备响应于所述第一网络设备本地保存的所述第一Objective发生了变更而生成的；
所述处理单元2004，用于根据所述第一Objective变更报文变更所述存储单元2006保存的所述第一Objective，其中，所述第一网络设备本地保存的发生变更的所述第一Objective与所述存储单元2006保存的发生变更的所述第一Objective是相同的。
可选的，所述处理单元2004，用于根据所述第一Objective变更报文变更所述存储单元2006保存的所述第一Objective具体包括：所述处理单元2004用于根据所述第一Objective变更报文删除所述存储单元2006保存的所述第一Objective。
可选的，所述处理单元2004，用于根据所述第一Objective变更报文变更所述存储单元2006保存的所述第一Objective具体包括：所述处理单元2004用于根据所述第一Objective变更报文修改所述存储单元2006保存的所述第一Objective。
可选的，所述第二网络设备还包括：发送单元2008，用于向第三网络设备转发所述第一Objective；所述处理单元2004还用于确定第一通信链路是否发生故障，所述第一通信链路是所述接收单元2002接收所述第一网络设备发送的第一Objective的通信链路；当所述处理单元2004确定所述第一通信链路发生故障，所述发送单元2008还用于向所述第三网络设备发送第二Objective变更报文以指示所述第三网络设备删除所述第三网络设备本地保存的所述第一Objective。
图10所示的第二网络设备可以执行上述实施例的方法中第二网络设备执行的相应步骤。应用在ANIMA网络场景中，当网络设备检测到本地保存的Objective发生变更时，所述网络设备自动的向所述网络设备的peer网络设备通知所述Objective的变更，以便所述peer网络设备及时变更本地保存的Objective，有助于所述peer网络设备减少CPU和存储资源的占用。
图11为本申请实施例的第二网络设备2100的硬件结构示意图。图11所示的第二网络设备2100可以执行上述实施例的方法中第二网络设备执行的相应步骤。
如图11所示，所述第二网络设备2100包括处理器2101、存储器2102、接口2103和总线2104。其中接口2103可以通过无线或有线的方式实现，具体来讲可以是网卡。上述处理器2101、存储器2102和接口2103通过总线2104连接。
所述接口2103具体可以包括发送器和接收器，用于第二网络设备与上述实施例中的第一网络设备之间收发信息，或者用于第二网络设备与上述实施例中的第三网络设备之间收发信息。例如，所述接口2103用于支持接收所述第一网络设备发送的第一Objective和第一Objective变更报文，或者用于支持向所述第三网络设备发送第一 Objective和第二Objective变更报文。作为举例，所述接口2103用于支持图2中的过程S102和S106。所述处理器2101用于执行上述实施例中由第二网络设备进行的处理。例如，所述处理器2101用于根据所述第一Objective变更报文变更存储器2102保存的第一Objective；还用于确定所述第二网络设备和所述第一网络设备之间的，用于传输所述第一Objective的第一通信链路是否发生故障；和/或用于本文所描述的技术的其他过程。作为举例，所述处理器2101用于支持图2中的过程S107。存储器2102包括操作系统21021和应用程序21022，用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及第二网络设备的处理过程。可选的，所述存储器2102可以包括只读存储器(英文：Read-only Memory，缩写：ROM)和随机存取存储器(英文：Random Access Memory，缩写：RAM)。其中，所述ROM包括基本输入/输出系统(英文：Basic Input/Output System，缩写：BIOS)或嵌入式系统；所述RAM包括应用程序和操作系统。当需要运行第二网络设备2100时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导第二网络设备2100进入正常运行状态。在第二网络设备2100进入正常运行状态后，运行在RAM中的应用程序和操作系统，从而，完成方法实施例中涉及第二网络设备的处理过程。
可以理解的是，图11仅仅示出了第二网络设备2100的简化设计。在实际应用中，第二网络设备可以包含任意数量的接口，处理器或者存储器。
图12为本申请实施例的另第二网络设备2200的硬件结构示意图。图12所示的第二网络设备2200可以执行上述实施例的方法中第二网络设备执行的相应步骤。
如图12所述，第二网络设备2200包括：主控板2210、接口板2230、交换网板2220和接口板2240。主控板2210、接口板2230和2240，以及交换网板2220之间通过系统总线与系统背板相连实现互通。其中，主控板2210用于完成系统管理、设备维护、协议处理等功能。交换网板2220用于完成各接口板(接口板也称为线卡或业务板)之间的数据交换。接口板2230和2240用于提供各种业务接口(例如，POS接口、GE接口、ATM接口等)，并实现数据包的转发
接口板2230可以包括中央处理器2231、转发表项存储器2234、物理接口卡2233和网络处理器2232。其中，中央处理器2231用于对接口板进行控制管理并与主控板上的中央处理器进行通信。转发表项存储器2234用于保存转发表项。物理接口卡2233用于完成流量的接收和发送。网络存储器2232用于根据所述转发表项控制物理接口卡2233收发流量。
具体的，物理接口卡2233用于接收所述第一网络设备发送的第一Objective和第一Objective变更报文，或者用于向所述第三网络设备发送第一Objective和第二Objective变更报文。
中央处理器2211还用于根据所述第一Objective变更报文变更所述第二网络设备保存的第一Objective；还用于确定所述第二网络设备和所述第一网络设备之间的、用于传输所述第一Objective的第一通信链路是否发生故障。当所述中央处理器2211确定所述第一通信链路发生故障时，触发物理接口卡2233向所述第三网络设备发送所述第二Objective变更报文。
中央处理器2211还用于生成所述第二Objective变更报文。中央处理器2211将所述第一Objective和所述第二Objective变更报文经由中央处理器2231向物理接口卡2233发送。物理接口卡2233向所述第三网络设备发送所述第一Objective和所述第二Objective变更报文。
中央处理器2231还用于控制网络存储器2232获取转发表项存储器2234中的转发表项，并且，中央处理器2231还用于控制网络存储器2232经由物理接口卡2233完成流量的接收和发送。
应理解，本发明实施例中接口板2240上的操作与所述接口板2230的操作一致，为了简洁，不再赘述。应理解，本实施例的第二网络设备2200可对应于上述方法实施例所具有的功能和/或所实施的各种步骤，在此不再赘述。
此外，需要说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，第二网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，第二网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，第二网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的第二网络设备的数据接入和处理能力要大于集中式架构的设备。具体采用哪种架构，取决于具体的组网部署场景，此处不做任何限定。
在上述图7或图8或图9或图10或图11或图12所述的实施例中，可选的，所述第一Objective变更报文为GRASP消息，所述GRASP消息包括第一标识，所述第一标识用于指示所述GRASP消息为Objective变更报文。进一步可选的，所述GRASP消息还包括第二标识，所述第二标识用于指示所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective的变更类型。
另外，本申请实施例提供了一种计算机存储介质，用于储存为上述第一网络设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
另外，本申请实施例提供了一种计算机存储介质，用于储存为上述第二网络设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本申请实施例还包括一种ANIMA网络系统，所述ANIMA网络系统包括第一网络设备和第二网络设备，所述第一网络设备为前述图7或图8或图9中的第一网络设备，所述第二网络设备为前述图10或图11或图12中的第二网络设备。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于用户设备中。当然，处理器和存储介质也可以作为分立组件存在于用户设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明。所应理解的是，以上所述仅为本申请的具体实施方式而已。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (21)

  1. 一种自主网络集成模型和方法ANIMA网络的信息处理方法，其特征在于，所述方法包括：
    第一网络设备向第二网络设备发送第一目标Objective，所述第一网络设备和所述第二网络设备运行有ANIMA协议；
    所述第一网络设备确定本地保存的所述第一Objective是否发生变更；
    当所述第一网络设备确定本地保存的所述第一Objective发生变更，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective，其中，所述第一网络设备本地保存的发生变更的所述第一Objective与所述第二网络设备本地保存的发生变更的所述第一Objective是相同的。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一网络设备确定本地保存的所述第一Objective是否发生变更包括：
    所述第一网络设备确定本地保存的所述第一Objective是否被删除；
    当所述第一网络设备确定本地保存的所述第一Objective发生变更，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective包括：
    当所述第一网络设备确定本地保存的所述第一Objective被删除，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备删除所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
  3. 根据权利要求1所述的方法，其特征在于，
    所述第一网络设备确定本地保存的所述第一Objective是否发生变更包括：
    所述第一网络设备确定本地保存的所述第一Objective是否被修改；
    当所述第一网络设备确定本地保存的所述第一Objective发生变更，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective包括：
    当所述第一网络设备确定本地保存的所述第一Objective被修改，所述第一网络设备向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备修改所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，还包括：
    所述第一网络设备获取去使能ANIMA消息，所述去使能ANIMA消息用于指示所述第一网络设备关闭第一端口的ANIMA功能，所述第一端口是所述第一网络设备向所述第二网络设备发送所述第一Objective的端口；
    在所述第一网络设备根据所述去使能ANIMA消息关闭所述第一端口的ANIMA功能前，所述第一网络设备向所述第二网络设备发送第二Objective变更报文以指示所述第二网络设备根据所述第二Objective变更报文删除所述第二网络设备本地保存的 来自所述第一网络设备的所述第一Objective。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述第一Objective变更报文为通用自主信令协议GRASP消息，所述GRASP消息包括第一标识，所述第一标识用于指示所述GRASP消息为Objective变更报文。
  6. 根据权利要求5所述的方法，其特征在于，所述GRASP消息还包括第二标识，所述第二标识用于指示所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective的变更类型。
  7. 一种自主网络集成模型和方法ANIMA网络的信息处理方法，其特征在于，所述方法包括：
    第二网络设备接收第一网络设备发送的第一目标Objective，所述第一网络设备和所述第二网络设备运行有ANIMA协议；
    所述第二网络设备保存所述第一Objective；
    所述第二网络设备接收所述第一网络设备发送的第一Objective变更报文，所述第一Objective变更报文是所述第一网络设备响应于所述第一网络设备本地保存的所述第一Objective发生了变更而生成的；
    所述第二网络设备根据所述第一Objective变更报文变更所述第二网络设备本地保存的所述第一Objective，其中，所述第一网络设备本地保存的发生变更的所述第一Objective与所述第二网络设备本地保存的发生变更的所述第一Objective是相同的。
  8. 根据权利要求7所述的方法，其特征在于，
    所述第二网络设备根据所述第一Objective变更报文变更所述第二网络设备本地保存的所述第一Objective包括：所述第二网络设备根据所述第一Objective变更报文删除所述第二网络设备保存的所述第一Objective。
  9. 根据权利要求7所述的方法，其特征在于，所述第二网络设备根据所述第一Objective变更报文变更所述第二网络设备本地保存的所述第一Objective包括：所述第二网络设备根据所述第一Objective变更报文修改所述第二网络设备保存的所述第一Objective。
  10. 根据权利要求7-9中任一项所述的方法，其特征在于，还包括：
    所述第二网络设备向第三网络设备转发所述第一Objective；
    所述第二网络设备确定第一通信链路是否发生故障，所述第一通信链路是所述第二网络设备接收所述第一网络设备发送的第一Objective的通信链路；
    当所述第二网络设备确定所述第一通信链路发生故障，所述第二网络设备向所述第三网络设备发送第二Objective变更报文以指示所述第三网络设备删除所述第三网络设备本地保存的所述第一Objective。
  11. 一种第一网络设备，其特征在于，所述第一网络设备包括：
    发送器，用于向第二网络设备发送第一目标Objective，所述第一网络设备和所述第二网络设备运行有自主网络集成模型和方法ANIMA协议；
    处理器，用于确定本地保存的所述第一Objective是否发生变更；
    当所述处理器确定本地保存的所述第一Objective发生变更，所述发送器还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective，其中，所述第一网络设备本地保存的发生变更的所述第一Objective与所述第二网络设备本地保存的发生变更的所述第一Objective是相同的。
  12. 根据权利要求11所述的第一网络设备，其特征在于，
    所述处理器，用于确定本地保存的所述第一Objective是否发生变更具体包括：
    所述处理器用于确定本地保存的所述第一Objective是否被删除；
    当所述处理器确定本地保存的所述第一Objective发生变更，所述发送器还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective具体包括：
    当所述处理器确定本地保存的所述第一Objective被删除，所述发送器还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备删除所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
  13. 根据权利要求11所述的第一网络设备，其特征在于，
    所述处理器，用于确定本地保存的所述第一Objective是否发生变更具体包括：
    所述处理器用于确定本地保存的所述第一Objective是否被修改；
    当所述处理器确定本地保存的所述第一Objective发生变更，所述发送器还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备变更所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective具体包括：
    当所述处理器确定本地保存的所述第一Objective被修改，所述发送器还用于向所述第二网络设备发送第一Objective变更报文以指示所述第二网络设备修改所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
  14. 根据权利要求11-13中任一项所述的第一网络设备，其特征在于，
    所述处理器还用于获取去使能ANIMA消息，所述去使能ANIMA消息用于指示所述处理器关闭第一端口的ANIMA功能，所述第一端口是所述发送器向所述第二网络设备发送所述第一Objective的端口；
    在所述处理器根据所述去使能ANIMA消息关闭所述第一端口的ANIMA功能前，所述发送器还用于向所述第二网络设备发送第二Objective变更报文以指示所述第二网络设备根据所述第二Objective变更报文删除所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective。
  15. 根据权利要求11-14中任一项所述的第一网络设备，其特征在于，所述第一Objective变更报文为通用自主信令协议GRASP消息，所述GRASP消息包括第一标识，所述第一标识用于指示所述GRASP消息为Objective变更报文。
  16. 根据权利要求15所述的第一网络设备，其特征在于，所述GRASP消息还包括第二标识，所述第二标识用于指示所述第二网络设备本地保存的来自所述第一网络设备的所述第一Objective的变更类型。
  17. 一种第二网络设备，其特征在于，所述第二网络设备包括：
    接收器，用于接收第一网络设备发送的第一目标Objective，所述第一网络设备和所述第二网络设备运行有自主网络集成模型和方法ANIMA协议；
    存储器，用于保存所述第一Objective；
    所述接收器还用于接收所述第一网络设备发送的第一Objective变更报文，所述第一Objective变更报文是所述第一网络设备响应于所述第一网络设备本地保存的所述第一Objective发生了变更而生成的；
    处理器，用于根据所述第一Objective变更报文变更所述存储器保存的所述第一Objective，其中，所述第一网络设备本地保存的发生变更的所述第一Objective与所述存储器保存的发生变更的所述第一Objective是相同的。
  18. 根据权利要求17所述的第二网络设备，其特征在于，
    所述处理器，用于根据所述第一Objective变更报文变更所述存储器保存的所述第一Objective具体包括：所述处理器用于根据所述第一Objective变更报文删除所述存储器保存的所述第一Objective。
  19. 根据权利要求17所述的第二网络设备，其特征在于，所述处理器，用于根据所述第一Objective变更报文变更所述存储器保存的所述第一Objective具体包括：所述处理器用于根据所述第一Objective变更报文修改所述存储器保存的所述第一Objective。
  20. 根据权利要求17-19中任一项所述的第二网络设备，其特征在于，所述第二网络设备还包括：
    发送器，用于向第三网络设备转发所述第一Objective；
    所述处理器还用于确定第一通信链路是否发生故障，所述第一通信链路是所述接收器接收所述第一网络设备发送的第一Objective的通信链路；
    当所述处理器确定所述第一通信链路发生故障，所述发送器还用于向所述第三网络设备发送第二Objective变更报文以指示所述第三网络设备删除所述第三网络设备本地保存的所述第一Objective。
  21. 一种自主网络集成模型和方法ANIMA网络系统，所述ANIMA网络系统包括第一网络设备和第二网络设备，所述第一网络设备为权利要求11至16中任一所述的第一网络设备，所述第二网络设备为权利要求17至20中任一所述的第二网络设备。
PCT/CN2018/119269 2017-12-27 2018-12-05 一种anima网络的信息处理方法、设备及系统 WO2019128651A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18894504.2A EP3720078B1 (en) 2017-12-27 2018-12-05 Anima network information processing method, device, and system
US16/913,274 US11095514B2 (en) 2017-12-27 2020-06-26 System and method for propagating anima network objective changes

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711449449.6 2017-12-27
CN201711449449.6A CN109981315B (zh) 2017-12-27 2017-12-27 一种anima网络的信息处理方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/913,274 Continuation US11095514B2 (en) 2017-12-27 2020-06-26 System and method for propagating anima network objective changes

Publications (1)

Publication Number Publication Date
WO2019128651A1 true WO2019128651A1 (zh) 2019-07-04

Family

ID=67063094

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/119269 WO2019128651A1 (zh) 2017-12-27 2018-12-05 一种anima网络的信息处理方法、设备及系统

Country Status (4)

Country Link
US (1) US11095514B2 (zh)
EP (1) EP3720078B1 (zh)
CN (1) CN109981315B (zh)
WO (1) WO2019128651A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112583510A (zh) * 2019-09-30 2021-03-30 华为技术有限公司 一种报文转发方法、设备及系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017070817A1 (zh) * 2015-10-26 2017-05-04 华为技术有限公司 协商对象的选择方法、响应发现消息的方法、相关装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1459213B1 (en) * 2001-11-15 2017-05-10 Good Technology Holdings Limited System and methods for asychronous synchronization
CN100466659C (zh) * 2004-07-13 2009-03-04 华为技术有限公司 一种自动配置终端设备的方法
US20070130217A1 (en) * 2005-10-13 2007-06-07 Unwired Software, Inc. Many to many data synchronization
CN101521927B (zh) * 2009-04-03 2012-09-05 中兴通讯股份有限公司 一种组播转发路径收敛的方法和系统
US9088491B2 (en) * 2012-03-07 2015-07-21 Citrix Systems, Inc. Systems and methods for comparing configuration files and generating corrective commands
US9307006B2 (en) * 2012-04-11 2016-04-05 Salesforce.Com, Inc. System and method for synchronizing data objects in a cloud based social networking environment
US9626177B1 (en) * 2015-09-11 2017-04-18 Cohesity, Inc. Peer to peer upgrade management

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017070817A1 (zh) * 2015-10-26 2017-05-04 华为技术有限公司 协商对象的选择方法、响应发现消息的方法、相关装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
B. CARPENTER: "Generic Autonomic Signaling Protocol Application Program Interface (GRASP API) draft-liu-anima-grasp-api-05", NETWORK WORKING GROUP INTERNET-DRAFT - IETF, 2 October 2017 (2017-10-02), XP055623496, Retrieved from the Internet <URL:https://tools.ietf.org/pdf/draft-liu-anima-grasp-api-05.pdf> *
B. CARPENTER: "Transferring Bulk Data over the GeneRic Autonomic Signaling Protocol (GRASP) draft-carpenter-anima-grasp-bulk-00", NETWORK WORKING GROUP INTERNET-DRAFT - IETF, 12 September 2017 (2017-09-12), XP015121738, Retrieved from the Internet <URL:https://tools.ietf.org/pdf/draft-carpenter-anima-grasp-bulk-00.pdf> *

Also Published As

Publication number Publication date
EP3720078A1 (en) 2020-10-07
US11095514B2 (en) 2021-08-17
CN109981315A (zh) 2019-07-05
CN109981315B (zh) 2021-08-27
EP3720078B1 (en) 2022-02-02
US20200351153A1 (en) 2020-11-05
EP3720078A4 (en) 2021-01-27

Similar Documents

Publication Publication Date Title
CN108574616B (zh) 一种处理路由的方法、设备及系统
US9787632B2 (en) Centralized configuration with dynamic distributed address management
CA3148150A1 (en) Connection establishment method,device,integrated access backhaul node and storage medium
US9723083B2 (en) Method and apparatus for multipath communication
WO2021043086A1 (zh) 一种sbfd会话的建立方法、设备及系统
WO2019076295A1 (zh) 一种处理报文的方法、设备及系统
WO2015117385A1 (zh) 网络虚拟化处理方法、装置及系统
WO2022001669A1 (zh) 建立vxlan隧道的方法及相关设备
WO2015180154A1 (zh) 网络控制方法和装置
EP2597821B1 (en) Method and system for auto-configuration, and network node
JP7430224B2 (ja) パケット処理方法およびゲートウェイ・デバイス
WO2010095028A2 (en) Maximum transmission unit (mtu) size discovery mechanism and method for data-link layers
WO2020057445A1 (zh) 一种通信系统、方法及装置
WO2022083563A1 (zh) 链路检测方法、链路检测装置、终端设备和存储介质
CN103825826A (zh) 一种动态路由的实现方法和装置
CN112995027B (zh) 路由发布方法及vtep节点
WO2019128651A1 (zh) 一种anima网络的信息处理方法、设备及系统
CN108282346B (zh) 软件升级方法及装置
CN113271252B (zh) 通信建立方法、系统和计算机可读存储介质
WO2022068330A1 (zh) 一种检测路由环路的方法、设备及系统
WO2016065925A1 (zh) 控制器替换方法及装置
US11907253B2 (en) Secure cluster pairing for business continuity and disaster recovery
CN113260072B (zh) Mesh组网流量调度方法、网关设备和存储介质
CN114389992A (zh) 一种控制流量转发方法、设备及系统
WO2017012315A1 (zh) 业务监听控制方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18894504

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018894504

Country of ref document: EP

Effective date: 20200630