Method and system for handling call establishment by user equipment in a wireless communication network

By queries and updates the CC status during call establishment recovery in the wireless communication network, the problem of resource waste during deadlock is solved and the user experience and call success rate is improved.

CN111148168BActive Publication Date: 2024-11-15SAMSUNG ELECTRONICS CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN201910794381.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-11-06
Filing Date
2019-08-27
Publication Date
2024-11-15
Estimated Expiration
2039-08-27

AI Technical Summary

Technical Problem

In wireless communication networks, due to deadlock between user equipment (UE) and the network, excessive radio resources are consumed before the timer expires, resulting in user experience delays and resource waste.

Method used

After the call establishment recovery process, the UE determines its call control (CC) status and transmits a CC status query message to the base station in order to update the call status according to the received status, thereby releasing radio resources in advance, avoiding waiting for the timer to expire.

Benefits of technology

Reduces latency of call completion, improves user experience, effectively utilizes radio resources, and reduces resource waste during deadlocks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111148168B_ABST
    Figure CN111148168B_ABST
Patent Text Reader

Abstract

A method for establishing a call in a wireless communication network, performed by a user equipment (UE), the method comprising: determining a first call control (CC) state of the UE after performing a recovery procedure for call establishment; transmitting a CC state query message to a first base station connected to a first network; determining a second CC state of the first base station according to a CC state message received from the first base station in response to the CC state query message; and establishing the call by updating the first CC state based on the determined second CC state.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Indian Patent Application No. 201841042013 filed on November 6, 2018, in the Indian Intellectual Property Office, the disclosure of which is incorporated herein in its entirety by reference. Technical Field

[0003] The present disclosure relates to wireless communication networks, and more particularly to methods and systems for handling call establishment by User Equipment (UE) in wireless communication networks. Background Art

[0004] To initiate a call or send a message, the 3rd Generation Partnership Project (3 rd Certain defined messages are specified in the 3GPP (3rd Generation Partnership Project) specifications. During a call or when transmitting messages, there are certain situations where a transmission transmitted by the UE or the network (e.g., a base station) may not be received by the intended recipient (e.g., a transmission transmitted by the UE is not received by the network, or a transmission transmitted by the network is not received by the UE) due to various reasons (e.g., the UE is in an out of synchronization (OOS) state due to handover, etc.). In this situation, a deadlock situation occurs in which each entity (e.g., the UE and the network) is waiting for a response from the other entity (e.g., the network waits for a transmission from the UE, and the UE waits for a transmission from the network). In 3GPP, defined timers are used to recover from deadlock situations based on timer expiration.

[0005] However, there are certain disadvantages in being in a deadlock situation until a defined timer expires. During the deadlock period, excessive radio resources are consumed until the timer expires, and the user experience deteriorates due to delays when the UE and the network are in a deadlock situation.

[0006] It would therefore be desirable to address the aforementioned shortcomings or other deficiencies, or at least provide a useful alternative. Summary of the invention

[0007] Therefore, some example embodiments herein provide a method for establishing a call in a wireless communication network performed by a user equipment (UE). The method includes: determining a first call control (CC) state of the UE after performing a recovery procedure for call establishment; transmitting a CC state query message to a first base station connected to a first network; determining a second CC state of the first base station according to a CC state message received from the first base station in response to the CC state query message; and establishing a call by updating the first CC state based on the determined second CC state.

[0008] In some example embodiments, establishing the call includes transmitting a CC connection acknowledgement (ACK) message to the first base station.

[0009] In some example embodiments, the transmitting transmits the CC status query message to the first base station after a defined time interval.

[0010] In some example embodiments, the method further includes determining, based on the CC state message, that a mismatch occurs between the first CC state and the second CC state, and releasing radio resources in response to determining that the mismatch occurs.

[0011] In some example embodiments, the method further includes receiving a handover command message from the second base station after transmitting a connection message for establishing a call to the second base station while connected to the second network via the second base station, and transmitting a handover completion message to the first base station after performing the handover, wherein transmitting the CC status query message transmits the CC status query message to the first base station after a defined time interval.

[0012] In some example embodiments, the method further includes receiving a Single Radio Voice Call Continuity (SRVCC) handover command message from a second base station during establishment of a Voice over Long Term Evolution (VoLTE) call, and transmitting an SRVCC handover completion message to the first base station after performing the handover, wherein transmitting the CC status query message to the first base station after a defined time interval.

[0013] Some example embodiments of the present invention disclose a user equipment (UE) for establishing a call in a wireless communication network. The UE includes a memory storing computer-readable instructions and at least one processor, which is coupled to the memory and configured to execute the computer-readable instructions to: determine a first call control (CC) state of the UE after performing a recovery process of call establishment, transmit a CC state query message to a first base station connected to a first network, determine a second CC state of the first base station according to a CC state message received from the first base station in response to the CC state query message, and establish the call by updating the first CC state based on the determined second CC state.

[0014] These and other aspects of some of the example embodiments herein will be better appreciated and understood when considered in conjunction with the following description and accompanying drawings. However, it should be understood that the following description, although indicating some example embodiments and many of their specific details, is given as an illustration rather than a limitation. Many changes and modifications may be made within the scope of the example embodiments herein without departing from the spirit of the present invention, and the example embodiments herein include all such modifications. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The method is illustrated in the accompanying drawings, in which the same reference numerals indicate corresponding parts in the various figures. Some example embodiments of the present invention will be better understood from the following description with reference to the accompanying drawings, in which:

[0016] Figure 1a is an overview of a wireless communication network for handling call setup according to some example embodiments as disclosed herein;

[0017] Figure 1b is an overview of a wireless communication network in which radio resources are managed during handover according to some example embodiments as disclosed herein;

[0018] Figure 2 is a block diagram of a UE for processing call setup according to some example embodiments as disclosed herein;

[0019] Figure 3 is a block diagram of a call setup controller of a UE according to some example embodiments as disclosed herein;

[0020] Figure 4 is a block diagram of a base station (also referred to herein as a "network") according to some example embodiments as disclosed herein;

[0021] Figure 5 is a flow chart illustrating a method for processing call establishment by a UE in a wireless communication network according to some example embodiments as disclosed herein;

[0022] Figure 6 is a flow chart illustrating a method for managing radio resources by a UE in a wireless communication network according to some example embodiments as disclosed herein;

[0023] Figure 7 is a sequential flow chart illustrating releasing a failed call to save radio resources according to some example embodiments as disclosed herein;

[0024] Figure 8 is a sequential flow diagram illustrating various operations performed by a UE for establishing a call during a radio link failure according to some example embodiments as disclosed herein;

[0025] Fig. 9 is a sequential flow chart illustrating various operations performed by a UE for establishing a call according to some example embodiments as disclosed herein. The process is applicable to second generation (2 nd Generation, 2G) and third generation (3 rd Generation, 3G) network;

[0026] Fig.10 is a sequential flow diagram illustrating various operations performed by a UE for establishing a call during a 3G to 2G handover according to some example embodiments as disclosed herein; and

[0027] Fig.11 is a sequential flow diagram illustrating various operations performed by a UE for establishing a call during a SRVCC handover from an LTE network to a 3G / 2G network according to some example embodiments as disclosed herein. DETAILED DESCRIPTION

[0028] Some example embodiments of the present invention and their various features and advantageous details will be explained more fully with reference to the non-limiting example embodiments shown in the accompanying drawings and described in detail in the following description. Descriptions of well-known components and processing technologies are omitted so as not to unnecessarily obscure the example embodiments of the present invention. Moreover, the various example embodiments described herein are not necessarily mutually exclusive, because some example embodiments can be combined with one or more other example embodiments to form new example embodiments. Unless otherwise specified, the term "or" as used herein refers to a non-exclusive or. The examples used herein are merely intended to facilitate understanding of the ways in which some example embodiments of the present invention can be practiced, and further enable those skilled in the art to practice the example embodiments of the present invention. Therefore, these examples should not be interpreted as limiting the scope of the example embodiments herein.

[0029] As is conventional in the art, some example embodiments may be described and illustrated in terms of blocks that perform one or more functions described. These blocks, which may be referred to herein as units or modules, are physically implemented by analog and / or digital circuits, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may be optionally driven by firmware and / or software. The circuit may be, for example, embodied in one or more semiconductor chips, or embodied on substrate supports such as printed circuit boards. The circuits constituting the blocks may be implemented by dedicated hardware, or by at least one processor (e.g., one or more programmed microprocessors and associated circuit systems), or by a combination of dedicated hardware that performs some functions of the blocks and processors that perform other functions of the blocks. Without departing from the scope of the example embodiments, each block of some example embodiments may be physically separated into two or more interactive and discrete blocks. Similarly, without departing from the scope of the example embodiments, the blocks of some example embodiments may be physically combined into more complex blocks.

[0030] The accompanying drawings are used to help easily understand various technical features, and it should be understood that some example embodiments presented herein are not limited by the accompanying drawings. Thus, except for those specifically set forth in the accompanying drawings, the present disclosure should be interpreted as extending to any changes, equivalents and substitutes. Although the terms first, second, etc. can be used to describe various elements in this article, these elements should not be limited by these terms. These terms are usually only used to distinguish one element from another element.

[0031] Some example embodiments herein provide methods and systems for handling call setup by a UE in a wireless communication network.

[0032] Some example embodiments herein include determining that a CC state of the UE matches a CC state of the network after a recovery procedure.

[0033] Some example embodiments herein include transmitting a CC status query message to a network in order to obtain a CC status of the network.

[0034] Some example embodiments herein include transmitting a CC status query message to a network after expiration of a time interval defined at the UE.

[0035] Some example embodiments comprise managing radio resources by releasing radio resources allocated to the UE upon determining that the CC state of the UE does not match the CC state of the network.

[0036] Some example embodiments herein include establishing a call after determining that a CC state of the UE matches a CC state of the network.

[0037] Therefore, some example embodiments of the present invention provide a UE for processing call establishment in a wireless communication network. The UE includes a call establishment controller coupled to a memory and at least one processor. The call establishment controller is configured to detect the CC state of the UE after a recovery process of the call establishment. Further, the call establishment controller is configured to send a CC state query message to the network in order to obtain the CC state of the network. Further, the call establishment controller is configured to determine the CC state of the network according to a CC state message received from the network in response to the CC state query message. Further, the call establishment controller is configured to establish a call by updating the CC state of the UE based on the determined network CC state.

[0038] Unlike conventional methods and systems, the proposed method can be used to save radio resources by releasing the call in advance instead of waiting for the timer (e.g., NAS T310 / T303) to expire. Therefore, instead of the user of UE 100 remaining in the dialing state, the network 200 releases the resources corresponding to the call, notifies the user of UE 100 that the call is not connected, and provides the user with an opportunity to redial the call. Therefore, by reducing the delay in completing the call, the user's experience is improved.

[0039] Unlike conventional methods and systems, the method can also be used to improve call success rate (CSR) and utilize radio resources in a more efficient manner during deadlock situations between the UE and the network. This leads to an improved and better user experience by reducing the delay in completing the call.

[0040] Unlike conventional methods and systems, when a deadlock situation is detected, the UE changes its CC state to a CC state expected by the network (eg, matches the CC state of the network) in order to efficiently utilize radio resources.

[0041] Different from conventional methods and systems, in case the CC state change is confirmed at the network side, the UE will change the UE CC state to be compatible with the network CC state, thereby avoiding a deadlock situation to effectively utilize radio resources.

[0042] Referring now to the drawings, and more particularly to Figures 1a to 11 , some example embodiments are shown.

[0043] Figure 1a1 is an overview of a wireless communication network 1000 for processing call establishment according to some example embodiments as disclosed herein; the wireless communication network 1000 includes a UE 100 and a base station 200. The UE 100 may be, for example, but not limited to, a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a tablet computer, a laptop computer, etc. Those skilled in the art may also refer to the UE 100 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, etc. Those skilled in the art may also refer to the base station 200 as a node B, an evolved-Node B (eNB), a sector, a site, a base transceiver system (BTS), an access point (AP), a relay node, a remote radio head (RRH), a radio unit (RU) and / or a small cell.

[0044] UE 100 may comply with a variety of different communication protocols, allowing UE 100 to communicate over the fifth generation (5G) th 5G) networks, using any common type of LTE or LTE-Advanced (LTE-A) radio access technology (RAT) th The base station 200 can be connected to a corresponding network, such as a 5G network, a 4G network, a network using LTE or LTE-A RAT, a 3G network and / or a 2G network. By communicating with the base station 200, the UE 100 can be connected to the corresponding network via the base station 200. Therefore, the base station 200 is also referred to as "network 200", "first network 200a" and / or "second network 200b" herein.

[0045] For example, consider that when the UE is in the OOS state, radio resources are managed by the UE 100 in the wireless communication network 1000. In some example embodiments, the UE 100 is configured to detect the CC state of the UE 100 after the resumption procedure of the call establishment. After the resumption procedure of the call establishment, the UE 100 is configured to send a CC state query message to the network 200 in order to obtain the CC state of the network 200.

[0046] In response to the CC status query message, UE 100 is configured to determine the CC status of network 200 according to the CC status message received from network 200. Based on the determination, UE 100 is configured to establish a call by updating the CC status of UE based on the determined CC status of network 200.

[0047] In some example embodiments, the wireless communication network may be a third generation (3G) network 200, and the UE 100 is a mobile originated (MO) UE initiating a call to a mobile terminated (MT) UE. During the MO call setup time, after the radio bearer setup is completed, the UE CC state is in the CC_CALL_DELIVERED state, and the network CC state is in the CC_CALL_DELIVERED state. The network 200 transmits a CC CONNECT message to the UE 100. The network 200 starts a timer (e.g., CC_T313 for 30 seconds). The UE 100 moves to an out of sync / out of service (OOS) state, and a NAS T310 / T303 timer is started at the UE 100. Due to the OOS, the UE 100 cannot receive the CC CONNECT message.

[0048] Further, the UE 100 transmits a cell update message (eg, a cell update: rl-failure message) to the network 200. Based on the cell update message, the network 200 transmits a cell update confirm message (eg, SI: Cell_DCH) to the UE 100.

[0049] Because the network 200 (e.g., a mobile switching center (MSC)) has triggered the CC connection message, the CC state at the network 200 changes from the CC_Call_Transfer state to the CC_CONNECT_INDICATION state, and a timer CC_T313 (e.g., of 30 seconds duration) at the network 200 starts. Both the UE 100 and the network 200 wait for responses from each other (e.g., the UE 100 waits for a connection message from the network 200, and the network 200 waits for a connection ACK message from the UE 100 to proceed further).

[0050] In conventional methods and systems, after recovering from OOS, the UE 100 goes back into service and waits for a call control (CC) connect message state. When a timer (e.g., a NAS T310 timer) expires and the UE 100 does not receive a CC connect message from the network 200, the UE 100 transmits a disconnect message to the network 200. Based on the disconnect message, the call setup fails and after the timer at the network 200 or the UE 100 expires, the radio resources corresponding to the call will be released. This results in a negative user experience due to excessive delays in waiting for the call to be connected, and results in excessive waste of radio resources.

[0051] However, according to some example embodiments, after recovery from OOS (e.g., UE 100 may initiate a recovery procedure after a timer expires at UE 100), UE 100 may transmit a status query message to determine the CC status of the network. According to some example embodiments, UE 100 may use the following conditions to determine when to trigger the status query message:

[0052] 1. UE 100 CC state: CC_Call_Transfer,

[0053] 2. Allocate radio bearer resources, and

[0054] 3. Recover from OOS with radio resource control (RRC) state of CELL_DCH and without releasing circuit switched (CS) bearers.

[0055] Based on the CELL UPDATE CONFIRM message, the UE 100 transmits a CC status query to the network 200. The network 200 transmits a network 200 CC status (e.g., CC_CONNECT_INDICATION cause: in response to the status query) to the UE 100. Based on the network 200 CC status, the UE 100 transmits a RESOURCE RELEASE COMPLETE message to the network 200 (e.g., if the CC_STATE of the network is CC_CONNECT_INDICATION which confirms that the network 200 transmitted a CONNECT message to the UE 100, the UE 100 transmits a RELEASE COMPLETE message with CC cause: TEMPORARY FAILURE to the network).

[0056] Therefore, UE 100 can save radio resources by releasing the call in advance instead of waiting for the timer (e.g., NAS T310 / T303) to expire. Therefore, instead of the user of UE 100 remaining in the dialing state, network 200 releases the resources corresponding to the call, notifies the user of UE 100 that the call is not connected, and provides the user with an opportunity to redial the call. Therefore, by reducing the delay in completing the call, the user's experience is improved. In the case of a dual subscriber identity module (Subscriber Identity Module, SIM) dual standby (Dual Subscriber Identity Module Dual Stand-by, DSDS) UE, a stack other than the stack attempting to execute the call can use radio frequency (RF) resources after the call is released without the additional delay of waiting for the timer to expire.

[0057] In some example embodiments, if the network 200CC_state corresponds to CC_connect_indication, the UE 100 determines that the network 200 transmitted a connection message to the UE 100, and therefore the UE 100CC state (e.g., CC_call_transfer) does not match the network 200CC state (e.g., CC_connect_indication). Upon confirming that the CC state at the network 200 has changed, the UE 100 will change the UE 100CC state to be compatible (e.g., match) with the network 200CC state. According to the changed UE 100CC state, the UE 100 transmits a CC_connect_ACK message to the network 200.

[0058] In some example embodiments, if the network 200 CC_state corresponds to the CC_disconnect_indication state, the UE 100 determines that the network 200 transmits a disconnect message to the UE 100, and thus the UE 100 CC state (e.g., CC_call_transfer) does not match the network 200 CC state (e.g., CC_disconnect_indication). Therefore, the UE 100 will change the UE 100 CC state to be compatible (e.g., match) with the CC state of the network 200. According to the changed UE 100 CC state, the UE 100 transmits a release complete message to the network 200. According to some example embodiments, if there is any CC state mismatch between the UE 100 and the network 200, similar appropriate actions will be taken according to the 3GPP specification.

[0059] For example, consider that the CC state of UE 100 is in CC_Call_Transfer state, and the CC state of network 200 is in CC_Call_Transfer state. The network 200 transmits a CC connection message to UE 100, and the network 200 starts a timer (e.g., CC_T313 for 30 seconds). UE 100 does not receive the CC connection message for any reason (e.g., OOS, etc.), and UE 100 starts an internal timer for a threshold time (e.g., the threshold is 8 seconds). When the timer expires, UE 100 will trigger a status query. UE 100 transmits a CC status query message to the network 200. The network 200 transmits a CC status to UE 100 (e.g., CC_Connect indicates cause: in response to status query). Based on the CC status, UE 100 performs the action. The action corresponds to releasing radio resources or establishing a call.

[0060] In some example embodiments, UE 100 waits for a threshold time (defined by the user) before transmitting a status query message to network 200. Based on the CC status of the network, UE 100 proceeds with the action. The action corresponds to releasing radio resources or establishing a call.

[0061] In some example embodiments, if the NETWORK 200CC_STATE corresponds to the CALL_TRANSFER state, the UE 100 will not perform any action and wait for the CONNECT message because the UE 100CC state is the same as the NETWORK 200CC state.

[0062] Figure 1b is an overview of a wireless communication network in which radio resources are managed during handover according to some example embodiments as disclosed herein.

[0063] In this case, due to the handover, the UE 100 moves from the 3G network (e.g., network 200b) to the 2G network (network 200a). In some example embodiments, an RRC connection is established, and a paging response is transmitted from the UE 100 to the second network 200b (e.g., 3G network). The second network 200b transmits a call setup message to the UE 100. The UE 100 transmits a call confirmation message to the second network 200b. The UE 100 transmits a call connection message to the second network 200b. At this time, the UE 100 is in the CC_CONNECT_REQUEST state. The second network 200b transmits a handoverFromUTRANCommand-GSM to the UE 100. The UE 100 transmits a handover completion message to the first network 200a.

[0064] In conventional methods and systems, if during handover from the second network 200b to the first network 200a, the second network 200b transmits a connection confirmation message to the UE 100, the call setup will fail, and the radio resources corresponding to the call will be released after the timer at the network 200 or the UE 100 expires. This results in a negative user experience due to excessive delays in waiting for the call to be connected, and results in excessive waste of radio resources.

[0065] However, according to some example embodiments, after transmitting the handover complete message to the first network 200a, the UE 100 starts an internal timer (duration defined by the user, e.g., 8 seconds), and after the timer expires, the UE 100 transmits a CC status query message to the first network 200a. The first network 200a transmits a CC status message (e.g., CC_Connection Indication Cause: Response to Status Query) to the UE 100. Based on the CC status message, the UE 100 responds as if a connection confirmation message was received from the second network 200b.

[0066] In some example embodiments, when a connection confirmation message is missed at UE 100 due to a handover from a 3G network to a 2G network, after the connection message is transmitted to the second network 200b, UE 100 will start a timer with a threshold value (in the example, the threshold value is 8 seconds). When the timer expires, UE 100 will transmit a status query message to the 2G network (e.g., first network 200a). The 2G network responds with a status message that the CC state is the active state. In addition, if the CC state at the network side is CC_active state and the UE 100CC state is CC_connection_request, the UE 100 responds as if the missed connection confirmation message was received from the second network 200b.

[0067] Return to reference Figure 1a In some example embodiments, UE 100 may be involved in an SRVCC handover from an LTE network to a 3G / 2G network. Network 200 transmits a VoLTE call message to the UE LTE protocol stack. The UE LTE protocol stack transmits an incoming VoLTE call notification message to a user interface (UI) application. The user interface application transmits a call acceptance message to the UE LTE protocol stack. The UE LTE protocol stack transmits a message (e.g., a 200ok message) to the network 200. The network 200 transmits an SRVCC handover (HO) command to the UE LTE protocol stack.

[0068] In a conventional method and system, after the network 200 transmits an SRVCC HO command to the UE LTE protocol stack, the UE LTE protocol stack transmits a "Call context transferred to CC with alarm state" message to the UE 2G / 3G protocol stack. The network 200 transmits a confirmation message, but the UE 100 does not receive the confirmation message due to the HO process. Then, the UE 2G / 3G protocol stack transmits an SRVCC HO completion message to the network 200. At this time, the UE 100 CC state is in the alarm state, and the network 200 CC state is in the activated state. However, in the network 200, after the UE 100 transmits the SRVCC HO completion message, the Proxy-Call Session Control Function (P-CSCF) entity provides the Mobile Switching Center (MSC) (e.g., the network 200) with an MO call context with a CC connection state, which results in a call context mismatch between the UE 100 and the network 200. Because the UE 100 does not receive the confirmation message, the call setup will fail and the resources corresponding to the call will be released after the timer expires at the network 200 or the UE 100. This results in a negative user experience due to excessive delays in waiting for the call to be connected, and results in excessive waste of radio resources.

[0069] However, in some example embodiments, the UE LTE protocol stack transmits a call context transfer message including a CC with a connection request state to the UE 2G / 3G protocol stack. The UE 2G / 3G protocol stack transmits an SRVCC HO complete message to the network. The UE 2G / 3G protocol stack starts an internal timer of a specified duration (e.g., 8 seconds as a threshold), and the UE 2G / 3G protocol stack transmits a CC status query message to the network 200. The network 200 transmits a CC status message (e.g., CC_Connection Indication Cause: Response to Status Query) to the UE 100. Based on the CC status message, the UE 100 responds as if a connection confirmation was received from the network 200.

[0070] In some example embodiments, the UE 100 will start a timer that lasts for a threshold time (e.g., 8 seconds), and once the timer expires, the UE 100 will request the CC status of the network 200. The UE 100 transmits a status query message to the 2G / 3G network 200. The network 200 responds with a status message that the CC status is activated. In this case, if the CC status at the network 200 is CC_ACTIVE, and if the UE 100 if it is CC_CONNECT_REQUEST (indicating that the UE 100 is still at the alerting stage), the UE 100 responds as if a CONNECT CONFIRM message was received from the network 200.

[0071] Although Figure 1a and Figure 1b An overview of the wireless communication network 1000 is shown, but it should be understood that some example embodiments are not limited thereto. In some example embodiments, the wireless communication network 1000 may include fewer or more components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the example embodiments.

[0072] Figure 2 1 is a block diagram of a UE 100 according to some example embodiments as disclosed herein. In some example embodiments, the UE 100 includes a call setup controller 110, at least one processor 120, a communicator 130, and a memory 140. The operations described herein as being performed by any or all of the call setup controller 110 and the UE 100 may be performed by at least one processor (e.g., at least one processor 120) running a program code including instructions corresponding to the operations. The instructions may be stored in a memory (e.g., memory 140) of the UE 100. The term "processor" as used in the present disclosure may refer to, for example, a hardware-implemented data processing device having a circuit system that is physically constructed to perform desired operations including, for example, operations represented as codes and / or instructions included in a program. In at least some example embodiments, the above-mentioned hardware-implemented data processing device may include, but is not limited to, a microprocessor, a central processing unit (CPU), a processor core, a multi-core processor; a multiprocessor, an application-specific integrated circuit (ASIC), and a field programmable gate array (FPGA).

[0073] Consider a first scenario in which radio resources are managed by UE 100 in wireless communication network 1000, and the UE is in an OOS state. In some example embodiments, call setup controller 110 is configured to detect the CC state of UE 100 after a resumption procedure of call setup. After the resumption procedure of call setup, call setup controller 110 is configured to send a CC state query message to network 200 in order to obtain the CC state of network 200.

[0074] In response to the CC status query message, call setup controller 110 is configured to determine the CC status of network 200 according to the CC status message received from network 200. Based on the determination, call setup controller 110 is configured to establish a call by updating the CC status with the determined CC status of network 200.

[0075] Consider a second scenario, in which radio resources are managed by UE 100 in wireless communication network 1000, UE 100 performs handover from first network 200a to second network 200b, and UE 100 is in OOS state / HO process state. In some example embodiments, call setup controller 110 is configured to send a handover completion message after performing handover from first network 200a to second network 200b. Further, call setup controller 110 is configured to send a CC state query message to second network 200b so as to obtain the CC state of the second network after the time interval determined at UE 100 expires. In response to the CC state query message, call setup controller 110 is configured to determine the CC state of network 200b according to the CC state message received from second network 200b. In addition, call setup controller 110 is configured to establish a call by updating the CC state of second network 200b based on the determined CC state of second network 200b.

[0076] Consider a third scenario, in which radio resources are managed by UE 100 in wireless communication network 1000, UE 100 performs SRVCC handover from LTE domain to CS domain, and UE 100 is in OOS state / HO process state. In some example embodiments, call setup controller 110 is configured to send an SRVCC handover completion message after performing handover from first network 200a to second network 200b. Further, call setup controller 110 is configured to send a CC state query message to the network after a time interval determined at UE 100 expires, so as to obtain the CC state of second network 200b. Further, call setup controller 110 is configured to determine the CC state of second network 200b according to the CC state message received from first network 200a. Further, call setup controller 110 is configured to establish a call by updating the CC state of second network 200b with the determined CC state of second network 200b.

[0077] At least one processor 120 is configured to execute computer-readable instructions stored in the memory 140. The communicator 130 is configured to communicate internally between internal hardware components and / or communicate with external devices via one or more networks (e.g., the wireless communication network 1000, the network 200, the first network 200a, and / or the second network 200b). The communicator 130 is configured to communicate with the call establishment controller 110 to manage radio resources or establish a call in the wireless communication network 1000. The communicator 130 may be embodied, for example, by a circuit or circuit system, or alternatively, by at least one processor (e.g., at least one processor 120) running a program code stored in a memory (e.g., the memory 140) including instructions corresponding to any or all operations described herein as being performed by the communicator 130.

[0078] The memory 140 stores computer-readable instructions to be executed by at least one processor 120. The memory 140 may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable and programmable memory (EEPROM). In addition, in some examples, the memory 140 may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or propagation signal. However, the term "non-transitory" should not be interpreted as the memory 140 being non-removable. In some examples, the memory 140 may be configured to store an amount of information that exceeds the capacity of the memory 140. For example, a non-transitory storage medium may store data that changes over time (e.g., in a random access memory (RAM) or a cache).

[0079] although Figure 2 Various hardware components of UE 100 are shown, but it should be understood that some example embodiments are not limited thereto. In some example embodiments, UE 100 may include fewer or more components. Further, the labels or names of the components are for illustrative purposes only and do not limit the scope of the example embodiments. One or more components may be combined together to perform the same or substantially similar functions to manage radio resources in wireless communication network 1000.

[0080] Figure 31 is a block diagram of a call setup controller 110 according to some example embodiments as disclosed herein. In some example embodiments, the call setup controller 110 includes a CC state detector 110a, a CC state transmitter 110b, a CC state determiner 110c, a CC state updater 110d, a user interface application 110e, a UE LTE protocol stack 110f, and / or a UE 2G / 3G protocol stack 110g. The operations described herein as being performed by any one or all of the CC state detector 110a, the CC state transmitter 110b, the CC state determiner 110c, the CC state updater 110d, the user interface application 110e, the UE LTE protocol stack 110f, and the UE 2G / 3G protocol stack 110g may be performed by at least one processor (e.g., at least one processor 120) running a program code including instructions corresponding to the operations. The instructions may be stored in a memory (e.g., memory 140) of the UE 100.

[0081] Consider a first scenario in which radio resources are managed by UE 100 in wireless communication network 1000, and the UE is in an OOS state. In some example embodiments, CC state detector 110a detects the CC state of UE 100 after a resumption procedure of call setup. CC state transmitter 110b sends a CC state query message to network 200. CC state determiner 110c obtains the CC state of network 200. Further, CC state determiner 110c determines the CC state of UE 100 that matches the CC state of network 200.

[0082] In some example embodiments, CC state determiner 110c determines the CC state of network 200 according to a CC state message received from network 200. Further, CC state updater 110d updates the CC state using the determined CC state of network 200. CC state updater 110d establishes a call.

[0083] If the CC state of the UE 100 does not match the CC state of the network 200 , the CC state updater 110 d releases the radio resources allocated to the UE 100 .

[0084] If the CC state of the UE 100 matches the CC state of the network 200, the CC state updater 110d updates the CC state corresponding to the determined CC state of the network 200, and the CC state updater 110d establishes the call.

[0085] In some example embodiments, the UE LTE protocol stack 110f receives a VoLTE call message from the network 200. The UE LTE protocol stack 110f transmits an incoming VoLTE call notification message to the UI application 110e. The user interface application 110e transmits a call accept message to the UE LTE protocol stack 110f. The UE LTE protocol stack 110f transmits a message (e.g., 200ok) to the network 200. The network 200 transmits an SRVCC HO command to the UE LTE protocol stack 110f.

[0086] The UE LTE protocol stack 110f transmits a call context transfer message including a CC with a connection request state to the UE 2G / 3G protocol stack 110g. The UE 2G / 3G protocol stack 110g transmits an SRVCC HO completion message to the network. The UE 2G / 3G protocol stack 110g starts an internal timer that expires at a specified time (e.g., 8 seconds, and / or as defined by the user), and the UE 2G / 3G protocol stack 110g transmits a CC status query message to the network 200. The network 200 transmits a CC status message (e.g., CC_Connection Indication Cause: Response to Status Query) to the UE 100. Based on the CC status message, the UE 100 assumes that a connection confirmation is received.

[0087] although Figure 3 Various hardware components of call setup controller 110 are shown, but it should be understood that some example embodiments are not limited thereto. In some example embodiments, call setup controller 110 may include fewer or more components. Further, the labels or names of the components are for illustrative purposes only and do not limit the scope of some example embodiments. One or more components may be combined together to perform the same or substantially similar functions to manage radio resources or establish calls in wireless communication network 1000.

[0088] Figure 4 2 is a block diagram of a base station 200 (also referred to herein as "network 200" or "wireless communication network 200") according to some example embodiments as disclosed herein. In some example embodiments, network 200 includes a radio resource controller 210, at least one processor 220, a communicator 230, a memory 240, and a timer 250. The operations described herein as being performed by any or all of radio resource controller 210, wireless communication network 200, and timer 250 may be performed by at least one processor (e.g., at least one processor 220) running program code including instructions corresponding to the operations. The instructions may be stored in a memory (e.g., memory 240) of wireless communication network 200. Timer 250 may be a CC_T313 timer having a determined, defined, and / or configurable duration (e.g., 30 seconds).

[0089] The radio resource controller 210 receives a CC status query message from the UE 100. Based on the CC status query message, the radio resource controller 210 transmits a CC status message of the network 200 to the UE 100. The at least one processor 220 is configured to execute computer-readable instructions stored in the memory 240 and perform various processes. The communicator 230 is configured for internal communication between internal hardware components and / or to communicate with external devices via one or more networks (e.g., the wireless communication network 1000). The communicator 230 is configured to communicate with the radio resource controller 210 to manage radio resources or establish calls in the wireless communication network 1000. The communicator 230 may be embodied, for example, by a circuit or circuit system, or alternatively, by at least one processor (e.g., at least one processor 220) running a program code stored in a memory (e.g., the memory 240) including instructions corresponding to any or all operations described herein as being performed by the communicator 230.

[0090] The memory 240 stores computer-readable instructions to be executed by at least one processor 220. The memory 240 may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable and programmable memory (EEPROM). In addition, in some examples, the memory 240 may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or propagation signal. However, the term "non-transitory" should not be interpreted as the memory 240 being non-removable. In some examples, the memory 240 may be configured to store an amount of information that exceeds the capacity of the memory 140. For example, a non-transitory storage medium may store data that changes over time (e.g., in a random access memory (RAM) or a cache).

[0091] although Figure 4 Various hardware components of network 200 are shown, but it should be understood that some example embodiments are not limited thereto. In some example embodiments, network 200 may include fewer or more components. Further, the labels or names of the components are for illustrative purposes only and do not limit the scope of the example embodiments. One or more components may be combined together to perform the same or substantially similar functions to manage radio resources or establish calls in wireless communication network 1000.

[0092] Figure 5is a flow chart illustrating a method for processing call establishment by a UE 100 in a wireless communication network 1000 according to some example embodiments as disclosed herein;

[0093] At S802, the method includes detecting (e.g., determining) a CC state of the UE 100 after a resumption procedure of call setup. In some example embodiments, the method allows a CC state detector 110a to detect a CC state of the UE 100 after a resumption procedure of call setup. At S804, the method includes sending (e.g., transmitting) a CC state query message to the network 200. In some example embodiments, the method allows a CC state transmitter 110b to send a CC state query message to the network 200. At S806, the method includes obtaining a CC state message of the network 200. In some example embodiments, the method allows a CC state determiner 110c to obtain a CC state message of the network 200.

[0094] At S808, the method includes determining a CC state of the network 200 according to a CC state message received from the network 200. In some example embodiments, the method allows a CC state determiner 110c to determine a CC state of the network 200 according to a CC state message received from the network 200. At S810, the method includes updating a CC state based on the determined CC state of the network 200. In some example embodiments, the method allows a CC state updater 110d to update a CC state based on the determined CC state of the network 200. At S812, the method includes establishing a call. In some example embodiments, the method allows a CC state updater 110d to establish a call.

[0095] The various actions, behaviors, blocks, operations, etc. in flowchart S800 may be performed in the order presented, in a different order, or simultaneously. Further, in some example embodiments, some of the actions, behaviors, blocks, operations, etc. may be omitted, added, modified, skipped (etc.) without departing from the scope of the example embodiments.

[0096] Figure 6 is a flowchart S900 illustrating a method for managing radio resources by a UE 100 in a wireless communication network 1000 according to some example embodiments as disclosed herein;

[0097] At S902, the method includes detecting a CC state of the UE 100 after a resumption procedure of call setup. In some example embodiments, the method allows a CC state detector 110a to detect a CC state of the UE 100 after a resumption procedure of call setup. At S904, the method includes transmitting a CC state query message to the network 200. In some example embodiments, the method allows a CC state transmitter 110b to send a CC state query message to the network 200. At S906, the method includes obtaining a CC state of the network 200. In some example embodiments, the method allows a CC state determiner 110c to obtain a CC state of the network 200 based on a CC state message received from the network 200.

[0098] At S908, the method includes determining that the CC state of the UE 100 does not match the CC state of the network 200. In some example embodiments, the method allows the CC state determiner 110c to determine whether the CC state of the UE 100 matches the CC state of the network 200.

[0099] If the CC state of the UE 100 does not match the CC state of the network 200, then at S910, the method includes the UE 100 releasing the call. In some example embodiments, the method allows the CC state updater 110d to release the call.

[0100] In some example embodiments, if the CC state of the UE 100 does not match the CC state of the network 200, then at S912, the method includes updating a CC state corresponding to the determined CC state of the network 200. In some example embodiments, the method allows the CC state updater 110d to update a CC state corresponding to the determined CC state of the network 200. At S914, the method includes establishing a call. In some example embodiments, the method allows the CC state updater 110d to establish the call.

[0101] The proposed method can be used to save radio resources by releasing the call in advance instead of waiting for the timer (e.g., NAS T310 / T303) to expire. With the early call release, instead of the user of UE 100 being in the dialing state, the network 200 releases the resources corresponding to the call, notifies the user of UE 100 that the call is not connected, and provides the user with an opportunity to redial the call. Therefore, by reducing the delay in completing the call, the user's experience is improved.

[0102] The various actions, behaviors, blocks, operations, etc. in flowchart S900 may be performed in the order presented, in a different order, or simultaneously. Further, in some example embodiments, some of the actions, behaviors, blocks, operations, etc. may be omitted, added, modified, skipped (etc.) without departing from the scope of the example embodiments.

[0103] Figure 7 is a sequential flow diagram illustrating releasing a CS call to save radio resources according to some example embodiments as disclosed herein.

[0104] In this case, during the MO call setup time, after the radio bearer setup is completed, at S1002, the UE 100 CC state is in the CC_Call_Transfer state, and at S1004, the network 200 CC state is in the CC_Call_Transfer state. At S1006, the network 200 transmits a CC connect message to the UE 100. At S1008, the network 200 starts a timer 250 (e.g., CC_T313 lasts for 30 seconds). At S1010, the UE 100 moves to an out-of-sync / out-of-service (OOS) state, and the NAST310 / T303 timer starts running at the UE 100. Due to the OOS state, the UE 100 cannot receive a connect message.

[0105] At S1012, UE 100 transmits a cell update message (eg, cell update: rl-failure message) to network 200. At S1014, based on the cell update message, network 200 transmits a cell update confirm message (eg, SI: Cell_DCH) to UE 100.

[0106] Referring back to S1006 and S1008, since the network 200 (e.g., MSC) has triggered the CC connection message, the network 200 CC state at the MSC changes from CC_Call_Transfer to CC_Connection_Indication, and the timer 250 (e.g., CC_T313 lasts for 30 seconds) is started. After S1008, both the UE 100 and the network 200 are waiting for each other's response. (e.g., the UE 100 is waiting for the CC connection message from the network 200, and the network 200 is waiting for the connection ACK message from the UE 100).

[0107] In conventional methods and systems, after recovering from OOS, the UE 100 goes back into service and waits for a call control (CC) connect message state. When a timer (e.g., a NAS T310 timer) expires and the UE 100 does not receive a CC connect message from the network 200, the UE 100 transmits a disconnect message to the network 200. Based on the disconnect message, the call setup fails and after the timer at the network 200 or the UE 100 expires, the radio resources corresponding to the call will be released. This results in a negative user experience due to excessive delays in waiting for the call to be connected, and results in excessive waste of radio resources.

[0108] However, according to some example embodiments, at S1016, after recovering from OOS, UE 100 transmits a status query message to determine the CC status of the network. According to some example embodiments, UE 100 may use the following conditions to determine when to trigger the status query message:

[0109] 1. UE 100 CC state: CC_Call_Transfer,

[0110] 2. Allocate radio bearer resources, and

[0111] 3. Recovery from OOS with RRC state CELL_DCH is performed without releasing the CS bearer.

[0112] Based on the cell update confirmation message, the UE 100 transmits a CC status query to the network 200. At S1018, the network 200 transmits a CC status (e.g., CC_connection indication cause: in response to the status query) to the UE 100. At 1020, based on the received CC status, the UE 100 determines that the UE 100 CC status (e.g., CC_call_transfer) does not match the network 200 CC status (e.g., CC_connection_indication). Therefore, the UE 100 releases the radio resources and transmits a resource release complete message to the network 200 (e.g., if the CC_status of the network is CC_connection_indication which confirms that the network 200 transmitted the connection message to the UE 100, the UE 100 transmits a release complete message with CC cause: temporary failure to the network).

[0113] The proposed method can be used to save radio resources by releasing the call in advance instead of waiting for the timer (e.g., NAS T310 / T303) to expire. Therefore, instead of the user of UE 100 remaining in the dialing state, the network 200 releases the resources corresponding to the call, notifies the user of UE 100 that the call is not connected, and provides the user with an opportunity to redial the call. Therefore, by reducing the delay in completing the call, the user's experience is improved. In the case of a dual subscriber identity module (SIM) dual standby (DSDS) UE, a stack other than the stack attempting to execute the call can use the radio frequency (RF) resources after the call is released without the additional delay of waiting for the timer to expire.

[0114] Figure 8 Is a sequential flow chart showing various operations performed by UE100 for establishing a call during a radio link failure according to some example embodiments as disclosed herein.

[0115] In this case, at S1102, the CC state of UE 100 is in CC_Call_Transfer state, and at S1104, the CC state of network 200 is in CC_Call_Transfer state. At S1106, network 200 transmits a CC connect message to UE 100. At S1108, network 200 starts timer 250 (e.g., CC_T313 lasts for 30 seconds).

[0116] At S1110, the UE 100 moves to the OOS state, and the NAS T310 / T303 timer starts running at the UE 100. Due to the OOS state, the UE 100 cannot receive a connection message. At S1112, the UE 100 transmits a cell update message (e.g., a cell update: rl-failure message) to the network 200. At S1114, based on the cell update message, the network 200 transmits a cell update confirmation message (e.g., SI: Cell_DCH) to the UE 100.

[0117] After recovering from OOS, at S1116, UE 100 transmits a status query message to determine the CC status of the network. According to some example embodiments, UE 100 may use the following conditions to determine when to trigger the status query message:

[0118] 1. UE 100 CC state is CC_CALL_TRANSFER,

[0119] 2. Allocate radio access bearer resources, and

[0120] 3. Recovery from OOS with RRC state CELL_DCH is performed without releasing the CS bearer.

[0121] Based on the cell update confirmation message, the UE 100 transmits a CC status query to the network 200. At S1118, the network 200 transmits a CC status (e.g., CC_connected indication cause: in response to the status query) to the UE 100. At S1120, based on the received CC status, the UE 100 determines that the UE 100 CC status (e.g., CC_call_transfer) does not match the network 200 CC status (e.g., CC_connected_indication). Therefore, the UE 100 updates the UE 100 CC status to match the CC status expected by the network 200 (e.g., as if CC_connected was received from the network 200). At S1122, the UE 100 transmits a CC connection confirmation message to the network 200.

[0122] In some example embodiments, referring to S1118, if the CC state message from the network 200 indicates that the CC_state of the network 200 corresponds to the CC_connection_indication state, then in S1106, the UE 100 determines that the network 200 transmits a connection message to the UE 100, and therefore, the UE 100 CC state (e.g., CC_call_transfer) does not match the network 200 CC state (e.g., CC_connection_indication). With confirmation that the CC state at the network 200 has changed, the UE 100 will change the UE 100 CC state to be compatible (e.g., match) with the CC state of the network 200. According to the changed UE 100 CC state, the UE 100 transmits a CC_connection_ACK message (e.g., CC connection confirmation message) to the network 200.

[0123] In some example embodiments, referring to S1118, if the CC status message from the network 200 indicates that the CC_status of the network 200 corresponds to the CC_disconnect_indication state, the UE 100 determines that the network 200 transmits a disconnect message to the UE 100, and therefore, the UE 100 CC status (e.g., CC_call_transfer) does not match the network 200 CC status (e.g., CC_disconnect_indication). Therefore, the UE 100 will change the UE 100 CC status to be compatible (e.g., match) with the CC status of the network 200. According to the changed UE 100 CC status, the UE 100 transmits a release complete message to the network 200. According to some example embodiments, if there is any other CC status mismatch between the UE 100 and the network 200, similar appropriate actions will be taken according to the 3GPP specification.

[0124] Fig. 9 is a sequential flow chart illustrating various operations performed by the UE 100 for establishing a call according to some example embodiments as disclosed herein. These operations apply to both 2G and 3G networks.

[0125] In this case, at S1202, the CC state of the UE 100 is in the CC_Call_Transfer state, and at S1204, the CC state of the network 200 is in the CC_Call_Transfer state. At S1206, the network 200 transmits a CC connection message to the UE 100, and at S1208, the network 200 starts a timer 250 (e.g., CC_T313 for 30 seconds). At S1210, the UE 100 does not receive the CC connection message for any reason (e.g., OSS state) and the UE 100 starts an internal timer for a threshold time (in the example, the threshold is 8 seconds). At S1212, when the timer expires, the UE 100 will trigger a status query. At S1214, the UE 100 transmits a CC status query message to the network 200. At S1216, the network 200 transmits a CC status to the UE 100 (e.g., CC_Connect indicating a cause: in response to a status query). At S1218 , based on the CC status, the UE 100 performs an action (eg, releases radio resources or establishes a call).

[0126] In some example embodiments, the threshold of the internal timer is defined by an external source (e.g., a user). Then, in S1212, the UE 100 waits for the threshold of the internal timer (defined by the user) to expire before triggering a status query message to the network 200 in S1214. Based on the CC state of the network determined according to the CC state message received by the UE 100 in S1216, the UE 100 proceeds with further actions in S1218.

[0127] In some example embodiments, if the CC state message transmitted in S1216 indicates that the CC_state of the network 200 corresponds to the CC_connect_indication, then in S1206 the UE 100 determines that the network 200 transmitted the connection message to the UE 100, and therefore, the CC state (e.g., CC_Call_Transfer) of the UE 100 does not match the CC state (e.g., CC_Connect_Indication) of the network 200. Upon confirming the CC state change at the network 200, the UE 100 will change the UE 100 CC state to be compatible (e.g., match) with the CC state of the network 200. According to the changed UE 100 CC state, the UE 100 transmits a CC_Connect_ACK message to the network 200.

[0128] In some example embodiments, if the CC status message transmitted in S1216 indicates that the CC_status of the network 200 corresponds to the CC_disconnect_indication, the UE 100 determines that the network transmits a disconnect message to the UE 100, and therefore, the UE 100 CC status (e.g., CC_call_transfer) does not match the network 200 CC status (e.g., CC_disconnect_indication). Therefore, the UE 100 will change the UE 100 CC status to be compatible (e.g., match) with the CC status of the network 200. According to the changed UE 100 CC status, the UE 100 then transmits a release complete message to the network 200.

[0129] In some example embodiments, if the CC status message transmitted in S1216 indicates that the CC_status of the network 200 corresponds to the call_transfer state, the UE 100 will wait for a connect message from the network 200 because the UE 100 CC status matches the network 200 CC status.

[0130] In some example embodiments, if there is any other CC status mismatch between UE 100 and network 200, similar appropriate actions will be taken according to the 3GPP specifications.

[0131] Fig.10 is a sequential flow diagram illustrating various operations performed by the UE 100 for establishing a call during a 3G to 2G handover according to some example embodiments as disclosed herein.

[0132] At S1302, an RRC connection is established, and a paging response is transmitted from the second network 200b (e.g., a 3G network) to the UE 100. At S1304, the second network 200b transmits a call setup message to the UE 100. At S1306, the UE 100 transmits a call confirmation message to the second network 200b. At S1308, the UE 100 transmits a call connection message to the second network 200b. At S1310, the UE 100 is in a CC_Connection_Request state. At S1312, the second network 200b transmits a handoverFromUTRANCommand-GSM to the UE 100. At S1314, the UE 100 transmits a handover completion message to the first network 200a (e.g., a 2G network).

[0133] In conventional methods and systems, if during handover from the second network 200b to the first network 200a, the second network 200b transmits a connection confirmation message to the UE 100, the call setup will fail, and the radio resources corresponding to the call will be released after the timer expires at the network 200 or the UE 100. This results in a negative user experience due to excessive delays in waiting for the call to be connected, and results in excessive waste of radio resources.

[0134] However, according to some example embodiments, at S1316, after transmitting the handover complete message to the first network 200a, the UE 100 starts an internal timer that expires at a specified threshold (e.g., 8 seconds). After the internal timer expires, at S1318, the UE 100 transmits a CC status query message to the first network 200a. At S1320, the first network 200a transmits a CC status message (e.g., CC_Connection Indication Cause: Response to Status Query) to the UE 100. At S1312, based on the received CC status message, the UE 100 responds as if (e.g., assuming) a connection confirmation was received from the second network 200b.

[0135] In some example embodiments, when a connection confirmation message is missed at UE 100 due to a handover from a 3G network to a 2G network, after the connection message is transmitted to the second network 200b, UE 100 will start a timer with a threshold value (in the example, the threshold value is 8 seconds). When the timer expires, UE 100 will transmit a status query message to the 2G network (e.g., first network 200a). The 2G network responds with a status message that the CC state is the activated state. In addition, if the CC state at the network side is CC_Active state, and the UE 100CC state is CC_Connection_Request state, the UE 100 responds as if the missed connection confirmation message was received from the second network 200b.

[0136] Fig.11 is a sequential flow diagram illustrating various operations performed by the UE 100 for establishing a call during a SRVCC handover from an LTE network to a 3G / 2G network according to some example embodiments as disclosed herein.

[0137] At S1402, the network 200 transmits a VoLTE call message to the UE LTE protocol stack 110f. At S1404, the UE LTE protocol stack 110f transmits an incoming VoLTE call notification message to the user interface (UI) application 110e. At S1406, the user interface application 110e transmits a call acceptance message to the UE LTE protocol stack 110f. At S1408, the UE LTE protocol stack 110f transmits a message (e.g., a 200ok message) to the network 200. At S1410, the network 200 transmits an SRVCC HO command to the UE LTE protocol stack 110f.

[0138] In a conventional method and system, after the network 200 transmits the SRVCC HO command to the UE LTE protocol stack, the UE LTE protocol stack transmits a "Call context transferred to CC with alarming state" message to the UE 2G / 3G protocol stack. The network 200 transmits a confirmation message, but the UE 100 does not receive the confirmation message due to the HO process. Then, the UE 2G / 3G protocol stack transmits an SRVCC HO completion message to the network 200. At this time, the UE 100 CC state is in the alarming state and the network 200 CC state is in the activated state. However, in the network 200, after the UE 100 transmits the SRVCC HO completion message, the proxy call session control function (P-CSCF) entity provides the mobile switching center (MSC) (e.g., the network 200) with the MO call context with the CC connected state, which causes the call context mismatch between the UE 100 and the network 200. Because the UE 100 does not receive the confirmation message, the call setup will fail, and after the timer expires at the network 200 or the UE 100, the resources corresponding to the call will be released. This results in a negative user experience due to excessive delays in waiting for the call to be connected, and results in excessive waste of radio resources.

[0139] However, in some example embodiments, at S1412, the UE LTE protocol stack 110f transmits a call context transfer message including a CC with a connection request state to the UE 2G / 3G protocol stack 110g. At S1414, the UE 2G / 3G protocol stack 110g transmits a SRVCC HO complete message to the network. At S1416, the UE 2G / 3G protocol stack 110g starts an internal timer of a specified duration (e.g., 8 seconds), and at S1418, the UE 2G / 3G protocol stack 110g transmits a CC status query message to the network 200. At S1420, the network 200 transmits a CC status (e.g., CC_Connection Indication Cause: Response to Status Query) to the UE 100. At S1422, based on the CC status message, the UE 100 responds as if a connection confirmation was received from the network 200.

[0140] In some example embodiments, the UE 100 will start a timer for a threshold time (in the example, the threshold is 8 seconds), and once the timer expires, the UE 100 will request the CC status of the network 200. The UE 100 transmits a status query message to the 2G / 3G network 200. The network 200 responds with a status message that the CC status is activated. In this case, if the CC status at the network 200 is CC_ACTIVE, and if the UE 100 if it is CC_CONNECT_REQUEST (indicating that the UE 100 is still at the alerting stage), the UE 100 responds as if a connection confirmation message was received from the network 200.

[0141] While some example embodiments relate to call establishment during handoff between certain types of networks, some example embodiments may relate to call establishment during handoff between other types of networks.

[0142] Example embodiments disclosed herein may be implemented using at least one software program running on at least one hardware device and performing network management functions to control elements.

[0143] The various operations of the above-described methods may be performed by any suitable means capable of performing these operations, such as various hardware and / or software implemented in some form of hardware (eg, processor, ASIC, etc.).

[0144] The software may include an ordered listing of executable instructions for implementing logical functions and may be embodied in any "processor readable medium" for use by or in conjunction with an instruction execution system, apparatus or device (such as a single-core or multi-core processor or a system containing a processor).

[0145] The blocks or steps of the methods or algorithms and functions described in conjunction with the example embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. If implemented in software, the functions may be stored or transmitted on a tangible, non-transitory computer-readable medium as one or more instructions or codes. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an electrically programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD ROM, or any other form of storage medium known in the art.

[0146] The foregoing description of some example embodiments will so fully reveal the general nature of the example embodiments herein that others may readily modify and / or adapt such example embodiments for various applications by applying current knowledge without departing from the general concept, and such adaptations and modifications should and are intended to be understood as being within the meaning and scope of equivalents of the example embodiments. It should be understood that the wording or terminology employed herein is for descriptive purposes and not for limiting purposes. Therefore, although some example embodiments herein have been described, those skilled in the art will recognize that some example embodiments herein may be modified within the spirit and scope of the example embodiments as described herein.

Claims

1. A method for establishing a call in a wireless communication network, performed by a user equipment UE, the method include: After performing a call establishment recovery procedure, determining a first call control CC state of the UE; transmitting a CC status query message to a first base station connected to the first network; In response to the CC state query message, determining a second CC state of the first base station according to the CC state message received from the first base station; establishing the call by updating the first CC status based on the determined second CC status; determining, based on the CC state message, that a mismatch occurs between a first CC state and a second CC state; and In response to determining that the mismatch occurs, radio resources are released.

2. The method of claim 1, wherein the establishing the call comprises transmitting a CC connection confirm message to the first base station. 3 . The method of claim 1 , wherein the transmitting transmits the CC status query message to the first base station after a defined time interval.

4. The method of claim 1, further comprising: include: receiving a handover command message from the second base station after transmitting a connect message for establishing a call to the second base station while connected to the second network via the second base station; and transmitting a handover complete message to the first base station after performing the handover, The transmitting of the CC status query message comprises transmitting the CC status query message to the first base station after a defined time interval.

5. The method of claim 1, further comprising: include: During establishment of a Voice over Long Term Evolution (VoLTE) call, receiving a Single Radio Voice Call Continuity (SRVCC) handover command message from a second base station; and transmitting an SRVCC handover complete message to the first base station after performing the handover, The transmitting of the CC status query message comprises transmitting the CC status query message to the first base station after a defined time interval.

6. A user equipment UE for establishing a call in a wireless communication network, include: a memory storing computer-readable instructions; and at least one processor coupled to the memory and configured to execute the computer-readable instructions to: After performing a call establishment recovery procedure, determining a first call control CC state of the UE; transmitting a CC status query message to a first base station connected to the first network; In response to the CC state query message, determining a second CC state of the first base station according to the CC state message received from the first base station; establishing the call by updating the first CC status based on the determined second CC status; determining, based on the CC state message, that a mismatch occurs between a first CC state and a second CC state; and In response to determining that the mismatch occurs, radio resources are released. 7 . The UE of claim 6 , wherein the at least one processor is configured to execute the computer-readable instructions to establish the call including transmitting a CC connection confirm message to the first base station.

8. The UE of claim 6, wherein the at least one processor is configured to execute the computer-readable instructions to transmit the CC status query message to the first base station after a defined time interval.

9. The UE of claim 6, wherein the at least one processor is configured to execute the computer-readable instructions to: receiving a handover command message from the second base station after transmitting a connect message for establishing a call to the second base station while connected to the second network via the second base station; transmitting a handover complete message to the first base station after performing the handover; as well as After a defined time interval, the CC status query message is transmitted to the first base station.

10. The UE of claim 6, wherein the at least one processor is configured to execute the computer-readable instructions to: During establishment of a Voice over Long Term Evolution (VoLTE) call, receiving a Single Radio Voice Call Continuity (SRVCC) handover command message from a second base station; transmitting an SRVCC handover complete message to the first base station after performing the handover; and After a defined time interval, the CC status query message is transmitted to the first base station.

Citation Information

Patent Citations

  • Message handling

    CN104168598A

  • CSFB call establishment method and device

    CN105706518A

  • Method, device, equipment and system for call processing

    CN106488521A

  • Paging method and apparatus considering carrier aggregation environment in mobile communication system

    US20110105141A1

  • Methods and Apparatuses for Managing Multiple Call Sessions During a Transfer

    US20120213197A1