WO2012027940A1 - Short-message processing method and short-message center - Google Patents
Short-message processing method and short-message center Download PDFInfo
- Publication number
- WO2012027940A1 WO2012027940A1 PCT/CN2010/080062 CN2010080062W WO2012027940A1 WO 2012027940 A1 WO2012027940 A1 WO 2012027940A1 CN 2010080062 W CN2010080062 W CN 2010080062W WO 2012027940 A1 WO2012027940 A1 WO 2012027940A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- short message
- error
- user
- message
- called end
- Prior art date
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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/184—Messaging devices, e.g. message centre
Abstract
A short-message processing method and short-message center are disclosed in the present invention. Wherein, the method includes that: a short-message center confirms that forwarding a short-message fails due to an error of a user cause; the short-message center transmits a notification message to a called end or calling end of the short-message and notifies the called end or calling end that the forwarding the short-message fails due to the error of the user cause. The present invention achieves an effect of increasing user experience.
Description
短消息处理方法和短消息中心 技术领域 本发明涉及通信领域， 具体而言， 涉及一种短消息处理方法和短消息中 The present invention relates to the field of communications, and in particular to a short message processing method and a short message.
背景技术 短消息中心负责短消息的存储转发， 是短消息业务的核心网元。 长期以 来， 短消息下发成功率不高是短消息业务面临的一个重要问题。 短消息下发 成功率也直接影响着用户的体 -险。 短消息下发成功率不高是因为短消息下发给用户终端时会出错。 出错的 原因包括两大类： 网络原因错误和用户原因错误。 其中， 网络原因错误主要 指参与短消息业务的各种网元因为处理能力或其他问题产生的错误， 这类错 误是用户无法控制的。 用户原因错误主要指由于用户原因而发生的错误， 例 如， 用户手机内存满、 用户关机、 寻呼无响应以及无效目的号码等错误。 发明人发现， 在实际应用过程中， 经常会发生由用户原因错误导致的短 消息下发失败， 而主叫端和被叫端均不知道由用户原因错误导致了短消息下 发失败， 从而影响了用户的体验。 发明内容 本发明的主要目的在于提供一种短消息处理方案， 以至少解决上述的相 关技术中由用户原因错误导致的短消息下发失败引起的影响用户体验的问 题。 为了实现上述目的， 根据本发明的一个方面， 提供了一种短消息处理方 法。 该方法包括： 短消息中心确定由于用户原因错误导致短消息转发失败； 短消息中心向短消息的被叫端或主叫端发送通知消息， 通知主叫端或被叫端 由于用户原因错误导致短消息转发失败。 为了实现上述目的，根据本发明的另一个方面，提供了一种短消息中心。 该短消息中心包括： 确定模块， 用于确定由于用户原因错误导致短消息转发
失败； 发送模块， 用于向短消息的被叫端或主叫端发送通知消息， 通知主叫 端或被叫端由于用户原因错误导致短消息转发失败。 通过本发明， 釆用短消息中心确定用户原因错误导致短消息转发失败， 并通知主叫端或被叫端的方式， 解决了相关技术中由用户原因错误导致的短 消息下发失败引起的影响用户体验的问题，进而达到了提高用户体验的效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中： 图 1是 居本发明实施例的用户原因错误通知架构图； 图 2是 居本发明实施例的短消息处理方法的流程图； 图 3是 居本发明实施例的短消息处理方法的具体的流程图； 图 4是 居本发明实施例的短消息中心的结构框图； 图 5是 居本发明实施例的发送模块的一种结构框图； 图 6是才艮据本发明实施例的发送模块的另一种结构框图； 以及 图 7是 居本发明实施例的短消息中心的具体的结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互组合。 实施例一 图 1是 居本发明实施例的用户原因错误通知架构图， 该架构中包括短 消息中心、 主叫用户和被叫用户， 短消息中心通过无线网络与主叫用户和被 叫用户进行消息的交互。 本发明实施例就是基于该架构实现的。 本发明实施例提供了一种短消息处理方法。 图 2是 居本发明实施例的 短消息处理方法的流程图， 如图 2所示， 该方法包括：
步骤 S202, 短消息中心确定由于用户原因错误导致短消息转发失败； 步骤 S204 , 短消息中心向短消息的被叫端或主叫端发送通知消息， 通知 主叫端或被叫端由于用户原因错误导致短消息转发失败。 该实施例中， 短消息中心在确定由于用户原因错误导致短消息转发失败 后， 通知主叫端或被叫端由于用户原因错误导致短消息转发失败， 从而使得 主叫端或被叫端能够据此进行相应的处理， 提高了用户的体验。 并且， 本实 施例主要针对用户错误进行改进， 提高消息下发成功率。 例如， 在本发明实施例的一种优选实施方式中， 如果短消息中心确定用 户原因错误的类型为被叫端内存满错误， 则短消息中心可以向被叫端发送通 知消息， 该通知消息用于通知被叫端释放内存， 其中， 该通知消息为闪信。 其中， 在转发短消息失败的情况下， 短消息中心会接收到错误码， 不同的错 误码用来表示不同的错误类型， 从而短消息中心可以根据该错误码的内容确 定用户原因错误的类型为被叫端内存满错误。 该实施例在被叫端内存满时， 通知被叫端释放内存， 从而克服了用户原因错误， 使得短消息能够被正常接 收， 提高了短消息下发成功率。 同时， 由于闪信不占用户空间的短消息内存， 在用户终端内存已满的情况下， 用户终端也能够收到通知消息， 增强了该实 施例的实用性。 并且， 闪信能够自动显示于用户终端主界面之上， 提示效果 也比普通短消息好。 或者， 在本发明实施例的另一种优选实施方式中， 如果短消息中心确定 用户原因错误的类型为被叫端寻呼无响应错误， 则短消息中心向主叫端发送 通知消息，该通知消息用于通知主叫端暂时不要发送短消息给被叫端。其中， 在转发短消息失败的情况下， 短消息中心会接收到错误码， 不同的错误码用 来表示不同的错误类型， 从而短消息中心可以根据该错误码的内容确定用户 原因错误的类型为被叫端寻呼无响应错误。该实施例在被叫端寻呼无响应时， 通知主叫端暂时不发送短消息给被叫端， 从而减少了向该被叫端发送的短消 息的数量， 提高了短消息下发成功率。 当用户原因错误类型为其他类型的错误时， 短消息中心也可以才艮据错误 码来进行确定错误的类型， 并才艮据用户原因错误类型通知主叫端或被叫端， 使主叫端或被叫端能够进行相应的操作。 优选地， 短消息中心向主叫端发送的上述通知消息为闪信。 由于闪信不
占用户空间的短消息内存， 从而可以降低用户终端内存的负荷。 并且， 闪信 能够自动显示于用户终端主界面之上， 提示效果也比普通短消息好。 在本发明实施例的又一种优选实施方式中， 短消息中心确定由于用户原 因错误导致短消息转发失败之后， 短消息中心可以记录由于用户原因错误导 致被叫端接收短消息失败， 并在短消息中心再次接收到发给该被叫端的短消 息时， 短消息中心可以拒绝转发该短消息或者也可以尝试向该被叫端转发该 短消息。 优选地， 短消息中心可以在确定用户原因错误为临时性错误， 尝试 向被叫端下发接收到的短消息；而在确定该用户原因错误不是临时性错误时， 拒绝转发该短消息。 在该实施例中， 短消息中心在确定被叫用户由于用户原 因错误导致接收短消息失败的情况下， 选择性地不向该用户发送短消息， 从 而减少再次发生用户原因错误的可能性， 在用户原因错误为临时性错误时， 也就是错误随时有可能消除时， 短消息中心也可以尝试下发该短消息， 这同 样能够提高短消息的下发成功率。 实施例二 图 3是 居本发明实施例的短消息处理方法的具体的流程图， 如图 3所 示， 该方法包括： 步骤 S301 , 为短消息中心系统配置用户通知策略。 例如， 针对被叫用户 手机内存满错误， 配置的策略是给被叫用户发送通知闪信， 提示用户删除本 地短消息以释放空间。 针对被叫寻呼无响应错误， 配置的策略是向主叫用户 发送通知消息， 提示主叫用户此时被叫用户寻呼无响应， 暂时不要再发送短 信给此用户， 该通知消息可以是闪信。 针对其他用户原因错误， 也都可以配 置类似的策略。 步骤 S302, 短消息中心判断下发的消息是起呼消息还是通知消息， 如果 ^^呼消息， 则进入步骤 S303 , 如果是通知消息则进入步骤 S307。 步骤 S303 , 对于起呼消息， 短消息中心按照现有流程正常处理。 在下发 短消息之前， 检查该消息目的用户的状态是否为失败， 如果状态为成功， 则 直接下发， 如果为失败， 则根据配置决定是尝试下发还是直接返回上一次失 败的错误码。 具体地， 当失败原因为临时性的原因， 如被叫用户寻呼无响应 这种随时可能被克月艮的错误时， 则尝试下发； 当失败原因为非临时性错误时， 如被叫用户欠费、 被叫用户未定制某种业务这些需要长时间才能被克服的错
误时， 拒绝下发该消息， 直接返回上一次失败的错误码。 其中， 错误码能够 指示错误类型。 步骤 S304,短消息中心在接收到上一步下发短消息的响应后，进行判断。 如果该响应为成功，则检查本消息目的用户的上一条消息的状态是否为失败， 如果本消息目的用户的上一条消息的状态是失败，则修改该用户状态为成功。 如果该响应为失败， 则进入步骤 S305。 步骤 S305 , 根据用户原因错误的类型以及系统配置的通知策略， 短消息 中心向本消息的主叫或被叫用户发送通知消息， 该通知消息可以是闪信。 步骤 S306 , 短消息中心记录本消息的目的用户的状态为失败， 并记录失 败原因， 供步骤 S303中判断某用户上一条短消息状态时使用。 步骤 S307 , 对于通知消息的响应消息， 不再发送通知消息， 以便避免通 知消息在短消息中心系统中发生循环。 本实施例在原有短消息业务核心流程的基础上， 增加了用户原因通知流 程。 当短消息下发遇到用户原因错误时， 可以才艮据错误原因， 向主叫用户或 被叫用户发送提示消息， 有效减少了再次发生类似用户原因错误的可能性， 从而提高了短消息的下发成功率。 实施例三 对应于上述方法实施例， 本发明实施例还提供了一种短消息中心， 该短 消息中心可以用于实现实施例一和实施例二的方法。 图 4是才艮据本发明实施 例的短消息中心的结构框图， 该短消息中心包括： 确定模块 42 , 用于确定由 于用户原因错误导致短消息转发失败； 发送模块 44 , 耦合至确定模块 42 , 用于向短消息的被叫端或主叫端发送通知消息， 通知主叫端或被叫端由于用 户原因错误导致短消息转发失败。 图 5是 居本发明实施例的发送模块的一种结构框图， 优选地， 该确定 模块包括： 第一确定子模块 52 , 用于确定用户原因错误的类型为被叫端内存 满错误； 第一发送子模块 54 , 耦合至第一确定子模块 52 , 用于向被叫端发 送通知消息， 通知消息用于通知被叫端释放内存， 其中， 该通知消息为闪信。 图 6是 居本发明实施例的发送模块的另一种结构框图， 优选地， 第二 确定子模块 62 , 用于确定用户原因错误的类型为被叫端寻呼无响应错误； 第
二发送子模块 64 , 耦合至第二确定子模块 62 , 用于向主叫端发送通知消息， 该通知消息用于通知主叫端暂时不要发送短消息给被叫端。 其中， 该通知消 息可以为闪信。 图 7是 居本发明实施例的短消息中心的具体的结构框图， 该短消息中 心还包括： 记录模块 72 , 用于记录被叫端由于用户原因错误导致接收短消息 失败； 接收模块 74 , 耦合至记录模块 72 , 用于再次接收到发给被叫端的短 消息； 处理模块 76 , 耦合至接收模块 74 , 用于拒绝发送接收模块接收到的 短消息或尝试向被叫端下发接收模块接收到的短消息。 优选地， 如果短消息中心确定用户原因错误为临时性错误， 处理模块 76 尝试向被叫端下发接收到的短消息； 否则， 处理模块 76 拒绝发送接收到的 短消息。 综上所述， 本发明实施例在短消息下发遇到用户原因错误时， 可以才艮据 错误原因， 向主叫用户或被叫用户发送提示消息， 有效减少了再次发生类似 用户原因错误的可能性， 从而提高了短消息的下发成功率。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 并 且在某些情况下， 可以以不同于此处的顺序执行所示出或描述的步骤， 或者 将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软件 结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的 ^"神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。
BACKGROUND A short message center is responsible for storing and forwarding short messages, and is a core network element of a short message service. For a long time, the low success rate of short message delivery is an important issue for short message services. The success rate of short message delivery also directly affects the user's body-risk. The success rate of sending a short message is not high because an error occurs when a short message is sent to the user terminal. There are two main reasons for errors: network cause errors and user cause errors. Among them, the network cause error mainly refers to errors caused by various processing factors or other problems of various network elements participating in the short message service, such errors are beyond the control of the user. User-related errors mainly refer to errors that occur due to user reasons, such as errors such as the user's mobile phone full memory, user shutdown, paging non-response, and invalid destination number. The inventor has found that in the actual application process, the short message delivery failure caused by the user's cause error often occurs, and neither the calling end nor the called end knows that the short message delivery failure is caused by the user's cause error, thereby affecting The user experience. SUMMARY OF THE INVENTION A main object of the present invention is to provide a short message processing solution to solve at least the problem of affecting user experience caused by a failure of a short message transmission caused by a user cause error in the related art. In order to achieve the above object, according to an aspect of the present invention, a short message processing method is provided. The method includes: the short message center determines that the short message forwarding fails due to a user error; the short message center sends a notification message to the called end or the calling end of the short message, notifying that the calling end or the called end is short due to the user reason error Message forwarding failed. In order to achieve the above object, according to another aspect of the present invention, a short message center is provided. The short message center includes: a determining module, configured to determine that the short message is forwarded due to a user error The sending module is configured to send a notification message to the called end or the calling end of the short message, and notify the calling end or the called end that the short message forwarding fails due to the user reason error. Through the invention, the short message center is used to determine that the user's cause error causes the short message to be forwarded, and the calling party or the called party is notified, which solves the impact of the short message sending failure caused by the user's cause error in the related art. The problem of experience, in turn, achieves the effect of improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a block diagram of a user cause error notification in the embodiment of the present invention; FIG. 2 is a flowchart of a short message processing method in an embodiment of the present invention; FIG. 3 is a short message processing in the embodiment of the present invention. FIG. 4 is a structural block diagram of a short message center according to an embodiment of the present invention; FIG. 5 is a structural block diagram of a transmitting module according to an embodiment of the present invention; FIG. 6 is a block diagram of an embodiment of the present invention. Another structural block diagram of the transmitting module; and FIG. 7 is a specific structural block diagram of the short message center in the embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. Embodiment 1 FIG. 1 is a structural diagram of a user cause error notification according to an embodiment of the present invention. The architecture includes a short message center, a calling user, and a called user. The short message center performs a wireless network with the calling user and the called user. The interaction of the message. The embodiment of the invention is implemented based on the architecture. The embodiment of the invention provides a short message processing method. 2 is a flowchart of a short message processing method according to an embodiment of the present invention. As shown in FIG. 2, the method includes: Step S202, the short message center determines that the short message forwarding fails due to the user's reason error; Step S204: The short message center sends a notification message to the called end or the calling end of the short message, notifying the calling end or the called end that the user is wrong due to the user Causes short message forwarding to fail. In this embodiment, after determining that the short message forwarding fails due to a user error, the short message center notifies the calling end or the called end that the short message forwarding fails due to a user error, so that the calling end or the called end can This is handled accordingly, improving the user experience. Moreover, the embodiment mainly improves the user error and improves the success rate of the message delivery. For example, in a preferred embodiment of the embodiment of the present invention, if the short message center determines that the type of the user cause error is the called terminal full memory error, the short message center may send a notification message to the called end, and the notification message is used by the notification message. The memory of the called party is released, wherein the notification message is a flash message. In the case that the short message fails to be forwarded, the short message center receives the error code, and different error codes are used to indicate different error types, so that the short message center can determine the type of the user cause error according to the content of the error code. The memory is full for the called end. In this embodiment, when the called end memory is full, the called end is notified to release the memory, thereby overcoming the user's cause error, so that the short message can be normally received, and the success rate of the short message is improved. At the same time, since the flash message does not occupy the short message memory of the user space, the user terminal can also receive the notification message when the user terminal memory is full, which enhances the practicability of the embodiment. Moreover, the flash message can be automatically displayed on the main interface of the user terminal, and the prompt effect is better than the ordinary short message. Or, in another preferred embodiment of the embodiment of the present invention, if the short message center determines that the type of the user cause error is the called end page no response error, the short message center sends a notification message to the calling end, the notification The message is used to notify the calling party not to send a short message to the called party. In the case that the short message fails to be forwarded, the short message center receives the error code, and different error codes are used to indicate different error types, so that the short message center can determine the type of the user cause error according to the content of the error code. No response error for the called end page. In this embodiment, when the called end page is not responding, the calling party is notified that the short message is not sent to the called end temporarily, thereby reducing the number of short messages sent to the called end, and improving the success rate of sending the short message. . When the user causes the error type to be another type of error, the short message center can also determine the type of the error according to the error code, and notify the calling or called terminal according to the user reason error type, so that the calling end Or the called end can perform the corresponding operation. Preferably, the notification message sent by the short message center to the calling end is a flash message. Because of the flash letter The short message memory of the user space can reduce the load of the user terminal memory. Moreover, the flash message can be automatically displayed on the main interface of the user terminal, and the prompt effect is better than the ordinary short message. In still another preferred embodiment of the present invention, after the short message center determines that the short message forwarding fails due to a user error, the short message center may record that the called party fails to receive the short message due to a user error, and is short. When the message center receives the short message sent to the called end again, the short message center may refuse to forward the short message or may attempt to forward the short message to the called end. Preferably, the short message center may determine that the user cause error is a temporary error, and attempt to deliver the received short message to the called terminal; and when it is determined that the user cause error is not a temporary error, the short message is refused to be forwarded. In this embodiment, the short message center selectively determines that the called user fails to receive the short message due to the user's cause error, thereby reducing the possibility of reoccurring the user's cause error. When the user's cause error is a temporary error, that is, when the error is likely to be eliminated at any time, the short message center can also try to deliver the short message, which can also improve the success rate of the short message. Embodiment 2 FIG. 3 is a specific flowchart of a short message processing method according to an embodiment of the present invention. As shown in FIG. 3, the method includes: Step S301: Configure a user notification policy for a short message center system. For example, if the called user's mobile phone is full of errors, the configured policy is to send a notification flash to the called user, prompting the user to delete the local short message to release the space. For the called page no response error, the configured policy is to send a notification message to the calling user, prompting the calling user that the called user does not respond at this time, and no longer send a short message to the user, the notification message may be flashing. letter. Similar strategies can be configured for other user cause errors. Step S302: The short message center determines whether the sent message is a start message or a notification message. If the message is sent, the process proceeds to step S303, and if it is the notification message, the process proceeds to step S307. Step S303: For the originating message, the short message center processes normally according to the existing process. Before the short message is sent, check whether the status of the user of the message is a failure. If the status is successful, the status is successful. If the status is successful, the status is directly delivered. If the status is successful, the configuration determines whether to attempt to deliver or directly return the previous failed error code. Specifically, when the reason for the failure is temporary, for example, if the called user's page is unresponsive, such as an error that may be ruined at any time, the user attempts to deliver; when the reason for the failure is a non-transitory error, such as called The user owes money, the called user does not customize a certain service, which takes a long time to be overcome. In case of error, refuse to deliver the message and return directly to the last failed error code. Among them, the error code can indicate the type of error. Step S304: After receiving the response of the short message sent by the previous step, the short message center performs the determination. If the response is successful, check whether the status of the previous message of the user of the message is a failure. If the status of the previous message of the user of the message is a failure, the status of the user is modified to be successful. If the response is a failure, it proceeds to step S305. Step S305: The short message center sends a notification message to the calling or called user of the message according to the type of the user's cause error and the notification policy configured by the system, and the notification message may be a flash message. Step S306, the short message center records the status of the destination user of the message as a failure, and records the reason for the failure, and is used when determining a short message status of a user in step S303. Step S307, for the response message of the notification message, the notification message is no longer sent, so as to avoid looping of the notification message in the short message center system. In this embodiment, based on the core process of the original short message service, a user cause notification process is added. When the short message is sent to the user for the cause error, the prompt message may be sent to the calling user or the called user according to the error reason, thereby effectively reducing the possibility of a similar user cause error, thereby improving the short message. The success rate is issued. The third embodiment corresponds to the foregoing method embodiment, and the embodiment of the present invention further provides a short message center, and the short message center can be used to implement the methods of the first embodiment and the second embodiment. 4 is a structural block diagram of a short message center according to an embodiment of the present invention. The short message center includes: a determining module 42 configured to determine that a short message forwarding failure occurs due to a user cause error; and a sending module 44 coupled to the determining module 42 And sending a notification message to the called end or the calling end of the short message, notifying the calling end or the called end that the short message forwarding fails due to the user reason error. 5 is a structural block diagram of a transmitting module according to an embodiment of the present invention. Preferably, the determining module includes: a first determining submodule 52, configured to determine that a type of a user cause error is a memory full error of the called end; The sending sub-module 54 is coupled to the first determining sub-module 52, and configured to send a notification message to the called end, where the notification message is used to notify the called end to release the memory, where the notification message is a flash message. FIG. 6 is another structural block diagram of a transmitting module according to an embodiment of the present invention. Preferably, the second determining sub-module 62 is configured to determine that the type of the user's cause error is a called terminal non-response error; The second sending sub-module 64 is coupled to the second determining sub-module 62, and configured to send a notification message to the calling end, where the notification message is used to notify the calling end that the short message is not sent to the called end temporarily. The notification message may be a flash message. FIG. 7 is a block diagram of a specific structure of a short message center according to an embodiment of the present invention. The short message center further includes: a recording module 72, configured to record that the called end fails to receive the short message due to a user error; the receiving module 74, coupled To the recording module 72, for receiving the short message sent to the called end again; the processing module 76 is coupled to the receiving module 74, for rejecting the short message received by the sending and receiving module or attempting to send the receiving module to the called end Short message to. Preferably, if the short message center determines that the user cause error is a temporary error, the processing module 76 attempts to deliver the received short message to the called end; otherwise, the processing module 76 refuses to send the received short message. In summary, the embodiment of the present invention can send a prompt message to the calling user or the called user according to the error reason when the short message is sent to the user causing the error, which effectively reduces the occurrence of similar user error. The possibility, thereby improving the success rate of short message delivery. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.
Claims
1. 一种短消息处理方法， 其特征在于， 包括: 短消息中心确定由于用户原因错误导致短消息转发失败； 所述短消息中心向所述短消息的被叫端或主叫端发送通知消息， 通 知所述主叫端或所述被叫端由于所述用户原因错误导致所述短消息转发 失败。 A method for processing a short message, comprising: the short message center determining that the short message forwarding fails due to a user error; the short message center sending a notification message to the called end or the calling end of the short message Notifying the calling terminal or the called terminal that the short message forwarding fails due to the user reason error.
2. 根据权利要求 1所述的方法， 其特征在于， 所述短消息中心向所述短消 息的被叫端或主叫端发送通知消息包括： The method according to claim 1, wherein the sending, by the short message center, the notification message to the called end or the calling end of the short message comprises:
所述短消息中心确定所述用户原因错误的类型为所述被叫端内存满 错误； The short message center determines that the type of the user cause error is the called terminal memory full error;
所述短消息中心向所述被叫端发送所述通知消息， 所述通知消息用 于通知所述被叫端释放内存， 其中， 所述通知消息为闪信。 The short message center sends the notification message to the called end, where the notification message is used to notify the called end to release the memory, wherein the notification message is a flash message.
3. 根据权利要求 1所述的方法， 其特征在于， 所述短消息中心向所述短消 息的被叫端或主叫端发送通知消息包括： The method according to claim 1, wherein the sending, by the short message center, the notification message to the called end or the calling end of the short message comprises:
所述短消息中心确定所述用户原因错误的类型为所述被叫端寻呼无 响应错误； Determining, by the short message center, that the type of the user cause error is the called end paging no response error;
所述短消息中心向所述主叫端发送所述通知消息， 所述通知消息用 于通知所述主叫端暂时不要发送短消息给所述被叫端。 The short message center sends the notification message to the calling end, and the notification message is used to notify the calling terminal not to send a short message to the called end temporarily.
4. 根据权利要求 3所述的方法， 其特征在于， 所述通知消息为闪信。 4. The method according to claim 3, wherein the notification message is a flash message.
5. 根据权利要求 1所述的方法， 其特征在于， 在短消息中心确定由于用户 原因错误导致短消息转发失败之后， 所述方法还包括： The method according to claim 1, wherein after the short message center determines that the short message forwarding fails due to a user error, the method further includes:
所述短消息中心记录所述被叫端由于用户原因错误导致接收短消息 失败； The short message center records that the called end fails to receive the short message due to a user error;
所述短消息中心再次接收到发给所述被叫端的短消息； 所述短消息中心拒绝发送接收到的所述短消息或尝试向所述被叫端 下发接收到的所述短消息。 The short message center receives the short message sent to the called end again; the short message center refuses to send the received short message or attempts to deliver the received short message to the called end.
6. 根据权利要求 5所述的方法， 其特征在于， 所述短消息中心拒绝发送接 收到的所述短消息或尝试向所述被叫端下发接收到的所述短消息包括： 如果所述短消息中心确定所述用户原因错误为临时性错误， 则所述 短消息中心尝试向所述被叫端下发接收到的所述短消息； 否则， 所述短 消息中心拒绝发送接收到的所述短消息。 The method according to claim 5, wherein the short message center refuses to send the received short message or attempts to send the received short message to the called end, including: The short message center determines that the user cause error is a temporary error, and the short message center attempts to deliver the received short message to the called terminal; otherwise, the short message center refuses to send the received short message. The short message.
7. —种短消息中心， 其特征在于， 包括： 7. A short message center, characterized in that it comprises:
确定模块， 用于确定由于用户原因错误导致短消息转发失败； 发送模块， 用于向所述短消息的被叫端或主叫端发送通知消息， 通 知所述主叫端或所述被叫端由于所述用户原因错误导致所述短消息转发 失败。 a determining module, configured to determine that the short message forwarding fails due to a user error; the sending module, configured to send a notification message to the called end or the calling end of the short message, to notify the calling end or the called end The short message forwarding failure due to the user cause error.
8. 根据权利要求 7所述的短消息中心， 其特征在于， 所述发送模块包括： 第一确定子模块， 用于确定所述用户原因错误的类型为所述被叫端 内存满错误； The short message center according to claim 7, wherein the sending module comprises: a first determining submodule, configured to determine that the type of the user cause error is the called terminal full memory error;
第一发送子模块， 用于向所述被叫端发送所述通知消息， 所述通知 消息用于通知所述被叫端释放内存， 其中， 所述通知消息为闪信。 And a first sending submodule, configured to send the notification message to the called end, where the notification message is used to notify the called end to release a memory, where the notification message is a flash message.
9. 根据权利要求 7所述的短消息中心， 其特征在于， 所述发送模块包括： 第二确定子模块， 用于确定所述用户原因错误的类型为所述被叫端 寻呼无响应错误； The short message center according to claim 7, wherein the sending module comprises: a second determining submodule, configured to determine that the type of the user cause error is the called end paging no response error ;
第二发送子模块， 用于向所述主叫端发送所述通知消息， 所述通知 消息用于通知所述主叫端暂时不要发送短消息给所述被叫端。 The second sending submodule is configured to send the notification message to the calling end, where the notification message is used to notify the calling terminal not to send a short message to the called end temporarily.
10. 根据权利要求 7所述的短消息中心， 其特征在于， 所述短消息中心还包 括： 10. The short message center according to claim 7, wherein the short message center further comprises:
记录模块， 用于记录所述被叫端由于用户原因错误导致接收短消息 失败； a recording module, configured to record that the called end fails to receive the short message due to a user error;
接收模块， 用于再次接收到发给所述被叫端的短消息； 处理模块， 用于拒绝发送所述接收模块接收到的所述短消息或尝试 向所述被叫端下发所述接收模块接收到的所述短消息。 a receiving module, configured to receive the short message sent to the called end again; the processing module, configured to refuse to send the short message received by the receiving module or attempt to send the receiving module to the called end The short message received.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010276086.2 | 2010-09-01 | ||
| CN2010102760862A CN101951574A (en) | 2010-09-01 | 2010-09-01 | Short message processing method and short message center |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2012027940A1 true WO2012027940A1 (en) | 2012-03-08 |
Family
ID=43454904
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2010/080062 WO2012027940A1 (en) | 2010-09-01 | 2010-12-21 | Short-message processing method and short-message center |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101951574A (en) |
| WO (1) | WO2012027940A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102638777A (en) * | 2011-02-15 | 2012-08-15 | 中兴通讯股份有限公司 | SMS (Short Message Service) sending method and device |
| CN104507059B (en) * | 2014-12-19 | 2018-01-16 | 广东欧珀移动通信有限公司 | A kind of multimedia message transmitting administrative method and multimedia message send managing device |
| CN105991837A (en) * | 2015-03-05 | 2016-10-05 | 西安酷派软件科技有限公司 | Prompting method and device and terminal |
| CN108566628A (en) * | 2018-07-19 | 2018-09-21 | 北京小米移动软件有限公司 | Short message repeating method, device, equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1747567A (en) * | 2004-09-10 | 2006-03-15 | 华为技术有限公司 | Message delivering method and system |
| CN101068381A (en) * | 2007-06-07 | 2007-11-07 | 中兴通讯股份有限公司 | Short message system and short message retransmitting method |
| CN101730021A (en) * | 2009-11-20 | 2010-06-09 | 中国电信股份有限公司 | Processing method and system for insufficient short message storage space of code division multiple access terminal |
-
2010
- 2010-09-01 CN CN2010102760862A patent/CN101951574A/en active Pending
- 2010-12-21 WO PCT/CN2010/080062 patent/WO2012027940A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1747567A (en) * | 2004-09-10 | 2006-03-15 | 华为技术有限公司 | Message delivering method and system |
| CN101068381A (en) * | 2007-06-07 | 2007-11-07 | 中兴通讯股份有限公司 | Short message system and short message retransmitting method |
| CN101730021A (en) * | 2009-11-20 | 2010-06-09 | 中国电信股份有限公司 | Processing method and system for insufficient short message storage space of code division multiple access terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101951574A (en) | 2011-01-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7082313B2 (en) | Secure short message service | |
| US9049677B2 (en) | Method, apparatus and system for paging processing and information displaying | |
| US8855689B2 (en) | Direct SMS message delivery over broadband data networks through an SMS-C | |
| WO2012146088A1 (en) | Missed call notification device and method | |
| WO2009143756A1 (en) | Message service implementation method and device | |
| US9525985B2 (en) | Method for sending short message in multi-mode terminal and multi-mode terminal | |
| WO2012027940A1 (en) | Short-message processing method and short-message center | |
| US20180027028A1 (en) | Terminal and Terminal Call Soft Switching Method | |
| US20180227332A1 (en) | A method and computer program products for probing the status of an ip-based communication connection in order to receive an incoming communication | |
| EP2797285B1 (en) | Method and apparatus for network communication | |
| JP5749746B2 (en) | Call attempt notification | |
| US8743689B2 (en) | Method and apparatus for SMS termination overload protection | |
| US8401173B2 (en) | Telephone-line-connection method | |
| JP4896866B2 (en) | System and method for conditionally attempting emergency call setup | |
| KR20160003266A (en) | Access control method and apparatus | |
| AU2019369205B9 (en) | Exchange, communication system, registration method, and program | |
| JP2012516580A (en) | SMS transport resource control | |
| US20080037734A1 (en) | System and method for fast, reliable setup of voicemail playback | |
| WO2012022074A1 (en) | User information query method and multimedia messaging service center | |
| US20120076282A1 (en) | Telephone notification method and system, signaling monitoring unit and server | |
| JP2019220898A (en) | Radio communication terminal, communication method, and communication program | |
| JP2013150088A (en) | Communication control system and communication control method | |
| WO2011009265A1 (en) | Message delivering method and device used for telecommunication network | |
| KR100671310B1 (en) | System and method for uploading?downloading a multimedia message | |
| CA2596182C (en) | System and method for fast, reliable setup of voicemail playback |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10856626 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 10856626 Country of ref document: EP Kind code of ref document: A1 |