WO2019184752A1 - 网络设备的管理方法、装置及系统 - Google Patents

网络设备的管理方法、装置及系统 Download PDF

Info

Publication number
WO2019184752A1
WO2019184752A1 PCT/CN2019/078537 CN2019078537W WO2019184752A1 WO 2019184752 A1 WO2019184752 A1 WO 2019184752A1 CN 2019078537 W CN2019078537 W CN 2019078537W WO 2019184752 A1 WO2019184752 A1 WO 2019184752A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
identifier
information
control
forwarding
Prior art date
Application number
PCT/CN2019/078537
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 EP19777499.5A priority Critical patent/EP3764594A4/en
Publication of WO2019184752A1 publication Critical patent/WO2019184752A1/zh
Priority to US17/033,385 priority patent/US11374857B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/38—Flow based routing
    • 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/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • 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/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing 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/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • 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/34—Signalling channels for network management communication
    • H04L41/344—Out-of-band transfers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/20—Hop count for routing purposes, e.g. TTL
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/42—Centralised routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application relates to the field of communications, and in particular, to a method, device, and system for managing a network device.
  • Autonomic Networking is a network of self-configuring, self-optimizing, self-repairing, and self-protection functions consisting of multiple network devices.
  • a network management system (NMS) is generally used to manage and maintain the network device.
  • NMS network management system
  • the NMS needs to establish a communication connection with each network device in the ad hoc network through the northbound interface, and then the NMS can instruct each network device to perform related management operations through the northbound interface, and obtain related information reported by each network device. Information to achieve management of each network device.
  • the management method in the related art has a high dependency on the NMS, and the application flexibility is poor, and the northbound interface needs to be deployed in the NMS and each network device, which increases the cost of the management method.
  • the present invention provides a management method, device, and system for a network device, which can solve the problem that the management method in the related art has high cost and poor application flexibility.
  • the technical solutions are as follows:
  • the first aspect provides a management method of a network device, which can be applied to a first network device in an ad hoc network.
  • the method may include: acquiring management information of a service flow, where the management information includes a type of management operation and the service.
  • An identifier of the flow the first network device is a starting network device of the service flow; determining, according to the identifier of the service flow, a second network device on a forwarding path of the service flow, where the second network device is the first network a network device of the next hop of the device; sending a control packet to the second network device, where the control packet includes the management information, and the second network device may forward the control packet to the forwarding path hop by hop
  • Each of the network devices, the control message is used to instruct the second network device to perform the management operation, and obtain information associated with the management operation; afterwards, the first network device can receive the response message from the second network device, The response message includes information related to the management operation acquired by the second network device.
  • the management method of the network device provided by the application can implement the management of the second network device on the forwarding path of the service flow by using the starting network device of the service flow, the management method avoids the dependence on the NMS, and effectively reduces the network.
  • the management cost of the device improves the management flexibility of the network device.
  • the first network device may include a control plane and a service plane; correspondingly, the first network device sends a control packet to the second network device, including: sending, by the service plane, the control packet to the second network device;
  • Receiving, by the second network device, the response message from the second network device comprising: receiving, by the control plane, a response message from the second network device.
  • the control plane is a plane independent of the service plane, and the control plane of each network device in the ad hoc network has full connectivity, the response packet is guaranteed to be normal regardless of whether the service plane of the second network device fails. Receiving and transmitting to ensure that the first network device can analyze and locate the fault of the second network device in time.
  • control packet may further include: a task identifier and an identifier of the starting network device of the service flow, where the identifier of the initial network device is an identifier of the first network device, and the task identifier is the first network device.
  • the response packet sent by the second network device may also include the task identifier, so that the first network device may determine, according to the task identifier in the response packet, a management operation of the service flow corresponding to the response packet, and perform the presentation. So that the administrator can accurately know the information corresponding to the management operations for different business flows.
  • control packet may further include: an identifier of the current network device, where the identifier of the current network device is used to indicate a network device that currently sends the control packet, where the control packet sent by the first network device is The identifier of the current network device is the identifier of the first network device.
  • the network device that receives the control packet may determine the identifier of the current network device as the identifier of the network device of the previous hop and carry it in the response packet to the first network device. Further, the first network device can identify the forwarding path of the service flow according to the identifier of the network device of the last hop of each network device, and the network device included in the forwarding path, that is, the forwarding path can be visualized.
  • control packet may further include: a type of information to be obtained;
  • control packet may instruct the second network device to perform a management operation according to the type of the management operation, and acquire information indicating the type of the information to be acquired.
  • the second network device is instructed to obtain the corresponding type of information by using the type of the information to be obtained, which effectively improves management flexibility.
  • each of the network devices in the ad hoc network may be configured with multiple function modules for performing different operations, and the control message may further include: an object name of the function module for performing the management operation;
  • control message may be used to instruct the second network device to perform the management operation by using the function module indicated by the object name, and acquire information associated with the management operation.
  • the corresponding function module is instructed to perform the management operation by the object name, and the associated information is obtained, thereby improving the accuracy of managing the network device.
  • control packet may further include: control information, where the control information may include at least one of the first forwarding control information and the second forwarding control information.
  • the first forwarding control information is used to indicate that the second network device forwards the control packet or stops forwarding the control packet when the second network device does not support the management operation;
  • the second forwarding control information is used to indicate that the second network device forwards the control packet to one of the next hop network devices when the network device of the next hop of the second network device includes at least two, or The network device of each next hop of the second network device forwards the control message separately.
  • control information in the control packet By encapsulating the control information in the control packet, flexible control of the second network device can be implemented, and the flexibility of network device management is improved.
  • control message may be a Generic Autonomic Signaling Protocol (GRASP) request message, where the GRASP request message may include: a message type field, a task identifier field, and a management object field;
  • GRASP Generic Autonomic Signaling Protocol
  • the message type field is used to indicate the message type of the control message
  • the task identifier field is used to carry the task identifier.
  • the management object field is configured to carry at least one of a type of the management operation, an identifier of the service flow, an identifier of the initial network device, the object name, a type of the information to be acquired, and the control information.
  • management object field may include: an object name field and an object information field;
  • the object name field is used to carry the object name
  • the object information field includes: a starting network device identification field, a current network device identification field, a forwarding path information field, a control information field, an operation type field, and a management information field;
  • the initial network device identifier field is used to carry the identifier of the network device that is forwarded; the current network device identifier field is used to carry the identifier of the network device that forwards the control packet; the forwarding path information field includes a path type field and a key field, the path type field is used to carry the type of the forwarding path, where the key field is used to carry the identifier of the service flow; the control information field is used to carry the control information; the operation type field is used to carry the management The type of operation; the management information field is used to carry the type of the information to be acquired.
  • the response message sent by the second network device may further include: an identifier of the second network device and an identifier of the network device of the last hop of the second network device; the method further includes:
  • the first network device may determine a forwarding path of the service flow according to the identifier of the second network device and the identifier of the network device of the last hop of the second network device (that is, the identifier of the first network device)
  • the network device is included to enable identification of the forwarding path of the service flow.
  • the forwarding path of the service flow may further include a downstream network device that is located downstream of the second network device, and the method may further include:
  • Receiving, by the second network device, the response packet from the downstream network device, the response packet from the downstream network device may include: an identifier of the downstream network device and an identifier of the network device of the last hop of the downstream network device;
  • the process of determining, by the first network device, the network device included in the forwarding path of the service flow may include:
  • the forwarding path and the network device included in the forwarding path can thereby realize the visualization of the forwarding path, thereby improving the flexibility of subsequent management of the network device on the forwarding path.
  • the method further includes:
  • the management information is encapsulated by using the forwarding model to obtain the control message.
  • the first network device may encapsulate the control packet by using the same forwarding model as the service packet, and may forward the control packet in an out-of-band manner to avoid the actual service.
  • the second aspect provides a network device management method, which can be applied to a second network device in an ad hoc network.
  • the method can include: receiving a control packet from the first network device, where the control packet includes a service flow.
  • Management information the management information includes a type of management operation and an identification of the service flow, the first network device is a starting network device of the service flow; performing a management operation according to the type of the management operation, and acquiring the management operation Associated information; sending a response message to the first network device, the response message including the information associated with the management operation.
  • the second network device may perform a management operation under the instruction of the control packet sent by the first network device, and report the obtained information associated with the management operation to the The first network device, whereby the first network device can implement management of the second network device on the forwarding path, the method avoids the dependence on the NMS, reduces the management cost of the network device, and improves the management flexibility of the network device. Sex.
  • control packet may further include: an identifier of the current network device, where the identifier of the current network device is used to indicate a network device that sends the control packet, where the network device that sends the control packet is in the service flow.
  • the network device located at the last hop of the second network device On the forwarding path, the network device located at the last hop of the second network device;
  • the method may further include:
  • the response message further includes: an identifier of the second network device and an identifier of the network device of the last hop of the second network device.
  • the first network device may identify the forwarding path of the service flow and the network device included in the forwarding path according to the identifier of the second network device and the identifier of the network device of the previous hop. That is, the visualization of the forwarding path can be realized.
  • the second network device may include a control plane and a service plane.
  • the process of receiving the control packet from the first network device may include: receiving, by the service plane, a control packet from the first network device, And sending the control message to the control surface;
  • the process of performing a management operation according to the type of the management operation and acquiring information associated with the management operation may include: performing the management operation through the control plane, and acquiring information associated with the management operation;
  • the process of sending the response packet to the first network device may include: sending, by using the control plane, the response packet to the first network device.
  • the control plane is a plane independent of the service plane, and the control plane of each network device in the ad hoc network has full connectivity, the response packet is guaranteed to be normal regardless of whether the service plane of the second network device fails. Receiving and transmitting to ensure that the first network device can analyze and locate the fault of the second network device in time.
  • the method may further include:
  • the second network device forwards the control packet to the network device of the next hop, and can implement the hop-by-hop forwarding of the control packet on the forwarding path, so that each network device on the forwarding path can receive the control packet. And performing a corresponding management operation, whereby the first network device can implement management of each network device on the forwarding path of the service flow.
  • the process for the second network device to forward the control packet to the network device of the next hop of the second network device may include:
  • the updated control message is forwarded to the network device of the next hop of the second network device.
  • the second network device updates and then forwards the identifier of the current network device in the control packet, and ensures that the network device of the next hop can accurately determine the network of the previous hop based on the identifier of the current network device in the control packet.
  • the identity of the device is not limited to the identity of the device.
  • control packet may further include: a type of the information to be obtained; and correspondingly, the acquiring the information associated with the management operation may include:
  • the second network device is instructed to obtain the corresponding type of information by using the type of the information to be obtained, which effectively improves management flexibility.
  • control packet may further include: control information, where the control information includes at least one of the first forwarding control information and the second forwarding control information;
  • the process of forwarding the control packet to the network device of the next hop of the second network device may include:
  • the control packet is forwarded to the network device of the next hop;
  • the process of forwarding the control packet to the network device of the next hop of the second network device may include:
  • the network device of the next hop of the second network device includes at least two, if the second forwarding control information is the first control information, determining a target network device from the network devices of the at least two next hops, And forwarding the control packet to the target network device; if the second forwarding control information is the second control information, forwarding the control packet to each network device of the next hop.
  • the second network device By controlling the manner in which the second network device forwards the control packet by using the control information encapsulated in the control packet, the second network device can be flexibly controlled, and the flexibility of the network device management is improved.
  • control packet may further include: a task identifier and an identifier of the starting network device of the service flow, where
  • the identifier of the initial network device is an identifier of the first network device
  • the task identifier is an identifier that is allocated by the first network device for the management operation of the service flow; the response packet may further include: the task identifier.
  • the response packet includes the task identifier, so that the first network device can determine the management operation of the service flow corresponding to the response packet according to the task identifier in the response packet, and perform the presentation, so that the administrator can accurately learn Information corresponding to the management operations of different business flows.
  • the response message may be a GRASP response message, where the GRASP response message may include: a message type field, a task identifier field, and a management object field;
  • the message type field is used to indicate the message type of the response message
  • the task identifier field is used to carry the task identifier.
  • the management object field is configured to carry information acquired by the second network device and associated with the management operation.
  • management object field may include: an object name field and an object information field;
  • the object name field is used to carry the object name
  • the object information field includes: a starting network device identification field, an upstream network device identification field, a current network device identification field, a role identification field, a forwarding path information field, a management information field, and an information field;
  • the initial network device identifier field is used to carry the identifier of the starting network device of the service flow; the upstream network device identifier field is used to carry the identifier of the network device of the last hop of the second network device; the current network
  • the device identification field is used to carry the identifier of the current network device, that is, the identifier of the second network device; the role identifier field is used to carry the role of the second network device on the forwarding path of the service flow;
  • the forwarding path information field includes a path type field, a path status field, and a keyword field, where the path type field is used to carry the type of the forwarding path, where the path status field is used to carry the path status of the forwarding path, where the key field is used to carry the service flow.
  • the management information field is used to carry the type of the information to be acquired, and the information field is used to carry the information acquired by the second network device and associated with the management operation.
  • the third aspect provides a management device for a network device, which is applied to a first network device in an ad hoc network, where the device may include at least one module, where the at least one module may be used to implement the network provided by the foregoing first aspect.
  • Device management method for a network device, which is applied to a first network device in an ad hoc network, where the device may include at least one module, where the at least one module may be used to implement the network provided by the foregoing first aspect.
  • a fourth aspect provides a management device for a network device, which is applied to a second network device in an ad hoc network, where the device may include at least one module, where the at least one module may be used to implement the network provided by the second aspect.
  • Device management method for a network device, which is applied to a second network device in an ad hoc network, where the device may include at least one module, where the at least one module may be used to implement the network provided by the second aspect.
  • a network device in a fifth aspect, can include: a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the computer program to implement the first The method for managing a network device provided by the aspect, or the method for managing a network device provided by the second aspect.
  • the sixth aspect provides a network device, where the network device includes: a main control board, and a switching network board and at least one interface board respectively connected to the main control board, the main control board, the at least one interface board, and
  • the switching network board may be used to implement the management method of the network device provided by the foregoing first aspect, or may be used to implement the management method of the network device provided by the foregoing second aspect.
  • a seventh aspect a computer readable storage medium having stored therein instructions for causing a computer to execute the network device provided by the first aspect when the computer readable storage medium is run on a computer
  • a computer program product comprising instructions for causing a computer to execute the management method of the network device provided by the above first aspect, or performing the above second aspect, is provided when the computer program product is run on a computer Management method of network equipment.
  • a ninth aspect provides a management system for a network device, which is applied to an ad hoc network, where the management system may include: a first network device and a second network device;
  • the first network device may include the management device of the network device provided by the foregoing third aspect, or may be the network device provided by the foregoing fifth or sixth aspect;
  • the second network device may include the management device of the network device provided by the foregoing fourth aspect, or may be the network device provided by the fifth aspect or the sixth aspect.
  • the embodiment of the present invention provides a network device management method, device, and system.
  • the first network device in the self-organizing network obtains the management information of the service flow
  • the second network can be hopped to the next hop.
  • the device sends a control message, where the control message includes the management information, the control message is used to instruct the second network device to perform the management operation, obtain information associated with the management operation, and associate the acquired management operation with the management operation.
  • the information is encapsulated in the response packet and reported to the first network device, so that the first network device can implement management of the second network device on the forwarding path. Since the management method can be triggered by the first network device, the dependency on the NMS is avoided, and the management flexibility is improved. Moreover, since the northbound interface is not required to be deployed in each network device, the management cost of the network device is effectively reduced.
  • FIG. 1 is an architectural diagram of a self-organizing node using a reference model of ANIMA according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a self-organizing network according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for managing a network device according to an embodiment of the present invention.
  • FIG. 4 is a structural diagram of a method for managing a network device according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a control packet according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a response packet according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a network device management apparatus according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of another network device management apparatus according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of still another network device management apparatus according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of still another network device management apparatus according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of another network device according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a management system of a network device according to an embodiment of the present invention.
  • IETF Internet Engineering Task Force
  • RRC Request for Comments
  • ANIMA Autonomic Networking Integrated Model and Approach
  • a network device using an ANIMA reference model can be classified into an Autonomic Networking Infrastructure (ANI) and an Autonomic Service Agent (ASA).
  • ANI is the basic framework platform of ANIMA, which can provide an independent and stable management plane for self-organizing nodes.
  • the ANI mainly includes Bootstrapping Remote Secure Key Infrastructures (BRSKI) and self-organizing control planes ( Autonomic Control Plane, ACP) and the three core components of the GRASP module.
  • BRSKI Bootstrapping Remote Secure Key Infrastructures
  • ACP Autonomic Control Plane
  • the ACP can automatically assign addresses to the self-organizing nodes newly added to the ANIMA domain and establish a hop-by-hop security tunnel with the adjacent self-organizing nodes, so that all the self-organizing nodes in the ANIMA domain can be fully connected.
  • the ASA is a functional module (also referred to as a service instance) for implementing self-organizing functions in a self-organizing node, and the self-organizing function may include a query function and a subscription function.
  • Multiple ASAs can be deployed within each ad hoc node to implement different functions. For example, ASA 1 to ASA 3 have a total of 3 ASAs deployed in the self-organizing node shown in FIG. 1.
  • the self-organizing node After the self-organizing node obtains the domain certificate issued by the controller of the self-organizing network, it can join the self-organizing network (also called ANIMA domain), and the self-organizing node joining the ANIMA domain may also be called an ACP Node.
  • the ACP Node can include a control plane and a data plane.
  • the control plane is also called the ACP Virtual Routing Forwarding (VRF) module.
  • the ACP VRF module can be understood as a virtual routing instance of the self-organizing network, which includes an independent routing protocol, an access interface, and a routing table. So it can be equivalent to a separate virtual router.
  • the control plane includes a virtual-out-of-band channel (VOOB), which can be used to implement network management tasks.
  • VOOB virtual-out-of-band channel
  • the service plane is a regular service plane and can be used to forward service packets.
  • the control plane ie, the ACP VRF module
  • the ACP VRF Since the control plane (ie, the ACP VRF module) has an independent forwarding plane, its connectivity has no dependence on the service plane. Regardless of whether the service plane has routing and which forwarding model is adopted, it does not affect the connectivity of the ACP VRF, and its isolation is high. Moreover, as long as the ACP Node is located in the ANIMA domain, the ACP VRF will always exist, and it is not affected by the configuration and operation status of the service plane, so its stability is high; in addition, the ACP VRF can also be used for low-power lossy network routing.
  • the Routing Protocol for LLN (RPL) implements data interaction between any two ACP Nodes in the ANIMA domain, that is, the ACP VRF has full connectivity in the ANIMA domain.
  • the ACP VRF adopts GRASP as a unified communication protocol, has rich basic communication capabilities, and has high scalability, and can carry a rich data type. Further, since the ACP Nodes can communicate through the ACP secure tunnel after the secure bootstrapping of the BRSKI, the communication security between the ACP Nodes is high. Moreover, within the same ACP Node, all data of the other party can be securely accessed between the ACP VRF and the business plane.
  • FIG. 2 is a schematic structural diagram of a self-organizing network according to an embodiment of the present invention.
  • the self-organizing network may include multiple network devices, and each network device is an ad-hoc node.
  • the network device may be a terminal host (such as a server or a computer terminal), or may be an intermediate forwarding device (such as a router or a switch), and the type of the network device is not limited in the embodiment of the present invention.
  • Each network device in the ad hoc network is a device that obtains a domain certificate of the ANIMA domain and completes the BRSKI initiation and ACP secure tunnel establishment, that is, each network device has successfully joined the ANIMA domain. For example, as shown in FIG.
  • the self-organizing network may include a total of 8 network devices R1 to R8, and the network devices C1 and C2 are extra-domain devices of the ANIMA domain.
  • the starting network device of each service flow in the ad hoc network can manage other network devices on the forwarding path of the service flow, thereby effectively improving the flexibility of network device management. .
  • FIG. 3 is a flowchart of a method for managing a network device according to an embodiment of the present invention. The method may be applied to the self-organizing network shown in FIG. 2, and the method may include:
  • Step 101 The first network device acquires management information of the service flow.
  • the first network device is an Ingress network device of the service flow, and may also be referred to as an Ingress Node.
  • the administrator may determine the starting network device (ie, the first network device) of the service flow, and may The first network device sends the management information; or the administrator can remotely log in to the first network device by using an operation and maintenance (OM) interface provided by the first network device;
  • OM operation and maintenance
  • the management information of the service flow may be input to the first network device by means of a command line.
  • the management information may include at least the type of management operation and the identification of the service flow.
  • the type of management operation may include at least one of a query operation, a subscribe operation, an unsubscribe operation, and a re-subscribe operation.
  • the query operation is used to query related information of the network device on the forwarding path
  • the subscription operation is used to subscribe to related information of the network device on the forwarding path
  • the unsubscribe operation is used to cancel the subscription of the related information of the network device, and the resubscribing operation is performed.
  • the state of the forwarding path of the service flow is detected by the first network device, for example, when a network device exits the ANIMA domain, the related information of the network device on the forwarding path is re-acquired.
  • the information about the foregoing network device may include a forwarding entry of the network device, a path state of the downstream path, and a state of the network device, which are not limited in this embodiment of the present invention.
  • the identifier of the service flow may be an identifier that can uniquely identify the service flow.
  • the type of identification of the service flow may also be different depending on the type of the ad hoc network. For example, when the ad hoc network belongs to a public network (ie, a public network), the identifier of the service flow may be a destination Internet Protocol (IP) address of the service flow; when the ad hoc network belongs to a virtual private network (Virtual The private network (VPN), that is, the private network, the identifier of the service flow may include the destination IP address of the service flow and the VPN instance identifier.
  • IP Internet Protocol
  • VPN Virtual The private network
  • the forwarding path of a service flow is as shown by the dotted arrow in FIG. 2.
  • the starting network device of the service flow is R1.
  • the target network device is R8, and the transit (Transit) network devices are R2 to R7.
  • the target network device refers to a network device located at the end of the forwarding path, and the forwarding network device refers to a network device on the forwarding path for connecting the starting network device and the target network device.
  • the first network device R1 can be remotely logged in through the OM interface provided by the first network device R1, and the command is input to the first network device R1 in a command line manner. Management information for business flows.
  • the management information acquired by the first network device R1 may include, in addition to the type of the management operation and the identifier of the service flow, the first control flow. Control information, and second control information for indicating feedback information of each network device.
  • the first control information may include: the number of control packets sent, the interval at which the control packet is sent, the timeout period of the operation, and some encapsulation parameters in the control packet (for example, parameters carried in the encapsulation header of the control packet)
  • the second control information may include: detailed level control information of the feedback information, control information of a type of information to be carried by the response message fed by each network device, and a message for indicating whether to carry an error (Error) message or a log ( Logging) Control information of information, etc.
  • the content of the information included in the management information may be flexibly set according to actual requirements, which is not limited by the embodiment of the present invention.
  • Step 102 The first network device determines, according to the identifier of the service flow, the second network device on the forwarding path of the service flow.
  • the second network device is a network device located at a next hop of the first network device on a forwarding path of the service flow.
  • the first network device may obtain the forwarding entry from the locally stored forwarding database (FDB) according to the identifier of the service flow in the management information, and based on the The forwarding entry determines a second network device on the forwarding path of the traffic flow.
  • FDB forwarding database
  • the ASA may use the service flow according to the identifier of the service flow in the management information.
  • the path information may include the identifier of the network device of the next hop, or may also include the identifier of the outbound interface (ie, the target network device), and the Label Switching Path (Label Switching Path, LSP) information such as the label stack.
  • Label Switching Path Label Switching Path
  • the first network device R1 may query, according to the identifier of the service flow, the second network device on the forwarding path of the service flow from the FDB of the service plane as the network device R2.
  • Step 103 The first network device encapsulates the management information to obtain a control packet.
  • the first network device may encapsulate the management information according to a preset forwarding model to obtain a control packet.
  • the forwarding model of the service flow may be determined based on the identifier of the service flow, and the forwarding is performed.
  • the model may generally include an IP model or a Multi-Protocol Label Switching (MPLS) model, etc., wherein the IP model may include a fourth edition Internet Protocol (IPv4) model and a sixth edition Internet Protocol (IPv6) model.
  • IPv4 Internet Protocol
  • IPv6 sixth edition Internet Protocol
  • the first network device may encapsulate the management information according to the determined forwarding model to obtain a control packet.
  • the control packet can be forwarded to each network device on the forwarding path of the service flow hop by hop.
  • the network device that receives the control packet needs to perform the management operation indicated by the control packet, and the response packet is sent to the first A network device reports information associated with the management operation, so that the first network device can implement management of each network device on the forwarding path.
  • control packet may further include a task identifier and an identifier of a starting network device of the service flow, where the identifier of the initial network device is an identifier of the first network device, and the task identifier is It may be a unique identifier assigned by the first network device for the management operation of the service flow.
  • the task identifier may be a unique identifier randomly assigned by the first network device for management operations of the traffic flow.
  • control message may further include: at least one of an identifier of the current network device, a type of information to be acquired, an object name of a function module for performing the management operation, and control information.
  • the identifier of the current network device is used to indicate the network device that currently sends the control packet.
  • the identifier of the current network device is also the identifier of the first network device.
  • the type of the information to be acquired may indicate the type of information that the second network device needs to acquire associated with the management operation.
  • the object name may instruct the second network device to perform a management operation by the function module indicated by the object name.
  • the control information may include at least one of the first forwarding control information and the second forwarding control information; the first forwarding control information is used to not support the management operation in the second network device (for example, the object is not deployed in the second network device)
  • the function module indicated by the name indicates that the second network device continues to forward the control message or stops forwarding the control message; the second forwarding control information is used by the network device of the next hop of the second network device to include at least At the same time, the second network device is instructed to forward the control message to the network device of the next hop, or to the network device of each next hop of the second network device.
  • FIG. 5 is a schematic structural diagram of a control packet according to an embodiment of the present invention.
  • the control packet may be a GRASP request message, where the GRASP request message may include a transport header and user data.
  • User Datagram Protocol (UDP) headers and GRASP packets are the payload of the GRASP request message.
  • UDP User Datagram Protocol
  • the GRASP request message may adopt different transport encapsulation headers according to different forwarding models.
  • the transport encapsulation header may adopt an IPv4 encapsulation header or an IPv6 encapsulation header
  • the transport encapsulation header may adopt a tunnel encapsulation header
  • the tunnel header may include an IPinIP (IP encapsulated in IP) encapsulation header, a Generic Routing Encapsulation (GRE) encapsulation header, or a Virtual Extensible LAN (VXLAN) tunnel encapsulation header
  • the transport encapsulation header may adopt an MPLS encapsulation header
  • the MPLS encapsulation header may include an MPLS label stack and an IP encapsulation header.
  • the source port number can be randomly assigned by the first network device.
  • the UDP destination port number is the listening port number of the GRASP module. Therefore, the second network device that receives the control packet can distribute the control packet to the GRASP according to the UDP destination port number. The module processes it.
  • the GRASP Packet can include: [message-type, session-id, objective].
  • the message-type is a message type field, and is used to indicate a message type of the control packet.
  • the control message may use a GRASP synchronization mechanism, that is, the control message may be a GRASP synchronization request message.
  • the message-type can be set to M_REQ_SYN.
  • the session-id is a task identifier field, and is used to carry the task identifier assigned by the first network device for the management operation of the service flow.
  • the response packet sent by the second network device after receiving the control packet also includes the task identifier, and the first network device may match the received response packet according to the task identifier to determine corresponding to each response packet. Management operations for business flows.
  • the objective is a management object field
  • the management object field is used to carry at least one of a type of a management operation, an identifier of a service flow, an identifier of a starting network device, an object name, a type of information to be acquired, and control information.
  • the object-name field is an object name field, and the object name field is used to carry an object name that can uniquely identify a function module (ie, a management object) in the second network device for performing the management operation.
  • the object name may be composed of UTF-8 (a variable length character encoding for Unicode) characters.
  • the character length of the object name is not limited in the embodiment of the present invention.
  • the object name can be divided into two types: standard name and private name, wherein the standard name is uniformly allocated by The Internet Assigned Numbers Authority (IANA), and the private name can be defined by the ASA in the network device, and
  • the private name usually contains at least one character ":".
  • the private name of the ASA that can implement the subscription function in the network device can be "xxxx.com:PathStatusSubcribe".
  • Objective-flags is an object flag field that specifies the type of operation that GRASP pre-defines, for example, can be set to F_SYNCH.
  • Loop-count is a loop count field. This field can be used to avoid an infinite loop when the GRASP module performs operations such as a Discovery operation, a Negotiation operation, or a Flood operation.
  • the objective-value is an object information field.
  • UUA unique local address
  • Current is the current network device identifier field, which is used to carry the identifier of the network device that currently sends the control packet.
  • the identifier of the network device may include the ACP ULA of the current network device and the management address of the service plane of the current network device.
  • the first network device is the network device R1 shown in FIG. 2, in the control packet sent by the first network device R1, the ingress field and the current field are all carried by the first network.
  • the path-info is a forwarding path information field, which is used to carry information about the forwarding path of the service flow.
  • the path-type is a path type field, which is used to carry the type of the forwarding path.
  • the type of the forwarding path varies according to the forwarding model, and may include IPv4, IPv6, IPv4-VRF, IPv6-VRF, or MPLS.
  • the key field is used to carry the identifier of the service flow.
  • the type of the identifier of the service flow carried by the keyword field varies according to the type of the forwarding path.
  • the identifier of the service flow may be the destination IPv4 address of the forwarding path.
  • the identifier of the service flow may be the destination IPv4 address of the forwarding path and the VRF name.
  • Path-status is the path status field, which is used to carry the status of the forwarding path.
  • the path-status field may be a preset initial value; after receiving the control packet, the second network device may update the path-status field by using the obtained path state.
  • the path state may generally include: a continuous state (continued), a disconnected state (broken), and a terminated state (terminated).
  • the path state may be determined to be a continuous state; when the second network device that receives the control packet does not When the target network device is not queried to the network device of the next hop, the path state may be determined to be the disconnected state; when the second network device that receives the control packet is the target network device, the path state may be determined to be the terminated state. .
  • the path state may further include: a sub-branch state, where the sub-path state may be used to indicate whether the downstream path of the second network device includes multiple sub-paths (ie, whether there are multiple next-hop network devices) Correspondingly, when there are multiple sub-paths, the path status of each sub-path may also be included in the path status.
  • a sub-branch state where the sub-path state may be used to indicate whether the downstream path of the second network device includes multiple sub-paths (ie, whether there are multiple next-hop network devices)
  • the path status of each sub-path may also be included in the path status.
  • the control-flags are control information fields, and the control information field may be used to carry control information, and the control information may include at least one of first forwarding control information (CF_TRANSIT) and second forwarding control information (CF_ALL_SUBPATH).
  • the first forwarding control information is used to indicate that the second network device continues to forward the control packet or stops forwarding the control packet when the second network device does not support the management operation;
  • the second forwarding control information When the network device for the next hop of the second network device includes at least two, instructing the second network device to forward the control packet to the network device of one of the next hops, or to the second network device Each next hop network device forwards the control message separately.
  • the op-type is an operation type field, which is used to carry a type of management operation, and the types of the management operations may include a query operation, a subscription operation, an unsubscribe operation, and a resubscription operation.
  • the first network device in order to ensure service security, for the service data in the second network device, can only perform a read-only operation.
  • Timeout is a timeout field that can be used to configure a timeout for a subscription operation to prevent the subscription operation from occupying related resources indefinitely. For example, when the field is X, it can indicate that the subscription operation is invalid after the X duration, and when the field is 0, it can indicate that there is no timeout limit.
  • the type is a management information field, which is used to carry the type of the information to be obtained; the params is an information field, and the field is used to carry the information associated with the management operation, that is, the information indicating the type of the information to be acquired.
  • *[type,params] indicates that the type and params fields may include multiple groups, and each group may record a type of information to be acquired, and information indicating the type.
  • the administrator can define a type field corresponding to the objective-name according to requirements. For example, if the forwarding path of the service flow needs to be identified, the first network device may query the network device of the last hop of each network device on the forwarding path, and correspondingly, the type of the information to be obtained carried in the type field may include: Controls the input interface name of the message, or the IP address of the input interface that controls the message.
  • the various fields of the payload in the control packet may be selected according to actual requirements. For example, for the query operation, the timeout field may not be set; or the control-flags field may not be set in the control packet.
  • the second network device can directly forward the control packet to each network device of the next hop.
  • the embodiment of the present invention does not limit the type of the field encapsulated in the control packet.
  • each network device after receiving the control packet, each network device needs to obtain the management information encapsulated in the control packet to perform the management operation. Therefore, when the first network device encapsulates the control packet, the first hop-by-hop sending mechanism may be determined based on the forwarding model, and the network device that receives the control packet is encapsulated in the control packet and sent to the hop by hop.
  • the related fields of the control message are different according to the forwarding model.
  • the related field may be a Time To Live (TTL), a Hop-Limit, a Router Alert, a Label Alert, or a Control Word.
  • TTL Time To Live
  • Hop-Limit a Hop-Limit
  • Router Alert a Label Alert
  • Control Word Control Word
  • Step 104 The first network device sends the control packet to the second network device.
  • the first network device may send the control packet to the second network device by using the service plane, and the second network device may further forward the control packet to the downstream network device located downstream thereof, so that the control may be performed.
  • the packet is forwarded hop by hop to each network device on the forwarding path.
  • the first network device R1 can send a control message to the second network device R2 through its service plane.
  • control packet is encapsulated by using the same forwarding model as the service packet, and is theoretically forwarded based on the same forwarding path as the service packet, thereby implementing simulation of the service packet;
  • control packet is forwarded in an out-of-band manner, so that the forwarding of service packets of the actual service flow is not affected. And because it does not depend on service packets, the flexibility of the control message generation and forwarding is higher.
  • Step 105 The second network device performs a management operation according to the type of the management operation, and acquires information associated with the management operation.
  • the second network device may obtain the management information encapsulated in the control packet, perform a management operation based on the type of the management operation specified in the management information, and acquire and manage the packet.
  • the associated information is manipulated.
  • a plurality of functional modules for performing different operations are deployed in each of the network devices in the self-organizing network, and the control packets sent by the first network device may also include The object name of the function module for performing the management operation (ie, the objective-name) and the type of the information to be acquired. Therefore, after receiving the control message, the second network device can execute the function module indicated by the object name. This management operation.
  • the second network device may acquire information indicating the type of the information to be acquired.
  • the second network device R2 can receive the control message sent by the first network device through the service plane, and can send the control message to the control plane, for example, can be sent to run in the control.
  • In-plane host stack The host protocol stack can distribute the control packet to the GRASP module according to the UDP destination port number in the control packet, and the GRASP module further distributes the control packet to the objective-name according to the objective-name in the control packet.
  • the indicated ASA is processed. For example, if the management operation is a query operation, the ASA indicated by the objective-name is the ASA for implementing the query function. After receiving the control message distributed by the GRASP module, the ASA for implementing the query function may perform the query operation and obtain information indicated by the type of the information to be acquired.
  • the second network device may not need to perform the management operation.
  • the second network device may further determine whether to continue forwarding the control packet according to the first forwarding control information encapsulated in the control packet. For example, when the first forwarding control information in the control packet is preset control information (for example, 1), the second network device may forward the control packet to the network device of the next hop, that is, the second network. The device may perform step 108 and step 109; when the first forwarding control information in the control packet is not preset control information (for example, the first forwarding control information is 0), the second network device may stop forwarding the control packet. The control packet can be discarded, that is, the second network device does not need to perform step 108 and step 109 again.
  • Step 106 The second network device encapsulates the obtained information associated with the management operation to obtain a response packet.
  • the second network device may encapsulate the information associated with the management operation according to the preset encapsulation model, and obtain a response packet.
  • the response packet may further include an identifier of the second network device and an identifier of the network device of the last hop of the second network device, that is, an identifier of the first network device, to facilitate the first network.
  • the device may identify the forwarding path of the service flow and the forwarding path according to the identifier of each network device on the forwarding path and the identifier of the network device of the last hop of each network device.
  • the second network device can directly determine the identifier of the current network device in the control packet as the network device of the previous hop because the control packet received by the second network device further includes the identifier of the current network device.
  • logo For example, the second network device may determine the identifier carried in the current field in the control packet as the identifier of the network device of the previous hop.
  • the identifier of the network device of the previous hop is the first network. The identity of the device.
  • control packet sent by the first network device may further include: a task identifier and an identifier of the starting network device of the service flow, and correspondingly, the response packet generated by the second network device
  • the task identifier and the identifier of the initial network device may also be included, so that the first network device may identify a management operation of the service flow corresponding to the response message based on the task identifier.
  • FIG. 6 is a schematic structural diagram of a response packet according to an embodiment of the present invention.
  • the response packet may be a GRASP response message.
  • the GRASP response message may include: an Internet Protocol Security (IPsec) protocol.
  • IPsec Internet Protocol Security
  • IPv6 encapsulation header IPv6 over IPsec header
  • UDP encapsulation header UDP encapsulation header
  • GRASP packet the UDP encapsulation header and the GRASP packet constitute the payload of the response packet.
  • the communication of the ACP VRF of each network device in the ad hoc network is performed based on a secure tunnel established by the ACP, so the IPv6 over IPsec header can be adopted.
  • the security tunnel may be an IPsec tunnel or an IPsec-based GRE tunnel (IPsec with GRE).
  • the DestPort is the UDP destination port number
  • the GRASP_LISTEN_PORT is the listening port number of the GRASP module
  • the listening port number is the well-known port number
  • the SrcPort is the source port number.
  • the source port number can be randomly assigned.
  • the UDP destination port number is the listening port number of the GRASP module. Therefore, the first network device that receives the response packet can distribute the response packet to the GRASP according to the UDP destination port number. The module processes it.
  • GRASP_Packet can include: [message type, session-id, objective].
  • the message-type is a message type field, which is used to indicate the message type of the response packet.
  • the response message may also use the synchronization mechanism of the GRASP, that is, the response message may be a GRASP synchronization response message. Accordingly, the message type can be set to M_SYNCH.
  • the session-id is a task identifier field, and is used to carry a task identifier, where the task identifier can be copied from the received control packet by the second network device.
  • the objective is a management object field, and is used to carry information acquired by the second network device and associated with the management operation.
  • the objective-name is an object name field for carrying the object name of the function module that performs the management operation.
  • the object name is the same as the object name encapsulated in the control message received by the second network device.
  • Objective-flags is an object flag field that specifies the type of operation and can be set to F_SYNCH.
  • the ingress is the starting network device identifier field, and is used to carry the identifier of the starting network device.
  • the ingress field may carry the ACP ULA of the first network device R1 and the service plane of the first network device R1. Manage the address.
  • the definition of the field indicates that the identifier of the network device of the last hop may include the ACP ULA of the network device of the last hop and the management address of the service plane of the network device of the last hop.
  • the upstream field may carry the ACP ULA of the first network device R1 and the management address of the service plane of the first network device R1.
  • the current field may carry the ACP ULA of the second network device R2, and the management of the service plane of the second network device R2. address.
  • the role is a role identifier field, which is used to carry the role of the second network device on the forwarding path of the service flow.
  • the role of the second network device may be any one of a forwarding network device, a target network device, and an edge network device. After the second network device receives the control packet, if the network device of the next hop is queried, and the network device of the next hop belongs to the ad hoc network, the role may be determined to be a forwarding network device; The network device of the next hop, but the network device of the next hop does not belong to the ad hoc network, and may determine that the role is an edge network device; if the second network device does not query the network device of the next hop, it may determine Its role is the target network device.
  • the role carried in the role identifier field in the response packet sent by the second network device R2 is the forwarding network device.
  • the path-info is a forwarding path information field, which is used to carry information about the forwarding path of the service flow.
  • the definition of the field may be the same as the definition of the forwarding path information field in the control packet.
  • the second network device may query the state of the corresponding forwarding path according to the path-type field and the path-keys field in the forwarding path information field in the control packet, and may obtain the query by using a query.
  • the status of the forwarding path updates the path-status field in path-info.
  • the type is a management information field, and is used to carry the type of information to be obtained.
  • the params is an information field, and is used to carry the information associated with the management operation acquired by the second network device.
  • the path-status field in the response packet fed back to the first network device may be set to Broken; and can return the reason why the detailed query forwarding entry failed in the params field. And, because the forwarding path is interrupted, the second network device can stop forwarding the control message.
  • Step 107 The second network device sends a response message to the first network device.
  • the second network device may send the response packet to the first network device by using the control plane.
  • the first network device may receive the response packet reported by the second network device by using the control plane. Since the control plane between the network devices in the ad hoc network has full connectivity, the response packet can be sent to the first network device in time, regardless of whether the service plane of the second network device fails.
  • a network device can locate and analyze faults on the service plane in time, effectively improving the reliability of managing network devices.
  • the second network device R2 may send the generated response message to the first network device R1 through its control plane.
  • the timing at which the second network device sends the response packet is also different.
  • the second network device may, after performing the query operation and obtaining the information of the query operation indication, feed back the response packet encapsulated with the acquired information to the first network device in real time. That is, the second network device can feed back the information associated with the query operation to the first network device by using the response message.
  • the second network device may report the response packet encapsulating the information to the first network device when detecting that the information indicated by the subscription operation changes, or the second network device may The information of the subscription operation is periodically queried according to the subscription period indicated by the subscription operation, and the response packet encapsulated with the information is reported to the first network device.
  • Step 108 The second network device determines, according to the identifier of the service flow, a network device that is located at a next hop of the second network device on a forwarding path of the service flow.
  • the second network device may determine the service from the forwarding entry stored in the local FDB, based on the identifier of the service flow encapsulated in the control packet, in addition to performing the management operation.
  • the network device of the next hop of the second network device On the forwarding path of the flow, the network device of the next hop of the second network device. Since only the ACP VRF of the network device belonging to the self-organizing network (ie, joining the AINMA domain) can achieve full connectivity, when the second network device determines that there is no next hop network device on the forwarding path (ie, the second network device) When the network device of the next hop does not belong to the ad hoc network, the second network device may not forward the control packet, that is, step 109 is not performed.
  • the ASA that receives the control message in the second network device R2 can perform a query in the FDB of the service plane according to the identifier of the service flow to determine the network device of the next hop.
  • the second network device R2 may determine that its next hop network device includes R3, R4, and R5.
  • Step 109 The second network device forwards the control packet to the network device of the next hop.
  • the second network device may forward the control packet to the network device of the next hop through the control plane, Therefore, the network device of the next hop can continue to forward the control packet.
  • the network device of the next hop determined by the second network device in the foregoing step 108 includes at least two, that is, a forwarding path of the service flow, an equal route exists in a downstream forwarding path of the second network device ( In the case of the Equal-Cost Multi-Path Routing (ECMP), the second network device can separately forward the control packet to each network device of the next hop.
  • ECMP Equal-Cost Multi-Path Routing
  • the second network device may further determine, according to the second forwarding control information encapsulated in the control packet, a forwarding manner of the control packet. For example, if the second forwarding control information is the first control information (for example, 0), the second network device may determine a target network device from the network devices of the at least two next hops, and the control packet Forwarding to the target network device; if the second forwarding control information is the second control information (for example, 1), the second network device may forward the control packet to each next hop network device. Wherein, when the second network device determines the target network device from the network devices of the at least two next hops, the hash algorithm may be used for determining.
  • the second forwarding control information is the first control information (for example, 0)
  • the second network device may determine a target network device from the network devices of the at least two next hops, and the control packet Forwarding to the target network device; if the second forwarding control information is the second control information (for example, 1), the second network device may forward the control packet to
  • the second network device may directly perform calculation according to a related field in the control packet (also referred to as a static hash algorithm), thereby selecting the target network device to ensure the at least two network devices of the next hop.
  • a related field in the control packet also referred to as a static hash algorithm
  • the second network device R2 may determine, according to the identifier of the service flow, a network device with three next hops of R3, R4, and R5. If the second forwarding control information encapsulated in the control packet is 1, the second network device R2 may copy the control packet and forward the control packet to the network devices R3, R4, and R5, respectively.
  • the forwarding path of a service flow includes only two network devices, R6 and R8, wherein the network device R6 is the initial network device, and the second network device of the next hop R8 is the target network device, and after the second network device R8 receives the control packet, the second network device R8 is the target network device and there is no next hop network device because the second network device R8 is in the forwarding path of the service flow. Therefore, the second network device R8 may stop forwarding the control packet, and may discard the control packet after obtaining the information encapsulated in the control packet.
  • control packet sent by the first network device may further include the identifier of the current network device, so the second network device may also adopt the second network before forwarding the control packet.
  • the identifier of the device itself updates the identifier of the current network device in the control packet, and then forwards the updated control packet to the network device of the next hop, so that the network device of the next hop can accurately obtain the previous one.
  • the current field in the control packet sent by the first network device R1 may carry the ACP ULA of the first network device R1 and the management address of the service plane of the first network device R1; the second network device R2 is receiving After the control message, the current field may be updated to the ACP ULA of the second network device R2 and the management address of the service plane of the second network device R2. Thereafter, the second network device R2 can forward the updated control message to the network devices R3, R4, and R5, respectively.
  • the forwarding path of the service flow further includes a downstream network device located downstream of the second network device
  • the second network device may further forward the control packet to the downstream network device hop by hop, and thus the forwarding path
  • the network device belonging to the ad hoc network can receive the control message.
  • each network device that receives the control packet can perform a management operation according to the type of the management operation in the control packet, obtain the information associated with the management operation, and report the response packet to the first network device.
  • the information related to the management operation, the report response message, and the continuation of the forwarding control message refer to the related description in the foregoing steps 105 to 109, and details are not described herein again.
  • the network devices R3 to R8 can receive the control from the first network device R1 on the forwarding path of the service flow of the network device starting with the first network device R1. For the message, the network devices R3 to R8 can also perform management operations, obtain information related to the management operation, and send the generated response message to the first network device R1.
  • the downstream network device located downstream of the second network device reports the response packet
  • the network device of the last hop of the downstream network device is not the first network device, so the downstream network device needs to pass the The method of hopping forwards the response packet to the first network device. That is, the response packet sent by the downstream network device is finally reported to the first network device by using the second network device.
  • the network device may also be referred to as an edge network device or an edge node, and the edge network device does not need to continue forwarding control messages. Therefore, in the embodiment of the present invention, only the forwarding network device needs to continue to forward the control packet, and the target network device and the edge network device do not need to forward the control packet.
  • Step 110 The first network device presents information associated with the management operation.
  • the first network device may obtain the response operation associated with the management operation in each response message.
  • the information is summarized, and the summarized result is presented to the remote terminal or the NMS through the OM interface, so that the administrator can know the information acquired by each network device on the forwarding path after performing the management operation.
  • the first network device may determine, according to the specified task identifier assigned to the specified management operation of the specified service flow, the task identifier from the received multiple response packets.
  • the response message of the specified task identifier is presented, and the information in the determined response message is presented as information associated with the specified management operation.
  • the response message sent by the second network device further includes the identifier of the second network device and the identifier of the network device of the last hop of the second network device, and the response packet sent by the downstream network device of the second network device.
  • the identifier of the downstream network device and the identifier of the network device of the last hop of the downstream network device are also included, so the first network device can also be based on its own identifier, the identifier of the second network device, and the second network device.
  • the identifier of the network device of one hop, the identifier of each downstream network device, and the identifier of the network device of the last hop of each downstream network device determine the forwarding path of the service flow, and the network device included in the forwarding path
  • the visualization of the forwarding path is implemented, and the specified management operation is performed on the designated network device according to the determined forwarding path and the network device, thereby effectively improving the management efficiency of the network device.
  • the first network device may match the session-id, ingress, and path-info fields in the response packet reported by each network device (including the second network device and the downstream network device), and the foregoing fields are the same.
  • the plurality of response packets are determined to be the packets reported by the plurality of network devices on the same forwarding path, and the identifiers of the current network devices in the plurality of response packets and the identifiers of the upstream network devices may be based on the identifiers of the plurality of response packets. Identifying a forwarding path with the first network device as a root node and a network device on the forwarding path.
  • each network device that joins the ANIMA domain will behave as a host route in the RPL routing table, and the prefix is the ACP ULA of the network device.
  • the RPL route reconverges.
  • the network device on the forwarding path can normally return the response packet to the first network device, the first network device can query the RPL routing table to check the status of the forwarding path when the information of the forwarding path is summarized according to the response packet. Specifies the status of the network device.
  • the first network device detects that the path state of the forwarding path of a certain service flow changes (for example, a network device on the forwarding path exits the ANIMA domain), the same session-id, ingress-acp-ula, The path-type and path-keys fields encapsulate control packets, and collect and refresh the forwarding path information through the control packets.
  • the first network device may determine the network device as an "isolated" network device on the forwarding path. If the first network device has previously performed a subscription operation on the "isolated” network device, the first network device may send a control message to the user to indicate that the subscription is unsubscribed (ie, the type of the management information encapsulated in the control packet is Unsubscribe) to clear the relevant subscription cache information in the network device.
  • the subscription cache information of the network device may also be timed out, that is, the network device may automatically clear the timeout period corresponding to the subscription operation.
  • the subscription caches information may also be timed out, that is, the network device may automatically clear the timeout period corresponding to the subscription operation.
  • the first network device in order to prevent a network device from reporting a response message after the network device has not reported the response message, the first network device incorrectly
  • a network device is identified as an "isolated" network device, and the first network device may also be configured with a caching mechanism, that is, the first network device may wait for a certain period of time after receiving the response packet, and then perform a summary calculation of the forwarding path. .
  • steps 108 through 109 may be performed prior to step 105 or concurrently with step 105. Any method that can be easily conceived by those skilled in the art within the technical scope of the present application is intended to be included in the scope of the present application and therefore will not be described again.
  • the embodiment of the present invention provides a method for managing a network device.
  • the control packet may be sent to the second network device of the next hop.
  • the control message includes the management information, where the control message is used to instruct the second network device to perform the management operation, obtain information associated with the management operation, and encapsulate the acquired information associated with the management operation.
  • the response packet is sent to the first network device, so that the first network device can implement management of the second network device on the forwarding path. Since the management method can be triggered by the first network device, the dependency on the NMS is avoided, and the management flexibility is improved. Moreover, since the northbound interface is not required to be deployed in each network device, the management cost of the network device is effectively reduced, and a relatively efficient solution can be provided for some small and medium-sized networks or the Internet of Things (IoT).
  • IoT Internet of Things
  • the NMS since the NMS understands the running status of the network device by querying a large number of entries to the network device, when the network is large, the NMS has obvious performance problems. Moreover, the NMS is limited to the northbound interface, and the types of management operations that can be implemented are limited, and it is difficult to accurately track and manage the network devices on the forwarding path of the service flow.
  • the NMS manages the network device the Simple Network Management Protocol (SNMP) packets that are exchanged between the two devices need to be forwarded through a regular forwarding entry (for example, a routing table).
  • SNMP Simple Network Management Protocol
  • the first network device in the ad hoc network may send a control packet through the service plane, and receive the second network device and the downstream network device of the second network device by using the control plane.
  • the response packet has no effect on the service packet of the service flow, and ensures that the response packet is sent to the first network device to ensure the first network regardless of whether the service plane of the network device fails.
  • the device can analyze and locate the fault in time.
  • the execution of the management operation and the acquisition of the information associated with the management operation in the response message are performed by the second network device, and are not performed by the NMS. Compared with the NMS, the types of management operations that can be performed inside the second network device are rich, so that the management flexibility can be further improved.
  • the method provided by the embodiment of the present invention has no dependence on the forwarding model of the service flow in the ad hoc network, and can be applied to various forwarding models, and has wide adaptability; and the administrator only needs to start the service flow network.
  • the management method is based on the security architecture of ANIMA ANI, and has high security, and the management method provides a general management framework based on service flow, which has good scalability.
  • FIG. 7 is a schematic structural diagram of a network device management apparatus according to an embodiment of the present invention.
  • the apparatus may be applied to a first network device in an ad hoc network.
  • the apparatus may include:
  • the obtaining module 201 can be used to implement the method shown in step 101 in the embodiment shown in FIG.
  • the first determining module 202 can be used to implement the method shown in step 102 in the embodiment shown in FIG.
  • the sending module 203 can be used to implement the method shown in step 104 in the embodiment shown in FIG.
  • the receiving module 204 is configured to receive a response message from the second network device, where the response message includes information related to the management operation, and the implementation process may refer to the method shown in step 107 in the embodiment shown in FIG. No longer.
  • control packet sent by the sending module 203 may further include: a task identifier and an identifier of a starting network device of the service flow, where the identifier of the initial network device is an identifier of the first network device, and the task identifier is An identifier assigned by the first network device to the management operation of the traffic flow.
  • control packet further includes: an identifier of the current network device, where the identifier of the current network device is used to indicate a network device that currently sends the control packet, where the identifier of the current network device is the first network device Logo.
  • control packet further includes: a type of information to be obtained;
  • the control message is used to instruct the second network device to perform a management operation according to the type of the management operation, and acquire information about the type indication of the information to be acquired.
  • control message further includes: control information, where the control information includes at least one of the first forwarding control information and the second forwarding control information;
  • the first forwarding control information is used to indicate that the second network device forwards the control packet or stops forwarding the control packet when the second network device does not support the management operation;
  • the second forwarding control information is used to indicate that the second network device forwards the control packet to one of the next hop network devices when the network device of the next hop of the second network device includes at least two, or The network device of each next hop of the second network device forwards the control message separately.
  • the response message sent by the second network device further includes an identifier of the second network device and an identifier of the network device of the last hop of the second network device.
  • FIG. 8 is another embodiment provided by the embodiment of the present invention. A schematic structural diagram of a management device of a network device. Referring to FIG. 8, the device may further include:
  • the second determining module 205 is configured to determine, according to the identifier of the second network device, the identifier of the network device of the last hop of the second network device, the network device included in the forwarding path of the service flow.
  • the embodiment of the present invention provides a management device for a network device, and after obtaining the management information of the service flow, the device may send a control packet to the second network device of the next hop, where the control packet includes The management information, the control message is used to instruct the second network device to perform the management operation, obtain the information associated with the management operation, and encapsulate the obtained information associated with the management operation in the response message and report the information to the The first network device, whereby the first network device can implement management of the second network device on the forwarding path. Since the management method can be triggered by the first network device, the dependency on the NMS is avoided, and the management flexibility is improved. Moreover, since the northbound interface is not required to be deployed in each network device, the management cost of the network device is effectively reduced.
  • FIG. 9 is a schematic structural diagram of another apparatus for managing a network device according to an embodiment of the present disclosure.
  • the device may be applied to a second network device in an ad hoc network.
  • the device may include:
  • the receiving module 301 is configured to receive a control packet from the first network device, where the control packet includes management information of the service flow, where the management information includes a type of the management operation and an identifier of the service flow, where the first network device is the service The starting network device of the stream.
  • the control packet includes management information of the service flow, where the management information includes a type of the management operation and an identifier of the service flow, where the first network device is the service The starting network device of the stream.
  • the processing module 302 can be used to implement the method shown in step 105 in the embodiment shown in FIG. 3 above.
  • the first sending module 303 can be used to implement the method shown in step 107 in the embodiment shown in FIG. 3 above.
  • control packet may further include: an identifier of the current network device, where the identifier of the current network device is used to indicate the network device that sends the control packet, and the network device that sends the control packet is in the service flow.
  • the network device located in the last hop of the second network device On the forwarding path, the network device located in the last hop of the second network device.
  • FIG. 10 is a schematic structural diagram of another apparatus for managing a network device according to an embodiment of the present invention. Referring to FIG. 10, the apparatus may further include:
  • the first determining module 304 is configured to determine, according to the identifier of the current network device, an identifier of the network device of the last hop of the second network device as an identifier of the current network device, that is, the current network device may be The identifier is determined to determine the identity of the network device of the last hop.
  • the response message may further include: an identifier of the second network device and an identifier of the network device of the last hop of the second network device.
  • the apparatus may further include:
  • the second determining module 305 can be used to implement the method shown in step 108 in the embodiment shown in FIG. 3 above.
  • the second sending module 306 can be used to implement the method shown in step 109 in the embodiment shown in FIG. 3 above.
  • the second sending module 306 can be configured to:
  • the updated control message is forwarded to the network device of the next hop of the second network device.
  • control packet may further include: a type of information to be obtained; the processing module 302 may be configured to:
  • control message further includes: control information, where the control information includes at least one of the first forwarding control information and the second forwarding control information;
  • the second sending module 306 can be configured to:
  • the control packet is forwarded to the network device of the next hop;
  • the second sending module 306 can be configured to:
  • the network device of the next hop of the second network device includes at least two, if the second forwarding control information is the first control information, determining a target network device from the network devices of the at least two next hops, And forwarding the control packet to the target network device; if the second forwarding control information is the second control information, forwarding the control packet to each network device of the next hop.
  • control packet further includes: a task identifier, and an identifier of the starting network device of the service flow, where
  • the identifier of the initial network device is an identifier of the first network device
  • the task identifier is an identifier that is allocated by the first network device for the management operation of the service flow;
  • the response packet further includes: the task identifier.
  • the embodiment of the present invention provides a management device for a network device, where the device can perform management indicated by the type of the management operation in the control packet after receiving the control packet from the first network device.
  • the operation, the information associated with the management operation is obtained, and the obtained information is encapsulated in the response message and reported to the first network device, so that the first network device can implement the second network device on the forwarding path.
  • Management since the management method can be triggered by the first network device, the dependency on the NMS is avoided, and the management flexibility is improved. Moreover, since the northbound interface is not required to be deployed in each network device, the management cost of the network device is effectively reduced.
  • the network device 500A may include: a main control board 510, and a switching network board 520 and at least one connected to the main control board 510, respectively.
  • Interface board For example, in the structure shown in FIG. 11, the network device is provided with two interface boards, an interface board 530 and an interface board 540. The two interface boards establish a connection through the switching network board 520.
  • the central control unit 510 is provided with a central processing unit 511.
  • the interface board 530 is provided with a central processing unit 531, a network processor 532, a physical interface card 533, and a forwarding entry storage 534.
  • the central processing unit 531 is connected to the forwarding entry storage 534 and the network processor 532, respectively, and forwards entries. Both memory 534 and physical interface card 533 are coupled to network processor 532.
  • the interface board 540 is provided with a central processing unit 541, a network processor 542, a physical interface card 543, and a forwarding entry storage 544.
  • the central processing unit 541 is connected to the forwarding entry storage 544 and the network processor 542, respectively, and forwards entries. Both memory 544 and physical interface card 543 are coupled to the network processor 542.
  • the function of the main control board 510 can refer to the related descriptions in step 102, step 103, and step 110 in the embodiment shown in FIG. 3; the interface board 530, the interface board 540, and the switch
  • the function of the stencil 520 reference may be made to the related descriptions in the step 101, the step 104, and the step 107 in the embodiment shown in FIG. 3, and details are not described herein again.
  • the function of the main control board 510 can refer to the related description in step 105, step 106, step 107, and step 108 in the embodiment shown in FIG. 3; the interface board 530 and the interface board
  • the functions of the 540 and the switching network board 520 reference may be made to the related descriptions in the step 104 and the step 107 in the embodiment shown in FIG. 3, and details are not described herein again.
  • FIG. 12 is a schematic structural diagram of another network device according to an embodiment of the present invention.
  • the network device 600 may include: a processor 610, a communication interface 620, and a memory 630.
  • the communication interface 620 and the memory 630 are respectively associated with the processor. 610 is connected.
  • communication interface 620 and memory 630 are coupled to processor 610 via bus 640.
  • the processor 610 can be a central processing unit (CPU), and the processor 610 includes one or more processing cores.
  • the processor 610 executes various functional applications and data processing by running a software program.
  • the communication interface 620 can be used for communication between the network device 600 and an external device, such as a display, a third-party device (for example, a storage device, a mobile terminal, etc.).
  • an external device such as a display, a third-party device (for example, a storage device, a mobile terminal, etc.).
  • the memory 630 stores a computer program executable on the processor 610, which may include, but is not limited to, random access memory (RAM), read only memory (ROM), and erasable programmable read only memory. (EPROM), flash memory, optical memory.
  • RAM random access memory
  • ROM read only memory
  • EPROM erasable programmable read only memory
  • flash memory optical memory.
  • This memory 630 is responsible for information storage, for example, the memory 630 is used to store software programs.
  • the network device 600 may further include an input/output (I/O) interface (not shown in FIG. 12).
  • the I/O interface is coupled to the processor 610, the communication interface 620, and the memory 630.
  • the I/O interface can be, for example, a universal serial bus (USB).
  • the processor 610 is configured to execute the computer program stored in the memory 630, and the processor 630 implements the computer program to implement the steps 101 to 104 in the embodiment shown in FIG. And the method shown in step 110.
  • the processor 610 is configured to execute a computer program stored in the memory 630, and the processor 630 implements the computer program to implement steps 105 to 109 in the embodiment shown in FIG. The method shown.
  • FIG. 13 is a schematic structural diagram of a network device management system according to an embodiment of the present disclosure.
  • the system may be applied to an ad hoc network.
  • the system may include: a first network device 01 and a second network device. 02.
  • the system may further include a downstream network device of the second network device 02.
  • the management system in the ad hoc network shown in FIG. 2 may include a first network device R1, a second network device R2, and downstream network devices R3 to R8 of the second network device R2.
  • the first network device 01 may include the device as shown in FIG. 7 or FIG. 8, or the first network device 01 may be the network device as shown in FIG. 11 or FIG. 12; the second network device 02 may include The device shown in FIG. 9 or FIG. 10, or the second network device 02 may be a network device as shown in FIG. 11 or FIG.
  • the embodiment of the present invention provides a computer readable storage medium, where the computer readable storage medium stores instructions, when the computer readable storage medium is run on a computer, causing the computer to execute the network device provided by the foregoing method embodiment Management method.
  • the embodiment of the present invention further provides a computer program product comprising instructions, when the computer program product is run on a computer, causing the computer to execute the management method of the network device provided by the foregoing method embodiment.

Abstract

本申请提供了一种网络设备的管理方法、装置及系统，属于通信领域，该方法包括：第一网络设备获取业务流的管理信息，该管理信息包括管理操作的类型和业务流的标识；根据该业务流的标识，确定该业务流的转发路径上的第二网络设备，该第二网络设备为第一网络设备的下一跳网络设备；向该第二网络设备发送控制报文，该控制报文包括管理信息，该控制报文用于指示第二网络设备执行管理操作，并获取与该管理操作关联的信息；接收来自该第二网络设备的响应报文，该响应报文包括该第二网络设备所获取到的与管理操作关联的信息。本申请提供的网络设备的管理方法的成本较低，灵活性较高。

Description

网络设备的管理方法、装置及系统
本申请要求于2018年03月30日提交中国专利局、申请号为201810277234.9、发明名称为“网络设备的管理方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，特别涉及一种网络设备的管理方法、装置及系统。
背景技术
自组织网络(Autonomic Networking)，是由多个网络设备组成的一种具有自配置、自优化、自修复和自我保护等功能的网络。
相关技术中，在完成自组织网络的部署后，通常会采用网络管理系统(Network Management System，NMS)来对网络设备进行管理和维护。具体的，该NMS需要先通过北向接口与自组织网络中的各个网络设备建立通信连接，然后，该NMS可以通过该北向接口指示各个网络设备执行相关的管理操作，并获取各个网络设备上报的相关信息，从而实现对各网络设备的管理。
但是，相关技术中的管理方法对NMS的依赖性较高，应用灵活性较差，并且由于该NMS以及各网络设备中均需部署北向接口，增加了该管理方法的成本。
发明内容
本申请提供了一种网络设备的管理方法、装置及系统，可以解决相关技术中的管理方法成本较高，应用灵活性较差的问题。技术方案如下：
第一方面，提供了一种网络设备的管理方法，可以应用于自组织网络中的第一网络设备，该方法可以包括：获取业务流的管理信息，该管理信息包括管理操作的类型和该业务流的标识，该第一网络设备为该业务流的起始网络设备；根据该业务流的标识，确定该业务流的转发路径上的第二网络设备，该第二网络设备为该第一网络设备的下一跳的网络设备；向该第二网络设备发送控制报文，该控制报文包括该管理信息，该第二网络设备可以将该控制报文逐跳转发至该转发路径上的各个网络设备，该控制报文用于指示该第二网络设备执行该管理操作，并获取与该管理操作关联的信息；之后，第一网络设备可以接收来自该第二网络设备的响应报文，该响应报文包括该第二网络设备获取到的与管理操作关联的信息。
本申请提供的网络设备的管理方法，可以通过业务流的起始网络设备实现对该业务流的转发路径上的第二网络设备的管理，该管理方法避免了对NMS的依赖，有效降低了网络设备的管理成本，提高了网络设备的管理灵活性。
可选的，该第一网络设备可以包括控制面和业务面；相应的，第一网络设备向第二网络设备发送控制报文，包括：通过业务面将控制报文发送至第二网络设备；
第二网络设备接收来自第二网络设备的响应报文，包括：通过控制面接收来自第二网络设备的响应报文。
由于该控制面是与业务面相独立的平面，且自组织网络中各个网络设备的控制面具有全连通性，因此无论第二网络设备的业务面是否发生故障时，都能保证响应报文的正常接收和发送，以确保该第一网络设备可以及时对第二网络设备的故障进行分析和定位。
可选的，该控制报文还可以包括：任务标识以及该业务流的起始网络设备的标识，该起始网络设备的标识即为第一网络设备的标识，该任务标识为第一网络设备为业务流的管 理操作分配的唯一标识。
第二网络设备上报的响应报文中也可以包括该任务标识，由此该第一网络设备可以根据响应报文中的任务标识，确定该响应报文所对应的业务流的管理操作并进行呈现，以便管理员可以准确获知针对不同业务流的管理操作所对应的信息。
可选的，该控制报文还可以包括：当前网络设备的标识，该当前网络设备的标识用于指示当前发送控制报文的网络设备，对于第一网络设备发送的控制报文而言，该当前网络设备的标识即为第一网络设备的标识。
接收到该控制报文的网络设备可以将该当前网络设备的标识确定为其上一跳的网络设备的标识，并携带在响应报文中上报至第一网络设备。进一步的，第一网络设备即可根据各个网络设备的上一跳的网络设备的标识，识别出该业务流的转发路径，以及该转发路径所包括的网络设备，即可以实现转发路径的可视化。
可选的，控制报文还可以包括：待获取信息的类型；
相应的，该控制报文可以指示第二网络设备根据管理操作的类型执行管理操作，并获取该待获取信息的类型指示的信息。
通过待获取信息的类型指示第二网络设备获取对应类型的信息，有效提高了管理的灵活性。
可选的，自组织网络中的每个网络设备中均可以部署有用于执行不同操作的多个功能模块，该控制报文中还可以包括：用于执行该管理操作的功能模块的对象名称；
相应的，该控制报文可以用于指示该第二网络设备通过该对象名称指示的功能模块执行该管理操作，并获取与该管理操作关联的信息。
针对不同的管理操作的类型，通过对象名称指示对应的功能模块执行该管理操作，并获取关联的信息，提高了对网络设备进行管理时的精准度。
可选的，控制报文还可以包括：控制信息，该控制信息可以包括第一转发控制信息和第二转发控制信息中的至少一种。
其中，该第一转发控制信息用于在该第二网络设备不支持该管理操作时，指示该第二网络设备转发该控制报文，或者停止转发该控制报文；
该第二转发控制信息用于在该第二网络设备的下一跳的网络设备包括至少两个时，指示该第二网络设备向其中一个下一跳的网络设备转发该控制报文，或者向该第二网络设备的每个下一跳的网络设备分别转发该控制报文。
通过在控制报文中封装该控制信息，可以实现对第二网络设备的灵活控制，提高了网络设备管理的灵活性。
可选的，该控制报文可以为通用自组织信令协议(Generic Autonomic Signaling Protocol，GRASP)请求消息，该GRASP请求消息可以包括：消息类型字段、任务标识字段以及管理对象字段；
该消息类型字段用于指示该控制报文的消息类型；
该任务标识字段用于携带该任务标识；
该管理对象字段用于携带该管理操作的类型、该业务流的标识、该起始网络设备的标识、该对象名称、该待获取信息的类型以及该控制信息中的至少一个。
进一步的，该管理对象字段可以包括：对象名称字段以及对象信息字段；
该对象名称字段用于携带该对象名称；
该对象信息字段包括：起始网络设备标识字段、当前网络设备标识字段、转发路径信息字段、控制信息字段、操作类型字段以及管理信息字段；
其中，该起始网络设备标识字段用于携带该起始网络设备的标识；该当前网络设备标识字段用于携带当前转发控制报文的网络设备的标识；该转发路径信息字段包括路径类型字段和关键字字段，该路径类型字段用于携带该转发路径的类型，该关键字字段用于携带该业务流的标识；该控制信息字段用于携带该控制信息；该操作类型字段用于携带该管理操作的类型；该管理信息字段用于携带该待获取信息的类型。
可选的，第二网络设备上报的响应报文还可以包括：第二网络设备的标识以及该第二网络设备的上一跳的网络设备的标识；该方法还包括：
根据该第二网络设备的标识，以及该第二网络设备的上一跳的网络设备的标识(也即是该第一网络设备的标识)，第一网络设备可以确定该业务流的转发路径所包括的网络设备，从而实现对该业务流的转发路径的识别。
可选的，该业务流的转发路径上还可以包括位于该第二网络设备下游的下游网络设备，该方法还可以包括：
接收第二网络设备转发的来自下游网络设备的响应报文，来自该下游网络设备的响应报文可以包括：该下游网络设备的标识以及该下游网络设备的上一跳的网络设备的标识；相应的，第一网络设备确定该业务流的转发路径所包括的网络设备的过程可以包括：
根据该第二网络设备的标识，该第二网络设备的上一跳的网络设备的标识，该下游网络设备的标识，以及该下游网络设备的上一跳的网络设备的标识，确定该业务流的转发路径，以及该转发路径所包括的网络设备，由此可以实现转发路径的可视化，从而可以提高后续对该转发路径上的网络设备进行管理时的灵活性。
可选的，第一网络设备在向该第二网络设备发送封装有该管理信息的控制报文之前，该方法还包括：
根据该业务流的标识，确定该业务流的转发模型；
采用该转发模型对该管理信息进行封装，得到该控制报文。
本申请提供的管理方法，第一网络设备可以采用与业务报文相同的转发模型封装控制报文，并可以采用带外(out-of-band)的方式转发控制报文，可以避免对实际业务流的业务报文的影响。
第二方面，提供了一种网络设备的管理方法，可以应用于自组织网络中的第二网络设备，该方法可以包括：接收来自第一网络设备的控制报文，该控制报文包括业务流的管理信息，该管理信息包括管理操作的类型以及该业务流的标识，该第一网络设备为该业务流的起始网络设备；根据该管理操作的类型执行管理操作，并获取与该管理操作关联的信息；向该第一网络设备发送响应报文，该响应报文包括该与该管理操作关联的信息。
本申请提供的网络设备的管理方法，第二网络设备可以在第一网络设备发送的控制报文的指示下执行管理操作，并将获取到的与管理操作关联的信息通过响应报文上报至该第一网络设备，由此该第一网络设备即可实现对转发路径上第二网络设备的管理，该方法避免了对NMS的依赖，降低了网络设备的管理成本，提高了网络设备的管理灵活性。
可选的，该控制报文还可以包括：当前网络设备的标识，该当前网络设备的标识用于指示发送该控制报文的网络设备，该发送该控制报文的网络设备为在该业务流的转发路径 上，位于该第二网络设备的上一跳的网络设备；
在接收来自第一网络设备的控制报文之后，该方法还可以包括：
根据该当前网络设备的标识，确定该第二网络设备的上一跳的网络设备的标识为当前网络设备的标识，也即是，可以将该当前网络设备的标识确定为确定该上一跳的网络设备的标识；
相应地，该响应报文还包括：该第二网络设备的标识以及该第二网络设备的上一跳的网络设备的标识。
第一网络设备接收到该响应报文后，可以根据第二网络设备的标识及其上一跳的网络设备的标识，识别出该业务流的转发路径，以及该转发路径所包括的网络设备，即可以实现转发路径的可视化。
可选的，该第二网络设备可以包括控制面和业务面；相应的，接收来自第一网络设备的控制报文的过程可以包括：通过该业务面接收来自第一网络设备的控制报文，并将该控制报文上送至该控制面；
根据该管理操作的类型执行管理操作，并获取与该管理操作关联的信息的过程可以包括：通过该控制面执行该管理操作，并获取与该管理操作关联的信息；
向该第一网络设备发送响应报文的过程可以包括：通过该控制面将该响应报文发送至该第一网络设备。
由于该控制面是与业务面相独立的平面，且自组织网络中各个网络设备的控制面具有全连通性，因此无论第二网络设备的业务面是否发生故障时，都能保证响应报文的正常接收和发送，以确保该第一网络设备可以及时对第二网络设备的故障进行分析和定位。
可选的，该方法还可以包括：
根据该业务流的标识，确定在该业务流的转发路径上，位于该第二网络设备的下一跳的网络设备；
将该控制报文转发至该第二网络设备的下一跳的网络设备。
第二网络设备将控制报文转发至下一跳的网络设备，可以实现控制报文在该转发路径上的逐跳转发，进而可以使得转发路径上的各个网络设备均能接收到该控制报文，并执行相应的管理操作，由此该第一网络设备可以实现对业务流的转发路径上的各个网络设备的管理。
可选的，第二网络设备将该控制报文转发至该第二网络设备的下一跳的网络设备的过程可以包括：
采用该第二网络设备的标识更新该控制报文中的该当前网络设备的标识；
将更新后的该控制报文转发至该第二网络设备的下一跳的网络设备。
第二网络设备对控制报文中的当前网络设备的标识进行更新后再转发，可以保证下一跳的网络设备能够基于控制报文中的当前网络设备的标识，准确确定其上一跳的网络设备的标识。
可选的，该控制报文还可以包括：待获取信息的类型；相应的，该获取与该管理操作关联的信息可以包括：
获取该待获取信息的类型指示的信息。
通过待获取信息的类型指示第二网络设备获取对应类型的信息，有效提高了管理的灵活性。
可选的，该控制报文还可以包括：控制信息，该控制信息包括第一转发控制信息和第二转发控制信息中的至少一种；
当该控制信息包括该第一转发控制信息时，将该控制报文转发至该第二网络设备的下一跳的网络设备的过程可以包括：
在该第二网络设备不支持该管理操作时，若该第一转发控制信息为预设控制信息，将该控制报文转发至该下一跳的网络设备；
当该控制信息包括该第二转发控制信息时，将该控制报文转发至该第二网络设备的下一跳的网络设备的过程可以包括：
在该第二网络设备的下一跳的网络设备包括至少两个时，若该第二转发控制信息为第一控制信息，从至少两个该下一跳的网络设备中确定一个目标网络设备，并将该控制报文转发至该目标网络设备；若该第二转发控制信息为第二控制信息，将该控制报文分别转发至每个该下一跳的网络设备。
通过在控制报文中封装的控制信息控制第二网络设备转发控制报文的方式，可以实现对第二网络设备的灵活控制，提高了网络设备管理的灵活性。
可选的，该控制报文还可以包括：任务标识以及该业务流的起始网络设备的标识，
该起始网络设备的标识为该第一网络设备的标识，该任务标识为该第一网络设备为该业务流的该管理操作分配的标识；该响应报文还可以包括：该任务标识。
响应报文中包括该任务标识，由此该第一网络设备可以根据响应报文中的任务标识，确定该响应报文所对应的业务流的管理操作并进行呈现，以便管理员可以准确获知针对不同业务流的管理操作所对应的信息。
可选的，该响应报文可以为GRASP响应消息，该GRASP响应消息可以包括：消息类型字段、任务标识字段和管理对象字段；
该消息类型字段用于指示该响应报文的消息类型；
该任务标识字段用于携带该任务标识；
该管理对象字段用于携带该第二网络设备获取的与该管理操作关联的信息。
进一步的，该管理对象字段可以包括：对象名称字段以及对象信息字段；
该对象名称字段用于携带该对象名称；
该对象信息字段包括：起始网络设备标识字段、上游网络设备标识字段、当前网络设备标识字段、角色标识字段、转发路径信息字段、管理信息字段和信息字段；
其中，该起始网络设备标识字段用于携带该业务流的起始网络设备的标识；该上游网络设备标识字段用于携带该第二网络设备的上一跳的网络设备的标识；该当前网络设备标识字段用于携带当前网络设备的标识，即该第二网络设备的标识；该角色标识字段用于携带该第二网络设备在该业务流的转发路径上的角色；该转发路径信息字段包括路径类型字段、路径状态字段以及关键字字段，该路径类型字段用于携带该转发路径的类型，该路径状态字段用于携带该转发路径的路径状态，该关键字字段用于携带该业务流的标识；该管理信息字段用于携带该待获取信息的类型，该信息字段用于携带该第二网络设备获取的与该管理操作关联的信息。
第三方面，提供了一种网络设备的管理装置，应用于自组织网络中的第一网络设备，该装置可以包括至少一个模块，该至少一个模块可以用于实现上述第一方面所提供的网络 设备的管理方法。
第四方面，提供了一种网络设备的管理装置，应用于自组织网络中的第二网络设备，该装置可以包括至少一个模块，该至少一个模块可以用于实现上述第二方面所提供的网络设备的管理方法。
第五方面，提供了一种网络设备，该网络设备可以包括：存储器，处理器及存储在存储器上并可在该处理器上运行的计算机程序，该处理器执行该计算机程序时实现上述第一方面所提供的网络设备的管理方法，或者实现上述第二方面所提供的网络设备的管理方法。
第六方面，提供了一种网络设备，该网络设备可以包括：主控板，以及分别与该主控板连接的交换网板和至少一个接口板，该主控板、该至少一个接口板以及该交换网板可以用于实现上述第一方面所提供的网络设备的管理方法，或者可以用于实现上述第二方面所提供的网络设备的管理方法。
第七方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该计算机可读存储介质在计算机上运行时，使得计算机执行上述第一方面所提供的网络设备的管理方法，或者执行上述第二方面所提供的网络设备的管理方法。
第八方面，提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面所提供的网络设备的管理方法，或者执行上述第二方面所提供的网络设备的管理方法。
第九方面，提供了一种网络设备的管理系统，应用于自组织网络，该管理系统可以包括：第一网络设备以及第二网络设备；
该第一网络设备可以包括上述第三方面所提供的网络设备的管理装置，或者可以为上述第五方面或第六方面所提供的网络设备；
该第二网络设备可以包括上述第四方面所提供的网络设备的管理装置，或者可以为上述第五方面或第六方面所提供的网络设备。
上述本发明实施例第三方面到第九方面所获得的技术效果与第一方面和第二方面中对应的技术手段所获得的技术效果近似，在这里不再赘述。
综上所述，本发明实施例提供了一种网络设备的管理方法、装置及系统，自组织网络中的第一网络设备获取到业务流的管理信息后，可以向下一跳的第二网络设备发送控制报文，该控制报文包括该管理信息，该控制报文用于指示该第二网络设备执行该管理操作，获取与该管理操作关联的信息，以及将获取到的与管理操作关联的信息封装在响应报文中并上报至该第一网络设备，由此该第一网络设备即可实现对转发路径上第二网络设备的管理。由于该管理方法可以由第一网络设备触发实现，避免了对NMS的依赖，提高了管理的灵活性。并且由于各网络设备中也无需再部署北向接口，因此有效降低了网络设备的管理 成本。
附图说明
图1是本发明实施例提供的一种采用ANIMA的参考模型的自组织节点的架构图；
图2是本发明实施例提供的一种自组织网络的结构示意图；
图3是本发明实施例提供的一种网络设备的管理方法的流程图；
图4是本发明实施例提供的一种网络设备的管理方法的架构图；
图5是本发明实施例提供的一种控制报文的结构示意图；
图6是本发明实施例提供的一种响应报文的结构示意图；
图7是本发明实施例提供的一种网络设备的管理装置的结构示意图；
图8是本发明实施例提供的另一种网络设备的管理装置的结构示意图；
图9是本发明实施例提供的又一种网络设备的管理装置的结构示意图；
图10是本发明实施例提供的再一种网络设备的管理装置的结构示意图；
图11是本发明实施例提供的一种网络设备的结构示意图；
图12是本发明实施例提供的另一种网络设备的结构示意图；
图13是本发明实施例提供的一种网络设备的管理系统的结构示意图。
具体实施方式
国际互联网工程任务组(The Internet Engineering Task Force，IETF)在编号为7575的征求修正意见书(Request For Comments，RFC)中对自组织网络(也可以称为自主网络)的概念，以及自组织网络的标准化解决方案(Autonomic Networking Integrated Model and Approach，ANIMA)的设计目标进行了定义，并初步定义了ANIMA的参考模型。
参考图1，采用ANIMA的参考模型的网络设备，也称为自组织节点(Autonomic Node)可以划分为自组织网络基础设施(Autonomic Networking Infrastructure，ANI)和自组织服务代理(Autonomic Service Agent，ASA)模块两部分。其中，ANI为ANIMA的基础框架平台，能够为自组织节点提供一个独立且稳定的管理平面，该ANI主要包括远程安全启动密钥基础设施(Bootstrapping Remote Secure Key Infrastructures，BRSKI)、自组织控制平面(Autonomic Control Plane，ACP)以及GRASP模块三个核心组件。其中ACP能够为新加入ANIMA域的自组织节点自动分配地址以及与相邻的自组织节点建立逐跳(hop-by-hop)的安全隧道，从而可以实现ANIMA域内所有自组织节点的路由全连通。ASA为自组织节点内用于实现自组织功能的功能模块(也可以称为业务实例)，该自组织功能可以包括查询功能和订阅功能等。每个自组织节点内可以部署多个用于实现不同功能的ASA。例如图1所示的自组织节点中部署有ASA 1至ASA 3共3个ASA。
自组织节点获取到自组织网络的控制器下发的域证书后，即可加入该自组织网络(也称为ANIMA域)，该加入ANIMA域的自组织节点也可以称为ACP Node。ACP  Node可以包括控制面和业务面(Data plane)。
其中，控制面也称为ACP虚拟路由转发(Virtual Routing Forwarding，VRF)模块，该ACP VRF模块可以理解为自组织网络的虚拟路由实例，其包含了独立的路由协议、接入接口以及路由表，因此可以相当于一个独立的虚拟路由器。该控制面包括虚拟带外通道(Virtual-out-of-band channel，VOOB)，能够用于实现网络管理任务。业务面为常规的业务平面，可以用于实现业务报文的转发。
由于该控制面(即ACP VRF模块)具有独立的转发面，其连通性对业务面无依赖。无论业务面是否具有路由以及采用何种转发模型，都不影响ACP VRF的连通性，其隔离性较高。并且，只要ACP Node位于ANIMA域中，ACP VRF就会一直存在，不受业务面的配置和运行状态影响，因此其稳定性较高；此外，该ACP VRF还可以通过低功耗有损网络路由协议(Routing Protocol for LLN，RPL)实现ANIMA域内的任意两个ACP Node的数据交互，即该ACP VRF具有ANIMA域内的全连通性。进一步的，该ACP VRF采用GRASP作为统一的通信协议，具有丰富的基础通信能力，其可扩展性较高，其能够携带的数据类型较为丰富。更进一步的，由于ACP Node之间可以在经过BRSKI的安全启动(Secure bootstrapping)后，通过ACP安全隧道进行通信，因此ACP Node之间的通信安全性较高。并且，在同一个ACP Node内部，ACP VRF和业务面之间可以安全地访问对方的所有数据。
图2是本发明实施例提供的一种自组织网络的结构示意图，如图2所示，该自组织网络可以包括多个网络设备，每个网络设备即为一个自组织节点。该每个网络设备可以是终端主机(例如服务器或者计算机终端等)，也可以是中间转发设备(例如路由器或交换机等)等，本发明实施例对该网络设备的类型不做限定。该自组织网络中的每个网络设备为获取到ANIMA域的域证书，且完成BRSKI启动和ACP安全隧道建立的设备，即该每个网络设备已经成功加入ANIMA域。示例的，如图2所示，该自组织网络中可以包括R1至R8共8个网络设备，而网络设备C1和C2则为ANIMA域的域外设备。通过本发明实施例提供的管理方法，该自组织网络中每个业务流的起始网络设备均可对该业务流的转发路径上的其他网络设备进行管理，有效提高了网络设备管理的灵活性。
图3是本发明实施例提供的一种网络设备的管理方法的流程图，该方法可以应用于图2所示的自组织网络中，参考图3，该方法可以包括：
步骤101、第一网络设备获取业务流的管理信息。
该第一网络设备为该业务流的起始(Ingress)网络设备，也可以称为Ingress Node。在本发明实施例中，当需要对某个业务流的转发路径上的网络设备进行管理时，管理员可以确定该业务流的起始网络设备(即第一网络设备)，并可以通过NMS向该第一网络设备发送管理信息；或者，管理员也可以采用远程终端通过该第一网络设备所提供的管理维护(Operation and maintenance，OM)接口远程登录至该第一网络设备； 之后，管理员可以通过命令行的方式向该第一网络设备输入该业务流的管理信息。该管理信息至少可以包括管理操作的类型以及业务流的标识。
该管理操作的类型可以包括查询(query)操作、订阅(subscribe)操作、取消订阅(unsubscribe)操作和重新订阅(re-subscribe)操作中的至少一种。其中，查询操作用于查询转发路径上的网络设备的相关信息，订阅操作用于订阅转发路径上的网络设备的相关信息，取消订阅操作用于取消对网络设备的相关信息的订阅，重新订阅操作用于在第一网络设备检测到业务流的转发路径的状态发生变化(例如某台网络设备退出ANIMA域)时，重新获取该转发路径上的网络设备的相关信息。上述网络设备的相关信息可以包括网络设备的转发表项、下游路径的路径状态以及网络设备的状态等，本发明实施例对此不做限定。
该业务流的标识可以为能够唯一标识该业务流的标识。根据该自组织网络的类型的不同，该业务流的标识的类型也可以不同。例如，当该自组织网络属于公用网络(即公网)时，该业务流的标识可以为该业务流的目的互联网协议(Internet Protocol，IP)地址；当该自组织网络属于虚拟专用网络(Virtual Private Network，VPN)，即私网时，该业务流的标识可以包括该业务流的目的IP地址以及VPN实例标识。
示例的，假设在图2所示的自组织网络中，某个业务流的转发路径如图2中的虚线箭头所示，从图2可以看出，该业务流的起始网络设备为R1，目标(Target)网络设备为R8，转发(Transit)网络设备为R2至R7。其中目标网络设备是指位于该转发路径终点的网络设备，转发网络设备是指该转发路径上用于连接起始网络设备和目标网络设备的网络设备。当管理员需要对该转发路径上的设备进行管理时，可以通过第一网络设备R1提供的OM接口远程登录该第一网络设备R1，并以命令行的方式向该第一网络设备R1输入该业务流的管理信息。
需要说明的是，在本发明实施例中，该第一网络设备R1获取到的管理信息除了可以包括管理操作的类型，以及业务流的标识之外，还可以包括用于控制操作流程的第一控制信息，以及用于指示各网络设备的反馈信息的第二控制信息。其中，该第一控制信息可以包括：控制报文的发送个数、控制报文的发送间隔、操作超时时间以及控制报文中的部分封装参数(例如控制报文的封装头中携带的参数)等；该第二控制信息可以包括：反馈信息的详细程度控制信息、各网络设备反馈的响应报文所需携带的信息的类型的控制信息以及用于指示是否携带错误(Error)信息或日志(Logging)信息的控制信息等。该管理信息中所包括的信息内容可以根据实际需求进行灵活设置，本发明实施例对此不做限定。
步骤102、第一网络设备根据该业务流的标识，确定该业务流的转发路径上的第二网络设备。
该第二网络设备为该业务流的转发路径上，位于该第一网络设备的下一跳的网络设备。在本发明实施例中，第一网络设备在获取到管理信息后，可以根据该管理信息中业务流的标识，从本地存储的转发数据库(Forwarding DataBase，FDB)中获取转发表项，并基于该转发表项确定该业务流的转发路径上的第二网络设备。
图4是本发明实施例提供的一种网络设备的管理方法的架构图，参考图4，第一网络设备在获取到管理信息后，其ASA可以根据该管理信息中业务流的标识，在业务面的FDB中查询该业务流的路径信息，该路径信息可以包括下一跳的网络设备的标识，或者还可以包括出接口(即目标网络设备)的标识，以及标记交换路径(Label Switching Path，LSP)标签栈等信息。
示例的，对于图2所示的自组织网络，第一网络设备R1基于业务流的标识，可以从业务面的FDB中查询得到该业务流的转发路径上的第二网络设备为网络设备R2。
步骤103、第一网络设备对该管理信息进行封装，得到控制报文。
在本发明实施例中，该第一网络设备可以按照预设的转发模型对该管理信息进行封装，得到控制报文。可选的，在上述步骤102中，第一网络设备根据该业务流的标识查询FDB以确定第二网络设备时，还可以同时基于该业务流的标识，确定该业务流的转发模型，该转发模型一般可以包括：IP模型或多协议标签交换(Multi-Protocol Label Switching，MPLS)模型等，其中IP模型可以包括第四版互联网协议(IPv4)模型和第六版互联网协议(IPv6)模型等。进一步的，该第一网络设备即可根据确定的转发模型，对管理信息进行封装，得到控制报文。该控制报文可以被逐跳转发至业务流的转发路径上的各个网络设备，接收到该控制报文的网络设备需执行该控制报文所指示的管理操作，并通过响应报文向第一网络设备上报与管理操作关联的信息，由此该第一网络设备即可实现对转发路径上各个网络设备的管理。
可选的，在本发明实施例中，该控制报文中还可以包括任务标识以及业务流的起始网络设备的标识，该起始网络设备的标识即第一网络设备的标识，该任务标识可以是第一网络设备为业务流的管理操作所分配的唯一标识。例如，该任务标识可以为第一网络设备为该业务流的管理操作随机分配的唯一标识。
进一步的，该控制报文还可以包括：当前网络设备的标识、待获取信息的类型、用于执行该管理操作的功能模块的对象名称以及控制信息中的至少一种。
其中，当前网络设备的标识用于指示当前发送控制报文的网络设备。相应的，对于该第一网络设备发送的控制报文，该当前网络设备的标识也即该第一网络设备的标识。该待获取信息的类型可以指示第二网络设备所需获取的与该管理操作关联的信息的类型。该对象名称可以指示第二网络设备通过该对象名称指示的功能模块执行管理操作。该控制信息可以包括第一转发控制信息和第二转发控制信息中的至少一种；该第一转发控制信息用于在第二网络设备不支持管理操作(例如第二网络设备中未部署该对象名称指示的功能模块)时，指示第二网络设备继续转发该控制报文，或者停止转发该控制报文；该第二转发控制信息用于在第二网络设备的下一跳的网络设备包括至少两个时，指示第二网络设备向其中一个下一跳的网络设备转发该控制报文，或者向第二网络设备的每个下一跳的网络设备分别转发该控制报文。
图5是本发明实施例提供的一种控制报文的结构示意图，如图5所示，该控制报文可以为GRASP请求消息，该GRASP请求消息可以包括传输封装头(Transport header)、用户数据报协议(User Datagram Protocol，UDP)封装头(header)以及GRASP 包(Packet)。该UDP header和GRASP Packet即为该GRASP请求消息的有效载荷(payload)。
其中，根据转发模型的不同，该GRASP请求消息可以采用不同的传输封装头。例如，当转发模型为原生(Native)IP模型时，该传输封装头可以采用IPv4封装头或IPv6封装头；当转发模型为IP隧道(Tunnel)模型时，该传输封装头可以采用隧道封装头(Tunnel Header)，该隧道封装头可以包括IPinIP(在IP内封装IP)封装头、通用路由封装(Generic Routing Encapsulation，GRE)封装头，或者虚拟可扩展局域网(Virtual Extensible LAN，VXLAN)Tunnel封装头等；当该转发模型为MPLS模型时，该传输封装头可以采用MPLS封装头，MPLS封装头可以包括MPLS标签栈以及IP封装头。
该UDP header可以包括：DestPort＝GRASP_LISTEN_PORT，SrcPort＝<随机分配>；其中，DestPort为UDP目的端口号，GRASP_LISTEN_PORT为GRASP模块的监听端口号，该监听端口号为知名端口号；SrcPort是指源端口号，该源端口号可以由第一网络设备随机分配。从该UDP header可以看出，该UDP目的端口号即为GRASP模块的监听端口号，因此接收到该控制报文的第二网络设备可以根据该UDP目的端口号，将该控制报文分发至GRASP模块进行处理。
GRASP Packet可以包括：[message-type，session-id，objective]。
其中，message-type为消息类型字段，用于指示该控制报文的消息类型，例如，该控制报文可以使用GRASP的同步(Synchronization)机制，即该控制报文可以为GRASP同步请求消息，相应的，该message-type可以设置为M_REQ_SYN。
session-id为任务标识字段，用于携带第一网络设备为业务流的管理操作所分配的任务标识。第二网络设备接收到控制报文后上报的响应报文也包括该任务标识，第一网络设备可以根据该任务标识对接收到的响应报文进行匹配，以确定每个响应报文所对应的业务流的管理操作。
objective为管理对象字段，该管理对象字段用于携带管理操作的类型、业务流的标识、起始网络设备的标识、对象名称、待获取信息的类型以及控制信息中的至少一个。例如，该管理对象字段的定义可以为：objective＝[objective-name，objective-flags，loop-count，objective-value]。
其中，objective-name为对象名称字段，该对象名称字段用于携带能够唯一标识第二网络设备中用于执行该管理操作的功能模块(即管理对象)的对象名称。该对象名称可以由UTF-8(一种针对统一码(Unicode)的可变长度字符编码)字符构成，本发明实施例对该对象名称的字符长度不做限定。此外，该对象名称可以分为标准名称和私有名称两种类型，其中标准名称由互联网数字分配机构(The Internet Assigned Numbers Authority，IANA)统一分配，私有名称可以由网络设备中的ASA自行定义，并且该私有名称中一般至少包含一个字符“:”。例如网络设备中能够实现订阅功能的ASA的私有名称可以为“xxxx.com:PathStatusSubcribe”。
objective-flags为对象标志字段，用来指定GRASP预定义的操作类型，例如可以设置为F_SYNCH。
loop-count为循环计数字段，该字段可以用于避免GRASP模块执行发现(Discovery)操作、协商(Negotiation)操作或者泛洪(Flood)操作等操作时出现无限循环。
objective-value为对象信息字段，该对象信息字段的定义可以为：objective-value＝[ingress,current,path-info,control-flags,[op-type,timeout],[*[type,params]]]。
其中，ingress为起始网络设备标识字段，该字段用于携带业务流的起始网络设备(即第一网络设备)的标识，该字段的定义可以为：ingress＝[ingress-acp-ula,ingress-global-addr]；也即是，该起始网络设备的标识可以包括起始网络设备的ACP的唯一本地地址(unique local address，ULA)以及该起始网络设备的全局地址，该全局地址即为该起始网络设备业务面的管理地址。
current为当前网络设备标识字段，该字段用于携带当前发送控制报文的网络设备的标识，该字段的定义可以为：current＝[current-acp-ula,current-global-addr]，即该当前网络设备的标识可以包括该当前网络设备的ACP ULA及当前网络设备的业务面的管理地址。
示例的，假设该第一网络设备为图2所示的网络设备R1，则在该第一网络设备R1所发送的控制报文中，该ingress字段和current字段所携带的均为该第一网络设备R1的标识。
path-info为转发路径信息字段，该字段用于携带业务流的转发路径的相关信息，该字段的定义可以为：path-info＝[path-type,path-status,path-keys]。其中，path-type为路径类型字段，用于携带转发路径的类型，该转发路径的类型根据转发模型的不同而不同，一般可以包括IPv4、IPv6、IPv4-VRF、IPv6-VRF或MPLS等；path-keys为关键字字段，用于携带该业务流的标识，该关键字字段所携带的业务流的标识的类型因转发路径的类型而异。例如，对于类型为IPv4的转发路径，该业务流的标识可以为转发路径的目的IPv4地址；对于类型为IPv4-VRF的转发路径，该业务流的标识可以为转发路径的目的IPv4地址以及VRF名称。path-status为路径状态字段，该字段用于携带转发路径的状态。在控制报文中，该path-status字段可以为预设的初始值；第二网络设备接收到该控制报文后，可以采用获取到的路径状态更新该path-status字段。其中，路径状态一般可以包括：连续状态(continued)、断开状态(broken)以及终止状态(terminated)等。
例如，当接收到控制报文的第二网络设备不为目标网络设备，且查询到下一跳的网络设备时，可以确定路径状态为连续状态；当接收到控制报文的第二网络设备不为目标网络设备，且未查询到下一跳的网络设备时，可以确定路径状态为断开状态；当接收到控制报文的第二网络设备为目标网络设备时，可以确定路径状态为终止状态。此外，该路径状态还可以包括：子路径(sub-branch)状态，该子路径状态可以用于指示第二网络设备的下游路径是否包括多个子路径(即是否存在多个下一跳的网络设备)；相应的，当存在多个子路径时，该路径状态中还可以包括每个子路径的路径状态。
control-flags为控制信息字段，该控制信息字段可以用于携带控制信息，该控制信息可以包括第一转发控制信息(CF_TRANSIT)和第二转发控制信息 (CF_ALL_SUBPATH)中的至少一种。其中，该第一转发控制信息用于在该第二网络设备不支持该管理操作时，指示该第二网络设备继续转发该控制报文，或者停止转发该控制报文；该第二转发控制信息用于在该第二网络设备的下一跳的网络设备包括至少两个时，指示该第二网络设备向其中一个下一跳的网络设备转发该控制报文，或者向该第二网络设备的每个下一跳的网络设备分别转发该控制报文。
op-type为操作类型字段，该字段用于携带管理操作的类型，该管理操作的类型可以包括查询操作、订阅操作、取消订阅操作和重新订阅操作等。在本发明实施例中，为了为保证业务安全，对于第二网络设备中的业务数据，该第一网络设备只能进行只读(read-only)操作。
timeout为超时时间字段，该字段可以用于为订阅操作配置超时时间，避免该订阅操作无限期占用相关资源。示例的，该字段为X时，可以表示在X时长后，该订阅操作失效，该字段为0时可以表示无超时限制。
type为管理信息字段，该字段用于携带待获取信息的类型；params为信息字段，该字段用于携带与管理操作关联的信息，也即是该待获取信息的类型指示的信息。*[type,params]表示该type和params字段可以包括多组，每组可以记录一种待获取信息的类型，以及该类型指示的信息。
在本发明实施例中，管理员可以根据需求，自行定义与该objective-name对应的type字段。例如，若需要识别该业务流的转发路径，则第一网络设备可以查询转发路径上每个网络设备的上一跳的网络设备，相应的，该type字段携带的待获取信息的类型可以包括：控制报文的输入接口名称，或者控制报文的输入接口的IP地址等。
需要说明的是，该控制报文中有效载荷的各个字段可以根据实际需求选取，例如，对于查询操作，可以无需设置该timeout字段；或者，该控制报文中也可以无需设置该control-flags字段，相应的，第二网络设备在接收到控制报文后，可以直接向每一个下一跳的网络设备转发该控制报文。本发明实施例对控制报文中封装的字段的类型不做限定。
还需要说明的是，由于每个网络设备接收到控制报文后，除了正常转发该控制报文之外，还需要获取该控制报文中封装的管理信息，以执行管理操作。因此第一网络设备在封装控制报文时，还可以基于转发模型，确定相应的逐跳上送机制，并在控制报文中封装用于指示接收到该控制报文的网络设备逐跳上送控制报文的相关字段，根据转发模型的不同，该相关字段也有所不同。例如该相关字段可以为生存时间值(Time To Live，TTL)、跳数限制(Hop-Limit)、路由告警(Router Alert)、标签告警(Label Alert)或者控制字(Control Word)等。其中，逐跳上送是指每个网络设备在通过业务面接收到控制报文后，将该控制报文上送至控制面进行处理，再由其控制面转发至下一跳的网络设备。
步骤104、第一网络设备向第二网络设备发送该控制报文。
进一步的，该第一网络设备可以通过业务面将控制报文发送至第二网络设备，该第二网络设备还可以将该控制报文转发至位于其下游的下游网络设备，以便可以将该 控制报文逐跳转发至该转发路径上的各个网络设备。
示例的，对于图2所示的自组织网络，第一网络设备R1可以通过其业务面将控制报文发送至第二网络设备R2。
由于在本发明实施例中，该控制报文采用了与业务报文相同的转发模型进行封装，并在理论上基于与业务报文相同的转发路径进行转发，实现了对业务报文的模拟；并且由于采用带外(out-of-band)的方式转发控制报文，因此不会对实际业务流的业务报文的转发造成影响。并且由于不依赖于业务报文，该控制报文生成和转发时的灵活性更高。
步骤105、第二网络设备根据管理操作的类型，执行管理操作，并获取与该管理操作关联的信息。
第二网络设备接收到来自第一网络设备的控制报文后，可以获取该控制报文中封装的管理信息，基于该管理信息中指定的管理操作的类型，执行管理操作，并获取与该管理操作关联的信息。
在本发明实施例中，由于自组织网络中的每个网络设备中均部署有用于执行不同操作的多个功能模块(即ASA)，且该第一网络设备发送的控制报文中还可以包括用于执行该管理操作的功能模块的对象名称(即objective-name)以及待获取信息的类型，因此第二网络设备在接收到控制报文后，可以通过该对象名称所指示的功能模块，执行该管理操作。相应的，在获取与该管理操作关联的信息时，第二网络设备可以获取该待获取信息的类型指示的信息。
示例的，参考图4，该第二网络设备R2可以通过业务面接收到第一网络设备发送的控制报文，并可以将该控制报文上送至控制面，例如可以上送至运行在控制面内的主机协议栈。该主机协议栈可以根据控制报文中的UDP目的端口号，将控制报文分发给GRASP模块，GRASP模块再根据控制报文中的objective-name，将控制报文进一步分发给该objective-name所指示的ASA进行处理。例如，若该管理操作为查询操作，则该objective-name所指示的ASA即为用于实现查询功能的ASA。该用于实现查询功能的ASA接收到GRASP模块分发的控制报文后，可以执行该查询操作，并获取该待获取信息的类型所指示的信息。
此外，若第二网络设备不支持该管理操作，例如该第二网络设备中未部署对象名称指示的功能模块，则该第二网络设备可以无需执行该管理操作。并且，第二网络设备还可以根据控制报文中所封装的第一转发控制信息，确定是否继续转发该控制报文。示例的，当该控制报文中的第一转发控制信息为预设控制信息(例如1)时，第二网络设备可以将该控制报文继续转发至下一跳的网络设备，即第二网络设备可以执行步骤108和步骤109；当该控制报文中的第一转发控制信息不为预设控制信息(例如该第一转发控制信息为0)时，第二网络设备可以停止转发该控制报文，并可以丢弃该控制报文，即第二网络设备无需再执行步骤108和步骤109。
步骤106、第二网络设备对获取到的与管理操作关联的信息进行封装，得到响应报文。
第二网络设备可以根据预设的封装模型，对获取到与管理操作关联的信息进行封装，得到响应报文。此外，该响应报文中还可以包括该第二网络设备的标识以及该第二网络设备的上一跳的网络设备的标识(也即是该第一网络设备的标识)，以便于第一网络设备获取到各个网络设备上报的响应报文后，可以根据转发路径上各个网络设备的标识，以及各个网络设备的上一跳的网络设备的标识，识别该业务流的转发路径，以及该转发路径所包括的网络设备，
由于第二网络设备所接收到的控制报文中还包括当前网络设备的标识，因此该第二网络设备可以直接将该控制报文中的当前网络设备的标识确定为上一跳的网络设备的标识。例如，第二网络设备可以将控制报文中current字段携带的标识确定为其上一跳的网络设备的标识，对于第二网络设备而言，其上一跳的网络设备的标识即第一网络设备的标识。
可选的，如上述步骤103所述，第一网络设备发送的控制报文还可以包括：任务标识以及业务流的起始网络设备的标识，相应的，该第二网络设备生成的响应报文也可以包括该任务标识以及该起始网络设备的标识，以便第一网络设备可以基于该任务标识识别该响应报文所对应的业务流的管理操作。
图6是本发明实施例提供的一种响应报文的结构示意图，该响应报文可以为GRASP响应消息，参考图6，该GRASP响应消息可以包括：基于安全协议(Internet Protocol Security，IPsec)的IPv6封装头(即IPv6 over IPsec header)、UDP封装头以及GRASP包，该UDP封装头以及GRASP包组成了该响应报文的有效载荷。
其中，由于自组织网络中各个网络设备的ACP VRF的通信都是基于ACP建立的安全隧道进行的，因此可以采用该IPv6 over IPsec header。其中，该安全隧道可以为IPsec隧道或者基于IPsec的GRE隧道(IPsec with GRE)等。
UDP Header可以包括：DestPort＝GRASP_LISTEN_PORT,SrcPort＝<随机分配>。其中，DestPort为UDP目的端口号，GRASP_LISTEN_PORT为GRASP模块的监听端口号，该监听端口号为知名端口号，SrcPort是指源端口号，该源端口号可以随机分配。从该UDP header可以看出，该UDP目的端口号即为GRASP模块的监听端口号，因此接收到该响应报文的第一网络设备可以根据该UDP目的端口号，将该响应报文分发至GRASP模块进行处理。
GRASP_Packet可以包括：[message type,session-id,objective]。
其中，message-type为消息类型字段，用于指示该响应报文的消息类型。例如，与该控制报文相对应，响应报文也可以使用GRASP的同步机制，即该响应报文可以为GRASP同步响应消息。相应的，该message type可以设置为M_SYNCH。
session-id为任务标识字段，用于携带任务标识，该任务标识可以为第二网络设备从接收到的控制报文中拷贝得到的。
objective为管理对象字段，用于携带第二网络设备所获取的与该管理操作关联的信息。例如，该管理对象字段的定义可以为：objective＝[objective-name,objective-flags,loop-count,objective-value]。
objective-name为对象名称字段，用于携带执行该管理操作的功能模块的对象名称。该对象名称与第二网络设备接收到的控制报文中所封装的对象名称相同。
objective-flags为对象标志字段，用来指定操作类型，可以设置为F_SYNCH。
objective-value为对象信息字段，该对象信息字段的定义可以为：objective-value＝[ingress,upstream,current,role,path-info,[*[type,params]]]。
ingress为起始网络设备标识字段，用于携带起始网络设备的标识，该字段的定义可以为：ingress＝[ingress-acp-ula,ingress-global-addr]。
示例的，对于图2所示的自组织网络，第二网络设备R2上报的响应报文中，该ingress字段可以携带有第一网络设备R1的ACP ULA，及该第一网络设备R1业务面的管理地址。
upstream为上游网络设备标识字段，用于携带第二网络设备的上一跳的网络设备的标识，该字段的定义可以为：upstream＝[upstream-acp-ula,upstream-global-addr]；从该字段的定义可以看出，该上一跳的网络设备的标识可以包括该上一跳的网络设备的ACP ULA以及该上一跳的网络设备业务面的管理地址。
示例的，对于图2所示的自组织网络，由于第二网络设备R2的上一跳的网络设备即为第一网络设备R1，因此该第二网络设备R2向第一网络设备R1上报的响应报文中，该upstream字段中可以携带有该第一网络设备R1的ACP ULA，以及该第一网络设备R1的业务面的管理地址。
current为当前网络设备标识字段，用于携带当前网络设备的标识，其定义可以为：current＝[current-acp-ula,current-global-addr]。
示例的，第二网络设备R2向第一网络设备R1上报的响应报文中，该current字段中可以携带有该第二网络设备R2的ACP ULA，以及该第二网络设备R2的业务面的管理地址。
role为角色标识字段，该字段用于携带该第二网络设备在业务流的转发路径上的角色。该第二网络设备的角色可以为转发网络设备、目标网络设备和边缘网络设备中的任一种。该第二网络设备在接收到控制报文后，若查询到下一跳的网络设备，且该下一跳的网络设备属于该自组织网络，则可以确定其角色为转发网络设备；若查询到下一跳的网络设备，但该下一跳的网络设备不属于该自组织网络，则可以确定其角色为边缘网络设备；若第二网络设备未查询到下一跳的网络设备，则可以确定其角色为目标网络设备。
示例的，对于图2所示的自组织网络，若第二网络设备R2查询到位于其下一跳的网络设备包括R3、R4和R5，且该R3、R4和R5均属于该自组织网络，则该第二网络设备R2上报的响应报文中，该角色标识字段携带的角色即为转发网络设备。
path-info为转发路径信息字段，该字段用于携带业务流的转发路径的相关信息，该字段的定义可以与控制报文中的转发路径信息字段的定义相同。并且，第二网络设备在接收到控制报文后，可以根据控制报文中的转发路径信息字段中的path-type字段 和path-keys字段，查询对应的转发路径的状态，并可以采用查询得到的转发路径的状态更新path-info中的path-status字段。
type为管理信息字段，用于携带待获取信息的类型；params为信息字段，用于携带第二网络设备获取到的与管理操作关联的信息。
示例的，当某个第二网络设备在执行管理操作时，发现转发路径中断(例如查询转发表项失败)时，可以将反馈至第一网络设备的响应报文中的path-status字段设置为broken；并可以在params字段中返回详细的查询转发表项失败的原因。并且，由于转发路径中断，因此该第二网络设备可以停止转发控制报文。
步骤107、第二网络设备将响应报文发送至第一网络设备。
在本发明实施例中，第二网络设备可以通过其控制面将响应报文发送至第一网络设备；相应的，第一网络设备可以通过其控制面接收第二网络设备上报的响应报文。由于自组织网络中各个网络设备之间的控制面具有全连通性，因此无论第二网络设备的业务面是否发生故障时，都能保证将响应报文及时上送至第一网络设备，以便第一网络设备可以及时对业务面的故障进行定位和分析，有效提高了对网络设备进行管理时的可靠性。
示例的，对于图2所示的自组织网络，第二网络设备R2可以通过其控制面将生成的响应报文发送至第一网络设备R1。
需要说明的是，根据控制报文中所封装的管理操作的类型的不同，第二网络设备发送响应报文的时机也有所不同。例如，当该管理操作为查询操作时，第二网络设备可以在执行该查询操作并获取到查询操作指示的信息后，将封装有该获取到的信息的响应报文实时反馈至第一网络设备，也即是，该第二网络设备可以通过该响应报文将与该查询操作关联的信息一次性反馈至第一网络设备。
当该管理操作为订阅操作时，第二网络设备可以在检测到该订阅操作指示的信息发生变化时，再将封装有该信息的响应报文上报至第一网络设备；或者第二网络设备可以根据该订阅操作指示的订阅周期，周期性的查询该订阅操作指示的信息，并向第一网络设备上报封装有该信息的响应报文。
步骤108、第二网络设备根据该业务流的标识，确定在该业务流的转发路径上，位于该第二网络设备的下一跳的网络设备。
第二网络设备接收到来自第一网络设备的控制报文后，除了执行管理操作，还可以基于该控制报文中封装的业务流的标识，从本地FDB中存储的转发表项中确定该业务流的转发路径上，第二网络设备的下一跳的网络设备。由于只有属于该自组织网络(即加入AINMA域)的网络设备的ACP VRF才能实现全连通，因此当第二网络设备确定该转发路径上不存在下一跳的网络设备(即该第二网络设备为业务流的目标网络设备)时，或者该下一跳的网络设备不属于该自组织网络时，第二网络设备可以不再转发该控制报文，即不再执行步骤109。
示例的，参考图4，该第二网络设备R2中接收到控制报文的ASA可以根据业务 流的标识在业务面的FDB中进行查询，以确定下一跳的网络设备。例如，该第二网络设备R2可以确定其下一跳的网络设备包括R3、R4和R5。
步骤109、第二网络设备将该控制报文转发至下一跳的网络设备。
若第二网络设备在上述步骤108中查询到了属于该自组织网络的下一跳的网络设备，则该第二网络设备可以通过控制面将该控制报文转发至该下一跳的网络设备，以便该下一跳的网络设备可以继续对该控制报文进行转发。
进一步的，若第二网络设备在上述步骤108中确定的下一跳的网络设备包括至少两个，即该业务流的转发路径上，该第二网络设备的下游转发路径中存在等价路由(Equal-Cost Multi path Routing，ECMP)时，该第二网络设备可以分别向每个下一跳的网络设备分别转发该控制报文。
或者，该第二网络设备还可以根据控制报文中封装的第二转发控制信息，确定该控制报文的转发方式。例如，若该第二转发控制信息为第一控制信息(例如0)，则该第二网络设备可以从该至少两个下一跳的网络设备中确定一个目标网络设备，并将该控制报文转发至该目标网络设备；若该第二转发控制信息为第二控制信息(例如1)，则该第二网络设备可以将该控制报文分别转发至每个下一跳的网络设备。其中，第二网络设备从至少两个下一跳的网络设备中确定目标网络设备时，可以采用哈希算法进行确定。例如第二网络设备可以根据控制报文中的相关字段直接进行计算(这种方式也称为静态哈希算法)，从而选取出该目标网络设备，以保证该至少两个下一跳的网络设备对应的子路径的负载较为均衡。
示例的，对于图2所示的自组织网络，第二网络设备R2接收到控制报文后，可以基于该业务流的标识，确定出R3、R4和R5共三个下一跳的网络设备。若该控制报文中封装的第二转发控制信息为1，则该第二网络设备R2可以对该控制报文进行复制，并分别转发至网络设备R3、R4和R5。
或者，假设在图2所示的自组织网络中，某个业务流的转发路径仅包括R6和R8两个网络设备，其中网络设备R6为起始网络设备，其下一跳的第二网络设备R8为目标网络设备，则当第二网络设备R8接收到控制报文后，由于在该业务流的转发路径上，该第二网络设备R8为目标网络设备，不存在下一跳的网络设备，因此该第二网络设备R8可以停止转发该控制报文，并且可以在获取到控制报文中封装的信息后，丢弃该控制报文。
需要说明的是，如上述步骤103所述，第一网络设备发送的控制报文中还可以包括当前网络设备的标识，因此第二网络设备在转发控制报文之前，还可以采用该第二网络设备自身的标识更新该控制报文中的当前网络设备的标识，然后再将该更新后的控制报文转发至该下一跳的网络设备，以便下一跳的网络设备可以准确获取到上一跳的网络设备的标识。
示例的，该第一网络设备R1发送的控制报文中的current字段可以携带有第一网络设备R1的ACP ULA，以及第一网络设备R1的业务面的管理地址；第二网络设备R2在接收到该控制报文后，可以将该current字段更新为第二网络设备R2的ACP ULA， 以及第二网络设备R2的业务面的管理地址。之后，第二网络设备R2即可将该更新后的控制报文分别转发至网络设备R3、R4和R5。
进一步的，由于当业务流的转发路径上还包括位于第二网络设备下游的下游网络设备时，第二网络设备还可以将控制报文逐跳转发至该下游网络设备，因此该转发路径上属于该自组织网络的网络设备均可以接收到该控制报文。相应的，每个接收到该控制报文的网络设备均可以根据该控制报文中管理操作的类型，执行管理操作，获取与该管理操作关联的信息，并向第一网络设备上报响应报文。该下游网络设备执行管理操作、获取与管理操作关联的信息、上报响应报文以及继续转发控制报文的实现过程可以参考上述步骤105至步骤109中的相关描述，此处不再赘述。
示例的，对于图2所示的自组织网络，以第一网络设备R1为起始网络设备的业务流的转发路径上，网络设备R3至R8均可以接收到来自该第一网络设备R1的控制报文，则网络设备R3至R8也可以分别执行管理操作、获取与管理操作关联的信息，并可以分别将生成的响应报文发送至第一网络设备R1。
需要说明的是，位于第二网络设备下游的下游网络设备在上报响应报文时，由于该下游网络设备的上一跳的网络设备并不是该第一网络设备，因此该下游网络设备需要通过逐跳转发的方式将响应报文上报至第一网络设备。也即是，该下游网络设备发送的响应报文最终需要通过第二网络设备上报至第一网络设备。
还需要说明的是，在本发明实施例中，若转发路径上的某个网络设备查询到转发路径上存在下一跳的网络设备，但该下一跳的网络设备不属于该自组织网络时，该网络设备也可以称为边缘网络设备或边缘节点(Egress Node)，该边缘网络设备无需再继续转发控制报文。由此可知，在本发明实施例中，业务流的转发路径上，仅转发网络设备需继续转发控制报文，而目标网络设备和边缘网络设备则无需转发该控制报文。
步骤110、第一网络设备呈现与管理操作关联的信息。
第一网络设备在接收到第二网络设备发送的响应报文，以及第二网络设备转发的来自第二网络设备的下游网络设备的响应报文后，可以获取各个响应报文中与管理操作关联的信息，对该信息进行汇总，并可以通过OM接口向远程终端或者NMS呈现汇总后的结果，以便管理员可以及时获知转发路径上各个网络设备执行该管理操作后所获取的信息。
例如，对于某个指定业务流的指定管理操作，第一网络设备可以根据为该指定业务流的指定管理操作所分配的指定任务标识，从接收到的多个响应报文中确定出任务标识为该指定任务标识的响应报文，并将该确定出的响应报文中的信息作为与该指定管理操作关联的信息进行呈现。由此，管理员可以准确获知针对不同业务流的管理操作所对应的信息。
此外，由于第二网络设备上报的响应报文还包括该第二网络设备的标识以及该第二网络设备的上一跳的网络设备的标识，第二网络设备的下游网络设备上报的响应报文还包括该下游网络设备的标识以及该下游网络设备的上一跳的网络设备的标识，因此该第一网络设备还可以根据其自身的标识，第二网络设备的标识，第二网络设备的 上一跳的网络设备的标识，每个下游网络设备的标识，以及每个下游网络设备的上一跳的网络设备的标识，确定出该业务流的转发路径，以及该转发路径所包括的网络设备，实现了转发路径的可视化，进而可以根据该确定出的转发路径和网络设备，对指定的网络设备实施指定的管理操作，有效提高了网络设备的管理效率。
示例的，第一网络设备可以对各个网络设备(包括第二网络设备和下游网络设备)上报的响应报文中的session-id、ingress以及path-info等字段进行匹配，将上述各个字段均相同的多个响应报文确定为同一转发路径上的多个网络设备上报的报文，进而可以基于其自身的标识，该多个响应报文中的当前网络设备的标识，以及上游网络设备的标识，识别出以该第一网络设备为根节点的转发路径以及该转发路径上的网络设备。
需要说明的是，在正常情况下，加入ANIMA域中的每个网络设备都会表现为RPL路由表中的一条主机路由，其前缀即为网络设备的ACP ULA。当网络设备离开ANIMA域时，RPL路由会重新收敛。转发路径上的网络设备可以正常将响应报文返回给第一网络设备时，第一网络设备在根据响应报文汇总转发路径的信息时，可以查询RPL路由表，以检查转发路径的状态，以及指定网络设备的状态。
当第一网络设备检测到某个业务流的转发路径的路径状态发生变化时(如转发路径上的某台网络设备退出ANIMA域)时，可以使用相同的session-id、ingress-acp-ula、path-type、path-keys等字段封装得到控制报文，并通过该控制报文重新收集和刷新转发路径的信息。在收集完所有网络设备反馈的响应报文并重新汇总转发路径的信息后，若某个网络设备的上一跳的网络设备的标识未携带在该转发路径的信息中(即第一网络设备未接收到该上一跳的网络设备发送的响应报文)时，第一网络设备可以将该网络设备确定为该转发路径上的“孤立”网络设备。若第一网络设备此前对该“孤立”网络设备执行过订阅操作，则第一网络设备可以向其发送用于指示取消订阅的控制报文(即该控制报文中封装的管理信息的类型为取消订阅)，以清除该网络设备中相关的订阅缓存信息。当然，若第一网络设备未发送用于指示取消订阅的控制报文，该网络设备的订阅缓存信息也可以被超时老化掉，即该网络设备可以在到达订阅操作对应的超时时间时，自动清除该订阅缓存信息。
此外，考虑到各个网络设备反馈响应报文的时序的问题，为了避免某个网络设备上报响应报文后，其上一跳的网络设备还未上报响应报文时，第一网络设备误将该某个网络设备识别为“孤立”网络设备，该第一网络设备中还可以设置有缓存机制，即第一网络设备可以在接收到响应报文后，等待一定时长后再进行转发路径的汇总计算。
还需要说明的是，本发明实施例提供的网络设备的管理方法的步骤的先后顺序可以进行适当调整，步骤也可以根据情况进行相应增减。例如，步骤108至步骤109可以在步骤105之前执行，或者与步骤105同时执行。任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本申请的保护范围之内，因此不再赘述。
综上所述，本发明实施例提供了一种网络设备的管理方法，自组织网络中的第一网络设备获取到业务流的管理信息后，可以向下一跳的第二网络设备发送控制报文，该控制报文包括该管理信息，该控制报文用于指示该第二网络设备执行该管理操作， 获取与该管理操作关联的信息，以及将获取到的与管理操作关联的信息封装在响应报文中并上报至该第一网络设备，由此该第一网络设备即可实现对转发路径上第二网络设备的管理。由于该管理方法可以由第一网络设备触发实现，避免了对NMS的依赖，提高了管理的灵活性。并且由于各网络设备中也无需再部署北向接口，因此有效降低了网络设备的管理成本，可以为一些中小型网络或者物联网(Internet of Things，IoT)提供较为高效的解决方案。
此外，由于NMS是通过向网络设备查询大量表项来了解网络设备运行状态，因此当网络的规模较大时，NMS存在较为明显的性能问题。并且NMS受限于北向接口，其所能实施的管理操作的类型有限，难以对业务流的转发路径上的网络设备进行精准地跟踪和管理。又由于NMS对网络设备进行管理时，两者之间交互的简单网络管理协议(Simple Network Management Protocol，SNMP)报文需要通过常规的转发表项(例如：路由表)进行转发。当路由出现故障(例如，选路错误)时，NMS将无法对上述故障进行定位分析，即此时，网络设备就处于脱管状态。
而在本发明实施例提供的管理方法中，自组织网络中的第一网络设备可以通过业务面发送控制报文，并通过控制面来接收第二网络设备以及第二网络设备的下游网络设备上报的响应报文，该管理过程对业务流的业务报文没有影响，并且无论网络设备的业务面是否发生故障时，都能保证将响应报文送达第一网络设备，以确保该第一网络设备可以及时对故障进行分析和定位。此外，由于在本发明实施例提供的方法中，管理操作的执行，以及响应报文中与管理操作关联的信息的获取均是由第二网络设备执行的，而并非是由NMS执行的。相较于NMS，第二网络设备内部所能执行的管理操作的类型较为丰富，因此可以进一步提高管理的灵活性。
此外，本发明实施例提供的方法对自组织网络中的业务流的转发模型无无依赖，可以适用各类转发模型，具有广泛的适应性；并且，管理员只需在业务流的起始网络设备中输入管理信息，即可对业务流的转发路径上的各个网络设备实施指定的管理操作，该管理方法操作简单。进一步的，该管理方法基于ANIMA ANI的安全架构，具有较高的安全性，并且该管理方法提供了基于业务流的通用管理框架，其具备良好的扩展性。
图7是本发明实施例提供的一种网络设备的管理装置的结构示意图，该装置可以应用于自组织网络中的第一网络设备，参考图7，该装置可以包括：
获取模块201，可以用于实现图3所示实施例中步骤101所示的方法。
第一确定模块202，可以用于实现图3所示实施例中步骤102所示的方法。
发送模块203，可以用于实现图3所示实施例中步骤104所示的方法。
接收模块204，用于接收来自第二网络设备的响应报文，该响应报文包括与管理操作关联的信息，其实现过程可以参考图3所示实施例中步骤107所示的方法，此处不再赘述。
可选的，该发送模块203发送的控制报文还可以包括：任务标识以及业务流的起始网络设备的标识，该起始网络设备的标识为第一网络设备的标识，该任务标识为该第一网络设备为该业务流的该管理操作分配的标识。
可选的，该控制报文还包括：当前网络设备的标识，该当前网络设备的标识用于指示当前发送该控制报文的网络设备，该当前网络设备的标识为所述第一网络设备的标识。
可选的，该控制报文还包括：待获取信息的类型；
该控制报文用于指示该第二网络设备根据该管理操作的类型执行管理操作，并获取该待获取信息的类型指示的信息。
可选的，该控制报文还包括：控制信息，该控制信息包括第一转发控制信息和第二转发控制信息中的至少一种；
其中，该第一转发控制信息用于在该第二网络设备不支持该管理操作时，指示该第二网络设备转发该控制报文，或者停止转发该控制报文；
该第二转发控制信息用于在该第二网络设备的下一跳的网络设备包括至少两个时，指示该第二网络设备向其中一个下一跳的网络设备转发该控制报文，或者向该第二网络设备的每个下一跳的网络设备分别转发该控制报文。
可选的，第二网络设备上报的响应报文还包括该第二网络设备的标识以及该第二网络设备的上一跳的网络设备的标识；图8是本发明实施例提供的另一种网络设备的管理装置的结构示意图，参考图8，该装置还可以包括：
第二确定模块205，用于根据第二网络设备的标识，以及第二网络设备的上一跳的网络设备的标识，确定该业务流的转发路径所包括的网络设备。
综上所述，本发明实施例提供了一种网络设备的管理装置，该装置获取到业务流的管理信息后，可以向下一跳的第二网络设备发送控制报文，该控制报文包括该管理信息，该控制报文用于指示该第二网络设备执行该管理操作，获取与该管理操作关联的信息，以及将获取到的与管理操作关联的信息封装在响应报文中并上报至该第一网络设备，由此该第一网络设备即可实现对转发路径上第二网络设备的管理。由于该管理方法可以由第一网络设备触发实现，避免了对NMS的依赖，提高了管理的灵活性。并且由于各网络设备中也无需再部署北向接口，因此有效降低了网络设备的管理成本。
图9是本发明实施例提供的又一种网络设备的管理装置的结构示意图，该装置可以应用于自组织网络中的第二网络设备，参考图9，该装置可以包括：
接收模块301，用于接收来自第一网络设备的控制报文，该控制报文包括业务流的管理信息，该管理信息包括管理操作的类型以及业务流的标识，该第一网络设备为该业务流的起始网络设备。接收模块301的功能可以参考上述图3所示实施例中步骤104的相关描述，此处不再赘述。
处理模块302，可以用于实现上述图3所示实施例中步骤105所示的方法。
第一发送模块303，可以用于实现上述图3所示实施例中步骤107所示的方法。
可选的，该控制报文还可以包括：当前网络设备的标识，该当前网络设备的标识用于指示发送该控制报文的网络设备，发送该控制报文的网络设备为在该业务流的转发路径上，位于第二网络设备的上一跳的网络设备。图10是本发明实施例提供的再一种网络设备的管理装置的结构示意图，参考图10，该装置还可以包括：
第一确定模块304，用于根据该当前网络设备的标识，确定该第二网络设备的上一跳的网络设备的标识为该当前网络设备的标识，也即是，可以将该当前网络设备的标识确定为确定该上一跳的网络设备的标识。
相应地，该响应报文还可以包括：该第二网络设备的标识以及该第二网络设备的上一跳的网络设备的标识。
可选的，如图10所示，该装置还可以包括：
第二确定模块305，可以用于实现上述图3所示实施例中步骤108所示的方法。
第二发送模块306，可以用于实现上述图3所示实施例中步骤109所示的方法。
可选的，该第二发送模块306，可以用于：
采用该第二网络设备的标识更新该控制报文中的该当前网络设备的标识；
将更新后的该控制报文转发至该第二网络设备的下一跳的网络设备。
可选的，该控制报文还可以包括：待获取信息的类型；该处理模块302，可以用于：
获取该待获取信息的类型指示的信息。
可选的，该控制报文还包括：控制信息，该控制信息包括第一转发控制信息和第二转发控制信息中的至少一种；
当该控制信息包括该第一转发控制信息时，该第二发送模块306可以用于：
在该第二网络设备不支持该管理操作时，若该第一转发控制信息为预设控制信息，将该控制报文转发至该下一跳的网络设备；
当该控制信息包括该第二转发控制信息时，该第二发送模块306可以用于：
在该第二网络设备的下一跳的网络设备包括至少两个时，若该第二转发控制信息为第一控制信息，从该至少两个下一跳的网络设备中确定一个目标网络设备，并将该控制报文转发至该目标网络设备；若该第二转发控制信息为第二控制信息，将该控制报文分别转发至每个下一跳的网络设备。
可选的，该控制报文还包括：任务标识以及该业务流的起始网络设备的标识，
该起始网络设备的标识为该第一网络设备的标识，该任务标识为该第一网络设备为该业务流的该管理操作分配的标识；该响应报文还包括：该任务标识。
综上所述，本发明实施例提供了一种网络设备的管理装置，该装置可以在接收到 来自第一网络设备的控制报文后，执行该控制报文中管理操作的类型所指示的管理操作，获取与该管理操作关联的信息，以及将获取到的信息封装在响应报文中并上报至第一网络设备，由此该第一网络设备即可实现对转发路径上第二网络设备的管理，由于该管理方法可以由第一网络设备触发实现，避免了对NMS的依赖，提高了管理的灵活性。并且由于各网络设备中也无需再部署北向接口，因此有效降低了网络设备的管理成本，
关于上述实施例中的装置，其中各个模块执行操作的实现方式已经在有关该方法的实施例中进行了详细描述，故此处不再阐述说明。
图11是本发明实施例提供的一种网络设备的结构示意图，参考图11，该网络设备500A可以包括：主控板510，以及分别与该主控板510连接的交换网板520和至少一个接口板。示例的，在图11所示的结构中，该网络设备中设置有接口板530和接口板540共两个接口板。该两个接口板通过交换网板520建立连接。
其中，主控板510中设置有中央处理器511。接口板530中设置有中央处理器531、网络处理器532、物理接口卡533以及转发表项存储器534；其中，中央处理器531分别与转发表项存储器534以及网络处理器532连接，转发表项存储器534和物理接口卡533均与该网络处理器532连接。接口板540中设置有中央处理器541、网络处理器542、物理接口卡543以及转发表项存储器544；其中，中央处理器541分别与转发表项存储器544以及网络处理器542连接，转发表项存储器544和物理接口卡543均与该网络处理器542连接。
当该网络设备为第一网络设备时，该主控板510的功能可以参考图3所示实施例中步骤102、步骤103以及步骤110中的相关描述；该接口板530、接口板540以及交换网板520的功能可以参考图3所示实施例中步骤101、步骤104以及步骤107中的相关描述，此处不再赘述。
当该网络设备为第二网络设备时，该主控板510的功能可以参考图3所示实施例中步骤105、步骤106、步骤107以及步骤108中的相关描述；该接口板530、接口板540以及交换网板520的功能可以参考图3所示实施例中步骤104以及步骤107中的相关描述，此处不再赘述。
图12是本发明实施例提供的另一种网络设备的结构示意图，参考图12，该网络设备600可以包括：处理器610、通信接口620和存储器630，通信接口620和存储器630分别与处理器610相连，示例地，如图12所示，通信接口620和存储器630通过总线640与处理器610相连。
其中，处理器610可以为中央处理器(CPU)，处理器610包括一个或者一个以上处理核心。处理器610通过运行软件程序，从而执行各种功能应用以及数据处理。
其中，通信接口620可以为多个，该通信接口620用于网络设备600与外部设备 进行通信，该外部设备例如显示器、第三方设备(例如，存储设备、移动终端等)等。
其中，存储器630存储有可在该处理器610上运行的计算机程序，该存储器630可以包括但不限于：随机存取存储器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM)、快闪存储器、光存储器。该存储器630负责信息存储，例如，该存储器630用于存储软件程序。
可选地，该网络设备600还可以包括：输入/输出(I/O)接口(图12中未示出)。I/O接口与处理器610、通信接口620以及存储器630连接。I/O接口例如可以为通用串行总线(USB)。
当该网络设备为第一网络设备时，处理器610被配置为执行存储器630中存储的计算机程序，处理器630通过执行该计算机程序来实现上述图3所示实施例中步骤101至步骤104，以及步骤110所示的方法。
当该网络设备为第二网络设备时，处理器610被配置为执行存储器630中存储的计算机程序，处理器630通过执行该计算机程序来实现上述图3所示实施例中步骤105至步骤109所示的方法。
图13是本发明实施例提供的一种网络设备的管理系统的结构示意图，该系统可以应用于自组织网络，如图13所示，该系统可以包括：第一网络设备01以及第二网络设备02。进一步的，该系统还可以包括该第二网络设备02的下游网络设备。例如，图2所示的自组织网络中的管理系统可以包括第一网络设备R1，第二网络设备R2，以及第二网络设备R2的下游网络设备R3至R8。
其中，该第一网络设备01可以包括如图7或图8所示的装置，或者该第一网络设备01可以为如图11或图12所示的网络设备；该第二网络设备02可以包括如图9或图10所示的装置，或者该第二网络设备02可以为如图11或图12所示的网络设备。
本发明实施例提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该计算机可读存储介质在计算机上运行时，使得计算机执行上述方法实施例所提供的网络设备的管理方法。
本发明实施例还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述方法实施例所提供的网络设备的管理方法。

Claims (29)

  1. 一种网络设备的管理方法，其特征在于，应用于自组织网络中的第一网络设备，所述方法包括：
    获取业务流的管理信息，所述管理信息包括管理操作的类型和所述业务流的标识，所述第一网络设备为所述业务流的起始网络设备；
    根据所述业务流的标识，确定所述业务流的转发路径上的第二网络设备，所述第二网络设备为所述第一网络设备的下一跳的网络设备；
    向所述第二网络设备发送控制报文，所述控制报文包括所述管理信息，所述控制报文用于指示所述第二网络设备根据所述管理操作的类型执行管理操作，并获取与所述管理操作关联的信息；
    接收来自所述第二网络设备的响应报文，所述响应报文包括所述与所述管理操作关联的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述控制报文还包括：任务标识以及所述业务流的起始网络设备的标识，所述起始网络设备的标识为所述第一网络设备的标识，所述任务标识为所述第一网络设备为所述业务流的所述管理操作分配的标识。
  3. 根据权利要求2所述的方法，其特征在于，所述控制报文还包括：当前网络设备的标识，所述当前网络设备的标识用于指示当前发送所述控制报文的网络设备，所述当前网络设备的标识为所述第一网络设备的标识。
  4. 根据权利要求1所述的方法，其特征在于，所述控制报文还包括：待获取信息的类型；
    所述控制报文用于指示所述第二网络设备根据所述管理操作的类型执行管理操作，并获取所述待获取信息的类型指示的信息。
  5. 根据权利要求1所述的方法，其特征在于，所述控制报文还包括：控制信息，所述控制信息包括第一转发控制信息和第二转发控制信息中的至少一种；
    其中，所述第一转发控制信息用于在所述第二网络设备不支持所述管理操作时，指示所述第二网络设备转发所述控制报文，或者停止转发所述控制报文；
    所述第二转发控制信息用于在所述第二网络设备的下一跳的网络设备包括至少两个时，指示所述第二网络设备向其中一个下一跳的网络设备转发所述控制报文，或者向所述第二网络设备的每个下一跳的网络设备分别转发所述控制报文。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述第二网络设备上报的响应报文还包括：所述第二网络设备的标识以及所述第二网络设备的上一跳的网络设备的标识；所述方法还包括：
    根据所述第二网络设备的标识，以及所述第二网络设备的上一跳的网络设备的标识，确定所述业务流的转发路径所包括的网络设备。
  7. 一种网络设备的管理方法，其特征在于，应用于自组织网络中的第二网络设备，所述方法包括：
    接收来自第一网络设备的控制报文，所述控制报文包括业务流的管理信息，所述管理信息包括管理操作的类型以及所述业务流的标识，所述第一网络设备为所述业务流的起始网络设备；
    根据所述管理操作的类型执行管理操作，并获取与所述管理操作关联的信息；
    向所述第一网络设备发送响应报文，所述响应报文包括所述与所述管理操作关联的信息。
  8. 根据权利要求7所述的方法，其特征在于，所述控制报文还包括：当前网络设备的标识，所述当前网络设备的标识用于指示发送所述控制报文的网络设备，所述发送所述控制报文的网络设备为在所述业务流的转发路径上，位于所述第二网络设备的上一跳的网络设备；
    在所述接收来自第一网络设备的控制报文之后，所述方法还包括：
    根据所述当前网络设备的标识，确定所述第二网络设备的上一跳的网络设备的标识为所述当前网络设备的标识；
    相应地，所述响应报文还包括：所述第二网络设备的标识以及所述第二网络设备的上一跳的网络设备的标识。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    根据所述业务流的标识，确定在所述业务流的转发路径上，位于所述第二网络设备的下一跳的网络设备；
    将所述控制报文转发至所述第二网络设备的下一跳的网络设备。
  10. 根据权利要求9所述的方法，其特征在于，所述将所述控制报文转发至所述第二网络设备的下一跳的网络设备，包括：
    采用所述第二网络设备的标识更新所述控制报文中的所述当前网络设备的标识；
    将更新后的所述控制报文转发至所述第二网络设备的下一跳的网络设备。
  11. 根据权利要求7至10任一所述的方法，其特征在于，所述控制报文还包括：待获取信息的类型；
    所述获取与所述管理操作关联的信息，包括：
    获取所述待获取信息的类型指示的信息。
  12. 根据权利要求9或10所述的方法，其特征在于，所述控制报文还包括：控制信息，所述控制信息包括第一转发控制信息和第二转发控制信息中的至少一种；
    当所述控制信息包括所述第一转发控制信息时，所述将所述控制报文转发至所述第二网络设备的下一跳的网络设备，包括：
    在所述第二网络设备不支持所述管理操作时，若所述第一转发控制信息为预设控制信息，将所述控制报文转发至所述下一跳的网络设备；
    当所述控制信息包括所述第二转发控制信息时，所述将所述控制报文转发至所述第二网络设备的下一跳的网络设备，包括：
    在所述第二网络设备的下一跳的网络设备包括至少两个时，若所述第二转发控制信息为第一控制信息，从至少两个所述下一跳的网络设备中确定一个目标网络设备，并将所述控制报文转发至所述目标网络设备；若所述第二转发控制信息为第二控制信息，将所述控制报文分别转发至每个所述下一跳的网络设备。
  13. 根据权利要求7至10任一所述的方法，其特征在于，所述控制报文还包括：任务标识以及所述业务流的起始网络设备的标识，
    所述起始网络设备的标识为所述第一网络设备的标识，所述任务标识为所述第一网络设备为所述业务流的所述管理操作分配的标识；
    所述响应报文还包括：所述任务标识。
  14. 一种网络设备的管理装置，其特征在于，应用于自组织网络中的第一网络设备，所述装置包括：
    获取模块，用于获取业务流的管理信息，所述管理信息包括管理操作的类型和所述业务流的标识，所述第一网络设备为所述业务流的起始网络设备；
    第一确定模块，用于根据所述业务流的标识，确定所述业务流的转发路径上的第二网络设备，所述第二网络设备为所述第一网络设备的下一跳的网络设备；
    发送模块，用于向所述第二网络设备发送控制报文，所述控制报文包括所述管理 信息，所述控制报文用于指示所述第二网络设备根据所述管理操作的类型执行管理操作，并获取与所述管理操作关联的信息；
    接收模块，用于接收来自所述第二网络设备的响应报文，所述响应报文包括所述与所述管理操作关联的信息。
  15. 根据权利要求14所述的装置，其特征在于，所述控制报文还包括：任务标识以及所述业务流的起始网络设备的标识，所述起始网络设备的标识为所述第一网络设备的标识，所述任务标识为所述第一网络设备为所述业务流的所述管理操作分配的标识。
  16. 根据权利要求15所述的装置，其特征在于，所述控制报文还包括：当前网络设备的标识，所述当前网络设备的标识用于指示当前发送所述控制报文的网络设备，所述当前网络设备的标识为所述第一网络设备的标识。
  17. 根据权利要求14所述的装置，其特征在于，所述控制报文还包括：待获取信息的类型；
    所述控制报文用于指示所述第二网络设备根据所述管理操作的类型执行管理操作，并获取所述待获取信息的类型指示的信息。
  18. 根据权利要求14所述的装置，其特征在于，所述控制报文还包括：控制信息，所述控制信息包括第一转发控制信息和第二转发控制信息中的至少一种；
    其中，所述第一转发控制信息用于在所述第二网络设备不支持所述管理操作时，指示所述第二网络设备转发所述控制报文，或者停止转发所述控制报文；
    所述第二转发控制信息用于在所述第二网络设备的下一跳的网络设备包括至少两个时，指示所述第二网络设备向其中一个下一跳的网络设备转发所述控制报文，或者向所述第二网络设备的每个下一跳的网络设备分别转发所述控制报文。
  19. 根据权利要求14至18任一所述的装置，其特征在于，所述第二网络设备上报的响应报文还包括：所述第二网络设备的标识以及所述第二网络设备的上一跳的网络设备的标识；所述装置还包括：
    第二确定模块，用于根据所述第二网络设备的标识，以及所述第二网络设备的上一跳的网络设备的标识，确定所述业务流的转发路径所包括的网络设备。
  20. 一种网络设备的管理装置，其特征在于，应用于自组织网络中的第二网络设 备，所述装置包括：
    接收模块，用于接收来自第一网络设备的控制报文，所述控制报文包括业务流的管理信息，所述管理信息包括管理操作的类型以及所述业务流的标识，所述第一网络设备为所述业务流的起始网络设备；
    处理模块，用于根据所述管理操作的类型执行管理操作，并获取与所述管理操作关联的信息；
    第一发送模块，用于向所述第一网络设备发送响应报文，所述响应报文包括所述与所述管理操作关联的信息。
  21. 根据权利要求20所述的装置，其特征在于，所述控制报文还包括：当前网络设备的标识，所述当前网络设备的标识用于指示发送所述控制报文的网络设备，所述发送所述控制报文的网络设备为在所述业务流的转发路径上，位于所述第二网络设备的上一跳的网络设备；所述装置还包括：
    第一确定模块，用于根据所述当前网络设备的标识，确定所述第二网络设备的上一跳的网络设备的标识为所述当前网络设备的标识；
    相应地，所述响应报文还包括：所述第二网络设备的标识以及所述第二网络设备的上一跳的网络设备的标识。
  22. 根据权利要求21所述的装置，其特征在于，所述装置还包括：
    第二确定模块，用于根据所述业务流的标识，确定在所述业务流的转发路径上，位于所述第二网络设备的下一跳的网络设备；
    第二发送模块，用于将所述控制报文转发至所述第二网络设备的下一跳的网络设备。
  23. 根据权利要求22所述的装置，其特征在于，所述第二发送模块，用于：
    采用所述第二网络设备的标识更新所述控制报文中的所述当前网络设备的标识；
    将更新后的所述控制报文转发至所述第二网络设备的下一跳的网络设备。
  24. 根据权利要求20至23任一所述的装置，其特征在于，所述控制报文还包括：待获取信息的类型；所述处理模块，用于：
    获取所述待获取信息的类型指示的信息。
  25. 根据权利要求22或23所述的装置，其特征在于，所述控制报文还包括：控 制信息，所述控制信息包括第一转发控制信息和第二转发控制信息中的至少一种；
    当所述控制信息包括所述第一转发控制信息时，所述第二发送模块，用于：
    在所述第二网络设备不支持所述管理操作时，若所述第一转发控制信息为预设控制信息，将所述控制报文转发至所述下一跳的网络设备；
    当所述控制信息包括所述第二转发控制信息时，所述第二发送模块，用于：
    在所述第二网络设备的下一跳的网络设备包括至少两个时，若所述第二转发控制信息为第一控制信息，从至少两个所述下一跳的网络设备中确定一个目标网络设备，并将所述控制报文转发至所述目标网络设备；若所述第二转发控制信息为第二控制信息，将所述控制报文分别转发至每个所述下一跳的网络设备。
  26. 根据权利要求20至23任一所述的装置，其特征在于，所述控制报文还包括：任务标识以及所述业务流的起始网络设备的标识，
    所述起始网络设备的标识为所述第一网络设备的标识，所述任务标识为所述第一网络设备为所述业务流的所述管理操作分配的标识；
    所述响应报文还包括：所述任务标识。
  27. 一种网络设备，其特征在于，所述网络设备包括：存储器，处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求1至6任一所述的网络设备的管理方法，或者实现如权利要求7至13任一所述的网络设备的管理方法。
  28. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述计算机可读存储介质在计算机上运行时，使得计算机执行如权利要求1至6任一所述的网络设备的管理方法，或者如权利要求7至13任一所述的网络设备的管理方法。
  29. 一种网络设备的管理系统，其特征在于，应用于自组织网络，所述管理系统包括：第一网络设备以及第二网络设备；
    所述第一网络设备包括如权利要求14至19任一所述的装置，或者所述第一网络设备为如权利要求27所述的网络设备；
    所述第二网络设备包括如权利要求20至26任一所述的装置，或者所述第二网络设备为如权利要求27所述的网络设备。
PCT/CN2019/078537 2018-03-30 2019-03-18 网络设备的管理方法、装置及系统 WO2019184752A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19777499.5A EP3764594A4 (en) 2018-03-30 2019-03-18 METHOD, EQUIPMENT, AND SYSTEM FOR MANAGING NETWORK DEVICES
US17/033,385 US11374857B2 (en) 2018-03-30 2020-09-25 Network device management method and apparatus, and system for indicating a network device to perform management operation

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810277234.9A CN110324165B (zh) 2018-03-30 2018-03-30 网络设备的管理方法、装置及系统
CN201810277234.9 2018-03-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/033,385 Continuation US11374857B2 (en) 2018-03-30 2020-09-25 Network device management method and apparatus, and system for indicating a network device to perform management operation

Publications (1)

Publication Number Publication Date
WO2019184752A1 true WO2019184752A1 (zh) 2019-10-03

Family

ID=68059272

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/078537 WO2019184752A1 (zh) 2018-03-30 2019-03-18 网络设备的管理方法、装置及系统

Country Status (4)

Country Link
US (1) US11374857B2 (zh)
EP (1) EP3764594A4 (zh)
CN (2) CN113364610B (zh)
WO (1) WO2019184752A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4210286A4 (en) * 2020-09-21 2024-02-28 Huawei Tech Co Ltd METHOD, DEVICE AND SYSTEM FOR IMPLEMENTING SERVICE PATH DETECTION

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113364610B (zh) * 2018-03-30 2022-08-09 华为技术有限公司 网络设备的管理方法、装置及系统
CN110380966B (zh) 2018-04-13 2020-11-06 华为技术有限公司 一种发现转发路径的方法及其相关设备
CN108737183B (zh) 2018-05-22 2021-06-22 华为技术有限公司 一种转发表项的监测方法及装置
US11232526B2 (en) 2019-05-31 2022-01-25 Iunu, Inc. Centralized governance regulatory compliance (C-GRC) system
CN112968919B (zh) * 2019-12-12 2023-05-30 上海欣诺通信技术股份有限公司 一种数据处理方法、装置、设备和存储介质
CN113300951B (zh) * 2020-02-21 2023-10-24 华为技术有限公司 一种发送报文的方法、设备及系统
US11694212B2 (en) * 2020-03-25 2023-07-04 Iunu, Inc. Decentralized governance regulatory compliance (D-GRC) controller
CN113452538B (zh) 2020-03-26 2022-12-13 华为技术有限公司 控制设备、执行设备、设备管理方法和设备管理系统
CN116232973A (zh) * 2020-04-03 2023-06-06 华为技术有限公司 信息处理方法、装置及系统
CN115174564A (zh) * 2021-03-19 2022-10-11 华为技术有限公司 报文处理方法以及相关设备
CN115134192A (zh) * 2021-03-25 2022-09-30 中兴通讯股份有限公司 信息处理方法、设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060056302A1 (en) * 2004-09-10 2006-03-16 Jin-Ho Ahn Apparatus for implementation of adaptive routing in packet switched networks
CN101459602A (zh) * 2008-11-28 2009-06-17 烽火通信科技股份有限公司 一种在分组传送网络中传送管理和控制信息的装置及方法
CN101512980A (zh) * 2006-09-07 2009-08-19 摩托罗拉公司 通过多跳网格网络传输管理业务
CN103379526A (zh) * 2012-04-24 2013-10-30 中兴通讯股份有限公司 一种维护网元的方法和系统

Family Cites Families (50)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3436871B2 (ja) * 1997-10-23 2003-08-18 株式会社東芝 通信資源管理方法及びノード装置
KR100428774B1 (ko) * 2002-01-24 2004-04-28 삼성전자주식회사 멀티 프로토콜 레이블 스위칭 트래픽 엔지니어링 스케줄링장치
CN100512283C (zh) * 2004-07-29 2009-07-08 国家数字交换系统工程技术研究中心 一种将路由器的控制平面同数据平面的硬件相分离的方法
US7447796B2 (en) * 2004-12-17 2008-11-04 International Business Machines Corporation System, method and program product to route message packets
US20090116404A1 (en) * 2007-11-01 2009-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Topology discovery in heterogeneous networks
US8018941B2 (en) * 2008-09-30 2011-09-13 At&T Intellectual Property I, L.P. Demand-based distribution of internet protocol routing information across a network
KR101089832B1 (ko) * 2010-01-25 2011-12-05 포항공과대학교 산학협력단 네트워크 자율 관리 시스템
US20110228696A1 (en) * 2010-03-19 2011-09-22 Navneet Agarwal Dynamic directed acyclic graph (dag) topology reporting
EP2387180B1 (en) * 2010-05-14 2019-12-18 Viavi Solutions Inc. Network communication with unaddressed network devices
CN102136990B (zh) * 2010-06-09 2013-11-06 华为技术有限公司 一种业务叠加网络的业务路由方法及系统
US8995266B2 (en) * 2010-07-07 2015-03-31 Cisco Technology, Inc. Performing path-oriented systems management
US8619773B2 (en) * 2010-07-29 2013-12-31 Cisco Technology, Inc. Service request packet including an exterior network protocol attribute
US8711859B2 (en) * 2010-11-30 2014-04-29 Cisco Technology, Inc. Interconnecting virtual domains
US8615015B1 (en) * 2010-12-30 2013-12-24 Juniper Networks, Inc. Apparatus, systems and methods for aggregate routes within a communications network
CN102209363B (zh) * 2011-05-18 2015-05-20 中兴通讯股份有限公司 一种在操作维护中心配置到基站路由的实现方法及系统
CN102170371B (zh) * 2011-05-18 2013-07-10 武汉烽火网络有限责任公司 一种基于集中式管理的收集网络设备重要信息的方法
WO2012106869A1 (zh) * 2011-07-06 2012-08-16 华为技术有限公司 一种报文处理方法及相关设备
CN104380658B (zh) * 2013-04-28 2018-06-05 华为技术有限公司 流分类器、业务路由触发器、报文处理的方法和系统
CN103581018B (zh) * 2013-07-26 2017-08-11 北京华为数字技术有限公司 报文发送方法、路由器以及业务交换器
CN103414633B (zh) * 2013-08-08 2016-09-07 北京华为数字技术有限公司 一种网络中路径建立的方法及装置
CN104518967B (zh) * 2013-09-30 2017-12-12 华为技术有限公司 路由方法、设备和系统
US9210075B2 (en) * 2013-10-08 2015-12-08 Ciena Corporation Method and apparatus for managing end-to-end consistency of bi-directional MPLS-TP tunnels via in-band communication channel (G-ACH) protocol
US10313236B1 (en) * 2013-12-31 2019-06-04 Sanmina Corporation Method of flow based services for flash storage
KR20150091880A (ko) * 2014-02-04 2015-08-12 한국전자통신연구원 모바일 애드혹 네트워크 환경에서 icn 기반 콘텐트 통신 방법 및 장치
WO2015161416A1 (zh) * 2014-04-21 2015-10-29 华为技术有限公司 一种报文传输方法、设备及通信系统
CN110034971B (zh) * 2014-05-26 2022-11-18 华为技术有限公司 检测业务链的方法及装置
WO2015197564A1 (en) * 2014-06-23 2015-12-30 Getclouder Ltd. Cloud hosting systems featuring scaling and load balancing with containers
CN109714274B (zh) * 2014-08-14 2022-04-05 华为技术有限公司 一种获取对应关系的方法和路由设备
CN105636234B (zh) * 2014-10-27 2021-06-25 中兴通讯股份有限公司 一种开站方法、基站、基站控制器及开站系统
WO2016082167A1 (zh) * 2014-11-28 2016-06-02 华为技术有限公司 业务处理装置及方法
CN105812162A (zh) * 2014-12-30 2016-07-27 北京华为数字技术有限公司 一种获取业务流的转发路径信息的装置及方法
CN111934943A (zh) * 2014-12-30 2020-11-13 华为技术有限公司 位转发入口路由器、位转发路由器及操作管理维护检测方法
US20180131599A1 (en) * 2015-05-15 2018-05-10 Telefonaktiebolaget L M Ericsson (Publ) Routing In A Multi-Path Network
CN106341298B (zh) * 2015-07-06 2019-03-22 中兴通讯股份有限公司 报文发送方法及装置
US9912566B1 (en) * 2015-07-20 2018-03-06 Cisco Technology, Inc. Method and apparatus for tracing paths in service function chains
CN106576074B (zh) * 2015-07-31 2020-04-21 华为技术有限公司 路由规则的获取方法、设备和系统
CN106656905B (zh) * 2015-10-28 2020-02-21 新华三技术有限公司 防火墙集群实现方法及装置
CN106464590B (zh) * 2015-11-27 2019-11-19 华为技术有限公司 一种获取路径信息的方法及装置
GB2549549B (en) * 2016-04-19 2020-12-23 Cisco Tech Inc A mapping database system for use with content chunks
US10972384B2 (en) * 2016-07-27 2021-04-06 New H3C Technologies Co., Ltd. Processing of data stream
US11277338B2 (en) * 2016-09-26 2022-03-15 Juniper Networks, Inc. Distributing service function chain data and service function instance data in a network
CN108075991B (zh) * 2016-11-18 2020-09-08 新华三技术有限公司 报文转发方法及装置
CN106790647B (zh) * 2017-01-15 2020-06-23 网宿科技股份有限公司 一种自适应服务管理的方法和系统
US10678580B2 (en) * 2017-05-09 2020-06-09 Vmware, Inc. Methods and apparatus to publish internal commands as an application programming interface in a cloud infrastructure
US10757011B2 (en) * 2017-05-25 2020-08-25 Zycada Networks, Inc. Context-aware path computation and selection
US11134088B2 (en) * 2017-12-14 2021-09-28 Telefonaktiebolaget Lm Ericsson (Publ) Secure next-hop communication
US10819685B2 (en) * 2018-03-02 2020-10-27 Futurewei Technologies, Inc. Lightweight secure autonomic control plane
CN113364610B (zh) * 2018-03-30 2022-08-09 华为技术有限公司 网络设备的管理方法、装置及系统
CN110380966B (zh) * 2018-04-13 2020-11-06 华为技术有限公司 一种发现转发路径的方法及其相关设备
CN108737183B (zh) * 2018-05-22 2021-06-22 华为技术有限公司 一种转发表项的监测方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060056302A1 (en) * 2004-09-10 2006-03-16 Jin-Ho Ahn Apparatus for implementation of adaptive routing in packet switched networks
CN101512980A (zh) * 2006-09-07 2009-08-19 摩托罗拉公司 通过多跳网格网络传输管理业务
CN101459602A (zh) * 2008-11-28 2009-06-17 烽火通信科技股份有限公司 一种在分组传送网络中传送管理和控制信息的装置及方法
CN103379526A (zh) * 2012-04-24 2013-10-30 中兴通讯股份有限公司 一种维护网元的方法和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3764594A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4210286A4 (en) * 2020-09-21 2024-02-28 Huawei Tech Co Ltd METHOD, DEVICE AND SYSTEM FOR IMPLEMENTING SERVICE PATH DETECTION

Also Published As

Publication number Publication date
EP3764594A4 (en) 2021-04-21
CN110324165B (zh) 2021-05-11
EP3764594A1 (en) 2021-01-13
CN113364610B (zh) 2022-08-09
US11374857B2 (en) 2022-06-28
CN113364610A (zh) 2021-09-07
US20210014158A1 (en) 2021-01-14
CN110324165A (zh) 2019-10-11

Similar Documents

Publication Publication Date Title
WO2019184752A1 (zh) 网络设备的管理方法、装置及系统
US10057116B2 (en) Method and device for configuring and managing network element equipment, and network element equipment
EP3188409A1 (en) Oam mechanisms for evpn active-active services
US9935781B2 (en) Managing a large network using a single point of configuration
US11290386B2 (en) FlowSpec message processing method and system, and apparatus
WO2015131560A1 (zh) 一种分配分段路由标记的方法和分段路由节点
US20150326469A1 (en) Oam aided explicit path report via igp
CN108964940B (zh) 消息发送方法及装置、存储介质
US20170331641A1 (en) Deployment Of Virtual Extensible Local Area Network
EP3069471B1 (en) Optimized multicast routing in a clos-like network
US11799688B2 (en) Method for managing virtual private network, and device
WO2017141076A1 (en) Stateless multicast protocol for low-power and lossy networks
US10404544B2 (en) Network topology determining method and apparatus, and centralized network status information storage device
US11489752B2 (en) Forwarding entry monitoring method and apparatus
US20230291682A1 (en) Method and device for processing data packet, storage medium, and electronic device
US11601335B2 (en) Methods and systems for neighbor-acknowledged graceful insertion/removal protocol
US11522792B2 (en) Method for discovering forwarding path and related device thereof
US20200403908A1 (en) Fault diagnosis method and apparatus thereof
US9755939B2 (en) Network wide source group tag binding propagation
WO2018000859A1 (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: 19777499

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019777499

Country of ref document: EP

Effective date: 20201008