Handling IMS and CSFB call at user equipment in wireless network

Abstract

Methods and apparatuses are provided for controlling a voice call at a user equipment (UE) in a wireless network. A method includes transmitting, to a network entity, a tracking area update (TAU) service request for a subsystem (IMS) initiation; receiving, from the network entity, a TAU service reject message; and in response to the TAU service reject message, stopping a circuit switch (CS) fall back call in at least one legacy radio technology (RAT).

Claims

1. A method for controlling a voice call at a user equipment (UE) in a wireless network, the method comprising: transmitting, to a network entity, a tracking area update (TAU) request or a service request for an internet protocol multimedia subsystem (IMS) initiation in an abnormal state in which at least one timer is running; receiving, from the network entity, a TAU reject message or a service reject message due to congestion of the network entity; and in response to the TAU reject message or the service reject message due to the congestion, starting a circuit switch (CS) fall back call in at least one legacy radio technology (RAT) even if the at least one timer has not expired.

2. The method of claim 1, further comprising triggering, by the UE, a radio resource control (RRC) establishment for a mobile originated (MO) IMS call for the IMS.

3. The method of claim 1, wherein the abnormal state includes running the at least one timer of the UE when the UE transfers the TAU request or the service request for the IMS initiation.

4. The method of claim 1, further comprising outputting, to an IMS client, information indicating a connection failure for the IMS.

5. The method of claim 4, receiving, by the UE, an RRC connection release request related to the connection failure for the IMS.

6. The method of claim 1, further comprising, in response to the TAU reject message or the service reject message, flushing data related to an IMS call.

7. The method of claim 1, wherein the TAU reject message or the service reject message indicates that the CS fall back call starts due to a TAU rejection or a service rejection.

8. A method for controlling a voice call at a network entity in a wireless network, the method comprising: receiving, from a user equipment (UE), a tracking area update (TAU) request or a service request for an internet protocol multimedia subsystem (IMS) initiation in an abnormal state of the UE in which at least one timer of the UE is running; and in response to the TAU service request or the service request, transmitting, to the UE, a TAU reject message or a service reject message due to congestion of the network entity for starting a circuit switch (CS) fall back call in at least one legacy radio technology (RAT) even if the at least one timer has not expired.

9. The method of claim 8, further comprising attempting a radio resource control (RRC) connection by a non-access stratum (NAS) for an IMS call request, according to an RRC initiation from the UE.

10. The method of claim 8, wherein the abnormal state includes running the at least one timer of the UE when the UE transfers the TAU request or the service request for the IMS initiation.

11. The method of claim 8, further comprising transmitting, from the network entity, an RRC connection release request related to a connection failure for the IMS.

12. The method of claim 8, wherein the TAU reject message or the service reject message indicates that the CS fall back call starts due to a TAU rejection or a service rejection.

13. A user equipment (UE) for a voice call in a wireless network, the UE comprising: a transceiver; and at least one processor, which is connected to the transceiver, configured to control the transceiver to: transmit, to a network entity, a tracking area update (TAU) request or a service request for an internet protocol multimedia subsystem (IMS) initiation in an abnormal state in which at least one timer is running, receive, from the network entity, a TAU reject message or a service reject message due to congestion of the network entity, and in response to the TAU reject message or the service request message due to the congestion, start a circuit switch (CS) fall back call in at least one legacy radio technology (RAT) even if the at least one timer has not expired.

14. The UE of claim 13, wherein the least one processor is further configured to trigger an RRC establishment for a mobile originated (MO) IMS call for the IMS.

15. The UE of claim 13, wherein the abnormal state includes running the at least one timer of the UE when the UE transfers the TAU request or the service request for the IMS initiation.

16. The UE of claim 13, wherein the at least one processor is further configured to output, to an IMS client, information indicating a connection failure for the IMS.

17. The UE of claim 16, wherein the at least one processor is further configured to control the transceiver to transmit, to the network entity, an RRC connection release request related to the connection failure for the IMS.

18. The UE of claim 13, wherein in response to the TAU reject message or the service reject message, the at least one processor is further configured to flush data related to an IMS call.

19. The UE of claim 13, wherein the TAU reject message or the service reject message indicates that the CS fall back call starts due to a TAU rejection or a service rejection.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The above and other aspects, features, and advantages of the present disclosure will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which:

(2) FIG. 1A is flow diagram illustrating an IMS call drop in a single SIM and a dual SIM scenario;

(3) FIG. 1B is flow diagram illustrating an IMS call drop in a multi SIM scenario;

(4) FIG. 2 is a diagram illustrating components of a UE for handling an IMS and CSFB call in wireless network, according to an embodiment of the present disclosure;

(5) FIG. 3 is a flow diagram illustrating a method for handling an IMS and CSFB call at the UE in wireless network, according to an embodiment of the present disclosure;

(6) FIG. 4 is a flow diagram illustrating a method for handling an IMS and CSFB call at a UE that is attempting to update when a retransmission timer expires in wireless network, according to an embodiment of the present disclosure;

(7) FIG. 5 is a sequence diagram illustrating operations performed for handling an IMS and CSFB call when the UE is registered and attempting to update, according to an embodiment of the present disclosure;

(8) FIG. 6 is a sequence diagram illustrating operations performed for handling a pending IMS call in the case of TAU failure due to timer expiration, according to an embodiment of the present disclosure;

(9) FIG. 7 is a sequence diagram illustrating operations performed for handling an IMS voice/emergency call when the UE receives a lower layer failure for a TAU request message, according to an embodiment of the present disclosure;

(10) FIG. 8 is a sequence diagram illustrating operations performed for handling an IMS call when a UE receives a TAU reject, according to an embodiment of the present disclosure;

(11) FIG. 9 is a sequence diagram illustrating operations performed for handling an IMS call while a congestion timer is running, according to an embodiment of the present disclosure;

(12) FIG. 10 is a sequence diagram illustrating operations performed for handling CS paging during IMS call establishment, according to an embodiment of the present disclosure;

(13) FIG. 11 is a flow diagram illustrating a method for IMS call handling of an IMS call flow indicating success and failure to an upper layer, according to an embodiment of the present disclosure;

(14) FIG. 12 is a flow diagram illustrating a method for handling an IMS call flow in evolved packet system (EPS) mobility management (EMM) abnormal states, according to an embodiment of the present disclosure;

(15) FIG. 13 is a flow diagram illustrating a method for handling an IMS call and a CSFB call at UE supporting multi SIMs, according to an embodiment of the present disclosure;

(16) FIG. 14 is a flow diagram illustrating a method for handling an IMS call and a CSFB call at UE, during CS paging, supporting multi SIMs, according to an embodiment of the present disclosure; and

(17) FIG. 15 is a diagram illustrating a computing environment implementing the method for handling an IMS call and a CSFB call at UE in a wireless network, according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

(18) Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals although they are illustrated in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present disclosure.

(19) The term or, as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended to facilitate an understanding of the ways in which the embodiments can be practiced and to further enable those skilled in the art to practice the embodiments. Accordingly, the examples should not be construed as limiting the scope of the embodiments described herein.

(20) Generally, LTE is a technology proposed by the 3.sup.rd generation partnership project (3GPP) which supports a high data rate (e.g., 50 Mbps uplink (UL) and 100 Mbps downlink (DL)) and is purely packet switched (PS) system. A PS system handles massive types of data. In order to improve IMS call procedures in a multimode device capable of LTE/3.sup.rd generation (3G)/2.sup.nd generation (2G), the 3GPP has provided one or more mechanisms to enhance signaling procedures to a modem. However, the one or more mechanisms provided by the 3GPP have not been accurate in handling an IMS call on an LTE network when a UE is in an abnormal state.

(21) The abnormal state may include one or more of IMS calls triggered in an evolved universal terrestrial radio access network (EUTRAN) when the UE is attempting to update and one or more timers (e.g. T3411/T3402/T3346) are running, IMS calls triggered in the EUTRAN when the UE is in a service request initiated state and one or more timers are running, IMS calls triggered in EUTRAN when the UE is waiting for TAU accept/reject from a network entity and one or more timers are running, IMS calls triggered in the EUTRAN during a UE initiated TAU procedure with a TAU active flag set to true, IMS calls triggered in the EUTRAN when the UE has received TAU reject/lower layer failure for the TAU with the TAU active flag as true, and IMS calls triggered from the UE when reselection is performed from the LTE to global system for mobile communication (GSM)/universal mobile telecommunications system (UMTS) radio access technology (RAT).

(22) Unlike conventional systems and methods, as shown in FIGS. 1A and 1B, embodiments of the present disclosure provide the UE, when, during a TAU retransmit timer (T3411/T3402/T3430/T3440) or upon a TAU initiation or service request and waiting for a response from the network, the UE initiates a VoLTE/IMS call, then high layers can provide a request to the NAS to check whether the UE is in a proper state to continue the call in the LTE, or whether it can move to a legacy radio access technology (RAT) to complete the call in the CS domain. When the NAS receives this indication, the UE can immediately trigger the TAU irrespective of its timer states. After sending to the TAU that its attempts failed or max attempts are reached, this failure is indicated to the IMS client/dialer so that the IMS client will not trigger any further data and pending data will be flushed. This will avoid unnecessary re-transmissions of the SIP data packets from the IMS client. In case of a failure from the NAS, the IMS client/dialer can initiate a CS voice call by moving to a legacy RAT to complete the user request.

(23) Unlike conventional systems and methods, embodiments of the present disclosure provide a unique evolved packet system (EPS) mobility management (EMM) that caters to IMS call requests to handle or prioritize the IMS mobile originated (MO)/MT call requests when the UE is in an EMM abnormal state, such as, for example, attempting update/attach and running one or more timers T3411/T3410/T3430.

(24) Unlike conventional systems and methods, the proposed mechanism increases the success rate of VoLTE/IMS calls in DSDS devices where an RF is shared between two stacks.

(25) FIG. 2 is a diagram illustrating components of a UE communicating with a network entity for handing an IMS call and a CSFB call in wireless network, according to an embodiment of the present disclosure.

(26) A UE 102 includes a processor 202, a memory 204 coupled to the processor 202, a NAS 206 coupled to the processor 202, a communication unit 208, and a modem 210. The UE 102 may be embodied as a laptop, a desktop computer, a mobile phone, a mobile station, a mobile terminal, a smart phone, a personal digital assistant (PDA), a tablet, a phablet, or any other electronic device.

(27) In an embodiment, the NAS 206 can be configured to receive an IMS indication when the IMS call is initiated at the UE 102. The IMS indication notifies the NAS 206 that the IMS call has been triggered by the UE 102.

(28) Further, the NAS 206 can be configured to detect a state of the UE 102. The state of the UE 102 can include the abnormal state, such as, for example, initiation of TAU, running or expiration of timers, one or more of timers T3411, T3346, T3402 or T3430, dropping a call (IMS/CSFB), delaying of a call, or the like.

(29) Call drops and call delays based on timers are shown below in Table 1.

(30) TABLE-US-00001 TABLE 1 Call Delays/Drops Based on Timers Timer Name Timer Value T3411 (At TAU failure due to lower layer failure, 10 s T3430 timeout or TAU rejected) T3346 (TAU reject received with a timer value for 15-30 mins T3346) T3402 (TAU accept with EMM cause #16 or #17 and Default 12 mins the attempt counter is equal to 5 for CS/PS mode 2 UE, or TAU accept with EMM cause #22) T3430 (TAU request sent) 15 s

(31) Further, the NAS 206 can be configured to perform an action based on the state of the UE 102 to trigger one of the IMS call and a CSFB call, as described in greater detail below with respect to FIGS. 4-7.

(32) The NAS 206 can be configured to detect whether a connection to a network entity 220 in the wireless network is successful or unsuccessful. The UE 102 can be connected to the network entity 220.

(33) Further, the NAS 206 can be configured to perform triggering the IMS call when the connection to the network entity is successful, or triggering the CSFB call when the connection to the network entity is unsuccessful.

(34) The NAS 206 can be configured to receive an IMS indication when the IMS call is initiated from the first SIM at the UE 102. Further, the NAS 206 can be configured to detect that the UE 102 is in a connected mode, and a second SIM at the UE 102 is signaling data to the wireless network. Further, the NAS 206 can be configured to block the signaling of data at the second SIM and trigger the IMS call from the first SIM.

(35) The modem 210 can be configured to detect that CS paging is received at the second SIM while the IMS call is ongoing on the first SIM, and ignore the CS paging at the second SIM.

(36) The memory 204 may include one or more computer-readable storage media. The memory 204 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable read only memories (EPROMs) or electrically erasable and programmable read only memories (EEPROMs). In addition, the memory 204 may, in some examples, be considered a non-transitory storage medium. The term non-transitory may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term non-transitory should not be interpreted that the memory 204 is non-movable. In some examples, the memory 204 can be configured to store larger amounts of information than the memory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in random access memory (RAM) or cache). The communication unit 208 can be configured to communicate internally between the units and externally with the networks.

(37) FIG. 2 shows a limited overview of the units of the UE 102 but it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE 102 may include fewer or more units. Further, the labels or names of the units are used only for illustrative purposes and do not limit the scope of the disclosure. One or more units can be combined together to perform same or substantially similar function in the UE 102.

(38) FIG. 3 is flow diagram illustrating a method for handling an IMS call and a CSFB call at a UE, according to an embodiment of the present disclosure. The method is performed by an NAS in a UE.

(39) In step 302, the method includes receiving an IMS indication when an IMS call is initiated at the UE. In an embodiment, the method allows the NAS 206 to receive the IMS indication when the IMS call is initiated at the UE 102.

(40) In step 304, the method includes detecting a state of the UE 102. In an embodiment, the method allows the NAS 206 to detect the state of the UE 102.

(41) In step 306, the method includes performing an action based on the state of the UE 102 to trigger one of the IMS call and the CSFB call. In an embodiment, the method allows the NAS 206 to perform the action based on the state of the UE 102 to trigger one of the IMS call and the CSFB call.

(42) The various actions, acts, blocks, steps, or the like in the method may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

(43) FIG. 4 is a flow diagram illustrating a method for handling an IMS call and a CSFB call at a UE serving an attempt to update when a retransmission timer expires in a wireless network, according to an embodiment of the present disclosure. The method is performed by an NAS in a UE.

(44) In step 402, the method includes receiving, by the NAS 206, an IMS indication when an IMS call is initiated at the UE 102.

(45) In step 404, the method includes determining whether the UE 102 is in a TAU initiated state. In an embodiment, the method allows the NAS 206 to detect the state of the UE 102.

(46) If the NAS 206 detects that the UE 102 is in the TAU initiated state, the NAS 206 determines whether the UE 102 is serving the ATTEMPTING-TO-UPDATE and whether one or more of retransmission timers T3411, T3346, T3402, and T3430 have expired, in step 406.

(47) If the UE 102 is determined to be serving the ATTEMPTING-TO-UPDATE and the one or more of the retransmission timers T3411, T3346, T3402, and T3430 have expired, the method includes stopping the transmission timer and setting the TAU active flag to true, in step 408, to indicate data pending to the network entity 220. In an embodiment, the method allows the NAS 206 to stop the transmission timer and set the TAU Active flag. The method then proceeds to step 414 as described below.

(48) If the UE 102 is not serving the ATTEMPTING-TO-UPDATE and the one or more of the retransmission timers T3411, T3346, T3402, and T3430 are running, the method includes indicating a failure to an IMS client and deleting the pending data, in step 410, thereby triggering the CSFB call. In an embodiment, the method allows the NAS 206 to indicate the failure to the IMS client and deleting the pending data.

(49) If the NAS 206 determines that the UE 102 is not in a TAU initiated state, the method includes waiting for a TAU accept/reject or unit one or more timers expire, in step 412. In an embodiment, the method allows the NAS 206 to wait for the TAU accept/reject or until the one or more timers expire.

(50) Further, in step 414, the method includes determining whether an area update accepts message is received from the network entity 220. In an embodiment, the method allows the NAS 206 to make the determination.

(51) If the NAS 206 determines that the area update accepts message is received from the network entity 220, the method includes triggering the IMS call, in step 416. In an embodiment the method allows the NAS 206 to trigger the IMS call.

(52) If the NAS 206 determines that the area update accepts message is rejected from the network entity 220, the method includes indicating that the TAU failed to an upper layer and that the UE 102 cannot send user data, in step 418. In an embodiment, the method allows the NAS 206 to provide the indication.

(53) In step 420, the method includes triggering the CSFB call. In an embodiment, the method allows the NAS 206 to trigger the CSFB call.

(54) The various actions, acts, blocks, steps, or the like in the method may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

(55) FIG. 5 is a sequence diagram illustrating operations performed for handling the IMS call and the CSFB call in the UE in a registered and attempting to update state, according to an embodiment of the present disclosure.

(56) Unlike conventional systems and methods, the proposed mechanism allows the UE 102 to immediately perform T3411 timer expiry actions and set the active flag as true in the TAU request. If the TAU is completed successfully, the UE 102 can therefore proceed with IMS signaling procedures and continue the IMS call. Thus, the proposed method can be utilized to effectively handle the MO Voice Call when the UE 102 is in a registered, attempting to update, update-MM state.

(57) In an embodiment, the NAS 206 (i.e. the NAS 206 in the UE 102) receives a combined evolved packet system (EPS) attach accept (location area identity (LAI)) from the network entity 220, in step 502. The NAS 206 broadcasts the TAI change observed indication and the TAU requests message (combined TA LA) to the network entity 220, in step 504. Further, the network entity 220 broadcasts a lower layer failure indication, to the NAS 206, in an RRC connection, in step 506. The NAS 206 broadcasts the TAU request message to the network entity 220 by setting the active flag to true, in step 508, thereby triggering the IMS call.

(58) FIG. 6 is a sequence diagram illustrating operations performed in handling a pending IMS call in case of a TAU failure due to expiration of one or more timers, according to an embodiment of the present disclosure.

(59) Unlike conventional methods and systems, the proposed mechanism can effectively handle the IMS call and the CSFB call during an MO voice/emergency call pending when the UE 102 initiates the TAU procedure with active flag set to true and during an RRC connection release request, received from the network entity 220, with lower layer failure/normal before receiving the TAU accept/reject request message.

(60) According to an embodiment, the NAS 206 releases the RRC connection locally, in response to the request received from the network entity 220, and switches to GSM enhanced data rates for GSM evolution (EDGE) radio access network (GERAN)/UTRAN to support the voice call through the CS. Also, the NAS 206 can send an indication to the IMS client so that pending data can be flushed at the modem 210 and a transmission control protocol-Internet protocol (TCP-IP).

(61) In an embodiment, the NAS 206 (i.e. the NAS 206 in the UE 102) receives the combined EPS attach accept (LAI) from the network entity 220, in step 602. The NAS 206 broadcasts the TAI change observed indication and the TAU requests message (combined TA LA) to the network entity 220, in step 604. Further, the network entity 220 broadcasts a lower layer failure indication, to the NAS 206, in the RRC connection, in step 606. The NAS 206 broadcasts the TAU request message to the network entity 220 by setting the active flag to true, in step 608.

(62) The NAS 206 can be configured to release the RRC connection locally, in step 610. Further, the NAS 206 can be configured to indicate the connection failure to the IMS client. Furthermore, the NAS 206 can be configured to flush the pending data due to the IMS call at modem 210 and the TCP-IP to prevent unwanted data/re-transmissions of the data packets after the call is ended or attempted in legacy RATs.

(63) FIG. 7 is a sequence diagram illustrating operations performed for handling an IMS voice/emergency call in case the UE receives a lower layer failure request message, from the network entity, in response to the received TAU request message from the NAS 206, according to an embodiment of the present disclosure.

(64) In an embodiment, the NAS 206 receives the combined EPS attach accept (LAI) from the network entity 220, in step 702. The NAS 206 broadcasts the TAI change observed indication and the TAU requests message (combined TA LA) to the network entity 220, in step 704. Further, the network entity 220 broadcasts a lower layer failure indication, to the NAS 206, in an RRC connection, in step 706. The NAS 206 broadcasts the TAU request message to the network entity 220 by setting the active flag to true, in step 708.

(65) If the NAS 206 receives the RRC connection failure request message from the network entity 220 before the TAU accept/reject request message, in step 710. The NAS 206 can stop the timer T3430 and indicate the RRC connection failure to the IMS client. Further, the NAS 206 can be configured to flush the pending data due to the IMS call at the modem 210 and the TCP-IP to prevent unwanted data/re-transmissions of the data packets after the call is ended or attempted in legacy RATs.

(66) FIG. 8 is a sequence diagram illustrating handling of an IMS Call when the UE receives the TAU reject message, according to an embodiment of the present disclosure.

(67) In an embodiment, the NAS 206 receives the combined EPS attach accept (LAI) from the network entity 220, in step 802. The NAS 206 broadcasts the TAI change observed indication and the TAU requests message (combined TA LA) to the network entity 220, in step 804. Further, the network entity 220 broadcasts a lower layer failure indication, to the NAS 206, in the RRC connection, in step 806. The NAS 206, thereon, broadcasts the TAU request message to the network entity 220 by setting the active flag to true, in step 808.

(68) Further, the NAS 206 receives the TAU Reject message with temporary cause, such as, for example, NW failure/congestion/MSC not reachable, in step 810. The NAS 206 releases the RRC connection locally and switches to the GERAN/UTRAN to support voice call through CS, in step 812. Also, the NAS 206 can send the indication to the IMS client (i.e., IMS application at the UE 102) so that pending data can be flushed at the modem 210 and the TCP-IP.

(69) FIG. 9 is a sequence diagram illustrating operations performed for handling CS paging during IMS call establishment, according to an embodiment of the present disclosure.

(70) In an embodiment, the UE 102 broadcasts the TAU/service request (RRC establishment can be mentioned as the IMS call) to the network entity 220, in step 902. Further, the network entity 220, in response to received TAU/service request, broadcasts the TAU/service request reject, in step 904, to wait for RRC release of the connection locally, in step 906.

(71) Therefore, the UE 102 indicates a connection failure to the IMS client. Further, the UE 102 can flush the pending data due to an IMS call at the modem 210 and the TCP-IP, to prevent unwanted data/re-transmissions after call is ended or attempted in legacy RATs.

(72) FIG. 10 is a sequence diagram illustrating operations performed for handling CS paging during the IMS call establishment, according to an embodiment of the present disclosure.

(73) The UE 102 is capable of supporting multi SIM, and if the VoLTE call is triggered from the IMS client, the modem 210 receives an indication from the IMS client for a VoLTE call, in step 1002. The modem connection with the network entity 220 is established in response to an indication received from the UE 102. The UE 102 therefore sends a response to the IMS client to start transmitting an SIP data.

(74) Further, the modem 210 detects that CS paging is received at the second SIM while the IMS call is ongoing on the first SIM, in step 1004. Thus, the modem 210 can be configured to ignore the CS paging and continue the IMS call by ending the VoLTE call, and once the call is ended the IMS client can send an indication to the modem 210 that the call has ended.

(75) The UE 102 initiates the IMS call when the UE 102 is in registered and idle states and either a TAU with an active flag or a service request is triggered. CS paging is received from the network entity, but the modem 210 receives the indication indicating the VoLTE call establishment is in progress, therefore the modem 210 can ignore the CS paging and continue the VoLTE call.

(76) Unlike conventional systems and methods, the embodiments prioritize the IMS call request in the UE 102 during the abnormal states, occurring at the UE 102, to maximize the chances of successful IMS call establishment.

(77) FIG. 11 is a flow diagram illustrating a method for handling an IMS Call in EMM abnormal states, according to an embodiment of the present disclosure.

(78) In step 1102, a method includes receiving an IMS indication when an IMS call is initiated at the UE 102. In an embodiment, the method allows the NAS 206 to receive the IMS indication.

(79) In step 1104, the method includes connecting the NAS 206 to the network entity 220 and indicating an accept/reject request message to the upper layer. In an embodiment, the method allows the NAS 206 to provide the indication to the upper layer.

(80) In step 1106, the method includes determining whether the connection to the network entity 220 in the wireless network is successful. In an embodiment, the method allows the NAS 206 to make the determination.

(81) If the connection to the network entity 220 in the wireless network is unsuccessful, the method includes sending the failure indication to the upper layer and triggering the CSFB call (move to 2G/3G to continue the call on the CS domain), in step 1108. In an embodiment, the method allows the NAS 206 to send the failure indication and trigger the CSFB call.

(82) If the connection to the network entity 220 in the wireless network is successful, the method includes triggering the IMS call (continue call on LTE network using IMS procedures), in step 1110. In an embodiment, the method allows the NAS 206 to trigger the IMS call.

(83) The various actions, acts, blocks, steps, or the like in the method may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

(84) FIG. 12 is a flow diagram illustrating a method for handling an IMS call in EMM abnormal states, according to an embodiment of the present disclosure.

(85) In step 1202, a method includes receiving the IMS indication when the IMS call is initiated at the UE 102. In an embodiment, the method allows the NAS 206 to receive the IMS indication.

(86) In step 1204, the method includes determining whether the state of the UE 102 is a TAU initiated state. In an embodiment, the method allows the NAS 206 to determine the state of the UE 102.

(87) If the NAS 206 detects that the UE 102 is not in the TAU initiated state, the method includes triggering, by the NAS 206, the CSFB call, by following the existing 3G protocols, in step 1206.

(88) If the NAS 206 detects that the UE 102 is in the TAU initiated state, the method includes prioritizing by the NAS 206 (in the UE 102) the MO voice call in the RRC connection request, in step 1208. In step 1210, the method includes sending a request, by the NAS 206, to the network entity 220 to prioritize IMS traffic over normal traffic.

(89) For example, when a user initiates the IMS call and the UE 102 is in the registered and idle state, either a TAU with an active flag or a service request will be triggered. Further, the connection request for such a message can be considered on priority by the network entity 220, hence establishment of the IMS call in the RRC connection request is introduced, usage of such an establishment can make the network entity aware of the reason for the connection request so that the network entity 220 can prioritize and minimize problems such as congestion, network failures, or the like.

(90) The various actions, acts, blocks, steps, or the like in the method may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

(91) FIG. 13 is a flow diagram illustrating a method for handling an IMS call and a CSFB call at UE supporting multi SIM, according to an embodiment of the present disclosure.

(92) In step 1302, the method includes receiving an IMS indication when an IMS call is initiated from a first SIM at the UE 102. In an embodiment, the method allows the NAS 206 to receive the IMS indication.

(93) In step 1304, the method includes detecting that the UE 102 is in connected mode and that a second SIM at the UE 102 is signaling data to the wireless network. In an embodiment, the method allows the NAS 206 to perform the detections.

(94) In step 1306, the method includes blocking the signaling of data at the second SIM. In an embodiment, the method allows the NAS 206 to block the signaling.

(95) In step 1308, the method includes triggering the IMS call from the first SIM. In an embodiment, the method allows the NAS 206 to trigger the IMS call.

(96) Further, the UE 102 supporting the multi SIM (DSDA, DSDS) is described in greater detail below with respect to FIG. 14.

(97) The various actions, acts, blocks, steps, or the like in the method may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

(98) FIG. 14 is a flow diagram illustrating a method for handling an IMS call and a CSFB call at UE, during CS paging, supporting multi SIM, according to an embodiment of the present disclosure.

(99) In step 1402, the method includes receiving the IMS indication when the IMS call is initiated from the first SIM at the UE 102. In an embodiment, the method allows the NAS 206 to receive the IMS indication.

(100) In step 1404, the method includes detecting that the UE 102 is in connected mode and that the second SIM at the UE 102 is signaling data to the wireless network. In an embodiment, the method allows the NAS 206 perform the detections.

(101) In step 1406, the method includes blocking the signaling of data at the second SIM. In an embodiment, the method allows the NAS 206 to block the signaling.

(102) In step 1408, the method includes triggering the IMS call from the first SIM. In an embodiment, the method allows the NAS 206 to trigger the IMS call.

(103) In step 1410, the method includes detecting that the CS paging is received at the second SIM while the IMS call is ongoing on the first SIM. In an embodiment, the method allows the modem 210 to detect that the CS paging is received at the second SIM.

(104) In step 1412, the method includes ignoring the CS paging at the second SIM. In an embodiment, the method allows the modem 210 to ignore the CS paging at the second SIM and continue on the VoLTE call.

(105) The various actions, acts, blocks, steps, or the like in the method may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

(106) FIG. 15 is a diagram illustrating a computing environment implementing the method for handing an IMS call and a CSFB call at the UE in wireless network, according to an embodiment of the present disclosure.

(107) A computing environment 1502 comprises at least one processing unit 1508, which is equipped with a control unit 1504 and an arithmetic logic unit (ALU) 1506, a memory 1510, a storage unit 1512, a plurality of networking devices 1516, and a plurality of input/output (I/O) devices 1514. The processing unit 1508 is responsible for processing the instructions of the schemes. The processing unit 1508 receives commands from the control unit 1504 in order to perform its processing. Further, any logical and arithmetic operations involved in the execution of the instructions are computed with the help of the ALU 1506.

(108) The overall computing environment 1502 can be composed of multiple homogeneous or heterogeneous cores, multiple central processing units (CPUs) of different kinds, special media and other accelerators. The processing unit 1508 is responsible for processing the instructions of the schemes. Further, the plurality of processing units 1508 may be located on a single chip or over multiple chips.

(109) The scheme having instructions and codes required for the implementation are stored in the memory unit 1510, the storage 1512, or both. At the time of execution, the instructions may be fetched from the corresponding memory 1510 or storage 1512, and executed by the processing unit 1508.

(110) In case of any hardware implementations various networking devices 1516 or external I/O devices 1514 may be connected to the computing environment to support the implementation through the networking unit and the I/O device unit.

(111) The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in the FIGS. 1 through 15 include blocks which can be at least one of a hardware device, or a combination of hardware device and software units.

(112) The present disclosure may be utilized in conjunction with the manufacture of integrated circuits, chip sets, or system-on-chips (SoCs). One skilled in the art would know how to dice wafers and package die to produce integrated circuits. Integrated circuits so manufactured are considered part of this disclosure.

(113) While the disclosure has been shown and described with reference to certain embodiments thereof, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims.