Wireless Device Connection Rejection Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Wireless communication systems face challenges in efficiently handling connection rejections, leading to poor user experience due to repeated rejections during times of congestion or denial of service attacks, which can result in significant rates of connection rejections and service denial.

Innovation Solution

Implementing enhanced connection rejection handling techniques in wireless devices, including randomizing barring timers, prioritizing connections, and reporting congestion conditions to networks, to manage barring conditions and distribute connection requests more evenly, thereby reducing congestion and susceptibility to denial of service attacks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If connection requests are sent during congestion, then service availability is improved, but connection rejection rate increases

Engineering Contradiction:
Improveservice availabilityVSAvoidconnection rejection rate
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The wireless device performs preliminary actions by detecting congestion indicators before sending connection requests. When congestion is detected, the device implements barring to prevent sending requests during high-load periods, thereby avoiding rejections and maintaining service availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The connection request sending behavior is made dynamic through congestion-based barring. The device adjusts its connection attempts based on real-time network conditions, implementing barring when congestion is detected and allowing requests when conditions are favorable, optimizing both service availability and rejection rate.

Inventive Principle:
Principle #15Dynamics

2Object-affected harmful factors

If barring is implemented to reduce congestion, then connection rejection rate decreases, but service access delay increases

Engineering Contradiction:
Improveconnection rejection rateVSAvoidservice access delay
Core Design Contradiction:
Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The device implements barring as a preliminary measure when congestion is detected, preventing multiple rejections. The barring timer is set based on congestion severity, allowing the device to resume connection attempts after a controlled delay, balancing rejection reduction with access speed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The barring duration parameter is dynamically adjusted based on congestion indicators. When severe congestion is detected, longer barring periods are applied to reduce rejection rates. When mild congestion occurs, shorter barring periods maintain faster access, optimizing the trade-off between rejection reduction and access delay.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If multiple connection requests are sent to overcome rejections, then service availability is improved, but network load increases

Engineering Contradiction:
Improveservice availabilityVSAvoidnetwork load
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The device performs preliminary congestion detection before sending connection requests. By identifying network congestion in advance, the device can implement barring to prevent sending multiple requests that would increase network load, while still maintaining service availability through selective request transmission.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The device uses feedback from congestion indicators to control connection request transmission. When congestion is detected, barring is implemented to reduce the quantity of connection requests sent to the network. This feedback mechanism balances service availability with network load management, preventing excessive request flooding.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11096232B2Enhancements to connection rejection procedures
Publication Date: 2021.08.17 APPLE INC
  • US11096232B2 patent drawing
  • US11096232B2 patent drawing
  • US11096232B2 patent drawing

AI summary

This disclosure relates to techniques for efficiently handling connection rejections. A wireless device may detect barring conditions in response to receiving one or more connection rejections. The wireless device may bar one or more connections based on the barring conditions, and may attempt to access network services over one or more other connections.