Resilient network database
This invention relates to methods and apparatus for providing a resilient network database. The invention relates particularly, but not exclusively, to the IP Multimedia Subsystem (IMS). The invention is directed to an interface for a database node comprising: a port for receiving a request for information from a network node; a processor for determining if the database node can respond to said request; and a transmitter for forwarding the request to another database node if the particular database node cannot respond. The invention is also directed to a distributed database comprising a number of database nodes, wherein a request received by one node is forwarded to other nodes in the distributed database if the particular node cannot handle the request.
1. A Home Subscriber Server (HSS) database node comprising:
an application processing layer configured to provide HSS functionality specific to the HSS database node; and
an interface for connection to an Internet Protocol (IP) network, wherein the interface is isolated from the application processing layer, and wherein the interface comprises:
a port configured to receive a request for information from a network node connected to said IP network;
a processor configured to determine if said HSS database node can respond to said request using the application processing layer; and
a transmitter configured to forward the request to another HSS database node if said HSS database node cannot respond to the request for information on the IP network.
2. the HSS database node according to claim 1 , wherein:
said processor is configured to further obtain said information from said application processing layer if said HSS database node can respond to said request;
said port is configured to further receive said information from said another HSS database node if said HSS database node cannot respond to said request; and
said transmitter is configured to further send said information to said network node.
3. the HSS database node according to claim 1 , wherein said request is a Server Assignment Request.
4. the HSS database node according to claim 1 , wherein said transmitter is configured to forward said request using a Diameter application.
5. the HSS database node according to claim 1 , wherein said transmitter is configured to further send status information to said another HSS database node.
6. the HSS database node according to claim 5 , wherein said transmitter is configured to further share said status information with remote network nodes.
7. the HSS database node according to claim 1 , wherein said transmitter is configured to further send routing information to said another HSS database node.
8. the HSS database node according to claim 1 , wherein said HSS database node is arranged to store information for a number of subscribers such that information for a particular subscriber is stored on at least two of a plurality of HSS database nodes.
9. the HSS database node according to claim 1 , configured to interact with the other HSS database node to avoid deployment of a service location function (SLF) in said IP network.
10. A distributed Home Subscriber Server (HSS) database comprising a plurality of distributed HSS database nodes, each of said plurality of distributed HSS database nodes comprising:
a database core comprising an application processing layer configured to provide HSS functionality specific to each HSS database node; and
an interface for connection to an Internet Protocol (IP) network, wherein the interface is separate from the database core, the interface comprising:
a port configured to receive a request for information from a network node connected to said network;
a processor configured to determine if said one distributed HSS database node can respond to said request using the database core; and
a transmitter configured to forward the request to another one of said plurality of distributed HSS database nodes if said one distributed HSS database node cannot respond on the IP network.
11. the distributed database according to claim 10 , wherein said plurality of distributed HSS database nodes are geographically dispersed.
12. the distributed database according to claim 10 , wherein said IP network comprises a home realm of a single network operator.
13. the distributed HSS database according to claim 10 , wherein each of said plurality of HSS database nodes is arranged to store information for a number of subscribers such that information for a particular subscriber is stored on at least two of said plurality of HSS database nodes.
14. the distributed HSS database according to claim 10 , wherein the plurality of HSS database nodes are configured to interact to avoid deployment of a service location function (SLF) in the IP network.
15. A method of operating a Home Subscriber Server (HSS) database node connected to an Internet Protocol (IP) network, comprising:
receiving, by an interface of said HSS database node, a request for information from a network node connected to said IP network;
determining, by the interface of said HSS database node, if an application processing layer of said HSS database node can respond to said request, wherein the application processing layer is separate from the interface; and
forwarding, by the interface of said HSS database node, the request to another HSS database node if said HSS database node cannot respond on the IP network.
16. the method of operating said HSS database node according to claim 15 , further comprising:
if said HSS database node can respond to said request, obtaining said information from said HSS database node;
if said HSS database node cannot respond to said request, receiving said information from said another HSS database node; and
sending said information to said network node.
17. the method of operating said HSS database node according to claim 15 , further comprising sending status information to said another HSS database node.
18. A method of operating the HSS database node according to claim 17 , further comprising sending said status information to other nodes in the network.
19. the method of operating the HSS database node according to claim 17 , further comprising sending said status information to other nodes in the IP network.
20. the method of operating said HSS database node according to claim 15 , further comprising receiving one of status and routing information from other HSS database nodes.
21. the method according to claim 15 , wherein said HSS database node is arranged to store information for a number of subscribers such that information for a particular subscriber is stored on at least two of a plurality of HSS database nodes.
22. the method according to claim 15 , further comprising arranging said HSS database node to communicate with other HSS database nodes avoids deployment of a service location function (SLF) in the IP network.