构建短信服务器的最佳实践是什么 [英] What are the best practices for building an SMS server

问题描述

我正在尝试构建一个系统，在该系统中我的终端节点能够通过 GSM 网络发送/接收 SMS 消息.我现在需要构建一个服务器解决方案，该解决方案将发送 SMS 消息，充当包含我的业务逻辑的网络服务器和客户端(节点)之间的网关.沟通是双向的.我读过一些关于完整的 SMS 服务器解决方案(可能充当 GSM 网关)的内容，但结果证明它们太贵了.我曾考虑将手机连接到我的服务器(然后使用一些 API)，但我的服务器可能会转到数据中心，因此我无法以这种方式连接任何东西.我不希望有太多的消息(比如每天 100 条/双向).而且我也不打算拥有太多客户(少于 100 个).在这里，我要求提供通用的系统解决方案(例如最佳实践).

I am trying to build a system in which I have terminal nodes capable of sending/receiving SMS messages over a GSM network. I now need to construct a server solution which would send SMS messages acting as a gateway between a webserver holding my business logic and the clients (nodes). The communication is both ways. I've read something about complete SMS server solutions (that act as a GSM gateway, possibly), but they turn out to be too expensive. I've thought about attaching a mobile phone to my server (and then using some APIs), but it may be that my server will go to a data-center whereby I cannot attach anything in this way. I do not expect to have too many messages (like 100 per day/both ways). And I do not plan to have too many clients too (less than 100). Here I'm asking for a general system solution (e.g. best practice).

推荐答案

构建这样的 SMS 服务器有三种基本的替代方案:

There are three basic alternatives for building such an SMS server:

1) 将手机或 USB GSM 记忆棒连接到服务器，并将其用于 SMS 通信.限制是

1) Attach mobile phones or USB GSM sticks to the server and use these for SMS communicaton. Limitations are

• 数量有限(不过你每天 100 条短信应该没问题).

• Limited volumes (however your 100 SMS/day should be fine).

可能由于消费硬件而相当不可靠(例如，电话/棒固件不是为 24x7 操作而构建的，您可能需要定期重置设备；大多数手机需要电池才能运行，电池会耗尽).

Possibly rather unreliable due to consumer hardware (e.g. phone/stick firmware is not built for 24x7 operation, you may need to reset devices regularly; most mobile phones require a battery in order to function, batteries wear out).

由于 RF 规则和移动网络覆盖范围，可能不适用于数据中心.

Possibly not placable in data centers, due to RF rules and mobile network coverage.

手机号码方案仅限于 SIM MSISDN.

Mobile number scheme limited to SIM MSISDN.

2) 将 SMS 连接到网络运营商的 SMS 网关.网络运营商正是将这些用于此场景:批量 SMS 通信.这些是专有的，通常谈论更容易"消化消息传输协议.限制:

2) Connect the SMS to a network operators SMS gateway. Network operators use these exactly for this scenario: bulk SMS communication. These are proprietary and usually talk an "easier" to digest message transport protocol. Limitations:

• 您在连接和协议方面都与网络运营商绑定.

• You are bound to the network operator, connection-wise and protocol-wise.

可能会延迟通信，因为网关可能会进行存储转发.

Possibly delays in communication since the gateway might do store-and-forward.

根据定价方案可能只对大批量有意义.

Depending on pricing scheme might make sense only for high volumes.

3) 将 SMS 服务器连接到移动运营商 SS7 网络，将其添加为网元.限制:

3) Connect the SMS server to the mobile operators SS7 network, adding it as a network element. Limitations:

• 复杂的实现.需要专用硬件(SS7 接口卡)和驱动程序进行编程.

• Complex implementation. Requires dedicated hardware (an SS7 interface card) and drivers to be programmed.

需要与网络运营商进行非平凡的网络集成，包括广泛的测试.

Requires non-trivial network integration with network operator including extensive testing.

需要 E1/T1 线路(或更大，或 SIGTRAN)进行连接，这通常是数据中心的事情，但并非在每个数据中心都可用.

Requires an E1/T1 line (or bigger, or SIGTRAN) for connection this is typically a data center thing, but not available in every data center.

在定价方案和操作方面价格昂贵.

Expensive, in terms of pricing scheme and operation.

假设我了解您的要求，对于您的情况，我会选择选项 1) 并将 SMS 服务器放置在覆盖良好的地方，即不一定在数据中心.将其作为服务器基础设施的前端出售.如果必须将其放入数据中心，请转到选项 2) 并查看您的移动网络运营商 SMS 批发产品.

Assuming I understand your requirements, for your case I would go for option 1) and place the SMS server where it has good coverage, i.e. not necessarily in the data center. Sell it as a head-end for the server infrastructure. If putting it in the data center is a must, then go to option 2) and check out your mobile network operators SMS wholesale offerings.

这篇关于构建短信服务器的最佳实践是什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！