Information processing method and device

Abstract

The invention provides an information processing method, which comprises the steps that a second node receives a first node identifier and a first interface identifier sent by a first node, the first node identifier is used for identifying the first node, and the first interface identifier is used for identifying a first interface, used for communicating with the second node, of the first node; and the second node obtains the first link information according to the first node identifier, the first interface identifier, the second node identifier and the second interface identifier. The second node identifier is used for identifying a second node, and the second interface identifier is used for identifying a second interface of the second node for communicating with the first node. The first link information is used for identifying a first link between the first interface and the second interface. The first link is a link bearing a large particle service or a link bearing a small particle service. By means of the scheme, the second node can automatically find the first link between the second node and the first node, and maintenance of network information is facilitated.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular, to an information processing method and apparatus. Background Art

[0002] With the development of communication technologies, more and more services are carried in communication networks. Correspondingly, the service traffic transmitted in communication networks is also increasing. In some scenarios, to improve the service quality provided for services and rationally utilize network resources, large-granule technologies can be applied to transmit service traffic. Large-granule technologies have advantages such as flexible bandwidth allocation on demand, and their applications are becoming more and more widespread. Moreover, to rationally utilize bandwidth resources, the bandwidth carried by a physical port can also be divided into multiple sub-slots, or the slot corresponding to a large bandwidth in large-granule technologies can be divided into multiple sub-slots, and the multiple sub-slots obtained by division are used to carry customer services with lower bandwidth requirements. Among them, the customer services transmitted using large-granule technologies can be referred to as "large-granule services", and the customer services carried by sub-slots can also be referred to as "small-granule services". In addition, the technology of using sub-slots to carry customer services can also be referred to as "small-granule technology".

[0003] Currently, after deploying large-granule technologies or small-granule technologies in a network, the maintenance cost of network information related to large-granule technologies or small-granule technologies is relatively high.

[0004] Therefore, there is an urgent need for a solution that can solve or partially solve the above problems. Summary of the Invention

[0005] Embodiments of this application provide an information processing method and apparatus, which can reduce the maintenance cost of network information related to large-granule technologies or small-granule technologies.

[0006] In a first aspect, an embodiment of the present application provides an information processing method, which can be applied to a second node. The second node may receive a first node identifier and a first interface identifier sent by a first node, where the first node identifier is used to identify the first node, and the first interface identifier is used to identify a first interface of the first node for communicating with the second node. After receiving the first node identifier and the first interface identifier, the second node may combine the first node identifier, the first interface identifier, its own second node identifier, and a second interface identifier to obtain first link information. Wherein, the second node identifier is used to identify the second node, and the second interface identifier is used to identify a second interface of the second node for communicating with the first node. The first link information is used to identify a first link between the first interface and the second interface. Wherein, the first link is a link carrying large-granularity services or a link carrying small-granularity services. It can be seen that with the solution of the embodiment of the present application, the first node can notify the second node of information related to the link (i.e., the first node identifier and the first interface identifier), so that the second node can determine the first link between the first node and the second node for carrying large-granularity services or small-granularity services. In other words, the second node can automatically discover the first link between itself and the first node, and the discovery of large-granularity links / small-granularity links is more flexible, which is beneficial to the maintenance of network information.

[0007] In a possible implementation manner, the first node may send the foregoing first node identifier and first interface identifier to the second node by sending a first Link Layer Discovery Protocol (LLDP) message to the second node. Wherein, the first LLDP message includes the first node identifier and the first interface identifier. As a specific example, the first LLDP message may include a first type length value (TLV). After receiving the first LLDP message, the second node may parse the first LLDP message to obtain the first TLV, and further obtain the first node identifier and the first interface identifier carried in the first TLV.

[0008] In a possible implementation manner, the first TLV may include multiple sub-TLVs. As a specific example, the first TLV may include a first sub-TLV and a second sub-TLV. The first sub-TLV is used to carry the first node identifier, and the second sub-TLV is used to carry the first interface identifier. After parsing the first TLV, the second node may obtain the first node identifier through the first sub-TLV and obtain the first interface identifier through the second sub-TLV.

[0009] In a possible implementation, the first TLV may be an existing TLV in the LLDP packet. For this case, it is possible to avoid extending new TLVs based on LLDP. As a specific example, the first TLV may be a vendor TLV.

[0010] In a possible implementation, if the first link is a link for carrying large-granularity services, then the first interface may be a first flexible Ethernet group (FlexEgroup) included in the first node. Correspondingly, the first node identifier may be the identifier of the first FlexE group. Similarly, the second interface may be a second FlexE group included in the second node. Correspondingly, the second node identifier may be the identifier of the second FlexE group.

[0011] In a possible implementation, if the first link is a link for carrying large-granularity services. Then, in a specific example, the first link is a link between the first physical interface of the first node and the second physical interface of the second node. For this case:

[0012] In an example, the first node may send the foregoing first LLDP packet to the second node through the overhead (OH) channel corresponding to the first link. Correspondingly, the second node may receive the first LLDP packet through the OH channel corresponding to the first link. The OH channel corresponding to the first link is used to carry the link information of the first link. Among them, the OH channel corresponding to the first link can be used to carry the link information of the first link, rather than the link information of other links. Once the first link fails, the OH channel corresponding to the first link becomes unavailable. Correspondingly, the second node cannot receive the first LLDP packet sent by the first node. In other words, if the second node can receive the first LLDP packet, it means that the first link is fault-free. Therefore, in this way, the link information of the faulty link can be naturally not discovered, and the link information received by the second node is the link information of the fault-free link. Among them, the link information of the first link may include at least one of the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier.

[0013] In yet another example, the first node may send the first LLDP message to the second node through a general OH channel. Among them, the link information of multiple links carrying large-granularity services between the first node and the second node is transmitted through the general OH channel. In other words, the general OH channel is no longer uniquely bound to a certain link carrying large-granularity services. For this case, the second node may receive the first LLDP message through the general OH channel, so as to obtain the first node identifier and the first interface identifier.

[0014] In a possible implementation manner, considering that it is precisely because the general OH channel is no longer uniquely bound to a certain link, therefore, in order to enable the second node to determine which link the received first node identifier and first interface identifier specifically correspond to, the foregoing first LLDP message may further include the identifier of the first physical interface. In this way, the second node can determine that the first node identifier and the first interface identifier are for the link corresponding to the first physical interface based on the identifier of the first physical interface.

[0015] In a possible implementation manner, if the first node sends the first LLDP message to the second node through the general OH channel, then when the second node receives the first LLDP message, it only indicates that the first physical interface of the first node is fault-free, but does not indicate that the first link is fault-free. For this case, before the second node combines the first node identifier and the first interface identifier, as well as its own second node identifier and second interface identifier to obtain the first link information, it may first determine whether the first link is faulty. Specifically, as described above, if the first LLDP message is sent to the second node through the general OH channel, and the first LLDP message includes the identifier of the first physical interface, then the second node may determine the second physical interface connected to the first physical interface based on the identifier of the first physical interface. Further, the second node may determine whether the second physical interface is faulty. Correspondingly, the second node may determine whether the first link is faulty according to whether the second physical interface is faulty. For example, if the second physical interface is faulty, it is determined that the first link is faulty; if the second physical interface is fault-free, it is determined that the first link is fault-free. After the second node determines that the first link is fault-free, it combines the first node identifier and the first interface identifier, as well as its own second node identifier and second interface identifier to obtain the first link information.

[0016] In a possible implementation, the second node can further determine the link attributes of the first link, so as to further send the link attributes of the first link and the first link information to the controller. In other words, using the solution of the embodiments of the present application, the second node can automatically discover the first link between itself and the first node, and report the first link information and the link attributes of the first link to the controller. Without the controller sending the corresponding configuration information to the second node, the second node can automatically report the first link information and the link attributes of the first link to the controller, which is beneficial to network maintenance. Correspondingly, the controller can calculate the end-to-end path for the service based on the first link information and the link attributes of the first link. In some embodiments, the first link is a link carrying large-granularity services. For this case, the link attributes of the first link may include the identifier of the first physical interface, the identifier of the second physical interface, the additional attributes of the first physical interface, and the additional attributes of the second physical interface. Among them, the additional attributes of the first physical interface include at least one attribute of the first physical interface. Similarly, the additional attributes of the second physical interface include at least one attribute of the second physical interface.

[0017] In a possible implementation, if any physical interface is referred to as the target physical interface, the additional attributes of the target physical interface may include the large-granularity capability supported by the target physical interface, the configured bandwidth of the target physical interface, the remaining bandwidth of the target physical interface, and the available time slots of the target physical interface. Among them: The configured bandwidth of the target physical interface can be understood as the total bandwidth of the target physical interface; the remaining bandwidth of the target physical interface refers to the bandwidth that has not been occupied by services or reserved for specific services; the available time slots of the target physical interface refer to the time slots that have not been allocated to services. The large-granularity capability supported by the target physical interface refers to the capability related to carrying large-granularity services.

[0018] In a possible implementation, the large-granularity capabilities supported by the target physical interface may include: the granularity bearing capacity supported by the target physical interface, the cross-physical layer (PHY) bundling capacity, the dynamic large-granularity channel capacity, the static large-granularity channel capacity, and the large-granularity time slot following capacity. Among them: The granularity bearing capacity supported by the target physical interface is used to indicate the bandwidth granularity corresponding to the time slot carrying large-granularity services. The cross-PHY bundling capacity is used to indicate the ability to bundle and use the time slots corresponding to different PHYs included in the FlexE group. The dynamic large-granularity channel capacity is used to indicate whether it can participate in the calculation of the dynamic end-to-end path. Among them, if the target physical interface has the dynamic large-granularity channel capacity, it means that the target physical interface supports participating in the calculation of the dynamic end-to-end path. The dynamic end-to-end path mentioned here refers to the path carrying large-granularity services. The static large-granularity channel capacity indicates whether a static end-to-end path can be established through static configuration. Among them, if the target physical interface has the static large-granularity channel capacity, it means that the target physical interface can establish a static end-to-end path through static configuration. The static end-to-end path mentioned here refers to the path carrying small-granularity services. The large-granularity time slot following capacity refers to automatically following the upstream large-granularity time slot configuration, so that the local end can establish communication with the upstream.

[0019] In a possible implementation, the first node may send the additional attributes of the first physical interface to the second node. Correspondingly, the second node may receive the additional attributes of the first physical interface sent by the first node. In other words, the way for the second node to obtain the additional attributes of the first physical interface is: receiving the additional attributes of the first physical interface sent by the first node.

[0020] In a possible implementation, the first node may carry the additional attributes of the foregoing first physical interface in the foregoing first LLDP message and send them to the second node. For this case, the first node can send the first node identifier, the first interface identifier, and the additional attributes of the first physical interface to the second node through one LLDP message. In a possible implementation, the additional attributes of the first physical interface may be carried by the foregoing first TLV. In some scenarios, the first TLV may include a third sub-TLV, and the third sub-TLV is used to carry the large-granularity capabilities supported by the first physical interface. For example, the value field of the third sub-TLV may include the indication bits corresponding to the foregoing large-granularity capabilities respectively.

[0021] In a possible implementation, if the large-granularity time slot following ability indicates that the target physical interface has the ability to automatically follow the upstream large-granularity time slot configuration, then this large-granularity time slot following ability can also be used to indicate the following manner in which the target physical interface automatically follows the upstream large-granularity time slot configuration. The following manner includes: following through data-plane packets and / or following through control-plane packets. Herein, following through data-plane packets means interacting with the upstream node through data packets to achieve following the upstream time slot configuration; following through control-plane packets means interacting with the upstream node through control packets to achieve following the upstream time slot configuration. In this way, the second node can determine the following manner in which the first physical interface automatically follows the upstream large-granularity time slot configuration. Correspondingly, in the time slot negotiation phase, the second node can select the corresponding time slot negotiation manner to negotiate time slots with the first node.

[0022] In a possible implementation, in addition to including the third sub-TLV, the first TLV may further include a first bandwidth sub-TLV and a first time slot sub-TLV. The first bandwidth sub-TLV is used to carry the configured bandwidth of the first physical interface and the remaining bandwidth of the first physical interface; the first time slot sub-TLV can be used to carry the available time slots of the first physical interface. Of course, the configured bandwidth of the first physical interface and the remaining bandwidth of the first physical interface may also be carried by different bandwidth sub-TLVs respectively, and the embodiments of the present application do not make specific limitations.

[0023] In a possible implementation, when the first node and the second node are deployed with large-granularity technology, the first FlexE group of the first node may include multiple physical interfaces. For example, it may include the aforementioned first physical interface and the third physical interface. Correspondingly, the second FlexE group of the second node may include multiple physical interfaces. For example, it may include the aforementioned second physical interface and the fourth physical interface. For this case, the link between the aforementioned first interface and the second interface may further include a second link between the third physical interface and the fourth physical interface. For this case, the first node may further send a second LLDP message to the second node, and the second LLDP message includes a first node identifier and a first interface identifier. Correspondingly, after receiving the second LLDP message, the second node may obtain second link information based on the first node identifier, the first interface identifier, the local second node identifier, and the second interface identifier in the second LLDP message. This second link information is the same as the first link information and also includes a quadruple, namely: the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier. Additionally, the second node may further determine the link attributes of the second link. Among them, the link attributes of the second link may include: the identifier of the third physical interface, the identifier of the fourth physical interface, the additional attributes of the third physical interface, and the additional attributes of the fourth physical interface. Specifically, the second node may obtain the additional attributes of the fourth physical interface locally and receive the additional attributes of the third physical interface sent by the first node.

[0024] In a possible implementation, after obtaining the first link information, the second link information, the link attributes of the first link, and the link attributes of the second link, the first node may merge the first link information, the second link information, the link attributes of the first link, and the link attributes of the second link to obtain target link information and target link attributes. As described above, the first link information and the second link information are the same. Therefore, the first link information and the second link information can be combined into one, that is: the target link information may be the first link information. Correspondingly, the target link attributes include the link attributes of the first link and the link attributes of the second link. Thus, the second node may obtain the target link information and the target link attributes between the first FlexE group of the first node and the second FlexE group of the second node.

[0025] In a possible implementation, the second node may report the target link information and the target link attributes to the controller, so that the controller can calculate an end-to-end path for the service based on the target link information and the target link attributes.

[0026] In a possible implementation, if the first link is a link for carrying small-granularity services, the first interface may be the first client included in the first node. Correspondingly, the first interface identifier may be the first client identifier. Correspondingly, the second interface may be the second client included in the second node, and the second interface identifier may be the second client identifier.

[0027] In a possible implementation, considering that the index of the first client is unique on the first node and it can identify the first client, therefore, the first client identifier may be the index of the first client. Similarly, the second client identifier may be the index of the second client.

[0028] In a possible implementation, considering that the first node may include multiple FlexE groups, each FlexE group may include multiple clients, each client may correspond to a transmission identifier, and the transmission identifier is unique within the FlexE group. The transmission identifiers of the clients included in different FlexE groups may be the same. Therefore, the combination of the transmission identifier corresponding to the FlexE group and the client is unique on the first node. Therefore, in one example, the first client identifier may also be determined according to the transmission identifier of the first client and the identifier of the FlexE group to which the first client belongs. Similarly, the second client identifier may also be determined according to the transmission identifier of the second client and the identifier of the FlexE group to which the second client belongs.

[0029] In a possible implementation, considering that the client has interface attributes, the node may allocate an interface index (ifindex) to the clients it includes, and the ifindex is unique on the node. Therefore, the first client identifier may be the interface index of the first client. Similarly, the second client identifier may be the interface index of the second client.

[0030] In a possible implementation, if the small-granularity technology is implemented by directly dividing sub-time slots on the physical port, considering that the physical interface obtained by dividing for the first client is unique on the first node, therefore, the first client identifier may be the identifier of the physical interface obtained by dividing for the first client. Similarly, the second client identifier may be the identifier of the physical interface obtained by dividing for the second client.

[0031] In a possible implementation, if the first link is a link carrying small particle services. Then, in a specific example, the first link is a link between the first client of the first node and the second client of the second node. For this case:

[0032] In an example, the first node can send a first LLDP message to the second node through the general communication channel (GCC) corresponding to the first link. Correspondingly, the second node can receive the first LLDP message through the GCC corresponding to the first link. In this scenario, the GCC corresponding to the first link can be used to carry the link information of the first link, rather than the link information of other links. Once the first link fails, the GCC corresponding to the first link becomes unavailable. Correspondingly, the second node cannot receive the first LLDP message sent by the first node. In other words, if the second node can receive the first LLDP message, it means that the first link is fault-free. Therefore, by using this method, the link information of the faulty link can be naturally not discovered, and the link information received by the second node is the link information of the fault-free link.

[0033] In another example, a general GCC can be included between the first node and the second node, and the link information of multiple links carrying small particle services between the first node and the second node is transmitted through the general GCC. In this scenario, the general GCC is no longer uniquely bound to a certain link carrying small particle services. For this case, the first node can send a first LLDP message to the second node through the general GCC. Correspondingly, the second node can receive the first LLDP message through the general GCC.

[0034] In a possible implementation, precisely because the general GCC is no longer uniquely bound to a certain link, in order for the second node to determine which link the received first node identifier and first interface identifier specifically correspond to, the foregoing first LLDP message may further include the transmission identifier of the first client. In this way, the second node can determine, based on the transmission identifier of the first client, that the first node identifier and the first interface identifier correspond to the link corresponding to the first client. Among them, the transmission identifier of the first client is the same as the transmission identifier of the second client. Therefore, the second node can determine the second client based on the transmission identifier of the first client, and further locate the first link as the link connected to the second client.

[0035] In a possible implementation, if the first node can send the first LLDP packet to the second node through the general GCC, when the second node receives the first LLDP packet, it only indicates that the first client of the first node is fault-free, but does not indicate that the first link is fault-free. For this situation, before the second node obtains the first link information by combining the first node identifier and the first interface identifier, and its own second node identifier and the second interface identifier, it can first determine whether the first link is faulty. Specifically, as described above, if the first LLDP packet is sent to the second node through the general GCC, the first LLDP packet includes the identifier of the first client, and the second node can determine the second client connected to the first client according to the identifier of the first client. Further, the second node can determine whether the second client is faulty, and further determine whether the second link is faulty. For example, if the second client is fault-free, the second node can determine that the first link is fault-free; if the second client is faulty, the second node can determine that the first link is faulty. After the second node determines that the first link is fault-free, it can further obtain the first link information by combining the first node identifier and the first interface identifier, and its own second node identifier and the second interface identifier.

[0036] In a possible implementation, the second node can further determine the link attributes of the first link, so as to further send the link attributes of the first link and the first link information to the controller. Correspondingly, the controller can calculate the end-to-end path for the service based on the first link information and the link attributes of the first link. In some embodiments, the first link is a link carrying small granularity services. For this situation, the link attributes of the first link may include the identifier of the first client, the identifier of the second client, the additional attributes of the first client, and the additional attributes of the second client. Among them, the additional attributes of the first client include at least one attribute of the first client. Similarly, the additional attributes of the second client include at least one attribute of the second client.

[0037] In a possible implementation, any client is referred to as the target client. The target client can be the first client, the second client, the third client, or the fourth client. The additional attributes of the target client include one or more of the following: the small particle capabilities supported by the target client, the configured bandwidth of the target client, the remaining bandwidth of the target client, and the available sub-slots of the target client. Among them: the configured bandwidth of the target client can be understood as the total bandwidth of the target client; the remaining bandwidth of the target client refers to the bandwidth that has not been occupied by services or reserved for specific services; the available time slots of the target client refer to the time slots that have not been allocated to services; the small particle capabilities supported by the target client refer to the capabilities related to carrying small particle services.

[0038] In a possible implementation, the small particle capabilities supported by the target client include one or more of the following: whether the target client supports small particle technology, dynamic small particle channel capabilities, static small particle channel capabilities, and small particle time slot following capabilities. Among them, the target client having the dynamic small particle channel capabilities indicates that the target client can participate in the calculation of the dynamic end-to-end path; the target client having the static small particle channel capabilities indicates that the target client can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths for carrying small particle services. The small particle time slot following capabilities are used to indicate whether the target client has the ability to automatically follow the upstream small particle time slot configuration.

[0039] In a possible implementation, the first node can send the additional attributes of the first client to the second node. In other words, the way for the second node to obtain the additional attributes of the first client can be: receiving the additional attributes of the first client sent by the first node.

[0040] In a possible implementation, the first node can carry the additional attributes of the first client in the first LLDP packet and send it to the second node. For this case, through one LLDP packet, the first node can send the first node identifier, the first interface identifier, and the additional attributes of the first client to the second node. As a specific example, the additional attributes of the first client can be carried by the first TLV.

[0041] In a specific example, the first TLV may include a fourth sub-TLV, and the fourth sub-TLV is used to carry the small particle capabilities supported by the first client. For example, the value field of the fourth sub-TLV may include indication bits corresponding to the foregoing small particle capabilities respectively.

[0042] In a specific example, in addition to including the fourth sub-TLV, the first TLV may further include a second bandwidth sub-TLV and a second time slot sub-TLV. The second bandwidth sub-TLV is used to carry the configured bandwidth of the first client and the remaining bandwidth of the first client; the second time slot sub-TLV may be used to carry the available time slots of the first client. Of course, the configured bandwidth of the first client and the remaining bandwidth of the first client may also be carried by different bandwidth sub-TLVs respectively, and the embodiments of the present application do not make specific limitations.

[0043] In a possible implementation manner, the first node may carry the additional attributes of the first client in an operation administration and maintenance (OAM) code block and send them to the second node. For this case, the second node may parse the OAM code block to obtain the additional attributes of the first client.

[0044] In a possible implementation manner, if the small particle time slot following capability indicates that the target client has the ability to automatically follow the upstream small particle time slot configuration, the small particle time slot following capability further indicates the following manner for the target client to automatically follow the upstream small particle time slot configuration. The following manner includes: following through data plane messages and / or following through control plane messages. In this way, the second node can determine the following manner for the first client to automatically follow the upstream large particle time slot configuration. Correspondingly, in the time slot negotiation phase, the second node can select a corresponding time slot negotiation manner to negotiate with the first node for the time slot.

[0045] In a possible implementation manner, the second node may send the second node identifier and the second interface identifier to the first node, so that the first node can obtain the first link information based on the second node identifier, the second interface identifier, the first node identifier, and the first interface identifier.

[0046] In a possible implementation manner, if the first link is a link carrying large particle services, the second node may further send the additional attributes of the second physical interface to the first node.

[0047] In a possible implementation, if the first link is a link carrying small-granularity services, the second node may also send additional attributes of the second client to the first node.

[0048] In a second aspect, an embodiment of the present application provides an information processing method. This method can be applied to a first node. The first node can obtain a first node identifier and a first interface identifier. The first node identifier is used to identify the first node, and the first interface identifier is used to identify a first interface of the first node for communicating with the second node. Further, the first node identifier and the first interface identifier are sent to the second node. The first node identifier and the first interface identifier are used to enable the second node to obtain first link information. The first link information is used to indicate a first link between the first interface and a second interface of the second node. The first link is a link carrying large-granularity services or a link carrying small-granularity services. It can be seen that with the solution of the embodiment of the present application, when the first node and the second node are deployed to carry large-granularity services or small-granularity services, the first node can notify the second node of link-related information (i.e., the first node identifier and the first interface identifier), so that the second node can determine the first link between the first node and the second node for carrying large-granularity services or small-granularity services. In other words, the second node can automatically discover the first link between itself and the first node, which is beneficial to the maintenance of network information.

[0049] In a possible implementation, the sending the first node identifier and the first interface identifier to the second node includes: sending a first Link Layer Discovery Protocol (LLDP) message to the second node. The first LLDP message includes a first Type-Length-Value (TLV). The first TLV includes the first node identifier and the first interface identifier.

[0050] In a possible implementation, the first TLV includes a first sub-TLV and a second sub-TLV. The first sub-TLV includes the first node identifier, and the second sub-TLV includes the first interface identifier.

[0051] In a possible implementation, the first TLV is a vendor TLV.

[0052] In a possible implementation, if the first link is a link carrying large-granularity services, then: the first interface identifier includes: a first FlexE group identifier corresponding to the first node. The first FlexE group identifier is used to identify the first FlexE group corresponding to the first node.

[0053] In a possible implementation, the first link is a link between a first physical interface of the first node and a second physical interface of the second node. Sending a first Link Layer Discovery Protocol (LLDP) packet to the second node includes: sending the first LLDP packet to the second node through an overhead (OH) channel corresponding to the first link, where the OH channel corresponding to the first link is used to carry link information of the first link.

[0054] In a possible implementation, sending a first Link Layer Discovery Protocol (LLDP) packet to the second node includes: sending the first LLDP packet to the second node through a common OH channel, where link information of multiple links carrying large-granularity services between the first node and the second node is transmitted through the common OH channel.

[0055] In a possible implementation, the first link is a link between a first physical interface of the first node and a second physical interface of the second node, and the first LLDP packet further includes an identifier of the first physical interface.

[0056] In a possible implementation, the method further includes: sending additional attributes of the first physical interface to the second node.

[0057] In a possible implementation, the additional attributes of the first physical interface include one or more of the following: large-granularity capabilities supported by the first physical interface, configured bandwidth of the first physical interface, remaining bandwidth of the first physical interface, and available time slots of the first physical interface.

[0058] In a possible implementation, the large-granularity capabilities supported by the first physical interface include one or more of the following: particle carrying capabilities supported by the first physical interface, cross-PHY bundling capabilities, dynamic large-granularity channel capabilities, static large-granularity channel capabilities, and large-granularity time slot following capabilities. Among them, the first physical interface having the dynamic large-granularity channel capability indicates that the first physical interface can participate in the calculation of a dynamic end-to-end path, and the first physical interface having the static large-granularity channel capability indicates that the first physical interface can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths for carrying large-granularity services, and the large-granularity time slot following capability is used to indicate whether the first physical interface has the ability to automatically follow the upstream large-granularity time slot configuration.

[0059] In a possible implementation, a first Type-Length-Value (TLV) of the first LLDP packet further includes a third sub-TLV, and the third sub-TLV includes the large-granularity capabilities supported by the first physical interface.

[0060] In a possible implementation, if the large-granularity time slot following capability indicates that the first physical interface has the ability to automatically follow the upstream large-granularity time slot configuration, the large-granularity time slot following capability further indicates the following mode for the first physical interface to automatically follow the upstream large-granularity time slot configuration, and the following mode includes: following through data-plane packets and / or following through control-plane packets.

[0061] In a possible implementation, if the first link is a link carrying small-granularity services, then: the first interface identifier includes: the first client identifier corresponding to the first node, and the first client identifier is used to identify the first client corresponding to the first node.

[0062] In a possible implementation, the first client identifier is the index of the first client; or, the first client identifier is determined according to the transmission identifier of the first client and the identifier of the FlexE group to which the first client belongs; or, in a scenario where sub-time slots are directly divided for a physical port, the first client identifier is the identifier of the physical interface that divides to obtain the first client, or the first client identifier is the interface index of the first client.

[0063] In a possible implementation, the first link is a link between the first client of the first node and the second client of the second node, and sending the first Link Layer Discovery Protocol (LLDP) packet to the second node includes: sending the first LLDP packet to the second node through the general communication channel (GCC) corresponding to the first link.

[0064] In a possible implementation, sending the first Link Layer Discovery Protocol (LLDP) packet to the second node includes: sending the first LLDP packet to the second node through the general GCC, where the link information of multiple links carrying small-granularity services between the first node and the second node is transmitted through the general GCC channel.

[0065] In a possible implementation, the first link is a link between the first client of the first node and the second client of the second node, and the transmission identifier of the first client is further included in the first LLDP packet.

[0066] In a possible implementation, the method further includes: sending the additional attributes of the first client to the second node.

[0067] In a possible implementation, the additional attributes of the first client include one or more of the following: the small particle capabilities supported by the first client, the configured bandwidth of the first client, the remaining bandwidth of the first client, and the available sub-slots of the first client.

[0068] In a possible implementation, the small particle capabilities supported by the first client include one or more of the following: whether the first client supports small particle technology, dynamic small particle channel capabilities, static small particle channel capabilities, and small particle time slot following capabilities. Among them, the first client having the dynamic small particle channel capabilities indicates that the first client can participate in the calculation of the dynamic end-to-end path. The first client having the static small particle channel capabilities indicates that the first client can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths carrying small particle services. The small particle time slot following capabilities are used to indicate whether the first client has the ability to automatically follow the upstream small particle time slot configuration.

[0069] In a possible implementation, the first TLV of the first LLDP packet further includes a fourth sub-TLV, and the small particle capabilities supported by the first client are included in the fourth sub-TLV; or, the small particle capabilities supported by the first client are carried by the operation, administration, and maintenance (OAM) code block sent by the first node to the second node.

[0070] In a possible implementation, if the small particle time slot following capabilities indicate that the first client has the ability to automatically follow the upstream small particle time slot configuration, then the small particle time slot following capabilities also indicate the following method for the first client to automatically follow the upstream small particle time slot configuration. The following methods include: following through data plane packets and / or following through control plane packets.

[0071] In a third aspect, an embodiment of the present application provides an information processing apparatus, which is applied to a second node. The apparatus includes: a receiving unit, configured to receive a first node identifier and a first interface identifier sent by a first node, where the first node identifier is used to identify the first node, and the first interface identifier is used to identify a first interface of the first node for communicating with the second node; a processing unit, configured to obtain first link information according to the first node identifier, the first interface identifier, a second node identifier, and a second interface identifier, where the second node identifier is used to identify the second node, the second interface identifier is used to identify a second interface of the second node for communicating with the first node, and the first link information is used to indicate a first link between the first interface and the second interface, and the first link is a link for carrying large-granularity services or a link for carrying small-granularity services.

[0072] In a possible implementation manner, the receiving unit is configured to: receive a first Link Layer Discovery Protocol (LLDP) packet sent by the first node, where the first LLDP packet includes a first Type-Length-Value (TLV), and the first TLV includes the first node identifier and the first interface identifier.

[0073] In a possible implementation manner, the first TLV includes a first sub-TLV and a second sub-TLV, the first sub-TLV includes the first node identifier, and the second sub-TLV includes the first interface identifier.

[0074] In a possible implementation manner, the first TLV is a vendor TLV.

[0075] In a possible implementation manner, if the first link is a link for carrying large-granularity services, then: the first interface identifier includes: a first FlexE group identifier corresponding to the first node, and the first FlexE group identifier is used to identify a first FlexE group corresponding to the first node; the second interface identifier includes: a second FlexE group identifier corresponding to the second node, and the second FlexE group identifier is used to identify a second FlexE group corresponding to the second node.

[0076] In a possible implementation manner, the first link is a link between a first physical interface of the first node and a second physical interface of the second node. The receiving unit is configured to: receive the first LLDP packet through an overhead (OH) channel corresponding to the first link, where the OH channel corresponding to the first link is used to carry link information of the first link.

[0077] In a possible implementation, the receiving unit is configured to: receive the first LLDP packet through a common OH channel, where link information of multiple links carrying large granularity services between the first node and the second node is transmitted through the common OH channel.

[0078] In a possible implementation, the first link is a link between a first physical interface of the first node and a second physical interface of the second node, and the identifier of the first physical interface is further included in the first LLDP packet.

[0079] In a possible implementation, the processing unit is specifically configured to: determine a second physical interface connected to the first physical interface according to the identifier of the first physical interface; and obtain the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier when the second physical interface is fault-free.

[0080] In a possible implementation, the processing unit is further configured to: determine the link attributes of the first link, where the link attributes of the first link include at least one of the following: the identifier of the first physical interface, the identifier of the second physical interface, additional attributes of the first physical interface, and additional attributes of the second physical interface.

[0081] In a possible implementation, the target physical interface includes the first physical interface or the second physical interface, and the additional attributes of the target physical interface include one or more of the following: the large granularity capability supported by the target physical interface, the configured bandwidth of the target physical interface, the remaining bandwidth of the target physical interface, and the available time slots of the target physical interface.

[0082] In a possible implementation, the large granularity capability supported by the target physical interface includes one or more of the following: the granularity carrying capability supported by the target physical interface, cross-PHY bundling capability, dynamic large granularity channel capability, static large granularity channel capability, and large granularity time slot following capability, where the target physical interface having the dynamic large granularity channel capability indicates that the target physical interface can participate in the calculation of a dynamic end-to-end path, the target physical interface having the static large granularity channel capability indicates that the target physical interface can establish a static end-to-end path through static configuration, both the dynamic end-to-end path and the static end-to-end path are paths carrying large granularity services, and the large granularity time slot following capability is used to indicate whether the target physical interface has the ability to automatically follow the upstream large granularity time slot configuration.

[0083] In a possible implementation, the device further includes: receiving additional attributes of the first physical interface sent by the first node.

[0084] In a possible implementation, the first TLV of the first LLDP packet further includes a third sub-TLV, and the third sub-TLV includes the large granule capability supported by the first physical interface.

[0085] In a possible implementation, if the large granule time slot following capability indicates that the target physical interface has the ability to automatically follow the upstream large granule time slot configuration, the large granule time slot following capability further indicates the following mode of the target physical interface automatically following the upstream large granule time slot configuration, and the following mode includes: following through data plane packets and / or following through control plane packets.

[0086] In a possible implementation, the receiving unit is further configured to: receive a second LLDP packet sent by the first node, where the second LLDP packet includes the first node identifier and the first interface identifier; the processing unit is further configured to obtain second link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier, the second link information is the same as the first link information, the second link information is used to identify a second link between the first interface and the second interface, the second link is a link carrying large granule services, and the second link is a link between a third physical interface of the first node and a fourth physical interface of the second node; determine link attributes of the second link, and the link attributes of the second link include at least one of the following: an identifier of the third physical interface, an identifier of the fourth physical interface, additional attributes of the third physical interface, and additional attributes of the fourth physical interface.

[0087] In a possible implementation, the processing unit is further configured to: merge the first link information, the second link information, the link attributes of the first link, and the link attributes of the second link to obtain target link information and target link attributes, the target link information is the first link information, and the target link attributes include the link attributes of the first link and the link attributes of the second link.

[0088] In a possible implementation, the device further includes: a sending unit, configured to send the target link information and the target link attributes to a controller.

[0089] In a possible implementation, if the first link is a link carrying small particle services, then: the first interface identifier includes: the first client identifier corresponding to the first node, and the first client identifier is used to identify the first client corresponding to the first node; the second interface identifier includes: the second client identifier corresponding to the second node, and the second client identifier is used to identify the second client corresponding to the second node.

[0090] In a possible implementation, the first client identifier is the index of the first client; or, the first client identifier is determined according to the transmission identifier of the first client and the identifier of the FlexE group to which the first client belongs; or, in a scenario where physical ports are directly divided into sub-time slots, the first client identifier is the identifier of the physical interface from which the first client is divided, or the first client identifier is the interface index of the first client.

[0091] In a possible implementation, the first link is a link between the first client of the first node and the second client of the second node, and the receiving unit is configured to: receive the first LLDP message through the general communication channel (GCC) corresponding to the first link.

[0092] In a possible implementation, the receiving unit is configured to: receive the first LLDP message through the general GCC, where the link information of multiple links carrying small particle services between the first node and the second node is transmitted through the general GCC channel.

[0093] In a possible implementation, the first link is a link between the first client of the first node and the second client of the second node, and the first LLDP message further includes the transmission identifier of the first client.

[0094] In a possible implementation, the processing unit is specifically configured to: determine the second client connected to the first client according to the transmission identifier of the first client; and obtain the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier when the second client is fault-free.

[0095] In a possible implementation, the processing unit is further configured to: determine the link attributes of the first link, where the link attributes of the first link include at least one of the following: the identifier of the first client, the identifier of the second client, the additional attributes of the first client, and the additional attributes of the second client.

[0096] In a possible implementation, the target client includes the first client or the second client, and the additional attributes of the target client include one or more of the following: the small-granule capabilities supported by the target client, the configured bandwidth of the target client, the remaining bandwidth of the target client, and the available sub-slots of the target client.

[0097] In a possible implementation, the small-granule capabilities supported by the target client include one or more of the following: whether the target client supports small-granule technology, dynamic small-granule channel capabilities, static small-granule channel capabilities, and small-granule time-slot following capabilities. Among them, the target client having the dynamic small-granule channel capabilities indicates that the target client can participate in the calculation of the dynamic end-to-end path, and the target client having the static small-granule channel capabilities indicates that the target client can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths for carrying small-granule services, and the small-granule time-slot following capabilities are used to indicate whether the target client has the ability to automatically follow the upstream small-granule time-slot configuration.

[0098] In a possible implementation, the receiving unit is further configured to: receive the additional attributes of the first client sent by the first node.

[0099] In a possible implementation, the first TLV of the first LLDP packet further includes a fourth sub-TLV, and the fourth sub-TLV includes the small-granule capabilities supported by the first client; or, the small-granule capabilities supported by the first client are carried by the operation, administration, and maintenance (OAM) code block sent by the first node to the second node.

[0100] In a possible implementation, if the small-granule time-slot following capabilities indicate that the target client has the ability to automatically follow the upstream small-granule time-slot configuration, then the small-granule time-slot following capabilities further indicate the following method for the target client to automatically follow the upstream small-granule time-slot configuration, and the following method includes: following through data-plane packets and / or following through control-plane packets.

[0101] In a possible implementation, the sending unit included in the device is configured to: send the first link information and the link attributes of the first link to the controller.

[0102] In a possible implementation, the device further includes: sending the second node identifier and the second interface identifier to the first node, so that the first node obtains the first link information based on the second node identifier, the second interface identifier, and the first node identifier and the first interface identifier.

[0103] In a fourth aspect, an embodiment of the present application provides an information processing device, which is applied to a first node. The device includes: a processing unit, configured to obtain a first node identifier and a first interface identifier, where the first node identifier is used to identify the first node, and the first interface identifier is used to identify a first interface of the first node for communicating with a second node; a sending unit, configured to send the first node identifier and the first interface identifier to the second node, where the first node identifier and the first interface identifier are used to enable the second node to obtain first link information, and the first link information is used to indicate a first link between the first interface and a second interface of the second node, and the first link is a link carrying large-granularity services or a link carrying small-granularity services.

[0104] In a possible implementation, the sending unit is configured to: send a first Link Layer Discovery Protocol (LLDP) message to the second node, where the first LLDP message includes a first Type-Length-Value (TLV), and the first TLV includes the first node identifier and the first interface identifier.

[0105] In a possible implementation, the first TLV includes a first sub-TLV and a second sub-TLV, the first sub-TLV includes the first node identifier, and the second sub-TLV includes the first interface identifier.

[0106] In a possible implementation, the first TLV is a vendor TLV.

[0107] In a possible implementation, if the first link is a link carrying large-granularity services, then: the first interface identifier includes: a first FlexE group identifier corresponding to the first node, and the first FlexE group identifier is used to identify the first FlexE group corresponding to the first node.

[0108] In a possible implementation, the first link is a link between a first physical interface of the first node and a second physical interface of the second node. The sending unit is configured to: send the first LLDP packet to the second node through an overhead OH channel corresponding to the first link, where the OH channel corresponding to the first link is used to carry link information of the first link.

[0109] In a possible implementation, the sending unit is configured to: send the first LLDP packet to the second node through a common OH channel, where link information of multiple links carrying large granularity services between the first node and the second node is transmitted through the common OH channel.

[0110] In a possible implementation, the first link is a link between a first physical interface of the first node and a second physical interface of the second node, and the first LLDP packet further includes an identifier of the first physical interface.

[0111] In a possible implementation, the sending unit is further configured to: send additional attributes of the first physical interface to the second node.

[0112] In a possible implementation, the additional attributes of the first physical interface include one or more of the following: large granularity capabilities supported by the first physical interface, configured bandwidth of the first physical interface, remaining bandwidth of the first physical interface, and available time slots of the first physical interface.

[0113] In a possible implementation, the large granularity capabilities supported by the first physical interface include one or more of the following: granularity bearing capabilities supported by the first physical interface, cross-PHY bundling capabilities, dynamic large granularity channel capabilities, static large granularity channel capabilities, and large granularity time slot following capabilities. Wherein, the first physical interface having the dynamic large granularity channel capabilities indicates that the first physical interface can participate in the calculation of dynamic end-to-end paths, and the first physical interface having the static large granularity channel capabilities indicates that the first physical interface can establish static end-to-end paths through static configuration. Both the dynamic end-to-end paths and the static end-to-end paths are paths for carrying large granularity services, and the large granularity time slot following capabilities are used to indicate whether the first physical interface has the ability to automatically follow the upstream large granularity time slot configuration.

[0114] In a possible implementation, a first TLV of the first LLDP packet further includes a third sub-TLV, and the third sub-TLV includes the large granularity capabilities supported by the first physical interface.

[0115] In a possible implementation, if the large-granularity time slot following ability indicates that the first physical interface has the ability to automatically follow the upstream large-granularity time slot configuration, then the large-granularity time slot following ability also indicates the following method for the first physical interface to automatically follow the upstream large-granularity time slot configuration, and the following method includes: following through data-plane packets and / or following through control-plane packets.

[0116] In a possible implementation, if the first link is a link carrying small-granularity services, then: the first interface identifier includes: the first client identifier corresponding to the first node, and the first client identifier is used to identify the first client corresponding to the first node.

[0117] In a possible implementation, the first client identifier is the index of the first client; or, the first client identifier is determined according to the transmission identifier of the first client and the identifier of the FlexE group to which the first client belongs; or, in a scenario where sub-time slots are directly divided for a physical port, the first client identifier is the identifier of the physical interface obtained by dividing to obtain the first client, or the first client identifier is the interface index of the first client.

[0118] In a possible implementation, the first link is a link between the first client of the first node and the second client of the second node, and the sending unit is configured to: send the first LLDP packet to the second node through the general communication channel GCC corresponding to the first link.

[0119] In a possible implementation, the sending unit is configured to: send the first LLDP packet to the second node through the general GCC, where the link information of multiple links carrying small-granularity services between the first node and the second node is transmitted through the general GCC channel.

[0120] In a possible implementation, the first link is a link between the first client of the first node and the second client of the second node, and the transmission identifier of the first client is further included in the first LLDP packet.

[0121] In a possible implementation, the sending unit is further configured to: send the additional attributes of the first client to the second node.

[0122] In a possible implementation, the additional attributes of the first client include one or more of the following: the small particle capabilities supported by the first client, the configured bandwidth of the first client, the remaining bandwidth of the first client, and the available sub-slots of the first client.

[0123] In a possible implementation, the small particle capabilities supported by the first client include one or more of the following: whether the first client supports small particle technology, dynamic small particle channel capabilities, static small particle channel capabilities, and small particle time slot following capabilities. Among them, the first client having the dynamic small particle channel capabilities indicates that the first client can participate in the calculation of the dynamic end-to-end path. The first client having the static small particle channel capabilities indicates that the first client can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths carrying small particle services. The small particle time slot following capabilities are used to indicate whether the first client has the ability to automatically follow the upstream small particle time slot configuration.

[0124] In a possible implementation, the first TLV of the first LLDP packet further includes a fourth sub-TLV, and the fourth sub-TLV includes the small particle capabilities supported by the first client; or, the small particle capabilities supported by the first client are carried by the operation, administration, and maintenance (OAM) code block sent by the first node to the second node.

[0125] In a possible implementation, if the small particle time slot following capabilities indicate that the first client has the ability to automatically follow the upstream small particle time slot configuration, then the small particle time slot following capabilities further indicate the following method for the first client to automatically follow the upstream small particle time slot configuration. The following method includes: following through data plane packets and / or following through control plane packets.

[0126] In a fifth aspect, an embodiment of the present application provides an information processing device, including: a communication interface and a processor. According to the communication interface and the processor, the communication device executes the method according to any one of the above first aspects or any one of the above second aspects.

[0127] In a specific design, the above information processing device may be a chip, the above communication interface includes an interface circuit, and the processor includes a processing circuit. The interface circuit may include an input circuit and an output circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, so that any implementation manner of any aspect in the first aspect is implemented, or any implementation manner of any aspect in the second aspect is implemented.

[0128] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions or a computer program, which, when running on a processor, execute the method described in any item of the above first aspect, or, when running on a processor, execute the method described in any item of the above second aspect.

[0129] In a seventh aspect, an embodiment of the present application provides a computer program product, including a computer program product, which, when running on a processor, executes the method described in any item of the above first aspect or any item of the above second aspect.

[0130] In an eighth aspect, an embodiment of the present application provides a chip system, which may include a processor. The processor is coupled to a memory and is configured to execute any implementation manner in the above first aspect, or the processor is coupled to a memory and is configured to execute any implementation manner in the above second aspect. Optionally, the chip system further includes a memory. The memory is used to store a computer program (which may also be referred to as code or instructions). The processor is configured to call and run the computer program from the memory, so that a device installed with the chip system executes any implementation manner of the first aspect or any implementation manner of the second aspect.

[0131] In a ninth aspect, an embodiment of the present application provides an information processing device, including: an interface circuit and a processing circuit. The interface circuit may include an input circuit and an output circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, so that any implementation manner of the first aspect is implemented, or any implementation manner of the second aspect is implemented. In a specific implementation, the processing circuit includes operations performed by a Flexe shim layer.

[0132] In a specific implementation process, the above information processing device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be transistors, gate circuits, flip-flops, and various logic circuits, etc. The input signal received by the input circuit may be received and input by, for example but not limited to, a receiver. The signal output by the output circuit may be output to, for example but not limited to, a transmitter and transmitted by the transmitter. Moreover, the input circuit and the output circuit may be the same circuit, which serves as the input circuit and the output circuit at different times respectively. The present application does not limit the specific implementation manners of the processor and various circuits.

[0133] In another implementation manner, the information processing device may be some components in a first network node, such as integrated circuit products like a system-on-chip or a communication chip, etc. The interface circuit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc. on the chip or chip system. The processing circuit may be the logic circuit on the chip. BRIEF DESCRIPTION OF THE DRAWINGS

[0134] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0135] Figure 1a It is a schematic diagram of an SPN architecture supporting small particle technology provided by an embodiment of the present application;

[0136] Figure 1b It is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0137] Figure 1c It is a schematic diagram of a network structure provided by an embodiment of the present application;

[0138] Figure 1d It is a schematic diagram of static configuration information provided by an embodiment of the present application;

[0139] Figure 2 It is a flowchart of an information processing method provided by an embodiment of the present application.

[0140] Figure 3a It is a schematic diagram of the structure of a vendor TLV provided by an embodiment of the present application;

[0141] Figure 3b It is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application;

[0142] Figure 3cA schematic structural diagram of a manufacturer TLV provided by an embodiment of the present application;

[0143] Figure 3d Another schematic diagram of an exemplary application scenario provided by an embodiment of the present application;

[0144] Figure 3e A schematic diagram of an exemplary application scenario provided by an embodiment of the present application;

[0145] Figure 3f A schematic diagram of another exemplary application scenario provided by an embodiment of the present application;

[0146] Figure 3g A schematic structural diagram of a manufacturer TLV provided by an embodiment of the present application;

[0147] Figure 3h A schematic diagram of an OAM code block provided by an embodiment of the present application;

[0148] Figure 4a A schematic diagram of an exemplary application scenario provided by an embodiment of the present application;

[0149] Figure 4b A schematic flow diagram of an information processing method provided by an embodiment of the present application;

[0150] Figure 4c A schematic flow diagram of an information processing method provided by an embodiment of the present application;

[0151] Figure 4d A schematic structural diagram of a manufacturer TLV provided by an embodiment of the present application;

[0152] Figure 5a A schematic diagram of an exemplary application scenario provided by an embodiment of the present application;

[0153] Figure 5b A schematic flow diagram of an information processing method provided by an embodiment of the present application;

[0154] Figure 5c A schematic flow diagram of an information processing method provided by an embodiment of the present application;

[0155] Figure 5d A schematic structural diagram of a manufacturer TLV provided by an embodiment of the present application;

[0156] Figure 6a A schematic structural diagram of an information processing device provided by an embodiment of the present application;

[0157] Figure 6b A schematic structural diagram of another information processing device provided by an embodiment of the present application;

[0158] Figure 7 Schematic diagram of the structure of a data processing information processing device provided by an embodiment of the present application;

[0159] Figure 8 Schematic diagram of the structure of another data information processing device provided by an embodiment of the present application. Detailed implementation manners

[0160] An embodiment of the present application provides an information processing method, which is beneficial to the maintenance of network information.

[0161] Before introducing the path information processing method provided by an embodiment of the present application, the technologies and / or terms related to the present application are first introduced.

[0162] The large-granularity technology and the small-granularity technology are two relative concepts. They correspond to different bandwidth granularities for carrying customer services. The large-granularity technology has a larger bandwidth granularity for carrying customer services, and the small-granularity service has a smaller bandwidth granularity for carrying customer services.

[0163] The large-granularity technology can correspond to different technical terms in different standards. Correspondingly, the small-granularity technology can correspond to different technical terms in different standards. As an example, the large-granularity technology can be called the FlexE technology; as another example, the large-granularity technology can be called the metro transport network (MTN) technology. Correspondingly, the small-granularity technology can be called the fine grained MTN (fgMTN) technology. As another example, the large-granularity technology can be called the slicing packet network (SPN), and correspondingly, the small-granularity technology can be called the SPN2.0 technology or the fine grained unit (FGU) technology.

[0164] Next, the technical terms related to the large-granularity technology and the small-granularity technology are introduced.

[0165] FlexE group: Each FlexE group includes one or more PHYs. When multiple PHYs are included, the multiple PHYs are physically independent. A network device applying FlexE technology can identify which PHYs are included in a FlexE group by the numbers of the PHYs to achieve the logical bundling of multiple PHYs. For example, the number of each PHY can be identified by a number between 1 and 254, and 0 and 255 are reserved numbers. The number of a PHY can correspond to an interface on the network device. The same number needs to be used to identify the same PHY between two adjacent network devices. The numbers of each PHY included in a FlexE group do not have to be consecutive. Usually, there is one FlexE group between two network devices, but this application does not limit that there is only one FlexE group between two network devices, that is, there can also be multiple FlexE groups between two network devices. One PHY can be used to carry at least one client, and one client can be transmitted on at least one PHY. FlexE can support the mapping and transmission of any number of different FlexE clients on any group of PHYs, so as to achieve functions such as PHY bundling, channelization, and sub-rate. Among them, in the MTN technology, the FlexE group can be called the MTN section (MTN Section, MTNS) group.

[0166] FlexE client: Corresponds to various user interfaces or bandwidths of the network. The FlexE client represents the customer data stream transmitted in the specified time slots (one or more time slots) on the FlexEGroup. Multiple FlexE clients can be carried on one FlexE Group, and one FlexE client can correspond to one to multiple user service data streams (which can also be called MAC clients). The FlexE client can be flexibly configured according to bandwidth requirements and supports Ethernet media access control (MAC) data streams of various rates (such as 10G, 40G, n*25G data streams, and even non-standard rate data streams). For example, the data stream can be transmitted to the FlexE shim layer in the form of 64B / 66B encoding. Customers sent through the same FlexE group need to share the same clock, and these customers need to be adapted according to the allocated time slot rate. In this application, the service data stream of the corresponding FlexE client can be transmitted through the FlexE client (which can also be called the FlexE client interface). The FlexE client interface is a logical interface. Each FlexE interface can be logically divided into one or more FlexE client interfaces. Each FlexE interface can be divided into multiple time slots in the time domain, and each FlexE client interface occupies at least one of the multiple time slots. Among them: 64 / 66B means that the data code block includes 66 bits. The first two bits of the 66 bits are synchronization bits, and the last 64 bits are data bits. In the Physical Coding Sublayer (PCS), the 64 / 66B can be extracted through the first two synchronization bits. Among them, in the MTN technology, the FlexE client can be called the MTN channel (MTN path, MTNP) or the MTNS client.

[0167] FlexE shim: As an additional logical layer inserted between the MAC and PHY (PCS) in the traditional Ethernet architecture, it is the core architecture for implementing FlexE technology based on the time slot distribution mechanism. For the transmitting end, the main function of the FlexE shim is to encapsulate data into pre-divided time slots (slots). Then, according to the FlexE time slot table, each divided time slot is mapped to the PHY in the FlexE group for transmission. Among them, each time slot is mapped to a PHY in the FlexE group. Taking the 100GE PHY as an example, the FlexE Shim layer can divide each 100GE PHY in the FlexE Group into 20 data-carrying channels of time slots (slots), and the bandwidth corresponding to each slot is 5Gbps. Every time the PHY sends 1023 * 20 Slot of 64 / 66B data, a FlexE overhead (OH) is inserted to inform the receiving end how to parse the received data.

[0168] Small-granularity services: In some embodiments, the slots corresponding to large bandwidth can be further divided into multiple sub-slots to carry customer services with smaller bandwidth requirements. The above services are also referred to as small-granularity services. For example, the above large bandwidth can be understood as the bandwidth corresponding to the service layer of the small-granularity service. For example, when the service layer of the small-granularity service is the MTN channel layer, the bandwidth of the MTN channel layer is 5Gbps. The slot corresponding to the large bandwidth of 5Gbps is further divided into 480 sub-slots at a granularity of 10Mbps, and these 480 sub-slots are used to carry small-granularity services. For example, the 1st sub-slot, the 3rd sub-slot, and the 5th sub-slot among these 480 sub-slots are used to carry small-granularity service 1. Another example is when the service layer of the small-granularity service is the 10GE Ethernet physical layer, the corresponding large bandwidth is further divided into multiple sub-slots at a finer granularity to carry small-granularity services. Thus, it can be seen that the bandwidth granularity of small-granularity is finer. For example, the bandwidth requirement of the dedicated power line service is 10Mbps. At this time, the small-granularity technology can be used to allocate a specified bandwidth for the dedicated power line service to carry the service traffic of the dedicated power line service. The above dedicated power line service is a kind of small-granularity service.

[0169] Among them, when transmitting fine-grained services, for the transmitting end, in one example, the FlexE shim can encapsulate data into pre-divided sub-slots according to the time slot configuration of the fine grains for transmission. For the receiving end, the FlexE shim can restore the data received through the slot with a corresponding bandwidth of 5 Gbps into the original fine-grained service data according to the time slot configuration of the fine grains and continue the transmission. In another example, for the transmitting end, the data can be encapsulated into the corresponding sub-slots for transmission by using the MTN channel layer adaptation function (MTN path adaptation function). For the receiving end, the data received through the slot with a corresponding bandwidth of 5 Gbps can be restored into the original fine-grained service data by using the MTN channel layer adaptation function and continue the transmission. In one example, the fine-grained service data can be carried in the fine granularity unit (FGU) base frame. In one example, the fine granularity unit can also be referred to as the fine granularity basic unit (fgBU). In the following description, the two can be used interchangeably.

[0170] Regarding the FlexE OH insertion method and the structure of the overhead frame, in a specific implementation, the relevant description part of FlexE in the optical internetworking forum (OIF) can be referred to, and details are not described here.

[0171] Next, a possible SPN architecture supporting fine-grained technology is introduced. See Figure 1a , which is a schematic diagram of an SPN architecture supporting fine-grained technology provided by an embodiment of this application.

[0172] As Figure 1a shown, the SPN architecture includes a slicing packet layer (SPL), a slicing channel layer (SCL), a slicing transport layer (STL), a software-defined network (SDN) slice control plane integrating management and control, and an ultra-high-precision time and frequency synchronization technology.

[0173] SCL includes the FGU layer, the MTN channel (MTN path, MTNP) layer, and the MTN section (MTN Section, MTNS) layer. The FGU layer provides an end-to-end deterministic low-latency N*10Mbps granularity hard slice channel for small granularity services. The FGU layer is an independent sub-layer and can be flexibly selected to be carried on the MTN channel layer or the Ethernet physical layer as needed. In other words, the service layer of the FGU layer can be either the MTN channel layer or the Ethernet physical layer.

[0174] Based on the original high-speed Ethernet physical layer interface, STL has added a 10GE Ethernet physical layer interface. The 10GE Ethernet physical layer can be applied to the customer-premises equipment (CPE) scenario and directly carry the FGU layer.

[0175] Next, taking the MTN channel layer carrying small granularity services as an example, the MTNS and MTNP are introduced from the perspectives of the sending-side behavior and the receiving-side behavior.

[0176] First, the sending-side behavior and the receiving-side behavior of MTNS are introduced.

[0177] In an example, taking 100GBASE-R PHY as an example, MTNS provides a point-to-point connection, is responsible for time-slotting the adjacent nodes connected by the Ethernet PHY, and provides functions of binding, sub-rate, and channelization. MTNS is bidirectional and symmetric. Here, an example of one data transmission direction is used for illustration.

[0178] On the sending side, MTNS inserts a special O code block into the 66B code block sequence, inserts a D code block after every 1023*20 66B code blocks, inserts a D code block after every 1023*20 66B code blocks, and a total of 7 D code blocks need to be inserted. After inserting the 7th D code block, after another 1023*20 code blocks, a special O code block is inserted. In this way, a total of 8*(1023*20 + 1) code blocks constitute an MTNS frame. The O code block plus the aforementioned 7 D code blocks constitute the overhead of the MTNS frame. The overhead carries some point-to-point link configuration information indicating MTNS, such as time-slot configuration information, section layer group configuration information, and so on.

[0179] MTNS continuously sends data to the receiving end according to the above frame structure. The continuous MTNS frames are equivalent to a 66B code block stream, which is converted into bits, optical signals, or other analog signals such as electrical pulses according to the lower PHY layer protocol defined by the Institute of Electrical and Electronics Engineers (IEEE) 802.3 and sent out from the sending-side device.

[0180] At the receiving end, first, according to the protocol of the Ethernet lower PHY layer, the received signal (such as bits, optical signals, or other analog signals such as electrical pulses) locks the frame header of the MTNS frame by identifying the O code block. According to the fixed count, it can be known that the next overhead code block appears after 1023 * 20 code blocks. Correspondingly, the receiving end can determine the positions of the data corresponding to each time slot in the received signal according to the O code block.

[0181] MTNS can only provide point-to-point connections, while MTNP is responsible for providing "end-to-end channel connections" from the network entrance to the network exit. MTNP provides end-to-end rigid hard pipe connections and provides operation, administration, maintenance, and protection (OAM&P) functions. A typical network configuration of MTNP can be referred to Figure 1b as shown Figure 1b which is a schematic diagram of a network architecture provided by an embodiment of this application.

[0182] Next, in combination with Figure 1b the sending-side behavior and receiving-side behavior of MTNP will be introduced.

[0183] As Figure 1b shown, there is an end-to-end MTNP between provider edge (PE) 1 and PE2, and a point-to-point MTNS between PE1 and PE2.

[0184] On the network-to-network interface (NNI) side of PE1, the MTNP layer obtains the client signal from the MAC layer, and the client signal can be a MAC frame. The MAC mentioned here can be the processing module of the MAC layer. After the MTNP layer obtains the MAC frame, it encodes the MAC frame into a sequence of 64 / 66B code blocks. Specifically, each MAC frame will be encoded into a sequence of 66B code blocks bounded by a start code block (S code block) and an end code block (i.e., T code block). A series of MAC frame sequences will be encoded into a series of 66B code block sequences. Then, PE1 can complete the MTNP OAM insertion in the MTNP. After PE1 completes the MTNP OAM insertion in the MTNP, it maps the 66B code block sequence containing the OAM code block to the pre-configured and specified MTNS time slot. Subsequently, PE1 sends the data out according to the behavior of the MTNS sending side described above.

[0185] In one example, if there is no valid MAC frame waiting to be sent, then the MTNP fills the 66B code block with I code blocks to ensure that there is always data being sent in the hard pipeline of the MTNP.

[0186] On the receiving side of the P node, first, according to the receiving side behavior of the MTNS described above, it identifies the MTNS frame. Subsequently, according to the pre-configuration, it recovers the MTNP data from the specified MTNS time slot. The P node then performs MTNP forwarding. It should be noted here that the essential difference between MTNP forwarding and IP forwarding and MAC bridge forwarding is that MTNP forwarding exclusively occupies the device forwarding resources and does not support statistical multiplexing. The same number of MTNS time slots need to be configured at both the entrance and the exit of the network node (such as the P node).

[0187] As described above, in some embodiments, the slot corresponding to the large bandwidth can be further divided into multiple sub-slots for carrying small-granularity services. For example, a slot with a corresponding bandwidth of 5 Gbps is further divided at a granularity of 10 Mbps into 480 sub-slots, and these 480 sub-slots are used to carry small-granularity services. In this case, the MTNFGU further divides 480 10-Mbps time slots in the 5-Gbps MTNP in a hierarchical manner. In this scenario, the MTNP and the MTN FGU can be decoupled, and at this time, the MTNP serves as the service layer of the MTN FGU. In one example, a fine-grained basic unit (fg-BU) is the basic unit for the FGU to carry information. The fg-BU may include FGU base frame overhead and FGU base frame payload. Among them, the FGU base frame overhead can be used to carry small-granularity time slot information, and the FGU base frame payload is used to carry the small-granularity service data. Among them, the small-granularity time slot information can be the mapping relationship between the sub-slot and the sub-client. The sub-client is similar to the FlexE client and also corresponds to various user interfaces or bandwidths of the network. The difference from the FlexE client is that the sub-client represents the client data stream transmitted on the sub-slot, and one sub-client can correspond to one or more sub-slots.

[0188] For the scenario of further dividing a slot with a corresponding bandwidth of 5 Gbps at a granularity of 10 Mbps, in one example, an FGU base frame may include 24 sub-time slots, each sub-time slot includes 65 bytes, and each sub-time slot can carry 8 code blocks of 65 bits. In other words, the aforementioned base frame payload can include 65 * 24 = 1560 bytes. 20 FGU base frames form a multiplexed frame, and 24 × 20 = 480 sub-time slots are provided in the multiplexed frame. For the NNI transmission side of PE1, like the MTNP, the MTN FGU layer first encodes the MAC frame client signal into a 66B code block sequence and then inserts the OAM code block. It should be noted at this time that the OAM code block of the small-granularity MTNP (fgMTNP) is inserted in the MTN FGU layer, rather than the OAM code block of the MTNP. Subsequently, a series of 66B code block sequences containing the fgMTNP OAM code block are mapped into the 10-Mbps time slot specified according to the pre-configuration in the fg-BU.

[0189] The fgBU sequence itself is actually a string of 66B code blocks, which can be equivalent to the customer signal of MTNP. After inserting the MTNP OAM code block, according to the behavior of the MTNP transmitting side described above, it is mapped into the time slots specified by MTNS.

[0190] On the receiving side of the P node, according to the behavior of the MTNP receiving side described above, the MTNP signal is restored, and then the OAM code block in the MTNP is extracted. After the receiving side of the P node restores the MTNP signal, the framing of fg-BU can be completed by searching for the S code block.

[0191] The P node performs fgMTNP forwarding. The fgMTNP forwarding, like the MTNP forwarding, is TDM forwarding, occupying the exclusive device forwarding resources and not supporting statistical multiplexing. The P node will not terminate the OAM code block of fgMTNP.

[0192] The behavior of the transmitting side of the P node is the reverse process of the behavior of the receiving side of the P node, which will not be elaborated here. In addition, the behavior of the receiving side of the PE2 node is the reverse process of the behavior of the transmitting side of the PE1 node, which will not be elaborated here.

[0193] Regarding Figure 1a For other contents in the SPN architecture shown, reference can be made to the relevant descriptions in the China Mobile SPN small-granularity white paper, which will not be elaborated here.

[0194] Although in the above description, the MAC frame is encoded using the 64 / 66B encoding method, the above is only shown as a possible implementation method, and the encoding technology used to encode the MAC frame is not limited to the 64 / 66B described above. For example, the MAC frame can also be encoded using the 64 / 65B encoding method; or, the MAC frame can also be encoded using the 256 / 257B encoding method, etc., which will not be listed one by one here. Currently, if large-granularity technology is to be deployed in the network, the path carrying large-granularity services can be configured through static configuration. Correspondingly, if small-granularity technology is to be deployed in the network, the path carrying small-granularity services can be configured through static configuration.

[0195] Next, taking the small-granularity technology as an example, the current deployment method of the small-granularity technology will be introduced.

[0196] Step 1: The controller can obtain the static physical layer topology.

[0197] Among them, the static network topology can be understood as the network topology reported by the node to the controller based on the configuration information obtained by the controller by sending the configuration information for obtaining the network topology to the node.

[0198] Step 2: The controller can calculate the end-to-end path for the service based on the static physical layer topology. Refer to Figure 1c for understanding. Figure 1c This is a schematic diagram of a network structure provided by an embodiment of the present application. In one example, the calculated end-to-end path can be: PE1 - P1 - P2 - PE2.

[0199] Step 3: The controller decomposes the end-to-end path to obtain the static configuration information corresponding to each node in the end-to-end path. For example, the static configuration information corresponding to PE1, P1, P2, and PE2 can be obtained. For any node, its corresponding static configuration information can include the following three contents:

[0200] 1. Create east-west interface objects. Here, east-west includes east and west, and east and west are two relative concepts. For a node, if the east corresponds to its upstream node, then the west can correspond to its downstream node. Among them, the east corresponding to the upstream node can be understood as the east interface being used to communicate with the upstream node, and the west can correspond to the downstream node, which can be understood as the west interface being used to communicate with the upstream node. Correspondingly, if the east corresponds to its downstream node, then the west can correspond to its upstream node.

[0201] 2. Create fine-grained channel (fg-channel) objects, where the fg-channel is a channel for carrying small-granularity services.

[0202] 3. Configure interface attributes, where the interface attributes can include attributes such as time slots, bandwidth, and the fg-client corresponding to the interface.

[0203] Regarding the static configuration information corresponding to each node, it can be understood in combination with Figure 1d for understanding. Figure 1d This is a schematic diagram of static configuration information provided by an embodiment of the present application. In Figure 1d , taking the west corresponding to the downstream node and the east corresponding to the upstream node as an example for illustration. As Figure 1d shown, for the path PE1 - P1 - P2 - PE2, the channel between PE1 and P1 corresponds to client1, the channel between P1 and P2 corresponds to client2, and the channel between P2 and PE2 corresponds to client3. Then: The static configuration information corresponding to each node can be as shown in the figure. Among them, the content after " / / " in the figure is the annotation part, which is used to explain the meaning of the corresponding static configuration information. Therefore, regarding Figure 1d the meaning of the static configuration information shown, it will not be repeated here.

[0204] Step 4: The controller distributes the static configuration information corresponding to each node to the corresponding node step by step through the Network Configuration Protocol (NETCONF).

[0205] Step 5: Each node processes the received static configuration information to obtain a corresponding forwarding table, so that the static configuration information takes effect, so as to process traffic based on the forwarding table during the traffic forwarding phase. Among them, the processing of the static configuration information by the node includes the following three processes.

[0206] 1. Create objects. For example, create the aforementioned east-west interface object and fg-channel object.

[0207] 2. Hold the aforementioned interface attributes. Specifically, convert the interface attributes into configuration information and store them in a database (DB).

[0208] 3. The static configuration information takes effect, and the interface attributes stored in the DB can be used as a forwarding table to guide traffic forwarding.

[0209] The method of deploying the large-granularity technology is similar to the method of deploying the small-granularity technology. The difference is that when deploying the large-granularity technology, the fg-channel object in the aforementioned step 3 is the MTN-channel object, and the MTN-channel is a channel for carrying large-granularity services. Correspondingly, the fg-client in the configuration interface attributes is the client. Similarly, in step 5, the objects created by the node do not include the fg-channel object but include the MTN-channel object.

[0210] As can be seen from the above description, currently, when the controller calculates the end-to-end path for the service, it uses a static network topology. As previously described, the static network topology is the network topology reported by the node to the controller based on the configuration information issued by the controller. In other words, the node depends on the configuration command of the controller to obtain static link information. Each time a static network topology is obtained, the controller needs to issue corresponding configuration information to the node, which results in a high network maintenance cost.

[0211] To solve or at least partially solve the above problems, the embodiments of the present application provide an information processing method. Next, in combination with the accompanying drawings, this information processing method will be introduced.

[0212] See Figure 2 , which is a schematic flowchart of an information processing method provided by the embodiments of the present application.

[0213] In the embodiments of the present application, a "node" is a network element in a network. In some scenarios, a "node" may also be referred to as a "network device".

[0214] The information processing method provided by the embodiments of the present application can be applied to, for example, Figure 1c the network scenario shown. In this scenario, the first node and the second node can correspond to Figure 1c any two connected nodes. For example, the first node corresponds to PE1, and the second node corresponds to P1 or P3; or, the first node corresponds to P1, and the second node corresponds to P2 or P3; and so on. Details are not listed here one by one.

[0215] Figure 2 The method shown may include the following S101 - S104.

[0216] S101: The first node obtains a first node identifier and a first interface identifier. The first node identifier is used to identify the first node, and the first interface identifier is used to identify the first interface through which the first node communicates with the second node.

[0217] The first node identifier is the unique identifier of the first node and is unique within the network to which the first node belongs. In other words, the node identifiers corresponding to different nodes in the network to which the first node belongs are different. The embodiments of the present application do not specifically limit the first node identifier. In one example, the first node identifier may be the label switching router identifier (LSR ID) of the first node. In another example, the first node identifier may be the loopback address of the first node.

[0218] The first interface identifier is used to identify the first interface. The first node can communicate with the second interface of the second node through the first interface. Among them, the link between the first interface and the second interface is called the first link. The first interface mentioned here can be a physical interface or a logical interface. The first interface identifier is unique on the first node. In other words, for the first node, the node identifiers corresponding to its different interfaces are different.

[0219] In the embodiments of the present application, the first link is a link for carrying large - granularity services, or the first link is a link for carrying small - granularity services. The first interface is related to the type of the first link. Correspondingly, the first interface identifier is also related to the type of the first link.

[0220] In one example, if the first link is a link for carrying large-granularity services, the first interface may be the first FlexE group included in the first node. Correspondingly, the first node identifier may be the identifier of the first FlexE group.

[0221] In another example, if the first link is a link for carrying small-granularity services, the first interface may be the first client included in the first node. Correspondingly, the first interface identifier may be the first client identifier.

[0222] In a specific example, considering that the index of the first client is unique on the first node and it can identify the first client, the first client identifier may be the index of the first client.

[0223] In another specific example, considering that the first node may include multiple FlexE groups, each FlexE group may include multiple clients, each client may correspond to a transmission identifier, the transmission identifier is unique within the FlexE group, and the transmission identifiers of the clients included in different FlexE groups may be the same. Therefore, the combination of the transmission identifier corresponding to the FlexE group and the client is unique on the first node. Therefore, in one example, the first client identifier may also be determined according to the transmission identifier of the first client and the identifier of the FlexE group to which the first client belongs. For example, the first client identifier may be calculated by the following formula (1):

[0224] port-id = (Group-idx << 32) | client-id Formula (1)

[0225] In Formula (1):

[0226] port-id is the first interface identifier;

[0227] Group-idx is the identifier of the FlexE group to which the first client belongs;

[0228] The client-id is the transmission identifier of the first client.

[0229] In another specific example, considering that the client has interface attributes, the node can assign an ifindex to the client it includes, and the ifindex is unique on the node. Therefore, the first client identifier can be the interface index of the first client.

[0230] In yet another specific example, if the small particle technology is implemented by directly dividing time slots of a physical port, considering that the physical interface of the first client obtained by division is unique on the first node, the first client identifier can be the identifier of the physical interface of the first client obtained by division.

[0231] In the embodiment of the present application, the first node can obtain the first node identifier and the first interface identifier by, for example, reading its own configuration information.

[0232] In an example, the first node can obtain the first node identifier and the first interface identifier when the state of the link related to itself changes. Among them, the change in the state of the link related to itself can include various situations. Several possible situations are introduced below.

[0233] As an example, the change in the state of the link related to itself can be that the state of the physical interface included in the first node has changed. For example, fault indication information indicating a physical interface failure is generated.

[0234] As yet another example, if the first node supports large particle services, the change in the state of the link related to itself can be that the number of PHYs (which can also be called physical interfaces) of the first node has changed. For example, a new PHY is created, or an existing PHY is deleted. The change in the state of the link related to itself can also be that the configuration information related to large particles has changed. For example, the time slot configuration has changed, the capabilities have changed, etc. These are not listed one by one here. The capabilities mentioned here can be the large particle capabilities supported by the target physical interface mentioned below. Regarding the large particle capabilities supported by the target physical interface, reference can be made to the relevant description part below, and no detailed description is made here.

[0235] As another example, if the first node supports small-granularity services and the state of the link related to itself changes, it can be that the number of large-granularity objects (clients) of the first node changes. For example, a new client is created, or an existing client is deleted. The change in the state of the link related to itself can also be that the configuration information related to small granularity changes. For example, the time slot configuration changes, the capabilities change, and so on. These are not listed one by one here. The capabilities mentioned here can be the small-granularity capabilities supported by the target client mentioned below. Regarding the small-granularity capabilities supported by the target client, reference can be made to the relevant description part below, and no detailed description is given here.

[0236] S102: The first node sends the first node identifier and the first interface identifier to the second node. The first node identifier and the first interface identifier are used to enable the second node to obtain first link information. The first link information is used to indicate a first link between the first interface and a second interface of the second node. The first link is a link carrying large-granularity services or a link carrying small-granularity services.

[0237] S103: The second node receives the first node identifier and the first interface identifier sent by the first node.

[0238] After the first node obtains the first node identifier and the first interface identifier, it can send the first node identifier and the first interface identifier to the second node. The first node can carry the first node identifier and the first interface identifier in a message and send it to the second node. Correspondingly, the second node can receive the foregoing message sent by the first node, so as to obtain the first node identifier and the first interface identifier carried in the message. The embodiments of the present application do not specifically limit the message, and the message can be any message that supports interaction between nodes.

[0239] In a specific example, the first node can send the foregoing first node identifier and first interface identifier to the second node by sending a first LLDP message to the second node, where the first LLDP message includes the first node identifier and the first interface identifier. In an example, the first LLDP message can be an LLDP message extended based on the optical internet forum neighbor discovery (OIF-ND) protocol.

[0240] The embodiments of the present application do not specifically limit the carrying positions of the first node identifier and the first interface identifier in the first LLDP packet. As an example, the first node identifier and the first interface identifier can be carried through available fields in a traditional LLDP packet. As another example, the first LLDP packet includes a first TLV, and the first node identifier and the first interface identifier are carried through the first TLV.

[0241] The embodiments of the present application do not specifically limit the first TLV. The first TLV can be an existing TLV in the LLDP packet or a newly extended TLV. When the first TLV is an existing TLV in a traditional LLDP packet, the first TLV can be, for example, an organization TLV.

[0242] The embodiments of the present application do not specifically limit the carrying positions of the first node identifier and the first interface identifier in the first TLV. In one example, the first node identifier and the first interface identifier can be carried through the value field of the first TLV. As a specific example, the first TLV can include a first sub-TLV and a second sub-TLV. The first sub-TLV includes the first node identifier, and the second sub-TLV includes the first interface identifier. Among them, the type field of the first sub-TLV is used to indicate that the first sub-TLV is used to carry the first node identifier, and the type field of the second sub-TLV is used to indicate that the second sub-TLV is used to carry the first interface identifier.

[0243] Next, taking the first TLV as the organization TLV as an example, the structure of the first TLV will be described. Refer to Figure 3a , Figure 3a which is a schematic diagram of the structure of an organization TLV provided by the embodiments of the present application.

[0244] As Figure 3a shown, the organization TLV includes: a type field (whose value is 127), a length field, an organizationally unique identifier (OUI) field, and a sub-TLV field. In the embodiments of the present application, the sub-TLV field includes a first sub-TLV and a second sub-TLV. The value field of the first sub-TLV is used to carry the aforementioned first node identifier, and the value field of the second sub-TLV is used to carry the aforementioned first interface identifier. Among them, for any one of the first sub-TLV and the second sub-TLV, the length of its value field can be fixed. In this case, this sub-TLV may not include a length field. Of course, the length of the value field of this sub-TLV can also be flexibly defined. In this case, the length of the value field is determined by the length field of this sub-TLV (Figure 3a (not shown in the figure) indication.

[0245] As described above, the first link may be a link for carrying large - granularity services. For this case, in one example, the first link may be a link between the first physical interface of the first node and the second physical interface of the second node. For this case, when the first node sends the first LLDP packet to the second node, there are multiple implementation manners in specific implementation. Two possible implementation manners are introduced below.

[0246] In one example, the first node may send the first LLDP packet to the second node through the OH channel corresponding to the first link. It can be understood in combination with Figure 3b for understanding. Figure 3b This is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application. As Figure 3b shown, the first node includes a first FlexE group, the first FlexE group includes a first physical interface, the second node includes a second FlexE group, the second FlexE group includes a second physical interface, then the first link between the first physical interface and the second physical interface includes a corresponding OH channel, and the first node may send the first LLDP packet to the second node through the OH channel.

[0247] In this scenario, the OH channel corresponding to the first link can be used to carry the link information of the first link, rather than the link information of other links. Once the first link fails, the OH channel corresponding to the first link becomes unavailable. Correspondingly, the second node cannot receive the first LLDP packet sent by the first node. In other words, if the second node can receive the first LLDP packet, it means that the first link is fault - free. Therefore, by adopting this method, the link information of the faulty link can be naturally not discovered, and the link information received by the second node is the link information of the fault - free link. Among them, the link information of the first link may include at least one of the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier.

[0248] In another example, the first node may send the first LLDP packet to the second node through a general OH channel. Among them, the link information of multiple links carrying large-granularity services between the first node and the second node is all transmitted through the general OH channel. In other words, if there are N links carrying large-granularity services between the first node and the second node, the link information of each link among the N links carrying large-granularity services can be transmitted through this general OH channel, and the general OH channel is no longer uniquely bound to a certain link carrying large-granularity services. It is precisely because the general OH channel is no longer uniquely bound to a certain link that, in order to enable the second node to determine which link the received first node identifier and first interface identifier specifically correspond to, the foregoing first LLDP packet may further include an identifier of the first physical interface. In this way, the second node can determine that the first node identifier and the first interface identifier are for the link corresponding to the first physical interface based on the identifier of the first physical interface. In a specific example, the identifier of the first physical interface may be carried by a sub-TLV in the first TLV. Taking the first TLV as the vendor TLV as an example, in addition to including the foregoing first sub-TLV and second sub-TLV, the vendor TLV may further include a sub-TLV for carrying the identifier of the first physical interface. For this case, the structure of the vendor TLV may be as Figure 3c shown, Figure 3c is a schematic structural diagram of a vendor TLV provided by an embodiment of the present application. Among them, Figure 3c the shown vendor TLV compared with Figure 3a the shown vendor TLV, has one more sub-TLV 301 for carrying the identifier of the physical interface.

[0249] can be understood with reference to Figure 3d for understanding, Figure 3d is another schematic diagram of an exemplary application scenario provided by an embodiment of the present application. As Figure 3d shown, the first node includes a first FlexE group, the first FlexE group includes a first physical interface and a third physical interface, the second node includes a second FlexE group, the second FlexE group includes a second physical interface and a fourth physical interface, the first physical interface is connected to the second physical interface, the third physical interface is connected to the fourth physical interface, and there is also a general OH channel between the first node and the second node. Specifically, there is a general OH channel between the first FlexE group and the second FlexE group. The first node may send the first LLDP packet to the second node through the general OH channel. For this case, in addition to including the first node identifier and the first interface identifier, the first LLDP packet further includes an identifier of the first physical interface.

[0250] As described above, the first link may be a link for carrying small particle services. For this case, in one example, the first link may be a link between the first client of the first node and the second client of the second node. For this case, when the first node sends the first LLDP packet to the second node, there may be multiple implementation manners in specific implementation. The following introduces two possible implementation manners.

[0251] In one example, the first node may send the first LLDP packet to the second node through the GCC corresponding to the first link. It can be understood in combination with Figure 3e this. Figure 3e FIG. is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application. As Figure 3e shown, the first node includes a first client, and the second node includes a second client. Then, the first link between the first client and the second client includes a corresponding GCC. The first node may send the first LLDP packet to the second node through the GCC.

[0252] In this scenario, the GCC corresponding to the first link can be used to carry the link information of the first link, rather than the link information of other links. Once the first link fails, the GCC corresponding to the first link becomes unavailable. Correspondingly, the second node cannot receive the first LLDP packet sent by the first node. In other words, if the second node can receive the first LLDP packet, it means that the first link is fault-free. Therefore, by adopting this method, the link information of the faulty link can be naturally not discovered, and the link information received by the second node is the link information of the fault-free link. Among them, the link information of the first link may include at least one of a first node identifier, a first interface identifier, a second node identifier, and a second interface identifier.

[0253] In another example, as Figure 3f shown, Figure 3f FIG. is a schematic diagram of another exemplary application scenario provided by an embodiment of the present application. As Figure 3f shown, the first node includes a first client and a third client, the second node includes a second client and a fourth client, and a general GCC is included between the first node and the second node. The link information of multiple links carrying small particle services between the first node and the second node is all transmitted through the general GCC. For example, the link information corresponding to the link between the first client and the second client, and the link information corresponding to the link between the third client and the fourth client can both be transmitted through the general GCC. In other words, the general GCC is no longer uniquely bound to a certain link carrying small particle services.

[0254] For this case, the first node may send the first LLDP packet to the second node through the general GCC. Since the general GCC is no longer uniquely bound to a certain link, in order for the second node to determine which link the received first node identifier and the first interface identifier specifically correspond to, the foregoing first LLDP packet may further include the transmission identifier of the first client. In this way, the second node can determine, based on the transmission identifier of the first client, that the first node identifier and the first interface identifier are for the link corresponding to the first client. The transmission identifier of the first client is the same as the transmission identifier of the second client. Therefore, the second node can determine the second client based on the transmission identifier of the first client, and further locate the first link as the link connected to the second client.

[0255] In a specific example, the transmission identifier of the first client may be carried by a sub-TLV in the first TLV. Taking the first TLV as the vendor TLV as an example, in addition to including the foregoing first sub-TLV and second sub-TLV, the vendor TLV may further include a sub-TLV for carrying the transmission identifier of the first client. For this case, the structure of the vendor TLV may be as Figure 3g shown Figure 3g which is a schematic structural diagram of a vendor TLV provided by an embodiment of the present application. Among them, Figure 3g the shown vendor TLV compared with Figure 3a the shown vendor TLV has one more sub-TLV 302 for carrying the transmission identifier of the first client.

[0256] S104: The second node obtains first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier. The second node identifier is used to identify the second node, and the second interface identifier is used to identify the second interface of the second node for communicating with the first node.

[0257] After receiving the first LLDP packet, the second node may obtain the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier. In an example, the first link information may include a quadruple, which are respectively: the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier.

[0258] The second node identifier is the unique identifier of the second node and is unique within the network to which the second node belongs. The embodiments of the present application do not specifically limit the second node identifier. In one example, the second node identifier may be the LSR ID of the second node. In another example, the second node identifier may be the loopback address of the second node.

[0259] The second interface identifier is used to identify the second interface through which the second node can communicate with the first interface of the first node. The second interface mentioned here can be a physical interface or a logical interface. The second interface identifier is unique on the second node.

[0260] In the embodiments of the present application, the first link is a link for carrying large-granularity services, or the first link is a link for carrying small-granularity services. The second interface is related to the type of the first link, and correspondingly, the second interface identifier is also related to the type of the first link.

[0261] In one example, if the first link is a link for carrying large-granularity services, the second interface may be the second FlexE group included in the second node. Correspondingly, the second node identifier may be the identifier of the second FlexE group.

[0262] In another example, if the first link is a link for carrying small-granularity services, the second interface may be the second client included in the second node. Correspondingly, the second node identifier may be the second client identifier.

[0263] In a specific example, considering that the index of the second client is unique on the second node and can identify the second client, the second client identifier may be the index of the second client.

[0264] In another specific example, considering the combination of the transmission identifiers corresponding to the FlexE group and the client, which is unique on the second node, in one example, the second client identifier may also be determined according to the transmission identifier of the second client and the identifier of the FlexE group to which the second client belongs. For this case, the determination method of the first interface identifier can refer to the description of formula (1) above and will not be repeated here.

[0265] In another specific example, considering that the client has interface attributes, the node can assign an ifindex to the client it includes, and the ifindex is unique on the node. Therefore, the second client identifier can be the interface index of the second client.

[0266] In yet another specific example, if the small particle technology is implemented by directly dividing time slots for physical ports, considering that the physical interface of the second client obtained by division is unique on the second node, therefore, the second client identifier can be the identifier of the physical interface of the second client obtained by division.

[0267] As described above, if the foregoing first link is a link carrying large-granularity services, then in one example, the first node may send the foregoing first LLDP message to the second node through the OH channel corresponding to the first link. For this case, when the second node receives the first LLDP message, it can naturally determine that the first link is fault-free. Therefore, for this case, after receiving the first node identifier and the first interface identifier, the second node may directly obtain the first link information based on the received first node identifier, first interface identifier, as well as the local second node identifier and second interface identifier. In another example, the first node may send the first LLDP message to the second node through a general OH channel. For this case, when the second node receives the first LLDP message, it only indicates that the first physical interface of the first node is fault-free, but does not indicate that the first link is fault-free. For this case, before executing S104, the second node may first determine whether the first link is faulty. Specifically, as described above, if the first LLDP message is sent to the second node through a general OH channel, the first LLDP message includes the identifier of the first physical interface, and the second node may determine the second physical interface connected to the first physical interface according to the identifier of the first physical interface. For example, the second node may determine the second physical interface connected to the first physical interface according to its own interface connection relationship. Further, the second node may determine whether the second physical interface is faulty. For example, the second node may detect whether the local device includes the fault indication information of the second physical interface. If the local device does not include the fault indication information of the second physical interface, it means that the second physical interface is fault-free. Correspondingly, the second node may determine that the first link is fault-free. For this case, the second node may further execute S104 to obtain the first link information. Correspondingly, if the local device includes the fault indication information of the second physical interface, it indicates that the second physical interface is faulty. Correspondingly, the second node may determine that the first link is faulty. For this case, in one example, the second node may no longer execute S104, or after the second node executes S104, it may correspondingly save the first link information and the fault indication indicating the first link failure.

[0268] As described above, if the foregoing first link is a link carrying small-granularity services, then in one example, the first node may send the foregoing first LLDP message to the second node through the GCC corresponding to the first link. For this case, when the second node receives the first LLDP message, it can naturally determine that the first link is fault-free. Therefore, for this case, after receiving the first node identifier and the first interface identifier, the second node may directly obtain the first link information based on the received first node identifier, first interface identifier, as well as the local second node identifier and second interface identifier.

[0269] In yet another example, the first node may send the first LLDP packet to the second node through the general GCC. For this case, when the second node receives the first LLDP packet, it only indicates that the first client of the first node is fault-free, but does not indicate that the first link is fault-free. For this case, before executing S104, the second node may first determine whether the first link is faulty. Specifically, as described above, if the first LLDP packet is sent to the second node through the general GCC, the first LLDP packet includes the identifier of the first client, and the second node may determine the second client connected to the first client according to the identifier of the first client. For example, the second node may determine the second client connected to the first client according to its own interface connection relationship. Further, the second node may determine whether the second client is faulty. For example, the second node may detect whether the local device includes the fault indication information of the second client. If the local device does not include the fault indication information of the second client, it means that the second client is fault-free. Correspondingly, the second node may determine that the first link is fault-free. For this case, the second node may further execute S104 to obtain the first link information. Correspondingly, if the local device includes the fault indication information of the second client, it indicates that the second client is faulty. Correspondingly, the second node may determine that the first link is faulty. For this case, in one example, the second node may no longer execute S104, or after the second node executes S104, it may correspondingly save the first link information and the fault indication indicating the first link fault.

[0270] In one example, the second node may also determine the link attribute of the first link, so as to further send the link attribute of the first link and the first link information to the controller. Correspondingly, the controller may calculate the end-to-end path for the service based on the first link information and the link attribute of the first link.

[0271] In the embodiment of the present application, the link attribute of the first link is related to the link type of the first link. Among them, the link type of the first link may be a link carrying large-granularity services or a link carrying small-granularity services. Next, the link attribute of the first link will be described.

[0272] In some embodiments, the first link is a link for carrying large-granularity services. In this case, the link attributes of the first link may include the identifier of the first physical interface, the identifier of the second physical interface, additional attributes of the first physical interface, and additional attributes of the second physical interface. Among them, the additional attributes of the first physical interface include at least one attribute of the first physical interface. Similarly, the additional attributes of the second physical interface include at least one attribute of the second physical interface.

[0273] Next, any physical interface is referred to as the target physical interface, and the additional attributes of the first physical interface and the additional attributes of the second physical interface are described. Among them, the target physical interface may be the first physical interface or the second physical interface, or may also be the third physical interface or the fourth physical interface mentioned below.

[0274] In one example, the additional attributes of the target physical interface may include the large-granularity capabilities supported by the target physical interface, the configured bandwidth of the target physical interface, the remaining bandwidth of the target physical interface, and the available time slots of the target physical interface. Among them: The configured bandwidth of the target physical interface can be understood as the total bandwidth of the target physical interface; the remaining bandwidth of the target physical interface refers to the bandwidth that has not been occupied by services or reserved for specific services; the available time slots of the target physical interface refer to the time slots that have not been allocated to services. The large-granularity capabilities supported by the target physical interface refer to the capabilities related to carrying large-granularity services.

[0275] In a specific example, the large-granularity capabilities supported by the target physical interface may include: the granularity carrying capabilities supported by the target physical interface, cross-PHY bundling capabilities, dynamic large-granularity channel capabilities, static large-granularity channel capabilities, and large-granularity time slot following capabilities.

[0276] The granularity carrying capabilities supported by the target physical interface are used to indicate the bandwidth granularity corresponding to the time slots carrying large-granularity services. For example, the granularity carrying capabilities supported by the target physical interface may include 5G granularity carrying capabilities. In this case, the bandwidth corresponding to one time slot is 5G; for another example, the granularity carrying capabilities supported by the target physical interface may include 2G granularity carrying capabilities. In this case, the bandwidth corresponding to one time slot is 2G; for yet another example, the granularity carrying capabilities supported by the target physical interface may include 1G granularity carrying capabilities. In this case, the bandwidth corresponding to one time slot is 1G.

[0277] Cross-PHY bundling ability, which is used to indicate the ability to bundle time slots corresponding to different PHYs included in a FlexE group for use. For example, if a FlexE group includes PHY1 and PHY2, PHY1 includes slot1, and PHY2 includes slot2, then the time slots allocated for services can include slot1 and slot2.

[0278] The dynamic large-granularity channel ability is used to indicate whether it can participate in the calculation of the dynamic end-to-end path. Among them, if the target physical interface has the dynamic large-granularity channel ability, it means that the target physical interface supports participating in the calculation of the dynamic end-to-end path. The dynamic end-to-end path mentioned here refers to the path carrying large-granularity services.

[0279] The static large-granularity channel ability indicates whether a static end-to-end path can be established through static configuration. Among them, if the target physical interface has the static large-granularity channel ability, it means that the target physical interface can establish a static end-to-end path through static configuration. The static end-to-end path mentioned here refers to the path carrying small-granularity services.

[0280] The large-granularity time slot following ability refers to automatically following the upstream large-granularity time slot configuration, so that the local end can establish communication with the upstream.

[0281] In one example, if the large-granularity time slot following ability indicates that the target physical interface has the ability to automatically follow the upstream large-granularity time slot configuration, then this large-granularity time slot following ability can also be used to indicate the following method by which the target physical interface automatically follows the upstream large-granularity time slot configuration. The following methods include: following through data-plane messages and / or following through control-plane messages. Among them, following through data-plane messages means interacting with the upstream node through data messages to achieve following the upstream time slot configuration; following through control-plane messages means interacting with the upstream node through control messages to achieve following the upstream time slot configuration.

[0282] In the embodiments of this application, the second node can obtain the additional attributes of the second physical interface and receive the additional attributes of the first physical interface sent by the first node.

[0283] In one example, the first node can carry the additional attributes of the first physical interface in a message and send it to the second node. The message mentioned here can be an LLDP message. This LLDP message can be the aforementioned first LLDP message. In this case, the first node can send the first node identifier, the first interface identifier, and the additional attributes of the first physical interface to the second node through one LLDP message. In another example, this LLDP message can also be another LLDP message different from the aforementioned first LLDP message, and the embodiments of this application do not make specific limitations.

[0284] If the additional attributes of the first physical interface are carried by the first LLDP packet, then as an example, the additional attributes of the first physical interface can be carried by the aforementioned first TLV. In some scenarios, the first TLV may include a third sub-TLV, and the third sub-TLV is used to carry the large-granularity capabilities supported by the first physical interface. For example, the value field of the third sub-TLV may include indication bits corresponding to the aforementioned various large-granularity capabilities respectively. It can be understood in combination with Table 1 below. Table 1 shows the bit positions corresponding to the various large-granularity capabilities and related descriptions.

[0285] Table 1

[0286]

[0287]

[0288] In one example, in addition to including the third sub-TLV, the first TLV may further include a first bandwidth sub-TLV and a first time slot sub-TLV. The first bandwidth sub-TLV is used to carry the configured bandwidth of the first physical interface and the remaining bandwidth of the first physical interface; the first time slot sub-TLV can be used to carry the available time slots of the first physical interface. Of course, the configured bandwidth of the first physical interface and the remaining bandwidth of the first physical interface may also be carried by different bandwidth sub-TLVs respectively, and the embodiments of the present application do not make specific limitations.

[0289] In one example, in addition to including the third sub-TLV, the first TLV may further include a fifth sub-TLV, and the fifth sub-TLV is used to identify the large-granularity capabilities. The fifth sub-TLV and the third sub-TLV may be two adjacent sub-TLVs in the first TLV. The third sub-TLV is located after the fifth sub-TLV. After the second node parses the fifth sub-TLV, it can determine that the third sub-TLV after the fifth sub-TLV is the sub-TLV carrying the large-granularity capabilities.

[0290] In one example, the first node may send the first node identifier and the first interface identifier to the second node only when its own first physical interface has the dynamic large-granularity channel capabilities. Or, after receiving the first LLDP packet, the second node further determines whether the first physical interface has the dynamic large-granularity channel capabilities. Only when it is determined that the first physical interface has the dynamic large-granularity channel capabilities and its own second physical interface also has the dynamic large-granularity channel capabilities, does it execute S104.

[0291] In some embodiments, the first link is a link carrying small particle services. In this case, the link attributes of the first link may include the identifier of the first client, the identifier of the second client, the additional attributes of the first client, and the additional attributes of the second client. Among them, the additional attributes of the first client include at least one attribute of the first client. Similarly, the additional attributes of the second client include at least one attribute of the second client.

[0292] Next, the first client or the second client is represented by the target client, and the additional attributes of the first client and the additional attributes of the second client are described.

[0293] In one example, the additional attributes of the target client may include the small particle capabilities supported by the target client, the configured bandwidth of the target client, the remaining bandwidth of the target client, and the available time slots of the target client. Among them: The configured bandwidth of the target client can be understood as the total bandwidth of the target client; the remaining bandwidth of the target client refers to the bandwidth that has not been occupied by services or reserved for specific services; the available time slots of the target client refer to the time slots that have not been allocated to services; the small particle capabilities supported by the target client refer to the capabilities related to carrying small particle services.

[0294] In a specific example, the small particle capabilities supported by the target client may include: whether the target client supports small particle technology, dynamic small particle channel capabilities, static small particle channel capabilities, and small particle time slot following capabilities. Among them:

[0295] Whether the target client supports small particle technology refers to whether the time slots corresponding to the target client support being divided into multiple sub-time slots to carry small particle services.

[0296] The dynamic small particle channel capabilities are used to indicate whether it can participate in the calculation of the dynamic end-to-end path. Among them, if the target client has the dynamic small particle channel capabilities, it means that the target client supports participating in the calculation of the dynamic end-to-end path. The dynamic end-to-end path mentioned here refers to the path carrying small particle services.

[0297] The static small particle channel capability indicates whether a static end-to-end path can be established through static configuration. Among them, if the target client has the static small particle channel capability, it means that the target client can establish a static end-to-end path through static configuration. The static end-to-end path mentioned here refers to the path carrying small particle services.

[0298] The small particle time slot following capability refers to automatically following the upstream small particle time slot configuration, so that the local end can establish communication with the upstream.

[0299] In one example, if the small particle time slot following capability indicates that the target client has the ability to automatically follow the upstream small particle time slot configuration. Then this small particle time slot following capability can also be used to indicate the following method for the target client to automatically follow the upstream small particle time slot configuration. The following methods include: following through data plane messages and / or following through control plane messages. Among them, following through data plane messages means interacting with the upstream node with data messages to achieve following the upstream time slot configuration; following through control plane messages means interacting with the upstream node with control messages to achieve following the upstream time slot configuration.

[0300] In the embodiments of the present application, the second node can obtain the additional attributes of the second client and receive the additional attributes of the first client sent by the first node.

[0301] In one example, the first node can carry the additional attributes of the first client in the OAM code block and send them to the second node. See Figure 3h , Figure 3h which is a schematic diagram of an OAM code block provided by the embodiments of the present application. As Figure 3h shown, the OAM code block 303 is a standard OAM code block, and the OAM code block 304 is an OAM code block carrying the additional attributes of the first client. Among them, the type field in the OAM code block 304 indicates that this OAM code block is used to carry the additional attributes of the first client. The additional attributes of the first client can be carried by some or all of the 4 value fields, namely value1, value2, value3, and value4, in the OAM code block. For example, value1 can be used to carry the small particle capabilities supported by the first client. For this case, the meanings of each bit of value1 can be understood with reference to Table 2 below; correspondingly, value2 is used to carry the configured bandwidth of the first client, value3 is used to carry the remaining bandwidth of the first client, and value4 is used to carry the available time slots of the first client.

[0302] In yet another example, the first node may carry additional attributes of the first client in a message and send the message to the second node. The message mentioned here may be an LLDP message. This LLDP message may be the aforementioned first LLDP message. In this case, the first node can send the first node identifier, the first interface identifier, and the additional attributes of the first client to the second node through one LLDP message. In yet another example, this LLDP message may also be another LLDP message different from the aforementioned first LLDP message, and the embodiments of the present application do not make specific limitations.

[0303] If the additional attributes of the first client are carried by the first LLDP message, then as an example, the additional attributes of the first client may be carried by the aforementioned first TLV. In some scenarios, the first TLV may include a fourth sub-TLV, and the fourth sub-TLV is used to carry the small-granularity capabilities supported by the first client. For example, the value field of the fourth sub-TLV may include indication bits corresponding to the aforementioned various small-granularity capabilities. It can be understood in combination with Table 2 below. Table 2 shows the bit positions corresponding to the various small-granularity capabilities and related descriptions.

[0304] Table 2

[0305]

[0306] In one example, in addition to including the fourth sub-TLV, the first TLV may further include a second bandwidth sub-TLV and a second time slot sub-TLV. The second bandwidth sub-TLV is used to carry the configured bandwidth of the first client and the remaining bandwidth of the first client; the second time slot sub-TLV may be used to carry the available time slots of the first client. Of course, the configured bandwidth of the first client and the remaining bandwidth of the first client may also be carried by different bandwidth sub-TLVs respectively, and the embodiments of the present application do not make specific limitations.

[0307] In one example, in addition to including the fourth sub-TLV, the first TLV may further include a sixth sub-TLV, and this sixth sub-TLV is used to identify small-granularity capabilities. The sixth sub-TLV and the fourth sub-TLV may be two adjacent sub-TLVs in the first TLV. The fourth sub-TLV is located after the sixth sub-TLV. After the second node parses the sixth sub-TLV, it can determine that the fourth sub-TLV after the sixth sub-TLV is the sub-TLV carrying the small-granularity capabilities.

[0308] In one example, when the first node and the second node are deployed with large particle technology, the first FlexE group of the first node may include multiple physical interfaces. For example, it may include the aforementioned first physical interface and the third physical interface. Correspondingly, the second FlexE group of the second node may include multiple physical interfaces. For example, it may include the aforementioned second physical interface and the fourth physical interface. For this case, the link between the aforementioned first interface and the second interface may further include a second link between the third physical interface and the fourth physical interface. For this case, the first node may further send a second LLDP packet to the second node, and the second LLDP packet includes a first node identifier and a first interface identifier. Correspondingly, after receiving the second LLDP packet, the second node may obtain second link information based on the first node identifier, the first interface identifier, the local second node identifier, and the second interface identifier in the second LLDP packet. This second link information is the same as the first link information and also includes a quadruple, namely: the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier.

[0309] Regarding the manner in which the first node sends the second LLDP packet to the second node, it is similar to the manner in which the first node sends the first LLDP packet to the second node. For the relevant content, reference can be made to the relevant description part of the first LLDP packet above, and no repeated description will be made here.

[0310] In addition, the second node may further determine the link attributes of the second link. Among them, the link attributes of the second link may include: the identifier of the third physical interface, the identifier of the fourth physical interface, the additional attributes of the third physical interface, and the additional attributes of the fourth physical interface. Specifically, the second node may obtain the additional attributes of the fourth physical interface locally and receive the additional attributes of the third physical interface sent by the first node.

[0311] Regarding the additional attributes of the third physical interface and the additional attributes of the fourth physical interface, reference can be made to the relevant description part of the additional attributes of the target physical interface above, and no repeated description will be made here. Regarding the specific implementation of the first node sending the additional attributes of the third physical interface to the second node, reference can be made to the description part of the first node sending the additional attributes of the first physical interface to the second node above, and no repeated description will be made here.

[0312] After obtaining the first link information, the second link information, the link attributes of the first link, and the link attributes of the second link, the first node can merge the first link information, the second link information, the link attributes of the first link, and the link attributes of the second link to obtain the target link information and the target link attributes. As mentioned above, the first link information and the second link information are the same, so the first link information and the second link information can be combined into one, that is, the target link information can be the first link information. Correspondingly, the target link attributes include the link attributes of the first link and the link attributes of the second link. Thus, the second node can obtain the target link information and the target link attributes between the first FlexE group of the first node and the second FlexE group of the second node.

[0313] In an example, the second node may report the target link information and the target link attributes to the controller, so that the controller calculates an end-to-end path for the service based on the target link information and the target link attributes.

[0314] In one example, nodes can notify each other of their own node identifiers and interface identifiers. In other words, the second node can also send the second node identifier and the second interface identifier to the first node, so that the first node can obtain the first link information based on the received second node identifier, the second interface identifier, and the local first node identifier and the first interface identifier. Among them, the implementation principle of "the second node sends the second node identifier and the second interface identifier to the first node" is the same as the implementation principle of "the first node sends the first node identifier and the first interface identifier to the second node". Therefore, for the specific implementation of "the second node sends the second node identifier and the second interface identifier to the first node", please refer to the specific description of S102 in the previous text, and no repeated description will be made here.

[0315] It can be seen from the above description that, by using the solution of the embodiment of the present application, the second node can automatically discover the large-grain link or small-grain link between itself and the first node, without the need for the controller to configure the command trigger, and the discovery of large-grain links / small-grain links is more flexible. In one example, after the second node discovers the link, there is no need for the controller to send the corresponding configuration information to the second node. The second node can automatically report the link information and link attributes to the controller, which is conducive to maintaining the network.

[0316] The above introduces the information processing method provided in the embodiment of the present application. Next, the solution provided in the embodiment of the present application is introduced in combination with specific scenarios.

[0317] See also Figure 4a , which is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application.Figure 4a As shown, Node 1 includes FlexE group1, Node 2 includes FlexE group2, and communication is established between FlexE group1 of Node 1 and FlexE group2 of Node 2. FlexE group1 includes two physical interfaces, namely Physical Interface 1 and Physical Interface 3. FlexE group2 also has two physical interfaces, namely Physical Interface 2 and Physical Interface 4. Physical Interface 1 is connected to Physical Interface 2, and Physical Interface 3 is connected to Physical Interface 4.

[0318] In one example, Node 1 can execute Figure 4b the information processing method shown. Figure 4b It is a schematic flowchart of an information processing method provided by an embodiment of this application.

[0319] Figure 4b The method shown may include the following S201 - S210.

[0320] S201: Determine whether the number of physical interfaces included in itself has changed.

[0321] If the number of physical interfaces included in itself has changed, then further execute S204.

[0322] S202: Determine whether the state of the physical interface has changed.

[0323] If it is determined that there is an alarm on the physical interface, then execute S206.

[0324] In the embodiment of this application, for example, traditional fault detection means can be used to determine whether there is a fault on the physical interface. For example, traditional fault detection means can be used to determine whether there is one or more alarm signals such as laser_mod_err, eth_los, loss frame (LOF), loss multi - frame (LOM), signal fault (SF), signal degradation (SD), phynum_mismatch, so as to determine whether there is an alarm on the physical interface.

[0325] S203: Determine whether the configuration related to large granules has changed, where the configuration related to large granules includes: capabilities, time - slot configuration.

[0326] The time - slot configuration mentioned here can be the time - slot granularity or the specific time - slots allocated for services.

[0327] If the configuration related to the large particles has changed, then further execute S207.

[0328] S204: Determine whether a new physical interface has been created.

[0329] If so, execute S205; if not, execute S209.

[0330] S205: Determine whether the physical interface supports the dynamic large particle channel capability.

[0331] If so, execute S206; if not, execute S209.

[0332] S206: Determine whether the interface state of the physical interface is effective (up).

[0333] The physical interface mentioned here can be a newly created physical interface or a physical interface with an alarm.

[0334] If so, execute S208; if not, execute S209.

[0335] S207: Determine whether the configuration with changes includes link attributes.

[0336] Among them, there may be many situations for the configuration with changes. Some of the configurations may have nothing to do with the link attributes. Therefore, it is possible to determine whether the configuration with changes includes link attributes, so as to determine whether to execute the link discovery processing flow.

[0337] If the configuration with changes includes link attributes, then execute S208; if not, then end the process.

[0338] S208: Execute the link discovery processing flow.

[0339] S209: Determine whether the link is effective.

[0340] Among them, the judgment conditions for the link to be effective can include the following 3 items:

[0341] 1. Determine that the physical interfaces belonging to the same FlexE group have the same FlexE docking parameters (such as FlexE group idx).

[0342] 2. Determine that none of the physical interfaces included in the FlexE group have alarms.

[0343] 3. For a certain physical interface, determine that both the physical interface and the physical interface of the peer node connected to this physical interface support the dynamic large particle channel capability.

[0344] S210: Refresh the network topology according to the judgment result.

[0345] Among them, refreshing the network topology may include three cases. One is adding a topology, another is deleting a topology, and the other is modifying the link attributes of existing links. For example, in the scenario of adding a physical interface, a topology is added; in the case where a physical interface fails or a physical interface is deleted, the topology is deleted; in the case where the link attributes change, the link attributes of existing links are modified.

[0346] In the embodiment of the present application, when specifically implemented, S208 may include Figure 4c the steps S301 - S308 shown. Figure 4c It is a schematic flowchart of an information processing method provided by an embodiment of the present application.

[0347] S301: Node 1 sends an LLDP packet 1 to Node 2 through the OH channel between physical interface 1 and physical interface 2. The LLDP packet 1 includes node identifier 1, interface identifier 1, and additional attributes of physical interface 1.

[0348] In one example, the node identifier 1 may be the loopback address of Node 1, and the interface identifier 1 may be the identifier of FlexE group1.

[0349] As an example, the LLDP packet 1 may include a vendor TLV1, and the structure of the vendor TLV1 may be referred to Figure 4d for understanding. Figure 4d It is a schematic diagram of the structure of a vendor TLV provided by an embodiment of the present application. As Figure 4d shown, the vendor TLV includes 6 sub - TLVs. Sub - TLV1 is used to carry node identifier 1, sub - TLV2 is used to carry interface identifier 1, sub - TLV3 is used to identify the large - granularity capability, sub - TLV4 is used to carry the large - granularity capability of physical interface 1, sub - TLV5 is used to carry the configured bandwidth and remaining bandwidth of physical interface 1; sub - TLV6 is used to carry the available time slots of physical interface 1.

[0350] S302: Node 1 sends an LLDP packet 2 to Node 2 through the OH channel between physical interface 3 and physical interface 4. The LLDP packet 2 includes node identifier 1, interface identifier 1, and additional attributes of physical interface 3.

[0351] In the embodiments of the present application, the carrying manner of the node identifier 1, the interface identifier 1, and the additional attributes of the physical interface 3 in the LLDP packet 2 is the same as the carrying manner of the node identifier 1, the interface identifier 1, and the additional attributes of the physical interface 1 in the LLDP packet 1. Therefore, regarding the "carrying manner of the node identifier 1, the interface identifier 1, and the additional attributes of the physical interface 3 in the LLDP packet 2", reference can be made to the relevant description part in S301, and no repeated description will be made here.

[0352] S303: Node 2 receives the LLDP packet 1 sent by Node 1, and obtains link information 1 and link attributes 1 according to the local node identifier 2 and interface identifier 2. Node 2 receives the LLDP packet 2 sent by Node 1, and obtains link information 2 and link attributes 2 according to the local node identifier 2 and interface identifier 2.

[0353] In one example, the node identifier 2 may be the loopback address of Node 2, and the interface identifier 2 may be the identifier of FlexE group2.

[0354] Among them, the link information 1 and the link information 2 are the same, and both include a quadruple: node identifier 1, node identifier 2, interface identifier 1, interface identifier 2. The link attributes 1 include: the identifier of the physical interface 1, the additional attributes of the physical interface 1, the identifier of the physical interface 2, and the additional attributes of the physical interface 2. The link attributes 2 include: the identifier of the physical interface 3, the additional attributes of the physical interface 3, the identifier of the physical interface 4, and the additional attributes of the physical interface 4.

[0355] S304: Node 2 merges the link information 1, the link attributes 1, the link information 2, and the link attributes 2 to obtain link information 3 and link attributes 3.

[0356] Among them, the link information 3 is the link information 1, and the link attributes 3 include the link attributes 1 and the link attributes 2. As Figure 4a shown, the link information 3 and the link attributes 3 obtained by Node 2 correspond to Figure 4a shown in 401.

[0357] S305: Node 2 sends the LLDP packet 3 to Node 1 through the OH channel between the physical interface 1 and the physical interface 2. The LLDP packet 3 includes the node identifier 2, the interface identifier 2, and the additional attributes of the physical interface 2.

[0358] S306: Node 2 sends the LLDP packet 4 to Node 1 through the OH channel between the physical interface 3 and the physical interface 4. The LLDP packet 4 includes the node identifier 2, the interface identifier 2, and the additional attributes of the physical interface 4.

[0359] S307: Node 1 receives the LLDP packet 3 sent by Node 2, and obtains link information 1 and link attributes 1 based on the local node identifier 1 and interface identifier 1. Node 1 receives the LLDP packet 4 sent by Node 2, and obtains link information 2 and link attributes 2 based on the local node identifier 1 and interface identifier 1.

[0360] S308: Node 1 merges the link information 1, link attributes 1, link information 2, and link attributes 2 to obtain link information 3 and link attributes 3.

[0361] As Figure 4a shown, the link information 3 and link attributes 3 obtained by Node 1 correspond to Figure 4a the 402 shown.

[0362] The implementation principles of S305 - S308 are the same as those of S301 - S304. For the specific implementation of S305 - S308, reference can be made to the relevant descriptions of S301 - S304 in the previous text, and no repeated description will be given here.

[0363] See Figure 5a , which is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application. As Figure 5a shown, Node 1 includes client11 and client12, and Node 2 includes client21 and client22. Client11 of Node 1 and client21 of Node 2 establish communication to carry small - granularity services. Client12 of Node 1 and client22 of Node 2 establish communication to carry small - granularity services, and a general GCC is included between Node 1 and Node 2.

[0364] In one example, the Node 1 can execute Figure 5b the information - processing method shown. Figure 5b It is a flowchart of an information - processing method provided by an embodiment of the present application.

[0365] Figure 5b The method shown can include the following S401 - S410.

[0366] S401: Determine whether the number of large - granularity objects included in itself has changed.

[0367] If the number of large - granularity objects included in itself has changed, then further execute S404.

[0368] S402: Determine whether the state of the physical interface or the client has changed.

[0369] If it is determined that there is an alarm in the physical interface or the client, then execute S406.

[0370] For the specific implementation of determining whether a physical interface fails, reference may be made to the description part of S402 above.

[0371] In the embodiments of the present application, for example, traditional fault detection means may be used to determine whether a client has one or more alarm signals such as LOM, LOF, local fault (LF), and remote fault (RF), so as to determine whether the client has an alarm.

[0372] S403: Determine whether the configuration related to small particles has changed, where the configuration related to small particles includes: capabilities, time slot configuration.

[0373] The time slot configuration mentioned here may be the specific time slot allocated for services.

[0374] If the configuration related to small particles has changed, then S407 is further executed.

[0375] S404: Determine whether a new large particle object has been created.

[0376] If so, execute S405; if not, execute S409.

[0377] S405: Determine whether the client supports dynamic small particle channel capabilities.

[0378] The client mentioned here may be the newly created large particle object.

[0379] If so, execute S406; if not, execute S409.

[0380] S406: Determine whether the interface state of the physical interface or the client is up.

[0381] The physical interface mentioned here may be the physical interface carrying the newly created large particle object or the physical interface with an alarm.

[0382] The client port mentioned here may be the newly created large particle object or the client with an alarm.

[0383] If so, execute S408; if not, execute S409.

[0384] S407: Determine whether the changed configuration includes link attributes.

[0385] Among them, there may be many situations where the configuration has changed. Some of these configurations may have nothing to do with the link attributes. Therefore, it is possible to determine whether the changed configuration includes link attributes, so as to determine whether to execute the link discovery processing flow.

[0386] If the changed configuration includes link attributes, then execute S408; if not, end the process.

[0387] S408: Execute the link discovery processing flow.

[0388] S409: Determine whether the link is effective.

[0389] Among them, the judgment conditions for the link to be effective can include the following three items:

[0390] 1. Determine that both the local client and the peer client have enabled the small particle technology.

[0391] The local client mentioned here refers to the client of the local node, and the peer client refers to the client used by the peer node to connect to the local client.

[0392] 2. Determine that both the local client and the peer client support the dynamic small particle channel capability.

[0393] 3. Determine that both the local client and the peer client have no faults.

[0394] S410: Refresh the network topology according to the judgment result.

[0395] Among them, refreshing the network topology can include three situations. One is to add a topology, another is to delete a topology, and there is also a situation of modifying the link attributes of an existing link. For example, in the scenario of adding a large particle object, add a topology; in the case of a physical interface failure or a physical interface being deleted, delete the topology; in the case of a change in link attributes, modify the link attributes of an existing link.

[0396] In the embodiment of the present application, when S408 is specifically implemented, it may include Figure 5c the steps S501 - S508 shown. Figure 5c It is a schematic flow diagram of an information processing method provided by an embodiment of the present application.

[0397] S501: Node 1 sends an LLDP packet 1 to Node 2 through the general GCC between Node 1 and Node 2. The LLDP packet 1 includes Node ID 1, Interface ID 1, the transmission ID of client11, and the additional attributes of client11.

[0398] In one example, the node identifier 1 may be the loopback address of node 1, and the interface identifier 1 may be the index of client11. Among them, the transmission identifiers of client11 and client21 are the same.

[0399] As an example, the LLDP packet 1 may include a vendor TLV2, and the structure of the vendor TLV2 can be referred to Figure 5d for understanding. Figure 5d It is a schematic diagram of the structure of a vendor TLV provided by an embodiment of this application. As Figure 5d shown, the vendor TLV includes 7 sub-TLVs. Sub-TLV1 is used to carry the node identifier 1, sub-TLV2 is used to carry the interface identifier 1, sub-TLV3 is used to carry the transmission identifier of client11, sub-TLV4 is used to identify the small particle capability, sub-TLV5 is used to carry the small particle capability of client11, sub-TLV6 is used to carry the configured bandwidth of client11 and the remaining bandwidth of client11; sub-TLV7 is used to carry the available time slots of client11.

[0400] S502: Node 1 sends an LLDP packet 2 to node 2 through the general GCC between node 1 and node 2. The LLDP packet 2 includes the node identifier 1, the interface identifier 3, the transmission identifier of client12, and the additional attributes of client12.

[0401] In one example, the interface identifier 3 may be the index of client12. Among them, the transmission identifiers of client12 and client22 are the same.

[0402] In the embodiments of this application, the carrying manner of the node identifier 1, the interface identifier 3, the transmission identifier of client12, and the additional attributes of client12 in the LLDP packet 2 is the same as the carrying manner of the node identifier 1, the interface identifier 1, the transmission identifier of client11, and the additional attributes of client11 in the LLDP packet 1. Therefore, regarding the "carrying manner of the node identifier 1, the interface identifier 3, the transmission identifier of client12, and the additional attributes of client12 in the LLDP packet 2", reference can be made to the relevant description part in S501, and no repeated description will be made here.

[0403] S503: Node 2 receives the LLDP packet 1 sent by node 1, and obtains link information 1 and link attribute 1 according to the local node identifier 2 and interface identifier 2. Node 2 receives the LLDP packet 2 sent by node 1, and obtains link information 2 and link attribute 2 according to the local node identifier 2 and interface identifier 4.

[0404] In one example, the node identifier 2 may be the loopback address of node 2, the interface identifier 2 may be the index of client21, and the interface identifier 4 may be client21.

[0405] Wherein:

[0406] Link information 1 includes a quadruple: node identifier 1, node identifier 2, interface identifier 1, interface identifier 2, and link attribute 1 includes: the identifier of client11, additional attributes of client11, the identifier of client21, additional attributes of client21.

[0407] Link information 2 includes a quadruple: node identifier 1, node identifier 2, interface identifier 3, interface identifier 4. Link attribute 2 includes: the identifier of client12, additional attributes of client12, the identifier of client22, additional attributes of client22.

[0408] Among them, the link information 1, link attribute 1, link information 2, and link attribute 2 obtained by node 2 can correspond to Figure 5a the 501 shown.

[0409] S504: Node 2 sends LLDP packet 3 to node 1 through the general GCC between node 1 and node 2. LLDP packet 3 includes node identifier 2, interface identifier 2, the transmission identifier of client12, and additional attributes of client12.

[0410] S505: Node 2 sends LLDP packet 4 to node 1 through the general GCC between node 1 and node 2. LLDP packet 4 includes node identifier 2, interface identifier 4, the transmission identifier of client22, and additional attributes of client22.

[0411] S506: Node 1 receives LLDP packet 3 sent by node 2 and obtains link information 1 and link attribute 1 according to the local node identifier 1 and interface identifier 1. Node 1 receives LLDP packet 4 sent by node 2 and obtains link information 2 and link attribute 2 according to the local node identifier 1 and interface identifier 3.

[0412] Among them, the link information 1, link attribute 1, link information 2, and link attribute 2 obtained by node 1 can correspond to Figure 5a the 502 shown.

[0413] The implementation principle of S504 - S506 is the same as that of S501 - S503. For the specific implementation of S504 - S506, reference can be made to the relevant descriptions of S501 - S503 above, and no repeated description will be given here.

[0414] Based on the information processing method provided in the above embodiments, the embodiments of the present application further provide a corresponding information processing device. Next, this device will be introduced with reference to the accompanying drawings.

[0415] See Figure 6a , which is a schematic structural diagram of an information processing device provided by an embodiment of the present application. Figure 6a The information processing device shown can be applied to the second node and is used to execute the information processing method executed by the second node provided in the above embodiments.

[0416] Figure 6a The information processing device 610 shown includes: a receiving unit 611 and a processing unit 612.

[0417] The receiving unit 611 is configured to receive a first node identifier and a first interface identifier sent by the first node. The first node identifier is used to identify the first node, and the first interface identifier is used to identify the first interface through which the first node communicates with the second node;

[0418] The processing unit 612 is configured to obtain first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier. The second node identifier is used to identify the second node, and the second interface identifier is used to identify the second interface through which the second node communicates with the first node. The first link information is used to indicate a first link between the first interface and the second interface, and the first link is a link carrying large-granularity services or a link carrying small-granularity services.

[0419] In a possible implementation manner, the receiving unit 611 is configured to: receive a first Link Layer Discovery Protocol (LLDP) packet sent by the first node. The first LLDP packet includes a first Type-Length-Value (TLV), and the first TLV includes the first node identifier and the first interface identifier.

[0420] In a possible implementation manner, the first TLV includes a first sub-TLV and a second sub-TLV. The first sub-TLV includes the first node identifier, and the second sub-TLV includes the first interface identifier.

[0421] In a possible implementation manner, the first TLV is a vendor TLV.

[0422] In a possible implementation, if the first link is a link carrying large-granularity services, then: the first interface identifier includes: the first FlexE group identifier corresponding to the first node, and the first FlexE group identifier is used to identify the first FlexE group corresponding to the first node; the second interface identifier includes: the second FlexE group identifier corresponding to the second node, and the second FlexE group identifier is used to identify the second FlexE group corresponding to the second node.

[0423] In a possible implementation, the first link is a link between the first physical interface of the first node and the second physical interface of the second node. The receiving unit 611 is configured to: receive the first LLDP packet through the overhead (OH) channel corresponding to the first link, where the OH channel corresponding to the first link is used to carry the link information of the first link.

[0424] In a possible implementation, the receiving unit 611 is configured to: receive the first LLDP packet through a common OH channel, where the link information of multiple links carrying large-granularity services between the first node and the second node is transmitted through the common OH channel.

[0425] In a possible implementation, the first link is a link between the first physical interface of the first node and the second physical interface of the second node, and the first LLDP packet further includes the identifier of the first physical interface.

[0426] In a possible implementation, the processing unit 612 is specifically configured to: determine the second physical interface connected to the first physical interface according to the identifier of the first physical interface; and obtain the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier when the second physical interface is fault-free.

[0427] In a possible implementation, the processing unit 612 is further configured to: determine the link attribute of the first link, and the link attribute of the first link includes at least one of the following: the identifier of the first physical interface, the identifier of the second physical interface, the additional attribute of the first physical interface, and the additional attribute of the second physical interface.

[0428] In a possible implementation, the target physical interface includes the first physical interface or the second physical interface, and the additional attributes of the target physical interface include one or more of the following: the large particle capabilities supported by the target physical interface, the configured bandwidth of the target physical interface, the remaining bandwidth of the target physical interface, and the available time slots of the target physical interface.

[0429] In a possible implementation, the large particle capabilities supported by the target physical interface include one or more of the following: the particle carrying capabilities supported by the target physical interface, cross-PHY bundling capabilities, dynamic large particle channel capabilities, static large particle channel capabilities, and large particle time slot following capabilities. Among them, the target physical interface having the dynamic large particle channel capabilities indicates that the target physical interface can participate in the calculation of dynamic end-to-end paths; the target physical interface having the static large particle channel capabilities indicates that the target physical interface can establish static end-to-end paths through static configuration. Both the dynamic end-to-end paths and the static end-to-end paths are paths for carrying large particle services, and the large particle time slot following capabilities are used to indicate whether the target physical interface has the ability to automatically follow the upstream large particle time slot configuration.

[0430] In a possible implementation, the device further includes: receiving the additional attributes of the first physical interface sent by the first node.

[0431] In a possible implementation, the first TLV of the first LLDP packet further includes a third sub-TLV, and the third sub-TLV includes the large particle capabilities supported by the first physical interface.

[0432] In a possible implementation, if the large particle time slot following capabilities indicate that the target physical interface has the ability to automatically follow the upstream large particle time slot configuration, then the large particle time slot following capabilities further indicate the following methods for the target physical interface to automatically follow the upstream large particle time slot configuration. The following methods include: following through data plane packets and / or following through control plane packets.

[0433] In a possible implementation, the receiving unit 611 is further configured to: receive a second LLDP packet sent by the first node, where the second LLDP packet includes the first node identifier and the first interface identifier; the processing unit 612 is further configured to obtain second link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier, where the second link information is the same as the first link information, and the second link information is used to identify a second link between the first interface and the second interface, the second link is a link carrying large-granularity services, and the second link is a link between a third physical interface of the first node and a fourth physical interface of the second node; determine link attributes of the second link, where the link attributes of the second link include at least one of the following: an identifier of the third physical interface, an identifier of the fourth physical interface, additional attributes of the third physical interface, and additional attributes of the fourth physical interface.

[0434] In a possible implementation, the processing unit 612 is further configured to: merge the first link information, the second link information, the link attributes of the first link, and the link attributes of the second link to obtain target link information and target link attributes, where the target link information is the first link information, and the target link attributes include the link attributes of the first link and the link attributes of the second link.

[0435] In a possible implementation, the device further includes: a sending unit, configured to send the target link information and the target link attributes to a controller.

[0436] In a possible implementation, if the first link is a link carrying small-granularity services, then: the first interface identifier includes: a first client identifier corresponding to the first node, and the first client identifier is used to identify a first client corresponding to the first node; the second interface identifier includes: a second client identifier corresponding to the second node, and the second client identifier is used to identify a second client corresponding to the second node.

[0437] In a possible implementation, the first client identifier is an index of the first client; or, the first client identifier is determined according to a transmission identifier of the first client and an identifier of a FlexE group to which the first client belongs; or, in a scenario where physical ports are directly divided into sub-time slots, the first client identifier is an identifier of a physical interface obtained by dividing to obtain the first client, or the first client identifier is an interface index of the first client.

[0438] In a possible implementation, the first link is a link between a first client of the first node and a second client of the second node, and the receiving unit 611 is configured to: receive the first LLDP message through a general communication channel GCC corresponding to the first link.

[0439] In a possible implementation, the receiving unit 611 is configured to: receive the first LLDP message through a general GCC, where link information of multiple links carrying small granular services between the first node and the second node is transmitted through the general GCC channel.

[0440] In a possible implementation, the first link is a link between a first client of the first node and a second client of the second node, and the first LLDP message further includes a transmission identifier of the first client.

[0441] In a possible implementation, the processing unit 612 is specifically configured to: determine a second client connected to the first client according to the transmission identifier of the first client; and obtain the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier when the second client is fault-free.

[0442] In a possible implementation, the processing unit 612 is further configured to: determine link attributes of the first link, where the link attributes of the first link include at least one of the following: an identifier of the first client, an identifier of the second client, additional attributes of the first client, and additional attributes of the second client.

[0443] In a possible implementation, the target client includes the first client or the second client, and the additional attributes of the target client include one or more of the following: small granular capabilities supported by the target client, configured bandwidth of the target client, remaining bandwidth of the target client, and available sub-slots of the target client.

[0444] In a possible implementation, the small particle capabilities supported by the target client include one or more of the following: whether the target client supports small particle technology, dynamic small particle channel capabilities, static small particle channel capabilities, and small particle time slot following capabilities. Among them, the target client having the dynamic small particle channel capabilities indicates that the target client can participate in the calculation of the dynamic end-to-end path. The target client having the static small particle channel capabilities indicates that the target client can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths carrying small particle services. The small particle time slot following capabilities are used to indicate whether the target client has the ability to automatically follow the upstream small particle time slot configuration.

[0445] In a possible implementation, the receiving unit 611 is further configured to: receive the additional attributes of the first client sent by the first node.

[0446] In a possible implementation, the first TLV of the first LLDP packet further includes a fourth sub-TLV, and the small particle capabilities supported by the first client are included in the fourth sub-TLV; alternatively, the small particle capabilities supported by the first client are carried by an operation, administration, and maintenance (OAM) code block sent by the first node to the second node.

[0447] In a possible implementation, if the small particle time slot following capabilities indicate that the target client has the ability to automatically follow the upstream small particle time slot configuration, then the small particle time slot following capabilities further indicate the following method for the target client to automatically follow the upstream small particle time slot configuration. The following method includes: following through data plane packets and / or following through control plane packets.

[0448] In a possible implementation, the sending unit included in the device is configured to: send the first link information and the link attributes of the first link to the controller.

[0449] In a possible implementation, the device further includes: sending the second node identifier and the second interface identifier to the first node, so that the first node obtains the first link information based on the second node identifier, the second interface identifier, and the first node identifier and the first interface identifier.

[0450] See Figure 6b , which is a schematic structural diagram of another information processing device provided by an embodiment of the present application. Figure 6bThe information processing device shown can be applied to the first node and is used to execute the information processing method executed by the first node provided in the foregoing embodiments.

[0451] Figure 6b The information processing device 620 shown includes: a processing unit 621 and a sending unit 622.

[0452] The processing unit 621 is used to obtain a first node identifier and a first interface identifier. The first node identifier is used to identify the first node, and the first interface identifier is used to identify the first interface of the first node for communicating with the second node.

[0453] The sending unit 622 is used to send the first node identifier and the first interface identifier to the second node. The first node identifier and the first interface identifier are used to enable the second node to obtain first link information. The first link information is used to indicate a first link between the first interface and a second interface of the second node. The first link is a link carrying large-granularity services or a link carrying small-granularity services.

[0454] In a possible implementation manner, the sending unit 622 is used to: send a first Link Layer Discovery Protocol (LLDP) packet to the second node. The first LLDP packet includes a first Type-Length-Value (TLV), and the first TLV includes the first node identifier and the first interface identifier.

[0455] In a possible implementation manner, the first TLV includes a first sub-TLV and a second sub-TLV. The first sub-TLV includes the first node identifier, and the second sub-TLV includes the first interface identifier.

[0456] In a possible implementation manner, the first TLV is a vendor TLV.

[0457] In a possible implementation manner, if the first link is a link carrying large-granularity services, then: the first interface identifier includes: a first FlexE group identifier corresponding to the first node, and the first FlexE group identifier is used to identify the first FlexE group corresponding to the first node.

[0458] In a possible implementation manner, the first link is a link between a first physical interface of the first node and a second physical interface of the second node. The sending unit 622 is used to: send the first LLDP packet to the second node through an overhead (OH) channel corresponding to the first link, where the OH channel corresponding to the first link is used to carry the link information of the first link.

[0459] In a possible implementation, the sending unit 622 is configured to: send the first LLDP packet to the second node through a common OH channel, where link information of multiple links carrying large granularity services between the first node and the second node is transmitted through the common OH channel.

[0460] In a possible implementation, the first link is a link between a first physical interface of the first node and a second physical interface of the second node, and the identifier of the first physical interface is further included in the first LLDP packet.

[0461] In a possible implementation, the sending unit 622 is further configured to: send additional attributes of the first physical interface to the second node.

[0462] In a possible implementation, the additional attributes of the first physical interface include one or more of the following: the large granularity capabilities supported by the first physical interface, the configured bandwidth of the first physical interface, the remaining bandwidth of the first physical interface, and the available time slots of the first physical interface.

[0463] In a possible implementation, the large granularity capabilities supported by the first physical interface include one or more of the following: the granularity bearing capabilities supported by the first physical interface, cross-PHY bundling capabilities, dynamic large granularity channel capabilities, static large granularity channel capabilities, and large granularity time slot following capabilities. Among them, the first physical interface having the dynamic large granularity channel capabilities indicates that the first physical interface can participate in the calculation of dynamic end-to-end paths, and the first physical interface having the static large granularity channel capabilities indicates that the first physical interface can establish static end-to-end paths through static configuration. Both the dynamic end-to-end paths and the static end-to-end paths are paths for carrying large granularity services, and the large granularity time slot following capabilities are used to indicate whether the first physical interface has the ability to automatically follow the upstream large granularity time slot configuration.

[0464] In a possible implementation, a first TLV of the first LLDP packet further includes a third sub-TLV, and the large granularity capabilities supported by the first physical interface are included in the third sub-TLV.

[0465] In a possible implementation, if the large granularity time slot following capabilities indicate that the first physical interface has the ability to automatically follow the upstream large granularity time slot configuration, the large granularity time slot following capabilities further indicate the following method for the first physical interface to automatically follow the upstream large granularity time slot configuration, and the following method includes: following through data plane packets and / or following through control plane packets.

[0466] In a possible implementation, if the first link is a link carrying small particle services, then: the first interface identifier includes: a first client identifier corresponding to the first node, and the first client identifier is used to identify the first client corresponding to the first node.

[0467] In a possible implementation, the first client identifier is the index of the first client; or, the first client identifier is determined according to the transmission identifier of the first client and the identifier of the FlexE group to which the first client belongs; or, in a scenario where physical ports are directly divided into sub-slots, the first client identifier is the identifier of the physical interface that divides to obtain the first client, or the first client identifier is the interface index of the first client.

[0468] In a possible implementation, the first link is a link between the first client of the first node and the second client of the second node, and the sending unit 622 is configured to: send the first LLDP message to the second node through a general communication channel GCC corresponding to the first link.

[0469] In a possible implementation, the sending unit 622 is configured to: send the first LLDP message to the second node through a general GCC, where link information of multiple links carrying small particle services between the first node and the second node is transmitted through the general GCC channel.

[0470] In a possible implementation, the first link is a link between the first client of the first node and the second client of the second node, and the first LLDP message further includes a transmission identifier of the first client.

[0471] In a possible implementation, the sending unit 622 is further configured to: send additional attributes of the first client to the second node.

[0472] In a possible implementation, the additional attributes of the first client include one or more of the following: small particle capabilities supported by the first client, configured bandwidth of the first client, remaining bandwidth of the first client, and available sub-slots of the first client.

[0473] In a possible implementation, the small particle capabilities supported by the first client include one or more of the following: whether the first client supports small particle technology, dynamic small particle channel capabilities, static small particle channel capabilities, and small particle time slot following capabilities. Among them, the first client having the dynamic small particle channel capabilities indicates that the first client can participate in the calculation of the dynamic end-to-end path. The first client having the static small particle channel capabilities indicates that the first client can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths for carrying small particle services. The small particle time slot following capabilities are used to indicate whether the first client has the ability to automatically follow the upstream small particle time slot configuration.

[0474] In a possible implementation, the first TLV of the first LLDP packet further includes a fourth sub-TLV, and the small particle capabilities supported by the first client are included in the fourth sub-TLV; alternatively, the small particle capabilities supported by the first client are carried by the operation, administration, and maintenance (OAM) code block sent by the first node to the second node.

[0475] In a possible implementation, if the small particle time slot following capabilities indicate that the first client has the ability to automatically follow the upstream small particle time slot configuration, then the small particle time slot following capabilities further indicate the following manner in which the first client automatically follows the upstream small particle time slot configuration. The following manner includes: following through data plane packets and / or following through control plane packets.

[0476] See Figure 7 , which is a schematic structural diagram of an information processing device provided in an embodiment of the present application. Figure 7 The information processing device 700 shown includes a processing circuit 710 and an interface circuit 720. The processing circuit 710 and the interface circuit 720 are coupled to each other. It can be understood that the interface circuit 720 can be a transceiver or an input / output interface. Optionally, the information processing device 700 may further include a memory for storing instructions executed by the processing circuit or storing input data required for the processing circuit 710 to run instructions or storing data generated after the processing circuit 710 runs instructions. In one example, the interface circuit 720 is used to perform the transceiver operations executed by the first node provided in the above method embodiment, and the processing circuit 710 is used to perform other operations executed by the first node except for the transceiver operations. In another example, the interface circuit 720 is used to perform the transceiver operations executed by the second node provided in the above method embodiment, and the processing circuit 710 is used to perform other operations executed by the second node except for the transceiver operations.

[0477] See Figure 8 , which is a schematic structural diagram of another information processing device provided by an embodiment of the present application. Figure 8 The information processing device 800 shown includes a processor 810 and a communication interface 820. The processor 810 and the communication interface 820 are coupled to each other. It can be understood that the communication interface 820 can be a transceiver or an input / output interface. Optionally, the information processing device 800 may further include a memory 830 for storing instructions executed by the processor 810 or storing input data required for the processor 810 to run instructions or storing data generated after the processor 810 runs instructions. In one example, the communication interface 820 is used to perform the transceiver operations executed by the first node provided in the above method embodiment, and the processor 810 is used to perform other operations except the transceiver operations executed by the first node. In another example, the communication interface 820 is used to perform the transceiver operations executed by the second node provided in the above method embodiment, and the processor 810 is used to perform other operations except the transceiver operations executed by the second node.

[0478] An embodiment of the present application provides a computer-readable storage medium, including instructions or a computer program, which, when running on a processor, executes the method described in any one of the above method embodiments.

[0479] An embodiment of the present application provides a computer program product, including a computer program product, which, when running on a processor, executes the method described in any one of the above method embodiments.

[0480] An embodiment of the present application further provides a communication system, which may include the first node and the second node mentioned in the above method embodiments. The first node is used to perform the operations executed by the first node mentioned in the above embodiments, and the second node is used to perform the operations executed by the second node mentioned in the above embodiments, so that the communication system can execute the information processing method provided in the above embodiments. The terms "first", "second", "third", "fourth", etc. (if any) in the specification, claims and drawings of the present application are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments described here can be implemented in an order different from that shown or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these process, method, product or device.

[0481] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0482] In several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is only a logical service division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of devices or units can be in electrical, mechanical, or other forms.

[0483] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0484] In addition, each service unit in various embodiments of the present application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software service units.

[0485] If the integrated unit is implemented in the form of a software service unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in various embodiments of the present application. The foregoing storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks, or optical discs, and other media that can store program codes.

[0486] Those skilled in the art should be able to realize that in one or more of the above examples, the operations described in the present invention can be implemented by hardware, software, firmware, or any combination thereof. When implemented using software, these operations can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. The computer-readable medium includes computer storage media and communication media, where the communication media includes any medium that facilitates the transfer of a computer program from one place to another. The storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0487] The above specific implementation manners have further elaborated on the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above is only the specific implementation manner of the present invention.

[0488] In the above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the various embodiments of the present application.

Claims

1. An information processing method, characterized in that Applied to a second node, the method includes: Receiving a first node identifier and a first interface identifier sent by a first node, where the first node identifier is used to identify the first node, and the first interface identifier is used to identify a first interface of the first node for communicating with the second node; Obtaining first link information according to the first node identifier, the first interface identifier, a second node identifier, and a second interface identifier, where the second node identifier is used to identify the second node, the second interface identifier is used to identify a second interface of the second node for communicating with the first node, and the first link information is used to indicate a first link between the first interface and the second interface, and the first link is a link for carrying large-granularity services or a link for carrying small-granularity services.

2. The method according to claim 1, characterized in that, The receiving the first node identifier and the first interface identifier sent by the first node includes: Receiving a first Link Layer Discovery Protocol (LLDP) packet sent by the first node, where the first LLDP packet includes a first Type-Length-Value (TLV), and the first TLV includes the first node identifier and the first interface identifier.

3. The method according to claim 2, characterized in that, The first TLV includes a first sub-TLV and a second sub-TLV, the first sub-TLV includes the first node identifier, and the second sub-TLV includes the first interface identifier.

4. The method according to claim 2 or 3, characterized in that, The first TLV is a vendor TLV.

5. The method according to any one of claims 2 to 4, characterized in that If the first link is a link for carrying large-granularity services, then: The first interface identifier includes: a first FlexE group identifier corresponding to the first node, and the first FlexE group identifier is used to identify a first FlexE group corresponding to the first node; The second interface identifier includes: a second FlexE group identifier corresponding to the second node, and the second FlexE group identifier is used to identify a second FlexE group corresponding to the second node.

6. The method according to claim 5, wherein The first link is a link between a first physical interface of the first node and a second physical interface of the second node, and the receiving the first Link Layer Discovery Protocol (LLDP) packet sent by the first node includes: Receiving the first LLDP packet through an overhead (OH) channel corresponding to the first link, where the OH channel corresponding to the first link is used to carry link information of the first link.

7. The method according to claim 5, characterized in that The receiving the first Link Layer Discovery Protocol (LLDP) packet sent by the first node includes: Receiving the first LLDP packet through a common OH channel, where link information of multiple links for carrying large-granularity services between the first node and the second node is transmitted through the common OH channel.

8. The method according to claim 7, wherein The first link is a link between a first physical interface of the first node and a second physical interface of the second node, and the first LLDP packet further includes an identifier of the first physical interface.

9. The method according to claim 8, characterized in that Before obtaining the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier, the method further includes: Determine a second physical interface connected to the first physical interface according to the identifier of the first physical interface; Obtain first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier, including: When the second physical interface is fault-free, obtain the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier.

10. The method according to any one of claims 6-9, characterized in that, The method further includes: Determine the link attributes of the first link, where the link attributes of the first link include at least one of the following: the identifier of the first physical interface, the identifier of the second physical interface, the additional attributes of the first physical interface, and the additional attributes of the second physical interface.

11. The method according to claim 10, wherein The target physical interface includes the first physical interface or the second physical interface, and the additional attributes of the target physical interface include one or more of the following: The large-granularity capability supported by the target physical interface, the configured bandwidth of the target physical interface, the remaining bandwidth of the target physical interface, and the available time slots of the target physical interface.

12. The method according to claim 11, wherein The large-granularity capability supported by the target physical interface includes one or more of the following: The granularity-bearing capability supported by the target physical interface, the cross-PHY bundling capability, the dynamic large-granularity channel capability, the static large-granularity channel capability, and the large-granularity time-slot following capability. Among them, the target physical interface having the dynamic large-granularity channel capability indicates that the target physical interface can participate in the calculation of the dynamic end-to-end path, and the target physical interface having the static large-granularity channel capability indicates that the target physical interface can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths for carrying large-granularity services, and the large-granularity time-slot following capability is used to indicate whether the target physical interface has the ability to automatically follow the upstream large-granularity time-slot configuration.

13. The method according to claim 12, wherein The method further includes: receiving the additional attributes of the first physical interface sent by the first node.

14. The method according to claim 12 or 13, characterized in that, The first TLV of the first LLDP packet further includes a third sub-TLV, and the third sub-TLV includes the large-granularity capability supported by the first physical interface.

15. The method according to any one of claims 12 - 14, characterized in that, If the large-granularity time-slot following capability indicates that the target physical interface has the ability to automatically follow the upstream large-granularity time-slot configuration, the large-granularity time-slot following capability further indicates the following method for the target physical interface to automatically follow the upstream large-granularity time-slot configuration, and the following method includes: following through data-plane packets and / or following through control-plane packets.

16. The method according to any one of claims 10-14, characterized in that, The method further includes: Receiving a second LLDP packet sent by the first node, where the second LLDP packet includes the first node identifier and the first interface identifier; Obtain second link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier. The second link information is the same as the first link information, and the second link information is used to identify a second link between the first interface and the second interface. The second link is a link for carrying large-granularity services, and the second link is a link between a third physical interface of the first node and a fourth physical interface of the second node; Determine the link attributes of the second link. The link attributes of the second link include at least one of the following: the identifier of the third physical interface, the identifier of the fourth physical interface, the additional attributes of the third physical interface, and the additional attributes of the fourth physical interface.

17. The method according to claim 16, wherein The method further includes: Merge the first link information, the second link information, the link attributes of the first link, and the link attributes of the second link to obtain target link information and target link attributes. The target link information is the first link information, and the target link attributes include the link attributes of the first link and the link attributes of the second link.

18. The method according to claim 17, characterized in that, The method further includes: Send the target link information and the target link attributes to the controller.

19. The method according to any one of claims 2-4, characterized in that If the first link is a link for carrying small-granularity services, then: The first interface identifier includes: a first client identifier corresponding to the first node, and the first client identifier is used to identify the first client corresponding to the first node; The second interface identifier includes: a second client identifier corresponding to the second node, and the second client identifier is used to identify the second client corresponding to the second node.

20. The method according to claim 19, wherein The first client identifier is the index of the first client; or, the first client identifier is determined according to the transmission identifier of the first client and the identifier of the FlexE group to which the first client belongs; or, in a scenario where physical ports are directly divided into sub-time slots, the first client identifier is the identifier of the physical interface from which the first client is divided, or the first client identifier is the interface index of the first client.

21. The method according to claim 19 or 20, characterized in that, The first link is a link between the first client of the first node and the second client of the second node. Receiving the first Link Layer Discovery Protocol (LLDP) packet sent by the first node includes: Receiving the first LLDP packet through the general communication channel (GCC) corresponding to the first link.

22. The method according to claim 19 or 20, characterized in that, Receiving the first Link Layer Discovery Protocol (LLDP) packet sent by the first node includes: Receiving the first LLDP packet through the general GCC, where the link information of multiple links for carrying small-granularity services between the first node and the second node is transmitted through the general GCC channel.

23. The method according to claim 22, wherein The first link is the link between the first client of the first node and the second client of the second node, and the transmission identifier of the first client is further included in the first LLDP packet.

24. The method according to claim 23, characterized in that, Before obtaining the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier, the method further includes: Determining a second client connected to the first client according to the transmission identifier of the first client; Obtaining the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier, including: When the second client is fault-free, obtaining the first link information according to the first node identifier, the first interface identifier, the second node identifier, and the second interface identifier.

25. The method according to any one of claims 21-24, characterized in that, The method further includes: Determining the link attributes of the first link, where the link attributes of the first link include at least one of the following: the identifier of the first client, the identifier of the second client, the additional attributes of the first client, and the additional attributes of the second client.

26. The method according to claim 25, wherein The target client includes the first client or the second client, and the additional attributes of the target client include one or more of the following: The small-granularity capability supported by the target client, the configured bandwidth of the target client, the remaining bandwidth of the target client, and the available sub-slots of the target client.

27. The method according to claim 26, wherein The small-granularity capability supported by the target client includes one or more of the following: Whether the target client supports small-granularity technology, dynamic small-granularity channel capability, static small-granularity channel capability, and small-granularity time-slot following capability. Among them, the target client having the dynamic small-granularity channel capability indicates that the target client can participate in the calculation of the dynamic end-to-end path, and the target client having the static small-granularity channel capability indicates that the target client can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths carrying small-granularity services, and the small-granularity time-slot following capability is used to indicate whether the target client has the ability to automatically follow the upstream small-granularity time-slot configuration.

28. The method according to claim 27, wherein The method further includes: receiving the additional attributes of the first client sent by the first node.

29. The method according to claim 27 or 28, characterized in that, The first TLV of the first LLDP packet further includes a fourth sub-TLV, and the small-granularity capability supported by the first client is included in the fourth sub-TLV; Or, The small-granularity capability supported by the first client is carried by the operation, administration, and maintenance (OAM) code block sent by the first node to the second node.

30. The method according to any one of claims 27-29, characterized in that, If the small granule time slot following ability indicates that the target client has the ability to automatically follow the upstream small granule time slot configuration, then the small granule time slot following ability also indicates the following mode for the target client to automatically follow the upstream small granule time slot configuration. The following mode includes: following through data plane messages and / or following through control plane messages.

31. The method according to claim 25, wherein The method further includes: Sending the first link information and the link attributes of the first link to the controller.

32. An information processing method, characterized in that, Applied to the first node, the method includes: Obtaining a first node identifier and a first interface identifier, where the first node identifier is used to identify the first node, and the first interface identifier is used to identify the first interface of the first node for communicating with the second node; Sending the first node identifier and the first interface identifier to the second node, where the first node identifier and the first interface identifier are used to enable the second node to obtain first link information, and the first link information is used to indicate a first link between the first interface and a second interface of the second node, and the first link is a link carrying large granule services or a link carrying small granule services.

33. The method according to claim 32, wherein, The sending the first node identifier and the first interface identifier to the second node includes: Sending a first Link Layer Discovery Protocol (LLDP) message to the second node, where the first LLDP message includes a first Type-Length-Value (TLV), and the first TLV includes the first node identifier and the first interface identifier.

34. The method according to claim 33, wherein The first TLV includes a first sub-TLV and a second sub-TLV. The first sub-TLV includes the first node identifier, and the second sub-TLV includes the first interface identifier.

35. The method according to claim 33 or 34, characterized in that, The first TLV is a vendor TLV.

36. The method according to any one of claims 33-35, characterized in that, If the first link is a link carrying large granule services, then: The first interface identifier includes: a first FlexE group identifier corresponding to the first node, and the first FlexE group identifier is used to identify the first FlexE group corresponding to the first node.

37. The method according to claim 36, wherein The first link is a link between a first physical interface of the first node and a second physical interface of the second node. The sending the first Link Layer Discovery Protocol (LLDP) message to the second node includes: Sending the first LLDP message to the second node through an overhead (OH) channel corresponding to the first link, where the OH channel corresponding to the first link is used to carry the link information of the first link.

38. The method according to claim 36, characterized in that, The sending the first Link Layer Discovery Protocol (LLDP) message to the second node includes: Sending the first LLDP message to the second node through a common OH channel, where the link information of multiple links carrying large granule services between the first node and the second node is transmitted through the common OH channel.

39. The method according to claim 37 or 38, characterized in that, The method further includes: Sending additional attributes of the first physical interface to the second node.

40. The method according to claim 39, wherein The additional attributes of the first physical interface include one or more of the following: The large-granule capabilities supported by the first physical interface, the configured bandwidth of the first physical interface, the remaining bandwidth of the first physical interface, and the available time slots of the first physical interface.

41. The method according to claim 40, wherein The large-granule capabilities supported by the first physical interface include one or more of the following: The granularity-bearing capabilities supported by the first physical interface, cross-PHY bundling capabilities, dynamic large-granule channel capabilities, static large-granule channel capabilities, and large-granule time-slot following capabilities. Among them, the first physical interface having the dynamic large-granule channel capabilities indicates that the first physical interface can participate in the calculation of dynamic end-to-end paths; the first physical interface having the static large-granule channel capabilities indicates that the first physical interface can establish static end-to-end paths through static configuration. Both the dynamic end-to-end paths and the static end-to-end paths are paths for carrying large-granule services. The large-granule time-slot following capabilities are used to indicate whether the first physical interface has the ability to automatically follow the upstream large-granule time-slot configuration.

42. The method according to claim 40 or 41, characterized in that, The first TLV of the first LLDP packet further includes a third sub-TLV, and the third sub-TLV includes the large-granule capabilities supported by the first physical interface.

43. The method according to any one of claims 33-35, characterized in that, If the first link is a link for carrying small-granule services, then: The first interface identifier includes: the first client identifier corresponding to the first node, and the first client identifier is used to identify the first client corresponding to the first node.

44. The method according to claim 43, wherein The first client identifier is the index of the first client; or the first client identifier is determined according to the transmission identifier of the first client and the identifier of the FlexE group to which the first client belongs; or in the scenario of directly dividing sub-time slots for physical ports, the first client identifier is the identifier of the physical interface obtained by dividing to get the first client, or the first client identifier is the interface index of the first client.

45. The method according to claim 43 or 44, characterized in that, The first link is a link between the first client of the first node and the second client of the second node. Sending the first Link Layer Discovery Protocol (LLDP) packet to the second node includes: Sending the first LLDP packet to the second node through the general communication channel (GCC) corresponding to the first link.

46. The method according to claim 43 or 44, characterized in that, Sending the first Link Layer Discovery Protocol (LLDP) packet to the second node includes: Sending the first LLDP packet to the second node through the general GCC, where the link information of multiple links for carrying small-granule services between the first node and the second node is transmitted through the general GCC channel.

47. The method according to claim 46, wherein The first link is a link between the first client of the first node and the second client of the second node, and the first LLDP packet further includes the transmission identifier of the first client.

48. The method according to any one of claims 45-47, characterized in that, The method further includes: Sending the additional attributes of the first client to the second node.

49. The method according to claim 48, wherein The additional attributes of the first client include one or more of the following: The small particle capabilities supported by the first client, the configured bandwidth of the first client, the remaining bandwidth of the first client, and the available sub-slots of the first client.

50. The method according to claim 49, wherein, The small particle capabilities supported by the first client include one or more of the following: Whether the first client supports small particle technology, dynamic small particle channel capabilities, static small particle channel capabilities, and small particle time slot following capabilities. Among them, the first client having the dynamic small particle channel capabilities indicates that the first client can participate in the calculation of the dynamic end-to-end path. The first client having the static small particle channel capabilities indicates that the first client can establish a static end-to-end path through static configuration. Both the dynamic end-to-end path and the static end-to-end path are paths for carrying small particle services. The small particle time slot following capabilities are used to indicate whether the first client has the ability to automatically follow the upstream small particle time slot configuration.

51. The method according to claim 49 or 50, characterized in that, The first TLV of the first LLDP packet further includes a fourth sub-TLV, and the fourth sub-TLV includes the small particle capabilities supported by the first client; Or, The small particle capabilities supported by the first client are carried by the operation, administration, and maintenance (OAM) code block sent by the first node to the second node.

52. An information processing apparatus, characterized in that, The device includes a plurality of functional modules, and the plurality of functional modules interact with each other to implement the method according to any one of claims 1 to 51.

53. An information processing device, characterized in that, Including: A communication interface and a processor. According to the communication interface and the processor, the communication device executes the method according to any one of claims 1 - 51.

Images