Service Request Data Anonymization With Consistent Token Replacement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data anonymization techniques fail to anonymize sensitive information in service request documents without destroying the internal structure or exposing customer networks to malicious threats, and are not scalable for diverse network, location, and user data.

Innovation Solution

An anonymization server employs a combination of rule-based and deep learning techniques, including data preprocessing, tagging, collision resolution, and replacement logic to identify and identically replace repeated sensitive information, preserving the internal consistency of the documents.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Object-affected harmful factors

If conventional data anonymization techniques are used, then sensitive information is anonymized, but the internal structure of the document is destroyed

Engineering Contradiction:
Improvesensitive information exposureVSAvoidinternal structure consistency
Core Design Contradiction:
Object-affected harmful factorsVSStability of the object's composition

Solution Approach 1:

The system segments the anonymization process into distinct stages: identifying repeated sensitive information sequences, tagging them with unique identifiers, and replacing them with anonymized tokens. This segmentation allows the system to selectively anonymize only the sensitive portions while leaving the rest of the document structure intact.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates anonymized copies of the original document by replacing sensitive information sequences with standardized anonymized tokens. This copying approach preserves the document's internal structure and relationships while eliminating sensitive data, allowing the anonymized version to maintain usability for analysis purposes.

Inventive Principle:
Principle #26Copying

2Object-affected harmful factors

If conventional data anonymization techniques are used, then sensitive information is anonymized, but customer networks are exposed to malicious threats

Engineering Contradiction:
Improvesensitive information exposureVSAvoidnetwork security
Core Design Contradiction:
Object-affected harmful factorsVSReliability

Solution Approach 1:

The system performs preliminary anonymization of service request documents before they are stored or shared. By proactively identifying and anonymizing sensitive information sequences in advance, the system prevents potential security threats before they can materialize, ensuring that even if documents are accessed, the sensitive information is already protected.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If conventional data anonymization techniques are used, then processing is simple, but scalability for diverse network, location, and user data is limited

Engineering Contradiction:
Improveanonymization process complexityVSAvoidscalability for diverse data
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system employs a universal anonymization approach that identifies repeated information sequences regardless of their content or context. The same tagging and replacement mechanism works across diverse data types including network information, location data, and user information, making the system scalable and adaptable without requiring data-type-specific processing logic.

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

Data Source

PatentUS12443754B2Automated data anonymization
Publication Date: 2025.10.14 CISCO TECHNOLOGY INC
  • US12443754B2 patent drawing
  • US12443754B2 patent drawing
  • US12443754B2 patent drawing

AI summary

In one example embodiment, a server that is in communication with a network that includes a plurality of network elements obtains, from the network, a service request record that includes sensitive information related to at least one of the plurality of network elements. The server parses the service request record to determine that the service request record includes a sequence of characters that is repeated in the service request record, and tags the sequence of characters as a particular sensitive information type. Based on the tagging, the server identically replaces the sequence of characters so as to preserve an internal consistency of the service request record. After identically replacing the sequence of characters, the server publishes the service request record for analysis without revealing the sequence of characters.