CN110493292B

CN110493292B - Capability notification method, device, system, storage medium and electronic device

Info

Publication number: CN110493292B
Application number: CN201810456489.1A
Authority: CN
Inventors: 敖婷; 喻敬海
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-05-14
Filing date: 2018-05-14
Publication date: 2022-08-19
Anticipated expiration: 2038-05-14
Also published as: CN110493292A

Abstract

The invention provides a capability notification method, a device, a system, a storage medium and an electronic device, wherein the method comprises the following steps: setting a link layer discovery protocol message LLDPDU (link layer discovery protocol) in a local end system, wherein the LLDPDU carries capability information of the local end system; and sending the LLDPDU to a peer-to-peer system. The invention can solve the technical problem that the two ends of the system are incompatible easily when LRP links are established at the two ends of the system in the related technology.

Description

Capability notification method, device, system, storage medium and electronic device

Technical Field

The present invention relates to the field of communications, and in particular, but not limited to, a capability notification method, apparatus, system, storage medium, and electronic apparatus.

Background

As the demand for network devices becomes more diverse, it is required that various information and device attributes can be interacted between the devices. The IEEE802.1 working group has established for this purpose the MRP (media redundancy protocol) protocol for enabling registration and de-registration of some device attributes between devices, e.g. vlan id, multicast membership, etc. However, with the diversification of networks and the great abundance of application scenarios, the MRP protocol is limited by the size of its registration information, and cannot meet the requirements of link registration in many application scenarios. Therefore, a point-to-point hop-by-hop Link Registration Protocol (LRP) is proposed in the IEEE802.1 working group, and the Protocol can ensure that the registered information is as high as 1MB, so that the Protocol can be more suitable for more large-capacity application scene requirements.

In the related art, before the registered devices at the two ends effectively establish connection, no interaction of capabilities is performed, which results in incompatibility of device capabilities and failure in connection establishment.

In view of the above problems in the related art, no effective solution has been found at present.

Disclosure of Invention

The embodiment of the invention provides a capability notification method, a capability notification device, a capability notification system, a storage medium and an electronic device.

According to an embodiment of the present invention, there is provided a capability advertisement method including: setting a link layer discovery protocol message LLDPDU (link layer discovery protocol) in a local end system, wherein the LLDPDU carries capability information of the local end system; and sending the LLDPDU to a peer-to-peer system.

According to another embodiment of the present invention, there is provided a capability notification apparatus including: a setting module, configured to set a link layer discovery protocol message LLDPDU in a home terminal system, where the LLDPDU carries capability information of the home terminal system; and the sending module is used for sending the LLDPDU to a peer-to-peer system.

According to another embodiment of the present invention, a capability notification system is provided, which includes a home terminal system and a peer terminal system, where the home terminal system includes: a first setting module, configured to set a first link layer discovery protocol message LLDPDU in a home terminal system, where the first LLDPDU carries capability information of the home terminal system; a first sending module, configured to send the first LLDPDU to the peer system; the opposite-end system comprises: a second setting module, configured to set a second LLDPDU in an opposite-end system, where the second LLDPDU carries capability information of the opposite-end system; and a second sending module, configured to send the second LLDPDU to the home system.

According to a further embodiment of the present invention, there is also provided a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.

According to yet another embodiment of the present invention, there is also provided an electronic device, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.

By the invention, the capability information of the system at the local end is sent to the opposite-end system, so that the systems at two ends of the link can mutually inform the capabilities of the LRP protocols, the compatibility of the systems at two ends of the link is ensured, the LRP link between two ends can be more quickly and effectively established, and the technical problem that the two ends of the system are incompatible easily when the LRP link is established at the two ends of the system in the related technology is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention and do not constitute a limitation of the invention. In the drawings:

FIG. 1 is a network architecture diagram of an embodiment of the present invention;

FIG. 2 is a flow diagram of a capability advertisement method according to an embodiment of the present invention;

fig. 3 is a block diagram of a configuration of a capability advertisement device according to an embodiment of the present invention;

FIG. 4 is a block diagram of a capability advertisement system according to an embodiment of the present invention;

FIG. 5 is a system connection diagram of an embodiment;

FIG. 6 is a flow diagram illustrating an LRP protocol in a first embodiment;

FIG. 7 is a flowchart of matching application capabilities in the present embodiment;

fig. 8 is a flowchart illustrating the LRP protocol in this embodiment.

Detailed Description

The invention will be described in detail hereinafter with reference to the drawings and embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

Example 1

The embodiment of the present application may operate on a network architecture shown in fig. 1, where fig. 1 is a network architecture diagram of the embodiment of the present invention, and as shown in fig. 1, based on an LRP protocol, the LRP protocol supports two transmission mechanisms, one is a transmission mechanism based on ecp (encryption Control protocol), and the other is a transmission mechanism based on tcp (transmission Control protocol). ECP is a two-layer Protocol, and in order to ensure that each LRPDU (Link-Local Registration Protocol Data Unit for short) can be transmitted in an ECP message, there is a need to limit the length of the LRPDU; TCP is a four-layer transport mechanism that can support LRPDU's of greater length. The upper layer Application of the LRP protocol triggers LRP instances, each instance comprising a registry database and an Application database. The corresponding Application information received through LRP-DT will be stored in the registry database for Application. And meanwhile, the Application puts the information which needs to be synchronized to other applications for use into an Application database.

In this embodiment, a capability advertisement method operating in the network architecture is provided, and fig. 2 is a flowchart of the capability advertisement method according to an embodiment of the present invention, as shown in fig. 2, the flowchart includes the following steps:

step S202, a link layer discovery protocol message LLDPDU is arranged in a home terminal system, wherein the LLDPDU carries the capability information of the home terminal system;

step S204, the LLDPDU is sent to the opposite system.

Through the steps, the capability information of the local system is sent to the opposite-end system, so that the systems at two ends of the link can mutually inform the capabilities of the LRP protocols, the systems at two ends of the link can be compatible, the LRP links between two ends can be quickly and effectively established, and the technical problem that the two ends of the system are incompatible when the LRP links are established at the two ends of the system in the related technology is solved.

Optionally, the capability of the home terminal system includes a transmission mechanism of a link registration protocol LRP supported by the home terminal system. The transmission mechanism includes at least one of: the encryption control protocol ECP, the transmission control protocol TCP.

Optionally, before sending the LLDPDU to the peer system, the method further includes: the LLDP protocol is triggered by the LRP instance and then the LLDPDU is set by the LLDP protocol.

Optionally, after sending the LLDPDU to the peer system or before sending the LLDPDU to the peer system, the capability information of the peer system is further received, and it is determined whether the capabilities of the peer system and the home system are matched.

Optionally, after determining whether the capabilities of the peer system and the home system are matched, the method further includes: when the capabilities of the opposite end system and the local end system are matched, the capabilities are notified to an LRP example of the local end system, and matching detection of an upper layer application program is initiated.

Optionally, initiating match detection for the upper-layer application includes: and the LRP example of the local terminal system sends the information carrying the corresponding upper-layer application program identifier to the opposite terminal system.

Optionally, after the LRP instance initiates match detection for the upper layer application, the method further comprises: the LRP instance of the local end system judges whether the upper layer application corresponding to the LRP instance of the opposite end system is matched with the upper layer application corresponding to the LRP instance of the local end system; and when the application programs of the opposite end system and the local end system are matched, establishing LRP connection between the opposite end system and the local end system.

Optionally, the determining, by the LRP instance of the home terminal system, whether the upper layer application program corresponding to the LRP instance of the peer system matches the upper layer application program corresponding to the LRP instance of the home terminal system includes: the LRP example of the local terminal system receives a second message sent by the opposite terminal system through an LRP protocol, wherein the second message carries a second application identifier of the opposite terminal system; and judging whether the upper-layer application program corresponding to the LRP instance of the opposite-end system and the local-end system is matched or not by matching the first application identifier and the second application identifier of the local-end system.

Optionally, the determining whether the capabilities of the peer system and the home system are matched includes one of the following:

receiving a notification message sent by an opposite-end system, wherein the notification message is used for describing the capability of the opposite-end system; judging whether the capabilities of the opposite terminal system and the local terminal system are matched or not according to the notification message;

after the LLDPDU is sent to the opposite terminal system for a preset number of times, whether a notification message sent by the opposite terminal system is received or not is determined, and when the notification message is not received, the capability mismatching between the opposite terminal system and the local terminal system is judged.

Optionally, before the LLDPDU is set by the home terminal system, the method further includes: and the application program in the local end system initiates an information synchronization request to a port connected with the local end system and the opposite end system, and establishes an LRP example at the port. The LRP instance further triggers LLDP to send LRP capability discovery TLV (Type-Length-Value), i.e., LLDPDU.

Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method according to the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention or portions thereof contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes several instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the method of the embodiments of the present invention.

Example 2

In this embodiment, a capability notification apparatus and a system are further provided for implementing the foregoing embodiments and preferred embodiments, which have already been described and are not described again. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 3 is a block diagram of a capability notification apparatus according to an embodiment of the present invention, as shown in fig. 3, the apparatus including:

a setting module 30, configured to set a link layer discovery protocol message LLDPDU in a home terminal system, where the LLDPDU carries capability information of the home terminal system;

and a sending module 32, configured to send the LLDPDU to the peer system.

Optionally, the capability of the home terminal system includes a transmission mechanism of the LRP supported by the home terminal system.

Optionally, the apparatus further comprises: the judging module is used for triggering an LRP protocol when the capacities of the opposite end system and the home end system are matched, and judging whether the application programs of the opposite end system and the home end system are matched or not through the LRP protocol; and the establishing module is used for establishing LRP connection between the opposite end system and the local end system when the application programs of the opposite end system and the local end system are matched.

Fig. 4 is a block diagram of a structure of a capability notification system according to an embodiment of the present invention, as shown in fig. 4, including a home terminal system 40 and a peer terminal system 42, where the home terminal system 40 includes: a first setting module 400, configured to set a first link layer discovery protocol message LLDPDU in a home system, where the first LLDPDU carries capability information of the home system; a first sending module 402, configured to send the first LLDPDU to the peer system;

the peer system 42 includes: a second setting module 420, configured to set a second LLDPDU in the peer system, where the second LLDPDU carries capability information of the peer system; a second sending module 422, configured to send the second LLDPDU to the local system.

It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.

Example 3

The present embodiment proposes a method that enables discovery of LRP capabilities before initiating the LRP protocol.

In this embodiment, the notification of the LRP capability is performed by expanding the LLDP protocol supported by most of the devices, so that the nodes at both ends of the link can notify each other of the capabilities of the LRP protocol, thereby ensuring that the LRP links between both ends can be established more quickly and efficiently. The method comprises the following steps:

a new TLV for LLDP (Link layer discovery protocol) LRP capability TLV is defined. The fields of the TLV include:

LRP capability TLV type

LRP capability TLV value

Wherein the TLV values mainly include the following: type supported by LRP transport protocol LRP-DT: ECP is also TCP, when both ends of the link support the same type of transport protocol as the transport protocol of the LRP, LLDP informs the LRP of a matching message, and LRP-DT initiates its end-to-end connection mechanism. Otherwise, an error message is announced to the LRP.

LRP-DT sends Hello message carrying Application ID (Application ID) to be linked, and the two establish connection only when the Application IDs interacted between the two endpoints are detected to be consistent. Each group of applications establishes a connection.

The embodiment further includes the following embodiments, which are used to explain the scheme of the embodiment in detail:

implementation mode one

As shown in fig. 5, fig. 5 is a schematic diagram of system connection of the embodiment, synchronization of some information is required between the system 1 (home end system) and the system 2 (peer end system), and because the amount of data to be synchronized is large, the LRP protocol is used here.

First, the Application1 in system 1 sends an information synchronization request to the port connected to system 2, and the LRP protocol creates an LRP instance on the port, where the LRP instance includes an Application database and a registry database of the Application1, and the transmission protocol of the LRP instance is ECP. The same Application2 in system 2 also initiates an information synchronization request, and LRP creates an LRP instance on the port connected with system 1 according to the request message, the LRP instance contains an Application database and registry database of Application2, and the transmission protocol of the LRP instance is ECP.

Therefore, before the connection between the system 1 and the system 2 is established, the LRP instance on the two ports where the system 1 and the system 2 are connected to each other will trigger the LLDP protocol that most systems will support first, at this time, the LLDP protocol triggered by the LRP will carry the relevant LRP capability discovery TLV information in the LLDPDU message before sending to the opposite end, and the format may be as shown in table 1:

TABLE 1

TLV type

TLV length

802.1OUI

S _u b-TLV type

Type of transmission

The sub-TLV type field indicates that the port of the system supports LRP protocol, and the TLV carries relevant information of LRP protocol.

The transmission type here refers to the type adopted by LRP-DT, 0 value is reserved, 1 means LRP-DT is ECP protocol, 2 means LRP-DT is TCP protocol, and 3 means both ECP and TCP transmission protocols are supported.

In this embodiment, the system 1 sends the LLDPDU carrying the LRP information through a port connected to the system 2. In the LLDPDU message, Sub-TLV type in LRP capability discovery TLV identifies that it is an LRP capability discovery TLV, and value in transmission type is 1 (ECP).

Similarly, the system 2 sends the LLDPDU carrying the LRP information through the port connected to the system 1. In this LLDPDU message, Sub-TLV type in LRP capability discovery TLV identifies that it is an LRP capability discovery TLV, and value in transmission type is 1 (ECP).

The LLDP protocol of system 1 receives the LLDPDU from system 2, and if it is known from the message that the peer system 2 also supports the LRP protocol, and the transmission protocol is ECP, and is compatible with the LRP protocol of this system, it notifies the LRP protocol of a success message of LRP capability discovery. And if the LRP protocol obtains the success message, sending an LRP connection message, wherein the connection message carries the Application ID of the Application1 on the upper layer. When the system 1 receives the Application ID from the system 2 and the Application ID given by the LRP instance are identical, it is determined that a connection is established between the two, and the synchronization of the related data can be performed. Fig. 6 is a schematic flowchart of the LRP protocol according to the first embodiment.

Second embodiment

In this embodiment, the system 1 sends the LLDPDU carrying the LRP information through a port connected to the system 2. In this LLDPDU message, Sub-TLV type in LRP capability discovery TLV identifies that it is an LRP capability discovery TLV, and value in transmission type is 1 (ECP). System 2 does not receive the synchronization message from the application and therefore does not create an LRP instance and therefore system 2 does not send LLDPDU containing the LRP capability discovery TLV. For the system 1, after several LLDPDU messages are continuously sent, if no LLDPDU carrying LRP capability discovery TLV is received from the system 2 at the opposite end, the system 1 considers that the system 2 does not support the LRP protocol and cannot implement synchronization between the two systems, and reports an error that the opposite end does not support LRP to the application program initiating this synchronization. Specific flow referring to fig. 7, fig. 7 is a flow chart of matching application capabilities in the present embodiment.

Third embodiment

First, the Application1 in system 1 sends an information synchronization request to the port connected to system 2, and the LRP protocol will first create an LRP instance on the port, where the LRP instance contains an Application database and a registry database of Application1, and the transmission protocol of the LRP instance is ECP. The same Application2 in system 2 also initiates an information synchronization request, and the LRP creates an LRP instance on the port connected to system 1 according to the request message, wherein the LRP instance includes an Application database and a registry database of Application2, and the transmission protocol of the LRP instance is ECP.

Therefore, before the connection between the system 1 and the system 2 is established, the LRP instance on the two interconnected ports of the system 1 and the system 2 will trigger the LLDP protocol that most systems will support first, and at this time, the LLDP protocol triggered by the LRP will carry the relevant LRP capability discovery TLV information in the LLDPDU message before sending to the opposite end. In this embodiment, the system 1 sends an LLDPDU message to the end system 2, where a value in a transmission type in a sub-TLV in the LRP capability discovery TLV is 1 (ECP). Similarly, the system 2 sends an LLDPDU message to the end system 1, where the value in the transmission type in the sub-TLV in the LRP capability discovery TLV is 2 (TCP). At this time, no matter system 1 and system 2 can find that the transmission type adopted by the opposite end is inconsistent with the transmission type adopted by the LRP instance in the present system and the transmission type of the local end, each feeds back an incompatible error notification to the application program which initiates the synchronization message.

Embodiment IV

The present embodiment is based on the first embodiment, that is, both the system 1 and the system 2 are ECP-based transport links. When the end-to-end two ends are found to adopt the same LRP transmission protocol, the system matching between the two ends is started, and the systems at the two ends transmit an Application program extension TLV through the ECP, wherein the TLV contains an Application ID field for uniquely marking different Application programs. After Application IDs between the system 1 and the system 2 are connected and interacted through ECP, if the Application IDs are consistent or the types of the Application IDs are the same, the two systems are successfully matched, and data can be synchronized; otherwise, the two systems fail to be matched, and error information is reported to respective application programs. See in particular fig. 6.

Fifth embodiment

In this embodiment, before the system 1 and the system 2 establish a connection, the LRP capability of the systems needs to be discovered first, that is, the systems advertise the LRP capability discovery TLV through the LLDP protocol. Here, a transport type value of 1 in the LRP capability discovery TLV issued by system 1 indicates that ECP is supported, and a transport type value of 3 in the LRP capability discovery TLV issued by system 2 indicates that both ECP and TCP are supported. At this time, the system 2 receives the transmission mode that the system 1 only supports the ECP, and after the system 1 receives the ECP and TCP supported by the system 2, both systems also consider the ECP and TCP to be compatible, and the system 2 defaults to establish the ECP end-to-end connection with the system 1.

Sixth embodiment

In this embodiment, before the system 1 and the system 2 establish a connection, the LRP capabilities of the systems need to be discovered first, that is, the two systems advertise the LRP capability discovery TLV through the LLDP protocol. Here, a transport type value of 3 in the LRP capability discovery TLV issued by system 1 indicates that ECP and TCP are supported, and a transport type value of 3 in the LRP capability discovery TLV issued by system 2 indicates that both ECP and TCP are supported. At this time, the system 1 and the system 2 consider the two to be compatible, and choose the default mode of both sides, i.e. the transmission mode of the TCP, to establish the TCP connection between the two.

Seventh embodiment

In this embodiment, the decision of whether the transmission types at both ends are consistent is done by the LRP instance.

First, the Application1 in system 1 sends an information synchronization request to the port connected to system 2, and the LRP protocol will first create an LRP instance on the port, where the LRP instance contains an Application database and a registry database of Application1, and the transmission protocol of the LRP instance is ECP. The same Application2 in system 2 also initiates an information synchronization request, and LRP creates an LRP instance on the port connected with system 1 according to the request message, the LRP instance contains an Application database and registry database of Application2, and the transmission protocol of the LRP instance is ECP.

Therefore, before the connection between the system 1 and the system 2 is established, the LRP instance on the two ports where the system 1 and the system 2 are connected to each other will trigger the LLDP protocol that most devices will support first, at this time, the LLDP protocol triggered by the LRP will carry the relevant LRP capability discovery TLV information in the LLDPDU message before sending to the opposite end, and the format may be as shown in table 2:

TABLE 2

TLV type

TLV length

802.1OUI

S _u b-TLV type

Type of transmission

The sub-TLV type field indicates that the port of the system supports LRP protocol, and the TLV carries the relevant information of LRP protocol.

The transmission type here refers to the type adopted by LRP-DT, 0 value is reserved, 1 indicates that LRP-DT is ECP protocol, 2 indicates that LRP-DT is TCP protocol, and 3 indicates that both ECP and TCP transmission protocols are supported.

In this embodiment, suppose that the system 1 sends an LLDPDU carrying LRP information through a port connected to the system 2. In the LLDPDU message, Sub-TLV type in LRP capability discovery TLV identifies that it is an LRP capability discovery TLV, and value in transmission type is 1 (ECP).

Similarly, suppose that the system 2 sends LLDPDU carrying LRP information through a port connected to the system 1. In this LLDPDU message, Sub-TLV type in LRP capability discovery TLV identifies that it is an LRP capability discovery TLV, and value in transmission type is 1 (ECP).

The LLDP of the system 1 receives the LLDP message from the system 2, obtains that the port transmission type of the connection system 1 of the system 2 is ECP, and notifies the LRP instance, and since the port transmission type linked with the system 2 in this instance is also ECP, the LRP instance starts to establish LRP connection.

If the LRP instance in the embodiment of the system 1 is the TCP, the transmission type is the TCP; in the LRP example of the present embodiment in the system 2, the transmission type is ECP.

When the LLDP of the system 1 receives the transmission type from the system 2, the LLDP directly notifies the LRP instance, and if the LRP instance is judged to be unmatched, the LRP instance does not establish LRP connection with the system 2.

As another example, in the LRP example in the present embodiment in the system 1, the transmission types are both ECP and TCP (i.e., the value is 3); in the LRP example of the present embodiment in the system 2, the transmission type is ECP.

When the LLDP of the system 1 receives the transmission type from the system 2, the LLDP instance directly notifies the LRP instance, and the LRP instance is judged to be consistent with the LRP instance, that is, both parties can transmit in the ECP manner, so that the LRP instance initiates the LLDP protocol notification system 2 again, and the transmission protocol of the LRP instance of the system 1 is ECP. When the system 1 receives the transmission protocol of the LRP instance of the LLDP protocol advertisement system 2 from the system 2 as ECP, it starts to establish the LRP connection system with the system 2. Fig. 8 shows a specific flow, and fig. 8 is a schematic flow chart of the LRP protocol in this embodiment.

By adopting the scheme of the embodiment, before LRP, the LRP capability is executed through LLDP, and the discovery of the LRP transport layer capability can make the linkage between LRP protocols more effective, and avoid the situation that two ends cannot be compatible.

Example 4

Embodiments of the present invention also provide a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.

Alternatively, in the present embodiment, the storage medium may be configured to store a computer program for executing the steps of:

s1, setting a link layer discovery protocol message LLDPDU at a local terminal system, wherein the LLDPDU carries the capability information of the local terminal system;

and S2, sending the LLDPDU to a peer-to-peer system.

Optionally, in this embodiment, the storage medium may include, but is not limited to: various media capable of storing computer programs, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.

Embodiments of the present invention also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the above method embodiments.

Optionally, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.

Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:

s1, setting a link layer discovery protocol message LLDPDU in a local end system, wherein the LLDPDU carries the capability information of the local end system;

and S2, sending the LLDPDU to a peer-to-peer system.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A capability advertisement method, comprising:

an application program in a local end system initiates an information synchronization request to a port connected with the local end system and an opposite end system, establishes an LRP instance at the port, and triggers an LLDP protocol by the LRP instance;

setting a link layer discovery protocol message LLDPDU (link layer discovery protocol) in the local end system through the LLDP protocol, wherein the LLDPDU carries capability information of the local end system, the capability information includes a transmission mechanism of a link registration protocol LRP (link layer discovery protocol) supported by the local end system, and the transmission mechanism includes at least one of the following: an encryption control protocol ECP, a transmission control protocol TCP;

and sending the LLDPDU to a peer-to-peer system.

2. The method of claim 1, further comprising:

receiving the capability information of the opposite-end system;

and judging whether the capabilities of the opposite end system and the local end system are matched.

3. The method of claim 2, wherein after determining whether the capabilities of the peer system and the home system match, the method further comprises:

when the capabilities of the opposite end system and the local end system are matched, the opposite end system notifies the local end system of the LRP instance, and the matching detection of the upper layer application program is initiated.

4. The method of claim 3, wherein initiating match detection for an upper-level application comprises:

and the LRP example of the local end system sends information carrying the corresponding upper layer application program identifier to an opposite end system.

5. The method of claim 3, wherein after the LRP instance initiates match detection for an upper-level application, the method further comprises:

the LRP instance of the local end system judges whether the upper-layer application corresponding to the LRP instance of the opposite end system is matched with the upper-layer application program corresponding to the LRP instance of the local end system;

and when the application programs of the opposite end system and the local end system are matched, establishing LRP connection between the opposite end system and the local end system.

6. The method of claim 5, wherein the determining, by the LRP instance of the local system, whether the upper-layer application corresponding to the LRP instance of the peer system matches the upper-layer application corresponding to the LRP instance of the local system comprises:

the LRP example of the local terminal system receives a second message sent by the opposite terminal system through an LRP protocol, wherein the second message carries a second application identifier of the opposite terminal system;

and judging whether the upper-layer application programs corresponding to the LRP instances of the opposite-end system and the local-end system are matched or not by matching the first application identifier and the second application identifier of the local-end system.

7. The method of claim 2, wherein determining whether the capabilities of the peer system and the home system match comprises one of:

receiving an announcement message sent by the opposite-end system, wherein the announcement message is used for describing the capability of the opposite-end system; judging whether the capabilities of the opposite terminal system and the local terminal system are matched or not according to the notification message;

after the LLDPDU is sent to a peer system for a preset number of times, determining whether a notification message sent by the peer system is received, and judging that the capabilities of the peer system and the home system are not matched when the notification message is not received.

8. A capability advertisement device, comprising:

a creating module, configured to initiate an information synchronization request to a port where a home terminal system and an opposite terminal system are connected by an application program located in the home terminal system, establish an LRP instance at the port, and trigger an LLDP protocol by the LRP instance;

a setting module, configured to set, in the home terminal system, a link layer discovery protocol message LLDPDU according to the LLDP protocol, where the LLDPDU carries capability information of the home terminal system, the capability information includes a transmission mechanism of a link registration protocol LRP supported by the home terminal system, and the transmission mechanism includes at least one of: an encryption control protocol ECP, a transmission control protocol TCP;

and the sending module is used for sending the LLDPDU to a peer-to-peer system.

9. The apparatus of claim 8, further comprising:

a determining module, configured to determine whether an upper layer application corresponding to an LRP instance of the peer system matches an upper layer application corresponding to an LRP instance of the home system when the capabilities of the peer system and the home system match;

and the establishing module is used for establishing LRP connection between the opposite end system and the local end system when the applications of the opposite end system and the local end system are matched.

10. A capability notification system comprises a local end system and an opposite end system, and is characterized in that the local end system comprises: a first creating module, configured to initiate an information synchronization request to a port where a local system is connected to an opposite system by an application located in the local system, establish an LRP instance at the port, and trigger an LLDP protocol by the LRP instance; a first setting module, configured to set, in the home terminal system, a first link layer discovery protocol message LLDPDU according to the LLDP protocol, where the first LLDPDU carries capability information of the home terminal system, where the capability information includes a transmission mechanism of a link registration protocol LRP supported by the home terminal system, and the transmission mechanism includes at least one of: an encryption control protocol ECP, a transmission control protocol TCP; a first sending module, configured to send the first LLDPDU to the peer system;

the peer-to-peer system includes: a second setting module, configured to set a second LLDPDU in an opposite-end system, where the second LLDPDU carries capability information of the opposite-end system; and the second sending module is used for sending the second LLDPDU to the home system.

11. A storage medium, in which a computer program is stored, wherein the computer program is arranged to, when executed by a processor, perform the method of any one of claims 1 to 7.

12. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 1 to 7.