Client-Side Schema Translation in Data Processing Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional client-side encoding in data processing systems requires all nodes to use the same schema for structuring records, which is inefficient and impractical for disparate types of nodes, complicating the rollout of new system capabilities and software versions.

Innovation Solution

A server in the data processing system stores database records with schema information, allowing clients to determine and translate records into their native schema, enabling different types of clients to use different schemas for processing records.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If all nodes use the same schema for structuring records, then data consistency is maintained, but system adaptability and ease of rolling out new capabilities are reduced

Engineering Contradiction:

Improveschema flexibilityVSAvoiddata consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the schema information from the data records themselves. Each record carries its own schema identifier, allowing different schema versions to coexist in the same system without requiring all nodes to use the same schema. This enables gradual rollout of new capabilities while maintaining data consistency within each schema version.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces schema identifiers as an intermediary between data records and processing nodes. These identifiers allow nodes to determine which schema version applies to each record, enabling flexible schema management while maintaining reliability through proper schema-based validation and processing.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If client-side encoding is implemented, then server computational burden is reduced, but schema management complexity increases

Engineering Contradiction:

Improveserver processing efficiencyVSAvoidschema management complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by having clients encode records with their schema identifiers attached before sending to the server. This preliminary tagging of records with schema information allows the server to efficiently process encoded records without needing to perform decoding, while the schema management complexity is handled by clients who already have schema definitions available.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11297139B2Method and apparatus for client side encoding in a data processing system

Publication Date: 2022.04.05 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

In one aspect, a server in a data processing system stores database records in association with schema information identifying the particular schema by which the stored records are structured. Storing the schema information advantageously enables the node to provide schema information in association with requested records, enabling clients to determine the schema(s) associated with requested records. As a further advantage, the server in one or more embodiments operates as a central repository of schema definitions. Consequently, any given client requesting a record of a given record type can retrieve the schema used for structuring that record and translate the received record into the schema used by the requesting node for records of that type. Thus, disparate types of clients, or clients running different software versions, may use a central repository of data records of a given type, even where the clients use different schemas for processing such records.