Cross-Domain Jump Login State Maintenance via Identifier Intermediary

Solution Overview

Problem

Conventional cross-domain jump methods fail to maintain user login states when switching between websites, leading to increased user operation time and power consumption, especially on mobile devices with limited battery life.

Innovation Solution

A method involving a browser, a first domain name server, and a second domain name server that utilize a cross-domain user identifier to maintain user login states by generating and transmitting a second identifier, allowing seamless transitions without requiring re-login, thereby reducing user operation time and power consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional cross-domain jump method is used, then user can switch between websites, but user login state cannot be maintained and operation time increases

Engineering Contradiction:

Improveuser operation timeVSAvoidre-login time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by generating and transmitting the cross-domain user identifier before the actual cross-domain jump occurs. The browser obtains the cross-domain user identifier from the first domain name server in advance, which contains encoded login state information. This preliminary preparation enables the second domain name server to recognize and maintain the user's login state without requiring re-login, thus resolving the time loss contradiction.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The cross-domain user identifier acts as an intermediary that carries login state information between different domain name servers. Instead of direct communication between domains or repeated authentication, the intermediary identifier encapsulates necessary authentication data, allowing the second domain name server to verify and maintain login state efficiently, thereby reducing operation time and improving ease of operation.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Use of energy by moving object

If conventional cross-domain jump method is used, then website switching is possible, but power consumption increases due to repeated login operations

Engineering Contradiction:

Improveterminal power consumptionVSAvoidbattery life

Core Design Contradiction:

Use of energy by moving objectVSProductivity

Solution Approach 1:

The system performs preliminary actions by generating and transmitting the cross-domain user identifier before the actual cross-domain jump occurs. The browser obtains the cross-domain user identifier from the first domain name server in advance, which contains encoded login state information. This preliminary preparation enables the second domain name server to recognize and maintain the user's login state without requiring re-login, thus resolving the time loss contradiction.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The cross-domain user identifier acts as an intermediary that carries login state information between different domain name servers. Instead of direct communication between domains or repeated authentication, the intermediary identifier encapsulates necessary authentication data, allowing the second domain name server to verify and maintain login state efficiently, thereby reducing operation time and improving ease of operation.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If cross-domain user identifier is generated and transmitted, then login state can be maintained, but system complexity increases

Engineering Contradiction:

Improvelogin state maintenanceVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The cross-domain user identifier serves multiple functions simultaneously: it acts as a unique user identifier, carries encoded login state information, and enables authentication across different domain name servers. This multi-functionality reduces the need for separate mechanisms for each function, thereby maintaining reliability while minimizing the increase in system complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system changes the parameter representation by encoding login state information within the cross-domain user identifier itself rather than using separate authentication mechanisms. This parameter integration simplifies the overall system architecture while ensuring reliable login state maintenance across domains.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentEP2874074B1Method for implementing cross-domain jump, browser, and domain name server

Publication Date: 2019.02.27 TENCENT TECHNOLOGY (SHENZHEN) CO LTD

Figure 1
Figure 2
Figure 3

AI summary

A method for implementing cross-domain jump includes: a second domain name server obtaining a cross-domain jump request of jumping from a first domain name to a second domain name sent by a browser, the request including a cross-domain user identifier corresponding to a first identifier of a user in the first domain name; the second domain name server obtaining a second identifier of the user in the second domain name corresponding to the user identifier, and generating a login state of the user in the second domain name according to the second identifier. The second domain name server recognizes identity of the user according to the second identifier, so that user does not need to log in while still maintaining the login state. Therefore, operation convenience of the user is improved. Further, a browser, a first domain name server and a second domain name server are provided.