Resilience Solution for Top Tier Bandwidth Managers

1 . A back up top tier bandwidth manager adapted to back up a top tier bandwidth manager upon fail-over of the top tier bandwidth manager in an Internet Protocol, IP, network, wherein said IP network comprises the top tier bandwidth manager comprising a resource map and being adapted to pre-allocate resources in bulk from a bottom tier of said IP network via a bottom-tier bandwidth manager also located in said IP network, the back up top tier bandwidth manager is wherein it comprises a copy of the resource map of the top tier bandwidth manager which it is backing up and means for synchronising states with the bottom tier bandwidth manager upon fail-over of the top tier bandwidth manager.

2 . The back up top tier bandwidth manager according to claim 1 , wherein it comprises means for performing fail-over from a failed top tier bandwidth manager by IP address takeover, wherein the backup top tier bandwidth manager comprises means for taking over the IP address of said failed top tier bandwidth manager as the routing protocol in use announce the new route to this IP address

3 . The back up top tier bandwidth manager according to claim 1 , wherein it comprises means for performing fail-over from a failed top tier bandwidth manager by configuring the clients with a primary and a secondary address.

4 . The back up top tier bandwidth manager according to claim 1 , wherein one of the states to be synchronised is the already admitted and active calls call.

5 . The back up top tier bandwidth manager according to claim 1 , wherein one of states is the pre-allocated bulk resources.

6 . The back up top tier bandwidth manager according to claim 1 , wherein it comprises a separate connection or a buffer to a client wherein the separate connection or the buffer is adapted to transfer call state synchronisation in parallel with normal operation.

7 . The back up top tier bandwidth manager according to claim 6 , characterised by means for handling new calls immediately while already admitted calls are refreshed at a slower timescale.

8 . The back up top tier bandwidth manager according to claim 6 , wherein for completing full synchronization before dealing with new call attempts.

9 . The back up top tier bandwidth manager according to claim 6 , wherein for skipping synchronization.

10 . The back up top tier bandwidth manager according to claim 6 , wherein for re-freshing active calls periodically.

11 . The back up top tier bandwidth manager according to claim 1 , wherein the top tier is the access layer and that the top tier bandwidth manager is an access bandwidth manager and that the back up top tier bandwidth manager is a back up access bandwidth manager.

12 . The back up top tier bandwidth manager according to claim 1 , wherein the bottom tier is the core network and that the bottom tier bandwidth manager is a core bandwidth manager.

13 . An Internet Protocol, IP, network comprising a top tier bandwidth manager comprising a resource map and being adapted to pre-allocate resources in bulk from a bottom tier of said IP network via a bottom-tier bandwidth manager also located in said IP network, the IP network comprises further a back up top tier bandwidth manager adapted to back up the top tier bandwidth manager upon fail-over of the top tier bandwidth manager, the network is wherein the back up top tier bandwidth manager comprises a copy of the resource map of the top tier bandwidth manager which it is backing up and means for synchronising states with the bottom tier bandwidth manager upon fail-over of the top tier bandwidth manager.

14 . The network according to claim 13 , wherein it comprises means for performing fail-over from a failed top tier bandwidth manager by IP address takeover, wherein the backup top tier bandwidth manager comprises means for taking over the IP address of said failed top tier bandwidth manager as the routing protocol in use announce the new route to this IP address

15 . The network according to claim 13 , wherein it comprises means for performing fail-over from a failed top tier bandwidth manager by configuring the clients with a primary and a secondary address.

16 . The network according to claim 13 , wherein one of the states to be synchronised is the already admitted and active calls call.

17 . The network according to claim 13 , wherein that one of the states to be synchronised is the pre-allocated bulk resources.

18 . The network according to claim 13 , wherein the back up top tier bandwidth manager comprises a separate connection or a buffer to a client wherein the separate connection or the buffer is adapted to transfer call state synchronisation in parallel with normal operation.

19 . The network according to claim 18 , wherein for handling new calls immediately while already admitted calls are refreshed at a slower timescale.

20 . The network according to claim 19 , wherein for completing full synchronization before dealing with new call attempts.

21 . The network according to claim 19 , wherein for skipping synchronization.

22 . The network according to claim 19 , wherein for re-freshing active calls periodically.

23 . The network according to claim 13 , wherein the top tier is the access layer and that the top tier bandwidth manager is an access bandwidth manager and that the back up top tier bandwidth manager is a back up access bandwidth manager.

24 . The network according to claim 12 , wherein the bottom tier is the core network and that the bottom tier bandwidth manager is a core bandwidth manager.