Preventive data decompression failure technology

Abstract

Preventive data decompression failure techniques are described, such as using predictive decompression failure indications to avoid data decompression failures and / or configuring a communication device to perform data transmission recovery before a reorder window timer expires. Preventive data compression failure operations may, for example, conditionally initiate a compressor memory reset according to some aspects of the present disclosure, such as using one or more triggering events to predictively indicate a decompression failure. Additionally or alternatively, the preventive data compression failure operations may provide for configuring a communication device to perform data transmission recovery before a reorder window timer expires, such as configuring a priority to provide data transmission recovery before a reorder window timer expires. Other aspects and features are also claimed and described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Patent Application No. 17 / 332,981, filed on May 27, 2021, entitled “PRECLUSIVE DATA DECOMPRESSION FAILURE TECHNIQUES,” and U.S. Provisional Patent Application No. 63 / 032,802, filed on June 1, 2020, entitled “PRECLUSIVE DATA DECOMPRESSION FAILURE TECHNIQUES,” the entire disclosures of which are expressly incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to wireless communication implementing data compression. Certain embodiments of the techniques discussed below can implement and provide preventive data decompression failure techniques, such as using predictive decompression failure indications to avoid data decompression failures and / or configuring a communication device to perform data transmission recovery before a reordering window timer expires. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services, such as telephony, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple access networks capable of supporting multiple users by sharing the available network resources. Such networks (generally multiple access networks) support communication for multiple users by sharing the available network resources.

[0005] A wireless communication network may include several base stations or Node Bs that can support communications for several user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a base station to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a base station.

[0006] The base station may transmit data and control information to the UE on the downlink and / or may receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference caused by transmissions from neighboring base stations or from other wireless radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from uplink transmissions of other UEs communicating with neighboring base stations or from other wireless RF transmitters. Such interference may degrade the performance of both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to increase, the potential for interference and congested networks grows as more UEs access long-range wireless communication networks and more short-range wireless systems are deployed in communities. Research and development continues to advance wireless technologies, not only to meet the growing demand for mobile broadband access, but also to advance and enhance the user experience of mobile communications.

[0008] For example, in order to accommodate increased data rates and capacity requirements, efficient spectrum usage and utilization of different types of user applications is becoming increasingly important. Therefore, various compression techniques have been proposed to facilitate increased efficiency with respect to spectrum usage. For example, several compression methods have been introduced to provide data packet header compression, such as Internet Protocol (IP) Header Compression (IPHC) and Robust Header Compression (RoHC). In addition, several compression methods have been introduced to provide uplink data compression (UDC), such as Adaptive Packet Data Compression (APDC) and Lossless Compression Algorithm (Deflate). Summary of the invention

[0009] Some aspects of the present disclosure are summarized below to provide a basic understanding of the technology discussed. This summary is not a broad overview of all envisioned features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects disclosed herein in an overview form as a preface to a more detailed description presented later.

[0010] In one aspect of the present disclosure, a wireless communication method is provided. The method may include detecting, by logic of a first device providing a transmission in a wireless network, an occurrence of a trigger event among a plurality of trigger events that predictively indicate a decompression failure at a second device receiving the transmission in the wireless network. The method may also include signaling, by the first device to a second device, a compressor memory reset for the transmission in response to detecting the occurrence of the trigger event.

[0011] In another aspect of the present disclosure, a device configured for wireless communication is provided. The device may include a component for detecting, by a first device providing a transmission in a wireless network, an occurrence of a trigger event among a plurality of trigger events that predictively indicates a decompression failure at a second device in the wireless network receiving the transmission. The device may also include a component for signaling a compressor memory reset for the transmission to a second device by the first device in response to detecting the occurrence of the trigger event.

[0012] In another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon for wireless communication is provided. The program code may include code for detecting, by a first device providing a transmission in a wireless network, an occurrence of a trigger event that predictively indicates a decompression failure at a second device in the wireless network receiving the transmission, among a plurality of trigger events. The program code may also include code for signaling, by the first device to the second device, a compressor memory reset for the transmission in response to detecting the occurrence of the trigger event.

[0013] In another aspect of the present disclosure, a device configured for wireless communication is provided. The device includes at least one processor and a memory coupled to the processor. The processor can be configured to detect, by a first device providing a transmission in a wireless network, an occurrence of a trigger event in a plurality of trigger events that predictively indicates a decompression failure at a second device in the wireless network receiving the transmission. The processor can also be configured to signal, by the first device, to the second device a reset of a compressor memory for the transmission corresponding to the detection of the occurrence of the trigger event.

[0014] According to various aspects of the present disclosure, the aforementioned systems, methods, and apparatuses may be implemented in conjunction with one or more additional features (e.g., the following features, either individually or in combination). For example, the aforementioned systems, methods, and apparatuses may include a trigger event that predictively indicates a decompression failure due to expiration of a reordering window timer at a second device. The aforementioned systems, methods, and apparatuses may include that the trigger event corresponds to a reconfiguration between the use of a split radio bearer and the use of a non-split radio bearer. The aforementioned systems, methods, and apparatuses may include that the trigger event corresponds to a secondary cell group (SCG) radio link failure (RLF). The aforementioned systems, methods, and apparatuses may include that the trigger event corresponds to one or more radio link control (RLC) layer automatic repeat request (ARQ) metrics measured by the first device. The aforementioned systems, methods, and apparatuses may include that the one or more RLC layer ARQ metrics include a round trip time to a reordering window timer duration metric. The aforementioned systems, methods, and apparatuses may include that the trigger event corresponds to at least one of a medium access control (MAC) metric measured by the first device or a hybrid automatic repeat request (HARQ) metric measured by the first device. The systems, methods, and apparatus may include at least one of a MAC metric or a HARQ metric, the at least one of the MAC metric or the HARQ metric including a block error rate (BLER). The systems, methods, and apparatus may include that the trigger event corresponds to at least one of a scheduling delay during an uncompleted retransmission or a non-receipt of an RLC layer state by the first device. The systems, methods, and apparatus may include providing a dynamic compressor memory reset when any of the plurality of trigger events is satisfied, wherein determining the occurrence of the trigger event and signaling a compressor memory reset provide a dynamic compressor memory reset when the trigger event occurs. The systems, methods, and apparatus may include providing a static compressor memory reset, the static compressor memory reset being configured for a periodic compressor memory reset for the transmission. The systems, methods, and apparatus may include that the periodic compressor memory reset is based at least in part on the number of packets transmitted. The systems, methods, and apparatus may include establishing a priority for some of the data transmitted to provide transmission recovery before the reordering window timer expires at the second device. The systems, methods and apparatus may include establishing a priority for some data of the transmission, including prioritizing an RLC level retransmission of a bearer carrying compressed data of the transmission over transmission of one or more other bearers. The systems, methods and apparatus may include establishing a priority for some data, including prioritizing a MAC level grant associated with the data. The systems, methods and apparatus may include increasing a duration of a reordering window timer. The systems, methods and apparatus may include dynamically increasing a duration of a reordering window timer based on a block error rate (BLER) condition.

[0015] In one aspect of the present disclosure, a wireless communication method is provided. The method may include identifying one or more radio bearers for transmission from a first device in a wireless network to a second device in the wireless network. The method may also include configuring the first device to compress data to be transmitted via the one or more radio bearers. Configuring the first device may include establishing a priority for some data to provide transmission recovery before a reordering window timer expires at the second device.

[0016] In another aspect of the present disclosure, an apparatus configured for wireless communication is provided. The apparatus may include components for identifying one or more radio bearers for transmission from a first device in a wireless network to a second device in the wireless network. The apparatus may also include components for configuring the first device to compress data to be transmitted via the one or more radio bearers. Configuring the first device may include establishing a priority for some data to provide transmission recovery before a reordering window timer expires at the second device.

[0017] In another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon for wireless communication is provided. The program code may include code for identifying one or more radio bearers for transmission from a first device in a wireless network to a second device in the wireless network. The program code may also include code for configuring the first device to compress data to be transmitted via the one or more radio bearers. Configuring the first device may include establishing a priority for some data to provide transmission recovery before a reordering window timer expires at the second device.

[0018] In another aspect of the present disclosure, a device configured for wireless communication is provided. The device includes at least one processor and a memory coupled to the processor. The processor can be configured to identify one or more radio bearers for transmission from a first device in a wireless network to a second device in the wireless network. The processor can also be configured to configure the first device to compress data to be transmitted via the one or more radio bearers. Configuring the first device may include establishing a priority for some data to provide transmission recovery before a reordering window timer expires at the second device.

[0019] According to various aspects of the present disclosure, the aforementioned systems, methods, and apparatus may be implemented in conjunction with one or more additional features (e.g., the features described below, either individually or in combination). For example, the aforementioned systems, methods, and apparatus may include establishing priorities for some data, thereby providing compression gains configured for a specific application associated with the data. The aforementioned systems, methods, and apparatus may include establishing priorities for some data that are configured based on the tolerance for delay of a specific application associated with the data. The aforementioned systems, methods, and apparatus may include establishing priorities for some data including prioritizing RLC-level retransmissions of a bearer carrying the transmitted compressed data over transmissions of one or more other bearers. The aforementioned systems, methods, and apparatus may include establishing priorities for some data including prioritizing MAC-level authorizations associated with the data. The aforementioned systems, methods, and apparatus may include increasing the duration of a reordering window timer. The aforementioned systems, methods, and apparatus may include dynamically increasing the duration of a reordering window timer based on BLER conditions. The systems, methods, and apparatus may include determining, by a first device, the occurrence of a trigger event selected from a plurality of trigger events to predictively indicate a decompression failure at a second device, and signaling, by the first device to the second device, a compressor memory reset for the transmission based at least in part on determining the occurrence of the trigger event. The systems, methods, and apparatus may include that the trigger event predictively indicates a decompression failure due to expiration of a reordering window timer at the second device. The systems, methods, and apparatus may include that the trigger event corresponds to a reconfiguration between the use of a separated radio bearer and the use of a non-separated radio bearer. The systems, methods, and apparatus may include that the trigger event corresponds to an SCG RLF. The systems, methods, and apparatus may include that the trigger event corresponds to one or more RLC layer ARQ metrics measured by the first device. The systems, methods, and apparatus may include that the trigger event corresponds to at least one of a MAC metric measured by the first device or a HARQ metric measured by the first device. The systems, methods, and apparatus may include that the trigger event corresponds to at least one of a scheduling delay during an uncompleted retransmission or an RLC layer state not received by the first device. The above systems, methods and apparatus may include providing a dynamic compressor memory reset upon the occurrence of any triggering event among a plurality of triggering events being satisfied, wherein determining the occurrence of the triggering event and signaling the compressor memory reset provides a dynamic compressor memory reset upon the occurrence of the triggering event. The above systems, methods and apparatus may include providing a static compressor memory reset, the static compressor memory reset being configured for a periodic compressor memory reset for the transmission.

[0020] After reading the description of the following specific exemplary embodiments in conjunction with the accompanying drawings, other aspects, features and embodiments will become apparent to those of ordinary skill in the art. Although features can be discussed relative to certain embodiments and drawings below, all embodiments can include one or more of the advantageous features discussed herein. In other words, although one or more embodiments can be discussed as having certain advantageous features, one or more of these features can also be used according to various embodiments. In a similar manner, although exemplary embodiments can be discussed below as device, system or method embodiments, exemplary embodiments can be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral that distinguishes the similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second reference numeral.

[0022] Figure 1 is a block diagram illustrating details of a wireless communication system according to some embodiments of the present disclosure.

[0023] Figure 2 is a block diagram conceptually illustrating a design of a base station and a UE configured according to some embodiments of the present disclosure.

[0024] Figure 3 Operation of a Deflate compression technique as may be implemented in accordance with some embodiments of the present disclosure is illustrated.

[0025] Figure 4 An example decompression failure scenario is shown as may be experienced in accordance with some embodiments of the present disclosure.

[0026] Figure 5 A ladder diagram is shown illustrating a decompression failure as may be experienced according to some embodiments of the present disclosure.

[0027] Figure 6 An example flow is provided for providing preventative data compression failure operations for conditionally initiating a compressor memory reset in accordance with some aspects of the present disclosure.

[0028] Figure 7 An example process is provided for providing preventive data compression failure operations for configuring a communication device for data transmission recovery before a reordering window timer expires according to some aspects of the present disclosure.

[0029] Figure 8 is a block diagram conceptually illustrating a design of a UE configured for preventive data compression failure operation according to some embodiments of the present disclosure.

[0030] Fig. 9 is a block diagram conceptually illustrating a design of a base station configured for preventive data compression failure operation according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0031] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Instead, the detailed description includes specific details for providing a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some cases, well-known structures and components are shown in block diagram form for clarity.

[0032] The present disclosure generally relates to providing or participating in communications between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various embodiments, these techniques and apparatuses may be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5th generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks / systems / devices), and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0033] For example, a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0034] TDMA networks can implement radio technologies such as GSM, for example. 3GPP defines the standard for the GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is the radio component of the network of GSM / EDGE together with connecting base stations (e.g., Ater interface and Abis interface) and base station controllers (A interface, etc.). The radio access network represents the component of the GSM network, through which phone calls and packet data are routed from the public switched telephone network (PSTN) and the Internet to subscriber phones (also known as user terminals or user equipment (UE)), and from subscriber phones to the PSTN and the Internet. The network of a mobile phone operator may include one or more GERANs, which in the case of a UMTS / GSM network may be coupled to a universal terrestrial radio access network (UTRAN). The operator network may also include one or more LTE networks and / or one or more other networks. Various different network types may use different radio access technologies (RATs) and radio access networks (RANs).

[0035] OFDMA network can realize radio technologies such as Evolved UTRA (E-UTRA), IEEE802.11, IEEE 802.16, IEEE802.20, flash-OFDM, etc. UTRA, E-UTRA and Global System for Mobile Communications (GSM) are part of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is the official version of UMTS using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in the documents provided by the organization named "3rd Generation Partnership Project (3rd Generation Partnership Project)" (3GPP), and cdma2000 is described in the documents provided by the organization named "3rd Generation Partnership Project2 (3rd Generation Partnership Project 2)" (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunications association groups to define a globally applicable third generation (3G) mobile phone specification. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution of wireless technologies from LTE, 4G, 5G, NR and beyond, to shared access to wireless spectrum between networks using a host of new and different radio access technologies or radio air interfaces.

[0036] 5G networks envision multiple deployments, multiple spectrums, and multiple services and devices that can be implemented using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to provide coverage (1) for networks with ultra-high density (e.g., about 1 megabit (M) nodes / km) 2 ), ultra-low complexity (e.g., about 10s of bits / s), ultra-low energy (e.g., about 10+ years of battery life), and deep coverage to reach challenging locations; (2) mission-critical control including strong security to protect sensitive personal, financial, or confidential information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond (ms)), and users with extensive mobility or a lack of mobility; and (3) enhanced mobile broadband, including ultra-high capacity (e.g., about 10Tbps / km 2 ), ultra-high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep perception with advanced discovery and optimization.

[0037] 5G NR devices, networks, and systems can be implemented to use optimized OFDM-based waveform features. These features may include: scalable digital schemes and transmission time intervals (TTIs); a general flexible architecture to efficiently multiplex services, and features with dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of the digital scheme in 5G NR and the extension of subcarrier spacing can efficiently address the operation of multiple services across multiple spectrums and multiple deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, the subcarrier spacing can appear at 15kHz, such as on bandwidths of 1, 5, 10, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing can appear at 30kHz on 80 / 100MHz bandwidths. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting with mmWave components at 28 GHz TDD, subcarrier spacing may occur at 120 kHz over a 500 MHz bandwidth.

[0038] 5G NR's scalable parameter set facilitates scalable TTI for various latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to start on symbol boundaries. 5G NR also envisions a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgments in the same subframe. The self-contained aggregate subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink / downlink, which can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic demands.

[0039] For clarity, certain aspects of the apparatus and techniques may be described below with reference to exemplary LTE implementations or in an LTE-centric manner, and LTE terminology may be used in parts of the following description as illustrative examples; however, the description is not intended to be limited to LTE applications. In fact, the present disclosure relates to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces (such as those of 5G NR).

[0040] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate with any combination of licensed or unlicensed spectrum depending on load and availability. Therefore, it will be apparent to those skilled in the art that the systems, devices, and methods described herein can be applied to other communication systems and applications besides the specific examples provided.

[0041] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional implementations and use cases can be implemented in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses can be implemented via integrated chip embodiments and / or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, AI-enabled devices, etc.). Although some examples may or may not specifically involve use cases or applications, various applicability of the above innovations may occur. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or OEM devices or systems incorporating one or more of the described aspects. In some practical settings, the device incorporating the described aspects and features may also have to include additional components and features for implementing and practicing the claimed and described embodiments. It is intended that the innovations described herein can be practiced in a variety of embodiments, including both large devices / small devices of varying sizes, shapes, and configurations, chip-level components, multi-component systems (e.g., RF chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0042] Figure 1 1 shows a wireless network 100 for communication according to some embodiments. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 The components in may have relevant counterparts in other network arrangements, including, for example, cellular network arrangements and non-cellular network arrangements (eg, device-to-device or peer-to-peer or ad hoc network arrangements, etc.).

[0043] Figure 1The wireless network 100 shown includes several base stations 105 and other network entities. A base station may be a station that communicates with a UE, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to this specific geographic coverage area of ​​a base station and / or a base station subsystem serving the coverage area, depending on the context in which the term is used. In an embodiment of the wireless network 100 herein, the base station 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks), and may use one or more of the same frequencies (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof) to provide wireless communications as adjacent cells. In some examples, a separate base station 105 or UE 115 may be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0044] A base station may provide communication coverage for a macro cell or a small cell (e.g., a pico cell or a femto cell) and / or other types of cells. A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with a service subscription to a network provider. Small cells, such as pico cells, typically cover a relatively small geographic area and may allow unrestricted access to UEs with a service subscription to a network provider. Small cells, such as femto cells, also typically cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may provide restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations with one of 3D, full dimensional (FD) or massive MIMO enabled. Base stations 105a-105c utilize their higher dimensional MIMO capabilities to utilize 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0045] The wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some scenarios, the network may be enabled or configured to handle dynamic switching between synchronous or asynchronous operation.

[0046] UE 115 is dispersed throughout the wireless network 100, and each UE may be fixed or mobile. It should be understood that although mobile devices are generally referred to as user equipment (UE) in the standards and specifications promulgated by the Third Generation Partnership Project (3GPP), those skilled in the art may also refer to such devices as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, mobile phones, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle-mounted component devices / modules, or some other suitable terminology. In this document, a "mobile" device or UE does not necessarily have the ability to move and may be fixed. Some non-limiting examples of mobile devices (e.g., embodiments that may include one or more of UE 115) include mobile phones, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebook computers, netbooks, smartbooks, tablet computers, and personal digital assistants (PDAs). The mobile device may additionally be an "Internet of Things" (IoT) or "Internet of Everything" (IoE) device, such as a car or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a logistics controller, a drone, a multi-rotor aircraft, a quad-rotor aircraft, a smart energy or security device, a solar panel or solar array, municipal lighting, water or other infrastructure; industrial automation and enterprise equipment; consumer devices and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammal implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home devices or smart home devices, such as home audio, video and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, the UE may be a device including a universal integrated circuit card (UICC). In another aspect, the UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UEs 115a-115d of the illustrated embodiment are examples of mobile smartphone-type devices accessing the wireless network 100. A UE may also be a machine specifically configured for communicating via connectivity, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), and the like. Figure 1 UEs 115e - 115k shown in FIG. 1 are examples of various machines configured for communications accessing wireless network 100 .

[0047] A mobile device such as UE 115 may be able to communicate with any type of base station, whether macro, pico, femto, relay, or other. Figure 1 In the present invention, a lightning beam (e.g., a communication link) indicates a wireless transmission between a UE and a serving base station (which is a base station designated to serve the UE on a downlink and / or uplink), or an expected transmission between base stations, and a backhaul transmission between base stations. In some scenarios, a UE may operate as a base station or other network node. Backhaul communications between base stations of the wireless network 100 may occur using wired and / or wireless communication links.

[0048] In operation at the wireless network 100, base stations 105a-105c use 3D beamforming and cooperative spatial technologies such as coordinated multi-point (CoMP) or multi-connectivity to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cell base station 105f. Macro base station 105d also transmits multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0049] The wireless network 100 of an embodiment supports mission critical communications with ultra-reliable and redundant links for mission critical devices such as UE 115e (which is a drone). The redundant communication links with UE 115e include links from macro base stations 105d and 105e and small cell base station 105. Other machine type devices, such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device), can communicate directly with base stations (such as small cell base station 105f and macro base station 105e) through the wireless network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which then reports it to the network through small cell base station 105f. The wireless network 100 may also provide additional network efficiency through dynamic, low-latency TDD / FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i - 115k communicating with a macro base station 105e .

[0050] Figure 2 1 shows a block diagram of a design of a base station 105 and a UE 115, which may be Figure 1 For the restricted association scenario (described above), the base station 105 can be Figure 1 105f in the small cell base station 105f, and UE 115 may be UE 115c or 115D operating in the service area of ​​base station 105f. To access small cell base station 105f, UE 115c or 115D will be included in the list of accessible UEs for small cell base station 105f. Base station 105 may also be some other type of base station. Figure 2 As shown, the base station 105 may be equipped with antennas 234a through 234t, and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communications.

[0051] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller / processor 240. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The transmit processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and a cell-specific reference signal. The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols (if applicable), and may provide an output symbol stream to modulators (MODs) 232a to 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0052] At the UE 115, antennas 252a to 252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the demodulators 254a to 254r, perform MIMO detection on the received symbols when applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to a data sink 260, and provide decoded control information to a controller / processor 280.

[0053] On the uplink, at the UE 115, a transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signals from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. Processor 238 may provide decoded data to a data sink 239 and decoded control information to controller / processor 240 .

[0054] The controllers / processors 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller / processor 240 or other processors and modules at the base station 105 or the controller / processor 280 or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution of various processes for the techniques described herein. Figure 6 and Figure 7 , and / or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0055] Wireless devices (e.g., base stations 105, UEs 115, etc.) of the wireless network 100 may utilize various compression techniques, for example, to promote efficient spectrum usage. As an example, compressing data prior to transmission may be beneficial, otherwise the air interface may become congested. For example, in the case of implementing a downlink-heavy TDD configuration, a smaller portion of the resources allocated for use by the uplink air interface may become congested. UEs 115 may utilize uplink data compression (UDC) techniques such as adaptive packet data compression (APDC) and Deflate to alleviate or reduce congestion.

[0056] Both Deflate and APDC use the LZ77 compression algorithm, which provides lossless data compression. Deflate further uses Huffman coding, which provides variable-length coding, to further compress some parameters and outputs of the LZ77 compression algorithm.

[0057] Figure 3 1 shows operations according to the Deflate compression technique, such as may be implemented by a wireless device (e.g., base station 105, UE 115, etc.) of wireless network 100. Figure 3 As shown, uncompressed data input 310 (e.g., application and / or control data to be sent by UE 115 in the uplink) is compressed by Deflate compression logic 320 (e.g., which may be executed by controller / processor 280 and / or transmit processor 264 of UE 115) to provide compressed data output 330 for transmission.

[0058] In the example shown, the uncompressed data input 310 is divided into a series of consecutive blocks. The block size may be arbitrary, but a maximum size of an incompressible block may be enforced (eg, a maximum incompressible block size of 65,535 bytes).

[0059] Each block of uncompressed data input 310 is passed through the LZ77 compression algorithm 321 of the Deflate compression logic 320 to provide lossless compression of the data. The LZ77 compression algorithm 321 can achieve compression by replacing repeated occurrences of data with a reference to a single copy of the data that existed earlier in the uncompressed data stream. A match can be encoded by a pair of numbers called a length-distance pair (distance is also called an offset). The LZ77 compression algorithm can use this reference to a repeated string in the previous block (e.g., a reference back to 32K of previous input bytes).

[0060] In addition to the LZ77 compression algorithm 321, the data is passed through Huffman encoding 322 to further compress the output of the LZ77 compression algorithm 321 using variable length coding. The output from the Huffman encoding 322 can be viewed as a table of variable length codes used to encode the source symbols, where the variable length codes are derived from the estimated probability or frequency of occurrence (weight) of each possible value of the source symbols. In the operation of the Huffman encoding 322 of the Deflate compression logic 320, a Huffman code tree is generated that describes a representation of the compressed data, where the Huffman code tree for each block is independent of other blocks.

[0061] The Deflate compression logic 320 compresses the uncompressed data input 310 block to provide a compressed data output comprising two parts. Figure 3As shown, compressed data output 330 includes Huffman code tree 331 and compressed data 332. Compressed data 332 may include literal bytes and pointers to repeated character strings. For example, literal bytes may include data strings that cannot be copied based on previous data (e.g., data that is not repeated in the data that existed in the previous 32KB data). As described above, pointers to repeated character strings may include length-distance pairs (e.g., a maximum length of 258 bytes and a maximum distance of 32KB). Huffman code tree 331 may provide encoding for each of the above-mentioned literal bytes and pointers. For example, a Huffman code tree may be provided for literal bytes and lengths, and another Huffman code tree may be provided for distances. Compressed data output 330 may therefore include a Huffman code tree (e.g., a compact form) and compressed data.

[0062] Decompression of data compressed by operation of the Deflate compression logic 320 follows the Huffman code tree of the compressed data output 330 to recover the literal bytes, length, and distance data. In the event of data duplication, the distance data may reference data from a previous block of data (e.g., backtracking to a maximum distance amount, such as a maximum distance of 32KB). However, even when data within a particular block of the compressed data output 330 is extracted, the data may not be successfully decompressed due to a failure to reference data from a previous block of the compressed data output 330. For example, a compressed data output 330 block including an instance of a data string and one or more references to a single copy of the data may exceed a decoding window implemented by a wireless device (e.g., a base station 105, a UE 115, etc.) receiving the compressed data transmission, such that a reference to the previous block fails. That is, even though a particular block has been received and the data carried therein has been extracted due to a compression technique that relies on a previous, currently unavailable compressed data block, decompression failure may still result.

[0063] The radio link control (RLC) acknowledgement mode (AM) implemented by wireless devices of some NR networks provides an example of the aforementioned decompression failure scenario. NR RLC AM recovers lost data packets through the RLC ARQ mechanism, where the data packets are delivered out of order to the NR Packet Data Convergence Protocol (PDCP). When data arrives through the media access control (MAC) and RLC entities, the NR RLC AM operation facilitates the NR PDCP split bearer (e.g., primary cell group (MSG) / secondary cell group (SCG) bearer) situation. NR PDCP utilizes a reordering window and timer mechanism to accommodate out-of-order data packets. For example, the reordering window establishes a timeframe within which data packets are received for reordering and provided to the upper layer. When the timer (referred to as the Treordering timer in this article) expires, the data packets received in the PDCP buffer are provided to the upper layer of the wireless device.

[0064] The expiration of the Treordering timer moves the reordering window to the next window time range (e.g., based on the state variable) and passes the packet to the upper layer. After the reordering window moves, NR PDCP discards the subsequently received packets that are beyond the reordering window time range as "out-of-window". Therefore, even if NR RLC AM can recover packets lost in transmission through the ARQ mechanism, these packets can still be received outside the updated reordering window time range and discarded as out-of-window. Therefore, the packets passed to the upper layer can be passed with some holes.

[0065] When using Deflate-based data compression for NR PDCP, the current PDCP packet may not be successfully decompressed if the previous packet is lost. This decompression failure scenario occurs in Figure 4 In the description. Figure 4 In the example of FIG. 4 , a wireless device (eg, base station 105, UE 115, etc.) implements a reordering window 400 that spans a time range 401. Compressed data blocks 410-413 may each include an instance of a Huffman code tree 331 and a Huffman code tree 332 as described above with reference to FIG. Figure 3 3. The compressed data 332 corresponding to the corresponding data block of the uncompressed data input 310 described above is shown. In the illustrated example, the compressed data block 410 (sequence number (SN) X) is outside the window with respect to the reordering window 400. However, the compressed data block 411 (SN X+1) is received within the reordering window 400. If the compressed data block 411 (SN X+1) includes compressed data whose distance of the length-distance pair points to data in the compressed data block 410 (SN X), the compressed data block 411 (SN X+1) cannot be correctly decompressed. Therefore, a decompression failure may be experienced for the compressed data block 411 (SN X+1).

[0066] The aforementioned decompression failure may extend beyond the inability to correctly decompress compressed data block 411 (SN X+1). For example, although compressed data blocks 412 (SN+2) and 413 (SN+3) may be correctly received, these compressed data blocks may include instances of data corresponding to data of compressed data block 411 (SN X+1), the distance of the length-distance pair of which is the pointing data in compressed data block 410 (SN X). Therefore, the decompression failure may be cascaded with respect to several compressed data blocks.

[0067] Various techniques may be utilized to detect compressor-decompressor desynchronization, such as may be caused by a decompression failure. For example, a checksum-based technique for identifying compressor-decompressor desynchronization may be implemented by a wireless device utilizing compression for data communications. Compressor-decompressor desynchronization may be identified based on a checksum calculated on a compressor memory such that a checksum received in a current data packet is not satisfied. As used herein, compressor memory refers to memory used by a compressor when compressing data or by a decompressor when decompressing data.

[0068] Signaling may be provided between wireless devices utilizing compression for data communication to indicate a reset of a compression buffer, such as when a compressor-decompressor desynchronization is detected. For example, a UDC header may include a reset bit to notify a decompressor at a wireless device receiving compressed data that a compression buffer of the wireless device sending the compressed data has been reset. A validation (e.g., a checksum) of the compression buffer may also be included in the UDC header, such as to resolve a mismatch (if any) between the compression buffer and the decompression buffer. In one example, a UDC Checksum Error Notification PDCP Control PDU may indicate that the compression buffer and the decompression buffer are out of sync, wherein the wireless device receiving the notification triggers a UDC buffer reset procedure to resynchronize the compression buffer.

[0069] As an example of a checksum for compression buffer validation, the checksum field of NR RLC, PDCP includes a 4-bit field containing validation bits for compression buffer contents, wherein the checksum is calculated over the contents of the current compression buffer before the current data packet is placed in the buffer. The checksum is derived from the values ​​of the first 4 bytes and the last 4 bytes in the entire compression buffer. Specifically, each byte is divided into two 4-bit numbers, 16 4-bit numbers are added together to obtain the sum, and the checksum is the complement of the rightmost 4 bits (i.e., 4LSBs) of the sum. The checksum error notification field (FE field) of NR RLC, PDCP is used to provide an indication of whether a checksum error is detected. Specifically, a FE field value of "0" indicates that no checksum error is detected, while a FE field value of "1" indicates that a checksum error is detected and the wireless device will reset the compression buffer. The compression buffer reset field (FR field) of NR RLC, PDCP is used (e.g., the FR field bit value is "1") to control the compressor memory reset, for example, in response to receiving an indication that the compression buffer validation failed (e.g., the FE field bit value is "1").

[0070] Figure 5 A ladder diagram illustrating NR RLC, PDCP operations providing communication of compressed data in which decompression failures are experienced is shown. Specifically, Figure 5The ladder diagram 500 of FIG. 1 illustrates the communication timing between wireless devices transmitting compressed data via one or more communication links of the wireless network 100. For example, the UDC can be implemented for an uplink established between the UE 115 and a network node such as the base station 105. In the illustrated example, it is assumed that the RLC and PDCP SNs are the same to simplify the example. The Treordering timer (reordering window timer) of the example has a duration of 100 milliseconds (ms).

[0071] exist Figure 5 In the example of , at time T0-T10, UE 115 sends compressed data blocks SN 0-50 to base station 105 (transmission 501). At time T10, base station 105 receives compressed data blocks SN 21-50, and requests retransmission of compressed data blocks SN 0-20 through RLC ARQ (transmission 502), and starts a PDCP reordering timer (Treordering timer). At time T60-T70, UE 115 sends compressed data blocks SN 51-100 to base station 105 (transmission 503). Thereafter, at time T110-T120, UE 115 receives a retransmission request from base station 105 to retransmit compressed data blocks SN 0-20, and the UE resends compressed data blocks SN0-20 to base station 105 (transmission 504). Figure 5 In the example of FIG. 1 , at time T10 - T110 , base station 105 and UE 115 perform RLC ARQ but without success.

[0072] At time T110, the PDCP reordering timer (Treordering timer) implemented by the base station 105 expires. Therefore, compressed data blocks SN 21-100 (with the lost compressed data blocks SN 0-20 as out of window) are given for decompression. At time T111, the base station 105 experiences a decompression failure because data from one or more compressed data blocks SN 0-20 are lost in the decompressor memory of the base station 105 for backward lookup. At time T112, the base station 105 sends a request to reset the compressor memory to the UE 115 by sending a PDCP control PDU containing a compressor memory reset request (e.g., FE field value is "1") (transmission 505).

[0073] UE 115 sends compressed data blocks SN 101-150 to base station 105 at time T160-T170 (transmission 506), and then receives a request to reset the compressor memory and reset the compressor memory context at time T175. Base station 105 receives compressed data blocks SN 101-150, which are given decompression when the PDCP reordering timer (Treordering timer) expires later. Although compressed data blocks SN 101-150 are delivered in sequence, since UE 115 transmits before receiving the request to reset its compressor memory, the compressor checksum fails and base station 105 experiences a decompression failure. At time T205, base station 105 sends another request to reset the compressor memory to UE 115 by sending a PDCP control PDU containing a compressor memory reset request (e.g., FE field value is "1") (transmission 507).

[0074] UE 115 sends compressed data blocks SN 151-200 to base station 105 at time T210-T220 together with a compressor memory reset (e.g., a FR field bit value of "1") (transmission 508), and later receives a re-request to reset the compressor memory and reset the compressor memory context at time T235. Base station 105 receives compressed data blocks SN 151-200, which are given decompression when the PDCP reordering timer (Treordering timer) expires later. Compressed data blocks SN 151-200 are delivered in order, and since the compressor memory of UE 115 has been reset before transmitting compressed data blocks SN 151-200, the compressor checksum passes. However, UE 115 thereafter receives a re-request to reset the compressor memory and reset the compressor memory context. UE 115 thereafter sends compressed data blocks SN 201-250 to base station 105 together with a compressor memory reset (e.g., a FR field bit value of "1") (transmission 509). However, this compressor memory reset is unnecessary and may result in inefficient data compression operations.

[0075] exist Figure 5 In the example of , even if many compressed data blocks are correctly decoded, a cycle of compressor memory reset will be performed. Specifically, even if base station 105 successfully decompresses the compressed data blocks it has received, UE 115 does not necessarily reset the compressor memory.

[0076] Embodiments of the present disclosure are configured to provide preventive data decompression failure techniques. Preventive data decompression failure techniques implemented according to the concepts described herein can be used, for example, to avoid decompression failures and / or unnecessary compressor memory resets. According to some aspects of the present disclosure, data decompression failures and associated requests for compressor memory resets can be avoided using predictive decompression failure indications and / or configuring a communication device to perform data transmission recovery before a reorder window timer expires.

[0077] In operation of a preventive data decompression failure technique using one or more predictive decompression failure indications according to some aspects of the present disclosure, a wireless device (e.g., UE 115, base station 105, etc.) conditionally initiates a compressor memory reset, e.g., corresponding to or otherwise based at least in part on one or more triggering events. For example, the UE may conditionally initiate a compressor memory reset for a UDC based on one or more triggering events to limit the impact of packet loss at the UE PDCP.

[0078] The trigger event used according to the embodiment of the one or more trigger events predictively indicates a decompression failure. The trigger event predictively indicating a decompression failure according to an embodiment of the present disclosure may, for example, include one or more events selected, identified, or otherwise specified as providing a priori indication of a decompression failure at another communication device, such as in the absence of corresponding signaling provided by other communication devices to control a compressor memory reset. For example, a trigger event may indirectly indicate the possibility of a reordering window timer failure at the PDCP. The trigger event may predictively indicate a decompression failure due to expiration of a reordering window timer at a wireless device receiving compressed data (e.g., a compressor memory reset triggered by an event indicating expiration of a Treordering timer, where a compressed data block is outside the window).

[0079] In an example, the trigger event may correspond to a reconfiguration between use of a split radio bearer and use of a non-split radio bearer. For example, the radio bearer reconfiguration trigger event of some embodiments may be used to trigger a compressor memory reset for each reconfiguration from a split radio bearer to a non-split radio bearer and from a non-split radio bearer to a split radio bearer.

[0080] In another example, the triggering event may correspond to a SCG Radio Link Failure (RLF).The SCG RLF triggering event of some embodiments may be used to trigger a compressor memory reset for each SCG RLF.

[0081] As another example, the triggering event may correspond to one or more RLC layer ARQ metrics measured by a wireless device (e.g., UE 115, base station 105, etc.) transmitting compressed data. To illustrate an RLC layer ARQ metric that may be used as a triggering event, assume that the reordering window timer (Treordering) duration is 100 ms, the RLC round trip time (RTT) is approximately 15 ms, and the state is prohibited is 40 ms. A wireless device receiving compressed data requesting the same NAK for the second time may experience the reordering window timer expiration before receiving the retransmitted compressed data block (15+40+15+40+15>100). Therefore, the wireless device transmitting compressed data may calculate an RLC ARQ metric, such as an RTT determined based on NAK, state delay, etc. versus the reordering window timer (Treordering timer) duration metric to be used as one or more RLC ARQ triggering events. The RLC ARQ metric may therefore be used to trigger a compressor memory reset, such as when the RLC ARQ metric indicates that the reordering window timer expires before receiving the retransmitted compressed data block.

[0082] In yet another example, the triggering event may correspond to a MAC metric and / or a hybrid automatic repeat request (HARQ) metric measured by a wireless device (e.g., UE 115, base station 105, etc.) transmitting compressed data. For illustration, a MAC metric such as an uplink and / or downlink metric and / or a HARQ metric such as a decoding failure may indicate a relatively high block error rate (BLER) or a BLER exceeding a threshold (e.g., T BLER ). For example, even a slight BLER at 8 component carriers can often result in very large packet losses, and often the peak rates have tight timing control. Therefore MAC metrics and / or HARQ metrics can be used to trigger a compressor memory reset, e.g. when the MAC / HARQ metrics indicate a possible decompression failure.

[0083] As another example, the triggering event may correspond to a scheduling delay during an incomplete retransmission and / or an RLC layer state that is not received by the wireless device transmitting the compressed data. For example, a threshold (e.g., T ) of scheduling delay during an incomplete compressed data retransmission in the uplink and / or an RLC layer state that is not received in the downlink may be set to a value greater than 100. SchedDely ) amount can provide one or more triggering events. To illustrate, for a certain threshold amount of time (e.g., T SchedDely=70ms, where Treordering=100ms, RTT=15ms, and StatusProh=40ms) the absence of an RLC STATUS PDU in the downlink may indicate that the NAK was likely not recovered in time. Therefore, the scheduling delay may be used to trigger a compressor memory reset during an incomplete retransmission and / or unreceived RLC layer status.

[0084] Trigger events such as the example trigger events described above can be utilized in accordance with preventive data decompression failure techniques to provide dynamic compressor memory resets (e.g., causing compressor memory to reset when any of the above trigger events are met). An embodiment may use one or more of the described trigger events to initiate relatively frequent compressor memory resets, resulting in a reduction in overall compression gain. For example, multiple of the aforementioned trigger events may be used to initiate preventive data decompression failure operations that initiate relatively frequent compressor memory resets. Additionally or alternatively, static compressor memory resets may be implemented in accordance with aspects of the present disclosure. For example, in addition to conditional compressor memory resets implemented using one or more trigger events, static compressor memory resets may be initiated corresponding to or based at least in part on various defined actions.

[0085] In an example, a static compressor memory reset may be provided periodically. For example, the compressor memory may be reset every Nth PDCP packet. According to some aspects, every Nth PDCP packet may be generated with a compression reset (e.g., notified via the FR field). For example, N may depend on a configuration value, a current throughput rate, a MAC transport block (TB) size, a PDCP / RLC configuration (timers, counters, etc.), and / or the like. As an example, N may be approximately 100 packets, where N may be lower when the PDCP reordering timer is low.

[0086] Figure 6 Example preventive data compression failure operations for conditionally initiating a compressor memory reset according to some aspects of the present disclosure are described. Specifically, Figure 6 Flow 600 illustrates the use of triggering events to predictively indicate decompression failures according to some aspects of the present disclosure. Figure 6 The functions of the blocks shown in the flowchart 600 may be implemented by a wireless device (e.g., base station 105, UE 115, etc.) of the wireless network 100. According to some embodiments, the functions of the flowchart 600 may be performed in whole or in part by logic of one or more processors (e.g., controller / processor 240 of base station 105, controller / processor 280 of UE 115, etc.) of a wireless device that transmits compressed data via one or more communication links of the wireless network 100.

[0087] In block 601 of the example process 600, an occurrence of a trigger event among a plurality of trigger events may be detected. For example, the trigger event may predictively indicate a decompression failure at a second device receiving a transmission from a first device in a wireless network. According to some aspects of the present disclosure, logic of a first device transmitting in a wireless network may detect or otherwise determine the occurrence of the trigger event. In an example of implementing UDC, logic of a UE transmitting to a base station in an uplink may analyze one or more aspects of a communication link (e.g., radio bearer configuration / reconfiguration, SCG RLF metrics, RLC ARQ metrics, MAC metrics, HARQ metrics, RTT metrics, RLC state metrics, etc.) and detect the occurrence of a trigger event. The trigger event may, for example, include a radio bearer reconfiguration trigger event, an SCG RLF trigger event, an RLC ARQ trigger event, a MAC trigger event, a HARQ trigger event, an RLC state trigger event, the like, and combinations thereof.

[0088] At block 602, a compressor reset for the transmission may be signaled corresponding to detecting the occurrence of a triggering event (e.g., based at least in part on detecting or otherwise determining the occurrence of a triggering event). The compressor reset may be signaled, for example, by a first device transmitting to a second device in a wireless network. According to some aspects of the present disclosure, the first device may signal a compressor memory reset using one or more reset bits to indicate a compressor memory reset. In an example of implementing UDC, a UE transmitting to a base station in an uplink may transmit (e.g., using a transmit processor 264, a TX MIMO processor 266, and / or MODs 254a-254r and antennas 252a-252r, e.g., under the control of a controller / processor 280) a UDC header containing a reset bit to notify a decompressor at a base station receiving compressed data that the UE's compression buffer has been reset, thereby initiating a corresponding compressor memory reset at the base station. Validation (e.g., a checksum) of the compression buffer may also be included in the UDC header, which may be used, for example, to resolve a mismatch (if any) between the compression buffer and the decompression buffer.

[0089] According to some aspects of the present disclosure, a preventative data decompression failure technique configured to avoid decompression failures and / or unnecessary compressor memory resets may include configuring a communication device to perform transmission recovery before a reordering window timer expires. For example, in addition to or as an alternative to using a predictive decompression failure indication, an embodiment may configure one or more wireless devices transmitting compressed data to perform transmission recovery before a reordering window timer expires.

[0090] In an example, a wireless device (e.g., base station 105, UE 115, etc.) receiving compressed data can implement an increased reordering window timer (e.g., Treordering timer) duration (e.g., implement a timer duration that is greater than an initial or natively configured timer duration). For example, the reordering window timer duration can be reconfigured by the receiver to provide an increased duration, thereby allowing or facilitating more time to recover data through retransmission at the RLC / MAC level. For example, the reordering window timing duration can be dynamically configured (increased) at the receiver corresponding to a MAC / RLC BLER condition (e.g., based at least in part on the MAC / RLC BLER condition). According to some aspects of the present disclosure, the reordering window timer duration can be configured based on a value that is configured to be large enough to accommodate HARQ retransmission delays and RLC retransmission delays. In some examples, the reordering window timer duration can be increased by a multiplier value (e.g., a preset value internal to the wireless device, a value that can be configured by the RAN, a value indicated by a MAC CE, etc.). For example, the value of such a multiplier may be selected based on various aspects of the wireless device(s), the application(s) providing and / or consuming the data, the communication, data compression, and / or the like, such as the tolerance of a particular application to delays and / or data transmission errors, the RTT of the communication link, etc. According to some aspects of the present disclosure, the reordering window timer duration may be increased to a default large value, such as infinity.

[0091] In another example, a wireless device (e.g., base station 105, UE 115, etc.) transmitting compressed data may be configured to prioritize to provide transmission recovery, etc., before the reordering window timer expires at the wireless device (e.g., base station 105, UE 115) receiving the compressed data. For example, bearer channel / logical channel (LC) specific data may be prioritized to ensure fast recovery before the PDCP reordering window timer expires. According to some aspects of the present disclosure, RLC-level retransmissions of a bearer carrying compressed data may be prioritized over transmissions of one or more other bearers. For example, RLC-level retransmissions may be prioritized over conventional configurations, such as to facilitate fast retransmissions for compressed bearers only. Additionally or alternatively, MAC-level authorizations associated with data may be prioritized. For example, more opportunities with logical channel priority (LCP), priority bit rate (PBR), bucket size duration (BSD), and logical channel bucket content value (Bj) may be used to prioritize MAC-level authorizations for retransmissions.

[0092] The foregoing techniques for configuring a communication device for data transmission resumption prior to expiration of a reordering window timer may be implemented for specific situations, such as based on (one or more) wireless devices, (one or more) applications providing and / or consuming data, communications, data compression, and / or the like. For example, one or more such configuration techniques may be implemented for compressed data transmission for applications that benefit from higher compression gains and / or have relaxed delay requirements. According to some aspects of the present disclosure, configuration of a communication device for transmission resumption prior to expiration of a reordering window timer may be performed, for example, for compression configuration for a particular radio bearer.

[0093] Figure 7 Example preventive data compression failure operations for configuring a communication device for data transmission recovery before a reordering window timer expires according to some aspects of the present disclosure are described. Specifically, Figure 7 Flow 700 illustrates configuration of a wireless device for prioritization to provide data transmission resumption before expiration of a reordering window timer according to some aspects of the present disclosure. Figure 7 The functions of the blocks shown in the flowchart 700 may be implemented by a wireless device (e.g., base station 105, UE 115, etc.) of the wireless network 100. According to some embodiments, the functions of the flowchart 700 may be performed in whole or in part by logic of one or more processors (e.g., controller / processor 240 of base station 105, controller / processor 280 of UE 115, etc.) of a wireless device that transmits compressed data via one or more communication links of the wireless network 100.

[0094] At block 701 of example process 700, one or more radio bearers for transmission from a first device in a wireless network to a second device in the wireless network may be identified. For example, one or more radio bearers (e.g., separate radio bearers for MSG and SCG bearers, non-separate radio bearers for MSG or SCG bearers, etc.) may be identified or otherwise determined for use with respect to an NR PDCP communication link in which data compression is to be implemented. For example, base station 105 may select one or more radio bearers for use with respect to a communication link implemented for UE 115, wherein the selected radio bearer(s) may be indicated to the UE via signaling (e.g., RRC, DCI, etc.).

[0095] In block 702, a first device may be configured to compress data to be transmitted via one or more radio bearers. According to some aspects of the present disclosure, a wireless device (e.g., base station 105, UE 115, etc.) to transmit compressed data is configured to compress the data. Configuring the first device may, for example, include establishing a priority for some data to provide data transmission recovery before the reordering window timer expires at a second device. For example, when configuring a wireless device (e.g., UE 115) to transmit compressed data (e.g., UDC), the wireless device may be configured to prioritize to provide transmission recovery before the reordering window timer expires at another wireless device (e.g., base station 105) receiving the compressed data. In some examples, the wireless device may be configured to establish a priority for some data by prioritizing RLC-level retransmissions of a bearer carrying compressed data over transmissions of one or more other bearers. Additionally or alternatively, the wireless device may be configured to establish a priority for some data by prioritizing a MAC-level grant associated with the data. According to some aspects of the present disclosure, prioritization of some data provides a compression gain configured for a specific application associated with the data. Additionally or alternatively, prioritization of some data is configured based on the tolerance for delay of a particular application associated with the data.

[0096] Configuring the communication device to resume transmission before the reordering window timer expires may include configuring one or more wireless devices to Figure 7 For example, according to some aspects of the present disclosure, a wireless device (eg, base station 105, UE 115, etc.) that is to receive compressed data may be configured to increase the duration of the reordering window timer.

[0097] Figure 8 1 is a block diagram illustrating a UE 115 configured according to one aspect of the present disclosure. The UE 115 includes Figure 2 1. The structure, hardware, and components of UE 115 are shown in FIG. 1. For example, UE 115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in memory 282 and controls components of UE 115 that provide features and functions of UE 115. Under the control of controller / processor 280, UE 115 sends and receives signals via wireless radios 801a-r and antennas 252a-r. Wireless radios 801a-r include various components and hardware (e.g., Figure 2 115), including modulators / demodulators 254a-r, a MIMO detector 256, a receive processor 258, a transmit processor 264, and a TX MIMO processor 266.

[0098] As previously described, one or more algorithms stored by the memory 282 configure the processor / controller 280, the transmit processor 264, and / or the receive processor 258 to perform one or more processes related to wireless communications performed by the UE 115. For example, according to some aspects of the present disclosure, the preventive data decompression failure logic 802 can be stored in the memory 282 to enable and provide such operations: using predictive decompression failure indications and / or configurations for transmission recovery to avoid data decompression failures before the reordering window timer expires. The functions of the above-mentioned processes 600 and / or 700 can be implemented, for example, by the UE 115 using the preventive data decompression failure logic 802. For example, in an example of implementing UDC, the predictive data decompression failure logic 803 may include a database of one or more triggering events, wherein the one or more triggering events are selected to predictively indicate a decompression failure at a second device (e.g., a base station 105) receiving compressed data from the UE 115. Additionally, the predictive data decompression failure logic 803 may include logic for detecting or otherwise determining the occurrence of a triggering event and for signaling a compressor reset for the transmission in response to detecting the occurrence of the triggering event (e.g., based at least in part on determining the occurrence of the triggering event), as described above with respect to Figure 6 As described in process 600 of . The data decompression failure avoidance configuration logic 804 may, for example, include logic for identifying or otherwise determining one or more radio bearers for transmitting compressed data. In an example of implementing UDC, the data decompression failure avoidance configuration logic 804 may analyze signaling from the base station 105 for information of (one or more) radio bearers. In addition, the data decompression failure avoidance configuration logic 804 may include logic for configuring the UE 115 to compress data to be transmitted via one or more radio bearers, such as by establishing priorities for some data to provide transmission recovery before the reordering window timer expires. According to some aspects of the present disclosure, the data decompression failure avoidance configuration logic 804 may include logic for configuring another device (e.g., the base station 105) for data decompression failure avoidance, such as providing signaling for implementing an increase in the duration of the reordering window timer at the other device.

[0099] Fig. 9 1 is a block diagram illustrating a base station 105 configured according to one aspect of the present disclosure. The base station 105 includes Figure 21. The structure, hardware, and components of the base station 105 shown in FIG. 1. For example, the base station 105 includes a controller / processor 240 that operates to execute logic or computer instructions stored in a memory 242 and to control components of the base station 105 that provide the features and functions of the base station 105. Under the control of the controller / processor 240, the base station 105 transmits and receives signals via wireless radios 901a-t and antennas 234a-t. The wireless radios 901a-t include various components and hardware (e.g., Figure 2 105), including modulators / demodulators 232a-t, a MIMO detector 236, a receive processor 238, a transmit processor 220, and a TX MIMO processor 230.

[0100] As previously described, one or more algorithms stored by the memory 242 configure the processor / controller 240, the transmit processor 220, and / or the receive processor 228 to perform one or more processes related to wireless communications performed by the base station 105. For example, according to some aspects of the present disclosure, the preventive data decompression failure logic 902 may be stored in the memory 242 to enable and provide such an operation: before the reordering window timer expires, the predictive decompression failure indication and / or the configuration for transmission recovery are used to avoid data decompression failure. The functions of the above-mentioned processes 600 and / or 700 may be implemented, for example, by the base station 105 using the preventive data decompression failure logic 902. In an example of implementing UDC, the predictive data decompression failure logic 903 may include a database of one or more triggering events, and the one or more triggering events are selected to predictively indicate decompression failure. The predictive data decompression failure logic 903 may also include such logic for providing information about the triggering event in the one or more such triggering events to another device such as the UE 115, so as to be used as a predictive decompression failure indication when implementing the preventive data decompression failure operation. The data decompression failure avoidance configuration logic 904 may include information about one or more configurations for data decompression failure avoidance, such as information about prioritization of some data to provide transmission resumption before expiration of a reordering window timer. The data decompression failure avoidance configuration logic 904 may include logic for signaling the data decompression failure avoidance configuration information to another device (e.g., UE 115). Additionally or alternatively, the data decompression failure avoidance configuration logic 904 may include logic for configuring the base station 105 for data decompression failure avoidance, such as by implementing an increase in the duration of a reordering window timer at another device.

[0101] Although the above has been configured for UDC operation Figure 8 UE 115 and Fig. 9Although the example is described for the base station 105 of FIG. 1 , the illustrated example may provide for operation according to the preventive data decompression failure technique for data compression other than UDC. For example, in an example in which downlink data compression is implemented, the preventive data decompression failure logic 802 may include information and logic corresponding to the information and logic described above with reference to the preventive data decompression failure logic 902, and accordingly the preventive data decompression failure logic 902 may include information and logic corresponding to the information and logic described above with reference to the preventive data decompression failure logic 802.

[0102] 1. Methods, apparatus, and articles for wireless communications may provide for detecting, by logic of a first device providing a transmission in a wireless network, the occurrence of a trigger event among multiple trigger events that predictively indicates a decompression failure at a second device receiving the transmission in the wireless network, and, in response to detecting the occurrence of the trigger event, signaling, by the first device to the second device, a compressor memory reset for the transmission.

[0103] 2. The method, apparatus, and article of manufacture of clause 1, wherein the triggering event predictively indicates a decompression failure due to expiration of a reordering window timer at the second device.

[0104] 3. The method, apparatus and article of manufacture of any of clauses 1 and 2, wherein the triggering event corresponds to a reconfiguration between usage of a split radio bearer and usage of a non-split radio bearer.

[0105] 4. The method, apparatus, and article of manufacture of any one of clauses 1 and 2, wherein the triggering event corresponds to a SCGRLF.

[0106] 5. The method, apparatus and article of any one of clauses 1 and 2, wherein the triggering event corresponds to one or more RLC layer ARQ metrics measured by the first device.

[0107] 6. The method, apparatus and article of any one of clauses 1, 2 and 5, wherein the one or more RLC layer ARQ metrics include a metric of round trip time relative to a reordering window timer duration.

[0108] 7. The method, apparatus, and article of manufacture of any of clauses 1 and 2, wherein the triggering event corresponds to at least one of a MAC metric measured by the first device or a HARQ metric measured by the first device.

[0109] 8. The method, apparatus, and article of manufacture of any of clauses 1, 2, and 7, wherein the at least one of the MAC metric or the HARQ metric comprises a BLER.

[0110] 9. The method, apparatus and article of any one of clauses 1 and 2, wherein the triggering event corresponds to at least one of a scheduling delay during an incomplete retransmission or an RLC layer state not received by the first device.

[0111] 10. The method, apparatus and article of any one of clauses 1-9 further provide a dynamic compressor memory reset when any trigger event among the multiple trigger events occurs, wherein the occurrence of the trigger event is detected and the compressor memory reset is signaled to provide the dynamic compressor memory reset when the trigger event occurs.

[0112] 11. The method, apparatus and article of manufacture of any one of clauses 1-10, further providing a static compressor memory reset configured for a periodic compressor memory reset for the transmission.

[0113] 12. The method, apparatus, and article of manufacture of any one of clauses 1-11, wherein the periodic compressor memory reset corresponds to a number of packets transmitted.

[0114] 13. The method, apparatus and article of manufacture of any one of clauses 1-12, further providing for establishing a priority for some data of the transmission to provide transmission resumption before expiration of a reordering window timer at the second device.

[0115] 14. Methods, apparatus and articles according to any of clauses 1-13, wherein establishing priority for some of the transmitted data includes prioritizing radio link control (RLC) layer retransmissions of a bearer carrying compressed data for the transmission over transmissions of one or more other bearers.

[0116] 15. The method, apparatus, and article of manufacture of any of clauses 1-13, wherein establishing priority for some data comprises prioritizing a MAC level grant associated with the data.

[0117] 16. The method, apparatus and article of manufacture of any one of clauses 1-15, further providing for increasing the duration of the reordering window timer.

[0118] 17. The method, apparatus and article of manufacture of any of clauses 1-16, wherein the duration of the reordering window timer is dynamically increased according to BLER conditions.

[0119] 18. Methods, apparatus, and articles for wireless communications can provide for identifying one or more radio bearers for transmission from a first device in a wireless network to a second device in the wireless network, and configuring the first device to compress data to be transmitted via the one or more radio bearers, wherein configuring the first device can include establishing priority for some data to provide transmission recovery before a reordering window timer expires at the second device.

[0120] 19. The method, apparatus, and article of manufacture of clause 18, wherein prioritizing some data provides a compression gain configured for a particular application associated with the data.

[0121] 20. The method, apparatus, and article of manufacture of any of clauses 18 and 19, wherein establishing a priority for some data is configured according to a tolerance for delay of a particular application associated with the data.

[0122] 21. The method, apparatus and article of manufacture of any of clauses 18-20, wherein establishing priority for some data comprises prioritizing RLC-level retransmissions of bearers carrying compressed data for the transmission over transmissions of one or more other bearers.

[0123] 22. The method, apparatus, and article of manufacture of any of clauses 18-20, wherein establishing priority for some data comprises prioritizing a MAC level grant associated with the data.

[0124] 23. The method, apparatus and article of manufacture of any of clauses 18-22, further providing for increasing the duration of the reordering window timer.

[0125] 24. The method, apparatus and article of manufacture of any of clauses 18-74, wherein the duration of the reordering window timer is dynamically increased corresponding to BLER conditions.

[0126] 25. The method, apparatus and article described in any one of clauses 18-24 further provide for detecting, through the logic of the first device, the occurrence of a trigger event among multiple trigger events that predictively indicates a decompression failure at the second device, and for signaling, through the first device to the second device, a compressor memory reset for the transmission in response to the detection of the occurrence of the trigger event.

[0127] 26. The method, apparatus, and article of manufacture of any of clauses 18-25, wherein the triggering event predictively indicates a decompression failure due to expiration of a reordering window timer at the second device.

[0128] 27. A method, apparatus and article of manufacture as recited in any of clauses 18-25, wherein the triggering event corresponds to a reconfiguration between usage of a split radio bearer and usage of a non-split radio bearer.

[0129] 28. The method, apparatus, and article of manufacture of any of clauses 18-25, wherein the triggering event corresponds to a SCG RLF.

[0130] 29. The method, apparatus and article of manufacture of any of clauses 18-25, wherein the triggering event corresponds to one or more RLC layer ARQ metrics measured by the first device.

[0131] 30. The method, apparatus, and article of manufacture of clauses 18-25, wherein the triggering event corresponds to at least one of a medium access control (MAC) metric measured by the first device or a hybrid automatic repeat request (HARQ) metric measured by the first device.

[0132] 31. The method, apparatus and article of manufacture of clauses 18-25, wherein the triggering event corresponds to at least one of a scheduling delay during an incomplete retransmission or a radio link control (RLC) layer state not received by the first device.

[0133] 32. The method, apparatus and article of manufacture according to clauses 18-31, further comprising:

[0134] A dynamic compressor memory reset is provided upon an occurrence of any triggering event among the plurality of triggering events being satisfied, wherein detecting the occurrence of the triggering event and signaling a compressor memory reset provides the dynamic compressor memory reset upon the occurrence of the triggering event.

[0135] 34. The method, apparatus and article of manufacture according to clauses 18-32, further comprising:

[0136] A static compressor memory reset is provided, which is configured for periodic compressor memory reset for said transmission.

[0137] Those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0138] The functional blocks and modules described herein (eg, Figure 2The functional blocks and modules in the embodiment may include processors, electronic devices, hardware devices, electronic components, logic circuits, memory, software codes, firmware codes, etc., or any combination thereof. In addition, the features related to the preventive data decompression failure technology discussed herein may be implemented via a dedicated processor circuit system, via executable instructions, and / or a combination thereof.

[0139] The skilled person will further understand that the various illustrative logical blocks, modules, circuits, and algorithm steps (e.g., Figure 6 and Figure 7 The logic blocks in the system (in the example) can be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. The technician can implement the described functions in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. The technician will also easily recognize that the order or combination of components, methods, or interactions described herein are merely examples, and the components, methods, or interactions of various aspects of the present disclosure may be combined or performed in a manner different from those illustrated and described herein.

[0140] The various illustrative logic blocks, modules, and circuits described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but, in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).

[0141] The steps of the method or algorithm described in conjunction with the disclosure herein can be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module can reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium can be integrated into the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In an alternative, the processor and the storage medium can reside in a user terminal as discrete components.

[0142] In one or more exemplary designs, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions can be stored or transmitted on a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that promotes the transmission of a computer program from one place to another. Computer-readable storage media can be any available medium that can be accessed by a general or special-purpose computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code components in the form of instructions or data structures and can be accessed by a general or special-purpose computer or a general or special-purpose processor. In addition, the connection can be appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair or digital subscriber line (DSL) is used to transmit software from a website, server or other remote source, then the coaxial cable, fiber optic cable, twisted pair or DSL are all included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), hard disk, solid state disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0143] As used herein, including in the claims, the term "and / or," when used in a list of two or more items, means that any one of the listed items may be employed alone, or any combination of two or more of the listed items may be employed. For example, if a composition is described as comprising components A, B, and / or C, the composition may: comprise A alone; comprise B alone; comprise C alone; comprise a combination of A and B; comprise a combination of A and C; comprise a combination of B and C; or comprise a combination of A, B, and C. Furthermore, as used herein, including in the claims, "or" used in a list of items beginning with "at least one" means a disjunctive list, such that, for example, a list of "at least one of A, B, or C" means any one of A or B or C or AB or AC or BC or ABC (i.e., A and B and C), or any combination thereof.

[0144] The foregoing description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein, but to be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A wireless communication method, comprising: detecting, by logic of a first device providing transmission of compressed data in a wireless network, an occurrence of a trigger event selected from a plurality of different types of trigger events as predictively indicating a decompression failure at a second device receiving the transmission of the compressed data in the wireless network, the trigger event of the decompression failure at the second device resulting from a reference to a previous block of compressed data that is not available at the second device, without requiring that the first device have received from the second device signaling a control compressor memory reset corresponding to the trigger event; as well as Corresponding to detecting the occurrence of the triggering event, the first device signals the second device receiving the transmission of the compressed data to reset a compressor memory of the second device.

2. The method of claim 1 , wherein the plurality of different types of trigger events include trigger events corresponding to different communication events in the wireless network, and wherein the trigger event corresponds to a decompression failure due to expiration of a reordering window timer at the second device.

3. The method according to claim 1, wherein the trigger event corresponds to a reconfiguration between the use of a separate radio bearer and the use of a non-separate radio bearer, a secondary cell group SCG radio link failure RLF, one or more radio link control RLC layer automatic repeat request ARQ metrics measured by the first device, a media access control MAC metric measured by the first device, or at least one of a hybrid automatic repeat request HARQ metric measured by the first device, or a scheduling delay during an incomplete retransmission or a radio link control RLC layer state not received by the first device.

4. The method according to claim 1, further comprising: Providing a dynamic compressor memory reset upon the occurrence of any trigger event among the plurality of different types of trigger events being satisfied, wherein detecting the occurrence of the trigger event and signaling a reset of the compressor memory of the second device provides the dynamic compressor memory reset upon the occurrence of the trigger event.

5. The method according to claim 1, further comprising: A static compressor memory reset is provided, which is configured to periodically reset the compressor memory of the second device for the transmission of the compressed data, wherein the static compressor memory reset implements the periodic reset of the compressor memory of the second device corresponding to the number of data packets transmitted for the compressed data, and wherein the periodic reset of the compressor memory of the second device is performed in addition to the compressor memory reset of the second device corresponding to the detection of the occurrence of the trigger event.

6. The method according to claim 1, further comprising: Priority is established for some data of the transmission of the compressed data to provide transmission recovery before expiration of a reordering window timer implemented by the second device, the reordering window timer being used to establish a duration during which packets of the transmission of the compressed data are received for reordering and provided to an upper layer.

7. The method of claim 6, wherein establishing a priority for some data of the transmission of the compressed data comprises: prioritizing a radio link control, RLC, level retransmission of a bearer of compressed data carrying the transmission of the compressed data over transmission of one or more other bearers; or A Medium Access Control (MAC) level grant associated with the data is prioritized.

8. The method according to claim 6, wherein the duration of the reordering window timer is dynamically increased corresponding to a block error rate (BLER) condition.

9. An apparatus configured for wireless communication, the apparatus comprising: a processing system comprising at least one processor; as well as a memory storage coupled to the at least one processor, wherein the processing system is configured to cause the apparatus to: detecting, by a first device providing transmission of compressed data in a wireless network, an occurrence of a trigger event selected from a plurality of different types of trigger events as predictively indicating a decompression failure at a second device receiving the transmission of the compressed data in the wireless network, the trigger event of the decompression failure at the second device resulting from a reference to a previous block of compressed data that is not available at the second device, without requiring that the first device have received from the second device signaling a control compressor memory reset corresponding to the trigger event; as well as Corresponding to detecting the occurrence of the triggering event, the first device signals the second device receiving the transmission of the compressed data to reset a compressor memory of the second device.

10. The apparatus of claim 9, wherein the plurality of different types of trigger events include trigger events corresponding to different communication events in the wireless network, and wherein the trigger event corresponds to a decompression failure due to expiration of a reordering window timer at the second device.

11. An apparatus according to claim 9, wherein the trigger event corresponds to a reconfiguration between the use of a separate radio bearer and the use of a non-separate radio bearer, a secondary cell group SCG radio link failure RLF, one or more radio link control RLC layer automatic repeat request ARQ metrics measured by the first device, a media access control MAC metric measured by the first device, or at least one of a hybrid automatic repeat request HARQ metric measured by the first device, or a scheduling delay during an incomplete retransmission or a radio link control RLC layer state not received by the first device.

12. The apparatus of claim 9, wherein the processing system is further configured to cause the apparatus to: Providing a dynamic compressor memory reset upon the occurrence of any trigger event among the plurality of different types of trigger events, wherein detecting the occurrence of the trigger event and signaling a reset of the compressor memory of the second device provides the dynamic compressor memory reset upon the occurrence of the trigger event.

13. The apparatus of claim 9, wherein the processing system is further configured to cause the apparatus to: providing a static compressor memory reset, the static compressor memory reset being configured for periodic resetting of the compressor memory of the second device for transmission of the compressed data, wherein the static compressor memory reset implements the periodic resetting of the compressor memory of the second device corresponding to the number of packets of the transmission of the compressed data, and wherein, The periodic resetting of the compressor memory of the second device is performed in addition to the resetting of the compressor memory of the second device corresponding to detecting the occurrence of the triggering event.

14. The apparatus of claim 9, wherein the processing system is further configured to cause the apparatus to: Priority is established for some data of the transmission of the compressed data to provide transmission recovery before expiration of a reordering window timer implemented by the second device, the reordering window timer being used to establish a duration during which packets of the transmission of the compressed data are received for reordering and provided to an upper layer.

15. A wireless communication method, comprising: identifying one or more radio bearers for transmission of compressed data from a first device in a wireless network to a second device in the wireless network for receiving transmission of the compressed data; as well as The first device is configured to compress data for transmission to the second device via the one or more radio bearers, wherein configuring the first device includes establishing a priority at the first device for transmission of some data from the first device to the second device to provide transmission recovery before expiration of a reordering window timer implemented by the second device for receiving packets for transmission of the compressed data, and the reordering window timer is used to establish a duration during which packets for transmission of the compressed data are received for reordering and provided to an upper layer.

16. The method of claim 15, wherein prioritizing transmission of some data at the first device provides a compression gain configured for a particular application associated with the data.

17. The method of claim 15, wherein establishing a priority at the first device for transmission of some data is configured according to a tolerance for delay of a particular application associated with the data.

18. The method of claim 15, wherein establishing, at the first device, a priority for transmission of some data comprises: prioritizing a radio link control, RLC, level retransmission of a bearer of compressed data carrying the transmission of the compressed data over transmission of one or more other bearers; or A Medium Access Control (MAC) level grant associated with the data is prioritized.

19. The method of claim 15, wherein the duration of the reordering window timer is dynamically increased corresponding to a block error rate (BLER) condition.

20. The method of claim 15, further comprising: detecting, by logic of the first device, an occurrence of a trigger event of a plurality of different types of trigger events selected to predictively indicate a decompression failure at the second device, the occurrence of the trigger event of the decompression failure at the second device being due to referencing a previous block of compressed data that is not available at the second device; as well as Corresponding to detecting the occurrence of the triggering event, the first device signals the second device receiving the transmission of the compressed data to reset a compressor memory of the second device.

21. The method of claim 20, wherein the triggering event predictively indicates a decompression failure due to expiration of a reordering window timer at the second device.

22. A method according to claim 20, wherein the trigger event corresponds to a reconfiguration between the use of a separate radio bearer and the use of a non-separate radio bearer, a secondary cell group SCG radio link failure RLF, one or more radio link control RLC layer automatic repeat request ARQ metrics measured by the first device, a media access control MAC metric measured by the first device, or at least one of a hybrid automatic repeat request HARQ metric measured by the first device, or a scheduling delay during an incomplete retransmission or a radio link control RLC layer state not received by the first device.

23. The method of claim 20, further comprising: Providing a dynamic compressor memory reset upon the occurrence of any trigger event among a plurality of trigger events satisfying the different types, wherein detecting the occurrence of the trigger event and signaling a reset of the compressor memory of the second device provides the dynamic compressor memory reset upon the occurrence of the trigger event.

24. The method of claim 20, further comprising: A static compressor memory reset is provided, which is configured to periodically reset the compressor memory of the second device for the transmission of the compressed data, wherein the static compressor memory reset implements the periodic reset of the compressor memory of the second device corresponding to the number of data packets transmitted for the compressed data, and wherein the periodic reset of the compressor memory of the second device is performed in addition to the compressor memory reset of the second device corresponding to the detection of the occurrence of the trigger event.

25. An apparatus configured for wireless communication, the apparatus comprising: a processing system comprising at least one processor, and a memory storage coupled to the at least one processor, wherein the processing system is configured to cause the apparatus to: identifying one or more radio bearers for transmission of compressed data from a first device in a wireless network to a second device in the wireless network for receiving transmission of the compressed data; as well as The first device is configured to compress data for transmission to the second device via the one or more radio bearers, wherein configuring the first device includes establishing a priority at the first device for transmission of some data from the first device to the second device to provide transmission recovery before expiration of a reordering window timer implemented by the second device for receiving packets for transmission of the compressed data, and the reordering window timer is used to establish a duration during which packets for transmission of the compressed data are received for reordering and provided to an upper layer.

26. The apparatus of claim 25, wherein prioritizing transmission of some data at the first device provides a compression gain configured for a particular application associated with the data.

27. The apparatus of claim 25, wherein establishing a priority at the first device for transmission of some data is configured according to a tolerance for delay of a particular application associated with the data.

28. The apparatus of claim 25, wherein the processing system is further configured to cause the apparatus to: prioritizing a radio link control, RLC, level retransmission of a bearer of compressed data carrying the transmission of the compressed data over transmission of one or more other bearers; or A Medium Access Control (MAC) level grant associated with the data is prioritized.

29. The apparatus of claim 25, wherein the duration of the reordering window timer is dynamically increased according to a condition corresponding to a block error rate (BLER).

30. The apparatus of claim 25, wherein the processing system is further configured to cause the apparatus to: detecting, by the first device, an occurrence of a trigger event of a plurality of different types of trigger events selected to predictively indicate a decompression failure of the plurality of trigger events at the second device, the occurrence of the trigger event of the decompression failure at the second device being due to referencing a previous block of compressed data that is not available at the second device; and Corresponding to detecting the occurrence of the triggering event, the first device signals the second device receiving the transmission of the compressed data to reset a compressor memory of the second device.

31. A computer readable medium having program code recorded thereon, wherein: The program code may be executed by one or more processors of a device configured for wireless communication, so that the processors perform the method according to any one of claims 1-8 and 15-24.

Images