Method, apparatus, and computer program product for expediting an emergency services initiation
A method, apparatus, and computer program product provide enhanced emergency services fallback procedures. The user equipment may indicate the emergency services fallback within the registration request message to a network entity, such as the access and mobility management function. Upon receiving the registration request message the emergency services fallback procedure is triggered. The user equipment receives an indication, such as via an access stratum layer and the received indication is considered, such as by the non-access stratum layer in the user equipment, as the registration response message. The user equipment is configured to respond differently upon receiving differently configured registration response rejection messages or upon expiration of a response timer.
1 . A method comprising:
during a registration update procedure between a user equipment (UE) and an access and mobility management function (AMF), causing a registration request for emergency services fallback to be sent;
starting a timer when the registration request is sent;
in response to expiry of the timer, causing an emergency services fallback attempt failure notification to be sent to upper layers of the UE;
receiving a response to the registration request, the response to the registration request indicating rejection of the registration request;
in response to the response to the registration request indicating rejection of the registration request, (i) stopping the timer, (ii) initiating communication via a cell connected to an evolved packet core or a core network, and (iii) initiating a mobility management procedure,
wherein the response to the registration request indicating rejection of the registration request comprises a predefined cause value, the predefined cause value indicating one of (a) an identity of the UE cannot be derived, or (b) no suitable cells are in a tracking area of the UE.
2 . The method according to claim 1 ,
wherein the registration request to be sent comprises a follow-on request bit defining that no follow-on request is pending.
3 . The method according to claim 1 , further comprising:
determining that the registration request for emergency services fallback has been accepted in an instance in which a mode has changed or a connection has been established with a network.
4 . The method according to claim 3 , further comprising:
stopping the timer upon determining that the registration request for emergency services fallback has been accepted.
5 . The method according to claim 1 ,
wherein the core network is a Fifth Generation (5G) core network.
6 . The method according to claim 5 , further comprising:
starting a timer when said communication via the cell is initiated; and
stopping the timer upon determining that said communication via the cell has been accepted.
7 . The method according to claim 1 , further comprising:
determining expiry of the timer based on a predefined time limit.
8 . The method according to claim 1 ,
wherein the mobility management procedure is an Evolved Packet System Mobility Management (EMM) procedure or a Fifth Generation Mobility Management (5GMM) procedure.
9 . The method according to claim 1 ,
wherein initiating said communication via the cell connected to the evolved packet core or the core network comprises:
in response to the predefined cause value indicating (a) an identity of the UE cannot be derived, initiating said communication via the cell connected to the evolved packet core or the core network, based on domain priority and selection rules.
10 . The method according to claim 1 ,
wherein initiating said communication via the cell connected to the evolved packet core or the core network comprises:
in response to the predefined cause value indicating (b) no suitable cells are in a tracking area of the UE, initiating said communication via the cell connected to the evolved packet core or the core network, based on an emergency services support indicator.
11 . An apparatus comprising:
at least one processor; and
at least one memory comprising instructions, that when executed by the at least one processor, cause the apparatus at least to:
during a registration update procedure between a user equipment (UE) and an access and mobility management function (AMF), cause a registration request for emergency services fallback to be sent;
start a timer when the registration request is sent;
in response to expiry of the timer, cause an emergency services fallback attempt failure notification to be sent to upper layers of the UE;
receive a response to the registration request, the response to the registration request indicating rejection of the registration request;
in response to the response to the registration request indicating rejection of the registration request, (i) stop the timer, (ii) initiate communication via a cell connected to an evolved packet core or a core network, and (iii) initiate a mobility management procedure,
wherein the response to the registration request indicating rejection of the registration request comprises a predefined cause value, the predefined cause value indicating one of (a) an identity of the UE cannot be derived, or (b) no suitable cells are in a tracking area of the UE.
12 . The apparatus according to claim 11 ,
wherein the registration request to be sent comprises a follow-on request bit defining that no follow-on request is pending.
13 . The apparatus according to claim 11 , wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to:
determine that the registration request for emergency services fallback has been accepted in an instance in which a mode has changed or a connection has been established with a network.
14 . The apparatus according to claim 13 , wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to:
stop the timer upon determining that the registration request for emergency services fallback has been accepted.
15 . The apparatus according to claim 11 , wherein the core network is a Fifth Generation (5G) core network.
16 . The apparatus according to claim 15 , wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to:
start a timer when said communication via the cell is initiated; and
stop the timer upon determining that said communication via the cell has been accepted.
17 . The apparatus according to claim 11 , wherein instructions, when executed by the at least one processor, further cause the apparatus at least to:
determine expiry of the timer based on a predefined time limit.
18 . The apparatus according to claim 11 ,
wherein the mobility management procedure is an Evolved Packet System Mobility Management (EMM) procedure or a Fifth Generation Mobility Management (5GMM) procedure.
19 . The apparatus according to claim 11 , wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to:
in response to the predefined cause value indicating (a) an identity of the UE cannot be derived, initiate said communication via the cell connected to the evolved packet core or the core network, based on domain priority and selection rules.
20 . The apparatus according to claim 11 , wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to:
in response to the predefined cause value indicating (b) no suitable cells are in a tracking area of the UE, initiate said communication via the cell connected to the evolved packet core or the core network, based on an emergency services support indicator.