System and method for rejecting a request to alter a connection

• US 7,986,623 B2
• Filed: 06/18/2007
• Issued: 07/26/2011
• Est. Priority Date: 10/16/2006
• Status: Active Grant

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Bardalai, Snigdho Chandra
• Primary Examiner(s): Yao; Kwang B
• Assistant Examiner(s): Bokhari; Syed M
• Application Number:
  US11/764,525
• Publication Number:
  US 20080112322A1
• Time in Patent Office: 1,499 Days
• Field of Search: 370/389, 370/228, 370/338, 709/238, 709/227, 714/4, 455/452
• US Class Current: 370/230
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/724 at intermediate nodes, e.g. resource reservation protocol [RSVP]
• CPC Class Codes: H04L 47/762 triggered by the network
• CPC Class Codes: H04L 47/765 triggered by the end-points

Abstract

A method for rejecting a request to alter a connection includes establishing a first connection with a first node and a second connection with a second node. The second connection passes through the first node and has an associated first end-to-end state. The method also includes transmitting, for relay by the first node to the second node, a first request to alter the second connection with the second node so that the second connection will have an associated second end-to-end state. The method additionally includes receiving a rejection message from the first node indicating that the first request to alter the second connection failed. The method further includes transmitting a second request to alter the second connection with the second node to ensure that the second connection is again in the associated first end-to-end state.

Claims

1. a method for rejecting a request to alter a connection, comprising:

establishing a first connection with a first node of a network at a third node of the network;

establishing a second connection with a second node of the network at the third node of the network, the second connection passing through the first node and having an associated first end-to-end state;

transmitting from the third node, for relay by the first node to the second node, a first request to alter the second connection with the second node so that the second connection will have an associated second end-to-end state, wherein the first request to alter the second connection comprises a first request selected from the group consisting of a request to delete the second connection and a request to perform an administrative modification to the second connection;

at the third node, receiving a rejection message from the first node indicating that the first request to alter the second connection failed; and

transmitting from the third node a second request to alter the second connection with the second node to revert the second connection back to the associated first end-to-end state in the case that one of the nodes made changes to the end-to-end state in anticipation of the failed request to alter the second connection.

2. The method of claim 1, wherein the rejection message comprises at least one field with a value that is complimentary to a value within at least one corresponding field in the first request.

3. The method of claim 1, wherein the rejection message is received within a first amount of time after the first request was transmitted.

4. The method of claim 1, wherein the rejection message comprises an ErrorSpec Type Length Value field having a first value.

5. A method for rejecting a request to alter a connection, comprising:

establishing a first connection with a first node of a network at a third node of the network and establishing a second connection with a second node of the network at the third node of the network, wherein the first node and the second node have established a third connection with each other, the third connection having an associated first end-to-end state;

at the third node, receiving from the first node a first request to alter the third connection between the first node and the second node so that the third connection will have an associated second end-to-end state, wherein the first request to alter the third connection comprises a first request selected from the group consisting of a request to delete the third connection and a request to perform an administrative modification to the third connection;

transmitting the first request to the second node from the third node;

upon determining that the first request failed, transmitting from the third node a rejection message to the first node indicating that the first request to alter the third connection failed; and

at the third node, receiving a second request to alter the third connection between the first node and the second node to revert the third connection back to the associated first end-to-end state in the case that one of the nodes made changes to the end-to-end state in anticipation of the failed request to alter the third connection.

6. The method of claim 5:

further comprising;

determining the cause of the failure of the first request; and

generating a value to be used with an ErrorSpec Type Length Value field in the rejection message; and

wherein transmitting a rejection message to the first node comprises transmitting a rejection message with the value in the ErrorSpec Type Length Value field to the first node.

7. A system for rejecting a request to alter a connection, comprising:

an interface operable to;

establish a first connection with a first node; and

establish a second connection with a second node, the second connection passing through the first node and having an associated first end-to-end state; and

a processor coupled to the interface and operable to transmit, for relay by the first node to the second node, a first request to alter the second connection with the second node so that the second connection will have an associated second end-to-end state, wherein the first request to alter the second connection comprises a first request selected from the group consisting of a request to delete the second connection and a request to perform an administrative modification to the second connection; and

wherein;

the interface is further operable to receive a rejection message from the first node indicating that the first request to alter the second connection failed; and

the processor is further operable to transmit a second request to alter the second connection with the second node to revert the second connection back to the associated first end-to-end state in the case that one of the nodes made changes to the end-to-end state in anticipation of the failed request to alter the second connection.

8. The system of claim 7, wherein the rejection message comprises at least one field with a value that is complimentary to a value within at least one corresponding field in the first request.

9. The system of claim 7, wherein the rejection message is received within a first amount of time after the first request was transmitted.

10. The system of claim 7, wherein the rejection message comprises an ErrorSpec Type Length Value field having a first value.

11. The system of claim 7, wherein the first request to alter the second connection comprises a first request selected from the group consisting of a request to delete the second connection and a request to perform an administrative modification to the second connection.

12. A system for rejecting a request to alter a connection, comprising:

an interface operable to;

establish a first connection with a first node and establishing a second connection with a second node, wherein the first node and the second node have established a third connection with each other, the third connection having an associated first end-to-end state; and

receive from the first node a first request to alter the third connection between the first node and the second node so that the third connection will have an associated second end-to-end state, wherein the first request to alter the third connection comprises a first request selected from the group consisting of a request to delete the third connection and a request to perform an administrative modification to the third connection; and

a processor coupled to the interface and operable to;

transmit the first request to the second node; and

upon determining that the first request failed, transmit a rejection message to the first node indicating that the first request to alter the third connection failed; and

wherein the interface is further operable to receive a second request to alter the third connection between the first node and the second node to revert the third connection back to the associated first end-to-end state in the case that one of the nodes made changes to the end-to-end state in anticipation of the failed request to alter the third connection.

13. The system of claim 12 wherein:

the processor is further operable to;

determine the cause of the failure of the first request; and

generate a value to be used with an ErrorSpec Type Length Value field in the rejection message; and

wherein the processor operable to transmit a rejection message to the first node comprises a processor operable to transmit a rejection message with the value in the ErrorSpec Type Length Value field to the first node.