WO2022036701A1

WO2022036701A1 - Enhancement for fast release of non-dds

Info

Publication number: WO2022036701A1
Application number: PCT/CN2020/110550
Authority: WO
Inventors: Hao Zhang; Yan Wang; Jian Li; Miao Fu; Jing Zhou
Original assignee: Qualcomm Incorporated
Priority date: 2020-08-21
Filing date: 2020-08-21
Publication date: 2022-02-24

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for an enhancement for a fast release of a non-DDS. A UE (e.g., non-DDS) may initiate at least one hold timer after a call procedure concludes. The call procedure may be associated with the UE and a cell/base station. The UE may determine whether the at least one hold timer expires before a control packet is received from the cell/base station. When the at least one hold timer expires before the control packet is received from the cell/base station, the UE may increase the at least one hold timer by a time period.

Description

ENHANCEMENT FOR FAST RELEASE OF NON-DDS

BACKGROUND Technical Field

The present disclosure relates generally to communication systems, and more particularly, to an enhancement for a fast release of a non-default data subscription (non-DDS) .

Introduction

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE) that includes a memory and at least one processor coupled to the memory. The memory may include instructions that, when executed by the at least one processor, cause the at least one processor to initiate at least one hold timer after a call procedure concludes, the call procedure associated with the UE and at least one of a cell or a base station; determine whether the at least one hold timer expires before a control packet is received from the at least one of the cell or the base station; and increase the at least one hold timer by a time period when the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

FIG. 4 is a call flow diagram illustrating communications between a UE and a base station.

FIG. 5 is a call flow diagram illustrating communications between a non-default data subscription (non-DDS) and a cell.

FIG. 6 is a call flow diagram illustrating communications between a non-DDS and a cell.

FIG. 7 is a flowchart of a method of wireless communication of a UE.

FIG. 8 is a diagram illustrating an example of a hardware implementation for an example apparatus.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC) ) . The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) . The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface) . The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN) ) may interface with core network 190 through second backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface) . The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .

Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102', employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

A base station 102, whether a small cell 102' or a large cell (e.g., macro base station) , may include and/or be referred to as an eNB, gNodeB (gNB) , or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range. The base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.

The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182” . The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 /UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 /UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The core network 190 may include a Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.

The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, 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 communications device, a remote 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, a client, or some other suitable terminology.

Referring again to FIG. 1, in certain aspects, the UE 104 may include a timer increaser component 198 that is configured to initiate at least one hold timer after a call procedure concludes, the call procedure associated with the UE and at least one of a cell or a base station; determine whether the at least one hold timer expires before a control packet is received from the at least one of the cell or the base station; and increase the at least one hold timer by a time period when the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station. Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While

subframes

3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infra applies also to a 5G NR frame structure that is TDD.

Other wireless communication technologies may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols/slot and 2 ^μ slots/subframe. The subcarrier spacing and symbol length/duration are a function of the numerology. The subcarrier spacing may be equal to 2 ^μ*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology.

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .

FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) ACK/NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318 TX may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354 RX receives a signal through its respective antenna 352. Each receiver 354 RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with 198 of FIG. 1.

Wireless communication systems may be configured to share available system resources and provide various telecommunication services (e.g., telephony, video, data, messaging, broadcasts, etc. ) based on multiple-access technologies such as CDMA systems, TDMA systems, FDMA systems, OFDMA systems, SC-FDMA systems, TD-SCDMA systems, etc. that support communication with multiple users. In many cases, common protocols that facilitate communications with wireless devices are adopted in various telecommunication standards. For example, communication methods associated with eMBB, mMTC, and URLLC may be incorporated in the 5G NR telecommunication standard, while other aspects may be incorporated in the 4G LTE standard. As mobile broadband technologies are part of a continuous evolution, further improvements in mobile broadband remain useful to continue the progression of such technologies.

FIG. 4 is a call flow diagram 400 illustrating communications between a UE 402 and a base station 404. At 406, the UE 402 may determine when a call procedure concludes, such as conclusion of a voice call, video call, short message service (SMS) , etc. At 408, the UE may initiate a hold timer after the call procedure concludes. The hold timer may be associated with a first time period that, when expired, may cause the UE 402 to attempt to release a RRC connection with the base station 404. At 410, the UE 402 may receive a control packet from the base station 404, such as router advertisement (RA) communicated via a paging indication.

At 412, the UE 402 may determine whether the hold timer expires before or after the control packet is received, at 410. If the timer expires before the control packet is received, at 410, the UE 402 may increase the hold timer by a time period, at 414. For example, the hold timer may be incremented by a value of 500 milliseconds (ms) or some other configurable value. In some cases, the RRC connection may be reestablished with the base station 404 after the UE 402 releases the RRC connection. As such, the UE 402 may re-initiate the hold timer, at 418. Based on the increased/incremented time period of the hold timer, the UE 402 may again determine, at 412, whether the hold timer expires before or after a next control packet is received. If the timer again expires before the next control packet is received, the UE 402 may again increase the hold timer by another time period. That is, the UE 402 may repeat steps 412-418 until the UE 402 determines, at 412, that the timer expires after a control packet is received.

After the UE 402 determines, at 412, that the timer expires after the control packet is received, the UE 402 may transmit, at 420, an extended service request (ESR) and/or a tracking area update (TAU) request to the base station 404. At 422, the UE 402 may receive an ESR and/or a TAU acceptance from the base station 404. Following ESR and/or TAU acceptance, the UE 402 may release, at 424, the RRC connection with the base station 404.

FIGs. 5-6 are call flow diagrams 500-600 illustrating communications between a non-default data subscription (non-DDS) 502/602 (e.g., a UE) and a cell 504/604 (e.g., a Long Term Evolution (LTE) cell or a base station) . The cell 504/604 may be further associated with a default data subscription (DDS) 506/606 (e.g., a UE) . In examples, the UE that corresponds to the non-DDS subscriber 502/602 and the UE that corresponds to the DDS subscriber 506/606, may be a dual subscriber identity module (SIM) dual standby (DSDS) type UE that supports wireless communication, e.g., LTE communication.

When a service such as a voice call, video call, SMS, etc. ends (e.g., at 508/608) for the non-DDS 502/602, the UE/non-DDS 502/602 may be configured to start a hold timer, at 508/608, for releasing an RRC connection with the cell 504/604 after the hold timer expires, at 510/610. The RRC connection release may be triggered by the non-DDS 502/602 based on a forced release of an ESR and/or a TAU. For example, the non-DDS 502/602 may transmit, at 512/612, a TAU_request to the cell 504/604 and the cell 504/604 may indicate, at 514/614, to the non-DDS 502/602 a TAU_acceptance to the transmitted TAU_request. At 516/616, the non-DDS 502/602 may attempt to release the RRC connection.

For the cell 504/604 to complete the release of the RRC connection, the cell 504/604 may be configured to transmit, at 518/618, a paging indication (Page_Ind) to the non-DDS 502/602. The paging indication may indicate to the non-DDS 502/602 that the cell 504/604 has further data to transfer to the non-DDS 502/602 for which a RRC connection may need to be established. In examples, the paging indication may indicate, at 518/618, that a control packet, such as an RA, is to be transmitted from the cell 504/604 to the non-DDS 502/602. The RA may be associated with an Internet Control Message Protocol (ICMP) , such as Internet Control Message Protocol version 6 (ICMPv6) , and/or an Internet Protocol (IP) , such as Internet Protocol version 6 (IPv6) .

Accordingly, the RRC connection release, at 516/616, by the non-DDS 502/602 may occur too quickly for the cell 504/604 (e.g., within 100 ms of starting the hold timer, at 508/608) such that the RA may not be transmitted in association with the paging indication. For example, the RRC connection release, at 516/616, may occur before the paging indication is transmitted, at 518/618, from the cell 504/604. Thus, the cell 504/604 may attempt to re-page the non-DDS 502/602 and/or reestablish the RRC connection, at 520/620. Since the RRC connection release, at 516/616, may be forced by the non-DDS 502/602, the cell 504/604 may not have enough time to successfully complete the paging indication/RA processes and the corresponding data may not be transmitted for the next RRC connection.

Referring again to FIG. 5, as there may appear to be no pending data from the perspective of the non-DDS 502 to transmit to the cell 504 for procedure 1 523 (e.g., since services such as voice call, video call, SMS, etc., have concluded) , the non-DDS 502 may initiate a hold timer, at 522, immediately after the RRC connection is reestablished, at 520, by the cell 504. The hold timer started at 522 may have a same time period as the hold timer started at 508. After expiration of the hold timer started at 522, the non-DDS 502 may trigger a second forced release of the ESR and/or the TAU and a loop procedure 1 may occur, at 524, where the loop procedure 1 may be similar to procedure 1 523. In examples, the loop procedure 1 524 may be followed by subsequent loop procedures (e.g., up through a loop procedure P) until the cell 504 is able to complete the RA procedure and end, at 526. Loop procedures 1 through N may cause radio frequency (RF) resources to be wasted by the non-DDS 502. Further, excess power may be consumed by maintaining the non-DDS 502 in a connection mode while meaningful information/messages are not being transferred.

Referring again to FIG. 6, the time period for each successive hold timer may be incrementally increased at 619 (e.g., based on n*T) for RRC connection release. That is, each of successive hold timers (e.g., the hold timers started at 608 and 622) may not have a same/fixed time period. Instead, a dynamic time period may be used by the non-DDS 602 to accommodate different timing behaviors of different network operators. For example, after the non-DDS 602 receives the Page_Ind, the time period may be increased, at 619, by n+1. Therefore, when the RRC connection is established, at 620, the hold timer started at 622 may have an increased time period based on the previous hold time period plus n*T.

For incrementing successive hold timers based on n*T, T may refer to a single increment (e.g., 500 ms or some other configurable value) of the timer and n may refer to a number of times the paging indication is received by the non-DDS 602 during a T_guard period. The T_guard period may be associated with an entire guard period (e.g., 10 sec) of the timer. Both T and T_guard may be configurable. In some case, a particular increase, at 619, in the dynamic time period may not allow the procedure to end, at 626. Instead, one or more loop procedures Q may occur, where the number of loop procedures Q may be less than the number of loop procedures P that may occur in the call flow diagram 500. For example, at 624, the hold timer for loop procedure 1 may be equal to the hold timer for procedure 1 623 plus (n*T) . After the hold timer is extended/enlarged to a particular value in a particular iteration, the cell 604 may complete the high level procedure associated with the Page_Ind so that the process may end, at 626. In examples, a hold timer that is extended to 2,000 ms (e.g., 2 sec) may allow the non-DDS 602 to receive the Page_Ind from the cell 604 before the non-DDS 602 attempts to release the RRC connection so that the procedure may end, at 626, without a further loop procedure, such as 624.

FIG. 7 is a flowchart 700 of a method of wireless communication. The method may be performed by a non-DDS/UE, e.g., the non-DDS 502/602, the UE 104, which may include the memory 360 and which may be the entire UE 104 or a component of the UE 104, such as the TX processor 368, the RX processor 356, and/or the controller/processor 359.

At 702, the UE may determine when a call procedure concludes. For example, referring to FIGs. 4-6, the UE 402 may determine, at 406, when a call procedure concludes. Further, the non-DDS UE 502/602 may determine, at 508/608, that a call has ended.

At 704, the UE may initiate at least one hold timer after the call procedure concludes, the call procedure associated with the UE and at least one of a cell or a base station. For example, referring to FIGs. 4-6, the UE 402 may initiate, at 408, a hold timer after the call procedure concludes. Further, the non-DDS UE 502/602 may start a hold timer (hold_timer) , at 508/608, after the call has ended. The call procedure may be associated with the non-DDS UE 502/504 and the cell 504/604. The UE 402 may correspond to at least one of the non-DDS 502/602 or the DDS 506/606.

At 706, the UE may receive a control packet from the at least one of the cell or the base station. For example, referring to FIGs. 4-6, the UE 402 may receive, at 410, a control packet from the base station 404. Further, the non-DDS UE 502/602 may receive, at 518/618, a Page_Ind for the RA from the cell 504/604.

At 708, the UE may determine whether the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station. For example, referring to FIGs. 4-6, the UE 402 may determine, at 412, whether the hold timer expires before or after the control packet is received, at 410, from the base station 404. The control packet may be transmitted, at 518/618, based on a paging indication associated with an upper layer procedure. In examples, the control packet transmitted, at 518/618, may be a RA.

At 710, the UE may increase the at least one hold timer by a time period when the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station. For example, referring to FIGs. 4 and 6, the UE 402 may increase, at 414, the hold timer by a time period, when the timer expires before the control packet is received by the UE 402. Further, the non-DDS UE 602 may increase, at 619, the hold timer by a time period. In examples, the time period may be configurable. In some case, the RRC connection may be reestablished (e.g., at 520/620) after the RRC connection is released (e.g., at 516/616) by the non-DDS 502/602.

At 712, the UE may re-initiate the at least one hold timer when the at least one hold timer expires before the control packet is received. For example, referring to FIGs. 4 and 6, the UE 402 may re-initiate, at 418, the hold timer when the timer expires before the control packet is received by the UE 402. Further, the non-DDS UE 602 may re-initiate, at 622, or start the hold_timer.

The at least one hold timer (e.g., 622) may not be re-initiated when the at least one hold timer expires after the control packet is received. Thus, at 714, if the UE determines the at least one hold timer expired after the control packet is received, the UE may transmit at least one of an ESR message or a TAU request message (e.g., after the at least one hold timer expires) . For example, referring to FIG. 4, the UE 402 may transmit, at 420, an ESR and/or TAU request to the base station 404, if the UE 402 determines that the hold timer expired after the control packet was received, at 410.

At 716, the UE may receive at least one of an ESR acceptance message or a TAU acceptance message after the at least one of the ESR message or the TAU request message is transmitted. For example, referring to FIG. 4, the UE 402 may receive, at 422, an ESR and/or TAU request from the base station 404, when the UE 402 determines that the hold timer expired after the control packet was received, at 410.

At 718, the UE may release the RRC connection after the at least one hold timer expires. For example, referring to FIG. 4, the UE 402 may release, at 424, the RRC connection, when the UE 402 determines that the hold timer expired after the control packet was received, at 410.

FIG. 8 is a diagram 800 illustrating an example of a hardware implementation for an apparatus 802. The apparatus 802 is a UE and includes a cellular baseband processor 804 (also referred to as a modem) coupled to a cellular RF transceiver 822 and one or more SIM cards 820, an application processor 806 coupled to a secure digital (SD) card 808 and a screen 810, a Bluetooth module 812, a wireless local area network (WLAN) module 814, a Global Positioning System (GPS) module 816, and a power supply 818. The cellular baseband processor 804 communicates through the cellular RF transceiver 822 with the UE 104 and/or BS 102/180. The cellular baseband processor 804 may include a computer-readable medium /memory. The computer-readable medium /memory may be non-transitory. The cellular baseband processor 804 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the cellular baseband processor 804, causes the cellular baseband processor 804 to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the cellular baseband processor 804 when executing software. The cellular baseband processor 804 further includes a reception component 830, a communication manager 832, and a transmission component 834. The communication manager 832 includes the one or more illustrated components. The components within the communication manager 832 may be stored in the computer-readable medium /memory and/or configured as hardware within the cellular baseband processor 804. The cellular baseband processor 804 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 802 may be a modem chip and include just the baseband processor 804, and in another configuration, the apparatus 802 may be the entire UE (e.g., see 350 of FIG. 3) and include the aforediscussed additional modules of the apparatus 802.

The reception component 830 is configured, e.g., as described in connection with 706 and 716, to receive a control packet from the at least one of the cell or the base station; and to receive at least one of an ESR acceptance message or a TAU acceptance message after the at least one of the ESR message or the TAU request message is transmitted. The communication manager 832 includes a determination component 840 that is configured, e.g., as described in connection with 702 and 708, to determine when a call procedure concludes; and to determine whether the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station. The communication manager 832 further includes an initiation component 842 that is configured, e.g., as described in connection with 704, to initiate at least one hold timer after the call procedure concludes, the call procedure associated with the UE and at least one of a cell or a base station. The communication manager 832 further includes an increaser component 844 that is configured, e.g., as described in connection with 710, to increase the at least one hold timer by a time period when the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station. The communication manager 832 further includes a re-initiation component 846 that is configured, e.g., as described in connection with 712, to re-initiate the at least one hold timer when the at least one hold timer expires before the control packet is received. The communication manager 832 further includes a releaser component 848 that is configured, e.g., as described in connection with 718, to release the RRC connection after the at least one hold timer expires. The transmission component 834 is configured, e.g., as described in connection with 714, to transmit at least one of an ESR message or a TAU request message after the at least one hold timer expires.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 7. As such, each block in the aforementioned flowchart of FIG. 7 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

In one configuration, the apparatus 802, and in particular the cellular baseband processor 804, includes means for initiating at least one hold timer after a call procedure concludes, the call procedure associated with the UE and at least one of a cell or a base station; means for determining whether the at least one hold timer expires before a control packet is received from the at least one of the cell or the base station; and means for increasing the at least one hold timer by a time period when the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station. The apparatus 802 may further include means for re-initiating the at least one hold timer when the at least one hold timer expires before the control packet is received. The apparatus 802 may further include means for releasing a RRC connection after the at least one hold timer expires. The apparatus 802 may further include means for receiving the control packet from the at least one of the cell or the base station. The apparatus 802 may further include means for transmitting at least one of an ESR message or a TAU request message after the at least one hold timer expires. The apparatus 802 may further include means for receiving at least one of an ESR acceptance message or a TAU acceptance message after the at least one of the ESR message or the TAU request message is transmitted. The apparatus 802 may further include means for determining when the call procedure concludes. The aforementioned means may be one or more of the aforementioned components of the apparatus 802 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 802 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

Further disclosure is included in the Appendix.

It is understood that the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” should be interpreted to mean “under the condition that” rather than imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”

Claims

A method of wireless communication of a user equipment (UE) , comprising:

initiating at least one hold timer after a call procedure concludes, the call procedure associated with the UE and at least one of a cell or a base station;

determining whether the at least one hold timer expires before a control packet is received from the at least one of the cell or the base station; and

increasing the at least one hold timer by a time period when the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station.
The method of claim 1, wherein the control packet is transmitted based on a paging indication associated with an upper layer procedure.
The method of claim 2, wherein the control packet is a routing advertisement (RA) .
The method of claim 1, wherein the UE corresponds to at least one of a non-default data subscription (non-DDS) or a default data subscription (DDS) .
The method of claim 1, further comprising re-initiating the at least one hold timer when the at least one hold timer expires before the control packet is received.
The method of claim 5, wherein the at least one hold timer is not re-initiated when the at least one hold timer expires after the control packet is received.
The method of claim 1, further comprising releasing a radio resource control (RRC) connection after the at least one hold timer expires.
The method of claim 7, wherein the RRC connection is reestablished after the RRC connection is released.
The method of claim 1, further comprising receiving the control packet from the at least one of the cell or the base station.
The method of claim 1, further comprising transmitting at least one of an extended service request (ESR) message or a tracking area update (TAU) request message after the at least one hold timer expires.
The method of claim 10, further comprising receiving at least one of an ESR acceptance message or a TAU acceptance message after the at least one of the ESR message or the TAU request message is transmitted.
The method of claim 1, further comprising determining when the call procedure concludes.
The method of claim 1, wherein the time period is configurable.
An apparatus for wireless communication at a user equipment (UE) , comprising:

a memory; and

at least one processor coupled to the memory and configured to:

initiate at least one hold timer after a call procedure concludes, the call procedure associated with the UE and at least one of a cell or a base station;

determine whether the at least one hold timer expires before a control packet is received from the at least one of the cell or the base station; and

increase the at least one hold timer by a time period when the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station.
The apparatus of claim 14, wherein the control packet is transmitted based on a paging indication associated with an upper layer procedure.
The apparatus of claim 15, wherein the control packet is a routing advertisement (RA) .
The apparatus of claim 14, wherein the UE corresponds to at least one of a non-default data subscription (non-DDS) or a default data subscription (DDS) .
The apparatus of claim 14, wherein the at least one processor is further configured to re-initiate the at least one hold timer when the at least one hold timer expires before the control packet is received.
The apparatus of claim 18, wherein the at least one hold timer is not re-initiated when the at least one hold timer expires after the control packet is received.
The apparatus of claim 14, wherein the at least one processor is further configured to release a radio resource control (RRC) connection after the at least one hold timer expires.
The apparatus of claim 20, wherein the RRC connection is reestablished after the RRC connection is released.
The apparatus of claim 14, wherein the at least one processor is further configured to receive the control packet from the at least one of the cell or the base station.
The apparatus of claim 14, wherein the at least one processor is further configured to transmit at least one of an extended service request (ESR) message or a tracking area update (TAU) request message after the at least one hold timer expires.
The apparatus of claim 23, wherein the at least one processor is further configured to receive at least one of an ESR acceptance message or a TAU acceptance message after the at least one of the ESR message or the TAU request message is transmitted.
The apparatus of claim 14, wherein the at least one processor is further configured to determine when the call procedure concludes.
The apparatus of claim 14, wherein the time period is configurable.
An apparatus for wireless communication at a user equipment (UE) , comprising:

means for initiating at least one hold timer after a call procedure concludes, the call procedure associated with the UE and at least one of a cell or a base station;

means for determining whether the at least one hold timer expires before a control packet is received from the at least one of the cell or the base station; and

means for increasing the at least one hold timer by a time period when the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station.
The apparatus of claim 27, wherein the control packet is transmitted based on a paging indication associated with an upper layer procedure.
The apparatus of claim 28, wherein the control packet is a routing advertisement (RA) .
The apparatus of claim 27, wherein the UE corresponds to at least one of a non-default data subscription (non-DDS) or a default data subscription (DDS) .
The apparatus of claim 27, further comprising means for re-initiating the at least one hold timer when the at least one hold timer expires before the control packet is received.
The apparatus of claim 31, wherein the at least one hold timer is not re-initiated when the at least one hold timer expires after the control packet is received.
The apparatus of claim 27, further comprising means for releasing a radio resource control (RRC) connection after the at least one hold timer expires.
The apparatus of claim 33, wherein the RRC connection is reestablished after the RRC connection is released.
The apparatus of claim 27, further comprising means for receiving the control packet from the at least one of the cell or the base station.
The apparatus of claim 27, further comprising means for transmitting at least one of an extended service request (ESR) message or a tracking area update (TAU) request message after the at least one hold timer expires.
The apparatus of claim 36, further comprising means for receiving at least one of an ESR acceptance message or a TAU acceptance message after the at least one of the ESR message or the TAU request message is transmitted.
The apparatus of claim 27, further comprising means for determining when the call procedure concludes.
The apparatus of claim 27, wherein the time period is configurable.
A computer-readable medium storing computer executable code, the code when executed by at least one processor causes the at least one processor to:

initiate at least one hold timer after a call procedure concludes, the call procedure associated with the UE and at least one of a cell or a base station;

determine whether the at least one hold timer expires before a control packet is received from the at least one of the cell or the base station; and

increase the at least one hold timer by a time period when the at least one hold timer expires before the control packet is received from the at least one of the cell or the base station.