WO2018210225A1 - 一种自动实现ioam封装的方法及装置、存储介质 - Google Patents

一种自动实现ioam封装的方法及装置、存储介质 Download PDF

Info

Publication number
WO2018210225A1
WO2018210225A1 PCT/CN2018/086834 CN2018086834W WO2018210225A1 WO 2018210225 A1 WO2018210225 A1 WO 2018210225A1 CN 2018086834 W CN2018086834 W CN 2018086834W WO 2018210225 A1 WO2018210225 A1 WO 2018210225A1
Authority
WO
WIPO (PCT)
Prior art keywords
ioam
configuration
tlvs
packet
configuration information
Prior art date
Application number
PCT/CN2018/086834
Other languages
English (en)
French (fr)
Inventor
魏月华
肖敏
陈然
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US16/614,449 priority Critical patent/US11177976B2/en
Priority to EP18801533.3A priority patent/EP3627792A4/en
Publication of WO2018210225A1 publication Critical patent/WO2018210225A1/zh

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/26—Special purpose or proprietary protocols or architectures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5601—Transfer mode dependent, e.g. ATM
    • H04L2012/5625—Operations, administration and maintenance [OAM]
    • 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, and in particular, to a method and apparatus, and a storage medium for automatically implementing in-band operation management and maintenance (IOAM, In-situ Operations, Administration and Maintenance, or In-band Operations, Administration and Maintenance).
  • IOAM in-band operation management and maintenance
  • In-situ Operations, Administration and Maintenance or In-band Operations, Administration and Maintenance
  • IOAM is a new data communication network operation management and maintenance (OAM) technology proposed by the industry. This technology is currently in the rapid development stage under the joint promotion of the industry, and is in the Internet Engineering Task Force (IETF). Carry out standardization work.
  • IETF Internet Engineering Task Force
  • IOAM is characterized in that IOAM data content is encapsulated into service data packets as service data packets. A part of the data is transmitted in the network, and the out-of-band OAM data content is encapsulated into a specially constructed OAM data message and transmitted as a separate protocol message in the network.
  • IOAM can implement functions that cannot be implemented by out-of-band OAM, such as detecting network nodes through which service data packets actually pass, verifying that the transmission path of service data is consistent with expectations, and adding traffic data packets. Serial number information to detect packet loss and out-of-order, etc. Accordingly, in order to implement the above functions, the network administrator needs to perform IOAM transmission nodes including an IOAM Transit Node and an IOAM Egress Node.
  • the IOAM transit node is a node that needs to process the IOAM data content on the service data packet transmission path. Given that IOAM includes a variety of optional features, as well as the type of traffic carried by the network and the variability of the transmission path, these configurations are often complex and easily changeable.
  • IOAM encapsulation is to insert an IOAM header (IOAM header) into the service data message.
  • Figure 1 is an IOAM header format diagram. As shown in Figure 1, the IOAM header is used to indicate the location of the IOAM data content (as in Figure 1). The IOAM header indication) and the length (such as the IOAM header length in Figure 1) also carry a set of IOAM function option types/lengths/values (TLVs, Type/Length/Value) as IOAM data content, where Each IOAM function option TLV corresponds to an IOAM function and carries the data required to complete the IOAM function.
  • TLVs IOAM function option type/lengths/values
  • the IOAM encapsulation in the network that is, the node inserted into the IOAM header is called an IOAM Ingress Node.
  • the IOAM ingress node can be either a network node such as a switch or a router, or a network terminal such as a personal computer or a server. Since the IOAM ingress node needs to complete the insertion of the IOAM header, it is necessary to determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, which is determined by the network administrator according to the configuration on each IOAM transmission node. It is determined and sent to the IOAM ingress node.
  • the configuration on the IOAM transit node is usually complicated and easy to change. Therefore, the method of implementing IOAM encapsulation by manually sending information at the IOAM ingress node increases network management. The burden of the staff is easy to make mistakes.
  • an embodiment of the present disclosure provides a method, an apparatus, and a storage medium for automatically implementing IOAM encapsulation.
  • the IOAM ingress node sends a first packet carrying the IOAM configuration request information to the IOAM centralized configuration point;
  • the IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • a sending unit configured to send, to the IOAM centralized configuration point, the first packet that carries the IOAM configuration request information
  • a receiving unit configured to receive a second packet that is sent by the IOAM centralized configuration point and that carries the IOAM configuration information of each IOAM transmission node;
  • the encapsulating unit is configured to perform IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • Embodiments of the present disclosure also provide a storage medium storing a computer program configured to perform the above-described method of automatically implementing IOAM encapsulation.
  • the IOAM ingress node sends a first packet carrying the IOAM configuration request information to the IOAM centralized configuration point; the IOAM ingress node receives the IOAM that is sent by the IOAM centralized configuration point and carries each IOAM transmission node. A second packet of the configuration information; the IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • the technical solution of the embodiment of the present disclosure solves the problem that the IOAM encapsulation node realizes the IOAM encapsulation by manually sending information at the IOAM ingress node, which increases the burden on the network administrator and is error-prone, and also enables the IOAM ingress node to support Automatically obtain the information required for IOAM encapsulation triggered by traffic.
  • FIG. 1 is a format diagram of an IOAM header according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart 1 of a method for automatically implementing IOAM encapsulation according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart 2 of a method for automatically implementing IOAM encapsulation according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of automatically implementing IOAM encapsulation by extending DHCP according to an embodiment of the present disclosure
  • FIG. 5 is a format diagram of a DHCP message according to an embodiment of the present disclosure.
  • FIG. 6 is a format diagram of an IOAM configuration information TLV according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of automatically implementing IOAM encapsulation by extending PCEP according to an embodiment of the present disclosure
  • FIG. 8 is a format diagram of a PCEP packet according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of an apparatus for automatically implementing an IOAM package according to an embodiment of the present disclosure.
  • FIG. 2 is a schematic flowchart 1 of a method for automatically implementing IOAM encapsulation according to an embodiment of the present disclosure. As shown in FIG. 2, the method for automatically implementing IOAM encapsulation includes the following steps:
  • Step 201 The IOAM ingress node sends a first packet carrying the IOAM configuration request information to the IOAM centralized configuration point.
  • the method further includes:
  • the IOAM configuration information of the IOAM transmission node corresponding to the identifier of the IOAM transmission node is carried in the second packet.
  • the IOAM ingress node obtains the identifiers of the IOAM transmission nodes on the service data packet transmission path by running the routing protocol and the signaling protocol, and the IOAM ingress node sends the identifiers of the IOAM transmission nodes together with the IOAM configuration request information to the IOAM centralized configuration. point.
  • the IOAM ingress node when the triggering operation of the network administrator is obtained, the IOAM ingress node sends a first packet carrying the IOAM configuration request information to the IOAM centralized configuration point; or
  • the IOAM ingress node When the triggering instruction of the network management module or the control application is obtained, the IOAM ingress node sends a first packet carrying the IOAM configuration request information to the IOAM centralized configuration point; or
  • the IOAM ingress node When the triggering of the service data packet is obtained, the IOAM ingress node sends a first packet carrying the IOAM configuration request information to the IOAM centralized configuration point.
  • Step 202 The IOAM ingress node receives the second packet that is sent by the IOAM centralized configuration point and carries the IOAM configuration information of each IOAM transmission node.
  • the IOAM configuration information of the respective IOAM transmission nodes is stored in the IOAM centralized configuration point, where the IOAM centralized configuration point pair is stored when the IOAM configuration information of the IOAM transmission node changes.
  • the IOAM configuration information is updated.
  • Step 203 The IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • the first packet is a request packet, and a set of TLVs is set in the request packet, where in the TLV, an IOAM configuration request is indicated by a type field, and a length field is used to represent the Describe the length of the TLV, and the value field indicates a group of IOAM transmission node identifiers;
  • the second packet is a response packet, and a set of TLVs is set in the response packet.
  • the type field indicates the IOAM configuration information
  • the length field indicates the length of the TLV.
  • the value field represents a set of IOAM configuration information.
  • the request message and the response message adopt a first protocol
  • the setting a set of TLVs in the response message is: setting a set of TLVs in the response message by using an option field.
  • the first protocol may be, but is not limited to, a Dynamic Host Configuration Protocol (DHCP).
  • DHCP Dynamic Host Configuration Protocol
  • the first packet is a DHCP request packet, and an option field is adopted in the DHCP request packet.
  • Setting a set of TLVs wherein, in the TLV, an IOAM configuration request is indicated by a type field, a length of the TLV is represented by a length field, and a set of IOAM transmission node identifiers is represented by a value field;
  • the second packet is And a DHCP response message, in the DHCP response message, a set of TLVs is set by using an option field, where, in the TLV, the type field indicates the IOAM configuration information, and the length field indicates the length of the TLV, and the value is The field represents a set of IOAM configuration information.
  • the value field indicates a group of IOAM configuration information, including: the value field includes one or more data lists, and each data list corresponds to IOAM configuration information of an IOAM transmission node, where the data list is in the data list.
  • the first field indicates the IOAM transmission node identifier
  • the second field indicates the length of the data list
  • the third field indicates the IOAM configuration information.
  • the third field includes a set of TLVs, wherein in the TLV, an IOAM function code supported by the IOAM transport node is indicated by a type field, a length of the TLV is represented by a length field, and an IOAM function is indicated by a value field. Configuration information.
  • the request message and the response message adopt a second protocol
  • Setting a set of TLVs in the request message where: setting a set of TLVs through the object field in the request message;
  • Setting a set of TLVs in the response message is: setting a set of TLVs through the object field in the response message.
  • the second protocol may be, but is not limited to, a Path Computation Element Protocol (PCEP).
  • PCEP Path Computation Element Protocol
  • the first packet is a PCEP request packet, and the object field is passed in the PCEP request packet.
  • Setting a set of TLVs wherein, in the TLV, an IOAM configuration request is indicated by a type field, a length of the TLV is represented by a length field, and a set of IOAM transmission node identifiers is represented by a value field;
  • the second packet is a PCEP response message, in the PCEP response message, a set of TLVs is set by using an object field, wherein in the TLV, the type field indicates the IOAM configuration information, and the length field indicates the length of the TLV, and the value is The field represents a set of IOAM configuration information.
  • the value field indicates a group of IOAM configuration information, including: the value field includes one or more data lists, and each data list corresponds to IOAM configuration information of an IOAM transmission node, where the data list is in the data list.
  • the first field indicates the IOAM transmission node identifier
  • the second field indicates the length of the data list
  • the third field indicates the IOAM configuration information.
  • the third field includes a set of TLVs, wherein in the TLV, an IOAM function code supported by the IOAM transport node is indicated by a type field, a length of the TLV is represented by a length field, and an IOAM function is indicated by a value field. Configuration information.
  • the IOAM ingress node determines, according to the IOAM configuration information of each IOAM transmission node, the IOAM function option TLVs included in the IOAM data content, and the length of each IOAM function option TLV; according to the IOAM function option TLVs and each IOAM function option The length of the TLV is inserted into the IOAM header in the service data message.
  • FIG. 3 is a schematic flowchart 2 of a method for automatically implementing IOAM encapsulation according to an embodiment of the present disclosure. As shown in FIG. 3, the method for automatically implementing IOAM encapsulation includes the following steps:
  • Step 301 The network administrator performs IOAM configuration on each IOAM transmission node through the network management, and saves the IOAM configuration information of each IOAM transmission node in the IOAM centralized configuration point.
  • the IOAM centralized configuration point is a device that stores IOAM configuration information of all nodes in the IOAM network domain. It can be set up with the network management system or an IOAM configuration server connected to the network management system.
  • Step 302 The IOAM ingress node sends a first packet carrying the IOAM transport node identifier and the IOAM configuration request information to the IOAM centralized configuration point.
  • the IOAM ingress node runs a routing protocol (such as the Open Shortest Path First (OSPF) protocol, the Intermediate System-to-Intermediate System (IS-IS) protocol), and the signaling protocol.
  • OSPF Open Shortest Path First
  • IS-IS Intermediate System-to-Intermediate System
  • the signaling protocol For example, the Resource Reservation Protocol (RSVP) and the Label Distribution Protocol (LDP) can obtain the identifiers of the IOAM transmission nodes (referred to as IOAM transmission node identifiers) on the service data packet transmission path.
  • the IOAM ingress node sends these IOAM transport node identities along with the IOAM configuration request information to the IOAM centralized configuration point.
  • the timing at which the IOAM ingress node sends the first packet carrying the IOAM configuration request information to the IOAM centralized configuration point is very flexible, and may be sent under the trigger of the network administrator, or may be triggered by the network management/control application. Send it, or send it under the trigger of the service data packet.
  • Step 303 The IOAM centrally configures the point response request, and returns a second packet carrying the IOAM configuration information of each IOAM transmission node to the IOAM ingress node.
  • the IOAM centralized configuration point receives the first packet carrying the IOAM transmission node identifier and the IOAM configuration request information sent by the IOAM ingress node, and then returns the second packet carrying the IOAM configuration information of each IOAM transmission node to the IOAM ingress node.
  • These IOAM transport nodes are the nodes corresponding to the IOAM transport node identities sent by the IOAM ingress node.
  • the IOAM configuration information of the IOAM transmission node includes which IOAM capabilities are supported by the node, and the enabling status and related parameter configuration of each IOAM capability.
  • Step 304 The IOAM ingress node performs IOAM encapsulation according to the IOAM configuration information of each IOAM transmission node in the second packet.
  • the IOAM ingress node After the IOAM ingress node obtains the IOAM configuration of each node on the service data packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, thereby enabling IOAM encapsulation.
  • FIG. 4 is a schematic diagram of automatically implementing IOAM encapsulation by extending DHCP according to an embodiment of the present disclosure.
  • the IOAM ingress node and the IOAM centralized configuration point perform the following steps:
  • Step 11 The network administrator performs IOAM configuration on the IOAM transmission node through the network management, and saves the IOAM configuration information of each IOAM transmission node in the IOAM centralized configuration point.
  • the IOAM centralized configuration point is an IOAM configuration server connected to the network management system, and the server also serves as a DHCP server that dynamically allocates an IP address.
  • Step 12 The IOAM ingress node sends a DHCP request message carrying the IOAM transport node identifier and the IOAM configuration request information to the IOAM configuration server.
  • FIG. 5 is a format diagram of a DHCP message.
  • the DHCP request message contains a set of options in the form of TLVs.
  • TLV time difference
  • the length field indicates the length of the TLV
  • the value field indicates a group of IOAM transmission node identifiers, so that the DHCP request message carries the IOAM transmission node identifier and the IOAM configuration request information.
  • Step 13 The IOAM configuration server responds to the request and returns a DHCP response message carrying the IOAM configuration information of each IOAM transmission node to the IOAM ingress node.
  • the IOAM configuration server After receiving the DHCP request message carrying the IOAM transmission node identifier and the IOAM configuration request information, the IOAM configuration server sends a DHCP request message sending node, that is, an IOAM ingress node, to the DHCP carrying the IOAM configuration information of each IOAM transmission node.
  • the response packet may be in the option field of writing the IOAM configuration information in the form of a TLV into the DHCP response message.
  • Figure 6 is a format diagram of the IOAM configuration information TLV. As shown in Figure 6, the Type field of the TLV. Indicates the IOAM configuration information, the Length field indicates the length of the TLV, and the Value field contains a set of IOAM configuration information.
  • each DataList carries The IOAM configuration information of an IOAM transmission node, where one field indicates "IOAM transmission node identifier", another field indicates the length of the DataList, and further includes a set of sub-TLVs (Sub-TLVs), each Sub-TLV Carrying configuration information of an IOAM function, where a Sub-Type field indicates a code of an IOAM function supported by the IOAM transmission node, The Length field indicates the length of the Sub-TLV, and the Value field indicates the configuration information of the IOAM function represented by the Sub-Type field, including whether the IOAM function is enabled in the node, and when enabled, the IOAM is enabled.
  • DataList data list
  • each DataList carries The IOAM configuration information of an IOAM transmission node, where one field indicates "IOAM transmission node identifier", another field indicates the length of the DataList, and further includes a set of sub-TLVs (Sub-TLVs), each Sub-TLV Carrying configuration information of an IOAM function
  • Function-related configuration parameter values such as the configuration parameters related to the IOAM tracing function defined by the IETF proposal draft-brockners-inband-oam-data, include: Pre-allocated mode or Incremental The mode inserts node information and the number of bytes required for node information.
  • Step 14 After obtaining the IOAM configuration information of each IOAM transmission node on the service data packet transmission path, the IOAM ingress node performs IOAM encapsulation.
  • the IOAM ingress node After the IOAM ingress node obtains the IOAM configuration information of each IOAM transmission node on the service data packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, so that the service data can be performed.
  • the IOAM encapsulation of the message After the IOAM ingress node obtains the IOAM configuration information of each IOAM transmission node on the service data packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, so that the service data can be performed.
  • the IOAM encapsulation of the message After the IOAM ingress node obtains the IOAM configuration information of each IOAM transmission node on the service data packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, so
  • FIG. 7 is a schematic diagram of automatic implementation of IOAM encapsulation by extending PCEP.
  • the IOAM ingress node and the IOAM centralized configuration point perform the following steps:
  • Step 21 The network administrator performs IOAM configuration on the IOAM transmission node through the network management, and saves the IOAM configuration information of each IOAM transmission node in the IOAM centralized configuration point.
  • the IOAM centralized configuration point is the network management itself.
  • Step 22 The IOAM ingress node sends a PCEP request packet carrying the IOAM transport node identifier and the IOAM configuration request information to the network management.
  • FIG 8 is a format diagram of a PCEP packet.
  • the PCEP request packet contains a set of objects (Objects) in the form of TLVs.
  • the Type field indicates an IOAM configuration request
  • the Length field indicates The length of the TLV
  • the Value field indicates a set of IOAM transport node identifiers, so that the PCEP request message carries the IOAM transport node identifier and the IOAM configuration request information.
  • Step 23 The network management system responds to the request, and returns a PCEP response message carrying the IOAM configuration information of each IOAM transmission node to the IOAM ingress node.
  • the network management system After receiving the PCEP request message carrying the IOAM transmission node identifier and the IOAM configuration request information, the network management system sends a PCEP response packet to the PCEP request packet sending node, that is, the IOAM ingress node, and replies with the IOAM configuration information of each IOAM transmission node.
  • the carrying manner may be that the IOAM configuration information is written into the object field of the PCEP response message in the form of a TLV, and the TLV adopts the format shown in FIG. 6.
  • Step 24 After obtaining the IOAM configuration information of each IOAM transmission node on the service data packet transmission path, the IOAM ingress node performs IOAM encapsulation.
  • the IOAM ingress node After the IOAM ingress node obtains the IOAM configuration information of each IOAM transmission node on the service data packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, so that the service data can be performed.
  • the IOAM encapsulation of the message After the IOAM ingress node obtains the IOAM configuration information of each IOAM transmission node on the service data packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, so that the service data can be performed.
  • the IOAM encapsulation of the message After the IOAM ingress node obtains the IOAM configuration information of each IOAM transmission node on the service data packet transmission path, it can determine which IOAM function option TLVs and the length of each IOAM function option TLV are included in the IOAM data content, so
  • FIG. 9 is a schematic structural diagram of an apparatus for automatically implementing an IOAM package according to an embodiment of the present disclosure. As shown in FIG. 9, the apparatus includes:
  • the sending unit 91 is configured to send, to the IOAM centralized configuration point, the first packet that carries the IOAM configuration request information.
  • the receiving unit 92 is configured to receive, by the IOAM centralized configuration point, a second packet that carries the IOAM configuration information of each IOAM transmission node;
  • the encapsulating unit 93 is configured to perform IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • the device further includes:
  • the obtaining unit 94 is configured to obtain an identifier of each IOAM transmission node on the service data packet transmission path;
  • the IOAM configuration information of the IOAM transmission node corresponding to the identifier of the IOAM transmission node is carried in the second packet.
  • the IOAM configuration information of the respective IOAM transmission nodes is stored in the IOAM centralized configuration point, where the IOAM centralized configuration point pair is stored when the IOAM configuration information of the IOAM transmission node changes.
  • the IOAM configuration information is updated.
  • the sending unit 91 is configured to: when the triggering operation of the network administrator is obtained, send the first packet carrying the IOAM configuration request information to the IOAM centralized configuration point; or, when obtaining the network management module or the control When the triggering instruction is applied, the first packet carrying the IOAM configuration request information is sent to the IOAM centralized configuration point; or, when the service data packet is triggered, the first packet carrying the IOAM configuration request information is sent to the IOAM centralized configuration point. Text.
  • the first packet is a request packet, and a set of TLVs is set in the request packet, where in the TLV, an IOAM configuration request is indicated by a type field, and a length field is used to represent the Describe the length of the TLV, and the value field indicates a group of IOAM transmission node identifiers;
  • the second packet is a response packet, and a set of TLVs is set in the response packet.
  • the type field indicates the IOAM configuration information
  • the length field indicates the length of the TLV.
  • the value field represents a set of IOAM configuration information.
  • the request message and the response message adopt a first protocol
  • the setting a set of TLVs in the response message is: setting a set of TLVs in the response message by using an option field.
  • the request message and the response message adopt a second protocol
  • Setting a set of TLVs in the request message where: setting a set of TLVs through the object field in the request message;
  • Setting a set of TLVs in the response message is: setting a set of TLVs through the object field in the response message.
  • the value field indicates a group of IOAM configuration information, including:
  • the value field includes one or more data lists, each data list corresponding to an IOAM configuration information of an IOAM transmission node, where, in the data list, the first field indicates an IOAM transmission node identifier, and the second field is Indicates the length of the data list, and the third field indicates the IOAM configuration information.
  • the third field includes a set of TLVs, where in the TLV, an IOAM function code supported by the IOAM transport node is indicated by the type field, and the length of the TLV is represented by a length field.
  • the value field indicates the configuration information of the IOAM function.
  • the implementation functions of the units in the apparatus for automatically implementing the IOAM package shown in FIG. 9 can be understood by referring to the foregoing description of the method for automatically implementing the IOAM package.
  • the functions of the units in the apparatus for automatically implementing the IOAM package shown in FIG. 9 can be realized by a program running on the processor, or can be realized by a specific logic circuit.
  • each unit in the device that automatically implements the IOAM package may be implemented by a central processing unit (CPU), or a microprocessor (MPU, Micro Processor Unit), or a digital signal. Processor (DSP, Digital Signal Processor), or Field Programmable Gate Array (FPGA) implementation.
  • CPU central processing unit
  • MPU Microprocessor
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • embodiments of the present disclosure can be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware aspects. Moreover, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the embodiment of the present invention further provides a storage medium, wherein a computer program is configured, and the computer program is configured to perform the method for automatically implementing IOAM encapsulation in the embodiment of the present invention.
  • the IOAM ingress node sends a first packet carrying the IOAM configuration request information to the IOAM centralized configuration point; the IOAM ingress node receives the IOAM that is sent by the IOAM centralized configuration point and carries each IOAM transmission node. A second packet of the configuration information; the IOAM ingress node performs IOAM encapsulation on the service data packet according to the IOAM configuration information of each IOAM transmission node.
  • the method for implementing IOAM encapsulation by manually sending information at the IOAM ingress node in the related art is solved, which increases the burden on the network administrator and is prone to error, and also enables the IOAM ingress node to support automatic triggering of service traffic. Get the information needed for IOAM packaging.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Automation & Control Theory (AREA)
  • Library & Information Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Small-Scale Networks (AREA)

Abstract

本公开公开了一种自动实现IOAM封装的方法及装置、存储介质，所述方法包括：IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；所述IOAM入口节点接收所述IOAM集中配置点发送的携带各个IOAM传输节点的IOAM配置信息的第二报文；所述IOAM入口节点根据各个IOAM传输节点的IOAM配置信息，对业务数据报文进行IOAM封装。

Description

一种自动实现IOAM封装的方法及装置、存储介质
相关申请的交叉引用
本申请基于申请号为201710352927.5、申请日为2017年05月18日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及通信领域，尤其涉及一种自动实现带内操作管理维护(IOAM，In-situ Operations、Administration and Maintenance或者In-band Operations、Administration and Maintenance)封装的方法及装置、存储介质。
背景技术
IOAM是业界新提出的一种数据通信网络操作管理维护(OAM)技术，该技术目前在业界的共同推动下处于快速发展阶段，且正在国际标准化组织互联网工程任务组(IETF，Internet Engineering Task Force)开展标准化的工作。
IETF的IOAM系列提案draft-brockners-inband-oam-requirements、draft-brockners-inband-oam-transport和draft-brockners-inband-oam-data分别描述了IOAM的需求来源、封装格式和数据内容，与已经完成标准化并在数据通信网络中广泛部署的带外OAM(Out-of-band Operations、Administration and Maintenance)相比较，IOAM的特点是IOAM数据内容被封装进业务数据报文中，作为业务数据报文的一部分在网络中传递，而带外OAM数据内容则是被封装进专门构造的OAM数据报文中，作为单独的协议报文在网络中传递。作为带外OAM的补充，IOAM可以实现一些带 外OAM所不能实现的功能，比如探测业务数据报文实际经过的网络节点，验证业务数据的传输路径与预期是否一致，以及给业务数据报文添加序列号信息以检测丢包和乱序等，相应地，为了实现上述功能，网络管理员需要对包括IOAM中间节点(IOAM Transit Node)和IOAM出口节点(IOAM Egress Node)在内的IOAM传输节点进行配置，IOAM传输节点就是业务数据报文传输路径上需要对IOAM数据内容进行处理的节点。考虑到IOAM包含多种可选的功能，以及网络所承载业务流量的类型和传输路径的易变性，上述配置通常是比较复杂且易于改变的。
IOAM封装就是给业务数据报文插入一个IOAM头部(IOAM Header)，图1是IOAM头部格式图，如图1所示，IOAM头部除了用于指示IOAM数据内容的位置(如图1中的IOAM头部指示)和长度(如图1中的IOAM头部长度)，还携带了作为IOAM数据内容的一组IOAM功能选项类型/长度/取值(TLVs，Type/Length/Value)，其中每个IOAM功能选项TLV对应一种IOAM功能并携带了完成该IOAM功能所需的数据。网络中负责IOAM封装，也即插入IOAM头部的节点被称为IOAM入口节点(IOAM Ingress Node)，IOAM入口节点既可以是交换机或路由器等网络节点，也可以是个人电脑或服务器等网络终端。IOAM入口节点由于要完成IOAM头部的插入，所以需要确定IOAM数据内容包含哪些IOAM功能选项TLVs以及每个IOAM功能选项TLV的长度，这些信息由网络管理员根据各IOAM传输节点上的配置情况加以确定并下发给IOAM入口节点，如前所述，IOAM传输节点上的配置通常是比较复杂且易于改变的，所以这种在IOAM入口节点通过人工下发信息实现IOAM封装的方法增加了网络管理员的负担，且容易出错。
发明内容
为解决上述技术问题，本公开实施例提供了一种自动实现IOAM封装 的方法及装置、存储介质。
本公开实施例提供的自动实现带内IOAM封装的方法，包括：
IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；
所述IOAM入口节点接收所述IOAM集中配置点发送的携带各个IOAM传输节点的IOAM配置信息的第二报文；
所述IOAM入口节点根据各个IOAM传输节点的IOAM配置信息，对业务数据报文进行IOAM封装。
本公开实施例提供的自动实现IOAM封装的装置，包括：
发送单元，配置为向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；
接收单元，配置为接收所述IOAM集中配置点发送的携带各个IOAM传输节点的IOAM配置信息的第二报文；
封装单元，配置为根据各个IOAM传输节点的IOAM配置信息，对业务数据报文进行IOAM封装。
本公开实施例还提供一种存储介质，该存储介质存储有计算机程序，该计算机程序配置为执行上述自动实现IOAM封装的方法。
本公开实施例的技术方案中，IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；所述IOAM入口节点接收所述IOAM集中配置点发送的携带各个IOAM传输节点的IOAM配置信息的第二报文；所述IOAM入口节点根据各个IOAM传输节点的IOAM配置信息，对业务数据报文进行IOAM封装。采用本公开实施例的技术方案，解决了相关技术中在IOAM入口节点通过人工下发信息实现IOAM封装的方法增加了网络管理员的负担，且容易出错的问题，同时也使得IOAM入口节点能够支持在业务流量的触发下自动获取IOAM封装所需信息。
附图说明
附图以示例而非限制的方式大体示出了本文中所讨论的各个实施例。
图1为本公开实施例的IOAM头部格式图；
图2为本公开实施例的自动实现IOAM封装的方法的流程示意图一；
图3为本公开实施例的自动实现IOAM封装的方法的流程示意图二；
图4为本公开实施例的通过扩展DHCP自动实现IOAM封装的示意图；
图5为本公开实施例的DHCP报文的格式图；
图6为本公开实施例的IOAM配置信息TLV的格式图；
图7为本公开实施例的通过扩展PCEP自动实现IOAM封装的示意图；
图8为本公开实施例的PCEP报文的格式图；
图9为本公开实施例的自动实现IOAM封装的装置的结构组成示意图。
具体实施方式
为了能够更加详尽地了解本公开实施例的特点与技术内容，下面结合附图对本公开实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本公开实施例。
图2为本公开实施例的自动实现IOAM封装的方法的流程示意图一，如图2所示，所述自动实现IOAM封装的方法包括以下步骤：
步骤201：IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文。
本公开实施例中，所述方法还包括：
所述IOAM入口节点获取业务数据报文传输路径上各个IOAM传输节点的标识；
在所述第一报文中携带所述IOAM配置请求信息的同时，还携带所述各个IOAM传输节点的标识，其中，所述IOAM传输节点的标识用于指示所述IOAM集中配置点将与所述IOAM传输节点的标识对应的IOAM传输 节点的IOAM配置信息携带在所述第二报文中。
这里，IOAM入口节点通过运行路由协议和信令协议获取业务数据报文传输路径上各IOAM传输节点的标识，IOAM入口节点会把这些IOAM传输节点的标识连同IOAM配置请求信息一道发送给IOAM集中配置点。
本公开实施例中，当获得网络管理员的触发操作时，所述IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；或者，
当获得网络管理模块或控制应用的触发指令时，所述IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；或者，
当获得业务数据报文的触发时，所述IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文。
步骤202：所述IOAM入口节点接收所述IOAM集中配置点发送的携带各个IOAM传输节点的IOAM配置信息的第二报文。
本公开实施例中，所述IOAM集中配置点中存储有所述各个IOAM传输节点的IOAM配置信息，其中，当IOAM传输节点的IOAM配置信息发生变化时，所述IOAM集中配置点对所存储的IOAM配置信息进行更新。
步骤203：所述IOAM入口节点根据各个IOAM传输节点的IOAM配置信息，对业务数据报文进行IOAM封装。
本公开实施例中，所述第一报文为请求报文，在所述请求报文中设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置请求，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM传输节点标识；
所述第二报文为响应报文，在所述响应报文中设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置信息，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM配置信息。
在一实施方式中，所述请求报文和所述响应报文采用第一协议；
所述在所述请求报文中设置一组TLV，为：在所述请求报文中通过选项字段设置一组TLV；
所述在所述响应报文中设置一组TLV，为：在所述响应报文中通过选项字段设置一组TLV。
具体地，第一协议可以但不局限于是动态主机配置协议(DHCP，Dynamic Host Configuration Protocol)，相应地，所述第一报文为DHCP请求报文，在所述DHCP请求报文中通过选项字段设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置请求，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM传输节点标识；所述第二报文为DHCP响应报文，在所述DHCP响应报文中通过选项字段设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置信息，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM配置信息。所述通过取值字段表示一组IOAM配置信息，包括：所述取值字段包括一个或多个数据列表，每个数据列表对应一个IOAM传输节点的IOAM配置信息，其中，在所述数据列表中，通过第一字段表示IOAM传输节点标识，通过第二字段表示所述数据列表的长度，通过第三字段表示IOAM配置信息。所述第三字段包括一组TLV，其中，在所述TLV中，通过类型字段表示IOAM传输节点支持的一种IOAM功能代码，通过长度字段表示所述TLV的长度，通过取值字段表示IOAM功能的配置信息。
在另一实施方式中，所述请求报文和所述响应报文采用第二协议；
所述在所述请求报文中设置一组TLV，为：在所述请求报文中通过对象字段设置一组TLV；
所述在所述响应报文中设置一组TLV，为：在所述响应报文中通过对象字段设置一组TLV。
具体地，第二协议可以但不局限于是路径计算单元协议(PCEP，Path  Computation Element Protocol)，相应地，所述第一报文为PCEP请求报文，在所述PCEP请求报文中通过对象字段设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置请求，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM传输节点标识；所述第二报文为PCEP响应报文，在所述PCEP响应报文中通过对象字段设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置信息，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM配置信息。所述通过取值字段表示一组IOAM配置信息，包括：所述取值字段包括一个或多个数据列表，每个数据列表对应一个IOAM传输节点的IOAM配置信息，其中，在所述数据列表中，通过第一字段表示IOAM传输节点标识，通过第二字段表示所述数据列表的长度，通过第三字段表示IOAM配置信息。所述第三字段包括一组TLV，其中，在所述TLV中，通过类型字段表示IOAM传输节点支持的一种IOAM功能代码，通过长度字段表示所述TLV的长度，通过取值字段表示IOAM功能的配置信息。
之后，IOAM入口节点根据各个IOAM传输节点的IOAM配置信息，确定IOAM数据内容所包括的IOAM功能选项TLVs、以及每个IOAM功能选项TLV的长度；根据所述IOAM功能选项TLVs以及每个IOAM功能选项TLV的长度，在业务数据报文中插入IOAM头部。
图3为本公开实施例的自动实现IOAM封装的方法的流程示意图二，如图3所示，所述自动实现IOAM封装的方法包括以下步骤：
步骤301：网络管理员通过网管对各个IOAM传输节点进行IOAM配置，并把各个IOAM传输节点的IOAM配置信息保存在IOAM集中配置点中。
这里，IOAM集中配置点是一个保存有IOAM网络域中所有节点的IOAM配置信息的设备，它既可以与网管合设，也可以是与网管相连的一 个IOAM配置服务器。
步骤302：IOAM入口节点向IOAM集中配置点发送携带IOAM传输节点标识和IOAM配置请求信息的第一报文。
这里，IOAM入口节点通过运行路由协议(比如开放式最短路径优先(OSPF，Open Shortest Path First)协议、中间系统到中间系统(IS-IS，Intermediate System-to-Intermediate System)协议)和信令协议(比如资源预留协议(RSVP，Resource Reservation Protocol)、标签分发协议(LDP，Label Distribution Protocol))，能够获取业务数据报文传输路径上各个IOAM传输节点的标识(简称为IOAM传输节点标识)，IOAM入口节点会把这些IOAM传输节点标识连同IOAM配置请求信息一同发送给IOAM集中配置点。
本公开实施例中，IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文的时机非常灵活，可以在网络管理员的触发下发送，或者可以在网络管理/控制应用的触发下发送，或者也可以在业务数据报文的触发下发送。
步骤303：IOAM集中配置点响应请求，向IOAM入口节点回复携带各个IOAM传输节点的IOAM配置信息的第二报文。
这里，IOAM集中配置点接收到IOAM入口节点发送的携带IOAM传输节点标识和IOAM配置请求信息的第一报文后，向IOAM入口节点回复携带各个IOAM传输节点的IOAM配置信息的第二报文，这些IOAM传输节点就是与IOAM入口节点所发送的IOAM传输节点标识相对应的节点。IOAM传输节点的IOAM配置信息包括该节点支持哪些IOAM能力以及各IOAM能力的使能情况和相关参数配置。
步骤304：IOAM入口节点根据第二报文中的各个IOAM传输节点的IOAM配置信息，进行IOAM封装。
这里，IOAM入口节点获取业务数据报文传输路径上各个节点的IOAM配置后，就能够确定IOAM数据内容包含哪些IOAM功能选项TLVs以及每个IOAM功能选项TLV的长度，也就能够进行IOAM封装。
下面结合具体应用示例对本公开实施例的技术方案作进一步详细描述。
实施例一
图4为本公开实施例的通过扩展DHCP自动实现IOAM封装的示意图。本实施例中，IOAM入口节点与IOAM集中配置点要执行如下步骤：
步骤11：网络管理员通过网管对IOAM传输节点进行IOAM配置，并把各IOAM传输节点的IOAM配置信息保存在IOAM集中配置点。
在本实施例中，IOAM集中配置点是与网管相连的IOAM配置服务器，该服务器同时还作为动态分配IP地址的DHCP服务器。
步骤12：IOAM入口节点向IOAM配置服务器发送携带IOAM传输节点标识和IOAM配置请求信息的DHCP请求报文。
图5是DHCP报文的格式图，如图5所示，DHCP请求报文包含一组TLV形式的选项(Options)，通过增加一个新的选项TLV，其中类型(Type)字段表示IOAM配置请求，长度(Length)字段表示该TLV的长度，取值(Value)字段表示一组IOAM传输节点标识，就可以使得DHCP请求报文携带IOAM传输节点标识和IOAM配置请求信息。
步骤13：IOAM配置服务器响应请求，向IOAM入口节点回复携带各个IOAM传输节点的IOAM配置信息的DHCP响应报文。
IOAM配置服务器在收到携带IOAM传输节点标识和IOAM配置请求信息的DHCP请求报文后，会向DHCP请求报文发送节点，也即IOAM入口节点，回复携带各个IOAM传输节点的IOAM配置信息的DHCP响应报文，携带的方式可以是把IOAM配置信息以一个TLV的形式写入DHCP响 应报文的选项字段，图6是IOAM配置信息TLV的格式图，如图6所示，该TLV的Type字段表示IOAM配置信息，Length字段表示该TLV的长度，Value字段包含一组IOAM的配置信息，Value字段里面所包含的信息的组织有不同的结构，具体通过数据列表(DataList)表示，每个DataList携带一个IOAM传输节点的IOAM配置信息，其中通过一个字段表示“IOAM传输节点标识”，通过另一个字段表示该DataList的长度，此外，还包含一组子TLVs(Sub-TLVs)，每个Sub-TLV携带一种IOAM功能的配置信息，其中子类型(Sub-Type)字段表示IOAM传输节点支持的一种IOAM功能的代码，Length字段表示该Sub-TLV的长度，Value字段表示Sub-Type字段所代表的IOAM功能的配置信息，包括该IOAM功能是否在本节点使能(Enabled)，以及在使能的情况下与该IOAM功能相关的配置参数值，比如，IETF提案draft-brockners-inband-oam-data所定义的IOAM跟踪(Tracing)功能相关的配置参数就包括：采用预分配(Pre-allocated)模式还是递增(Incremental)模式插入节点信息，以及节点信息所需占用的字节数。
步骤14：IOAM入口节点获取业务数据报文传输路径上各个IOAM传输节点的IOAM配置信息后，进行IOAM封装。
IOAM入口节点获取业务数据报文传输路径上各个IOAM传输节点的IOAM配置信息后，就能够确定IOAM数据内容包含哪些IOAM功能选项TLVs以及每个IOAM功能选项TLV的长度，也就能够进行针对业务数据报文的IOAM封装。
实施例二
图7是通过扩展PCEP自动实现IOAM封装的示意图。本实施例中，IOAM入口节点与IOAM集中配置点要执行如下步骤：
步骤21：网络管理员通过网管对IOAM传输节点进行IOAM配置，并把各IOAM传输节点的IOAM配置信息保存在IOAM集中配置点。
在本实施例中，IOAM集中配置点就是网管本身。
步骤22：IOAM入口节点向网管发送携带IOAM传输节点标识和IOAM配置请求信息的PCEP请求报文。
图8是PCEP报文的格式图，如图8所示，PCEP请求报文包含一组TLV形式的对象(Objects)，通过增加一个新的对象TLV，其中Type字段表示IOAM配置请求，Length字段表示该TLV的长度，Value字段表示一组IOAM传输节点标识，就可以使得PCEP请求报文携带IOAM传输节点标识和IOAM配置请求信息。
步骤23：网管响应请求，向IOAM入口节点回复携带各IOAM传输节点IOAM配置信息的PCEP响应报文。
网管在收到携带IOAM传输节点标识和IOAM配置请求信息的PCEP请求报文后，会向PCEP请求报文发送节点，也即IOAM入口节点，回复携带各IOAM传输节点IOAM配置信息的PCEP响应报文，携带的方式可以是把IOAM配置信息以一个TLV的形式写入PCEP响应报文的对象字段，该TLV采用如图6所示的格式。
步骤24：IOAM入口节点获取业务数据报文传输路径上各个IOAM传输节点的IOAM配置信息后，进行IOAM封装。
IOAM入口节点获取业务数据报文传输路径上各个IOAM传输节点的IOAM配置信息后，就能够确定IOAM数据内容包含哪些IOAM功能选项TLVs以及每个IOAM功能选项TLV的长度，也就能够进行针对业务数据报文的IOAM封装。
图9为本公开实施例的自动实现IOAM封装的装置的结构组成示意图，如图9所示，所述装置包括：
发送单元91，配置为向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；
接收单元92，配置为接收所述IOAM集中配置点发送的携带各个IOAM传输节点的IOAM配置信息的第二报文；
封装单元93，配置为根据各个IOAM传输节点的IOAM配置信息，对业务数据报文进行IOAM封装。
本公开实施例中，所述装置还包括：
获取单元94，配置为获取业务数据报文传输路径上各个IOAM传输节点的标识；
在所述第一报文中携带所述IOAM配置请求信息的同时，还携带所述各个IOAM传输节点的标识，其中，所述IOAM传输节点的标识用于指示所述IOAM集中配置点将与所述IOAM传输节点的标识对应的IOAM传输节点的IOAM配置信息携带在所述第二报文中。
本公开实施例中，所述IOAM集中配置点中存储有所述各个IOAM传输节点的IOAM配置信息，其中，当IOAM传输节点的IOAM配置信息发生变化时，所述IOAM集中配置点对所存储的IOAM配置信息进行更新。
本公开实施例中，所述发送单元91，配置为当获得网络管理员的触发操作时，向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；或者，当获得网络管理模块或控制应用的触发指令时，向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；或者，当获得业务数据报文的触发时，向IOAM集中配置点发送携带IOAM配置请求信息的第一报文。
本公开实施例中，所述第一报文为请求报文，在所述请求报文中设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置请求，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM传输节点标识；
所述第二报文为响应报文，在所述响应报文中设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置信息，通过长度字段表示所 述TLV的长度，通过取值字段表示一组IOAM配置信息。
本公开实施例中，所述请求报文和所述响应报文采用第一协议；
所述在所述请求报文中设置一组TLV，为：在所述请求报文中通过选项字段设置一组TLV；
所述在所述响应报文中设置一组TLV，为：在所述响应报文中通过选项字段设置一组TLV。
本公开实施例中，所述请求报文和所述响应报文采用第二协议；
所述在所述请求报文中设置一组TLV，为：在所述请求报文中通过对象字段设置一组TLV；
所述在所述响应报文中设置一组TLV，为：在所述响应报文中通过对象字段设置一组TLV。
本公开实施例中，所述通过取值字段表示一组IOAM配置信息，包括：
所述取值字段包括一个或多个数据列表，每个数据列表对应一个IOAM传输节点的IOAM配置信息，其中，在所述数据列表中，通过第一字段表示IOAM传输节点标识，通过第二字段表示所述数据列表的长度，通过第三字段表示IOAM配置信息。
本公开实施例中，所述第三字段包括一组TLV，其中，在所述TLV中，通过类型字段表示IOAM传输节点支持的一种IOAM功能代码，通过长度字段表示所述TLV的长度，通过取值字段表示IOAM功能的配置信息。
本领域技术人员应当理解，图9所示的自动实现IOAM封装的装置中的各单元的实现功能可参照前述自动实现IOAM封装的方法的相关描述而理解。图9所示的自动实现IOAM封装的装置中的各单元的功能可通过运行于处理器上的程序而实现，也可通过具体的逻辑电路而实现。
在实际应用中，所述自动实现IOAM封装的装置中的各个单元所实现的功能，均可由中央处理器(CPU，Central Processing Unit)、或微处理器 (MPU，Micro Processor Unit)、或数字信号处理器(DSP，Digital Signal Processor)、或现场可编程门阵列(FPGA，Field Programmable Gate Array)等实现。
本领域内的技术人员应明白，本公开的实施例可提供为方法、系统、或计算机程序产品。因此，本公开可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
相应地，本发明实施例还提供一种存储介质，其中存储有计算机程序，该计算机程序配置为执行本发明实施例的自动实现IOAM封装的方法。
以上所述，仅为本公开的较佳实施例而已，并非用于限定本公开的保护范围。
工业实用性
本公开实施例的技术方案中，IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；所述IOAM入口节点接收所述IOAM集中配置点发送的携带各个IOAM传输节点的IOAM配置信息的第二报文；所述IOAM入口节点根据各个IOAM传输节点的IOAM配置信息，对业务数据报文进行IOAM封装。如此，解决了相关技术中在IOAM入口节点通过人工下发信息实现IOAM封装的方法增加了网络管理员的负担，且容易出错的问题，同时也使得IOAM入口节点能够支持在业务流量的触发下自动获取IOAM封装所需信息。

Claims (19)

  1. 一种自动实现带内操作管理维护IOAM封装的方法，所述方法包括：
    IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；
    所述IOAM入口节点接收所述IOAM集中配置点发送的携带各个IOAM传输节点的IOAM配置信息的第二报文；
    所述IOAM入口节点根据各个IOAM传输节点的IOAM配置信息，对业务数据报文进行IOAM封装。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述IOAM入口节点获取业务数据报文传输路径上各个IOAM传输节点的标识；
    在所述第一报文中携带所述IOAM配置请求信息的同时，还携带所述各个IOAM传输节点的标识，其中，所述IOAM传输节点的标识用于指示所述IOAM集中配置点将与所述IOAM传输节点的标识对应的IOAM传输节点的IOAM配置信息携带在所述第二报文中。
  3. 根据权利要求1所述的方法，其中，所述IOAM集中配置点中存储有所述各个IOAM传输节点的IOAM配置信息，其中，当IOAM传输节点的IOAM配置信息发生变化时，所述IOAM集中配置点对所存储的IOAM配置信息进行更新。
  4. 根据权利要求1所述的方法，其中，
    当获得网络管理员的触发操作时，所述IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；或者，
    当获得网络管理模块或控制应用的触发指令时，所述IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；或者，
    当获得业务数据报文的触发时，所述IOAM入口节点向IOAM集中配置点发送携带IOAM配置请求信息的第一报文。
  5. 根据权利要求2所述的方法，其中，所述第一报文为请求报文，在所述请求报文中设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置请求，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM传输节点标识；
    所述第二报文为响应报文，在所述响应报文中设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置信息，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM配置信息。
  6. 根据权利要求5所述的方法，其中，所述请求报文和所述响应报文采用第一协议；
    所述在所述请求报文中设置一组TLV，为：在所述请求报文中通过选项字段设置一组TLV；
    所述在所述响应报文中设置一组TLV，为：在所述响应报文中通过选项字段设置一组TLV。
  7. 根据权利要求5所述的方法，其中，所述请求报文和所述响应报文采用第二协议；
    所述在所述请求报文中设置一组TLV，为：在所述请求报文中通过对象字段设置一组TLV；
    所述在所述响应报文中设置一组TLV，为：在所述响应报文中通过对象字段设置一组TLV。
  8. 根据权利要求5所述的方法，其中，所述通过取值字段表示一组IOAM配置信息，包括：
    所述取值字段包括一个或多个数据列表，每个数据列表对应一个IOAM传输节点的IOAM配置信息，其中，在所述数据列表中，通过第 一字段表示IOAM传输节点标识，通过第二字段表示所述数据列表的长度，通过第三字段表示IOAM配置信息。
  9. 根据权利要求8所述的方法，其中，所述第三字段包括一组TLV，其中，在所述TLV中，通过类型字段表示IOAM传输节点支持的一种IOAM功能代码，通过长度字段表示所述TLV的长度，通过取值字段表示IOAM功能的配置信息。
  10. 一种自动实现IOAM封装的装置，所述装置包括：
    发送单元，配置为向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；
    接收单元，配置为接收所述IOAM集中配置点发送的携带各个IOAM传输节点的IOAM配置信息的第二报文；
    封装单元，配置为根据各个IOAM传输节点的IOAM配置信息，对业务数据报文进行IOAM封装。
  11. 根据权利要求10所述的装置，其中，所述装置还包括：
    获取单元，配置为获取业务数据报文传输路径上各个IOAM传输节点的标识；
    在所述第一报文中携带所述IOAM配置请求信息的同时，还携带所述各个IOAM传输节点的标识，其中，所述IOAM传输节点的标识用于指示所述IOAM集中配置点将与所述IOAM传输节点的标识对应的IOAM传输节点的IOAM配置信息携带在所述第二报文中。
  12. 根据权利要求10所述的装置，其中，所述IOAM集中配置点中存储有所述各个IOAM传输节点的IOAM配置信息，其中，当IOAM传输节点的IOAM配置信息发生变化时，所述IOAM集中配置点对所存储的IOAM配置信息进行更新。
  13. 根据权利要求10所述的装置，其中，所述发送单元，配置为当 获得网络管理员的触发操作时，向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；或者，当获得网络管理模块或控制应用的触发指令时，向IOAM集中配置点发送携带IOAM配置请求信息的第一报文；或者，当获得业务数据报文的触发时，向IOAM集中配置点发送携带IOAM配置请求信息的第一报文。
  14. 根据权利要求11所述的装置，其中，所述第一报文为请求报文，在所述请求报文中设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置请求，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM传输节点标识；
    所述第二报文为响应报文，在所述响应报文中设置一组TLV，其中，在所述TLV中，通过类型字段表示IOAM配置信息，通过长度字段表示所述TLV的长度，通过取值字段表示一组IOAM配置信息。
  15. 根据权利要求14所述的装置，其中，所述请求报文和所述响应报文采用第一协议；
    所述在所述请求报文中设置一组TLV，为：在所述请求报文中通过选项字段设置一组TLV；
    所述在所述响应报文中设置一组TLV，为：在所述响应报文中通过选项字段设置一组TLV。
  16. 根据权利要求14所述的装置，其中，所述请求报文和所述响应报文采用第二协议；
    所述在所述请求报文中设置一组TLV，为：在所述请求报文中通过对象字段设置一组TLV；
    所述在所述响应报文中设置一组TLV，为：在所述响应报文中通过对象字段设置一组TLV。
  17. 根据权利要求14所述的装置，其中，所述通过取值字段表示一 组IOAM配置信息，包括：
    所述取值字段包括一个或多个数据列表，每个数据列表对应一个IOAM传输节点的IOAM配置信息，其中，在所述数据列表中，通过第一字段表示IOAM传输节点标识，通过第二字段表示所述数据列表的长度，通过第三字段表示IOAM配置信息。
  18. 根据权利要求17所述的装置，其中，所述第三字段包括一组TLV，其中，在所述TLV中，通过类型字段表示IOAM传输节点支持的一种IOAM功能代码，通过长度字段表示所述TLV的长度，通过取值字段表示IOAM功能的配置信息。
  19. 一种存储介质，所述存储介质中存储有计算机可执行指令，该计算机可执行指令配置为执行权利要求1-9任一项所述的自动实现IOAM封装的方法。
PCT/CN2018/086834 2017-05-18 2018-05-15 一种自动实现ioam封装的方法及装置、存储介质 WO2018210225A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/614,449 US11177976B2 (en) 2017-05-18 2018-05-15 Method and device for automatically implementing IOAM encapsulation and storage medium
EP18801533.3A EP3627792A4 (en) 2017-05-18 2018-05-15 METHOD AND DEVICE FOR THE AUTOMATIC IMPLEMENTATION OF AN IOAM ENCAPSULATION AND STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710352927.5A CN108965204B (zh) 2017-05-18 2017-05-18 一种自动实现ioam封装的方法及装置
CN201710352927.5 2017-05-18

Publications (1)

Publication Number Publication Date
WO2018210225A1 true WO2018210225A1 (zh) 2018-11-22

Family

ID=64273334

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/086834 WO2018210225A1 (zh) 2017-05-18 2018-05-15 一种自动实现ioam封装的方法及装置、存储介质

Country Status (4)

Country Link
US (1) US11177976B2 (zh)
EP (1) EP3627792A4 (zh)
CN (1) CN108965204B (zh)
WO (1) WO2018210225A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112866042A (zh) * 2019-11-12 2021-05-28 中兴通讯股份有限公司 网络质量检测方法、装置、计算机设备和计算机可读介质

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10498639B2 (en) * 2018-03-13 2019-12-03 Futurewei Technologies, Inc. Collecting network OAM flow data using out-of-band messages
US10855577B2 (en) * 2018-08-21 2020-12-01 Cisco Technology, Inc. Service traffic replication and dynamic policy enforcement in a multi-cloud service mesh
CN109743340B (zh) * 2019-04-04 2019-07-30 华为技术有限公司 报文处理的方法和网络装置
CN112448926B (zh) * 2019-08-30 2022-07-08 烽火通信科技股份有限公司 一种带内操作管理维护ioam的处理方法及系统
US11483238B2 (en) * 2019-10-14 2022-10-25 Cisco Technology, Inc. Centralized path computation for information-centric networking
CN112188525B (zh) * 2020-09-28 2022-04-15 烽火通信科技股份有限公司 一种基于策略模板定制的ioam部署方法及系统
CN113992497B (zh) * 2021-11-03 2023-05-26 烽火通信科技股份有限公司 Ioam测量计算方法、装置、设备及存储介质
CN114745302B (zh) * 2022-03-30 2023-09-15 新华三技术有限公司 通信方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150092564A1 (en) * 2013-09-27 2015-04-02 Futurewei Technologies, Inc. Validation of Chained Network Services
WO2017070023A1 (en) * 2015-10-20 2017-04-27 Cisco Technology, Inc. Triggered in-band operations, administration, and maintenance in a network environment

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102082678A (zh) * 2009-12-01 2011-06-01 杭州华三通信技术有限公司 一种端口取消oam协议的处理方法和设备
WO2012145903A1 (zh) * 2011-04-28 2012-11-01 华为技术有限公司 操作、管理、维护配置信息查询的方法及节点
CN104486119A (zh) * 2014-12-16 2015-04-01 盛科网络（苏州）有限公司 通过改进openflow协议实现批量管理交换机的方法及系统
CN105893061A (zh) * 2016-06-12 2016-08-24 杭州勒芒科技有限公司 应用程序开发方法及系统
US10560354B2 (en) * 2017-03-24 2020-02-11 Cisco Technology, Inc. End-to-end, in situ packet enrichment for network analytics
US10560554B2 (en) * 2017-05-12 2020-02-11 Futurewei Technologies, Inc. In-situ OAM sampling and data validation

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150092564A1 (en) * 2013-09-27 2015-04-02 Futurewei Technologies, Inc. Validation of Chained Network Services
WO2017070023A1 (en) * 2015-10-20 2017-04-27 Cisco Technology, Inc. Triggered in-band operations, administration, and maintenance in a network environment

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
BROCKNERS: "IETF Network Working Group Data Requirements for In-band OAM", DATA FORMATS FOR IN-SITU OAM DRAFT-BROCKNERS-INBAND-OAM-DATA-02, 3 March 2017 (2017-03-03), XP015116269 *
BROCKNERS: "IETF Network Working Group Data Requirements for In-band OAM", ENCAPSULATIONS FOR IN-SITU OAM DATA DRAFT - BROCKNERS - INBAND - OAM- TRANSPO- RT-02, 3 March 2017 (2017-03-03), XP015116269 *
BROCKNERS: "IETF Network Working Group Data Requirements for In-band OAM", REQUIREMENTS FOR IN-BAND OAM DRAFT - BROCKNERS - INBAND - OAM - REQUIREMENTS-01, 19 January 2017 (2017-01-19), XP015114447 *
See also references of EP3627792A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112866042A (zh) * 2019-11-12 2021-05-28 中兴通讯股份有限公司 网络质量检测方法、装置、计算机设备和计算机可读介质
CN112866042B (zh) * 2019-11-12 2023-07-18 中兴通讯股份有限公司 网络质量检测方法、装置、计算机设备和计算机可读介质

Also Published As

Publication number Publication date
EP3627792A1 (en) 2020-03-25
EP3627792A4 (en) 2021-03-03
CN108965204B (zh) 2022-01-25
US11177976B2 (en) 2021-11-16
CN108965204A (zh) 2018-12-07
US20200204401A1 (en) 2020-06-25

Similar Documents

Publication Publication Date Title
WO2018210225A1 (zh) 一种自动实现ioam封装的方法及装置、存储介质
WO2018210213A1 (zh) 一种实现ioam封装的方法及装置、存储介质
EP3154227B1 (en) Packet transmission method, node, path management server and storage medium
WO2018188464A1 (zh) 一种实现ioam的方法、装置及存储介质
EP3139560B1 (en) Packet processing method, device and computer storage medium
US10243827B2 (en) Techniques to use a network service header to monitor quality of service
US11012261B2 (en) Associating VXLANs with tunnels
US10862793B2 (en) Centralized error telemetry using segment routing header tunneling
WO2018188661A1 (zh) 封装方法、装置和节点
WO2016045098A1 (zh) 交换机、控制器、系统及链路质量检测方法
WO2018188662A1 (zh) 信息通告方法及装置
WO2018188663A1 (zh) 信息通告方法及装置
WO2015184771A1 (zh) 一种业务功能链操作、管理和维护方法及节点设备
EP3073698A1 (en) Method for processing address resolution protocol message, forwarder and controller
CN103580894A (zh) 操作、管理和维护oam配置的方法、设备及系统
WO2021190009A1 (zh) 性能测量方法、装置、设备和存储介质
CN112350934A (zh) 数据传输方法、网络节点和数据传输系统
WO2015035616A1 (zh) 跨网通信方法及装置
WO2017193732A1 (zh) 一种伪线数据报文的封装、解封装方法和相关装置
WO2015184740A1 (zh) 检测层次信息的处理方法及装置
EP3188408B1 (en) Method and apparatus for determining network topology, and centralized network state information storage device
WO2013078873A1 (zh) 识别应答报文的方法及设备
WO2020024906A1 (zh) 路径标识传输方法和装置、计算机可读存储介质
WO2020024907A1 (zh) 路径标识传输方法、装置和计算机可读存储介质
US20130259057A1 (en) Pseudowire groups in a packet switched network

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: 18801533

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: 2018801533

Country of ref document: EP

Effective date: 20191218