RFID Tag Firmware Customization for Mainframe Service Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mainframe computer systems face challenges in securely and efficiently allowing authorized users to perform service procedures, as they often require physical presence and may not adapt to user-specific attributes such as language, disabilities, or physical limitations, leading to potential data loss, system degradation, or invalidation of service contracts.

Innovation Solution

A system that uses a unique RFID tag to authenticate and gather attribute data from authorized users, adapting the service procedure instructions and system components to accommodate individual user needs, such as language, experience level, and physical capabilities, ensuring secure access and efficient service execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system provides access based on authentication using user identification, password, and physical RFID tag, then security is improved and only authorized users can access service procedures, but the system cannot adapt to user-specific attributes such as language, disabilities, or physical limitations

Engineering Contradiction:
ImprovesecurityVSAvoiduser customization
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The authentication system is segmented into two independent parts: (1) security authentication using RFID tag and credentials, and (2) attribute-based customization using additional data fields in the RFID tag. This allows the system to separately handle security verification and user adaptation without interfering with each other.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The RFID tag is designed to serve multiple functions: it stores both authentication credentials (for security verification) and user attribute data (for customization). This multi-functional approach allows a single device to enable both secure access and personalized service procedure display.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If the system displays standard service procedure instructions to all users, then implementation is simple and fast, but users with specific needs such as color blindness, language preferences, or physical limitations cannot efficiently perform service procedures

Engineering Contradiction:
Improveservice procedure efficiencyVSAvoidinstruction customization complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

User attribute data is pre-stored in the RFID tag before the service procedure begins. The system automatically retrieves and applies these attributes at the start of the service procedure, eliminating the need for real-time customization decisions or manual user input during the procedure execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system automatically configures the service procedure display based on user attributes stored in the RFID tag without requiring manual intervention. The firmware reads the attribute data and autonomously adjusts the interface, making the customization process transparent and self-executing.

Inventive Principle:
Principle #25Self-service

3Reliability

If the system requires physical presence at the mainframe location for service procedures, then security is maintained, but authorized users cannot remotely diagnose or repair the system

Engineering Contradiction:
ImprovesecurityVSAvoidsystem downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The RFID tag acts as an intermediary that carries the user's authentication credentials and attribute data. This portable mediator enables the user to be physically present at the system location without requiring the system to be at a fixed location, facilitating remote servicing while maintaining security through the tag-based authentication.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If the system provides detailed service procedure instructions to all users, then users with low experience level can perform procedures, but experienced users face information overload and reduced efficiency

Engineering Contradiction:
Improveaccessibility for inexperienced usersVSAvoidservice procedure speed
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The service procedure instructions are customized based on user experience level stored in the RFID tag. Inexperienced users receive detailed, step-by-step instructions with comprehensive guidance, while experienced users receive condensed, high-level instructions. This local adaptation of information quality optimizes both accessibility and efficiency for different user groups.

Inventive Principle:
Principle #3Local quality

Applied Scientific Principles

This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.

Function Achieved in This Case

The system ensures secure access and efficient service procedures by customizing instructions and system interactions based on user attributes, reducing downtime and maintaining service contract validity by ensuring only authorized users can perform service procedures.

Implementation Method 1

an authorized user may run... a physical radio frequency identification (RFID) tag... The tag includes authentication data and attribute data for the user... a tag reader that reads the authentication data and the attribute data from the tag

Methodology Applied
Scientific EffectRadio frequency identification (RFID):

Data Source

PatentUS10430567B2Customizable firmware based on access attributes
Publication Date: 2019.10.01 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10430567B2 patent drawing
  • US10430567B2 patent drawing
  • US10430567B2 patent drawing

AI summary

Embodiments include validating a user for performing a service procedure for a system and customizing the system for the user for the service procedure. An example computer-implemented method includes validating authorization of the user based on authentication data from a tag uniquely identifying the user. The method further includes receiving attribute data for the user from the tag. The method further includes generating and/or adapting a set of service procedure instructions that are customized for the user based on the attribute data. The method further includes displaying the set of service procedure instructions that are customized for the user.