Secondary Account Sensitive Operation Verification via Primary Supervision

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods require all sensitive operations to be performed with a primary account, leading to inefficiencies and delays due to the need for multiple operations to be managed by the primary account, which can hinder timely processing and compromise security.

Innovation Solution

An information interaction method and system that allows sensitive operations to be performed with a secondary account under the supervision of a primary account, utilizing a server to receive pre-performing messages from secondary accounts, determine corresponding primary account identifiers, send verification requests, and instruct secondary accounts to perform or cancel operations based on verification results.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sensitive operations are performed with a primary account, then security is maintained, but processing timeliness deteriorates due to the burden of managing multiple operations

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing timeliness
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent divides account operations into two segments: sensitive operations that require primary account authorization and non-sensitive operations that can be performed by secondary accounts. This segmentation allows secondary accounts to handle routine tasks independently, improving processing timeliness while the primary account maintains security oversight for critical operations through pre-authorization mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a pre-authorization mechanism as an intermediary between the primary account and secondary account operations. The system stores pre-authorization information that allows secondary accounts to perform sensitive operations without real-time primary account intervention, thus improving timeliness while maintaining security through prior authorization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If all sensitive operations require primary account involvement, then security is ensured, but operational efficiency deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidoperational efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements pre-authorization of sensitive operations in advance. The primary account authorizes specific sensitive operations beforehand, and the system stores these authorizations. Secondary accounts can then execute pre-authorized operations without requiring real-time primary account involvement, significantly improving operational efficiency while maintaining security through prior authorization.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables secondary accounts to independently perform both non-sensitive operations and pre-authorized sensitive operations without continuous primary account intervention. This self-service capability for secondary accounts improves operational efficiency while the primary account maintains security through initial authorization and system-level controls.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10476889B2Information interaction method, apparatus and system
Publication Date: 2019.11.12 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US10476889B2 patent drawing
  • US10476889B2 patent drawing
  • US10476889B2 patent drawing

AI summary

An information interaction method, apparatus and system are provided. A sensitive operation pre-performing message is received from a terminal where a secondary account is located. The sensitive operation pre-performing message may carry a secondary account identifier. Based on the secondary account identifier and a pre-stored association relationship between a primary account identifier and the secondary account identifier, the primary account identifier corresponding to the secondary account identifier may be determined. Based on the determined primary account identifier, a sensitive operation verification request message may be sent to a terminal where the primary account is located. A verification result information may be received from the terminal where the primary account is located. Based on the verification result information, sensitive operation instruction information may be sent to the terminal where the secondary account is located to instruct the terminal where the secondary account is located to perform or cancel the sensitive operation.