Glossary
Comprehensive glossary of mobile industry terminology
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
A random number sequence assigned by the administration body to the company leasing the short code.
View article
Document issued by Sales Account Management to provide commercials and coverage per destination.
View article
Route Cause Analysis - The process of trying to determine what was actually the route cause of a problem.
View article
Rich Communications Service – a GSMA standard messaging suite that is the successor to SMS/MMS – based on consolidated GSMA standards call Universal Protocol that is gaining momentum and it being heavily promoted as a leading A2P channel. It supported by Google, the GSMA, Vodafone Group and operators around the world.
View article
Reach is a term commonly used in the SMS ecosystem to describe the destinations each mobile operator can send a message to. Reach is determined by commercial agreements, technical connectivity, and hub arrangements etc. A typical tier one mobile operator will have reach to hundreds of other mobile operators. If T-Mobile can send a message to Vodafone UK, then you would say T-Mobile has reach to Vodafone UK.
View article
Whenever you use Sinch services, in one way or another, you are interacting with a resource. These resources are either exposed directly through one of our REST APIs or indirectly through one of our applications.  Examples of resources are phone numbers, messages, calls and conversations.  
View article
A message created by a client that is received, acknowledged, and performed by a server.
View article
An acknowledgement or status message created by a server that is received by a client.
View article
REST (Representational State Transfer) is a set of architectural guidelines for implementing an API.  The principles of REST were formulated by computer scientist Roy Fielding in 2000 and have since become the dominant paradigm for implementing APIs. This is because the REST paradigm is flexible and adaptable to client requirements. Unlike alternatives it is language and framework agnostic. It works in the principle level rather than the protocol level. An API is described as “RESTful” if it implements the REST paradigm.  Sinch has plenty of RESTful APIs which allow developers to leverage capabilities like SMS messaging and automated email marketing. They get their power by having REST features like the following.   Client-Server Architecture Like most applications and sites on the web, RESTful APIs follow a client-server architecture. This consists of three components: Client – the API customer. This could be a developer writing an app or testing with Postman Server – backend which hosts the API platform Resources – capabilities of the API that developers can use to enhance their applications. Resources can be modified by create, read, update and delete methods. As an example, let’s look at the Sinch SMS API. Clients, which are typically Sinch customers, can access it by signing up to Sinch and receiving an API token for authentication. They can then send requests to the API through their code or using Postman.   The XMS server hosts four resources: Batches are sets of SMS messages that can be sent to one or more numbers. Inbounds are incoming messages. Groups are sets of phone numbers that can send or receive messages. Delivery reports tell customers whether their messages have been successfully sent to their destination. Sinch clients can access these resources through HTTP requests to add capabilities to their applications.   Hierarchical architecture RESTful architecture typically contains 3 tiers. REST layer – this is the tier that communicates with the client. It responds to HTTP requests, transferring data in the form of JSON. Service layer – this contains the business logic implementing API resources. Data layer – this persists data in a database such as MySQL. For example, the SMS API implements this in the form of a Multi Service Layer (MSL) platform. The REST and service layers are implemented by Spring-based component called Gateway and Adapter. Gateway has the ability to queue SMS messages for processing. Adapter is specialized to process MMS messages. In the SMS API, MySQL is used to implement the data layer, allowing customer data to be persisted and retrieved for later use.   HTTP Methods RESTful APIs are normally accessed through HTTP requests. There are 9 different types of HTTP request but the four most common are GET, POST, PUT and DELETE. For example, one of SMS API’s resources enables processing of batches of messages. This resource contains: POST methods to send and update batch messages. These tell Sinch servers to create and send a new message batch or to modify the parameters of an existing message batch, depending on what the customer wants to do. GET methods to retrieve a batch of messages and retrieve a list of batches. This allows clients to keep track of their message batches. PUT method to replace a batch DELETE method tells Sinch servers to cancel a batch of messages.   Unique Resource Endpoints One of the core principles of RESTful architecture is that API resources and methods are attached to URIs called endpoints. Endpoints have the same structure as a website URL, but instead of loading an application onto your browser, they enable you to send HTTP requests to the API.   Each endpoint specifies a particular resource. For example in the SMS API the endpoint https://us.sms.api.sinch.com/xms/v1/{service_plan_id}/batches specifies the resource for sending a batch of messages.  The ability to access API resources the same way you would access any other resources makes RESTful APIs an extremely powerful development tool and the backbone of modern web development.   Sinch REST APIs Sinch has REST APIs for: SMS WhatsApp RCS Voice Verification.  
View article
When an SMS message is sent to a recipient, it is expected it will be delivered to the handset within seconds. However, delivering an SMS is a relatively complex process, and an SMSC takes several measures to ensure a reliable service including retrying a message should it fail to deliver. An SMS may fail to deliver to a handset on its first delivery attempt for many reasons. These reasons can either be temporary or permanent, and if the latter, no additional retries will be attempted, and the delivery notification will be sent back to the sender to confirm the message failed.
View article
Revenue Share is an integral part of Premium SMS. It is a billing mechanism that enables content providers to charge end-users to participate in mobile marketing events, also known as reverse billing. Charges are made by the wireless carrier directly to the mobile subscriber's account and share of charges or revenue is split between the operator, the content provider and the aggregator. Revenue Sharing message types include: - Premium SMS - Premium MO - Premium MT - Premium 2-way.
View article
Radio Frequency Identification (RFID) is a technology using electromagnetic fields to read data store in tags embedded in other items such as ID cards.
View article
When a subscriber travels outside their home operator service area, we say they are roaming onto another network. It is important SMS messages are still delivered correctly when a subscriber is roaming, and as such the foreign network’s VLR communicates with the HLR of the home network to ensure the location of the subscriber is maintained at all times. It should be noted that even while roaming, a subscriber will always send a message via their home SMSC.
View article
A routing class is a term used by Sinch to explain a collection of routing attributes that together define the overall quality and performance of the SMS product. For example, the direct routing class is a made up of all Sinch’s direct connections and its own SMSCs to create a very high-quality set of routes used for mission critical services.
View article
Real Time Communication (RTC) is live, instant communication with minimal latency.
View article
Report Transaction Event.
View article
Real-Time Lookup is based on real-time HLR queries only and is commonly used for authentication services where additional information in addition to MCC+MNC is needed.
View article
Real Time Protocol (RTP) is a network protocol for delivering audio and video over IP networks.
View article