The full production GSMS offer provides many advantages:

• Text messages are supported in almost all mobile devices and since the cross-carrier SMS is also supported by the platform, the GSMS APIs provide an effective and convenient way for you to connect to your more than 300 million subscribers in the USA and Canada and also for your customers to connect back to you through text messages.
• Multiple protocol interfaces are supported by the GSMS which includes the following:
  • HTTP - REST like interface for quick and simple development and integration with your application to send and receive SMS
  • Web Services interface using SOAP-XML is also supported
  • SMPP¹ – Native protocol for SMS
  • SMTP¹ – Email to send and receive SMS from and to your application
  • Note:  In the trial environment SOAP and HTTP are currently supported
• Provides a way of recording and managing the consent of your customers (mobile subscribers)
• Supports broadcasting a short message to multiple destination mobile numbers.
• Provides support for batch messaging. There are two methods; one with which you could create/ define a common message template with customized parameters and store it in the gateway. Another API method is provided to deliver the message by passing in the actual parameter values to be substituted in the template which forms the final message content.
• The platform provides API methods for scheduling of short messages so that your application can send short messages that would be scheduled for delivery at a later point in time. This feature helps build campaign management applications that can schedule promotional messages to its subscribers on a periodic interval.
• Supports sending of binary SMS and WAP-Push (Service Indication type only) messages.
• API method that takes just the text as the input and can create and send a mobile barcode to the destination subscribers.
• The platform also supports API method to cancel delivery of a message that was sent earlier to the system that are still queuing and scheduling inside the system for delivery. The interface doesn’t cancel the messages that are already sent to the carrier network through the AT&T GSMS gateway.
• The platform can be integrated with existing systems or used as a stand-alone web-based application for a wide variety of applications, including:
  • Workforce management and communication
  • Mobile marketing campaigns via SMS and e-mail
  • Mobile commerce
  • HR functions, job placement and staffing
  • Shift confirmations, scheduling
  • Reminders
  • Voting, polling, surveying, sweepstakes
• Easy to use and integrate APIs along with sample code snippets allows you learn, develop and launch your application quickly.
• Provides an option for archival² of all messaging activity.
• Provides reporting and analytical tools² to enhance your business needs. To achieve the same level of functionalities for your application development outside this platform, you might have to establish multiple contracts, develop and integrate your code against multiple API sets. Instead, with AT&T Global Messaging suite, one contract - with one convenient monthly payment - provides a single, integrated service offering multi-carrier SMS capability through one of our SMS aggregator relationships and customer support.

• Binary SMS Support:
  • Binary SMS is supported by the system which empowers you to build feature enriched sophisticated applications. Binary SMS basically is split into a User Data Header (UDH) and the actual data. The mobile devices (including non-phone devices) would use the information present in the User Data Header to interpret the actual data sent in the message. This way the binary SMS could be used to send logos, ringtones, telephone settings and WAP-Push messages.
  • Binary SMS allows you to send rich content via text messages such as over the air (OTA) configuration messages. OTA capabilities are considered a main component of mobile network operator and enterprise-grade Mobile Device Management software. These capabilities include the ability to remotely configure a single mobile device, an entire fleet of mobile devices or any IT-defined set of mobile devices; send software and OS updates; remotely lock and wipe a device, which protects the data stored on the device when it is lost or stolen; and remote troubleshooting. OTA commands are sent as a binary SMS message.
    OTA device management commands using binary SMS are of high demand. Please note that the device to which you could send an OTA commands containing binary SMS need not just be a phone device; it could be any device installed with a SIM that could have SMS capabilities.
    Home/enterprise security systems, enterprise level automated machinery controller, prison anklets, postal tracking devices and tablet computers are some common examples of such devices which when custom built could be remotely controlled by sending over the air mobile device management commands using Binary SMS.
    Hence the binary SMS opens up a new world of possibilities for innovative applications that could be explored. Typically the solution shall include a server component, which would send out the management commands to the mobile devices in the form of binary SMS the over the air using the carrier network, and a client component, which runs on the device that would receive and implements the management commands.
  • You can also use Binary SMS targeted to a specific port on a mobile device to wake up a specific service on that device. Please note that it is dependent on the device on what is enabled to accept.
• Flash SMS
  • You could send Flash SMS to devices that support it.
• WAP Push support
  • Using the capabilities of the binary SMS Service Indication (SI) type messages is supported. Using WAP Push messages you could develop an application with rich user experience where it could direct the end user device to a WAP address where particular content may be stored ready for viewing or downloading to the handset. The address could be a simple page or multimedia content (e.g. polyphonic ring tone).
• Multiple protocol supported interface
  • The platform supports multiple interfaces to send and receive SMS from your application.
    • HTTP – REST like interface for quick and simple development and integration with your application to send and receive SMS
    • Web Services interface using SOAP-XML is also supported.
    • SMPP³ – Native protocol for SMS
    • SMTP³ – Email to send and receive SMS from and to your application
• Ability to Schedule, Cancel SMS
  • The platform provides API methods for scheduling of short messages so that your application can send short messages that would be scheduled for delivery at a later point in time.
  • The platform also supports API method to cancel delivery of a message that was sent earlier to the system that are still queuing and scheduling inside the system for delivery. The interface doesn’t cancel the messages that are already sent to the carrier network through the AT&T GSMS gateway.
• Mobile Barcode and Binary SMS
  • Mobile 2D barcodes are beginning to be used in the mobile ticketing applications like in the case of the airline and other transportation industries for SMS check-in and boarding passes.
  • With the evolution of mobile Bar Coded Boarding Pass (BPCP) which is being worked on by IATA (International Air Transport Association), mobile check-in and ticketing are expected to be the next key industry breakthrough in the airline industry.
  • In addition, 2D barcodes can also be implemented in event ticketing (concerts, movies, sport events) and discount couponing.
  • Mobile tickets with 2D barcodes can be provided to the consumer in various formats, such as SMS (via WAP-Push), MMS, via a mobile application, or through the mobile browser (WAP).
  • Since SMS can provide the mobile ticketing service from anywhere, at any time, without special applications and with a standard mobile phone, text messaging remains an optimal technology to handle applications such as mobile check-in, ticketing and discount couponing.