Glossary
Comprehensive glossary of mobile industry terminology
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Short Message Peer-to-Peer Protocol (SMPP) is an open message transfer protocol that enables users to interact with an SMSC. The protocol defines the information which needs to be exchanged between the user and the SMSC and the operations associated with the exchange of SMS messages. Every request made using SMPP has an associated response.   It is used primarily for connecting third-party services with SMSCs to enable various types of automated SMS services.   Refer to the SMPP documentation on our developer documentation site for more information.
View article
A Short Message Service – Mobile Originating (SMS-MO) is an SMS sent from the SIM card.
View article
A Short Message Service – Mobile Terminating (SMS-MT) is an SMS received by the SIM card.
View article
Located in two geo-redundant data center sites in the Washington DC area and Chicago – this Digital Interconnect messaging hub processes all national US traffic (SMS traffic between carriers in the USA and Canada), along with some international traffic that is typically from US service providers / operators to operators outside of the USA/Canada marketplace.
View article
Short Message Service (SMS) - more commonly referred to as text messaging. An SMS message is 160 characters long. The two most common forms of SMS are Person-to-Person (P2P), where messages are exchanged between two mobile phones and Application-to-Person (A2P), where messages originate from a system or application and are sent to a mobile phone.   SMS is currently one of the most popular messaging formats for sending text messages. As well as interpersonal communication, the ubiquity of SMS makes it ideal for automated communications and marketing campaigns.  The roots of SMS go back to the 1980s, when two German engineers began to pioneer a telephone messaging format that was compatible with the GSM standards of the time.    The Rise and Rise of SMS Messaging On 3 rd December 1992, a software engineer called Neil Papworth sent the message “Merry Christmas” to his colleague. This might not sound like a big deal but it was. His message was the first SMS, and it heralded the dawn of a new era in mobile communications.  Neil’s first message precipitated an avalanche in mobile messaging.  Just a year after it was sent, SMS was popular enough for Nokia to introduce a “beep” feature letting users know when they had received a message. In 1999 a new milestone was reached when users were able to exchange messages on multiple networks.   By the 2010s, hundreds of thousands of messages were being sent every second! SMS texting had become as natural to people as saying hi in the supermarket. The distinctive “text speak” that SMS’s 160 character limit gave birth to has infiltrated our language, with abbreviations like LOL and LMAO common parts of everyday speech.  Because of this, many companies view SMS as a crucial marketing campaign tool. Nissan used it to effectively reboost their customer engagement and studies have found that text is the marketing medium most trusted by customers.  Now that we’re comfortably into the 21 st century, SMS is more popular than ever, and its importance to digital marketing can only increase.   Automated SMS Message Campaigns Neil Papworth sent the first text from a computer, with a view to developing SMS services for Vodafone. In 1992 he was alone in his achievement. Now, developers all over the world create apps enabling clients and businesses to launch automated SMS campaigns. To do this effectively, they need access to API resources and messaging platforms that can send and receive high volumes of SMS messages. Sinch specializes in providing exactly this capability to clients. Developers wanting to use Sinch for SMS services have two main options: SMS APIs SMS SDKs.   Using SMS APIs Sinch API platforms provide a comprehensive set of resources that clients can integrate into their applications. These add functionality such as sending SMS campaigns, receiving incoming messages and accessing delivery reports enabling customers to evaluate campaign success. Sinch has the following SMS related APIs: SMS – API dedicated to sending and receiving SMS messages. It’s useful for orchestrating SMS campaigns. RCS – API enabling clients to send rich and engaging mobile campaigns that can default to SMS when messaging non-RCS handsets. Conversation – integrates SMS and RCS capabilities into a single API Numbers – API allowing clients to look up and search for mobile numbers. This is useful for enhancing SMS campaigns. To help clients use our resources, Sinch provides extensive documentation in the form of API references.   Using SDKs SDKs provide a language specific way of integrating API resources into an application that obviates the need to work with raw endpoints. Sinch currently has SDKs in the following languages: Python .NET. Take a look at the Sinch SMS Product page to learn more about our SMS products, or click here to sign up to our self-service portal and get started today.
View article
Short Message Service Center (SMSC) is a server connected to an SS7 Network whose role is to send and receive messages to and from recipient handsets. Often it operates in a “store and forward” configuration, but some carriers operate in a “forward only” or a “forward and store” configuration.
View article
The date/time the CONNECTION Process in the CONNECTION SERVER processed the MT.
View article
Simple Mail Transfer Protocol (SMTP) is an internet standard communication protocol for electronic mail transmission. Mail servers and other message transferagents use SMTP to send and receive mail messages.
View article
Simple Object Access Protocol (SOAP) A protocol used to exchange XML encoded messages over networks. Also referred to as SOAP.
View article
This refers to non-SMS enabled messaging apps such as WhatsApp, WeChat, Line, Tango, Facebook Messenger, and the many other messaging apps in the marketplace today.
View article
Spam is unsolicited, usually commercial or fraudulent mobile messages (SMS, MMS, social), typically sent to a large number of recipients.
View article
Signalling System 7 (SS7) is how the majority of the world’s mobile networks communicate with each other. It is a set of telephony protocols enabling the transmission of voice, data, control/session management information, and of course SMS. The SS7 protocol has layers based on the OSI (Open Systems Interchange) model. The MAP (Mobile Application Part) layer provides the functionality required for SMS transmission. The SMSC, HLR, VLR and MSC communicate together over the SS7 network utilizing MAP commands.
View article
Programs or messages that result in only normal text messaging charges being applied to the mobile subscriber’s wireless bill or that result in messages being deducted from a subscriber’s messaging plan allowance.
View article
A program that requires single opt-in where the mobile subscriber is billed standard SMS rates as per the subscriber’s mobile plan.
View article
The delivery status of a MT message according to the timestamps received from servers in the MT delivery chain.
View article
SIM Tool Kit, or Service Text Messages (the functionality is the same). It is sometimes also called the SIM Application Toolkit. These are binary SMS messages sent to the phone, mainly by Operators but also by our customers, to update the SIM card and/or the phone with service-related information. Examples where STKs are used: - Enable the phone for Internet connectivity - Update prepaid phones - Activate new phones/SIM cards - Upgrade phone ROM/Flash memory software.
View article
In SMPP terms, a “store” is an internal holding place for messages that are unable to be routed either to a supplier/carrier, or to the customer. The message sits in the store until they can be delivered or until they expire.
View article
A Mobile Subscriber is a person who has a mobile phone account with a mobile operator.
View article
Sinch subprojects are a way to group resources together under a parent project.  They can either have separate API credentials or the same credentials as the parent project.
View article
Sinch Voice Application Markup Language (SVAML) is a command language to inform legacy Sinch (Voice) SDKs, it works on the same principal as HTML but is specific to Sinch technology.   Learn more about the Sinch Voice Products.
View article