SMS Source Address Encoding for Non-Latin Characters

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current SMS technologies are limited in encoding free-form text source addresses, restricting them to the GSM default alphabet, which prevents the use of non-Latin characters and limits message length, especially in the TP-Originating-Address (TP-OA) field, making it impossible to reply to messages using this field as a destination address.

Innovation Solution

Implementing alternative encoding schemes such as UCS2 and National Language table-based encoding in the TP-OA field, or using new fields like the TP User Data Header, to allow for a wider character set and increased message length, enabling the use of non-Latin characters and additional encoding schemes like GSM default, UCS2, or National Language table-based encoding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If GSM default alphabet encoding is used in TP-OA field, then backwards compatibility is maintained, but character set is limited to Latin characters and message length is restricted

Engineering Contradiction:

Improvecharacter set supportVSAvoidmessage length

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent changes the encoding parameter from GSM default alphabet to UCS2 or National Language table-based encoding, enabling support for non-Latin characters while increasing message length capacity by over 50%

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The patent makes the TP-OA field multi-functional by enabling it to accommodate multiple encoding schemes (GSM default, UCS2, National Language tables), allowing the same field to serve both Latin and non-Latin character requirements

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If UCS2 encoding is used in TP-OA field, then non-Latin characters can be displayed, but message length increases by over 50% compared to GSM default alphabet

Engineering Contradiction:

Improvecharacter set supportVSAvoidmessage length

Core Design Contradiction:

Adaptability or versatilityVSLength of moving object

Solution Approach 1:

The patent applies parameter changes by switching from UCS2 to National Language table-based encoding, which reduces the message length requirement while maintaining support for non-Latin characters through language-specific optimized character sets

Inventive Principle:

Principle #35Parameter changes

3Ease of operation

If TP-OA field is used as destination address for replies, then message routing is enabled, but character encoding limitations prevent use of non-Latin characters

Engineering Contradiction:

Improvemessage routingVSAvoidcharacter set support

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent makes the TP-OA field universal by enabling it to function both as a routing address and as a display field supporting multiple character sets including non-Latin characters through UCS2 and National Language table-based encoding

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP2740244B1Character enablement in short message service

Publication Date: 2020.07.01 BLACKBERRY LTD

Figure 1a~1b
Figure 2a
Figure 2b

AI summary

A method is provided for encoding characters that specify a source address of an SMS message. The method comprises modifying a type of address field within an originating address field, the modification indicative of an encoding scheme used for the source address of the SMS message.