Session recovery from dedicated bearer failure
Techniques and systems for recovering a communication session from a dedicated bearer failure are disclosed. For example, a P-CSCF node can determine that a dedicated bearer associated with a communication session has failed, and, in response, send a SIP message to a UE associated with the communication session, the SIP message causing the UE to refrain from sending SIP requests using a SIP INVITE method. The process may further include identifying a first network node associated with an identifier of the UE, the first network node comprising one of a PGW or a SMF, and sending an instruction to the first network node to dissociate the dedicated bearer from the communication session. This causes a new attach procedure to be performed by the UE to recover the session without session failure.
1. A system comprising:
a proxy call session control function (P-CSCF) node; and
a first network node comprising one of a packet data network gateway (PGW) or a session management function (SMF),
wherein the P-CSCF node is configured to:
determine that a dedicated bearer associated with a communication session has failed;
send a Session Initiation Protocol (SIP) message to a user equipment (UE) associated with the communication session, the SIP message causing the UE to refrain from sending SIP requests using a SIP INVITE method;
determine that the first network node is associated with an identifier of the UE; and
send an instruction to the first network node to dissociate the dedicated bearer from the communication session,
wherein the first network node is configured to send a message to the UE to cause the UE to perform a new attach procedure to recover the communication session.
2. The system of claim 1 , further comprising a second network node comprising one of a policy and charging rules function (PCRF) or a policy control function (PCF), wherein the P-CSCF node is configured to determine that the dedicated bearer associated with the communication session has failed by:
sending a request to the second network node; and
at least one of:
receiving an error code from the second network node; or
failing to receive a response from the second network node within a predetermined time period since the sending of the request to the second network node.
3. The system of claim 2 , wherein the request sent to the second network node comprises an authorization authentication request (AAR).
4. The system of claim 1 , further comprising a second network node comprising one of a policy and charging rules function (PCRF) or a policy control function (PCF), wherein the P-CSCF node is configured to determine that the dedicated bearer associated with the communication session has failed by determining that a communication link used to communicate with the second network node is broken.
5. The system of claim 1 , wherein the P-CSCF node is configured to determine that the first network node is associated with the identifier of the UE using a lookup table that associates UE identifiers with at least one of assigned PGWs or assigned SMF s.
6. The system of claim 1 , wherein the P-CSCF node is configured to send the instruction to the first network node using a representational state transfer (REST) application programming interface (API).
7. The system of claim 1 , wherein the P-CSCF node is configured to determine that the dedicated bearer associated with the communication session has failed during setup of the communication session.
8. A method comprising:
determining, by a proxy call session control function (P-CSCF) node, that a dedicated bearer associated with a communication session has failed;
sending, by the P-CSCF node, a Session Initiation Protocol (SIP) message to a user equipment (UE) associated with the communication session, the SIP message causing the UE to refrain from sending SIP requests using a SIP INVITE method;
identifying, by the P-CSCF node, a first network node associated with an identifier of the UE, the first network node comprising one of a packet data network gateway (PGW) or a session management function (SMF); and
sending, by the P-CSCF node, an instruction to the first network node to dissociate the dedicated bearer from the communication session.
9. The method of claim 8 , wherein the determining, by the P-CSCF node, that the dedicated bearer associated with the communication session has failed comprises:
sending, by the P-CSCF node, a request to a second network node, the second network node comprising one of a policy and charging rules function (PCRF) or a policy control function (PCF); and
at least one of:
receiving, by the P-CSCF node, an error code from the second network node; or
failing to receive, by the P-CSCF node, a response from the second network node within a predetermined time period since the sending of the request to the second network node.
10. The method of claim 9 , wherein the request sent to the second network node comprises an authorization authentication request (AAR).
11. The method of claim 8 , wherein the determining, by the P-CSCF node, that the dedicated bearer associated with the communication session has failed comprises:
determining, by the P-CSCF node, that a communication link used to communicate with a second network node is unavailable, the second network node comprising one of a policy and charging rules function (PCRF) or a policy control function (PCF).
12. The method of claim 8 , wherein the identifying the first network node comprises using a lookup table that associates UE identifiers with at least one of assigned PGWs or assigned SMFs.
13. The method of claim 8 , wherein the instruction is sent by the P-CSCF node to the first network node using a representational state transfer (REST) application programming interface (API).
14. The method of claim 8 , wherein the sending, by the P-CSCF node, the instruction to the first network node to dissociate the dedicated bearer from the communication session causes the first network node to send a message to the UE to cause the UE to perform a new attach procedure to recover the communication session.
15. The method of claim 8 , wherein the P-CSCF node determines that the dedicated bearer associated with the communication session has failed during setup of the communication session.
16. The method of claim 8 , further comprising, prior to the determining, by the P-CSCF node, that the dedicated bearer associated with the communication session has failed, receiving, by the P-CSCF node, and from the UE, a SIP request using the SIP INVITE method.
17. The method of claim 8 , wherein the communication session comprises one of a Voice over Long Term Evolution (VoLTE) call or a Voice over New Radio (VoNR) call.
18. A method comprising:
sending, by a user equipment (UE), to a first proxy call session control function (P-CSCF) node, a first Session Initiation Protocol (SIP) request using a SIP INVITE method to setup a communication session;
receiving, by the UE, a SIP response from the first P-CSCF node;
in response to the receiving of the SIP response, refraining, by the UE, from sending SIP requests using the SIP INVITE method;
receiving, by the UE, a message to perform a new attach procedure to recover the communication session;
in response to the receiving of the message, sending, by the UE, to the first P-CSCF node or a second P-CSCF node, a second SIP request using a SIP REGISTER method; and
sending, by the UE, to the first P-CSCF node or the second P-CSCF node, a third SIP request using the SIP INVITE method to recover the communication session.
19. The method of claim 18 , wherein the message to perform the new attach procedure is received from one of a packet data network gateway (PGW) or a session management function (SMF).
20. The method of claim 18 , wherein the SIP response received from the first P-CSCF node is indicative of a dedicated bearer associated with the communication session having failed.