SIP server with multiple identifiers
View Patent ↗A Session Initiation Protocol (SIP) server within an Internet Protocol Multimedia Subsystem (IMS) network may be associated with multiple, different identifiers. In some embodiments, a process for implementing the multiple, different identifiers of the SIP server within the IMS network may include maintaining, at a home subscriber server (HSS), a first identifier of a Session Initiation Protocol (SIP) server in association with a user, and inserting a second identifier of the SIP server in a message header of a SIP request during a wireless communication session of the user. In some embodiments, the first identifier of the SIP server may be transmitted over Diameter (Cx) interfaces, while the second identifier of the SIP server may be transmitted over SIP (ISC) interfaces. Using multiple identifiers of a SIP server allows for minimizing downtime while restoring the user's wireless communication session in the event of a failure of the SIP server.
1. A computer-implemented method comprising:
receiving a Session Initiation Protocol (SIP) message;
determining a SIP server for a user associated with the SIP message;
storing a first identifier of the SIP server in a home subscriber server (HSS); and
inserting a second identifier of the SIP server in a message header of the SIP message,
wherein the first identifier of the SIP server comprises a first fully qualified domain name (FQDN) of the SIP server, and the second identifier of the SIP server comprises a second FQDN of the SIP server, and
wherein the first FQDN of the SIP server corresponds to a domain associated with a traffic distribution server that is configured to allocate SIP servers among registered users of an Internet Protocol Multimedia Subsystem (IMS).
2. The computer-implemented method of claim 1 , further comprising, prior to the storing the first identifier:
receiving, at an intermediary network device, the second identifier of the SIP server; and
converting, at the intermediary network device, the second identifier of the SIP server to the first identifier of the SIP server, wherein the storing the first identifier of the SIP server in the HSS comprises uploading the first identifier of the SIP server from the intermediary network device to the HSS.
3. The computer-implemented method of claim 1 , wherein the SIP server comprises a serving call session control function (S-CSCF) node.
4. The computer-implemented method of claim 1 , further comprising:
receiving an additional SIP message;
retrieving the first FQDN from the HSS;
querying a domain name system (DNS) server using the first FQDN;
receiving a NULL response from the DNS server, the NULL response being indicative of a failure of the SIP server; and
in response to receiving the NULL response, re-registering the user in order to assign a new SIP server and to restore a wireless communication session.
5. The computer-implemented method of claim 1 , further comprising, prior to the storing the first identifier:
determining that one of the first identifier or the second identifier is to be transmitted over a Diameter interface to the HSS; and
selecting the first identifier of the SIP server for transmission to the HSS based at least in part on the Diameter interface.
6. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed, cause one or more communication devices to perform acts comprising:
receiving a Session Initiation Protocol (SIP) message associated with a user;
retrieving, from a home subscriber server (HSS), a first identifier of a SIP server that is associated with the user;
determining the SIP server associated with the first identifier;
sending the SIP message to the SIP server; and
inserting a second ID of the SIP server in a message header of the SIP message,
the first identifier of the SIP server comprises a first fully qualified domain name (FQDN) of the SIP server, the first FQDN corresponding to a domain associated with a traffic distribution server that is configured to monitor SIP servers of an IMS for failure conditions, and
the second identifier of the SIP server comprises a second FQDN of the SIP server, the second FQDN corresponding to a domain associated with a domain name system (DNS) server that is configured to translate domain names into numerical Internet Protocol (IP) addresses.
7. The one or more non-transitory computer-readable media of claim 6 , the acts further comprising, prior to the receiving the SIP message, storing the first identifier of the SIP server in the HSS as part of an Internet Protocol Multimedia Subsystem (IMS) registration procedure.
8. The one or more non-transitory computer-readable media of claim 7 , the acts further comprising, prior to the storing the first identifier, selecting the first identifier for transmission to the HSS based at least in part on a determination that the transmitting is to occur over a Diameter interface.
9. The one or more non-transitory computer-readable media of claim 7 , the acts further comprising, during the IMS registration procedure, and prior to the transmitting:
receiving the second identifier of the SIP server;
converting the second identifier of the SIP server to the first identifier of the SIP server that is transmitted to the HSS as part of the IMS registration procedure.
10. A system comprising:
one or more processors; and
memory storing computer-executable instructions that, when executed on the one or more processors, cause performance of operations comprising:
receiving a Session Initiation Protocol (SIP) message associated with a user;
retrieving, from a home subscriber server (HSS), an identifier of a SIP server that is associated with the user;
querying a domain name system (DNS) server using the identifier;
receiving a NULL response from the DNS server, the NULL response being indicative of a failure of the SIP server; and
in response to receiving the NULL response, re-registering the user in order to assign a new SIP server and to restore a wireless communication session.
11. The system of claim 10 , wherein re-registering the user comprises storing a first identifier of the new SIP server in the HSS.
12. The system of claim 11 , the operations further comprising, prior to storing the first identifier, selecting the first identifier for transmission to the HSS based at least in part on a determination that transmitting the first identifier to the HSS is to occur over a Diameter interface.
13. The system of claim 11 , the operations further comprising:
receiving an additional SIP message associated with the user; and
inserting a second identifier of the new SIP server in a message header of the additional SIP message.
14. The system of claim 13 , the operations further comprising:
receiving the second identifier from the new SIP server during an Internet Protocol Multimedia Subsystem (IMS) registration procedure associated with the re-registering of the user;
converting the second identifier to the first identifier; and
forwarding the first identifier to the HSS for maintaining the first identifier in association with the user.
15. The system of claim 13 , wherein the first identifier of the new SIP server comprises a first hostname of the new SIP server, and the second identifier of the new SIP server comprises a second hostname of the new SIP server.
16. The system of claim 10 , wherein the identifier comprises a fully qualified domain name (FQDN) corresponding to a domain of a traffic distribution server that is configured to monitor SIP servers of an Internet Protocol Multimedia Subsystem (IMS) for failure conditions, and wherein the DNS server is communicatively coupled to the traffic distribution server and configured to return the NULL response if the traffic distribution server indicates that the SIP server has failed.