HTTP-URI Error Recovery in User Equipment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In IP Multimedia Subsystem (IMS) environments, user equipment (UE) faces challenges in detecting and resolving Hyper Text Transfer Protocol (HTTP) Uniform Resource Identifier (URI) character encoding errors, particularly due to varying operator configurations, leading to inefficiencies in error recognition and resolution.

Innovation Solution

The UE employs an HTTP-URI error-recovery method involving the transmission of first and second HTTP requests with different URI encoding schemes, specifically using percent-encoding or not, to identify and correct URI character encoding errors, enabling rapid recovery from errors such as Bad Request, Not Found, or Conflict responses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the UE uses a single URI encoding scheme (percent-encoding) to transmit HTTP requests, then the requests can be transmitted in a standardized format, but URI character encoding errors occur when different operators have different configurations in the application server

Engineering Contradiction:
ImproveURI encoding scheme compatibilityVSAvoidHTTP request success rate
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic switching between different URI encoding schemes (percent-encoding and non-percent-encoding) based on the response received from the application server. When a percent-encoded request returns an error, the system automatically switches to non-percent-encoding for subsequent requests, and vice versa. This dynamic adaptation resolves the contradiction by making the encoding scheme flexible rather than fixed, allowing compatibility with different operator configurations while maintaining reliable communication.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the encoding parameter of the URI based on the operational conditions. By detecting errors related to URI encoding and switching between percent-encoding and non-percent-encoding modes, the system adjusts the encoding parameter to match the application server's configuration expectations. This parameter change enables the system to adapt to different operator configurations and resolve encoding errors, improving both compatibility and reliability.

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If the UE detects URI character encoding errors, then the issues can be identified, but it takes much effort and time to recognize and fix the issue due to varying operator configurations

Engineering Contradiction:
ImproveError detection accuracyVSAvoidError recovery time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements a feedback mechanism where the system monitors the responses from the application server to detect URI encoding errors. When an error response is received, the system automatically feeds this information back into the request generation process by switching the encoding scheme. This closed-loop feedback enables precise error detection and immediate corrective action, eliminating the need for manual error recognition and significantly reducing error recovery time.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs self-diagnosis and self-correction by automatically detecting URI encoding errors through response monitoring and autonomously switching between encoding schemes without requiring manual intervention. This self-service capability allows the system to identify and fix encoding issues independently, reducing both the effort and time required for error recovery while maintaining precise error detection.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If the UE transmits HTTP requests with percent-encoding for specific characters, then the requests follow RFC and 3GPP standards, but encoding errors occur with certain application server configurations

Engineering Contradiction:
ImproveStandard complianceVSAvoidRequest transmission success
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system dynamically adjusts the encoding approach based on the application server's configuration. It starts with percent-encoding to maintain standard compliance, but when errors occur, it automatically switches to non-percent-encoding. This dynamic behavior allows the system to follow RFC and 3GPP standards when appropriate while adapting to specific server configurations that may not expect percent-encoding, thereby maintaining both standard compliance and transmission success.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the encoding parameter of URI characters based on the operational context and server response. By switching between percent-encoding and non-percent-encoding modes, the system maintains standard compliance through percent-encoding when it works, but transitions to alternative encoding when server configuration causes errors. This parameter adjustment resolves the contradiction between adhering to standards and ensuring successful transmission across different operator environments.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12093126B2Http-URI error-recovery method and user equipment thereof
Publication Date: 2024.09.17 MEDIATEK SINGAPORE PTE LTD
  • US12093126B2 patent drawing
  • US12093126B2 patent drawing
  • US12093126B2 patent drawing

AI summary

A Hyper Text Transfer Protocol (HTTP)-Uniform Resource Identifier (URI) error-recovery method is provided. The HTTP-URI error-recovery method is applied in user equipment (UE). The HTTP-URI error-recovery method includes the following steps. The UE transmits a first HTTP request with a first URI encoding scheme to an application server through an interface. Then, the UE receives a specific error response corresponding to the first HTTP request from the application server. Then, the UE transmits a second HTTP request with a second encoding scheme to the application server based on the specific error response.