WO2022048466A1 - 一种操作管理维护oam报文处理方法及设备 - Google Patents

一种操作管理维护oam报文处理方法及设备 Download PDF

Info

Publication number
WO2022048466A1
WO2022048466A1 PCT/CN2021/113974 CN2021113974W WO2022048466A1 WO 2022048466 A1 WO2022048466 A1 WO 2022048466A1 CN 2021113974 W CN2021113974 W CN 2021113974W WO 2022048466 A1 WO2022048466 A1 WO 2022048466A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
identifier
oam
type
indication information
Prior art date
Application number
PCT/CN2021/113974
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 JP2023514707A priority Critical patent/JP2023539689A/ja
Priority to EP21863533.2A priority patent/EP4199447A4/en
Publication of WO2022048466A1 publication Critical patent/WO2022048466A1/zh
Priority to US18/176,718 priority patent/US20230208756A1/en

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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/304—Route determination for signalling traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/659—Internet protocol version 6 [IPv6] addresses

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and device for processing operation management and maintenance (English: Operation Administration and Maintenance, OAM for short) messages.
  • operation management and maintenance English: Operation Administration and Maintenance, OAM for short
  • Multi-Protocol Label Switching-Transport Profile (English: Multi Protocol Label Switching-Transport Profile, MPLS-TP for short) is a strict subset of MPLS. In order to meet the requirements of the transport network, some features of MPLS that are not suitable for transport network scenarios are excluded. , a connection-oriented transmission technology that combines MPLS packet switching and transport network characteristics. OAM mainly includes three aspects: Fault Management (English: Fault Management), Performance Monitoring (English: Performance Monitoring) and Protection Switching (English: Protection Switching), which can reflect the network operation status and is the most important network management method for operators.
  • the OAM mechanism of MPLS-TP draws on and multiplexes the Y.1731 standard, mainly including the Label Switch Path (English: Label Switch Path, referred to as: LSP) layer, Pseudo Wire (English: Pseudo Wire, referred to as: PW) layer, segment (English: Section, abbreviation: Sec) layer and ring (English: Ring) OAM function.
  • LSP Label Switch Path
  • PW Pseudo Wire
  • Sec Section, abbreviation: Sec
  • ring English: Ring
  • the IP mode of MPLS-TP OAM uses the existing network device ID and path ID to respectively identify the sender's network device and the path to be detected, so there is no need to configure an additional maintenance entity group (English: Maintenance Entity Group, abbreviated as: MEG) identification and maintenance of entity group end points (English: Maintenance Entity Group End Points, abbreviated as: MEP) identification, which can realize fault management, performance monitoring and protection switching, which greatly saves configuration costs and improves detection efficiency. operator's favor.
  • MEG Maintenance Entity Group
  • MEP Maintenance Entity Group End Points
  • IPv4 Internet Protocol version 4
  • IPv6 Internet Protocol version 6
  • IPv6 Internet Protocol version 6
  • the embodiments of the present application provide an OAM packet processing method and device, which can expand the scope of application to make IPv4 and IPv6 applicable, improve the MPLS-TP OAM mechanism, and improve the operation of the MPLS-TP OAM. Providers provide a better user experience.
  • an embodiment of the present application provides a method for processing an OAM packet based on MPLS-TP.
  • the method may include: a first network device generates an OAM packet, where the OAM packet includes indication information and the first network device. and the indication information is used to indicate the type of the identity of the first network device.
  • the indication information can be specifically used to indicate whether the OAM message is a message of an IPv4 network or a message of an IPv6 network; thus, the first network device sends the OAM message to the second network device.
  • the indication information in the OAM packet generated by the first network device indicates whether the identifier of the first network device is an IPv4 address or an IPv6 address, and when the indication information carried in the OAM packet indicates that the IP address of the first network device is an IPv4 address
  • the identification of the first network device included in the OAM message is the IPv4 address of the first network device
  • the indication information carried in the OAM message indicates that the IP address of the first network device is an IPv6 address
  • the OAM message The identifier of the first network device included in the text is the IPv6 address of the first network device, so that it can be ensured that the recipient network device that receives the OAM message determines the first network device carried in the OAM message based on the indication information.
  • the identification type of the device, and the identification of the first network device is accurately read from the OAM message, so that the user can not only perform MPLS-TP OAM, reduce the configuration workload, but also complete the IPv4 network, IPv6 network and Multi-scenario MPLS-TP OAM including IPv4 and IPv6 networks broadens the application scope of MPLS-TP OAM and improves user experience.
  • the indication information in the OAM packet is used to indicate that the type of the identifier of the first network device is an IPv6 address. This way, it is ensured that the method works for IPv6 networks.
  • the type of the indication information in the OAM packet used for the identification of the first network device is an IPv4 address. This way, make sure the method works for IPv4 networks
  • the OAM packet includes a Type field for indicating the MEG type, and the Type field may be used to carry the indication information.
  • the indication information is used to indicate that the type of the identifier of the first network device is an IPv6 address; if the value of the Type field is the second value, the indication The information is used to indicate that the type of the identifier of the first network device is an IPv4 address.
  • the OAM packet includes a Reserved field, and at least one bit in the Reserved field may be used to carry the indication information.
  • the indication information is used to indicate that the type of the identity of the first network device is an IPv6 address
  • the indication information is used to indicate that the type of the identifier of the first network device is an IPv4 address.
  • an embodiment of the present application provides a method for processing an OAM packet based on MPLS-TP.
  • the method may include: after the first network device sends the OAM packet to the second network device, the second network device receives the OAM packet.
  • the OAM packet sent by the first network device, the OAM packet includes indication information and the identity of the first network device, the indication information is used to indicate the type of the identity of the first network device, and is specifically used to indicate that the OAM packet is an IPv4 network
  • the packet is still a packet of the IPv6 network; thus, the second network device can read the identifier of the first network device in the OAM packet according to the indication information.
  • the OAM packet received by the second network device includes indication information, and the indication information is used to indicate the type of the identifier of the first network device, that is, to indicate whether the identifier of the first network device is an IPv4 address or an IPv6 address.
  • the second network device may determine the type of the identifier of the first network device carried in the OAM packet based on the indication information, and accurately read the identifier of the first network device from the OAM packet.
  • the user It can not only execute MPLS-TP OAM, reduce the workload of configuration, but also complete MPLS-TP OAM in multiple scenarios such as IPv4 network, IPv6 network and network including IPv4 and IPv6, which expands the application scope of MPLS-TP OAM and improves the performance of MPLS-TP OAM. User experience.
  • the indication information in the OAM packet may be used to indicate that the type of the identifier of the first network device is an IPv6 address.
  • S1002 may, for example, include: the second network device reads the first network device's identifier from the OAM packet. IPv6 address. This way, it is ensured that the method works for IPv6 networks.
  • the type of the indication information in the OAM packet used for the identification of the first network device is an IPv4 address
  • the inflow of S1002 may include: the second network device reads the IPv4 address of the first network device from the OAM packet address. This way, it is ensured that the method works for IPv4 networks.
  • the OAM packet includes a Type field for indicating the MEG type, and the Type field may be used to carry the indication information.
  • the indication information is used to indicate that the type of the identifier of the first network device is an IPv6 address; if the value of the Type field is the second value, the indication The information is used to indicate that the type of the identifier of the first network device is an IPv4 address.
  • the OAM packet includes a Reserved field, and at least one bit in the Reserved field may be used to carry the indication information.
  • the indication information is used to indicate that the type of the identity of the first network device is an IPv6 address
  • the indication information is used to indicate that the type of the identifier of the first network device is an IPv4 address.
  • an embodiment of the present application provides a method for processing an OAM packet based on MPLS-TP.
  • the method is applicable to an IPv6 network.
  • the method may include: a first network device generates an OAM packet, and the OAM packet includes the first network device. An IPv6 address of a network device; the first network device sends an OAM packet to the second network device.
  • the second network device can accurately read the identifier of the first network device from the OAM message after receiving the OAM message.
  • the user can execute MPLS-TP OAM in IP mode, reducing configuration It can also complete MPLS-TP OAM in IPv6 network scenarios, improving user experience.
  • an embodiment of the present application provides a method for processing an OAM packet based on MPLS-TP.
  • the method is applicable to an IPv6 network.
  • the method may include: a second network device receiving an OAM packet sent by a first network device, The OAM message includes the IPv6 address of the first network device; the second network device reads the IPv6 address of the first network device from the OAM message.
  • the OAM packet received by the second network device includes the IPv6 address of the first network device, so that the second network device can accurately read the identifier of the first network device from the OAM packet.
  • the user can not only It can perform MPLS-TP OAM in IP mode, reducing the workload of configuration, and can also complete MPLS-TP OAM in IPv6 network scenarios, improving user experience.
  • the OAM message may also include indication information, which is used to indicate the type of the identifier of the first network device, and is specifically used to indicate whether the OAM message is an IPv4 network message or a packets of an IPv6 network.
  • indication information is used to indicate the type of the identifier of the first network device, and is specifically used to indicate whether the OAM message is an IPv4 network message or a packets of an IPv6 network.
  • the OAM packet may further include a path identifier from the first network device to the second network device.
  • the path identifier may be any one of the following identifiers: a label switched path LSP identifier, a segment section identifier, a pseudowire PW identifier or a ring ring identifier.
  • the field used to carry the path identifier in the OAM packet may be adjacent to the field used to carry the identifier of the first network device. In this way, the receiver can be made accurate based on the path identifier and the identifier of the first network device. The completion of OAM detection.
  • the OAM packet may be a packet corresponding to the IP mode of MPLS-TP OAM.
  • the OAM packet may also be a packet corresponding to other modes of MPLS-TP OAM.
  • the indication information in the OAM packet corresponding to the ICC mode may also be used to indicate the first network
  • the type of the device's identification that is, the MEP ID
  • the mode corresponding to the OAM message mentioned in the embodiment of the present application is not specifically limited in the embodiment of the present application.
  • the present application further provides a first communication device, including a transceiver unit and a processing unit.
  • the transceiving unit is configured to perform the transceiving operation in the method provided by the first aspect, any possible implementation manner of the first aspect, the third aspect, or any possible implementation manner of the third aspect;
  • the processing unit is configured to perform Other operations other than the transceiving operation in the method provided by the first aspect, any possible implementation manner of the first aspect, the third aspect, or any possible implementation manner of the third aspect.
  • the transceiver unit is configured to send an OAM packet to the second network device; the processing unit is configured to generate an OAM packet.
  • an embodiment of the present application further provides a second communication device, where the second communication device includes a transceiver unit and a processing unit.
  • the transceiving unit is configured to perform the transceiving operation in the method provided by the second aspect, any possible implementation manner of the second aspect, the fourth aspect, or any possible implementation manner of the fourth aspect;
  • the processing unit is configured to perform Other operations other than the transceiving operation in the method provided by the second aspect, any possible implementation manner of the second aspect, the fourth aspect, or any possible implementation manner of the fourth aspect.
  • the transceiver unit is configured to receive the OAM packet sent by the first network device;
  • the processing unit is configured to read the instruction information according to the instruction information. The identifier of the first network device in the OAM message.
  • an embodiment of the present application further provides a first communication apparatus, including a first communication interface and a processor.
  • the first communication interface is used to perform the sending operation in the method provided by the foregoing first aspect, any possible implementation manner of the first aspect, the third aspect, or any possible implementation manner of the third aspect;
  • the processor It is used to perform other operations other than the receiving and sending operations in the method provided in the first aspect, any possible implementation manner of the first aspect, the third aspect, or any possible implementation manner of the third aspect.
  • the first communication apparatus may further include a second communication interface, where the second communication interface is used to perform the receiving operation of the aforementioned first network device.
  • an embodiment of the present application further provides a second communication apparatus, including a first communication interface and a processor.
  • the first communication interface is used to perform the receiving operation in the method provided by the second aspect, any possible implementation manner of the second aspect, the fourth aspect, or any possible implementation manner of the fourth aspect;
  • the processor It is used to perform other operations other than the receiving and sending operations in the method provided by the second aspect, any possible implementation manner of the second aspect, the fourth aspect, or any possible implementation manner of the fourth aspect.
  • the second communication apparatus may further include a second communication interface, where the second communication interface is used to perform the sending operation of the aforementioned second network device.
  • an embodiment of the present application further provides a first communication apparatus, where the first communication apparatus includes a memory and a processor.
  • the memory includes computer-readable instructions; a processor in communication with the memory is configured to execute the computer-readable instructions, so that the first communication device is configured to execute the first aspect and any possible implementation of the first aspect The method provided by the method, the third aspect, or any one possible implementation manner of the third aspect.
  • an embodiment of the present application further provides a second communication apparatus, where the second communication apparatus includes a memory and a processor.
  • the memory includes computer-readable instructions; a processor in communication with the memory is configured to execute the computer-readable instructions, so that the second communication device is configured to execute the second aspect and any possible implementation of the second aspect The method provided by the method, the fourth aspect, or any one possible implementation manner of the fourth aspect.
  • the embodiments of the present application further provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer is made to execute the above first aspect, the first Any possible implementation of the one aspect, the second aspect, any possible implementation of the second aspect, the third aspect, any possible implementation of the third aspect, the fourth aspect, or any one of the fourth aspect Methods provided by possible implementations.
  • the embodiments of the present application further provide a computer program product, including a computer program or computer-readable instructions, when the computer program or the computer-readable instructions are run on a computer, the computer is made to execute the foregoing first aspect , any possible implementation of the first aspect, the second aspect, any possible implementation of the second aspect, the third aspect, any possible implementation of the third aspect, the fourth aspect or any of the fourth aspect A possible implementation provides the method.
  • an embodiment of the present application further provides a communication system, where the communication system includes the first communication device provided in the fifth aspect, the seventh aspect, or the ninth aspect, and the sixth aspect, the eighth aspect or the The tenth aspect provides a second communication device.
  • the communication device in the foregoing embodiment may be a network device for executing the foregoing method, or may refer to a single board, a line card, a chip, or the like for executing the foregoing method.
  • 1a is a schematic diagram of the format of an OAM PDU in an ICC mode in an embodiment of the application;
  • 1b is a schematic diagram of the format of an OAM PDU in an IP mode in an embodiment of the application
  • 2a is a schematic diagram of the format of an OAM PDU in an IPv4 mode in an embodiment of the application
  • 2b is a schematic diagram of the format of an OAM PDU in an IPv6 mode in an embodiment of the application;
  • FIG. 3 is a signaling flowchart of a method 100 for processing an OAM packet in an embodiment of the present application
  • 4a is a schematic diagram of an OAM PDU in which the Type field indicates an LSP IPv6 mode in an embodiment of the present application;
  • 4b is a schematic diagram of an OAM PDU in which the Type field indicates a PW IPv4 mode in an embodiment of the present application;
  • 4c is a schematic diagram of an OAM PDU in which the Type field indicates the Section IPv4 mode in the embodiment of the application;
  • 4d is a schematic diagram of an OAM PDU in which the Type field indicates the Section IPv6 mode in the embodiment of the application;
  • 4e is a schematic diagram of an OAM PDU in which the Type field indicates the Ring IPv4 mode in an embodiment of the application;
  • 4f is a schematic diagram of an OAM PDU in which the Type field indicates the Ring IPv6 mode in an embodiment of the application;
  • 5a is a schematic diagram of an OAM PDU in which the Reserved field of an LSP scene indicates an IPv4 mode in an embodiment of the present application;
  • 5b is a schematic diagram of an OAM PDU in which the Reserved field of an LSP scene indicates an IPv6 mode in an embodiment of the present application;
  • 5c is a schematic diagram of an OAM PDU in which the Reserved field of a PW scene indicates an IPv4 mode in an embodiment of the present application;
  • 5d is a schematic diagram of an OAM PDU in which the Reserved field of the PW scene indicates an IPv6 mode in an embodiment of the present application;
  • 5e is a schematic diagram of an OAM PDU in which the Reserved field of the Section scene indicates an IPv4 mode in an embodiment of the present application;
  • 5f is a schematic diagram of an OAM PDU in which the Reserved field of the Section scene indicates an IPv6 mode in an embodiment of the present application;
  • 5g is a schematic diagram of an OAM PDU in which the Reserved field of the Ring scene indicates an IPv4 mode in an embodiment of the present application;
  • 5h is a schematic diagram of an OAM PDU in which the Reserved field of the Ring scene indicates an IPv6 mode in an embodiment of the application;
  • FIG. 6 is a schematic diagram of another OAM PDU corresponding to the scenario of FIG. 2b in an embodiment of the application;
  • FIG. 7 is a signaling flowchart of a method 200 for processing an OAM packet in an embodiment of the present application
  • FIG. 8a is a schematic diagram of another OAM PDU corresponding to the scenario of FIG. 4a in an embodiment of the present application;
  • FIG. 8b is a schematic diagram of another OAM PDU corresponding to the scenario of FIG. 4a in an embodiment of the present application;
  • FIG. 8c is a schematic diagram of still another OAM PDU corresponding to the scenario of FIG. 4a in an embodiment of the application;
  • FIG. 9 is a schematic flowchart of an OAM packet processing method 300 in an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of an OAM packet processing method 400 in an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of an OAM packet processing method 500 in an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of an OAM packet processing method 600 in an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a first communication apparatus 1300 according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a second communication apparatus 1400 in an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a first communication apparatus 1500 in an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a second communication apparatus 1600 according to an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a first communication apparatus 1700 according to an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of a second communication apparatus 1800 in an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of a communication system 1900 in an embodiment of the present application.
  • ordinal numbers such as “1”, “2”, “3”, “first”, “second” and “third” are used to distinguish multiple objects, and are not used to limit the order of multiple objects .
  • a and/or B mentioned in this application should be understood to include the following situations: only A, only B, or both A and B are included.
  • MPLS-TP OAM refers to the OAM mechanism defined in MPLS-TP. Since MPLS-TP OAM is compatible with the functions of MPLS OAM, it has been extended according to the unique situation of the transport network. Therefore, MPLS-TP OAM has received extensive attention from operators. .
  • MPLS-TP OAM is divided into two modes: International Telecommunication Union Carrier Code (English: International Telecommunication Union Carrier Code, referred to as: ICC) mode and Internet Protocol (English: Internet Protocol, referred to as: IP) mode.
  • the ICC mode is the mode defined in Y.1731.
  • the network device needs to configure the maintenance entity group End Points Identification (English: Maintenance Entity Group End Points Identification, referred to as: MEP ID) and the maintenance entity group. Identification (English: Maintenance Entity Group Identification, referred to as: MEG ID), and carry MEP ID and MEG ID in the OAM message to manage the network.
  • MEP ID Maintenance Entity Group Identification
  • MEG ID Maintenance Entity Group Identification
  • the network device does not need to configure additional MEP ID and MEG ID, but carries the network device ID and path ID in the OAM message to manage the network.
  • the OAM message may include, for example: a continuous monitoring message (English: Continuity Check Message, referred to as: CCM), a loss measurement message (English: Loss Measurement Message, referred to as: LMM), a packet loss measurement response (English: Loss Measurement Reply, abbreviation: LMR) and so on.
  • CCM Continuous Monitoring message
  • LMM Loss Measurement Message
  • LMR packet loss measurement response
  • the format of the protocol data unit (English: Protocol Data Unit, PDU) of the CCM in ICC mode is shown in Figure 1a
  • the CCM PDU includes: MEG level (English: Maintenance Entity Group Level, referred to as: MEL) field, version (English: Version) field, operation code (English: Operation Code, referred to as: OpCode) field, remote defect indication (English: Remote Defect Indication, referred to as: RDI) field, reserved (English: Reserved) field, Period (English: Period) field, Type Length Value (English: Type Length Value, abbreviation: TLV) Offset (English: Offset) field, Sequence Number (English: Sequence Number) field, MEP ID field, MEG ID (also known as MAID), TxFCf field for the count of data frames sent by the local end, RxFCb field for the count of data frames received by the local end, TxFCb field for the count of data frames sent by the opposite end,
  • MEG level Terms: Maintenance Entity Group Level, referred
  • the value of the MEL field is used to identify the level of the CCM PDU, and the value range is an integer from 0 to 7; the value of the Version field is used to identify the protocol version used.
  • the applicable protocol version It is Y.1731, and the value of the Version field corresponding to the protocol version is 0; the value of the OpCode field is used to identify the type of the OAM PDU, so that the content of the OAM PDU can be identified based on the type of the OAM PDU.
  • the value of OpCode is 1;
  • the value of the RDI field is used to identify whether the MEP at the sending end has detected a failure.
  • the value of the RDI field is used to identify the period of sending CCMs, for example: when the value of the Period field is 1, it means that the period of sending CCMs is 3.33 milliseconds (that is, sending 300 frames of CCMs per second), When the value of the Period field is 2, it indicates that the period of sending CCM is 10 milliseconds (that is, sending 100 frames of CCM per second); the value of the TLV Offset field is used to indicate that the first TLV in the OAM PDU is relative to the TLV Offset field
  • the value of the Sequence Number field is 0; the length of the MEP ID field is 16 bits, and the value of the MEP ID is used to uniquely identify the sender of the CCM frame in the MEG ID. MEP, usually the lower 13 bits are valid; the length of the MEP ID field is 384 bits, and the value of the MEG ID is used to globally uniquely identify the MEG to which the MEP that sends the CCM frame belongs; the value of the TxFCf field is used to indicate the transmission in the CCM frame.
  • the value of the RxFCb field is used to indicate the non-exceeded data frame counter received by the peer MEP when the CCM frame is transmitted.
  • the value of the RxFCb field is zero; the value of the TxFCb field is used to indicate the count value of the data frame counters that are not exceeded by the peer MEP during CCM frame transmission.
  • the values of the TxFCf field, RxFCb field, and TxFCb field are all zero.
  • the value of the End TLV field is used to identify the number of all-zero bytes included in the CCM PDU.
  • the format of the CCM PDU in IP mode is shown in Figure 1b.
  • the CCM PDU includes: MEL field, Version field, OpCode field, RDI field, Reserved field, Period field, TLV Offset field, Sequence Number field, Type field, Reserved/ PWType field, network device identification field, path identification field, Reserved field, TxFCf field, RxFCb field, TxFCb field, Reserved field and End TLV field.
  • MEL field, the Version field, the OpCode field, the RDI field, the Period field, the TLV Offset field, the Sequence Number field, the TxFCf field, the RxFCb field, the TxFCb field, and the End TLV field are described in Figure 1a.
  • the value of the Type field is used to indicate the path type detected by the CCM.
  • the value of the Type field is 1, indicating that the CCM detects a Label Switched Path (English: Label Switched Path, abbreviated as: LSP);
  • PW pseudowire
  • the value of the identification field of the network device can be the LSR ID; the value of the path identification field The value is used to uniquely identify the path to be detected.
  • the value of the path identifier field may specifically be the identifier of the tunnel where the LSR is located.
  • the MPLS-TP OAM operation is performed based on the maintenance entity (English: Maintenance Entity, referred to as: ME).
  • Maintenance Entity Group Intermediate Points referred to as: MIP
  • MEP Maintenance Entity Group Intermediate Points
  • MEP has the ability to initiate and terminate OAM packets, and can perform fault management and performance monitoring
  • MIP is an intermediate node of MEG, which can forward OAM packets and respond to some OAM packets, but cannot initiate OAM packets.
  • the network device In the ICC mode, in order to uniquely identify the sender's network device and the transmission path detected by the OAM, the network device configures the MEP ID and MEG ID, and carries the MEP ID and MEG ID in the OAM message. In this way, if there are a large number of network devices in the network, a large amount of configuration needs to be performed. Moreover, for the effectiveness of OAM detection, it is necessary to avoid the configuration of duplicate MEP IDs and MEG IDs on a large number of network devices. Not simple and convenient enough.
  • the IP mode uses the known information on the network device - the identification and path identification of the network device, to replace the functions of the MEP ID and MEG ID in the OAM message, that is, to uniquely identify the sender's network device and the transmission path detected by the OAM, Therefore, the IP mode of MPLS-TP OAM does not require network equipment to configure MEP ID and MEG ID, which can save the user's configuration workload, and does not need to consider the problem of repeated configuration. It has obvious advantages and is favored by users.
  • the OAM message in the IP mode of MPLS-TP OAM is shown in Figure 1b.
  • the length of the identification field of the network device is 32 bits, which is only suitable for carrying the fourth version of the Internet Protocol (English: Internet Protocol version 4, abbreviated as:
  • the IP address of the network device in the IPv4) scenario cannot carry the 128-bit IP address of the network device in the Internet Protocol version 6 (English: Internet Protocol version 6, referred to as: IPv6) scenario. Therefore, the IP mode of MPLS-TP OAM cannot be satisfied.
  • an embodiment of the present application provides a method for processing an OAM message.
  • the OAM message generated by the sender's network device includes indication information, where the indication information is used to indicate the type of the identifier of the sender's network device, that is, to indicate the sending Whether the identifier of the sender's network device is an IPv4 address or an IPv6 address, when the indication information carried in the OAM packet indicates that the IP address of the sender's network device is an IPv4 address, the identifier of the first network device included in the OAM packet is the first network device.
  • An IPv4 address of a network device when the indication information carried in the OAM message indicates that the IP address of the sender's network device is an IPv6 address, the identifier of the first network device included in the OAM message is the IPv6 address of the first network device.
  • the second network device that receives the OAM message can determine the type of the identifier of the sender's network device carried in the OAM message based on the indication information, and can accurately read the OAM message from the Get the identifier of the sender's network device.
  • users can implement MPLS-TP OAM to reduce the configuration workload, and can also implement MPLS-TP OAM in multiple scenarios, such as IPv4 network, IPv6 network, and networks including IPv4 and IPv6, to expand the bandwidth.
  • MPLS-TP OAM is improved, and the user experience is improved.
  • the OAM message in the embodiment of the present application may be a message corresponding to any mode of MPLS-TP OAM.
  • the OAM message is a message corresponding to the ICC mode of MPLS-TP OAM
  • the OAM The indication information in the message can also be used to indicate the type of the identification (that is, the MEP ID) of the first network device, and is specifically used to indicate that the OAM message is a message of an IPv4 network or a message of an IPv6 network. Since the IP mode of MPLS-TP OAM does not require network equipment to configure MEP ID and MEG ID, it can save configuration resources. Therefore, the IP mode provides better user experience. Based on this, in the embodiment of this application, the IP of MPLS-TP OAM is used.
  • the OAM packet corresponding to the mode is used as an example for related description and description.
  • the value of the Type field is set to indicate the MEG type detected by the CCM and the applicable IP network.
  • the value of the Type field is 1 to 4, indicating that the CCM detects MEGs of LSP, PW, Section (English: Section) and Ring (English: Ring) types, and is applicable to IPv4 networks;
  • the value of the Type field is 5 to 8 indicates that the CCM detects MEGs of LSP, PW, Section and Ring types, respectively, and is applicable to IPv6 networks.
  • the format of the CCM PDU in the generated CCM is shown in Figure 2a, the CCM PDU includes the MEL field, the Version field, the OpCode field, the RDI field, the Reserved field, and the Period field.
  • TLV Offset field Sequence Number field, TxFCf field, RxFCb field, TxFCb field, Reserved field and End TLV field, it also includes: Type field, Reserved field, network device identification field, path identification field, Reserved field.
  • the value of the Type field is 1, indicating that the CCM detects the MEG of the LSP type and is applicable to the IPv4 network;
  • the value of the identification field of the network device is the LSR ID, which may specifically be the 32-bit IPv4 address of the LSR.
  • the value of the path identifier field is the identifier of the tunnel (English: Tunnel) where the LSR is located.
  • the format of the CCM PDU in the generated CCM is shown in Figure 2b.
  • the value of the Type field is 6, indicating that the CCM detects the PW type MEG is applicable to IPv6 network;
  • the value of the identification field of the network device is the LSR ID, and the LSR ID may specifically be the 128-bit IPv6 address of the LSR;
  • the value of the path identification field is the virtual channel (English: Virtual Channel) of the PW. , referred to as: VC) logo.
  • the receiver's network device can accurately read the identifier of the sender's network device based on the indication information in the received OAM packet, thereby effectively implementing the OAM function.
  • the network device in the embodiments of the present application refers to any network device capable of implementing the OAM function, for example, it may be a Packet Transport Network (English: Packet Transport Network, PTN for short) device, switch, router, etc., There is no specific limitation in the embodiments of the present application.
  • Packet Transport Network English: Packet Transport Network, PTN for short
  • FIG. 3 is a schematic flowchart of an OAM packet processing method 100 according to an embodiment of the present application.
  • the method 100 may include, for example:
  • the network device 1 generates an OAM packet, where the OAM packet includes indication information and an identification 1 of the network device 1 , and the indication information is used to indicate the type of the identification 1 of the network device 1 .
  • the network device 1 is the MEP in the MEG that initiates the OAM message, and the MEP in the MEG that receives and terminates the OAM message is the network device 2 .
  • OAM packet specifically refers to the packet corresponding to the IP mode of MPLS-TP OAM.
  • the OAM message includes the identifier 1 of network device 1 and the path identifier 1, which are respectively used to inform network device 2 that the network device that initiated the OAM detection is network device 1, and the path detected by OAM is path 1, so as to ensure that the OAM message can be detected based on the OAM message.
  • This paper implements effective OAM detection.
  • the identifier 1 of the network device 1 may be an LSR ID, and the LSR ID is used to uniquely identify the LSR.
  • the LSR ID can be, for example, the IP address of the LSR. If the LSR belongs to the IPv4 network, the LSR ID is the IPv4 address of the LSR. If the LSR belongs to the IPv6 network, the LSR ID is the IPv6 address of the LSR.
  • Path ID 1 is an IP address of the LSR.
  • the OAM function In order to widen the application scope of MPLS-TP OAM and make the OAM function applicable to various scenarios such as IPv4 network, IPv6 network and network including IPv4 and IPv6, if the identifier 1 of the network device 1 is an IPv4 address, it is used to carry the The field of the identifier 1 of the network device 1 occupies at least 32 bits of space in the OAM packet; if the identifier 1 of the network device 1 is an IPv6 address, the field used to carry the identifier 1 of the network device 1 occupies at least 32 bits of space; 128-bit space in the OAM message.
  • the OAM packet also carries indication information, which is used to indicate the type of the identifier 1 of the network device 1, that is, the indication information can be It is used to indicate whether the OAM packet is an IPv4 network packet or an IPv6 network packet, or in other words, the indication information may indicate whether the identifier 1 of the network device 1 is an IPv6 address or an IPv4 address. In this way, the recipient network device can accurately obtain the identifier 1 of the network device 1 from the OAM message based on the indication information, thereby enabling effective OAM detection.
  • the indication information may be carried in the Type field, where the Type field is also used to indicate the type of MEG.
  • the value of the Type field is 1, indicating that the OAM detects the MEG of the LSP type, and the ID 1 of the network device 1 that initiates the OAM detection is the IPv4 address;
  • the value of the Type field is 2, indicating that the OAM detects the MEG of the PW type , and the identification 1 of the network device 1 that initiates the OAM detection is an IPv4 address;
  • the value of the Type field is 3, indicating that the OAM detects the MEG of the Section type, and the identification 1 of the network device 1 that initiates the OAM detection is an IPv4 address;
  • the Type field is an IPv4 address;
  • the value of the Type field is 4, indicating that the OAM detects the MEG of the Ring type, and the identifier 1 of the network device 1 that initiates the OAM detection is an IPv4 address;
  • the value of the Type field is 5, indicating that the O
  • the identifier 1 of 1 is an IPv6 address. Based on this, when the value of the Type field is any value from 1 to 4, it can indicate that the type of the identifier 1 of the network device 1 is an IPv4 address; when the value of the Type field is any value from 5 to 8, it can be Indicates that the type of the identity 1 of the network device 1 is an IPv6 address.
  • the indication information may also be carried in the Reserved field.
  • the Reserved field is a space of 16 bits (bit 0 to bit 15), and the current lower 8 bits and the 12th bit have been occupied, which are used to represent the service type of the PW.
  • the indication information may specifically be at least one of the 8th bit, the 9th bit, the 10th bit, the 11th bit, the 13th bit, the 14th bit and the 15th bit.
  • the first value indicates that the type of the identifier 1 of the network device 1 is an IPv4 address
  • the second value indicates that the type of the identifier 1 of the network device 1 is IPv6 address.
  • the first value is 0, and the second value is 1.
  • the value of the 8th bit of the Reserved field is 0, it indicates that the The type of the identifier 1 of the network device 1 is an IPv4 address
  • the value of the 8th bit of the Reserved field is 1, it indicates that the type of the identifier 1 of the network device 1 is an IPv6 address.
  • the first value is 00
  • the second value is 11.
  • the 8th and 9th bits of the Reserved field when the 8th and 9th bits of the Reserved field is 00, it indicates that the type of the identifier 1 of the network device 1 is an IPv4 address.
  • the value of the 8th and 9th bits of the Reserved field When the value of the 8th and 9th bits of the Reserved field is 11, it indicates the type of the identifier 1 of the network device 1. is an IPv6 address.
  • the first value is 0, and the second value is 1.
  • bits 8 to 11 of the Reserved field are When it is 0000 (the value is 0), it indicates that the type of the identifier 1 of the network device 1 is an IPv4 address.
  • bits 8th to 11th bits of the Reserved field are 0001 (the value is 1), it indicates that the network device Identifier of 1
  • the type of 1 is an IPv6 address.
  • the format of the OAM PDU is introduced by taking the path types detected in the CCM as LSP, Section, PW, and Ring as an example.
  • LSR ID is represented by Direction field and Ring Node ID field;
  • the Reserved field carries the indication information
  • the 8th bit of the Reserved field is used to carry the indication information.
  • the format of the OAM PDU is introduced.
  • the lower 8 bits and the 12th bit in the Reserved field are occupied to indicate the type of the PW VC (that is, the service type of the PW).
  • the Reserved field is also called the PW VC Type field.
  • the Type field 3, indicating that the OAM detects the MEG of the Section type.
  • the identifier 1 of the network device 1 occupies the continuous space of the OAM PDU in the OAM message, and the field carrying the identifier 1 of the network device 1 is adjacent to the field carrying the path identifier 1.
  • the 128-bit network device 1 in order not to extend the field length of the identifier 1 of the bearer network device 1 in the current IP mode, when the network device 1 is a network device in an IPv6 network, the 128-bit network device 1 The identifier 1 is segmented and divided into the first 32 bits and the last 96 bits, wherein the first 32 bits are stored in the field of the identifier 1 of the bearer network device 1 in the current IP mode, and the reserved field after the field of the bearer path identifier 1 Stores the last 96 bits of an IPv6 address.
  • the format of the OAM PDU in this implementation manner can refer to, for example, FIG. 6 .
  • the network device 1 generates the OAM packet carrying the indication information, making it possible for the OAM mechanism to be applicable to a wider range of application scenarios.
  • the network device 1 sends an OAM packet to the network device 2.
  • the network device 2 receives the OAM packet sent by the network device 1 .
  • the timing, regularity and specific sending method of the network device 1 sending the OAM message to the network device 2 are not limited.
  • the network device 2 reads the identifier 1 of the network device 1 in the OAM packet according to the indication information.
  • the network device 2 after receiving the OAM message, the network device 2 obtains indication information from the OAM message, and based on the indication of the indication information, accurately reads the identifier 1 of the network device 1 from the OAM message.
  • the indication information is used to indicate that the type of the identifier 1 of the network device 1 is an IPv6 address
  • S304 may be that the network device 2 reads the IPv6 address of the network device 1 from the OAM packet.
  • the indication information is used to indicate that the type of the identifier 1 of the network device 1 is an IPv4 address
  • S304 may be that the network device 2 reads the IPv4 address of the network device 1 from the OAM packet.
  • S304 may specifically refer to: the network device 2 parses the OAM packet to obtain the value of the Type field, based on the Type field The value of , determines that the type of the identifier 1 of the network device 1 that initiates the OAM message is an IPv4 address. Then, read the 32-bit information before the field used to carry the path identifier 1 and adjacent to the field from the OAM message. , as the identification 1 of the network device 1, that is, the IPv4 address of the network device 1.
  • S304 may specifically refer to: the network device 2 parses the OAM message to obtain the value of the Type field, and determines based on the value of the Type field
  • the type of the identifier 1 of the network device 1 that initiates the OAM message is an IPv6 address, then, read the 128-bit information before the field used to carry the path identifier 1 and adjacent to the field from the OAM message, as the network device
  • the identification of 1 is 1, that is, the IPv6 address of the network device 1.
  • S304 may specifically refer to: the network device 2 parses the OAM message to obtain the value of the Type field, and determines the network device that initiates the OAM message based on the value of the Type field
  • the type of identifier 1 of 1 is an IPv6 address, then, read the 32-bit information before the field used to carry path identifier 1 and adjacent to the field, and the information after the field used to carry path identifier 1 from the OAM message And the adjacent 96 bits of this field are spliced together to obtain the identifier 1 of the network device 1, that is, the IPv6 address of the network device 1.
  • S304 may specifically refer to: the network device 2 parses the OAM packet to obtain the value of the 8th bit in the Reserved field , based on the value of the 8th bit in the Reserved field, it is determined that the type of the identifier 1 of the network device 1 that initiates the OAM message is an IPv4 address, then, read from the OAM message after the Reserved field, used to carry the path identifier 1
  • the 32-bit information before the field is used as the identification 1 of the network device 1, that is, the IPv4 address of the network device 1.
  • S304 may specifically refer to: the network device 2 parses the OAM packet to obtain the value of the 8th bit in the Reserved field, based on the Reserved field The value of the 8th bit determines that the type of the identifier 1 of the network device 1 that initiates the OAM message is an IPv6 address. Then, read the reserved field from the OAM message, but before the field used to carry the path identifier 1. The 128-bit information is used as the identification 1 of the network device 1, that is, the IPv6 address of the network device 1.
  • the examples in the embodiments of the present application take the OAM packet as the CCM as an example for description, and other OAM packets such as LMM and LMR packets are all applicable to the OAM packet processing method provided in the embodiments of the present application That is, the OAM packet carries indication information for indicating the type of the identity of the network device, so that the OAM mechanism is applicable to more network scenarios.
  • the OAM packet carries indication information for indicating the type of the identity of the network device, so that the OAM mechanism is applicable to more network scenarios.
  • the relevant descriptions of the CCM messages which will not be repeated in this embodiment of the present application.
  • the network device 2 can implement the OAM detection on the MEGs from the network device 1 to the network device 2 based on the received OAM message.
  • the specific detection principle and implementation method are not the improvement points of the embodiments of the present application.
  • the embodiments of the present application will not be described in detail.
  • the OAM message generated by the sender's network device includes indication information, and the indication information is used to indicate the type of the identifier of the sender's network device, that is, to indicate the identifier of the sender's network device. Whether it is an IPv4 address or an IPv6 address.
  • the indication information carried in the OAM packet indicates that the IP address of the sender's network device is an IPv4 address
  • the identifier of the sender's network device included in the OAM packet is the IPv4 address of the sender's network device.
  • the indication information carried in the OAM message indicates that the IP address of the sender's network device is an IPv6 address
  • the identifier of the sender's network device included in the OAM message is the IPv6 address of the sender's network device, and in this way, receiving
  • the recipient network device of the OAM message can determine the type of the identifier of the sender's network device carried in the OAM message based on the indication information, and accurately read the sender's network device from the OAM message.
  • users can not only execute MPLS-TP OAM to reduce the workload of configuration, but also complete MPLS-TP OAM for IPv4 networks, IPv6 networks, and networks including IPv4 and IPv6 in multiple scenarios, broadening MPLS-TP OAM.
  • the scope of application improves the user experience.
  • FIG. 7 is a schematic flowchart of an OAM packet processing method 200 according to an embodiment of the present application.
  • the method 200 takes the IP mode of MPLS-TP OAM as an example, and is applicable to an IPv6 network.
  • the method 200 may include:
  • the network device 1 generates an OAM packet, where the OAM packet includes the IPv6 address of the network device 1 .
  • the identifier 1 of the network device 1 carried in the OAM packet needs to occupy a space of 128 bits.
  • the OAM message generated by the network device 1 needs to include a space of 128 bits for carrying the identifier 1 of the network device 1.
  • the OAM packet may extend the field carrying the identifier 1 of the network device 1 from 32 bits to 128 bits, so as to carry the IPv6 address of the network device 1 .
  • the OAM PDU in the OAM message generated based on the method 200 can be shown in Fig. 8a, for example.
  • the OAM packet does not extend the field bearing the ID 1 of the network device 1, but uses 96 bits of the Reserved field after the field that bears the ID 1 of the path, and uses the 96 bits of the Reserved field after the field that bears the ID 1 of the network device 1, which is used to bear the last field of the IPv6 address of the network device 1. 96 bits; or, use 128 bits of the Reserved field after the field for carrying the path identifier 1 to carry the IPv6 address of the network device 1.
  • the OAM PDU in the OAM message generated based on the method 200 can be referred to, for example, as shown in FIG. 8b or as shown in FIG. 8c, wherein, in FIG.
  • the field carries the first 32 bits of the IPv6 address of the network device 1
  • the Reserved field carries the last 96 bits of the IPv6 address of the network device 1; 128 bits of the IPv6 address of network device 1.
  • the OAM packet may further include a path identifier 1, which is used to indicate a path type detected by the OAM, and the path type may be, for example, LSP, PW, Section, or Ring.
  • the path identifier 1 may be any one of the following identifiers: an LSP identifier, a Section identifier, a PW identifier or a Ring identifier.
  • the network device 1 sends an OAM packet to the network device 2.
  • the network device 2 receives the OAM packet sent by the network device 1 .
  • the network device 2 reads the IPv6 address of the network device 1 from the OAM message.
  • the network device 2 after receiving the OAM message, the network device 2 reads the identifier 1 of the network device 1 from the OAM message, that is, reads the 128-bit IPv6 address of the network device 1 from the OAM message.
  • the OAM packet may further include indication information for indicating the type of the identification of the network device 1, specifically for indicating whether the OAM packet is an IPv4 network packet or an IPv6 network packet.
  • indication information for indicating the type of the identification of the network device 1, specifically for indicating whether the OAM packet is an IPv4 network packet or an IPv6 network packet.
  • the OAM message generated by the sender's network device includes the IPv6 address of the network device 1 as the identifier 1 of the network device 1.
  • the recipient's network device that receives the OAM message The identifier of the sender's network device can be accurately read from the OAM packet.
  • the user can not only execute MPLS-TP OAM in IP mode to reduce configuration workload, but also complete MPLS-TP OAM in IPv6 network scenarios. , which improves the user experience.
  • FIG. 9 shows a schematic flowchart of a method 300 for processing an OAM packet in an embodiment of the present application.
  • the method 300 is directed to the IP mode of MPLS-TP OAM, and takes the first network device as the execution subject.
  • the method 300 may include:
  • the first network device generates an OAM message, the OAM message includes indication information and an identifier of the first network device, and the indication information is used to indicate the type of the identifier of the first network device;
  • the first network device sends the OAM packet to the second network device.
  • the first network device may be the network device 1 in the foregoing method 100
  • the second network device may be the network device 2 in the foregoing method 100
  • For specific operations performed by the first network device reference may be made to operations performed by the network device 1 in the method 100 .
  • the OAM packet may be the OAM packet in method 100
  • the indication information may be the indication information in method 100
  • the identifier of the first network device may be identifier 1 of network device 1 in method 100 .
  • the indication information in the OAM packet is used to indicate that the type of the identifier of the first network device is an IPv6 address. In this way, it is ensured that the method 300 is applicable to IPv6 networks.
  • the type of the indication information in the OAM packet used for the identification of the first network device is an IPv4 address. This way, make sure that the method 300 is suitable for IPv4 networks
  • the OAM packet includes a Type field for indicating the MEG type, and the Type field may be used to carry the indication information.
  • the indication information is used to indicate that the type of the identifier of the first network device is an IPv6 address; if the value of the Type field is the second value, the indication The information is used to indicate that the type of the identifier of the first network device is an IPv4 address.
  • the OAM packet includes a Reserved field, and at least one bit in the Reserved field may be used to carry the indication information.
  • the indication information is used to indicate that the type of the identity of the first network device is an IPv6 address
  • the indication information is used to indicate that the type of the identifier of the first network device is an IPv4 address.
  • the OAM packet may further include a path identifier from the first network device to the second network device.
  • the path identifier may be any one of the following identifiers: a label switched path LSP identifier, a segment section identifier, a pseudowire PW identifier or a ring ring identifier.
  • the field used to carry the path identifier in the OAM packet may be adjacent to the field used to carry the identifier of the first network device. In this way, the receiver can be made accurate based on the path identifier and the identifier of the first network device. The completion of OAM detection.
  • the OAM message in the embodiment of the present application is specifically a message corresponding to the IP mode of MPLS-TP OAM.
  • the OAM packet generated by the first network device includes indication information, and the indication information is used to indicate the type of the identification of the first network device, that is, to indicate the identification of the first network device.
  • the identifier of the first network device included in the OAM packet is the IPv4 address of the first network device address; when the indication information carried in the OAM message indicates that the IP address of the first network device is an IPv6 address, the identifier of the first network device included in the OAM message is the IPv6 address of the first network device, so that it can be Ensure that the recipient network device that receives the OAM message determines the type of the identifier of the first network device carried in the OAM message based on the indication information, and accurately reads the first network device from the OAM message In this way, users can not only execute MPLS-TP OAM in IP mode, reducing the configuration workload, but also complete MPLS-TP OAM in multiple scenarios such as IPv4 network, IPv6 network, and networks including IPv4 and IPv6 networks.
  • the application range of MPLS-TP OAM is not only execute MPLS-TP OAM in IP mode, reducing the configuration workload, but also complete MPLS-TP OAM in multiple scenarios such as IPv4 network, IP
  • FIG. 10 shows a schematic flowchart of a method 400 for processing an OAM packet in an embodiment of the present application.
  • the method 400 is directed to the IP mode of MPLS-TP OAM, and takes the second network device as the execution subject.
  • the method 400 may include:
  • the second network device receives an OAM message sent by the first network device, where the OAM message includes indication information and an identifier of the first network device, and the indication information is used to indicate the type of the identifier of the first network device;
  • the second network device reads the identifier of the first network device in the OAM packet according to the indication information.
  • the second network device may be the network device 2 in the foregoing method 100
  • the first network device may be the network device 1 in the foregoing method 100
  • the OAM packet may be the OAM packet in method 100
  • the indication information may be the indication information in method 100
  • the identifier of the first network device may be identifier 1 of network device 1 in method 100 .
  • the indication information in the OAM packet may be used to indicate that the type of the identifier of the first network device is an IPv6 address.
  • S1002 may, for example, include: the second network device reads the first network device's identifier from the OAM packet. IPv6 address. In this way, it is ensured that the method 400 is applicable to IPv6 networks.
  • the type of the indication information in the OAM packet used for the identification of the first network device is an IPv4 address
  • the inflow of S1002 may include: the second network device reads the IPv4 address of the first network device from the OAM packet address. In this way, it is ensured that the method 400 is applicable to IPv4 networks.
  • the OAM packet includes a Type field for indicating the MEG type, and the Type field may be used to carry the indication information.
  • the indication information is used to indicate that the type of the identifier of the first network device is an IPv6 address; if the value of the Type field is the second value, the indication The information is used to indicate that the type of the identifier of the first network device is an IPv4 address.
  • the OAM packet includes a Reserved field, and at least one bit in the Reserved field may be used to carry the indication information.
  • the indication information is used to indicate that the type of the identity of the first network device is an IPv6 address
  • the indication information is used to indicate that the type of the identifier of the first network device is an IPv4 address.
  • the OAM packet may further include a path identifier from the first network device to the second network device.
  • the path identifier may be any one of the following identifiers: a label switched path LSP identifier, a segment section identifier, a pseudowire PW identifier or a ring ring identifier.
  • the field used to carry the path identifier in the OAM packet may be adjacent to the field used to carry the identifier of the first network device. In this way, the receiver can be made accurate based on the path identifier and the identifier of the first network device. The completion of OAM detection.
  • the OAM message in the embodiment of the present application is specifically a message corresponding to the IP mode of MPLS-TP OAM.
  • the OAM packet received by the second network device includes indication information, where the indication information is used to indicate the type of the identifier of the first network device, that is, indicating the type of the first network device's identity Whether the identifier is an IPv4 address or an IPv6 address, in this way, the second network device can determine the type of the identifier of the first network device carried in the OAM message based on the indication information, and accurately read from the OAM message
  • the identifier of the first network device so that the user can not only execute MPLS-TP OAM in IP mode to reduce the configuration workload, but also complete MPLS-TP OAM in multiple scenarios such as IPv4 network, IPv6 network, and networks including IPv4 and IPv6. , which expands the application scope of MPLS-TP OAM and improves the user experience.
  • FIG. 11 shows a schematic flowchart of a method 500 for processing an OAM packet in an embodiment of the present application.
  • the method 500 is directed to the IP mode of MPLS-TP OAM, and takes the first network device as the execution subject.
  • the method 500 may include:
  • the first network device generates an OAM packet, where the OAM packet includes the IPv6 address of the first network device;
  • the first network device sends an OAM packet to the second network device.
  • the first network device may be the network device 1 in the foregoing method 200
  • the second network device may be the network device 2 in the foregoing method 200
  • the OAM packet may be the OAM packet in method 200
  • the IPv6 address of the first network device may be the IPv6 address of network device 1 in method 200 .
  • the OAM packet may further include a path identifier from the first network device to the second network device.
  • the path identifier may be any one of the following identifiers: a label switched path LSP identifier, a segment section identifier, a pseudowire PW identifier or a ring ring identifier.
  • the field used to carry the path identifier in the OAM packet may be adjacent to the field used to carry the identifier of the first network device. In this way, the receiver can be made accurate based on the path identifier and the identifier of the first network device. The completion of OAM detection.
  • the OAM message in the embodiment of the present application is specifically a message corresponding to the IP mode of MPLS-TP OAM.
  • the OAM message generated by the first network device includes the IPv6 address of the first network device as the identifier of the first network device, so that the second network device receives the OAM message.
  • the identifier of the first network device can be accurately read from the OAM message.
  • the user can not only execute MPLS-TP OAM in IP mode to reduce configuration workload, but also complete MPLS-TP in IPv6 network scenarios.
  • TP OAM improves the user experience.
  • FIG. 12 shows a schematic flowchart of a method 600 for processing an OAM packet in an embodiment of the present application.
  • the method 600 is directed to the IP mode of MPLS-TP OAM, and takes the second network device as the execution subject.
  • the method 600 may include:
  • a second network device receives an OAM packet sent by a first network device, where the OAM packet includes the IPv6 address of the first network device;
  • the second network device reads the IPv6 address of the first network device from the OAM packet.
  • the second network device may be the network device 2 in the foregoing method 200
  • the first network device may be the network device 1 in the foregoing method 200
  • the OAM packet may be the OAM packet in method 200
  • the IPv6 address of the first network device may be the IPv6 address of network device 1 in method 200 .
  • the OAM packet may further include a path identifier from the first network device to the second network device.
  • the path identifier may be any one of the following identifiers: a label switched path LSP identifier, a segment section identifier, a pseudowire PW identifier or a ring ring identifier.
  • the field used to carry the path identifier in the OAM packet may be adjacent to the field used to carry the identifier of the first network device. In this way, the receiver can be made accurate based on the path identifier and the identifier of the first network device. The completion of OAM detection.
  • the OAM message in the embodiment of the present application is specifically a message corresponding to the IP mode of MPLS-TP OAM.
  • the OAM message received by the second network device includes the IPv6 address of the first network device, so that the second network device can accurately read the first network device from the OAM message.
  • the identification of a network device In this way, users can not only execute MPLS-TP OAM in IP mode, reducing configuration workload, but also complete MPLS-TP OAM in IPv6 network scenarios, improving user experience.
  • an embodiment of the present application further provides a first communication apparatus 1300, as shown in FIG. 13 .
  • the first communication device 1300 includes a processing unit 1301 and a sending unit 1302 .
  • the processing unit 1301 is configured to perform the processing operations performed by the network device 1 in the embodiments shown in FIG. 3 and FIG. 7 and the processing operations performed by the first network device in the embodiments shown in FIG. 9 and FIG. 11 ;
  • the sending unit 1302 It is used to perform the sending operation performed by the network device 1 in the embodiments shown in FIG. 3 and FIG. 7 and the sending operation performed by the first network device in the embodiments shown in FIG. 9 and FIG. 11 .
  • the processing unit 1301 may perform the operation in the embodiment in FIG. 3: generate an OAM message.
  • the sending unit 1302 may perform the operation in the embodiment in FIG. 3 : send an OAM packet to the network device 2 .
  • an embodiment of the present application further provides a second communication apparatus 1400, as shown in FIG. 14 .
  • the second communication apparatus 1400 includes a receiving unit 1401 and a processing unit 1402 .
  • the receiving unit 1401 is configured to perform the receiving operation performed by the network device 2 in the embodiments shown in FIG. 3 and FIG. 7 and the receiving operation performed by the second network device in the embodiments shown in FIG. 10 and FIG. 12 ;
  • the processing unit 1402 It is used to perform the processing operations performed by the network device 2 in the embodiments shown in FIG. 3 and FIG. 7 and the processing operations performed by the second network device in the embodiments shown in FIG. 10 and FIG. 12 .
  • the receiving unit 1401 may perform the operation in the embodiment in FIG. 3: receive the OAM packet sent by the network device 1;
  • the processing unit 1402 may perform the operation in the embodiment in FIG. 3: read the OAM packet according to the instruction information Identification 1 of network device 1.
  • an embodiment of the present application further provides a first communication apparatus 1500, as shown in FIG. 15 .
  • the first communication device 1500 includes a first communication interface 1501 , a second communication interface 1502 and a processor 1503 .
  • the first communication interface 1501 is used to perform the aforementioned receiving operations performed by the network device 1 in the embodiments shown in FIGS. 3 and 7 and the first network device in the embodiments shown in FIGS. 9 and 11;
  • the second communication interface 1502 is used to execute the sending operation performed by the network device 1 in the foregoing embodiments shown in FIGS. 3 and 7 and the first network device in the embodiments shown in FIGS. 9 and 11;
  • the processor 1503 is used to execute the above-mentioned implementation shown in FIGS.
  • the processor 1503 may perform the operation in the embodiment in FIG. 3: generate an OAM message.
  • an embodiment of the present application further provides a second communication apparatus 1600, as shown in FIG. 16 .
  • the second communication device 1600 includes a first communication interface 1601 , a second communication interface 1602 and a processor 1603 .
  • the first communication interface 1601 is used to perform the receiving operation performed by the network device 2 in the embodiments shown in FIGS. 3 and 7 and the second network device in the embodiments shown in FIGS. 10 and 12; the second communication interface 1602 is used to perform the receiving operation.
  • the sending operations performed by the network device 2 in the embodiments shown in FIGS. 3 and 7 and the second network device in the embodiments shown in FIGS. 10 and 12 are described above.
  • the processor 1603 is configured to perform other operations except the receiving operation and the sending operation performed by the network device 2 in the embodiments shown in FIGS. 3 and 7 and the second network device in the embodiments shown in FIGS. 10 and 12 .
  • the processor 1603 may perform the operation in the embodiment in FIG. 3: according to the indication information, read the identifier 1 of the network device 1 in the OAM packet.
  • an embodiment of the present application further provides a first communication apparatus 1700, as shown in FIG. 17 .
  • the first communication device 1700 includes a memory 1701 and a processor 1702 in communication with the memory 1701 .
  • the memory 1701 includes computer-readable instructions; the processor 1702 is configured to execute the computer-readable instructions, so that the first communication device 1700 executes the method performed by the network device 1 side in the embodiments shown in FIG. 3 and FIG. 7 , And the method performed by the first network device in the embodiments shown in FIG. 9 and FIG. 11 .
  • an embodiment of the present application further provides a second communication apparatus 1800, as shown in FIG. 18 .
  • the second communication device 1800 includes a memory 1801 and a processor 1802 in communication with the memory 1801 .
  • the memory 1801 includes computer-readable instructions; the processor 1802 is configured to execute the computer-readable instructions, so that the second communication device 1800 executes the method performed by the network device 2 side in the embodiments shown in FIG. 3 and FIG. 7 , And the method performed by the second network device in the embodiments shown in FIG. 10 and FIG. 12 .
  • the processor may be a central processing unit (English: central processing unit, abbreviation: CPU), a network processor (English: network processor, abbreviation: NP) or a combination of CPU and NP.
  • the processor may also be an application-specific integrated circuit (English: application-specific integrated circuit, abbreviation: ASIC), a programmable logic device (English: programmable logic device, abbreviation: PLD) or a combination thereof.
  • the above-mentioned PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), a field programmable logic gate array (English: field-programmable gate array, abbreviation: FPGA), a general-purpose array logic (English: generic array logic, abbreviation: GAL) or any combination thereof.
  • the processor may refer to one processor, or may include multiple processors.
  • the memory may include volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); the memory may also include non-volatile memory (English: non-volatile memory), For example, read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid-state hard disk (English: solid-state drive, Abbreviation: SSD); the memory may also comprise a combination of the above-mentioned kinds of memory.
  • the memory may refer to one memory, or may include multiple memories.
  • computer-readable instructions are stored in the memory, and the computer-readable instructions include a plurality of software modules, such as a sending module, a processing module and a receiving module. After executing each software module, the processor can perform corresponding operations according to the instructions of each software module. In this embodiment, the operation performed by a software module actually refers to the operation performed by the processor according to the instruction of the software module. After the processor executes the computer-readable instructions in the memory, it can perform all operations that can be performed by each network node in the OAM detection according to the instructions of the computer-readable instructions.
  • the second communication device 1502 of the first communication device 1500 can be specifically used as the sending unit 1302 in the first communication device 1300 to realize the connection between the first network device and the second network device.
  • the first communication interface 1501 of the first communication apparatus 1500 can be specifically used as a receiving unit in the first communication apparatus 1300, for example, can be used to receive other OAM packets sent by the upstream network device.
  • the first communication interface 1601 of the second communication device 1600 can be specifically used as the receiving unit 1401 in the second communication device 1400 to realize data communication between the first network device and the second network device; the second communication device 1600 The second communication interface 1602 can be specifically used as a sending unit in the second communication apparatus 1400 to implement data communication between the second network device and the downstream network device.
  • an embodiment of the present application further provides a communication system 1900, as shown in FIG. 19 .
  • the communication system 1900 includes a first communication device 1901 and a second communication device 1902, wherein the first communication device 1901 may specifically be the first communication device 1300, the first communication device 1500 or the first communication device 1700, the second communication device 1902 may specifically be the above-mentioned second communication device 1400 , second communication device 1600 or second communication device 1800 .
  • each communication device in the foregoing embodiment may be a network device for executing the foregoing method, or may refer to a single board, a line card, a chip, or the like for executing the foregoing method.
  • an embodiment of the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the computer is made to execute the above FIG. 3 , FIG. 7 , and FIG. 9 . - the OAM message processing method in the embodiment shown in FIG. 12 .
  • the embodiments of the present application also provide a computer program product, including a computer program or computer-readable instructions, when the computer program or the computer-readable instructions are run on a computer, the computer is made to execute the aforementioned FIG. 3 , FIG. 7 , The OAM packet processing method in the embodiment shown in FIG. 9-FIG. 12 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开了一种OAM报文处理方法及设备，包括：第一网络设备生成OAM报文，该OAM报文为包括指示信息和第一网络设备的标识的MPLS-TP的报文，指示信息用于指示第一网络设备的标识的类型；第一网络设备向第二网络设备发送所述OAM报文，这样，第二网络设备接收到该OAM报文后即可基于该指示信息，确定该OAM报文中携带的第一网络设备的标识的类型，并从OAM报文中准确的读取第一网络设备的标识，这样，使得IPv4网络、IPv6网络以及包括IPv4和IPv6的网络等多种场景中均能够实现MPLS-TP OAM，扩宽了MPLS-TP OAM的应用范围，提高了用户的使用体验。

Description

一种操作管理维护OAM报文处理方法及设备
本申请要求于2020年9月3日提交中国国家知识产权局、申请号为202010917057.3、申请名称为“一种操作管理维护OAM报文处理方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别是涉及一种操作管理维护(英文：Operation Administration and Maintenance，简称：OAM)报文处理方法及设备。
背景技术
多协议标签交换传输协议(英文：Multi Protocol Label Switching-Transport Profile，简称：MPLS-TP)是MPLS的一个严格子集，为了适应传送网的要求，排除MPLS某些不适用于传送网场景的特性，融合了MPLS包交换和传送网特性的面向连接的传输技术。OAM主要包括故障管理(英文：Fault Management)、性能监控(英文：Performance Monitoring)和保护倒换(英文：Protection Switching)三个方面,能够反映网络运行状况，是运营商最重要的网络管理手段。MPLS-TP的OAM机制借鉴和复用了Y.1731标准，主要包含在标签交换路径(英文：Label Switch Path，简称：LSP)层、伪线(英文：Pseudo Wire，简称：PW)层、段(英文：Section，简称：Sec)层和环(英文：Ring)的OAM功能。
目前，MPLS-TP OAM的IP模式由于采用已有的网络设备标识和路径标识分别标识发送方网络设备和待检测路径，无需在网络设备上额外配置维护实体组(英文：Maintenance Entity Group，简称：MEG)标识和维护实体组终端点(英文：Maintenance Entity Group End Points，简称：MEP)标识，即可实现故障管理、性能监控和保护倒换，大大的节约了配置成本，提高了检测效率，受到很多运营商的青睐。
但是，MPLS-TP OAM的IP模式仅适用第四版互联网协议(英文：Internet Protocol version 4，简称：IPv4)，OAM报文中用于承载网络设备的标识的字段也仅是与IPv4对应的32比特的空间。随着IPv4向第六版互联网协议(英文：Internet Protocol version 6，简称：IPv6)的演进，亟待解决MPLS-TP OAM场景下无法适用IPv6的问题，提供一种能够适用于IPv4和IPv6的MPLS-TP OAM机制。
发明内容
基于此，本申请实施例提供了一种OAM报文处理方法及设备，能够在发挥MPLS-TP OAM的优势的基础上，扩大适用范围使得适用IPv4和IPv6，完善MPLS-TP OAM机制，为运营商提供更好的使用体验。
第一方面，本申请实施例提供了一种基于MPLS-TP的OAM报文的处理方法，该方法可以包括：第一网络设备生成OAM报文，该OAM报文包括指示信息和第一网络设备的标识，指示信息用于指示第一网络设备的标识的类型。例如，该指示信息具体可以用于指示该OAM报文是IPv4网络的报文还是IPv6网络的报文；从而，第一网络设备向第二网络设 备发送所述OAM报文。这样，第一网络设备生成的OAM报文中的指示信息指示第一网络设备的标识是IPv4地址还是IPv6地址，当OAM报文中携带的指示信息指示该第一网络设备的IP地址是IPv4地址时，该OAM报文中包括的第一网络设备的标识为第一网络设备的IPv4地址；当OAM报文中携带的指示信息指示该第一网络设备的IP地址是IPv6地址时，该OAM报文中包括的第一网络设备的标识为第一网络设备的IPv6地址，如此，能够确保接收到该OAM报文的接收方网络设备基于该指示信息，确定该OAM报文中携带的第一网络设备的标识的类型，并且，从该OAM报文中准确的读取第一网络设备的标识，如此，用户既可以执行MPLS-TP OAM，减少配置工作量，也可以完成IPv4网络、IPv6网络以及包括IPv4和IPv6的网络等多场景的MPLS-TP OAM，扩宽了MPLS-TP OAM的应用范围，提高了用户的使用体验。
作为一个示例，OAM报文中的指示信息用于指示第一网络设备的标识的类型为IPv6地址。这样，确保该方法适用于IPv6网络。
作为另一个示例，OAM报文中的指示信息用于第一网络设备的标识的类型为IPv4地址。这样，确保该方法适用于IPv4网络
在一些可能的实现方式中，OAM报文中包括用于指示MEG类型的Type字段，该Type字段可以用于承载所述指示信息。具体实现时，如果该Type字段的取值为第一值，则该指示信息用于指示第一网络设备的标识的类型为IPv6地址；如果该Type字段的取值为第二值，则该指示信息用于指示第一网络设备的标识的类型为IPv4地址。
在另一些可能的实现方式中，OAM报文中包括Reserved字段，该Reserved字段中的至少一个比特位可以用于承载所述指示信息。具体实现时，如果该Reserved字段中至少一个比特位为第一值，则该指示信息用于指示第一网络设备的标识的类型为IPv6地址，如果该Reserved字段中至少一个比特位为第二值，则该指示信息用于指示第一网络设备的标识的类型为IPv4地址。
第二方面，本申请实施例提供了一种基于MPLS-TP的OAM报文的处理方法，该方法可以包括：在第一网络设备向第二网络设备发送OAM报文后，第二网络设备接收第一网络设备发送的OAM报文，该OAM报文包括指示信息和第一网络设备的标识，指示信息用于指示第一网络设备的标识的类型，具体用于指示该OAM报文是IPv4网络的报文还是IPv6网络的报文；从而，第二网络设备能够根据所述指示信息，读取OAM报文中第一网络设备的标识。这样，第二网络设备接收到的OAM报文中包括指示信息，该指示信息用于指示第一网络设备的标识的类型，即，指示第一网络设备的标识是IPv4地址还是IPv6地址，这样，第二网络设备即可基于该指示信息，确定该OAM报文中携带的第一网络设备的标识的类型，并且，从该OAM报文中准确的读取第一网络设备的标识，如此，用户既可以执行MPLS-TP OAM，减少配置工作量，也可以完成IPv4网络、IPv6网络以及包括IPv4和IPv6的网络等多场景的MPLS-TP OAM，扩宽了MPLS-TP OAM的应用范围，提高了用户的使用体验。
作为一个示例，OAM报文中的指示信息可以用于指示第一网络设备的标识的类型为IPv6地址，那么，S1002例如可以包括：第二网络设备从OAM报文中读取第一网络设备 的IPv6地址。这样，确保该方法适用于IPv6网络。
作为另一个示例，OAM报文中的指示信息用于第一网络设备的标识的类型为IPv4地址，那么，S1002流入可以包括：第二网络设备从OAM报文中读取第一网络设备的IPv4地址。这样，确保该方法适用于IPv4网络。
在一些可能的实现方式中，OAM报文中包括用于指示MEG类型的Type字段，该Type字段可以用于承载所述指示信息。具体实现时，如果该Type字段的取值为第一值，则该指示信息用于指示第一网络设备的标识的类型为IPv6地址；如果该Type字段的取值为第二值，则该指示信息用于指示第一网络设备的标识的类型为IPv4地址。
在另一些可能的实现方式中，OAM报文中包括Reserved字段，该Reserved字段中的至少一个比特位可以用于承载所述指示信息。具体实现时，如果该Reserved字段中至少一个比特位为第一值，则该指示信息用于指示第一网络设备的标识的类型为IPv6地址，如果该Reserved字段中至少一个比特位为第二值，则该指示信息用于指示第一网络设备的标识的类型为IPv4地址。
第三方面，本申请实施例提供了一种基于MPLS-TP的OAM报文的处理方法，该方法适用于IPv6网络，例如可以包括：第一网络设备生成OAM报文，该OAM报文包括第一网络设备的IPv6地址；第一网络设备向第二网络设备发送OAM报文。这样，确保第二网络设备接收到该OAM报文后即可从该OAM报文中准确的读取第一网络设备的标识，如此，用户既可以执行IP模式下的MPLS-TP OAM，减少配置工作量，也可以完成IPv6网络场景的MPLS-TP OAM，提高了用户的使用体验。
第四方面，本申请实施例提供了一种基于MPLS-TP的OAM报文的处理方法，该方法适用于IPv6网络，例如可以包括：第二网络设备接收第一网络设备发送的OAM报文，所述OAM报文包括所述第一网络设备的IPv6地址；第二网络设备从所述OAM报文中读取所述第一网络设备的IPv6地址。这样，第二网络设备接收到的OAM报文中包括第一网络设备的IPv6地址，从而第二网络设备即可从该OAM报文中准确的读取第一网络设备的标识，如此，用户既可以执行IP模式下的MPLS-TP OAM，减少配置工作量，也可以完成IPv6网络场景的MPLS-TP OAM，提高了用户的使用体验。
上述第三方面和第四方面提供的方法中，OAM报文中还可以包括指示信息，用于指示第一网络设备的标识的类型，具体用于指示该OAM报文是IPv4网络的报文还是IPv6网络的报文。关于指示信息在OAM报文中的携带方式可以参见上述第一方面或第二方面中关于指示信息的相关描述。
需要说明的是，上述第一方面到第四方面提供的方法中，该OAM报文还可以包括所述第一网络设备到所述第二网络设备的路径标识。该路径标识可以为下述标识中的任意一种：标签交换路径LSP标识、段Section标识、伪线PW标识或环Ring标识。具体而言，该OAM报文中用于承载该路径标识的字段可以和用于承载第一网络设备的标识的字段相邻，这样，能够使得接收方基于路径标识和第一网络设备的标识准确的完成OAM检测。
需要说明的是，上述第一方面到第四方面提供的方法中，OAM报文可以是MPLS-TP OAM的IP模式对应的报文。或者，OAM报文也可以是MPLS-TP OAM的其他模式对应 的报文，以MPLS-TP OAM的ICC模式为例，ICC模式对应的OAM报文中的指示信息也可以用于指示第一网络设备的标识(即MEP ID)的类型，具体用于指示该OAM报文为IPv4网络的报文或IPv6网络的报文。即，本申请实施例中提及的OAM报文对应的模式在本申请实施例中不作具体限定。
第五方面，本申请还提供了第一通信装置，包括收发单元和处理单元。其中，收发单元用于执行上述第一方面、第一方面任意一种可能的实现方式、第三方面或第三方面任意一种可能的实现方式提供的方法中的收发操作；处理单元用于执行上述第一方面、第一方面任意一种可能的实现方式、第三方面或第三方面任意一种可能的实现方式提供的方法中除了收发操作以外的其他操作。例如：当所述第一通信装置执行所述第一方面所述的方法时，所述收发单元用于向第二网络设备发送OAM报文；所述处理单元用于生成OAM报文。
第六方面，本申请实施例还提供了第二通信装置，该第二通信装置包括收发单元和处理单元。其中，收发单元用于执行上述第二方面、第二方面任意一种可能的实现方式、第四方面或第四方面任意一种可能的实现方式提供的方法中的收发操作；处理单元用于执行上述第二方面、第二方面任意一种可能的实现方式、第四方面或第四方面任意一种可能的实现方式提供的方法中除了收发操作以外的其他操作。例如：当所述第二通信装置执行所述第二方面所述的方法时，所述收发单元用于接收第一网络设备发送的OAM报文；所述处理单元用于根据指示信息，读取OAM报文中第一网络设备的标识。
第七方面，本申请实施例还提供了一种第一通信装置，包括第一通信接口和处理器。其中，第一通信接口用于执行前述第一方面、第一方面任意一种可能的实现方式、第三方面或第三方面任意一种可能的实现方式提供的方法中的发送操作；处理器，用于执行前述第一方面、第一方面任意一种可能的实现方式、第三方面或第三方面任意一种可能的实现方式提供的方法中除所述接收和发送操作以外的其他操作。该第一通信装置还可以包括第二通信接口，第二通信接口用于执行前述第一网络设备的接收操作。
第八方面，本申请实施例还提供了一种第二通信装置，包括第一通信接口和处理器。其中，第一通信接口用于执行前述第二方面、第二方面任意一种可能的实现方式、第四方面或第四方面任意一种可能的实现方式提供的方法中的接收操作；处理器，用于执行前述第二方面、第二方面任意一种可能的实现方式、第四方面或第四方面任意一种可能的实现方式提供的方法中除所述接收和发送操作以外的其他操作。该第二通信装置还可以包括第二通信接口，第二通信接口用于执行前述第二网络设备的发送操作。
第九方面，本申请实施例还提供了一种第一通信装置，该第一通信装置包括存储器和处理器。其中，该存储器包括计算机可读指令；与该存储器通信的处理器用于执行所述计算机可读指令，使得所述第一通信装置用于执行以上第一方面、第一方面任意一种可能的实现方式、第三方面或第三方面任意一种可能的实现方式提供的方法。
第十方面，本申请实施例还提供了一种第二通信装置，该第二通信装置包括存储器和处理器。其中，该存储器包括计算机可读指令；与该存储器通信的处理器用于执行所述计算机可读指令，使得所述第二通信装置用于执行以上第二方面、第二方面任意一种可能的实现方式、第四方面或第四方面任意一种可能的实现方式提供的方法。
第十一方面，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得所述计算机执行以上第一方面、第一方面任意一种可能的实现方式、第二方面、第二方面任意一种可能的实现方式、第三方面、第三方面任意一种可能的实现方式、第四方面或第四方面任意一种可能的实现方式提供的方法。
第十二方面，本申请实施例还提供了计算机程序产品，包括计算机程序或计算机可读指令，当所述计算机程序或所述计算机可读指令在计算机上运行时，使得计算机执行前述第一方面、第一方面任意一种可能的实现方式、第二方面、第二方面任意一种可能的实现方式、第三方面、第三方面任意一种可能的实现方式、第四方面或第四方面任意一种可能的实现方式提供的方法。
第十三方面，本申请实施例还提供了一种通信系统，该通信系统包括第五方面、第七方面或第九方面提供的所述的第一通信装置以及第六方面、第八方面或第十方面提供的第二通信装置。
需要说明的是，上述实施例中的通信装置，可以是用于执行上述方法的网络设备，也可以是指用于执行上述方法的单板、线卡、芯片等。
附图说明
图1a为本申请实施例中一种ICC模式下OAM PDU的格式示意图；
图1b为本申请实施例中一种IP模式下OAM PDU的格式示意图；
图2a为本申请实施例中一种IPv4模式下OAM PDU的格式示意图；
图2b为本申请实施例中一种IPv6模式下OAM PDU的格式示意图；
图3为本申请实施例中一种OAM报文处理方法100的信令流程图；
图4a为本申请实施例中Type字段指示LSP IPv6模式的OAM PDU的示意图；
图4b为本申请实施例中Type字段指示PW IPv4模式的OAM PDU的示意图；
图4c为本申请实施例中Type字段指示Section IPv4模式的OAM PDU的示意图；
图4d为本申请实施例中Type字段指示Section IPv6模式的OAM PDU的示意图；
图4e为本申请实施例中Type字段指示Ring IPv4模式的OAM PDU的示意图；
图4f为本申请实施例中Type字段指示Ring IPv6模式的OAM PDU的示意图；
图5a为本申请实施例中LSP场景Reserved字段指示IPv4模式的OAM PDU的示意图；
图5b为本申请实施例中LSP场景Reserved字段指示IPv6模式的OAM PDU的示意图；
图5c为本申请实施例中PW场景Reserved字段指示IPv4模式的OAM PDU的示意图；
图5d为本申请实施例中PW场景Reserved字段指示IPv6模式的OAM PDU的示意图；
图5e为本申请实施例中Section场景Reserved字段指示IPv4模式的OAM PDU的示意图；
图5f为本申请实施例中Section场景Reserved字段指示IPv6模式的OAM PDU的示意图；
图5g为本申请实施例中Ring场景Reserved字段指示IPv4模式的OAM PDU的示意图；
图5h为本申请实施例中Ring场景Reserved字段指示IPv6模式的OAM PDU的示意图；
图6为本申请实施例中图2b场景对应的另一种OAM PDU的示意图；
图7为本申请实施例中一种OAM报文处理方法200的信令流程图；
图8a为本申请实施例中图4a场景对应的另一种OAM PDU的示意图；
图8b为本申请实施例中图4a场景对应的又一种OAM PDU的示意图；
图8c为本申请实施例中图4a场景对应的再一种OAM PDU的示意图；
图9为本申请实施例中一种OAM报文处理方法300的流程示意图；
图10为本申请实施例中一种OAM报文处理方法400的流程示意图；
图11为本申请实施例中一种OAM报文处理方法500的流程示意图；
图12为本申请实施例中一种OAM报文处理方法600的流程示意图；
图13为本申请实施例中一种第一通信装置1300的结构示意图；
图14为本申请实施例中一种第二通信装置1400的结构示意图；
图15为本申请实施例中一种第一通信装置1500的结构示意图；
图16为本申请实施例中一种第二通信装置1600的结构示意图；
图17为本申请实施例中一种第一通信装置1700的结构示意图；
图18为本申请实施例中一种第二通信装置1800的结构示意图；
图19为本申请实施例中一种通信系统1900的结构示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请中的“1”、“2”、“3”、“第一”、“第二”以及“第三”等序数词用于对多个对象进行区分，不用于限定多个对象的顺序。
本申请中提及的“A和/或B”，应该理解为包括以下情形：仅包括A，仅包括B，或者同时包括A和B。
根据运营商网络的实际需要，通常将网络的管理工作划分为3大类：操作(英文：Operation)、管理(英文：Administration)和维护(英文：Maintenance)，简称OAM。MPLS-TP OAM是指在MPLS-TP中定义的OAM机制，由于MPLS-TP OAM兼容MPLS OAM的功能，针对传送网的特有情况进行了相应扩展，所以，MPLS-TP OAM受到运营商的广泛关注。
目前，MPLS-TP OAM分为两种模式：国际电信联盟运营商代码(英文：International Telecommunication Union Carrier Code，简称：ICC)模式和互联网协议(英文：Internet Protocol，简称：IP)模式。其中，ICC模式是Y.1731中定义的模式，在ICC模式下，网络设备需要配置维护实体组的终端点的标识(英文：Maintenance Entity Group End Points Identification，简称：MEP ID)和维护实体组的标识(英文：Maintenance Entity Group  Identification，简称：MEG ID)，并将MEP ID和MEG ID携带在OAM报文中，实现对网络的管理。IP模式下，网络设备以无需额外配置MEP ID和MEG ID，而将网络设备的标识和路径标识携带在OAM报文中，实现对网络的管理。
其中，OAM报文例如可以包括：连续监测报文(英文：Continuity Check Message，简称：CCM)、损耗测量报文(英文：Loss Measurement Message，简称：LMM)、丢包测量应答(英文：Loss Measurement Reply，简称：LMR)等。
以MPLS-TP OAM的CCM为例，ICC模式下该CCM的协议数据单元(英文：Protocol Data Unit，简称：PDU)的格式如图1a所示，该CCM PDU包括：MEG等级(英文：Maintenance Entity Group Level，简称：MEL)字段、版本(英文：Version)字段、操作码(英文：Operation Code，简称：OpCode)字段、远端缺陷指示(英文：Remote Defect Indication，简称：RDI)字段、预留(英文：Reserved)字段、周期(英文：Period)字段、类型长度值(英文：Type Length Value，简称：TLV)的偏置(英文：Offset)字段、序列号(英文：Sequence Number)字段、MEP ID字段、MEG ID(也称为MAID)、对本端发送数据帧计数TxFCf字段、对本端接收数据帧计数RxFCb字段、对对端发送数据帧计数TxFCb字段、Reserved字段和结束TLV(英文：End TLV)字段。其中，MEL字段的取值用于标识该CCM PDU的等级，取值范围为0～7的整数；Version字段的取值用于标识所使用的协议版本，对于MPLS-TP OAM，适用的协议版本为Y.1731，该协议版本对应的Version字段的取值为0；OpCode字段的值用于标识OAM PDU的类型，以便基于OAM PDU的类型识别OAM PDU的内容，对于CCM，OpCode的取值为1；RDI字段的取值用于标识发送端MEP是否检测到故障，当RDI字段的取值为1时，表示发送端MEP已检测出故障；当RDI字段的取值为0时，表示发送端MEP没有检测出故障；Period字段的取值用于标识发送CCM的周期，例如：当Period字段的取值为1时，表示发送CCM的周期为3.33毫秒(即，每秒发送300帧CCM),当Period字段的取值为2时，表示发送CCM的周期为10毫秒(即，每秒发送100帧CCM)；TLV Offset字段的取值用于指示OAM PDU中第一个TLV相对于TLV Offset字段的偏移量，具体取值与OAM PDU类型相关，例如：当TLV Offset＝0时，它指示第一个TLV紧跟着TLV Offset字段，CCM中TLV Offset的取值为0x46；Sequence Number字段的取值用于标识序列号，对于MPLS-TP OAM，Sequence Number字段的取值为0；MEP ID字段的长度为16比特，该MEP ID的取值用于在MEG ID中唯一标识发送CCM帧的MEP，通常取低13比特有效；MEP ID字段的长度为384比特，该MEG ID的取值用于全局唯一的标识发送CCM帧的MEP所属MEG；TxFCf字段的取值用于指示在CCM帧传输时，运载MEP向其对等MEP发送的未超标数据帧计数器的计数值；RxFCb字段的取值用于指示在CCM帧传输时，对等MEP接收到的未超标数据帧计数器的计数值，当不进行双端性能统计时，RxFCb字段的取值为零；TxFCb字段的取值用于指示在CCM帧传输时，对等MEP发送的未超标数据帧计数器的计数值。当不进行双端性能统计时，TxFCf字段、RxFCb字段和TxFCb字段的取值均为零。End TLV字段的取值用于标识该CCM PDU中包括的全零字节的数量。
IP模式下该CCM PDU的格式如图1b所示，该CCM PDU包括：MEL字段、Version 字段、OpCode字段、RDI字段、Reserved字段、Period字段、TLV Offset字段、Sequence Number字段、Type字段、Reserved/PWType字段、网络设备的标识字段、路径标识字段、Reserved字段、TxFCf字段、RxFCb字段、TxFCb字段、Reserved字段和End TLV字段。其中，MEL字段、Version字段、OpCode字段、RDI字段、Period字段、TLV Offset字段、Sequence Number字段、TxFCf字段、RxFCb字段、TxFCb字段和End TLV字段相关描述参见图1a中的说明。Type字段的取值用于指示该CCM检测的路径类型，例如：Type字段的取值为1，表示该CCM检测标签交换路径(英文：Label Switched Path，简称：LSP)；Reserved/PWType字段的取值用于指示业务类型，例如：当Reserved/PWType字段的取值为0x0000时，用于指示Type字段的取值所指示的路径类型，如：Type＝1且Reserved/PWType＝0x0000，表示CCM检测LSP，当Reserved/PWType字段的取值为0x0002～0x001B、0x1001和0x1002，分别用于指示不同的伪线(英文：Pseudo Wire，简称：PW)业务类型；网络设备的标识字段的取值用于唯一标识发送该CCM的网络设备，例如：假设网络设备为标签交换路由器(英文：Label Switching Router，简称：LSR)，那么，网络设备的标识字段的取值可以是LSR ID；路径标识字段的取值用于唯一标识待检测的路径，例如：假设网络设备为LSR，那么，该路径标识字段的取值具体可以是LSR所在的隧道的标识。
需要说明的是，MPLS-TP OAM操作基于维护实体(英文：Maintenance Entity，简称：ME)进行，一个ME可以理解为一条路径的两个端点，即，一对MEP以及中间经过的MEG中间节点(英文：Maintenance Entity Group Intermediate Points，简称：MIP)，OAM功能主要运行在两个MEP之间。一个或者多个属于同一条传送路径的ME构成一个MEG。其中，MEP具有发起和终止OAM报文的能力，可以进行故障管理和性能监测，而MIP是MEG的中间节点，能够转发OAM报文，并响应部分的OAM报文，并不能发起OAM报文。
在ICC模式下，为了能够唯一标识发送方网络设备和OAM检测的传送路径，网络设备配置MEP ID和MEG ID，并将MEP ID和MEG ID携带在OAM报文中。这样，如果网络中的网络设备数量较多，需要进行的配置量较大，而且，为了OAM检测的有效性，还需要避免大量网络设备上配置重复的MEP ID和MEG ID，这对于用户而言不够简单和方便。而IP模式则利用网络设备上已知的信息——网络设备的标识和路径标识，替代OAM报文中MEP ID和MEG ID的功能，即：唯一标识发送方网络设备和OAM检测的传送路径，所以，MPLS-TP OAM的IP模式无需网络设备配置MEP ID和MEG ID，能够节约用户的配置工作量，更无需考虑重复配置的问题，优势较为明显，受到用户的青睐。
目前，MPLS-TP OAM的IP模式下的OAM报文如图1b所示，网络设备的标识字段的长度为32比特，仅适用于携带第四版互联网协议(英文：Internet Protocol version 4，简称：IPv4)场景下网络设备的IP地址，无法携带第六版互联网协议(英文：Internet Protocol version 6，简称：IPv6)场景下网络设备128比特的IP地址，所以，MPLS-TP OAM的IP模式无法满足IPv6网络以及从IPv4平滑演进到IPv6的网络。
基于此，本申请实施例提供了一种OAM报文处理方法，发送方网络设备生成的OAM报文中包括指示信息，该指示信息用于指示发送方网络设备的标识的类型，即，指示发送方网络设备的标识是IPv4地址还是IPv6地址，当OAM报文中携带的指示信息指示该发送 方网络设备的IP地址是IPv4地址时，该OAM报文中包括的第一网络设备的标识为第一网络设备的IPv4地址；当OAM报文中携带的指示信息指示该发送方网络设备的IP地址是IPv6地址时，该OAM报文中包括的第一网络设备的标识为第一网络设备的IPv6地址，这样，接收到该OAM报文的第二网络设备即可基于该指示信息，确定该OAM报文中携带的发送方网络设备的标识的类型，并且，从该OAM报文中准确的读取发送方网络设备的标识，如此，用户既可以执MPLS-TP OAM，减少配置工作量，也可以完成IPv4网络、IPv6网络以及包括IPv4和IPv6的网络等多场景的MPLS-TP OAM，扩宽了MPLS-TP OAM的应用范围，提高了用户的使用体验。
需要说明的是，本申请实施例中的OAM报文可以是MPLS-TP OAM的任意模式对应的报文，例如，如果OAM报文为MPLS-TP OAM的ICC模式对应的报文，则，OAM报文中的指示信息也可以用于指示第一网络设备的标识(即MEP ID)的类型，具体用于指示该OAM报文为IPv4网络的报文或IPv6网络的报文。由于MPLS-TP OAM的IP模式无需网络设备配置MEP ID和MEG ID，能够节约配置资源，所以，IP模式给用户的使用体验更好，基于此，本申请实施例中以MPLS-TP OAM的IP模式对应的OAM报文为例进行相关描述和说明。
举例来说，仍然以CCM为例，本申请实施例中，设置Type字段的取值用于指示该CCM检测的MEG类型以及适用的IP网络。例如：Type字段的取值为1～4分别表示该CCM检测LSP、PW、段(英文：Section)和环(英文:Ring)类型的MEG，且适用IPv4网络；Type字段的取值为5～8分别表示该CCM检测LSP、PW、Section和Ring类型的MEG，且适用IPv6网络。
作为一个示例，对于IPv4网络中的网络设备而言，生成的CCM中的CCM PDU的格式如图2a所示，该CCM PDU除了包括MEL字段、Version字段、OpCode字段、RDI字段、Reserved字段、Period字段、TLV Offset字段、Sequence Number字段、TxFCf字段、RxFCb字段、TxFCb字段、Reserved字段和End TLV字段以外，还包括：Type字段、Reserved字段、网络设备的标识字段、路径标识字段、Reserved字段。其中，Type字段的取值为1，表示该CCM检测LSP类型的MEG且适用IPv4网络；网络设备的标识字段的取值为该LSR ID，该LSR ID具体可以是该LSR的32比特的IPv4地址；路径标识字段的取值为该LSR所在隧道(英文：Tunnel)的标识。
作为另一个示例，对于IPv6网络中的网络设备而言，生成的CCM中的CCM PDU的格式如图2b所示，该CCM PDU中，Type字段的取值为6，表示该CCM检测PW类型的MEG且适用IPv6网络；网络设备的标识字段的取值为该LSR ID，该LSR ID具体可以是该LSR的128比特的IPv6地址；路径标识字段的取值为PW的虚拟信道(英文：Virtual Channel，简称：VC)的标识。
这样，接收方网络设备即可基于所接收到OAM报文中的指示信息，准确的读取到发送方网络设备的标识，从而有效的实现OAM的功能。
需要说明的是，本申请实施例中的网络设备，是指能够实现OAM功能的任意网络设备，例如，可以是分组传输网(英文：Packet Transport Network，简称：PTN)设备、交换 机、路由器等，在本申请实施例中不作具体限定。
可以理解的是，上述场景仅是本申请实施例提供的一个场景示例，本申请实施例并不限于此场景。
下面结合附图，通过实施例来详细说明本申请实施例中一种OAM报文处理方法的具体实现方式。
本申请实施例提供的一种OAM报文处理方法100，该方法100以MPLS-TP OAM的IP模式为例，适用于IPv4网络、IPv6网络以及既包括IPv4又包括IPv6的网络。图3为本申请实施例中一种OAM报文处理方法100的流程示意图。参见图3，该方法100例如可以包括：
S301，网络设备1生成OAM报文，该OAM报文包括指示信息和网络设备1的标识1，指示信息用于指示网络设备1的标识1的类型。
其中，网络设备1为MEG中发起OAM报文的MEP，该MEG中接收并终止该OAM报文的MEP为网络设备2。OAM报文，具体是指MPLS-TP OAM的IP模式对应的报文。
OAM报文中包括网络设备1的标识1和路径标识1，分别用于告知网络设备2发起该OAM检测的网络设备为网络设备1，OAM检测的路径为路径1，从而确保能够基于该OAM报文实现有效的OAM检测。以网络设备1为LSR为例，网络设备1的标识1可以是LSR ID，该LSR ID用于唯一标识LSR。LSR ID例如可以是该LSR的IP地址，如果LSR属于IPv4网络，则，LSR ID为该LSR的IPv4地址，如果LSR属于IPv6网络，则，LSR ID为该LSR的IPv6地址。路径标识1
为了扩宽MPLS-TP OAM的应用范围，使得OAM功能适用于IPv4网络、IPv6网络以及包括IPv4和IPv6的网络等多种场景，如果该网络设备1的标识1为IPv4地址，则，用于承载该网络设备1的标识1的字段至少占用该OAM报文中的32比特的空间；如果该网络设备1的标识1为IPv6地址，则，用于承载该网络设备1的标识1的字段至少占用该OAM报文中的128比特的空间。为了让接收方网络设备能够有效的获取到网络设备1的标识1，在该OAM报文中也携带了指示信息，该指示信息用于指示网络设备1的标识1的类型，即，指示信息可以用于指示OAM报文为IPv4网络的报文还是IPv6网络的报文，或者说，指示信息可以指示网络设备1的标识1是IPv6地址还是IPv4地址。这样，接收方网络设备即可基于指示信息，准确的从OAM报文中获得网络设备1的标识1，从而能够实现有效的OAM检测。
作为一个示例，指示信息可以被承载于Type字段中，该Type字段还用于指示MEG的类型。例如：Type字段的取值为1，表示该OAM检测LSP类型的MEG，且发起OAM检测的网络设备1的标识1为IPv4地址；Type字段的取值为2，表示该OAM检测PW类型的MEG，且发起OAM检测的网络设备1的标识1为IPv4地址；Type字段的取值为3，表示该OAM检测Section类型的MEG，且发起OAM检测的网络设备1的标识1为IPv4地址；Type字段的取值为4，表示该OAM检测Ring类型的MEG，且发起OAM检测的网络设备1的标识1为IPv4地址；Type字段的取值为5，表示该OAM检测LSP类型的MEG， 且发起OAM检测的网络设备1的标识1为IPv6地址；Type字段的取值为6，表示该OAM检测PW类型的MEG，且发起OAM检测的网络设备1的标识1为IPv6地址；Type字段的取值为7，表示该OAM检测Section类型的MEG，且发起OAM检测的网络设备1的标识1为IPv6地址；Type字段的取值为8，表示该OAM检测Ring类型的MEG，且发起OAM检测的网络设备1的标识1为IPv6地址。基于此，Type字段的取值为1～4中的任意一个数值时，可以指示网络设备1的标识1的类型为IPv4地址；Type字段的取值为5～8中的任意一个数值时，可以指示网络设备1的标识1的类型为IPv6地址。
作为另一个示例，指示信息还可以被承载在Reserved字段中。例如，使用该Reserved字段中未被占用的至少一个比特位承载该指示信息。需要说明的是，Reserved字段为16比特(第0位到第15位)的空间，目前的低8位和第12位已经被占用，用于表征PW的业务类型。基于此，指示信息具体可以是第8位、第9位、第10位、第11位、第13位、第14位以及第15位中的至少一位。当至少一个比特位为第一值时，则指示所网络设备1的标识1的类型为IPv4地址，当至少一个比特位为第二值时，则指示所网络设备1的标识1的类型为IPv6地址。一种情况下，以Reserved字段的第8位承载指示信息为例，第一值为0，第二值为1，此时，当该Reserved字段的第8位的取值为0时，指示所网络设备1的标识1的类型为IPv4地址，当该Reserved字段的第8位的取值为1时，指示所网络设备1的标识1的类型为IPv6地址。另一种情况下，以Reserved字段的第8位和第9位承载指示信息为例，第一值为00，第二值为11，此时，当该Reserved字段的第8位和第9位的取值为00时，指示所网络设备1的标识1的类型为IPv4地址，当该Reserved字段的第8位和第9位的取值为11时，指示所网络设备1的标识1的类型为IPv6地址。再一种情况下，以Reserved字段的第8位到第11位承载指示信息为例，第一值为0，第二值为1，此时，当该Reserved字段的第8位到第11位为0000(取值为0)时，指示所网络设备1的标识1的类型为IPv4地址，当该Reserved字段的第8位到第11位为0001(取值为1)时，指示所网络设备1的标识1的类型为IPv6地址。
对于Type字段承载指示信息的情况，以CCM中检测的路径类型为LSP、Section、PW和Ring为例，介绍OAM PDU的格式。
检测的路径类型为LSP时，如果网络设备1的标识1为网络设备1的IPv4地址，则，OAM PDU具体参见上述图2a所示，Type字段＝1，表示该OAM检测LSP类型的MEG且网络设备1的标识1的类型为IPv4地址；网络设备1的标识1字段(图中表示为LSR ID)＝网络设备1的32比特的IPv4地址；路径标识1字段(图中表示为LSP ID)＝该网络设备1所在Tunnel的标识。如果网络设备1的标识1为网络设备1的IPv6地址，则，OAM PDU具体参见图4a所示，Type字段＝5，表示该OAM检测LSP类型的MEG且网络设备1的标识1的类型为IPv6地址；LSR ID＝网络设备1的128比特的IPv6地址；路径标识1字段(图中表示为LSP ID)＝该网络设备1所在Tunnel的标识。
检测的路径类型为PW时，如果网络设备1的标识1为网络设备1的IPv4地址，则，OAM PDU具体参见上述图4b所示，Type字段＝2，表示该OAM检测PW类型的MEG且网络设备1的标识1的类型为IPv4地址；网络设备1的标识1字段(图中表示为LSR ID) ＝网络设备1的32比特的IPv4地址；路径标识1字段(图中表示为PW VC ID)＝该网络设备1所在PW VC的标识。如果网络设备1的标识1为网络设备1的IPv6地址，则，OAM PDU具体参见上述图2b所示，Type字段＝6，表示该OAM检测PW类型的MEG且网络设备1的标识1的类型为IPv6地址；LSR ID＝网络设备1的128比特的IPv6地址；路径标识1字段(图中表示为PW VC ID)＝该网络设备1所在PW VC的标识。其中，Reserved字段中的低8位和第12位被占用，用于表示该PW VC的类型(即表示PW的业务类型)，该场景下，Reserved字段也称为PW VC Type字段。
检测的路径类型为Section时，如果网络设备1的标识1为网络设备1的IPv4地址，则，OAM PDU具体参见上述图4c所示，Type字段＝3，表示该OAM检测Section类型的MEG且网络设备1的标识1的类型为IPv4地址；网络设备1的标识1字段(图中表示为LSR ID)＝网络设备1的32比特的IPv4地址；路径标识1字段(图中表示为Section ID)＝该网络设备1所属Section的标识。如果网络设备1的标识1为网络设备1的IPv6地址，则，OAM PDU具体参见图4d所示，Type字段＝7，表示该OAM检测Section类型的MEG且网络设备1的标识1的类型为IPv6地址；LSR ID＝网络设备1的128比特的IPv6地址；路径标识1字段(图中表示为Section ID)＝该网络设备1所属Section的标识。
检测的路径类型为Ring时，如果网络设备1的标识1为网络设备1的IPv4地址，则，OAM PDU具体参见上述图4e所示，Type字段＝4，表示该OAM检测Ring类型的MEG且网络设备1的标识1的类型为IPv4地址；网络设备1的标识1通过Ring中该网络设备1的标识1(图中表示为Ring Node ID)和方向表示，即，该OAM PDU中包括8比特的方向(英文：Direction)字段和8比特的Ring Node ID字段；路径标识1字段(图中表示为Ring ID)＝该网络设备1所属的Ring的标识。如果网络设备1的标识1为网络设备1的IPv6地址，则，OAM PDU具体参见图4f所示，Type字段＝8，表示该OAM检测Ring类型的MEG且网络设备1的标识1的类型为IPv6地址；LSR ID通过Direction字段和Ring Node ID字段表示；路径标识1字段(图中表示为Ring ID)＝该网络设备1所属Ring的标识。
对于Reserved字段承载指示信息的情况，假设Reserved字段的第8位用于承载指示信息，以CCM中检测的路径类型为LSP、Section、PW和Ring为例，介绍OAM PDU的格式。
检测的路径类型为LSP时，Type字段＝1，表示该OAM检测LSP类型的MEG。如果网络设备1的标识1为网络设备1的IPv4地址，则，OAM PDU具体参见上述图5a所示，Reserved字段的第8位＝0，指示网络设备1的标识1的类型为IPv4地址；网络设备1的标识1字段(图中表示为LSR ID)＝网络设备1的32比特的IPv4地址；路径标识1字段(图中表示为LSP ID)＝该网络设备1所在Tunnel的标识。如果网络设备1的标识1为网络设备1的IPv6地址，则，OAM PDU具体参见图5b所示，Reserved字段的第8位＝1，指示网络设备1的标识1的类型为IPv6地址；LSR ID＝网络设备1的128比特的IPv6地址；路径标识1字段(图中表示为LSP ID)＝该网络设备1所在Tunnel的标识。
检测的路径类型为PW时，Type字段＝2，表示该OAM检测PW类型的MEG。如果网络设备1的标识1为网络设备1的IPv4地址，则，OAM PDU具体参见上述图5c所示， Reserved字段的第8位＝0，指示网络设备1的标识1的类型为IPv4地址；网络设备1的标识1字段(图中表示为LSR ID)＝网络设备1的32比特的IPv4地址；路径标识1字段(图中表示为PW VC ID)＝该网络设备1所在PW VC的标识。如果网络设备1的标识1为网络设备1的IPv6地址，则，OAM PDU具体参见上述图5d所示，Reserved字段的第8位＝1，指示网络设备1的标识1的类型为IPv6地址；LSR ID＝网络设备1的128比特的IPv6地址；路径标识1字段(图中表示为PW VC ID)＝该网络设备1所在PW VC的标识。其中，Reserved字段中的低8位和第12位被占用，用于表示该PW VC的类型(即表示PW的业务类型)，该场景下，Reserved字段也称为PW VC Type字段。
检测的路径类型为Section时，Type字段＝3，表示该OAM检测Section类型的MEG。如果网络设备1的标识1为网络设备1的IPv4地址，则，OAM PDU具体参见上述图5e所示，Reserved字段的第8位＝0，指示网络设备1的标识1的类型为IPv4地址；网络设备1的标识1字段(图中表示为LSR ID)＝网络设备1的32比特的IPv4地址；路径标识1字段(图中表示为Section ID)＝该网络设备1所属Section的标识。如果网络设备1的标识1为网络设备1的IPv6地址，则，OAM PDU具体参见图5f所示，Reserved字段的第8位＝1，指示网络设备1的标识1的类型为IPv6地址；LSR ID＝网络设备1的128比特的IPv6地址；路径标识1字段(图中表示为Section ID)＝该网络设备1所属Section的标识。
检测的路径类型为Ring时，Type字段＝4，表示该OAM检测Ring类型的MEG。如果网络设备1的标识1为网络设备1的IPv4地址，则，OAM PDU具体参见上述图5g所示，Reserved字段的第8位＝0，指示网络设备1的标识1的类型为IPv4地址；网络设备1的标识1通过Direction字段和Ring Node ID字段表示；路径标识1字段(图中表示为Ring ID)＝该网络设备1所属的Ring的标识。如果网络设备1的标识1为网络设备1的IPv6地址，则，OAM PDU具体参见图5h所示，Reserved字段的第8位＝1，指示网络设备1的标识1的类型为IPv6地址；LSR ID通过Direction字段和Ring Node ID字段表示；路径标识1字段(图中表示为Ring ID)＝该网络设备1所属Ring的标识。
需要说明的是，上述示例中，网络设备1的标识1占用OAM报文中OAM PDU的连续空间，且承载网络设备1的标识1的字段和承载路径标识1的字段相邻。在另一些可能的实现方式中，为了不对目前IP模式下承载网络设备1的标识1的字段长度进行扩展，也可以在网络设备1为IPv6网络中的网络设备时，将128比特的网络设备1的标识1进行分段，划分为前32比特和后96比特，其中，前32比特存储在目前IP模式下承载网络设备1的标识1的字段中，在承载路径标识1的字段之后的Reserved字段中存储IPv6地址的后96位。以图2b所示的场景为例，该实现方式中OAM PDU的格式例如可以参见图6。
这样，网络设备1生成携带指示信息的OAM报文，使得OAM机制适用更加广泛的应用场景成为了可能。
S302，网络设备1向网络设备2发送OAM报文。
S303，网络设备2接收网络设备1发送的OAM报文。
本申请实施例中，不对网络设备1向网络设备2发送OAM报文的时机、规律以及具体发送方式进行限定。
S304，网络设备2根据指示信息，读取OAM报文中网络设备1的标识1。
具体实现时，网络设备2接收到OAM报文后，从该OAM报文中获取指示信息，基于指示信息的指示，准确的从OAM报文中读取网络设备1的标识1。作为一个示例，当指示信息用于指示网络设备1的标识1的类型为IPv6地址，那么，S304可以是网络设备2从OAM报文中读取网络设备1的IPv6地址。作为另一个示例，当指示信息用于指示网络设备1的标识1的类型为IPv4地址，那么，S304可以是网络设备2从OAM报文中读取网络设备1的IPv4地址。
举例来说：假设OAM报文中的OAM PDU的格式如图2a、图4b、图4c或图4e，S304具体可以是指：网络设备2解析OAM报文获得Type字段的取值，基于Type字段的取值确定发起OAM报文的网络设备1的标识1的类型为IPv4地址，那么，从该OAM报文中读取用于承载路径标识1的字段之前且该字段相邻的32比特的信息，作为网络设备1的标识1，即，网络设备1的IPv4地址。假设OAM报文中的OAM PDU的格式如图4a、图2b、图4d或图4f，S304具体可以是指：网络设备2解析OAM报文获得Type字段的取值，基于Type字段的取值确定发起OAM报文的网络设备1的标识1的类型为IPv6地址，那么，从该OAM报文中读取用于承载路径标识1的字段之前且该字段相邻的128比特的信息，作为网络设备1的标识1，即，网络设备1的IPv6地址。此外，假设OAM报文中的OAM PDU的格式如图6，S304具体可以是指：网络设备2解析OAM报文获得Type字段的取值，基于Type字段的取值确定发起OAM报文的网络设备1的标识1的类型为IPv6地址，那么，从该OAM报文中读取用于承载路径标识1的字段之前且该字段相邻的32比特的信息，以及用于承载路径标识1的字段之后且该字段相邻的96比特，将两者进行拼接获得网络设备1的标识1，即，网络设备1的IPv6地址。
举例来说：假设OAM报文中的OAM PDU的格式如图5a、图5c、图5e或图5g，S304具体可以是指：网络设备2解析OAM报文获得Reserved字段中第8位的取值，基于Reserved字段中第8位的取值确定发起OAM报文的网络设备1的标识1的类型为IPv4地址，那么，从该OAM报文中读取Reserved字段之后的、用于承载路径标识1的字段之前的32比特的信息，作为网络设备1的标识1，即，网络设备1的IPv4地址。假设OAM报文中的OAM PDU的格式如图5b、图5d、图5f或图5h，S304具体可以是指：网络设备2解析OAM报文获得Reserved字段中第8位的取值，基于Reserved字段中第8位的取值确定发起OAM报文的网络设备1的标识1的类型为IPv6地址，那么，从该OAM报文中读取Reserved字段之后的、用于承载路径标识1的字段之前的128比特的信息，作为网络设备1的标识1，即，网络设备1的IPv6地址。
需要说明的是，本申请实施例中的举例以OAM报文为CCM为例进行说明，对于LMM、LMR报文等其它的OAM报文，均适用于本申请实施例提供的OAM报文处理方法，即，在OAM报文中携带用于指示网络设备的标识的类型的指示信息，使得OAM机制适用更多的网络场景。所有类型OAM报文的具体实现方式均可以参见CCM报文的相关描述，在本申请实施例不再赘述。
需要说明的是，网络设备2基于接收到的OAM报文，即可实现对网络设备1到网络 设备2的MEG的OAM检测，具体的检测原理和实现方式不是本申请实施例的改进点，在本申请实施例不作详细介绍。
可见，通过本申请实施例提供的方法100，发送方网络设备生成的OAM报文中包括指示信息，该指示信息用于指示发送方网络设备的标识的类型，即，指示发送方网络设备的标识是IPv4地址还是IPv6地址，当OAM报文中携带的指示信息指示该发送方网络设备的IP地址是IPv4地址时，该OAM报文中包括的发送方网络设备的标识为发送方网络设备的IPv4地址；当OAM报文中携带的指示信息指示该发送方网络设备的IP地址是IPv6地址时，该OAM报文中包括的发送方网络设备的标识为发送方网络设备的IPv6地址，这样，接收到该OAM报文的接收方网络设备即可基于该指示信息，确定该OAM报文中携带的发送方网络设备的标识的类型，并且，从该OAM报文中准确的读取发送方网络设备的标识，如此，用户既可以执行MPLS-TP OAM，减少配置工作量，也可以完成IPv4网络、IPv6网络以及包括IPv4和IPv6的网络等多场景的MPLS-TP OAM，扩宽了MPLS-TP OAM的应用范围，提高了用户的使用体验。
图7为本申请实施例中一种OAM报文处理方法200的流程示意图。参见图7，该方法200以MPLS-TP OAM的IP模式为例，适用于IPv6网络，该方法200例如可以包括：
S701，网络设备1生成OAM报文，该OAM报文包括网络设备1的IPv6地址。
由于网络设备1的标识的类型为IPv6地址，所以，OAM报文中携带的网络设备1的标识1需要占用128比特的空间。为了适用IPv6网络下的MPLS-TP OAM机制，网络设备1生成的OAM报文中需要包括128比特的空间用于承载网络设备1的标识1。
作为一个示例，OAM报文可以将承载网络设备1的标识1的字段进行扩展，从32比特扩展为128比特，用于承载网络设备1的IPv6地址。以图4a对应场景为例，基于该方法200生成的OAM报文中的OAM PDU例如可以参见图8a所示。
作为另一个示例，OAM报文不扩展承载网络设备1的标识1的字段，而是利用用于承载路径标识1的字段之后的Reserved字段的96比特，用于承载网络设备1的IPv6地址的后96比特；或者，利用用于承载路径标识1的字段之后的Reserved字段的128比特，用于承载网络设备1的IPv6地址。仍然以图4a对应场景为例，基于该方法200生成的OAM报文中的OAM PDU例如可以参见图8b所示或图8c所示，其中，图8b中原用于承载网络设备1的标识1的字段承载网络设备1的IPv6地址的前32比特，Reserved字段承载网络设备1的IPv6地址的后96比特；图8c中原用于承载网络设备1的标识1的字段的取值不限定，Reserved字段承载网络设备1的IPv6地址的128比特。
需要说明的是，该OAM报文中还可以包括路径标识1，用于指示OAM检测的路径类型，路径类型例如可以是：LSP、PW、Section或Ring。那么，该路径标识1可以为下述标识中的任意一种：LSP标识、Section标识、PW标识或Ring标识。
S702，网络设备1向网络设备2发送OAM报文。
S703，网络设备2接收网络设备1发送的OAM报文。
S704，网络设备2从OAM报文中读取网络设备1的IPv6地址。
具体实现时，网络设备2接收到OAM报文后，从该OAM报文中读取网络设备1的标识1，即，从OAM报文中读取128比特长度的网络设备1的IPv6地址。
该实施例中，OAM报文中还可以包括指示信息，用于指示网络设备1的标识的类型，具体用于指示该OAM报文是IPv4网络的报文还是IPv6网络的报文。关于指示信息在OAM报文中的携带方式可以参见上述图3所示实施例中关于指示信息的相关描述。
可见，通过本申请实施例提供的方法200，发送方网络设备生成的OAM报文中包括网络设备1的IPv6地址作为网络设备1的标识1，这样，接收到该OAM报文的接收方网络设备即可从该OAM报文中准确的读取发送方网络设备的标识，如此，用户既可以执行IP模式下的MPLS-TP OAM，减少配置工作量，也可以完成IPv6网络场景的MPLS-TP OAM，提高了用户的使用体验。
图9示出了本申请实施例中一种OAM报文处理方法300的流程示意图。参见图9，该方法300针对MPLS-TP OAM的IP模式，以第一网络设备为执行主体，该方法300例如可以包括：
S901，第一网络设备生成OAM报文，该OAM报文包括指示信息和第一网络设备的标识，指示信息用于指示第一网络设备的标识的类型；
S902，第一网络设备向第二网络设备发送所述OAM报文。
其中，第一网络设备可以是上述方法100中的网络设备1，第二网络设备是上述方法100中的网络设备2。该第一网络设备执行的操作具体可以参见网络设备1在方法100中执行的操作。其中，OAM报文可以是方法100中的OAM报文，指示信息可以是方法100中的指示信息，第一网络设备的标识可以是方法100中网络设备1的标识1。
作为一个示例，OAM报文中的指示信息用于指示第一网络设备的标识的类型为IPv6地址。这样，确保该方法300适用于IPv6网络。
作为另一个示例，OAM报文中的指示信息用于第一网络设备的标识的类型为IPv4地址。这样，确保该方法300适用于IPv4网络
在一些可能的实现方式中，OAM报文中包括用于指示MEG类型的Type字段，该Type字段可以用于承载所述指示信息。具体实现时，如果该Type字段的取值为第一值，则该指示信息用于指示第一网络设备的标识的类型为IPv6地址；如果该Type字段的取值为第二值，则该指示信息用于指示第一网络设备的标识的类型为IPv4地址。
在另一些可能的实现方式中，OAM报文中包括Reserved字段，该Reserved字段中的至少一个比特位可以用于承载所述指示信息。具体实现时，如果该Reserved字段中至少一个比特位为第一值，则该指示信息用于指示第一网络设备的标识的类型为IPv6地址，如果该Reserved字段中至少一个比特位为第二值，则该指示信息用于指示第一网络设备的标识的类型为IPv4地址。
作为一个示例，该OAM报文还可以包括所述第一网络设备到所述第二网络设备的路径标识。该路径标识可以为下述标识中的任意一种：标签交换路径LSP标识、段Section标识、伪线PW标识或环Ring标识。具体而言，该OAM报文中用于承载该路径标识的字段可以和用于承载第一网络设备的标识的字段相邻，这样，能够使得接收方基于路径标识 和第一网络设备的标识准确的完成OAM检测。
需要说明的是，本申请实施例中的OAM报文具体为MPLS-TP OAM的IP模式对应的报文。
可见，通过本申请实施例提供的方法300，第一网络设备生成的OAM报文中包括指示信息，该指示信息用于指示第一网络设备的标识的类型，即，指示第一网络设备的标识是IPv4地址还是IPv6地址，当OAM报文中携带的指示信息指示该第一网络设备的IP地址是IPv4地址时，该OAM报文中包括的第一网络设备的标识为第一网络设备的IPv4地址；当OAM报文中携带的指示信息指示该第一网络设备的IP地址是IPv6地址时，该OAM报文中包括的第一网络设备的标识为第一网络设备的IPv6地址，这样，能够确保接收到该OAM报文的接收方网络设备基于该指示信息，确定该OAM报文中携带的第一网络设备的标识的类型，并且，从该OAM报文中准确的读取第一网络设备的标识，如此，用户既可以执行IP模式下的MPLS-TP OAM，减少配置工作量，也可以完成IPv4网络、IPv6网络以及包括IPv4和IPv6的网络等多场景的MPLS-TP OAM，扩宽了MPLS-TP OAM的应用范围，提高了用户的使用体验。
图10示出了本申请实施例中一种OAM报文处理方法400的流程示意图。参见图10，该方法400针对MPLS-TP OAM的IP模式，以第二网络设备为执行主体，该方法400例如可以包括：
S1001，第二网络设备接收第一网络设备发送的OAM报文，该OAM报文包括指示信息和第一网络设备的标识，指示信息用于指示第一网络设备的标识的类型；
S1002，第二网络设备根据所述指示信息，读取OAM报文中第一网络设备的标识。
其中，第二网络设备可以是上述方法100中的网络设备2，第一网络设备是上述方法100中的网络设备1。该第二网络设备执行的操作具体可以参见网络设备2在方法100中执行的操作。其中，OAM报文可以是方法100中的OAM报文，指示信息可以是方法100中的指示信息，第一网络设备的标识可以是方法100中网络设备1的标识1。
作为一个示例，OAM报文中的指示信息可以用于指示第一网络设备的标识的类型为IPv6地址，那么，S1002例如可以包括：第二网络设备从OAM报文中读取第一网络设备的IPv6地址。这样，确保该方法400适用于IPv6网络。
作为另一个示例，OAM报文中的指示信息用于第一网络设备的标识的类型为IPv4地址，那么，S1002流入可以包括：第二网络设备从OAM报文中读取第一网络设备的IPv4地址。这样，确保该方法400适用于IPv4网络。
在一些可能的实现方式中，OAM报文中包括用于指示MEG类型的Type字段，该Type字段可以用于承载所述指示信息。具体实现时，如果该Type字段的取值为第一值，则该指示信息用于指示第一网络设备的标识的类型为IPv6地址；如果该Type字段的取值为第二值，则该指示信息用于指示第一网络设备的标识的类型为IPv4地址。
在另一些可能的实现方式中，OAM报文中包括Reserved字段，该Reserved字段中的至少一个比特位可以用于承载所述指示信息。具体实现时，如果该Reserved字段中至少一个比特位为第一值，则该指示信息用于指示第一网络设备的标识的类型为IPv6地址，如果 该Reserved字段中至少一个比特位为第二值，则该指示信息用于指示第一网络设备的标识的类型为IPv4地址。
作为一个示例，该OAM报文还可以包括所述第一网络设备到所述第二网络设备的路径标识。该路径标识可以为下述标识中的任意一种：标签交换路径LSP标识、段Section标识、伪线PW标识或环Ring标识。具体而言，该OAM报文中用于承载该路径标识的字段可以和用于承载第一网络设备的标识的字段相邻，这样，能够使得接收方基于路径标识和第一网络设备的标识准确的完成OAM检测。
需要说明的是，本申请实施例中的OAM报文具体为MPLS-TP OAM的IP模式对应的报文。
可见，通过本申请实施例提供的方法400，第二网络设备接收到的OAM报文中包括指示信息，该指示信息用于指示第一网络设备的标识的类型，即，指示第一网络设备的标识是IPv4地址还是IPv6地址，这样，第二网络设备即可基于该指示信息，确定该OAM报文中携带的第一网络设备的标识的类型，并且，从该OAM报文中准确的读取第一网络设备的标识，如此，用户既可以执行IP模式下的MPLS-TP OAM，减少配置工作量，也可以完成IPv4网络、IPv6网络以及包括IPv4和IPv6的网络等多场景的MPLS-TP OAM，扩宽了MPLS-TP OAM的应用范围，提高了用户的使用体验。
图11示出了本申请实施例中一种OAM报文处理方法500的流程示意图。参见图11，该方法500针对MPLS-TP OAM的IP模式，以第一网络设备为执行主体，该方法500例如可以包括：
S1101，第一网络设备生成OAM报文，该OAM报文包括第一网络设备的IPv6地址；
S1102，第一网络设备向第二网络设备发送OAM报文。
其中，第一网络设备可以是上述方法200中的网络设备1，第二网络设备是上述方法200中的网络设备2。该第一网络设备执行的操作具体可以参见网络设备1在方法200中执行的操作。其中，OAM报文可以是方法200中的OAM报文，第一网络设备的IPv6地址可以是方法200中网络设备1的IPv6地址。
作为一个示例，该OAM报文还可以包括所述第一网络设备到所述第二网络设备的路径标识。该路径标识可以为下述标识中的任意一种：标签交换路径LSP标识、段Section标识、伪线PW标识或环Ring标识。具体而言，该OAM报文中用于承载该路径标识的字段可以和用于承载第一网络设备的标识的字段相邻，这样，能够使得接收方基于路径标识和第一网络设备的标识准确的完成OAM检测。
需要说明的是，本申请实施例中的OAM报文具体为MPLS-TP OAM的IP模式对应的报文。
可见，通过本申请实施例提供的方法500，第一网络设备生成的OAM报文中包括第一网络设备的IPv6地址作为第一网络设备的标识，这样，使得第二网络设备接收到该OAM报文后即可从该OAM报文中准确的读取第一网络设备的标识，如此，用户既可以执行IP模式下的MPLS-TP OAM，减少配置工作量，也可以完成IPv6网络场景的MPLS-TP OAM，提高了用户的使用体验。
图12示出了本申请实施例中一种OAM报文处理方法600的流程示意图。参见图12，该方法600针对MPLS-TP OAM的IP模式，以第二网络设备为执行主体，该方法600例如可以包括：
S1201，第二网络设备接收第一网络设备发送的OAM报文，所述OAM报文包括所述第一网络设备的IPv6地址；
S1202，第二网络设备从所述OAM报文中读取所述第一网络设备的IPv6地址。
其中，第二网络设备可以是上述方法200中的网络设备2，第一网络设备是上述方法200中的网络设备1。该第二网络设备执行的操作具体可以参见网络设备2在方法200中执行的操作。其中，OAM报文可以是方法200中的OAM报文，第一网络设备的IPv6地址可以是方法200中网络设备1的IPv6地址。
作为一个示例，该OAM报文还可以包括所述第一网络设备到所述第二网络设备的路径标识。该路径标识可以为下述标识中的任意一种：标签交换路径LSP标识、段Section标识、伪线PW标识或环Ring标识。具体而言，该OAM报文中用于承载该路径标识的字段可以和用于承载第一网络设备的标识的字段相邻，这样，能够使得接收方基于路径标识和第一网络设备的标识准确的完成OAM检测。
需要说明的是，本申请实施例中的OAM报文具体为MPLS-TP OAM的IP模式对应的报文。
可见，通过本申请实施例提供的方法600，第二网络设备接收到的OAM报文中包括第一网络设备的IPv6地址，从而第二网络设备即可从该OAM报文中准确的读取第一网络设备的标识，如此，用户既可以执行IP模式下的MPLS-TP OAM，减少配置工作量，也可以完成IPv6网络场景的MPLS-TP OAM，提高了用户的使用体验。
此外，本申请实施例还提供了一种第一通信装置1300，参见图13所示。该第一通信装置1300包括处理单元1301和发送单元1302。其中，处理单元1301用于执行上述图3、图7所示实施例中网络设备1执行的处理操作、以及图9和图11所示实施例中第一网络设备执行的处理操作；发送单元1302用于执行上述图3、图7所示实施例中网络设备1执行的发送操作、以及图9和图11所示实施例中第一网络设备执行的发送操作。例如：处理单元1301可以执行图3中实施例中的操作：生成OAM报文。例如：发送单元1302可以执行图3中实施例中的操作：向网络设备2发送OAM报文。
此外，本申请实施例还提供了一种第二通信装置1400，参见图14所示。该第二通信装置1400包括接收单元1401和处理单元1402。其中，接收单元1401用于执行上述图3、图7所示实施例中网络设备2执行的接收操作、以及图10和图12所示实施例中第二网络设备执行的接收操作；处理单元1402用于执行上述图3、图7所示实施例中网络设备2执行的处理操作、以及图10和图12所示实施例中第二网络设备执行的处理操作。例如：接收单元1401可以执行图3中实施例中的操作：接收网络设备1发送的OAM报文；处理单元1402可以执行图3中实施例中的操作：根据指示信息，读取OAM报文中网络设备1的标识1。
此外，本申请实施例还提供了一种第一通信装置1500，参见图15所示。该第一通信装置1500包括第一通信接口1501、第二通信接口1502和处理器1503。其中，第一通信接口1501用于执行前述用于执行上述图3和7所示实施例中网络设备1、图9和11所示实施例中第一网络设备执行的接收操作；第二通信接口1502用于执行前述图3和7所示实施例中网络设备1、图9和11所示实施例中第一网络设备执行的发送操作；处理器1503用于执行上述图3和7所示实施例中网络设备1、图9和11所示实施例中第一网络设备执行的除了接收操作和发送操作之外的其他操作。例如：处理器1503可以执行图3中实施例中的操作：生成OAM报文。
此外，本申请实施例还提供了一种第二通信装置1600，参见图16所示。该第二通信装置1600包括第一通信接口1601、第二通信接口1602和处理器1603。其中，第一通信接口1601用于执行前述图3和7所示实施例中网络设备2、图10和12所示实施例中第二网络设备执行的接收操作；第二通信接口1602用于执行前述图3和7所示实施例中网络设备2、图10和12所示实施例中第二网络设备执行的发送操作。处理器1603用于执行上述图3和7所示实施例中网络设备2、图10和12所示实施例中第二网络设备执行的除了接收操作和发送操作以外的其他操作。例如：处理器1603可以执行图3中实施例中的操作：根据指示信息，读取OAM报文中网络设备1的标识1。
此外，本申请实施例还提供了一种第一通信装置1700，参见图17所示。该第一通信装置1700包括存储器1701和与存储器1701通信的处理器1702。其中，存储器1701包括计算机可读指令；处理器1702用于执行所述计算机可读指令，使得该第一通信装置1700执行以上图3、图7所示实施例中网络设备1侧执行的方法，以及图9和图11所示实施例中第一网络设备执行的方法。
此外，本申请实施例还提供了一种第二通信装置1800，参见图18所示。该第二通信装置1800包括存储器1801和与存储器1801通信的处理器1802。其中，存储器1801包括计算机可读指令；处理器1802用于执行所述计算机可读指令，使得该第二通信装置1800执行以上图3、图7所示实施例中网络设备2侧执行的方法，以及图10和图12所示实施例中第二网络设备执行的方法。
可以理解的是，上述实施例中，处理器可以是中央处理器(英文：central processing unit，缩写：CPU)，网络处理器(英文：network processor，缩写：NP)或者CPU和NP的组合。处理器还可以是专用集成电路(英文：application-specific integrated circuit，缩写：ASIC)，可编程逻辑器件(英文：programmable logic device，缩写：PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，缩写：CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，缩写：FPGA)，通用阵列逻辑(英文：generic array logic,缩写：GAL)或其任意组合。处理器可以是指一个处理器，也可以包括多个处理器。存储器可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬 盘(英文：solid-state drive，缩写：SSD)；存储器还可以包括上述种类的存储器的组合。存储器可以是指一个存储器，也可以包括多个存储器。在一个具体实施方式中，存储器中存储有计算机可读指令，所述计算机可读指令包括多个软件模块，例如发送模块，处理模块和接收模块。处理器执行各个软件模块后可以按照各个软件模块的指示进行相应的操作。在本实施例中，一个软件模块所执行的操作实际上是指处理器根据所述软件模块的指示而执行的操作。处理器执行存储器中的计算机可读指令后，可以按照所述计算机可读指令的指示，执行OAM检测中的各网络节点可以执行的全部操作。
可以理解的是，上述实施例中，第一通信装置1500的第二通信装置1502，具体可以被用作第一通信装置1300中的发送单元1302，实现第一网络设备到第二网络设备之间的数据通信；第一通信装置1500的第一通信接口1501，具体可以被用作第一通信装置1300中的接收单元，例如可以用于接收由上游网络设备发送的其他OAM报文。同理，第二通信装置1600的第一通信接口1601，具体可以被用作第二通信装置1400中的接收单元1401，实现第一网络设备到第二网络设备的数据通信；第二通信装置1600的第二通信接口1602，具体可以被用作第二通信装置1400中的发送单元，实现第二网络设备到下游网络设备的数据通信。
此外，本申请实施例还提供了一种通信系统1900，参见图19所示。该通信系统1900包括第一通信装置1901以及第二通信装置1902，其中，第一通信装置1901具体可以是上述第一通信装置1300、第一通信装置1500或第一通信装置1700，第二通信装置1902具体可以是上述第二通信装置1400、第二通信装置1600或第二通信装置1800。
需要说明的是，上述实施例中的各个通信装置，可以是用于执行上述方法的网络设备，也可以是指用于执行上述方法的单板、线卡、芯片等。
此外，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得所述计算机执行以上图3、图7、图9-图12所示实施例中的所述OAM报文处理方法。
此外，本申请实施例还提供了计算机程序产品，包括计算机程序或计算机可读指令，当所述计算机程序或所述计算机可读指令在计算机上运行时，使得计算机执行前述图3、图7、图9-图12所示实施例中的所述OAM报文处理方法。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到上述实施例方法中的全部或部分步骤可借助软件加通用硬件平台的方式来实现。基于这样的理解，本申请的技术方案可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如只读存储器(英文：read-only memory，ROM)/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者诸如路由器等网络通信设备)执行本申请各个实施例或者实施例的某些部分所述的方法。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例和设备实施例而言，由于其基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。以上所描述的设备及系统实施例仅仅是示意性的，其中作 为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
以上所述仅是本申请的优选实施方式，并非用于限定本申请的保护范围。应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请的前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本申请的保护范围。

Claims (48)

  1. 一种基于多协议标签交换传输协议MPLS-TP的操作管理维护OAM报文的处理方法，其特征在于，所述方法包括：
    第一网络设备生成OAM报文，所述OAM报文包括指示信息和所述第一网络设备的标识，所述指示信息用于指示所述第一网络设备的标识的类型；
    所述第一网络设备向第二网络设备发送所述OAM报文。
  2. 根据权利要求1所述的方法，其特征在于，所述指示信息用于指示所述第一网络设备的标识的类型为第六版互联网协议IPv6地址。
  3. 根据权利要求1所述的方法，其特征在于，所述指示信息用于所述第一网络设备的标识的类型为第四版互联网协议IPv4地址。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述OAM报文中包括用于指示维护实体组MEG类型的类型Type字段，所述Type字段用于承载所述指示信息。
  5. 根据权利要求4所述的方法，其特征在于，所述Type字段的取值为第一值，所述指示信息用于指示所述第一网络设备的标识的类型为IPv6地址，所述Type字段的取值为第二值，所述指示信息用于指示所述第一网络设备的标识的类型为IPv4地址。
  6. 根据权利要求1-3任一项所述的方法，其特征在于，所述OAM报文中包括预留Reserved字段，所述Reserved字段用于承载所述指示信息。
  7. 根据权利要求6所述的方法，其特征在于，所述Reserved字段中至少一个比特位为第一值时，所述指示信息用于指示所述第一网络设备的标识的类型为IPv6地址，所述至少一个比特位为第二值时，所述指示信息用于指示所述第一网络设备的标识的类型为IPv4地址。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述OAM报文还包括所述第一网络设备到所述第二网络设备的路径标识。
  9. 根据权利要求8所述的方法，其特征在于，所述OAM报文中用于承载所述路径标识的字段和用于承载所述第一网络设备的标识的字段相邻。
  10. 根据权利要求8或9所述的方法，其特征在于，所述路径标识为下述标识中的任意一种：标签交换路径LSP标识、段Section标识、伪线PW标识或环Ring标识。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述OAM报文为MPLS-TP OAM的IP模式对应的报文。
  12. 一种基于多协议标签交换传输协议MPLS-TP的操作管理维护OAM报文的处理方法，其特征在于，所述方法包括：
    第二网络设备接收第一网络设备发送的OAM报文，所述OAM报文包括指示信息和所述第一网络设备的标识，所述指示信息用于指示所述第一网络设备的标识的类型；
    所述第二网络设备根据所述指示信息，读取所述OAM报文中所述第一网络设备的标识。
  13. 根据权利要求12所述的方法，其特征在于，所述指示信息用于指示所述第一网络设备的标识的类型为第六版互联网协议IPv6地址，所述第二网络设备根据所述指示信息， 读取所述OAM报文中所述第一网络设备的标识，包括：
    所述第二网络设备从所述OAM报文中读取所述第一网络设备的IPv6地址。
  14. 根据权利要求12所述的方法，其特征在于，所述指示信息用于指示所述第一网络设备的标识的类型为第四版互联网协议IPv4地址，所述第二网络设备根据所述指示信息，读取所述OAM报文中所述第一网络设备的标识，包括：
    所述第二网络设备从所述OAM报文中读取所述第一网络设备的IPv4地址。
  15. 根据权利要求12-14任一项所述的方法，其特征在于，所述OAM报文中包括用于指示维护实体组MEG类型的类型Type字段，所述Type字段用于承载所述指示信息。
  16. 根据权利要求15所述的方法，其特征在于，所述Type字段的取值为第一值，所述指示信息用于指示所述第一网络设备的标识的类型为IPv6地址，所述Type字段的取值为第二值，所述指示信息用于指示所述第一网络设备的标识的类型为IPv4地址。
  17. 根据权利要求12-14任一项所述的方法，其特征在于，所述OAM报文中包括预留Reserved字段，所述Reserved字段中的比特位用于承载所述指示信息。
  18. 根据权利要求17所述的方法，其特征在于，所述Reserved字段中至少一个比特位为第一值时，所述指示信息用于指示所述第一网络设备的标识的类型为IPv6地址，所述至少一个比特位为第二值时，所述指示信息用于指示所述第一网络设备的标识的类型为IPv4地址。
  19. 根据权利要求12-18任一项所述的方法，其特征在于，所述OAM报文还包括所述第一网络设备到所述第二网络设备的路径标识。
  20. 根据权利要求19所述的方法，其特征在于，所述OAM报文中用于承载所述路径标识的字段和用于承载所述第一网络设备的标识的字段相邻。
  21. 根据权利要求19或20所述的方法，其特征在于，所述路径标识为下述标识中的任意一种：标签交换路径LSP标识、段Section标识、伪线PW标识或环Ring标识。
  22. 根据权利要求12-21任一项所述的方法，其特征在于，所述OAM报文为MPLS-TP OAM的IP模式对应的报文。
  23. 一种第一网络设备，其特征在于，包括：
    处理单元，用于生成OAM报文，所述OAM报文包括指示信息和所述第一网络设备的标识，所述指示信息用于指示所述第一网络设备的标识的类型；
    收发单元，用于向第二网络设备发送所述OAM报文。
  24. 根据权利要求23所述的第一网络设备，其特征在于，所述指示信息用于指示所述第一网络设备的标识的类型为第六版互联网协议IPv6地址。
  25. 根据权利要求23所述的第一网络设备，其特征在于，所述指示信息用于所述第一网络设备的标识的类型为第四版互联网协议IPv4地址。
  26. 根据权利要求23-25任一项所述的第一网络设备，其特征在于，所述OAM报文中包括用于指示维护实体组MEG类型的类型Type字段，所述Type字段用于承载所述指示信息。
  27. 根据权利要求26所述的第一网络设备，其特征在于，所述Type字段的取值为第一 值，所述指示信息用于指示所述第一网络设备的标识的类型为IPv6地址，所述Type字段的取值为第二值，所述指示信息用于指示所述第一网络设备的标识的类型为IPv4地址。
  28. 根据权利要求23-25任一项所述的第一网络设备，其特征在于，所述OAM报文中包括预留Reserved字段，所述Reserved字段用于承载所述指示信息。
  29. 根据权利要求28所述的第一网络设备，其特征在于，所述Reserved字段中至少一个比特位为第一值时，所述指示信息用于指示所述第一网络设备的标识的类型为IPv6地址，所述至少一个比特位为第二值时，所述指示信息用于指示所述第一网络设备的标识的类型为IPv4地址。
  30. 根据权利要求23-29任一项所述的第一网络设备，其特征在于，所述OAM报文还包括所述第一网络设备到所述第二网络设备的路径标识。
  31. 根据权利要求30所述的第一网络设备，其特征在于，所述OAM报文中用于承载所述路径标识的字段和用于承载所述第一网络设备的标识的字段相邻。
  32. 根据权利要求30或31所述的第一网络设备，其特征在于，所述路径标识为下述标识中的任意一种：标签交换路径LSP标识、段Section标识、伪线PW标识或环Ring标识。
  33. 根据权利要求23-32任一项所述的第一网络设备，其特征在于，所述OAM报文为MPLS-TP OAM的IP模式对应的报文。
  34. 一种第二网络设备，其特征在于，包括：
    收发单元，用于接收第一网络设备发送的OAM报文，所述OAM报文包括指示信息和所述第一网络设备的标识，所述指示信息用于指示所述第一网络设备的标识的类型；
    处理单元，用于根据所述指示信息，读取所述OAM报文中所述第一网络设备的标识。
  35. 根据权利要求34所述的第二网络设备，其特征在于，所述指示信息用于指示所述第一网络设备的标识的类型为第六版互联网协议IPv6地址，所述处理单元，具体用于：
    从所述OAM报文中读取所述第一网络设备的IPv6地址。
  36. 根据权利要求34所述的第二网络设备，其特征在于，所述指示信息用于指示所述第一网络设备的标识的类型为第四版互联网协议IPv4地址，所述处理单元，具体用于：
    从所述OAM报文中读取所述第一网络设备的IPv4地址。
  37. 根据权利要求34-36任一项所述的第二网络设备，其特征在于，所述OAM报文中包括用于指示维护实体组MEG类型的类型Type字段，所述Type字段用于承载所述指示信息。
  38. 根据权利要求37所述的第二网络设备，其特征在于，所述Type字段的取值为第一值，所述指示信息用于指示所述第一网络设备的标识的类型为IPv6地址，所述Type字段的取值为第二值，所述指示信息用于指示所述第一网络设备的标识的类型为IPv4地址。
  39. 根据权利要求34-36任一项所述的第二网络设备，其特征在于，所述OAM报文中包括预留Reserved字段，所述Reserved字段中的比特位用于承载所述指示信息。
  40. 根据权利要求39所述的第二网络设备，其特征在于，所述Reserved字段中至少一个比特位为第一值时，所述指示信息用于指示所述第一网络设备的标识的类型为IPv6地址，所述至少一个比特位为第二值时，所述指示信息用于指示所述第一网络设备的标识的类型 为IPv4地址。
  41. 根据权利要求34-40任一项所述的第二网络设备，其特征在于，所述OAM报文还包括所述第一网络设备到所述第二网络设备的路径标识。
  42. 根据权利要求41所述的第二网络设备，其特征在于，所述OAM报文中用于承载所述路径标识的字段和用于承载所述第一网络设备的标识的字段相邻。
  43. 根据权利要求41或42所述的第二网络设备，其特征在于，所述路径标识为下述标识中的任意一种：标签交换路径LSP标识、段Section标识、伪线PW标识或环Ring标识。
  44. 根据权利要求34-43任一项所述的第二网络设备，其特征在于，所述OAM报文为MPLS-TP OAM的IP模式对应的报文。
  45. 一种通信装置，其特征在于，包括：
    存储器，该存储器包括计算机可读指令；
    与该存储器通信的处理器，所述处理器用于执行所述计算机可读指令，使得所述通信装置用于执行权利要求1-11任一项所述的方法。
  46. 一种通信装置，其特征在于，包括：
    存储器，该存储器包括计算机可读指令；
    与该存储器通信的处理器，所述处理器用于执行所述计算机可读指令，使得所述通信装置用于执行权利要求12-22任一项所述的方法。
  47. 一种计算机可读存储介质，其特征在于，包括计算机可读指令，其特征在于，当所述计算机可读指令在计算机上运行时，使得所述计算机实施权利要求1-22任一项所述的方法。
  48. 一种通信系统，其特征在于，包括权利要求45所述的通信装置和权利要求46所述的通信装置；
    或者，包括权利要求23-33任一项所述的第一网络设备和权利要求34-44任一项所述的第二网络设备。
PCT/CN2021/113974 2020-09-03 2021-08-23 一种操作管理维护oam报文处理方法及设备 WO2022048466A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2023514707A JP2023539689A (ja) 2020-09-03 2021-08-23 運用、管理、及び保守ｏａｍパケット処理方法及びデバイス
EP21863533.2A EP4199447A4 (en) 2020-09-03 2021-08-23 OPERATIONS MANAGEMENT AND MAINTENANCE (OAM) PACKET PROCESSING METHOD AND APPARATUS
US18/176,718 US20230208756A1 (en) 2020-09-03 2023-03-01 Operation, Administration, and Maintenance OAM Packet Processing Method and Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010917057.3 2020-09-03
CN202010917057.3A CN114221867A (zh) 2020-09-03 2020-09-03 一种操作管理维护oam报文处理方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/176,718 Continuation US20230208756A1 (en) 2020-09-03 2023-03-01 Operation, Administration, and Maintenance OAM Packet Processing Method and Device

Publications (1)

Publication Number Publication Date
WO2022048466A1 true WO2022048466A1 (zh) 2022-03-10

Family

ID=80491587

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/113974 WO2022048466A1 (zh) 2020-09-03 2021-08-23 一种操作管理维护oam报文处理方法及设备

Country Status (5)

Country Link
US (1) US20230208756A1 (zh)
EP (1) EP4199447A4 (zh)
JP (1) JP2023539689A (zh)
CN (1) CN114221867A (zh)
WO (1) WO2022048466A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115242736B (zh) * 2022-07-15 2024-04-12 云合智网(上海)技术有限公司 轻载荷报文的传输方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130259056A1 (en) * 2012-03-27 2013-10-03 Juniper Networks, Inc. Oam label switched path for fast reroute of protected label switched paths
CN103580894A (zh) * 2012-07-31 2014-02-12 华为技术有限公司 操作、管理和维护oam配置的方法、设备及系统
CN104380673A (zh) * 2012-04-04 2015-02-25 阿尔卡特朗讯公司 用于在IPv6网络中使用标签分发协议(LDP)实例的系统和方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8259590B2 (en) * 2007-12-21 2012-09-04 Ciena Corporation Systems and methods for scalable and rapid Ethernet fault detection

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130259056A1 (en) * 2012-03-27 2013-10-03 Juniper Networks, Inc. Oam label switched path for fast reroute of protected label switched paths
CN104380673A (zh) * 2012-04-04 2015-02-25 阿尔卡特朗讯公司 用于在IPv6网络中使用标签分发协议(LDP)实例的系统和方法
CN103580894A (zh) * 2012-07-31 2014-02-12 华为技术有限公司 操作、管理和维护oam配置的方法、设备及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
7 January 2015 (2015-01-07), W. GEORGE, ED. TIME WARNER CABLE C. PIGNATARO, ED. CISCO: "Gap Analysis for Operating IPv6-Only MPLS Networks; rfc7439.txt", XP015104527, Database accession no. 7439 *
SAM ALDRIN HUAWEI TECHNOLOGIES M.VENKATESAN DELL INC. KANNAN KV SAMPATH REDEEM SOFTWARE THOMAS D. NADEAU BROCADE: "BFD Management Information Base (MIB) extensions for MPLS and MPLS-TP Networks; draft-ietf-bfd-mpls-mib-05.txt", BFD MANAGEMENT INFORMATION BASE (MIB) EXTENSIONS FOR MPLS AND MPLS-TP NETWORKS; DRAFT-IETF-BFD-MPLS-MIB-05.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, 29 December 2014 (2014-12-29), Internet Society (ISOC) 4, rue des Falaises CH- 1205 Geneva, Switzerland , pages 1 - 23, XP015103743 *
See also references of EP4199447A4

Also Published As

Publication number Publication date
US20230208756A1 (en) 2023-06-29
CN114221867A (zh) 2022-03-22
EP4199447A1 (en) 2023-06-21
EP4199447A4 (en) 2024-01-17
JP2023539689A (ja) 2023-09-15

Similar Documents

Publication Publication Date Title
WO2020233192A1 (zh) 一种为业务流提供业务服务的方法和装置
US11870690B2 (en) Packet processing method and apparatus, device, and storage medium
WO2018210213A1 (zh) 一种实现ioam封装的方法及装置、存储介质
WO2011079702A1 (zh) 丢包检测方法和装置及路由器
WO2017036180A1 (zh) 报文的处理方法及装置
US9774494B2 (en) Method, node, and system for detecting performance of layer 3 virtual private network
WO2015149523A1 (zh) 一种oam报文快速发送和检测处理的方法、装置及存储介质
US20150036510A1 (en) Method and device for measuring ethernet performance
CN103580894A (zh) 操作、管理和维护oam配置的方法、设备及系统
WO2021073377A1 (zh) 一种组播流检测方法、设备及系统
WO2022048466A1 (zh) 一种操作管理维护oam报文处理方法及设备
WO2022028216A1 (zh) 网络层可达信息传输方法、系统、装置以及网络设备
WO2022160665A1 (zh) 一种报文转发的方法、报文处理方法及设备
WO2019157802A1 (zh) 测量网络性能的方法、设备和网络系统
US20230318970A1 (en) Packet Processing Method and Apparatus
JP7334392B2 (ja) ビットエラーを通知する方法および関連するデバイス
CN104954259A (zh) 一种实现ptn业务收敛的方法及pe
EP4250646A1 (en) Bit error information acquisition method and device
JPWO2022048466A5 (zh)
WO2023284547A1 (zh) 一种故障检测的方法、装置和系统
WO2024011982A1 (zh) 报文转发方法、系统、网络设备、存储介质及程序产品
CN114143142B (zh) 一种报文传输方法及装置
WO2022057779A1 (zh) 一种实现业务路径检测的方法、设备和系统
WO2022161061A1 (zh) 一种故障检测方法、网络设备及系统
WO2022222544A1 (zh) 一种操作维护管理oam检测方法及装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2023514707

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021863533

Country of ref document: EP

Effective date: 20230313

NENP Non-entry into the national phase

Ref country code: DE