Smart Terminal Event Recording Script Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of smart terminals face inconvenience due to the need for multiple complicated operations when performing tasks, such as checking weather information, which can be time-consuming and annoying.

Innovation Solution

A method is introduced to record events generated for performing tasks in a smart terminal, allowing users to activate an event recording mode, record these events, assign an identification code, and store them in an XML script format, enabling subsequent retrieval and execution with minimal user input.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users perform tasks through multiple complicated operations, then the task can be completed with precise control, but the operation time and user effort increase significantly

Engineering Contradiction:
Improveuser operation simplicityVSAvoidtask execution time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system automatically records user operations and generates event scripts in advance, storing them for future execution. This preliminary action eliminates the need for users to repeat the same complex operations manually, thereby reducing both user effort and execution time for recurring tasks.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the user's operation sequence in the form of an event script (XML format). This copied script can be stored and re-executed multiple times without requiring the user to perform the original complex operations again, thus improving ease of operation and reducing time loss.

Inventive Principle:
Principle #26Copying

2Ease of operation

If multiple complicated operations are required for task execution, then precise task control is achieved, but the device complexity increases

Engineering Contradiction:
Improvetask execution simplicityVSAvoidoperation sequence management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system extracts the essential operation sequence from user interactions and isolates it as a separate event script (XML file). This extracted script can be stored, managed, and executed independently, reducing the complexity burden on the main system while maintaining precise task control.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system transforms the operation sequence into a standardized parameter format (XML script with identification codes). This parameter transformation simplifies the management and execution of complex operations by converting them into structured, machine-readable data that can be easily stored and retrieved.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If events are recorded in detailed XML script format, then event retrieval and reproduction accuracy improve, but the data storage requirements increase

Engineering Contradiction:
Improveevent recording accuracyVSAvoiddata storage volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system changes the parameter representation of recorded events into a compact XML format with standardized elements and identification codes. This parameter transformation maintains high recording accuracy for event reproduction while reducing storage requirements through efficient data structuring and compression.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9870235B2Recording events generated for performing a task through user equipment
Publication Date: 2018.01.16 KT CORP
  • US9870235B2 patent drawing
  • US9870235B2 patent drawing
  • US9870235B2 patent drawing

AI summary

Described embodiments provide for a method of recording events generated for performing a task through user equipment. In the method, an activation input may be received for activating an event recording mode. Upon the activation of the event recording mode, events generated in the user equipment may be recorded. Upon the receipt of an inactivation input for inactivating the event recording mode, an identification code may be assigned to a set of the recorded events. The set of the generated events may be stored with the assigned identification code.