[go: up one dir, main page]

WO2018188663A1 - 信息通告方法及装置 - Google Patents

信息通告方法及装置 Download PDF

Info

Publication number
WO2018188663A1
WO2018188663A1 PCT/CN2018/083101 CN2018083101W WO2018188663A1 WO 2018188663 A1 WO2018188663 A1 WO 2018188663A1 CN 2018083101 W CN2018083101 W CN 2018083101W WO 2018188663 A1 WO2018188663 A1 WO 2018188663A1
Authority
WO
WIPO (PCT)
Prior art keywords
ioam
node
pcep
message
capability information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/083101
Other languages
English (en)
French (fr)
Inventor
陈然
肖敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2018188663A1 publication Critical patent/WO2018188663A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/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
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling

Definitions

  • the present disclosure relates to the field of communication technologies, for example, to an information notification method and apparatus.
  • IOAM In-situ Operation Administration and Maintenance
  • IOAM is also called in-band OAM.
  • In-band OAM is sent along with data packets, and no additional control plane messages are required to send OAM data.
  • In-band OAM is generally deployed in 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
  • in-band OAM can be used in different scenarios, such as Internet Protocol Version 6, IPV6, and Virtual Extensible LAN-Generic Protocol Extension (VXLAN-GPE).
  • IPV6 Internet Protocol Version 6
  • VXLAN-GPE Virtual Extensible LAN-Generic Protocol Extension
  • SFC service function chain
  • 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.
  • An embodiment of the present application provides an information notification method, including:
  • the IOAM node encapsulates IOAM capability information using one of the following protocols: Extended Path Computation Unit Communication Protocol (PCEP), Extended PCEP-Link State (LS), or OpenFlow OpenFlow Protocol;
  • PCEP Extended Path Computation Unit Communication Protocol
  • LS Extended PCEP-Link State
  • OpenFlow OpenFlow Protocol OpenFlow OpenFlow Protocol
  • the IOAM node sends a PCEP message, a PCEP-LS message, or an OpenFlow protocol message carrying the IOAM capability information to a predetermined node.
  • An embodiment of the present application provides an information notification method, including:
  • the predetermined node receives the PCEP message, the PCEP-LS message, or the OpenFlow protocol message sent by the IOAM node;
  • the predetermined node parses the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, and includes:
  • the processing module is configured to encapsulate the IOAM capability information by using one of the following protocols: an extended PCEP, an extended PCEP-LS, or an OpenFlow protocol;
  • the sending module is configured to: send the PCEP message, the PCEP-LS message, or the OpenFlow protocol message that carries the IOAM capability information to the predetermined node.
  • the embodiment of the present application provides an information notification apparatus, which is applied to a predetermined node, and includes:
  • the receiving module is configured to: receive a PCEP message, a PCEP-LS message, or an OpenFlow protocol message sent by the IOAM node;
  • the parsing module is configured to parse the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed Any one of the above information notification methods is implemented when the reader reads execution.
  • An embodiment of the present application provides an information notification apparatus, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is read and executed by the processor , to implement any of the above information notification methods.
  • the embodiment of the present application further provides a machine readable medium, where a computer program is stored thereon, and when the computer program is executed by the processor, any one of the foregoing information notification methods is implemented.
  • the embodiment of the present application further provides a machine readable medium storing a computer program, where the computer program is executed by a processor to implement any of the above information notification methods.
  • the node information supporting the IOAM function in the IOAM domain is collected by extending the PCEP, the PCEP-LS, or the OpenFlow protocol, so that the node that collects the IOAM function in the IOAM domain is collected by the predetermined node.
  • FIG. 1 is a flowchart of an information notification method according to an embodiment of the present application
  • FIG. 2 is a flowchart of an information notification method according to another embodiment of the present application.
  • FIG. 3 is a network connection diagram according to an embodiment of the present application.
  • FIG. 5 is a network connection diagram according to another embodiment of the present application.
  • FIG. 6 is a flowchart of an information notification method according to another embodiment of the present application.
  • FIG. 7 is a network connection diagram according to another embodiment of the present application.
  • FIG. 8 is a flowchart of an information notification method according to another embodiment of the present application.
  • FIG. 9 is a schematic diagram of a format of an IOAM capability type length value according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of a format of a path tracking subtype length value according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of a format of a path verification subtype length value according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram of an information notification apparatus according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of an information notification apparatus according to another 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 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:
  • Step 101 The IOAM node encapsulates the IOAM capability information by using an extended Path Computation Element Protocol (PCEP), or encapsulates the IOAM capability by using an extended PCEP-link-state (PCEP-LS). Information, or, encapsulates IOAM capability information using the OpenFlow protocol.
  • PCEP Path Computation Element Protocol
  • PCEP-LS extended PCEP-link-state
  • Step 102 The IOAM node sends a PCEP message, a PCEP-LS message, or an OpenFlow protocol message that carries the IOAM capability information to the predetermined node.
  • the IOAM node may use the extended PCEP to encapsulate the IOAM capability information, and send the PCEP message carrying the IOAM capability information to the predetermined node; or the IOAM node may encapsulate the IOAM capability information by using the extended PCEP-LS, and will carry The PCEP-LS packet of the IOAM capability information is sent to the predetermined node.
  • the IOAM node may encapsulate the IOAM capability information by using the OpenFlow protocol, and send an OpenFlow protocol message carrying the IOAM capability information to the predetermined node.
  • the predetermined node may be a Path Computation Element (PCE) or a controller or a network management system in the network management system.
  • PCE Path Computation Element
  • the PCE is an entity capable of computing and knowing the path between any nodes in an autonomous system (AS). It can be integrated inside the router or exist as a separate entity in the network. Can be integrated with the network management system. PCE is more aware of network traffic and path selection within the AS and can therefore be used for better path computation.
  • the nodes in the IOAM domain can work as a Path Computation Client (PCC), so the PCEP can be extended to notify the PCE of its own supported IOAM capabilities.
  • PCC Path Computation Client
  • the OpenFlow protocol is used to describe the criteria used for the interaction between the controller and the switch, as well as the interface standards for the controller and switch.
  • the core part of the protocol is a collection of information structures for the OpenFlow protocol.
  • the OpenFlow protocol can be run between the nodes and controllers in the IOAM domain. In some scenarios using the OpenFlow protocol, the OpenFlow protocol can be extended to perform IOAM capability advertisement in the IOAM domain.
  • the IOAM node encapsulates the IOAM capability information by using the extended PCEP, and may include:
  • the IOAM node extends the Open message in the PCEP to carry IOAM capability information.
  • the IOAM node encapsulates the IOAM capability information by using the extended PCEP-LS, and may include:
  • the IOAM node adds a PCEP-LS object (Object); the IOAM capability information is encapsulated by the added PCEP-LS object.
  • Object PCEP-LS object
  • the added PCEP-LS object may include at least one of: Node Descriptors Type Length Value (TLV), Prefix Descriptors TLV, and Link Description Link Descriptors TLV.
  • TLV Type Length Value
  • Prefix Descriptors TLV Prefix Descriptors TLV
  • Link Description Link Descriptors TLV Link Description Link Descriptors
  • the IOAM capability information may be carried by at least one of a Node Descriptor TLV, a Prefix Descriptor TLV, and a Link Descriptor TLV.
  • the IOAM node encapsulates the IOAM capability information by using the OpenFlow protocol, and may include: the IOAM node encapsulates the IOAM capability information in a flow table function response (table feature reply) message.
  • the IOAM node encapsulating the IOAM capability information in the table feature reply message may include: adding one or more IOAM matching fields in the table feature reply message, and specifying to match the one or more IOAM matching fields. Subsequent operations, such as modifying or adding new entries, may be used to modify or add IOAM data.
  • the IOAM capability information may include the following information: a type of IOAM.
  • the types of 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 embodiment of the present application provides an information notification method, including:
  • Step 201 The predetermined node receives a PCEP message, a PCEP-LS message, or an OpenFlow protocol message sent by the IOAM node.
  • Step 202 The predetermined node parses the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • the predetermined node may be a controller or a network manager in the PCE or network management system.
  • the predetermined node may receive the PCEP message sent by the IOAM node, and parse the IOAM capability information advertised by the IOAM node from the PCEP message; or, the predetermined node receives the PCEP-LS message sent by the IOAM node, and from the PCEP - The LSAM capability information advertised by the IOAM node is parsed in the LS packet; or the predetermined node receives the OpenFlow protocol message sent by the IOAM node, and parses the IOAM capability information advertised by the IOAM node from the OpenFlow protocol message.
  • the IOAM capability information may be carried by an Open message in the PCEP, or encapsulated in an added PCEP-LS object, or carried by a table feature reply message of the OpenFlow protocol.
  • the added PCEP-LS object may include at least one of the following: a node descriptor TLV, a prefix descriptor TLV, and a link descriptor TLV.
  • the IOAM capability information may be carried by at least one of a Node Descriptor TLV, a Prefix Descriptor TLV, and a Link Descriptor TLV.
  • the IOAM capability information may include: a type of IOAM; in an exemplary embodiment, 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 Bit Indexed Explicit Replication (BIER) domain is an IOAM domain, and all BIER nodes in FIG. 3 are also nodes supporting IOAM technology at the same time.
  • a BIER-Forwarding Ingress Router (BFIR) is also called an IOAM encapsulation node
  • BFER BIER egress router
  • BFR BIER forwarding node
  • the data message is sent from the BIER ingress node to the BIER egress node.
  • BIER BIER Ingress Node
  • IOAM encapsulation node interacts with the PCE.
  • FIG. 4 is a flowchart of an information notification method according to the embodiment. Referring to FIG. 4, the method provided in this embodiment includes:
  • step 301 the BIER ingress node carries the IOAM capability TLV through the extended PCEP-LS object, and notifies the PCE that it supports the IOAM capability.
  • the IOAM capability information may be carried by an extension node descriptor TLV (NODE Descriptors TLV), a link descriptor TLV (Link Descriptors TLV), and a prefix descriptor TLV (Prefix Descriptors TLV).
  • NODE Descriptors TLV extension node descriptors TLV
  • Link Descriptors TLV Link Descriptors TLV
  • Prefix Descriptors TLV prefix Descriptors TLV
  • the Type field identifies the TLV as the IOAM capability type length value (IOAM-capability TLV); the Length field is the total length of the TLV; and the Option type field is the type of the IOAM.
  • the IETF defines three types of IOAM types: in-suit OAM Tracing Option, in-suit OAM Proof of Transit Option, and In-situ OAM Edge-to-Edge Option.
  • the Reserved field is a reserved field to be expanded.
  • the one or more option sub-TLVs may include an in-suit OAM Tracing Option Sub-TLV, an in-suit OAM Proof of Transit Option Sub-TLV, and an end-to-end In-situ OAM Edge-to-Edge Option Sub-TLV.
  • FIG. 10 is a schematic diagram of a format of a path tracking subtype length value. As shown in FIG. 10, the F byte is used to indicate the type of path tracking, and currently includes the following two types: Pre-allocated Trace Option and Incremental Trace Option.
  • FIG. 11 is a schematic diagram of the format of the path verification subtype length value.
  • the path verification subtype length value is defined as the following three types: universal proof of Transit (universal POT), network service header metadata (NSH metadata) path verification, and Proof of Transit of Segment Routing (SR POT).
  • universal POT universal proof of Transit
  • NSH metadata network service header metadata
  • SR POT Proof of Transit of Segment Routing
  • the IOAM encapsulation node/BIER ingress node interacts with the PCE.
  • the nodes supporting the IOAM and BIER technologies in the IOAM and BIER domains may interact with the PCE, or the designated IOAM node may interact with the PCE. This application is not limited to this, and which nodes the PCE interacts with depends on the actual deployment.
  • the BIER ingress node/IOAM encapsulation node collects the supported IOAM of the relevant node in the IOAM domain through the Interior Gateway Protocol (IGP).
  • IGP Interior Gateway Protocol
  • Step 302 After receiving the PCEP-LS packet, the PCE analyzes which nodes support the IOAM capability.
  • the segment routing (SR) domain is an IOAM domain
  • all the SR nodes in FIG. 5 are also nodes supporting the IOAM technology at the same time. All of the SR nodes in Figure 5 interact with the PCE.
  • the SR ingress node is also called an IOAM encapsulation node
  • the SR egress node is also called an IOAM decapsulation node
  • the SR forwarding node is also called an intermediate IOAM forwarding node; as shown in FIG. 5, the data packet is sent from the SR ingress node. Go to the SR exit node.
  • FIG. 6 is a flowchart of an information notification method provided by this embodiment. As shown in FIG. 6, the process of this embodiment includes:
  • the IOAM-related node (such as the node supporting both the SR technology and the IOAM technology in FIG. 5) sends an Open message carrying the IOAM Capability TLV to the PCE, indicating that the IOAM node supports the IOAM.
  • Step 402 After receiving the extended Open message, the PCE parses to know which nodes support the IOAM capability.
  • the VXLAN domain is an IOAM domain, and all nodes supporting the VXLAN technology in FIG. 7 also support IOAM.
  • the VXLAN domain and the nodes in the IOAM domain that support VXLAN and IOAM technologies interact with the controller.
  • Network Virtual Edge (NVE) is also called IOAM encapsulation node.
  • NVE is also called IOAM decapsulation node.
  • VXLAN forwarding node is also called intermediate IOAM forwarding node.
  • data packet From the IOAM encapsulation node to the IOAM decapsulation node.
  • FIG. 8 is a flowchart of an information notification method provided by this embodiment. As shown in FIG. 8, the process of this embodiment includes:
  • Step 501 The IOAM node sends a table feature reply message carrying the IOAM capability information to the controller, indicating that the IOAM node supports the IOAM function.
  • one or more IOAM matching fields may be added in the table feature reply message, and at the same time, an operation performed after matching the IOAM matching field may be specified, and may be an operation of modifying or adding a new item.
  • the controller After receiving the table feature reply message, the controller calculates the forwarding path of the IOAM node according to the IOAM capability information carried in the table feature reply message, and processes the IOAM capability information, and obtains the IOAM node forwarding path and the processed IOAM capability information. Send to the IOAM node.
  • the IOAM node After receiving the data packet carrying the IOAM packet, the IOAM node matches the IOAM header according to the IOAM node forwarding path and the IOAM capability information received from the controller, and then performs operations on the IOAM data, such as modifying or adding a new entry. And forward the data packet after the operation.
  • Step 502 After receiving the extended flow table function response message, the controller parses to know which nodes support the IOAM capability.
  • an embodiment of the present application 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 PCEP, or encapsulate the IOAM capability information by using the extended PCEP-LS, or encapsulate the IOAM capability information by using the OpenFlow protocol;
  • the sending module 902 is configured to: send a PCEP message, a PCEP-LS message, or an OpenFlow protocol message that carries the IOAM capability information to the predetermined node.
  • the processing module 901 may be configured to encapsulate the IOAM capability information with the extended PCEP by:
  • the Open message in the PCEP is extended to carry IOAM capability information.
  • the processing module 901 may be configured to encapsulate the IOAM capability information with the extended PCEP-LS by:
  • the added PCEP-LS object may include at least one of the following: a node descriptor TLV, a prefix descriptor TLV, and a link descriptor TLV.
  • the processing module 901 may be configured to encapsulate the IOAM capability information by using the OpenFlow protocol in the following manner:
  • the IOAM capability information is encapsulated in a flow table function reply (table feature reply) message.
  • the IOAM capability information may include the following information: a type of IOAM; in an exemplary embodiment, 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 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 PCEP message, a PCEP-LS message, or an OpenFlow protocol message sent by the IOAM node;
  • the parsing module 1002 is configured to parse the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • the IOAM capability information may be carried by an Open message in the PCEP, or encapsulated in an added PCEP-LS object, or carried by a table feature reply message of the OpenFlow protocol.
  • the IOAM capability information may include: a type of IOAM.
  • 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.
  • An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed
  • the information notification method of the above IOAM node side is implemented when the reader reads and executes.
  • 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 one or more processors; wherein the memory is configured to store a program for information notification; the information is used for information notification.
  • an information notification apparatus which is applied to an IOAM node, including: a transmission module, a memory, and one or more processors; wherein the memory is configured to store a program for information notification; the information is used for information notification.
  • the IOAM node encapsulates the IOAM capability information by using the extended PCEP, or encapsulates the IOAM capability information by using the extended PCEP-LS, or encapsulates the IOAM capability information by using the OpenFlow protocol; and transmits the PCEP message carrying the IOAM capability information and the PCEP-LS packet through the transmission module.
  • the text or OpenFlow protocol message is sent to the predetermined node.
  • the processor may include, but is not limited to, a processing device such as a Microcontroller Unit (MCU) or a Field-Programmable Gate Array (FPGA).
  • MCU Microcontroller Unit
  • FPGA Field-Programmable Gate Array
  • the memory may be set as a software program and a module for storing application software, such as a program instruction/module corresponding to the information notification method of the present application, and the processor executes various function applications and data processing by running a software program and a module 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
  • An embodiment of the present application provides an information notification apparatus, which is applied to a predetermined node, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed When the device reads and executes, the information notification method on the predetermined node side described above is implemented.
  • the embodiment of the present application further provides an information notification apparatus, which is applied to a predetermined node, including: a transmission module, a memory, and one or more processors; wherein the memory is configured to store a program for information notification; the information notification is used When the program is read and executed by the processor, the following operations are performed:
  • the IOAM capability information advertised by the IOAM node is parsed from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • the processor may include, but is not limited to, a processing device such as an MCU or an FPGA.
  • the predetermined nodes described above 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 a program instruction/module 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, the remote memory being connectable 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, where the computer program is executed by the processor to implement the above information notification method on the IOAM node side or the 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., a hard disk drive
  • all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits.
  • each module/unit in the above 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. / instruction to achieve its corresponding function.
  • This application is not limited to any specific combination of hardware and software.
  • the present disclosure collects node information that supports the IOAM function in the IOAM domain by extending the PCEP, PCEP-LS, or OpenFlow protocol, thereby implementing node information that the predetermined node collects to support the IOAM function in the IOAM domain.

Landscapes

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

Abstract

一种信息通告方法及装置。上述信息通告方法包括：带内操作管理维护IOAM节点利用扩展的路径计算单元通信协议PCEP封装IOAM能力信息，或者，利用扩展的PCEP-链路状态LS封装IOAM能力信息，或者，利用开放流OpenFlow协议封装IOAM能力信息；并将携带IOAM能力信息的PCEP消息、PCEP-LS报文或者OpenFlow协议消息发送给预定节点。

Description

信息通告方法及装置 技术领域
本公开涉及通信技术领域，例如涉及一种信息通告方法及装置。
背景技术
互联网工程任务组(Internet Engineering Task Force，IETF)提出了带内操作管理维护(In-situ Operation Administration and Maintenance，IOAM)，其中，IOAM又称带内OAM。带内OAM随着数据报文一起发送，不需要额外的控制面报文发送OAM数据，带内OAM一般是在一个特定的域内部署。IOAM可以实现多种路径跟踪、路径验证以及服务等级协议(Service-Level Agreement，SLA)验证等复杂的OAM功能。
根据部署，带内OAM可以在不同的场景中使用，比如在互联网协议第6版(Internet Protocol Version 6，IPV6)、虚拟扩展局域网的通用协议扩展(Virtual Extensible LAN-Generic Protocol Extension，VXLAN-GPE)、业务功能链(Service Function Chain，SFC)及段路由(segment routing，SR)等场景下。但是，在IOAM场景下，通过IOAM域外的节点还不能实现IOAM功能。
发明内容
本申请实施例提供一种信息通告方法及装置，以实现预定节点收集到IOAM域内支持IOAM功能的节点信息。
本申请实施例提供一种信息通告方法，包括：
IOAM节点利用如下协议之一封装IOAM能力信息：扩展的路径计算单元通信协议(PCEP)、扩展的PCEP-链路状态(LS)、或者开放流OpenFlow协议；
所述IOAM节点将携带所述IOAM能力信息的PCEP消息、PCEP-LS报文或者OpenFlow协议消息发送给预定节点。
本申请实施例提供一种信息通告方法，包括：
预定节点接收IOAM节点发送的PCEP消息、PCEP-LS报文或者OpenFlow协议消息；
所述预定节点从所述PCEP消息、PCEP-LS报文或者OpenFlow协议消息中解 析所述IOAM节点通告的IOAM能力信息。
本申请实施例提供一种信息通告装置，应用于IOAM节点，包括：
处理模块，设置为利用如下协议之一封装IOAM能力信息：扩展的PCEP、扩展的PCEP-LS、或者OpenFlow协议；
发送模块，设置为：将携带所述IOAM能力信息的PCEP消息、PCEP-LS报文或者OpenFlow协议消息发送给预定节点。
本申请实施例提供一种信息通告装置，应用于预定节点，包括：
接收模块，设置为：接收IOAM节点发送的PCEP消息、PCEP-LS报文或者OpenFlow协议消息；
解析模块，设置为：从所述PCEP消息、PCEP-LS报文或者OpenFlow协议消息中解析所述IOAM节点通告的IOAM能力信息。
本申请实施例提供一种信息通告装置，应用于IOAM节点，包括：存储器以及一个或多个处理器；其中，存储器设置为存储用于信息通告的程序；该用于信息通告的程序在被处理器读取执行时实现上述任意一种信息通告方法。
本申请实施例提供一种信息通告装置，包括：存储器以及一个或多个处理器；其中，存储器设置为存储用于信息通告的程序；该用于信息通告的程序在被处理器读取执行时，实现上述任意一种信息通告方法。
此外，本申请实施例还提供一种机器可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述任意一种信息通告方法。
本申请实施例还提供一种机器可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述任意一种信息通告方法。
本申请实施例通过扩展PCEP、PCEP-LS或者OpenFlow协议来收集IOAM域内支持IOAM功能的节点信息，从而实现预定节点收集到IOAM域内支持IOAM功能的节点信息。
附图说明
图1为本申请一实施例提供的信息通告方法的流程图；
图2为本申请另一实施例提供的信息通告方法的流程图；
图3为本申请一实施例提供的网络连接图；
图4为本申请另一实施例提供的信息通告方法的流程图；
图5为本申请另一实施例提供的网络连接图；
图6为本申请另一实施例提供的信息通告方法的流程图；
图7为本申请另一实施例提供的网络连接图；
图8为本申请另一实施例提供的信息通告方法的流程图；
图9为本申请一实施例提供的IOAM能力类型长度值的格式示意图；
图10为本申请一实施例提供的路径跟踪子类型长度值的格式示意图；
图11为本申请一实施例提供的路径验证子类型长度值的格式示意图；
图12为本申请一实施例提供的信息通告装置的示意图；
图13为本申请另一实施例提供的信息通告装置的示意图。
具体实施方式
以下结合附图对本申请实施例进行说明，应当理解，以下所说明的实施例仅用于说明和解释本申请，并不用于限定本申请。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
在IOAM域的多个边缘节点中，将OAM数据报文嵌入在数据报文中的边缘节点又称为IOAM封装节点，要离开IOAM域的边缘节点将OAM数据报文移除，该节点又称为IOAM解封装节点。在一实施例中，IOAM的路径验证方法是：在IOAM封装节点，将OAM数据报文嵌入在数据报文中，IOAM转发节点根据一定的算法将相关的OAM信息填入OAM数据报文中，IOAM解封装节点根据IOAM转发节点填入OAM数据报文中的OAM信息校验路径是否与配置的路径一致，并将OAM数据报文移除。这里，实现路径校验的节点可以由IOAM域外设置的预定节点来完成，譬如外置的预定节点基于完整的带内的OAM数据报文来完成路径校验。
如图1所示，本申请实施例提供一种信息通告方法，包括：
步骤101、IOAM节点利用扩展的路径计算单元通信协议(Path Computation Element Protocol，PCEP)封装IOAM能力信息，或者，利用扩展的PCEP-链路状态(PCEP-link-state，PCEP-LS)封装IOAM能力信息，或者，利用开放流(OpenFlow)协议封装IOAM能力信息。
步骤102、IOAM节点将携带IOAM能力信息的PCEP消息、PCEP-LS报文或者OpenFlow协议消息发送给预定节点。本实施例中，IOAM节点可以利用扩展的PCEP封装IOAM能力信息，并将携带IOAM能力信息的PCEP消息发送给预定节点；或者，IOAM节点可以利用扩展的PCEP-LS封装IOAM能力信息，并将携带IOAM能力信息的PCEP-LS报文发送给预定节点；或者，IOAM节点可以利用OpenFlow协议封装IOAM能力信息，并将携带IOAM能力信息的OpenFlow协议消息发送给预定节点。
在示例性实施方式中，预定节点可以为路径计算单元(Path Computation Element，PCE)或者网络管理系统中的控制器或者网管。
其中，PCE是有能力计算、且在自治系统(autonomous system，AS)中知道任何节点之间的路径的实体，它可以集成在路由器的内部，也可以作为一个单独的实体存在于网络中，还可以同网管系统集成在一起。PCE更加了解AS内的网络流量和路径选择，因此可被用于更好的路径计算。IOAM域内的节点可以作为路径计算客户端(Path computation client，PCC)工作，所以可以扩展PCEP向PCE通告其本身支持的IOAM能力。
OpenFlow协议用来描述控制器和交换机之间交互所用信息的标准，以及控制器和交换机的接口标准。协议的核心部分是用于OpenFlow协议信息结构的集合。IOAM域内的节点与控制器之间可以运行OpenFlow协议，在某些使用OpenFlow协议场景下，可以通过扩展OpenFlow协议来进行IOAM域内的IOAM能力通告。
在示例性实施方式中，IOAM节点利用扩展的PCEP封装IOAM能力信息，可以包括：
IOAM节点扩展PCEP中的开放(Open)消息来携带IOAM能力信息。
在示例性实施方式中，IOAM节点利用扩展的PCEP-LS封装IOAM能力信息，可以包括：
IOAM节点增加PCEP-LS对象(Object)；利用增加的PCEP-LS对象封装IOAM能力信息。
在示例性实施方式中，增加的PCEP-LS对象可以包括以下至少之一：节点描述符(Node Descriptors)类型长度值(Type Length Value，TLV)、前缀描述符(Prefix Descriptors)TLV以及链路描述符(Link Descriptors)TLV。
在示例性实施方式中，IOAM能力信息可以由以下至少之一携带：节点描述符TLV、前缀描述符TLV以及链路描述符TLV。
在示例性实施方式中，IOAM节点利用OpenFlow协议封装IOAM能力信息，可以包括：IOAM节点在流表功能响应(table feature reply)消息中封装IOAM能力信息。
在示例性实施方式中，IOAM节点在table feature reply消息中封装IOAM能力信息，可以包括：在table feature reply消息中增加一个或者多个IOAM匹配字段，并规定匹配所述一个或多个IOAM匹配字段后所进行的操作，比如，可以是修改或添加新条目等操作以修改或添加IOAM数据。
在示例性实施方式中，IOAM能力信息可以包括以下信息：IOAM的类型。在示例性实施方式中，IOAM的类型包括：路径跟踪、路径验证以及端到端的验证。
在示例性实施方式中，IOAM能力信息还可以包括以下信息至少之一：路径跟踪的子类型、路径验证的子类型以及端到端的验证子类型。
如图2所示，本申请实施例提供一种信息通告方法，包括：
步骤201、预定节点接收IOAM节点发送的PCEP消息、PCEP-LS报文或者OpenFlow协议消息；
步骤202、预定节点从PCEP消息、PCEP-LS报文或者OpenFlow协议消息中解析IOAM节点通告的IOAM能力信息。在示例性实施方式中，预定节点可以为PCE或者网络管理系统中的控制器或者网管。
在示例性实施方式中，预定节点可以接收IOAM节点发送的PCEP消息，并从PCEP消息中解析IOAM节点通告的IOAM能力信息；或者，预定节点接收IOAM节点发送的PCEP-LS报文，并从PCEP-LS报文中解析IOAM节点通告的IOAM能力信息；或者，预定节点接收IOAM节点发送的OpenFlow协议消息，并从OpenFlow协议消息中解析IOAM节点通告的IOAM能力信息。
在示例性实施方式中，IOAM能力信息可以由PCEP中的Open消息携带，或者，封装在增加的PCEP-LS对象中，或者，由OpenFlow协议的流表功能响应(table feature reply)消息携带。
在示例性实施方式中，增加的PCEP-LS对象可以包括以下至少之一：节点描述符TLV、前缀描述符TLV以及链路描述符TLV。
在示例性实施方式中，IOAM能力信息可以由以下至少之一携带：节点描述符TLV、前缀描述符TLV以及链路描述符TLV。
在示例性实施方式中，IOAM能力信息可以包括：IOAM的类型；在示例性实施方式中，所述IOAM的类型包括：路径跟踪、路径验证以及端到端的验证。
在示例性实施方式中，IOAM能力信息还可以包括以下至少之一信息：路径跟踪的子类型、路径验证的子类型以及端到端的验证子类型。
下面通过多个实施例对本申请进行说明。
实施例一
本实施例中，如图3所示，位索引显式复制(Bit Indexed Explicit Replication，BIER)域又是IOAM域，图3中的所有的BIER节点也是同时支持IOAM技术的节点。如图3所示，BIER入口节点(Bit-Forwarding Ingress Router，BFIR)又叫做IOAM封装节点，BIER出口节点(Bit-Forwarding Egress Router，BFER)又叫做IOAM解封装节点，BIER转发节点(Bit forwarding Router，BFR)又叫做中间的IOAM转发节点。如图3所示，数据报文从BIER入口节点发往BIER出口节点。在图3中仅BIER入口节点(BFIR)/IOAM封装节点与PCE之间有交互。
图4为本实施例提供的信息通告方法的流程图，参见图4，本实施例提供的方法包括：
步骤301，BIER入口节点通过扩展的PCEP-LS对象(object)携带IOAM能力TLV，向PCE通告其支持IOAM能力。
在示例性实施方式中，可以通过扩展节点描述符TLV(NODE Descriptors TLV)、链路描述符TLV(Link Descriptors TLV)及前缀描述符TLV(Prefix Descriptors TLV)携带IOAM能力信息。
本实施例中，IOAM能力TLV的详细格式可以参见图9。在图9中，类型(Type)字段标识本TLV为IOAM能力类型长度值(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)、路径验证子类型长度值(in-suit OAM Proof of Transit Option Sub-TLV)以及端到端的验证子类型长度值(In-situ OAM Edge-to-Edge Option Sub-TLV)。
图10为路径跟踪子类型长度值的格式示意图。如图10所示，F字节用于表示路径跟踪的类型，目前包括以下两种类型：预分配跟踪选项(Pre-allocated Trace Option)及增量跟踪选项(Incremental Trace Option)。
图11为路径验证子类型长度值的格式示意图。如图11所示，定义了路径验证子类型长度值包括以下三种类型：通用路径验证(universal Proof of Transit，通用POT)、网络服务报头元数据(Network Service Header metadata，NSH metadata)路径验证及段路由路径验证(Proof of Transit of Segment Routing，SR POT)。
本实施例中，仅IOAM封装节点/BIER入口节点与PCE之间有交互。在其他实现方式中，也可以IOAM及BIER域内支持IOAM及BIER技术的节点均与PCE之间有交互，或者，也可以指定的IOAM节点与PCE之间有交互。本申请对此并不限定，PCE与哪些节点进行交互取决于实际的部署。
本实施例中，仅IOAM封装节点/BIER入口节点与PCE之间有交互，那么BIER入口节点/IOAM封装节点会通过内部网关协议(Interior Gateway Protocol，IGP)收集到IOAM域内的相关节点的支持IOAM能力，统一上报给PCE。
步骤302，PCE接收到PCEP-LS报文后，解析了解哪些节点支持IOAM能力。
实施例二
本实施例中，如图5所示，段路由(Segment Routing，SR)域又是IOAM域，图5中的所有的SR节点也是同时支持IOAM技术的节点。图5中所有的SR节点均与PCE之间有交互。如图5所示，SR入口节点又叫做IOAM封装节点，SR出口节点又叫做IOAM解封装节点，SR转发节点又叫做中间的IOAM转发节点；如图5所示，数据报文从SR入口节点发往SR出口节点。
图6为本实施例提供的信息通告方法的流程图。如图6所示，本实施例的流程包括：
步骤401，IOAM相关的节点(如图5中既支持SR技术也支持IOAM技术 的节点)向PCE发送携带IOAM能力类型长度值(IOAM Capability TLV)的开放(Open)消息，表明IOAM节点支持IOAM的功能。
步骤402，PCE收到扩展的开放(Open)消息后，解析了解哪些节点支持IOAM能力。
实施例三
本实施例中，如图7所示，VXLAN域又是IOAM域，图7中的所有支持VXLAN技术的节点也同时支持IOAM。在图7中，VXLAN域及IOAM域内支持VXLAN及IOAM技术的节点均与控制器之间有交互。如图7所示，网络边缘设备(Network Virtual Edge，NVE)又叫做IOAM封装节点，NVE又叫做IOAM解封装节点，VXLAN转发节点又叫做中间的IOAM转发节点；如图7所示，数据报文从IOAM封装节点发往IOAM解封装节点。
图8为本实施例提供的信息通告方法的流程图。如图8所示，本实施例的流程包括：
步骤501，IOAM节点向控制器发送携带IOAM能力信息的流表功能响应(table feature reply)消息，表明IOAM节点支持IOAM的功能。
在示例性实施方式中，可以在table feature reply消息中的增加一个或者多个IOAM匹配字段，并同时规定匹配IOAM匹配字段后所进行的操作，可以是修改或添加新条目等操作。
控制器接收到table feature reply消息后，根据table feature reply消息中携带的IOAM能力信息计算IOAM节点转发路径，并对IOAM能力信息进行处理，将获得的IOAM节点转发路径以及处理后的IOAM能力信息下发给IOAM节点。
IOAM节点在接收到携带有IOAM报文的数据报文后，根据从控制器接收到的IOAM节点转发路径和IOAM能力信息匹配IOAM header，再对IOAM数据进行操作，例如修改或添加新条目等操作，并将操作后的数据报文进行转发。
步骤502，控制器收到扩展的流表功能响应消息后，解析了解哪些节点支持IOAM能力。
如图12所示，本申请实施例提供一种信息通告装置，应用于IOAM节点，包括：
处理模块901，设置为：利用扩展的PCEP封装IOAM能力信息，或者，利用扩展的PCEP-LS封装IOAM能力信息，或者，利用OpenFlow协议封装IOAM 能力信息；
发送模块902，设置为：将携带IOAM能力信息的PCEP消息、PCEP-LS报文或者OpenFlow协议消息发送给预定节点。在示例性实施方式中，处理模块901可以设置为：通过以下方式利用扩展的PCEP封装IOAM能力信息：
扩展PCEP中的Open消息来携带IOAM能力信息。
在示例性实施方式中，处理模块901可以设置为：通过以下方式利用扩展的PCEP-LS封装IOAM能力信息：
增加PCEP-LS对象；利用增加的PCEP-LS对象封装IOAM能力信息；
在示例性实施方式中，增加的PCEP-LS对象可以包括以下至少之一：节点描述符TLV、前缀描述符TLV以及链路描述符TLV。
在示例性实施方式中，处理模块901可以设置为：通过以下方式利用OpenFlow协议封装IOAM能力信息：
在流表功能响应(table feature reply)消息中封装IOAM能力信息。
在示例性实施方式中，IOAM能力信息可以包括以下信息：IOAM的类型；在示例性实施方式中，所述IOAM的类型包括：路径跟踪、路径验证以及端到端的验证。
在示例性实施方式中，IOAM能力信息还可以包括以下信息至少之一：路径跟踪的子类型、路径验证的子类型以及端到端的验证子类型。
如图13所示，本申请实施例还提供一种信息通告装置，应用于预定节点，包括：
接收模块1001，设置为：接收IOAM节点发送的PCEP消息、PCEP-LS报文或者OpenFlow协议消息；
解析模块1002，设置为：从PCEP消息、PCEP-LS报文或者OpenFlow协议消息中解析IOAM节点通告的IOAM能力信息。
在示例性实施方式中，IOAM能力信息可以由PCEP中的Open消息携带，或者，封装在增加的PCEP-LS对象中，或者，由OpenFlow协议的table feature reply消息携带。
在示例性实施方式中，IOAM能力信息可以包括：IOAM的类型。在示例性实施方式中，所述IOAM的类型包括：路径跟踪、路径验证以及端到端的验证。
在示例性实施方式中，IOAM能力信息还可以包括以下信息至少之一：路径 跟踪的子类型、路径验证的子类型以及端到端的验证子类型。
关于上述信息通告装置的相关说明可以参照上述方法实施例的说明，故于此不再赘述。
本申请实施例提供一种信息通告装置，应用于IOAM节点，包括：存储器以及一个或多个处理器；其中，存储器设置为存储用于信息通告的程序；该用于信息通告的程序在被处理器读取执行时实现上述IOAM节点侧的信息通告方法。
本申请实施例还提供一种信息通告装置，应用于IOAM节点，包括：传输模块、存储器以及一个或多个处理器；其中，存储器设置为存储用于信息通告的程序；该用于信息通告的程序在被处理器读取执行时，执行以下操作：
IOAM节点利用扩展的PCEP封装IOAM能力信息，或者，利用扩展的PCEP-LS封装IOAM能力信息，或者，利用OpenFlow协议封装IOAM能力信息；通过传输模块将携带IOAM能力信息的PCEP消息、PCEP-LS报文或者OpenFlow协议消息发送给预定节点。
其中，处理器可以包括但不限于微处理器(Microcontroller Unit，MCU)或可编程逻辑器件(Field-Programmable Gate Array，FPGA)等的处理装置。
存储器可设置为存储应用软件的软件程序以及模块，如本申请的信息通告方法对应的程序指令/模块，处理器通过运行存储在存储器内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器可进一步包括相对于处理器远程设置的存储器，这些远程存储器可以通过网络连接至IOAM节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输模块可以设置为经由一个网络接收或者发送数据。在一个实例中，传输模块可以为射频(Radio Frequency，RF)模块，其设置为通过无线方式与互联网进行通信。
本申请实施例提供一种信息通告装置，应用于预定节点，包括：存储器以及一个或多个处理器；其中，存储器设置为存储用于信息通告的程序；该用于信息通告的程序在被处理器读取执行时，实现上述预定节点侧的信息通告方法。
本申请实施例还提供一种信息通告装置，应用于预定节点，包括：传输模块、存储器以及一个或多个处理器；其中，存储器设置为存储用于信息通告的程序；该用于信息通告的程序在被处理器读取执行时，执行以下操作：
接收IOAM节点发送的PCEP消息、PCEP-LS报文或者OpenFlow协议消息；从PCEP消息、PCEP-LS报文或者OpenFlow协议消息中解析IOAM节点通告的IOAM能力信息。
其中，处理器可以包括但不限于MCU或FPGA等的处理装置。
在一实施例中，上述的预定节点还可包括更多或者更少的组件，或者具有不同的配置。存储器可设置为存储应用软件的软件程序以及模块，如本申请实施例中的信息通告方法对应的程序指令/模块，处理器通过运行存储在存储器内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器可进一步包括相对于处理器远程设置的存储器，这些远程存储器可以通过网络连接至预定节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输模块可以设置为经由一个网络接收或者发送数据。在一个实例中，传输模块可以为射频(Radio Frequency，RF)模块，其设置为通过无线方式与互联网进行通信。
此外，本申请实施例还提供一种机器可读介质，存储有计算机程序，所述计算机程序被处理器执行时实现IOAM节点侧或预定节点侧的上述信息通告方法。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于机器可读介质中，如只读存储器、磁盘或光盘等计算机可读存储介质。在示例性实施方式中，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。本申请不限制于任何特定形式的硬件和软件的结合。
虽然本申请所揭露的实施方式如上，但所述的内容仅为便于理解本申请而采用的实施方式，并非用以限定本申请。
工业实用性
本公开通过扩展PCEP、PCEP-LS或者OpenFlow协议来收集IOAM域内支持IOAM功能的节点信息，从而实现预定节点收集到IOAM域内支持IOAM功能的节点信息。

Claims (21)

  1. 一种信息通告方法，包括：
    带内操作管理维护IOAM节点利用如下协议之一封装IOAM能力信息：扩展的路径计算单元通信协议PCEP、扩展的PCEP-链路状态LS、或者开放流OpenFlow协议；
    所述IOAM节点将携带所述IOAM能力信息的PCEP消息、PCEP-LS报文或者OpenFlow协议消息发送给预定节点。
  2. 根据权利要求1所述的方法，其中，所述预定节点为路径计算单元、网络管理系统中的控制器或网络管理系统中的网管。
  3. 根据权利要求1所述的方法，其中，所述IOAM节点利用扩展的PCEP封装IOAM能力信息，包括：
    所述IOAM节点扩展所述PCEP中的开放Open消息来携带所述IOAM能力信息。
  4. 根据权利要求1所述的方法，其中，所述IOAM节点利用扩展的PCEP-LS封装IOAM能力信息，包括：
    所述IOAM节点增加PCEP-LS对象；
    利用增加的所述PCEP-LS对象封装所述IOAM能力信息。
  5. 根据权利要求3所述的方法，其中，所述PCEP-LS对象包括以下至少之一：节点描述符类型长度值TLV、前缀描述符TLV以及链路描述符TLV；所述IOAM能力信息由以下至少之一携带：节点描述符TLV、前缀描述符TLV以及链路描述符TLV。
  6. 根据权利要求1所述的方法，其中，所述IOAM节点利用OpenFlow协议封装IOAM能力信息，包括：
    所述IOAM节点在流表功能响应table feature reply消息中封装所述IOAM能力信息。
  7. 根据权利要求6所述的方法，其中，所述IOAM节点在table feature reply消息中封装所述IOAM能力信息，包括：
    在所述table feature reply消息中增加一个或者多个IOAM匹配字段，并规定匹配所述一个或者多个IOAM匹配字段后所进行的操作。
  8. 根据权利要求1至7任一项所述的方法，其中，所述IOAM能力信息包括：IOAM的类型；其中，所述IOAM的类型包括：路径跟踪、路径验证以及端到端的验证。
  9. 根据权利要求8所述的方法，其中，所述IOAM能力信息还包括以下信息至少之一：路径跟踪的子类型、路径验证的子类型以及端到端的验证子类型。
  10. 一种信息通告方法，包括：
    预定节点接收带内操作管理维护IOAM节点发送的路径计算单元通信协议PCEP消息、PCEP-链路状态LS报文或者开放流OpenFlow协议消息；
    所述预定节点从所述PCEP消息、PCEP-LS报文或者OpenFlow协议消息中解析所述IOAM节点通告的IOAM能力信息。
  11. 根据权利要求10所述的方法，其中，所述预定节点为路径计算单元、网络管理系统中的控制器或网络管理系统中的网管。
  12. 根据权利要求10所述的方法，其中，所述IOAM能力信息由PCEP中的开放Open消息携带，或者，封装在增加的PCEP-LS对象中，或者，由OpenFlow协议的流表功能响应table feature reply消息携带。
  13. 根据权利要求12所述的方法，其中，所述PCEP-LS对象包括以下至少之一：节点描述符类型长度值TLV、前缀描述符TLV以及链路描述符TLV；所述IOAM能力信息由以下至少之一携带：节点描述符TLV、前缀描述符TLV以及链路描述符TLV。
  14. 根据权利要求10至13任一项所述的方法，其中，所述IOAM能力信息包括：IOAM的类型；其中，所述IOAM的类型包括：路径跟踪、路径验证以及端到端的验证。
  15. 根据权利要求14所述的方法，其中，所述IOAM能力信息还包括以下信息至少之一：路径跟踪的子类型、路径验证的子类型以及端到端的验证子类型。
  16. 一种信息通告装置，应用于带内操作管理维护IOAM节点，包括：
    处理模块，设置为利用如下协议之一封装IOAM能力信息：扩展的路径计算单元通信协议PCEP、扩展的PCEP-链路状态LS、或者开放流OpenFlow协议；
    发送模块，设置为：将携带所述IOAM能力信息的PCEP消息、PCEP-LS报文或者OpenFlow协议消息发送给预定节点。
  17. 一种信息通告装置，应用于预定节点，包括：
    接收模块，设置为：接收带内操作管理维护IOAM节点发送的路径计算单元通信协议PCEP消息、PCEP-链路状态LS报文或者开放流OpenFlow协议消息；
    解析模块，设置为：从所述PCEP消息、PCEP-LS报文或者OpenFlow协议消息中解析所述IOAM节点通告的IOAM能力信息。
  18. 一种信息通告装置，应用于带内操作管理维护IOAM节点，包括：存储器以及一个或多个处理器；其中，存储器设置为存储用于信息通告的程序；该用于信息通告的程序在被处理器读取执行时实现如权利要求1至9任一项所述的信息通告方法。
  19. 一种信息通告装置，应用于预定节点，包括：存储器以及一个或多个处理器；其中，存储器设置为存储用于信息通告的程序；该用于信息通告的程序在被处理器读取执行时，实现如权利要求10至15任一项所述的信息通告方法。
  20. 一种机器可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至9任一项所述的信息通告方法。
  21. 一种机器可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求10至15任一项所述的信息通告方法。
PCT/CN2018/083101 2017-04-13 2018-04-13 信息通告方法及装置 Ceased WO2018188663A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710241351.5A CN108737127B (zh) 2017-04-13 2017-04-13 一种信息通告方法及装置
CN201710241351.5 2017-04-13

Publications (1)

Publication Number Publication Date
WO2018188663A1 true WO2018188663A1 (zh) 2018-10-18

Family

ID=63792271

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/083101 Ceased WO2018188663A1 (zh) 2017-04-13 2018-04-13 信息通告方法及装置

Country Status (2)

Country Link
CN (1) CN108737127B (zh)
WO (1) WO2018188663A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112868214A (zh) * 2018-11-02 2021-05-28 思科技术公司 分组内的协调负载转移oam记录
CN113810229A (zh) * 2021-09-16 2021-12-17 烽火通信科技股份有限公司 一种基于时序调度的ioam质量性能数据分析方法和装置
EP4047888A4 (en) * 2019-11-19 2022-12-21 Huawei Technologies Co., Ltd. METHOD OF OUTPUTTING OAM CONFIGURATION INFORMATION AND CONTROL NODES

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109743340B (zh) * 2019-04-04 2019-07-30 华为技术有限公司 报文处理的方法和网络装置
CN113783745A (zh) * 2020-06-10 2021-12-10 中国电信股份有限公司 网络遥测信息采集方法和系统、bier域入口节点
CN114301839B (zh) * 2020-09-22 2023-05-12 华为技术有限公司 一种组播报文传输方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1848775A (zh) * 2005-09-30 2006-10-18 华为技术有限公司 多跳伪线故障检测、上报和维护协商控制方法
CN101335692A (zh) * 2007-06-27 2008-12-31 华为技术有限公司 协商pcc和pce之间安全能力的方法及其网络系统
CN101945048A (zh) * 2010-09-20 2011-01-12 中兴通讯股份有限公司 一种标签交换路径的建立方法、系统及装置
CN101986622A (zh) * 2010-11-08 2011-03-16 中兴通讯股份有限公司 一种pce状态属性的自动识别方法及系统
CN104579946A (zh) * 2013-10-21 2015-04-29 华为技术有限公司 确定路径计算单元的方法及通信设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105009544B (zh) * 2014-01-23 2018-04-20 华为技术有限公司 报文的隧道处理方法、交换设备及控制设备
CN105516015A (zh) * 2014-09-25 2016-04-20 中兴通讯股份有限公司 通知消息的获取、上报方法、装置及通知消息的交互系统
CN105306276B (zh) * 2015-11-13 2019-07-09 上海斐讯数据通信技术有限公司 基于软件定义网络的oam协议封装方法、系统及epon接入网

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1848775A (zh) * 2005-09-30 2006-10-18 华为技术有限公司 多跳伪线故障检测、上报和维护协商控制方法
CN101335692A (zh) * 2007-06-27 2008-12-31 华为技术有限公司 协商pcc和pce之间安全能力的方法及其网络系统
CN101945048A (zh) * 2010-09-20 2011-01-12 中兴通讯股份有限公司 一种标签交换路径的建立方法、系统及装置
CN101986622A (zh) * 2010-11-08 2011-03-16 中兴通讯股份有限公司 一种pce状态属性的自动识别方法及系统
CN104579946A (zh) * 2013-10-21 2015-04-29 华为技术有限公司 确定路径计算单元的方法及通信设备

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112868214A (zh) * 2018-11-02 2021-05-28 思科技术公司 分组内的协调负载转移oam记录
CN112868214B (zh) * 2018-11-02 2024-01-19 思科技术公司 分组内的协调负载转移oam记录
EP4047888A4 (en) * 2019-11-19 2022-12-21 Huawei Technologies Co., Ltd. METHOD OF OUTPUTTING OAM CONFIGURATION INFORMATION AND CONTROL NODES
CN113810229A (zh) * 2021-09-16 2021-12-17 烽火通信科技股份有限公司 一种基于时序调度的ioam质量性能数据分析方法和装置
CN113810229B (zh) * 2021-09-16 2023-12-05 烽火通信科技股份有限公司 一种基于时序调度的ioam质量性能数据分析方法和装置

Also Published As

Publication number Publication date
CN108737127B (zh) 2022-07-22
CN108737127A (zh) 2018-11-02

Similar Documents

Publication Publication Date Title
WO2018188663A1 (zh) 信息通告方法及装置
WO2018188662A1 (zh) 信息通告方法及装置
CN108737128B (zh) 一种实现带内操作管理维护ioam的方法及装置
EP3627792B1 (en) Method and device for automatically implementing ioam encapsulation, and storage medium
US10243827B2 (en) Techniques to use a network service header to monitor quality of service
US10439931B2 (en) Data packet processing method, service node, and delivery node
EP3787243B1 (en) Data packet processing method and apparatus, storage medium, and electronic device
WO2016089575A1 (en) Inter-domain service function chaining
CN111327445B (zh) 报文采样方法及解封装方法、节点、系统及存储介质
WO2016045098A1 (zh) 交换机、控制器、系统及链路质量检测方法
WO2018210213A1 (zh) 一种实现ioam封装的方法及装置、存储介质
CN103828310B (zh) 一种链路发现的方法、系统及设备
WO2015184771A1 (zh) 一种业务功能链操作、管理和维护方法及节点设备
WO2018121257A1 (zh) 报文发送方法、装置、系统以及存储介质
WO2015035616A1 (zh) 跨网通信方法及装置
US11489768B2 (en) Method for creating inter-domain bidirectional tunnel, communication method and device, and storage medium
US20220247655A1 (en) Method for Confirming In-Situ Flow Information Telemetry Capability and Device
CN110784402B (zh) 路径标识传输方法、装置和计算机可读存储介质
WO2017193732A1 (zh) 一种伪线数据报文的封装、解封装方法和相关装置
CN108075991B (zh) 报文转发方法及装置
WO2015154393A1 (zh) 业务节点能力处理方法、装置、业务分类器及业务控制器
CN107231309B (zh) 获取sdn全网视图的方法、控制器及目的交换节点
CN116366395A (zh) 一种报文传输的方法及装置
CN112751741B (zh) 一种报文的传输方法及装置
CN105991307B (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: 18783976

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18783976

Country of ref document: EP

Kind code of ref document: A1