Enhanced handling of syntactical error of packet data network connection

Abstract

A user equipment (UE) in a cellular network implements one or more mechanisms to manage syntactical errors in packet filters. Responsive to detecting an error in at least one packet filter received during a bearer configuration procedure, the UE modifies a current packet filter configuration by removing the at least one packet filter while retaining a copy of the current packet filter configuration prior to modification. The UE transmits a bearer resource modification request to the cellular network to delete the at least one packet filter having the error. The UE maintains the modified current packet filter configuration responsive to the cellular network accepting the bearer resource modification request.

Description

ENHANCED HANDLING OF SYNTACTICAL ERROR OF PACKET DATA NETWORK CONNECTION BACKGROUND

[0001] In modern wireless communication networks, user equipment (UE) establishes and maintains connectivity with a packet data network (PDN) through bearer connections, which define the quality of service (QoS) and traffic flow parameters for data transmission. To ensure efficient data delivery, the network dynamically configures and modifies bearer parameters, including the Traffic Flow Template (TFT) and associated packet filters. These packet filters determine which data packets are routed through specific bearers, enabling optimized network resource allocation and prioritization of different types of traffic.

[0002] However, during the bearer activation or modification process, the UE may receive requests from the network that contain syntactical errors in the packet filters. Such errors can arise due to misconfigurations, conflicting filter precedence values, or inconsistencies in network signaling. According to existing 3rd Generation Partnership Project (3GPP) specifications, when the UE detects such errors, it is required to delete the conflicting packet filters to ensure that only valid configurations are retained. While this approach maintains compliance with network policies, it introduces challenges in practical implementations, as it can inadvertently lead to the removal of necessary packet filters, causing service disruptions and degrading user experience.

[0003] In certain real-world deployments, such as those observed in commercial networks, the handling of these errors has led to unintended consequences. When the UE detects an error and requests a bearer resource modification, the network may respond by adjusting its configuration without fully accepting the modification request. In such cases, the existing bearer may be removed, and the packet filters associated with the newly allocated bearer may also be deleted. This results in a scenario where the PDN connection becomes non-functional, leading to dropped data sessions and call failures. This issue is particularly problematic in networks where frequent bearer modifications occur, as it creates instability and negatively impacts service continuity.SUMMARY OF EMBODIMENTS

[0004] In accordance with one aspect, a method at a user equipment (UE) of a cellular network includes modifying, responsive to detecting an error in at least one packet filter received during a bearer configuration procedure with the cellular network, modifying a current packet filter configuration by removing the at least one packet filter while retaining a copy of the current packet filter configuration prior to modification. A bearer resource modification request is transmitted to the cellular network to delete the at least one packet filter having the error. The modified current packet filter configuration is maintained responsive to the cellular network accepting the bearer resource modification request.

[0005] In at least some embodiments, the current packet filter configuration comprises a Traffic Flow Template (TFT) that includes one or more packet filters, and the method further comprises, responsive to detecting the error in at least one packet filter, retaining a copy of the TFT prior to modifying the current packet filter configuration. A modified TFT that excludes the at least one packet filter having the error is maintained responsive to the cellular network accepting the bearer resource modification request.

[0006] In at least some embodiments, the method further includes, responsive to the cellular network rejecting the bearer resource modification request, determining whether the retained copy of the current packet filter configuration still includes the at least one packet filter having the error. In response to the retained copy of the current packet filter configuration still including the at least one packet filter having the error, a conflict resolution procedure is initiated. In response to the retained copy of the current packet filter configuration no longer including the at least one packet filter having the error, the retained copy of the current packet filter configuration is restored.

[0007] In at least some embodiments, the method further includes, responsive to the retained copy of the current packet filter configuration still including the at least one packet filter having the error, locally releasing a dedicated bearer and initiating a mobility update procedure to synchronize bearer resource configurations with the cellular network. In response to the retained copy of the current packet filterconfiguration no longer including the at least one packet filter having the error, the retained copy of the current packet filter configuration is restored.

[0008] In at least some embodiments, locally releasing the dedicated bearer includes removing a bearer associated with the at least one packet filter having the error while maintaining connectivity for one or more other active bearers.

[0009] In at least some embodiments, the mobility update procedure includes transmitting a signaling message to the cellular network to provide an updated packet filter configuration.

[0010] In at least some embodiments, transmitting the signaling message includes transmitting a Tracking Area Update request comprising information related to the updated packet filter configuration.

[0011] In at least some embodiments, the error in the packet filter comprises a syntactical error that renders the packet filter invalid or unusable according to one or more predefined network rules.

[0012] In at least some embodiments, the syntactical error comprises at least one of: an incorrect format, an invalid precedence value, ora missing parameter in a definition of the at least one packet filter.

[0013] In at least some embodiments, retaining the copy of the current packet filter configuration prior to modification includes retaining the current packet filter configuration via a temporary holding mechanism.

[0014] In at least some embodiments, the method further includes deactivating the temporary holding mechanism in response to the cellular network accepting the bearer resource modification request.

[0015] In at least some embodiments, preventing deletion of one or more valid packet filters to maintain uninterrupted Packet Data Network connectivity in response to detecting the error in the at least one packet filter.

[0016] In accordance with another aspect, a user equipment device includes one or more radio frequency (RF) modems configured to wirelessly communicate with at least one network. One or more processors are coupled to the one or more RFmodems. At least one memory stores executable instructions. The executable instructions are configured to manipulate at least one of the one or more processors or the one or more RF modems to modify, responsive to a detected error in at least one packet filter received during a bearer configuration procedure with the cellular network, a current packet filter configuration by removing the at least one packet filter while retaining a copy of the current packet filter configuration prior to modification. The executable instructions are further configured to manipulate at least one of the one or more processors or the one or more RF modems to transmit a bearer resource modification request to the cellular network to delete the at least one packet filter having the error, and maintain the modified current packet filter configuration responsive to the cellular network accepting the bearer resource modification request.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The present disclosure may be better understood, and its numerous features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference symbols in different drawings indicates similar or identical items.

[0018] FIG. 1 is a diagram illustrating an example wireless system employing a user equipment (LIE) configured to enhance the handling of syntactical errors in packet filters during Evolved Packet System bearer activation and modification in accordance with some embodiments.

[0019] FIG. 2 is a block diagram illustrating example configurations for enhanced bearer resource management employed by a UE of FIG. 1 in accordance with some embodiments.

[0020] FIG. 3 is a diagram illustrating an example hardware configuration of a UE of FIG. 1 in accordance with some embodiments.

[0021] FIG. 4 is a flow diagram illustrating an example method for handling syntactical errors in packet filters at a UE of FIG. 1 in accordance with some embodiments.DETAILED DESCRIPTION

[0022] In existing cellular networks, the process of activating and modifying dedicated Evolved Packet System (EPS) bearer contexts relies on the correct configuration of packet filters within the TFT. Packet filters play a role in directing specific types of traffic through designated bearers, ensuring efficient network resource utilization and maintaining the expected QoS for different applications. However, when the UE receives an EPS bearer context activation or modification request including syntactical errors in the packet filters, the UE must take corrective action to avoid conflicts in traffic handling. A syntactical error refers to, for example, an issue in the structure or format of a packet filter definition that makes it invalid or unusable according to predefined network rules.

[0023] Current cellular network standards specify that the UE should delete any conflicting packet filters when processing such requests. While this mechanism is designed to maintain consistency in bearer configuration, it introduces an unintended issue where necessary packet filters may also be removed if the network does not fully process or accept the UE’s modification request. This problem is particularly evident in scenarios where the UE attempts to delete incorrect filters, but the network responds by removing the entire bearer while also discarding the packet filters associated with a newly allocated bearer. As a result, the PDN connection becomes non-functional, leading to service interruptions and potential call drops.

[0024] As such, to address these and other challenges, the following describes embodiments of systems and methods for enhancing UE behavior when handling syntactical errors in packet filters. The UE, in at least some embodiments, is configured to handle syntactical errors in packet filters by modifying its current packet filter configuration upon detecting an error. When an erroneous packet filter is identified, the UE removes the erroneous filter while retaining a copy of the current packet filter configuration prior to modification. After this modification, the UE transmits a bearer resource modification request to the network, notifying it of the deletion of the erroneous packet filter. If the network accepts the modification request, the UE maintains the modified packet filter configuration and proceeds with normal operation. If the network rejects the request, the UE evaluates whether the retained copy of the packet filter configuration still includes the erroneous packet filter. When the retained copy continues to contain the error, the UE initiates aconflict resolution procedure by locally releasing the dedicated bearer and triggering a mobility update procedure, such as a Tracking Area Update (TAU), to resynchronize with the network. If the retained copy no longer includes the erroneous packet filter, the UE restores the copy of the packet filter configuration to maintain PDN connectivity without unnecessary bearer or filter loss.

[0025] By implementing a mechanism that allows the UE to temporarily hold packet filter configurations during the modification process and restore them when necessary, the UE ensures that network connectivity remains stable, even in the presence of signaling inconsistencies. This approach mitigates the risk of unintended packet filter deletion, reduces service disruptions, and improves the overall reliability of PDN connections while maintaining compliance with existing 3GPP specifications. By preventing unintended deletions and optimizing bearer handling, the techniques described herein significantly enhance service reliability, improve user experience, and enable more stable network performance, particularly in environments with frequent bearer modifications.

[0026] For ease of illustration, the following techniques are described in an example context in which one or more UEs and one or more RANs implement at least a Fourth Generation (4G) Long-Term Evolution (3GPP LTE) standard (e.g., 3GPP Release 8, Release 9, Release 10, etc.) or a Fifth Generation (3G) New Radio (NR) standard (e.g., 3GPP Release 13, 3GPP Release 16, 3GPP Release 17, etc.) (hereinafter, "3G NR" or "3G NR standard"). However, it should be understood that the present disclosure is not limited to networks employing an LTE or 3G NR RAT configuration, but rather, the techniques described herein can be implemented in any network environment employing bearer resource management and mobility operations, particularly where a UE handles syntactical errors in packet filters to maintain PDN connectivity and minimize service disruptions.

[0027] Additionally, the present disclosure is not limited to any specific network configurations or architectures for implementing bearer management or packet filter handling within a PDN connection. Instead, the described techniques can be applied across various network configurations where a UE processes bearer activation, modification, and resource management procedures. Furthermore, the present disclosure is not restricted to the examples and contexts provided herein, but rather,the techniques can be implemented in any network environment where a UE handles syntactical errors in packet filters while maintaining PDN connectivity and minimizing service disruptions.

[0028] FIG. 1 illustrates a mobile cellular network 100 (also referred to here as “cellular network 100” or “network 100”) in accordance with at least some embodiments. As shown, the mobile cellular network 100 includes a device, such as a user equipment (UE) 102, that is configured to communicate with one or more base stations (BSs) 104 (illustrated as BS 104-1 and BS 104-2) through one or more wireless communication links 106 (illustrated as wireless links 106-1 and 106-2). The UE 102, in at least some embodiments, includes any of a variety of wireless communication devices, such as a cellular phone, a cellular-enabled tablet computer or cellular-enabled notebook computer, a cellular-enabled wearable device, an automobile, or other vehicle employing cellular services (e.g., for navigation, provision of entertainment services, in-vehicle mobile hotspots, etc.), and so on. In at least some embodiments, the UE 102 employs a single RAT 108. In other embodiments, the UE 102 is a multi-mode UE that employs multiple RATs 108 (illustrated as RAT 108-1 and RAT 108-2). Examples of multiple RATs include cellular-based RATs, such as a 3GPP Long-Term Evolution (3GPP LTE) RAT, a 3GPP Fifth Generation New Radio (3G NR) RAT, a WLAN RAT, and the like. It should be understood that although FIG. 1 only shows the UE 102 implementing two different RATs 108, the UE 102, in at least some implementations, implements three or more different RATs 108. In at least some embodiments, one or more RAT modules 110 (illustrated as RAT module 110-1 and RAT module 110-2) manage the RATs 108 and enable communication between the UE 102 and the radio access technology of the network 100. The one or more RAT modules 110, in at least some embodiments, include one or more of a modem chipset(s) of the UE 102, a protocol stack(s), driver software, and the like.

[0029] In at least some embodiments, the BSs 104 are implemented in a macrocell, microcell, small cell, picocell, and the like, or any combination thereof. Examples of base stations 104 include an Evolved Universal Terrestrial Radio Access Network Node B (E-UTRAN Node B), Evolved Node B (eNodeB or eNB), Next Generation (NG or NGEN) Node B (gNode B or gNB), and so on. The BSs 104 communicate with the UE 102 via the wireless links 106, which are implementedusing any suitable type of wireless link. The wireless links 106, in at least some embodiments, include a downlink of data and control information communicated from the base stations 104 to the UE 102, an uplink of data and control information communicated from the UE 102 to the BSs 104, or both. In at least some embodiments, the wireless links 106 (or bearers), such as data radio bearers (DRBs) and signal radio bearers (SRBs), are implemented using any suitable communication protocol or standard, or combination of communication protocols or standards, such as 3GPP 4G LTE, 3G NR, and so on. In at least some embodiments, multiple wireless links 106 are aggregated in a carrier aggregation to provide a higher data rate for the UE 102. Also, multiple wireless links 106 from multiple BSs 104 are configured, in at least some embodiments, for coordinated multipoint (CoMP) communication with the UE 102, as well as dual connectivity, such as single-RAT LTE-LTE or NR-NR dual connectivity or multi-radio access technology (Multi-RAT) dual connectivity (MR-DC) including E-UTRA-NR dual connectivity (EN-DC), NGEN radio access network (RAN) E-UTRA-NR dual connectivity (NGEN-DC), and NR E-UTRA dual connectivity (NE-DC).

[0030] The BSs 104 collectively form a Radio Access Network (RAN) 112, such as an E-UTRAN or 3G NR RAN. The base stations 104 are connected to a core network (CN) 114 (illustrated as CN 114-1 and CN 114-2) via control-plane and userplane interfaces through one or more links 116 (illustrated as link 116-1 and link 116-2). Depending on the configuration of the mobile cellular network 100, the core network 114 is either an Evolved Packet Core (EPC) network 114-1 or a 3G Core Network (3GC) 114-2. For example, in an E-UTRAN configuration or a 3G non-standalone (NSA) EN-DC configuration, the core network 114 is an EPC network 114-1 that includes, for example, a Mobility Management Entity (MME) 118, a Serving Gateway (SGW) 120, and a Packet Data Network Gateway (PGW) 122. The MME 118 provides control-plane functions, such as registration and authentication of multiple UEs 102, authorization, mobility management, and so on. The SGW 120 transfers user-plane packets related to audio calls, video calls, Internet traffic, and the like. The PGW 122 provides connectivity from the UE 102 to external packet data networks 124, such as the Internet 126 and an Internet Protocol Multimedia Subsystem (IMS) network 128, by being the point of exit and entry of traffic for the UE 102. In a 3G standalone (SA) configuration or an NSA NE-DC or NGEN-DC configuration, the core network 114 is a 3GC network 114-2. The 3GC 114-2includes, for example, an Access and Mobility Management function (AMF) 130, a User Plane Function (UPF) 132, and a Session Management Function (SMF) 134. The AMF 130 provides control-plane functions such as registration and authentication of multiple UEs 102, authorization, mobility management, and so on. The UPF 132 transfers user-plane packets related to audio calls, video calls, Internet traffic, and the like. The SMF 134 manages protocol data unit (PDU) sessions.

[0031] In at least some embodiments, the core network 114 communicatively couples the UE 102 to an IMS network 128 via the RAN 112. The IMS network 128 provides various IMS services to the UE 102, such as IMS short messages, IMS unstructured supplementary service data (USSD), IMS value-added service data, IMS supplementary service data, IMS voice calls, and IMS video calls. To this end, an entity (e.g., a server or a group of servers) operating in the IMS network 128 supports packet exchange with the UE 102. The packets convey signaling (such as session initiation protocol (SIP) messages, IP messages, or other suitable messages) as well as data (or media), such as voice or video. In at least some embodiments, the IMS network includes entities (not shown) such as a Proxy Call Session Control Function (P-CSCF), an Interrogating Call Session Control Function (l-CSCF), a Serving Call Session Control Function (S-CSCF), a Home Subscriber Server (HSS), a Media Gateway Control Function (MGCF), and the like.

[0032] PDN connectivity in modern wireless communication relies on the proper configuration and management of bearer resources within the EPS). Each bearer is associated with a TFT, which includes packet filters that define how network traffic is classified and routed. These packet filters ensure that different types of data traffic are assigned to appropriate bearers based on QoS requirements. However, in certain scenarios, the network 100 may send an EPS bearer activation or modification request that includes syntactical errors in the packet filters, leading to inconsistencies in traffic flow management.

[0033] As described above, ensuring seamless connectivity and service continuity at a UE 102 involves balancing efficient packet filter management with reliable bearer handling, particularly in the context of handling syntactical errors or conflicts during bearer activation and modification. When these errors occur, the UE 102 decides how to handle conflicting packet filters without disrupting active data sessions.Dynamic network signaling conditions introduce challenges such as unintended bearer removals, loss of valid packet filters, and disruptions in PDN connectivity. To address these and other challenges, the UE 102, in one or more embodiments, employs an enhanced bearer resource management mechanism 136 to intelligently manage packet filter modifications while preserving network stability.

[0034] For example, the UE 102 integrates a temporary holding mechanism for packet filters and TFT configurations that allows it to evaluate network responses before permanently modifying its bearer configuration. By temporarily retaining existing (e.g., current) packet filters during the modification process, the UE 102 prevents the accidental loss of valid filters due to unexpected network responses. In at least some embodiments, when the network 100 initiates an EPS bearer context deactivation or modification procedure that would remove a newly received TFT or packet filter, the UE 102 rejects the network-initiated deactivation and instead proceeds with its own bearer resource modification request to delete an outdated TFT or packet filter. This approach ensures that the UE 102 prioritizes its own modification decisions while maintaining alignment with network behavior. By intelligently managing bearer resources, the UE 102 minimizes service disruptions, maintains PDN connectivity, and enhances overall network reliability.

[0035] FIG. 2 illustrates various example configurations employed, individually or in combination, by the UE 102 as part of the enhanced bearer resource management mechanism 136, in accordance with at least some embodiments. These configurations include a packet filter holding configuration 202, a dynamic conflict resolution configuration 204, and a synchronization-based modification configuration 206. The enhanced bearer resource management mechanism 136 implements these configurations either independently or based on specific network responses and service conditions to optimize packet filter handling and avoid unintended bearer deactivations.

[0036] As part of these configurations, the enhanced bearer resource management mechanism 136, in at least some embodiments, includes a temporary holding mechanism 208, which allows the UE 102 to retain one or more existing packet filter configurations, which include, for example, one or more packet filters and one or more TFT configurations, during modification processes. The temporaryholding mechanism 208 helps ensure that packet filters are not prematurely deleted due to unexpected network responses.

[0037] In the packet filter holding configuration 202, the temporary holding mechanism 208 is utilized to retain the UE’s existing packet filters and TFT configuration while processing a bearer resource modification request. If the network 100 rejects the request, the UE 102 checks whether the retained copy of the current packet filter configuration still includes the erroneous packet filter. If the retained copy still contains the error, the UE 102 initiates dynamic conflict resolution by releasing the dedicated bearer and triggering a mobility update procedure. If the retained copy no longer includes the error, the UE 102 restores the retained copy of the current packet filter configuration, thereby preventing unintended deletions due to network signaling inconsistencies, minimizing service disruptions, and preserving active data sessions.

[0038] The dynamic conflict resolution configuration 204 relies on the temporary holding mechanism 208 to assess whether the identified packet filter conflict persists after the network 100 rejects a modification request. If the retained copy of the packet filter configuration still includes the erroneous packet filter, the UE 102 initiates dynamic conflict resolution by locally releasing the dedicated bearer and triggering a mobility update procedure, such as a Tracking Area Update (TAU), to resynchronize with the network 100 while ensuring that other active bearers remain unaffected. In at least some embodiments, if the network 100 initiates a deactivation or modification procedure that would remove a newly received TFT or packet filter, the UE 102 rejects the network-initiated deactivation and instead proceed with its own bearer resource modification request to delete an outdated TFT or packet filter. This ensures that the UE 102 maintains control over its bearer modifications while ensuring that bearer resources are synchronized with the network 100.

[0039] These processes ensure that the UE 102 and network 100 remain aligned in bearer and packet filter management, reducing the risk of PDN connection failures. Conversely, if the conflict no longer exists following the rejection, such as when the network 100 has initiated a separate bearer resource modification or activation that resolves the issue, the temporary holding mechanism enables the UE 102 to restorethe retained packet filters and TFT configuration, preventing unnecessary service interruptions.

[0040] In the synchronization-based modification configuration 206, the temporary holding mechanism 208 ensures that packet filters are not permanently removed while the UE 102 evaluates network responses and overall PDN connectivity status before finalizing any changes to its bearer configuration. If the network 100 removes an old bearer but rejects the UE’s modification request, the temporary holding mechanism retains the packet filters associated with the newly allocated bearer. This configuration allows for adaptive restoration of valid packet filters and TFT settings, mitigating the risk of service disruptions caused by unintended bearer deletions. Additionally, the UE 102 maintains connectivity for one or more active bearers during the modification process, ensuring that ongoing data transmissions, such as voice calls, video streaming, or enterprise VPN sessions, remain unaffected. This capability enables the UE to intelligently manage bearer modifications without compromising existing services, enhancing network stability and user experience in scenarios with frequent bearer reconfigurations.

[0041] Across these configurations, the enhanced bearer resource management mechanism 136 dynamically adapts to network signaling conditions by evaluating modification outcomes before committing to bearer changes. The inclusion of the temporary holding mechanism 208 ensures that PDN connectivity is maintained without premature bearer or packet filter loss, thereby improving service reliability and user experience in networks with frequent bearer modifications. Additionally, the UE 102 optimizes bearer resource configuration by selectively modifying packet filters and bearer assignments based on network conditions. This optimization process ensures that bearer resources are allocated efficiently, preventing unnecessary deletions and maintaining QoS requirements for active data sessions. By intelligently managing bearer resource configuration, the UE 102 reduces the risk of service interruptions and ensures a stable network connection across different mobility and signaling scenarios.

[0042] FIG. 3 illustrates an example device diagram 300 of a UE 102. In at least some embodiments, the device diagram 300 describes a UE that implements the enhanced bearer resource management techniques described herein. The UE 102may include additional functions and interfaces that are omitted from FIG. 3 for the sake of clarity. The UE 102, in at least some embodiments, includes antennas 302, a radio frequency (RF) front end 304, and a modem subsystem 306. The modem subsystem 306 includes multiple transceivers 308 (e.g., a 3GPP 4G LTE transceiver 308-1 and a 3G NR transceiver 308-2) for communicating with one or more base stations 104 in a RAN 112, such as a 3G RAN, an E-UTRAN, a combination thereof, and so on. The modem subsystem 306 also includes an RF modem, such as cellular modem 310 (also referred to as a baseband processor or a communication processor) that is responsible for managing the operations of the transceivers 308. In at least some embodiments, the modem 310 is implemented as a modem baseband processor, software-defined radio module, configurable modem (e.g., multi-mode, multi-band modem), wireless data interface, wireless modem, and so on. The modem 310 supports, for example, one or more of data access, messaging, or data-based services of a wireless network, as well as various audio-based communication (e.g., voice calls).

[0043] The RF front end 304, in at least some embodiments, includes a transmitting (Tx) front end 304-1 and a receiving (Rx) front end 304-2. The Tx front end 304-1 includes components such as one or more power amplifiers (PA), drivers, mixers, filters, and so on. The Rx front end 304-2 includes components such as low-noise amplifiers (LNAs), mixers, filters, and so on. The RF front end 304, in at least some embodiments, couples or connects the modem subsystem 306, including the LTE transceiver 308-1 and the 3G NR transceiver 308-2, to the antennas 302 to facilitate various types of wireless communication.

[0044] In at least some embodiments, the antennas 302 of the UE 102 include an array of multiple antennas configured similarly to or different from each other. The antennas 302 and the RF front end 304, in at least some embodiments, are tuned to or are tunable to one or more frequency bands, such as those defined by the 3GPP LTE, 3GPP 3G NR, IEEE Wireless Local Area Network (WLAN), IEEE Wireless Metropolitan Area Network (WMAN), or other communication standards. In at least some embodiments, the antennas 302, the RF front end 304, and the transceivers 308 are configured to support beamforming (e.g., analog, digital, or hybrid) or In-Phase and Quadrature (l / Q) operations (e.g., I / Q modulation or demodulation operations) for the transmission and reception of communications with one or morebase stations 104. By way of example, the antennas 302 and the RF front end 304 operate in sub-gigahertz bands, sub-6 GHz bands, above 6 GHz bands, or a combination of these bands defined by the 3GPP LTE, 3GPP 3G NR, or other communication standards.

[0045] In at least some embodiments, the antennas 302 include one or more receiving antennas positioned in a one-dimensional shape (e.g., a line) or a two-dimensional shape (e.g., a triangle, a rectangle, or an L-shape) for implementations that include three or more receiving antenna elements. While the one-dimensional shape enables the measurement of one angular dimension (e.g., an azimuth or an elevation), the two-dimensional shape enables two angular dimensions to be measured (e.g., both azimuth and elevation). Using at least a portion of the antennas 302, the UE 102 can form beams that are steered or un-steered, wide or narrow, or shaped (e.g., as a hemisphere, cube, fan, cone, or cylinder). The one or more transmitting antennas may have an un-steered omnidirectional radiation pattern or may produce a wide steerable beam. Either of these techniques enables the UE 102 to transmit a radio signal to illuminate a large volume of space. In some embodiments, the receiving antennas generate thousands of narrow steered beams (e.g., 2000 beams, 4000 beams, or 6000 beams) with digital beamforming to achieve desired levels of angular accuracy and angular resolution.

[0046] The UE 102, in at least some embodiments, includes one or more sensors 312 implemented to detect various properties such as one or more of temperature, supplied power, power usage, battery state, or the like. Examples of sensors include a thermal sensor, a battery sensor, a power usage sensor, and so on.

[0047] The UE 102 also includes at least one processor 314. The processor 314, in at least some embodiments, is a single-core processor or a multiple-core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. In at least some embodiments, the processor 314 is implemented at least partially in hardware, including, for example, components of an integrated circuit or a System-on-a-Chip (SoC), a Digital-Signal-Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), a Complex Programmable Logic Device (CPLD), other implementations in silicon or other hardware, or a combination thereof. Examples of the processor(s)314 include a communication processor if not implemented within the modem subsystem 306), an application processor, microprocessors, DSPs, controllers, and so on. An application processor, in at least some embodiments, provides computing resources to applications executing on the UE 102. For example, an application provides a self-contained operating environment that delivers system capabilities (e.g., graphics processing, memory management, and multimedia processing) to support applications executing on the UE 102.

[0048] The UE 102, in at least some embodiments, further includes a Wi-Fi controller 316, which is responsible for managing the device’s connection to Wi-Fi networks. The Wi-Fi controller 316 handles tasks such as scanning for available networks, establishing and maintaining Wi-Fi connections, and managing data transmission over Wi-Fi. The UE 102 interacts with the modem subsystem 306 and other components to coordinate network access and ensure seamless switching between Wi-Fi and cellular networks. The Wi-Fi controller 316, in at least some embodiments, is implemented as an integrated circuit (IC), either part of an SoC, or as a discrete component within the UE 102.

[0049] The UE 102 further includes a power management unit (PMU) 318, which is responsible for managing power distribution across the various components of the UE 102, including the RF front end 304, the modem subsystem 306, and the modem 310. The PMU 318 optimizes power usage by adjusting the power levels supplied to different components based on their operational state, ensuring that power consumption is minimized during periods of low activity or when certain components are disabled, such as when specific RATs are deprioritized or disabled based on the RAT selection techniques described herein. The PMU 318 also manages battery charging and ensures efficient power delivery to components when needed. In at least some embodiments, the PMU 318 is implemented as an IC that is either part of an SoC or as a discrete component within the UE 102.

[0050] The UE 102 further includes a non-transitory computer-readable storage media 320 (CRM 320). The computer-readable storage media described herein excludes propagating signals. The CRM 320, in at least some embodiments, includes any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM),read-only memory (ROM), or Flash memory useable to store device data 322 of the UE 102. In at least some embodiments, the device data 322 includes user data, multimedia data, beamforming codebooks, applications 324, an operating system 326 of the UE 102, a user interface(s) 328, and so on, which are executable by the processor(s) 314 to enable user-plane communication, control-plane signaling, and user interaction with the UE 102. The user interface 328, in at least some embodiments, is configured to receive inputs from a user of the UE 102, such as to receive input from a user that defines and or facilitates one or more aspects of adverse radio link condition detection. In at least some embodiments, the user interface 328 includes a graphical user interface (GUI) that receives the input information via a touch input. In other instances, the user interface 328 includes an intelligent assistant that receives the input information via an audible input or speech. Alternatively, or additionally, the operating system 326 of the UE 102 is maintained as firmware or an application on the CRM 320 and executed by the processor(s) 314.

[0051] The CRM 320, in at least some embodiments, further includes a communication manager 330. Alternatively, or additionally, the communication manager 330, in at least some embodiments, is implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE 102. In at least some embodiments, the communication manager 330 configures the RF front end 304, the LTE transceiver 308-1 , the 3G NR transceiver 308-2, or a combination thereof to perform one or more wireless communication operations.

[0052] The UE 102 also includes the enhanced bearer resource management mechanism 136 described herein. The enhanced bearer resource management mechanism 136, in at least some embodiments, is implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE 102. In other embodiments, one or more portions of the enhanced bearer resource management 136 are implemented in the CRM 320.

[0053] FIG. 4 illustrates a flow diagram of a method 400 for enhancing UE handling of syntactical errors in packet filters during EPS bearer activation and modification. The processes described below with respect to method 400 are detailed further with reference to FIGs. 1 through 3 above. For purposes of description, method 400 is described with respect to an example implementation ofthe UE 102 illustrated in FIG. 1 and FIG. 3, but it will be appreciated that, in other implementations, method 400 is performed within systems with different configurations of UE 102. Furthermore, method 400 is not limited to the sequence of operations shown in FIG. 4, as at least some operations can occur in parallel or in a different sequence. Additionally, in at least some implementations, method 400 can include one or more different operations beyond those depicted in FIG. 4.

[0054] At block 402, the UE 102 is in an operational state where it has already established a PDN connection with one or more dedicated EPS bearers. These dedicated bearers are used to handle specific types of traffic, such as Voice over LTE (VoLTE) calls, video streaming, enterprise VPN connections, or real-time gaming applications. Each dedicated bearer is associated with a TFT, which includes one or more packet filters that define which packets are allowed to be transmitted over that bearer. For example, a dedicated bearer for VoLTE may have a packet filter that allows Session Initiation Protocol (SIP) signaling traffic, while a video streaming bearer may include packet filters matching specific IP addresses and port numbers for media servers. Similarly, a Virtual Private Network (VPN) bearer may enforce filtering rules that only permit traffic to a corporate VPN gateway, and a real-time gaming bearer may prioritize low-latency packets for multiplayer gaming traffic.

[0055] At block 404, the UE 102 receives an EPS bearer configuration request (e.g., activation or modification request) from the network 100. This request is part of the standard bearer management procedures in 3GPP or other networks and is used to establish, update, or modify dedicated bearers that handle specific types of traffic. These requests are typically triggered by various network conditions, application requirements, or QoS adjustments. The request includes, for example, one or more packet filters associated with a TFT.

[0056] The network 100 may send a bearer activation or modification request in response to several scenarios, including application-specific QoS requirements, where a VoLTE call or video streaming service requires a dedicated bearer with appropriate QoS settings; policy and charging control (PCC) rule updates, where the network 100 adjusts bearer parameters based on service policies; handover or mobility events, where the UE 102 moves between cells and the network 100 modifies bearers to maintain service continuity; network-triggered optimizations,where bearers are reconfigured to balance traffic loads; error corrections, where the network 100 identifies and resolves packet filter inconsistencies to ensure proper traffic classification, and the like. For example, the network 100 may send a bearer activation request to establish a dedicated IMS bearer for a VoLTE call, a QoS-guaranteed bearer for high-definition video streaming, or a VPN-specific bearer restricting traffic to a corporate gateway. Alternatively, a bearer modification request may be sent during handover events, when updating a TFT due to a packet filter conflict, or when optimizing network resources.

[0057] At block 406, the UE 102 evaluates the received bearer activation or modification request to determine whether any syntactical errors exist in the packet filters before proceeding with further processing. Examples of syntactical errors include duplicate packet filter precedence values, incorrect formatting, a missing parameter in a definition of packet filter, or inconsistencies that could lead to bearer misconfigurations.

[0058] At block 408, if no syntactical errors are detected in the packet filters received in the EPS bearer activation or modification request, the UE 102 proceeds with the normal processing of the request. Normal processing includes, for example, validating the request parameters, updating the TFT, and configuring the appropriate packet filters for the dedicated bearer. If the request is for bearer activation, the UE 102 establishes a new dedicated bearer and applies the associated QoS settings. If the request is for bearer modification, the UE updates the TFT rules by adding, modifying, or replacing packet filters according to the network’s instructions. The UE 102 then sends an acknowledgment to the network 100, confirming that the bearer activation or modification has been successfully applied. The process then exits at block 426.

[0059] At block 410, if syntactical errors are detected in the packet filters, the UE 102 initiates the enhanced bearer resource management mechanism 136 to handle the error while preserving network stability. This mechanism 136 ensures that misconfigured packet filters do not cause unintended traffic disruptions, incorrect bearer assignments, or loss of active connections. At block 412, the UE 102, in response to detecting the syntactical errors, the UE 102 performs a packet filter deletion process and the enhanced bearer resource management mechanism 136implements the packet filter holding configuration 202. In at least some embodiments, the packet filter deletion process includes modifying a current packet filter configuration by removing only the specific packet filters identified as incorrect while ensuring that all other valid filters within the TFT remain unchanged. During this process, the UE 102 updates the TFT by permanently deleting the misconfigured packet filters that caused the syntactical error while retaining any previously stored and valid filters. The packet filter holding configuration 202 activates the temporary holding mechanism 208 to retain a copy of the existing or current packet filter configuration (e.g., packet filters and TFT configuration) priorto the modification. This ensures that valid configurations are not immediately deleted, allowing the UE 102 to evaluate the network response before making irreversible changes.

[0060] At block 414, the UE 102 then triggers a bearer resource modification request to the network 100, requesting deletion of the incorrect packet filters. This modification request is sent while the temporary holding mechanism 208 maintains the previously existing packet filter configuration, preventing any immediate disruptions to the PDN connection. At block 416, the UE 102 evaluates the response from the network 100 regarding the modification request. Based on the network response, the enhanced bearer resource management mechanism 136 determines the next course of action.

[0061] At block 418, if the network 100 accepts the bearer resource modification request initiated by the UE 102 to delete the erroneous packet filter, the UE 102 maintains the modified packet filter configuration and proceeds with normal operation. Since the erroneous packet filter was already removed locally at the time of detection, no further deletions are needed at this stage. The UE 102 ensures that all other valid filters within the TFT remain unchanged. With the network’s acceptance, the UE 102 finalizes the modification and acknowledges the successful update to the network 100. The temporary holding mechanism 208, which retained a copy of the prior packet filter configuration for potential restoration, is deactivated, as the network 100 has confirmed the update. The UE 102 then resumes normal operation, ensuring that the bearer configuration remains consistent with the network 100 while preserving PDN connectivity and preventing unnecessary service disruptions. The process then exits at block 426

[0062] At block 420, if the network 100 rejects the bearer resource modification request, the UE 102 determines whether the retained copy of the packet filter configuration still includes the erroneous packet filter. Since the UE 102 has already removed the erroneous packet filter locally, the UE 102 evaluates the stored configuration, which was retained prior to modification, to check if the stored configuration still includes the error. At block 422, if the retained copy no longer includes the erroneous packet filter (e.g., the network 100 has initiated a separate bearer resource modification or activation that corrected the issue), the UE 102 activates the synchronization-based modification configuration 206 and restores the retained copy of the packet filter configuration (e.g., the packet filters and TFT configuration) maintained by the temporary holding mechanism 208. This ensures that all necessary packet filters remain intact, preventing unnecessary service disruptions and maintaining seamless PDN connectivity. The process then exits at block 426.

[0063] At block 424, if the retained copy of the packet filter configuration still includes the erroneous packet filter, indicating that the issue has not been resolved either by the UE’s local removal or by a network-initiated modification, the UE 102 initiates the dynamic conflict resolution configuration 204. As part of this process, the UE 102 locally releases the dedicated bearer and triggers a mobility update procedure, such as a TAU, to synchronize its bearer resource configurations with the network 100. In at least some embodiments, if the network 100 initiates a deactivation or modification procedure that would remove a newly received TFT or packet filter, the UE 102 may reject the network-initiated deactivation and instead proceed with its own bearer resource modification request to delete an outdated TFT or packet filter. This approach ensures that the UE 102 maintains control over its bearer modifications while preventing unnecessary service disruptions. The mobility update procedure ensures that the UE 102 provides the network 100 with an updated bearer state, preventing inconsistencies between the UE 102 and the network 100. By aligning its stored packet filter settings with the network’s expected state, the UE 102 avoids potential service failures caused by unresolved conflicts. Once the UE 102 completes the update, the UE 102 proceeds with normal operation, ensuring uninterrupted connectivity for other active bearers. The process then exits at block 426.

[0064] By implementing the techniques described above, the UE 102 intelligently manages bearer modifications while maintaining connectivity for active bearers, ensuring uninterrupted PDN connectivity and minimizing service disruptions. The temporary holding mechanism 208 prevents unintended deletions of valid packet filters, allowing the UE 102 to evaluate network responses before making permanent changes. In scenarios where a dedicated bearer is to be released due to packet filter conflicts, the UE 102 ensures that other active bearers remain functional, preserving connectivity for applications, such as VoLTE calls, video streaming, and real-time gaming. These enhancements improve service reliability, optimize network resource utilization, and provide a seamless user experience, particularly in environments with frequent bearer reconfigurations and mobility events.

[0065] In some embodiments, certain aspects of the techniques described above may be implemented by one or more processors of a processing system executing software. The software comprises one or more sets of executable instructions stored or otherwise tangibly embodied on a non-transitory computer-readable storage medium. The software can include the instructions and certain data that, when executed by the one or more processors, manipulate the one or more processors to perform one or more aspects of the techniques described above. The non-transitory computer-readable storage medium can include, for example, a magnetic or optical disk storage device, solid state storage devices such as Flash memory, a cache, random access memory (RAM) or other non-volatile memory device or devices, and the like. The executable instructions stored on the non-transitory computer-readable storage medium may be in source code, assembly language code, object code, or other instruction format that is interpreted or otherwise executable by one or more processors.

[0066] A computer-readable storage medium may include any storage medium, or combination of storage media, accessible by a computer system during use to provide instructions and / or data to the computer system. Such storage media can include, but is not limited to, optical media (e.g., compact disc (CD), digital versatile disc (DVD), Blu-Ray disc), magnetic media (e.g., floppy disc , magnetic tape, or magnetic hard drive), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or Flash memory), or microelectromechanical systems (MEMS)-based storage media. The computer-readable storage medium may be embedded in the computing system (e.g., system RAM or ROM), fixedly attached to the computing system (e.g, a magnetic hard drive), removably attached to the computing system (e.g., an optical disc or Universal Serial Bus (USB)-based Flash memory), or coupled to the computer system via a wired or wireless network (e.g., network accessible storage (NAS)).

[0067] Note that not all of the activities or elements described above in the general description are required, that a portion of a specific activity or device may not be required, and that one or more further activities may be performed, or elements included, in addition to those described. Still further, the order in which activities is listed are not necessarily the order in which they are performed. Also, the concepts have been described with reference to specific embodiments. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present disclosure as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present disclosure.

[0068] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any feature(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature of any or all the claims. Moreover, the particular embodiments disclosed above are illustrative only, as the disclosed subject matter may be modified and practiced in different but equivalent manners apparent to those skilled in the art having the benefit of the teachings herein. No limitations are intended to the details of construction or design herein shown, other than as described in the claims below. It is therefore evident that the particular embodiments disclosed above may be altered or modified and all such variations are considered within the scope of the disclosed subject matter. Accordingly, the protection sought herein is as set forth in the claims below.

Claims

WHAT IS CLAIMED IS:

1. A method at a user equipment (UE) (102) of a cellular network (100), comprising:responsive to detecting an error in at least one packet filter received during a bearer configuration procedure with the cellular network, modifying a current packet filter configuration by removing the at least one packet filter while retaining a copy of the current packet filter configuration prior to modification;transmitting a bearer resource modification request to the cellular network to delete the at least one packet filter having the error; and responsive to the cellular network accepting the bearer resource modification request, maintaining the modified current packet filter configuration.

2. The method of claim 1 , wherein the current packet filter configuration comprises a Traffic Flow Template (TFT) that includes one or more packet filters, and the method further comprises:responsive to detecting the error in at least one packet filter, retaining a copy of the TFT prior to modifying the current packet filter configuration; and responsive to the cellular network accepting the bearer resource modification request, maintaining a modified TFT that excludes the at least one packet filter having the error.

3. The method of any one of claims 1 or 2, further comprising:responsive to the cellular network rejecting the bearer resource modification request, determining whether the retained copy of the current packet filter configuration still includes the at least one packet filter having the error;responsive to the retained copy of the current packet filter configuration still including the at least one packet filter having the error, initiating a conflict resolution procedure; andresponsive to the retained copy of the current packet filter configuration no longer including the at least one packet filter having the error, restoring the retained copy of the current packet filter configuration.

4. The method of claim 3, further comprising:responsive to the retained copy of the current packet filter configuration still including the at least one packet filter having the error, locally releasing a dedicated bearer and initiating a mobility update procedure to synchronize bearer resource configurations with the cellular network; andresponsive to the retained copy of the current packet filter configuration no longer including the at least one packet filter having the error, restoring the retained copy of the current packet filter configuration.

5. The method of claim 4, wherein locally releasing the dedicated bearer comprises:removing a bearer associated with the at least one packet filter having the error while maintaining connectivity for one or more other active bearers.

6. The method of claim 4, wherein the mobility update procedure comprises transmitting a signaling message to the cellular network to provide an updated packet filter configuration.

7. The method of claim 6, wherein transmitting the signaling message comprises:transmitting a Tracking Area Update request comprising information related to the updated packet filter configuration.

8. The method of any one of claims 1 to 7, wherein the error in the packet filter comprises a syntactical error that renders the packet filter invalid or unusable according to one or more predefined network rules.

9. The method of claim 8, wherein the syntactical error comprises at least one of:an incorrect format,an invalid precedence value, ora missing parameter in a definition of the at least one packet filter.

10. The method of any one of claims 1 to 10, wherein retaining the copy of the current packet filter configuration prior to modification comprises: retaining the current packet filter configuration via a temporary holdingmechanism.

11. The method of claim 10, further comprising:responsive to the cellular network accepting the bearer resource modification request, deactivating the temporary holding mechanism.

12. The method of any one of claims 1 to 11 , further comprising:responsive to detecting the error in the at least one packet filter, preventing deletion of one or more valid packet filters to maintain uninterrupted Packet Data Network connectivity.

13. A user equipment (102), comprising:one or more radio frequency (RF) modems (310) configured to wirelessly communicate with at least one network (100);one or more processors (314) coupled to the one or more RF modems; and at least one memory (320) storing executable instructions, the executable instructions configured to manipulate at least one of the one or more processors or the one or more RF modems to:responsive to a detected error in at least one packet filter received during a bearer configuration procedure, modifying a current packet filter configuration by removing the at least one packet filter while retaining a copy of the current packet filter configuration prior to modification;transmit a bearer resource modification request to the network to delete the at least one packet filter having the detected error; and responsive to the network accepting the bearer resource modification request, maintain the modified current packet filter configuration.

14. A computer-readable storage medium (320) embodying a set of executable instructions, the set of executable instructions to manipulate a user equipment device (102) to perform the method of any of claims 1 to 13.

Images