WO2018188662A1 - 信息通告方法及装置 - Google Patents
信息通告方法及装置 Download PDFInfo
- Publication number
- WO2018188662A1 WO2018188662A1 PCT/CN2018/083100 CN2018083100W WO2018188662A1 WO 2018188662 A1 WO2018188662 A1 WO 2018188662A1 CN 2018083100 W CN2018083100 W CN 2018083100W WO 2018188662 A1 WO2018188662 A1 WO 2018188662A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ioam
- node
- capability information
- bgp
- attribute
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0226—Mapping or translating multiple network management protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
Definitions
- the present disclosure relates to the field of communications, for example, to an information notification method and apparatus.
- IOAM In-situ Operation Administration and Maintenance
- the IOAM is sent along with the data message and does not require additional control plane messages to send OAM data.
- IOAM is typically deployed within a specific domain.
- IOAM can implement complex OAM functions such as multiple path tracking, path verification, and Service-Level Agreement (SLA) authentication.
- SLA Service-Level Agreement
- IOAM can be used in different scenarios, such as Internet Protocol Version 6, IPV6, Virtual Extensible LAN-Generic Protocol Extension (VXLAN-GPE), and service functions.
- IPV6 Virtual Extensible LAN-Generic Protocol Extension
- SFC Service Function Chaining
- SR segment routing
- the IOAM function cannot be implemented through a node outside the IOAM domain.
- the embodiment of the present application provides an information notification method and apparatus, so as to implement node information collected by a predetermined node to support an IOAM function in an IOAM domain.
- the embodiment of the present application provides an information notification method, including:
- the IOAM node encapsulates IOAM capability information using Extended Border Gateway Protocol (BGP)-Link State (LS), or encapsulates IOAM capability information using Network Configuration Protocol (NETCONF);
- BGP Extended Border Gateway Protocol
- LS Link State
- NETCONF Network Configuration Protocol
- the IOAM node sends a BGP-LS message or a NETCONF message carrying the IOAM capability information to a predetermined node, where the predetermined node is a controller in the network management system or a network management system in the network management system.
- the embodiment of the present application provides another information notification method, including:
- the predetermined node receives the BGP-LS packet or the NETCONF message sent by the IOAM node;
- the predetermined node parses the IOAM capability information advertised by the IOAM node from the BGP-LS message or the NETCONF message, where the predetermined node is a controller in the network management system or a network management system in the network management system .
- An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, and includes:
- a processing module configured to encapsulate IOAM capability information by using extended BGP-LS, or encapsulate IOAM capability information by using NETCONF;
- the sending module is configured to send the BGP-LS message or the NETCONF message carrying the IOAM capability information to the predetermined node, where the predetermined node is a controller in the network management system or a network management system in the network management system.
- the embodiment of the present application provides another information notification apparatus, which is applied to a controller in a network management system or a network management system in a network management system, and includes:
- a receiving module configured to receive a BGP-LS packet or a NETCONF message sent by the IOAM node
- a parsing module configured to parse the IOAM capability information advertised by the IOAM node from the BGP-LS message or the NETCONF message, where the predetermined node is a controller in a network management system or a network management system network management.
- the embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, including: a memory and at least one processor; wherein the memory is used to store a program for information notification; the program for information notification is used by the processor.
- the above-mentioned information notification method applied to the IOAM node side is implemented at the time of reading execution.
- the embodiment of the present application provides another information notification apparatus, which is applied to a controller in a network management system or a network management system in a network management system, and includes: a memory and at least one processor; wherein the memory is used to store information for information notification.
- the program; the program for information notification implements the above-described information notification method applied to the predetermined node side when being read and executed by the processor.
- the embodiment of the present application further provides a machine readable medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement the information notification method applied to an IOAM node side.
- the embodiment of the present application further provides another machine readable medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement the above-mentioned controller or network management system applied to the network management system.
- the information notification method of the network management system is also provided.
- the node information supporting the IOAM function in the IOAM domain is collected by the BGP-LS (Border Gateway Protocol-Link State) or the NETCONF, so that the node that the predetermined node collects the IOAM function in the IOAM domain is collected. information.
- FIG. 1 is a flowchart of an information notification method according to an embodiment of the present application.
- FIG. 3 is a schematic diagram of a network connection according to an embodiment of the present application.
- FIG. 4 is a schematic diagram of another network connection according to an embodiment of the present application.
- FIG. 5 is a schematic diagram of still another network connection according to an embodiment of the present application.
- FIG. 6 is a schematic diagram of a format of an IOAM capability TLV according to an embodiment of the present application.
- FIG. 7 is a schematic diagram of a format of a path tracking sub-TLV according to an embodiment of the present application.
- FIG. 8 is a schematic diagram of a format of a path verification sub-TLV according to an embodiment of the present application.
- FIG. 9 is a schematic diagram of an information notification apparatus according to an embodiment of the present application.
- FIG. 10 is another schematic diagram of an information notification apparatus according to an embodiment of the present application.
- the edge node that embeds the OAM data packet in the data packet is also called the IOAM encapsulation node.
- the edge node that leaves the IOAM domain removes the OAM data packet.
- the path verification method of the IOAM is: embedding the OAM data packet in the data packet in the IOAM encapsulation node, and the IOAM forwarding node fills the relevant OAM information into the OAM data packet according to a certain algorithm, the IOAM
- the decapsulation node replaces the OAM information in the OAM data packet with the IOAM forwarding node to check whether the path is consistent with the configured path and removes the OAM data packet.
- the node that implements the path check may be completed by a predetermined node set outside the IOAM domain, for example, the external predetermined node completes the path check based on the complete in-band OAM data message.
- an embodiment of the present application provides an information notification method, including:
- the IOAM node encapsulates the IOAM capability information by using the extended BGP-LS, or encapsulates the IOAM capability information by using the NETCONF.
- the IOAM node may encapsulate the IOAM capability information in two ways, including: encapsulating the IOAM capability information by using an extended Border Gateway Protocol (BGP)-Link State (LS), or Encapsulate IOAM capability information using Network Configuration (NETCONF).
- BGP Border Gateway Protocol
- LS Long Term Evolution
- NETCONF Network Configuration
- Step 102 The IOAM node sends a BGP-LS message or a NETCONF message carrying the IOAM capability information to the predetermined node.
- the IOAM node may use the extended BGP-LS to encapsulate the IOAM capability information, and send the BGP-LS packet carrying the IOAM capability information to the predetermined node; or the IOAM node may encapsulate the IOAM capability information by using the NETCONF.
- a NETCONF message carrying IOAM capability information is sent to the predetermined node.
- the predetermined node may be a controller in the network management system or a network management system in the network management system.
- the IOAM node encapsulates the IOAM capability information by using the extended BGP-LS, and may include: adding, by the IOAM node, at least one BGP-LS attribute; and encapsulating the IOAM capability information by using the added at least one BGP-LS attribute.
- the added at least one BGP-LS attribute may include at least one of the following: a node attribute, a prefix attribute, and a link attribute.
- the IOAM node encapsulating the IOAM capability information by using the NETCONF may include: the IOAM node encapsulates the IOAM capability information in a HELLO message of the NETCONF.
- the IOAM capability information may include a type of IOAM; wherein the types of the IOAM may include: path tracking, path verification, and end-to-end verification.
- the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.
- the IOAM capability information may include at least one of: an IOAM type of the IOAM encapsulation node, and an IOAM of the predetermined IOAM node within the IOAM encapsulation node pre-collected by the IOAM encapsulation node Types of.
- the embodiment of the present application further provides an information notification method, including:
- Step 201 The predetermined node receives the BGP-LS packet or the NETCONF message sent by the IOAM node.
- Step 202 The predetermined node parses the IOAM capability information advertised by the IOAM node from the BGP-LS packet or the NETCONF message.
- the predetermined node may parse the IOAM capability information advertised by the IOAM node from the BGP-LS packet after receiving the BGP-LS packet sent by the IOAM node; or the predetermined node may receive the IOAM node. After the NETCONF message is sent, the IOAM capability information advertised by the IOAM node is parsed from the NETCONF message.
- the predetermined node may be a controller in the network management system or a network management system in the network management system.
- the IOAM capability information may be encapsulated in an added BGP-LS attribute or carried by a NETCONF HELLO message.
- the added BGP-LS attribute may include at least one of the following: a node attribute, a prefix attribute, and a link attribute.
- the IOAM capability information may include the following information: a type of IOAM; wherein the types of the IOAM include: path tracking, path verification, end-to-end verification.
- the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.
- the IOAM capability information may include one or more of the following: an IOAM type of the IOAM encapsulation node, and a predetermined IOAM node within the IOAM domain pre-collected by the IOAM encapsulation node.
- the type of IOAM may include one or more of the following: an IOAM type of the IOAM encapsulation node, and a predetermined IOAM node within the IOAM domain pre-collected by the IOAM encapsulation node. The type of IOAM.
- the IOAM domain shown in FIG. 3 to FIG. 5 may be a domain that supports segment routing (SR).
- SR segment routing
- the multiple IOAM nodes in the figure are also nodes that can support the SR technology.
- an IOAM encapsulation node may be referred to as an SR ingress node
- an IOAM decapsulation node may be referred to as an SR egress node
- an intermediate IOAM forwarding node may be referred to as an SR forwarding node.
- the data message is sent from the IOAM encapsulation node to the IOAM decapsulation node.
- FIG. 3 there is interaction between the IOAM node and the controller (corresponding to the predetermined node described above) in the IOAM domain, that is, the node supporting the SR technology in the SR domain interacts with the controller.
- the controller there is an interaction between the IOAM encapsulation node (or SR ingress node) and the controller.
- Figure 5 there is an interaction between the specified IOAM node and the controller.
- the interaction between the controller and the IOAM nodes depends on the actual deployment, which is not limited in this application.
- the process of the information notification method includes:
- Step 1101 A related node in the IOAM domain (for example, a node supporting IOAM in the IOAM domain in FIG. 3, that is, a node supporting the SR technology in the SR domain, or an IOAM encapsulation node or an SR ingress node in FIG. 4, or specified in FIG.
- the IOAM node carries the Type Length Value (TLV) of the IOAM capability information through the extended BGP-LS attribute to notify the controller of its ability to support IOAM.
- TLV Type Length Value
- the extended BGP-LS attribute may include a newly added node attribute and link attribute; since the SR information is related to the node information and each link may also have its own IOAM capability information,
- the IOAM capability TLV is carried by extending the node attributes and link attributes.
- the definition of node attributes and link attributes can refer to standard RFC7752.
- the detailed format of the IOAM capability TLV can be seen in FIG. 6.
- the Type field identifies the TLV as the IOAM-capability TLV; the Length field is the total length of the TLV; the Option type field is the type of the IOAM, and now the IETF defines the type of the IOAM: In-suit OAM Tracing Option, in-suit OAM Proof of Transit Option, and In-situ OAM Edge-to-Edge Option; Reserved field is reserved To be expanded.
- one or more option sub-TLVs may also be defined.
- the option sub-TLV may include at least one of the following: an in-suit OAM Tracing Option Sub-TLV, an in-suit OAM Proof of Transit Option Sub-TLV, and an In-situ OAM Edge-to-Edge Option Sub-TLV (End-to-End Verification Sub-TLV).
- FIG. 7 is a schematic diagram of a format of an in-suit OAM Tracing Option Sub-TLV.
- the F byte is used to indicate the type of path tracking, including the following two types: Pre-allocated Trace Option and Incremental Trace Option.
- Figure 8 is a schematic diagram of the format of the in-suit OAM Proof of Transit Option Sub-TLV; the path verification sub-TLV defines the following three types of IOAM: Proof of Transit (POT), network service Host service data (NSH metadata) and segment routing path verification (SR POT).
- POT Proof of Transit
- NSH metadata network service Host service data
- SR POT segment routing path verification
- an IOAM encapsulation node (or an SR ingress node) interacts with the controller, the IOAM encapsulation node (or the SR ingress node) passes an Interior Gateway Protocol (IGP).
- IGP Interior Gateway Protocol
- Step 1102 After receiving the BGP-LS packet, the controller analyzes which nodes support the IOAM capability.
- the IOAM domain shown in FIG. 3 to FIG. 5 may also be a Virtual eXtensible Local Area Network (VXLAN) domain, and all the IOAM nodes in the figure support the nodes of the VXLAN technology.
- VXLAN Virtual eXtensible Local Area Network
- the IOAM encapsulation node in the IOAM domain shown in Figure 3, can be called Network Virtual Edge (NVE), the IOAM decapsulation node can be called NVE, and the intermediate IOAM forwarding node can be called VXLAN forwarding. node.
- NVE Network Virtual Edge
- the data message is sent from the IOAM encapsulation node to the IOAM decapsulation node.
- FIG. 3 there is interaction between a node that can support IOAM in the IOAM domain and a controller (corresponding to the predetermined node described above), and an interaction between a node supporting the VXLAN technology in the VXLAN domain and the controller.
- a node that can support IOAM in the IOAM domain and a controller (corresponding to the predetermined node described above), and an interaction between a node supporting the VXLAN technology in the VXLAN domain and the controller.
- Figure 4 there is an interaction between the IOAM Encapsulation Node (or NVE) and the controller.
- Figure 5 there is an interaction between the specified IOAM node (or VXLAN node) and the controller.
- the interaction between the controller and the IOAM nodes depends on the actual deployment, which is not limited in this application.
- the process of the information notification method includes:
- Step 1201 A related node in the IOAM domain (for example, a node supporting IOAM in the IOAM domain in FIG. 3, that is, a node supporting VXLAN technology in the VXLAN domain, or an IOAM encapsulation node or NVE in FIG. 4, or an IOAM specified in FIG.
- the node or VXLAN node notifies the controller of its ability to support IOAM by extending the IOAM capability parameter in the NETCONF (Network Configuration Protocol).
- NETCONF Network Configuration Protocol
- the two parties when the NETCONF establishes a link between the relevant node and the controller in the IOAM domain, the two parties send HELLO packets to each other.
- the HELLO packet sent by the relevant node in the IOAM domain to the controller carries the capability information of the relevant node in the IOAM domain, for example, the following Extensible Markup Language (XML) format message, where the bold part is new.
- XML Extensible Markup Language
- Types of IOAM include: in-suit OAM Tracing Option, in-suit OAM Proof of Transit Option, and In-situ OAM Edge-to-Edge Option.
- the path tracking type includes Pre-allocated Trace Option and Incremental Trace Option.
- the IOAM encapsulation node can collect the IOAM capability of the relevant node in the IOAM domain through the IGP. Unified reporting to the controller.
- Step 1202 After receiving the NETCONF message carrying the IOAM capability parameter, the controller parses to know which nodes support the IOAM capability.
- the IOAM domain in Figures 3 through 5 may be a BIER domain, and all IOAM nodes in the figure are also nodes supporting BIER technology.
- the IOAM encapsulation node may be called an ingress node of the BIER
- the IOAM decapsulation node may be called an exit node of the BIER
- the intermediate IOAM forwarding node may be called a forwarding node of the BIER.
- the data message is sent from the IOAM encapsulation node to the IOAM decapsulation node.
- FIG. 3 there is interaction between the node supporting the IOAM in the IOAM domain and the controller (corresponding to the predetermined node described above), that is, the node supporting the BIER technology in the BIER domain interacts with the controller.
- the controller corresponding to the predetermined node described above
- the IOAM encapsulation node or BIER ingress node
- the controller there is an interaction between the specified IOAM node and the controller.
- the interaction between the controller and which IOAM nodes depends on the actual deployment, which is not limited in this application.
- the process of the information notification method includes:
- Step 1301 A related node in the IOAM domain (for example, a node supporting IOAM in the IOAM domain in FIG. 3, that is, a node supporting BIER technology in the BIER domain, or an IOAM encapsulation node or a BIER ingress node in FIG. 4, or specified in FIG.
- the IOAM node carries the type length value TLV of the IOAM capability information through the extended BGP-LS attribute to inform the controller of its ability to support IOAM.
- the extended BGP-LS attribute may include a newly added prefix attribute; since the BIER information is associated with a prefix, in the BIER scenario, the Prefix Attribute TLV is extended to carry the IOAM capability TLV.
- the format of the BGP-LS Prefix Attribute TLV can be found in the standard RFC7752.
- the detailed format of the IOAM capability TLV can be seen in FIG. 6.
- the Type field identifies the TLV as the IOAM-capability TLV; the Length field is the total length of the TLV; the Option type field is the IOAM type, and now the IETF defines the following IOAM types: in-suit OAM Tracing Option (path tracking) ), in-suit OAM Proof of Transit Option and In-situ OAM Edge-to-Edge Option; Reserved field, reserved field, to be extended.
- one or more Option Sub-TLVs may also be defined.
- the option sub-TLV may include at least one of the following: an in-suit OAM Tracing Option Sub-TLV, an in-suit OAM Proof of Transit Option Sub-TLV, and an In-situ OAM.
- Edge-to-Edge Option Sub-TLV End-to-End Verification Sub-TLV.
- Figure 7 is a schematic diagram of the format of the in-suit OAM Tracing Option Sub-TLV.
- the F-byte is used to indicate the type of path tracking, including the following two types: Pre-allocated Trace Option. ) and Incremental Trace Option.
- FIG. 8 is a schematic diagram of a format of an in-suit OAM Proof of Transit Option Sub-TLV.
- the Path Verifier sub-TLV includes the following three types of IOAM defined: Generic POT, NSH metadata, and SR POT.
- the IOAM encapsulation node or the BIER ingress node collects the support of the relevant node in the IOAM domain through the IGP.
- the IOAM capability is uniformly reported to the controller.
- Step 1302 After receiving the BGP-LS packet, the controller analyzes which nodes support the IOAM capability.
- the embodiment of the present application further provides an information notification apparatus, which is applied to an IOAM node, and includes:
- the processing module 901 is configured to encapsulate the IOAM capability information by using the extended BGP-LS, or encapsulate the IOAM capability information by using the network configuration protocol NETCONF;
- the sending module 902 is configured to send the BGP-LS message or the NETCONF message carrying the IOAM capability information to the predetermined node.
- the predetermined node is a controller in the network management system or a network management system in the network management system.
- the processing module 901 can be configured to utilize the extended BGP-LS to encapsulate IOAM capability information in the following manner:
- Adding at least one BGP-LS attribute encapsulating the IOAM capability information by using the added at least one BGP-LS attribute; wherein the added at least one BGP-LS attribute includes at least one of the following: a node attribute, a prefix attribute, and a link attribute.
- the processing module 901 can be configured to encapsulate IOAM capability information with NETCONF by encapsulating the IOAM capability information in a HELLO message of the NETCONF.
- the IOAM capability information may include a type of IOAM; wherein the types of the IOAM may include: path tracking, path verification, and end-to-end verification.
- the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.
- the IOAM capability information may include at least one of: an IOAM type of the IOAM encapsulation node, and an IOAM of the predetermined IOAM node within the IOAM encapsulation node pre-collected by the IOAM encapsulation node Types of.
- the embodiment of the present application further provides an information notification apparatus, which is applied to a predetermined node, and includes:
- the receiving module 1001 is configured to receive a BGP-LS packet sent by the IOAM node or a network configuration protocol NETCONF message;
- the parsing module 1002 is configured to parse the IOAM capability information advertised by the IOAM node from the BGP-LS packet or the NETCONF message.
- the predetermined node is a controller in the network management system or a network management system in the network management system.
- the IOAM capability information may be encapsulated in the added BGP-LS attribute or carried by the NETCONF HELLO message.
- the added BGP-LS attribute may include at least one of the following: a node attribute, a prefix attribute, and a link attribute. .
- the IOAM capability information may include a type of the IOAM, where the types of the IOAM include: path tracking, path verification, and end-to-end verification.
- the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.
- the IOAM capability information may include at least one of: an IOAM type of the IOAM encapsulation node, and an IOAM of the predetermined IOAM node within the IOAM encapsulation node pre-collected by the IOAM encapsulation node Types of.
- the embodiment of the present application further provides an information notification apparatus, which is applied to an IOAM node, including: a memory and at least one processor; wherein the memory is configured to store a program for information notification; the program for information notification is used by the processor
- the information notification method of the above IOAM node side is implemented when the read is executed.
- the embodiment of the present application further provides an information notification apparatus, which is applied to an IOAM node, including: a transmission module, a memory, and at least one processor; wherein the memory is configured to store a program for information notification; the program for information notification is When executed by the processor, do the following:
- the BGP-LS packet or the NETCONF message carrying the IOAM capability information is sent to the predetermined node through the transmission module.
- the processor may include, but is not limited to, a processing device such as a microprocessor (MCU) or a programmable logic device (FPGA).
- MCU microprocessor
- FPGA programmable logic device
- an IOAM node may also include more or fewer components or have different configurations.
- the memory may be set as a software program and a module for storing application software, such as program instructions or modules corresponding to the information notification method of the present application, and the processor executes various functional applications and data processing by running software programs and modules stored in the memory. That is, the above method is implemented.
- the memory can include high speed random access memory and can also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
- the memory can further include memory remotely located relative to the processor, which can be connected to the IOAM node over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
- the transmission module can be arranged to receive or transmit data via a network.
- the transmission module can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.
- RF Radio Frequency
- the embodiment of the present application further provides an information notification apparatus, which is applied to a predetermined node, including: a memory and at least one processor; wherein the memory is configured to store a program for information notification; the program for information notification is in the processor.
- the information notification method of the above-mentioned predetermined node side is implemented at the time of reading execution.
- the embodiment of the present application further provides an information notification apparatus, which is applied to a predetermined node (for example, a controller or a network management system in a network management system), including: a transmission module, a memory, and at least one processor; wherein the memory is configured to be stored for storage
- a predetermined node for example, a controller or a network management system in a network management system
- the memory is configured to be stored for storage
- a program for information notification when being read and executed by the processor, performs the following operations:
- the IOAM capability information advertised by the IOAM node is parsed from the BGP-LS message or the NETCONF message.
- the processor may include, but is not limited to, a processing device such as an MCU or an FPGA.
- a predetermined node may also include more or fewer components or have different configurations.
- the memory may be configured as a software program and a module for storing application software, such as program instructions or modules corresponding to the information notification method in the embodiment of the present application, and the processor executes various functional applications by running a software program and a module stored in the memory. And data processing, that is, to achieve the above method.
- the memory can include high speed random access memory and can also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
- the memory can further include memory remotely located relative to the processor, which can be connected to the predetermined node over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
- the transmission module can be arranged to receive or transmit data via a network.
- the transmission module can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.
- RF Radio Frequency
- the embodiment of the present application further provides a machine readable medium storing a computer program, which is implemented by the processor to implement an information notification method on an IOAM node side or a predetermined node side.
- a program to instruct related hardware e.g., a processor
- a machine readable medium such as a read only memory, disk or optical disk.
- Computer readable storage medium e.g., all or part of the steps of the above embodiments may also be implemented using at least one integrated circuit.
- each module or unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. Or instructions to implement their respective functions. This application is not limited to any specific combination of hardware and software.
- the embodiment of the invention can implement the node information collected by the predetermined node to support the IOAM function in the IOAM domain.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Multimedia (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
公开了一种信息通告方法及装置。信息通告方法包括:IOAM节点利用扩展的BGP-LS封装IOAM能力信息,或者利用NETCONF封装IOAM能力信息;并将携带IOAM能力信息的BGP-LS报文或NETCONF消息发送给预定节点。
Description
本公开涉及通信领域,例如涉及一种信息通告方法及装置。
互联网工程任务组(Internet Engineering Task Force,IETF)提出了带内操作管理维护(In-situ Operation Administration and Maintenance,IOAM)。IOAM随着数据报文一起发送,不需要额外的控制面报文发送OAM数据。IOAM一般是在一个特定的域内部署。IOAM可以实现多种路径跟踪、路径验证、服务等级协议(Service-Level Agreement,SLA)验证等复杂的OAM功能。
根据部署,IOAM可以在不同的场景中使用,比如在互联网协议版本6(Internet Protocol Version 6,IPV6)、虚拟扩展局域网的通用协议扩展(Virtual Extensible LAN-Generic Protocol Extension,VXLAN-GPE)、服务功能链(Service Function Chaining,SFC)及分段路由(segment routing,SR)等场景下。但是,在IOAM场景下,通过IOAM域外的节点还不能实现IOAM功能。
发明内容
本申请实施例提供一种信息通告方法及装置,以实现预定节点收集到IOAM域内支持IOAM功能的节点信息。
本申请实施例提供了一种信息通告方法,包括:
IOAM节点利用扩展的边界网关协议(BGP)-链路状态(LS)封装IOAM能力信息,或者利用网络配置协议(NETCONF)封装IOAM能力信息;
所述IOAM节点将携带所述IOAM能力信息的BGP-LS报文或NETCONF消息发送给预定节点,其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。本申请实施例提供了另一种信息通告方法,包括:
预定节点接收IOAM节点发送的BGP-LS报文或者NETCONF消息;
所述预定节点从所述BGP-LS报文或者所述NETCONF消息中解析所述 IOAM节点通告的IOAM能力信息,其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。
本申请实施例提供一种信息通告装置,应用于IOAM节点,包括:
处理模块,用于利用扩展的BGP-LS封装IOAM能力信息,或者利用NETCONF封装IOAM能力信息;
发送模块,用于将携带所述IOAM能力信息的BGP-LS报文或NETCONF消息发送给预定节点,其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。
本申请实施例提供了另一种信息通告装置,应用于网络管理***中的控制器或者网络管理***中的网管,包括:
接收模块,用于接收IOAM节点发送的BGP-LS报文或者NETCONF消息;
解析模块,用于从所述BGP-LS报文或者所述NETCONF消息中解析所述IOAM节点通告的IOAM能力信息,其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。
本申请实施例提供了一种信息通告装置,应用于IOAM节点,包括:存储器以及至少一个处理器;其中,存储器用于存储用于信息通告的程序;该用于信息通告的程序在被处理器读取执行时实现上述应用于IOAM节点侧的信息通告方法。
本申请实施例提供了另一种信息通告装置,应用于网络管理***中的控制器或者网络管理***中的网管,包括:存储器以及至少一个处理器;其中,存储器用于存储用于信息通告的程序;该用于信息通告的程序在被处理器读取执行时,实现上述应用于预定节点侧的信息通告方法。
本申请实施例还提供了一种机器可读介质,其上存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现上述应用于IOAM节点侧的信息通告方法。
本申请实施例还提供了另一种机器可读介质,其上存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现上述应用于网络管理***中的控制器或者网络管理***中的网管的信息通告方法。
本申请实施例通过扩展BGP-LS(Border Gateway Protocol-Link State,边界网关协议链路状态)或者NETCONF来收集IOAM域内支持IOAM功能的节点 信息,从而实现预定节点收集到IOAM域内支持IOAM功能的节点信息。
图1为本申请实施例的信息通告方法的流程图;
图2为本申请实施例的信息通告方法的另一流程图;
图3为本申请实施例的一种网络连接示意图;
图4为本申请实施例的另一种网络连接示意图;
图5为本申请实施例的再一种网络连接示意图;
图6为本申请实施例的IOAM能力TLV的格式示意图;
图7为本申请实施例的路径跟踪子TLV的格式示意图;
图8为本申请实施例的路径验证子TLV的格式示意图;
图9为本申请实施例的信息通告装置的示意图;
图10为本申请实施例的信息通告装置的另一示意图。
在IOAM域的多个边缘节点中,将OAM数据报文嵌入在数据报文中的边缘节点又称为IOAM封装节点,要离开IOAM域的边缘节点将OAM数据报文移除,该节点又称为IOAM解封装节点。在一实施例中,IOAM的路径验证方法是:在IOAM封装节点,将OAM数据报文嵌入在数据报文中,IOAM转发节点根据一定算法将相关的OAM信息填入OAM数据报文中,IOAM解封装节点根据IOAM转发节点填入OAM数据报文中的OAM信息校验路径是否与配置的路径一致,并将OAM数据报文移除。这里,实现路径校验的节点可以由IOAM域外设置的预定节点来完成,譬如外置的预定节点基于完整的带内的OAM数据报文来完成路径校验。
如图1所示,本申请实施例提供了一种信息通告方法,包括:
步骤101,IOAM节点利用扩展的BGP-LS封装IOAM能力信息,或者利用NETCONF封装IOAM能力信息。
在示例性实施方式中,IOAM节点封装IOAM能力信息可以有两种方式,包括:利用扩展的边界网关协议(Border Gateway Protocol,BGP)-链路状态(Link State,LS)封装IOAM能力信息,或者,利用网络配置协议(Network Configuration, NETCONF)封装IOAM能力信息。
步骤102,IOAM节点将携带IOAM能力信息的BGP-LS报文或NETCONF消息发送给预定节点。
在示例性实施方式中,IOAM节点可以利用扩展的BGP-LS封装IOAM能力信息,并将携带IOAM能力信息的BGP-LS报文发送给预定节点;或者,IOAM节点可以利用NETCONF封装IOAM能力信息,并将携带IOAM能力信息的NETCONF消息发送给预定节点。
在示例性实施方式中,预定节点可以为网络管理***中的控制器或者网络管理***中的网管。
在示例性实施方式中,IOAM节点利用扩展的BGP-LS封装IOAM能力信息,可以包括:IOAM节点增加至少一个BGP-LS属性;利用增加的至少一个BGP-LS属性封装IOAM能力信息。
在示例性实施方式中,增加的至少一个BGP-LS属性可以包括以下至少之一:节点属性、前缀属性、以及链路属性。
在示例性实施方式中,IOAM节点利用NETCONF封装IOAM能力信息,可以包括:IOAM节点将IOAM能力信息封装在NETCONF的HELLO消息中。
在示例性实施方式中,IOAM能力信息可以包括IOAM的类型;其中,IOAM的类型可以包括:路径跟踪、路径验证、以及端到端的验证。
在示例性实施方式中,IOAM能力信息还可以包括以下信息至少之一:路径跟踪的子类型、路径验证的子类型、以及端到端的验证子类型。
在示例性实施方式中,当IOAM节点为IOAM封装节点时,IOAM能力信息可以包括以下至少一项:IOAM封装节点的IOAM的类型、及IOAM封装节点预先收集的IOAM域内的预定IOAM节点的IOAM的类型。
如图2所示,本申请实施例还提供了一种信息通告方法,包括:
步骤201,预定节点接收IOAM节点发送的BGP-LS报文或者NETCONF消息。
步骤202,预定节点从BGP-LS报文或者NETCONF消息中解析IOAM节点通告的IOAM能力信息。
在示例性实施方式中,预定节点可以在收到IOAM节点发送的BGP-LS报文之后,从BGP-LS报文中解析IOAM节点通告的IOAM能力信息;或者,预 定节点可以在收到IOAM节点发送的NETCONF消息之后,从NETCONF消息中解析IOAM节点通告的IOAM能力信息。
在示例性实施方式中,预定节点可以为网络管理***中的控制器或者网络管理***中的网管。
在示例性实施方式中,IOAM能力信息可以封装在增加的BGP-LS属性中,或者,由NETCONF的HELLO消息携带。
在示例性实施方式中,增加的BGP-LS属性可以包括以下至少之一:节点属性、前缀属性、以及链路属性。
在示例性实施方式中,IOAM能力信息可以包括以下信息:IOAM的类型;其中,所述IOAM的类型包括:路径跟踪、路径验证、端到端的验证。
在示例性实施方式中,IOAM能力信息还可以包括以下至少之一信息:路径跟踪的子类型、路径验证的子类型、以及端到端的验证子类型。
在示例性实施方式中,当IOMA节点为IOAM封装节点时,IOAM能力信息可以包括以下一项或多项:IOAM封装节点的IOAM的类型、以及IOAM封装节点预先收集的IOAM域内的预定IOAM节点的IOAM的类型。
在一实施例中,图3至图5所示的IOAM域可以是支持分段路由(segment routing,SR)的域,图中的多个IOAM节点也是可以支持SR技术的节点。
以图3为例,在图3所示的IOAM域,IOAM封装节点可以叫做SR入口节点,IOAM解封装节点可以叫做SR出口节点,中间的IOAM转发节点可以叫做SR转发节点。如图3所示,数据报文从IOAM封装节点发往IOAM解封装节点。
在图3中,IOAM域内支持IOAM节点与控制器(对应上述的预定节点)之间有交互,也即SR域内支持SR技术的节点与控制器之间有交互。在图4中,IOAM封装节点(或SR入口节点)与控制器之间有交互。在图5中,指定的IOAM节点与控制器之间有交互。
在另一实施例中,控制器与哪些IOAM节点之间进行交互取决于实际的部署,本申请对此不作限定。
在本实施例中,信息通告方法的流程,包括:
步骤1101,IOAM域内的相关节点(比如,图3中IOAM域内支持IOAM的节点,也即SR域内支持SR技术的节点,或者,图4中IOAM封装节点或 SR入口节点,或者,图5中指定的IOAM节点)通过扩展的BGP-LS属性携带IOAM能力信息的类型长度值(Type Length Value,TLV),向控制器通告其支持IOAM能力。
在一实施例中,扩展的BGP-LS的属性可以包括新增加的一种节点属性及链路属性;由于SR的信息与节点信息相关以及每条链路也可以有自己的IOAM能力信息,所以在SR场景下,通过扩展节点属性及链路属性来携带IOAM能力TLV。其中,关于节点属性与链路属性的定义可以参照标准RFC7752。
在一实施例中,IOAM能力TLV的详细格式可以参见图6。在图6中,类型(Type)字段标识本TLV为IOAM-capability TLV;长度(Length)字段为本TLV的总长度;选项类型(Option type)字段为IOAM的类型,现在IETF定义IOAM的类型:in-suit OAM Tracing Option(路径跟踪)、in-suit OAM Proof of Transit Option(路径验证)和In-situ OAM Edge-to-Edge Option(端到端的验证);保留(Reserved)字段为预留字段,待扩展。
在一实施例中,还可以定义一个或者多个选项子TLV(Option Sub-TLV)。其中,选项子TLV可以包括以下至少之一:有in-suit OAM Tracing Option Sub-TLV(路径跟踪子TLV)、in-suit OAM Proof of Transit Option Sub-TLV(路径验证子TLV)和In-situ OAM Edge-to-Edge Option Sub-TLV(端到端的验证子TLV)。
图7为路径跟踪子TLV(in-suit OAM Tracing Option Sub-TLV)的格式示意图。F字节用于表示路径跟踪的类型,包括以下两种类型:预分配跟踪(Pre-allocated Trace Option)及增量跟踪(Incremental Trace Option)。
图8为路径验证子TLV(in-suit OAM Proof of Transit Option Sub-TLV)的格式示意图;路径验证子TLV定义了以下三种IOAM的类型:通用路径验证(Proof of Transit,POT)、网络服务主机元数据(network service Host,NSH metadata)及段路由路径验证(SR POT)。
本发明实施例中,如图4所示,如果由IOAM封装节点(或SR入口节点)与控制器进行交互,那么IOAM封装节点(或SR入口节点)会通过内部网关协议(Interior Gateway Protocol,IGP)收集到IOAM域内的相关节点的支持IOAM能力,统一上报给控制器。
步骤1102,控制器接收到BGP-LS报文后,解析了解哪些节点支持IOAM 能力。
在一实施例中,图3至图5所示的IOAM域也可以是可扩展虚拟局域网(Virtual eXtensible Local Area Network,VXLAN)域,图中的所有的IOAM节点支持VXLAN技术的节点。
以图3为例,在图3所示的IOAM域中,IOAM封装节点可以叫做网络边缘设备(Network Virtual Edge,NVE),IOAM解封装节点可以叫做NVE,中间的IOAM转发节点可以叫做VXLAN的转发节点。如图3所示,数据报文从IOAM封装节点发往IOAM解封装节点。
在图3中,IOAM域内可以支持IOAM的节点与控制器(对应上述的预定节点)之间有交互,以及VXLAN域内支持VXLAN技术的节点与控制器之间有交互。在图4中,IOAM封装节点(或NVE)与控制器之间有交互。在图5中,指定的IOAM节点(或VXLAN节点)与控制器之间有交互。
在另一实施例中,控制器与哪些IOAM节点之间进行交互取决于实际的部署,本申请对此不作限定。
在本实施例中,信息通告方法的流程包括:
步骤1201,IOAM域内的相关节点(比如,图3中IOAM域内支持IOAM的节点,也即VXLAN域内支持VXLAN技术的节点,或者,图4中IOAM封装节点或NVE,或者,图5中指定的IOAM节点或VXLAN节点)通过扩展NETCONF(网络配置协议)中携带IOAM能力参数,向控制器通告其支持IOAM能力。
在一实施例中,NETCONF在IOAM域内的相关节点和控制器建立链接时,双方互相向对端发送HELLO报文。IOAM域内的相关节点向控制器发送的HELLO报文中携带IOAM域内的相关节点的能力信息,例如可以是以下可扩展标记语言(Extensible Markup Language,XML)格式报文,其中,粗体部分是新加的IOAM域内相关节点的IOAM能力相关信息,IOAM能力相关信息包括IOAM的类型。IOAM的类型包括:in-suit OAM Tracing Option(路径跟踪)、in-suit OAM Proof of Transit Option(路径验证)和In-situ OAM Edge-to-Edge Option(端到端的验证。在一实施例中,in-suit OAM Tracing Option类型下,路径跟踪类型包括:预分配跟踪(Pre-allocated Trace Option)及增量跟踪(Incremental Trace Option)。
在一实施例中,如图4所示,如果由IOAM封装节点(或NVE)与控制器进行交互,那么IOAM封装节点(或NVE)可以通过IGP收集到IOAM域内 的相关节点的支持IOAM能力,统一上报给控制器。
步骤1202,控制器接收到携带IOAM能力参数的NETCONF消息后,解析了解哪些节点支持IOAM能力。
在一实施例中,图3至图5中的IOAM域可以是BIER域,图中的所有的IOAM节点也是支持BIER技术的节点。
以图3为例,在图3所示的IOAM域中,IOAM封装节点可以叫做BIER的入口节点,IOAM解封装节点可以叫做BIER的出口节点,中间的IOAM转发节点可以叫做BIER的转发节点。如图3所示,数据报文从IOAM封装节点发往IOAM解封装节点。
在图3中,IOAM域内支持IOAM的节点与控制器(对应上述的预定节点)之间有交互,也即BIER域内支持BIER技术的节点与控制器之间有交互。在图4中,IOAM封装节点(或BIER入口节点)与控制器之间有交互。在图5中,指定的IOAM节点与控制器之间有交互。
在另一实施例中,控制器与哪些IOAM节点之间进行交互取决于实际的部署,本申请对此并不限定。
在本实施例中,信息通告方法的流程包括:
步骤1301,IOAM域内的相关节点(比如,图3中IOAM域内支持IOAM的节点,也即BIER域内支持BIER技术的节点,或者,图4中IOAM封装节点或BIER入口节点,或者,图5中指定的IOAM节点)通过扩展的BGP-LS属性携带IOAM能力信息的类型长度值TLV,向控制器通告其支持IOAM能力。
这里扩展的BGP-LS的属性可以包括新增加的一种前缀属性;由于BIER信息与前缀(prefix)相关联,所以在BIER场景中,扩展Prefix Attribute TLV来携带IOAM能力TLV。其中,BGP-LS Prefix Attribute TLV的格式可以参见标准RFC7752。
在一实施例中,IOAM能力TLV的详细格式可以参见图6。在图6中,Type字段标识本TLV为IOAM-capability TLV;Length字段为本TLV的总长度;Option type字段为IOAM的类型,现在IETF定义以下IOAM的类型:in-suit OAM Tracing Option(路径跟踪)、in-suit OAM Proof of Transit Option(路径验证)和In-situ OAM Edge-to-Edge Option(端到端的验证);Reserved字段,预留字段,待扩展。
在一实施例中,还可以定义一个或者多个Option Sub-TLV。其中,选项子TLV可以包括以下至少之一:in-suit OAM Tracing Option Sub-TLV(路径跟踪子TLV)、in-suit OAM Proof of Transit Option Sub-TLV(路径验证子TLV)以及In-situ OAM Edge-to-Edge Option Sub-TLV(端到端的验证子TLV)。
图7为路径跟踪子TLV(in-suit OAM Tracing Option Sub-TLV)的格式示意图;其中,F字节用于表示路径跟踪的类型,包括以下两种类型:预分配跟踪(Pre-allocated Trace Option)及增量跟踪(Incremental Trace Option)。
图8为路径验证子TLV(in-suit OAM Proof of Transit Option Sub-TLV)的格式示意图。路径验证子TLV包括定义了以下三种IOAM的类型:通用POT、NSH metadata及SR POT。
本实施例中,如图4所示,如果由IOAM封装节点(或BIER入口节点)与控制器之间有交互,那么IOAM封装节点或BIER入口节点会通过IGP收集到IOAM域内的相关节点的支持IOAM能力,统一上报给控制器。
步骤1302,控制器接收到BGP-LS报文后,解析了解哪些节点支持IOAM能力。
此外,如图9所示,本申请实施例还提供一种信息通告装置,应用于IOAM节点,包括:
处理模块901,设置为利用扩展的BGP-LS封装IOAM能力信息,或者利用网络配置协议NETCONF封装IOAM能力信息;
发送模块902,设置为将携带IOAM能力信息的BGP-LS报文或NETCONF消息发送给预定节点。
其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。
在示例性实施方式中,处理模块901可以设置为通过以下方式利用扩展的BGP-LS封装IOAM能力信息:
增加至少一个BGP-LS属性;利用增加的至少一个BGP-LS属性封装IOAM能力信息;其中,增加的至少一个BGP-LS属性包括以下至少之一:节点属性、前缀属性、以及链路属性。
在示例性实施方式中,处理模块901可以设置为通过以下方式利用NETCONF封装IOAM能力信息:将IOAM能力信息封装在NETCONF的 HELLO消息中。
在示例性实施方式中,IOAM能力信息可以包括IOAM的类型;其中,IOAM的类型可以包括:路径跟踪、路径验证、以及端到端的验证。
在示例性实施方式中,IOAM能力信息还可以包括以下至少之一信息:路径跟踪的子类型、路径验证的子类型、端到端的验证子类型。
在示例性实施方式中,当IOMA节点为IOAM封装节点时,IOAM能力信息可以包括以下至少一项:IOAM封装节点的IOAM的类型、及IOAM封装节点预先收集的IOAM域内的预定IOAM节点的IOAM的类型。
如图10所示,本申请实施例还提供一种信息通告装置,应用于预定节点,包括:
接收模块1001,设置为接收IOAM节点发送的BGP-LS报文或者网络配置协议NETCONF消息;
解析模块1002,设置为从BGP-LS报文或者NETCONF消息中解析IOAM节点通告的IOAM能力信息。
其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。
其中,IOAM能力信息可以封装在增加的BGP-LS属性中,或者,由NETCONF的HELLO消息携带;其中,增加的BGP-LS属性可以包括以下至少之一:节点属性、前缀属性、以及链路属性。
其中,IOAM能力信息可以包括IOAM的类型;其中,所述IOAM的类型包括:路径跟踪、路径验证、以及端到端的验证。
其中,IOAM能力信息还可以包括以下信息至少之一:路径跟踪的子类型、路径验证的子类型、以及端到端的验证子类型。
在示例性实施方式中,当IOMA节点为IOAM封装节点时,IOAM能力信息可以包括以下至少一项:IOAM封装节点的IOAM的类型、及IOAM封装节点预先收集的IOAM域内的预定IOAM节点的IOAM的类型。
关于上述信息通告装置的相关说明可以参照上述方法实施例的说明,故于此不再赘述。
本申请实施例还提供一种信息通告装置,应用于IOAM节点,包括:存储器以及至少一个处理器;其中,存储器设置为存储用于信息通告的程序;该用于信 息通告的程序在被处理器读取执行时实现上述IOAM节点侧的信息通告方法。
本申请实施例还提供一种信息通告装置,应用于IOAM节点,包括:传输模块、存储器以及至少一个处理器;其中,存储器设置为存储用于信息通告的程序;该用于信息通告的程序在被处理器读取执行时,执行以下操作:
利用扩展的BGP-LS封装IOAM能力信息,或者利用NETCONF封装IOAM能力信息;通过传输模块将携带IOAM能力信息的BGP-LS报文或NETCONF消息发送给预定节点。
其中,处理器可以包括但不限于微处理器(MCU)或可编程逻辑器件(FPGA)等的处理装置。
本领域普通技术人员可以理解,上述结构仅为示意,其并不对上述电子装置的结构造成限定。例如,IOAM节点还可包括更多或者更少的组件,或者具有不同的配置。
存储器可设置为存储应用软件的软件程序以及模块,如本申请的信息通告方法对应的程序指令或模块,处理器通过运行存储在存储器内的软件程序以及模块,从而执行各种功能应用以及数据处理,即实现上述的方法。存储器可包括高速随机存储器,还可包括非易失性存储器,如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中,存储器可还包括相对于处理器远程设置的存储器,这些远程存储器可以通过网络连接至IOAM节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输模块可以设置为经由一个网络接收或者发送数据。在一个实例中,传输模块可以为射频(Radio Frequency,RF)模块,其设置为通过无线方式与互联网进行通信。
本申请实施例还提供一种信息通告装置,应用于预定节点,包括:存储器以及至少一个处理器;其中,存储器设置为存储用于信息通告的程序;该用于信息通告的程序在被处理器读取执行时实现上述预定节点侧的信息通告方法。
本申请实施例还提供一种信息通告装置,应用于预定节点(比如,网络管理***中的控制器或网管),包括:传输模块、存储器以及至少一个处理器;其中,存储器设置为存储用于信息通告的程序;该用于信息通告的程序在被处理器读取执行时,执行以下操作:
接收IOAM节点发送的BGP-LS报文或者NETCONF消息;从BGP-LS报 文或者NETCONF消息中解析IOAM节点通告的IOAM能力信息。
其中,处理器可以包括但不限于MCU或FPGA等的处理装置。
本领域普通技术人员可以理解,上述结构仅为示意,其并不对上述电子装置的结构造成限定。例如,预定节点还可包括更多或者更少的组件,或者具有不同的配置。
存储器可设置为存储应用软件的软件程序以及模块,如本申请实施例中的信息通告方法对应的程序指令或模块,处理器通过运行存储在存储器内的软件程序以及模块,从而执行各种功能应用以及数据处理,即实现上述的方法。存储器可包括高速随机存储器,还可包括非易失性存储器,如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中,存储器可还包括相对于处理器远程设置的存储器,这些远程存储器可以通过网络连接至预定节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输模块可以设置为经由一个网络接收或者发送数据。在一个实例中,传输模块可以为射频(Radio Frequency,RF)模块,其设置为通过无线方式与互联网进行通信。
此外,本申请实施例还提供一种机器可读介质,存储有计算机程序,所述计算机程序被处理器执行时实现IOAM节点侧或者预定节点侧的信息通告方法。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成,所述程序可以存储于机器可读介质中,如只读存储器、磁盘或光盘等计算机可读存储介质。在示例性实施方式中,上述实施例的全部或部分步骤也可以使用至少一个集成电路来实现。相应地,上述实施例中的各模块或单元可以采用硬件的形式实现,例如通过集成电路来实现其相应功能,也可以采用软件功能模块的形式实现,例如通过处理器执行存储于存储器中的程序或指令来实现其相应功能。本申请不限制于任何特定形式的硬件和软件的结合。
本发明实施例可以实现预定节点收集到IOAM域内支持IOAM功能的节点信息。
Claims (28)
- 一种信息通告方法,包括:带内操作管理维护IOAM节点利用扩展的边界网关协议BGP-链路状态LS封装IOAM能力信息,或者利用网络配置协议NETCONF封装IOAM能力信息;所述IOAM节点将携带所述IOAM能力信息的BGP-LS报文或NETCONF消息发送给预定节点。
- 根据权利要求1所述的方法,其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。
- 根据权利要求1所述的方法,其中,所述IOAM节点利用扩展的BGP-LS封装IOAM能力信息,包括:所述IOAM节点增加至少一个BGP-LS属性;利用增加的所述至少一个BGP-LS属性封装所述IOAM能力信息。
- 根据权利要求3所述的方法,其中,所述增加至少一个的BGP-LS属性包括以下至少之一:节点属性、前缀属性、以及链路属性。
- 根据权利要求1所述的方法,其中,所述IOAM节点利用NETCONF封装IOAM能力信息,包括:所述IOAM节点将所述IOAM能力信息封装在NETCONF的HELLO消息中。
- 根据权利要求1至5任一项所述的方法,其中,所述IOAM能力信息包括IOAM的类型;其中,所述IOAM的类型包括:路径跟踪、路径验证、以及端到端的验证。
- 根据权利要求6所述的方法,其中,所述IOAM能力信息还包括以下信息至少之一:路径跟踪的子类型、路径验证的子类型、以及端到端的验证子类型。
- 根据权利要求6所述的方法,其中,当所述IOAM节点为IOAM封装节点时,所述IOAM能力信息包括以下至少一项:所述IOAM封装节点的IOAM的类型、及所述IOAM封装节点预先收集的IOAM域内的预定IOAM节点的IOAM的类型。
- 一种信息通告方法,包括:预定节点接收带内操作管理维护IOAM节点发送的边界网关协议BGP-链路状态LS报文或者网络配置协议NETCONF消息;所述预定节点从所述BGP-LS报文或者所述NETCONF消息中解析所述IOAM节点通告的IOAM能力信息。
- 根据权利要求9所述的方法,其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。
- 根据权利要求9所述的方法,其中,所述IOAM能力信息封装在增加的BGP-LS属性中,或者,由NETCONF的HELLO消息携带。
- 根据权利要求11所述的方法,其中,所述增加的BGP-LS属性包括以下至少之一:节点属性、前缀属性、以及链路属性。
- 根据权利要求9至12任一项所述的方法,其中,所述IOAM能力信息包括IOAM的类型;其中,所述IOAM的类型包括:路径跟踪、路径验证、以及端到端的验证。
- 根据权利要求13所述的方法,其中,所述IOAM能力信息还包括以下信息至少之一:路径跟踪的子类型、路径验证的子类型、以及端到端的验证子类型。
- 根据权利要求13所述的方法,其中,当所述IOMA节点为IOAM封装节点时,所述IOAM能力信息包括以下至少一项:所述IOAM封装节点的IOAM的类型、及所述IOAM封装节点预先收集的IOAM域内的预定IOAM节点的IOAM的类型。
- 一种信息通告装置,应用于带内操作管理维护IOAM节点,包括:处理模块,设置为利用扩展的边界网关协议BGP-链路状态LS封装IOAM能力信息,或者利用网络配置协议NETCONF封装IOAM能力信息;发送模块,设置为将携带所述IOAM能力信息的BGP-LS报文或NETCONF消息发送给预定节点。
- 根据权利要求16所述的装置,其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。
- 根据权利要求16所述的装置,其中,所述处理模块设置为通过以下方式利用扩展的BGP-LS封装IOAM能力信息:增加至少一个BGP-LS属性;利用增加的至少一个BGP-LS属性封装所述IOAM能力信息;其中,所述增加的至少一个BGP-LS属性包括以下至少之一:节点属性、前缀属性、以及链路属性。
- 根据权利要求16所述的装置,其中,所述处理模块设置为通过以下方式利用NETCONF封装IOAM能力信息:将所述IOAM能力信息封装在 NETCONF的HELLO消息中。
- 根据权利要求16至19任一项所述的装置,其中,所述IOAM能力信息包括IOAM的类型;其中,所述IOAM的类型包括:路径跟踪、路径验证、以及端到端的验证。
- 一种信息通告装置,包括:接收模块,设置为接收带内操作管理维护IOAM节点发送的边界网关协议BGP-链路状态LS报文或者网络配置协议NETCONF消息;解析模块,设置为从所述BGP-LS报文或者所述NETCONF消息中解析所述IOAM节点通告的IOAM能力信息。
- 根据权利要求21所述的装置,其中,所述预定节点为网络管理***中的控制器或者网络管理***中的网管。
- 根据权利要求21所述的装置,其中,所述IOAM能力信息封装在增加的BGP-LS属性中,或者,由NETCONF的HELLO消息携带;其中,所述增加的BGP-LS属性包括以下至少之一:节点属性、前缀属性、以及链路属性。
- 根据权利要求21或23所述的装置,其中,所述IOAM能力信息包括IOAM的类型;其中,所述IOAM的类型包括:路径跟踪、路径验证、以及端到端的验证。
- 一种信息通告装置,应用于带内操作管理维护IOAM节点,包括:存储器以及至少一个处理器;其中,存储器设置为存储用于信息通告的程序;该用于信息通告的程序在被处理器读取执行时实现如权利要求1至7任一项所述的信息通告方法。
- 一种信息通告装置,包括:存储器以及至少一个处理器;其中,存储器设置为存储用于信息通告的程序;该用于信息通告的程序在被处理器读取执行时,实现如权利要求8至13任一项所述的信息通告方法。
- 一种机器可读介质,其上存储有计算机程序,所述计算机程序被处理器执行时实现如权利要求1至8任一项所述的信息通告方法。
- 一种机器可读介质,其上存储有计算机程序,所述计算机程序被处理器执行时实现如权利要求9至15任一项所述的信息通告方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/604,929 US11063810B2 (en) | 2017-04-13 | 2018-04-13 | Information notification method and device |
EP18784280.2A EP3611877A4 (en) | 2017-04-13 | 2018-04-13 | INFORMATION NOTIFICATION PROCEDURE AND DEVICE |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710240493.XA CN108737124B (zh) | 2017-04-13 | 2017-04-13 | 一种信息通告方法及装置 |
CN201710240493.X | 2017-04-13 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018188662A1 true WO2018188662A1 (zh) | 2018-10-18 |
Family
ID=63792291
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/083100 WO2018188662A1 (zh) | 2017-04-13 | 2018-04-13 | 信息通告方法及装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US11063810B2 (zh) |
EP (1) | EP3611877A4 (zh) |
CN (1) | CN108737124B (zh) |
WO (1) | WO2018188662A1 (zh) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10972377B2 (en) * | 2018-11-02 | 2021-04-06 | Cisco Technology, Inc. | Coordinated offloaded recording of in-situ operations, administration, and maintenance (IOAM) data to packets traversing network nodes |
CN111277426B (zh) * | 2018-12-05 | 2022-08-19 | 中兴通讯股份有限公司 | 一种ioam信息的处理方法和装置 |
CN111385121B (zh) * | 2018-12-29 | 2021-08-03 | 华为技术有限公司 | 一种操作管理维护iOAM报文的传输方法及相应装置 |
US11150963B2 (en) * | 2019-02-28 | 2021-10-19 | Cisco Technology, Inc. | Remote smart NIC-based service acceleration |
CN109743340B (zh) | 2019-04-04 | 2019-07-30 | 华为技术有限公司 | 报文处理的方法和网络装置 |
US11343261B2 (en) * | 2019-04-05 | 2022-05-24 | Cisco Technology, Inc. | Technologies for proving packet transit through uncompromised nodes |
CN112672363B (zh) * | 2019-10-15 | 2023-04-18 | 华为技术有限公司 | 随流信息遥测能力的确认方法和设备 |
CN113783745A (zh) * | 2020-06-10 | 2021-12-10 | 中国电信股份有限公司 | 网络遥测信息采集方法和***、bier域入口节点 |
CN113938403A (zh) * | 2020-07-13 | 2022-01-14 | 华为技术有限公司 | 一种能力通告方法及相关设备 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102868569A (zh) * | 2012-06-30 | 2013-01-09 | 华为技术有限公司 | 三层虚拟专用网的性能检测方法、节点和*** |
EP2645640A2 (en) * | 2012-03-27 | 2013-10-02 | Juniper Networks, Inc. | Oam label switched path for fast reroute of protected label switched paths |
CN103780420A (zh) * | 2012-10-25 | 2014-05-07 | 中国电信股份有限公司 | Vpls环境下以太网连通性检测的自动配置方法和*** |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7895425B2 (en) * | 2007-08-03 | 2011-02-22 | Cisco Technology, Inc. | Operation, administration and maintenance (OAM) in a service insertion architecture (SIA) |
EP2466797A1 (en) * | 2010-12-17 | 2012-06-20 | Telefonaktiebolaget L M Ericsson AB (Publ) | Interworking for OAM information exchange |
US9967191B2 (en) * | 2013-07-25 | 2018-05-08 | Cisco Technology, Inc. | Receiver-signaled entropy labels for traffic forwarding in a computer network |
US9124485B2 (en) * | 2013-08-19 | 2015-09-01 | Cisco Technology, Inc. | Topology aware provisioning in a software-defined networking environment |
US20150124626A1 (en) * | 2013-11-05 | 2015-05-07 | Electronics And Telecommunications Research Institute | Method of supporting in-band operations, administration and maintenance (oam) for point-to-multipoint (p2mp) data transfer in multi-protocol label switching-transport profile (mpls-tp) network |
US9363585B2 (en) * | 2014-04-17 | 2016-06-07 | Alcatel Lucent | Operations administration and management service for an optical layer of a communication network |
CN105530115B (zh) * | 2014-10-23 | 2019-10-22 | 华为技术有限公司 | 一种实现操作管理维护功能的方法及装置 |
CN105871722B (zh) * | 2015-01-19 | 2020-02-14 | 中兴通讯股份有限公司 | 标签构造以及标签报文转发方法及装置 |
US10237068B2 (en) * | 2015-04-27 | 2019-03-19 | Cisco Technology, Inc. | Network path proof of transit using in-band metadata |
US9992056B2 (en) * | 2015-10-20 | 2018-06-05 | Cisco Technology, Inc. | Triggered in-band operations, administration, and maintenance in a network environment |
US10355983B2 (en) * | 2016-05-09 | 2019-07-16 | Cisco Technology, Inc. | Traceroute to return aggregated statistics in service chains |
US10742551B2 (en) * | 2016-06-21 | 2020-08-11 | Cisco Technology, Inc. | Packet path recording with fixed header size |
US20180062991A1 (en) * | 2016-08-30 | 2018-03-01 | Cisco Technology, Inc. | Deterministic controller-based path query |
CN106385344B (zh) * | 2016-09-05 | 2019-09-06 | 新华三技术有限公司 | 一种报文监控方法和装置 |
US10454828B2 (en) * | 2016-12-21 | 2019-10-22 | Cisco Technology, Inc. | Machine learning-derived entropy path graph from in-situ OAM (iOAM) data |
US10588012B2 (en) * | 2017-07-28 | 2020-03-10 | Cisco Technology, Inc. | In-situ operations, administration and management proxy |
US10582027B2 (en) * | 2017-11-04 | 2020-03-03 | Cisco Technology, Inc. | In-band metadata export and removal at intermediate nodes |
-
2017
- 2017-04-13 CN CN201710240493.XA patent/CN108737124B/zh active Active
-
2018
- 2018-04-13 EP EP18784280.2A patent/EP3611877A4/en active Pending
- 2018-04-13 WO PCT/CN2018/083100 patent/WO2018188662A1/zh unknown
- 2018-04-13 US US16/604,929 patent/US11063810B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2645640A2 (en) * | 2012-03-27 | 2013-10-02 | Juniper Networks, Inc. | Oam label switched path for fast reroute of protected label switched paths |
CN102868569A (zh) * | 2012-06-30 | 2013-01-09 | 华为技术有限公司 | 三层虚拟专用网的性能检测方法、节点和*** |
CN103780420A (zh) * | 2012-10-25 | 2014-05-07 | 中国电信股份有限公司 | Vpls环境下以太网连通性检测的自动配置方法和*** |
Non-Patent Citations (2)
Title |
---|
F. BROCKNERS ET AL.: "Requirements for In-situ OAM", DRAFT-BROCKNERS-INBAND-OAM-REQUIREMENTS-03, 13 March 2017 (2017-03-13), pages 1 - 24, XP015118624 * |
See also references of EP3611877A4 * |
Also Published As
Publication number | Publication date |
---|---|
US11063810B2 (en) | 2021-07-13 |
EP3611877A1 (en) | 2020-02-19 |
CN108737124A (zh) | 2018-11-02 |
US20200162307A1 (en) | 2020-05-21 |
CN108737124B (zh) | 2022-07-19 |
EP3611877A4 (en) | 2020-12-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018188662A1 (zh) | 信息通告方法及装置 | |
CN108737128B (zh) | 一种实现带内操作管理维护ioam的方法及装置 | |
US11777783B2 (en) | Network slicing with smart contracts | |
WO2018188663A1 (zh) | 信息通告方法及装置 | |
EP2993835B1 (en) | Service routing system, device and method | |
US10862793B2 (en) | Centralized error telemetry using segment routing header tunneling | |
US10243827B2 (en) | Techniques to use a network service header to monitor quality of service | |
WO2018210213A1 (zh) | 一种实现ioam封装的方法及装置、存储介质 | |
WO2018210225A1 (zh) | 一种自动实现ioam封装的方法及装置、存储介质 | |
CN108270673B (zh) | 报文发送方法、装置以及*** | |
US10581735B2 (en) | Packet processing method and apparatus | |
WO2015184771A1 (zh) | 一种业务功能链操作、管理和维护方法及节点设备 | |
US10693777B2 (en) | In-situ operations, administration, and maintenance (iOAM) for software defined architectures (SDAs) | |
US11888900B2 (en) | Cryptographic security audit using network service zone locking | |
CN106385344A (zh) | 一种报文监控方法和装置 | |
US20230362053A1 (en) | Network configuration sending method and apparatus, storage medium, and electronic device | |
CN113765800A (zh) | 传输报文的方法、装置、***、设备及可读存储介质 | |
WO2020114083A1 (zh) | 一种ioam信息的处理方法和装置 | |
CN107231309B (zh) | 获取sdn全网视图的方法、控制器及目的交换节点 | |
WO2016037490A1 (zh) | 一种动态主机配置协议dhcp消息的处理方法及装置 | |
CN110011820B (zh) | 一种***间的连接方法、设备及计算机存储介质 | |
CN104219146A (zh) | 接入网中基于ancp配置标签的方法和装置 | |
CN116074235A (zh) | 报文处理方法、装置及*** | |
WO2016180044A1 (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: 18784280 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2018784280 Country of ref document: EP Effective date: 20191113 |