Multi-hop physical layer data collection protocol

By combining request/response message exchange with the third-level and fourth-level protocols, the multi-hop network path link configuration problem is solved, and comprehensive data collection and link configuration of physical layer attributes is realized, ensuring network equipment communication security and reliability.

CN118984346APending Publication Date: 2024-11-19HEWLETT PACKARD ENTERPRISE DEV LP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411058528.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-09-25
Filing Date
2020-12-17
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

The prior art is difficult to ensure that each physical link in a multi-hop network path is properly configured, resulting in an endpoint device not being able to effectively rely on physical link characteristics, especially when devices are spaced multiple hops apart.

Method used

By combining the third and fourth level protocols, request/response message exchanges to collect physical layer parameters or attribute values, traverse along the multi-hop network path and add local attribute values ​​to the request, the target endpoint generates response messages containing the collected Attribute value.

Benefits of technology

A more comprehensive data collection for multi-hop network paths is achieved, ensuring the correct configuration and security of link attributes, and enhancing the communication reliability between network devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118984346A_ABST
    Figure CN118984346A_ABST
Patent Text Reader

Abstract

Relates to a multi-hop physical layer data collection protocol. The disclosed embodiments utilize Layer 3 and / or Layer 4 protocols to collect physical layer attributes along a multi-hop network path between a source node and a target node. The use of Layer 3 or Layer 4 protocols provides the ability to span multiple links or networks between a source node and a target node while also collecting physical layer attributes. Once physical layer properties along a network path may be understood, decisions related to the configuration of the network path and / or whether to communicate via the network path are improved.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Divisional Application Instructions

[0002] This application is a divisional application of the Chinese invention patent application with an application date of December 17, 2020, a priority date of September 25, 2020, an application number of 202011497956.9, and a name of “Multi-hop physical layer data collection protocol”. Technical Field

[0003] The present application relates to the field of network communications, and more particularly to a multi-hop physical layer data collection protocol. Background Art

[0004] Encryption and synchronization functions are typically implemented at the physical network layer. However, this solution relies on an unbroken chain of secure links between two devices in network communication with each other. In order to ensure the security of communications that rely on encryption and / or synchronization at the link level, it is important to verify that such communications are in place before performing said communications. Summary of the invention

[0005] A method performed by a network device, the method comprising: receiving a packet at the network device and via a network link; decoding the packet; identifying a message included in the packet based on the decoding; decoding the message; identifying a request for a first layer or second layer (L1 or L2) attribute of the network link via the decoding of the message; appending the value of the requested L1 or L2 attribute of the network link to the L1 or L2 attribute portion of the packet; appending the address of the network device to the packet; associating the address with the value in the packet; identifying a target address of the packet based on the packet; and forwarding the appended packet to the target address in response to the target address being different from a local address of the network device.

[0006] A system comprises: a hardware processing circuit; and one or more hardware memories storing instructions, wherein when the instructions are executed, the hardware processing circuit is configured to perform the following operations: receiving a packet at a network device and via a network link; decoding the packet; identifying a message included in the packet based on the decoding; decoding the message; identifying a request for a first layer or second layer (L1 or L2) attribute of the network link via the decoding of the message; appending the value of the requested L1 or L2 attribute of the network link to the L1 or L2 attribute portion of the packet; appending the address of the network device to the packet; associating the address with the value in the packet; identifying a destination address of the packet based on the packet; and forwarding the appended packet to the destination address in response to the destination address being different from a local address of the network device.

[0007] A non-transitory computer-readable storage medium comprising instructions which, when executed, configure a hardware processing circuit to perform the following operations: receiving a packet at a network device and via a network link; decoding the packet; identifying a message included in the packet based on the decoding; decoding the message; identifying a request for a layer 1 or layer 2 (L1 or L2) attribute of the network link via the decoding of the message; appending the value of the requested L1 or L2 attribute of the network link to the L1 or L2 attribute portion of the packet; appending the address of the network device to the packet; associating the address with the value in the packet; identifying a destination address of the packet based on the packet; and forwarding the appended packet to the destination address in response to the destination address being different from a local address of the network device. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is an overview diagram of a network in which one or more disclosed embodiments are implemented.

[0009] Figure 2 is an example network protocol stack in which each layer of the network protocol stack is identified relative to the ISO network model.

[0010] Figure 3 is an example format of an ICMP message.

[0011] Figure 4 An example third level protocol header is shown.

[0012] Figure 5 is an example LSP-ping packet.

[0013] Figure 6 An example level 4 protocol header is shown.

[0014] Figure 7 is a flow diagram of an example method performed by one or more disclosed embodiments.

[0015] Figure 8 is a flow diagram of an example method performed by one or more disclosed embodiments.

[0016] Fig. 9 Illustrated is a block diagram of an example machine upon which any one or more of the techniques (eg, methodologies) discussed herein may be performed. DETAILED DESCRIPTION

[0017] Embodiments for collecting physical layer link properties across a network path that includes multiple network devices are disclosed. While the physical layer maintains information that is important for ensuring secure communications, the physical layer does not provide for communications across multiple network links. As a result, it may be difficult to determine the configuration and / or property settings of the physical network layer of a network device, particularly where the network device is multiple hops away from a device attempting to determine the state of the device. As a result, the technical problem results in that it may be difficult to ensure that each physical link of a multi-hop network path is properly configured, thereby preventing endpoint devices from effectively relying on physical link characteristics that may otherwise be beneficial.

[0018] The disclosed embodiments provide a technical solution to the technical problem by combining the use of a third-level protocol and / or a fourth-level protocol to provide a traversal of a multi-hop network path between two endpoint devices that communicate with each other. The third-level protocol and / or the fourth-level protocol are combined with a request / response message exchange that facilitates the collection of physical layer (e.g., first and / or second levels of the Open Systems Interconnection (OSI) model) parameters or attribute values. When a request travels along a multi-hop network path, one or more devices included in the path add their local attribute values ​​to the request itself based on the request. When the request reaches the target endpoint, the target endpoint generates a response message that includes all physical layer attribute values ​​collected from other devices.

[0019] Figure 1 is an overview of a network in which one or more disclosed embodiments may be implemented. Figure 1A source device 102 is shown. The source device is connected to a target device 104 via a network 103. Communication between the source device 102 and the target device 104 is accomplished via a plurality of devices included within the network 103. These devices include a server 107, a router 108, a router 110, and a router 112. The plurality of devices within the network 103 provide at least two different network paths between the source device 102 and the target device 104. For example, network traffic may travel from the server 107 to the router 106, to the router 112, to the target device 104 via a first path. Alternatively, network traffic may travel from the server 107 to the router 106, to the router 108, to the router 110, and then to the target device 104 via a second path. A third path from the source device 102 to the target device 104 includes the server 107, the router 106, the router 108, the router 110, the router 112, and then to the target device 104. A fourth path from source device 102 to target device 104 includes server 107 , router 106 , router 112 , router 110 , and then to target device 104 .

[0020] The disclosed embodiments recognize that it may be useful to understand the conditions at the link or physical layer at each device within a network path between two devices, such as a source device 102 and a target device 104. Thus, for example, for the first path discussed above, it may be useful to understand one or more first (1) level or second (2) level parameters of links 122, 124, 130, and 134 that connect the devices comprising the first path as described above. Similarly, if network traffic between the source device 102 and the target device 104 is traversing the second path, it may be useful to understand the link status for links 122, 126, 128, 132, and 136. Thus, the disclosed embodiments utilize a third level and / or fourth level protocol to traverse the network path between the source device 102 and the target device 104. The request for the first (1) level and / or second (2) level parameters is initiated by the source device 102 and the network path to the target device is traversed via the third level or fourth level protocol. When the request is received and processed by one or more devices included in the network path, these network devices add information related to the local values ​​of the requested first-level and / or second-level parameters to the request message. The request is then forwarded along the network path to the target. In at least some embodiments, upon reaching the target, the target device 104 also adds its local first-level and / or second-level parameters to a portion of the request. A response message is then generated by the target device 104, wherein the response message includes the following portion of the request: the portion indicates the value of the requested attribute collected along the network path. The response message is then delivered to the original source device via the same third-level and / or fourth-level protocol used to deliver the request to the target. Using the third-level and / or fourth-level protocol to collect the first-level and / or second-level attributes along the network path enables more comprehensive data collection of the first-level and / or second-level attributes than using the first-level and / or second-level protocols alone, because these protocols are generally unable to traverse multiple different first-level and / or second-level links. The first-level and / or second-level attribute values ​​that may be requested through the disclosed embodiments include, but are not limited to, an attribute indicating whether media access control (MAC) security (MACSec) is enabled, an attribute indicating whether synchronous Ethernet (SyncE) is enabled, an attribute indicating whether precision time protocol (PTP) is enabled, an attribute indicating whether optical transport network (OTN) security is enabled, an attribute indicating a maximum transmission data unit (MTU) size, an attribute indicating a synchronization state of a network device, or an attribute indicating a first-level or second-level characteristic of a network device.

[0021] Figure 2is an example network protocol stack, wherein each layer of the network protocol stack is identified relative to the ISO network model. At the bottom of the stack is the physical layer 202, which corresponds to the physical and / or data link layer in the ISO model. The Internet Protocol (IP) 204 resides at the network layer of the ISO model. In the ISO model, the network layer is considered to be "layer 3". The network layer provides a means for transmitting variable length data from one node to another node connected via one or more networks. In this context, a network is a physical medium that connects many nodes. Each node within a network has a unique address that identifies the node within the network. The protocols included in the network layer include routing protocols, multicast group management, network layer information and errors, and network layer address assignment.

[0022] The User Datagram Protocol (UDP) 206 and the Transmission Control Protocol (TCP) 208 are two examples of transport layer protocols. The transport layer protocols are considered as the fourth layer protocols within the ISO model. Some transport layer protocols such as the TCP protocol 208 provide reliable and ordered end-to-end data delivery. In at least some embodiments, this is achieved by explicitly confirming each byte of the transmitted data via a sequence number that identifies each byte. In some embodiments, the transport layer segments the data message into multiple parts and retransmits those segments for which the confirmation has not been received. Other transport layer protocols such as the UDP protocol 206 do not ensure reliable delivery. The OSI model defines five categories of transport protocols, labeled TP0...TP4. The classification is based on the presence or absence of various features, such as segmentation and reassembly, error recovery, retransmission, flow control, etc.

[0023] Figure 2 It is also illustrated that a network basic input output system (netbios) protocol 210 and / or a socket protocol 212 are included in the session layer of ISO. The ISO presentation layer includes, for example, an ASCII layer 214 or a secure socket layer 216. The ISO application layer includes, for example, a hypertext transfer protocol (HTTP) 222, a domain name service protocol 220, and a label switched path (LSP)-ping protocol 218. Figure 2 It is further illustrated that the IP protocol 204 includes a protocol known as the Internet Control Message Protocol (ICMP). For links within the network path between the source device and the destination device, some of the disclosed embodiments utilize layer 3 protocols (e.g., the IP protocol 204, and in particular the ICMP protocol 224) to collect information related to layer 1 or layer 2 of the ISO model (e.g., information related to the physical layer 202). For links within the network path between the source device and the destination device, some of the disclosed embodiments utilize layer 4 protocols (e.g., the TCP protocol 208 or the UDP protocol 206) to collect information related to layer 1 or layer 2 of the ISO model.

[0024] Figure 3 is an example format of an ICMP message. Example ICMP message 300 includes a type field 302, a code field 304, a checksum field 306, and a type-specific data field 308. Some embodiments define a specific value of type field 302 to indicate that ICMP message 300 is a request for first (1) level and / or second (2) level parameters at each node receiving example ICMP message 300. Some embodiments define a specific value of code field 304 to indicate that ICMP message 300 is a request for first (1) level and / or second (2) level parameters at each node receiving example ICMP message 300. Some embodiments define a second specific value of code field 304 to indicate that ICMP message 300 is a response to a previous request for first (1) level and / or second (2) level parameters at each node.

[0025] For example, some embodiments define an extended echo request (type value is 42) to indicate a request for first (1) level and / or second (2) level parameters. In at least some of these embodiments, a response to an extended echo request is indicated via a type value of 43. Other embodiments define alternative values ​​for requests and responses for first (1) level and / or second (2) level parameters. For example, at the time of this writing, values ​​between 44 and 252 are unassigned. Therefore, some embodiments select from unassigned identifiers to identify request / response messages that are the subject of the present disclosure.

[0026] Some embodiments utilize ICMP extended object classes and class subtypes to identify requests or responses for first (1) level and / or second (2) level parameter values. For example, some embodiments encode requests and / or responses in an interface information object. (Class 2).

[0027] Some embodiments store an indication of a first (1) level or second (2) level parameter of the requested node in the type-specific data field 308. Some example first (1) level or second (2) level parameters requested by the example ICMP message 300 include an attribute indicating whether Media Access Control (MAC) Security (MACSec) is enabled, an attribute indicating whether Precision Time Protocol (PTP) is enabled, an attribute indicating whether Optical Transport Network (OTN) security is enabled, an attribute indicating whether Synchronous Ethernet (SyncE) is enabled, or an attribute indicating a Maximum Transmission Data Unit (MTU) size.

[0028] Figure 3An example format of an ICMP data field 310 is illustrated. The ICMP data field 310 is shown to include two parts. A first request portion 312 defines which first-level or second-level parameters are requested by the example ICMP message 300. The example first request portion 312 illustrates the use of XML to provide a list of requested parameters. In the illustrated embodiment, the example message requests a first attribute 316 indicating whether MACSec is enabled, a second attribute 318 indicating whether PTP is enabled, and a third attribute 320 indicating whether synchronous Ethernet is enabled.

[0029] The second portion 314 defines data associated with a specific node along a network path between a source device that originally generated the example ICMP message 300 and a destination device that is identified by a destination IP address of an IP protocol header that encapsulates the ICMP message 300. Each node along the path adds a node entry 322 to the second portion 314. The node entry 322 defines the attributes requested by the first request portion 312. For example, the example node entry 322 illustrates a value for an attribute 324 that is enabled for MACSec, a value for an attribute 326 that is enabled for PTP, and a value for a SyncE attribute 328. The node entry 322 also identifies the node that provides the requested attribute value. In at least some embodiments, the node is identified by the node's IP address. Some embodiments may use a station address or other unique identifier to identify the node. Note that as the example ICMP message 300 travels along a network path between a source device (e.g., source device 102) to a destination device (e.g., destination device 104), each node within the network path, or at least some of the nodes within the network path, is appended with an additional second portion 314 that identifies the corresponding node via an XML element 330 and includes parameter values ​​specific to the corresponding node.

[0030] In some example embodiments, a device within a network path between a source node and a target node adds a node entry 322 to an ICMP message, wherein the added or attached node entry indicates one or more attribute values ​​requested. Thus, the collection of added or attached node entries represents a collective response to a request along a network path, wherein the collective response aggregates attribute values ​​from one or more network devices along the network path. Thus, for example, if three attribute values ​​are requested by a request, and there are five (5) network devices along the network path between the source device and the target device, the response message to the request includes up to fifteen attribute entries, wherein each attribute entry defines a separate attribute value from one of the five devices. This is just one example, but typically, as the request moves along a network path from a source device to a target, the request aggregates attribute values, and the response message includes this aggregation of attribute values, and provides these values ​​back to the source device.

[0031] Figure 4 An example level 3 protocol header is shown. Figure 4 The example of FIG. 400 shows an Internet Protocol (IP) header. The IP header 400 includes a version field 402, an Internet header length (IHL) field 404, a type of service (TOS) field 406, a total length field 408, an identification field 410, a flag field 417, a fragment offset field 418, a time to live (TTL) field 412, a protocol field 412, a header checksum field 420, a source address field 414, and a destination address field 416, an option field 422, and a data field 424. Note that Figure 4 The example IP header 400 is an IP v4 header. Some embodiments utilize an IP version 6 header (not shown).

[0032] Figure 5 5 is an example LSP-ping message 500. The example LSP-ping message 500 is encapsulated in a TCP or UDP protocol header by at least some of the disclosed embodiments. The example LSP-ping message 500 includes a version number field 502, a global flag field 504, a message type field 506, a reply mode field 508, a return code field 510, a return subcode field 512, a sender handle field 514, a sequence number field 516, a timestamp field 518 sent in seconds, a timestamp field 520 sent in microseconds, a timestamp field 522 received in seconds, a timestamp field 524 received in microseconds, and a type-length-value (TLV) field 526.

[0033] The TLV field 526 includes zero or more TLVs, two examples of which are shown as TLVs 528 and 530. Each TLV includes a type field 532, a length field 534, and a value field 536.

[0034] Consistent with at least RFC 4379, LSP-ping and traceroute utilize the reply mode field 508 to signal that the LSP-ping message 500 is for a Multi-Protocol Label Switching (MPLS) echo request. In at least some embodiments, a predefined value of one (1) has been assigned to indicate identical. The LSP-ping message 500 may also be used to indicate an MPLS echo reply using a predefined value of two (2).

[0035] Some of the disclosed embodiments define new values ​​for the reply mode field 508. For example, in some embodiments, the new first predefined value indicates an enhanced MPLS echo request, and in some embodiments, an enhanced MPLS echo reply is indicated in the second predefined value. The enhanced MPLS echo request and reply provide the ability to collect first level and / or second level attribute values ​​from the link layer of devices within the network path between a source device and a destination device as the MPLS echo request propagates along a network path (e.g., via the IP protocol). The enhanced MPLS echo request and enhanced MPLS echo reply define additional TLVs that complete the collection of first level and / or second level attribute values.

[0036] Some of the disclosed embodiments define a first predefined type field value for the type field 532, the type field 532 defining a request for a first (1) level or second (2) level attribute value. For example, using the above example of a first level or second level attribute, the first predefined type field value requests an attribute indicating whether MACSecis is enabled, the second predefined type field value requests an attribute indicating whether PTP is enabled, or the third predefined type field value requests an attribute indicating whether Synchronous Ethernet (SyncE) is enabled. In some other embodiments, the type field 532 value indicates a request for a first level or second (2) level attribute, the specific attribute requested being indicated in the value field 536. Some of the disclosed embodiments decode a TLV included in an LSP-ping packet (such as, the example LSP-ping message 500) to identify a request for a first level or second level attribute value.

[0037] In some embodiments, a device within a network path between a source node and a target node adds a TLV to an LSP-ping packet, wherein the added or attached TLV indicates the requested value. Thus, the set of added or attached TLV entries represents a collective response to a request along the network path, wherein the collective response aggregates responses from one or more network devices along the network path. Thus, for example, if three attribute values ​​are requested by a request, and there are five (5) network devices along the network path between the source device and the target device, the response message to the request includes up to fifteen TLV entries, wherein each TLV entry defines a separate attribute value from one of the five devices. This is just one example, but typically, as the request moves along the network path from the source device to the target, the request aggregates attribute values, and the response message includes this aggregation of attribute values, and provides these values ​​back to the source device.

[0038] For example, continuing the above example, some embodiments define a fourth type of field value indicating that an attribute value is defined by a TLV, wherein the attribute value indicates whether MACSec is enabled at the node to which the attribute value is added. The value field 536 of the corresponding TLV then defines at least the provided attribute value and the identification of the node providing the attribute value (e.g., via the IP address, station address, or other unique identifier of the node). The example value field format is shown as value field 538. The example value field 538 utilizes XML format to define the identification 540 (shown as "X") of the node providing the attribute value and the value 542 (shown as "Y") of the attribute. The example value field 538 is merely an example, and other methods of defining attribute values ​​and node identifications are not beyond the scope of the disclosed embodiments.

[0039] Figure 6 An example format of a level 4 protocol header is shown. Figure 6 UDP header 600 is a User Datagram Protocol (UDP) header. UDP header 600 includes a source port field 602, a destination port field 604, a length field 606, a checksum field 608, and a variable length payload data field 610. In some embodiments, a packet having a UDP header such as UDP header 600 will be in a packet such as the one described above with respect to Figure 4 In some embodiments, the protocol field 413 indicates that a UDP protocol header is included in the packet (e.g., a predefined value of seventeen (17) indicates that a UDP header is present in the IP packet, while a predefined value of six (6) indicates that a TCP header is present in the IP packet). In some embodiments, the data field 610 stores substantially the same information as described above with respect to Figure 5 The LSP-ping message 500 discussed is consistent with the data.

[0040] Figure 7 is a flowchart of an example method performed by one or more of the disclosed embodiments. Figure 7 One or more operations discussed are performed by hardware processing circuitry. For example, in some embodiments, a hardware processor (e.g., hardware processor 902 discussed below) is configured by instructions (e.g., instructions 924 discussed below) stored in a memory (e.g., memory 904 and / or 906) to perform the following operations with respect to Figure 7 and one or more operations discussed in method 700.

[0041] After starting operation 705, method 700 moves to operation 710. In operation 710, a first packet is received via a network link. For example, Figure 1Each of the network devices (such as server 107, router 106, router 108, router 110, and target device 104) receives the packet via link 122, 124, 126, 128, or 136, respectively.

[0042] In operation 720, the packet is decoded. In some embodiments, the third layer or fourth layer protocol header of the received first packet is decoded. Decoding the first packet may include parsing the fields in the first packet to explain the meaning of the first packet. For example, in some embodiments, operation 720 includes identifying the first packet as an ICMP message (e.g., by parsing the IP protocol header included in the first packet). In some embodiments, operation 720 includes decoding a TCP header or a UDP header. For example, in some embodiments, the first packet includes an IP header specifying that the first packet includes a TCP header or a UDP header. Operation 720 then provides the first packet to a code module or other instructions to further parse and decode the identified header.

[0043] In operation 730, the message is identified based on the decoding. For example, in an embodiment of identifying an ICMP message, an ICMP message (e.g., having at least Figure 3 In an embodiment where the layer 4 protocol header is decoded, operation 730 detects an LSP-ping message, such as the one described above with reference to FIG. Figure 5 Example LSP-ping message 500 discussed. In some embodiments, the service access point field in the fourth level header indicates a destination port for the first packet, wherein the destination port is managed by the LSP-ping application. Thus, in these embodiments, the LSP-ping application receives the first packet from, for example, a UDP protocol or a TCP protocol.

[0044] Operation 740 decodes the message identified in operation 730. For example, in an embodiment where an ICMP message is received, the ICMP message is decoded. For example, similar to the above description of Figure 3 The ICMP header of the example ICMP header discussed is decoded to identify the values ​​in the type field 302 and / or the code field 304. In embodiments that receive an LSP-ping message, one or more fields of the example LSP-ping message 500 are decoded to determine their values. For example, in some embodiments, the reply mode field 508 is decoded to determine that it indicates that the message is an enhanced MPLS echo request.

[0045] Operation 750 decodes the message to identify a request for a layer 1 or layer 2 attribute of a network link (e.g., a link on which the first packet is received). As described above, some embodiments encode the request in an ICMP message, while some other embodiments encode the request in an LSP-ping message. Some other embodiments encode the request in a different layer 3 or layer 4 protocol.

[0046] Operation 760 appends information to the first packet. The information indicates the value of the requested L1 or L2 attribute. For example, as described above, in embodiments utilizing an ICMP message for the request, in at least some of these embodiments, the value of the requested L1 or L2 attribute is encoded in the ICMP data field 310 of the ICMP message. For example, Figure 3 An example of encoding one or more requested attribute values ​​in an ICMP message is shown. Some embodiments of method 700 encode one or more requested attribute values ​​consistent with this example. Some other embodiments encode one or more requested attribute values ​​consistent with this example. Figure 3 Some other embodiments, such as embodiments receiving LSP-ping messages, may encode one or more requested attribute values ​​in different ways. Figure 5 The example encodings shown and discussed in the corresponding description consistently encode the requested attributes.

[0047] Operation 770 associates the address of the executing device with the attribute value included in the first packet by operation 760. In some embodiments, the address of the executing device is an Internet Protocol (IP) address (v4 or v6 address). Figure 3 As discussed, some embodiments utilizing ICMP messages associate the device's identification with the device's requested attribute value via XML element 330. Some other embodiments associate the device's identification with the device's requested attribute value via an XML element including identification 540 and value 542. Some other embodiments associate the device's identification with the device's requested attribute value via an XML element including identification 540 and value 542. Figure 3 or Figure 5 Another way not shown in FIG. 1 is to associate a device identification with a property value.

[0048] Operation 780 identifies a destination address of the first packet based on the first packet. In some embodiments, the destination address is an IP address. In some other embodiments, the destination address is a station address. For example, some embodiments parse the IP header of the first packet to identify the destination IP address specified in the destination address field of the IP header.

[0049] In operation 790, the first packet is processed based on the target address. In some embodiments, if the target address identifies an executing device, then the target address indicating that the device is executing method 700 is a target address for a request for a first (1) level or second (2) level attribute value. In some embodiments, if the target address is equal to an IP address of the executing device, then the device executing method 700 is the target device.

[0050] Therefore, in this case, operation 790 generates a new second packet, and the second packet interchanges the IP address of the first packet (the source IP becomes the target IP of the second packet, and the target IP of the first packet becomes the source IP of the second packet). The portion of the first packet that includes the L1 or L2 attributes is also copied from the first packet to the second packet. The second packet is then transmitted to the IP address specified in its target IP header field. Note that in the case where the execution device is the target device for the first packet, the first-level and / or second-level attribute values ​​of the execution device do not have to be added to the first packet as described above, but are only added to the second packet, which is then transmitted to the device identified by the source address field of the first packet.

[0051] In some embodiments, the destination address of the first packet does not identify an execution device. In these cases, operation 790 forwards the first packet including the additional information to the destination specified in the first packet. After operation 790 is completed, method 700 moves to end operation 795.

[0052] Figure 8 is a flowchart of an example method performed by one or more of the disclosed example embodiments. Figure 8 One or more operations discussed are performed by hardware processing circuitry. For example, in some embodiments, a hardware processor (e.g., hardware processor 902 discussed below) is configured by instructions (e.g., instructions 924 discussed below) stored in a memory (e.g., memory 904 and / or 906) to perform the following operations with respect to Figure 8 and one or more operations discussed in connection with method 800. In some embodiments, method 800 comprises the steps described above with respect to Figure 1 The source device 102 in question is used for execution.

[0053] After starting operation 805, method 800 moves to operation 810, in which message data is generated. The message data indicates a request for a value of a first layer or second layer attribute. Figure 3As discussed, some embodiments generate an ICMP message. In some embodiments, the ICMP message is generated to indicate a request for a value for a layer 1 and / or layer 2 attribute. For example, as described above, some embodiments set the type field 302 and / or the code field 304 to indicate that the ICMP message is a request for a layer 1 and / or layer 2 attribute. Figure 3 As discussed, some embodiments generate the message data to include data fields similar to the ICMP data field 310, and in some embodiments include data requesting one or more attributes, including first level and / or second level attributes.

[0054] Some embodiments generate the message data as an LSP-ping message, such as the one described above with reference to Figure 5 Example LSP-ping message discussed. In some embodiments, the reply mode field 508 is set to a predefined value indicating that the LSP-ping message includes a request for attributes, including first level and / or second (2) level attributes.

[0055] In operation 815, the message data is encapsulated within a layer 3 or layer 4 protocol header. For example, as discussed above, in embodiments where the request is encoded in an ICMP message, the ICMP message is encoded within an IP header (layer 3 header). In embodiments where an LSP-ping is utilized to encode the request, the LSP-ping message is encapsulated within a TCP or UDP header (e.g., a layer 4 header) in some embodiments.

[0056] In operation 820, the packet is transmitted. The packet includes a layer 3 or layer 4 protocol header and an encapsulated message. The packet is transmitted to a target device. For example, in some embodiments, an IP header (e.g., IP header 400) identifies a target address via an address in a target address field (e.g., field 416) of the IP header.

[0057] Operation 825 receives a second packet from the target device. Figure 1 As discussed, source device 102 receives a response message from target device 104 .

[0058] The layer 3 or layer 4 protocol header is decoded from the received second packet (see operation 830). For example, some embodiments decode the ICMP message (such as the one described above with respect to Figure 3 Some other embodiments decode the UDP protocol header (such as the example ICMP message 300 discussed above). Figure 6 The example UDP header 600 discussed above is decoded.

[0059] Thereafter, in operation 835, the second message data is identified based on the decoding of operation 830. For example, in some embodiments, the second message data is decoded from the ICMP data field 310 of the ICMP message. Some other embodiments decode the second message data from the TLV field 526 of the example LSP-ping message 500.

[0060] In operation 840, a response to the request is decoded from the second message data. For example, in some embodiments, the response is encoded with the same Figure 3 The second portion 314 of the discussion is formatted in a similar manner. In some other embodiments, the request is received from Figure 5 Data formatted in a manner similar to the example response shown in field 538 (eg, including an example XML entry, the example XML entry, for example, including an identifier 540 and a value 542) is decoded.

[0061] As shown in operation 845, one or more L1 or L2 attribute values ​​of the corresponding one or more network devices are decoded from the response. For example, in some embodiments, operation 845 parses or otherwise decodes the ICMP data field 310 to identify the L1 and / or L2 attribute values. In some embodiments utilizing LSP-ping to request the L1 and / or L2 attribute values, operation 845 decodes the TLV included in the TLV field 526. For example, in some embodiments, operation 845 decodes the TLV included in the TLV field 526 according to the above description of Figure 5 The description of field 538 discussed above is used to operate.

[0062] Once the attribute value is decoded, some embodiments display the attribute value on a display screen or include the attribute value in a report. Some embodiments change the network configuration based on the determined attribute value. For example, in some embodiments, method 800 generates one or more configuration messages, and one or more configuration messages are used to change the first and / or second level attributes of the network device in the network path to improve performance and / or reliability. After operation 845 is completed, method 800 moves to end operation 850.

[0063] Fig. 9 A block diagram of an example machine 900 is illustrated on which any one or more of the techniques (e.g., methodologies) discussed herein may be performed. The machine 900 (e.g., a computer system) may include a hardware processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 904, and a static memory 906, some or all of which may communicate with each other via an interconnection link 908 (e.g., a bus).

[0064] Specific examples of main memory 904 include random access memory (RAM) and semiconductor memory devices, which in some embodiments may include storage locations in a semiconductor such as registers. Specific examples of static memory 906 include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.

[0065] The machine 900 may also include a display device 910, an input device 912 (e.g., a keyboard), and a user interface (UI) navigation device 914 (e.g., a mouse). In one example, the display device 910, the input device 912, and the UI navigation device 914 may be a touch screen display. The machine 900 may additionally include a mass storage device (e.g., a drive unit) 916, a beacon signal generating device 918, a network interface device 920, and one or more sensors 921 (such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors). The machine 900 may include an output controller 928, such as a serial (e.g., universal serial bus (USB), parallel or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with one or more peripheral devices (e.g., printers, card readers, etc.) or control one or more peripheral devices. In some embodiments, the hardware processor 902 and / or the instruction 924 may include a processing circuit and / or a transceiver circuit.

[0066] The mass storage device 916 may include a machine-readable medium 922 on which is stored a collection of one or more data structures or instructions 924 (e.g., software) embodied or utilized by any one or more of the techniques or functionality described herein. In at least some embodiments, the machine-readable medium 922 is a non-transitory computer-readable storage medium. The instructions 924 may also reside, completely or at least partially, within the main memory 904, within the static memory 906, or within the hardware processor 902 during execution of the instructions by the machine 900. In one example, one or any combination of the hardware processor 902, the main memory 904, the static memory 906, or the mass storage device 916 may constitute a machine-readable medium.

[0067] Specific examples of machine-readable media may include: nonvolatile memory, such as semiconductor memory devices (e.g., EPROM or EEPROM) and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.

[0068] Although machine-readable medium 922 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (eg, a centralized or distributed database and / or associated caches and servers) configured to store instructions 924 .

[0069] The apparatus of the machine 900 may be one or more of the following: a hardware processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), one or more hardware memories (including one or more of a main memory 904 and a static memory 906). In some embodiments, the apparatus of the machine 900 also includes one or more sensors 921, a network interface device 920, one or more antennas 960, a display device 910, an input device 912, a UI navigation device 914, a mass storage device 916, instructions 924, a beacon signal generating device 918, and an output controller 928. The apparatus may be configured to perform one or more methods and / or operations disclosed herein. The apparatus may be intended to be a component of the machine 900 to perform one or more methods and / or operations disclosed herein, and / or to perform a portion of one or more methods and / or operations disclosed herein. In some embodiments, the apparatus may include a pin or other means for receiving power. In some embodiments, the apparatus may include power regulation hardware.

[0070] The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions executed by the machine 900 and causing the machine 900 to perform any one or more of the techniques of the present disclosure or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memory and optical and magnetic media. Specific examples of machine-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, the machine-readable medium may include non-transitory machine-readable media. In some examples, the machine-readable medium may include machine-readable media that is not a transient propagation signal.

[0071] The instructions 924 may also be transmitted or received over a communication network 926 using a transmission medium via the network interface device 920 using any of a variety of transmission protocols (e.g., frame relay, Internet Protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, and a wireless data network (e.g., a wireless network known as a wireless network). The Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, known as IEEE 802.16 series of standards), IEEE 802.15.4 series of standards, Long Term Evolution (LTE) series of standards, Universal Mobile Telecommunications System (UMTS) series of standards, peer-to-peer (P2P) networks, etc.

[0072] In one example, the network interface device 920 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 926. In one example, the network interface device 920 may include one or more antennas 960 to use at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology for wireless communication. In some examples, the network interface device 920 may use multi-user MIMO technology for wireless communication. The term "transmission medium" should be deemed to include any intangible medium capable of storing, encoding, or carrying instructions for execution by the machine 900, and includes digital or analog communication signals or other intangible media to facilitate the communication of such software.

[0073] As described herein, examples may include or may operate on logical multiple components, modules or mechanisms. A module is a tangible entity (e.g., hardware) that can perform a specified operation and may be configured or arranged in some way. In one example, a circuit may be arranged as a module in a specified manner (e.g., internally or with respect to external entities such as other circuits). In one example, all or part of one or more computer systems (e.g., independent client or server computer systems) or one or more hardware processors may be configured as a module that performs a specified operation by firmware or software (e.g., instructions, application parts or applications). In one example, software may reside on a machine-readable medium. In one example, software causes hardware to perform a specified operation when executed by the underlying hardware of the module.

[0074] The techniques of various embodiments can be implemented using software, hardware and / or a combination of software and hardware. Various embodiments relate to devices, such as management entities (e.g., network monitoring nodes), routers, gateways, switches, access points, DHCP servers, DNS servers, AAA servers), user equipment devices (e.g., wireless nodes such as mobile wireless terminals, base stations, communication networks and communication systems). Various embodiments also relate to methods for controlling and / or operating one or more communication devices, such as network management nodes, access points, wireless terminals (WTs), user equipment (UEs), base stations, control nodes, DHCP nodes, DNS servers, AAA nodes, mobility management entities (MMEs), networks and / or communication systems. Various embodiments also relate to non-transient machines (e.g., computers), readable media (e.g., ROMs, RAMs, CDs, hard disks, etc.), which include machine-readable instructions for controlling one or more steps of the machine-implemented method.

[0075] It should be understood that the specific order or hierarchy of steps in the disclosed process is provided as an example method. It should be understood that the specific order or hierarchy of steps in the process can be rearranged based on design preferences while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in an example order and are not meant to be limited to the specific order or hierarchy presented.

[0076] In various embodiments, the devices and nodes described herein are implemented using one or more modules to perform steps corresponding to one or more methods (e.g., signal generation, transmission, processing, analysis and / or reception steps). Therefore, in some embodiments, various features are implemented using modules. Such modules can be implemented using software, hardware, or a combination of software and hardware. In some embodiments, each module is implemented as an individual circuit having a device or system including a separate circuit for implementing the functions corresponding to each described module. Many of the above methods or method steps can be implemented using machine executable instructions (such as software) included in a machine readable medium (such as a memory device, such as RAM, a floppy disk, etc.) to control a machine (e.g., a general-purpose computer with or without additional hardware) to implement all or part of the above methods, for example, in one or more nodes. Therefore, various embodiments are particularly related to a machine readable medium, such as a non-transitory computer readable medium, including machine executable instructions for causing a machine (e.g., a processor and associated hardware) to perform one or more steps of the above (multiple) methods. Some embodiments relate to a device including a processor configured to implement one, more or all operations of the disclosed embodiments.

[0077] In some embodiments, one or more processors (e.g., CPUs) of one or more devices (e.g., communication devices, such as routers, switches, network-connected servers, network management nodes, wireless terminals (UEs), and / or access nodes) are configured to perform the steps of the methods described as being performed by the device. The configuration of the processor may be achieved by controlling the processor configuration using one or more modules (e.g., software modules) and / or by including hardware (e.g., hardware modules) in the processor that performs the enumerated steps and / or controls the processor configuration. Thus, some but not all embodiments relate to a communication device, such as a user device, having a processor, which includes a module corresponding to each step of the various described methods performed by the device in which the processor is included. In some but not all embodiments, the communication device includes a module corresponding to each step of the various described methods performed by the device in which the processor is included. These modules may be implemented purely in hardware, such as as circuits, or may be implemented using software and / or hardware or a combination of software and hardware.

[0078] Some embodiments relate to a computer program product, which includes a computer-readable medium, which includes a code for causing one or more computers to implement various functions, steps, actions and / or operations (e.g., one or more steps described above). Depending on the embodiment, the computer program product can and sometimes does include different codes for each step to be performed. Therefore, the computer program product can and sometimes does include codes for each individual step of the method, such as a method for operating a communication device (e.g., a network management node, an access point, a base station, a wireless terminal or a node). The code can be in the form of machine (e.g., computer) executable instructions stored on a computer-readable medium such as a RAM (random access memory), a ROM (read-only memory) or other types of storage devices. In addition to relating to a computer program product, some embodiments also relate to a processor configured to implement one or more of the various functions, steps, actions and / or operations of one or more of the above-mentioned methods. Therefore, some embodiments relate to a processor (e.g., a CPU) configured to implement some or all steps of the method described herein. The processor can be used in, for example, a communication device or other device described in this application.

[0079] Although described in the context of communication systems including wired, optical, cellular, Wi-Fi, Bluetooth, and BLE, at least some of the methods and apparatus of various embodiments are applicable to a variety of communication systems, including IP-based and non-IP-based, OFDM and non-OFDM and / or non-cellular systems.

[0080] In view of the above description, many other variations of the methods and devices of the various embodiments described above will be clear to those skilled in the art. Such variations will be considered to be within the scope. The method and device can and in various embodiments are used with IP and non-IP based, wired and wireless (such as CDMA, orthogonal frequency division multiplexing (OFDM), Wi-Fi, Bluetooth, BLE, optical and / or various other types of communication technologies) that can be used to provide communication links between network-connected or associated devices or other devices (including receiver / transmitter circuits and logic and / or routines) to implement these methods.

[0081] Example 1 is a method performed by a network device, the method comprising: receiving a packet at the network device and via a network link; decoding the packet; identifying a message included in the packet based on the decoding; decoding the message; identifying a request for a first layer or second layer (L1 or L2) attribute of the network link via the decoding of the message; appending the value of the requested L1 or L2 attribute of the network link to the L1 or L2 attribute portion of the packet; appending the address of the network device to the packet; associating the address with the value in the packet; identifying a target address of the packet based on the packet; and forwarding the appended packet to the target address in response to the target address being different from a local address.

[0082] In Example 2, the subject matter of Example 1 optionally includes: wherein processing the packet based on the destination address includes: determining that the destination address is equivalent to the address of the network device; decoding the packet to identify the source address; generating a second packet, the second packet including the L1 or L2 attribute portion, the address, and the association; and transmitting the second packet to the source address.

[0083] In Example 3, the subject matter of any one or more of Examples 1 to 2 optionally includes: the attribute of the network link indicates a request for: a request for an attribute that Media Access Control Security (MACSec) is enabled, a request for an attribute that Synchronous Ethernet is enabled, a request for an attribute that Precision Time Protocol is enabled, a request for a synchronization state of a network device, a request for an attribute that Optical Transport Network (OTN) security is enabled, a request for an attribute indicating a maximum transmission data unit (MTU) size, or a request for a characteristic of the network device.

[0084] In Example 4, the subject matter of any one or more of Examples 1 to 3 may optionally include: wherein decoding the packet includes performing a second decoding of a layer 3 or layer 4 protocol header, and wherein identifying the message is based on the second decoding.

[0085] In Example 5, the subject matter of Example 4 optionally includes: wherein the layer 3 protocol header or the layer 4 protocol header is an Internet Control Message Protocol (ICMP) protocol header.

[0086] In Example 6, the subject matter of any one or more of Examples 4 to 5 optionally includes, wherein the layer 3 protocol header or the layer 4 protocol header is a user datagram protocol (UDP) header.

[0087] In Example 7, the subject matter of any one or more of Examples 1 to 6 optionally includes: wherein the packet is received from a source device and a destination device is identified by the destination address, wherein the network device is included in a network path between the source device and the destination device.

[0088] Example 8 is a system comprising: a hardware processing circuit; and one or more hardware memories storing instructions, which, when executed, configure the hardware processing circuit to perform the following operations: receiving a packet at a network device and via a network link; decoding the packet; identifying a message included in the packet based on the decoding; decoding the message; identifying a request for a first layer or second layer (L1 or L2) attribute of the network link via the decoding of the message; appending the value of the requested L1 or L2 attribute of the network link to the L1 or L2 attribute portion of the packet; appending the address of the network device to the packet; associating the address with the value in the packet; identifying a target address of the packet based on the packet; and forwarding the appended packet to the target address in response to the target address being different from a local address.

[0089] In Example 9, the subject matter of Example 8 optionally includes: wherein processing the packet based on the destination address includes: determining that the destination address is equivalent to the address of the network device; decoding the packet to identify the source address; generating a second packet, the second packet including the L1 or L2 attribute portion, the address, and the association; and transmitting the second packet to the source address.

[0090] In Example 10, the subject matter of any one or more of Examples 8 to 9 optionally includes: the attribute of the network link indicates a request for: a request for an attribute that Media Access Control Security (MACSec) is enabled, a request for an attribute that Synchronous Ethernet is enabled, a request for an attribute that Precision Time Protocol is enabled, a request for a synchronization state of a network device, a request for an attribute that Optical Transport Network (OTN) security is enabled, a request for an attribute indicating a maximum transmission data unit (MTU) size, or a request for a characteristic of the network device.

[0091] In Example 11, the subject matter of any one or more of Examples 8 to 10 optionally includes: wherein decoding the packet includes performing a second decoding of a layer 3 or layer 4 protocol header, and wherein identifying the message is based on the second decoding.

[0092] In Example 12, the subject matter of Example 11 optionally includes: wherein the third layer protocol header or the fourth layer protocol header is an Internet Control Message Protocol (ICMP) protocol header.

[0093] In Example 13, the subject matter of any one or more of Examples 11 to 12 may optionally include: wherein the layer 3 protocol header or the layer 4 protocol header is a user datagram protocol (UDP) header.

[0094] In Example 14, the subject matter of any one or more of Examples 8 to 13 optionally includes: wherein the packet is received from a source device and a destination device is identified by the destination address, wherein the network device is included in a network path between the source device and the destination device.

[0095] Example 15 is a non-transitory computer-readable storage medium comprising instructions, which, when executed, configure the hardware processing circuit to perform the following operations: receiving a packet at a network device and via a network link; decoding the packet; identifying a message included in the packet based on the decoding; decoding the message; identifying a request for a first layer or second layer (L1 or L2) attribute of the network link via the decoding of the message; appending the value of the requested L1 or L2 attribute of the network link to the L1 or L2 attribute portion of the packet; appending the address of the network device to the packet; associating the address with the value in the packet; identifying a destination address of the packet based on the packet; and forwarding the appended packet to the destination address in response to the destination address being different from a local address.

[0096] In Example 16, the subject matter of Example 15 optionally includes: wherein processing the packet based on the destination address includes: determining that the destination address is equivalent to the address of the network device; decoding the packet to identify the source address; generating a second packet, the second packet including the L1 or L2 attribute portion, the address, and the association; and transmitting the second packet to the source address.

[0097] In Example 17, the subject matter of any one or more of Examples 15 to 16 optionally includes: the attribute of the network link indicates a request for: a request for an attribute that Media Access Control Security (MACSec) is enabled, a request for an attribute that Synchronous Ethernet is enabled, a request for an attribute that Precision Time Protocol is enabled, a request for a synchronization state of a network device, a request for an attribute that Optical Transport Network (OTN) security is enabled, a request for an attribute indicating a maximum transmission data unit (MTU) size, or a request for a characteristic of the network device.

[0098] In Example 18, the subject matter of any one or more of Examples 15 to 17 optionally includes: wherein decoding the packet includes performing a second decoding of a layer 3 or layer 4 protocol header, and wherein identifying the message is based on the second decoding.

[0099] In Example 19, the subject matter of Example 18 optionally includes: wherein the third layer protocol header or the fourth layer protocol header is an Internet Control Message Protocol (ICMP) protocol header or a User Datagram Protocol (UDP) header.

[0100] In Example 20, the subject matter of any one or more of Examples 15 to 19 optionally includes: wherein the packet is received from a source device and a destination device is identified by the destination address, wherein the network device is included in a network path between the source device and the destination device.

Claims

1. A method performed by a network device, the method comprising: generating a packet including a message indicating a request for a value of a first layer L1 or a second layer L2 attribute; sending the packet to a target device; receiving a second packet from the target device, the second packet including a response message to the message; decoding the response message from the second packet; as well as One or more L1 or L2 attribute values ​​of one or more network devices traversed along a network path from the network device to the target device are decoded from the response message.

2. The method according to claim 1, further comprising: The one or more L1 or L2 property values ​​are displayed on a display screen or included in a report.

3. The method according to claim 1, further comprising: A network configuration is changed based on the one or more L1 or L2 attribute values.

4. The method of claim 1 , wherein generating the packet comprises: The message is generated and encapsulated in a third layer L3 or fourth layer L4 protocol header.

5. The method of claim 4, wherein the message is an Internet Control Message Protocol (ICMP) message, and the L3 or L4 protocol header comprises an Internet Protocol (IP) header.

6. The method of claim 5, wherein generating the ICMP message comprises: The type field or the code field is set to indicate that the ICMP message includes a request for a value of an L1 or L2 attribute.

7. The method of claim 5, wherein generating the ICMP message comprises: A data field requesting the value of the L1 or L2 attribute is included in the ICMP message.

8. The method of claim 4, wherein the message is an LSP-ping message, and the L3 or L4 protocol header comprises a Transmission Control Protocol (TCP) header or a User Datagram Protocol (UDP) header.

9. The method of claim 8, wherein generating the LSP-ping message comprises: The Reply Mode field is set to a predefined value indicating that the LSP-ping message includes a request for a value of an L1 or L2 attribute.

10. The method of claim 1, wherein decoding the response message from the second packet comprises: The L3 or L4 header is decoded from the second packet.

11. The method of claim 1 , wherein the response message is an ICMP message, and wherein decoding the one or more L1 or L2 attribute values ​​from the response message comprises: The one or more L1 or L2 attribute values ​​are decoded from an ICMP data field of the ICMP message.

12. The method of claim 1, wherein the response message is an LSP-ping message, and wherein decoding the one or more L1 or L2 attribute values ​​from the response message comprises: The one or more L1 or L2 attribute values ​​are decoded from a Type Length Value TLV field of the LSP-ping message.

13. The method according to claim 1, wherein the L1 or L2 attribute comprises at least one of the following: an attribute indicating whether Media Access Control Security (MACSec) is enabled, an attribute indicating whether Synchronous Ethernet (SyncE) is enabled, an attribute indicating whether Precision Time Protocol (PTP) is enabled, an attribute indicating whether Optical Transport Network (OTN) security is enabled, an attribute indicating a Maximum Transmission Data Unit (MTU) size, an attribute indicating a synchronization state of the network device, or an attribute indicating an L1 or L2 characteristic of the network device.

14. A system comprising: Hardware processing circuit; as well as One or more hardware memories storing instructions that, when executed, configure the hardware processing circuitry to perform operations comprising: generating a packet including a message indicating a request for a value of a first layer L1 or a second layer L2 attribute; sending the packet to a target device; receiving a second packet from the target device, the second packet including a response message to the message; decoding the response message from the second packet; and One or more L1 or L2 attribute values ​​of one or more network devices traversed along a network path from the network device to the target device are decoded from the response message.

15. The system of claim 14, the operations further comprising: The one or more L1 or L2 attribute values ​​are caused to be displayed on a display screen or included in a report.

16. The system of claim 14, the operations further comprising: A network configuration is changed based on the one or more L1 or L2 attribute values.

17. The system of claim 14, wherein the packet comprises an ICMP message encapsulated in an IP protocol header.

18. The system of claim 14, wherein the packet comprises an LSP-ping message encapsulated in a TCP or UDP header.

19. The system according to claim 14, wherein the L1 or L2 attributes include at least one of the following: an attribute indicating whether Media Access Control Security (MACSec) is enabled, an attribute indicating whether Synchronous Ethernet (SyncE) is enabled, an attribute indicating whether Precision Time Protocol (PTP) is enabled, an attribute indicating whether Optical Transport Network (OTN) security is enabled, an attribute indicating a Maximum Transmission Data Unit (MTU) size, an attribute indicating a synchronization state of the network device, or an attribute indicating an L1 or L2 characteristic of the network device.

20. A non-transitory computer-readable medium comprising instructions that, when executed, configure a hardware processing circuit to perform operations comprising: generating a packet including a message indicating a request for a value of a first layer L1 or a second layer L2 attribute; sending the packet to a target device; receiving a second packet from the target device, the second packet including a response message to the message; decoding the response message from the second packet; as well as One or more L1 or L2 attribute values ​​of one or more network devices traversed along a network path from the network device to the target device are decoded from the response message.

21. A method performed by a network device, the method comprising: generating a message identifying a physical layer attribute; sending the message to the target device; receiving a response message to the message from the target device; as well as One or more physical layer attribute values ​​of one or more network devices traversed along a network path from the network device to the target device are decoded from the response message.

22. The method according to claim 21, further comprising: The one or more physical layer property values ​​are displayed on a display screen or included in a report.

23. The method according to claim 21, further comprising: A network configuration is changed based on the one or more physical layer property values.

24. The method of claim 21, wherein generating the message comprises: The message is generated and encapsulated in a non-physical layer protocol header.

25. The method of claim 24, wherein the message is an Internet Control Message Protocol (ICMP) message and the non-physical layer protocol header comprises an Internet Protocol (IP) header.

26. The method of claim 25, wherein generating the ICMP message comprises: The type field or the code field is set to indicate that the ICMP message includes a request for a value of a non-physical layer protocol header attribute.

27. The method of claim 25, wherein generating the ICMP message comprises: A data field requesting the value of the non-physical layer attribute is included in the ICMP message.

28. The method of claim 24, wherein the message is an LSP-ping message, and the non-physical layer protocol header comprises a Transmission Control Protocol (TCP) header or a User Datagram Protocol (UDP) header.

29. The method of claim 28, wherein generating the LSP-ping message comprises: The Reply Mode field is set to a predefined value indicating that the LSP-ping message includes a request for a value of a physical layer attribute.

30. The method of claim 21, further comprising decoding a non-physical layer header from the response message.

31. The method of claim 21 , wherein the response message is an ICMP message, and wherein decoding the one or more physical layer attribute values ​​from the response message comprises: The one or more physical layer attribute values ​​are decoded from an ICMP data field of the ICMP message.

32. The method of claim 21, wherein the response message is an LSP-ping message, and wherein decoding the one or more physical layer attribute values ​​from the response message comprises: The one or more physical layer attribute values ​​are decoded from a type-length-value TLV field of the LSP-ping message.

33. The method of claim 21, wherein the physical layer attributes include at least one of the following: an attribute indicating whether Media Access Control Security (MACSec) is enabled, an attribute indicating whether Synchronous Ethernet (SyncE) is enabled, an attribute indicating whether Precision Time Protocol (PTP) is enabled, an attribute indicating whether Optical Transport Network (OTN) security is enabled, an attribute indicating a Maximum Transmission Data Unit (MTU) size, an attribute indicating a synchronization state of the network device, or an attribute indicating a non-physical layer characteristic of the network device.

34. A system comprising: Hardware processing circuit; as well as One or more hardware memories storing instructions that, when executed, configure the hardware processing circuitry to perform operations comprising: generating a message, the message identifying a physical layer attribute; sending the message to the target device; receiving a response message to the message from the target device; and One or more physical layer attribute values ​​of one or more network devices traversed along a network path from the network device to the target device are decoded from the response message.

35. The system of claim 34, the operations further comprising: The one or more physical layer property values ​​are caused to be displayed on a display screen or included in a report.

36. The system of claim 34, the operations further comprising: A network configuration is changed based on the one or more physical layer property values.

37. The system of claim 34, wherein the message comprises an ICMP message encapsulated in an IP protocol header.

38. The system of claim 34, wherein the message comprises an LSP-ping message encapsulated in a TCP or UDP header.

39. The system of claim 34, wherein the physical layer attributes include at least one of: an attribute indicating whether Media Access Control Security (MACSec) is enabled, an attribute indicating whether Synchronous Ethernet (SyncE) is enabled, an attribute indicating whether Precision Time Protocol (PTP) is enabled, an attribute indicating whether Optical Transport Network (OTN) security is enabled, an attribute indicating a Maximum Transmission Data Unit (MTU) size, an attribute indicating a synchronization state of the network device, or an attribute indicating a physical layer characteristic of the network device.

40. A non-transitory computer-readable medium comprising instructions that, when executed, configure a hardware processing circuit to perform operations comprising: generating a message, the message identifying a physical layer attribute; sending the message to the target device; receiving a response message to the message from the target device; as well as One or more physical layer attribute values ​​of one or more network devices traversed along a network path from the network device to the target device are decoded from the response message.