Markup Language Tags for Structured Data in Text Messages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current text messaging systems lack the ability to efficiently transmit and receive semi-structured or structured data using unstructured and untagged text message protocols, limiting their application in marketing and other data-intensive uses.

Innovation Solution

The use of Markup Language tags and structured or semi-structured data formats, such as comma delimited values and partitions, within text messages to enable hybrid real and virtual world marketing systems, including coupon exchanges, across various platforms and devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If unstructured text message protocols are used for transmission, then compatibility and ease of operation are improved, but the ability to transmit structured data and measurement precision are worsened

Engineering Contradiction:
Improveease of useVSAvoiddata structure capability
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The text message body is segmented into structured components using markup language tags (e.g., <item>, <category>, <value>). This segmentation allows unstructured text protocols to carry structured data by dividing the message into tagged elements that can be parsed and processed systematically, resolving the contradiction between ease of use and data structure capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Markup language tags serve as an intermediary layer between the unstructured text message protocol and the structured data requirements. These tags act as mediators that enable structured data transmission within unstructured text messages, allowing compatibility with existing protocols while providing the needed data organization and precision.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If structured data formats are implemented in text messages, then data transmission capability and productivity are improved, but device complexity increases

Engineering Contradiction:
Improvedata transmission efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The markup language tags are designed to be universal and multi-functional, working across different devices and platforms without requiring specialized processing hardware. The same tag structure can represent various types of structured data (coupons, product information, categories), reducing the need for device-specific implementations and lowering overall system complexity while maintaining high data transmission efficiency.

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

3Loss of information

If markup language tags are used within text messages, then data structure and information quality are improved, but message complexity and processing difficulty increase

Engineering Contradiction:
Improveinformation qualityVSAvoidmessage complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The markup language tags apply local quality by providing structured organization only where needed within the text message. Rather than requiring complete structural transformation of the entire message, specific portions can be tagged with markup elements (e.g., <item> for product items, <category> for categorization), preserving information quality in critical areas while keeping the overall message format simple and easy to process.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9680779B2System, method, and apparatus for storing, transmitting, receiving, and using structured data using un-structured text message bodies
Publication Date: 2017.06.13 MAROVETAB JACK L

AI summary

The present invention relates to the use of unstructured and untagged text message protocols to form a text message body that can be used to transmit and receive semi-structured, or structured text message bodies, which optionally may also use various, widely used Markup Languages. The semi-structure, or structure used within the text message body can be a format, such as, but not limited to, partitioning and/or comma delimited values, etc. The tagging for use with the text message body can be a protocol, such as, but not limited to, Extensible Markup Language (XML).