Data Using Device User ID Match Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to prevent sound data purchased by a user from being used by other users if the user ID is changed after the data is stored, leading to unauthorized use of the sound data.

Innovation Solution

A data using device and method that includes a data storage part, a user storage part, an authentication data acquisition part, a user acquisition part, a user determination part, an authentication storage processing part, a user deletion part, and a data use prohibition part, which ensures that sound data can only be used by the authorized user and prohibits use if the user ID is changed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If user ID is changed after sound data is stored in the electronic musical instrument, then the new user can access the device, but the previously purchased sound data can be used by the new user without authorization

Engineering Contradiction:
Improveuser change capabilityVSAvoiddata authorization security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary authentication by storing the user ID that was active at the time of data purchase in the authentication information storage unit. Before allowing data usage, the system checks whether the currently registered user ID matches the stored authentication user ID. This preliminary action ensures that even if a user changes the registered user ID, the previously purchased data remains protected because the authentication check occurs before data access is granted.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If authentication check is performed for every data access, then data security is maintained, but system complexity and processing time increase

Engineering Contradiction:
Improvedata securityVSAvoidauthentication process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication information is pre-stored in the authentication information storage unit during the data purchase process. This preliminary storage of authentication data eliminates the need for complex real-time authentication computations during data access, reducing processing time while maintaining security through the match check between current and stored user IDs.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If sound data is encrypted with user ID, then data can be securely transmitted from server, but data cannot be used if user ID is changed after storage

Engineering Contradiction:
Improvedata transmission securityVSAvoiduser flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary encryption of sound data with the user ID during the purchase and download process. The encrypted data is stored in the sound data storage unit along with the authentication information (original user ID). When the user changes their registered user ID, the system checks the stored authentication information to verify ownership, allowing the original purchaser to continue using their data even with a changed user ID, while preventing unauthorized use by new users.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3905075B1Data using device, data using program, and data using method
Publication Date: 2025.06.11 ROLAND CORP
  • EP3905075B1 patent drawingFigure 1
  • EP3905075B1 patent drawingFigure 2
  • EP3905075B1 patent drawingFigure 3(a)~3(c)

AI summary

A data using device (50) includes: a data storage part (52c) storing pieces of data used for the predetermined process; a user storage part (52b) storing a first user identification information; an authentication data acquisition part (S12); a user acquisition part (S12) acquiring a second user identification information from the external apparatus; a user determination part (S14); an authentication storage processing part (S16) storing the authentication data such that the authentication data is available for the predetermined process when the user determination part determines that the first and second user identification information match each other or when the first user identification information is not stored; a user deletion part (S15) deleting or instructing a user to delete the first user identification information when the first and second user identification information do not match each other; and a data use prohibition part (S4) prohibiting use of the authentication data when the first user identification information is deleted.