METHOD, DEVICE AND COMMUNICATION SYSTEM FOR TUNNELLING MANAGEMENT

Description

Field of the Invention

[0001] The present invention relates to the field of communications network technologies, and in particular, to a tunnel management method, a tunnel management apparatus, and a communications system in a communications network.

Background of the Invention

[0002] In an existing packet-switched communications network, a forwarding path must be set up between network nodes to forward service packets. A forwarding path is implemented through a tunnel management procedure, and is created or updated between network elements through a tunnel management request. However, it is possible that the tunnel management request fails for certain reasons. For example, an error occurs in the request message or resources of an associated network node are exhausted. In a prior art, a cause value is generally used to indicate the processing result of the tunnel management request. The cause value indicates whether the processing of the tunnel management request succeeds or fails and indicates the reason of failure when the tunnel management request fails.

[0003] In an evolved packet system (EPS), when the mobility management element is a mobility management entity (MME), signaling exchanged between the MME and a packet data network gateway (PDN-GW or P-GW) must cross a serving gateway (S-GW). When a mobile terminal initiates a mobility management or session management procedure that includes a tunnel management request, such as an EPS attach, routing area update, tracking area update, handover, or external PDN connectivity procedure, the MME sends a tunnel management request and the S-GW and PDN-GW cooperate to process the tunnel management request. No matter whether the processing of the tunnel management request is successful or not, the S-GW will send a response which includes a cause value to the MME, indicating the processing result to the MME

[0004] Reference document "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 8) 3GPP TS 24.008 V8.1.0 (2008-03)" discloses on page 215 a tunneling management method within the GPRS tunneling protocol. A mobile station (MS) initiates a packet data protocol (PDP) context activation with a network. When the initiation request fails, the network sends to the initiating node a response message comprising a single cause code. A limited number of various cause codes are disclosed. One specific cause code is disclosed in which both the cause and the identification of the specific node that the PDP context activation is present on (cause code #30 activation rejected by GCSN) are identified together.

[0005] Reference document "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 3GPP TS 24.301 V0.3.0 (2008-05)" describes in Chapter 6.5.3.1 the UE requested PDN connectivity procedure. In particular, if connectivity with the requested PDN cannot be accepted by the network, the MME shall send a PDN CONNECTIVITY REJECT message to the UE. The message contains the procedure transaction identity (PTI) and a cause value indicating the reason for rejecting the UE requested PDN connectivity. Amongst others, one cause value is disclosed that indicates non-specifically whether it is the SGN or PDN GW that rejected the PDN connectivity request.

[0006] Reference document "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access, (Release 8) 3GPP TS 23.401 V8.2.0 (2008-06)" describes in chapter 5.3.2.1 the E-UTRAN Initial Attach procedure.

[0007] In the tunnel management procedure, however, the inventor finds at least the following problem in the prior art:

If the tunnel management request fails, the node that initiates the tunnel management request receives a response but cannot determine the error of which node has caused the tunnel management request failure according to the response. As a result, the node that initiates the tunnel management request cannot perform processing according to the tunnel management failure caused by different nodes.

Summary of the Invention

[0008] The present invention provides a tunnel management method, a tunnel management apparatus, and a communications system, which enable a node that initiates a tunnel management request to correctly determine the node that has caused the tunnel management request failure and perform processing accordingly.

[0009] To achieve the above purposes, the following technical solution is provided:

According to the first aspect of the present invention a method of determining a node that causes failure in a tunnel management procedure comprises:

receiving a tunnel management request from an initiating node;

sending a response message to the initiating node, wherein the response message comprises a cause value indicating whether the tunnel management request is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that:

in the response message there is included information of a node that causes failure of the tunnel management request when the tunnel management request fails, the information enabling the correct determination of which node out of the different nodes in the tunnel management procedure caused the failure of the tunnel management request.

[0010] According to the second aspect of the present invention a method of determining a node that causes failure in a tunnel management procedure comprises

sending a tunnel management request to a tunnel management node;

receiving from the tunnel management node a response message, wherein the response message comprises a cause value indicating whether the tunnel management request is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that:

in the response message there is included information of a node that causes failure of the tunnel management request when the tunnel management request fails, the information enabling the correct determination of which node out of the different nodes in the tunnel management procedure caused the failure of the tunnel management request; and

finding the node that causes failure of the tunnel management request according to the node information.

[0011] According to the third aspect of the present invention a tunnel management procedure apparatus comprises:

a receiving unit (141), configured to receive a tunnel management request from an initiating node;

a sending unit (142), configured to send to the initiating node a response message, which comprises a cause value indicating whether the tunnel management request is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that the sending unit is further configured to include in the response message information of a node that causes failure of the tunnel management request when the tunnel management request fails, the information enabling the correct determination of which node out of different nodes in the tunnel management procedure caused the failure of the tunnel management request.

[0012] According to the fourth aspect of the present invention a tunnel management procedure apparatus comprises:

a sending unit (151), configured to send a tunnel management request to a tunnel management node;

a receiving unit (152), configured to receive a response message from a tunnel management node that comprises a cause value indicating whether the tunnel management is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that the tunnel management procedure apparatus further comprises:

the response message includes node information, being information of a node that causes failure of the tunnel management request when the tunnel management request fails the tunnel management procedure apparatus; and the apparatus further comprises

a searching unit (153) configured to find from a node the node information included in the response message and correctly determine which node, out of different nodes in the tunnel management procedure, caused the failure of the tunnel management request.

[0013] According to the fifth aspect of the present invention a communications system comprising,
an initiating node (161), configured to send a tunnel management request;
a tunnel management node (162), configured to receive the tunnel management request from the initiating node (161) and return a response to the initiating node (161), wherein the response comprises a cause value indicating whether the tunnel management request is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that;
the response includes node information, being information of a node that causes failure of the tunnel management request when the tunnel management request fails the tunnel management procedure apparatus; and
the initiating node (161) is further configured to find from the node information included in the response and correctly determine which node out of different nodes in the tunnel management procedure caused failure of the tunnel management request.

[0014] Reference is also made to the independent claims, and further embodiments in the dependent claims. In the present invention, because the response message received by the initiating node includes node information and the initiating node can find the node that causes failure of a tunnel management request according to the node information, even if the tunnel management node further sends the tunnel management request to a remote node, the initiating node is able to distinguish whether the tunnel management request failure is caused by the tunnel management node or the remote node according to the node information. Thus, the initiating node can process the tunnel management request failure more conveniently, more efficiently, and more quickly. The present invention solves the problem in the prior art that an initiating node in a conventional communications system is unable to determine which node has caused the error and therefore fails to perform effective processing.

Brief Description of the Drawings

[0015] 

FIG. 1 shows an architecture of an EPS network according to an embodiment of the present invention;

FIG. 2 is a flowchart of a tunnel management method according to a first embodiment of the present invention;

FIG. 3 is a flowchart of another tunnel management method according to the first embodiment of the present invention;

FIG. 4 is a block diagram of a tunnel management apparatus according to the first embodiment of the present invention;

FIG. 5 is a block diagram of another tunnel management apparatus according to n the first embodiment of the present invention;

FIG. 6 shows an architecture of a communications system according to the first embodiment of the present invention;

FIG. 7 shows a user attach procedure according to a second embodiment of the present invention;

FIG. 8 shows a tunnel management procedure with attach failure according to the second embodiment of the present invention;

FIG. 9 shows a tracking area update procedure according to a third embodiment of the present invention;

FIG. 10 shows a routing area update procedure according to the third embodiment of the present invention;

FIG. 11 shows a handover procedure in a radio access network according to a fourth embodiment of the present invention;

FIG. 12 shows a PDN connectivity procedure according to a fifth embodiment of the present invention;

FIG. 13 shows a P-GW initiated bearer update procedure according to a sixth embodiment of the present invention;

FIG. 14 is a block diagram of a tunnel management apparatus according to a seventh embodiment of the present invention;

FIG. 15 is a block diagram of another tunnel management apparatus according to the seventh embodiment of the present invention; and

FIG. 16 shows an architecture of a communications system according to an eighth embodiment of the present invention.

Detailed Description of the Embodiments

[0016] FIG. 1 shows an evolved packet system (EPS) network according to an embodiment of the present invention. The EPS network includes a mobile terminal, a radio access network, a serving gateway (S-GW), a mobility management element, a packet data network gateway (PDN-GW or P-GW), and a policy control entity. When the mobility management element is a mobility management entity (MME), the signaling exchanged between the MME and the PDN-GW must cross the S-GW. If the mobility management element is a serving GPRS support node (SGSN), the SGSN may also send a tunnel management request to the S-GW and cooperate with the S-GW to process a tunnel management request initiated by the PDN-GW.

[0017] The embodiments of a tunnel management method, apparatus and system of the present invention will be described in detail with reference to the accompanying drawings.

Embodiment 1

[0018] The first embodiment relates to a tunnel management method. As shown in FIG. 2, the method includes the following steps:

201. In a communications system, when it is necessary to manage a user plane forwarding path, an initiating node sends a tunnel management request to a tunnel management node.

202. The tunnel management node receives the tunnel management request from the initiating node and performs appropriate processing, and sends a response that includes a cause value indicating success or failure of the tunnel management request to the initiating node. The response message also includes information of the node that causes failure of the tunnel management request.

[0019] The embodiment provides another tunnel management method. As shown in FIG. 3, the method includes the following steps:

301. In a communications system, when it is necessary to manage a user plane forwarding path, an initiating node sends a tunnel management request to a tunnel management node.

302. The tunnel management node receives the tunnel management request from the initiating node and performs appropriate processing, and sends a response that includes a cause value indicating success or failure of the tunnel management request to the initiating node. The response message returned after processing failure also includes node information.

303. The initiating node finds the node that causes the tunnel management request failure according to the node information. In practice, reasons of failure are varied and therefore different processing is required after the node that causes the tunnel management request failure is located. The subsequent embodiments of the present invention describe the processing with regard to four of the error causes.

[0020] According to the tunnel management method shown in FIG. 2, the embodiment of the present invention provides a tunnel management apparatus. As shown in FIG. 4, the apparatus includes a receiving unit 41 and a sending unit 42.

[0021] The receiving unit 41 is configured to receive the tunnel management request from the initiating node. When the processing of the tunnel management request fails, the sending unit 42 is configured to send a response that includes node information to the initiating node. The node information is information of the node that causes the tunnel management request failure so that the initiating node can find the node that causes the tunnel management request failure according to the node information.

[0022] According to the tunnel management method shown in FIG. 3, the embodiment of the present invention provides a tunnel management apparatus. As shown in FIG. 5, the apparatus includes a sending unit 51, a receiving unit 52, and a searching unit 53.

[0023] The sending unit 51 is configured to send a tunnel management request to a tunnel management node, which returns a response that includes node information to the apparatus after processing the tunnel management request. The receiving unit 52 is configured to receive the response that includes node information returned by the tunnel management node. The searching node 53 is configured to find the node that causes the tunnel management request failure according to the node information.

[0024] The embodiment also provides a communications system. As shown in FIG. 6, the communications system includes an initiating node 61 and a tunnel management node 62. In the communications system, when it is necessary to manage a user plane forwarding path, the initiating node 61 is configured to send a tunnel management request; the tunnel management node 62 is configured to receive the tunnel management request from the initiating node 61 and return a response that includes node information to the initiating node 61; the initiating node 61 is further configured to find the node that causes the tunnel management request failure according to the node information and perform processing accordingly afterwards, for example, select an effective error check direction or select a new node. Specifically, the error check is: checking whether the error is caused by the local equipment implementation when the error cause included in the received response is an information element (IE) related error with the value such as "IE missing" or "IE decodes error" and checking the equipment implementation of the error node indicated in the response message when the local equipment implementation is correct. This helps the node to locate the error cause quickly and thus assures the correct proceeding of the subsequent procedure.

[0025] The embodiment of the present invention determines whether the failure of a tunnel management request is caused by the tunnel management node or a remote node according to the node information so that the initiating node can process the tunnel management request failure more conveniently, more efficiently and more quickly.

Embodiment 2

[0026] The application environment of the embodiment is an EPS network. FIG. 7 shows the processing of the network in a attach procedure in EPS network, especially when a tunnel management request fails. The method includes the following steps:

701. A user equipment (UE) sends an Attach Request to the MME.

702. The MME sends an Identity Request to the UE.

703. The UE sends an Identity Response to the MME according to the Identity Request of the MME.

[0027] In the embodiment, steps 702 and 703 are optional.

704. The MME and a home subscriber server (HSS) complete authentication of the UE together.

705. The MME and an equipment identity register (EIR) complete the IMEI check of the UE together.

706. The MME sends an Update Location request to the HSS.

707. The HSS sends an Insert Subscriber Data to the MME.

708. The MME returns an Insert Subscriber Data ACK to the HSS.

709. The HSS returns an Update Location ACK to the MME after the MME acknowledges the subscriber data.

710. After the MME receives the location update information, the MME sends a Create Default Bearer Request to the S-GW to create a bearer.

711. As a tunnel management node, the S-GW processes the Create Default Bearer Request sent by the MME. If the S-GW processes the Create Default Bearer Request successfully, steps 712, 713, 714, 716 and subsequent steps are performed; otherwise, step 715 and subsequent steps are performed.

712. The S-GW sends the Create Default Bearer Request to the P-GW.

713. The P-GW processes the Create Default Bearer Request sent from the S-GW and sends a Create Default Bearer Response to the S-GW. The response message includes a cause value indicating whether the processing of the Create Default Bearer Request is successful or unsuccessful, and if unsuccessful, indicating the reason of the processing failure.

714. After the S-GW receives the response from the P-GW, the S-GW returns a Create Default Bearer Response to the MME, indicating whether the processing of the Create Default Bearer Request is successful or unsuccessful with a cause value, and when the response received from the P-GW indicates processing failure, the response returned to the MME includes node information of the P-GW, identifying the node that causes the Create Default Bearer Request failure. The node information may be indicated by a field in the cause of the failure of the tunnel management request, or an IE in the response message.

715. When the S-GW fails to process the Create Default Bearer Request, the S-GW sends a Create Default Bearer Response to the MME, indicating the reason of the Create Default Bearer Request failure with a cause value. The response message includes node information of the S-GW, identifying the node that causes the Create Default Bearer Request failure. The node information may be indicated by a field in the error cause of the tunnel management request, or an IE in the response message.

[0028] To enable the MME to obtain more information about the Create Default Bearer Request failure, the response returned in the step may further include additional location information to identify the reason of the Create Default Bearer Request failure.
716. After the MME receives the Create Default Bearer Response, the MME performs processing according to the node information and additional location information included in the response message. As shown in FIG. 8, the processing of the MME includes the following steps:

801. The MME decodes the received Create Default Bearer Response to obtain the node information and additional location information included in the response.

802. The MME finds the node that causes the Create Default Bearer Request failure according to the obtained node information.

803. The MME analyzes the reason of the Create Default Bearer Request failure according to the cause value. If the reason of the request failure is resource insufficiency or equipment failure, the process proceeds to step 804. The resource insufficiency includes bandwidth insufficiency and memory insufficiency. If the reason of the request failure is IE missing or IE decodes error, for example, an IE in the Create Default Bearer Request is missing or a correct IE is not decoded, step 807 is performed.

804. The MME determines whether the node that causes the Create Default Bearer Request failure is the S-GW or P-GW. If the node is the S-GW, step 805 is performed; if it is the P-GW, step 806 is performed.

805. The MME selects a new S-GW without changing the P-GW and continues with another Create Default Bearer Request.

806. The MME selects a new P-GW without changing the S-GW and continues with another Create Default Bearer Request.

807. The MME locates the missing IE or the incorrectly decoded IE according to the additional location information. An operator may first check whether an error has occurred in the MME, for example, whether IEs in the sent request message are correct. If the IEs are incorrect, the operator can check the MME so that the MME sends the correct Create Default Bearer Request in the next attach procedure. If the IEs are correct, the operator can check whether an error has occurred in the node that causes the Create Default Bearer Request failure.

[0029] In practice, because the reasons of the Create Default Bearer Request failure are varied, the MME needs to perform different processing accordingly.

[0030] The interface protocol between S-GW and P-GW in the embodiment communicate is the GPRS Tunneling Protocol (GTP). In practice, the S-GW and P-GW may communicate over the Proxy Mobile IP Protocol (PMIP), in which case step 712 and step 713 above are modified as follows:

712'. The S-GW sends a Proxy Binding Update request to the P-GW.

713'. The P-GW processes the Proxy Binding Update request from the S-GW and sends a response to the S-GW if the P-GW fails to process the Proxy Binding Update request. The response is in particular a Proxy Binding ACK, which includes a cause value indicating failure of the processing.

[0031] With the node information included in the response returned by the S-GW, the MME can know the node that causes the Create Default Bearer Request failure. When the Create Default Bearer Request fails, the MME can adjust the node that causes the failure in time so that the subsequent procedure is performed correctly.

Embodiment 3

[0032] The embodiment is applicable to a tracking area update procedure. As shown in FIG. 9, when a tunnel management request fails, the processing on the network side includes the following steps:

901. A UE sends a Tracking Area Update Request to an evolved NodeB (eNodeB) and the eNodeB sends the Tracking Area Update Request to a new MME.

902. The new MME receives the Tracking Area Update Request and obtains a context from the old MME.

903. The new MME decides whether to select a new S-GW according to the user location information sent from the eNodeB. If the new MME decides not to select a new S-GW, the new MME sends an Update Bearer Request to the old S-GW.

904. As a tunnel management node, the old S-GW processes the Update Bearer Request sent from the new MME. If the old S-GW processes the Update Bearer Request successfully, steps 905, 906, 907, 909 and subsequent steps are performed; otherwise, step 908 and subsequent steps are performed.

905. The old S-GW sends an Update Bearer Request to the P-GW.

906. The P-GW processes the Update Bearer Request from the old S-GW and sends an Update Bearer Response to the old S-GW. The response message includes a cause value indicating whether the processing of the Update Bearer Request is successful or unsuccessful, and if unsuccessful, indicating the reason of the processing failure.

907. The old S-GW receives the Update Bearer Response from the P-GW and sends an Update Bearer Response to the new MME, indicating whether the processing of the Update Bearer Request is successful or unsuccessful with a cause value, and if the cause value included in the Update Bearer Response returned by the P-GW indicates processing failure, the response returned to the new MME includes the node information of the P-GW to identity the node that causes the Update Bearer Request failure. The node information may be indicated by a field in the cause of the failure of the tunnel management request, or an IE in the response message.

[0033] To enable the new MME to obtain more information about the Update Bearer Request failure, the response returned in the step may further include additional location information to identify the reason of the Update Bearer Request failure.

[0034] 908. When the old S-GW fails to process the Update Bearer Request, the old S-GW sends to the new MME an Update Bearer Response, which indicates the reason of the Update Bearer Request failure with a cause value and includes node information of the old S-GW identifying the node that causes the Update Bearer Request failure.

[0035] 909. The new MME receives the Update Bearer Response and performs processing according to the node information in the response message. For example, the new MME first checks for errors of the local node in the case of an IE related error and then the node causing occurrence of the error checks for errors.

[0036] In the embodiment, only the MME is updated in the tracking area update procedure and sometimes the S-GW is also updated. When it is necessary to update the S-GW, the processing is similar to that shown in FIG. 9 and the only difference is that the functions completed by the old S-GW are completed by the new S-GW, as shown by the broken lines.

[0037] The step where the new MME obtains a context is the same as steps 901 and 902. After the new MME obtains the context, the new MME decides whether to select a new S-GW. If a new S-GW is selected, the new MME sends a Create Bearer Request to the new S-GW. If the new S-GW processes the Create Bearer Request correctly, the new S-GW sends an Update Bearer Request to the P-GW; otherwise, the new S-GW returns to the new MME a Create Bearer Response, which includes node information of the new S-GW, indicating that the bearer update failure is caused by the new S-GW. After processing the Update Bearer Request, the P-GW returns an Update Bearer Response to the new S-GW. If the P-GW fails to process the Update Bearer Request, the P-GW returns to the new S-GW an Update Bearer Response that includes an error cause. The new S-GW also sends a Create Bearer Response to the new MME. When the response message received from the P-GW indicates processing failure, the response returned to the new MME includes node information of the P-GW, indicating that the bearer update failure is caused by the P-GW.

[0038] In practice, procedures like those in the second and third embodiments are adopted in many scenarios such as routing area update and PDN connectivity to implement the failure prompt of tunnel management requests.

[0039] In routing area update scenarios, with respect to a routing area update request from a UE, the following two cases may exist:

In the first case, the S-GW changes. In this case, the new SGSN acts as the initiating node of the Create Bearer Request and the new S-GW acts as the tunnel management node of the Create Bearer Request, and the P-GW acts as the remote node. The procedure is shown by the solid lines in FIG. 10.

[0040] The UE sends a Routing Area Update Request to the new SGSN. The new SGSN obtains a context from the old SGSN and afterwards sends a Create Bearer Request to the new S-GW. If the new S-GW processes the Create Bearer Request correctly, the new S-GW sends an Update Bearer Request to the P-GW; otherwise, the new S-GW sends to the new SGSN a Create Bearer Response which includes node information of the new S-GW, indicating that the bearer creation failure is caused by the new S-GW. After processing the Update Bearer Request, the P-GW returns to the new S-GW an Update Bearer Response which indicates processing success or failure with a cause value. If the P-GW fails to process the Update Bearer Request, the P-GW returns to the new S-GW an Update Bearer Response that indicates failure. The new S-GW also sends a Create Bearer Response to the new SGSN and when the message returned by the P-GW indicates processing failure, the message returned to the new SGSN includes node information of the P-GW, indicating that the bearer creation failure is caused by the P-GW.

[0041] In the second case, the S-GW does not change. In this case, the old SGSN acts as the initiating node of the Routing Area Update Request, the old S-GW acts as the tunnel management node of the Routing Area Update Request, and the P-GW acts as the remote node. The procedure is shown by the broken lines in FIG. 10.

[0042] The UE sends a Routing Area Update Request to the old SGSN. The old SGSN sends an Update Bearer Request to the old S-GW. If the old S-GW processes the Update Bearer Request correctly, the old S-GW sends an Update Bearer Request to the P-GW; otherwise, the old S-GW returns to the old SGSN an Update Bearer Response, which includes node information of the old S-GW, indicating that the bearer update failure is caused by the old S-GW. After processing the Update Bearer Request, the P-GW returns to the old S-GW an Update Bearer Response which indicates processing success or failure with a cause value. If the P-GW fails to process the Update Bearer Request, the P-GW returns to the old S-GW an Update Bearer Response that indicates failure. The old S-GW also sends an Update Bearer Response to the old SGSN and when the message returned by the P-GW indicates processing failure, the message returned to the old SGSN includes node information of the P-GW, indicating that the bearer update failure is caused by the P-GW.

[0043] From the above description, it is known that the method in the embodiment can indicate the node that causes failure of tracking area update or routing area update in a tracking area update or routing area update procedure so that the node causing the tracking area update or routing area update failure is adjusted in time and that the subsequent procedure proceeds correctly.

Embodiment 4

[0044] The scenario of the fourth embodiment is the handover from an evolved UMTS territorial radio access network (E-UTRAN) to a UMTS territorial radio access network (UTRAN). As shown in FIG. 11, when a tunnel management request fails, the processing of the network includes the following steps:

1101. A UE creates a forwarding tunnel for downlink service packets with the target SGSN of a radio access network and sends the serving radio network subsystem (SRNS) context to the target SGSN.

1102. The target SGSN receives the SRNS context and sends an Update Bearer Request to the target S-GW.

1103. As a tunnel management node, the target S-GW processes the Update Bearer Request sent from the target SGSN. If the target S-GW processes the Update Bearer Request successfully, steps 1104, 1105, 1107 and subsequent steps are performed; otherwise, steps 1106 and 1108 are performed.

1104. The target S-GW sends an Update Bearer Request to the P-GW.

1105. The P-GW processes the Update Bearer Request sent from the target SGSN and returns to the target S-GW an Update Bearer Response, which includes a cause value indicating processing success or failure. When the P-GW fails to process the Update Bearer Request, the P-GW returns to the target S-GW an Update Bearer Response that includes an error cause and node information of the P-GW.

1106. When the target S-GW fails to process the Update Bearer Request, the target S-GW sends to the target SGSN an Update Bearer Response, which indicates the reason of the Update Bearer Request failure with a cause value and includes node information of the target S-GW identifying the node that causes the Update Bearer Request failure.

1107. The target S-GW receives the response from the P-GW and sends to the target SGSN an Update Bearer Response, which includes a cause value indicating whether the processing of the Update Bearer Request is successful or unsuccessful. If the cause value included in the response received from the P-GW indicates processing failure, the target S-GW sends the node information in the response from the P-GW transparently to the target SGSN. The node information may be indicated by a field in the cause of the failure of the tunnel management request or an IE in the response message.

[0045] To enable the target SGSN to obtain more information about the Update Bearer Request failure, the response returned in the step may further include additional location information to identify the specific reason of the Update Bearer Request failure.

[0046] 1108. After the target SGSN receives the Update Bearer Response, the target SGSN performs processing according to the node information and additional location information included in the response message. In the case of an IE related error, the target SGSN first checks for errors in the local node. After it is determined that the processing of the SGSN is correct, the node that causes occurrence of the error checks for errors so that the next procedure can proceed correctly. In the case of resource insufficiency, if the node information indicates an error of the target S-GW, the target SGSN may select a new S-GW and initiate a tunnel management procedure.

[0047] From the above description, it is known that the method in the embodiment of the present invention indicates whether the node that causes a bearer update failure is the target S-GW or P-GW during the handover from an E-UTRAN to a UTRAN, so that the target SGSN can adjust the node causing the bearer update failure in time and that the subsequent procedure will proceed correctly.

Embodiment 5

[0048] The scenario of the fifth embodiment is a PDN connectivity procedure. As shown in FIG. 12, when the procedure fails, the method includes the following steps:

1201. A UE sends a PDN Connectivity Request to the MME.

1202. The MME receives the PDN Connectivity Request and sends a Create Default Bearer Request to the S-GW to create a bearer.

1203. As a tunnel management node, the S-GW processes the Create Default Bearer Request. If the S-GW processes the Create Default Bearer Request successfully, step 1204 to steps 1210 and 1212 are performed; otherwise, steps 1211 and 1212 are performed.

1204. The S-GW sends the Create Default Bearer Request to the P-GW.

1205. As a tunnel management node, the P-GW processes the Create Default Bearer Request. If the P-GW processes the Create Default Bearer Request successfully, step 1206 to steps 1208, 1210 and 1212 are performed; otherwise, steps 1209, 1210 and 1212 are performed.

1206. The P-GW creates an IP Connectivity Access Network (IP-CAN) session with a Policy and Charging Rules Function (PCRF).

1207. The PCRF sends to the P-GW a response message which includes a cause value indicating whether the IP-CAN session is created successfully or unsuccessfully.

1208. The P-GW receives the response from the PCRF and returns to the S-GW a Create Default Bearer Response, which includes a cause value indicating whether the processing of the Create Default Bearer Request succeeds or fails. When the cause value in the response received from the PCRF indicates processing failure, the response returned to the S-GW includes node information of the PCRF, identifying the node that causes the Create Default Bearer Request failure.

1209. The P-GW sends to the S-GW a Create Default Bearer Response, which includes a cause value indicating that the Create Default Bearer Request fails and node information of the P-GW, identifying the node that causes the Create Default Bearer Request failure.

[0049] The node information may be indicated by a field in the cause of failure of the tunnel management request, or an IE in the response message.

[0050] To enable the S-GW to obtain more information about the Create Default Bearer Request failure, the response returned in steps 1208 and 1209 may further include additional location information to identify the reason of the Create Default Bearer Request failure. The additional location information may be indicated by a field in the cause of the failure of the tunnel management request, or an IE in the response message.

[0051] 1210. The S-GW sends to the MME a Create Default Bearer Response, which includes a cause value indicating that the Create Default Bearer Request fails and node information, identifying the node that causes the Create Default Bearer Request failure. The node information is that included in the response received from the P-GW.

[0052] The node information may be indicated by a field in the cause of the failure of the tunnel management request, or an IE in the response message. To enable the MME to obtain more information about the Create Default Bearer Request failure, the response returned in the step may further include additional location information to identify the specific reason of the Create Default Bearer Request failure. The additional location information may be the additional location information included in the response received by the S-GW. The additional location information may also be indicated by a field in the cause of the failure of the tunnel management request, or an IE in the response message.

[0053] 1211. The S-GW sends to the MME a Create Default Bearer Response, which includes a cause value indicating that the Create Default Bearer Request fails and node information of the S-GW, identifying the node that causes the Create Default Bearer Request failure.

[0054] 1212. After the MME receives the Create Default Bearer Response, the MME performs processing according to the node information and additional location information included in the response message. In the case of an IE related error, the MME first checks for errors in the local node. After it is determined that the processing of the local node is correct, the node that causes occurrence of the error checks for errors so that the next procedure can proceed correctly. In the case of resource insufficiency, if the node information indicates an error of the P-GW, the MME may select a new P-GW and initiate a new tunnel management procedure. The specific error cause can be known from the additional location information, for example, which IE is lost and which IE is decoded incorrectly.

[0055] From the above description, it is known that in the PDN connectivity procedure, the method in the embodiment of the present invention can indicate whether the node causing the PDN connectivity failure is the S-GW, P-GW, or PCRF, so that the MME can adjust the node causing the PDN connectivity failure and that the subsequent procedure can proceed correctly.

Embodiment 6

[0056] The scenario of the sixth embodiment is the bearer creation initiated by the P-GW. As shown in FIG. 13, the method for indicating the bearer creation failure includes the following steps:

1301. The P-GW sends a Create Dedicated Bearer Request to the S-GW.

1302. As a tunnel management node, the S-GW processes the Create Dedicated Bearer Request. If the S-GW processes the Create Dedicated Bearer Request successfully, step 1303 to step 1310 and step 1312 are performed; otherwise, steps 1311 and 1312 are performed.

1303. The S-GW sends the Create Dedicated Bearer Request to the MME.

1304. After the MME receives the Create Dedicated Bearer Request, the MME processes the Create Dedicated Bearer Request. If the MME processes the Create Dedicated Bearer Request successfully, step 1305 to steps 1308, 1310, and 1312 are performed; otherwise, steps 1309, 1310, and 1312 are performed.

1305. The MME sends a Create Bearer Request to the eNodeB of the UE to create a bearer.

1306. The eNodeB configures a Radio Resource Connection (RRC) with the UE.

1307. The eNodeB returns a Create Bearer Response to the MME. If the RRC configuration fails, or the bearer between the eNodeB and the S-GW fails, the response returned by the eNodeB to the MME includes a failure cause value.

1308. The MME returns to the S-GW a Create Dedicated Bearer Response, which includes a cause value of the dedicated bearer creation failure and node information of the eNodeB, indicating that the dedicated bearer creation failure is caused by the eNodeB. The node information may be indicated by a field in the cause of failure of the bearer creation, or an IE in the response message.

1309. The MME returns to the S-GW a Create Dedicated Bearer Response, which includes a cause value of the dedicated bearer creation failure and node information of the MME, indicating that the dedicated bearer creation failure is caused by the MME. The node information may be indicated by a field in the cause of the failure of the bearer creation, or an IE in the response message.

1310. The S-GW sends to the P-GW a Create Dedicated Bearer Response, which includes a cause value indicating that the Create Dedicated Bearer Request fails and node information, identifying the node that causes the Create Dedicated Bearer Request failure. The node information is included in the response message sending from the MME. The node information may be indicated by a field in the cause of the failure of the Create Dedicated Bearer Request, or an IE in the response message.

1311. The S-GW sends to the P-GW a Create Dedicated Bearer Response, which includes a cause value indicating that the Create Dedicated Bearer Request fails and node information of the S-GW, identifying the node that causes the Create Dedicated Bearer Request failure.

[0057] To enable the P-GW to obtain more information about the Create Dedicated Bearer Request failure, the response returned in the step may further include additional location information to identify the reason of the Create Dedicated Bearer Request failure. The additional location information may also be indicated by a field in the cause of the failure of the tunnel management request, or an IE in the response message.

[0058] 1312. After the P-GW receives the Create Dedicated Bearer Response, the P-GW performs processing according to the node information and additional location information included in the response message. In the case of an IE related error, the P-GW first checks for errors in the local node. After it is determined that the processing of the local node is correct, the node that causes occurrence of the error checks for errors so that the next procedure can proceed correctly.

[0059] From the above description, it is known that in the dedicated bearer creation procedure, the method in the embodiment of the present invention can indicate whether the node causing the dedicated bearer creation failure is the S-GW, MME, or eNodeB, so that the P-GW can adjust the node causing the dedicated bearer creation failure and that the subsequent procedure can proceed correctly.

Embodiment 7

[0060] According to the second to sixth embodiments, the embodiment of the present invention provides a tunnel management apparatus. As shown in FIG. 14, the apparatus includes a receiving unit 141 and a sending unit 142.

[0061] The receiving unit 141 is configured to receive a tunnel management request from an initiating node; when the tunnel management request of the initiating node is processed unsuccessfully, the sending unit 142 is configured to send to the initiating node a response, which includes node information of the node that causes the tunnel management request failure.

[0062] The node that causes the tunnel management request failure may be the local node or a remote node. When the node causing the failure is the local node, to assure correct processing of the tunnel management apparatus, the sending unit 142 includes a determining module 1421 and a sending module 1422.

[0063] The determining module 1421 is configured to determine whether the local node is able to complete the tunnel management request. The sending module 1422 is configured to send to the initiating node a response message which includes a cause value of failure of the tunnel management request and local node information when the determining module 1421 determines that the local node is unable to complete the tunnel management request, where the local node information is the node information of the node that causes the tunnel management request failure.

[0064] When the node causing the tunnel management request failure is a remote node, two cases exist:

In the first case, the node that causes the tunnel management request failure is directly connected to the local node. When the local node processes the tunnel management request correctly, the sending unit 142 is further configured to send the tunnel management request to the remote node. After the remote node processes the tunnel management request, the remote node returns a tunnel management response to the local node. The response message includes a cause value indicating whether the processing is successful or unsuccessful. The receiving unit 141 of the local node is also configured to receive the response from the remote node. When the processing of the remote node is unsuccessful, the response includes a cause value of the tunnel management request failure. Therefore, the response sent by the sending unit 142 to the initiating node includes the cause value of the tunnel management request failure and information of the remote node. This means the response indicates that the remote node information is the node information of the node that causes the tunnel management request failure.

[0065] In the second case, the node that causes the tunnel management request failure is a remote node, which is connected to the local node via another remote node. In this case, the sending unit 142 is further configured to send the tunnel management request to the other remote node. The response returned by the other remote node to the local node includes the cause value of the tunnel management request failure and node information which is the information of the remote node. The receiving unit 141 is further configured to receive the response from the other remote node. The response includes the cause value of the tunnel management request failure and node information. The sending unit 142 sends to the initiating node a response that includes the failure cause value and the received node information. This means that the local node transmits the received cause value of the tunnel management request failure and the node information transparently to the initiating node.

[0066] To better distinguish the specific reason of the tunnel management request failure, the response received by the receiving unit 141 in the embodiment may also include additional location information, identifying the specific reason of the tunnel management request failure. For example, the additional location information may indicate which IE is missing or incorrectly decoded and which mandatory IE is missing. Likewise, the response sent by the sending unit 142 in the embodiment to the initiating node may also include the additional location information so that the initiating node can find the correct failure cause.

[0067] In practice, the tunnel management apparatus in the embodiment of the present invention may be configured in many network devices, such as the S-GW, P-GW, MME, and SGSN.

[0068] According to the tunnel management method shown in FIG. 8 in the second embodiment, the embodiment of the present invention provides another tunnel management apparatus. As shown in FIG. 15, the apparatus includes a sending unit 151, a receiving unit 152, and a searching unit 153.

[0069] The sending unit 151 is configured to send a tunnel management request to the tunnel management node. After the tunnel management node processes the tunnel management request, the tunnel management node returns a tunnel management response to the apparatus. If the processing is unsuccessful, the response returned to the apparatus includes node information and additional location information. The node information identifies the node that causes the tunnel management request failure. The additional location information identifies the specific reason of the tunnel management request failure. The receiving unit 152 is configured to receive the response that includes node information returned by the tunnel management node. The searching unit 153 is configured to find the node that causes the tunnel management request failure according to the node information and find the specific reason of the tunnel management request failure according to the additional location information to facilitate the error checking.

[0070] To guarantee that the apparatus in the embodiment performs error checking correctly, the tunnel management apparatus further includes a processing unit 154. The processing unit 154 is configured to select a new node to replace the node that causes the tunnel management request failure when the cause of the tunnel management request failure is resource insufficiency or equipment failure; or the processing unit 154 is configured to check for errors of the local node or instruct the node that causes the tunnel management request failure to check for errors when the cause of the tunnel management request failure is IE missing or IE decoded error.

[0071] If the network devices are defined as an initiating node, an intermediate node and a remote node, the function of the tunnel management apparatus shown in FIG. 14 to determine whether the local device is able to process the request can be configured on the intermediate node or the remote node; the function of sending or transparently transmitting the error node indication to the initiating node after receiving the response from the remote node can only be implemented on the intermediate node. The tunnel management apparatus shown in FIG. 15 is only configured on the initiating node. Depending on the specific type of tunnel management request, the initiating node may be an MME, or a P-GW, or an SGSN.

[0072] In the embodiment, the response returned by the intermediate node to the initiating node includes node information to enable the initiating node to find the node that causes the tunnel management request failure and make node adjustment accordingly, so that the subsequent procedure proceeds correctly.

Embodiment 8

[0073] The eighth embodiment provides a communications system. As shown in FIG. 16, the communications system includes an initiating node 161 and a tunnel management node 162. When it is necessary to manage a user plane forwarding path, the initiating node 161 is configured to send a tunnel management request to the tunnel management node 162. The tunnel management node 162 is configured to receive the tunnel management request from the initiating node 161 and determine whether the tunnel management node is able to complete the tunnel management request. If the tunnel management node 162 is unable to complete the tunnel management request, the tunnel management node 162 sends to the initiating node 161 a response which includes the cause value of the tunnel management request failure and information of the tunnel management node, indicating that the tunnel management node is the node that causes the tunnel management request failure. The initiating node 161 is further configured to find the node that causes the tunnel management request failure according to the node information in the response returned by the tunnel management node and perform related error checking.

[0074] The above communications system generally relates to the communication between two network devices, for example, between MME and S-GW and between S-GW and P-GW.

[0075] When a third network device exists in the communications system, the communications system in the embodiment further includes a remote node 163.

[0076] When the tunnel management node 162 is able to process the tunnel management request correctly, the tunnel management node 162 sends the tunnel management request to the remote node 163, which causes failure of the tunnel management request due to a certain reason, such as a local node error. The remote node 163 is then configured to return to the tunnel management node 162 a response which includes the cause value of the tunnel management request failure. In this case, the tunnel management node 162 is further configured to send to the initiating node 161 a response that includes the cause value of the tunnel management request failure and information of the remote node, indicating that the remote node is the node causing the tunnel management request failure.

[0077] If the remote node is connected to a connection processing device and the tunnel management request from the initiating node needs to be processed by the connection processing device, and if the device that ultimately causes the tunnel management request failure is the connection processing device, the processing of the communications system is as follows:

When the tunnel management node 162 is able to process the tunnel management request, the tunnel management node 162 sends the tunnel management request to the remote node 163. Because the remote node 163 processes the request correctly, the tunnel remote node sends the request to the connection processing device. The connection processing device fails to process the request and returns a failure cause value only to the remote node. Therefore, the response returned by the remote node 163 to the tunnel management node 162 includes the cause value of the tunnel management request failure and node information which is node information of the connection processing device. In this case, the tunnel management node 162 is further configured to send to the initiating node 161 a response that includes the cause value of the tunnel management request failure and the received node information. The received node information matches the node that causes the tunnel management request failure, that is, the connection processing device. In the embodiment, the tunnel management node 162 transmits the cause value of the tunnel management request failure and the received node information transparently to the initiating node.

[0078] The embodiment is applicable to a communications system with respect to various possible failure causes during the management of a user plane forwarding path and indicates the cause to the initiating node so that the initiating node performs appropriate processing.

[0079] Because the response received by the initiating node includes node information and the initiating node can find the node causing the tunnel management request failure according to the node information, the initiating node will be able to distinguish whether the tunnel management request failure is caused by the tunnel management node or the remote node, even if the tunnel management node further sends the tunnel management request to the remote node. Thus, the initiating node can process the tunnel management request failure more conveniently, more efficiently, and more quickly.

[0080] Through the descriptions of the preceding embodiments, those skilled in the art may understand that the present invention may be implemented by hardware only or by software and a necessary universal hardware platform. However, in most cases, using software and a necessary universal hardware platform are preferred. Based on such understandings, all or part of the technical solution under the present invention that makes contributions to the prior art may be essentially embodied in the form of a software product. The software product may be stored in a computer readable storage medium, such as a hard disk, a compact disk read-only memory (CD-ROM), and a floppy disk. The software product includes a number of instructions that enable a computer device (personal computer, server, or network device) to execute the methods provided in the embodiments of the present invention.

[0081] Although the invention has been described through some exemplary embodiments, the invention is not limited to such embodiments.

Claims

1. A method of determining a node that causes failure in a tunnel management procedure, comprising
receiving a tunnel management request from an initiating node;
sending a response message to the initiating node, wherein the response message comprises a cause value indicating whether the tunnel management request is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that:

in the response message there is included information of a node that causes failure of the tunnel management request when the tunnel management request fails, the information enabling correct determination of which node out of the different nodes in the tunnel management procedure caused the failure of the tunnel management request.

2. The method of claim 1, further comprising:

determining whether a local node is able to complete the tunnel management request; and

if the local node is unable to complete the tunnel management request, the node information comprised in the response message is information of the local node.

3. The method of claim 1, further comprising:

sending the tunnel management request to a remote node; and

receiving from the remote node a response message, which comprises a cause value of tunnel management request failure; wherein

the step of sending to the initiating node a response message comprises sending to the initiating node a response message that comprises the cause value of tunnel management request failure and information of the remote node, wherein the information of the remote node is information of the node that causes the tunnel management request failure.

4. The method of claim 1, further comprising:

sending the tunnel management request to a remote node; and

receiving from the remote node a response message, which comprises a cause value of tunnel management request failure and node information;

the step of sending to the initiating node a response message that comprises node information comprises: sending to the initiating node a response message that comprises the cause value of tunnel management request failure and the received node information, wherein the received node information is information of the node that causes the tunnel management request failure.

5. The method of claim 3 or 4, wherein:

the response message received from the remote node comprises additional location information for locating a missing information element, IE, or an incorrectly decoded IE, wherein the additional location information identifies a specific reason of the tunnel management request failure; and

the response message sent to the initiating node comprises the additional location information.

6. A method of determining a node that causes failure in a tunnel management procedure, comprising
sending a tunnel management request to a tunnel management node;
receiving from the tunnel management node a response message, wherein the response message comprises a cause value indicating whether the tunnel management request is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that:

in the response message there is included information of a node that causes failure of the tunnel management request when the tunnel management request fails, the information enabling correct determination of which node out of the different nodes in the tunnel management procedure caused the failure of the tunnel management request; and

finding the node that causes failure of the tunnel management request according to the node information.

7. The method of claim 6, further comprising:

if the cause of the tunnel management request failure is resource insufficiency or equipment failure, selecting a new node to replace the node that causes failure of the tunnel management request; and

if the cause of the tunnel management request failure is Information Element (IE) missing or IE decode error, locating a specific IE that is missing or incorrectly decoded according to additional location information.

8. A tunnel management procedure apparatus, comprising
a receiving unit (141), configured to receive a tunnel management request from an initiating node;
a sending unit (142), configured to send to the initiating node a response message, which comprises a cause value indicating whether the tunnel management request is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that the sending unit is further configured to include in the response message information of a node that causes failure of the tunnel management request when the tunnel management request fails, the information enabling correct determination of which node out of different nodes in the tunnel management procedure caused the failure of the tunnel management request.

9. The apparatus of claim 8, wherein the sending unit (142) comprises:

a determining module (1421), configured to determine whether a local node is able to complete the tunnel management request; and

a sending module (1422), configured to send to the initiating node a response message which comprises a cause value of tunnel management request failure and information of the local node when the local node is unable to complete the tunnel management request, wherein the local node information is information of the node that causes failure of the tunnel management request.

10. The apparatus of claim 8, wherein:

the sending unit (142) is further configured to send the tunnel management request to a remote node;

the receiving unit (141) is further configured to receive from the remote node a response message, which comprises a cause value of tunnel management request failure; and

wherein the information of a node is information of the remote node that causes the tunnel management request failure.

11. The apparatus of claim 8, wherein:

the sending unit (142) is further configured to send the tunnel management request to a remote node;

the receiving unit (141) is further configured to receive from the remote node a response message, which comprises a cause value of tunnel management request failure and node information; and

the sending unit (142) sends to the initiating node a response message which comprises the cause value of tunnel management request failure and the received node information, wherein the received node information is node information of the node that causes the tunnel management request failure.

12. The apparatus of claim 10 or 11, wherein:

the response message received from the remote node comprises additional location information for locating a missing information element, IE, or an incorrectly decoded IE, which identifies a specific reason of the tunnel management request failure; and

the response message sent by the sending unit to the initiating node comprises the additional location information.

13. A tunnel management procedure apparatus, comprising
a sending unit (151), configured to send a tunnel management request to a tunnel management node;
a receiving unit (152), configured to receive a response message from a tunnel management node that comprises a cause value indicating whether the tunnel management is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that
the response message includes node information, being information of a node that causes failure of the tunnel management request when the tunnel management request fails; and the apparatus further comprises
a searching unit (153), configured to find from the node information and correctly determine which node, out of different nodes in the tunnel management procedure, caused the failure of the tunnel management request.

14. The apparatus of claim 13, further comprising:

a processing unit (154), configured to select a new node to replace the node that causes failure of the tunnel management request when the cause of the tunnel management request failure is resource insufficiency or equipment failure; or configured to locate a specific Information Element (IE) that is missing or incorrectly decoded when the cause of the tunnel management request failure is IE missing or IE decode error.

15. A communications system, comprising:

an initiating node (161), configured to send a tunnel management request;

a tunnel management node (162), configured to receive the tunnel management request from the initiating node (161) and return a response to the initiating node (161), wherein the response comprises a cause value indicating whether the tunnel management request is successful or unsuccessful, and when unsuccessful indicates a reason, characterized in that:

the response includes node information, being information of a node that causes failure of the tunnel management request when the tunnel management request fails; and

the initiating node (161) is further configured to find from the node information and correctly determine which node out of different nodes in the tunnel management procedure caused failure of the tunnel management request

16. The system of claim 15, wherein:

the tunnel management node (162) is further configured to determine whether the tunnel management node (162) is able to complete the tunnel management request; and

if the tunnel management node (162) is unable to complete the tunnel management request, the tunnel management node (162) is further configured to send to the initiating node (161) a response message, which comprises a cause value of the tunnel management request failure and information of the tunnel management node, wherein the information of the tunnel management node is the node that causes failure of the tunnel management request.

17. The system of claim 15, further comprising a remote node (163), wherein:

the tunnel management node (162) is further configured to send the tunnel management request to the remote node (163);

the remote node (163) is configured to return to the tunnel management node (162) a response message, which comprises a cause value of tunnel management request failure; and

the tunnel management node (162) is further configured to send to the initiating node (161) a response message which comprises the cause value of tunnel management request failure and information of the remote node, wherein the information of the remote node is the node that causes failure of the tunnel management request.

18. The system of claim 15, further comprising a remote node (163), wherein:

the tunnel management node (162) is configured to send the tunnel management request to the remote node (163);

the remote node (163) is configured to return to the tunnel management node (162) a response message, which comprises a cause value of tunnel management request failure and node information; and

the tunnel management node (162) is further configured to send to the initiating node (161) a response message which comprises the cause value of tunnel management request failure and the received node information, wherein the received node information is the node that causes failure of the tunnel management request.

Ansprüche

1. Verfahren zum Bestimmen eines Knotens, der einen Ausfall in einer Tunnelmanagementprozedur verursacht, das Folgendes umfasst:

Empfangen einer Tunnelmanagementanforderung von einem einleitenden Knoten;

Senden einer Antwortnachricht an den einleitenden Knoten, wobei die Antwortnachricht einen Ursachenwert umfasst, der angibt, ob die Tunnelmanagementanforderung erfolgreich oder erfolglos ist, und die, wenn sie erfolglos ist, einen Grund angibt, dadurch gekennzeichnet, dass:

in der Antwortnachricht Informationen über einen Knoten enthalten sind, der den Ausfall der Tunnelmanagementanforderung verursacht, wenn die Tunnelmanagementanforderung fehlschlägt, wobei die Informationen die richtige Bestimmung ermöglichen, welcher Knoten aus den verschiedenen Knoten in der Tunnelmanagementprozedur den Ausfall der Tunnelmanagementanforderung verursacht hat.

2. Verfahren nach Anspruch 1, das ferner Folgendes umfasst:

Bestimmen, ob ein lokaler Knoten die Tunnelmanagementanforderung abschließen kann; wobei

falls der lokale Knoten die Tunnelmanagementanforderung nicht abschließen kann, die in der Antwortnachricht enthaltenen Knoteninformationen die Informationen über den lokalen Knoten sind.

3. Verfahren nach Anspruch 1, das ferner Folgendes umfasst:

Senden einer Tunnelmanagementanforderung an einen entfernten Knoten; und

Empfangen einer Antwortnachricht, die einen Ursachenwert des Ausfalls der Tunnelmanagementanforderung umfasst; von dem entfernten Knoten, wobei der Schritt des Sendens einer Antwortnachricht an den einleitenden Knoten das Senden einer Antwortnachricht, die den Ursachenwert des Ausfalls der Tunnelmanagementanforderung und Informationen über den entfernten Knoten umfasst, an den einleitenden Knoten umfasst, wobei die Informationen über den entfernten Knoten die Informationen über den Knoten sind, der den Ausfall der Tunnelmanagementanforderung verursacht.

4. Verfahren nach Anspruch 1, das ferner Folgendes umfasst:

Senden der Tunnelmanagementanforderung an einen entfernten Knoten; und

Empfangen einer Antwortnachricht, die einen Ursachenwert des Ausfalls der Tunnelmanagementanforderung und Knoteninformationen umfasst, von dem entfernten Knoten;

wobei der Schritt des Sendens einer Antwortnachricht, die die Knoteninformationen umfasst, an den einleitenden Knoten Folgendes umfasst: Senden einer Antwortnachricht, die den Ursachenwert des Ausfalls der Tunnelmanagementanforderung und die empfangenen Knoteninformationen umfasst, an den einleitenden Knoten, wobei die empfangenen Knoteninformationen die Informationen über den Knoten sind, der den Ausfall der Tunnelmanagementanforderung verursacht.

5. Verfahren nach Anspruch 3 oder 4, wobei:

die von dem entfernten Knoten empfangene Antwortnachricht zusätzliche Ortsinformationen zum Lokalisieren eines fehlenden Informationselements, IE, oder eines falsch decodierten IE umfasst, wobei die zusätzlichen Ortsinformationen einen spezifischen Grund des Ausfalls der Tunnelmanagementanforderung identifizieren; und

die an den einleitenden Knoten gesendete Antwortnachricht die zusätzlichen Ortsinformationen umfasst.

6. Verfahren zum Bestimmen eines Knotens, der einen Ausfall in einer Tunnelmanagementprozedur verursacht, das Folgendes umfasst:

Senden einer Tunnelmanagementanforderung an einen Tunnelmanagementknoten; Empfangen einer Antwortnachricht von dem Tunnelmanagementknoten, wobei die Antwortnachricht einen Ursachenwert umfasst, der angibt, ob die Tunnelmanagementanforderung erfolgreich oder erfolglos ist, und die, wenn sie erfolglos ist, einen Grund angibt, dadurch gekennzeichnet, dass:

in der Antwortnachricht Informationen über einen Knoten enthalten sind, der den Ausfall der Tunnelmanagementanforderung verursacht, wenn die Tunnelmanagementanforderung fehlschlägt, wobei die Informationen die richtige Bestimmung ermöglichen, welcher Knoten aus den verschiedenen Knoten in der Tunnelmanagementprozedur den Ausfall der Tunnelmanagementanforderung verursacht hat; und

Finden des Knotens, der den Ausfall der Tunnelmanagementanforderung verursacht, in Übereinstimmung mit den Knoteninformationen.

7. Verfahren nach Anspruch 6, das ferner Folgendes umfasst:

falls die Ursache des Ausfalls der Tunnelmanagementanforderung eine Betriebsmittelunzulänglichkeit oder ein Geräteausfall ist, Auswählen eines neuen Knotens, um den Knoten zu ersetzen, der den Ausfall der Tunnelmanagementanforderung verursacht; und

falls die Ursache des Ausfalls der Tunnelmanagementanforderung ein fehlendes Informationselement (IE) oder ein IE-Decodierfehler ist, Lokalisieren eines spezifischen IE, das fehlt oder falsch decodiert ist, in Übereinstimmung mit den zusätzlichen Ortsinformationen.

8. Vorrichtung für eine Tunnelmanagementprozedur, wobei die Vorrichtung Folgendes umfasst:

eine Empfangseinheit (141), die konfiguriert ist, eine Tunnelmanagementanforderung von einem einleitenden Knoten zu empfangen;

eine Sendeeinheit (142), die konfiguriert ist, eine Antwortnachricht, die einen Ursachenwert umfasst, der angibt, ob die Tunnelmanagementanforderung erfolgreich oder erfolglos ist, und die, wenn sie erfolglos ist, einen Grund angibt, an den einleitenden Knoten zu senden, dadurch gekennzeichnet, dass die Sendeeinheit ferner konfiguriert ist, Informationen eines Knotens, der den Ausfall der Tunnelmanagementanforderung verursacht, wenn die Tunnelmanagementanforderung fehlschlägt, in der Antwortnachricht zu enthalten, wobei die Informationen die richtige Bestimmung ermöglichen, welcher Knoten aus den verschiedenen Knoten in der Tunnelmanagementprozedur den Ausfall der Tunnelmanagementanforderung verursacht hat.

9. Vorrichtung nach Anspruch 8, wobei die Sendeeinheit (142) Folgendes umfasst:

ein Bestimmungsmodul (1421), das konfiguriert ist, zu bestimmen, ob ein lokaler Knoten die Tunnelmanagementanforderung abschließen kann; und

ein Sendemodul (1422), das konfiguriert ist, eine Antwortnachricht an den einleitenden Knoten zu senden, die einen Ursachenwert des Ausfalls der Tunnelmanagementanforderung und Informationen über den lokalen Knoten umfasst, wenn der lokale Knoten die Tunnelmanagementanforderung nicht abschließen kann, wobei die Informationen über den lokalen Knoten die Informationen über den Knoten sind, der den Ausfall der Tunnelmanagementanforderung verursacht.

10. Vorrichtung nach Anspruch 8, wobei:

die Sendeeinheit (142) ferner konfiguriert ist, die Tunnelmanagementanforderung an einen entfernten Knoten zu senden;

die Empfangseinheit (141) ferner konfiguriert ist, eine Antwortnachricht, die einen Ursachenwert des Ausfalls der Tunnelmanagementanforderung umfasst, von dem entfernten Knoten zu empfangen; und

wobei die Informationen über einen Knoten die Informationen über den entfernten Knoten sind, der den Ausfall der Tunnelmanagementanforderung verursacht.

11. Vorrichtung nach Anspruch 8, wobei
die Sendeeinheit (142) ferner konfiguriert ist, die Tunnelmanagementanforderung an einen entfernten Knoten zu senden;
die Empfangseinheit (141) ferner konfiguriert ist, eine Antwortnachricht, die einen Ursachenwert des Ausfalls der Tunnelmanagementanforderung und Knoteninformationen umfasst, von dem entfernten Knoten zu empfangen; und
die Sendeeinheit (142) eine Antwortnachricht, die den Ursachenwert des Ausfalls der Tunnelmanagementanforderung und die empfangenen Knoteninformationen umfasst, an den einleitenden Knoten sendet, wobei die empfangenen Knoteninformationen die Knoteninformationen über den Knoten sind, der den Ausfall der Tunnelmanagementanforderung verursacht.

12. Vorrichtung nach Anspruch 10 oder 11, wobei:

die von dem entfernten Knoten empfangene Antwortnachricht zusätzliche Ortsinformationen zum Lokalisieren eines fehlenden Informationselements, IE, oder

eines falsch decodierten IE umfasst, die einen spezifischen Grund des Ausfalls der Tunnelmanagementanforderung identifizieren; und

die durch die Sendeeinheit an den einleitenden Knoten gesendete Antwortnachricht die zusätzlichen Ortsinformationen umfasst.

13. Vorrichtung für eine Tunnelmanagementprozedur, wobei die Vorrichtung Folgendes umfasst
eine Sendeeinheit (151), die konfiguriert ist, eine Tunnelmanagementanforderung an einen Tunnelmanagementknoten zu senden;
eine Empfangseinheit (152), die konfiguriert ist, eine Antwortnachricht, die einen Ursachenwert umfasst, der angibt, ob das Tunnelmanagement erfolgreich oder erfolglos ist, und die, wenn es erfolglos ist, einen Grund angibt, von einem Tunnelmanagementknoten zu empfangen, dadurch gekennzeichnet, dass
die Antwortnachricht Knoteninformationen enthält, die die Informationen über einen Knoten sind, der den Ausfall der Tunnelmanagementanforderung verursacht, wenn die Tunnelmanagementanforderung fehlschlägt, wobei die Vorrichtung ferner Folgendes umfasst
eine Sucheinheit (153), die konfiguriert ist, aus den Knoteninformationen zu finden und richtig zu bestimmen, welcher Knoten aus den verschiedenen Knoten in der Tunnelmanagementprozedur den Ausfall der Tunnelmanagementanforderung verursacht hat.

14. Vorrichtung nach Anspruch 13, die ferner Folgendes umfasst:

eine Verarbeitungseinheit (154), die konfiguriert ist, einen neuen Knoten auszuwählen, um den Knoten zu ersetzen, der den Ausfall der Tunnelmanagementanforderung verursacht, wenn die Ursache des Ausfalls der Tunnelmanagementanforderung eine Betriebsmittelunzulänglichkeit oder ein Geräteausfall ist, oder die konfiguriert ist, ein spezifisches Informationselement (IE) zu lokalisieren, das fehlt oder falsch decodiert ist, wenn die Ursache des Ausfalls der Tunnelmanagementanforderung ein fehlendes IE oder ein IE-Decodierfehler ist.

15. Kommunikationssystem, das Folgendes umfasst,
einen einleitenden Knoten (161), der konfiguriert ist, eine Tunnelmanagementanforderung zu senden;
einen Tunnelmanagementknoten (162), der konfiguriert ist, die Tunnelmanagementanforderung von dem einleitenden Knoten (161) zu empfangen und eine Antwort an den einleitenden Knoten (161) zurückzusenden, wobei die Antwort einen Ursachenwert umfasst, der angibt, ob die Tunnelmanagementanforderung erfolgreich oder erfolglos ist, und die, wenn sie erfolglos ist, einen Grund angibt, dadurch gekennzeichnet, dass
die Antwort Knoteninformationen enthält, die die Informationen über einen Knoten sind, der den Ausfall der Tunnelmanagementanforderung verursacht, wenn die Tunnelmanagementanforderung fehlschlägt; und
der einleitende Knoten (161) ferner konfiguriert ist, aus den Knoteninformationen zu finden und richtig zu bestimmen, welcher Knoten aus den verschiedenen Knoten in der Tunnelmanagementprozedur den Ausfall der Tunnelmanagementanforderung verursacht hat.

16. System nach Anspruch 15, wobei:

der Tunnelmanagementknoten (162) ferner konfiguriert ist, zu bestimmen, ob der Tunnelmanagementknoten (162) die Tunnelmanagementanforderung abschließen kann; und

falls der Tunnelmanagementknoten (162) die Tunnelmanagementanforderung nicht abschließen kann, der Tunnelmanagementknoten (162) ferner konfiguriert ist, eine Antwortnachricht, die einen Ursachenwert des Ausfalls der Tunnelmanagementanforderung und Informationen über den Tunnelmanagementknoten umfasst, an den einleitenden Knoten (161) zu senden, wobei die Informationen über den Tunnelmanagementknoten den Knoten angeben, der den Ausfall der Tunnelmanagementanforderung verursacht.

17. System nach Anspruch 15, das ferner einen entfernten Knoten (163) umfasst, wobei:

der Tunnelmanagementknoten (162) ferner konfiguriert ist, die Tunnelmanagementanforderung an den entfernten Knoten (163) zu senden; der entfernte Knoten (163) konfiguriert ist, eine Antwortnachricht, die einen Ursachenwert des Ausfalls der Tunnelmanagementanforderung umfasst, an den Tunnelmanagementknoten (162) zurückzusenden; und

der Tunnelmanagementknoten (162) ferner konfiguriert ist, eine Antwortnachricht, die den Ursachenwert des Ausfalls der Tunnelmanagementanforderung und Informationen über den entfernten Knoten umfasst, an den einleitenden Knoten (161) zu senden, wobei die Informationen über den entfernten Knoten den Knoten angeben, der den Ausfall der Tunnelmanagementanforderung verursacht.

18. System nach Anspruch 15, das ferner einen entfernten Knoten (163) umfasst, wobei:

der Tunnelmanagementknoten (162) konfiguriert ist, die Tunnelmanagementanforderung an den entfernten Knoten (163) zu senden;

der entfernte Knoten (163) konfiguriert ist, eine Antwortnachricht, die einen Ursachenwert des Ausfalls der Tunnelmanagementanforderung und Knoteninformationen umfasst, an den Tunnelmanagementknoten (162) zurückzusenden; und

der Tunnelmanagementknoten (162) ferner konfiguriert ist, eine Antwortnachricht, die den Ursachenwert des Ausfalls der Tunnelmanagementanforderung und die empfangenen Knoteninformationen umfasst, an den einleitenden Knoten (161) zu senden, wobei die empfangenen Knoteninformationen den Knoten angeben, der den Ausfall der Tunnelmanagementanforderung verursacht.

Revendications

1. Procédé de détermination d'un noeud causant l'échec d'une procédure de gestion de tunnel, comprenant :

la réception d'une requête de gestion de tunnel depuis un noeud de lancement ;

l'envoi d'un message de réponse au noeud de lancement, le message de réponse comprenant une valeur de cause indiquant si la requête de gestion de tunnel aboutit ou non, et quand elle n'aboutit pas, indiquant une raison, caractérisé en ce que :

dans le message de réponse sont incluses des informations d'un noeud qui cause l'échec de la requête de gestion de tunnel quand la requête de gestion de tunnel échoue, les informations permettant la détermination correcte du noeud, parmi les différents noeuds dans la procédure de gestion de tunnel, qui a causé l'échec de la requête de gestion de tunnel.

2. Procédé selon la revendication 1, comprenant en outre :

la détermination qu'un noeud local est en mesure ou non de satisfaire à la requête de gestion de tunnel ; et

si le noeud local n'est pas en mesure de satisfaire à la requête de gestion de tunnel, les informations de noeud comprises dans le message de réponse sont des informations du noeud local.

3. Procédé selon la revendication 1, comprenant en outre :

l'envoi de la requête de gestion de tunnel à un noeud distant ; et

la réception depuis le noeud distant d'un message de réponse, lequel comprend une valeur de cause d'échec de la requête de gestion de tunnel ; dans lequel l'étape d'envoi au noeud de lancement d'un message de réponse comprend l'envoi au noeud de lancement d'un message de réponse qui comprend la valeur de cause de l'échec de la requête de gestion de tunnel et des informations du noeud distant, les informations du noeud distant étant des informations du noeud qui cause l'échec de la requête de gestion de tunnel.

4. Procédé selon la revendication 1, comprenant en outre:

l'envoi de la requête de gestion de tunnel à un noeud distant ; et

la réception depuis le noeud distant d'un message de réponse, lequel comprend une valeur de cause d'échec de la requête de gestion de tunnel et des informations de noeud;

l'étape d'envoi au noeud de lancement d'un message de réponse qui comprend des informations de noeud comprend : l'envoi au noeud de lancement d'un message de réponse qui comprend la valeur de cause d'échec de la requête de gestion de tunnel et

les informations de noeud reçues, les informations de noeud reçues étant des informations du noeud qui cause l'échec de la requête de gestion de tunnel.

5. Procédé selon la revendication 3 ou 4, dans lequel :

le message de réponse reçu depuis le noeud distant comprend des informations de position supplémentaires pour localiser un élément d'information, IE, manquant, ou

un IE décodé incorrectement, les informations de position supplémentaires identifiant une raison spécifique de l'échec de la requête de gestion de tunnel ; et

le message de réponse envoyé au noeud de lancement comprend les informations de position supplémentaires.

6. Procédé de détermination d'un noeud causant l'échec d'une procédure de gestion de tunnel, comprenant :

l'envoi d'une requête de gestion de tunnel à un noeud de gestion de tunnel ;

la réception depuis le noeud de gestion de tunnel d'un message de réponse, le message de réponse comprenant une valeur de cause indiquant si la requête de gestion de tunnel aboutit ou non, et quand elle n'aboutit pas, indiquant une raison, caractérisé en ce que :

dans le message de réponse sont incluses des informations d'un noeud qui cause l'échec de la requête de gestion de tunnel quand la requête de gestion de tunnel n'aboutit pas, les informations permettant la détermination correcte du noeud, parmi les différents noeuds dans la procédure de gestion de tunnel, qui a causé l'échec de la requête de gestion de tunnel ; et

la recherche du noeud qui cause l'échec de la requête de gestion de tunnel en fonction des informations de noeud.

7. Procédé selon la revendication 6, comprenant en outre :

si la cause de l'échec de la requête de gestion de tunnel est une insuffisance de ressources ou une panne d'équipement, la sélection d'un nouveau noeud pour remplacer le noeud qui cause l'échec de la requête de gestion de tunnel ; et

si la cause de l'échec de la requête de gestion de tunnel est l'absence d'un Elément d'Information (IE) ou une erreur de décodage d'IE, la localisation d'un IE spécifique manquant ou incorrectement décodé en fonction d'informations de position supplémentaires.

8. Appareil pour procédure de gestion de tunnel, comprenant :

une unité de réception (141), configurée pour recevoir une requête de gestion de tunnel depuis un noeud de lancement ;

une unité d'envoi (142), configurée pour envoyer au noeud de lancement un message de réponse, lequel comprend une valeur de cause indiquant si la requête de gestion de tunnel aboutit ou non, et quand elle n'aboutit pas, indiquant une raison, caractérisé en ce que l'unité d'envoi est configurée en outre pour inclure dans le message de réponse des informations d'un noeud qui cause l'échec de la requête de gestion de tunnel quand la requête de gestion de tunnel échoue, les informations permettant la détermination correcte du noeud, parmi les différents noeuds dans la procédure de gestion de tunnel, qui a causé l'échec de la requête de gestion de tunnel.

9. Appareil selon la revendication 8, dans lequel l'unité d'envoi (142) comprend :

un module de détermination (1421), configuré pour déterminer qu'un noeud local est en mesure ou non de satisfaire à la requête de gestion de tunnel ; et

un module d'envoi (1422), configuré pour envoyer au noeud de lancement un message de réponse qui comprend une valeur de cause de l'échec de la requête de gestion de tunnel et des informations du noeud local quand le noeud local n'est pas en mesure de satisfaire à la requête de gestion de tunnel, les informations du noeud local étant des informations du noeud qui cause l'échec de la requête de gestion de tunnel.

10. Appareil selon la revendication 8, dans lequel :

l'unité d'envoi (142) est configurée en outre pour envoyer la requête de gestion de tunnel à un noeud distant ;

l'unité de réception (141) est configurée en outre pour recevoir depuis le noeud distant un message de réponse, lequel comprend une valeur de cause de l'échec de la requête de gestion de tunnel ; et

dans lequel les informations d'un noeud sont des informations du noeud distant qui cause l'échec de la requête de gestion de tunnel.

11. Appareil selon la revendication 8, dans lequel :

l'unité d'envoi (142) est configurée en outre pour envoyer la requête de gestion de tunnel à un noeud distant ;

l'unité de réception (141) est configurée en outre pour recevoir depuis le noeud distant un message de réponse, lequel comprend une valeur de cause de l'échec de la requête de gestion de tunnel et des informations de noeud ; et

l'unité d'envoi (142) envoie au noeud de lancement un message de réponse qui comprend la valeur de cause de l'échec de la requête de gestion de tunnel et les informations de noeud reçues, les informations de noeud reçues étant des informations de noeud du noeud qui cause l'échec de la requête de gestion de tunnel.

12. Appareil selon la revendication 10 ou 11, dans lequel :

le message de réponse reçu depuis le noeud distant comprend des informations de position supplémentaires pour localiser un élément d'information, IE, manquant, ou

un IE décodé incorrectement, lesquelles identifient une raison spécifique de l'échec de la requête de gestion de tunnel ; et

le message de réponse envoyé par l'unité d'envoi au noeud de lancement comprend les informations de position supplémentaires.

13. Appareil pour procédure de gestion de tunnel, comprenant :

une unité d'envoi (151), configurée pour envoyer une requête de gestion de tunnel à un noeud de gestion de tunnel ;

une unité de réception (152), configurée pour recevoir d'un noeud de gestion de tunnel un message de réponse qui comprend une valeur de cause indiquant si la gestion de tunnel aboutit ou non, et quand elle n'aboutit pas, indique une raison, caractérisé en ce que

le message de réponse comporte des informations de noeud, celles-ci étant des informations d'un noeud qui cause l'échec de la requête de gestion de tunnel quand la requête de gestion de tunnel échoue ; et l'appareil comprenant en outre une unité de recherche (153), configurée pour trouver, à partir des informations de noeud, et déterminer correctement le noeud, parmi les différents noeuds dans la procédure de gestion de tunnel, qui a causé l'échec de la requête de gestion de tunnel.

14. Appareil selon la revendication 13, comprenant en outre :

une unité de traitement (154), configurée pour sélectionner un nouveau noeud pour remplacer le noeud qui cause l'échec de la requête de gestion de tunnel quand la cause de l'échec de la requête de gestion de tunnel est une insuffisance de ressources ou une panne d'équipement ; ou configurée pour localiser un Elément d'Information (IE) spécifique manquant ou incorrectement décodé quand la cause de l'échec de la requête de gestion de tunnel est l'absence d'un IE ou une erreur de décodage d'IE.

15. Système de communications, comprenant :

un noeud de lancement (161), configuré pour envoyer une requête de gestion de tunnel ;

un noeud de gestion de tunnel (162), configuré pour recevoir la requête de gestion de tunnel depuis le noeud de lancement (161) et renvoyer une réponse au noeud de lancement (161), la réponse comprenant une valeur de cause indiquant si la requête de gestion de tunnel aboutit ou non, et quand elle n'aboutit pas, indiquant une raison, caractérisé en ce que :

la réponse comporte des informations de noeud, celles-ci étant des informations d'un noeud qui cause l'échec de la requête de gestion de tunnel quand la requête de gestion de tunnel échoue ; et

le noeud de lancement (161) est configuré en outre pour trouver, à partir des informations de noeud, et déterminer correctement le noeud, parmi les différents noeuds dans la procédure de gestion de tunnel, qui a causé l'échec de la requête de gestion de tunnel.

16. Système selon la revendication 15, dans lequel :

le noeud de gestion de tunnel (162) est configuré en outre pour déterminer que le noeud de gestion de tunnel (162) est en mesure ou non de satisfaire à la requête de gestion de tunnel ; et

si le noeud de gestion de tunnel (162) n'est pas en mesure de satisfaire à la requête de gestion de tunnel, le noeud de gestion de tunnel (162) est configuré en outre pour envoyer au noeud de lancement (161) un message de réponse, lequel comprend une valeur de cause de l'échec de la requête de gestion de tunnel et des informations du noeud de gestion de tunnel, les informations du noeud de gestion de tunnel étant le noeud qui cause l'échec de la requête de gestion de tunnel.

17. Système selon la revendication 15, comprenant en outre un noeud distant (163), dans lequel :

le noeud de gestion de tunnel (162) est configuré en outre pour envoyer la requête de gestion de tunnel au noeud distant (163) ;

le noeud distant (163) est configuré pour renvoyer au noeud de gestion de tunnel (162) un message de réponse, lequel comprend une valeur de cause de l'échec de la requête de gestion de tunnel ; et

le noeud de gestion de tunnel (162) est configuré en outre pour envoyer au noeud de lancement (161) un message de réponse qui comprend la valeur de cause de l'échec de la requête de gestion de tunnel et des informations du noeud distant, les informations du noeud distant étant le noeud qui cause l'échec de la requête de gestion de tunnel.

18. Système selon la revendication 15, comprenant en outre un noeud distant (163), dans lequel :

le noeud de gestion de tunnel (162) est configuré pour envoyer la requête de gestion de tunnel au noeud distant (163) ;

le noeud distant (163) est configuré pour renvoyer au noeud de gestion de tunnel (162) un message de réponse, lequel comprend une valeur de cause de l'échec de la requête de gestion de tunnel et des informations de noeud ; et

le noeud de gestion de tunnel (162) est configuré en outre pour envoyer au noeud de lancement (161) un message de réponse qui comprend la valeur de cause de l'échec de la requête de gestion de tunnel et les informations de noeud reçues, les informations de noeud reçues étant le noeud qui cause l'échec de la requête de gestion de tunnel.

Drawing