Introduction

Short Message Service

Repository to describe, develop, document and test the Short Message Service API family

Scope

  • Service APIs for “Short Message Service” (see APIBacklog.md)
  • It provides the customer with the ability to:
    • to send SMS to the destination address(es). There are 3 different categories of SMS i.e. Service, Promotional & Transactional. This API is used to send all categories of messages. Pre-requisite for using this API is that SMS Sender application / enterprise (or customer) needs to onboard itself with the access provider before using this API. This API has only single operation i.e. Send SMS - Provides the capability to deliver SMS to the recepient. In order to the receive delivery receipt separate API to be defined which is to be implemented by the API consumer for sending back the delivery receipt to the 'Send SMS' API consumer in a standardized callback API.
    • NOTE: The scope of this API family should be limited (at least at a first stage) to 4G and 5G.
  • Describe, develop, document and test the APIs (with 1-2 Telcos)
  • Started: December 2023
  • Location: virtually

Meetings

  • Meetings are held virtually
  • Schedule: tbd
  • Meeting link: tbd

Contributorship and mailing list


Meetings

Registration / Join

Schedule: 

Create new Minutes page

Primary Contact: Tet (Tetsuya) CHIBA 
Project Lead:  Tet (Tetsuya) CHIBA 

Release Planning & Release Notes


Project Working Documents

Task Report

This is a mandatory step so that action items can be assigned between the Committers and Contributors of the project.  Edit the "Task Report" confluence macro below and change the label field to match your project repository.

Task report

Looking good, no incomplete tasks.

Project Files

No files shared here yet.