WO2010009642A1 - 多企业间的短信实现方法、系统和设备 - Google Patents

多企业间的短信实现方法、系统和设备 Download PDF

Info

Publication number
WO2010009642A1
WO2010009642A1 PCT/CN2009/072135 CN2009072135W WO2010009642A1 WO 2010009642 A1 WO2010009642 A1 WO 2010009642A1 CN 2009072135 W CN2009072135 W CN 2009072135W WO 2010009642 A1 WO2010009642 A1 WO 2010009642A1
Authority
WO
WIPO (PCT)
Prior art keywords
short message
server
message
sending
recipient number
Prior art date
Application number
PCT/CN2009/072135
Other languages
English (en)
French (fr)
Inventor
宋立岩
马海滨
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=40125627&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2010009642(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to BRPI0901013-0A priority Critical patent/BRPI0901013B1/pt
Priority to ES09704937.3T priority patent/ES2549902T3/es
Priority to EP09704937.3A priority patent/EP2169987B1/en
Publication of WO2010009642A1 publication Critical patent/WO2010009642A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/48—Message addressing, e.g. address format or anonymous messages, aliases
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, system and device for implementing short messages between multiple enterprises. Background technique
  • SMS has become one of the most widely used communication methods. It has the characteristics of low price, clear expression and high delivery rate, and is well received by users.
  • SMS Short Lesser Service
  • MAS Mobile le Agent Server, mobile agent server
  • System, MAS provides a common platform interface method, which is convenient and flexible to integrate with the existing office and application systems of the enterprise.
  • the mobile data service is used as the medium to transmit and receive information in both directions and interactively, to meet the enterprise informationization and personalization.
  • Mobile office needs have become the mainstream way of corporate SMS.
  • the operator deploys a short message server in the enterprise, and the short message server connects to the SMS gateway of the operator through a dedicated line or the Internet, and the network management respectively allocates corresponding short message service access codes for each enterprise short message server, and each The short message server of the enterprise sends a short message to the short message gateway through the respective short message service access code, and provides a short message sending interface for the enterprise by using the web mode, so that the enterprise can send a short message to the user group through the web interface.
  • the embodiments of the present invention provide a method, a system, and a device for implementing a short message between multiple enterprises, which are used to implement short message interaction between enterprises and save number resources.
  • An embodiment of the present invention provides a method for implementing a short message between multiple enterprises, including:
  • An embodiment of the present invention further provides a short message server, including:
  • a receiving unit configured to receive a short message sent by the sending party to the receiving party number
  • a first sending processing unit configured to add a unified short message access code in front of the sender number of the short message and send the short message access code to the short message gateway to send the short message to the mobile terminal corresponding to the receiving party number;
  • a second sending processing unit configured to send the short message to a PC client corresponding to the recipient number.
  • the embodiment of the present invention further provides a multi-enterprise SMS implementation system, including: a first short message server, and a short message gateway;
  • the first short message server is configured to: after receiving the short message sent by the sending party, add a unified short message access code to the short message gateway and send the short message to the short message gateway to send the short message to the Determining a mobile terminal corresponding to the recipient number; and transmitting the short message to a PC client corresponding to the recipient number.
  • the method of adding a unified short message access code to the sender's number through the short message server makes it unnecessary for the short message server of different enterprises to distinguish by the short message access code, thereby saving the number resource.
  • FIG. 1 is a flowchart of a method for implementing a short message between multiple enterprises in an embodiment of the present invention
  • FIG. 2 is a schematic diagram of networking applied in an embodiment of the present invention.
  • FIG. 3A is a schematic diagram of a networking diagram of a user of the enterprise A sending a short message to the mobile terminal through the user terminal A in the embodiment of the present invention
  • FIG. 3B is a flowchart of a user of the enterprise A sending a short message to the mobile terminal through the user terminal A in the embodiment of the present invention
  • FIG. 4A is a schematic diagram of a networking diagram in which a mobile terminal sends a short message to a user terminal A in enterprise A according to an embodiment of the present invention
  • 4B is a schematic diagram of a networking diagram in which a mobile terminal sends a short message to user terminal A in enterprise A according to an embodiment of the present invention
  • FIG. 5A is a schematic diagram of a networking diagram in which a user terminal A in an enterprise A sends a short message to a user terminal B according to an embodiment of the present invention
  • 5B is a flow chart of the user terminal A in the enterprise A sending a short message to the user terminal B in the embodiment of the present invention
  • 6A is a schematic diagram of networking of user terminal A in enterprise A to user terminal C in enterprise B in the embodiment of the present invention
  • 6B is a flowchart of the user terminal A in the enterprise A to the user terminal C in the enterprise B in the embodiment of the present invention
  • FIG. 7 is a schematic diagram of a system for implementing a short message between multiple enterprises in an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a short message server in an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a short message server in an embodiment of the present invention. detailed description
  • Embodiments of the present invention provide a method for implementing short message between multiple enterprises, which is applied to a network.
  • the information distribution server as shown in Figure 1, includes:
  • Step sl01 receiving the short message sent by the sending party to the receiving party number.
  • Step sl02 Add a unified short message access code in front of the sender number of the short message and send it to the short message gateway to send the short message to the mobile terminal corresponding to the recipient number.
  • Step sl03 Send the short message to a PC client corresponding to the recipient number.
  • the manner in which the unified short message access code is added to the sender's number by the short message server is such that the short message server of different enterprises does not need to be distinguished by the short message access code, thereby saving the number resource.
  • the following describes a method for implementing short message between multiple enterprises in the present invention in combination with a specific application scenario. As shown in FIG. 2, it is assumed that there are two enterprise users under the industry gateway in the network, and each has a short message server. Different from the prior art, the embodiment of the present invention deploys a message distribution server in the network for judging the short message server to which the receiver belongs and forwarding the short message accordingly. The following describes the various SMS transmissions of the network structure.
  • the user of the enterprise A sends a short message to the mobile terminal through the user terminal A (for the PC client), that is, the short message sending process of the PC->Phone, and the networking diagram of the scenario As shown in FIG. 3A, the short message sending process is as shown in FIG. 3B, and includes:
  • Step s301 The user terminal A sends a short message to the short message server.
  • the user terminal A can send a short message by calling a short message sending interface provided by the short message server.
  • Step s302 The short message server sends the short message to the industry gateway SM GM (Short Message GateWay) through the Submit message, and receives the short message receipt sent by the industry gateway.
  • SM GM Short Message GateWay
  • the short message server adds a short message access code before the sender number, and invokes a short message sending interface provided by the industry gateway, based on CMPP (China Mobi le Peer to Peer), SMPP (Short Message Peer to Peer, short)
  • CMPP China Mobi le Peer to Peer
  • SMPP Short Message Peer to Peer
  • the protocol such as the peer-to-peer protocol, sends a text message to the industry gateway, and carries the sender number after adding the unified SMS access code. Used by the recipient when replying to a text message.
  • Step s303 After receiving the receipt of the industry gateway, the short message server sends the short message receipt to the user terminal eight.
  • the mobile terminal sends a short message to the user terminal A in the enterprise A, and the user terminal A in the enterprise A receives the short message, that is, the short message sending process of the Phone->PC, that is, the PC from the Phone
  • the process of receiving the short message is as shown in FIG. 4A.
  • the short message receiving process of the user terminal A is as shown in FIG. 4B, and includes:
  • Step s401 The industry gateway receives the short message sent by the mobile terminal.
  • the mobile terminal After the mobile terminal adds a unified short message access code before registering the recipient number of the same number as the PC, the mobile terminal sends a short message to the industry gateway.
  • Step s402 The industry gateway submits the message to the message distribution server.
  • the industry gateway after receiving the short message, the industry gateway submits the short message content to the message distribution server through a protocol such as CMPP or SMPP.
  • Step s403 The message distribution server sends a message receipt to the industry gateway.
  • Step s404 The message distribution server determines whether the received number is an identifiable number, and if not, discards. Specifically, in this embodiment, the message distribution server determines whether the recipient number is the system receiving number, and if not, discards.
  • Step s405 The message distribution server removes the short message access code before the recipient number, and then determines which enterprise the recipient belongs to. Wherein, determining which enterprise the recipient belongs to, the enterprise may be selected according to the correspondence between the pre-configured enterprise member number and the enterprise.
  • Step s406 The message distribution server sends the short message to the short message server of the enterprise to which the user terminal A belongs by using HTTP.
  • Step s407 The short message server pushes the short message to the user terminal A through a UDP (User Datagram Protocol) message. If the user terminal A is offline, it needs to be saved as an offline short message.
  • HTTP Hypertext Transfer Protocol
  • Step s409 The message distribution server sends a short message receipt to the industry gateway.
  • the user terminal A (for the PC client) in the enterprise A sends a short message to the user terminal B (for the PC client), that is, the short message sending process of the internal PC->PC of the enterprise
  • Figure 5A shows the networking diagram of the scenario.
  • the SMS sending process of user terminal A is as shown in Figure 5B.
  • Step s501 The user terminal A sends a short message to the user terminal B, and first sends the short message to the short message month.
  • Step s502 The short message server accesses the enterprise database, and determines that the recipient is the user terminal B of the enterprise, and sends the short message content to the user terminal B through the HTTP protocol.
  • the short message server also needs to send the short message to the industry gateway, and then the industry gateway sends a short message to the mobile terminal of the receiver, which is not marked, which is equivalent to the sending of the short message of PC -> Phone.
  • Step s503 The short message server sends a short message receipt to the user terminal A through the HTTP protocol.
  • the entire process described above only needs to be done inside the enterprise network.
  • the user terminal A (for the PC client) in the enterprise A sends a short message to the user terminal C (for the PC client) in the enterprise B, that is, the PC->PC between the enterprises.
  • the short message sending process of the user terminal A is shown in FIG. 6B, and includes:
  • Step s601 User terminal A in enterprise A needs to send a short message to user terminal C in enterprise B. First, the short message is sent to the short message server in enterprise A.
  • Step s602 The short message server of enterprise A adds a short message access code before the recipient number, and forwards the short message to the industry gateway to send to the mobile terminal of the receiver.
  • the process may refer to FIG. 3A above.
  • the PC->Phone short message sending process described in FIG. 3B is not repeated here.
  • Step s603 The short message server of enterprise A determines that the recipient does not belong to the enterprise A, and forwards the short message to the message distribution server through the HTTP protocol.
  • Step s604 The message distribution server determines the enterprise to which the recipient number belongs, and the enterprise scene is obtained in the application scenario.
  • Step s605 The message distribution server forwards the short message to the short message server of enterprise B.
  • Step s606 The short message server of enterprise B queries whether the receiver, that is, the user terminal C, is online through the HTTP protocol.
  • Step s607 The short message server of the enterprise B obtains a status report of the user terminal C.
  • Step s608 The short message server of the enterprise B sends the short message content to the user terminal through the UDP protocol. (Note that if the user terminal C is not online, the short message server of the enterprise B saves the offline short message, and waits until the user terminal C is online. Send to user terminal C.
  • Step s609 The short message server of the enterprise B sends a notification of the receiving status to the message distribution server through the HTTP protocol.
  • Step s610 The message distribution server sends a notification of the receiving status to the short message server of the enterprise A through the HTTP protocol.
  • Step s611 The short message server of enterprise A sends a short message receipt to user terminal A.
  • the manner in which the unified short message access code is added to the sender's number by the short message server is such that the short message server of different enterprises does not need to be distinguished by the short message access code, so that the entire short message service can be
  • the SMS enterprise-level sending and replying functions can be realized, and the requirements of the personal short message service can be met, and the number resource is saved.
  • the embodiment of the present invention implements the same number of the PC client and the mobile terminal, supports direct reply of the short message, and can simultaneously receive the short message by the PC client and the mobile terminal.
  • the embodiment of the present invention further provides a multi-enterprise SMS implementation system. As shown in FIG.
  • the method includes: a message distribution server 10, at least two short message servers (hereinafter, the first short message server 20 and The second short message server 30 is described as an example, and the short message gateway 40.
  • the first short message server 20 is configured to: after receiving the short message sent by the sending party to the sending party, add a unified short message access code to the short message in front of the sender number of the short message, and send the short message to the short message gateway 40 to send the short message. Go to the mobile terminal corresponding to the recipient number; and send the short message to the PC client corresponding to the recipient number.
  • the message distribution server 10 is configured to: when the short message service of the recipient number is responsible by the second short message server 30, receive the short message sent by the first short message server 20, and pass the short message through the The second short message server 30 transmits to the PC client corresponding to the recipient number.
  • a structure of a short message server is as shown in FIG. 8, and includes: a receiving unit 11 configured to receive a short message sent by a sending direction to a receiving party number;
  • the first sending processing unit 12 is configured to add a unified short message access code in front of the sender number of the short message and send the short message access code to the short message gateway to send the short message to the mobile terminal corresponding to the receiving party number;
  • the second transmission processing unit 13 is configured to send the short message to the PC client corresponding to the recipient number.
  • a structure of a short message server is as shown in FIG. 9, wherein: the second sending processing unit 13 of the short message server specifically includes:
  • the determining sub-unit 131 is configured to determine whether the short message service is responsible for the receiving party number; the first sending sub-unit 132 is configured to: when the determining sub-unit 31 determines to be yes, send the short message to the receiving party number Corresponding PC client sends;
  • the second sending sub-unit 133 is configured to forward the short message to the message distribution server when the determining sub-unit 31 determines to be no, and the message server sends the short message to the PC client corresponding to the receiving party number. send.
  • the receiving unit 11 is further configured to receive a short message that is sent by the message distribution server and carries the second recipient number; the short message server further includes:
  • the third sending processing unit 14 is configured to receive the short message received by the receiving unit 11 to the device.
  • the PC client corresponding to the two recipient numbers is sent.
  • a manner of adding a unified short message access code to a sender's number by a short message server is used, so that the short message server of different enterprises does not need to be distinguished by the short message access code, so that the entire short message is obtained.
  • the service can use the unified SMS access code to realize the SMS-level sending and replying functions of the SMS, and can meet the needs of the personal short message service, saving the number resources.
  • the embodiment of the present invention implements the PC client and the mobile terminal with the same number, supports direct reply of the short message, and can simultaneously receive the short message by the PC client and the mobile terminal.
  • the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for making a The station apparatus performs the methods described in various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

多企业间的短信实现方法、 系统和设备 本申请要求于 2008 年 7 月 21 日提交中国专利局， 申请号为 200810132171. 4 , 发明名称为 "多企业间的短信实现方法、 系统和设备" 的 中国专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域， 尤其涉及一种多企业间的短信实现方法、 系 统和设备。 背景技术
随着通信行业的发展， 短信已经成为目前应用最为广泛的通信手段之一， 具有价格低， 表达清晰， 送达率高等特点， 深受广大用户的喜爱。
与此同时， 短信在企业方面的应用也已经开展的如火如荼， 从最开始的 企业信息机， 到现在流行的 MAS (Mobi le Agent Server , 移动代理服务器） ， 都是运营商为企业定制的企业短信系统， MAS提供通用的平台接口方式，便捷、 灵活地与企业现有的办公、 应用系统集成结合， 以移动数据业务为媒介进行 信息的收发双向传递和交互式传递， 满足企业信息化、 个性化、 移动化的办 公需求， 已成为当前企业短信的主流方式。
现有的企业短信方案中， 运营商在企业内部部署短信服务器， 短信服务 器通过专线或者 Internet连接到运营商的短信网关， 网管为每个企业的短信 服务器分别分配相应的短信服务接入码， 各企业的短信服务器通过各自的短 信服务接入码向短信网关发送短信， 并以 Web方式为企业提供短信发送界面， 使得企业可以通过 Web界面向用户群发短信。
发明人在实现本发明的过程中， 发现现有技术中的实现方式存在以下问 题：
现有企业短信方案中， 为了对不同企业的短信服务器进行区分， 需要为 每个企业分别分配独立的短信接入码， 造成号码资源的浪费。 发明内容
本发明的实施例提供一种多企业间的短信实现方法、 系统和设备， 用于 实现企业间的短信交互， 节约号码资源。
本发明的实施例提供一种多企业间的短信实现方法， 包括：
接收发送方向接收方号码发送的短信；
在所述短信的发送方号码前添加统一的短信接入码并向短信网关发送， 以将所述短信发送到所述接收方号码对应的移动终端；
将所述短信向所述接收方号码对应的 PC客户端发送。
本发明的实施例还提供一种短信服务器， 包括：
接收单元， 用于接收发送方向接收方号码发送的短信；
第一发送处理单元， 用于在所述短信的发送方号码前添加统一的短信接 入码并向短信网关发送， 以将所述短信发送到所述接收方号码对应的移动终 ¾ ;
第二发送处理单元， 用于将所述短信向所述接收方号码对应的 PC客户端 发送。
本发明的实施例还提供一种多企业间的短信实现系统， 包括： 第一短信 服务器、 以及短信网关；
所述第一短信服务器， 用于接收发送方向接收方号码发送的短信时， 在 所述短信的发送方号码前添加统一的短信接入码并向短信网关发送， 以将所 述短信发送到所述接收方号码对应的移动终端； 并将所述短信向所述接收方 号码对应的 PC客户端发送。
与现有技术相比， 本发明的实施例具有以下优点：
通过短信服务器在发送方号码中增加统一短信接入码的方式， 使得对于 不同企业的短信服务器不需要通过短信接入码进行区分， 节约了号码资源。 附图说明
图 1是本发明的实施例中多企业间的短信实现方法的流程图；
图 2是本发明的实施例中所应用的组网示意图；
图 3A是本发明的实施例中企业 A的用户通过用户终端 A向移动终端发送 短信的组网示意图；
图 3B是本发明的实施例中企业 A的用户通过用户终端 A向移动终端发送 短信的流程图；
图 4A是本发明的实施例中移动终端向企业 A中的用户终端 A发送短信的 组网示意图；
图 4B是本发明的实施例中移动终端向企业 A中的用户终端 A发送短信的 组网示意图；
图 5A是本发明的实施例中企业 A中的用户终端 A向用户终端 B发送短信 的组网示意图；
图 5B是本发明的实施例中企业 A中的用户终端 A向用户终端 B发送短信 的流程图；
图 6A是本发明的实施例中企业 A中的用户终端 A向企业 B中的用户终端 C的组网示意图；
图 6B是本发明的实施例中企业 A中的用户终端 A向企业 B中的用户终端 C的流程图；
图 7是本发明的实施例中多企业间的短信实现系统示意图；
图 8是本发明的实施例中短信服务器的结构示意图；
图 9是本发明的实施例中短信服务器的结构示意图。 具体实施方式
本发明的实施例提供一种多企业间的短信实现方法， 应用于网络中的消 息分发服务器， 如图 1所示， 包括：
歩骤 sl01、 接收发送方向接收方号码发送的短信。
歩骤 sl02、 在所述短信的发送方号码前添加统一的短信接入码并向短信 网关发送， 以将所述短信发送到所述接收方号码对应的移动终端。
歩骤 sl03、 将所述短信向所述接收方号码对应的 PC客户端发送。
本发明的实施例中， 通过短信服务器在发送方号码中增加统一短信接入 码的方式， 使得对于不同企业的短信服务器不需要通过短信接入码进行区分， 节约了号码资源。 以下结合一个具体的应用场景， 描述本发明中多企业间的短信实现方法， 如图 2所示， 假设网络中的行业网关下存在两个企业用户， 具有各自的短信 服务器。 本发明的实施例与现有技术不同的是， 在网络中部署消息分发服务 器， 用于对接收方所属的短信服务器进行判断并对短信进行相应的转发。 以 下结合对该网络结构对各种短信发送情况进行介绍。
具体的， 本发明的实施例的一应用场景中， 企业 A的用户通过用户终端 A (为 PC客户端） 向移动终端发送短信， 即 PC -〉 Phone的短信发送流程， 该场 景的组网示意图如图 3A所示， 短信发送流程如图 3B所示， 包括：
歩骤 s301、 用户终端 A向短信服务器发送短信。
具体的， 用户终端 A可以通过调用短信服务器提供的短信发送接口发送 短信。
歩骤 s302、 短信服务器通过 Submit 消息将短信发送给行业网关 SM GM ( Short Message GateWay, 短消息网关） ， 并接收行业网关发送的短信回执。
具体的， 短信服务器在发送方号码前增加短信接入码， 调用行业网关提 供的短信发送接口， 基于 CMPP ( China Mobi le Peer to Peer , 中国移动点对 点协议） 、 SMPP ( Short Message Peer to Peer , 短消息点对点协议） 等协 议， 发送短信至行业网关， 同时携带增加统一短信接入码后的发送方号码， 以便接收方回复短信时使用。
歩骤 s303、 短信服务器接收到行业网关的回执之后， 将短信回执发送至 用户终端八。 本发明的实施例的另一应用场景中， 移动终端向企业 A 中的用户终端 A 发送短信， 企业 A中的用户终端 A接收短信， 即 Phone -〉 PC的短信发送流程， 也即 PC从 Phone接收短信的流程， 该场景的组网示意图如图 4A所示， 用户 终端 A的短信接收流程如图 4B所示， 包括：
歩骤 s401、 行业网关接收到移动终端发送到的短信。
具体的， 移动终端在注册了 Phone与 PC同号的接收方号码前添加统一的 短信接入码之后， 向行业网关发送短信。
歩骤 s402、 行业网关将消息提交给消息分发服务器。
具体的， 行业网关收到短信之后， 通过 CMPP或 SMPP等协议向消息分发 服务器提交短信内容。
歩骤 s403、 消息分发服务器向行业网关发送消息回执。
歩骤 s404、 消息分发服务器判断接收号码是否为可识别的号码， 如果不 是则丢弃。 具体地， 在本实施例中， 消息分发服务器判断接收方号码是否为 系统接收号码， 如果不是则丢弃。
歩骤 s405、 消息分发服务器去掉接收方号码前的短信接入码， 进而判断 接收方属于哪个企业。 其中， 判断接收方属于哪个企业， 可以根据预先配置 的企业成员号码与企业的对应关系来选择企业。
歩骤 s406、消息分发服务器将短信通过 HTTP方式发送至用户终端 A所属 企业的短信服务器。
歩骤 s407、 短信服务器将短信通过 UDP (User Datagram Protocol , 用 户数据报协议）消息推送到用户终端 A, 如果用户终端 A不在线， 需要保存为 离线短信。 歩骤 s408、 短信服务器通过 HTTP (Hypertext Transfer Protocol , 超 文本传输协议） 方式向消息分发服务器发送短信回执。
歩骤 s409、 消息分发服务器向行业网关发送短信回执。 本发明的实施例的另一应用场景中， 企业 A中的用户终端 A (为 PC客户 端） 向用户终端 B (为 PC客户端）发送短信， 即企业内部 PC -〉 PC的短信发送 流程， 该场景的组网示意图如图 5A所示， 用户终端 A的短信发送流程如图 5B 所示， 包括：
歩骤 s501、 用户终端 A向用户终端 B发送短信， 首先将短信发送到短信 月艮 。
歩骤 s502、 短信服务器访问企业数据库， 判断接收方是本企业的用户终 端 B, 则将短信内容通过 HTTP协议发送至用户终端 B。
另外， 短信服务器还需要将短信发送至行业网关， 然后由行业网关发送 短信至接收方的移动终端上， 该歩骤没有标注， 相当于 PC -〉 Phone 的短信发 送，
歩骤 s503、 短信服务器通过 HTTP协议向用户终端 A发送短信回执。 上述整个流程只需要在企业网络内部进行。 本发明的实施例的另一应用场景中， 企业 A中的用户终端 A (为 PC客户 端） 向企业 B中的用户终端 C (为 PC客户端） 发送短信， 即企业之间 PC -〉 PC 的短信发送流程， 该场景的组网示意图如图 6A所示， 用户终端 A的短信发送 流程如图 6B所示， 包括：
歩骤 s601、 企业 A中的用户终端 A需要发送短信至企业 B中的用户终端 C, 首先短信被发送至企业 A中的短信服务器。
歩骤 s602、 企业 A的短信服务器在接收方号码前添加短信接入码， 并将 短信转发至行业网关以发送到接收方的移动终端， 该流程可以参考上述图 3A 与图 3B中描述的 PC -〉 Phone短信发送流程， 在这里不进行重复描述。
歩骤 s603、 企业 A的短信服务器判断接收方不属于本企业 A, 则将短信 通过 HTTP协议转发至消息分发服务器。
歩骤 s604、 消息分发服务器判断接收方号码所属的企业， 该应用场景中 获取到的为企业1¾。
歩骤 s605、 消息分发服务器将短信转发至企业 B的短信服务器。
歩骤 s606、 企业 B的短信服务器通过 HTTP协议查询接收方即用户终端 C 是否在线。
歩骤 s607、 企业 B的短信服务器获取到用户终端 C的状态报告。
歩骤 s608、 企业 B的短信服务器通过 UDP协议将短信内容发送给用户终 端(。 需要说明的是， 如果用户终端 C不在线， 则企业 B的短信服务器保存离 线短信， 等到用户终端 C在线时再发送给用户终端 C。
歩骤 s609、企业 B的短信服务器通过 HTTP协议向消息分发服务器发送接 收状态通知。
歩骤 s610、消息分发服务器通过 HTTP协议向企业 A的短信服务器发送接 收状态通知。
歩骤 s611、 企业 A的短信服务器向用户终端 A发送短信回执。
本发明的实施例提供的上述方法中， 通过短信服务器在发送方号码中增 加统一短信接入码的方式， 使得对于不同企业的短信服务器不需要通过短信 接入码进行区分， 使得整个短信业务可以使用统一的短信接入码， 即可实现 短信企业级的发送和回复功能， 并可以满足个人短信业务的需求， 节约了号 码资源。 另外， 本发明的实施例实现了 PC客户端、 移动终端同号， 支持短信 直接回复， 并可以做到 PC客户端和移动终端同时对短信进行接收。 本发明的实施例还提供一种多企业间的短信实现系统， 如图 7所示， 包 括： 消息分发服务器 10、 至少两个短信服务器（以下以第一短信服务器 20和 第二短信服务器 30为例进行说明） 、 以及短信网关 40。 其中： 第一短信服务器 20， 用于接收发送方向接收方号码发送的短信时， 在所 述短信的发送方号码前添加统一的短信接入码并向短信网关 40发送， 以将所 述短信发送到所述接收方号码对应的移动终端； 并将所述短信向所述接收方 号码对应的 PC客户端发送。
所述消息分发服务器 10， 用于当所述接收方号码的短信业务由第二短信 服务器 30负责时， 接收所述第一短信服务器 20发送的所述短信， 并将所述 短信通过所述第二短信服务器 30向所述接收方号码对应的 PC客户端发送。
本发明的实施例中， 一种短信服务器的结构如图 8所示， 包括： 接收单元 11， 用于接收发送方向接收方号码发送的短信；
第一发送处理单元 12， 用于在所述短信的发送方号码前添加统一的短信 接入码并向短信网关发送， 以将所述短信发送到所述接收方号码对应的移动 终端；
第二发送处理单元 13，用于将所述短信向所述接收方号码对应的 PC客户 端发送。
本发明的另一实施例中， 一种短信服务器的结构如图 9所示， 其中： 短信服务器的第二发送处理单元 13具体包括：
判断子单元 131， 用于判断是否负责所述接收方号码的短信业务； 第一发送子单元 132， 用于在所述判断子单元 31判断为是时， 将所述短 信向所述接收方号码对应的 PC客户端发送；
第二发送子单元 133， 用于在所述判断子单元 31判断为否时， 转发所述 短信至消息分发服务器， 由所述消息服务器将所述短信向所述接收方号码对 应的 PC客户端发送。
该短信服务器中： 接收单元 11还用于接收消息分发服务器发送的携带第 二接收方号码的短信； 该短信服务器中还包括：
第三发送处理单元 14，用于将接收单元 11接收的短信向本设备负责的第 二接收方号码对应的 PC客户端发送。
本发明的实施例提供的上述系统和设备中， 通过短信服务器在发送方号 码中增加统一短信接入码的方式， 使得对于不同企业的短信服务器不需要通 过短信接入码进行区分， 使得整个短信业务可以使用统一的短信接入码， 即 可实现短信企业级的发送和回复功能， 并可以满足个人短信业务的需求， 节 约了号码资源。 另外， 本发明的实施例实现了 PC客户端、 移动终端同号， 支 持短信直接回复， 并可以做到 PC客户端和移动终端同时对短信进行接收。
通过以上的实施方式的描述， 本领域的技术人员可以清楚地了解到本发 明可借助软件加必需的通用硬件平台的方式来实现， 当然也可以通过硬件， 但很多情况下前者是更佳的实施方式。 基于这样的理解， 本发明的技术方案 本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来， 该计算机软件产品存储在一个存储介质中， 包括若干指令用以使得一台设备 执行本发明各个实施例所述的方法。
以上公开的仅为本发明的几个具体实施例， 但是， 本发明并非局限于此， 任何本领域的技术人员能思之的变化都应落入本发明的保护范围。

Claims

权利要求书
1、 一种多企业间的短信实现方法， 其特征在于， 该方法包括： 接收发送方向接收方号码发送的短信；
在所述短信的发送方号码前添加统一的短信接入码并向短信网关发送， 以将所述短信发送到所述接收方号码对应的移动终端；
将所述短信向所述接收方号码对应的 PC客户端发送。
2、 如权利要求 1所述的方法， 其特征在于， 所述将短信向所述接收方号 码对应的 PC客户端发送包括：
判断是否负责所述接收方号码的短信业务；
是则将所述短信向所述接收方号码对应的 PC客户端发送， 否则转发所述 短信至消息分发服务器， 由所述消息分发服务器将所述短信向所述接收方号 码对应的 PC客户端发送。
3、 如权利要求 2所述的方法， 其特征在于， 所述由消息分发服务器将所 述短信向所述接收方号码对应的 PC客户端发送包括：
所述消息分发服务器获取所述接收方号码对应的 PC客户端的归属短信服 务器；
所述消息分发服务器通过所述归属短信服务器将所述短信向所述接收方 号码对应的 PC客户端发送。
4、 如权利要求 1所述的方法， 其特征在于， 还包括：
接收消息分发服务器发送的携带第二接收方号码的短信；
将所述短信向所述第二接收方号码对应的 PC客户端发送。
5、 如权利要求 4所述的方法， 其特征在于， 所述接收消息分发服务器发 送的携带第二接收方号码的短信前还包括：
所述短信网关接收移动终端向第二接收方号码发送的短信， 所述第二接 收方号码前携带统一的短信接入码； 所述短信网关向消息分发服务器发送所述短信；
所述消息分发服务器去掉所述短信接入码， 将所述短信向所述第二接收 方号码对应的 PC客户端的归属短信服务器发送。
6、 如权利要求 4所述的方法， 其特征在于， 所述接收消息分发服务器发 送的携带第二接收方号码的短信前还包括：
所述消息分发服务器接收第二短信服务器向第二接收方号码发送的短 信；
所述消息分发服务器将所述短信向所述第二接收方号码对应的 PC客户端 的归属短信服务器发送。
7、 一种短信服务器， 其特征在于， 该短信服务器包括：
接收单元， 用于接收发送方向接收方号码发送的短信；
第一发送处理单元， 用于在所述短信的发送方号码前添加统一的短信接 入码并向短信网关发送， 以将所述短信发送到所述接收方号码对应的移动终 第二发送处理单元， 用于将所述短信向所述接收方号码对应的 PC客户端 发送。
8、 如权利要求 7所述的短信服务器， 其特征在于， 所述第二发送处理单 元具体包括：
判断子单元， 用于判断是否负责所述接收方号码的短信业务；
第一发送子单元， 用于在所述判断子单元判断为是时， 将所述短信向所 述接收方号码对应的 PC客户端发送；
第二发送子单元， 用于在所述判断子单元判断为否时， 转发所述短信至 消息分发服务器， 由所述消息服务器将所述短信向所述接收方号码对应的 PC 客户端发送。
9、 如权利要求 7所述的短信服务器， 其特征在于， 所述接收单元， 还用 于接收消息分发服务器发送的携带第二接收方号码的短信； 还包括： 第三发送处理单元， 用于将所述短信向所述第二接收方号码对 应的 PC客户端发送。
10、 一种多企业间的短信实现系统， 其特征在于， 该系统包括： 第一短 信服务器、 以及短信网关；
所述第一短信服务器， 用于接收发送方向接收方号码发送的短信时， 在 所述短信的发送方号码前添加统一的短信接入码并向短信网关发送， 以将所 述短信发送到所述接收方号码对应的移动终端； 并将所述短信向所述接收方 号码对应的 PC客户端发送。
11、如权利要求 10所述的系统， 其特征在于， 还包括： 消息分发服务器、 以及第二短信服务器；
所述消息分发服务器， 用于当所述接收方号码的短信业务由所述第二短 信服务器负责时， 接收所述第一短信服务器发送的所述短信， 并将所述短信 通过所述第二短信服务器向所述接收方号码对应的 PC客户端发送。
PCT/CN2009/072135 2008-07-21 2009-06-04 多企业间的短信实现方法、系统和设备 WO2010009642A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
BRPI0901013-0A BRPI0901013B1 (pt) 2008-07-21 2009-06-04 Método para implantar transferência de mensagem curta entre múltiplas empresas
ES09704937.3T ES2549902T3 (es) 2008-07-21 2009-06-04 Método, sistema y dispositivo para implementar un servicio de mensajes cortos entre empresas
EP09704937.3A EP2169987B1 (en) 2008-07-21 2009-06-04 Method, system and device for implementing short messaging among enterprises

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810132171.4A CN101309458B (zh) 2008-07-21 2008-07-21 多企业间的短信实现方法、系统和设备
CN200810132171.4 2008-07-21

Publications (1)

Publication Number Publication Date
WO2010009642A1 true WO2010009642A1 (zh) 2010-01-28

Family

ID=40125627

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/072135 WO2010009642A1 (zh) 2008-07-21 2009-06-04 多企业间的短信实现方法、系统和设备

Country Status (5)

Country Link
EP (1) EP2169987B1 (zh)
CN (1) CN101309458B (zh)
BR (1) BRPI0901013B1 (zh)
ES (1) ES2549902T3 (zh)
WO (1) WO2010009642A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101309458B (zh) * 2008-07-21 2016-04-06 华为技术有限公司 多企业间的短信实现方法、系统和设备
CN103428653B (zh) * 2012-05-14 2016-12-07 中国移动通信集团安徽有限公司 异网短消息发送和接收方法、通信系统和应用接入网关
CN105323205A (zh) * 2014-05-30 2016-02-10 中兴通讯股份有限公司 消息推送处理方法、装置、推送服务器及应用服务器
CN109379704B (zh) * 2018-12-21 2020-07-03 珠海市小源科技有限公司 短信的区域信息校正方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1581907A (zh) * 2003-08-12 2005-02-16 华为技术有限公司 实现vpn短号短消息业务的系统及其方法
US20050266864A1 (en) * 2004-06-01 2005-12-01 Xuming Chen Non-intrusive network architecture for mass mobile messaging
CN1863249A (zh) * 2005-05-13 2006-11-15 华为技术有限公司 一种利用回铃音播放广告的方法
US20080004049A1 (en) * 2006-06-29 2008-01-03 Lucent Technologies Inc. Smpp message processing for sms spam filtering
CN101309458A (zh) * 2008-07-21 2008-11-19 华为技术有限公司 多企业间的短信实现方法、系统和设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003019959A1 (en) * 2001-08-27 2003-03-06 Sage Agent Networks Pte Ltd System and method for provisioning of text message services
TW200303690A (en) * 2002-02-18 2003-09-01 Empower Interactive Group Ltd Distributed message transmission system and method
ATE355708T1 (de) * 2002-08-21 2006-03-15 Intellprop Ltd Telekommunikationsdienstevorrichtung und verfahren
US20070233795A1 (en) * 2006-04-04 2007-10-04 Wireless Services Corp. Managing messages between multiple wireless carriers using a relatively limited number of identifiers
US7941557B2 (en) * 2007-11-28 2011-05-10 Yahoo! Inc. Dynamical routing for text messaging

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1581907A (zh) * 2003-08-12 2005-02-16 华为技术有限公司 实现vpn短号短消息业务的系统及其方法
US20050266864A1 (en) * 2004-06-01 2005-12-01 Xuming Chen Non-intrusive network architecture for mass mobile messaging
CN1863249A (zh) * 2005-05-13 2006-11-15 华为技术有限公司 一种利用回铃音播放广告的方法
US20080004049A1 (en) * 2006-06-29 2008-01-03 Lucent Technologies Inc. Smpp message processing for sms spam filtering
CN101309458A (zh) * 2008-07-21 2008-11-19 华为技术有限公司 多企业间的短信实现方法、系统和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2169987A4 *

Also Published As

Publication number Publication date
BRPI0901013B1 (pt) 2020-09-24
CN101309458A (zh) 2008-11-19
EP2169987B1 (en) 2015-08-05
EP2169987A1 (en) 2010-03-31
CN101309458B (zh) 2016-04-06
ES2549902T3 (es) 2015-11-03
BRPI0901013A2 (pt) 2015-06-23
EP2169987A4 (en) 2010-07-21

Similar Documents

Publication Publication Date Title
JP5550627B2 (ja) 通信システムにおけるグループ通信
CN103535004B (zh) 用于促进匿名音频和视频通信的方法和基于web的系统
CN109327513B (zh) 交互方法、装置及计算机可读存储介质
CN101374118A (zh) 一种消息互连的方法、系统及装置
CN101150595A (zh) 一种实时文件传输方法、系统及装置
WO2010121528A1 (zh) 一种移动终端及其基于p2p模式的数据传输方法
KR20090115465A (ko) 멀티클라이언트 간 세션 이동을 위한 시스템 및 방법
CN101981896A (zh) 用于cpm会话管理的方法和装置
US20080091781A1 (en) Group communication
CN102223293B (zh) 消息请求的路由方法及处理系统
CN102130845A (zh) 回执报告的发送方法及处理系统
CN102123133A (zh) 不同消息业务平台互通时传送消息回执的方法和消息系统
WO2010009642A1 (zh) 多企业间的短信实现方法、系统和设备
CN101547214A (zh) 一种推送企业内部数据的方法和网络侧设备
JP4959803B2 (ja) 通信システムにおける配信レポート
US8745145B2 (en) Method and system for transmitting large message mode CPM messages
AU2010213319B2 (en) Method and system for aggregating communications
EP2429256A1 (en) Method for negotiating message session relay protocol connection parameters
CN103457746A (zh) 会议数据的传输方法及装置
CN102026112B (zh) 一种融合ip消息的发送方法及系统
EP2445262A1 (en) System and method for routing instant messages
CN101237428A (zh) 基于即时通讯组建多人会话的方法、系统及服务器
CN101305623A (zh) 用于确定具有控制功能的pt服务器的方法和装置
WO2023155739A1 (zh) 数据传输的方法、网络设备和用户设备
KR101595128B1 (ko) 데이터 중심의 통신 서비스 방법 및 장치.

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2009704937

Country of ref document: EP

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09704937

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: PI0901013

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20090904