“Push” keep-alive mechanism for SIP user agents located behind NATS/firewalls
A user equipment (UE) and method is provided having one or more components configured to receive a non-session initiation protocol (SIP) notification from a SIP entity and in response to send a ping request to the SIP entity, the one or more components further configured to receive a SIP request from the SIP entity. A network component and method is also provided that include one or more components configured to send a non-session initiation protocol (SIP) notification to a user equipment (UE) and to receive a ping request from the UE and further to send a SIP request to the UE.
1. A user equipment (UE) comprising:
a microprocessor configured to:
receive a non-session initiation protocol (non-SIP) notification from a SIP entity to initiate a SIP session with the UE, wherein the non-SIP notification indicates to the UE that there is a pending SIP request from the SIP entity, wherein a network component is connected between the UE and the SIP entity, and wherein the network component is operable to block SIP messages from the SIP entity to the UE;
send a ping request to the SIP entity in response to receiving the non-SIP notification, wherein the ping request is operable to open a port on the network component to thereby allow an inbound SIP message flow to the UE through the port; and
receive a SIP request from the SIP entity through the open port,
wherein the non-SIP notification is:
received in an Unstructured Supplementary Service Data (USSD) message;
received via an IP Multimedia Subsystem (IMS) layer one (l1) protocol interface; or
received over a proprietary enterprise server,
wherein the UE is configured to implement a traversal technique to traverse a network address translator (NAT) or firewall at the network component, wherein the traversal technique is implemented using a push keep-alive mechanism based on a non-SIP protocol to unblock a SIP port on the NAT or firewall at the network component.
2. The UE of claim 1 , wherein the non-SIP notification bypasses or passes through the network component.
3. The UE of claim 1 , wherein the SIP entity is an SIP server, a SIP UE, a SIP gateway, an Internet Protocol (IP) Multimedia Subsystem (IMS) UE, an IMS Call Session Control Function (CSCF), or other SIP entity capable of exchanging SIP messaging flows with the UE.
4. The UE of claim 1 , wherein the network component allows the incoming SIP messaging flows after blocking the SIP messaging flows due to a period of inactivity between the UE and the SIP entity.
5. The UE of claim 1 , wherein the UE receives the non-SIP notification in the USSD message.
6. A network component comprising:
a microprocessor configured to:
send a non-session initiation protocol (non-SIP) notification to a user equipment (UE) to indicate that there is a pending SIP request from the network component and to initiate a SIP session with the UE, wherein a second network component is connected between the UE and the network component, and wherein the second network component is operable to block SIP messages from the SIP entity to the UE;
receive a ping request from the UE sent in response to the non-SIP notification, wherein the ping request is operable to open a port on the second network component to thereby allow an inbound SIP message flow to the UE through the port; and
send a SIP request to the UE through the open port,
wherein the non-SIP notification is:
sent to the UE in an Unstructured Supplementary Service Data (USSD) message;
sent to the UE via an IP Multimedia Subsystem (IMS) layer one (l1) protocol interface; or
sent to the UE over a proprietary enterprise server,
wherein the UE is configured to implement a traversal technique to traverse a network address translator (NAT) or firewall at the second network component, wherein the traversal technique is implemented using a push keep-alive mechanism based on a non-SIP protocol to unblock a SIP port on the NAT or firewall at the second network component.
7. The network component of claim 6 , wherein the microprocessor receives the ping request from the UE via the port in the second network component.
8. The network component of claim 7 , wherein the non-SIP notification bypasses or passes through the second network component.
9. The network component of claim 7 , wherein the second network component allows the incoming SIP messaging flows after blocking the SIP messaging flows due to a period of inactivity between the UE and the network component.
10. The network component of claim 7 , wherein the network component sends the non-SIP notification to the UE in the USSD message.
11. A method implemented on a user equipment (UE), the method comprising:
receiving a non-session initiation protocol (non-SIP) notification from a SIP entity to initiate a SIP session with the UE, wherein the non-SIP notification indicates to the UE that there is a pending SIP request from the SIP entity, wherein a network component is connected between the UE and the SIP entity, and wherein the network component is operable to block SIP messages from the SIP entity to the UE;
sending a ping request to the SIP entity in response to receiving the non-SIP notification, wherein the ping request is operable to open a port on the network component to thereby allow an inbound SIP message flow to the UE through the port; and
receiving a SIP request from the SIP entity through the open port,
wherein the non-SIP notification is:
received in an Unstructured Supplementary Service Data (USSD) message;
received via an IP Multimedia Subsystem (IMS) layer one (l1) protocol interface; or
received over a proprietary enterprise server,
wherein the UE is configured to implement a traversal technique to traverse a network address translator (NAT) or firewall at the network component, wherein the traversal technique is implemented using a push keep-alive mechanism based on a non-SIP protocol to unblock a SIP port on the NAT or firewall at the network component.
12. The method of claim 11 , wherein the ping request is sent to the SIP entity via the port on the network component.
13. The method of claim 12 wherein the non-SIP notification bypasses or passes through the network component.
14. The method of claim 12 , wherein the SIP entity is a SIP server, a SIP UE, a SIP gateway, an Internet Protocol (IP) Multimedia Subsystem (IMS) UE, an IMS Call Session Control Function (CSCF), or other SIP entity capable of exchanging SIP messaging flows with the UE.
15. The method of claim 11 , wherein the network component allows the incoming SIP messaging flows after blocking the SIP session due to a period of inactivity between the UE and the SIP entity.
16. The method of claim 12 , wherein the UE receives the non-SIP notification in the USSD message.
17. A method implemented on a session initiation protocol (SIP) entity, the method comprising:
sending a non-SIP notification to a user equipment (UE) to indicate that there is a pending SIP request from the SIP entity to initiate a SIP session with the UE, wherein a network component is connected between the UE and the SIP entity, wherein the network component is operable to block SIP messages from the SIP entity to the UE;
receiving a ping request from the UE sent in response to the non-SIP notification, wherein the ping request is operable to open a port on the network component to thereby allow an inbound SIP message flow to the UE through the port; and
sending a SIP request to the UE through the open port,
wherein the non-SIP notification is:
sent to the UE in an Unstructured Supplementary Service Data (USSD) message;
sent to the UE via an IP Multimedia Subsystem (IMS) layer one (l1) protocol interface; or
sent to the UE over a proprietary enterprise server,
wherein the UE is configured to implement a traversal technique to traverse a network address translator (NAT) or firewall at the network component, wherein the traversal technique is implemented using a push keep-alive mechanism based on a non-SIP protocol to unblock a SIP port on the NAT or firewall at the network component.
18. The method of claim 17 , wherein the ping request is received from the UE via the port.
19. The method of claim 18 , wherein the non-SIP notification bypasses or passes through the network component.
20. The method of claim 18 , wherein the SIP entity is a SIP server, a SIP UE, a SIP gateway, an Internet Protocol (IP) Multimedia Subsystem (IMS) UE, an IMS Call Session Control Function (CSCF), or other SIP entity capable of exchanging SIP messaging flows with the UE.
21. The method of claim 18 , wherein the network component allows the incoming SIP messaging flows after blocking the SIP session due to a period of inactivity between the UE and the SIP entity.
22. The method of claim 18 , wherein the SIP entity sends the non-SIP notification to the UE in the USSD message.