Systems and methods for selecting serving gateways to service user equipment
Some embodiments provide methods for selecting a serving gateway to service user equipment in communication with a network, including: receiving a message from a base transceiver station including a list of tracking areas handled by the base transceiver station, initiating a domain name system query for at least one tracking area in the list of tracking areas to identify information indicating a serving gateway serving the at least one tracking area, storing, in local memory, the information indicating the serving gateway serving the at least one tracking area, and upon an occurrence of a triggering event, retrieving, from the local memory, the stored information indicating the serving gateway serving the at least one tracking area.
1. A method for selecting a serving gateway to service user equipment in communication with a network, comprising:
receiving a message from a base transceiver station including a list of tracking areas handled by the base transceiver station;
initiating a domain name system query for at least one tracking area in the list of tracking areas to identify information indicating a serving gateway serving the at least one tracking area;
storing, in local memory, the information indicating the serving gateway serving the at least one tracking area, which includes storing the information as at least part of a table of sets of tracking area identities and at least one associated serving gateway; and
upon an occurrence of a triggering event, retrieving, from the local memory, the stored information indicating the serving gateway serving the at least one tracking area.
2. The method of claim 1 , wherein the message from the base transceiver station including the list of tracking areas includes an S1 setup message.
3. The method of claim 1 , wherein, for at least some tracking area identities, there is one and only one associated serving gateway.
4. The method of claim 1 , wherein at least some serving gateways are associated with more than one tracking area identifier.
5. The method of claim 1 , wherein the triggering event includes a receipt of an attach request from the base transceiver station identifying the user equipment and a tracking area from which the user equipment is connected to the network.
6. The method of claim 5 , wherein the attach request includes an S1 initial user equipment message.
7. The method of claim 1 , wherein the base transceiver station includes an evolved nodeB.
8. The method of claim 1 , further comprising periodically initiating the domain name system query for the at least one tracking area to periodically update the stored information indicating the serving gateway serving the at least one tracking area.
9. The method of claim 1 , wherein initiating the domain name system query for the at least one tracking area includes initiating the domain name system query using a tracking area identity fully qualified domain name associated with the at least one tracking area.
10. A mobility management entity in a communication network comprising:
memory;
an interface configured to receive a message from a base transceiver station including a list of tracking areas handled by the base transceiver station, to initiate a domain name system query for at least one tracking area in the list of tracking areas to identify information indicating a serving gateway serving the at least one tracking area;
wherein the mobility management entity is configured to store, in the memory, the information indicating the serving gateway serving the at least one tracking area as at least part of a table of sets of tracking area identities and at least one associated serving gateway, and upon an occurrence of a triggering event, retrieving, from the memory, the stored information indicating the serving gateway serving the at least one tracking area.
11. The mobility management entity of claim 10 , wherein the message from the base transceiver station including the list of tracking areas includes an S1 setup message.
12. The mobility management entity of claim 10 , wherein, for at least some tracking area identities, there is one and only one associated serving gateway.
13. The mobility management entity of claim 10 , wherein at least some serving gateways are associated with more than one tracking area identifier.
14. The mobility management entity of claim 10 , wherein the triggering event includes a receipt of an attach request from the base transceiver station identifying the user equipment and a tracking area from which the user equipment is connected to the network.
15. The mobility management entity of claim 14 , wherein the attach request includes an S1 initial user equipment message.
16. The mobility management entity of claim 10 , wherein the base transceiver station includes an evolved nodeB.
17. The mobility management entity of claim 10 , wherein the mobility management entity is configured to periodically initiate the domain name system query for the at least one tracking area to periodically update the stored information indicating the serving gateway serving the at least one tracking area.
18. The mobility management entity of claim 10 , wherein the mobility management entity is configured to initiate the domain name system query using a tracking area identity fully qualified domain name associated with the at least one tracking area.