Nothing Special   »   [go: up one dir, main page]

WO2021093465A1 - 发送报文、接收报文以进行oam的方法、装置及系统 - Google Patents

发送报文、接收报文以进行oam的方法、装置及系统 Download PDF

Info

Publication number
WO2021093465A1
WO2021093465A1 PCT/CN2020/117246 CN2020117246W WO2021093465A1 WO 2021093465 A1 WO2021093465 A1 WO 2021093465A1 CN 2020117246 W CN2020117246 W CN 2020117246W WO 2021093465 A1 WO2021093465 A1 WO 2021093465A1
Authority
WO
WIPO (PCT)
Prior art keywords
oam
path
message
information
head node
Prior art date
Application number
PCT/CN2020/117246
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 EP20888188.8A priority Critical patent/EP4044514A4/en
Publication of WO2021093465A1 publication Critical patent/WO2021093465A1/zh
Priority to US17/743,915 priority patent/US20220278904A1/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/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • 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/0894—Policy-based network configuration management
    • 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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication

Definitions

  • This application relates to the field of communications, and in particular to a method, device and system for sending and receiving messages for OAM.
  • OAM operation and maintenance management
  • OAM can complete fault detection, path discovery, fault location and performance monitoring, so as to realize network analysis and prediction , Planning and configuration, and can test and fault management of the service flow transmitted in the network.
  • OAM can be performed on the service flow.
  • the process of performing OAM on the service flow can be: configuring the identification information of the service flow on the head node of the forwarding path (such as a switch or a router), and the forwarding path is used to transmit the service flow in the network.
  • the path of the service flow the identification information may be the five-tuple information of the service flow (including the source address, destination address, source port number, destination port number, and protocol type of the service flow).
  • the head node When receiving the service flow corresponding to the identification information, the head node performs OAM on the service flow.
  • the present application provides a method, device, and system for sending and receiving messages, so as to reduce the difficulty of performing OAM on a path and improve the efficiency of performing OAM on a path.
  • the technical solution is as follows:
  • the present application provides a method for sending a message.
  • the controller generates a policy configuration message.
  • the policy configuration message includes operation, maintenance and management OAM configuration information and first path information.
  • the path information is used to identify the first path.
  • the controller sends the policy configuration message to the head node of the first path, so that the policy configuration message is used to instruct the head node to perform OAM on the first path according to the OAM configuration information.
  • OAM OAM
  • the policy configuration message is a segment routing policy SR Policy configuration message
  • the SR Policy configuration message includes information about candidate paths
  • the candidate path includes a list of segments
  • the first path is the candidate path or The path identified by this segment list.
  • the SR Policy configuration message when the first path is the candidate path, the SR Policy configuration message further includes identification information, and the identification information is used to indicate the head node.
  • the candidate path is the active path At this time, perform OAM on the candidate path according to the OAM configuration information.
  • the identification information can be used to instruct the head node to perform OAM on the active path.
  • the controller receives an OAM data message, and the OAM data message is obtained by performing OAM on the first path. In this way, the controller can perceive changes in the performance of the first path according to the OAM data message.
  • the policy configuration message is a border gateway routing BGP message or a path calculation communication protocol PCEP message.
  • the OAM configuration information includes at least one of OAM mode, OAM object, OAM granularity, or OAM frequency.
  • the OAM method includes at least one of the following methods: in-band operation and maintenance management IOAM method, Internet protocol flow performance measurement IPFPM method, in-band flow information measurement IFIT method, two-way active measurement protocol TWAMP method, one-way active measurement protocol OWAMP method and PING method.
  • the present application provides a method for receiving a message, in the method: the head node receives a policy configuration message, the policy configuration message includes operation maintenance management OAM configuration information and first path information, first The path information is used to identify the first path.
  • the head node performs OAM on the first path according to the OAM configuration information. In this way, when performing OAM on the first path, it is not necessary to determine all the service flows transmitted on the first path, and configure the identification information of each service flow in the head node, thereby reducing the difficulty of performing OAM on the first path and improving The efficiency of OAM on the first path.
  • the policy configuration message is a segment routing policy SR Policy configuration message
  • the SR Policy configuration message includes candidate path information
  • the candidate path includes a segment list
  • the first path is the candidate path or The path identified by this segment list.
  • the head node obtains OAM execution information according to the OAM configuration information; receives a first message; adds the OAM execution information to the first message to generate a second message; The path sends the second message. In this way, OAM is performed on the first path.
  • the head node generates a first message according to the OAM configuration information, and the first message includes OAM execution information.
  • the head node sends the first message through the first path. In this way, OAM is actively performed on the first path.
  • the head node when the first path is a candidate path, the head node obtains identification information; the identification information is used to indicate the head node, and when the candidate path is an active path, according to the OAM configuration information Perform OAM on the candidate path. In this way, the identification information can be used to instruct the head node to perform OAM on the active path.
  • the head node obtains the OAM data message by performing OAM on the first path; the head node sends the OAM data message to the controller.
  • the controller receives the OAM data message, and can perceive the change in the performance of the first path according to the OAM data message.
  • the policy configuration message is a border gateway routing BGP message or a path calculation communication protocol PCEP message.
  • the present application provides a message sending device, which is used to execute the first aspect or the method in any one of the possible implementation manners of the first aspect.
  • the device includes a unit for executing the method of the first aspect or any one of the possible implementation manners of the first aspect.
  • this application provides a device for receiving a message, which is used to execute the second aspect or the method in any one of the possible implementation manners of the second aspect.
  • the device includes a unit for executing the second aspect or any one of the possible implementation manners of the second aspect.
  • the present application provides a device for sending a message.
  • the device includes a processor, a memory, and a transceiver.
  • the processor, the memory and the transceiver may be connected through a bus system.
  • the memory is configured to store one or more programs
  • the processor is configured to execute one or more programs in the memory to implement the first aspect or the method in any possible implementation manner of the first aspect.
  • the present application provides a device for receiving a message, the device including: a processor, a memory, and a transceiver.
  • the processor, the memory and the transceiver may be connected through a bus system.
  • the memory is configured to store one or more programs
  • the processor is configured to execute one or more programs in the memory to implement the second aspect or the method in any possible implementation manner of the second aspect.
  • the present application provides a computer-readable storage medium with program code stored in the computer-readable storage medium, which when run on a computer, causes the computer to execute the first, second, and first aspects above Any possible implementation manner of or a method in any possible implementation manner of the second aspect.
  • this application provides a computer program product containing program code, which when run on a computer, enables the computer to execute the first aspect, the second aspect, any possible implementation manner of the first aspect, or the second aspect Any of the possible implementations of the method.
  • the present application provides a system for receiving messages, including the device described in the third aspect and the device described in the fourth aspect; or, the device described in the fifth aspect and the device described in the sixth aspect Device.
  • FIG. 1 is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of a segment routing policy (segment routing Policy, SR Policy) provided by an embodiment of the present application;
  • FIG. 3 is a flowchart of a method for sending a message for OAM according to an embodiment of the present application
  • FIG. 4 is a schematic structural diagram of an SR Policy configuration message provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of another SR Policy configuration message provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of another SR Policy configuration message provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of another SR Policy configuration message provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another SR Policy configuration message provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another SR Policy configuration message provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of another SR Policy configuration message provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of another SR Policy configuration message provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a TLV field structure provided by an embodiment of the present application.
  • FIG. 13 is a schematic diagram of another TLV field structure provided by an embodiment of the present application.
  • FIG. 14 is a schematic diagram of another TLV field structure provided by an embodiment of the present application.
  • FIG. 15 is a flowchart of a method for receiving a message to perform OAM according to an embodiment of the present application
  • FIG. 16 is a schematic structural diagram of an apparatus for sending a message for OAM according to an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of an apparatus for receiving a message to perform OAM according to an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of another apparatus for sending a message for OAM according to an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of another apparatus for receiving a message for OAM according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of a system structure for receiving a message for OAM according to an embodiment of the present application.
  • OAM Operation and maintenance management.
  • OAM on a communication network refers to the collection of OAM information by nodes in the communication network.
  • the definition of OAM is as follows:
  • Performance monitoring and generating maintenance information so as to evaluate the stability of the network based on the maintenance information
  • the OAM of a communication network can include fault detection, path discovery, fault location, and performance monitoring.
  • Nodes in the OAM domain in the communication network can perform OAM.
  • the OAM domain refers to the collection of all nodes that support the OAM function in the communication network.
  • An OAM domain usually has an entry node and an exit node.
  • the entry node can be called the head node, and the exit node can be called the tail node.
  • There is at least one path between the head node and the tail node, and the nodes that each path passes through can support the OAM function.
  • node A, node B, node C, and node D in the network architecture constitute an OAM domain.
  • the network architecture also includes a controller, which is connected to node A, and the controller can also be connected to node B, node C, and node D.
  • node A is the head node of the OAM domain
  • head node A is responsible for determining OAM configuration information
  • node C is the tail node of the OAM domain
  • head node A or tail node C can be based on the OAM information collected by each node in the OAM domain Obtain the OAM result, and report the OAM result to the controller.
  • there are two paths between the head node A and the tail node C there are two paths between the head node A and the tail node C.
  • One path is composed of nodes A, B, and C
  • the other path is composed of nodes A, D, and C.
  • the nodes in the communication network may be network devices, such as routers or switches.
  • the controller can generate a policy configuration message.
  • the policy configuration message includes OAM configuration information and the first Path information, the first path information is used to identify the first path, the first path is the path between the head node and the tail node; the policy configuration message is sent to the head node.
  • the head node receives the policy configuration message, and performs OAM on the first path identified by the first path information according to the OAM configuration information.
  • the detailed implementation process of the controller generating the policy configuration message to send the policy configuration message to the head node may refer to the subsequent embodiment shown in FIG. 3.
  • the network architecture shown in FIG. 1 can be applied to the scenario of SR Policy or the scenario of segment routing traffic engineering (SR TE).
  • the SR Policy scenario or the SR TE scenario includes a head node, a tail node, and at least one path between the head node and the tail node. And usually the nodes that each path passes through can support the OAM function.
  • the policy configuration message is a segment routing policy (segment routing policy, SR Policy) configuration message, etc.
  • the SR Policy configuration message includes candidate path information, and the candidate path includes a segment list.
  • the path is the candidate path or the path identified by the segment list.
  • the controller sends an SR Policy configuration message to the head node when the head node and the tail node configure the SR Policy, and configures the SR Policy between the head node and the tail node through the SR Policy configuration message.
  • the SR Policy defines the head node, tail node, and performance requirement information.
  • the SR Policy also defines at least one candidate path between the head node and the tail node. Each candidate path includes at least one segment list, and each segment list is used to identify the path between the head node and the tail node. A path.
  • the performance requirement information includes a parameter threshold of at least one performance parameter.
  • the at least one performance parameter includes one or more of delay and packet loss rate.
  • the parameter threshold includes one or more of the delay threshold and the packet loss rate threshold.
  • the delay threshold is used to indicate that when the path defined by the SR Policy is used to transmit services, the SR Policy can try to ensure that the delay generated by the path does not exceed the delay threshold.
  • the packet loss rate threshold is used to indicate that when the path defined by the SR Policy is used to transmit services, the SR Policy can try to ensure that the packet loss rate generated by the path does not exceed the packet loss rate threshold.
  • Each of the at least one candidate path includes at least one segment list.
  • load sharing can be performed among the multiple segment lists.
  • the head node may also select one or more segment lists from the at least one segment list, and send the service through the path identified by the selected segment list.
  • the SR Policy also defines the basic attribute information of each candidate path.
  • the basic attribute information of the any candidate path includes information such as the priority (Preference) of the any candidate path.
  • the basic attribute information of any candidate path also includes identification information (Binding SID) of the SR Policy.
  • the SR Policy also defines the basic attribute information of each segment list.
  • the basic attribute information of any segment list includes the weight of any segment list.
  • the active path there is one active path in the at least one candidate path, and other candidate paths in the at least one candidate path are inactive paths.
  • the active path can be used to send services to the tail node.
  • an embodiment of the present application provides a method for sending a message.
  • the method can be applied to the network architecture shown in Fig. 1, including:
  • Step 101 The controller generates a policy configuration message, the policy configuration message including OAM configuration information and first path information, and the first path information is used to identify the first path.
  • the policy configuration message is an SR Policy configuration message
  • the SR Policy configuration message includes information about the target candidate path
  • the target candidate path includes a target segment list
  • the first path is the target candidate path or the target segment list identifier path.
  • the target candidate path is one or more candidate paths among at least one candidate path defined by the SR Policy.
  • the target segment list is one or more segment lists in at least one segment list included in the target candidate path.
  • the OAM configuration information is OAM configuration information of the first path.
  • the controller When configuring the SR Policy between the head node and the tail node, the controller sends an SR Policy configuration message to the head node.
  • the SR Policy configuration message includes the basic configuration information of the SR Policy and the OAM configuration information of the first path.
  • the basic configuration information includes information about at least one candidate path defined by the SR Policy, and performance requirement information defined by the SR Policy.
  • the information of any candidate path includes basic attribute information of the any candidate path, at least one segment list, and basic belonging information of each segment list.
  • the first path (target candidate path) is one or more candidate paths in the at least one candidate path
  • the first path (target segment list) is one or more segments in the target candidate path List.
  • the OAM configuration information may include OAM attributes.
  • the OAM attribute may include at least one of OAM mode, OAM object, OAM granularity, or OAM frequency.
  • the OAM object may include one or more performance parameters such as delay and packet loss rate.
  • the OAM mode includes in-band OAM mode or out-of-band OAM mode, etc.
  • In-band OAM mode includes in-band operation and maintenance management (In-situ OAM, IOAM) mode, in-band flow detection (in-situ flow information telemetry, INT) method, Alternate Marking method, abstract inband flow analyzer (abstract inband flow analyzer, IFA method), Internet protocol flow performance monitor (IPFPM) method or in-band flow information measurement ( in-situ flow information telemetry, IFIT) methods, etc.
  • Out-of-band OAM methods include two-way active measurement protocol (TWAMP) method, one-way active measurement protocol (OWAMP) method or PING method, simple two-way active measurement protocol (simple two -way active measurement protocol, STAMP) mode, or, TWAMP LIGHT mode, etc.
  • the first field of the SR Policy configuration message includes basic attribute information of the target candidate path
  • the second field of the SR Policy configuration message includes the first
  • the first field is adjacent to the second field or the second field is located in the first field.
  • the third field of the SR Policy configuration message includes the target segment list
  • the fourth field of the SR Policy configuration message includes the OAM configuration information of the first path
  • the third field is adjacent to the fourth field or the fourth field is located in the third field.
  • the SR Policy configuration message is a border gateway protocol (BGP) message, and the controller can generate at least one BGP message.
  • BGP border gateway protocol
  • Any BGP message can include information about a candidate path.
  • the BGP message shown in Figure 4 includes a first field and at least one third field located after the first field. Assuming that the first field includes basic attribute information of the target candidate path, any first field located after the first field Three fields. Any third field includes a segment list in the target candidate path and basic attribute information of the segment list.
  • the first field may also include information such as the name of the SR Policy.
  • the second field of the BGP message includes the OAM configuration information of the target candidate path, and the first field is adjacent to the second field or the second field is located in the first field.
  • the second field immediately follows the first field, and is used to indicate that the OAM configuration information in the second field is the OAM configuration information of the target candidate path.
  • the second field is located in the first field, and is used to indicate that the OAM configuration information in the second field is the OAM configuration information of the target candidate path.
  • the first field is a type length value (TLV) field.
  • TLV type length value
  • the second field is also a TLV field.
  • the second field is a sub-TLV field located in the first field.
  • the fourth field of the BGP message includes the OAM configuration information of the target segment list
  • the BGP message has a third
  • the fields include the target segment list and basic attribute information of the target segment list.
  • the third field is adjacent to the fourth field, or the fourth field is located in the third field.
  • the fourth field immediately follows the third field, and is used to indicate that the OAM configuration information in the fourth field is the OAM configuration information of the target segment list.
  • the fourth field is located in the third field, and is used to indicate that the OAM configuration information in the fourth field is the OAM configuration information of the target segment list.
  • the third field is a TLV field.
  • the third field includes multiple sub-TLV fields, the target segment list includes multiple tags (Segments), each tag may correspond to a sub-TLV field, and for any sub-TLV field corresponding to any tag, the sub-TLV field includes the tag.
  • the basic attribute information of the target segment list corresponds to at least one sub-TLV, and the at least one sub-TLV field includes the basic attribute information of the target segment list.
  • the fourth field is also a TLV field.
  • the fourth field is a sub-TLV field located in the third field.
  • the SR Policy configuration message is a path calculation communication protocol (path calculation element communication protocol, PCEP) message, and the controller can generate at least one PCEP message.
  • PCEP path calculation element communication protocol
  • Any PCEP message may include the basic attribute information of each candidate path defined by the SR Policy, the segment list included in a candidate path, and the basic attribute information of the target segment list.
  • the candidate path defined by the SR Policy includes a segment list.
  • the controller can use a PCEP packet to configure a candidate path on the head node. In this way, the controller needs at least one PCEP packet to configure each candidate path of the SR Policy between the head node and the tail node.
  • the target candidate path includes a target segment list
  • the PCEP message includes the first field corresponding to each candidate path
  • the target candidate path includes The third field corresponding to the target segment list.
  • the first field corresponding to any candidate path includes the basic attribute information of any candidate path.
  • the basic attribute information of any candidate path includes the identification and priority of any candidate path.
  • the first field corresponding to any candidate path further includes the identifier and name of the SR Policy.
  • the third field corresponding to the target segment list includes the target segment list and basic attribute information of the target segment list.
  • the first field corresponding to any candidate path includes four TLV fields, which are the first TLV, the second TLV, the third TLV, and the fourth TLV, respectively.
  • the first TLV includes the identifier of the SR Policy
  • the second TLV includes the name of the SR Policy
  • the third TLV includes the identifier of any candidate path
  • the fourth TLV includes the priority of any candidate path.
  • the third field is a TLV field, which includes the target segment list and basic attribute information of the target segment list.
  • the third field may also include multiple sub-TLV fields.
  • the target segment list includes multiple tags. Each tag may correspond to a sub-TLV field.
  • the sub-TLV field includes The label.
  • the basic attribute information of the target segment list corresponds to at least one sub-TLV, and the at least one sub-TLV field includes the basic attribute information of the target segment list.
  • the second field of the PCEP message includes the OAM configuration information of the target candidate path, and the target candidate path
  • the corresponding first field is adjacent to the second field or the second field is located in the first field corresponding to the target candidate path.
  • the second field immediately follows the first field corresponding to the target candidate path, and is used to indicate that the OAM configuration information in the second field is the OAM configuration information of the target candidate path.
  • the second field is located in the first field corresponding to the target candidate path, and is used to indicate that the OAM configuration information in the second field is the OAM configuration information of the target candidate path.
  • the fourth field of the PCEP message includes the OAM configuration information of the target segment list
  • the PCEP message has a third
  • the fields include the target segment list and basic attribute information of the target segment list.
  • the third field is adjacent to the fourth field, or the fourth field is located in the third field.
  • the fourth field immediately follows the third field, and is used to indicate that the OAM configuration information in the fourth field is the OAM configuration information of the target segment list.
  • the fourth field is located in the third field, and is used to indicate that the OAM configuration information in the fourth field is the OAM configuration information of the target segment list.
  • the fourth field when the third field is adjacent to the fourth field, the fourth field is also a TLV field. Or, in a case where the fourth field is located in the third field, the fourth field is a sub-TLV field located in the third field.
  • the second field including the OAM configuration information of the target candidate path or the fourth field including the OAM configuration information of the target segment list is a TLV field.
  • the TLV field includes three subfields: Type, Length, and Value.
  • Type subfield may be used to include the OAM mode
  • Value subfield may be used to include at least one of OAM object, OAM granularity, or OAM frequency.
  • the SR Policy configuration message further includes identification information, and the identification information is used to instruct the head node to perform OAM on the active path, or the identification information is used to indicate the head node Perform OAM on the inactive path and the active path.
  • a TLV field can be added to the SR Policy configuration message, and the TLV field includes OAM configuration information.
  • TLV fields are listed next. Refer to the first type of TLV field shown in FIG. 12, in the first type of TLV field, the value of the type (Type) indicates the OAM mode, and the OAM mode can be a two-way active measurement protocol (Simple Two-way Active Measurement Protocol, STAMP). ) Mode, that is, the value of Type indicates that the first type of TLV is the STAMP TLV field.
  • the first type of TLV field also includes the address and port number of the head node, the address and port number of the tail node, and the OAM frequency.
  • the first type of TLV field may not include the OAM object, and the head node includes the default OAM object.
  • Length represents the total length of the value field, excluding the length of the Type and Length fields.
  • the DSCP field indicates the DSCP value to be set in the test packet.
  • Interval includes OAM frequency, which represents the time interval between two consecutive transmissions of data packets.
  • the data packet is a data packet in a test session, and the unit is microseconds.
  • the sender UDP port (Sender UDP Port) includes the port number of the head node, which represents the sender UDP port number, ranging from 49152 to 65535.
  • the receiver UDP port (Reflector UDP Port) includes the port number of the tail node.
  • the default value is 862 (TWAMP test receiver port), and the range is 1024 to 65535.
  • the sender IP sender IP
  • the receiver IP Reflector IP
  • the receiver IP includes the address of the tail node.
  • the Length field is 18 bytes, the address of the tail node is an IPv4 address.
  • the address of the tail node is an IPv6 address.
  • Rsvd field reserved for further use.
  • the value of the type (Type) indicates the OAM mode, and the OAM mode can be IOAM pre-allocated (IOAM Pre-allocated), that is, the value of Type.
  • the value indicates that the second TLV is the IOAM Pre-allocated Trace Option Sub-TLV field.
  • the OAM method may also be IOAM Incremental Trace (IOAM Incremental Trace), that is, the value of Type indicates that the second TLV is the IOAM Incremental Trace Option Sub-TLV field.
  • Length represents the total length of the value field, excluding the Type and Length fields.
  • the Namespace ID represents the 16-bit identifier of the IOAM namespace.
  • the IOAM Trace Type includes at least one of an OAM object, OAM granularity, or OAM frequency, and can be a 24-bit identifier. Flags can be 4-bit fields. Reserved field (Rsvd) A 4-bit field that can be reserved for further use.
  • the value of Type indicates the OAM mode.
  • the OAM mode can be IOAM edge-to-edge or IOAM edge-to-end (IOAM edge-to-end).
  • -Edge that is, the value of Type indicates that the third TLV is the IOAM Edge-to-Edge Option Sub-TLV field.
  • the Length word indicates the total length of the value field, excluding the Type and Length fields.
  • the Namespace ID can represent the 16-bit identifier of the IOAM namespace.
  • IOAM E2E Type includes at least one of OAM object, OAM granularity, or OAM frequency, and is a 16-bit identifier.
  • Type field may be allocated by the Internet Assigned Numbers Authority (IANA, Internet Assigned Numbers Authority). See Table 1. Table 1 illustrates the meaning of different values of Type.
  • Step 102 The controller sends the policy configuration message to the head node, where the policy configuration message is used to instruct the head node to perform OAM on the first path according to the OAM configuration information.
  • the head node After receiving the policy configuration message, the head node performs OAM on the first path according to the OAM configuration information included in the policy configuration message.
  • OAM For the detailed implementation process of the OAM performed by the head node, refer to the subsequent embodiment shown in FIG. 15, which is not described here.
  • the head node obtains the OAM data message when performing OAM on the first path, and sends the OAM data message to the controller.
  • the controller receives the OAM data message.
  • the controller since the controller generates a policy configuration message, the policy configuration message includes OAM configuration information and first path information, and the first path information is used to identify the first path; it is sent to the head node of the first path A policy configuration message, so that the head node can perform OAM on the first path according to the OAM configuration information included in the policy configuration message.
  • the controller since the controller generates a policy configuration message, the policy configuration message includes OAM configuration information and first path information, and the first path information is used to identify the first path; it is sent to the head node of the first path A policy configuration message, so that the head node can perform OAM on the first path according to the OAM configuration information included in the policy configuration message.
  • the performance of the first path can be obtained by performing OAM on the first path, so that when the performance of the first path changes, it can be sensed in time.
  • the head node obtains the OAM data message when performing OAM on the first path, and sends the OAM data message to the controller, so that the controller can also perceive the performance change of the first path according to the OAM data message.
  • an embodiment of the present application provides a method for receiving a message for OAM.
  • the method is applied to the network architecture shown in FIG. 1, and includes:
  • Step 201 The head node receives a policy configuration message, where the policy configuration message includes OAM configuration information and first path information, and the first path information is used to identify the first path.
  • the policy configuration message may be generated by the controller, and the controller may generate the policy configuration message in the manner of the embodiment shown in FIG. 3 above.
  • the head node receives the policy configuration message sent by the controller.
  • the policy configuration message is an SR Policy message
  • the SR Policy configuration message includes the basic configuration information of the SR Policy and the OAM configuration information.
  • the basic configuration information includes information of at least one candidate path, and performance requirement information of the SR Policy.
  • the information of any candidate path includes basic attribute information of the any candidate path, at least one segment list, and basic belonging information of each segment list.
  • the first path is one or more candidate paths in the at least one candidate path.
  • the one or more candidate paths are referred to as target candidate paths.
  • the first path is one or more segment lists in the target candidate path.
  • the one or more segment lists are referred to as target segment lists.
  • the head node may also send a policy response message to the controller.
  • the policy response message includes OAM response information, and the OAM response information is used to indicate whether it is successful on the head node. Configure the OAM function.
  • the policy configuration message may include a TLV field corresponding to the target candidate path, and the TLV field may include an OAM response message corresponding to the target candidate path.
  • the policy configuration message may include a TLV field corresponding to the target segment list, and the TLV field may include an OAM response message corresponding to the target segment list.
  • Step 202 The head node performs OAM on the first path according to the OAM configuration information included in the policy configuration message.
  • the head node After the head node receives the SR Policy configuration message, it can save the basic configuration information of the SR Policy. Then, perform OAM on the first path according to the OAM configuration information.
  • the head node determines the first field in the SR Policy configuration message that includes the basic attribute information of the target candidate path, and determines the SR according to the first field
  • the second field in the Policy configuration message that includes the OAM configuration information of the target candidate path, and the OAM configuration information of the target candidate path is extracted from the second field.
  • the head node determines the second field adjacent to the first field, or determines the second field located in the first field.
  • the OAM configuration information on the target candidate path includes at least one of OAM mode, OAM object, OAM granularity, or OAM frequency.
  • the OAM configuration information of the target candidate path includes the OAM mode but does not include the OAM object. At this time, the head node obtains the default OAM object.
  • the OAM configuration information of the target candidate path includes the OAM object, but does not include the OAM mode, and the head node obtains the default OAM mode at this time.
  • the head node obtains OAM execution information according to the OAM configuration information; receives a first message; adds the OAM execution information to the first message to generate a second message Text; Send a second message to the tail node through the candidate path to implement OAM on the candidate path.
  • the head node and the tail node are network devices in the communication network, so the head node can receive the first message from other network devices or terminal devices.
  • the OAM execution information obtained by the head node may include the OAM object.
  • the head node After receiving the first message, the head node, when determining to use the target candidate path to transmit the first message, adds OAM execution information to the header of the first message to obtain the second message.
  • the target candidate path includes at least one segment list, and the head node selects one or more segment lists from the at least one segment list, and sends a second message to the tail node using the path identified by the selected segment list.
  • the basic configuration information of the SR Policy includes the weight of each segment list in the at least one segment list, and the head node can select one or more segment lists from each segment list according to the weight of each segment list.
  • the any node receives the second message, and collects the path identified by the segment list according to the OAM object in the second message to obtain OAM information , And add the collected OAM information to the second message, and then forward the second message to the tail node.
  • the tail node receives the second message, collects the path identified by the segment list according to the OAM object in the second message to obtain OAM information, and obtains the OAM information according to the OAM information collected by itself and the OAM information in the second message result.
  • the head node may store identification information, or the SR Policy configuration message also includes the identification information; the identification information is used to instruct the head node to perform OAM on the active path, or the identification information is used to instruct the head node to perform OAM on the active path.
  • the inactive path and the active path perform OAM.
  • the operation of the head node to generate the second message may be: the head node obtains the identification information, and when it is determined to use the target candidate path to transmit the first message, the identification information is judged, and the identification information is judged
  • the head node determines whether the target candidate path is an active path, and if it is an active path, it adds the OAM execution information to the first packet to generate a second packet, That is, OAM is performed on the target candidate path. If it is an inactive path, the head node directly sends the first message to the tail node.
  • the head node directly adds the OAM execution information to the first message to generate the second message, that is, directly to the target The candidate path performs OAM.
  • the head node may obtain the identification information in the received policy configuration message, that is, the identification information is included in the policy configuration message.
  • the identification information can be added to the policy configuration message by the controller.
  • the head node obtains the identification information, or the head node reads the identification information saved by itself, that is, the identification information is set in the head node.
  • the identification information can be manually configured by the network administrator at the head node.
  • the identification information may also be that after receiving the control message sent by the controller, the head node generates identification information according to the instruction of the control message and saves the identification information in the head node.
  • the tail node sends an OAM data message to the controller, and the OAM data message includes the OAM result.
  • the head node adds the delay and/or packet loss rate to the first message to generate a second message, and uses the path identified by the selected segment list Send the second message to the tail node.
  • the any node receives the second message, collects the delay and/or packet loss rate of the path identified by the segment list (that is, OAM information is collected), and The collected delay and/or packet loss rate are added to the second message, and then the second message is forwarded to the tail node.
  • the tail node receives the second message, collects the delay and/or packet loss rate of the path identified by the segment list, calculates the average delay according to the delay collected by itself and the delay in the second message, and/or according to The packet loss rate collected by itself and the packet loss rate in the second message calculate the average packet loss rate to obtain the OAM result, and the OAM result includes the delay average value and/or the average packet loss rate.
  • the head node when the OAM mode is the out-of-band OAM mode, the head node generates a first message according to the OAM configuration information, the first message includes OAM execution information; the first message is sent to the tail node through the candidate path Document to achieve OAM on the candidate path.
  • the OAM execution information obtained by the head node may include the OAM object.
  • the message header of the first message generated by the head node includes OAM execution information.
  • the candidate path includes at least one segment list, and the head node selects one or more segment lists from the at least one segment list, and sends the first message to the tail node using the path identified by the selected segment list.
  • the any node receives the first message, collects the path identified by the segment list according to the OAM object in the first message, and obtains The OAM information is added to the first message, and then the first message is forwarded to the tail node.
  • the tail node receives the first message, collects the path identified by the segment list according to the OAM object in the first message, adds the collected OAM information to the first message, and sends the message to the head node The first message, so that the head node receives the first message and obtains the OAM result according to the OAM information in the received first message.
  • the operation of the head node to generate the first message may be: the head node judges the identification information, and after the judgment is made The identification information is used to instruct the head node to perform OAM on the active path, the head node determines whether the target candidate path is an active path, and if it is an active path, it generates a first message, that is, performs OAM on the target candidate path. When it is determined that the identification information is used to instruct the head node to perform OAM on the inactive path and the active path, the head node directly generates the first message, that is, directly performs OAM on the target candidate path.
  • the head node sends an OAM data message to the controller, and the OAM data message includes the OAM result.
  • the header of the first message generated by the head node includes delay and/or packet loss rate, etc.
  • the path identified by the selected segment list is used Send the first message to the tail node.
  • the any node receives the first message, collects the delay and/or packet loss rate of the path identified by the segment list, and collects the obtained delay and/ Or the packet loss rate is added to the first message, and then the first message is forwarded to the tail node.
  • the tail node receives the first message, collects the delay and/or packet loss rate of the path identified by the segment list, and adds the collected delay and/or packet loss rate to the first message, and sends it to the head node Send the first message.
  • the head node receives the first message, calculates the average delay according to the delay in the first message received, and/or calculates the average packet loss rate according to the packet loss rate in the received first message, to obtain OAM
  • the OAM result includes the average value of the delay and/or the average value of the packet loss rate.
  • the OAM configuration information may include the OAM frequency, and in this step, OAM is performed on the target candidate path according to the OAM frequency. That is, the head node generates the first message according to the OAM frequency, and sends the first message to the tail node through the target candidate path.
  • the head node determines the third field in the SR Policy configuration message that includes the target segment list, and determines the third field in the SR Policy configuration message according to the third field.
  • the fourth field includes the OAM configuration information of the target segment list, and the OAM configuration information of the target segment list is extracted from the fourth field.
  • the head node determines the fourth field adjacent to the third field, or determines the fourth field located in the third field.
  • the OAM configuration information in the target segment list includes at least one of OAM mode, OAM object, OAM granularity, or OAM frequency.
  • the OAM configuration information of the target segment list includes the OAM mode, but does not include the OAM object. At this time, the head node obtains the default OAM object. Or, the OAM configuration information of the target segment list includes the OAM object, but does not include the OAM mode. At this time, the head node obtains the default OAM mode.
  • the head node obtains OAM execution information according to the OAM configuration information; receives a first message; adds the OAM execution information to the first message to generate a second message Text; Send a second message to the tail node through the path identified by the target segment list to implement OAM on the path identified by the segment list.
  • the OAM execution information obtained by the head node may include the OAM object.
  • the head node After receiving the first message, the head node, when determining to use the path identified by the target segment list to transmit the first message, adds OAM execution information to the header of the first message to obtain the second message.
  • the any node receives the second message, collects the path identified by the target segment list according to the OAM object in the second message, and collects the obtained
  • the OAM information is added to the second message, and then the second message is forwarded to the tail node.
  • the tail node receives the second message, collects the path identified by the target segment list according to the OAM object in the second message, and obtains the OAM result according to the OAM information collected by itself and the OAM information in the second message.
  • the tail node sends an OAM data message to the controller, and the OAM data message includes the OAM result.
  • the head node adds the delay and/or packet loss rate to the first message to generate the second message, and uses the path identified by the target segment list to end The node sends the second message. For any node that the path identified by the segment list passes through, the any node receives the second message, collects the path identified by the target segment list to obtain the delay and/or packet loss rate, and then collects the acquired delay And/or the packet loss rate is added to the second message, and then the second message is forwarded to the tail node.
  • the tail node receives the second message, collects the path identified by the target segment list to obtain the delay and/or packet loss rate, and calculates the average delay according to the delay collected by itself and the delay in the second message, and/ Or, calculate the average packet loss rate according to the packet loss rate collected by itself and the packet loss rate in the second message to obtain an OAM result, where the OAM result includes the delay average value and/or the average packet loss rate.
  • the head node when the OAM mode is the out-of-band OAM mode, the head node generates a first message according to the OAM configuration information.
  • the first message includes OAM execution information; and sends the first message to the tail node through the path identified by the target segment list.
  • the OAM execution information obtained by the head node may include the OAM object.
  • the message header of the first message generated by the head node includes OAM execution information.
  • the any node receives the first message, collects the path identified by the target segment list according to the OAM object in the first message, and collects the obtained
  • the OAM information is added to the first message, and then the first message is forwarded to the tail node.
  • the tail node receives the first message, collects the path identified by the target segment list according to the OAM object in the first message, and sends the first message to the head node, so that the head node receives the first message, Obtain the OAM result according to the OAM information in the received first message.
  • the head node sends an OAM data message to the controller, where the OAM data message includes the OAM result obtained by collecting the target segment list.
  • the header of the first message generated by the head node includes delay and/or packet loss rate, etc.
  • the path identified by the target segment list is used to the end.
  • the node sends the first message.
  • the any node receives the first message, collects the delay and/or packet loss rate of the path identified by the target segment list, and collects the obtained delay and/ Or the packet loss rate is added to the first message, and then the first message is forwarded to the tail node.
  • the tail node receives the first message, collects the delay and/or packet loss rate of the path identified by the target segment list, adds the collected delay and/or packet loss rate to the first message, and sends it to the head node Send the first message.
  • the head node receives the first message, calculates the average delay according to the delay in the first message received, and/or calculates the average packet loss rate according to the packet loss rate in the received first message, to obtain OAM result.
  • OAM is performed on the path identified by the target segment list according to the OAM frequency. That is, the head node generates the first message according to the OAM frequency, and sends the first message to the tail node through the path identified by the target segment list.
  • the OAM configuration information may include OAM granularity, and the OAM granularity is used to indicate the granularity of the tail node to send the OAM result.
  • OAM granularity can be sent according to service flow or sent according to message.
  • the so-called sending by service flow means that the tail node sends an OAM data message to the controller after receiving each second message in the service flow.
  • the OAM data message includes the OAM result, and the OAM result is based on the received Every second message is obtained.
  • the so-called sending by message means that when the tail node receives a second message in the service flow, it sends an OAM data message to the controller.
  • the OAM data message includes the OAM result, and the OAM result is based on the first message.
  • the second message is obtained.
  • the first path may be adjusted. For example, when the first path is the target candidate path, the priority of the target candidate path is adjusted; when the first path is the target segment list, the weight of the target segment list is adjusted.
  • the policy configuration message since the head node receives the policy configuration message, the policy configuration message includes OAM configuration information and first path information, and the first path information is used to identify the first path, so that the head node can configure according to the policy
  • the OAM configuration information included in the message performs OAM on the first path.
  • the performance of the first path can be obtained by performing OAM on the first path, so that when the performance of the first path changes, it can be sensed in time.
  • the head node obtains the OAM data message when performing OAM on the first path, and sends the OAM data message to the controller, so that the controller can also perceive the performance change of the first path according to the OAM data message.
  • the controller or the head node may adjust the first path when it perceives that the performance of the first path cannot meet the performance requirement information defined by the SR Policy. For example, when the first path is the target candidate path, the priority of the target candidate path is adjusted; when the first path is the target segment list, the weight of the target segment list is adjusted.
  • an embodiment of the present application provides an apparatus 300 for sending a message for OAM.
  • the apparatus 300 may be deployed on the controller in any of the foregoing embodiments, for example, it may be deployed as shown in FIG. 3.
  • the controller in the example includes:
  • the processing unit 301 is configured to generate a policy configuration message, the policy configuration message including OAM configuration information and first path information, and the first path information is used to identify the first path;
  • the sending unit 302 is configured to send the policy configuration message to the head node of the first path, where the policy configuration message is used to instruct the head node to perform OAM on the first path according to the OAM configuration information.
  • the processing unit 301 obtains the detailed implementation process of generating the policy configuration message, which may refer to the relevant content of the controller generating the policy configuration message in step 301 of the embodiment shown in FIG. 3.
  • the policy configuration message is an SR Policy configuration message.
  • the SR Policy configuration message includes information about a candidate path, the candidate path includes a segment list, and the first path is the candidate path or the path identified by the segment list.
  • SR Policy configuration message refers to the relevant content of the SR Policy configuration message in step 301 of the embodiment shown in FIG. 3.
  • the SR Policy configuration message further includes identification information, and the identification information is used to indicate the head node.
  • the candidate path is an active path, according to the OAM configuration information Perform OAM on the candidate path.
  • the device 300 further includes:
  • the receiving unit 303 is configured to receive an OAM data message, which is obtained by performing OAM on the first path.
  • the policy configuration message is a border gateway routing BGP message or a path calculation communication protocol PCEP message.
  • the OAM configuration information includes at least one of OAM mode, OAM object, OAM granularity, or OAM frequency.
  • the OAM method includes at least one of the following methods: in-band operation and maintenance management IOAM method, Internet protocol flow performance measurement IPFPM method, in-band flow information measurement IFIT method, two-way active measurement protocol TWAMP method, one-way active Measurement protocol OWAMP method and PING method.
  • the processing unit generates a policy configuration message, the policy configuration message includes OAM configuration information and first path information, and the first path information is used to identify the first path.
  • the sending unit sends the policy configuration message to the head node of the first path, so that the policy configuration message is used to instruct the head node to perform OAM on the first path according to the OAM configuration information.
  • an embodiment of the present application provides an apparatus 400 for receiving a message for OAM.
  • the apparatus 400 may be deployed on the head node in any of the foregoing embodiments, for example, it may be deployed as shown in FIG. 15.
  • the head node in the example includes:
  • the receiving unit 401 is configured to receive a policy configuration message, the policy configuration message including OAM configuration information and first path information, and the first path information is used to identify the first path;
  • the processing unit 402 is configured to perform OAM on the first path according to the OAM configuration information.
  • the policy configuration message is an SR Policy configuration message
  • the SR Policy configuration message includes information about a candidate path
  • the candidate path includes a segment list
  • the first path is the candidate path or a path identified by the segment list.
  • the device 400 further includes: a sending unit 403,
  • the processing unit 402 is configured to obtain OAM execution information according to the OAM configuration information
  • the receiving unit 401 is further configured to receive the first message
  • the processing unit 402 is further configured to add OAM execution information to the first message to generate a second message;
  • the sending unit 403 is configured to send the second packet through the first path.
  • the processing unit 402 obtaining OAM information and generating the second packet, refer to the head node in step 202 of the embodiment shown in FIG. 15 for obtaining OAM information and generating related content of the second packet.
  • the processing unit 402 is configured to generate a first message according to OAM configuration information, where the first message includes OAM execution information;
  • the sending unit 403 is configured to send the first message through the first path.
  • the processing unit 402 obtains a detailed implementation process of generating the first packet, and reference may be made to the relevant content of the first packet generated by the head node in step 202 of the embodiment shown in FIG. 15.
  • the processing unit 402 is configured to obtain identification information, and the identification information is used to instruct the processing unit 402, when the candidate path is an active path, according to the OAM configuration
  • the information performs OAM on the candidate path.
  • processing unit 402 is further configured to obtain an OAM data message by performing OAM on the first path;
  • the sending unit 403 is configured to send OAM data messages to the controller.
  • the policy configuration message is a BGP message or a PCEP message.
  • the receiving unit receives a policy configuration message, the policy configuration message including OAM configuration information and first path information, and the first path information is used to identify the first path.
  • the processing unit performs OAM on the first path according to the OAM configuration information. In this way, when performing OAM on the first path, it is not necessary to determine all the service flows transmitted on the first path, and to configure the identification information of each service flow in the device, thereby reducing the difficulty of performing OAM on the first path, and Improve the efficiency of OAM on the first path.
  • an embodiment of the present application provides a schematic diagram of an apparatus 500 for sending a message for OAM.
  • the device 500 may be the controller in any of the foregoing embodiments, for example, may be the controller in the embodiment shown in FIG. 3.
  • the device 500 includes at least one processor 501, a bus system 502, a memory 503, and at least one transceiver 504.
  • the device 500 is a device with a hardware structure, and can be used to implement the functional modules in the device 300 described in FIG. 16.
  • the processing unit 301 in the device 300 shown in FIG. 16 can be implemented by calling the code in the memory 503 by the at least one processor 501.
  • the receiving unit 303 may be implemented by the transceiver 504.
  • the device 500 can also be used to implement the function of the collection and analysis device in any of the foregoing embodiments.
  • processor 501 may be a general-purpose central processing unit (central processing unit, CPU), network processor (network processor, NP), microprocessor, application-specific integrated circuit (ASIC) , Or one or more integrated circuits used to control the execution of the program of this application.
  • CPU central processing unit
  • NP network processor
  • ASIC application-specific integrated circuit
  • the above-mentioned bus system 502 may include a path for transferring information between the above-mentioned components.
  • the aforementioned transceiver 504 is used to communicate with other devices or a communication network.
  • the above-mentioned memory 503 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions.
  • the type of dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc Storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by Any other medium accessed by the computer, but not limited to this.
  • the memory can exist independently and is connected to the processor through a bus.
  • the memory can also be integrated with the processor.
  • the memory 503 is used to store application program codes for executing the solutions of the present application, and the processor 501 controls the execution.
  • the processor 501 is configured to execute the application program code stored in the memory 503, so as to realize the functions in the method of the present patent.
  • the processor 501 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 16.
  • the apparatus 500 may include multiple processors, such as the processor 501 and the processor 507 in FIG. 16. Each of these processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • an embodiment of the present application provides a schematic diagram of an apparatus 600 for receiving a message for OAM.
  • the apparatus 600 may be the head node in any of the foregoing embodiments, for example, may be the head node in the embodiment shown in FIG. 15.
  • the device 600 includes at least one processor 601, a bus system 602, a memory 603, and at least one transceiver 604.
  • the device 600 is a device with a hardware structure, and can be used to implement the functional modules in the device 400 described in FIG. 17.
  • the processing unit 402 in the device 400 shown in FIG. 17 can be implemented by calling the code in the memory 603 by the at least one processor 601.
  • the sending unit 403 may be implemented by the transceiver 604.
  • the device 600 can also be used to implement the function of the collection and analysis device in any of the foregoing embodiments.
  • processor 601 may be a general-purpose central processing unit (central processing unit, CPU), network processor (NP), microprocessor, application-specific integrated circuit (ASIC) , Or one or more integrated circuits used to control the execution of the program of this application.
  • CPU central processing unit
  • NP network processor
  • ASIC application-specific integrated circuit
  • the above-mentioned bus system 602 may include a path for transferring information between the above-mentioned components.
  • the aforementioned transceiver 604 is used to communicate with other devices or a communication network.
  • the aforementioned memory 603 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), or other types that can store information and instructions.
  • the type of dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc Storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by Any other medium accessed by the computer, but not limited to this.
  • the memory can exist independently and is connected to the processor through a bus.
  • the memory can also be integrated with the processor.
  • the memory 603 is used to store application program codes for executing the solutions of the present application, and the processor 601 controls the execution.
  • the processor 601 is configured to execute the application program code stored in the memory 603, so as to realize the functions in the method of the present patent.
  • the processor 601 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 19.
  • the apparatus 600 may include multiple processors, such as the processor 601 and the processor 607 in FIG. 19. Each of these processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • an embodiment of the present application provides a system 700 for receiving a message for OAM.
  • the system 700 includes: an apparatus 300 as shown in FIG. 16 and an apparatus 400 as shown in FIG. 17, or
  • the system 700 includes: the apparatus 500 as described in FIG. 18 and the apparatus 600 as described in FIG. 19.
  • the device 300 described in FIG. 16 or the device 500 described in FIG. 18 may be the controller 701, and the device 400 described in FIG. 17 or the device 600 described in FIG. 19 may be Head node 702.
  • the device 300 described in FIG. 16 or the device 500 described in FIG. 18 may be the controller in the embodiment shown in FIG. 3, and the device 400 described in FIG. 17 or the device 600 described in FIG. 19 may be It is the head node in the embodiment shown in FIG. 15.
  • system 700 may also include other network devices such as tail nodes.

Landscapes

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

Abstract

公开了一种发送报文、接收报文以进行OAM的方法、装置及系统，属于通信领域。该方法包括：控制器生成策略配置报文，策略配置报文包括操作维护管理OAM配置信息和第一路径信息，第一路径信息用于标识第一路径；控制器向第一路径的头节点发送策略配置报文，策略配置报文用于指示头节点根据OAM配置信息对第一路径进行OAM。本申请能够降低对路径进行OAM的难度，以及提高对路径进行OAM的效率。

Description

发送报文、接收报文以进行OAM的方法、装置及系统
本申请要求于2019年11月14日提交的申请号为201911115441.5、发明名称为“发送报文、接收报文以进行OAM的方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，特别涉及一种发送报文、接收报文以进行OAM的方法、装置及系统。
背景技术
网络的管理工作包括操作(operation)、管理(administration)、维护(maintenance)，简称操作维护管理(OAM)，OAM可以完成故障检测、路径发现、故障定位以及性能监控，从而实现对网络分析、预测、规划以及配置，并且可以对网络中传输的业务流进行测试和故障管理。
目前可以对业务流进行OAM，对业务流进行OAM的流程可以为：在转发路径的头节点(例如交换机或路径器)上配置该业务流的标识信息，该转发路径是网络中用于传输该业务流的路径，该标识信息可以是该业务流的五元组信息(包括业务流的源地址、目的地址、源端口号、目的端口号和协议类型)。头节点在接收到该标识信息对应的业务流时，对该业务流进行OAM。
目前除对业务流进行OAM外，还有对该转发路径进行OAM的需求，对转发路径进行OAM时：需要先确定出在该转发路径上传输的所有业务流，然后在头节点上配置确定的每个业务流的标识信息。对于配置的任一个标识信息，头节点在接收到该任一个标识信息对应的业务流时，对该业务流进行OAM，从而实现对该转发路径进行OAM。
在实现本申请的过程中，发明人发现现有技术至少存在以下问题：
目前很难确定出在转发路径上传输的所有业务流，导致对转发路径进行OAM的难度较大。另外，需要在头节点中配置确定的每个业务流的标识信息，配置次数较多，导致对转发路径进行OAM的效率较低。
发明内容
本申请提供了一种发送报文、接收报文的方法、装置及系统，以降低对路径进行OAM的难度，以及提高对路径进行OAM的效率。所述技术方案如下：
第一方面，本申请提供了一种发送报文的方法，在所述方法中：控制器生成策略配置报文，该策略配置报文包括操作维护管理OAM配置信息和第一路径信息，第一路径信息用于标识第一路径。控制器向第一路径的头节点发送该策略配置报文，这样通过该策略配置报文用于指示头节点根据该OAM配置信息对第一路径进行OAM。如此对第一路径进行OAM时不需要确定在第一路径上传输的所有业务流，以及在头节点中配置每个业务流的标识信息， 从而降低对第一路径进行OAM的难度，以及提高对第一路径进行OAM的效率。
在一种可能的实现方式中，该策略配置报文为段路由策略SR Policy配置报文，SR Policy配置报文包括候选路径的信息，该候选路径包括段列表，第一路径为该候选路径或者该段列表标识的路径。如此可以实现对SR Policy定义的第一路径进行OAM，这样在第一路径的性能发生变化时，通过对第一路径进行OAM，可以使头节点感知第一路径的性能发生变化的情况。
在另一种可能的实现方式中，在第一路径为所述侯选路径的情况下，SR Policy配置报文还包括标识信息，该标识信息用于指示头节点，当该候选路径为活跃路径时，根据该OAM配置信息对候选路径进行OAM。如此可以通过该标识信息指示头节点对活跃路径进行OAM。
在另一种可能的实现方式中，控制器接收OAM数据报文，该OAM数据报文是通过对第一路径进行OAM而获得的。这样控制器根据该OAM数据报文可以感知第一路径的性能发生变化的情况。
在另一种可能的实现方式中，策略配置报文为边界网关路由BGP报文或路径计算通信协议PCEP报文。
在另一种可能的实现方式中，OAM配置信息包括OAM方式、OAM对象、OAM粒度或OAM频率中的至少一个。
在另一种可能的实现方式中，OAM方式包括下述方式中的至少一种：带内操作维护管理IOAM方式、互联网协议流性能测量IPFPM方式、带内流信息测量IFIT方式、双向主动测量协议TWAMP方式、单向主动测量协议OWAMP方式以及PING方式。
第二方面，本申请提供了一种接收报文的方法，在所述方法中：头节点接收策略配置报文，该策略配置报文包括操作维护管理OAM配置信息和第一路径信息，第一路径信息用于标识第一路径。头节点根据该OAM配置信息对第一路径进行OAM。如此在对第一路径进行OAM时不需要确定在第一路径上传输的所有业务流，以及在头节点中配置每个业务流的标识信息，从而降低对第一路径进行OAM的难度，以及提高对第一路径进行OAM的效率。
在一种可能的实现方式中，策略配置报文为段路由策略SR Policy配置报文，该SR Policy配置报文包括候选路径的信息，该候选路径包括段列表，第一路径为该候选路径或者该段列表标识的路径。如此可以实现对SR Policy定义的第一路径进行OAM，这样在第一路径的性能发生变化时，通过对第一路径进行OAM，头节点可以感知第一路径的性能发生变化的情况。
在另一种可能的实现方式中，头节点根据该OAM配置信息获得OAM执行信息；接收第一报文；在第一报文中添加该OAM执行信息以生成第二报文；经过该第一路径发送第二报文。如此实现对第一路径进行OAM。
在另一种可能的实现方式中，头节点根据该OAM配置信息生成第一报文，第一报文包括OAM执行信息。头节点经过所述第一路径发送第一报文。如此实现主动对第一路径进行OAM。
在另一种可能的实现方式中，在第一路径为候选路径的情况下，头节点获得标识信息；该标识信息用于指示头节点，当该候选路径为活跃路径时，根据该OAM配置信息对该候选路径进行OAM。如此可以通过该标识信息指示头节点对活跃路径进行OAM。
在另一种可能的实现方式中，头节点通过对第一路径进行OAM而获得OAM数据报文；头节点向控制器发送OAM数据报文。这样控制器接收该OAM数据报文，根据该OAM数据 报文可以感知第一路径的性能发生变化的情况。
在另一种可能的实现方式中，策略配置报文为边界网关路由BGP报文或路径计算通信协议PCEP报文。
第三方面，本申请提供了一种发送报文的装置，用于执行第一方面或第一方面的任意一种可能实现方式中的方法。具体地，所述装置包括用于执行第一方面或第一方面的任意一种可能实现方式的方法的单元。
第四方面，本申请提供了一种接收报文的装置，用于执行第二方面或第二方面的任意一种可能实现方式中的方法。具体地，所述装置包括用于执行第二方面或第二方面的任意一种可能实现方式的方法的单元。
第五方面，本申请提供了一种发送报文的装置，所述装置包括：处理器、存储器和收发器。其中，所述处理器、所述存储器和所述收发器之间可以通过总线系统相连。所述存储器用于存储一个或多个程序，所述处理器用于执行所述存储器中的一个或多个程序，完成第一方面或第一方面的任意可能实现方式中的方法。
第六方面，本申请提供了一种接收报文的装置，所述装置包括：处理器、存储器和收发器。其中，所述处理器、所述存储器和所述收发器之间可以通过总线系统相连。所述存储器用于存储一个或多个程序，所述处理器用于执行所述存储器中的一个或多个程序，完成第二方面或第二方面的任意可能实现方式中的方法。
第七方面，本申请提供了一种计算机可读存储介质，计算机可读存储介质中存储有程序代码，当其在计算机上运行时，使得计算机执行上述第一方面、第二方面、第一方面的任意可能实现方式或第二方面的任意可能实现方式中的方法。
第八方面，本申请提供了一种包含程序代码的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面、第二方面、第一方面的任意可能实现方式或第二方面的任意可能实现方式中的方法。
第九方面，本申请提供了一种接收报文的系统，包括第三方面所述的装置和第四方面所述的装置；或者，包括第五方面所述的装置和第六方面所述的装置。
附图说明
图1是本申请实施例提供的一种网络架构示意图；
图2是本申请实施例提供的段路径策略(segment routing Policy，SR Policy)的结构示意图；
图3是本申请实施例提供的一种发送报文以进行OAM的方法流程图；
图4是本申请实施例提供的一种SR Policy配置报文的结构示意图；
图5是本申请实施例提供的另一种SR Policy配置报文的结构示意图；
图6是本申请实施例提供的另一种SR Policy配置报文的结构示意图；
图7是本申请实施例提供的另一种SR Policy配置报文的结构示意图；
图8是本申请实施例提供的另一种SR Policy配置报文的结构示意图；
图9是本申请实施例提供的另一种SR Policy配置报文的结构示意图；
图10是本申请实施例提供的另一种SR Policy配置报文的结构示意图；
图11是本申请实施例提供的另一种SR Policy配置报文的结构示意图；
图12是本申请实施例提供的一种TLV字段结构示意图；
图13是本申请实施例提供的另一种TLV字段结构示意图；
图14是本申请实施例提供的另一种TLV字段结构示意图；
图15是本申请实施例提供的一种接收报文以进行OAM的方法流程图；
图16是本申请实施例提供的一种发送报文以进行OAM的装置结构示意图；
图17是本申请实施例提供的一种接收报文以进行OAM的装置结构示意图；
图18是本申请实施例提供的另一种发送报文以进行OAM的装置结构示意图；
图19是本申请实施例提供的另一种接收报文以进行OAM的装置结构示意图；
图20是本申请实施例提供的一种接收报文以进行OAM的系统结构示意图。
具体实施方式
下面将结合附图对本申请实施方式作进一步地详细描述。
OAM：操作维护管理，对通信网络进行OAM指的是通信网络中的节点采集OAM信息。OAM的定义如下：
(1)性能监控并产生维护信息，从而根据维护信息评估网络的稳定性；
(2)通过定期查询的方式检测网络故障，产生各种维护信息和告警信息；
(3)在发生网络故障时，将业务调度或切换到其他的实体，以保证网络的正常运行；
(4)将故障信息传递给管理实体(例如控制器)。
综上可知，通信网络的OAM可以包括故障检测、路径发现、故障定位以及性能监控等。通信网络中的OAM域中的节点可以进行OAM。OAM域指的是通信网络中支持OAM功能的所有节点的集合。OAM域通常有一个入口节点和出口节点，入口节点可称为头节点，出口节点可称为尾节点。头节点与尾节点之间存在至少一条路径，每条路径经过的节点可以支持OAM功能。
例如参见图1所示的网络架构，假设该网络架构中的节点A、节点B、节点C和节点D组成的一个OAM域。该网络架构还包括控制器，控制器与节点A相连，控制器也可以与节点B、节点C和节点D相连。其中，节点A是该OAM域的头节点，头节点A负责确定OAM配置信息，节点C是该OAM域的尾节点，头节点A或尾节点C可以根据OAM域中各个节点采集到的OAM信息获取OAM结果，并上报该OAM结果给控制器。在该OAM域中头节点A与尾节点C之间有两条路径，其中一条路径由节点A、B、C组成，另一条路径由节点A、D、C组成。
可选的，通信网络中的节点可以是网络设备，例如可以为路径器或交换机等设备。
对于OAM域中的路径，目前有对该路径进行OAM的需求，为了能够对OAM域中的路径进行OAM.，控制器可以生成策略配置报文，该策略配置报文包括OAM配置信息和第一路径信息，第一路径信息用于标识第一路径，第一路径是头节点与尾节点之间的路径；向头节点发送该策略配置报文。头节点接收该策略配置报文，根据该OAM配置信息对第一路径信息标识的第一路径进行OAM。
其中，控制器生成策略配置报文以向头节点发送该策略配置报文的详细实现过程可以参见后续图3所示的实施例。头节点接收该策略配置报文以及对第一路径进行OAM的详细实 现过程可以参见后续图15所示的实施例，在此先不详细说明。
可选的，图1所示的网络架构可以应用于SR Policy的场景或分段路由流量工程(segment routing traffic engineering，SR TE)的场景等。SR Policy场景或SR TE场景包括头节点、尾节点以及头节点与尾节点之间的至少一条路径。且通常每条路径经过的节点可以支持OAM功能。
可选的，接下来以SR Policy的场景为例进行说明。在SR Policy的场景中，该策略配置报文为段路由策略(segment routing Policy，SR Policy)配置报文等，该SR Policy配置报文包括候选路径的信息，该候选路径包括段列表，第一路径为该候选路径或者该段列表标识的路径。
可选的，控制器在头节点和尾节点配置SR Policy时向头节点发送SR Policy配置报文，通过SR Policy配置报文在头节点与尾节点之间配置SR Policy。SR Policy定义了头节点、尾节点、性能需求信息。以及参见图2，SR Policy还定义了头节点与尾节点之间的至少一个侯选路径，每个侯选路径包括至少一个段列表，每个段列表用于标识头节点与尾节点之间的一条路径。
可选的，该性能需求信息包括至少一个性能参数的参数阈值，例如，该至少一个性能参数包括时延和丢包率等中的一个或多个。该参数阈值包括时延阈值和丢包率阈值等中的一个或多个。该时延阈值用于表示使用该SR Policy定义的路径传输业务时，该SR Policy可以尽量保证该路径产生的时延可以不超过该时延阈值。该丢包率阈值用于表示使用该SR Policy定义的路径传输业务时，该SR Policy可以尽量保证该路径产生的丢包率不超过该丢包率阈值。
所述至少一个候选路径中的每个候选路径包括至少一个段列表。可选的，当所述每个候选路径包括多个段列表时，多个段列表之间可以进行负载分担。可选的，头节点也可以从该至少一个段列表中选择一个或多个段列表，通过选择的段列表所标识的路径发送该业务。
可选的，参见图2，SR Policy还定义了每个侯选路径的基础属性信息。对于任一个侯选路径，该任一个侯选路径的基础属性信息包括该任一个侯选路径的优先级(Preference)等信息。当该任一个侯选路径是活跃路径的情况下，该任一个侯选路径的基础属性信息还包括SR Policy的标识信息(Binding SID)。
可选的，参见图2，SR Policy还定义了每个段列表的基础属性信息，对于任一个段列表，该任一个段列表的基础属性信息包括该任一个段列表的权重等。
可选的，该至少一个侯选路径中存在一个活跃路径，该至少一个侯选路径中的其他侯选路径为非活跃路径。头节点需要向尾节点发送业务时，可以使用活跃路径向尾节点发送业务。
在配置SR Policy之后，对SR Policy定义的侯选路径或SR Policy定义的的段列表标识的路径进行OAM是很有必要的。当对某个侯选路径或某个段列表标识的路径进行OAM时，可以及时发现该侯选路径提供的性能或该段列表标识的路径提供的性能不能满足该SR Policy定义的性能需求信息。详细实现过程可以参见如下图3或图15所示的实施例。
参见图3，本申请实施例提供了一种发送报文的方法，该方法可以应用于如图1所示的网络架构，包括：
步骤101：控制器生成策略配置报文，该策略配置报文包括OAM配置信息和第一路径信息，第一路径信息用于标识第一路径。
可选的，该策略配置报文为SR Policy配置报文，该SR Policy配置报文包括目标候选路径的信息，目标候选路径包括目标段列表，第一路径为目标候选路径或者目标段列表标识的路径。
目标侯选路径是SR Policy定义的至少一个侯选路径中的一个或多个侯选路径。目标段列表是目标侯选路径包括的至少一个段列表中的一个或多个段列表。该OAM配置信息是第一路径的OAM配置信息。
控制器在头节点上配置与尾节点之间的SR Policy时向头节点发送SR Policy配置报文。该SR Policy配置报文包括该SR Policy的基础配置信息和第一路径的OAM配置信息。
参见图2，该基础配置信息包括该SR Policy定义的至少一个侯选路径的信息，以及该SR Policy定义的性能需求信息等。对于任一个侯选路径，该任一个侯选路径的信息包括该任一个侯选路径的基础属性信息、至少一个段列表和每个段列表的基础属于信息。其中，第一路径(目标侯选路径)为该至少一个侯选路径中的一个或多个侯选路径，或者，第一路径(目标段列表)是目标侯选路径中的一个或多个段列表。
可选的，该OAM配置信息可以包括OAM属性。所述OAM属性可以包括OAM方式、OAM对象、OAM粒度或OAM频率中的至少一个。
可选的，OAM对象可以包括时延和丢包率等中的一个或多个性能参数。
可选的，OAM方式包括带内OAM方式或带外OAM方式等，带内OAM方式包括带内操作维护管理(In-situ OAM，IOAM)方式、带内流检测(in-situ flow information telemetry，INT)方式，交替标记(Alternate Marking)方式，抽象带内流量分析器(abstract inband flow analyzer，IFA方式)、互联网协议流性能测量(internet protocol flow performance monitor，IPFPM)方式或带内流信息测量(in-situ flow information telemetry，IFIT)方式等。带外OAM方式包括双向主动测量协议(two-way active measurement protocol，TWAMP)方式、单向主动测量协议(one-way active measurement protocol，OWAMP)方式或PING方式、简单的双向主动测量协议(simple two-way active measurement protocol，STAMP)方式、或者，轻双向主动测量协议(TWAMP LIGHT)方式等。
可选的，在第一路径为目标侯选路径的情况下，该SR Policy配置报文的第一字段包括目标侯选路径的基础属性信息，该SR Policy配置报文的第二字段包括第一路径的OAM配置信息，第一字段与第二字段相邻或第二字段位于第一字段中。
可选的，在第一路径为目标段列表的情况下，该SR Policy配置报文的第三字段包括该目标段列表，该SR Policy配置报文的第四字段包括第一路径的OAM配置信息，第三字段与第四字段相邻或第四字段位于第三字段中。
例如，参见图4，该SR Policy配置报文为边界网关路由(border gateway protocol，BGP)报文，控制器可以生成至少一个BGP报文。任一个BGP报文可以包括一个侯选路径的信息。如图4所示的BGP报文包括第一字段和位于第一字段之后的至少一个第三字段，假设第一字段包括目标侯选路径的基础性属性信息，位于第一字段之后的任一个第三字段，该任一个第三字段包括目标侯选路径中的一个段列表和该段列表的基础属性信息。可选的，第一字段中还可以包括SR Policy的名称等信息。
参见图4，在第一路径是目标侯选路径的情况下，该BGP报文的第二字段包括目标侯选路径的OAM配置信息，第一字段与第二字段相邻或者第二字段位于第一字段中。例如，在 图4所示的示例中，第二字段紧随第一字段之后，用于表示第二字段中的OAM配置信息是目标侯选路径的OAM配置信息。或者，在图5所示的示例中，第二字段位于第一字段中，用于表示第二字段中的OAM配置信息是目标侯选路径的OAM配置信息。
可选的，第一字段为类型长度内容(type length value，TLV)字段。在第一字段与第二字段相邻的情况下，第二字段也为TLV字段。，在第二字段位于第一字段的情况下，第二字段为位于第一字段中的子TLV字段。
参见图6，在第一路径是目标侯选路径包括的目标段列表标识的路径的情况下，该BGP报文的第四字段包括目标段列表的OAM配置信息，该BGP报文存在一个第三字段包括目标段列表和目标段列表的基础属性信息，该第三字段与该第四字段相邻，或者，该第四字段位于该第三字段中。例如，在图6所示的示例中，该第四字段紧随第三字段之后，用于表示该第四字段中的OAM配置信息是目标段列表的OAM配置信息。或者，在图7所示的示例中，该第四字段位于该第三字段中，用于表示该第四字段中的OAM配置信息是目标段列表的OAM配置信息。
可选的，第三字段为TLV字段。第三字段包括多个子TLV字段，目标段列表包括多个标签(Segment)，每个标签可以对应一个子TLV字段，对于任一个标签对应的子TLV字段，该子TLV字段包括该标签。目标段列表的基础属性信息对应至少一个子TLV，该至少一个子TLV字段包括目标段列表的基础属性信息。
在第三字段与第四字段相邻的情况下，第四字段也为TLV字段。或者，在第四字段位于第三字段中的情况下，第四字段为位于第三字段中的子TLV字段。
例如，参见图8，该SR Policy配置报文为路径计算通信协议(path computation element communication protocol，PCEP)报文，控制器可以生成至少一个PCEP报文。任一个PCEP报文可以包括SR Policy定义的各侯选路径的基础属性信息、一个侯选路径包括的段列表以及目标段列表的基础属性信息。
可选的，在该SR Policy配置报文为PCEP报文的情况下，SR Policy定义的侯选路径包括一个段列表。控制器可以使用一个PCEP报文在头节点上配置一个侯选路径，这样控制器需要至少一个PCEP报文在头节点与尾节点之间配置该SR Policy的各侯选路径。
例如，假设图8所示的PCEP报文用于配置目标侯选路径，目标侯选路径包括一个目标段列表，该PCEP报文包括每个侯选路径对应的第一字段和目标侯选路径包括的目标段列表对应的第三字段。对于任一个侯选路径，该任一个侯选路径对应的第一字段包括该任一个侯选路径的基础属性信息。该任一个侯选路径的基础属性信息包括该任一个侯选路径的标识和优先级。可选的，该任一个侯选路径对应的第一字段还包括SR Policy的标识和名称。目标段列表对应的第三字段包括目标段列表和目标段列表的基础属性信息。
可选的，参见图8，该任一个侯选路径对应的第一字段包括四个TLV字段，分别为第一TLV、第二TLV、第三TLV和第四TLV。第一TLV包括SR Policy的标识，第二TLV包括SR Policy的名称，第三TLV包括该任一个侯选路径的标识，第四TLV包括该任一个侯选路径的优先级。第三字段为TLV字段，该TLV字段包括目标段列表和目标段列表的基础属性信息。在PCEP报文中，第三字段也可以包括多个子TLV字段，目标段列表包括多个标签，每个标签可以对应一个子TLV字段，对于任一个标签对应的子TLV字段，该子TLV字段包括该标签。目标段列表的基础属性信息对应至少一个子TLV，该至少一个子TLV字段包括目 标段列表的基础属性信息。
参见图8，在第一路径是目标侯选路径的情况下，假设目标侯选路径为侯选路径1，该PCEP报文的第二字段包括目标侯选路径的OAM配置信息，目标侯选路径对应的第一字段与该第二字段相邻或者该第二字段位于目标侯选路径对应的第一字段中。例如，在图8所示的示例中，该第二字段紧随目标侯选路径对应的第一字段之后，用于表示第二字段中的OAM配置信息是目标侯选路径的OAM配置信息。或者，在图9所示的示例中，第二字段位于目标侯选路径对应的第一字段中，用于表示第二字段中的OAM配置信息是目标侯选路径的OAM配置信息。
参见图10，在第一路径是目标侯选路径包括的目标段列表标识的路径的情况下，该PCEP报文的第四字段包括目标段列表的OAM配置信息，该PCEP报文存在一个第三字段包括目标段列表和目标段列表的基础属性信息，该第三字段与该第四字段相邻，或者，该第四字段位于该第三字段中。例如，在图10所示的示例中，该第四字段紧随第三字段之后，用于表示该第四字段中的OAM配置信息是目标段列表的OAM配置信息。或者，在图11所示的示例中，该第四字段位于该第三字段中，用于表示该第四字段中的OAM配置信息是目标段列表的OAM配置信息。
在PCEP报文中，在第三字段与第四字段相邻的情况下，第四字段也为TLV字段。或者，在第四字段位于第三字段中的情况下，第四字段为位于第三字段中的子TLV字段。
可选的，包括目标侯选路径的OAM配置信息的第二字段或包括目标段列表的OAM配置信息的第四字段为TLV字段。TLV字段包括类型(Type)、长度(Length)和内容(Value)三个子字段。可以使用Type子字段包括OAM方式，使用Value子字段包括OAM对象、OAM粒度或OAM频率中的至少一个。
可选的，在第一路径为侯选路径的情况下，SR Policy配置报文还包括标识信息，该标识信息用于指示头节点对活跃路径进行OAM，或者，该标识信息用于指示头节点对非活跃路径和活跃路径进行OAM。
可选的，在本步骤中，可以在SR Policy配置报文中增加TLV字段，该TLV字段包括OAM配置信息。接下来列举了几种TLV字段。参见图12所示的第一种TLV字段，在第一种TLV字段中，类型(Type)的取值表示OAM方式，该OAM方式可以为双向主动测量协议(Simple Two-way Active Measurement Protocol,STAMP)方式，即Type的取值表示第一种TLV为STAMP TLV字段。第一种TLV字段还包括头节点的地址和端口号，尾节点的地址和端口号，以及OAM频率。第一种TLV字段可以不包括OAM对象，头节点包括默认的OAM对象。
在第一种TLV字段中，长度(Length)表示值字段的总长度，不包括Type和Length字段的长度。DSCP字段表示要在测试数据包中设置的DSCP值。间隔(Interval)包括OAM频率，表示连续两次传输数据包之间的时间间隔，该数据包是测试会话中的数据包，单位是微秒。发送方UDP端口(Sender UDP Port)包括头节点的端口号，表示发送方UDP端口号，范围为49152至65535。接收方UDP端口(Reflector UDP Port)包括尾节点的端口号。默认值为862(TWAMP测试接收器端口)，范围为1024至65535。发送方IP(Sender IP)包括头节点的地址，当Length字段为18字节时，头节点使用IPv4地址。当Length字段为42字节时，头节点使用IPv6。接收方IP(Reflector IP)包括尾节点的地址。当Length字段为18字 节时，尾节点的地址为IPv4地址。当Length字段为42字节时，尾节点的地址为IPv6地址。Rsvd为进一步使用而保留的字段。
参见图13所示的第二种TLV字段，在第二种TLV字段中，类型(Type)的取值表示OAM方式，该OAM方式可以为IOAM预分配(IOAM Pre-allocated)，即Type的取值表示第二种TLV为IOAM Pre-allocated Trace Option Sub-TLV字段。或者，该OAM方式也可以为IOAM增量跟踪(IOAM Incremental Trace)，即Type的取值表示第二种TLV为IOAM Incremental Trace Option Sub-TLV字段。Length表示值字段的总长度，不包括Type和Length字段。命名空间ID(NanmespaceID)表示IOAM命名空间的16位标识符。IOAM跟踪类型(IOAM Trace Type)包括OAM对象、OAM粒度或OAM频率等中的至少一个，可以为一个24位标识符。标志(Flags)可以为4位字段。保留字段(Rsvd)可以为进一步使用而保留的4位字段。
参见图14所示的第三种TLV字段，在第三种TLV字段中，类型(Type)的取值表示OAM方式，该OAM方式可以为IOAM边到边或IOAM端到端(IOAM Edge-to-Edge)，即Type的取值表示第三种TLV为IOAM Edge-to-Edge Option Sub-TLV字段。Length字表示值字段的总长度，不包括Type和Length字段。Name space ID可以表示IOAM命名空间的16位标识符。IOAM E2E Type包括OAM对象、OAM粒度或OAM频率等中的至少一个，是一个16位标识符。
上述Type字段可以由互联网编号分配机构(IANA，Internet Assigned Numbers Authority)分配。参见表1，表1对Type的不同取值所表示的含义进行了示例性说明。
表1
取值 含义
1 STAMP Sub-TLV
2 IOAM Pre-allocated Trace Option Sub-TLV
3 IOAM Incremental Trace Option Sub-TLV
4 IOAM Edge-to-Edge Trace Option Sub-TLV
步骤102：控制器向头节点发送该策略配置报文，该策略配置报文用于指示头节点根据该OAM配置信息对第一路径进行OAM。
头节点接收到该策略配置报文后，根据该策略配置报文包括的OAM配置信息对第一路径进行OAM。头节点进行OAM的详细实现过程可以参见后续图15所示的实施例，在此先不说明。
头节点在对第一路径进行OAM时会获取到OAM数据报文，向控制器发送该OAM数据报文。控制器接收该OAM数据报文。
在本申请实施例中，由于控制器生成策略配置报文，该策略配置报文包括OAM配置信息和第一路径信息，第一路径信息用于标识第一路径；向第一路径的头节点发送策略配置报文，这样头节点可以根据该策略配置报文包括的OAM配置信息对第一路径进行OAM。如此对第一路径进行OAM时不需要确定在第一路径上传输的所有业务流，以及在头节点中配置每个业务流的标识信息，从而降低对第一路径进行OAM的难度，以及提高对第一路径进行OAM的效率。通过对第一路径进行OAM可以得到第一路径的性能，这样在第一路径的性能 发生变化时，也能及时感知。头节点在对第一路径进行OAM时会获取到OAM数据报文，向控制器发送该OAM数据报文，这样控制器根据该OAM数据报文也能感知第一路径的性能变化。
参见图15，本申请实施例提供了一种接收报文以进行OAM的方法，该方法应用于图1所示的网络架构中，包括：
步骤201：头节点接收策略配置报文，该策略配置报文包括OAM配置信息和第一路径信息，第一路径信息用于标识第一路径。
可选的，该策略配置报文可以是控制器生成的，控制器可以采用上述图3所示实施例的方式生成该策略配置报文。在本步骤中，头节点接收控制器发送的该策略配置报文。
可选的，该策略配置报文为SR Policy报文，该SR Policy配置报文包括该SR Policy的基础配置信息和该OAM配置信息。该基础配置信息包括至少一个侯选路径的信息，以及该SR Policy的性能需求信息等。对于任一个侯选路径，该任一个侯选路径的信息包括该任一个侯选路径的基础属性信息、至少一个段列表和每个段列表的基础属于信息。
其中，第一路径为该至少一个侯选路径中的一个或多个侯选路径，为了便于说明称该一个或多个侯选路径为目标侯选路径。或者，第一路径是目标侯选路径中的一个或多个段列表，为了便于说明称该一个或多个段列表为目标段列表。
可选的，头节点在接收到该策略配置报文后，还可以向控制器发送策略响应报文，该策略响应报文包括OAM响应信息，该OAM响应信息用于指示是否成功在头节点上配置OAM功能。
可选的，在第一路径为目标侯选路径的情况下，该策略配置报文可以包括目标侯选路径对应的TLV字段，该TLV字段可以包括目标侯选路径对应的OAM响应消息。在第一路径为目标段列表的情况下，该策略配置报文可以包括目标段列表对应的TLV字段，该TLV字段可以包括目标段列表对应的OAM响应消息。
步骤202：头节点根据该策略配置报文包括的OAM配置信息对第一路径进行OAM。
头节点接收到该SR Policy配置报文后，可以保存该SR Policy的基础配置信息。然后根据该OAM配置信息对第一路径进行OAM。
可选的，在第一路径为目标侯选路径的情况下，头节点确定该SR Policy配置报文中的包括目标侯选路径的基础属性信息的第一字段，根据该第一字段确定该SR Policy配置报文中的包括目标侯选路径的OAM配置信息的第二字段，从第二字段中提取目标侯选路径的OAM配置信息。
可选的，在该SR Policy配置报文中，头节点确定与第一字段相邻的第二字段，或者确定位于第一字段中的第二字段。
可选的，在目标侯选路径的OAM配置信息包括OAM方式、OAM对象、OAM粒度或OAM频率中的至少一个。
可选的，目标侯选路径的OAM配置信息包括OAM方式，但不包括OAM对象，此时头节点获取默认的OAM对象。或者，目标侯选路径的OAM配置信息包括OAM对象，但不包括OAM方式，此时头节点获取默认的OAM方式。
在本步骤中，当该OAM方式为带内OAM方式时，头节点根据该OAM配置信息获得 OAM执行信息；接收第一报文；在第一报文中添加该OAM执行信息以生成第二报文；经过该侯选路径向尾节点发送第二报文，以实现对该侯选路径进行OAM。
头节点和尾节点为通信网络中的网络设备，因此头节点可以接收到来自其他网络设备或终端设备的第一报文。
头节点获得的OAM执行信息可以包括该OAM对象。头节点接收到第一报文后，在确定使用目标侯选路径传输第一报文时，在第一报文的报文头中添加OAM执行信息，得到第二报文。
目标侯选路径包括至少一个段列表，头节点从该至少一个段列表中选择中一个或多个段列表，使用选择的段列表所标识的路径向尾节点发送第二报文。
SR Policy的基础配置信息中包括该至少一个段列表中的每个段列表的权重，头节点可以根据每个段列表的权重，从每个段列表中选择一个或多个段列表。
对于选择的任一个段列表标识的路径经过的任一节点，该任一节点接收该第二报文，根据该第二报文中的该OAM对象对该段列表标识的路径进行采集得到OAM信息，并将采集得到的OAM信息添加到第二报文中，然后再向尾节点转发第二报文。尾节点接收第二报文，根据该第二报文中的该OAM对象对该该段列表标识的路径进行采集得到OAM信息，根据自身采集的OAM信息和第二报文中的OAM信息得到OAM结果。
可选的，头节点可以保存有标识信息，或者，SR Policy配置报文还包括该标识信息；该标识信息用于指示头节点对活跃路径进行OAM，或者，该标识信息用于指示头节点对非活跃路径和活跃路径进行OAM。
可选的，头节点生成第二报文的操作可以为：头节点获取该标识信息，在确定使用目标侯选路径传输第一报文时，对该标识信息进行判断，在判断出该标识信息用于指示头节点对活跃路径进行OAM的情况下，头节点确定目标侯选路径是否为活跃路径，如果是活跃路径，则在第一报文中添加该OAM执行信息以生成第二报文，即对目标侯选路径进行OAM。如果是非活跃路径，则头节点直接向尾节点发送第一报文。在判断出该标识信息用于指示头节点对非活跃路径和活跃路径进行OAM的情况下，则头节点直接在第一报文中添加该OAM执行信息以生成第二报文，即直接对目标侯选路径进行OAM。
可选的，头节点获取所述标识信息，可以是头节点在接收的策略配置报文中获得该标识信息，即该标识信息包括在策略配置报文中。该标识信息可以由控制器添加在策略配置报文中。
可选的，头节点获取所述标识信息，也可以是头节点读取自身保存的标识信息，即该标识信息设置在头节点中。该标识信息可以由网络管理员在头节点进行手工配置。该标识信息也可以是头节点在接收控制器发送的控制报文后，根据控制报文的指示，生成标识信息并保存在头节点中。
可选的，尾节点向控制器发送OAM数据报文，该OAM数据报文包括该OAM结果。
例如，假设该OAM对象为时延和/或丢包率等，头节点在第一报文中添加时延和/或丢包率以生成第二报文，使用该选择的段列表标识的路径向尾节点发送第二报文。对于该段列表标识的路径经过的任一节点，该任一节点接收该第二报文，采集该段列表标识的路径的时延和/或丢包率(即采集得到OAM信息)，并将采集得到的时延和/或丢包率添加到第二报文中，然后再向尾节点转发第二报文。尾节点接收第二报文，采集该段列表标识的路径的时延和/或 丢包率，根据自身采集的时延和第二报文中的时延计算时延平均值，和/或，根据自身采集的丢包率和该第二报文中的丢包率计算丢包率平均值，得到OAM结果，该OAM结果包括该时延平均值和/或丢包率平均值。
在本步骤中，当该OAM方式为带外OAM方式时，头节点根据该OAM配置信息生成第一报文，第一报文包括OAM执行信息；经过该侯选路径向尾节点发送第一报文，以实现对该侯选路径进行OAM。
头节点获得的OAM执行信息可以包括该OAM对象。头节点生成的第一报文的报文头中包括OAM执行信息。
该侯选路径包括至少一个段列表，头节点从该至少一个段列表中选择中一个或多个段列表，使用选择的段列表所标识的路径向尾节点发送第一报文。
对于选择的段列表标识的路径经过的任一节点，该任一节点接收该第一报文，根据该第一报文中的该OAM对象对该段列表标识的路径进行采集，并将采集得到的OAM信息添加到第一报文中，然后再向尾节点转发第一报文。尾节点接收第一报文，根据该第一报文中的该OAM对象对该段列表标识的路径进行采集，并将采集得到的OAM信息添加到第一报文中，并向头节点发送该第一报文，这样头节点接收该第一报文，根据接收的第一报文中的OAM信息得到OAM结果。
可选的，在头节点保存有标识信息或者SR Policy配置报文还包括该标识信息的情况下，头节点生成第一报文的操作可以为：头节点对该标识信息进行判断，在判断出该标识信息用于指示头节点对活跃路径进行OAM的情况下，头节点确定目标侯选路径是否为活跃路径，如果是活跃路径，则生成第一报文，即对目标侯选路径进行OAM。在判断出该标识信息用于指示头节点对非活跃路径和活跃路径进行OAM的情况下，则头节点直接生成第一报文，即直接对目标侯选路径进行OAM。
可选的，头节点向控制器发送OAM数据报文，该OAM数据报文包括该OAM结果。
例如，假设该OAM对象为时延和/或丢包率等，头节点生成的第一报文的报文头中包括时延和/或丢包率等，使用该选择的段列表标识的路径向尾节点发送第一报文。对于该段列表标识的路径经过的任一节点，该任一节点接收该第一报文，采集该段列表标识的路径的时延和/或丢包率，并将采集得到的时延和/或丢包率添加到第一报文中，然后再向尾节点转发第一报文。尾节点接收第一报文，采集该段列表标识的路径的时延和/或丢包率，并将采集得到的时延和/或丢包率添加到第一报文中，并向头节点发送该第一报文。头节点接收第一报文，根据接收的第一报文中的时延计算时延平均值，和/或，根据接收的该第一报文中的丢包率计算丢包率平均值，得到OAM结果，该OAM结果包括该时延平均值和/或丢包率平均值。
当该OAM方式为带外OAM方式时，该OAM配置信息可以包括OAM频率，在本步骤中根据该OAM频率对目标侯选路径进行OAM。即头节点根据该OAM频率生成第一报文，经过目标侯选路径向尾节点发送该第一报文。
可选的，在第一路径为目标段列表的情况下，头节点确定该SR Policy配置报文中的包括目标段列表的第三字段，根据该第三字段确定该SR Policy配置报文中的包括目标段表列的OAM配置信息的第四字段，从第四字段中提取目标段列表的OAM配置信息。
可选的，在该SR Policy配置报文中，头节点确定与第三字段相邻的第四字段，或者确定位于第三字段中的第四字段。
可选的，在目标段列表的OAM配置信息包括OAM方式、OAM对象、OAM粒度或OAM频率中的至少一个。
可选的，目标段列表的OAM配置信息包括OAM方式，但不包括OAM对象，此时头节点获取默认的OAM对象。或者，目标段列表的OAM配置信息包括OAM对象，但不包括OAM方式，此时头节点获取默认的OAM方式。
在本步骤中，当该OAM方式为带内OAM方式时，头节点根据该OAM配置信息获得OAM执行信息；接收第一报文；在第一报文中添加该OAM执行信息以生成第二报文；经过目标段列表标识的路径向尾节点发送第二报文，以实现对该段列表标识的路径进行OAM。
头节点获得的OAM执行信息可以包括该OAM对象。头节点接收到第一报文后，在确定使用目标段列表标识的路径传输第一报文时，在第一报文的报文头中添加OAM执行信息，得到第二报文。
对于目标段列表标识的路径经过的任一节点，该任一节点接收该第二报文，根据该第二报文中的该OAM对象对目标段列表标识的路径进行采集，并将采集得到的OAM信息添加到第二报文中，然后再向尾节点转发第二报文。尾节点接收第二报文，根据该第二报文中的该OAM对象对目标段列表标识的路径进行采集，根据自身采集得到的OAM信息和第二报文中的OAM信息得到OAM结果。
可选的，尾节点向控制器发送OAM数据报文，该OAM数据报文包括该OAM结果。
例如，假设该OAM对象为时延和/或丢包率等，头节点在第一报文中添加时延和/或丢包率以生成第二报文，使用目标段列表标识的路径向尾节点发送第二报文。对于该段列表标识的路径经过的任一节点，该任一节点接收该第二报文，对目标段列表标识的路径进行采集得到时延和/或丢包率，并将采集得到的时延和/或丢包率添加到第二报文中，然后再向尾节点转发第二报文。尾节点接收第二报文，对目标段列表标识的路径进行采集得到时延和/或丢包率，根据自身采集得到的时延和第二报文中的时延计算时延平均值，和/或，根据自身采集得到的丢包率和该第二报文中的丢包率计算丢包率平均值，得到OAM结果，该OAM结果包括该时延平均值和/或丢包率平均值。
在本步骤中，当该OAM方式为带外OAM方式时，头节点根据该OAM配置信息生成第一报文，第一报文包括OAM执行信息；经过目标段列表标识的路径向尾节点发送第一报文，以实现对目标段列表标识的路径进行OAM。
头节点获得的OAM执行信息可以包括该OAM对象。头节点生成的第一报文的报文头中包括OAM执行信息。
对于目标段列表标识的路径经过的任一节点，该任一节点接收该第一报文，根据该第一报文中的该OAM对象对目标段列表标识的路径进行采集，并将采集得到的OAM信息添加到第一报文中，然后再向尾节点转发第一报文。尾节点接收第一报文，根据该第一报文中的该OAM对象对目标段列表标识的路径进行采集，并向头节点发送该第一报文，这样头节点接收该第一报文，根据接收的第一报文中的OAM信息得到OAM结果。
可选的，头节点向控制器发送OAM数据报文，该OAM数据报文包括对目标段列表采集得到的OAM结果。
例如，假设该OAM对象为时延和/或丢包率等，头节点生成的第一报文的报文头中包括时延和/或丢包率等，使用目标段列表标识的路径向尾节点发送第一报文。对于目标段列表标 识的路径经过的任一节点，该任一节点接收该第一报文，采集目标段列表标识的路径的时延和/或丢包率，并将采集得到的时延和/或丢包率添加到第一报文中，然后再向尾节点转发第一报文。尾节点接收第一报文，采集目标段列表标识的路径的时延和/或丢包率，并将采集得到的时延和/或丢包率添加到第一报文中，并向头节点发送该第一报文。头节点接收第一报文，根据接收的第一报文中的时延计算时延平均值，和/或，根据接收的该第一报文中的丢包率计算丢包率平均值，得到OAM结果。
当该OAM方式为带外OAM方式时，在该OAM配置信息包括OAM频率时，在本步骤中根据该OAM频率对目标段列表标识的路径进行OAM。即头节点根据该OAM频率生成第一报文，经过目标段列表标识的路径向尾节点发送第一报文。
当该OAM方式为带内OAM方式时，该OAM配置信息可以包括OAM粒度，OAM粒度用于指示尾节点发送OAM结果的粒度。OAM粒度可以是按业务流发送或按报文发送。所谓按业务流发送是指尾节点在接收完该业务流中的每个第二报文时，向控制器发送OAM数据报文，该OAM数据报文包括OAM结果，该OAM结果是基于接收的每个第二报文得到的。所谓按报文发送是指尾节点在接收到该业务流中的一个第二报文时，向控制器发送OAM数据报文，该OAM数据报文包括OAM结果，该OAM结果是基于该一个第二报文得到的。
可选的，控制器或头节点根据OAM结果感知到第一路径的性能不能满足SR Policy定义的性能需求信息时，可以对第一路径进行调整。例如，在第一路径为目标侯选路径的情况下，调整目标侯选路径的优先级；在第一路径为目标段列表的情况下，调整目标段列表的权重。
在本申请实施例中，由于头节点接收策略配置报文，该策略配置报文包括OAM配置信息和第一路径信息，第一路径信息用于标识第一路径，这样头节点可以根据该策略配置报文包括的OAM配置信息对第一路径进行OAM。如此对第一路径进行OAM时不需要确定在第一路径上传输的所有业务流，以及在头节点中配置每个业务流的标识信息，从而降低对第一路径进行OAM的难度，以及提高对第一路径进行OAM的效率。通过对第一路径进行OAM可以得到第一路径的性能，这样在第一路径的性能发生变化时，也能及时感知。头节点在对第一路径进行OAM时会获取到OAM数据报文，向控制器发送该OAM数据报文，这样控制器根据该OAM数据报文也能感知第一路径的性能变化。其中，控制器或头节点在感知到第一路径的性能不能满足SR Policy定义的性能需求信息时，可以对第一路径进行调整。例如，在第一路径为目标侯选路径的情况下，调整目标侯选路径的优先级；在第一路径为目标段列表的情况下，调整目标段列表的权重。
参见图16，本申请实施例提供了一种发送报文以进行OAM的装置300，所述装置300可以部署在上述任一实施例中的控制器上，例如可以部署在如图3所示实施例中的控制器上，包括：
处理单元301，用于生成策略配置报文，该策略配置报文包括OAM配置信息和第一路径信息，第一路径信息用于标识第一路径；
发送单元302，用于向第一路径的头节点发送该策略配置报文，该策略配置报文用于指示头节点根据OAM配置信息对第一路径进行OAM。
可选的，处理单元301获取生成策略配置报文的详细实现过程，可以参见图3所示实施例的步骤301中的控制器生成策略配置报文的相关内容。
可选的，策略配置报文为SR Policy配置报文，SR Policy配置报文包括候选路径的信息，该候选路径包括段列表，第一路径为该候选路径或者该段列表标识的路径。
可选的，SR Policy配置报文的结构，可以参见图3所示实施例的步骤301中的SR Policy配置报文的相关内容。
可选的，在第一路径为所述侯选路径的情况下，SR Policy配置报文还包括标识信息，该标识信息用于指示头节点，当该候选路径为活跃路径时，根据OAM配置信息对该候选路径进行OAM。
可选的，所述装置300还包括：
接收单元303，用于接收OAM数据报文，该OAM数据报文是通过对第一路径进行OAM而获得的。
可选的，策略配置报文为边界网关路由BGP报文或路径计算通信协议PCEP报文。
可选的，OAM配置信息包括OAM方式、OAM对象、OAM粒度或OAM频率中的至少一个。
可选的，OAM方式包括下述方式中的至少一种：带内操作维护管理IOAM方式、互联网协议流性能测量IPFPM方式、带内流信息测量IFIT方式、双向主动测量协议TWAMP方式、单向主动测量协议OWAMP方式以及PING方式。
在申请实施例中，处理单元生成策略配置报文，该策略配置报文包括OAM配置信息和第一路径信息，第一路径信息用于标识第一路径。发送单元向第一路径的头节点发送该策略配置报文，这样通过该策略配置报文用于指示头节点根据该OAM配置信息对第一路径进行OAM。如此对第一路径进行OAM时不需要确定在第一路径上传输的所有业务流，以及在头节点中配置每个业务流的标识信息，从而降低对第一路径进行OAM的难度，以及提高对第一路径进行OAM的效率。
参见图17，本申请实施例提供了一种接收报文以进行OAM的装置400，所述装置400可以部署在上述任一实施例中的头节点上，例如可以部署在如图15所示实施例中的头节点上，包括：
接收单元401，用于接收策略配置报文，该策略配置报文包括OAM配置信息和第一路径信息，第一路径信息用于标识第一路径；
处理单元402，用于根据该OAM配置信息对第一路径进行OAM。
可选的，处理单元402对第一路径进行OAM的详细实现过程，可以参见图15所示实施例的步骤202中的头节点对第一路径进行OAM的相关内容。
可选的，该策略配置报文为SR Policy配置报文，该SR Policy配置报文包括候选路径的信息，该候选路径包括段列表，第一路径为该候选路径或者该段列表标识的路径。
可选的，所述装置400还包括：发送单元403，
处理单元402，用于根据OAM配置信息获得OAM执行信息；
接收单元401，还用于接收第一报文；
处理单元402，还用于在第一报文中添加OAM执行信息以生成第二报文；
发送单元403，用于经过所述第一路径发送所述第二报文。
可选的，处理单元402获得OAM信息以及生成第二报文的详细实现过程，可以参见图 15所示实施例的步骤202中的头节点获得OAM信息以及生成第二报文的相关内容。
可选的，处理单元402，用于根据OAM配置信息生成第一报文，第一报文包括OAM执行信息；
发送单元403，用于经过第一路径发送第一报文。
可选的，处理单元402获得生成第一报文的详细实现过程，可以参见图15所示实施例的步骤202中的头节点生成第一报文的相关内容。
可选的，在所述第一路径为候选路径的情况下，处理单元402，用于获得标识信息，该标识信息用于指示处理单元402，当该候选路径为活跃路径时，根据该OAM配置信息对该候选路径进行OAM。
可选的，处理单元402，还用于通过对第一路径进行OAM而获得OAM数据报文；
发送单元403，用于向控制器发送OAM数据报文。
可选的，该策略配置报文为BGP报文或PCEP报文。
在本申请实施例中，接收单元接收策略配置报文，该策略配置报文包括OAM配置信息和第一路径信息，第一路径信息用于标识第一路径。处理单元根据该OAM配置信息对第一路径进行OAM。如此在对第一路径进行OAM时不需要确定在第一路径上传输的所有业务流，以及在所述装置中配置每个业务流的标识信息，从而降低对第一路径进行OAM的难度，以及提高对第一路径进行OAM的效率。
参见图18，本申请实施例提供了一种发送报文以进行OAM的装置500示意图。该装置500可以是上述任一实施例中的控制器，例如可以是如图3所示实施例中的控制器。该装置500包括至少一个处理器501，总线系统502，存储器503以及至少一个收发器504。
该装置500是一种硬件结构的装置，可以用于实现图16所述的装置300中的功能模块。例如，本领域技术人员可以想到图16所示的装置300中的处理单元301可以通过该至少一个处理器501调用存储器503中的代码来实现，图16所示的装置300中的发送单元302和接收单元303可以通过该收发器504来实现。
可选的，该装置500还可用于实现上述任一实施例中采集分析设备的功能。
可选的，上述处理器501可以是一个通用中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
上述总线系统502可包括一通路，在上述组件之间传送信息。
上述收发器504，用于与其他设备或通信网络通信。
上述存储器503可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器503用于存储执行本申请方案的应用程序代码，并由处理器501来控制执行。处理器501用于执行存储器503中存储的应用程序代码，从而实现本专利方法中的功能。
在具体实现中，作为一种实施例，处理器501可以包括一个或多个CPU，例如图16中的CPU0和CPU1。
在具体实现中，作为一种实施例，该装置500可以包括多个处理器，例如图16中的处理器501和处理器507。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
参见图19，本申请实施例提供了一种接收报文以进行OAM的装置600示意图。该装置600可以是上述任一实施例中的头节点，例如可以是如图15所示实施例中的头节点。该装置600包括至少一个处理器601，总线系统602，存储器603以及至少一个收发器604。
该装置600是一种硬件结构的装置，可以用于实现图17所述的装置400中的功能模块。例如，本领域技术人员可以想到图17所示的装置400中的处理单元402可以通过该至少一个处理器601调用存储器603中的代码来实现，图17所示的装置400中的接收单元401和发送单元403可以通过该收发器604来实现。
可选的，该装置600还可用于实现上述任一实施例中采集分析设备的功能。
可选的，上述处理器601可以是一个通用中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
上述总线系统602可包括一通路，在上述组件之间传送信息。
上述收发器604，用于与其他设备或通信网络通信。
上述存储器603可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器603用于存储执行本申请方案的应用程序代码，并由处理器601来控制执行。处理器601用于执行存储器603中存储的应用程序代码，从而实现本专利方法中的功能。
在具体实现中，作为一种实施例，处理器601可以包括一个或多个CPU，例如图19中的CPU0和CPU1。
在具体实现中，作为一种实施例，该装置600可以包括多个处理器，例如图19中的处理器601和处理器607。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
参见图20，本申请实施例提供了一种接收报文以进行OAM的系统700，所述系统700包括：如图16所示的装置300和如图17所述的装置400，或者，所述系统700包括：如图18所述的装置500和如图19所述的装置600。
可选的，参见图20，如图16所述的装置300或如图18所述的装置500可以为控制器701，如图17所述的装置400或如图19所述的装置600可以为头节点702。例如如图16所述的装置300或如图18所述的装置500可以是如图3所示实施例中的控制器，如图17所述的装置400或如图19所述的装置600可以是如图15所示实施例中的头节点。
可选的，该系统700还可以包括尾节点等其他网络设备。
以上所述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (29)

  1. 一种发送报文以进行OAM的方法，其特征在于，所述方法包括：
    控制器生成策略配置报文，所述策略配置报文包括操作维护管理OAM配置信息和第一路径信息，所述第一路径信息用于标识第一路径；
    所述控制器向所述第一路径的头节点发送所述策略配置报文，所述策略配置报文用于指示所述头节点根据所述OAM配置信息对所述第一路径进行OAM。
  2. 如权利要求1所述的方法，其特征在于，所述策略配置报文为段路由策略SR Policy配置报文，所述SR Policy配置报文包括候选路径的信息，所述候选路径包括段列表，所述第一路径为所述候选路径或者所述段列表标识的路径。
  3. 如权利要求2所述的方法，其特征在于，在所述第一路径为所述侯选路径的情况下，所述SR Policy配置报文还包括标识信息，
    所述策略配置报文用于指示所述头节点根据所述OAM配置信息对所述第一路径进行OAM，包括：
    所述标识信息用于指示所述头节点，当所述候选路径为活跃路径时，根据所述OAM配置信息对所述候选路径进行OAM。
  4. 如权利要求1至3任一项所述的方法，其特征在于，所述控制器向所述头节点发送所述策略配置报文之后，所述方法还包括：
    所述控制器接收OAM数据报文，所述OAM数据报文是通过对所述第一路径进行OAM而获得的。
  5. 如权利要求1至4任一项所述的方法，其特征在于，所述策略配置报文为边界网关路由BGP报文或路径计算通信协议PCEP报文。
  6. 如权利要求1至5任一项所述的方法，其特征在于，所述OAM配置信息包括OAM方式、OAM对象、OAM粒度或OAM频率中的至少一个。
  7. 如权利要求6所述的方法，其特征在于，所述OAM方式包括下述方式中的至少一种：带内操作维护管理IOAM方式、互联网协议流性能测量IPFPM方式、带内流信息测量IFIT方式、双向主动测量协议TWAMP方式、单向主动测量协议OWAMP方式以及PING方式。
  8. 一种接收报文以进行OAM的方法，其特征在于，所述方法包括：
    头节点接收策略配置报文，所述策略配置报文包括操作维护管理OAM配置信息和第一路径信息，所述第一路径信息用于标识第一路径；
    所述头节点根据所述OAM配置信息对所述第一路径进行OAM。
  9. 如权利要求8所述的方法，其特征在于，所述策略配置报文为段路由策略SR Policy配置报文，所述SR Policy配置报文包括候选路径的信息，所述候选路径包括段列表，所述第一路径为所述候选路径或者所述段列表标识的路径。
  10. 如权利要求8或9所述的方法，其特征在于，所述头节点根据所述OAM配置信息对所述第一路径进行OAM，包括：
    所述头节点根据所述OAM配置信息获得OAM执行信息；
    所述头节点接收第一报文；
    所述头节点在所述第一报文中添加所述OAM执行信息以生成第二报文；
    所述头节点经过所述第一路径发送所述第二报文。
  11. 如权利要求8或9所述的方法，其特征在于，所述头节点根据所述OAM配置信息对所述第一路径进行OAM，包括：
    所述头节点根据所述OAM配置信息生成第一报文，所述第一报文包括OAM执行信息；
    所述头节点经过所述第一路径发送所述第一报文。
  12. 如权利要求9所述的方法，其特征在于，在所述第一路径为所述候选路径的情况下，所述头节点获得标识信息；
    所述头节点根据所述OAM配置信息对所述第一路径进行OAM，包括：
    所述标识信息用于指示所述头节点，当所述候选路径为活跃路径时，根据所述OAM配置信息对所述候选路径进行OAM。
  13. 如权利要求8至12任一项所述的方法，其特征在于，所述方法还包括：
    所述头节点通过对所述第一路径进行OAM而获得OAM数据报文；
    所述头节点向所述控制器发送所述OAM数据报文。
  14. 如权利要求8至13任一项所述的方法，其特征在于，所述策略配置报文为边界网关路由BGP报文或路径计算通信协议PCEP报文。
  15. 一种发送报文以进行OAM的装置，其特征在于，所述装置包括：
    处理单元，用于生成策略配置报文，所述策略配置报文包括操作维护管理OAM配置信息和第一路径信息，所述第一路径信息用于标识第一路径；
    发送单元，用于向所述第一路径的头节点发送所述策略配置报文，所述策略配置报文用于指示所述头节点根据所述OAM配置信息对所述第一路径进行OAM。
  16. 如权利要求15所述的装置，其特征在于，所述策略配置报文为段路由策略SR Policy配置报文，所述SR Policy配置报文包括候选路径的信息，所述候选路径包括段列表，所述第一路径为所述候选路径或者所述段列表标识的路径。
  17. 如权利要求16所述的装置，其特征在于，在所述第一路径为所述侯选路径的情况下，所述SR Policy配置报文还包括标识信息，所述标识信息用于指示所述头节点，当所述候选路径为活跃路径时，根据所述OAM配置信息对所述候选路径进行OAM。
  18. 如权利要求15至17任一项所述的装置，其特征在于，所述装置还包括：
    接收单元，用于接收OAM数据报文，所述OAM数据报文是通过对所述第一路径进行OAM而获得的。
  19. 如权利要求15至18任一项所述的装置，其特征在于，所述策略配置报文为边界网关路由BGP报文或路径计算通信协议PCEP报文。
  20. 如权利要求15至19任一项所述的装置，其特征在于，所述OAM配置信息包括OAM方式、OAM对象、OAM粒度或OAM频率中的至少一个。
  21. 如权利要求20所述的装置，其特征在于，所述OAM方式包括下述方式中的至少一种：带内操作维护管理IOAM方式、互联网协议流性能测量IPFPM方式、带内流信息测量IFIT方式、双向主动测量协议TWAMP方式、单向主动测量协议OWAMP方式以及PING方式。
  22. 一种接收报文以进行OAM的装置，其特征在于，所述装置包括：
    接收单元，用于接收策略配置报文，所述策略配置报文包括操作维护管理OAM配置信息和第一路径信息，所述第一路径信息用于标识第一路径；
    处理单元，用于根据所述OAM配置信息对所述第一路径进行OAM。
  23. 如权利要求22所述的装置，其特征在于，所述策略配置报文为段路由策略SR Policy配置报文，所述SR Policy配置报文包括候选路径的信息，所述候选路径包括段列表，所述第一路径为所述候选路径或者所述段列表标识的路径。
  24. 如权利要求22或23所述的装置，其特征在于，所述装置还包括：第一发送单元，
    所述处理单元，用于根据所述OAM配置信息获得OAM执行信息；
    所述接收单元，还用于接收第一报文；
    所述处理单元，还用于在所述第一报文中添加所述OAM执行信息以生成第二报文；
    所述第一发送单元，用于经过所述第一路径发送所述第二报文。
  25. 权利要求22或23所述的装置，其特征在于，所述装置还包括：第一发送单元，
    所述处理单元，用于根据所述OAM配置信息生成第一报文，所述第一报文包括OAM执行信息；
    所述第一发送单元，用于经过所述第一路径发送所述第一报文。
  26. 如权利要求23所述的装置，其特征在于，在所述第一路径为所述候选路径的情况下， 所述处理单元，用于获得标识信息，所述标识信息用于指示所述处理单元，当所述候选路径为活跃路径时，根据所述OAM配置信息对所述候选路径进行OAM。
  27. 如权利要求22至26任一项所述的装置，其特征在于，所述装置还包括：第二发送单元；
    所述处理单元，还用于通过对所述第一路径进行OAM而获得OAM数据报文；
    所述第二发送单元，用于向所述控制器发送所述OAM数据报文。
  28. 如权利要求22至27任一项所述的装置，其特征在于，所述策略配置报文为边界网关路由BGP报文或路径计算通信协议PCEP报文。
  29. 一种接收报文以进行OAM的系统，其特征在于，所述系统包括如权利要求15至21任一项所述的装置和如权利要求22至28任一项所述的装置。
PCT/CN2020/117246 2019-11-14 2020-09-23 发送报文、接收报文以进行oam的方法、装置及系统 WO2021093465A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20888188.8A EP4044514A4 (en) 2019-11-14 2020-09-23 METHOD, DEVICE AND SYSTEM FOR TRANSMITTING PACKETS AND RECEIVING PACKETS FOR PERFORMING OAM
US17/743,915 US20220278904A1 (en) 2019-11-14 2022-05-13 Method, Apparatus, and System for Sending Packet and Receiving Packet to Perform OAM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911115441.5 2019-11-14
CN201911115441.5A CN112804075B (zh) 2019-11-14 2019-11-14 发送报文、接收报文以进行oam的方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/743,915 Continuation US20220278904A1 (en) 2019-11-14 2022-05-13 Method, Apparatus, and System for Sending Packet and Receiving Packet to Perform OAM

Publications (1)

Publication Number Publication Date
WO2021093465A1 true WO2021093465A1 (zh) 2021-05-20

Family

ID=75803895

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/117246 WO2021093465A1 (zh) 2019-11-14 2020-09-23 发送报文、接收报文以进行oam的方法、装置及系统

Country Status (4)

Country Link
US (1) US20220278904A1 (zh)
EP (1) EP4044514A4 (zh)
CN (2) CN115733720A (zh)
WO (1) WO2021093465A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110971445B (zh) * 2019-09-24 2021-06-01 华为技术有限公司 一种网络的oam方法及装置
CN113542123B (zh) * 2021-05-31 2022-11-29 网络通信与安全紫金山实验室 一种转发路径的确定方法及装置
CN113644998B (zh) * 2021-08-23 2023-06-09 烽火通信科技股份有限公司 一种5g网络的ioam时延测量方法和装置
WO2023184218A1 (zh) * 2022-03-30 2023-10-05 新华三技术有限公司 通过bgp下发随流检测配置的方法及装置
WO2023213216A1 (zh) * 2022-05-06 2023-11-09 华为技术有限公司 一种报文处理的方法及相关设备
CN117955861A (zh) * 2022-10-31 2024-04-30 华为技术有限公司 随流检测方法、装置及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1703013A (zh) * 2004-05-27 2005-11-30 阿尔卡特公司 为多播通信会话提供oam支持的网络管理系统和方法
US20060031480A1 (en) * 2000-07-24 2006-02-09 Sasa Nijemcevic Network management support for OAM functionality and method therefore
CN101355441A (zh) * 2007-07-27 2009-01-28 华为技术有限公司 一种配置操作管理维护属性的方法、系统及设备
CN102388567A (zh) * 2011-09-22 2012-03-21 华为技术有限公司 配置操作管理维护属性的方法和装置
US20120271928A1 (en) * 2009-10-15 2012-10-25 Telefonaktiebolaget Lm Ericsson (Publ) Network Connection Segment Monitoring
CN105790988A (zh) * 2014-12-23 2016-07-20 中兴通讯股份有限公司 操作维护管理功能的实现方法及装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651582B (zh) * 2009-09-24 2011-12-07 中兴通讯股份有限公司 检测多协议标签交换网络链路连通性的方法及系统
CA2715472A1 (en) * 2009-09-29 2011-03-29 Ceragon Networks Ltd. Path protection by sharing continuity check messages
JP5625494B2 (ja) * 2010-05-26 2014-11-19 富士通株式会社 伝送装置、制御情報設定方法及び制御情報設定プログラム
CN104639362A (zh) * 2013-11-15 2015-05-20 中兴通讯股份有限公司 Oam性能监控方法及装置
CN105577413B (zh) * 2014-10-17 2019-09-10 中兴通讯股份有限公司 操作、管理和维护oam报文处理方法及装置
CN105871721B (zh) * 2015-01-19 2020-05-05 中兴通讯股份有限公司 一种段路由处理方法、处理装置及发送装置
US9992056B2 (en) * 2015-10-20 2018-06-05 Cisco Technology, Inc. Triggered in-band operations, administration, and maintenance in a network environment
US10666506B2 (en) * 2017-05-12 2020-05-26 Futurewei Technologies, Inc. In-situ OAM trace type extension with cascade bitmap and segment in-situ OAM
CN108964943B (zh) * 2017-05-18 2022-01-28 中兴通讯股份有限公司 一种实现ioam封装的方法及装置
CN109218058B (zh) * 2017-07-06 2021-09-14 中国电信股份有限公司 Oam信息的获取方法、系统及计算机可读存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060031480A1 (en) * 2000-07-24 2006-02-09 Sasa Nijemcevic Network management support for OAM functionality and method therefore
CN1703013A (zh) * 2004-05-27 2005-11-30 阿尔卡特公司 为多播通信会话提供oam支持的网络管理系统和方法
CN101355441A (zh) * 2007-07-27 2009-01-28 华为技术有限公司 一种配置操作管理维护属性的方法、系统及设备
US20120271928A1 (en) * 2009-10-15 2012-10-25 Telefonaktiebolaget Lm Ericsson (Publ) Network Connection Segment Monitoring
CN102388567A (zh) * 2011-09-22 2012-03-21 华为技术有限公司 配置操作管理维护属性的方法和装置
CN105790988A (zh) * 2014-12-23 2016-07-20 中兴通讯股份有限公司 操作维护管理功能的实现方法及装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US20220278904A1 (en) 2022-09-01
CN112804075B (zh) 2022-10-11
EP4044514A4 (en) 2022-12-14
CN112804075A (zh) 2021-05-14
CN115733720A (zh) 2023-03-03
EP4044514A1 (en) 2022-08-17

Similar Documents

Publication Publication Date Title
WO2021093465A1 (zh) 发送报文、接收报文以进行oam的方法、装置及系统
US10917340B2 (en) In-situ passive performance measurement in a network environment
KR102569305B1 (ko) 데이터 메시지 검출 방법, 디바이스 및 시스템
EP2486706B1 (en) Network path discovery and analysis
US20220294722A1 (en) Transmission Quality Detection Method, Apparatus, and System, and Storage Medium
CN113411834B (zh) 报文处理方法、装置、设备及存储介质
WO2019184752A1 (zh) 网络设备的管理方法、装置及系统
US9001669B2 (en) Remote stitched directed acyclic graphs
CN111771359B (zh) 用于连接通信网络的方法和系统
WO2021169290A1 (zh) 配置性能探测指示信息的方法及相关设备
WO2021018155A1 (zh) 一种路由信息监控方法和装置
JP2011082834A (ja) コンピュータシステム、及びコンピュータシステムの監視方法
JPH10303961A (ja) ネットワークの監視方法と装置
US20160301571A1 (en) Method and Device for Monitoring OAM Performance
JP2004328752A (ja) Ｏａｍ機能を可能にするアドレスの挿入
US20220255862A1 (en) Packet forwarding method, device, storage medium, and system
US20220255857A1 (en) Packet Processing Method, Network Node, and System
US11477100B2 (en) Residence time measurement for traffic engineered network
KR20140106235A (ko) 오픈플로우 스위치 및 그 패킷 처리 방법
US11902133B2 (en) Network performance monitoring using an active measurement protocol and relay mechanism
US20230086487A1 (en) Method for Determining Processing Capability, Node, and System
WO2016192618A1 (zh) 收集访问控制列表的方法、装置及系统
WO2021224931A1 (en) System and a method to efficiently exchange echo and stats messages between sdn controller and the open vswitches
WO2022257854A1 (zh) 一种报文发布方法、转发路径处理方法及装置
CN105765903A (zh) 一种拓扑发现方法及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20888188

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020888188

Country of ref document: EP

Effective date: 20220511

NENP Non-entry into the national phase

Ref country code: DE