P2P

Person-to-person SMS is traffic one person sends another. It has no sender registration or template approval, so it is not for application messages.

Definitions only — a term explained here is not a service we sell.

Person-to-person (P2P) messaging is traffic that starts on one person's handset and ends on another person's handset. It has no application bind, no sender registration and no template approval.

The difference from A2P is commercial and regulatory as much as technical: A2P runs under a commercial agreement and, in many markets, a registered sender, while P2P has neither. What is A2P SMS sets out the registered route that P2P lacks. Both use the same store-and-forward core.

Where a P2P message goes

  1. Application
  2. SMPP gateway
  3. SMSC
  4. HLR / HSS
  5. MSC / MME
  6. Handset
  7. Delivery receipt
The figure shows the application route: a P2P message starts at the sender's handset instead of the application and SMPP gateway.
Text description

The figure shows the application path: application to SMPP gateway, SMSC, HLR/HSS, MSC/MME, handset and delivery receipt. On a P2P message the sender's handset submits to the SMSC of its own network, which stores the message and forwards it to the recipient's network. No application or registered sender sits on the path.

FAQ

Is P2P cheaper than A2P?

Sometimes on paper, because the termination rate differs. For application traffic that rate usually signals a gray route.

Can P2P carry OTP?

A business one-time password is application traffic by definition. Sending it over a P2P route is the gray pattern operators filter.

Does P2P still matter?

Yes. People still text each other, and legitimate P2P interconnection carries that traffic. The problem is A2P disguised as P2P.

Learn more

Sources

  1. 3GPP TS 23.040: technical realization of the Short Message Service