Techniques to facilitate radio resource control message segmentation

Abstract

Apparatuses, methods, and computer-readable media for facilitating RRC message segmentation are disclosed herein. An example method for wireless communication at a user equipment (UE) includes receiving an indication from a network to enable a segment of an uplink control message. The example method also includes transmitting an uplink control message based on uplink control information to the network without the segment based on at least one of a channel condition or a count of connection releases from the network. In some examples, the uplink control information may have a size greater than a maximum PDCP SDU size.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Indian Patent Application Serial No. 202241053030, titled “TECHNIQUES TO FACILITATE RADIO RESOURCE CONTROLMESSAGE SEGMENTATION” and filed on September 16, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications employing message segmentation. Background Art

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

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, methods, computer-readable media, and apparatus for wireless communications are provided. An apparatus may include a user equipment (UE). The example apparatus may receive an indication from a network to enable segmentation of an uplink control message. The example apparatus may also send an uplink control message based on uplink control information to the network without the segmentation based on at least one of a channel condition or a count of connection releases from the network, the uplink control information having a size greater than a maximum packet data convergence protocol (PDCP) service data unit (SDU) size.

[0008] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0011] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0012] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0013] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

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

[0015] Figure 4 An example communication flow between a network entity and a UE according to various aspects of the present disclosure is illustrated.

[0016] Figure 5 is a diagram illustrating an example segmentation process for an uplink control message in accordance with various aspects of the present disclosure.

[0017] Figure 6 An example communication flow between a network entity and a UE according to various aspects of the present disclosure is illustrated.

[0018] Figure 7 Pseudo code is included that can facilitate a UE to determine whether to employ message segmentation for an uplink control message based on serving cell conditions in accordance with various aspects of the present disclosure.

[0019] Figure 8 An example communication flow between a network entity and a UE according to various aspects of the present disclosure is illustrated.

[0020] Fig. 9 An example communication flow between a network entity and a UE according to various aspects of the present disclosure is illustrated.

[0021] Fig.10 Pseudo code is included that can facilitate a UE to determine whether to employ message segmentation for an uplink control message based on a network behavior that causes the network to output an immediate connection release message in accordance with various aspects of the present disclosure.

[0022] Fig.11 An example communication flow between a network entity and a UE according to various aspects of the present disclosure is illustrated.

[0023] Fig.12 An example communication flow between a network entity and a UE according to various aspects of the present disclosure is illustrated.

[0024] Fig.13 A table illustrating different actions taken by a UE with respect to different instances of a capability query message is depicted in accordance with various aspects of the present disclosure.

[0025] Fig.14 An example communication flow between a network entity and a UE according to various aspects of the present disclosure is illustrated.

[0026] Fig.15 is a flow chart of a method of wireless communication at a UE according to the teachings disclosed herein.

[0027] Fig.16 is a flow chart of a method of wireless communication at a UE according to the teachings disclosed herein.

[0028] Fig.17 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0029] The wireless communication system supports message exchange between the UE and the network. For example, the UE may determine information for transmission, encode the information in a message, and then transmit a communication including the message. In some aspects, the amount of uplink control information encoded in the message may be large, and the size of the message may be undesirably large. For example, the size of the message may exceed a packet size limit. In such a scenario, in order to meet the packet size limit, the UE may be limited in the amount of uplink control information that the UE provides to the network via a message.

[0030] In some aspects, the UE may be configured to employ segmentation to send messages using segmentation. For example, the network may provide a segmentation indicator that enables or disables message segmentation at the UE for messages such as uplink control messages. In a scenario where message segmentation is disabled, the amount of uplink control information that the UE may encode in the uplink control message may be limited so that the size of the uplink control message is no greater than a packet size limit (e.g., the size of the uplink control message is less than or equal to the packet size limit). The UE may then send the uplink control message to the network without segmentation.

[0031] In a scenario where message segmentation is enabled, the amount of uplink control information that the UE can encode in the uplink control message is not subject to the packet size limit for one packet. However, the amount of uplink control information encoded in the uplink control message may or may not meet the packet size limit. In an example where the size of the uplink control message fails to meet the packet size limit, the UE may perform message segmentation and send the uplink control message via two or more segments. For example, the UE may divide the uplink control message into N segments so that the size associated with each corresponding segment meets the packet size limit. Each segment in the segment may contain a portion of the uplink control message. The UE may then send each of these segments to the network via a segmented message.

[0032] Thus, message segmentation may enable the UE to provide a larger amount of information.For example, when encoding an uplink control message, the UE may no longer be constrained by the packet size limit for one packet.

[0033] However, in some examples, the use of message segmentation may result in reduced communication performance between the UE and the network. For example, if an ACK message is not received from the network after sending an uplink control message or a segmented message, the UE may resend the uplink control message or a segment of the uplink control message (e.g., a segmented message). The resending of the uplink control message or the segmented message may result in delay time on the network side and / or consume transmission resources on the UE side.

[0034] In some examples, when channel conditions are not optimal, using segmentation to send uplink control messages may cause the UE to resort to retransmissions, which may cause delays in processing the uplink control messages at the network. For example, the network may use the information provided via the uplink control message to facilitate performing an attach procedure or a mobility procedure with the UE. In scenarios where channel conditions are poor, the UE may experience a high uplink / downlink block error rate (BLER) associated with sending uplink control messages, which may cause an overall delay in providing information for the uplink control message using segmentation at the UE.

[0035] In some aspects, the network may not be able to process message segmentation or may not be configured to receive uplink control messages with segmentation. For example, when the network receives an uplink control message with segmentation (e.g., when the network receives a segmentation message), the network may send a connection release message. In some aspects, the network may maintain a timer associated with receiving an uplink control message with segmentation. In some such examples, if the UE takes too long to transmit an uplink control message with segmentation, the network may send a connection release message. For example, the network may send a connection release message when a timer expires.

[0036] In some aspects, the UE may stop transmitting the remaining segments of the uplink control message after receiving the connection release message. Therefore, the UE may not be able to provide the network with information encoded in the uplink control message. Additionally, based on the network not receiving the information encoded in the uplink control message, the network may not be able to provide certain communication services to the UE.

[0037] Various aspects disclosed herein provide a technique for enabling a UE configured with message segmentation to determine whether to adopt message segmentation based on at least one of a channel condition or a count of connection releases from a network. For example, even when message segmentation is permitted based on the size of uplink control information associated with a message, the UE may determine to skip adopting message segmentation. As used herein, when message segmentation is enabled (e.g., via a segmentation indicator) and the size of the uplink control information fails to meet a packet size limit (e.g., the size of the uplink control message is greater than the packet size limit), the UE may be permitted to adopt message segmentation. For purposes of this disclosure, when the size of the uplink control message is greater than the packet size limit or the size of the uplink control information associated with the uplink control message is greater than the packet size limit, failure to meet the packet size limit may occur. Therefore, the size of the uplink control message and the size of the uplink control information may be used interchangeably.

[0038] In some examples, even when message segmentation is permitted, the UE may evaluate the channel conditions of the serving cell and determine to send the uplink control message without segmentation. That is, the size of the uplink control message may not meet the packet size limit (e.g., the size of the uplink control message is greater than the packet size limit), but the UE may determine to send the uplink control message without segmentation based on the channel conditions. For example, when the UE determines that the channel conditions are poor, the UE may send the uplink control message without segmentation. However, when the UE determines that the channel conditions are not poor, the UE may send the uplink control message with segmentation.

[0039] In some aspects, even when message segmentation is permitted, the UE may be configured to determine whether to employ message segmentation based on an assessment of the network and its ability to handle message segmentation. For example, the network may be configured to send a connection release message when it receives a segmented message or when a timer associated with receiving an uplink control message with segmentation expires. In aspects disclosed herein, the UE may maintain a count of connection release messages received from the network while attempting to send an uplink control message with segmentation. In some such examples, when the count of connection release messages is greater than a release threshold, the UE may determine to skip using message segmentation even when message segmentation is permitted (e.g., based on the size of the uplink control message).

[0040] For example, before generating an uplink control message, the UE may compare its count of connection release messages with a release threshold. In an example where the count of connection release messages is less than or equal to the release threshold, the UE may generate the uplink control message without being constrained by the packet size limit for one message. The UE may then send the uplink control message with or without segmentation based on the size of the uplink control message. In an example where the count of connection release messages is greater than the release threshold, the UE may then generate the uplink control message by limiting the amount of uplink control information encoded in the uplink control message based on the size of the uplink control message.

[0041] In some aspects disclosed herein, after the UE determines to skip adopting message segmentation even when permitted, the UE may continue to skip adopting message segmentation until the UE detects the occurrence of an update triggering event. In some examples, after detecting the occurrence of an update triggering event, the UE may be configured to send an update message to the network. The update message may notify the network to perform a resynchronization process with the UE. For example, the network may output a capability query message after receiving the update message.

[0042] In some examples, the UE may detect the occurrence of an update triggering event based on a change in channel conditions. For example, if the UE determines to skip adopting message segmentation after determining that the channel conditions are bad, the UE may detect the occurrence of an update triggering event after determining a change in channel conditions (e.g., the channel conditions are no longer bad or the channel conditions are good). In other examples, the UE may detect the occurrence of an update triggering event after performing a mobility procedure to another serving cell with better channel conditions.

[0043] In an example where the UE determines to skip adopting message segmentation based on a count of connection release messages, the UE may detect the occurrence of an update triggering event based on a change in its connection with the network. For example, the UE may detect the occurrence of an update triggering event in response to a change in at least one of a serving cell, a tracking area, or a serving network node. In some examples, the UE may determine a change in a tracking area based on a change in a tracking area identifier (TAI) and / or a change in a registration area (RA).

[0044] Various aspects presented herein may enable a UE to improve communication performance in scenarios where message segmentation is permitted. For example, under poor channel conditions, avoiding message segmentation may reduce overhead associated with uplink transmissions, which may avoid or reduce delays associated with procedures (such as attach procedures) based on information provided by the UE via uplink control messages. Avoiding message segmentation under poor channel conditions may also reduce the likelihood of connection drops due to lost acknowledgment messages from the network after the UE sends an uplink control message.

[0045] In an example where the UE avoids message fragmentation based on a count of connection release messages, the UE may be able to improve communication performance by maintaining a connection with the network. For example, if the network performs an immediate connection release after the UE sends a fragmentation message, the UE may have the ability to determine that the network cannot handle message fragmentation based on a count of connection release messages. In such an example, the UE may skip message fragmentation when communicating with the network to maintain a connection with the network.

[0046] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

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

[0048] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, or any combination thereof.

[0049] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0050] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0051] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NRBS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0052] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0053] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0054] Figure 1 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs (e.g., CU 110), which may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) (e.g., near RT RIC 125) via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework (e.g., SMO framework 105), or both. CU 110 may communicate with one or more DUs (e.g., DU 130) via corresponding midhaul links (such as F1 interfaces). DU 130 may communicate with one or more RUs (e.g., RU 140) via corresponding fronthaul links. RU 140 may communicate with corresponding UEs (e.g., UE 104) via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served by multiple RUs simultaneously.

[0055] Each of the units (i.e., CU (e.g., CU 110), DU (e.g., DU 130), RU (e.g., RU 140), and near-RT RIC (e.g., near-RT RIC 125), non-RT RIC (e.g., non-RT RIC 115), and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via the wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.

[0056] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), or service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signal transmission.

[0057] DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0058] Lower layer functionality may be implemented by one or more RUs. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, the RU 140 may be implemented to handle air (OTA) communications with one or more UEs (e.g., UE 104). In some specific implementations, the real-time and non-real-time aspects of the control plane and user plane communications with the RU 140 may be controlled by the corresponding DU. In some scenarios, this configuration may enable the DU and CU110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0059] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU, DU, RU, and near-RT RIC. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0060] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs, one or more DUs, or both, and the O-eNB with the near-RT RIC 125.

[0061] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0062] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between a RU (e.g., RU 140) and a UE (e.g., UE 104) may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

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

[0064] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / Wi-Fi AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0065] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0066] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, currently higher frequency bands are being explored to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0067] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0068] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

[0069] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0070] The core network 120 may include an access and mobility management function (AMF) (e.g., AMF 161), a session management function (SMF) (e.g., SMF 162), a user plane function (UPF) (e.g., UPF 163), a unified data management (UDM) (e.g., UDM 164), one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) (e.g., GMLC 165) and a location management function (LMF) (e.g., LMF 166). However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or a serving base station (e.g., base station 102). The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0071] Examples of UE include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access a network together and / or individually.

[0072] Reference again Figure 1 In certain aspects, a device communicating with a network, such as a UE 104 communicating with a network entity, such as a base station 102 or a component of a base station (e.g., a CU 110, a DU 130, and / or a RU 140), may be configured to manage one or more aspects of wireless communications. For example, the UE 104 may include a message segmentation component 198 configured to facilitate performing message segmentation based on channel conditions and / or network capabilities in addition to message size.

[0073] In certain aspects, the message segmentation component 198 may be configured to receive an indication from the network to enable segmentation of the uplink control message. The example message segmentation component 198 may also be configured to send an uplink control message based on uplink control information having a size greater than a maximum Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) size to the network without the segmentation based on at least one of channel conditions or a count of connection releases from the network.

[0074] Various aspects presented herein may enable a UE to skip employing message segmentation even when permitted, which may facilitate improved communication performance, for example, by reducing overhead associated with uplink transmissions and maintaining connectivity between the UE and the network.

[0075] Although the following description provides examples for 5G NR (and specifically, for message segmentation associated with UE capability information messages), the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, 6G, and / or other wireless technologies in which a UE sends uplink control messages that may be generated to have a size greater than a packet size limit.

[0076] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0077] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of equal size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0078]

[0079] Table 1: Parameter set, SCS and CP

[0080] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ As shown in Table 1, the subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0081] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

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

[0084] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0085] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0086] Figure 3 is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. Figure 3 In the illustrated example of , the first wireless device may include a base station 310, the second wireless device may include a UE 350, and the base station 310 may communicate with the UE 350 in an access network. Figure 3 As shown, base station 310 includes a transmit processor (TX processor 316), a transmitter 318Tx, a receiver 318Rx, an antenna 320, a receive processor (RX processor 370), a channel estimator 374, a controller / processor 375, and a memory 376. Example UE 350 includes antenna 352, a transmitter 354Tx, a receiver 354Rx, an RX processor 356, a channel estimator 358, a controller / processor 359, a memory 360, and a TX processor 368. In other examples, base station 310 and / or UE 350 may include additional or alternative components.

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

[0088] The TX processor 316 and the RX processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. The channel estimate from the channel estimator 374 can be used to determine the coding and modulation schemes and for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback sent by the UE 350. Each spatial stream can then be provided to a different antenna in the antenna 320 via a separate transmitter (e.g., transmitter 318Tx). Each transmitter 318Tx can modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0089] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna in the antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. In the case where multiple spatial streams are destined for the UE 350, two or more of the multiple spatial streams can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0091] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0092] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different ones of the antennas 352 via separate transmitters (e.g., transmitter 354Tx). Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0093] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding one of the antennas 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0094] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0095] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the message segmentation component 198.

[0096] In some aspects, a wireless communication system may support the exchange of radio capabilities of UEs in a network, for example, to provide communication services to the UE. In some examples, the network may obtain the radio capabilities of the UE via a UE capability query process. For example, a network entity may send (e.g., output) a capability query message received (e.g., obtained) by the UE. The capability query message may request information indicating capabilities associated with one or more radio access technologies (RATs) supported by the UE. The UE may then generate a UE capability information message based on the capability query message to provide to the network. Examples of UE capability information (e.g., uplink control information) may indicate one or more power classes, one or more frequency bands, one or more carrier aggregation frequency band combinations, one or more duplex modes, one or more service profiles (e.g., voice-centric, data-centric, etc.), one or more radio bearers, etc. supported by the UE. The UE capability information message may be an RRC message. The UE capability information message may be referred to as a "UECapabilityInformation" message or any other name.

[0097] In some aspects, the amount of information used to indicate the radio capabilities of the UE may be large, and the size of the uplink control information (e.g., UE capability information) associated with the UE capability information message may be undesirably large. For example, the size of the UE capability information message may exceed a packet size limit, such as a maximum PDCP SDU size. In such scenarios, in order to meet the packet size limit, the UE may be limited in its ability to express its radio capabilities.

[0098] In some aspects, the UE may be configured to employ segmentation to send the UE capability information message using segmentation. For example, the network may provide a segmentation indicator that enables or disables message segmentation at the UE for an uplink control message (such as a UE capability information message). In a scenario where message segmentation is disabled, the amount of uplink control information that the UE may encode in the uplink control message may be limited so that the size of the uplink control message is not greater than the packet size limit (e.g., the size of the uplink control message is less than or equal to the packet size limit). The UE may then send the uplink control message to the network without segmentation.

[0099] In a scenario where message segmentation is enabled, the amount of uplink control information that the UE can encode in an uplink control message may not be subject to the packet size limit for one message. However, the amount of uplink control information encoded in the uplink control message may or may not meet the packet size limit. In an example where the size of the uplink control message fails to meet the packet size limit, the UE may perform message segmentation and send the uplink control message via two or more segments. For example, the UE may divide the uplink control message into N segments so that the size associated with each corresponding segment meets the packet size limit. Each segment in the segment may contain a portion of the uplink control message. In some examples, the UE may be configured with a maximum number of segments, such as 16 segments. In such scenarios, the amount of uplink control information that the UE can encode into the uplink control message may be subject to the packet size limit and the maximum number of segments. The UE may then send each of these segments to the network via a segmented message. The segmented message may be referred to as a "ULDedicatedMessageSegment" message or any other name.

[0100] As an example, the packet size limit in LTE is 8188 bytes. In an example where the size of the uplink control message is less than or equal to the packet size limit, the UE may send the uplink control message without segmentation. In an example where the size of the uplink control message is greater than the packet size limit, the UE may generate N segments so that each segment contains a portion of the uplink control message and is less than or equal to the packet size limit. For example, the size of the uplink control message encoded by the UE may be 20,000 (20K) bytes. In such an example, the UE may divide the uplink control message into three segments. The three segments may have the same size or may have different sizes. However, the size of any one of the three segments is less than or equal to the packet size limit (e.g., less than or equal to the packet size limit of 8188 bytes).

[0101] Thus, message segmentation may enable the UE to provide a larger amount of uplink control information.For example, when encoding an uplink control message, the UE may no longer be constrained by the packet size limit for one packet.

[0102] Figure 4 An example communication flow 400 between a network entity 402 and a UE 404 as presented herein is illustrated. One or more aspects described with respect to the network entity 402 may be performed by a component of a base station or components of a base station such as a CU, DU, and / or RU. Aspects of the network entity 402 are performed by Figure 1 Base station 102 and / or Figure 3 Various aspects of UE 404 may be implemented by base station 310. Figure 1UE 104 and / or Figure 3 UE 350. Figure 4 Not shown in the illustrated example, but in additional or alternative examples, the network entity 402 and / or the UE 404 may communicate with one or more other base stations or UEs.

[0103] exist Figure 4 In the illustrated example, communication flow 400 facilitates UE 404 sending an uplink control message that can be obtained by network entity 402. In some aspects, UE 404 can send the uplink control message without segmentation. In other aspects, UE 404 can send the uplink control message with segmentation.

[0104] like Figure 4 As shown, network entity 402 and UE 404 are in communication. For example, UE 404 may perform a connection establishment procedure 410 to establish an RRC connection with network entity 402. UE 404 may then communicate with network entity 402 while operating in an RRC connected mode, which may be referred to as an "RRC_CONNECTED" mode or any other name.

[0105] exist Figure 4 In the illustrated example of , the network entity 402 may send (e.g., output) a capability query message 412 that is received (e.g., obtained) by the UE 404. The capability query message 412 may request the radio access capabilities of the UE 404. The radio access capabilities may be associated with one or more RATs, such as NR, E-UTRA, and / or other RATs.

[0106] like Figure 4 As shown, the network entity 402 may output a segmentation indicator 414 received by the UE 404. The segmentation indicator 414 may indicate whether message segmentation (e.g., RRC message segmentation) is enabled or disabled at the UE 404. For example, the segmentation indicator 414 may be set to a first value ("0") to indicate that message segmentation is disabled at the UE 404, and may be set to a second value ("1") to indicate that message segmentation is enabled at the UE 404. In some examples, the segmentation indicator 414 may be included with the capability query message 412. For example, the capability query message 412 may include one or more fields, and the segmentation indicator 414 may be provided via at least one field of the capability query message 412. The segmentation indicator 414 may be referred to as an "rrc-SegAllowed" field or any other name.

[0107] As described above, the UE 404 may be configured with message segmentation enabled or disabled. In the illustrated example, the UE 404 may perform a segmentation determination process 420 to determine whether the UE 404 is configured to employ message segmentation. If the UE 404 determines that it is not configured to employ message segmentation (e.g., the segmentation indicator 414 is set to a value indicating that message segmentation is disabled), the UE 404 may perform a generation process 422 to generate a UE capability information message 424 having an amount of information (e.g., uplink control information) that satisfies a packet size limit. For example, the amount of uplink control information that the UE 404 may encode in the UE capability information message 424 may be limited so that the size of the UE capability information message 424 is less than or equal to the packet size limit (e.g., the size of the UE capability information message 424 is less than or equal to the maximum PDCP SDU size). The UE capability information message 424 may be an RRC message and may be referred to as an "encoded RRC message," "encoded RRC PDU," or any other name. Then, the UE 404 may send the UE capability information message 424 without segmentation. That is, the UE 404 may send the UE capability information message 424 to the network entity 402 as a non-segmented message.

[0108] In a scenario where UE 404 determines that message segmentation is enabled (e.g., via segmentation determination process 420), the amount of uplink control information that the UE can encode in the uplink control message is not constrained by the packet size limit for one packet. For example, UE 404 can perform generation process 430 to generate UE capability information message 432 in response to capability query message 412. The amount of uplink control information that UE 404 can encode in UE capability information message 432 may not be constrained by the packet size limit.

[0109] However, the size of the UE capability information message 432 may or may not meet the packet size restriction. For example, the UE 404 may perform a size determination process 434 to determine whether the size of the UE capability information message 432 meets the packet size restriction.

[0110] In an example where the size of the UE capability information message 432 satisfies the packet size limit (e.g., the UE 404 determines that the size of the UE capability information message 432 is less than or equal to the packet size limit), the UE 404 may send the UE capability information message 432 to the network entity 402 without segmentation. In an example where the size of the UE capability information message 432 is greater than the packet size limit, the UE 404 may perform message segmentation and send the UE capability information message 432 via two or more segments. For example, the UE 404 may perform a segmentation process 440 and divide the UE capability information message 432 into N segments. In some examples, the UE 404 may be configured with a maximum number of segments, such as 16 segments. In such a scenario, the number of N segments may be less than or equal to the maximum number of segments (e.g., N≤16 segments).

[0111] like Figure 4 As shown, UE 404 may send a segmented message 442 that is received by network entity 402. The segmented message may be referred to as a "ULDedicatedMessageSegment" message or any other name. Network entity 402 may perform an assembly process 450 to reassemble UE capability information message 432 based on the segmented message 442 it received.

[0112] Figure 5 is a diagram illustrating an example segmentation process 500 for an uplink control message 502 as presented herein. Aspects of the uplink control message 502 may be Figure 4 This is achieved by sending the UE capability information message 432. Figure 5 In the example of , the segmentation process 500 can segment the uplink control message 502 into N segments. For example, the segmentation process 500 can generate the first segment 510 ("Segment (0)") ..., and the nth segment 520 ("Segment (N-1)").

[0113] Each of the segments may contain a portion of the uplink control message 502. For example, the first segment 510 includes a segment container 512 corresponding to the first portion of the uplink control message 502. The first segment 510 may also include a segment number indicator 514 and a segment type indicator 516. The segment number indicator 514 may indicate a sequence number of the segment based on the N segments. The segment type indicator 516 may indicate whether the corresponding segment is the last segment of the N segments. For example, the segment type indicator 516 may be set to a first value ("1") to indicate that the corresponding segment is the last segment of the N segments, otherwise it may be set to a second value ("0").

[0114] As an example, the segment number indicator 514 of the first segment 510 may be set to "0" to indicate that it is the first segment of the N segments, and the segment type indicator 516 of the first segment 510 may be set to the second value ("0") to indicate that it is not the last segment of the N segments. Additionally, the segment number indicator of the nth segment 520 may be set to "N-1" to indicate that it is the nth segment of the N segments, and the segment type indicator of the nth segment 520 may be set to the first value ("1") to indicate that it is the last segment of the N segments.

[0115] Additionally, the size of each corresponding segment may satisfy the packet size limit. As an example, the size of the uplink control message 502 may be 20K bytes, and the UE may be configured with a maximum PDCP SDU size of 9K bytes. In such examples, the UE may divide the uplink control message 502 into three segments, each segment having a size that satisfies the packet size limit (e.g., less than or equal to the maximum PDCP SDU size of 9K bytes). In some examples, the size of each segment message may be the same. For example, the size of each segment message in the three segment messages may be 6,666 bytes (e.g., 20K bytes / 3 segments=6,666 bytes / segment). In other examples, the size of the segment messages may be different. For example, the size of the first two segment messages may be equal to the packet size limit (e.g., 9K bytes), and the size of the third segment message may be equal to the remaining bytes (e.g., 20K bytes-9K bytes-9K bytes=2K bytes).

[0116] Reference again Figure 4 As an example, it can be appreciated that message segmentation may enable UE 404 to provide a larger amount of information via an uplink control message. For example, when encoding UE capability information message 432, UE 404 may no longer be constrained by the packet size limit for one packet.

[0117] However, as described above, in some scenarios, employing message segmentation may result in reduced communication performance. For example, if UE 404 does not receive an ACK message from network entity 402, UE 404 may resend one or more of segmented messages 442. In other examples, the network may not be able to process the message segmentation and send a connection release message that releases a connection (e.g., an RRC connection) between network entity 402 and UE 404. In such a scenario, UE 404 may stop sending segmented messages 442, and network entity 402 may not be able to determine the radio capabilities of UE 404.

[0118] Figure 6An example communication flow 600 between a network entity 602 and a UE 604 as presented herein is illustrated. One or more aspects described with respect to the network entity 602 may be performed by a component of a base station or components of a base station such as a CU, DU, and / or RU. Aspects of the network entity 602 are performed by Figure 1 Base station 102 and / or Figure 3 Various aspects of UE 604 may be implemented by Figure 1 UE 104 and / or Figure 3 UE 350. Figure 6 Not shown in the illustrated example, but in additional or alternative examples, the network entity 602 and / or the UE 604 may communicate with one or more other base stations or UEs.

[0119] exist Figure 6 In the illustrated example, the communication flow 600 facilitates the UE 604 to determine whether to skip applying message segmentation to an uplink control message even when message segmentation is permitted.

[0120] like Figure 6 As shown, the network entity 602 outputs a capability query message 610 that is received by the UE 604. The network entity 602 also outputs a segmentation indicator 612 that is received by the UE 604. The segmentation indicator 612 may indicate whether segmentation is disabled or enabled for the uplink control message associated with the capability query message 610. Aspects of the capability query message 610 may be similar to Figure 4 The capability query message 412. Various aspects of the segment indicator 612 may be similar to Figure 4 The segment indicator 414 is shown.

[0121] After receiving the capability query message 610 and the segmentation indicator 612, the UE 604 may perform a generation process 614 to generate UE capability information 616 in response to the capability query message 610. The amount of uplink control information that the UE 604 may encode in the UE capability information 616 may not be limited by the packet size limit.

[0122] exist Figure 6 In the illustrated example, the UE 604 may perform a determination process 618 to determine whether to apply segmentation based on at least one of a channel condition or a count of connection releases from the network. The UE 604 may perform the determination process 618 even when segmentation is permitted (e.g., the segmentation indicator 612 indicates that segmentation is enabled and the size of the UE capability information 616 is greater than the packet size limit).

[0123] In some examples, UE 604 may determine to skip application segmentation based on channel conditions. For example, UE 604 may determine that channel conditions are poor and therefore determine to skip application segmentation. In some examples, UE 604 may determine to perform segmentation based on channel conditions. For example, UE 604 may determine that channel conditions are not poor. Figure 7 , Figure 8 and Fig. 9 Various aspects of determining whether to perform segmentation based on channel conditions are described with examples.

[0124] In some examples, UE 604 may determine to skip application segmentation based on a count of connection releases from the network (e.g., via determination process 618). For example, UE 604 may determine that a count of connection releases maintained by UE 604 is greater than a threshold, and therefore determine to skip application segmentation. In other examples, UE 604 may determine to perform segmentation based on a count of connection releases. For example, UE 604 may determine that a count of connection releases maintained by UE 604 is less than or equal to a threshold. In combination Fig.10 , Fig.11 , Fig.12 , Fig.13 and Fig.14 Various aspects of determining whether to perform segmentation based on a count of connection releases from a network are described with examples.

[0125] In an example where the UE 604 determines to skip application segmentation, the UE 604 may send a UE capability information message 620 obtained by the network entity 602. In some examples, the UE 604 may determine to skip application segmentation when channel conditions are poor. Additionally or alternatively, the UE 604 may determine to skip application segmentation when a count of connection releases is greater than a threshold.

[0126] The UE capability information message 620 may be based on the UE capability information 616, but may include a reduced amount of information so that the size of the UE capability information message 620 is less than or equal to the packet size limit. In some examples, the UE 604 may perform a reduction process to reduce the size of the UE capability information 616 so that the size of the UE capability information message 620 meets the packet size limit.

[0127] In an example where the UE 604 determines application segmentation (e.g., via the determination process 618), the UE 604 may send the UE capability information 616 via two or more segmentation messages 622 obtained by the network entity 602. For example, when the channel condition is not bad, the UE 604 may determine the application segmentation. The UE 604 may additionally or alternatively determine the application segmentation when the count of connection releases from the network is less than or equal to a threshold.

[0128] In some examples, even when message segmentation is permitted, the UE may evaluate the channel conditions of the serving cell and determine to send the uplink control message without segmentation. That is, the size of the uplink control message may not meet the packet size limit (e.g., the size of the uplink control message is greater than the packet size limit), but the UE may determine to send the uplink control message without segmentation based on the channel conditions. For example, when the UE determines that the channel conditions are poor, the UE may send the uplink control message without segmentation. However, when the UE determines that the channel conditions are not poor, the UE may send the uplink control message with segmentation.

[0129] In some examples, the UE may determine channel conditions based on measurements associated with reference signal received power (RSRP), path loss, and / or signal-to-noise ratio (SNR). In some examples, the UE may determine that the channel condition is poor when the average RSRP is less than an RSRP threshold. In some examples, the UE may determine that the channel condition is poor when the average path loss is greater than a path loss threshold. In some examples, the UE may determine that the channel condition is poor when the average SNR is less than an SNR threshold. In some examples, the UE may determine that the channel condition is poor when at least two of the average RSRP, average path loss, and average SNR fail to meet their respective thresholds.

[0130] In an example where the UE determines that the channel condition is poor, the UE may determine to send the uplink control message without segmentation. For example, the UE may reduce the size of the uplink control message so that it meets the packet size limit. In some examples, the UE may re-encode the uplink control message so that the packet size limit is met. For example, the UE may be configured to encode a minimum amount of uplink control information when generating the uplink control message. The minimum amount of uplink control information may correspond to an uplink control message having a size less than or equal to the packet size limit.

[0131] Figure 7 Included is pseudo code 700 that can facilitate a UE to determine whether to employ message segmentation for an uplink control message based on serving cell conditions, as presented herein. Figure 7 The example pseudo-code 700 of may enable the UE to skip performing message segmentation even when message segmentation is permitted (e.g., based on the size of the uplink control message). Figure 7 In the example of , the pseudo code 700 includes a first pseudo code portion 710 to determine whether to send an uplink control message with segmentation or to send an uplink control message without segmentation. Figure 7As shown, the first pseudo-code section 710 includes a first test 712 to determine whether message segmentation is permitted based on the size of the uplink control message. For example, the UE may compare the size of the uplink control message ("msg_size") with the packet size limit ("pdcp_sdu_max_size"). If the result of the first test 712 is true (e.g., "msg_size > pdcp_sdu_max_size"), the UE may determine that message segmentation is permitted based on the size of the uplink control message.

[0132] The first pseudo-code section 710 includes a second test 714 to determine whether the serving cell condition is poor. The UE may determine the serving cell condition based on the second pseudo-code section 720 and the third pseudo-code section 730. As Figure 7 shown in the example, the second pseudo-code section 720 includes three example channel condition tests related to RSRP, path loss, and SNR. Then, the UE may determine the serving cell condition based on the results of the channel condition tests, as illustrated in the third pseudo-code section 730.

[0133] For example, in the first channel condition test 722 of the second pseudo-code section 720, the UE compares the average RSRP value with the RSRP threshold ("OEM_Thres_RSRP"). When the average RSRP value is less than the RSRP threshold ("RSRP avg < OEM_Thres_RSRP"), the UE may determine that the result of the first channel condition test 722 is true. Otherwise, the UE may determine that the result of the first channel condition test 722 is false.

[0134] In the second channel condition test 724 of the second pseudo-code section 720, the UE compares the average path loss value with the path loss threshold ("OEM_Thres_Pathloss"). When the average path loss value is greater than the path loss threshold (e.g., "Pathloss avg > OEM_Thres_Pathloss"), the UE may determine that the result of the second channel condition test 724 is true. Otherwise, the UE may determine that the result of the second channel condition test 724 is false.

[0135] In the third channel condition test 726 of the second pseudo-code section 720, the UE compares the average SNR value with the SNR threshold ("OEM_Thres_SNR"). When the average SNR value is less than the SNR threshold (e.g., "SNR avg < OEM_Thres_SNR"), the UE may determine that the result of the third channel condition test 726 is true. Otherwise, the UE may determine that the result of the third channel condition test 726 is false.

[0136] As shown in the third pseudo-code portion 730, the UE may set the value of the poor condition indicator 732 ("Srv_cell_Poor") based on the results of the corresponding channel condition test. Figure 7 In the illustrated example, when the result of the first channel condition test 722 is true, the result of the second channel condition test 724 is true, and the result of the third channel condition test 726 is true (e.g., "condition (1&2&3)"), the UE may set the value of the poor condition indicator 732 to a first value indicating that the serving cell condition is poor ("Srv_cell_Poor = TRUE"). Otherwise, the UE may set the value of the poor condition indicator 732 to a second value indicating that the serving cell condition is not poor ("Srv_cell_Poor = FALSE").

[0137] although Figure 7 The example third pseudo-code portion 730 uses the results of three example channel condition tests to determine the value of the bad condition indicator 732, but in other examples, the number of channel condition tests applied by the UE when setting the value of the bad condition indicator 732 may be different. Additionally, although Figure 7 The example third pseudocode portion 730 indicates that the UE sets the value of the bad condition indicator 732 to the first value ("TRUE") when the result of each of the three example channel condition tests is true, but in other examples, the UE may set the value of the bad condition indicator 732 to the first value ("TRUE") when the results of less than three example channel condition tests are true. For example, when the result of at least one of the three example channel condition tests is true, the UE may set the value of the bad condition indicator 732 to the first value ("TRUE"). In other examples, when the results of at least two of the three example channel condition tests are true, the UE may set the value of the bad condition indicator 732 to the first value ("TRUE"). In some examples, the channel condition tests may be weighted so that if the result of a particular channel condition test is true, the UE may set the value of the bad condition indicator 732 to the first value ("TRUE") based on the result of one channel condition test. However, if the result for a particular channel condition is false, then the UE may set the value of the poor condition indicator 732 to a first value ("TRUE") if the results of the other two channel condition tests are true.

[0138] Reference again Figure 7 In the first pseudo-code portion 710, the UE may apply a second test 714 to determine whether the serving cell condition is not bad. Figure 7In the example of , the result of the second test 714 may be based on the value of the bad condition indicator 732. For example, when the value of the bad condition indicator 732 is set to the second value ("FALSE"), the result of the second test 714 may be true (e.g., indicating that the serving cell condition is not bad). Figure 7 In the example of , when the value of the poor condition indicator 732 is false (e.g., "Srv_cell_Poor == FALSE"), the result of the second test 714 is true. Otherwise, when the value of the poor condition indicator 732 is set to the first value ("TRUE"), the UE may determine that the result of the second test 714 is false (e.g., indicating that the serving cell condition is poor).

[0139] like Figure 7 As shown in the example of , when the results of the first test 712 and the second test 714 are both true, the UE may determine to use message segmentation ("allow RRC segment") for the uplink control message and, for example, send the uplink control message with a segmented message via a "ULDedicatedMessageSegment" message. Additionally, if the result of at least one of the first test 712 and the second test 714 is false, the UE may determine to send the uplink control message without segmentation (e.g., "use legacy method"). For example, the UE may send the uplink control message via a "UECapabilityInformation" message. As described above, when the UE determines to send an uplink control message without segmentation, the UE sends a single message (e.g., an uplink control message), and the size of the uplink control message is configured to meet the packet size limit. For example, the UE may encode the amount of uplink control information in the uplink control message so that the size of the uplink control message is less than or equal to the maximum PDCP SDU size.

[0140] exist Figure 7In the example pseudocode 700 of , the "msg_size" variable represents the encoded size of the uplink control message. The value of the msg_size variable can be represented in bytes and can be determined by the UE after generating the uplink control message. The "pdcp_sdu_max_size" variable represents the maximum allowed size of the PDCP SDU. In some examples, the value of the pdcp_sdu_max_size variable can be known to the UE and / or can be assigned by the standard administration. For example, the UE can be pre-configured with the value of the pdcp_sdu_max_size variable. In other examples, the value of the pdcp_sdu_max_size variable can be configured and / or activated by the network at the UE, such as via DCI, MAC control element (MAC-CE) and / or RRC signaling.

[0141] exist Figure 7 In the second pseudo-code portion 720, the UE may determine an average RSRP value ("RSRP avg") based on one or more RSRP measurements. Similarly, the UE may determine an average path loss value ("Pathloss avg") based on one or more path loss measurements, and determine an average SNR value ("SNR avg") based on one or more SNR measurements.

[0142] exist Figure 7 In an example of a channel condition test, an RSRP threshold ("OEM_Thres_RSRP"), a path loss threshold ("OEM_Thres_Pathloss"), and an SNR threshold ("OEM_Thres_SNR") may be used to determine whether the result of a corresponding channel condition test is true or false. In some aspects, the values ​​of the corresponding thresholds may be known to the UE. For example, an original equipment manufacturer (OEM) may configure the values ​​of the corresponding thresholds at the UE. In some examples, the corresponding values ​​of one or more thresholds may be updated. For example, the OEM may provide a firmware update that is applied by the UE. In some such examples, the firmware update may update the corresponding values ​​of the RSRP threshold, the path loss threshold, and / or the SNR threshold at the UE.

[0143] Figure 8 An example communication flow 800 between a network entity 802 and a UE 804 as presented herein is illustrated. One or more aspects described with respect to the network entity 802 may be performed by a component of a base station or a component of a base station such as a CU, DU, and / or RU. Figure 8 As shown, UE 804 is in RRC connected mode with network entity 802, for example. Figure 4 Various aspects of UE 804 may be implemented by the network entity 402. Figure 4 UE 404 is implemented. Figure 8Not shown in the illustrated example, but in additional or alternative examples, the network entity 802 and / or the UE 804 may communicate with one or more other base stations or UEs.

[0144] exist Figure 8 In the illustrated example, communication flow 800 may facilitate Figure 7 For example, the communication process 800 may facilitate the UE 804 to determine whether to employ message segmentation based on the channel conditions of the serving cell (e.g., the network entity 802). For example, the UE 804 may evaluate the signal conditions of the serving cell based on one or more of RSRP, path loss, and SNR, such as in combination with Figure 7 804 may then determine whether to employ message segmentation based in part on the serving cell conditions, such as in conjunction with Figure 7 The first pseudo code portion 710 is described.

[0145] like Figure 8 As shown, the network entity 802 may send a capability query message 810 that is received by the UE 804. The capability query message 810 may include a segmentation indicator 812 ("RRC-SegAllowed-r16 enabled") that indicates that message segmentation is enabled for an uplink control message generated by the UE 804 in response to the capability query message 810. The UE 804 may then generate an uplink control message. For example, the UE 804 may perform an encoding process 820 to generate UE capability information based on the capability query message 810.

[0146] like Figure 8 As shown, UE 804 may send UE capability information with segmentation (e.g., via segmented message 840), or may send UE capability information as a single message (e.g., as UE capability information message 844 without segmentation). For example, UE 804 may perform process 830 to determine whether to employ message segmentation for UE capability information. Aspects of process 830 may correspond to Figure 7 The first test 712 and the second test 714 of the process 830 may be performed. For example, the process 830 includes two tests. The first test 832 may facilitate determining whether to allow message segmentation based on the size of the UE capability information. For example, the UE 804 may compare the size of the UE capability information with the packet size limit. Figure 7 As described in the first test 712, the size of the UE capability information may be represented by a "msg_size" variable, and the packet size limit may be represented by a "pdcp_sdu_max_size" variable.

[0147] In examples where the size of the UE capability information is less than or equal to the packet size limit, the UE 804 may determine that the result of the first test 832 is false and message fragmentation is not permitted based on the size of the UE capability information. In some such examples, the UE 804 may determine to send the UE capability information via a non-segmented message, such as the UE capability information message 844 (e.g., via a “UECapabilityInformation” message).

[0148] like Figure 8 As shown, process 830 includes a second test 834. The second test 834 can facilitate determining whether the serving cell condition is bad or not bad. Figure 8 In the example of , the result of the second test 834 can be based on the value of the poor condition indicator ("Srv_cell_Poor"). Figure 7 As described in the second test 714, the value of the poor condition indicator may be set based on channel condition tests associated with RSRP (e.g., the first channel condition test 722), path loss (e.g., the second channel condition test 724), and / or SNR (e.g., the third channel condition test 726).

[0149] In examples where the value of the poor condition indicator is set to a value indicating that the serving cell condition is poor (e.g., a value of "TRUE"), the UE 804 may determine that the result of the second test 834 is false and determine not to employ message segmentation even if message segmentation is permitted (e.g., the result of the first test 832 is true). In some such examples, the UE 804 may determine to send the UE capability information via a non-segmented message, such as a UE capability information message 844 (e.g., via a "UECapabilityInformation" message).

[0150] Therefore, in Figure 8 In the example of , when message segmentation is permitted based on the size of the UE capability information (e.g., the result of the first test 832 is true) and the serving cell condition is not bad (e.g., the result of the second test 834 is true), the UE 804 may adopt message segmentation of the UE capability information. That is, Figure 8 The example techniques may enable UE 804 to avoid message segmentation when serving cell conditions are poor even when message segmentation is permitted based on the size of UE capability information, which may improve communication performance by reducing overhead associated with uplink transmissions and / or reducing the likelihood of connection drops due to missed downlink signaling (such as acknowledgment messages) from network entity 802.

[0151] In some examples, UE 804 may determine to allow message segmentation based on the size of the UE capability information (e.g., the result of the first test 832 is true), but may also determine not to use message segmentation based on poor serving cell conditions (e.g., the result of the second test 834 is false). In some such examples, UE 804 may perform a reduction process 842 to reduce the size of the UE capability information so that the size of the UE capability information is less than or equal to the packet size limit. For example, UE 804 may generate new UE capability information in view of the packet size limit, such as in combination with Figure 4 The generation process 422 is described.

[0152] In some examples, after determining not to employ message segmentation based on poor serving cell conditions even when message segmentation is permitted, the UE may continue to skip employing message segmentation until the UE detects the occurrence of an update triggering event. For example, the UE may detect the occurrence of an update triggering event based on an improvement in serving cell conditions. In some examples, the UE may determine not to employ message segmentation based on poor serving cell conditions. Figure 7 The UE may detect an improvement in the serving cell condition by a change in the results of one or more of the channel condition tests of the second pseudo-code portion 720. In some examples, the UE may detect an improvement in the serving cell condition after performing a mobility procedure to another serving cell.

[0153] After detecting the occurrence of an update triggering event, the UE may resynchronize its radio capabilities with the network. For example, the UE may send an update message received by the network. In some such examples, the update message may cause the network to output another capability query message, which is received by the UE and enables the UE to provide its radio capabilities to the network. It is understood that before the UE detects the occurrence of an update triggering event, the amount of uplink control information that the UE can encode in the UE capability information message may be limited by the packet size limit. In such scenarios, in order to meet the packet size limit, the UE may be limited in its ability to express its radio capabilities. However, by resynchronizing its radio capabilities with the network after detecting an improvement in the serving cell conditions, the UE may have the ability to provide a larger amount of uplink control information because when generating new UE capability information, the UE may no longer be constrained by the packet size limit for one packet.

[0154] Fig. 9 An example communication flow 900 between a network entity 902 and a UE 904 as presented herein is illustrated. Aspects of the network entity 902 are Figure 4 The network entity 402 and / or Figure 8 The various aspects of UE 904 may be implemented by the network entity 802. Figure 4 UE 404 and / or Figure 8 UE 804. Fig. 9 Not shown in the illustrated example, but in additional or alternative examples, the network entity 902 and / or the UE 904 may communicate with one or more other base stations or UEs.

[0155] exist Fig. 9 In the example of , UE 904 may be configured to send an uplink control message (eg, UE capability information message) without segmentation based on determining that the serving cell condition is poor, such as in combination with Figure 8 The second test 834 and the sending of the UE capability information message 844 without segmentation are described. Fig. 9 In the illustrated example, communication flow 900 may facilitate UE 904 to perform capability resynchronization with network entity 902 based on the occurrence of an update triggering event. In some such scenarios, UE 904 may have the ability to provide a larger amount of uplink control information to network entity 902 because UE 904 may no longer be constrained by the packet size limit for one packet when a new UE capability information message is generated.

[0156] like Fig. 9 As shown, network entity 902 may output a capability query message 910 that is received by UE 904. Capability query message 910 may include a segmentation indicator 912 that indicates that message segmentation is enabled for an uplink control message generated by UE 904 in response to capability query message 910. Aspects of capability query message 910 may be similar to capability query message 412 and / or capability query message 810. Aspects of segmentation indicator 912 may be similar to segmentation indicator 414 and / or segmentation indicator 812.

[0157] The UE 904 may then generate an uplink control message. For example, the UE 904 may perform a generation process 920 to generate a first UE capability information message 922 for transmission without segmentation. For example, the UE 904 may limit the amount of uplink control information encoded in the first UE capability information message 922 so that the size of the first UE capability information message 922 is less than or equal to the packet size limit. Fig. 9 In the illustrated example of , the UE 904 generates a first UE capability information message 922 for transmission without segmentation based on channel conditions (e.g., poor serving cell conditions). The UE 904 may then transmit the first UE capability information message 922 that is received by the network entity 902. The UE 904 may transmit the first UE capability information message 922 without segmentation. For example, the UE 904 may transmit the first UE capability information message 922 via a “UECapabilityInformation” message.

[0158] exist Fig. 9In the illustrated example of , UE 904 performs monitoring process 930 to monitor for the occurrence of an update triggering event. For example, at 932, UE 904 may detect an improvement in serving cell conditions. In some examples, UE 904 may Figure 7 The UE 904 may detect an improvement in the serving cell condition by a change in the results of one or more of the channel condition tests included in the second pseudo-code portion 720. In some examples, the UE 904 may detect an improvement in the serving cell condition after performing a mobility procedure to another serving cell.

[0159] like Fig. 9 As shown, UE 904 may send an update message 934 obtained by network entity 902. Update message 934 may inform network entity 902 that UE 904 wants to resynchronize its capabilities with the network. For example, based on update message 934, network entity 902 and UE 904 may perform a capability resynchronization process 936. For example, network entity 902 may output a capability query message 938 in response to update message 934. Capability query message 938 may include a segmentation indicator 940 indicating that message segmentation is enabled. Aspects of capability query message 938 and segmentation indicator 940 may be similar to capability query message 910 and segmentation indicator 912, respectively.

[0160] exist Fig. 9 In the illustrated example of , UE 904 performs generation process 950 to generate a second UE capability information message 952. UE 904 may generate second UE capability information message 952 in response to capability query message 938. UE 904 may generate second UE capability information message 952 without being constrained by a packet size limit for one packet. In some such examples, the amount of uplink control information that UE 904 may encode in second UE capability information message 952 may be greater than the amount of uplink control information that UE 904 may encode in first UE capability information message 922. In some scenarios, UE 904 may be able to provide additional capability information that UE 904 was not previously able to provide. UE 904 may then send second UE capability information message 952 via segmented message 954 obtained by network entity 902. Aspects of segmented message 954 may be similar to Figure 4 Segmented message 442 and / or Figure 8 Segmented message 840.

[0161] As described above, in some aspects, the network may not be able to process message segmentation and / or may not be configured to receive uplink control messages in the case of segmentation. In some such examples, the network may be configured to send a connection release message when it receives an uplink control message (e.g., UE capability information message) in the case of segmentation. For example, in response to receiving a segmentation of a UE capability information message, the network may send a connection release message. In some aspects, the network may maintain a timer associated with receiving a UE capability information message in the case of segmentation. In some such examples, if the UE takes too long to transmit the UE capability information message in the case of segmentation, the network may send a connection release message. For example, if the network does not receive all segments of the UE capability information message before the timer expires, the network may send a connection release message. In some such scenarios, the UE may stop transmitting the remaining segments of the uplink control message after receiving the connection release message. Therefore, the UE may not provide the network with information encoded in the uplink control message. Additionally, based on the network not receiving information encoded in the uplink control message, the network may not provide certain communication services to the UE.

[0162] In some aspects, even when message segmentation is permitted, the UE may be configured to determine whether to employ message segmentation based on an assessment of the network and its ability to handle message segmentation. In aspects disclosed herein, the UE may maintain a count of connection release messages received from the network while attempting to send an uplink control message with segmentation. In some such examples, when the count of connection release messages is greater than a release threshold, the UE may determine to skip using message segmentation even when message segmentation is permitted (e.g., based on the size of the uplink control message).

[0163] For example, before generating an uplink control message, the UE may compare its count of connection release messages with a release threshold. In an example where the count of connection release messages is less than or equal to the release threshold, the UE may generate the uplink control message without being constrained by the packet size limit for one packet. The UE may then send the uplink control message with or without segmentation based on the size of the uplink control message. In an example where the count of connection release messages is greater than the release threshold, the UE may then generate the uplink control message by limiting the amount of uplink control information encoded in the uplink control message based on the size of the uplink control message.

[0164] In some examples, when the UE receives a connection release message immediately after sending an uplink control message with segmentation, the UE may increase the count of the connection release message. For example, the UE may initiate a timer when sending a segmentation message (e.g., a segmentation of an uplink control message), and maintain the timer until the sending of the uplink control message with segmentation is completed or the connection release message is received. In an example in which the UE receives a connection release message while the timer is active, the UE may increment the count of the connection release message. In some examples, when the UE is able to send an uplink control message with segmentation without receiving a connection release message from the network, the UE may reset the count of the connection release message. In other examples, if the UE receives a connection release message when the timer is inactive (e.g., when no attempt is made to send a segmentation message), the UE may determine that the network sending the connection release message has nothing to do with the ability of the network to process message segmentation. In such examples, the UE may skip incrementing the count of the connection release message.

[0165] In some examples, if the UE completes sending an uplink control message with segmentation before receiving a connection release message, the UE may determine that the network is capable of receiving the uplink control message with segmentation and therefore continue to use message segmentation when permitted (e.g., when message segmentation is enabled and the size of the UE capability information message fails to meet the packet size limit).

[0166] Fig.10 Included is pseudo code 1000 that can facilitate a UE to determine whether to employ message segmentation for an uplink control message based on network behavior causing the network to output an immediate connection release message as presented herein. Fig.10 The example pseudo code 1000 of can enable the UE to evaluate the network behavior and the ability of the network to support uplink control messages in the case of segmentation. For example, the network can be configured to send a connection release message when it receives a segmentation message or when a timer associated with receiving an uplink control message in the case of segmentation expires.

[0167] exist Fig.10In the example of , the pseudocode 1000 includes a first pseudocode portion 1010 and a second pseudocode portion 1020 that enable the UE to send an uplink control message with segmentation or without segmentation. For example, the first pseudocode portion 1010 includes a first test 1012 to determine whether message segmentation is permitted based on the size of the uplink control message. For example, the UE may compare the size of the uplink control message ("msg_size") with the packet size limit ("pdcp_sdu_max_size"). If the result of the first test 1012 is true (e.g., "msg_size>pdcp_sdu_max_size"), the UE may determine that message segmentation is permitted based on the size of the uplink control message. Otherwise, the UE may determine that the result of the first test 1012 is false. Aspects of the first test 1012 may be similar to Figure 7 The first test 712.

[0168] like Fig.10 As shown, the first pseudo-code portion 1010 includes a second test 1014 to determine whether the count of connection release messages meets a release threshold ("OEM_rel_thresh"). For example, the UE may maintain a connection release counter 1016 ("RRC_seg_release_counter") that indicates the count of connection release messages received by the UE when attempting to send an uplink control message with segmentation. Fig.10 In the example of , when the value of the connection release counter 1016 is less than or equal to the release threshold ("RRC_seg_release_counter<=OEM_rel_thresh"), the UE may determine that the output of the second test 1014 is true. Otherwise, the UE may determine that the output of the second test 1014 is false (e.g., when the value of the connection release counter 1016 is greater than the release threshold).

[0169] exist Fig.10 In the example of , a release threshold ("OEM_rel_thresh") is a parameter having a value that ensures that the UE observes a minimum number of immediate connection releases from the network. In some examples, the value of the release threshold may be known to the UE. For example, the OEM may configure the value of the release threshold at the UE. In some examples, the value of the release threshold may be updated. For example, the OEM may provide a firmware update that is applied by the UE. In some such examples, the firmware update may update the value of the release threshold.

[0170] exist Fig.10In the illustrated example of , if the output of at least one of the first test 1012 and the second test 1014 is false, the UE may determine to send an uplink control message without segmentation (e.g., "use legacy method"), as indicated by the second pseudo-code portion 1020. For example, the UE may send the uplink control message via a "UECapabilityInformation" message. As described above, when the UE determines to send an uplink control message without segmentation, the UE sends a single message (e.g., an uplink control message), and the size of the uplink control message is configured to meet the packet size limit. For example, the UE may encode the amount of uplink control information in the uplink control message so that the size of the uplink control message is less than or equal to the maximum PDCP SDU size.

[0171] Referring again to the example first pseudocode portion 1010, if the outputs of the first test 1012 and the second test 1014 are both true, the UE may determine to use message segmentation ("allow RRC segment") for the uplink control message, and send the uplink control message with a segmented message, for example via a "ULDedicatedMessageSegment" message.

[0172] exist Fig.10 In the example of , after sending the segmented message ("send it through ULDedicatedMessageSegment"), the UE may execute a third pseudo-code portion 1030 configured to manage the count of the connection release counter 1016. For example, the UE may start a timer 1032 ("T_window"). The timer 1032 may be set to a value that enables the UE to determine whether the connection release message is immediate. That is, if the UE receives a connection release message while the timer 1032 is active, the UE may determine that the connection release message is "immediate". Otherwise, the UE may determine that the connection release message is not immediate.

[0173] In some examples, the duration of timer 1032 may be known to the UE and / or may be assigned by a standard administration authority. For example, the UE may be pre-configured with the duration of timer 1032. In other examples, the duration of timer 1032 may be configured and / or activated by the network at the UE, such as via DCI, MAC-CE, and / or RRC signaling.

[0174] like Fig.10As shown, if the UE receives a connection release message ("NW sendconnection release immediately within T_window time") while timer 1032 is active, the UE increments the value of the connection release counter 1016 ("RRC_seg_release_counter++"). However, if the UE does not receive a connection release while timer 1032 is active, and therefore the UE successfully sends an uplink control message with segmentation, the UE may reset the count of connection releases from the network ("Reset "RRC_seg_release_counter"). The UE may also reset timer 1032 ("reset T_window").

[0175] Fig.11 An example communication flow 1100 between a network entity 1102 and a UE 1104 as presented herein is illustrated. One or more aspects described with respect to the network entity 1102 may be performed by a component of a base station or a component of a base station such as a CU, DU, and / or RU. Fig.11 As shown, UE 1104 is in RRC connected mode with network entity 1102, for example. Figure 4 402. Various aspects of UE 1104 may be implemented by Figure 4 UE 404 is implemented. Fig.11 Not shown in the illustrated example, but in additional or alternative examples, the network entity 1102 and / or the UE 1104 may communicate with one or more other base stations or UEs.

[0176] exist Fig.11 In the illustrated example, the communication process 1100 may facilitate Fig.10 For example, the communication process 1100 may facilitate the UE 1104 to determine whether to employ message segmentation based on network behavior. For example, the UE 1104 may maintain a count of connection release messages received in response to uplink control messages with segmentation, such as in conjunction with Fig.10 Then, the UE may determine whether to use message segmentation based in part on the count of the connection release message, such as in combination with Fig.10 The first pseudo code portion 1010 is described.

[0177] like Fig.11As shown, the network entity 1102 may send a capability query message 1110 that is received by the UE 1104. The capability query message 1110 may include a segmentation indicator 1112 ("RRC-SegAllowed-r16 enabled") that indicates that message segmentation is enabled for an uplink control message generated by the UE 1104 in response to the capability query message 1110. The UE 1104 may then generate an uplink control message. For example, the UE 1104 may perform an encoding process 1120 to generate UE capability information based on the capability query message 1110.

[0178] like Fig.11 As shown, UE 1104 may send UE capability information with segmentation (e.g., via segmented message 1136), or may send UE capability information as a single message (e.g., as UE capability information message 1150 without segmentation). For example, UE 1104 may perform process 1130 to determine whether to employ message segmentation for UE capability information. Aspects of process 1130 may correspond to Fig.10 The first test 1012 and the second test 1014 of the process 1130 may be performed. For example, the process 1130 includes two tests. The first test 1132 may facilitate determining whether to allow message segmentation based on the size of the UE capability information. For example, the UE 1104 may compare the size of the UE capability information with the packet size limit. Fig.10 As described in the first test 1012, the size of the UE capability information may be represented by a "msg_size" variable, and the packet size limit may be represented by a "pdcp_sdu_max_size" variable.

[0179] In examples where the size of the UE capability information is less than or equal to the packet size limit, the UE 1104 may determine that the result of the first test 1132 is false and message segmentation is not permitted based on the size of the UE capability information. In some such examples, the UE 1104 may determine to send the UE capability information via a non-segmented message, such as the UE capability information message 1150 (e.g., via a “UECapabilityInformation” message).

[0180] like Fig.11 As shown, process 1130 includes a second test 1134. The second test 1134 may facilitate determining whether a threshold number of connection release messages have been released. For example, the value of the release threshold ("OEM_rel_thresh") may be configured such that the UE receives multiple immediate connection release messages from the network. Fig.10As described in the second test 1014 , the result of the second test 1134 may be true when the connection release counter (“RRC_seg_release_counter”) is less than or equal to the release threshold (“RRC_seg_release_counter<=OEM_rel_thresh”).

[0181] In examples where the value of the connection release counter is greater than the release threshold, the UE 1104 may determine that the result of the second test 1134 is false and determine not to employ message segmentation even if message segmentation is permitted (e.g., the result of the first test 1132 is true). In some such examples, the UE 1104 may determine to send the UE capability information via a non-segmented message, such as a UE capability information message 1150 (e.g., via a “UECapabilityInformation” message).

[0182] exist Fig.11 In the illustrated example of , if the results of the first test 1132 and the second test 1134 are both true, the UE may continue to transmit UE capability information via a segmented message 1136 ("ULDedicatedMessageSegment") with segmentation. Fig.11 As shown in , after sending the fragmentation message, the UE 1104 may initiate a timer 1140. The duration of the timer 1140 may be configured to enable the UE 1104 to determine whether the connection release message is in response to the fragmentation message (eg, an "immediate" connection release message).

[0183] Then, UE 1104 may monitor for connection release messages from the network (e.g., network entity 1102). For example, UE 1104 may perform process 1144 to determine whether a connection release message is received while timer 1140 is active. If UE 1104 determines that a connection release message is not received while timer 1140 is active, UE 1104 may perform reset process 1146 and reset the value of the connection release counter and reset timer 1140, as in combination with Fig.10 1030. If UE 1104 determines that a connection release message is received while timer 1140 is active, UE 1104 may perform an incrementing process 1148 to increment a connection release counter ("RRC_seg_release_counter++"). For example, network entity 1102 may output a connection release message 1142 received by UE 1104. If UE 1104 receives a connection release message 1142 while timer 1140 is active, UE 1104 performs an incrementing process 1148 and increments the connection release counter by, for example, one.

[0184] Therefore, in Fig.11 In the example of , when message segmentation is permitted based on the size of the UE capability information (e.g., the result of the first test 1132 is true) and the evaluation of the network behavior (e.g., the result of the second test 1134 is true), the UE 1104 may adopt message segmentation of the UE capability information. That is, Fig.11 Example techniques of may enable UE 1104 to avoid message segmentation when network behavior indicates that the network cannot process and / or is not configured to receive uplink control messages with segmentation. In examples where the UE avoids message segmentation based on a count of connection release messages, the UE may be able to improve communication performance by maintaining a connection with the network. For example, if the network performs an immediate connection release after the UE sends a segmentation message, the UE may have the ability to determine that the network cannot process message segmentation based on a count of connection release messages. In such examples, the UE may skip message segmentation when communicating with the network to maintain a connection with the network.

[0185] Fig.12 An example communication flow 1200 between a network entity 1202 and a UE 1204 as presented herein is illustrated. Aspects of the network entity 1202 are Figure 4 The network entity 402 and / or Fig.11 1102. Various aspects of UE 1204 may be implemented by Figure 4 UE 404 and / or Fig.11 UE 1104. Fig.12 Not shown in the illustrated example, but in additional or alternative examples, the network entity 1202 and / or the UE 1204 may communicate with one or more other base stations or UEs.

[0186] exist Fig.12 In the example of , UE 1204 may be configured to send uplink control messages (e.g., UE capability information messages) without segmentation based on network behavior, such as in conjunction with Fig.11 The second test 1134 and sending the UE capability information message 1150 without segmentation are described.

[0187] like Fig.12 As shown, network entity 1202 may output a capability query message 1210 that is received by UE 1204. Capability query message 1210 may include a segmentation indicator 1212 that indicates that message segmentation is enabled for an uplink control message generated by UE 1204 in response to capability query message 1210. Aspects of capability query message 1210 may be similar to capability query message 412 and / or capability query message 1110. Aspects of segmentation indicator 1212 may be similar to segmentation indicator 414 and / or segmentation indicator 1112.

[0188] The UE may then perform process 1214 to determine whether the connection release counter meets the release threshold, such as in conjunction with Fig.11 1234. If the value of the connection release counter is greater than the release threshold (e.g., "RRC_seg_release_counter>OEM_rel_thresh"), the UE 1204 may generate an uplink control message. For example, the UE 1204 may perform a generation process 1234 to generate a UE capability information message 1236 for transmission without segmentation. For example, the UE 1204 may limit the amount of uplink control information encoded in the UE capability information message 1236 so that the size of the UE capability information message 1236 is less than or equal to the packet size limit. Then, the UE 1204 may send the UE capability information message 1236 received by the network entity 1202. The UE 1204 may send the UE capability information message 1236 without segmentation. For example, the UE 1204 may send the UE capability information message 1236 via a "UECapabilityInformation" message.

[0189] Returning to process 1214, if UE 1204 determines that the connection release count is not greater than the release threshold (e.g., "RRC_seg_release_counter<=OEM_rel_thresh"), UE 1204 may perform a generation process 1216 to generate a UE capability information message 1217. UE 1204 may generate UE capability information message 1217 without being constrained by the packet size limit for one packet. In some such examples, the amount of uplink control information that UE 1204 may encode in UE capability information message 1217 may be greater than the amount of uplink control information that UE 1204 may encode in UE capability information message 1236.

[0190] After generating the UE capability information message, the UE 1204 may perform a process 1218 to determine whether message segmentation is permitted and whether the count of connection releases meets a release threshold, such as in conjunction with Fig.11 If the UE 1104 determines that one of the tests is false, the UE 1104 performs a generation process 1234 to generate a new UE capability information message in view of the packet size limit. The UE 1104 may then send the new UE capability information message received by the network entity 1202.

[0191] Returning to process 1218, if UE 1204 determines that both tests are true, such as in combination with Fig.111204 may send a UE capability information message 1217 with segmentation. For example, UE 1204 may send a segmented message 1220 that is received by network entity 1202. Aspects of segmented message 1220 may be similar to Figure 4 Segmented message 442 and / or Fig.11 Segmented message 1136.

[0192] like Fig.12 As shown, after UE 1204 sends segment message 1220, UE 1204 may start timer 1222. Aspects of timer 1222 may be similar to Fig.11 1140. When the timer 1222 is active, the UE 1204 may also initiate a monitoring process 1224 to monitor for connection release messages from the network. For example, when the timer 1222 is active, the network entity 1202 may output a connection release message 1226 received by the UE 1204. In such a scenario, the UE 1204 may perform a stop process 1228 to stop transmitting any remaining segments of the UE capability information message 1217. The UE 1204 may also perform an increment process 1230 to increase the connection release count, such as in conjunction with Fig.11 The UE 1204 may then monitor for another capability query message from the network entity 1202 as described in the incremental process 1148 of FIG.

[0193] In an example where the UE 1204 does not receive a connection release message from the network entity 1202 while performing the monitoring process 1224 (e.g., while the timer 1222 is active), the UE 1204 may perform a reset process 1232. For example, if the UE 1204 successfully sends the UE capability information message 1217 with segmentation while the timer 1222 is active without receiving a connection release message, the UE 1204 may perform the reset process 1232. The UE 1204 may perform the reset process 1232 to reset the connection release count and the timer 1222, as described in conjunction with Fig.11 The UE 1204 may then monitor for another capability query message from the network entity 1202.

[0194] Fig.13 Depicted is a table 1300 illustrating different actions taken by a UE with respect to different instances of a capability query message, as presented herein. Fig.13 In the example of , the UE may be configured with a release threshold of one (1). Thus, the UE may continue to attempt to send uplink control messages with segmentation until the connection release counter reaches two (2). Fig.13 In the example of , the UE capability information has a size large enough so that the UE divides the UE capability information into eight (8) segments.

[0195] like Fig.13 As shown, the UE receives five instances of capability query messages, such as Fig.12 The example table 1300 includes a first column 1302 indicating a count of connection releases (e.g., a value of a connection release counter), a second column 1304 indicating whether the UE uses segmentation or not, and a timer (e.g., Fig.12 A third column 1306 indicates whether a connection release message is received when the timer 1222 of the UE is active, a fourth column 1308 indicates the number of segments sent before receiving the connection release message (if any), and a fifth column 1310 indicates what action the UE performs based on the information indicated by the third column 1306 and the fourth column 1308.

[0196] exist Fig.13 In the example shown, for a first instance 1320 of the capability query message ("Instance 1"), the UE determines that the value of the connection release counter is zero (0) and is less than or equal to the release threshold (1). Therefore, the UE may continue to send the UE capability information with the segments, as shown in the second column 1304. With respect to the first instance 1320, the "yes" in the third column 1306 indicates that the UE received a connection release message from the network while the timer was active, and the entry in the fourth column 1308 indicates that the UE sent four of the eight segments of the UE capability information. As shown in the fifth column 1310 of the first instance 1320, the UE increments the connection release count from "0" to "1" (e.g., as shown in conjunction with the UE's request to release the UE capability information). Fig.12 The UE also stops transmitting the remaining segments (eg, the remaining four segments) of the UE capability information.

[0197] exist Fig.13 In the example shown, for the second instance 1330 of the capability query message ("Instance 2"), the UE determines that the value of the connection release counter is one (1) and is less than or equal to the release threshold (1). Therefore, the UE may continue to send the UE capability information in the presence of segmentation, as shown in the second column 1304. Relative to the second instance 1330, the "No" in the third column 1306 indicates that the UE did not receive a connection release message from the network while the timer was active. Therefore, the UE may successfully complete the sending of the UE capability information in the presence of segmentation (e.g., the UE sends all eight (8) segments of the UE capability information). As shown in the fifth column 1310 of the second instance 1330, the UE resets the connection release count from "1" to "0" (e.g., as shown in conjunction with Fig.12 The reset process 1232 is described).

[0198] exist Fig.13In the illustrated example, for the third instance 1340 ("Instance 3") of the Capability Query message, the UE determines that the value of the Connection Release Counter is zero (0) and is less than or equal to the Release Threshold (1). Therefore, the UE may continue to send the UE capability information with the segments, as shown in the second column 1304. With respect to the third instance 1340, the "yes" in the third column 1306 indicates that the UE received a Connection Release message from the network while the timer was active, and the entry in the fourth column 1308 indicates that the UE sent five of the eight segments of the UE capability information. As shown in the fifth column 1310 of the third instance 1340, the UE increments the Connection Release Counter from "0" to "1" (e.g., as shown in conjunction with the UE's UE Release Counter). Fig.12 The UE also stops transmitting the remaining segments (eg, the remaining three segments) of the UE capability information.

[0199] exist Fig.13 In the illustrated example, for the fourth instance 1350 ("Instance 5") of the Capability Query message, the UE determines that the value of the Connection Release Counter is one (1) and is less than or equal to the Release Threshold (1). Therefore, the UE may continue to send the UE capability information with the segments, as shown in the second column 1304. With respect to the fourth instance 1350, the "yes" in the third column 1306 indicates that the UE received a Connection Release message from the network while the timer was active, and the entry in the fourth column 1308 indicates that the UE sent four of the eight segments of the UE capability information. As shown in the fifth column 1310 of the first instance 1320, the UE increments the Connection Release Counter from "1" to "2" (e.g., as shown in conjunction with the UE's 1304). Fig.12 The UE also stops transmitting the remaining segments (eg, the remaining four segments) of the UE capability information.

[0200] exist Fig.13 In the example shown, for the fifth instance 1360 ("Instance 5") of the Capability Query message, the UE determines that the value of the Connection Release Counter is two (2) and is greater than the Release Threshold (1). Therefore, the UE may determine to send the UE capability information without segmentation, such as in conjunction with Fig.12 1234 and UE capability information message 1236. When the UE sends the UE capability information without segmentation, the UE may skip initiating a timer for determining whether the UE receives a connection release message in response to the segmentation message. Additionally, since the UE sends the UE capability information without segmentation, there are no transmitted segments, as shown in the entry of the fourth column 1308 of the fifth instance 1360.

[0201] exist Fig.13In the example of , after the UE determines to send an uplink control message (e.g., UE capability information) without segmentation based on the connection release counter, the UE may continue to send subsequent uplink control messages without segmentation. For example, for the sixth instance of the capability query message, the value of the connection release counter remains greater than two (2) of the release threshold (1).

[0202] like Fig.13 As shown, after the UE determines to send an uplink control message without segmentation based on the connection release counter, the UE may perform a monitoring process to monitor the occurrence of an update triggering event. In an example in which the UE determines to skip using message segmentation based on the count of the connection release message, the UE may detect the occurrence of the update triggering event based on a change in its connection with the network. For example, the UE may detect the occurrence of the update triggering event in response to a change in at least one of a serving cell, a tracking area, or a serving network node. In some examples, the UE may determine a change in the tracking area based on a change in the TAI and / or a change in the RA.

[0203] Fig.14 An example communication flow 1400 between a network entity 1402 and a UE 1404 as presented herein is illustrated. Aspects of the network entity 1402 are represented by Figure 4 The network entity 402 and / or Fig.11 1402. Various aspects of UE 1404 may be implemented by Figure 4 UE 404 and / or Fig.11 UE 1104. Fig.14 Not shown in the illustrated example, but in additional or alternative examples, the network entity 1402 and / or the UE 1404 may communicate with one or more other base stations or UEs.

[0204] exist Fig.14 In the example of , UE 1404 may be configured to send uplink control messages (eg, UE capability information messages) without segmentation based on an evaluation of network behavior, such as in conjunction with Fig.11 The second test 1134 and sending the UE capability information message 1150 without segmentation are described. Fig.14 In the illustrated example, the communication flow 1400 may facilitate the UE 1404 to perform capability resynchronization with the network entity 1402 based on the occurrence of the update triggering event. In some such scenarios, the UE 1404 may have the ability to provide a larger amount of uplink control information to the network entity 1402 because the UE 1404 may no longer be constrained by the packet size limit for one packet when a new UE capability information message is generated.

[0205] like Fig.14As shown, network entity 1402 may output a capability query message 1410 that is received by UE 1404. Capability query message 1410 may include a segmentation indicator 1412 that indicates that message segmentation is enabled for an uplink control message generated by UE 1404 in response to capability query message 1410. Aspects of capability query message 1410 may be similar to capability query message 412 and / or capability query message 1110. Aspects of segmentation indicator 1412 may be similar to segmentation indicator 414 and / or segmentation indicator 1112.

[0206] The UE 1404 may then generate an uplink control message. For example, the UE 1404 may perform the generation process 1420 to generate a first UE capability information message 1422 for transmission without segmentation. For example, the UE 1404 may limit the amount of uplink control information encoded in the first UE capability information message 1422 so that the size of the first UE capability information message 1422 is less than or equal to the packet size limit. Fig.14 In the illustrated example of , UE 1404 generates a first UE capability information message 1422 for transmission without segmentation based on an evaluation of network behavior. For example, UE 1404 may determine that a count of connection releases (e.g., a connection release counter) is greater than a release threshold. Then, UE 1404 may transmit the first UE capability information message 1422 received by network entity 1402. UE 1404 may transmit the first UE capability information message 1422 without segmentation. For example, UE 1404 may transmit the first UE capability information message 1422 via a "UECapabilityInformation" message.

[0207] exist Fig.14 In the illustrated example of , UE 1404 performs monitoring process 1430 to monitor the occurrence of an update triggering event. For example, at 1432, UE 1404 may detect a serving cell change. In some examples, the UE may detect a serving cell change based on a change in the serving cell. In some examples, the UE may detect a serving cell change based on a change in a tracking area (e.g., a change in TAI and / or a change in RA). In some examples, the UE may detect a serving cell change based on a change in a serving network node. In some examples, the UE may detect a serving cell change after performing a mobility process.

[0208] like Fig.14As shown, UE 1404 may send an update message 1434 obtained by network entity 1402. Update message 1434 may inform network entity 1402 that UE 1404 wants to resynchronize its capabilities with the network. For example, based on update message 1434, network entity 1402 and UE 1404 may perform a capability resynchronization process 1436. For example, network entity 1402 may output a capability query message 1438 in response to update message 1434. Capability query message 1438 may include a segmentation indicator 1440 indicating that message segmentation is enabled. Aspects of capability query message 1438 and segmentation indicator 1440 may be similar to capability query message 1410 and segmentation indicator 1412, respectively.

[0209] exist Fig.14 In the illustrated example of , UE 1404 performs generation process 1450 to generate a second UE capability information message 1452. UE 1404 may generate the second UE capability information message 1452 in response to capability query message 1438. UE 1404 may generate the second UE capability information message 1452 without being constrained by the packet size limit for one packet. In some such examples, the amount of uplink control information that UE 1404 may encode in the second UE capability information message 1452 may be greater than the amount of uplink control information that UE 1404 may encode in the first UE capability information message 1422. In some scenarios, UE 1404 may be able to provide additional capability information that UE 1404 was previously unable to provide. UE 1404 may then send the second UE capability information message 1452 via a segmented message 1454 obtained by network entity 1402. Aspects of the segmented message 1454 may be similar to Figure 4 Segmented message 442 and / or Fig.11 Segmented message 1136.

[0210] Fig.15 1500 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 and / or Fig.17 The method may facilitate improved communication performance in scenarios where message segmentation is permitted, but channel conditions or network behavior may reduce the benefits of sending uplink control messages with segmentation.

[0211] At 1502, the UE receives an indication from the network to enable segmentation of an uplink control message, such as in conjunction with at least Figure 4 The segment indicator 414, Figure 8 The segment indicator 812, Fig.11 The segment indicator 1112 and / or Fig.12 The receipt of the indication at 1502 may be performed by Fig.17The cellular RF transceiver 1722 / message segmentation component 198 of the device 1704 is executed.

[0212] At 1504, the UE sends an uplink control message based on uplink control information to the network without the segmentation, the uplink control information having a size greater than the maximum PDCP SDU size, based on at least one of a channel condition or a count of connection releases from the network, such as in combination with at least Figure 8 The reduction process 842, Fig. 9 first UE capability information message 922, Fig.11 UE capability information message 1150 and / or Fig.12 The sending of the uplink control message without segmentation at 1504 may be performed by Fig.17 The cellular RF transceiver 1722 and / or the message segmentation component 198 of the device 1704 are executed.

[0213] Fig.16 1600 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 and / or Fig.17 The method may facilitate improved communication performance in scenarios where message segmentation is permitted, but channel conditions or network behavior may reduce the benefits of sending uplink control messages with segmentation.

[0214] At 1602, the UE receives an indication from the network to enable segmentation of an uplink control message, such as in conjunction with at least Figure 4 The segment indicator 414, Figure 8 The segment indicator 812, Fig.11 The segment indicator 1112 and / or Fig.12 The receipt of the indication at 1602 may be performed by Fig.17 The cellular RF transceiver 1722 / message segmentation component 198 of the device 1704 is executed.

[0215] At 1612, the UE sends an uplink control message based on uplink control information to the network without the segmentation based on at least one of a channel condition or a count of connection releases from the network, the uplink control information having a size greater than the maximum PDCP SDU size, such as in combination with at least Figure 8 The reduction process 842, Fig. 9 first UE capability information message 922, Fig.11 UE capability information message 1150 and / or Fig.12 The transmission of the uplink control message without segmentation at 1612 may be performed by Fig.17 The cellular RF transceiver 1722 and / or the message segmentation component 198 of the device 1704 are executed.

[0216] In some examples, the indication (e.g., at 1602) may enable RRC message segmentation. In some such examples, the uplink control message (e.g., at 1604) may include UE capability information having an encoded RRC message size that is reduced to meet the maximum PDCP SDU size so that the UE capability information is sent without segmentation.

[0217] In some examples, the UE may reduce the size of the uplink control message. For example, at 1604, the UE may reduce the size of the uplink control message to meet the maximum PDCP SDU size, such as in combination with at least Figure 8 The size of the uplink control message can be reduced by Fig.17 The cellular RF transceiver 1722 / message segmentation component 198 of the device 1704 is executed.

[0218] In some examples, the UE may send an uplink control message to the network without segmentation in response to channel conditions satisfying a threshold, such as in conjunction with Figure 7 The second test 714 and / or Figure 8 In some examples, satisfying the threshold is based on RSRP being less than an RSRP threshold, such as in conjunction with Figure 7 In some examples, satisfying the threshold is based on the average path loss being greater than the path loss threshold, such as in combination with Figure 7 In some examples, satisfying the threshold is based on the SNR being less than the SNR threshold, such as in combination with Figure 7 The third channel condition test 726 is described in detail. In some examples, satisfying the threshold is based on the corresponding measurement satisfying at least one of an RSRP threshold, a path loss threshold, and an SNR threshold.

[0219] In some examples, after determining that the channel condition is poor, the UE may perform a monitoring process to monitor for the occurrence of an update triggering event. For example, at 1614, the UE may send an update message in response to a change in the channel condition, such as in conjunction with Fig. 9 The update message 934 is described. The sending of the update message at 1614 can be performed by Fig.17 The cellular RF transceiver 1722 and / or the message segmentation component 198 of the device 1704 are executed.

[0220] At 1616, the UE may receive a capability query from the network based in part on the update message, such as in conjunction with Fig. 9The capability query message 938 is described. The reception of the capability query at 1616 may be performed by Fig.17 The cellular RF transceiver 1722 and / or the message segmentation component 198 of the device 1704 are executed.

[0221] At 1618, the UE may send a second uplink control message with segmentation in response to the capability query, such as in conjunction with Fig. 9 The second UE capability information message 952 and the segmentation message 954 are described. The sending of the second uplink control message with segmentation at 1618 can be performed by Fig.17 The cellular RF transceiver 1722 and / or the message segmentation component 198 of the device 1704 are executed.

[0222] In some examples, the UE sends an uplink control message without segmentation in response to a count of connection releases from the network being above a release threshold, such as in conjunction with at least Fig.11 UE capability information message 1150, Fig.12 UE capability information message 1236 and / or Fig.14 As described in the first UE capability information message 1422.

[0223] For example, at 1606, the UE may send one or more uplink control messages with segmentation, such as in conjunction with at least Fig.13 The UE capability information associated with the example of Table 1300 is described. At 1606, the transmission of one or more uplink control messages with segmentation may be performed by Fig.17 The cellular RF transceiver 1722 and / or the message segmentation component 198 of the device 1704 are executed.

[0224] At 1608, the UE may increment a count of connection releases in response to each reception of a connection release from the network within a time window after sending one of the one or more uplink control messages with segmentation, wherein the UE sends the uplink control message without segmentation in response to the count of connection releases being above a release threshold, as in conjunction with Fig.11 The incremental process 1148 and Fig.12 The increment process 1230 of the connection release is described. The increment of the count of the connection release at 1608 can be performed by Fig.17 The cellular RF transceiver 1722 / message segmentation component 198 of the device 1704 is executed.

[0225] At 1610, the UE may reset the count of connection releases in response to receiving an additional connection release outside a time window after sending one of the one or more uplink control messages, such as in conjunction with Fig.11The reset process 1146 and / or Fig.12 The reset process 1232 of the connection release is described. The reset of the count of connection release at 1610 can be performed by Fig.17 The cellular RF transceiver 1722 / message segmentation component 198 of the device 1704 is executed.

[0226] In some examples, after determining that the count of connection releases from the network is above the release threshold, the UE may perform a monitoring process to monitor for the occurrence of an update triggering event. For example, at 1620, the UE may send an update message in response to a change in at least one of a cell, a tracking area, or a serving network node, such as in conjunction with Fig.14 The update message 1434 is described. The sending of the update message at 1620 may be performed by Fig.17 The cellular RF transceiver 1722 and / or the message segmentation component 198 of the device 1704 are executed.

[0227] At 1622, the UE may receive a capability query from the network based in part on the update message, such as in conjunction with Fig.14 The capability query message 1438 is described. The reception of the capability query at 1622 may be performed by Fig.17 The cellular RF transceiver 1722 and / or the message segmentation component 198 of the device 1704 are executed.

[0228] At 1624, the UE may send a second uplink control message with segmentation in response to the capability query, such as in conjunction with Fig.14 The second UE capability information message 1452 and the segment message 1454 are described. The sending of the second uplink control message at 1624 may be performed by Fig.17 The cellular RF transceiver 1722 and / or the message segmentation component 198 of the device 1704 are executed.

[0229] Fig.171700 is a diagram illustrating an example of a hardware implementation for an apparatus 1704. The apparatus 1704 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1704 may include a cellular baseband processor 1724 (also referred to as a modem) coupled to one or more transceivers (e.g., a cellular RF transceiver 1722). The cellular baseband processor 1724 may include on-chip memory 1724'. In some aspects, the apparatus 1704 may also include one or more subscriber identity module (SIM) cards 1720 and an application processor 1706 coupled to a secure digital (SD) card 1708 and a screen 1710. The application processor 1706 may include on-chip memory 1706'. In some aspects, the device 1704 may also include a Bluetooth module 1712, a WLAN module 1714, an SPS module 1716 (e.g., a GNSS module), one or more sensor modules 1718 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1726, a power source 1730, and / or a camera 1732. The Bluetooth module 1712, the WLAN module 1714, and the SPS module 1716 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1712, the WLAN module 1714, and the SPS module 1716 may include their own dedicated antennas and / or communicate using one or more antennas 1780. The cellular baseband processor 1724 communicates with the UE 104 and / or with the RU associated with the network entity 1702 via one or more antennas 1780 through a transceiver (e.g., a cellular RF transceiver 1722). The cellular baseband processor 1724 and the application processor 1706 may each include a computer-readable medium / memory, such as an on-chip memory 1724' and an on-chip memory 1706', respectively. The additional memory module 1726 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory (e.g., on-chip memory 1724', on-chip memory 1706', and / or additional memory module 1726) may be non-transitory. The cellular baseband processor 1724 and the application processor 1706 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1724 / application processor 1706, enables the cellular baseband processor 1724 / application processor 1706 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1724 / application processor 1706 when executing software.The cellular baseband processor 1724 / application processor 1706 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1704 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1724 and / or the application processor 1706, while in another configuration, the device 1704 may be the entire UE (e.g., see. Figure 3 UE350) and includes additional modules of device 1704.

[0230] As discussed above, the message segmentation component 198 is configured to receive an indication from a network to enable segmentation of an uplink control message. The example message segmentation component 198 is also configured to send an uplink control message based on uplink control information to the network without the segmentation, the uplink control information having a size greater than a maximum Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) size, based on at least one of channel conditions or a count of connection releases from the network.

[0231] The message segmentation component 198 may be within the cellular baseband processor 1724, the application processor 1706, or both the cellular baseband processor 1724 and the application processor 1706. The message segmentation component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the foregoing.

[0232] As shown, the device 1704 may include various components configured for various functions. For example, the message segmentation component 198 may include an execution Fig.15 and / or Fig.15 Each block in the algorithm block in the flowchart is one or more hardware components.

[0233] In one configuration, the apparatus 1704 (and specifically the cellular baseband processor 1724 and / or the application processor 1706) includes means for receiving an indication from a network to enable segmentation of an uplink control message. The example apparatus 1704 also includes means for sending an uplink control message based on uplink control information to the network without the segmentation, the uplink control information having a size greater than the maximum PDCP SDU size, based on at least one of channel conditions or a count of connection releases from the network.

[0234] In another configuration, the example apparatus 1704 further includes means for reducing the size of the uplink control information to meet the maximum PDCP SDU size.

[0235] In another configuration, the example apparatus 1704 further includes means for sending an update message in response to a change in channel conditions. The example apparatus 1704 further includes means for receiving a capability query from the network based in part on the update message. The example apparatus 1704 further includes means for sending a second uplink control message with segmentation in response to the capability query.

[0236] In another configuration, the example apparatus 1704 further includes means for sending one or more uplink control messages with segmentation. The example apparatus 1704 further includes means for incrementing a count of connection releases in response to each reception of a connection release from the network within a time window after sending one of the one or more uplink control messages with segmentation, wherein the UE sends the uplink control message without segmentation in response to the count of connection releases being above a release threshold.

[0237] In another configuration, the example apparatus 1704 further includes means for sending an update message in response to a change in at least one of a cell, a tracking area, or a serving network node. The example apparatus 1704 further includes means for receiving a capability query from the network based in part on the update message. The example apparatus 1704 further includes means for sending a second uplink control message with segmentation in response to the capability query.

[0238] This means may be the message segmentation component 198 of the apparatus 1704 configured to perform the functions recited by this means. As described above, the apparatus 1704 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, this means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by this means.

[0239] Various aspects disclosed herein provide techniques for enabling a UE configured with message segmentation to determine whether to employ message segmentation based on at least one of channel conditions or a count of connection releases from the network. For example, even when message segmentation is permitted based on the size of an uplink control message, the UE may determine to skip employing message segmentation.

[0240] Various aspects presented herein may enable a UE to improve communication performance in scenarios where message segmentation is permitted. For example, under poor channel conditions, avoiding message segmentation may reduce overhead associated with uplink transmissions, which may avoid or reduce delays associated with procedures (such as attach procedures) based on information provided by the UE via uplink control messages. Avoiding message segmentation under poor channel conditions may also reduce the likelihood of connection drops due to lost acknowledgment messages from the network after the UE sends an uplink control message.

[0241] In an example where the UE avoids message fragmentation based on a count of connection release messages, the UE may be able to improve communication performance by maintaining a connection with the network. For example, if the network performs an immediate connection release after the UE sends a fragmentation message, the UE may have the ability to determine that the network cannot handle message fragmentation based on a count of connection release messages. In such an example, the UE may skip message fragmentation when communicating with the network to maintain a connection with the network.

[0242] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0243] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0244] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0245] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0246] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving an indication from a network to enable segmentation of an uplink control message; and sending an uplink control message based on the uplink control information to the network without the segmentation based on at least one of a channel condition or a count of connection releases from the network, the uplink control information having a size greater than a maximum packet data convergence protocol (PDCP) service data unit (SDU) size.

[0247] Aspect 2 is a method according to aspect 1, the method further comprising: reducing the size of the uplink control information to meet the maximum PDCP SDU size.

[0248] Aspect 3 is a method according to any one of aspects 1 and 2, the method further comprising: the uplink control message is sent to the network without the segmentation in response to the channel condition satisfying a threshold.

[0249] Aspect 4 is a method according to any one of Aspects 1 to 3, and the method also includes: satisfying the threshold is based on one or more of the following: the reference signal received power (RSRP) is less than the RSRP threshold, the average path loss is greater than the path loss threshold, or the signal-to-noise ratio (SNR) is less than the SNR threshold.

[0250] Aspect 5 is a method according to any one of Aspects 1 to 4, the method further comprising: the uplink control message is a first uplink control message, the method further comprising: sending an update message in response to a change in the channel condition; receiving a capability query from the network based in part on the update message; and sending a second uplink control message in response to the capability query in the presence of the segmentation.

[0251] Aspect 6 is a method according to any one of Aspects 1 and 2, the method further comprising: the uplink control message is sent to the network without the segmentation in response to the count of the connection release from the network being higher than a release threshold.

[0252] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: sending one or more uplink control messages in the presence of the segmentation; and incrementing the count of the connection release in response to each reception of a connection release from the network within a time window after sending one of the one or more uplink control messages in the presence of the segmentation, wherein the UE sends the uplink control message in the absence of the segmentation in response to the count of the connection release being higher than the release threshold.

[0253] Aspect 8 is a method according to any one of Aspects 1 to 7, the method further comprising: resetting the count of the connection release in response to receiving an additional connection release outside the time window after sending one of the one or more uplink control messages.

[0254] Aspect 9 is a method according to any one of Aspects 1 to 8, the method also including: the uplink control message is a first uplink control message, the method also including: sending an update message in response to a change in at least one of a cell, a tracking area or a serving network node; receiving a capability query from the network based in part on the update message; and sending a second uplink control message in response to the capability query in the presence of the segmentation.

[0255] Aspect 10: According to the method according to any one of aspects 1 to 9, the method further includes: enabling the indication of radio resource control (RRC) message segmentation.

[0256] Aspect 11 is a method according to any one of Aspects 1 to 10, the method further comprising: the uplink control message includes UE capability information having an encoded RRC message size, the encoded RRC message size being reduced to meet the maximum PDCP SDU size so as to send the UE capability information without the segmentation.

[0257] Aspect 12 is an apparatus for wireless communication at a UE, the apparatus comprising at least one processor coupled to a memory and configured to implement any one of aspects 1 to 11.

[0258] In aspect 13, the apparatus according to aspect 12 further comprises at least one antenna coupled to the at least one processor.

[0259] In aspect 14, the apparatus according to aspect 12 or 13 further comprises a transceiver coupled to the at least one processor.

[0260] Aspect 15 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 11.

[0261] In aspect 16, the apparatus according to aspect 15 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 1 to 11.

[0262] In aspect 17, the apparatus according to aspect 15 or 16 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 1 to 11.

[0263] Aspect 18 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 1 to 11.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and configured to: receiving an indication from a network to enable segmentation of an uplink control message; as well as An uplink control message based on uplink control information having a size greater than a maximum Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) size is sent to the network without the segmentation based on at least one of a channel condition or a count of connection releases from the network.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: The size of the uplink control information is reduced to meet the maximum PDCP SDU size.

3. The apparatus of claim 1 , wherein the at least one processor is configured to: The uplink control message is sent to the network without the segmentation in response to the channel condition satisfying a threshold.

4. The apparatus of claim 3, wherein to satisfy the threshold, the at least one processor is configured to determine at least one of: The reference signal received power (RSRP) is less than the RSRP threshold; The average path loss is greater than the path loss threshold, or The signal-to-noise ratio (SNR) is less than the SNR threshold.

5. The apparatus of claim 3, wherein the uplink control message is a first uplink control message, and the at least one processor is further configured to: sending an update message in response to a change in the channel condition; receiving a capability query from the network based in part on the update message; and A second uplink control message is sent with the segment in response to the capability query.

6. The apparatus of claim 1, wherein the at least one processor is configured to: The uplink control message is sent to the network without the segmentation in response to the count of the connection releases from the network being above a release threshold.

7. The apparatus of claim 6, wherein the at least one processor is further configured to: sending one or more uplink control messages with the segmentation; and In response to each reception of a connection release from the network within a time window after sending one of the one or more uplink control messages with the segmentation, the count of the connection release is incremented, wherein the UE sends the uplink control message without the segmentation in response to the count of the connection release being higher than the release threshold.

8. The apparatus of claim 7, wherein the at least one processor is further configured to: The count of the connection releases is reset in response to receipt of an additional connection release outside the time window after sending one of the one or more uplink control messages.

9. The apparatus of claim 6, wherein the uplink control message is a first uplink control message, and the at least one processor is further configured to: sending an update message in response to a change in at least one of a cell, a tracking area, or a serving network node; receiving a capability query from the network based in part on the update message; and A second uplink control message is sent with the segment in response to the capability query.

10. The apparatus of claim 1, wherein the indication enables radio resource control (RRC) message segmentation.

11. The apparatus of claim 10, wherein the uplink control message comprises UE capability information having an encoded RRC message size, the encoded RRC message size being reduced to satisfy the maximum PDCP SDU size so as to transmit the UE capability information without the segmentation.

12. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor.

13. A method of wireless communication at a user equipment (UE), the method comprising: receiving an indication from a network to enable segmentation of an uplink control message; as well as An uplink control message based on uplink control information having a size greater than a maximum Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) size is sent to the network without the segmentation based on at least one of a channel condition or a count of connection releases from the network.

14. The method according to claim 13, further comprising: The size of the uplink control information is reduced to meet the maximum PDCP SDU size.

15. The method of claim 13, wherein the uplink control message is sent to the network without the segmentation in response to the channel condition satisfying a threshold.

16. The method of claim 15, wherein satisfying the threshold is based on one or more of: The reference signal received power (RSRP) is less than the RSRP threshold; The average path loss is greater than the path loss threshold, or The signal-to-noise ratio (SNR) is less than the SNR threshold.

17. The method of claim 15, wherein the uplink control message is a first uplink control message, the method further comprising: sending an update message in response to a change in the channel condition; receiving a capability query from the network based in part on the update message; as well as A second uplink control message is sent with the segment in response to the capability query.

18. The method of claim 13, wherein the uplink control message is sent to the network without the segmentation in response to the count of the connection releases from the network being above a release threshold.

19. The method according to claim 18, further comprising: sending one or more uplink control messages with the segmentation; as well as In response to each reception of a connection release from the network within a time window after sending one of the one or more uplink control messages with the segmentation, the count of the connection release is incremented, wherein the UE sends the uplink control message without the segmentation in response to the count of the connection release being higher than the release threshold.

20. The method according to claim 19, further comprising: The count of the connection releases is reset in response to receipt of an additional connection release outside the time window after sending one of the one or more uplink control messages.

21. The method of claim 18, wherein the uplink control message is a first uplink control message, the method further comprising: sending an update message in response to a change in at least one of a cell, a tracking area, or a serving network node; receiving a capability query from the network based in part on the update message; as well as A second uplink control message is sent with the segment in response to the capability query.

22. The method of claim 13, wherein the indication enables radio resource control (RRC) message segmentation.

23. The method of claim 22, wherein the uplink control message includes UE capability information having an encoded RRC message size, the encoded RRC message size being reduced to satisfy the maximum PDCP SDU size so as to transmit the UE capability information without the segmentation.

24. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: means for receiving an indication from a network to enable segmentation of an uplink control message; and Means for sending an uplink control message based on uplink control information to the network without the segmentation based on at least one of a channel condition or a count of connection releases from the network, the uplink control information having a size greater than a maximum Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) size.

25. The apparatus according to claim 24, further comprising: Means for reducing the size of the uplink control information to meet the maximum PDCP SDU size.

26. The apparatus of claim 24, wherein the uplink control message is sent to the network without the segmentation in response to the channel condition satisfying a threshold.

27. The apparatus of claim 26, wherein the uplink control message is a first uplink control message, the apparatus further comprising: means for sending an update message in response to a change in said channel condition; means for receiving a capability query from the network based in part on the update message; and Means for sending a second uplink control message with the segmentation in response to the capability query.

28. The apparatus of claim 24, wherein the uplink control message is sent to the network without the segmentation in response to the count of the connection releases from the network being above a release threshold.

29. The apparatus according to claim 28, further comprising: means for transmitting one or more uplink control messages with said segmentation; as well as means for incrementing the count of connection releases in response to each reception of a connection release from the network within a time window after sending one of the one or more uplink control messages with the segmentation, wherein the UE sends the uplink control message without the segmentation in response to the count of connection releases being above the release threshold.

30. The apparatus according to claim 29, further comprising: Means for resetting the count of the connection releases in response to receipt of an additional connection release outside the time window after sending one of the one or more uplink control messages.

Images