Back to blog A2P Connectivity and Operations

Traceability and Safeguards in A2P SMS Traffic

A2P traffic can pass through several parties, which limits end-to-end traceability. Learn why controls should be proportionate and privacy should be protected.

Conceptual diagram of multiple parties in an A2P SMS traffic chain

A2P Traffic Can Involve Several Parties

An A2P traffic chain may include aggregators, carriers, and external platforms. As a result, a local operator does not necessarily control or guarantee end-to-end traceability across the entire chain.

When evaluating controls or tracking expectations, consider which parties are involved and each party’s limits of control. Do not attribute complete visibility over a global route to a single operator unless that capability has been substantiated.

  • Consider that several parties may be involved between the traffic’s origin and its destination.
  • Distinguish each participant’s control from tracking across the entire chain.
  • Avoid presenting end-to-end traceability as a guaranteed capability.
A2P Traffic Can Involve Several Parties

Apply Controls Proportionate to the Traffic Type

Operational controls on A2P traffic should be distinguished from those on P2P traffic. SUTEL’s consultation report cautions that extending intensive controls to P2P SMS could be unnecessary and disproportionate.

The scope of a control should address the problem it is intended to tackle. The available evidence does not support defining specific technical procedures for managing A2P queues or setting universal operational thresholds.

  • Distinguish A2P traffic from P2P traffic when considering controls.
  • Tailor the scope of monitoring to the identified problem and existing limits of control.
  • Do not extrapolate these principles into technical rules for queues or message states that are not supported by relevant documentation.
Apply Controls Proportionate to the Traffic Type

Protect Privacy and the Secrecy of Communications

Inspecting SMS content raises implications for privacy, confidentiality, and the secrecy of communications. Monitoring should take clear limits, specific safeguards, and proportionality into account to avoid indiscriminate processing.

The available evidence supports these general principles, but does not establish a specific technical procedure for managing queues, delivery reports, or message expiry. Defining such practices requires relevant primary documentation.

  • Consider the implications for privacy, confidentiality, and secrecy when monitoring SMS traffic.
  • Set clear limits and safeguards appropriate to the scope of monitoring.
  • Avoid processing message content indiscriminately.
  • Consult authoritative technical sources before establishing specific operational procedures.

Scope of the Available Evidence

The available information supports describing the involvement of several parties in A2P traffic, the limits of end-to-end traceability, and the importance of proportionate controls and privacy safeguards.

It is not sufficient to substantiate definitions of pending states, delivery reports, OTP expiry, queue limits, backpressure, or reconciliation and recovery procedures. These are not presented here as validated technical recommendations.

  • Use primary and technically authoritative documentation to define states, queues, and delivery reports.
  • Check that recommendations match the applicable interfaces and agreements.
  • Do not infer delivery or tracking capabilities that are not supported by the available evidence.

Source

The factual basis for this article is SUTEL’s public consultation report on SMS: https://sutel.go.cr/sites/default/files/audiencias/05772-sutel-dgm-2026-informe-de-consulta-publica-sms.pdf. The cited content addresses parties involved in A2P traffic, traceability limits, proportionate controls, and privacy safeguards. It is not a technical specification for queue management.

FAQ

Frequently asked questions

Does a local operator control all traceability of A2P traffic?

Not necessarily. An A2P chain may involve aggregators, carriers, and external platforms, so the local operator does not always control end-to-end traceability.

Should controls applied to A2P traffic automatically be extended to P2P?

No. SUTEL’s report cautions that applying intensive controls to P2P SMS could be unnecessary and disproportionate. The scope should take the traffic type and the problem being addressed into account.

What safeguards should be considered when monitoring SMS?

Monitoring should include clear limits, specific safeguards, and proportionality, since inspecting message content can raise issues relating to privacy, confidentiality, and the secrecy of communications.

Does this article define how to manage queues, DLRs, or pending OTPs?

No. The available evidence does not support definitions or technical procedures on those topics. Relevant primary documentation is needed to establish them.

Sources consulted

  1. Informe de consulta pública sobre SMS (05772-SUTEL-DGM-2026)Superintendencia de Telecomunicaciones de Costa Rica (SUTEL)
  2. Fuentes oficiales y técnicas sugeridas en el brief3GPP; ITU-T; GSMA; SMPP Developers Forum; IETF