Capability negotiation method, device, system and storage medium

Abstract

The present application discloses a method, device, system and storage medium for capability negotiation, which belongs to the field of communications. The method comprises: a first network entity obtains a capability update message, the capability update message comprises capability update information, and the capability update information indicates at least one capability that the first network entity needs to update; the first network entity sends the capability update message to the second network entity based on the capability negotiation session that has been established between the first network entity and the second network entity. The present application can simplify the process of negotiating capabilities, improve the efficiency of negotiating capabilities, realize dynamic negotiation capabilities, and reduce the burden on PCC and PCE.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a capability negotiation method, device, system and storage medium. Background Art

[0002] A path calculation element (PCE) is an entity that calculates network paths or constrains routing based on network topology information. A path computation client (PCC) is an entity that sends a path request to a PCE, usually a service ingress node that requests the PCE to calculate a path. When requesting to calculate a path, the PCC needs to negotiate with the PCE on the capabilities it needs.

[0003] Currently, after negotiating capabilities, the PCC or PCE may need to increase or decrease the negotiated capabilities. In other words, if the capabilities required by the PCC or PCE change, the PCC and PCE need to renegotiate the changed capabilities. However, currently, when the PCC and PCE negotiate the changed capabilities, they need to go through a complex process to negotiate the changed capabilities, which not only has a low efficiency in negotiating capabilities, but also increases the burden on the PCC and PCE. Summary of the invention

[0004] The present application provides a method, device, system and storage medium for capability negotiation to simplify the process of capability negotiation, improve the efficiency of capability negotiation and reduce the burden on PCC and PCE. The technical solution is as follows:

[0005] In a first aspect, the present application provides a method for capability negotiation, in which a first network entity obtains a capability update message, the capability update message includes capability update information, and the capability update information indicates at least one capability that the first network entity needs to update. The first network entity sends a capability update message to the second network entity based on a capability negotiation session that has been established between the first network entity and the second network entity.

[0006] Since the first network entity sends a capability update message to the second network entity based on the capability negotiation session that has been established between the first network entity and the second network entity, that is, when the first network entity renegotiates the capability, it does not need to disconnect the capability negotiation session, nor does it need to re-establish the capability session with the second network entity. Instead, it directly uses the capability negotiation session that has been established between the first network entity and the second network entity to renegotiate the capability, thereby realizing dynamic capability negotiation. This simplifies the process of renegotiating the capability, which not only improves the efficiency of negotiating the capability, but also reduces the burden on the first network entity and the second network entity. The first network entity is a PCC and the second network entity is a PCE; or, the first network entity is a PCE and the second network entity is a PCC, which reduces the burden on the PCC and the PCE.

[0007] In a possible implementation, the at least one capability includes an updated capability of the first network entity, and the capability update information includes capability information of the updated capability. Since the capability update information includes capability information of the updated capability, the second network entity can negotiate the updated capability of the first network entity.

[0008] In another possible implementation, the at least one capability includes a capability added by the first network entity, and the capability update information includes capability information of the added capability. Since the capability update information includes capability information of the added capability, the second network entity can obtain the updated capability of the first network entity based on the capability update information and negotiate the updated capability of the first network entity.

[0009] In another possible implementation, the at least one capability includes a capability reduced by the first network entity, and the capability update information includes capability information of the reduced capability. Since the capability update information includes capability information of the reduced capability, the second network entity can obtain the updated capability of the first network entity based on the capability update information and negotiate the updated capability of the first network entity.

[0010] In another possible implementation, the first network entity establishes the capability negotiation session. The first network entity negotiates one or more capabilities with the second network entity based on the capability negotiation session. Before the capability of the first network entity is updated, the first network entity has established the capability negotiation session, so that after the capability of the first network entity is updated, the first network entity can directly use the capability negotiation session to renegotiate the capability, so as to simplify the process of renegotiating the capability, which not only improves the efficiency of negotiating the capability, but also reduces the burden on the first network entity and the second network entity.

[0011] In another possible implementation manner, the capability update message includes a Path Computation Element Communication Protocol Open (PCEP Open) message or a Path Computation Element Communication Protocol Notification (PCNtf) message.

[0012] In another possible implementation, when the capability update message includes a PCEP Open message, the PCEP Open message also includes a dynamic capability negotiation identifier, and the dynamic capability negotiation identifier is used to indicate the capability required for renegotiating the first network entity. Since the dynamic capability negotiation identifier is used to indicate the capability required for renegotiating the first network entity, the second network entity can determine that the first network entity needs to renegotiate the capability based on the dynamic capability negotiation identifier.

[0013] In another possible implementation, when the capability update message includes a PCNtf message, the payload of the PCNtf message includes the capability update information. Since the payload of the PCNtf message includes the capability update information, the second network entity can determine that the payload of the PCNtf message includes the capability update information, and further determine that the first network entity needs to renegotiate capabilities.

[0014] In another possible implementation, the capability negotiation session is a PCEP session.

[0015] In a second aspect, the present application provides a method for capability negotiation, in which a second network entity receives a capability update message sent by a first network entity based on a capability negotiation session established between the second network entity and the first network entity, the capability update message including capability update information, the capability update information indicating at least one capability that needs to be updated by the first network entity. The second network entity updates the capability that takes effect on the second network entity based on the at least one capability.

[0016] Since the first network entity receives the capability update message sent by the first network entity based on the capability negotiation session established between the second network entity and the first network entity, that is, when renegotiating the capability with the first network entity, there is no need to disconnect the capability negotiation session, nor to re-establish the capability session with the first network entity, but directly use the capability negotiation session established between the first network entity and the second network entity to renegotiate the capability, thereby realizing dynamic capability negotiation. This simplifies the process of renegotiating the capability, which not only improves the efficiency of negotiating the capability, but also reduces the burden on the first network entity and the second network entity. The first network entity is a PCC and the second network entity is a PCE; or, the first network entity is a PCE and the second network entity is a PCC, which reduces the burden on the PCC and the PCE.

[0017] In a possible implementation, the at least one capability includes an updated capability of the first network entity, and the capability update information includes capability information of the updated capability. Since the capability update information includes capability information of the updated capability, the second network entity can negotiate the updated capability of the first network entity.

[0018] In another possible implementation, the at least one capability includes a capability added by the first network entity, and the capability update information includes capability information of the added capability. Since the capability update information includes capability information of the added capability, the second network entity obtains the updated capability of the first network entity based on the capability update information, thereby achieving negotiation of the updated capability of the first network entity.

[0019] In another possible implementation, the at least one capability includes a capability reduced by the first network entity, and the capability update information includes capability information of the reduced capability. Since the capability update information includes capability information of the reduced capability, the second network entity can obtain the updated capability of the first network entity based on the capability update information, thereby achieving negotiation of the updated capability of the first network entity.

[0020] In another possible implementation, the second network entity establishes the capability negotiation session. The second network entity negotiates one or more capabilities with the first network entity based on the capability negotiation session, and the effective capabilities include capabilities successfully negotiated by the second network entity. Before the capabilities of the first network entity are updated, the second network entity has established the capability negotiation session, so that after the capabilities of the first network entity are updated, the second network entity can directly use the capability negotiation session to renegotiate the capabilities, so as to simplify the process of renegotiating the capabilities, which not only improves the efficiency of negotiating the capabilities, but also reduces the burden on the first network entity and the second network entity.

[0021] In another possible implementation manner, the capability update message includes a Path Computation Element Communication Protocol Open (PCEP Open) message or a Path Computation Element Communication Protocol Notification (PCNtf) message.

[0022] In another possible implementation, when the capability update message includes a PCEP Open message, the PCEP Open message also includes a dynamic capability negotiation identifier, and the dynamic capability negotiation identifier is used to indicate the capability required for renegotiating the first network entity. Since the dynamic capability negotiation identifier is used to indicate the capability required for renegotiating the first network entity, the second network entity can determine that the first network entity needs to renegotiate the capability based on the dynamic capability negotiation identifier.

[0023] In another possible implementation, the second network entity updates the effective capability of the second network entity based on the at least one capability under the triggering of the dynamic capability negotiation identifier. Thus, the second network entity can determine that it needs to renegotiate capabilities with the first network entity based on the dynamic capability negotiation identifier.

[0024] In another possible implementation, when the capability update message includes a PCNtf message, the payload of the PCNtf message includes the capability update information. Since the payload of the PCNtf message includes the capability update information, the second network entity determines that the payload of the PCNtf message includes the capability update information, and further determines that the first network entity needs to renegotiate capabilities.

[0025] In another possible implementation, the capability negotiation session is a PCEP session.

[0026] In a third aspect, the present application provides a device for capability negotiation, configured to execute a method performed by a first network entity in the first aspect or any possible implementation of the first aspect. Specifically, the device includes a unit configured to execute a method performed by a first network entity in the first aspect or any possible implementation of the first aspect.

[0027] In a fourth aspect, the present application provides a device for capability negotiation, configured to execute a method performed by a second network entity in the second aspect or any possible implementation of the second aspect. Specifically, the device includes a unit configured to execute a method performed by a second network entity in the second aspect or any possible implementation of the second aspect.

[0028] In a fifth aspect, the present application provides a device for capability negotiation, the device comprising a transceiver, a processor, and a memory. The transceiver, the processor, and the memory may be connected via an internal connection. The memory is used to store a program, and the processor is used to execute the program in the memory and cooperate with the transceiver, so that the device completes the method performed by the first network entity in the first aspect or any possible implementation of the first aspect.

[0029] In a sixth aspect, the present application provides a device for capability negotiation, the device comprising a transceiver, a processor, and a memory. The transceiver, the processor, and the memory may be connected via an internal connection. The memory is used to store a program, and the processor is used to execute the program in the memory and cooperate with the transceiver, so that the device completes the method performed by the second network entity in the second aspect or any possible implementation of the second aspect.

[0030] In the seventh aspect, the present application provides a computer program product, which includes a computer program stored in a computer-readable storage medium, and the computer program is loaded by a processor to implement the above-mentioned first aspect, second aspect, any possible implementation of the first aspect, or any possible implementation of the second aspect.

[0031] In an eighth aspect, the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program is loaded by a processor to execute the method of the above-mentioned first aspect, the second aspect, any possible implementation of the first aspect, or any possible implementation of the second aspect.

[0032] In a ninth aspect, the present application provides a capability negotiation system, the system comprising the apparatus described in the third aspect and the apparatus described in the fourth aspect, or the system comprising the apparatus described in the fifth aspect and the apparatus described in the sixth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 This is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0034] Figure 2 It is a flow chart of a method for negotiating capability and maintaining capability negotiation session provided in an embodiment of the present application;

[0035] Figure 3 This is a flow chart of a capability negotiation method provided by an embodiment of the present application;

[0036] Figure 4 is a schematic diagram of capability update information provided by an embodiment of the present application;

[0037] Figure 5 It is a schematic diagram of the structure of a PCEP Open message provided in an embodiment of the present application;

[0038] Figure 6 It is a structural diagram of a PCNtf message provided in an embodiment of the present application;

[0039] Figure 7 is a schematic diagram of a device structure for capability negotiation provided in an embodiment of the present application;

[0040] Figure 8 is a schematic diagram of another device structure for capability negotiation provided in an embodiment of the present application;

[0041] Fig. 9 is a schematic diagram of another device structure for capability negotiation provided in an embodiment of the present application;

[0042] Fig.10is a schematic diagram of another device structure for capability negotiation provided in an embodiment of the present application;

[0043] Fig.11 It is a schematic diagram of the system structure of a capability negotiation provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] The implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0045] See also Figure 1 , the embodiment of the present application provides a network architecture, which includes a PCE and at least one PCC (for example, in Figure 1 In the network architecture shown, the at least one PCC includes PCC1 and PCC2). For each PCC, the PCC can communicate with the PCE.

[0046] The PCC and the PCE may perform service interaction. For example, if the service is a path service, the PCC may request the PCE to establish a path, or the PCE may actively establish a path for the PCC and send path information of the path to the PCC.

[0047] The established path is a path between the PCC and a certain device. Figure 1 For example, assume that PCC1 requests PCE to establish a path, where the path is between PCC1 and PCC2, and the devices on the path include PCC1, network device 1, network device 2, and PCC2.

[0048] In addition to the above-mentioned path services, the services exchanged between the PCC and the PCE may include other services, which will not be listed one by one.

[0049] The PCC may be a network device or a client or application running on the network device. The PCE may be a network device, a server, a controller or a client or application running on the network device, a server or a controller. The network device includes a switch, a router, a gateway or a base station.

[0050] The PCC supports at least one capability, and the PCE also supports at least one capability. The at least one capability may include segment routing internet protocol version 6 (SRv6) capability, segment routing traffic engineering (SR-TE) capability, PCE create label forwarding path (pce initiate label switched path, PCE Initiate-LSP) capability and / or segment routing policy (segment routing policy, SR Policy) capability, etc.

[0051] Before the PCC and the PCE perform service interaction, the PCC may negotiate capabilities with the PCE. The process of the PCC and the PCE negotiating capabilities includes the following operations (11) to (13):

[0052] (11): The PCC establishes a network connection with the PCE.

[0053] The network connection between the PCC and the PCE may be a transmission control protocol (TCP) connection, that is, the PCC may establish a TCP connection with the PCE through a TCP three-way handshake mechanism.

[0054] (12): The PCC establishes a capability negotiation session with the PCE.

[0055] The capability negotiation session may be a path computation element communication protocol (PCEP) session.

[0056] (13): The PCC negotiates one or more capabilities with the PCE based on the capability negotiation session.

[0057] See also Figure 2 In step (13), the PCC sends a first capability negotiation message to the PCE based on the capability negotiation session, the first capability negotiation message includes capability information of at least one capability to be negotiated, and the at least one capability is a capability supported by the PCC. The PCE receives the first capability negotiation message, obtains the at least one capability based on the capability information included in the first capability negotiation message, and determines a capability supported by itself from the at least one capability, the determined capability being a capability supported by both the PCC and the PCE. The PCE sets the capability of the capability negotiation session on the PCE side to the determined capability.

[0058] The PCE also sends a second capability negotiation message to the PCC based on the capability negotiation session, the second capability negotiation message including capability information of at least one capability to be negotiated, the at least one capability being a capability supported by the PCE. The PCC receives the second capability negotiation message, obtains the at least one capability based on the capability information included in the second capability negotiation message, and determines a capability supported by itself from the at least one capability, the determined capability being a capability supported by both the PCC and the PCE. The PCC sets the capability of the capability negotiation session on the PCC side to the determined capability.

[0059] For example, it is assumed that the capabilities supported by the PCC include SRv6 capabilities and SR-TE capabilities, and the capabilities supported by the PCE include SRv6 capabilities, SR-TE capabilities, and SR Policy capabilities. The PCC sends a first capability negotiation message to the PCE based on the capability negotiation session, and the first capability negotiation message includes capability information of the SRv6 capability and capability information of the SR-TE capability. The PCE receives the first capability negotiation message, determines based on the capability information included in the first capability negotiation message that both the PCC and the PCE support SRv6 capabilities and SR-TE capabilities, and sets the capabilities of the capability negotiation session on the PCE side to SRv6 capabilities and SR-TE capabilities.

[0060] The PCE also sends a second capability negotiation message to the PCC based on the capability negotiation session, and the second capability negotiation message includes capability information of the SRv6 capability, capability information of the SR-TE capability, and capability information of the SR Policy capability. The PCC receives the second capability negotiation message, determines based on the capability information included in the second capability negotiation message that both the PCC and the PCE support the SRv6 capability and the SR-TE capability, and sets the capability of the capability negotiation session on the PCC side to the SRv6 capability and the SR-TE capability.

[0061] Since the first capability negotiation message sent by the PCC to the PCE includes capability information of capabilities supported by the PCC, the PCE can record the capabilities supported by the PCC. Also, since the second capability negotiation message sent by the PCE to the PCC includes capability information of capabilities supported by the PCE, the PCC also records the capabilities supported by the PCE.

[0062] After negotiating the capability, the PCC can interact with the PCE based on the capability negotiation session. For example, still taking the path service as an example, the PCC can request the PCE to establish a path based on the capability negotiation session, and the path corresponds to a capability. If the capability corresponding to the path is the capability of the capability negotiation session on the PCE side, the PCE establishes the path for the PCC; if the capability corresponding to the path is not the capability of the capability negotiation session on the PCE side, the PCE refuses to establish the path for the PCC.

[0063] or,

[0064] The PCE establishes a path for the PCC and sends the path information of the path to the PCC based on the capability negotiation session. If the capability corresponding to the path is the capability of the capability negotiation session on the PCC side, the PCC receives the path information of the path; if the capability corresponding to the path is not the capability of the capability negotiation session on the PCC side, the PCC refuses to receive the path information of the path.

[0065] See also Figure 2 After the capability negotiation is completed, the PCC and the PCE need to maintain the capability negotiation session. The PCC sends a session maintenance message to the PCE regularly or irregularly, and the PCE sends a session maintenance message to the PCC regularly or irregularly, so that the PCC and the PCE maintain the capability negotiation session by sending the session maintenance messages to each other, so that the capability negotiation session always exists between the PCC and the PCE.

[0066] The session maintenance message may be a heartbeat message. For example, the session maintenance message may be a path computation element communication protocol keepalive (PECPKeepalive) message or other messages. The first capability negotiation message or the second capability negotiation message may be an open message defined by PCEP or other messages.

[0067] It should be noted that after the PCC and the PCE have negotiated the capabilities, the capabilities supported by the PCC or the capabilities supported by the PCE may be updated. The PCC may add new capabilities or reduce supported capabilities, and at this time the PCC needs to negotiate with the PCE the capabilities that the PCC needs to update. Alternatively, the PCE adds new capabilities or reduces supported capabilities, and at this time the PCE needs to negotiate with the PCC the capabilities that the PCE needs to update. The PCC or the PCE may negotiate the capabilities that need to be updated through any of the following embodiments.

[0068] See also Figure 3 The present application embodiment provides a capability negotiation method, which can be applied to Figure 1 In the network architecture shown, when the capability of the PCC is updated or the capability of the PCE is updated, the PCC or the PCE negotiates the capability to be updated through the method, including:

[0069] Operation 301: A first network entity obtains a capability update message, where the capability update message includes capability update information, and the capability update information indicates at least one capability that needs to be updated by the first network entity.

[0070] The first network entity is the PCC or PCE mentioned above, and the capabilities supported by the first network entity may be updated. For example, the first network entity may increase capabilities that need to be supported or reduce supported capabilities.

[0071] The at least one capability that needs to be updated for the first network entity includes the increased capability or the reduced capability, or the at least one capability that needs to be updated for the first network entity includes the updated capability of the first network entity.

[0072] Next, a specific example is given to illustrate that the capabilities supported by the first network entity include SRv6 capabilities and SR-TE capabilities. It is assumed that the capabilities supported by the first network entity are updated. The update includes adding capabilities that need to be supported or reducing supported capabilities. Next, two examples are given to illustrate the two update situations respectively.

[0073] In the first example, the first network entity adds a capability that needs to be supported. Assuming that the capability added by the first network entity is the SR Policy capability, the updated capability of the first network entity includes the SRv6 capability, the SR-TE capability, and the SR Policy capability. Therefore, at least one capability that needs to be updated by the first network entity includes the added SR Policy capability, or at least one capability that needs to be updated by the first network entity includes the updated capability of the first network entity, that is, including the SRv6 capability, the SR-TE capability, and the SR Policy capability.

[0074] In the second example, the first network entity reduces the supported capabilities. Assuming that the reduced capabilities of the first network entity are SRv6 capabilities, the updated capabilities of the first network entity include SR-TE capabilities. Therefore, at least one capability that needs to be updated by the first network entity includes the reduced SRv6 capability, or at least one capability that needs to be updated by the first network entity includes the updated capabilities of the first network entity, that is, includes SR-TE capabilities.

[0075] For the above capability update message, the payload of the capability update message includes capability update information.

[0076] The payload of the capability update message may include a type length value (TLV) field, and the TLV field includes the capability update information.

[0077] The TLV field includes a Type field, a Length field, and a Value field, and the Value field includes the capability update information.

[0078] The capability update information may indicate at least one capability that needs to be updated for the first network entity in the following two ways.

[0079] In a first manner, the capability update information includes capability information of each capability of the at least one capability.

[0080] For each capability of the at least one capability that needs to be updated by the first network entity, the capability information of the capability may include content such as a capability identifier of the capability.

[0081] In the case where the at least one capability includes the added capability, the capability update information includes capability information of the added capability. For example, for the first example listed above, the first network entity adds an SR Policy capability, and the capability update information includes capability information of the added SR Policy capability.

[0082] In the case where the at least one capability includes the reduced capability, the capability update information includes capability information of the reduced capability. For example, for the second example listed above, the first network entity reduces the SRv6 capability, and the capability update information includes capability information of the reduced SRv6 capability.

[0083] In the case where the at least one capability includes the updated capability, the capability update information includes capability information of the updated capability. For example, for the first example listed above, the updated capability of the first network entity includes SRv6 capability, SR-TE capability, and SR Policy capability, and the capability update information includes capability information of SRv6 capability, capability information of SR-TE capability, and capability information of SR Policy capability. For another example, for the second example listed above, the updated capability of the first network entity includes SR-TE capability, and the capability update information includes capability information of SR-TE capability.

[0084] In the second method, the capability update information is a field in the payload of the capability update message, different bits in the field correspond to different capabilities, the value of the bit corresponding to each capability of the at least one capability in the field is a first specified value, and the values ​​of other bits in the field are second specified values.

[0085] For example, Figure 4 The field shown is a field in the payload of the capability update message, and the field includes three bits, including the first bit, the second bit and the third bit. The first bit, the second bit and the third bit correspond to the SRv6 capability, the SR-TE capability and the SR Policy capability, respectively. Assuming that the first specified value is 1 and the second specified value is 0, the capability update information is the field, and the value of the bit corresponding to each capability in the at least one capability in the field is the first specified value 1, and the value of the other bits is the second specified value 0.

[0086] In the case where the at least one capability includes the added capability, the value of the bit corresponding to the added capability in the capability update information is the first specified value, and the values ​​of the other bits are the second specified values. For example, for the first example listed above, the first network entity adds the SR Policy capability, and the value of the third bit corresponding to the added SR Policy capability in the capability update information is the first specified value 1, and the values ​​of the first bit and the second bit are both the second specified value 0. The capability update information is as follows: Figure 4 As shown in Figure (a).

[0087] In the case where the at least one capability includes the reduced capability, the value of the bit corresponding to the reduced capability in the capability update information is the first specified value, and the values ​​of the other bits are the second specified values. For example, for the second example listed above, the first network entity reduces the SRv6 capability, and the value of the first bit corresponding to the reduced SRv6 capability in the capability update information is 1, and the values ​​of the second bit and the third bit are both the second specified value 0. The capability update information is as follows: Figure 4 As shown in Figure (b).

[0088] In the case where the at least one capability includes the updated capability, the value of the bit corresponding to each capability after the update in the capability update information is the first specified value, and the values ​​of the other bits are the second specified values. For example, for the first example listed above, the updated capabilities of the first network entity include SRv6 capability, SR-TE capability, and SR Policy capability. In the capability update information, the value of the first bit corresponding to the SRv6 capability, the value of the second bit corresponding to the SR-TE capability, and the value of the third bit corresponding to the SRPolicy capability are all the first specified value 1, such as Figure 4 As another example, for the second example listed above, the updated capability of the first network entity includes the SR-TE capability. In the capability update information, the value of the second characteristic corresponding to the SR-TE capability is the first specified value 1, and the value of the first bit and the value of the third bit are both the second specified value 0, such as Figure 4 As shown in Figure (d).

[0089] In the case where the at least one capability includes an increased capability or a decreased capability, the capability update message may further include indication information, where the indication information is used to indicate the capability update status of the first network entity, that is, the indication information is used to indicate whether the capability update status of the first network entity is to increase capability or decrease capability.

[0090] The capability update message includes a PCEP Open message or a path computation element communication protocol notification (path computation element communication protocol notification, PCNtf) message, etc.

[0091] Among them, the capability update message may be other messages besides the PCEP Open message or PCNtf message listed above, which are not listed here one by one.

[0092] In the case where the capability update message includes a PCEP Open message, the PCEP Open message further includes a dynamic capability negotiation identifier, where the dynamic capability negotiation identifier is used to indicate the capability required for renegotiating the first network entity.

[0093] See also Figure 5 The PCEP Open message includes version (Ver), flags, keepalive, dead timer (DeadTimer), segment identify (SID) and optional TLV.

[0094] The dynamic capability negotiation identifier may be included using a subfield in Flags, where the length of the subfield is one or more bits. For example, see Figure 5 In Flags, a subfield D is defined, and the subfield D is used to include the dynamic capability negotiation identifier. Also, an optional TLV may be used to include the capability update information.

[0095] In case the at least one capability includes an increased capability or a decreased capability, the indication information may also be included using an optional TLV.

[0096] The PCEP Open message is different from the Open message defined by PCEP in that: the PCEP Open message includes a dynamic capability negotiation identifier, indicating that the PCEP Open message is a capability update message for renegotiating capabilities.

[0097] In the case where the capability update message includes a PCNtf message, the payload of the PCNtf message includes the capability update information.

[0098] See also Figure 6 ,The PCNtf message includes Reserved, Flags, notification type (NT), notification value (NV) and capability TLV.

[0099] The capability update information may be included using the capability TLV.

[0100] In the case where the at least one capability includes an increased capability or a decreased capability, the indication information may also be included using a capability TLV.

[0101] The PCNtf message is different from the Notification message defined by PCEP in that the payload of the PCNtf message adds a capability TLV, including the capability update information, indicating that the PCEP Open message is a capability update message for renegotiating capabilities.

[0102] Operation 302: The first network entity sends the capability update message to the second network entity based on the capability negotiation session established between the first network entity and the second network entity.

[0103] When the first network entity is the PCC, the second network entity is the PCE; or, when the first network entity is the PCE, the second network entity is the PCC.

[0104] The capability negotiation session may be a session used by the first network entity and the second network entity for the last capability negotiation. The capability negotiation session may be a session established when the first network entity and the second network entity negotiate capabilities for the first time.

[0105] See also Figure 2 The first network entity and the second network entity establish a capability negotiation session when negotiating capabilities for the first time. After that, the first network entity and the second network entity send session maintenance messages to each other regularly or irregularly, and maintain the capability negotiation session through the session maintenance messages sent to each other.

[0106] Therefore, when the capability of the first network entity is updated, the first network entity can directly send the capability update message to the second network entity based on the capability negotiation session, thereby simplifying the process of renegotiating the capability, improving the efficiency of renegotiating the capability, and reducing the burden between the first network entity and the second network entity.

[0107] Since the first network entity has recorded the capabilities supported by the second network entity, after the first network entity updates its capabilities, the first network entity determines the capabilities supported by both the first network entity and the second network entity from the recorded capabilities supported by the second network entity, and updates the capabilities of the capability negotiation session on the first network entity side to the determined capabilities.

[0108] The operation of the first network entity determining capabilities supported by both the first network entity and the second network entity may include: the first network entity takes the intersection of the recorded capabilities supported by the second network entity and the updated capabilities of the first network entity, where the capabilities included in the intersection are capabilities supported by both the first network entity and the second network entity.

[0109] For example, it is assumed that the capabilities supported by the second network entity include SRv6 capability, SR-TE capability, and SR Policy capability. For the first example listed above, the updated capabilities of the first network entity include SRv6 capability, SR-TE capability, and SRPolicy capability. The first network entity determines that the capabilities supported by both the first network entity and the second network entity include SRv6 capability, SR-TE capability, and SR Policy capability. The capabilities of the capability negotiation session on the first network entity side are updated to SRv6 capability, SR-TE capability, and SR Policy capability.

[0110] For the second example listed above, the updated capability of the first network entity includes SR-TE capability. The first network entity determines that the capabilities supported by both the first network entity and the second network entity include SR-TE capability. The capability of the capability negotiation session on the first network entity side is updated to SR-TE capability.

[0111] Operation 303: The second network entity receives the capability update message, wherein the capability update message includes capability update information indicating at least one capability, and based on the at least one capability, updates the capabilities that take effect on the second network entity.

[0112] In the case where the capability update message is a PCEP Open message, the second network entity updates the effective capability of the second network entity based on the at least one capability under the triggering of the dynamic capability negotiation identifier included in the PCEP Open message.

[0113] In the case where the capability update message is a PCNtf message, when the second network entity detects that the payload of the PCNtf message includes capability update information, it determines that the capability supported by the first network entity is updated, and based on the at least one capability, updates the capability that takes effect on the second network entity.

[0114] The second network entity may update the effective capability through the following operations 3031 to 3033, where the effective capability includes the capability of the capability negotiation session on the second network entity side. The operations 3031 to 3033 specifically include the following contents:

[0115] 3031: The second network device obtains each updated capability of the first network entity based on the capability update information in the capability update message.

[0116] The at least one capability indicated by the capability update information may be an added capability or a reduced capability of the first network entity, or the at least one capability indicated by the capability update information may be an updated capability of the first network entity.

[0117] In the case where at least one capability indicated by the capability update information is a capability added or reduced by the first network entity, the second network entity records the capabilities supported by the first network entity when the second network entity negotiates capabilities with the first network entity last time. The second network entity may obtain each capability updated by the first network entity through the following operations (1) to (3).

[0118] (1): The second network entity determines the at least one capability indicated by the capability update information.

[0119] The second network entity may determine the at least one capability by using the following method 1 and method 2. The method 1 and method 2 are respectively:

[0120] Mode 1: The capability update information includes capability information of capabilities added or capabilities reduced by the first network entity, and the second network entity determines that the at least one capability includes a capability corresponding to each capability information in the capability update information.

[0121] For example, in the first example above, the capability update information includes capability information of an added SR Policy capability, and the second network entity determines that the at least one capability includes an SR Policy capability. For another example, in the second example above, the capability update information includes capability information of a reduced SRv6 capability, and the second network entity determines that the at least one capability includes an SRv6 capability.

[0122] Mode 2: The capability update information is a field in the capability update message, and the second network entity obtains a bit in the field whose bit value is a first specified value, and determines that the at least one capability includes the capability corresponding to the obtained bit.

[0123] For example, in the first example above, the capability update information is as follows: Figure 4 , the second network entity obtains the third bit of the field whose bit value is the first specified value 1, and determines that the at least one capability includes the SR Policy capability corresponding to the third bit. For another example, in the above second example, the capability update information is as follows: Figure 4 The field shown in Figure (b) in the figure, the second network entity obtains the first bit in the field whose bit value is the first specified value 1, and determines that the at least one capability includes the SRv6 capability corresponding to the first bit.

[0124] (2): When the second network entity determines that the first network entity has added capabilities, the second network entity obtains updated capabilities of the first network entity including the capabilities recorded by the second network entity and the at least one capability.

[0125] In the case that the capabilities recorded by the second network entity do not include the at least one capability, it indicates that the at least one capability is a capability added by the first network entity, thereby determining that the first network entity adds the capability.

[0126] The capability update message includes indication information, and when the indication information is used to indicate that the first network entity adds a capability, it is determined that the first network entity adds a capability.

[0127] (3): When the second network entity determines that the first network entity has reduced capabilities, the second network entity removes the at least one capability from the capabilities recorded by the second network entity, and the remaining capabilities are the updated capabilities of the first network entity.

[0128] In the case that the capabilities recorded by the second network entity include the at least one capability, it indicates that the at least one capability is a capability reduced by the first network entity, thereby determining that the capability of the first network entity is reduced.

[0129] When the capability update message includes indication information, and when the indication information is used to indicate that the first network entity reduces the capability, it is determined that the first network entity reduces the capability.

[0130] In the case that at least one capability indicated by the capability update information is an updated capability of the first network entity, the second network entity may obtain the updated capability of the first network entity according to the following method 1 and method 2.

[0131] In a first approach, the capability update information includes capability information of updated capabilities of the first network entity. Then, based on the capability update information, the updated capabilities of the first network entity are acquired, and the acquired capabilities include capabilities corresponding to the capability information in the capability update information.

[0132] For example, in the first example above, the capability update information includes the capability information of the SRv6 capability, the capability information of the SR-TE capability, and the capability information of the SR Policy capability after the first network entity is updated, and the second network entity obtains the updated capability of the first network entity including the SRv6 capability, the SR-TE capability, and the SR Policy capability. For another example, in the second example above, the capability update information includes the capability information of the SR-TE capability after the first network entity is updated, and the second network entity obtains the updated capability of the first network entity including the SR-TE capability.

[0133] In method 2, the capability update information is a field in the capability update message, and the second network entity obtains a bit whose bit value in the field is a first specified value, and obtains the updated capability of the first network entity including the capability corresponding to the obtained bit.

[0134] For example, in the first example above, the capability update information is as follows: Figure 4 , the second network entity obtains the first bit, the second bit, and the third bit of the field whose bit values ​​are the first specified value 1, and obtains the updated capabilities of the first network entity, including the SRv6 capability corresponding to the first bit, the SR-TE capability corresponding to the second bit, and the SR Policy capability corresponding to the third bit. For another example, in the second example above, the capability update information is as follows: Figure 4 The field shown in Figure (d) in the figure, the second network entity obtains the second bit in the field whose bit value is the first specified value 1, and obtains the updated capability of the first network entity including the SR-TE capability corresponding to the second bit.

[0135] After acquiring the updated capabilities of the first network entity, the second network entity replaces the recorded capabilities supported by the first network entity with the updated capabilities of the first network entity.

[0136] 3032: The second network device determines capabilities supported by the second network entity from the updated capabilities of the first network entity, where the determined capabilities are capabilities supported by both the first network entity and the second network entity.

[0137] In 3032, the second network entity takes the intersection of the updated capabilities of the first network entity and the capabilities supported by the second network entity to obtain capabilities supported by both the first network entity and the second network entity.

[0138] For example, in the above-mentioned first entity, the updated capabilities of the first network entity include SRv6 capability, SR-TE capability and SRPolicy capability; and the capabilities supported by the second network entity include SRv6 capability, SR-TE capability and SRPolicy capability, so the capabilities supported by both the first network entity and the second network entity include SRv6 capability, SR-TE capability and SRPolicy capability.

[0139] For another example, in the above-mentioned second entity, the updated capabilities of the first network entity include R-TE capabilities; and the capabilities supported by the second network entity include SRv6 capabilities, SR-TE capabilities and SRPolicy capabilities, so the capabilities supported by both the first network entity and the second network entity include SR-TE capabilities.

[0140] 3033: The second network entity updates the capability of the capability negotiation session on the second network entity side to the determined capability.

[0141] For example, in the above-mentioned first entity, the capabilities supported by both the first network entity and the second network entity include SRv6 capability, SR-TE capability and SRPolicy capability, so the capabilities of the capability negotiation session on the second network entity side are updated to SRv6 capability, SR-TE capability and SRPolicy capability.

[0142] For another example, in the above-mentioned second entity, the capabilities supported by both the first network entity and the second network entity include SR-TE capabilities, so the capabilities of the capability negotiation session on the second network entity side are updated to SRv6 capabilities, SR-TE capabilities and SR-TE capabilities.

[0143] The first network entity is a PCC, and the second network entity is a PCE, that is, when the PCC capability is updated, the PCC renegotiates the capability with the PCE through the operations of 301 to 303. Alternatively, the first network entity is a PCE, and the second network entity is a PCC, that is, when the PCE capability is updated, the PCE renegotiates the capability with the PCC through the operations of 301 to 303.

[0144] After the renegotiation of the capabilities, the PCC and PCE interact with each other. For example, taking the path service as an example, the PCC requests the PCE to establish a path based on the capability negotiation session. If the capability corresponding to the path is the capability of the capability negotiation session on the PCE side, the PCE establishes the path for the PCC; if the capability corresponding to the path is not the capability of the capability negotiation session on the PCE side, the PCE refuses to establish the path for the PCC. Or,

[0145] The PCE establishes a path for the PCC and sends the path information of the path to the PCC based on the capability negotiation session. If the capability corresponding to the path is the capability of the capability negotiation session on the PCC side, the PCC receives the path information of the path; if the capability corresponding to the path is not the capability of the capability negotiation session on the PCC side, the PCC refuses to receive the path information of the path.

[0146] In an embodiment of the present application, when the capability of the first network entity is updated, the first network entity sends a capability update message to the second network entity based on the capability negotiation session established between the first network entity and the second network entity, and the capability update message includes capability update information, and the capability update information indicates at least one capability that the first network entity needs to update. In this way, the second network entity updates the capability of the capability negotiation session on the second network entity side based on the at least one capability. Since the established capability negotiation session is the session used by the first network entity and the second network entity when negotiating the capability last time, and the first network entity and the second network entity maintain the capability negotiation session and do not disconnect it, when renegotiating the capability, the first network entity can directly use the established capability negotiation session to achieve dynamic capability negotiation. Therefore, when renegotiating the capability, there is no need to release the capability negotiation session or re-establish the capability negotiation session, which simplifies the process of renegotiating the capability, improves the efficiency of negotiating the capability, and reduces the burden between the first network entity and the second network entity. In addition, since dynamic capability negotiation is implemented between the first network entity and the second network entity, it is convenient for the network to upgrade new features and reduce the impact on existing services.

[0147] See also Figure 7 The embodiment of the present application provides a device 700 for capability negotiation, which can be deployed in the above Figure 3 The first network entity provided in the illustrated embodiment includes:

[0148] The processing unit 701 is configured to obtain a capability update message, where the capability update message includes capability update information, where the capability update information indicates at least one capability that needs to be updated by the device 700;

[0149] The sending unit 702 is configured to send the capability update message to the second network entity based on the capability negotiation session that has been established between the apparatus 700 and the second network entity.

[0150] The detailed implementation process of the processing unit 701 obtaining the capability update message can be found in Figure 3 The relevant contents in operation 301 in the illustrated embodiment will not be described in detail here.

[0151] In some embodiments, the at least one capability may include an updated capability of the apparatus 700, and the capability update information includes capability information of the updated capability.

[0152] In some embodiments, the at least one capability may include a capability added by the apparatus 700, and the capability update information includes capability information of the added capability.

[0153] In some embodiments, the at least one capability may include a reduced capability of the apparatus 700, and the capability update information includes capability information of the reduced capability.

[0154] The processing unit 701 may also be used for:

[0155] Establishing the capability negotiation session;

[0156] One or more capabilities are negotiated with the second network entity based on the capability negotiation session.

[0157] For details on the process of the processing unit 701 establishing the capability negotiation session and negotiating the capability, please refer to Figure 1 The relevant contents in the illustrated embodiment will not be described in detail here.

[0158] The capability update message may include a Path Computation Element Communication Protocol Open (PCEP Open) message or a Path Computation Element Communication Protocol Notification (PCNtf) message.

[0159] In the case where the capability update message includes a PCEP Open message, the PCEP Open message may further include a dynamic capability negotiation identifier, where the dynamic capability negotiation identifier is used to indicate the capability required for the apparatus 700 to be renegotiated.

[0160] In the case where the capability update message includes a PCNtf message, the payload of the PCNtf message may include the capability update information.

[0161] The capability negotiation session may be a PCEP session.

[0162] In the embodiment of the present application, since the sending unit can send a capability update message to the second network entity based on the capability negotiation session that has been established between the first network entity and the second network entity, that is, when the device renegotiates the capability, it is not necessary to disconnect the capability negotiation session, nor to re-establish the capability session with the second network entity, but directly use the capability negotiation session that has been established between the device and the second network entity to renegotiate the capability, thereby realizing dynamic capability negotiation. This simplifies the process of renegotiating the capability, improves the efficiency of negotiating the capability, and reduces the burden on the device and the second network entity.

[0163] See also Figure 8 The embodiment of the present application provides a device 800 for capability negotiation, which can be deployed in the above Figure 3 The second network entity provided in the illustrated embodiment includes:

[0164] A receiving unit 801 is configured to receive a capability update message sent by the first network entity based on a capability negotiation session established between the apparatus 800 and the first network entity, where the capability update message includes capability update information, where the capability update information indicates at least one capability that needs to be updated by the first network entity;

[0165] The processing unit 802 is configured to update the effective capability of the device 800 based on the at least one capability.

[0166] The detailed implementation process of the processing unit 802 updating the effective capability of the device 800 can be found in Figure 3 The relevant contents in operation 302 in the illustrated embodiment will not be described in detail here.

[0167] In some embodiments, the at least one capability may include an updated capability of the first network entity, and the capability update information includes capability information of the updated capability.

[0168] In some embodiments, the at least one capability may include a capability added by the first network entity, and the capability update information includes capability information of the added capability.

[0169] In some embodiments, the at least one capability may include a reduced capability of the first network entity, and the capability update information includes capability information of the reduced capability.

[0170] The processing unit 802 may also be used for:

[0171] Establishing the capability negotiation session;

[0172] One or more capabilities are negotiated with the first network entity based on the capability negotiation session, and the effective capabilities include the capabilities successfully negotiated by the apparatus 800.

[0173] The detailed implementation process of the processing unit 802 establishing the capability negotiation session and negotiating the capability can be found in Figure 1 The relevant contents in the illustrated embodiment will not be described in detail here.

[0174] The capability update message may include a Path Computation Element Communication Protocol Open (PCEP Open) message or a Path Computation Element Communication Protocol Notification (PCNtf) message.

[0175] In the case where the capability update message includes a PCEP Open message, the PCEP Open message may further include a dynamic capability negotiation identifier, where the dynamic capability negotiation identifier is used to indicate the capability required for renegotiating the first network entity.

[0176] The processing unit 802 may be configured to:

[0177] Under the triggering of the dynamic capability negotiation identifier, based on the at least one capability, the effective capabilities of the apparatus 800 are updated.

[0178] In the case where the capability update message includes a PCNtf message, the payload of the PCNtf message may include the capability update information.

[0179] The capability negotiation session may be a PCEP session.

[0180] In the embodiment of the present application, since the receiving unit receives the capability update message sent by the first network entity based on the capability negotiation session established between the second network entity and the first network entity, that is, when renegotiating the capability with the first network entity, it is not necessary to disconnect the capability negotiation session, nor is it necessary to re-establish the capability session with the first network entity, but directly use the capability negotiation session established between the first network entity and the device to renegotiate the capability, thereby realizing dynamic capability negotiation. This simplifies the process of renegotiating the capability, improves the efficiency of negotiating the capability, and reduces the burden on the first network entity and the device.

[0181] See also Fig. 9 , the present application embodiment provides a schematic diagram of a device 900 for capability negotiation. The device 900 may be the above Figure 3 The first network entity in the illustrated embodiment. The apparatus 900 comprises at least one processor 901 , an internal connection 902 , a memory 903 and at least one transceiver 904 .

[0182] The device 900 is a hardware structure device that can be used to implement Figure 7 The functional modules in the device 700 are as follows. For example, those skilled in the art may think of Figure 7 The processing unit 701 in the device 700 shown can be implemented by the at least one processor 901 calling the code in the memory 903. Figure 7 The sending unit 702 in the illustrated apparatus 700 may be implemented by the at least one transceiver 904 .

[0183] The device 900 may also be used to implement the function of the first network entity in any of the above embodiments.

[0184] The processor 901 may be a general-purpose central processing unit (CPU), a network processor (NP), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0185] The internal connection 902 may include a path to transmit information between the components. The internal connection 902 may be a single board or a bus.

[0186] The at least one transceiver 904 is used to communicate with other devices or communication networks.

[0187] The memory 903 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a bus. The memory may also be integrated with the processor.

[0188] The memory 903 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 901. The processor 901 is used to execute the application code stored in the memory 903, and cooperate with at least one transceiver 904, so that the device 900 implements the functions of the method of the present patent.

[0189] In a specific implementation, as an embodiment, the processor 901 may include one or more CPUs, such as Fig. 9 CPU0 and CPU1 in.

[0190] In a specific implementation, as an embodiment, the device 900 may include multiple processors, such as Fig. 9 901 and processor 907 in the embodiment. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0191] See also Fig.10, the present application embodiment provides a schematic diagram of a device 1000 for capability negotiation. The device 1000 may be the above Figure 3 The second network entity in the illustrated embodiment. The apparatus 1000 comprises at least one processor 1001 , an internal connection 1002 , a memory 1003 and at least one transceiver 1004 .

[0192] The device 1000 is a hardware structure device that can be used to implement Figure 8 The functional modules in the device 800 are as follows. For example, those skilled in the art may think of Figure 8 The processing unit 802 in the device 800 shown can be implemented by the at least one processor 1001 calling the code in the memory 1003. Figure 8 The receiving unit 801 in the device 800 shown may be implemented by the at least one transceiver 1004 .

[0193] The device 1000 may also be used to implement the function of the second network entity in any of the above embodiments.

[0194] The processor 1001 may be a general-purpose central processing unit (CPU), a network processor (NP), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0195] The internal connection 1002 may include a path to transmit information between the components. The internal connection 1002 may be a single board or a bus.

[0196] The at least one transceiver 1004 is used to communicate with other devices or communication networks.

[0197] The memory 1003 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a bus. The memory may also be integrated with the processor.

[0198] The memory 1003 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 1001. The processor 1001 is used to execute the application code stored in the memory 1003, and cooperate with at least one transceiver 1004, so that the device 1000 implements the functions of the method of the present patent.

[0199] In a specific implementation, as an embodiment, the processor 1001 may include one or more CPUs, such as Fig.10 CPU0 and CPU1 in.

[0200] In a specific implementation, as an embodiment, the device 1000 may include multiple processors, such as Fig.10 1001 and 1007 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0201] See also Fig.11 , the present application embodiment provides a schematic diagram of a capability negotiation system 1100. The system 1100 includes: Figure 7 The device 700 shown and Figure 8 The device 800 shown, or, comprising Fig. 9 The device 900 and Fig.10 The device 1000.

[0202] like Figure 7 The device 700 and Fig. 9 The device 900 may be a first network entity 1101, such as Figure 8 The device 800 and Fig.10 The device 1000 may be a second network entity 1102 .

[0203] A person skilled in the art will appreciate that all or part of the operations of the above embodiments may be performed by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the storage medium mentioned above may be a read-only memory, a disk or an optical disk, etc.

[0204] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A capability negotiation method, characterized in that: The method comprises: The first network entity obtains a capability update message, where the capability update message includes capability update information, and the capability update information indicates at least one capability that needs to be updated by the first network entity; The first network entity sends the capability update message to the second network entity based on the capability negotiation session established between the first network entity and the second network entity; The first network entity is a path computation element PCE, and the second network entity is a path computation client PCC; or, the first network entity is the PCC, and the second network entity is the PCE; The capability negotiation session is a session used by the first network entity and the second network entity when negotiating capabilities last time; The capability update message is a Path Computation Element Communication Protocol Open (PCEP) Open message, the PCEP Open message includes a dynamic capability negotiation identifier, and the dynamic capability negotiation identifier indicates that the PCEP Open message is a capability update message for renegotiating capabilities; or, The capability update message is a path computation unit communication protocol notification PCNtf message, the payload of the PCNtf message includes a capability type length value TLV, the capability TLV includes the capability update information, and the capability TLV indicates that the PCNtf message is a capability update message for renegotiating capabilities.

2. The method according to claim 1, characterized in that The at least one capability includes an updated capability of the first network entity, and the capability update information includes capability information of the updated capability; The at least one capability includes a capability added by the first network entity, and the capability update information includes capability information of the added capability; and / or, The at least one capability includes a reduced capability of the first network entity, and the capability update information includes capability information of the reduced capability.

3. The method according to claim 1 or 2, characterized in that Before the first network entity obtains the capability update message, the method further includes: The first network entity establishes the capability negotiation session; The first network entity negotiates one or more capabilities with the second network entity based on the capability negotiation session.

4. The method according to claim 1 or 2, characterized in that: The capability negotiation session is a PCEP session.

5. A capability negotiation method, characterized in that: The method comprises: The second network entity receives a capability update message sent by the first network entity based on a capability negotiation session established between the second network entity and the first network entity, wherein the capability update message includes capability update information, and the capability update information indicates at least one capability that the first network entity needs to update, wherein the first network entity is a path computation element PCE, and the second network entity is a path computation client PCC; or, the first network entity is the PCC, and the second network entity is the PCE; the capability negotiation session is a session used by the first network entity and the second network entity when negotiating capabilities last time; the capability update message is a path computation element communication protocol open PCEPOpen message, the PCEP Open message includes a dynamic capability negotiation identifier, and the dynamic capability negotiation identifier indicates that the PCEPOpen message is a capability update message for renegotiating capabilities; or, the capability update message is a path computation element communication protocol notification PCNtf message, the payload of the PCNtf message includes a capability type length value TLV, the capability TLV includes the capability update information, and the capability TLV indicates that the PCNtf message is a capability update message for renegotiating capabilities; The second network entity updates the effective capabilities of the second network entity based on the at least one capability when triggered by the dynamic negotiation identifier; or, when detecting that the capability TLV of the PCNtf message includes the capability update information, the second network entity updates the effective capabilities of the second network entity based on the at least one capability.

6. The method according to claim 5, characterized in that The at least one capability includes an updated capability of the first network entity, and the capability update information includes capability information of the updated capability; The at least one capability includes a capability added by the first network entity, and the capability update information includes capability information of the added capability; and / or, The at least one capability includes a reduced capability of the first network entity, and the capability update information includes capability information of the reduced capability.

7. The method according to claim 5 or 6, characterized in that Before the second network entity receives the capability update message sent by the first network entity, the method further includes: The second network entity establishes the capability negotiation session; The second network entity negotiates one or more capabilities with the first network entity based on the capability negotiation session, and the effective capabilities include capabilities successfully negotiated by the second network entity.

8. The method according to claim 5 or 6, characterized in that The capability negotiation session is a PCEP session.

9. A device for capability negotiation, characterized in that: The device comprises: a processing unit, configured to obtain a capability update message, wherein the capability update message includes capability update information, and the capability update information indicates at least one capability that needs to be updated by the device; a sending unit, configured to send the capability update message to the second network entity based on a capability negotiation session established between the device and the second network entity; The device is a path computation unit PCE, and the second network entity is a path computation client PCC; or, the device is the PCC, and the second network entity is the PCE; The capability negotiation session is a session used by the device and the second network entity when negotiating capabilities last time; The capability update message is a Path Computation Element Communication Protocol Open (PCEP) Open message, the PCEP Open message includes a dynamic capability negotiation identifier, and the dynamic capability negotiation identifier indicates that the PCEP Open message is a capability update message for renegotiating capabilities; or, The capability update message is a path computation unit communication protocol notification PCNtf message, the payload of the PCNtf message includes a capability type length value TLV, the capability TLV includes the capability update information, and the capability TLV indicates that the PCNtf message is a capability update message for renegotiating capabilities.

10. The device according to claim 9, characterized in that The at least one capability includes an updated capability of the device, and the capability update information includes capability information of the updated capability; The at least one capability includes a capability added by the device, and the capability update information includes capability information of the added capability; and / or, The at least one capability includes a reduced capability of the device, and the capability update information includes capability information of the reduced capability.

11. The device according to claim 9 or 10, characterized in that The processing unit is further used for: Establishing the capability negotiation session; One or more capabilities are negotiated with the second network entity based on the capability negotiation session.

12. The device according to claim 9 or 10, characterized in that The capability negotiation session is a PCEP session.

13. A device for capability negotiation, characterized in that: The device comprises: A receiving unit, configured to receive a capability update message sent by a first network entity based on a capability negotiation session established between the device and the first network entity, wherein the capability update message includes capability update information, and the capability update information indicates at least one capability that the first network entity needs to update, wherein the first network entity is a path computation element PCE, and the device is a path computation client PCC; or, the first network entity is the PCC, and the device is the PCE; the capability negotiation session is a session used by the first network entity and the device when the capability was negotiated last time; the capability update message is a path computation element communication protocol open PCEP Open message, the PCEP Open message includes a dynamic capability negotiation identifier, and the dynamic capability negotiation identifier indicates that the PCEP Open message is a capability update message for renegotiating capability; or, the capability update message is a path computation element communication protocol notification PCNtf message, the payload of the PCNtf message includes a capability type length value TLV, the capability TLV includes the capability update information, and the capability TLV indicates that the PCNtf message is a capability update message for renegotiating capability; A processing unit, configured to update the effective capabilities of the device based on the at least one capability when triggered by the dynamic negotiation identifier; or, when detecting that the capability TLV of the PCNtf message includes the capability update information, update the effective capabilities of the device based on the at least one capability.

14. The device according to claim 13, characterized in that The at least one capability includes an updated capability of the first network entity, and the capability update information includes capability information of the updated capability; The at least one capability includes a capability added by the first network entity, and the capability update information includes capability information of the added capability; and / or, The at least one capability includes a reduced capability of the first network entity, and the capability update information includes capability information of the reduced capability.

15. The device according to claim 13 or 14, characterized in that The processing unit is further used for: Establishing the capability negotiation session; One or more capabilities are negotiated with the first network entity based on the capability negotiation session, and the valid capabilities include capabilities successfully negotiated by the device.

16. The device according to claim 13 or 14, characterized in that The capability negotiation session is a PCEP session.

17. A capability negotiation system, characterized in that: The system comprises: the device according to any one of claims 9 to 12 and the device according to any one of claims 13 to 16.

18. A device for capability negotiation, characterized in that: The device comprises a memory, a processor and a computer program stored in the memory, and when the processor executes the computer program, the device implements the method according to any one of claims 1 to 8.

19. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

20. A computer program product, characterized in that The computer program product comprises a computer program stored in a computer-readable storage medium, and the computer program is loaded by a processor to implement the method according to any one of claims 1 to 8.

Images