TW201701697A - Communication link management following tune away - Google Patents

Abstract

Embodiments include systems and methods for managing a communication link of a first subscription following a tune away to a second subscription. A multi-standby communication device processor may determine whether a tune-away period is greater than or equal to a tune-away period threshold upon returning to a first subscription after performing a tune away to a second subscription, and may reduce a scheduling request threshold in response to determining that the tune-away period is greater than or equal to the tune-away period threshold. The device processor may reduce a random access channel request threshold in response to determining that the number of sent scheduling requests is greater than or equal to the reduced scheduling request threshold, and may declare a radio link failure in response to determining that the number of sent random access channel requests is greater than or equal to the reduced random access channel request threshold.

Description

Communication link management after tuning off

The present invention relates to communication link management after tune away.

A wireless device with multiple Subscriber Identification Modules (SIMs) can communicate with two or more cells of the wireless network. Some multi-custom multi-standby communication devices may allow two or more network interfaces or Subscriber Identification Modules (SIMs) to share a single radio frequency (RF) resource (eg, dual SIM dual standby, or "DSDS" device). However, RF resources in these devices can only be tuned to a single network at a time. A multi-custom multi-standby communication device can monitor multiple interfaces using a "tune-away" program in standby mode by tuning to a network in the main cell and quickly tune away to the second cell. The second network continues for a short period of time and then tune back to the first network to continue voice or data dialing. The tune away procedure may allow the multi-subscription multi-standby communication device to monitor the paging received on the second network or other indication or material for the incoming message. However, tune away from the other network interrupts communication with the first network and may reduce the amount of communication between the first network and the multi-subscription multi-standby communication device.

The systems, methods and apparatus of various embodiments enable a multi-custom multi-standby communication device to manage a first customized communication link by a processor of a multi-custom multi-standby communication device via: When returning to the first subscription after the subscription, determining whether the tuning off period is greater than or equal to the tuning off period threshold; in response to determining that the tuning off period is greater than or equal to the tuning off period threshold, reducing the scheduling request threshold; determining the sent row Whether the number of process requests is greater than or equal to the reduced schedule request threshold; in response to determining that the number of scheduled requests sent is not greater than or equal to the reduced schedule request threshold, one or more schedule requests are sent; Deciding whether the number of scheduling requests sent is greater than or equal to the reduced scheduling request threshold, reducing the random access channel request threshold; determining whether the number of random access channel requests sent is greater than or equal to the reduced random access Channel request threshold; in response to determining that the number of random access channel requests sent is not greater than or equal to the reduced a random access channel request threshold, transmitting one or more random channel requests; and declaring the first subscription in response to determining that the number of random access channel requests sent is greater than or equal to the reduced random access channel request threshold The radio link of the communication link failed.

In some embodiments, in response to determining that the tuning off period is greater than or equal to the tuning off period threshold, reducing the scheduling request threshold may include determining whether the data is in response to determining that the tuning off period is greater than or equal to the tuning off period threshold Queued for uplink transmission; and in response to determining that the tuning off period is greater than or equal to the tone The harmonic exit period threshold and the data is queued for uplink transmission, reducing the scheduling request threshold.

The various embodiments may also include: determining whether to receive an uplink grant in response to the one or more scheduling requests; and resetting the scheduling request threshold in response to determining to receive an uplink grant. The various embodiments may also include: deciding whether to grant the channel in response to the one or more random access channel requests; and resetting the random access channel request threshold in response to determining to grant the channel. The various embodiments may also include: determining whether to receive the uplink grant in response to the decision to receive the uplink grant or granting the channel; and reducing the uplink inactivity timer in response to the decision not to receive the downlink feedback The duration.

Various embodiments may also include declaring a radio link failure in response to determining that the uplink inactivity timer has timed out. The various embodiments may also include: deciding whether to transmit uplink data on the communication link; responding to determining that the uplink data has been transmitted, reducing the allowable retransmission threshold; and responding to the decision not to detect the downlink feedback, Send one or more uplink retransmissions.

Various embodiments may also include declaring a radio link failure in response to determining that the number of uplink retransmissions is greater than or equal to the reduced allowed retransmission threshold. The various embodiments may also include resetting the allowed retransmission threshold in response to determining to detect downlink feedback.

In various embodiments, declaring the radio link failure of the first subscribed communication link may include initiating a connection re-establishment procedure for the first subscribed communication link.

Various embodiments include a multi-custom communication device including a processor configured with processor-executable instructions for performing the operations of the various aspect methods described above. Various embodiments also include a non-transitory processor readable storage medium having processor executable software instructions stored thereon that are configured to cause a processor to perform the operations of the various aspect methods described above. Various embodiments also include a multi-custom communication device including means for performing the functions of the operations of the various aspect methods described above.

100‧‧‧Communication system

102‧‧‧First communication network

104‧‧‧Second communication network

110‧‧‧Multiple customized multi-standby communication equipment

130‧‧‧First Base Station

132‧‧‧Communication link

134‧‧‧wired or wireless communication link

140‧‧‧Second base station

142‧‧‧Communication link

144‧‧‧Communication link

200‧‧‧Multiple customized multi-standby communication equipment

202a‧‧‧First SIM interface

202b‧‧‧Second SIM interface

204a‧‧‧First Identification Module SIM-1

204b‧‧‧Second Identification Module SIM-1

206‧‧‧General Processor

208‧‧‧Encoder/Decoder (CODEC)

210‧‧‧Speakers

212‧‧‧ microphone

214‧‧‧ memory

216‧‧‧Based frequency data processor

218a‧‧‧RF resources

218b‧‧‧RF resources

220a‧‧‧Wireless antenna

220b‧‧‧Wireless antenna

222‧‧‧ memory

222a‧‧ agreement stack S1

222b‧‧‧ Agreement Stack S2

224‧‧‧Keyboard

226‧‧‧Touch screen display

228‧‧‧Modulator/Demodulator

230‧‧‧Data machine

300‧‧‧ method

302‧‧‧ squares

304‧‧‧Decision box

306‧‧‧Decision box

308‧‧‧ squares

310‧‧‧Decision box

312‧‧‧ square

314‧‧‧Decision box

316‧‧‧ square

318‧‧‧ square

320‧‧‧Decision box

322‧‧‧ squares

324‧‧‧Decision box

326‧‧‧ squares

328‧‧‧Decision box

330‧‧‧ square

332‧‧‧ squares

334‧‧‧ square

400‧‧‧ method

402‧‧‧ square

404‧‧‧Decision box

406‧‧‧Decision box

408‧‧‧ squares

410‧‧‧ square

412‧‧‧Decision box

414‧‧‧ squares

416‧‧‧Decision box

418‧‧‧ square

420‧‧‧ square

422‧‧‧ squares

424‧‧‧ squares

500‧‧‧Mobile communication equipment

502‧‧‧ processor

504‧‧‧Touch screen controller

506‧‧‧Touch screen controller

508‧‧‧Wireless transceiver

510‧‧‧Antenna

512‧‧‧Touch screen panel

514‧‧‧Speaker

516‧‧‧Hive Network Wireless Data Processor Chip

518‧‧‧ peripheral device connection interface

520‧‧‧Shell

522‧‧‧Power supply

524‧‧‧ physical button

526‧‧‧Power button

The drawings, which are incorporated herein by reference in their entirety in their entirety herein The drawings are used to explain the features of the various embodiments, and are not limited to the various embodiments.

1 is a block diagram of components of a communication system suitable for use with the various embodiments.

2 is a block diagram of components of a multi-custom multi-standby communication device in accordance with various embodiments.

3 is a program flow diagram illustrating a method for managing a first subscribed communication link by a processor of a multi-custom multi-standby communication device after tuning is detached to a second subscription, in accordance with various embodiments.

4 is a program flow diagram illustrating a method for managing a first subscribed communication link by a processor of a multi-custom multi-standby communication device after tuning is detached to a second subscription, in accordance with various embodiments.

Figure 5 is a block diagram of components of a mobile communication device suitable for use with the various embodiments.

The various embodiments will be described in detail with reference to the drawings. The same reference numbers will be used throughout the drawings to refer to the same or similar parts. References to specific examples and implementations are for illustrative purposes and are not intended to limit the scope of the claims.

Various embodiments include a plurality of multiples received by a processor of a multi-subscription multi-standby communication device implemented in a multi-subscription multi-standby communication device capable of reducing the time required to receive system information for each communication network A method of decoding system information of a communication network.

The terms "multi-subscription multi-standby communication device", "wireless device", "communication device" and "mobile communication device" are used interchangeably herein to refer to any or all of the following: cellular telephone, Smart phones, personal or mobile multimedia players, personal data assistants, laptops, tablets, smart phones, PDAs, wireless email receivers, cellular phones with multimedia Internet capabilities, wireless gaming controls And similar electronic devices and portable computing platforms including programmable processors and memory. Various embodiments may be particularly useful in any communication device that can support multiple wireless wide area network subscriptions and receive cell broadcasts.

As used herein, the terms "component," "module," "system," and the like are intended to include a computer-related entity such as, but not limited to, hardware, firmware, or hardware that is configured to perform a particular operation or function. Combination of body and software, software or software in execution. For example, a component can be, but is not limited to being, a program executed on a processor, a processor, an object, an executable, a thread executed, a program, and/or a computer. By way of illustration, both an application executing on a communication device and the communication device can be referred to as a component. One or more components can be located within a program and/or executed thread, and the components can be located on one processor or core and/or distributed between two or more processors or cores. Moreover, these components can execute from various non-transitory computer readable media having various instructions and/or data structures stored thereon. Components can communicate via local and/or remote programs, functions or program dialing, electronic signals, data packets, memory read/write, and other known computer, processor, and/or program related communication methods. .

A multi-custom communication device that allows two or more network interfaces or SIMs to share a single RF resource is referred to as a multi-subscription multi-standby communication device. The RF resources in these devices can only be tuned to a single network at a time. In order to support multiple subscriptions, the multi-subscription multi-standby communication device can be monitored by the "tuning off" procedure when the device is tuned to the first network (ie, tuned to the carrier signal associated with the first network). Multiple interfaces, quickly tuned out to the second network for a short period of time (ie, tuned to another carrier signal of the second network), then tuned back to A network to continue voice or data dialing. The tune away procedure allows the multi-subscription multi-standby communication device to monitor paging or system information from two or more communication networks. The tune away procedure may also allow the multi-subscription multi-standby communication device to support active dialing on the first subscription with the first network while monitoring the second subscription or incoming call received from the second network. Other instructions or materials for the message.

References to "First Network", "First Order", "Second Network" and "Second Order" are arbitrary and are used to refer to two or more subscriptions/networks. Road, usually because at any given time, the subscription/network can be in either active mode (in active voice or data dialing) or standby mode. For example, in this minute, the GSM subscription with the GSM network can dial the active data (hence the "first subscription"), and the WCDMA subscription with the WCDMA network is in standby mode (hence the "first" In the next minute, the WCDMA subscription can enter the active data dialing (become the "first" subscription) and the GSM subscription can enter the standby mode (becomes the "second" subscription). In addition, references to "first" and "second" subscriptions and networks are not intended to imply that the embodiments are limited to two subscriptions that share an RF resource, since only one subscription can use RF at a time. In the case of resources, three or more subscriptions can share one RF resource. The third subscription and the fourth subscription will be similar to the second subscription. Therefore, for the sake of brevity, the operation of the subscription in the standby mode in which the RF resources are shared during the tuning off period is generally described with reference to the "second" subscription.

A multi-subscription multi-standby communication device may include two or more Subscriber Identity Module (SIM) cards, each associated with a different service provider subscription. Multi-custom multi-standby communication devices can support a range of communication technologies and configurations, including dual SIM dual standby (DSDS) where two SIMs use one wireless unit. MSMS devices may also use different Radio Access Technology (RAT) protocols (eg, GSM, LTE, WCDMA, 1xRTT, etc.). Communication by a multi-subscription multi-standby communication device that uses two or more RATs in parallel may be referred to as a parallel RAT (CRAT). For example, a multi-subscription multi-standby communication device can use a single shared receiver and/or transmitter chain to access LTE for data and access GSM or 1xRTT for voice dialing (ie, GSM/SRLTE (single radio) LTE) or 1x SRLTE). As another example, a multi-subscription multi-standby communication device (eg, LTE DSDS) may use a single receiver to communicate using different RATs associated with two different SIMs (eg, LTE and GSM).

Because a multi-subscription multi-standby communication device with a single receiver and/or transmitter chain can only tune the receiver and/or transmitter chain to a single network at a time, multi-custom multi-standby communication devices are typically used. The "tune off" procedure supports CRAT communication (ie, time sharing for a single receiver/transmitter chain). The multi-custom multi-standby communication device can be resident on the first network or can communicate on the first network (for example, using the first subscription), and can be quickly tuned to the second network (for example, using the second Customized) and lasts for a short time (for example, to monitor a page received on the second network or other indication or material for the incoming message) and then tune back to the first network to continue voice or data dialing.

Performing tuning to another network disengages the transmission to the first network during the period of tune away ("tune off period") and may reduce the transmission of the multi-subscription multi-standby communication device to the first network and The amount of data delivered from the first network. For example, if a multi-custom multi-standby communication device using LTE DSDS or SRLTE performs long-term tuning and detachment to the second network, the multi-subscription multi-standby communication device may experience difficulty in reestablishing communication on the first network. And may experience radio link failure (RLF) and/or data communication period interruptions, especially when multi-subscription multi-standby communication devices are highly mobile.

Various embodiments enable a multi-subscription multi-standby communication device to declare (e.g., via a triggering decision) a radio link failure to tune back to the first network after tuning departures in accordance with certain conditions determined by a series of tests At the same time, the failed data communication communication period is recovered more quickly. When tuning back to the first network, the multi-subscription multi-standby communication device can determine whether the tuning off period exceeds the tuning off period threshold. The multi-subscription multi-standby communication device can also determine whether the multi-subscription multi-standby communication device has any data queued for transmission to the first network.

In some embodiments, if the tuning off period exceeds a threshold and the multi-custom multi-standby communication device has data to be transmitted, the multi-subscription multi-standby communication device can determine whether the multi-subscription multi-standby communication device is (eg, from The base station of the first network receives the uplink standard Give. The uplink grant may include resources on the uplink portion of the communication link with the first communication network that may allow the multi-subscription multi-standby communication device to transmit data queued for uplink transmission to the first communication network.

In response to the decision not to receive an uplink grant, the multi-subscription multi-standby communication device can reduce the allowed number of uplink scheduling requests (SRs) that the MSMS device can send to the first network. If the network grants uplink resources to the multi-subscription multi-standby communication device in response to one or more scheduling requests (ie, receives an uplink grant), the multi-subscription multi-standby communication device can reset the row The allowed number of requests is requested, and network communication is performed, for example, in a normal connection mode (for example, RRC_Connected mode in LTE). The decision may be based on channel conditions (eg, received signal strength, received signal strength indicator (RSSI), received signal reference power (RSRP) or another received signal strength and/or signal strength indication such as path loss estimate) Allows a reduced number of schedule requests.

In some embodiments, when the determined channel condition is relatively good, the multi-subscription multi-standby communication device can determine a smaller number of allowed scheduling requests (ie, the better the channel condition, the allowed scheduling request) The smaller the number, the more the multi-subscription multi-standby communication device can declare the radio link failure more quickly and initiate a connection re-establishment procedure for the first subscribed first communication link.

In some embodiments, in response to determining that the number of scheduling requests sent by the multi-subscription multi-standby communication device is greater than or equal to the reduced The number of scheduled scheduling requests, the multi-subscription multi-standby communication device can reduce the number of random access channel (RACH) requests that the multi-subscription multi-standby communication device can send to the first network. If the network grants a channel to a multi-subscription multi-standby communication device, the multi-subscription multi-standby communication device can reset the allowed number of RACH requests and can perform network communication, for example, in a normal connection mode (for example, LTE) RRC_Connected mode). In some embodiments, the multi-subscription multi-standby communication device can assert the radio link in response to determining that the number of RACH requests sent by the multi-subscription multi-standby communication device exceeds the reduced allowed number of RACH requests.

The multi-subscription multi-standby communication device can determine the reduced number of RACH requests based on the determined channel conditions. For example, the better the determined channel condition, the fewer the number of allowed RACH requests that the multi-subscription multi-standby communication device can determine, so that the multi-subscription multi-standby communication device can declare the radio link failure more quickly, and A connection re-establishment procedure is initiated for the first subscribed first communication link.

In response to the decision that the channel has been granted, the multi-subscription multi-standby communication device can determine whether the network grants sufficient uplink (UL) resources (eg, time slots, frames, resource blocks, resource elements, or other upstream). Link resources) to enable the multi-subscription multi-standby communication device to transmit uplink data to be transmitted (ie, waiting UL data) to the network. The multi-subscription multi-standby communication device can determine the reduced duration of the uplink inactivity timer for each resource bearer with pending uplink data, and the multi-subscription multi-standby communication device can Each uplink inactivity timer is initiated using the respective reduced timer duration of each uplink inactivity timer. The duration of each uplink inactivity timer can be determined based on channel conditions (eg, the better the channel condition, the shorter the timer duration), so that the multi-subscription multi-standby communication device can determine the radio link more quickly. failure. In response to the decision to send any pending uplink data to the first network without the multi-subscription multi-standby communication device, the uplink inactivity timer has timed out for the resource bearer, and the multi-subscription multi-standby communication device A radio link failure can be declared for the resource bearer and an attempt is made to re-establish the resource bearer.

In response to determining that the multi-subscription multi-standby communication device has transmitted uplink data on the resource bearer before the corresponding timer of the resource bearer expires, the multi-subscription multi-standby communication device may determine the multi-subscription multi-standby communication Whether the device receives downlink radio link control (DL RLC) feedback or control data feedback (eg, ACK) from the first network.

In some embodiments, the multi-subscription multi-standby communication device can determine the reduced number of allowed uplink retransmissions. The number of allowed retransmissions may be based on channel conditions (eg, the better the channel conditions, the fewer retransmissions allowed), so that the multi-subscription multi-standby communication device can determine the radio link failure more quickly. In response to determining that the number of uplink retransmissions is greater than or equal to the reduced number of allowed retransmissions, the multi-subscription multi-standby communication device may declare a radio link failure. When a multi-subscription multi-standby communication device declares RLF, multiple subscriptions are more The device communication device can initiate a connection re-establishment procedure (eg, an RRC connection re-establishment procedure in LTE).

Various embodiments may be implemented in various communication systems 100, such as systems including at least two mobile communication networks, examples of which are illustrated in FIG. The first communication network 102 and the second communication network 104 may each include a plurality of cellular base stations (e.g., a first base station 130 and a second base station 140). The multi-subscription multi-standby communication device 110 can communicate with the first communication network 102 via a communication link 132 to the first base station 130. The mobile communication device 110 can also communicate with the second mobile network 104 via a communication link 142 to the second base station 140. The first base station 130 can communicate with the first communication network 102 via a wired or wireless communication link 134, and the second base station 140 can communicate with the second communication network 104 via a wired or wireless communication link 144. Communication links 134 and 144 may include fiber optic backhaul links, microwave backhaul links, and other similar communication links.

Each of the communication networks 102 and 104 can support communication using one or more radio access technologies (RATs), and each of the communication links 132, 134, 142, and 144 can include A cellular connection established using a two-way wireless communication link of one or more RATs. Examples of RATs may include 3GPP Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Wideband CDMA (WCDMA), Global System of Action (GSM) and other RATs. Although communication links 132, 134, 142, and 144 are shown as single Links, but each of these communication links may include a plurality of frequencies or bands, each of which may include a plurality of logical channels. Additionally, each of the communication links 132, 134, 142, and 144 can use more than one RAT.

2 is a block diagram of components of a multi-custom multi-standby communication device 200 suitable for implementing various embodiments. Referring to FIGS. 1 and 2, in various embodiments, the multi-custom multi-standby communication device 200 can be similar to the multi-custom multi-standby communication device 110. The multi-subscription multi-standby communication device 200 can include a first SIM interface 202a that can receive a first identification module SIM-1 204a associated with the first subscription. The multi-subscription multi-standby communication device 200 can optionally also include a second SIM interface 202b that can receive a second identification module SIM-2 204b associated with the second subscription.

The SIM in various embodiments may be a Universal Integrated Circuit Card (UICC) configured to have SIM and/or USIM (Universal Subscriber Identity Module) applications, thereby enabling access to, for example, GSM and/or UMTS networks. UICC can also provide storage for phonebooks and other applications. Alternatively, in a CDMA network, the SIM may be a UICC Mobile Subscriber Identity Module (R-UIM) or a CDMA Subscriber Identity Module (CSIM) on the card. Each SIM card can have CPU, ROM, RAM, EEPROM, and I/O circuitry. The SIMs used in various embodiments may include user account information, an International Mobile User Identification Number (IMSI), a collection of SIM Application Toolkit (SAT) commands, and a storage space for the phone book contact. The SIM card can also store a home public land mobile network that is used to indicate the SIM card network service provider's provider ( HPLMN) code. The integrated circuit card identification (ICCID) SIM serial number can be printed on the SIM card for identification.

The multi-custom multi-standby communication device 200 can include at least one controller (such as general purpose processor 206) that can be coupled to an encoder/decoder (CODEC) 208. The CODEC 208 can in turn be coupled to the speaker 210 and the microphone 212. The general purpose processor 206 can also be coupled to at least one memory 214. Memory 214 can be a non-transitory computer readable storage medium that stores processor-executable instructions. The memory 214 can store an operating system (OS), as well as user application software and executable instructions. The memory 214 can also store application data, such as array data structures.

The general purpose processor 206 can be coupled to the data machine 230. Data machine 230 can include at least one baseband data processor 216 that can be coupled to memory 222 and modulator/demodulator 228. The baseband data processor 216 can include physical or logically separate baseband modem processors (e.g., BB1, BB2). Modulator/demodulator 228 can receive data from baseband data processor 216 and can utilize the encoded data to modulate the carrier signal and provide modulated signals to one or more RF resources 218a, 218b for transmission. Modulator/demodulator 228 may also extract information bearing signals from modulated carrier waveforms received from one or more RF resources 218a, 218b, and may provide demodulated signals to baseband data processor 216. Modulator/demodulator 228 can be or include a digital signal processor (DSP).

The baseband data processor 216 can write information to and read information from the memory 222. The memory 222 can also store instructions associated with the protocol stack (eg, the agreement stack S1 222a and the agreement stack S2 222b). The protocol stacks S1 222a, S2 222b typically include computer executable instructions for implementing communications using radio access protocols or protocols. Each protocol stack S1 222a, S2 222b typically includes a layered network communication protocol layer for providing networking capabilities. Data machine 230 can include one or more protocol stacks in protocol stacks S1 222a, S2 222b for enabling communication using one or more RATs. The protocol stacks S1 222a, S2 222b may be associated with SIM cards (eg, SIM-1 204a, SIM 2 204b) that are configured with subscriptions. For example, the agreement stack S1 222a and the agreement stack S2 222b may be associated with the SIM-1 204a. Only two protocol stacks S1 222a, S2 222b are shown as being unrestricted, and memory 222 can store more than two protocol stacks (not shown).

Each of the multiple subscription multi-standby communication devices 200, SIM and/or RAT (eg, SIM-1 204a, SIM-2 204b) may be coupled to data machine 230 and may be associated with RF resources or allowed to use RF Resources. The term "RF resource" is used herein to refer to all circuitry for transmitting and receiving RF signals, which may include: a baseband data processor 216 that performs baseband/dataphone functions for communicating/controlling RAT with a RAT; One or more radio units including transmitter and receiver components, one or more of radio antennas 220a, 220b, shown as RF resources 218a, 218b (eg, in FIG. 2); An additional circuit that includes one or more amplifiers and wireless units. In some embodiments, the RF resources may share a common baseband data processor 216 (i.e., a single device that performs baseband/dataframe functions for all RATs on a multi-custom multi-standby communication device). In some embodiments, each RF resource can include a baseband processor (eg, BB1, BB2) that is physically or logically separated.

The RF resources 218a, 218b may include transceivers associated with one or more RATs and may perform transmit/receive functions for the mobile communication device 200 on behalf of their respective RATs. The RF resources 218a, 218b may include separate transmit and receive circuits. In some embodiments, RF resource 218b may only include receiving circuitry. The RF resources 218a, 218b may be coupled to wireless antennas (eg, first wireless antenna 220a and second wireless antenna 220b), respectively. The RF resources 218a, 218b may also be coupled to the baseband data processor 216.

In some embodiments, general purpose processor 206, memory 214, baseband processor 216, and RF resources 218a, 218b may be included in mobile communication device 200 as a system on a chip. In some embodiments, the first and second SIMs 204a, 204b and their respective interfaces 202a, 202b can be external to the system on a chip. Additionally, various input and output devices can be coupled to components on a system on a chip, such as an interface or controller. Example user input components suitable for use in the mobile communication device 200 can include, but are not limited to, a keypad 224 and a touchscreen display 226.

In some embodiments, the keypad 224, the touchscreen display 226, the microphone 212, or a combination thereof can perform reception. The function is called to initiate an outgoing call. For example, touch screen display 226 can receive a contact to a contact or receive a phone number from a contact list. In another example, either or both of touch screen display 226 and microphone 212 can perform the function of receiving a request to initiate an outgoing call. For example, touch screen display 226 can receive a contact to a contact or receive a phone number from a contact list. As another example, the request to initiate an outgoing call may be in the form of a voice command received via the microphone 212. An interface may be provided between the various software modules and functional units in the multi-custom multi-standby communication device 200 to enable communication therebetween.

In the case of working together, the two SIMs 204a, 204b, the baseband processor 216, the RF resources 218a, 218b and the antennas 220a, 220b can implement communication on two or more RATs. For example, one SIM, baseband processor, and RF resources can be configured to support two different RATs. In other embodiments, more RATs can be supported on a multi-custom multi-standby communication device by adding more SIM cards, SIM interfaces, RF resources, and antennas for connecting to additional mobile networks.

3 illustrates a method 300 for managing a first subscribed communication link by a processor of a multi-subscription multi-standby communication after tuning is detached to a second subscription, in accordance with some embodiments. Referring to Figures 1-3, method 300 can be a device processor of a multi-custom multi-standby communication device (e.g., multi-subscription multi-standby communication devices 110, 200 of Figures 1 and 2) For example, general purpose processor 206, baseband processor 216, separate controller, and/or the like are implemented.

In block 302, the device processor may return to the first subscription after performing the tuning detachment to the second subscription. For example, during the communication session using the first subscribed first communication network (eg, the first network 102), the device processor can perform a tune away procedure to use the second subscription from the second communication network. A path (e.g., second network 104) receives and/or transmits a signal to a second communication network (e.g., second network 104). After performing the tune away, the device processor can return the multi-subscription multi-standby communication device to the first subscribed frequency.

Upon completion of the tune away from the first subscription to the second subscription, in decision block 304, the device processor may determine whether the tune away period (i.e., the duration elapsed during the execution of the tune away) is greater than or Equal to the tuning off period threshold. In response to determining that the tuning off period is not greater than or equal to the tuning off period threshold (ie, decision block 304 = "No"), in block 330, the device processor can enter the normal connection mode (eg, RRC_Connected mode) and perform normal communication. .

In response to determining that the tuning off period is greater than or equal to the tuning off period threshold (ie, decision block 304 = "Yes"), in decision block 306, the device processor can determine whether the multi-subscription multi-standby communication device has a queue waiting for Any uplink data transmitted by a network. In response to determining that there is no queue waiting for uplink data to be transmitted to the first network (i.e., decision block 306 = "No"), in block 330, The device processor can enter the normal connection mode (eg, RRC_Connected mode) and perform normal communication.

In response to determining that the multi-subscription multi-standby communication device has uplink data queued for transmission to the first network (i.e., decision block 306 = "Yes"), the device processor may reduce the scheduling request threshold in block 308. (SR_TH). The scheduling request threshold may include the number of scheduling requests that the multi-subscription multi-standby communication device can send to the base station of the first communication network. The allowed conditions may be determined based on channel conditions (eg, received signal strength, RSSI, RSRP, or another received signal strength and/or signal strength indication) between the multi-custom multi-standby communication device and the base station of the first communication network. The reduced number of schedule requests.

In some embodiments, when the determined channel condition is relatively good, the device processor can determine a smaller number of allowed scheduling requests (ie, the better the channel condition, the fewer the number of scheduling requests allowed) In order to enable the multi-subscription multi-standby communication device to declare the radio link failure more quickly and initiate a connection re-establishment procedure for the first subscribed first communication link. In some embodiments, the reduced schedule request threshold (ie, the reduced number of allowed schedule requests) may be less than the standard schedule request threshold / the number of criteria allowed for the schedule request.

In some embodiments, the device processor can determine a weighting factor based on the determined channel condition, and the device processor can apply the weighting factor to adjust the reduced number of allowed scheduling requests. For example, the device processor can detect less than or equal to -100 The downlink RSRP of dBm and can be determined as a weighting factor of one. As another example, the device processor can detect a downlink RSRP between -100 dBm and -80 dBm and can determine a weighting factor of 0.75. As yet another example, the device processor can detect a downlink RSRP greater than -80 dBm and can determine a weighting factor of 0.5. In some embodiments, the device processor may multiply the determined weighting factor by the determined reduced number of allowed scheduling requests to adjust the allowed scheduling request based on the determined channel condition. The decision to reduce the number. Other examples are also possible.

In decision block 310, the device processor can determine whether the number of scheduling requests sent by the multi-subscription multi-standby communication device is greater than or equal to the reduced allowed number of scheduling requests. In response to determining that the number of scheduling requests sent by the multi-subscription multi-standby communication device is not greater than or equal to the reduced allowed number of scheduling requests (ie, decision block 310 = "No"), in block 312 The device processor can send one or more scheduling requests to the base station of the first communication network.

In decision block 314, the device processor can determine whether the multi-subscription multi-standby communication device receives an uplink grant (eg, in response to one or more transmitted schedule requests).

In response to the decision to receive the uplink grant (i.e., decision block 314 = "Yes"), in block 316, the device processor can reset the schedule request threshold (i.e., the schedule request threshold can be set to standard) Schedule request threshold or standard number of scheduled requests allowed ). Then in decision block 328, the device processor can decide whether to receive downlink feedback from the base station of the first communication network. For example, when a multi-subscription multi-standby communication device receives an uplink grant, the device processor can transmit at least some of the data queued for uplink transmission. In response to data sent from the multi-subscription multi-standby communication device, the multi-subscription multi-standby communication device can determine whether, for example, the base station or another network unit has sent feedback. In response to determining to receive downlink feedback (ie, decision block 328 = "Yes"), in block 330, the device processor can enter a normal connection mode (eg, RRC_Connected mode) and perform normal communication.

In response to the decision not to receive downlink feedback (i.e., decision block 328 = "No"), the device processor can perform the operations of method 400 described with reference to FIG.

Returning to decision block 314, in response to the decision not to receive the uplink grant (i.e., decision block 314 = "No"), in decision block 310, the device processor can again determine the transmission by the multi-subscription multi-standby communication device. Whether the number of scheduling requests is greater than or equal to the reduced allowed number of scheduling requests.

Returning to decision block 310, in response to determining that the number of scheduling requests sent by the multi-subscription multi-standby communication device is greater than or equal to the reduced allowed number of scheduling requests (ie, decision block 310 = "Yes"), In block 318, the device processor can reduce the number of random access channel (RACH) requests that the multi-subscription multi-standby communication device can send to the first network (ie, the RACH threshold or RACH_TH) ). In some embodiments, the reduced RACH threshold (ie, the reduced number of allowed random access channel requests) may be less than a standard RACH threshold or a standard number of allowed random access channel requests.

In some embodiments, the device processor can determine a weighting factor based on the determined channel condition, and the device processor can apply the weighting factor to adjust the reduced number of random access channel requests. For example, the device processor can detect a downlink RSRP less than or equal to -100 dBm and can determine a weighting factor of one. As another example, the device processor can detect a downlink RSRP between -100 dBm and -80 dBm and can determine a weighting factor of 0.75. As yet another example, the device processor can detect a downlink RSRP greater than -80 dBm and can determine a weighting factor of 0.5. In some embodiments, the device processor may multiply the determined weighting factor by the determined reduced number of allowed random access channel requests to adjust the allowed random based on the determined channel condition. The decision to access the reduced number of channel requests. Other examples are also possible.

In decision block 320, the device processor can determine whether the number of random access channel requests sent by the multi-subscription multi-standby communication device is greater than or equal to the RACH threshold.

In response to determining that the number of random access channel requests sent by the multi-subscription multi-standby communication device is not greater than or equal to the RACH threshold (ie, decision block 320 = "No"), in block 322, the device processes The device may send one or more random access channel requests (eg, to a base station of the first communication network). In decision block 324, the device processor can determine whether to grant a channel to the multi-subscription multi-standby communication device (e.g., in response to the one or more random access channel requests). In response to the decision not to grant the channel (i.e., decision block 324 = "No"), in decision block 320, the device processor can again determine if the number of random access channel requests sent by the multi-subscription multi-standby communication device is greater than Or equal to the RACH threshold.

In response to the decision granting the channel (i.e., decision block 324 = "Yes"), in block 326, the device processor can reset the RACH threshold (i.e., the RACH threshold can be set to the standard RACH threshold or allowed random). The standard number of access channel requests). Then in decision block 328, the device processor can decide whether to receive downlink feedback from the base station of the first communication network. For example, when a channel is granted to a multi-custom multi-standby communication device, the device processor can transmit at least some of the data queued for uplink transmission. In response to data sent from the multi-subscription multi-standby communication device, the multi-subscription multi-standby communication device can determine whether, for example, the base station or another network unit has sent feedback. In response to determining to receive downlink feedback (ie, decision block 328 = "Yes"), in block 330, the device processor can enter a normal connection mode (eg, RRC_Connected mode) and perform normal communication. In response to the decision not receiving downlink feedback (ie, decision block 328 = "No" The device processor can perform the operations of the method 400 described with reference to FIG.

Returning to decision block 320, in response to determining that the number of random access channel requests sent by the multi-subscription multi-standby communication device is greater than or equal to the RACH threshold (ie, decision block 320 = "Yes"), in block 332, the device processes The device may declare that the radio link of the first subscribed communication link has failed, and in block 334, initiate a connection re-establishment procedure for the first subscribed first communication link.

Considering that the tuning off period is long enough that a more customized multi-standby communication device may experience difficulty reestablishing communication on the first network, the device processor can be tuned off by reducing the scheduling request threshold and/or the random access channel threshold. After the second communication network, the radio link of the communication link with the first communication network is declared more quickly. Accordingly, the systems and methods of various embodiments improve the management of a first subscribed communication link by a multi-custom multi-standby communication device after tuning is detached to a second subscription.

4 illustrates a multi-subscription multi-standby communication device (eg, the multi-subscription multi-standby communication device 110, 200 of FIGS. 1 and 2) after tuning is detached to a second subscription, in accordance with some embodiments. A method 400 of managing a first customized communication link by a processor. Referring to Figures 1-4, method 400 can be performed by a processor of a multi-custom multi-standby communication device (e.g., general purpose processor 206, baseband processor 216, separate controller, and/or the like) (i.e., device processor) )achieve.

In response to the decision not to receive downlink feedback (i.e., decision block 328 of method 300 = "No"), in block 402, the device processor may reduce the duration of the uplink inactivity timer. In some embodiments, the communication link with the first communication network can include one or more resource bearers, and the device processor can determine an uplink inactivity timer for each resource bearer with pending uplink data. The reduced duration. The device processor can then use the reduced timer duration to measure activity or inactivity on the communication link (ie, for each resource bearer). In some embodiments, the duration of each uplink inactivity timer can be determined based on channel conditions (eg, the better the channel condition, the shorter the timer duration), so that the multi-subscription multi-standby communication device can be more Quickly determine the radio link failure. In some embodiments, the reduced duration of the uplink inactivity timer (ie, the reduced duration of the uplink inactivity timer) may be less than the standard uplink inactivity timer duration.

In some embodiments, the device processor can determine a weighting factor based on the determined channel condition, and the device processor can apply the weighting factor to adjust the reduced duration of the uplink inactivity timer. For example, the device processor can detect a downlink RSRP less than or equal to -100 dBm and can determine a weighting factor of one. As another example, the device processor can detect a downlink RSRP between -100 dBm and -80 dBm and can determine a weighting factor of 0.75. As yet another example, the device processor can detect large The downlink RSRP is at -80 dBm and can be determined as a weighting factor of 0.5. In some embodiments, the device processor may multiply the determined weighting factor by the determined reduced uplink inactivity timer duration to adjust the reduced uplink based on the determined channel condition. The decision of the duration of the road inactivity timer. Other examples are also possible.

In decision block 404, the device processor can determine if any uplink data has been sent on the communication link/resource bearer. In response to determining that the uplink data has not been transmitted (ie, decision block 404 = "No"), in decision block 406, the device processor can determine if the uplink inactivity timer has timed out (ie, at the device) The processor times out without sending any pending uplink data to the first network). In response to determining that the inactivity timer has not timed out (i.e., decision block 406 = "No"), in decision block 404, the device processor can continue to determine if any uplink data is on the communication link and/or resources. Send on the bearer.

In response to determining that the inactivity timer has timed out (i.e., decision block 406 = "Yes"), in block 418, the device processor may declare that the radio link of the first subscribed communication link failed, and in the block In 420, a connection re-establishment procedure is initiated for the first subscribed first communication link.

Returning to decision block 404, in response to determining that the uplink data has been transmitted (i.e., decision block 406 = "Yes"), in block 408, the device processor can stop the uplink inactivity timer. In block 410, the device processor may reduce the allowed number of retransmissions of data that the multi-subscription multi-standby communication device can transmit to the first network (ie, allow retransmission threshold or RACH_TH). In some embodiments, the reduced allowable retransmission threshold (i.e., the reduced number of allowed data retransmissions) may be less than a standard allowed retransmission threshold or a standard number of allowed data retransmissions.

In some embodiments, the device processor can determine a weighting factor based on the determined channel condition, and the device processor can apply the weighting factor to adjust the reduced number of allowed data retransmissions. For example, the device processor can detect a downlink RSRP less than or equal to -100 dBm and can determine a weighting factor of one. As another example, the device processor can detect a downlink RSRP between -100 dBm and -80 dBm and can determine a weighting factor of 0.75. As yet another example, the device processor can detect a downlink RSRP greater than -80 dBm and can determine a weighting factor of 0.5. In some embodiments, the device processor may multiply the determined weighting factor by the determined reduced number of allowed data retransmissions to adjust the allowed data retransmission based on the determined channel condition. The decision to reduce the number. Other examples are also possible.

In decision block 412, the device processor can decide whether downlink feedback is detected. For example, the device processor can detect downlink radio link control (DL RLC) feedback or control data feedback (eg, ACK) from the first network. Downlink feedback can be The device processor receives the transmission of the uplink data to the first network. In some embodiments, the device processor may determine the reception or reception failure of the downlink feedback per resource bearer.

In response to the decision not to detect downlink feedback (ie, decision block 412 = "No"), in block 414, the device processor may use the first subscription to transmit one or more uplink data retransmissions. . In decision block 416, the device processor can determine whether the number of transmitted data retransmissions is greater than or equal to the reduced allowed retransmission threshold. In response to determining that the amount of data retransmissions sent is not greater than or equal to the reduced allowed retransmission threshold (i.e., decision block 416 = "No"), in decision block 412, the device processor may continue to determine whether to detect Downlink feedback.

In response to determining that the amount of data retransmissions sent is greater than or equal to the reduced allowed retransmission threshold (i.e., decision block 416 = "Yes"), in block 418, the device processor may declare the radio link to fail and In block 420, a connection re-establishment procedure is initiated for the first subscribed first communication link.

Returning to decision block 412, in response to the decision to detect downlink feedback (ie, decision block 412 = "Yes"), in block 422, the device processor may reset the allow retransmission threshold (ie, may allow The retransmission threshold is set to the standard allowed retransmission threshold or the standard number of retransmissions allowed). In block 424, the device processor can then enter a normal connection mode (eg, RRC_Connected mode) and perform normal communication on the first subscription.

The device may be received in the case where the multi-subscription multi-standby communication device may receive the grant uplink resource but may not receive the downlink feedback data, by using the uplink inactivity timer and/or by reducing the allow retransmission threshold The processor can declare the radio link failure of the communication link with the first communication network more quickly after the tuning is detached from the second communication network. Accordingly, these systems and methods improve the management of a first customized communication link by a multi-subscription multi-standby communication device after tuning is detached to a second subscription.

Various embodiments (including but not limited to the embodiments described with reference to Figures 1-4) may be implemented in any of a variety of mobile communication devices, examples of which are illustrated in Figure 5 (e.g., mobile communication devices) 500). In various embodiments, the mobile communication device 500 (eg, which may correspond to the multi-custom multi-standby communication devices 110 and 200 of FIGS. 1 and 2) may include a touch screen controller 504 and an internal Processor 502 of memory 506. Processor 502 can be one or more multi-core integrated circuits designated for general purpose or dedicated processing tasks. Internal memory 506 can be volatile or non-volatile memory, and can also be secure and/or encrypted memory, or unsecure and/or unencrypted memory, or any combination thereof. The touch screen controller 504 and the processor 502 can also be coupled to the touch screen panel 512, such as a resistive touch screen, a capacitive touch screen, an infrared sensor screen, and the like. In addition, the display of the mobile communication device 500 does not need to have a touch screen function.

The mobile communication device 500 can have two or more wireless signal transceivers 508 coupled to each other and/or coupled to the processor 502 for transmitting and receiving communications (eg, Peanut, Bluetooth, ZigBee, Wi-) Fi, RF wireless unit) and antenna 510. Transceiver 508 and antenna 510 can be used with the circuits described above to implement various wireless transmission protocol stacks and interfaces. The mobile communication device 500 can include one or more cellular network wireless data signals coupled to the processor and antenna 510 for communication via two or more cellular networks via two or more radio access technologies. Wafer 516.

The mobile communication device 500 can include a peripheral device connection interface 518 that is coupled to the processor 502. Peripheral device connection interface 518 can be configured to receive one type of connection individually, or can be configured to receive various types of physical and communication connections (public and proprietary), such as USB, Firewire, Thunderbolt, or PCIe. The peripheral device connection interface 518 can also be coupled to a similarly configured peripheral device port (not shown).

The mobile communication device 500 can also include a speaker 514 for providing audio output. The mobile communication device 500 can also include a housing 520 constructed of a combination of plastic, metal, or material for containing all or some of the components discussed herein. The mobile communication device 500 can include a power source 522 coupled to the processor 502, such as a disposable or rechargeable battery. The rechargeable battery can also be coupled to the peripheral device port to receive charging current from a source external to the mobile communication device 500. The mobile communication device 500 can also include for receiving user input Physical button 524. The mobile communication device 500 can also include a power button 526 for turning the mobile communication device 500 on or off.

Processor 502 can be any programmable microprocessor, microcomputer or processor chip that can be configured by software instructions (applications) to perform various functions, including the functionality of the various embodiments described below. In some mobile communication devices, multiple processors 502 may be provided, such as one processor dedicated to wireless communication functions and one processor dedicated to executing other applications. Typically, the software application can be stored in internal memory 506 before it is accessed and loaded into processor 502. Processor 502 can include internal memory sufficient to store application software instructions.

Various embodiments may be implemented in any number of single processor systems or multi-processor systems. Typically, programs are implemented on a processor in a short slice of time so that it appears that multiple programs are executing simultaneously on a single processor. When the program is removed from the processor at the end of the time slice, information relating to the current operational state of the program is stored in memory so that the program can resume its operation innocently while it is executing on the return processor. . The operation status data may include: a program address space, a stack space, a virtual address space, a register setting image (for example, a program counter, a stack indicator, an instruction register, a program status word, etc.), and charging information. , permissions, access restrictions, and status information.

The program can generate other programs, and the generated program (ie, the subprogram) may inherit the generated program (ie, the parent program). Some of the permissions and access restrictions (ie context). The program can be a heavyweight program that includes multiple feather level programs or threads that are shared with other programs/threads (eg, address space, stacking, licensing, and/or All or part of the program for access restrictions, etc.) Thus, a single program can include multiple feather-level programs or threads that share, have access to a single context (ie, the context of the processor), and/or operate within a single context.

The above description of the method and the flowchart of the program are provided for illustrative purposes only, and are not intended to be required or implied. As will be appreciated by those of ordinary skill in the art to which the present invention pertains, the sequence of blocks in the foregoing embodiments can be performed in any order. Words such as "after", "subsequent", "next" are not intended to limit the order of the blocks; these words are only used to guide the reader in reading the description of the method. In addition, any reference to a claim element in the singular (for example, the articles "a", ""

The various illustrative logical blocks, modules, circuits, and algorithm blocks described in connection with the embodiments disclosed herein can be implemented as an electronic hardware, a computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and blocks described above are generally described in terms of their function. Whether such functionality is implemented as hardware or software depends on the specific application and design constraints imposed on the overall system. Those with ordinary knowledge can The application is implemented in a variant to implement the described functionality, but such implementation decisions should not be construed as a departure from the scope of the various embodiments.

A general purpose processor, digital signal processor (DSP), special application integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic device designed to perform the functions described herein may be utilized , individual gate or transistor logic devices, individual hardware components, or any combination thereof, implement or perform various illustrative logic elements, logic blocks, modules, and circuits for implementing the embodiments described herein in connection with the embodiments disclosed herein. Hardware. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any general processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of communication devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some blocks or methods may be performed by a function-specific circuit.

In various embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the function can be stored as one or more instructions or code on non-transitory computer readable media or non-transitory processor readable media. The operations of the methods or algorithms disclosed herein may be embodied in a processor executable software module that may be located on a non-transitory computer readable or processor readable storage medium. The non-transitory computer readable or processor readable storage medium can be any storage medium that can be accessed by a computer or processor. Such non-transitory computer readable or processor by way of example and not limitation The readable medium can include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to store the required code in the form of an instruction or data structure. And any other media that can be accessed by a computer. As used herein, disks and optical discs include compact discs (CDs), laser discs, compact discs, digital versatile discs (DVDs), floppy discs, and Blu-ray discs, where the discs are typically magnetically replicated while the discs are used. Laser to optically copy data. Combinations of the above should also be included within the scope of non-transitory computer readable and processor readable media. In addition, the operations of the method or algorithm may be one of code and/or instructions, or any combination thereof, or a collection of non-transitory processor readable media and/or computer readable software that may be incorporated into a computer program product. In the media.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to practice or use the embodiments. Various modifications to these embodiments will be readily apparent to those skilled in the <RTIgt; </RTI> <RTIgt; </ RTI> <RTIgt; </ RTI> <RTIgt; Example. Therefore, the various embodiments are not intended to be limited to the embodiments shown herein, but are to be accorded to the broadest scope of the invention and the principles and novel features disclosed herein.

300‧‧‧ method

302‧‧‧ squares

304‧‧‧Decision box

306‧‧‧Decision box

308‧‧‧ squares

310‧‧‧Decision box

312‧‧‧ square

314‧‧‧Decision box

316‧‧‧ square

318‧‧‧ square

320‧‧‧Decision box

322‧‧‧ squares

324‧‧‧Decision box

326‧‧‧ squares

328‧‧‧Decision box

330‧‧‧ square

332‧‧‧ squares

334‧‧‧ square

Claims (30)

A method for managing a first subscribed communication link by a processor of a multi-custom multi-standby communication device, the method comprising the steps of: returning after a tuning is deactivated to a second subscription At the first subscription, determining whether a tuning off period is greater than or equal to a tuning off period threshold; in response to determining that the tuning off period is greater than or equal to the tuning off period threshold, reducing a scheduling request threshold; determining a scheduled schedule Whether the quantity of the request is greater than or equal to the reduced scheduling request threshold; sending one or more scheduling requests in response to the number of scheduling requests that are determined to be sent is not greater than or equal to the reduced scheduling request threshold; Reducing a random access channel request threshold in response to determining that the number of scheduled requests sent is greater than or equal to the reduced scheduling request threshold; determining whether a number of random access channel requests sent is greater than or equal to the reduced Random access channel request threshold; the number of random access channel requests responsive to the decision to send is not greater than or equal to the reduced Access channel request threshold, a transmission request or more random channels; and In response to determining that the number of random access channel requests sent is greater than or equal to the reduced random access channel request threshold, a radio link failure of the first subscribed communication link is declared. The method of claim 1, wherein in response to determining that the tuning off period is greater than or equal to the tuning off period threshold, reducing the scheduling request threshold comprises the step of: in response to determining that the tuning off period is greater than or equal to the tuning off period threshold, Determining whether the data is queued for uplink transmission; and in response to determining that the tuning out period is greater than or equal to the tuning off period threshold and the data is queued for uplink transmission, reducing the scheduling request threshold. According to the method of claim 1, the method further includes the steps of: determining whether an uplink grant is received in response to the one or more scheduling requests; and resetting the scheduling in response to determining to receive an uplink grant Request threshold. The method of claim 1, further comprising the steps of: deciding whether to grant a channel in response to the one or more random access channel requests; and resetting the random access channel request threshold in response to determining to grant a channel . According to the method of claim 1, the method further includes the steps of: determining whether to receive an uplink grant or granting a channel, determining whether to receive downlink feedback; and responding to the decision not to receive downlink feedback, reducing A duration of an uplink inactivity timer. According to the method of claim 5, the method further includes the step of declaring a radio link failure in response to determining that the uplink inactivity timer has timed out. According to the method of claim 1, the method further includes the steps of: determining whether uplink data is sent on the communication link; responding to the decision that the uplink data has been sent, reducing a allowed retransmission threshold; and responding to the decision without detecting Downlink feedback is detected and one or more uplink retransmissions are sent. The method of claim 7, further comprising the step of declaring a first predetermined radio link of the communication link in response to determining that the number of uplink retransmissions is greater than or equal to the reduced allowed retransmission threshold failure. According to the method of claim 7, the method further includes the step of: resetting the allowed retransmission threshold in response to determining to detect downlink feedback. The method of claim 1, wherein declaring a radio link failure of the first subscribed communication link comprises the step of initiating a connection re-establishment procedure for the first subscribed communication link. A multi-custom multi-standby communication device comprising: a plurality of radio frequency (RF) chains; and a processor coupled to the plurality of RF chains and configured to: after a tuning is detached to a second subscription Returning to a first subscription, determining whether a tuning off period is greater than or equal to a tuning off period threshold; in response to determining that the tuning off period is greater than or equal to the tuning off period threshold, reducing a scheduling request threshold; determining the transmitted row Whether the quantity requested by the process is greater than or equal to the reduced scheduling request threshold; sending one or more scheduling requests in response to the number of scheduling requests that are determined to be sent is not greater than or equal to the reduced scheduling request threshold Reducing a random access channel request threshold in response to determining that the number of scheduled requests sent is greater than or equal to the reduced scheduling request threshold; Determining whether a quantity of random access channel requests sent is greater than or equal to the reduced random access channel request threshold; the number of random access channel requests in response to determining transmission is not greater than or equal to the reduced random access a channel request threshold, transmitting one or more random channel requests; and declaring the first subscribed communication link in response to determining that the number of random access channel requests sent is greater than or equal to the reduced random access channel request threshold A radio link of the road failed. Determining a multi-standby communication device according to the request item 11, wherein the processor is further configured to: determine whether the data is queued for uplink transmission in response to determining that the tuning release period is greater than or equal to the tuning off period threshold; And in response to determining that the tuning off period is greater than or equal to the tuning off period threshold and the data is queued for uplink transmission, reducing the scheduling request threshold. The multi-standby communication device is customized according to the request item 11, wherein the processor is further configured to: determine whether an uplink grant is received in response to the one or more scheduling requests; and respond to the decision to receive one Uplink grant, reset the schedule request threshold. Configuring a multi-standby communication device according to the request item 11, wherein the processor is further configured to: determine whether to grant a channel in response to the one or more random access channel requests; and respond to the decision to grant a channel , reset the random access channel request threshold. The multi-standby communication device is customized according to the request item 11, wherein the processor is further configured to: in response to determining to receive an uplink grant or grant a channel, determine whether to receive downlink feedback; and respond to It is decided that no downlink feedback is received, reducing a duration of an uplink inactivity timer. The multi-standby communication device is subscribed according to the request item 15, wherein the processor is also configured to declare a radio link failure in response to determining that the uplink inactivity timer has timed out. The multi-standby communication device is customized according to the request item 11, wherein the processor is also configured to: determine whether uplink data is sent on the communication link; and in response to the decision that the uplink data has been sent, reduce an allowable Retransmission threshold; and In response to the decision not to detect downlink feedback, one or more uplink retransmissions are sent. Dedicating a multi-standby communication device according to the request item 17, wherein the processor is further configured to: declare a radio link in response to determining that an amount of uplink retransmission is greater than or equal to the reduced allowed retransmission threshold failure. The multi-standby communication device is customized according to the request item 17, wherein the processor is also configured to: reset the allowable retransmission threshold in response to determining to detect the downlink feedback. The multi-standby communication device is customized according to the request item 17, wherein the processor is also configured to initiate a connection re-establishment procedure for the first subscribed communication link. A non-transitory processor readable storage medium having processor executable software instructions stored thereon, the processor executable software instructions configured to: have a plurality of subscriptions having a plurality of radio frequency (RF) chains A processor of the standby communication device performs an operation of determining whether a tuning off period is greater than or equal to a tuning off period threshold when returning to a first subscription after the tuning is deactivated to a second subscription; Responding to determining whether the tuning off period is greater than or equal to the tuning off period threshold, reducing a scheduling request threshold; determining whether a quantity of the scheduled scheduling request is greater than or equal to the reduced scheduling request threshold; The number of scheduling requests is not greater than or equal to the reduced scheduling request threshold, one or more scheduling requests are sent; the number of scheduling requests that are determined to be sent is greater than or equal to the reduced scheduling request threshold Reducing a random access channel request threshold; determining whether a number of random access channel requests sent is greater than or equal to the reduced random access channel request threshold; in response to determining the number of random access channel requests sent Transmitting one or more random channel requests greater than or equal to the reduced random access channel request threshold; and responding to determining that the number of random access channel requests sent is greater than or equal to the reduced random access channel request threshold Declaring that a radio link of the first subscribed communication link fails. The non-transitory processor readable storage medium of claim 21, wherein the stored processor executable software instructions are configured to cause a processor to perform an operation in response to determining the tone Decreasing a schedule request threshold by greater than or equal to the tuning off period threshold includes: determining whether the data is queued for uplink transmission in response to determining that the tuning off period is greater than or equal to the tuning off period threshold; and responding The scheduling request threshold is decreased by determining that the tuning off period is greater than or equal to the tuning off period threshold and the data is queued for uplink transmission. The non-transitory processor readable storage medium of claim 21, wherein the stored processor executable software instructions are configured to cause a processor to perform operations further comprising: responding to the one or more rows The process request determines whether an uplink grant is received; and in response to determining to receive an uplink grant, resets the scheduling request threshold. The non-transitory processor readable storage medium of claim 21, wherein the stored processor executable software instructions are configured to cause a processor to perform operations further comprising: responding to the one or more randomities Accessing the channel request, deciding whether to grant a channel; and in response to the decision granting a channel, resetting the random access channel request threshold. The non-transitory processor readable storage medium of claim 21, wherein the stored processor executable software instructions are configured to cause a processor to perform operations further comprising: in response to determining to receive an uplink The channel grants or grants a channel to decide whether to receive downlink feedback; and in response to the decision not to receive downlink feedback, reducing a duration of an uplink inactivity timer. The non-transitory processor readable storage medium of claim 25, wherein the stored processor executable software instructions are configured to cause a processor to perform operations further comprising: in response to determining the uplink not The activity timer has timed out, stating that a radio link has failed. The non-transitory processor readable storage medium of claim 21, wherein the stored processor executable software instructions are configured to cause a processor to perform operations including: determining whether to transmit on the communication link Uplink data; in response to the decision that the uplink data has been transmitted, reducing the allowed retransmission threshold; and in response to the decision not to detect the downlink feedback, transmitting one or more uplink retransmissions. The non-transitory processor readable storage medium of claim 27, wherein the stored processor executable software instructions are configured to cause a processor to perform operations further comprising: in response to determining an uplink retransmission A quantity is greater than or equal to the reduced allowed retransmission threshold, declaring a radio link failure. The non-transitory processor readable storage medium of claim 27, wherein the stored processor executable software instructions are configured to cause a processor to perform operations further comprising: responding to a decision to detect a downlink Road feedback, reset the allowable retransmission threshold. A multi-custom multi-standby communication device, comprising: means for determining whether a tuning off period is greater than or equal to a tuning off period threshold when returning to a first subscription after tuning is detached to a second subscription; And a unit for reducing a scheduling request threshold in response to determining that the tuning off period is greater than or equal to the tuning off period threshold; determining whether a quantity of the scheduled scheduling request is greater than or equal to the reduced scheduling request threshold a unit for transmitting one or more scheduling requests in response to the number of scheduling requests that are determined to be sent is not greater than or equal to the reduced scheduling request threshold; Means for reducing a random access channel request threshold in response to the number of scheduling requests that determine the transmission being greater than or equal to the reduced scheduling request threshold; determining whether the number of random access channel requests sent is a unit greater than or equal to the reduced random access channel request threshold; transmitting one or more in response to the determined number of random access channel requests being sent is not greater than or equal to the reduced random access channel request threshold a unit of random channel request; and a radio for declaring the first subscribed communication link in response to the number of random access channel requests for determining transmission being greater than or equal to the reduced random access channel request threshold The unit where the link failed.