Browser Error Interface for Webpage Access Failure Diagnosis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users experience confusion due to vague error causes of webpage access failures in browsers, leading to a diminished user experience.

Innovation Solution

A method and apparatus that provide a detailed error prompt interface displaying browser, network, and webpage identifiers, along with error descriptions and buttons to guide users in resolving the error causes, including local and cloud diagnostics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If a common error prompt page is presented to indicate webpage access failure, then the user is notified of the error, but the user cannot obtain accurate error cause information leading to confusion

Engineering Contradiction:
Improveerror cause informationVSAvoiderror prompt interface
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The error prompt interface is segmented into multiple independent modules: error segment display area showing browser/network/webpage identifiers, error description area providing detailed error cause information, and operation button area offering actionable solutions. This segmentation allows the system to present comprehensive error information in an organized manner while maintaining interface clarity and usability.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If detailed error information and multiple identifiers are displayed, then accurate error location is achieved, but the interface complexity increases

Engineering Contradiction:
Improveerror location accuracyVSAvoiderror prompt interface
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The interface is divided into distinct segments (error segment display area, error description area, operation button area) that organize complex error information into manageable sections. Each segment handles specific information types, making the overall complex error prompt interface easier to navigate and understand while maintaining high error location accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The error prompt interface acts as an intermediary between the complex error diagnosis system and the user. It translates technical error information into user-friendly presentations with clear identifiers and actionable guidance, reducing the cognitive load on users while providing comprehensive error location capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If the user is provided with actionable buttons to resolve errors, then user experience is improved, but the system complexity increases

Engineering Contradiction:
Improveerror resolution processVSAvoiderror prompt interface
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The error prompt interface incorporates operation buttons that enable users to self-resolve common errors without requiring technical support or complex manual intervention. The buttons provide direct actions (such as refreshing the page, checking network settings, or contacting the website) that users can execute independently, improving ease of operation while the system handles the complexity of error diagnosis and solution generation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12554569B2Method for processing webpage access exception and related apparatus
Publication Date: 2026.02.17 HUAWEI TECH CO LTD
  • US12554569B2 patent drawing
  • US12554569B2 patent drawing
  • US12554569B2 patent drawing

AI summary

In the method, a terminal device receives a first input operation; the terminal device accesses, in response to the first input operation, a first webpage indicated by the first input operation; after failing to access the first webpage, the terminal device determines that an error cause of a webpage access failure includes a first error cause; and the terminal device displays a first error prompt interface; the error segment display area includes a browser identifier, a network identifier, and a webpage identifier, a display status of a first identifier indicates whether the first error cause is an error cause corresponding to the first identifier, and the first identifier is any one of the three identifiers; and the first button is used to trigger the terminal device to perform a first operation corresponding to the first error cause.