System and Method for Rejecting a Request to Alter a Connection

• US 20080112322A1
• Filed: 06/18/2007
• Published: 05/15/2008
• Est. Priority Date: 10/16/2006
• Status: Active Grant

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Network Communications Incorporated (Fujitsu Limited)
• Inventors: Bardalai, Snigdho Chandra
• Granted Patent: US 7,986,623 B2
• Time in Patent Office: Days
• US Class Current: 370/235
• 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;

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

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;

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

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.

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. The method of claim 1, 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.

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

establishing 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;

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;

transmitting the first request to the second node;

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

receiving a second request to alter the third connection between the first node and the second node to ensure that the third connection is again in the associated first end-to-end state.

7. The method of claim 6:

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.

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

establishing 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;

transmitting a first request to alter the third connection between the first node and the second node;

upon a first amount of time after the first request was transmitted having elapsed without receiving a response from the first node, transmitting a second request to alter the third connection between the first node and the second node; and

receiving a response from the first node indicating the first node is able to comply with the requested alteration.

9. 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; 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 ensure that the second connection is again in the associated first end-to-end state.

10. The system of claim 9, 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.

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

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

13. The system of claim 9, 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.

14. 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; 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 ensure that the third connection is again in the associated first end-to-end state.

15. The system of claim 14 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.

16. 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; and

a processor coupled to the interface and operable to;

transmit a first request to alter the third connection between the first node and the second node; and

upon a first amount of time after the first request was transmitted having elapsed without receiving a response from the first node, transmit a second request to alter the third connection between the first node and the second node; and

wherein the interface is further operable to receive a response from the first node indicating the first node is able to comply with the requested alteration.