EP2832174A1 - Network based detection and mitigation of hybrid client device reception outage events - Google Patents
Network based detection and mitigation of hybrid client device reception outage eventsInfo
- Publication number
- EP2832174A1 EP2832174A1 EP13733094.0A EP13733094A EP2832174A1 EP 2832174 A1 EP2832174 A1 EP 2832174A1 EP 13733094 A EP13733094 A EP 13733094A EP 2832174 A1 EP2832174 A1 EP 2832174A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- client device
- network
- wireless
- reception
- lte
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
- H04L1/0026—Transmission of channel quality indication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/02—Access restriction performed under specific conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1215—Wireless traffic scheduling for collaboration of different radio technologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
Definitions
- the present disclosure relates generally to operation within heterogeneous wireless systems such as, for example, hybrid network operation in which client devices can communicate using any one of several networks. More particularly, in one exemplary regard, the present disclosure introduces methods and apparatus for network-based detection and mitigation of hybrid client device reception outage events.
- a cellular network operator provides mobile telecommunications services to the public via a network infrastructure of e.g., cellular base stations (BS), base station controllers, infrastructure nodes, etc.
- BS base stations
- cellular network technologies e.g., cellular base stations (BS), base station controllers, infrastructure nodes, etc.
- BS base stations
- multimode operation allows a device to operate on any one of several network technologies, but does not enable operation on multiple network technologies simultaneously,
- a hybrid device can support both: (i) Long Term Evolution (LTE) and (ii) Code Division Multiple Access I X (CDMA IX) networks; i.e., the device can maintain a simultaneous connection between a first LTE network and a second CDMA IX network.
- LTE Long Term Evolution
- CDMA IX Code Division Multiple Access I X
- a LTE/CDMA IX hybrid device can conduct a voice call over the CDMA IX network while the mobile device is in LTE mode.
- a hybrid device can support both: ( ⁇ ) CDMA 1 X-EVDO (Evolution Data Optimized) and (ii) CDMA I X networks.
- hybrid network operation rely on the client device to manage its own operation between networks.
- the client device is responsible for maintaining its active connections to the various service networks; there are no required changes to existing network installations (i.e., hybrid network operation does not affect the legacy hardware and software of the network infrastructure).
- Cl ient-centric hybrid operation has several benefits. For example, there is very little (if any) infrastructure cost for the network operator. Moreover, hardware costs can be incorporated into the price of consumer devices. Additionally, hybrid network operation will not affect existing legacy devices. Similarly, devices capable of hybrid operation are also capable of normal operation.
- the client device will inevitably experience certain scheduling collisions.
- a mobile device while a mobile device is attached to the first LTE network, it must periodically ''tune out" the LTE network to perform CDMA IX actions (such as decoding the Quick Paging Channel (QPCH) to determine if the device is being paged). If the mobile device is receiving data from the LTE network during the tune out period, this data is lost, which may negatively impact throughput and ultimately user experience.
- a tuned-out mobile device will miss any broadcasted updated network resource information or control data; this can result in the mobile device being barred from access to the LTE network (at least for a period of time).
- network resources which are assigned to a tuned-out client device are wasted and/or underutilized.
- the aforementioned needs are satisfied by providing, inter alia, improved apparatus and methods for detection and mitigation of hybrid client device reception outage events.
- the method includes: determining a reception loss event associated with a client-device; adjusting operation for the client device; monitoring for reception recovery; if reception is recovered, resuming normal operation; and otherwise disconnecting the client device.
- the apparatus is a network-based entity (e.g., server).
- the apparatus is a mobile device such as a smartphone or tablet computer.
- the apparatus includes at least one wireless interface configured for wireless communication via at least first and second wireless technologies, the first technology being different than the second technology; at least one processor in data communication with the at least one wireless interface; and logic in data communication with the at least one processor.
- the logic is configured to: identify the occurrence of a reception loss event associated with a wireless interface of a client device, the wireless interface of the client device being compliant with the second wireless technology; adjust at least one aspect of the operation for the client device (e.g., the adjustment comprising adjustment of at least one aspect which will result in reduced network resource utilization by the client device for at least a period of time in one variant); monitor for reception recovery by the client device; when reception is recovered, resume operation according to an established protocol; and disconnect the client device when reception is not recovered.
- a computer-readable storage apparatus is further disclosed.
- the apparatus includes a storage medium having at least one computer program stored thereon, the at least one program being configured to, when executed, cause a computerized device to determine a reception loss event associated with a client-device; adjust operation for the client device; monitor for reception recovery; if reception is recovered, resume normal operation; and otherwise disconnect the client device.
- a hybrid network system is also disclosed, in one embodiment, the system includes at least two networks, and at least one network of the hybrid network system prioritizes one or more of its tasks based on high-priority tasks of one or more others of the at least two networks.
- a client device capable of hybrid network operation is further disclosed herein.
- the client device is a mobile wireless-enabled device one or more air interfaces for communication with multiple different wireless network infrastructures.
- a client device useful with in a wireless network is also disclosed, in one embodiment, the wireless network is configured to provide network-based detection and mitigation of client device reception outage events, and the client device includes: at least one wireless interface, the at least one interface configured for wireless communication via at least first and second wireless technologies, the first technology being different than the second technology; at least one processor in data communication with the at least one wireless interface; and logic in data communication with the at least one processor, in one variant, the logic is configured to: signal the occurrence or incipient occurrence of a reception loss event associated with the at least one wireless interface to a network entity; receive at least one adjustment of at least one aspect of the operation for the client device, the adjustment comprising adjustment of at least one aspect which will result in reduced network resource utilization by the client device for at least a period of time; and implement the received adjustment.
- a method of operating a wireless network entity so as to mitigate wasting of network resources associated with at least one mobile device of the network includes: receiving one or more communications from the at least one mobile device; evaluating the received one or more communications; inferring from the evaluation that a loss of reception event is incipient for the at least one mobile device; and adjusting operation of at least one of (i) the network, and/or (ii) the at least one mobile device based at least in part on the inference, the adjusting providing the mitigation.
- FIG. 1 is a logical block diagram illustrating one exemplary hybrid network system useful in conjunction with various features of the present disclosure.
- FIG. 2 is a functional block diagram of an exemplary embodiment of a user equipment
- FIG. 3 is a graphical representation of tune-away periods along an exemplary time line, in accordance with one embodiment.
- FIG. 4 is a logical flow diagram detailing one embodiment of a method for network- based detection and mitigation of hybrid client device reception outage events.
- FIG. 5 is a logical flow diagram detailing one exemplary implementation of the method of FIG. 4 in the context of Long Term Evolution network and a Code Division Multiple Access I networks.
- FIG. 6 is a functional block diagram of an exemplary embodiment of a wireless network apparatus useful for implementing various of the methods of the disclosure.
- LTE Long Term Evolution
- CDMA IX Code Division Multiple Access IX
- CDMA I X EVDO Evolution Data Optimized
- TD-LTE Time-Division Long-Term Evolution
- TD-LTE-Advanced Time Division Synchronous Code Division Multiple Access
- GSM Global System for Mobile Communications
- the various features are useful in combination with any network (cellular, wireless, wireline, or otherwise) that can benefit from network-based detection and mitigation of hybrid client device reception outage events.
- FIG. 1 illustrates an exemplary hybrid network system 100.
- the exemplary hybrid network includes a first LTE RAN (radio access network) 102A and a second CDMA IX RAN 102B in communication with a user equipment (UE) client device 200.
- LTE RAN radio access network
- CDMA IX RAN user equipment
- the LTE RAN and CDMA I X RAN are unsynchronized, and entirely unaware of the other RAN's operation.
- the RANs may have higher levels of coordination; e.g., the RANs may be loosely synchronized, or even tightly synchronized in certain aspects of their operation.
- the UE of FIG. 2 may be, for instance, a single-radio solution to support circuit-switched calls on a CDMA I X network and packet-switched calls on LTE; specifically, the UE has a single Radio Frequency (RF) processing "chain" which is used alternately for CDMA IX or LTE processing. Specifically, the single RF chain periodically tunes away from LTE and monitors CDMA I X activity, and vice versa.
- RF Radio Frequency
- the UE includes: (i) one or more Radio Frequency (RF) front-ends 202 (e.g., other RF front-ends may be present for other radio access technologies, etc.), (ii) one or more baseband processors 204, and (iii) at least one application processor 206 and associated memor(ies) 208.
- RF Radio Frequency
- the RF front-ends and baseband processors may be further specialized to handle a single wireless technology, or generalized to encompass multiple wireless technologies.
- the exemplary UE includes a first RF front-end that is coupled to both first and second baseband processors adapted to interface to a LTE network and CDMA IX network, respectively.
- first and second baseband processors adapted to interface to a LTE network and CDMA IX network, respectively.
- the foregoing configuration is purely illustrative, and various implementations may include other cellular technologies such as GSM, GPRS, EDGE, WCDMA, CD A2000, CDMA IX EVDO, LTE-A (LTE Advanced), etc. in various combinations.
- a RF front-end can (and generally will) include multiple receive and/or transmit antennas and/or chains.
- M1MO Multiple In Multiple Out
- SISO Single In Single Out
- MISO Multiple in Single Out
- SIMO Single In Multiple Out
- the UE 200 further includes a switching fabric 210 that can connect any one (or more) of the baseband processors 204 to various one (or more) of the antennas 202.
- the illustrated switching fabric is adapted to connect either the LTE baseband or CDMA IX baseband to the RF front-end.
- common embodiments may connect one baseband processor to one antenna ("one-to-one"), one-to-many, many-to- one, etc. This "switching" capability is desirable for a number of reasons, including inter alia: (i) power management, (ii) processing efficiency/flexibility, and (iii) antenna isolation constraints may require that only a subset of radios of a mobile device are active at any one time.
- the UE may include user interface components (display screens, buttons, touch screens such as a multi-touch display, dials, etc.), memory components (e.g., RAM (Random Access Memory), Flash, hard disk drives (HDD), etc.), power management components (e.g., batteries, charger components, etc.), and external interfaces (e.g., FireWireTM, Universal Serial BusTM (USB), Thunderbolt, etc.).
- user interface components display screens, buttons, touch screens such as a multi-touch display, dials, etc.
- memory components e.g., RAM (Random Access Memory), Flash, hard disk drives (HDD), etc.
- power management components e.g., batteries, charger components, etc.
- external interfaces e.g., FireWireTM, Universal Serial BusTM (USB), Thunderbolt, etc.
- FIG. 2 is merely illustrative of one exemplary embodiment. Still other variants useful with the various features disclosed herein are described with greater detail in co-owned and co-pending U.S.
- the exemplary UE 200 of FIG. 2 is capable of LTE/CDMA IX hybrid mode operation within, e.g., the hybrid network system of FIG. 1. Specifically, the UE 200 can place CDMA I X voice calls while registered with the LTE network. During hybrid operation, the UE can be registered to both a LTE network 102A and a CDMA IX network 102B. The UE is capable of receiving and responding to data and control messaging from either the LTE network or the CDMA IX network; however, as previously discussed, the UE cannot respond simultaneously to both networks, and hence in the illustrated embodiment is configured to always prioritize CDMA IX (voice call) traffic over LTE (data) traffic to ensure that user experience for voice calls is unaffected. Other implementations may have other prioritization schemes (e.g., where voice calls are lower priority, based on the type of traffic, historic device usage, QoS requirements, etc.)
- the UE 200 Once the UE 200 has connected to the LTE network 102A, the UE will periodically
- tune-away operation is subsumed in a larger group of client device reception outage events.
- these client device reception outage events are initiated by the client device (with or without network coordination) to intentionally or indirectly disable reception of the client device to achieve some other purpose or goal.
- Common examples include e.g., to perform measurements on other networks, to reduce power consumption, to reduce interference on other nearby devices, to preserve processing resources for other applications, etc.
- Tune-away events may be periodic in nature (or otherwise predictably scheduled), or may be entirely unpredictable, interrupting events, or variants or combinations thereof. The duration of tune-away events widely varies from a few milliseconds to several seconds.
- the UE may periodically tune-away from a LTE network to tune-in to the CDMA IX network to detect a paging channel, and perform serving cell and neighbor cell measurements of the CDMA I X network. More rarely, the tune-away event may require a substantially longer time interval to perform lengthy maintenance tasks. For example, one exemplary time line is shown in FIG. 3. As illustrated, over the course of normal operation, the mobile device periodically tunes to the CDMA IX network for brief time intervals 302. Occasionally, the device must perform much lengthier tasks 304.
- LAU Location Area Updates
- the mobile device must actively exchange information with the CDMA IX network, periods of poor reception (e.g., the mobile device may need additional time to decode messaging (e.g., paging channels, etc.)), etc.
- decode messaging e.g., paging channels, etc.
- TD-LTE Time-Division Long-Term Evolution
- TD-SCDMA Time Division Synchronous Code Division Multiple Access
- LTE also referred to as Frequency Division Duplex LTE (FD-LTE)
- FD-LTE Frequency Division Duplex LTE
- TD-LTE Time Division Duplex LTE
- the downlink and the uplink are on the same frequency and the separation occurs in the time domain, so that each direction in a call is assigned to specific timeslots.
- Time Division Synchronous Code Division Multiple Access allows traffic to be uplinked (from the mobile terminal to the base station) and downlinked (from the base station to the mobile terminal) using different time slots in the same frame.
- Embodiments of the present disclosure contemplate the use of these technologies together and separately (in combination with other technologies) in a hybrid network, such as by implementing the methodology described herein with respect to FIG. 4 (except using one or more different combinations of radio access technologies set forth herein).
- a UE connected to the TD-LTE network will periodically (or on an event driven or other basis) tune its radio away from the TD-LTE network to perform TD-SCDMA actions such as cell selection, registration, and receiving pages.
- GSM Global System for Mobile Communications
- GPRS General Packet Radio Service
- EDGE Enhanced Data rates for GSM Evolution
- UMTS Universal Mobile Telecommunications System
- Various other common embodiments may further combine either LTE, or TD-LTE with any of GSM, GPRS, EDGE, UMTS, etc.
- the network e.g., the evolved NodeB (eNB)
- the eNB may not be aware that the UE is tuned out. This can have significant undesirable effects. For example, the eNB may grant either uplink (UL) resources to the UE (which will be unused), or downlink (DL) resources for transmissions (which will be missed).
- UL uplink
- DL downlink
- the eNB will not receive Physical UpHnk Control Channel (PUCCH) information (e.g., Hybrid Automatic Repeat Request (HARQ) Acknowledgment (AC ) Non- acknowledgements (NACK); Channel Quality Indication (CQI), Rank Indication (RI), Precoding Matrix Information (PMI), etc.), which may result in unnecessary retransmissions, and/or incorrect or stale information.
- PUCCH Physical UpHnk Control Channel
- HARQ Hybrid Automatic Repeat Request
- AC Non- acknowledgements
- CQI Channel Quality Indication
- RI Rank Indication
- PMI Precoding Matrix Information
- stale information may occur when the UE is improperly operating with "stale" information. For example, if the eNB does not receive Sounding Reference Signals (SRS), the eNB may improperly schedule the UE for UL scheduling. Similarly, where the Radio Resource Connection (RRC) inactivity timer expires during tuned away operation, the UE and eNB can lose synchronization. In either circumstance, the UE may transmit control signaling on stale resources (e.g., PUCCH transmissions, SRS transmissions, Physical Random Access Channel (PRACH), etc.) which contributes to overall network pollution. in still other situations, the UE and the eNB may lose connectivity altogether. This can create a prolonged service blackout for the UE. For example, premature Radio Link Failure (RLF) may result in further synchronization problems, spotty reception, and excessive connection attempts.
- RLF Radio Link Failure
- a client device is connected to a first network, where the first network is entirely unaware of the client device's connections to other networks.
- the first network may have limited information on nearby networks (e.g., timing information, registered devices, etc.) which may be periodically refreshed, but is not integrated within the operational decisions for the first network.
- the network determines a reception loss event associated with a client- device.
- the reception loss is detected on the basis of one or more signaling exchanges or events which are incomplete and/or not received.
- reception loss is detected on the basis of a length of time during which no signaling is received from the client device.
- reception loss events are signaled to the network.
- the signaling is implicit in one or more existing protocols (that is, by mere invocation of the protocol, a loss event can be inferred).
- the signaling may be explicit (e.g., using a dedicated message protocol implemented for that purpose, or alternatively an existing message protocol that has been "repurposed” or upon which the necessary signaling is "piggybacked"), or may use a "mixed" approach of implicit and explicit techniques, such as where one of the two is more appropriate to one operating circumstance, and the other technique to another circumstance.
- reception loss is based on one or more failed access attempts initiated by the network.
- the network adjusts operation for the client device.
- the network adjusts by reserving fewer resources for the client device.
- the network may not reserve any resources for the client device.
- the network may deactivate one or more layers of device context.
- the one or more layers of device context include state information for one or more communication protocol stack software elements or layers.
- the network may deactivate one or more of: a physical software layer, a radio link layer, a medium access (e.g., MAC) layer, etc.
- the network monitors for reception recovery; if reception is recovered, the network resumes normal operation (which may occur immediately, or after a "wait" or other period to endure that reception has been in fact reliably recovered, so as to e.g., prevent the device from cycling modes repeatedly), in one embodiment, the network and client device negotiate resources for the connected operation, in alternate embodiments, the network and client device resume or re-negotiate one or more layers of device context information. For example, in one such example, the network may reactivate one or more of: a physical software layer, a radio link layer, a medium access layer, etc.
- the network simply defaults to the allocation that was associated with the client immediately before the loss event; this approach advantageously obviates further negotiation between the network and client device.
- the choice of which of the foregoing techniques to apply is determined based on one or more criteria; e.g., time duration of the loss event. For example, if the loss event duration is comparatively short (say, 100ms in the example context discussed supra), then the network will choose to reinstitute the prior resource allocation without negotiation. However, when a prescribed threshold is exceeded (say, e.g., 1000ms or I s), then the renegotiation is invoked.
- a prescribed threshold say, e.g., 1000ms or I s
- the network disconnects the client device at step 408.
- Example Operation - Referring now to FIG. 5, one exemplary implementation of the method 400 of FIG. 4 is shown and described. Specifically, one exemplary embodiment of a method 500 for network-based detection and mitigation of hybrid client device reception outage events is illustrated.
- the hybrid client device is a single-radio solution capable of communicating with a Long Term Evolution (LTE) network and Code Division Multiple Access I (CDMA IX) network. While the following operation is described with reference to the evolved Node B (eNB) of the LTE network, it is readily appreciated that various aspects of the present invention are widely applicable to base stations (regardless of technology), and more generally wireless server devices of any type (e.g., ad hoc networks, etc.)
- the eNB configures the UE with a dedicated Physical Uplink Control Channel (PUCCH) and/or Sounding Reference Signal (SRS) resources during Radio Resource Connection (RRC) setup.
- the dedicated PUCCH resources enable the UE to transmit one or more of: Scheduling Requests (SR), Channel Quality Indications (CQI), Rank indications (Ri), and/or Precoding Matrix indexes (PMI).
- SR Scheduling Requests
- CQI Channel Quality Indications
- Rh Rank indications
- PMI Precoding Matrix indexes
- Each PUCCH resource is identified according to, inter alia: location (e.g., time slot, subcarrier), periodicity, and offset of the dedicated resource.
- Dedicated SRS resources are specified according to a bandwidth, location, periodicity and offset of the dedicated resource.
- DTX detection Discontinuous Transmission
- the eNB monitors for a UE tune-away event, in one exemplary embodiment, the eNB monitors for one or more missed PUCCH and/or SRS signals e.g., via DTX detection.
- the eNB monitors for multiple missed PUCCH and/or SRS (e.g., one or more DTX occurrences). Checking for multiple DTX occurrences can ensure that the UE is actually tuned away (as opposed to just a momentary loss of reception caused by e.g., a deep fade).
- the number of consecutive DTX may be selected on the basis of a tradeoff between the time to detect a true tune-away with no UL transmission, and the probability of a false alarm (based on the eNB PUCCH/SRS DTX). in some embodiments, the tradeoff may be dynamically adjusted to optimize according to e.g., the probability of success, the probability of misdeiection, overall detection time, etc.
- the eNB once the eNB has detected a DTX event, the eNB starts a timer function (e.g., DTX__Monitoring_Timer).
- a timer function e.g., DTX__Monitoring_Timer.
- the length of the has a maximal upper limit (e.g., such that Radio Link Failure (RLF) is not declared during the DTX monitoring timeout).
- RLF Radio Link Failure
- the UE can explicitly or implicitly communicate with the eNB to provide information on an upcoming tune-away period.
- the eNB is implicitly signaled via existing messaging schemes.
- the eNB may infer an upcoming tune-away period if, for instance, the UE transmits a number of consecutive CQI measurements with a pre-determined value on PUCCH/PUSCH resources (e.g., a null value or zero value CQI is currently reserved and indicates that no defined Modulation and Coding Scheme (MCS) can be supported given the spectral efficiency estimation).
- MCS Modulation and Coding Scheme
- the eNB may infer an upcoming tune-away period when the UE transmits a number of consecutive Buffer State Reports (BSR) with a null (or zero) value on the available UL grant.
- BSR Buffer State Reports
- the eNB may infer an upcoming tune-away period based on a number of consecutive Power Headroom (PHR) reports with a specified value (e.g., LTE has a lowest PHR value of -23dBm). It is appreciated that detection of a tune-away event may also be based on any combinations of the foregoing.
- PHR Power Headroom
- the eNB treats the UE as a tuned-away UE, and proceeds to step 504.
- the eNB considers the UE as momentarily interrupted (i.e., no corrective action is necessary).
- the eNB can compensate for the tuned-away UE by implementing one or more corrective actions.
- the eNB starts a timer function (e.g., T ne- away_Release_Timer).
- the Tune-away_Release Timer is selected in one exemplary implementation on the basis of a tradeoff between the time to detect a UE recovery, and the probability of a complete disconnection. In some embodiments, this tradeoff may be dynamically adjusted to optimize according to e.g., maximize the tune-away time, minimize reconnection time, minimize time for reconnection in the event of actual reception loss, etc. In one such variant, once the eNB has detected a tune-away event, the eNB starts another timer (e.g., Tune-away JRelease Timer).
- corrective actions include e.g. and without limitation: (i) suspending the scheduling of the UE, (ii) suspending the RRC_Inactivity_ Timer (if running), (iii) suspending the C-DRX_Inactivity_Timer (Connected DRX operation) (if running), (iv) suspending RRC procedures (e.g., handover operation, radio link monitoring, re- establishment, etc.) (if running), (v) suspending various software stack components (e.g., Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) layers) (if running), and/or (vi) releasing any (or a portion of) physical layer dedicated resources (e.g., time slots, subcarriers, resource blocks, etc.).
- MAC Medium Access Control
- RLC Radio Link Control
- PDCP Packet Data Convergence Protocol
- the eNB monitors for UE recovery. If the UE recovers, then the eNB proceeds to step 506. Alternately, if the Time- away elease Timer expires without activity, then the eNB proceeds to step 508 for eNB initiated recovery. Alternately, if the Tune-away '_Release_ Timer expires without activity, then the eNB may proceed directly to step 10 (and hence dropping the UE).
- the eNB monitors for Random Access Channel (RACH) operation, if the UE initiates a RACH attempt, then the eNB will service the UE reinstate the UE via the procedure of step 506; otherwise, the eNB proceeds to step 508.
- RACH Random Access Channel
- the eNB monitors for PUCCH and/or SRS accesses from the UE, alternately or additionally, the eNB may also monitor RACH procedures from the tuned- away UE. In one exemplary embodiment, if a minimum threshold of consecutive PUCCH and/or SRS are detected, then the eNB can consider the UE to be tuned back to the LTE network. For RACH type embodiments, if the UE initiates a RACH procedure which is successful, then the eNB will consider the UE to be tuned back to the LTE network.
- the eNB reinstates the UE's previous state. Reinstatement of operation may include, without limitation: (i) resuming scheduling of the UE, (ii) resuming the RRC inactivity JTim r (if suspended), (iii) resuming the C-DRX ' ⁇ Inactivity _ Timer (if suspended), (iv) resuming RRC procedures (e.g., handover operation, radio link monitoring, re-establishment, etc.) (if suspended), (v) resuming any halted software stack components (e.g., Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) layers), and/or (vi) setting up any physical layer dedicated resources (e.g., time slots, subcarriers, resource blocks, etc.).
- MAC Medium Access Control
- RLC Radio Link Control
- PDCP Packet Data Convergence Protocol
- the eNB may attempt to re-establish connection to the UE. If the UE responds to the eNB's re-establishment attempt, then the eNB can reinstate the UE at step 506. If the re-establishment attempt fails, then the eNB can drop the UE altogether (step 510). For example, in one exemplary embodiment, the eNB sends a Physical Downlink Control Channel (PDCCH) message, if the UE is "tuned in", then the UE will responsively initiate a RACH attempt and the eNB can proceed to step 506. If the eNB does not receive the RACH, then the eNB proceeds to step 510. It will also be appreciated that the eNB may be configured to apply various retry and/or timeout logic to the foregoing process; e.g., n number of retries and/or expiration of a timer before proceeding to step 510.
- PDCCH Physical Downlink Control Channel
- the eNB drops the UE (when the connection cannot be re-established). In one embodiment, this includes: releasing any dedicated radio resources, removing the UE from the eNB active UE database, transitioning the UE to RRCJDLE operation, and releasing any signaling and data radio bearers. Apparatus -
- FIG. 6 illustrates one exemplary embodiment of a network entity 600 configured in accordance with the present disclosure.
- the network entity may be a stand-alone entity, or be incorporated with other network entities (e.g., a base station, a base station controller, a radio access network controller, etc.).
- the network entity includes a Long Term Evolution (LTE) evolved Node B (eNB).
- LTE Long Term Evolution
- eNB evolved Node B
- the network entity 600 generally includes a wireless (e.g., cellular) interface 602 for interfacing with cellular devices, a processor 604, and a storage apparatus 606.
- the cellular interface is shown as a wireless cellular interface configured for communication with one or more mobile devices, although other configurations and functionalities may be substituted.
- the cellular interface may be a wireline communication to a base station, where the base station is in communication with the mobile device.
- the cellular interface 602 of the apparatus 600 shown in FIG. 6 at a high level includes one or more radio transceiver circuits configured to transmit and receive data via radio frequency transmissions ( F).
- a radio transceiver generally include a modem processor, and one or more antennas.
- the radio transceiver is configured in accordance with Long Term Evolution (LTE) radio access technologies. It is recognized that various other implementations of the present invention may be configured for other cellular and/or wireless standards. Common examples of such technologies include: GSM, GPRS, EDGE, WCDMA, CDMA2000, CDMA IX, CDMA 1X-EVDO, LTE-A, etc. and various combinations thereof.
- LTE Long Term Evolution
- the aforementioned cellular interface 602 adjusts detects and mitigates hybrid client device reception outage events.
- the processor 604 includes one or more processors (or multi-core processor(s)).
- the processor is coupled to processing memory and/or the storage apparatus.
- processing memory and/or the storage apparatus Common implementations of the processing subsystem are implemented within signal processors, general processors, network processors, field programmable gate arrays (FPGAs), digital signal processors (DSPs), and any combination of the foregoing.
- Typical implementations of memory and storage apparatus include Random Access Memory (RAM) and variations thereof (Dynamic RAM, Static RAM, Synchronous RAM, etc.), Flash memory, and Hard Disk Drives (HDD).
- RAM Random Access Memory
- HDD Hard Disk Drives
- one or more memory apparatus may further be configured in various redundancy schemes (e.g., Redundant Arrays of Inexpensive Drives (RAID)), etc.
- RAID Redundant Arrays of Inexpensive Drives
- the network entity 600 is further coupled to a wired network infrastructure via a network interface 612.
- the network interface is generally adapted for use with Ethernet networks, although other suitable network variations include Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), MoCA, etc.
- SONET Synchronous Optical Networking
- ATM Asynchronous Transfer Mode
- MoCA MoCA
- Various forms of physical interface are widely used within the related arts, including for example Ethernet cable (e.g., CAT5), coaxial, fiber optics, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261685891P | 2012-03-26 | 2012-03-26 | |
PCT/US2013/033939 WO2013148728A1 (en) | 2012-03-26 | 2013-03-26 | Network based detection and mitigation of hybrid client device reception outage events |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2832174A1 true EP2832174A1 (en) | 2015-02-04 |
Family
ID=49990404
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP13733094.0A Withdrawn EP2832174A1 (en) | 2012-03-26 | 2013-03-26 | Network based detection and mitigation of hybrid client device reception outage events |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP2832174A1 (en) |
TW (1) | TWI498017B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9854601B2 (en) * | 2015-12-04 | 2017-12-26 | Qualcomm Incorporated | Deliberating retransmissions to avoid new hybrid automatic repeat requests (HARQ) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120020229A1 (en) * | 2010-03-31 | 2012-01-26 | Qualcomm Incorporated | Method and apparatus to facilitate support for multi-radio coexistence |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8223708B2 (en) * | 2008-06-10 | 2012-07-17 | Innovative Sonic Limited | Method and apparatus for handling scheduling information report |
US20110158117A1 (en) * | 2009-06-29 | 2011-06-30 | Qualcomm Incorporated | Power headroom report for simultaneous transmissions on disparate radio access technologies |
CA2806529C (en) * | 2010-07-26 | 2014-12-09 | Seven Networks, Inc. | Prediction of activity session for mobile network use optimization and user experience enhancement |
US8886239B2 (en) * | 2010-09-21 | 2014-11-11 | Qualcomm Incorporated | Buffer status report control for creating transmission gaps |
-
2013
- 2013-03-26 EP EP13733094.0A patent/EP2832174A1/en not_active Withdrawn
- 2013-03-26 TW TW102110753A patent/TWI498017B/en not_active IP Right Cessation
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120020229A1 (en) * | 2010-03-31 | 2012-01-26 | Qualcomm Incorporated | Method and apparatus to facilitate support for multi-radio coexistence |
Non-Patent Citations (2)
Title |
---|
RALF KREHER AND KARSTEN GAENGER: "LTE Signaling,Troubleshooting and Optimization", 16 December 2010, WILEY, ISBN: 9780470977712 * |
See also references of WO2013148728A1 * |
Also Published As
Publication number | Publication date |
---|---|
TW201345283A (en) | 2013-11-01 |
TWI498017B (en) | 2015-08-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9426672B2 (en) | Apparatus and methods for network detection and mitigation of hybrid client device operation | |
US11627627B2 (en) | Beam failure recovery procedures | |
TWI497932B (en) | Method and apparatus for monitoring for a radio link failure | |
US9319952B2 (en) | Apparatus and methods for synchronization recovery in a hybrid network | |
US9781737B2 (en) | Apparatus and methods for network assisted hybrid network operation | |
EP3363248B1 (en) | Techniques for downlink scheduling and uplink scheduling in a shared radio frequency spectrum band | |
EP2468050B1 (en) | Discontinuous reception for multi-component carrier system | |
WO2017170163A1 (en) | Base station and wireless terminal | |
US20150173016A1 (en) | Enhanced node b, user equipment and methods for discontinuous reception in inter-enb carrier aggregation | |
US20160057800A1 (en) | Method and system for random access procedure and radio link failure in inter-enb carrier aggregation | |
TWI774906B (en) | Methods and devices for control of bandwidth part switching | |
EP2257113A1 (en) | Method and apparatus for handling carriers | |
CN106465402B (en) | Method and apparatus for uplink transmission adaptation | |
US10327196B2 (en) | Apparatus and methods for intelligent scheduling in hybrid networks based on client identity | |
US20240049204A1 (en) | Communication method and apparatus | |
CN114731680A (en) | Failure recovery for serving cell | |
TWI498017B (en) | Apparatus and methods for network detection and mitigation of hybrid client device operation | |
JP2023534359A (en) | Method and apparatus for sidelink communication during fast MCG link recovery procedures | |
CN116709439A (en) | Communication method and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20140930 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAX | Request for extension of the european patent (deleted) | ||
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20170810 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: APPLE INC. |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 76/19 20180101AFI20190626BHEP Ipc: H04W 48/02 20090101ALN20190626BHEP |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 48/02 20090101ALN20190628BHEP Ipc: H04W 76/19 20180101AFI20190628BHEP |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 76/19 20180101AFI20190712BHEP Ipc: H04W 48/02 20090101ALN20190712BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20190826 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20200108 |