WO2004045233A1 - Procede de transmission de messages multimedia entre differents centres de messagerie multimedia - Google Patents

Procede de transmission de messages multimedia entre differents centres de messagerie multimedia Download PDF

Info

Publication number
WO2004045233A1
WO2004045233A1 PCT/CN2003/000349 CN0300349W WO2004045233A1 WO 2004045233 A1 WO2004045233 A1 WO 2004045233A1 CN 0300349 W CN0300349 W CN 0300349W WO 2004045233 A1 WO2004045233 A1 WO 2004045233A1
Authority
WO
WIPO (PCT)
Prior art keywords
multimedia message
sender
multimedia
report
center
Prior art date
Application number
PCT/CN2003/000349
Other languages
English (en)
French (fr)
Inventor
Fei Tang
Xiaobin Li
Minghai Liu
Bo Zhang
Yong Meng
Weishu Yang
Original Assignee
Huawei Technologies Co., Ltd
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
Application filed by Huawei Technologies Co., Ltd filed Critical Huawei Technologies Co., Ltd
Priority to EP03729804A priority Critical patent/EP1562391B1/en
Priority to AU2003242100A priority patent/AU2003242100A1/en
Priority to DE60315697T priority patent/DE60315697T2/de
Publication of WO2004045233A1 publication Critical patent/WO2004045233A1/zh
Priority to US11/127,759 priority patent/US7616739B2/en

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42382—Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/5307—Centralised arrangements for recording incoming messages, i.e. mailbox systems for recording messages comprising any combination of audio and non-audio components

Definitions

  • the present invention relates to a message forwarding technology, and in particular, to a method for forwarding multimedia messages between different multimedia message centers. Background of the invention
  • Multimedia technology enables people to express and convey information more accurately and vividly.
  • 3G mobile communication networks introduce multimedia to the field of mobile communications.
  • a new type of messaging service multimedia messaging (MMS, Multimedia Messaging Service)
  • MMS Multimedia Messaging Service
  • Short message communication method MMS provides a non-real-time multimedia communication method. Users can send or receive multimedia messages composed of text, images, video, audio, etc. On this platform, richer business applications and better service quality can be derived. .
  • the multimedia message center is responsible for sending messages composed of plain text, pictures, video, audio, and other media formats on the network.
  • the multimedia message center can provide three basic business capabilities: point-to-point business capabilities, point-to-application business capabilities
  • point-to-application business capabilities The service capability applied to the point and can provide two types of extended service capabilities: point-to-multipoint service capability, and application to multipoint service capability.
  • the multimedia message center device is located on the IP network side and connects to the wireless bearer network through a Wireless Application Protocol (WAP) gateway. Therefore, its service implementation is independent of the specific wireless bearer network, and supports GSM, GPRS, WCDMA and CDMA, CDMA2000 and other networks, and support future 3G networks.
  • WAP Wireless Application Protocol
  • the system structure of the multimedia message center equipment is shown in Figure 1.
  • the system interface involved is determined by the constituent network elements.
  • the definition and description of the interface is mainly focused on the standard process of service access.
  • the minimum requirements for the system physical interface specifications are set. To ensure the diversity of the system.
  • FIG. 1 is a structural diagram of a multimedia message center device system in the prior art.
  • the MMS terminal in the figure provides a multimedia message service through an MMS User Agent.
  • the MMS user agent is an application on the multimedia message terminal, which provides users with browsing, Edit and process multimedia messages, and send, receive, and delete messages, and connect to the MMS Relay / Server through the MM1 reference point.
  • the MMS Frame Relay / Server is called Multimedia Messaging Service Center (MMSC).
  • MMSC Multimedia Messaging Service Center
  • the multimedia message center performs protocol conversion, content adaptation, storage, and scheduling of multimedia messages, and completes the transfer of multimedia messages between different multimedia devices.
  • the multimedia message center generates Charging Detail Records (CDRs) for use in Billing.
  • CDRs Charging Detail Records
  • the MMS User Database is connected to the multimedia message center through the MM6 reference point, and stores user information, personalized information, interface information, and so on. In the target network, this database is part of the MSC system and is currently integrated in the MMSC.
  • the external value-added application server (MMS Value Added Service Applications) is connected to the multimedia message center through the MM7 reference point to provide value-added business services.
  • the billing system is connected to the multimedia message center through the MM8 reference point to complete the billing operation of the multimedia message center system.
  • External service devices such as email server, short message center (SMSC) and fax machine are connected to the multimedia message center through the MM3 reference point to provide external business services.
  • the reference point MM4 is an interface between two different multimedia message center, for transmitting messages between different multimedia message center, sending a message should be based on the Simple Mail Transfer Protocol (SMTP, Simple Mail Transfer Protocol) 0 Multimedia News on MM4
  • SMTP Simple Mail Transfer Protocol
  • 3GPP Third Generation Partnership Project
  • FIG. 3 is a flowchart of the MM4 interface protocol message interaction. As shown in Figure 3, the steps for forwarding multimedia messages between different multimedia message centers are:
  • the sender's multimedia message center receives the multimedia message submitted by the sender's terminal. After successfully addressing a peer multimedia message center, the sender's multimedia message center uses the routing forward request message MM4— forward.REQ, select a route for the multimedia message and forward it to the recipient's multimedia message center (Recipient MMSC), and the routing forward request message contains multimedia control information and multimedia message content; accordingly, the receiver's multimedia message center should use the route Forward response message MM4_forwardJ ES as a response, this response message contains the status required in MM4_forward.RES.
  • Table 1 The definitions of the two messages involved in this step are shown in Table 1:
  • a delivery report MM — delivery — repor REQ is generated and sent to the sender's multimedia message center.
  • Receiver Address Mandatory The address of the multimedia message receiver of the original multimedia message.
  • Sender Address Required The multimedia message originator address of the original multimedia message.
  • Date and time Mandatory The date and time (time stamp) that the multimedia message was processed (retrieved, timed out, rejected, etc.).
  • MM status Mandatory The status of the multimedia message, such as retrieved, timed out, and rejected.
  • MM status text Optional Status text corresponding to the status of the multimedia message.
  • the sender's multimedia message center receives the report sent by the receiver's multimedia message center, it responds by sending a report response message MM4_delivey_report.RES, which provides a MM4_delivey_repor REQ request in the response message Status information for processing situations.
  • MM4_delivey_report.RES which provides a MM4_delivey_repor REQ request in the response message Status information for processing situations.
  • MM4_forward.req, MM4_forward.res, MM4_delivey_report.req, and MM4_delivey_report.res are protocol messages of the MM4 interface, and the remaining messages are messages of other interfaces, which are used as a supplement to this process. .
  • multimedia messages can be forwarded between different multimedia message centers.
  • the existing message transmission protocol structure of the MM4 interface can complete the multimedia message forwarding function between different multimedia message centers in the message sending process, when the following situations occur, only the current message transmission protocol structure of the MM4 interface is used. The implementation of corresponding functions will not be completed.
  • the receiver terminal In the process of forwarding multimedia messages between different multimedia message centers, according to the 3GPP protocol, if the receiver terminal is not allowed to generate a transmission report, the receiver terminal will not generate a transmission report back to the receiver even if the sender terminal applies for a transmission report.
  • the sending multimedia message center can only confirm the success of the multimedia message forwarding based on the MM4-forward.RES which will definitely be received. Or not, it is impossible to know exactly whether the multimedia message is correctly delivered from the sender terminal to the receiver terminal. Summary of the invention
  • the main purpose of the present invention is to provide a method for forwarding multimedia messages between different multimedia message centers, so that the sender's multimedia message center can know exactly whether the multimedia messages are correctly delivered from the sender terminal to the receiver terminal.
  • a method for forwarding multimedia messages between different multimedia message centers including the following steps:
  • the sender's multimedia message center receives the multimedia message submitted by the sender's terminal, edits and generates a routing forward request message;
  • the sender's multimedia message center sends the routing forwarding request message generated in step a to the receiver's multimedia message center;
  • the receiving multimedia information center After receiving the routing forwarding request message, the receiving multimedia information center sends a routing forwarding response message to the sending multimedia messaging center;
  • the receiving multimedia message center issues a multimedia message according to the multimedia message related information in the route forwarding request message.
  • the receiving multimedia message center generates a sending report according to the current delivery situation and sends the sending report to the sending multimedia information center.
  • the generated transmission report further includes a field indicating whether the receiving party is allowed to generate the transmission report.
  • the method further includes the steps:
  • the sender's multimedia information center decides whether to generate a transmission report according to the fields in the transmission report that indicate whether the receiver is allowed to generate the transmission report and whether the terminal of the sender requires the transmission report.
  • Send report from sender terminal After receiving the transmission report, the sender's multimedia information center decides whether to generate a transmission report according to the fields in the transmission report that indicate whether the receiver is allowed to generate the transmission report and whether the terminal of the sender requires the transmission report.
  • Send report from sender terminal After receiving the transmission report, the sender's multimedia information center decides whether to generate a transmission report according to the fields in the transmission report that indicate whether the receiver is allowed to generate the transmission report and whether the terminal of the sender requires the transmission report.
  • Send report from sender terminal After receiving the transmission report, the sender's multimedia information center decides whether to generate a transmission report according to the fields in the transmission report that indicate whether the receiver is allowed to generate the transmission report and whether the terminal of the sender requires the transmission report.
  • Send report from sender terminal After receiving the transmission
  • the method further includes the steps:
  • g. Determine whether the sender's multimedia information center generates a send to the sender's terminal Report. If it is generated, the generated transmission report is sent to the terminal of the sender of the current multimedia message; otherwise, no processing is performed.
  • the receiving multimedia message center will generate a sending report and return it to the sending multimedia message center to indicate the current multimedia message delivery situation.
  • the original transmission report of the MM4 interface indicates whether the receiver allows the transmission report to be generated.
  • the sender's multimedia message center will decide whether to generate the transmission report based on the result indicated in the transmission report and whether the terminal of the sender requires the transmission report.
  • the transmission report is sent to the sender terminal of the current multimedia message.
  • the sender's multimedia message center can only confirm the success of the multimedia message forwarding based on the received routing forward request message, which cannot be determined It is a question of knowing whether a multimedia message is correctly delivered from a sender terminal to a receiver terminal.
  • the method can further solve the problems in practical use, such as not being delivered to the receiver's terminal, but being able to charge the sender's terminal.
  • Figure 1 is a structural diagram of a multimedia message center equipment system
  • FIG. 2 is a schematic diagram of interfaces between different multimedia message centers
  • Figure 3 is a flow chart of MM4 interface protocol message interaction
  • FIG. 4 is a flowchart of multimedia message forwarding according to the present invention. Mode of Carrying Out the Invention
  • the core idea of the present invention lies in the following: In the process of forwarding multimedia messages between different multimedia message centers, regardless of whether the receiving terminal allows the sending of a report, the receiving multimedia message center will generate a sending report and return it to the sending multimedia message center. Indicates the current delivery status of the message. This solves the problem that the sender's multimedia message center cannot know exactly whether the multimedia message is correctly delivered from the sender's terminal to the receiver's terminal.
  • MMS Relay / Server A (MMS Relay / Server) is the so-called multimedia message center.
  • the sender's terminal submits to the sender's multimedia message center.
  • the sender's multimedia message center forwards the multimedia message to the receiver's multimedia message center through the MM4 interface implemented by the SMTP protocol.
  • the receiver's multimedia message center completes the delivery of multimedia messages.
  • the multimedia message is delivered to the receiver's terminal.
  • the receiver's multimedia message center will inform the sender's multimedia message center of the current multimedia message delivery situation in the form of a report.
  • the step of implementing multimedia message forwarding in this embodiment includes: Step 401:
  • the sender's multimedia message center receives the multimedia message submitted by the sender's terminal, and edits and generates a routing forward request message MM4_forward.REQ, which is a message.
  • MM4_forward.REQ a routing forward request message
  • the editing here generally refers to the standard format specified by the agreement Generate a message.
  • the multimedia message center in order to complete the transfer of multimedia messages between different multimedia message centers and simultaneously complete the corresponding charging function, when the multimedia message center receives the currently submitted multimedia message, it edits and generates a route containing the charging information. Forward message
  • Step 402 The sender multimedia message center sends the routing request message generated in step 401 to the receiver multimedia message center.
  • Step 403 The receiver's multimedia information center returns a routing forward response message MM4_forward.RES to the sender's multimedia message center, that is, when the receiver's multimedia message center receives the MM4_forward.REQ submitted by the sender's multimedia message center, it sends it to the sender's multimedia message center Return a MM4—forward.RES as a response to the current reception situation.
  • Step 404 The receiver's multimedia message center issues a multimedia message according to the multimedia message related information in MM4_forward.REQ.
  • the receiving multimedia message center performs a multimedia message delivery operation according to the received current multimedia message related information carried in MM4-forward.REQ.
  • Step 405 The receiving multimedia message center generates a delivery report MM4_delivery_report.REQ according to the current delivery situation and sends it to the sending multimedia information center.
  • a corresponding MM4__delivery_report.REQ is generated according to the current multimedia message delivery situation and sent to the sender's multimedia message center of the current multimedia message, so that the sender's multimedia message center can be notified.
  • the status of the current multimedia message delivery is success or failure information, to ensure that the sender's multimedia message center completes the corresponding multimedia message forwarding process and completes the charging function based on the charging information in the MM4_forward.REQ message to implement the sending Party terminal communication fees.
  • the receiving multimedia message center sends a multimedia message to After that, the receiver's multimedia message center will
  • MM4_delivery_report.REQ decides whether to generate and deliver MM4_delivery_report.REQ, which indicates the status of multimedia message delivery, to the receiver's multimedia message center. This will occur when the receiver terminal is not allowed to generate MM4_delivery__report.REQ.
  • the sender's multimedia message center cannot receive the MM4_delivery_report.REQ, which indicates the delivery of the multimedia message, and can only confirm the success of the multimedia forwarding based on the MM4_forward.RES, which will definitely receive the routing forward response message, and it is impossible to know for sure The issue is whether the multimedia message is correctly delivered by the sender terminal to the receiver terminal.
  • the receiver multimedia message center may not necessarily send a transmission report to the receiver multimedia message center.
  • the sender's multimedia message center cannot charge the sender's terminal based on whether the multimedia message is successfully delivered. It can only complete the charge operation of the sender's terminal based on the success of the multimedia forwarding carried in MM4_forward.RES. This may cause the sender's Terminal submission The multimedia message is not delivered to the recipient terminal, has been charged the sender terminal issues.
  • the receiving multimedia message center after the receiving multimedia message center finishes sending the multimedia message, regardless of whether the receiving terminal is allowed to generate MM4_delivery_report.REQ, the receiving multimedia message center will generate a MM4_delivery_report.REQ to the sending multimedia message center, indicating that The current delivery situation of the multimedia message, so that the sender's multimedia message center can know exactly the current delivery situation of the multimedia message and correctly complete the charging function of the current multimedia message.
  • the sender's multimedia message center After receiving the MM4_delivery_report.REQ sent by the receiver's multimedia message center, the sender's multimedia message center will ⁇ according to the status information of MM4_delivery_report.REQ and the sender's terminal to It is required to generate a new sending report and send it to the sender terminal to inform the user of the delivery of the multimedia message submitted.
  • the present invention extends the MM4 interface delivery report MM4_delivery_report.REQ by adding an indication Whether the receiver is allowed to generate the field of MM4__delivery_report.REQ. As shown in Table 4, this embodiment is an extended field for sending a report MM4_delivery_report.REQ message:
  • Table 4 Step 406 After receiving the MM4_delivery_report.REQ, the multimedia information center of the sender, according to the information carried in MM4_delivery_report.REQ.
  • MM4 delivery—repor REQ information to decide whether to generate a delivery report sent to the sender terminal.
  • the sending multimedia information center will not generate a sending report to the sending terminal.
  • the receiving terminal allows the sending report and the sending terminal does not require MM4_delivery_reportREQ
  • the sending report sent to the sending terminal is not generated; only when the receiving terminal allows the sending report, the sending terminal Only when MM4_delivery_reportREQ is required, a delivery report sent to the sender terminal is generated.
  • the newly generated transmission report is provided to the sender terminal, and is different from the MM4_delivery_reportREQ sent by the receiver's multimedia message center to the sender's multimedia message center described above, but the transmission to the sender's sending terminal
  • the report is mainly generated according to the aforementioned MM4_delivery_reportREQ, because this is not the key point of the present invention, so it is not described in detail here.
  • Step 407 Determine whether the sender's multimedia message center generates and sends the message to the sender's terminal. If it is generated, send the generated transmission report to the terminal of the sender of the current multimedia message; otherwise, no processing is performed.
  • the receiver multimedia message center will generate a MM4_delivery_report.REQ and return it to the sender multimedia message center, indicating that the current multimedia message is issued. happening.
  • a field indicating whether the receiver is allowed to generate MM4_delivery_report.REQ is added to the original MM4 interface's sending report.
  • the sender's multimedia message center will use the result indicated in the sending report and whether the sending terminal requires the MM4_delivery_report. REQ to determine whether to generate a transmission report sent to the sender terminal, and if it is generated, send the transmission report to the sender terminal of the current multimedia message.
  • the present invention solves the existing multimedia message forwarding process in which the receiver terminal does not generate MM4-delivery-reportREQ, and the sender's multimedia message center can only confirm that the multimedia message is successfully forwarded based on the received MM4-forward.RES. Whether or not, it is impossible to know exactly whether the multimedia message is correctly delivered from the sender terminal to the receiver terminal.
  • the present invention can also solve some practical problems such as the multimedia message submitted by the sender terminal is not delivered to the receiver terminal, but the sender terminal fee is charged due to the problems described above.

Description

多媒体消息在不同多媒体消息中心之间转发的方法
技术领域
本发明涉及消息转发技术， 尤其是涉及一种多媒体消息在不同多媒 体消息中心之间转发的方法。 发明背景
在 2G移动通讯时代， 由于网絡带宽的原因， 抑制了数据业务的发 展， SMS短消息业务的自身缺陷难以解决。 随着第三代移动通信系统的 发展， 以它为承载网络的各种数据业务也如雨后春笋般诞生， 且涉及到 的领域比 2G更广阔。
多媒体技术使得人们能够更加准确地和生动地表达和传递信息， 3G 移动通信网络将多媒体引入到移动通信领域， 一种崭新的消息业务一多 媒体消息 （MMS, Multimedia Messaging Service )将从根本上改变人们 的短消息通信方式。 MMS提供了一种非实时的多媒体通信方式， 用户 可以发送或接收由文字、 图象、 视频、 音频等组成的多媒体消息， 在此 平台上可以衍生出更丰富业务应用和提供更好的服务质量。
多媒体消息中心负责在网络上发送由纯文本、 图片、 视频、 音频及 其他媒体格式组成的消息 , 该多媒体消息中心能够提供三种基本业务能 力： 点到点的业务能力、 点到应用的业务能力、 应用到点的业务能力， 并能够提供两种扩展的业务能力： 点到多点的业务能力、 应用到多点的 业务能力。
多媒体消息中心设备位于 IP 网络侧， 通过无线应用协议 ( WAP, Wireless Application Protocol ) 网关实现与无线承载网络的连接， 因此其 业务实现与具体无线承载网络无关， 支持 GSM、 GPRS, WCDMA和 CDMA、 CDMA2000等网络， 并支持未来的 3G网络。
多媒体消息中心设备系统结构如图 1所示， 涉及的系统接口由各组 成网元决定， 接口的定义和描述主要集中在业务接入的标准流程， 同时 对系统物理接口的规范设定了最低要求， 以保证系统的多样性。
图 1是现有技术中多媒体消息中心设备系统结构图， 图中的 MMS 终端通过 MMS用户代理（ MMS User Agent )提供多媒体消息服务， MMS 用户代理是多媒体消息终端上的一个应用， 提供用户浏览、 编辑、 处理 多媒体消息等功能, 以及消息的发送、接收、删除等操作， 并通过 MM1 参考点与 MMS帧中继 /服务器 （MMS Relay/Server)相连，这里的 MMS 帧中继 /服务器就是所说的多媒体消息中心 （MMSC , Multimedia Messaging Service Center )。 多媒体消息中心对多媒体消息进行协议转 换、 内容适配、 存储和调度， 完成多媒体消息在不同多媒体设备之间的 传递操作， 同时， 多媒体消息中心生成计费详单（CDR, Charging Detail Record )用于计费。 MMS用户数据库（ MMS User Database )通过 MM6 参考点与多媒体消息中心相连， 存储用户信息、 个性化信息、 接口信息 等。在目标网络中，该数据库是 MSC系统的一部分，目前集成在 MMSC 中。 外部增值应用服务器（ MMS Value Added Service Applications )通过 MM7 参考点与多媒体消息中心相连， 提供增值业务服务。 计费系统 ( Billing System )通过 MM8参考点与多媒体消息中心相连， 完成多媒 体消息中心系统的计费操作。 电子邮件服务器、 短消息中心 （SMSC ) 和传真机等外部服务设备通过 MM3参考点与多媒体消息中心相连， 提 供外部业务服务。
如图 2所示， 参考点 MM4是不同多媒体消息中心之间的接口， 用 于在不同多媒体消息中心之间传送消息， 消息的发送应当基于简单邮件 传输协议（SMTP, Simple Mail Transfer Protocol )0 多媒体消息在 MM4 接口上进行消息传输所要遵循的消息传输协议结构主要是遵循第三代 合作工程（3GPP, Third Generation Partnership Project )协议规定。
图 3是 MM4接口协议消息交互流程图， 如图 3所示， 多媒体消息 在不同多媒体消息中心之间转发的步骤为：
a、 发送方多媒体消息中心 （ Originator MMSC )接收到发送方终端 提交的多媒体消息， 在成功寻址到某个对等的多媒体消息中心后， 发送 方的多媒体消息中心使用路由前转请求消息 MM4— forward.REQ,为该多 媒体消息选路由前转到接收方多媒体消息中心 （Recipient MMSC ), 路 由前转请求消息中包含了多媒体控制信息和多媒体消息内容； 相应的， 接收方多媒体消息中心应以路由前转响应消息 MM4— forwardJ ES作为 响应， 该响应消息中包含 MM4—forward.RES 中所要求的状态。 本步骤 所涉及的两个消息的定义如表 1所示：
Figure imgf000005_0002
Figure imgf000005_0001
b、 当接收方多媒体消息中心完成多媒体消息的下发以后， 如果接 收方终端不允许产生发送报告， 则接收方多媒体中心就不会生成发送报 告； 如果接收方终端允许产生发送报告， 则根据当前的下发情况生成发 送报告 MM— delivery— repor REQ, 发送到发送方多媒体消息中心， 该发 送报告中仅包含 MMS控制信息。 如表 2所示， 是现有技术中 3GPP规 定的发送^ =艮告 MM4— delivery— reportREQ的消息格式： 信息单元 存在情况 说明
3GPP MMS 版本 必备 本文档所定义接收方多媒体消息中心的
MMS 版本。
消息类型 必备 参考点 MM4 上所用 消息的类型： "
MM4— delivery— report.REQ"。
事务处理 ID 必备 MM4_delivery_report.REQ/
MM4_delivery_report.RES对的标识。
消息 ID 必备 原始多媒体消息的标识。
接收方地址 必备 原始多媒体消息的多媒体消息接收方的地址。 发送方地址 必备 原始多媒体消息的多媒体消息始发方地址。 日期和时间 必备 处理（检索、 超时、 拒绝等）多媒体消息的日 期和时间 （时间戳）。
确认请求 可选 MM4— delivery— report.RES 的请求。
MM状态 必备 多媒体消息的状态， 例如已检索、 已超时和已 拒绝。
MM状态文本 可选 与多媒体消息状态相对应的状态文本。
表 2 c、如果发送方多媒体消息中心收到接收方多媒体消息中心的发送报 告， 则以发送 4艮告响应消息 MM4— delivey_report.RES作为回应， 该响应 消息中提供了 MM4— delivey— repor REQ请求处理情况的状态信息。
对多媒体消息中心而言， 支持 MM4— delivery— reportREQ是必须的。 涉 及发送报告的两个消息的定义如表 3所示： 抽象消息名 消息类型 方向
MM4— delivery— report. 请求 Recipient MMSC -> originator MMSC REQ
MM4_delivery_report. 响应 Originator MMSC -> recipient MMSC RES
表 3 在上述 MM4 接口消息的发送流程中， MM4—forward.req、 MM4_forward.res、 MM4_delivey_report.req和 MM4_delivey_report.res 为 MM4接口的协议消息， 其余消息为其他接口的消息， 是作为该流程 的补充。
通过上述步骤并遵循现有的消息传输协议结构， 能够实现多媒体消 息在不同多媒体消息中心之间转发。
虽然现有的 MM4接口的消息传输协议结构能够在消息发送流程中 完成不同多媒体消息中心之间多媒体消息的转发功能， 但是当出现如下 的情况时， 则只使用当前的 MM4接口的消息传输协议结构将无法完成 相应功能的实现。
在多媒体消息在不同多媒体消息中心之间转发流程中， 按 3GPP协 议规定， 如果接收方终端不允许产生发送报告， 即使发送方终端申请了 发送报告， 接收方终端也不会产生发送报告回送到接收方终端， 根据现 有技术的多媒体消息转发流程， 则在接收方终端不产生发送报告的情况 下， 发送方多媒体消息中心只能根据肯定会收到的 MM4—forward.RES 确认多媒体消息转发的成功与否， 而无法确切知道多媒体消息是否正确 由发送方终端下发到接收方终端。 发明内容
本发明的主要目的在于提供一种多媒体消息在不同多媒体消息中 心之间转发的方法， 以使发送方多媒体消息中心能够确切知道多媒体消 息是否正确由发送方终端下发到接收方终端。
本发明的目的是这样实现的： 一种多媒体消息在不同多媒体消息中 心之间转发的方法， 包括以下步骤：
a、发送方多媒体消息中心接收发送方终端提交的多媒体消息，编辑 生成路由前转请求消息；
b、发送方多媒体消息中心将步骤 a中生成的路由前转请求消息发送 到接收方多媒体消息中心；
c、接收方多媒体信息中心收到路由前转请求消息后，发送路由前转 响应消息给发送方多媒体消息中心；
d、 接收方多媒体消息中心根据路由前转请求消息中的多媒体消息 相关信息进行多媒体消息的下发操作。
e、接收方多媒体消息中心根据当前下发情况生成发送报告并发送给 发送方多媒体信息中心。
所述的方法， 在生成的发送报告中， 还包括一个表明接收方是否允 许生成发送报告的字段。
所述的方法还包括步骤：
f、发送方多媒体信息中心在接收到所述的发送报告后，根据发送报 告中携带的表明接收方是否允许生成发送报告的字段和发送方终端是 否要求得到发送报告的信息， 决定是否生成发送给发送方终端的发送报 告。
所述的方法还包括步骤：
g、 判断发送方多媒体信息中心是否生成发送给发送方终端的发送 报告。 如果生成， 则把所生成的发送报告发送到当前多媒体消息的发送 方终端； 否则不作处理。
在本发明中， 无论接收方终端是否允许产生发送报告， 接收方多媒 体消息中心都会产生一个发送报告返回给发送方多媒体消息中心， 表明 当前多媒体消息的下发情况。 同时， 在原有的 MM4接口的发送报告中 表明接收方是否允许生成发送报告， 发送方多媒体消息中心会根据发送 报告中表明的结果和发送方终端是否要求发送报告来决定是否生成发 送报告， 并把该发送报告发送到当前多媒体消息的发送方终端。 如此， 解决了现有多媒体消息转发流程中， 在接收方终端不产生发送报告的情 况下 , 发送方多媒体消息中心只能根据收到的路由前转请求消息确认多 媒体消息转发成功与否 , 无法确切知道多媒体消息是否正确由发送方终 端下发到接收方终端的问题。
该方法在实际应用中， 比如： 发送计费信息时， 可进一步解决： 由 没有下发到接收方终端， 却能收取发送方终端的费用等现实使用中的问 题。 附图简要说明
图 1是多媒体消息中心设备系统结构图；
图 2是不同的多媒体消息中心之间的接口示意图；
图 3是 MM4接口协议消息交互流程图；
图 4是本发明多媒体消息转发的流程图。 实施本发明的方式
下面结合附图和具体实施例进一步说明本发明的实施方法。 本发明的核心思想在于： 多媒体消息在不同的多媒体消息中心之间 转发的过程中， 不管接收方终端是否允许产生发送报告， 接收方多媒体 消息中心都会产生一个发送报告返回给发送方多媒体消息中心， 表明当 前多某体消息的下发情况。 由此解决发送方多媒体消息中心无法确切知 道多媒体消息是否正确由发送方终端下发到接收方终端的问题。
在另一个专利申请中已提出了一种可以使多媒体消息在不同多媒 体消息中心之间进行信息转发并同时完成相应计费功能的方法， 其实现 的方式为： 对目前的 MM4— forward.REQ消息结构进行相应扩展， 使它 能够通过包括增值业务提供商（VASP )业务应用的代码、 服务代码、 业 务代码、 计费类型、 费率的五个字段， 从而准确地表明当前服务的 VAP 应用、 当前服务的业务以及准确的计费信息， 成功地解决了在不同多媒 体消息中心之间进行信息转发且完成相应计费功能的问题。
本实施例就是以转发计费信息为例来描述本发明的具体实施过程。 本实施例的多媒体信息转发方法所采用的网络环境与图 2所示的一 致， 在该组网图中， MMS中继 /服务器 A ( MMS Relay/Server )就是所 说的多媒体消息中心， 多媒体消息首先由发送方终端提交到发送方多媒 体消息中心， 发送方多媒体消息中心通过采用 SMTP协议实现的 MM4 接口把多媒体消息转发到接收方多媒体消息中心， 接收方多媒体消息中 心完成多媒体消息的下发工作， 最终把多媒体消息下发到接收方终端， 同时接收方多媒体消息中心还会以发送报告的形式告知发送方多媒体 消息中心当前多媒体消息的下发情况。
如图 4所示， 本实施例中实现多媒体消息转发的步骤包括： 步骤 401、 发送方多媒体消息中心接收发送方终端提交的多媒体消 息，编辑生成路由前转请求消息 MM4— forward.REQ,该消息带有标识多 媒体消息的相关信息， 此处所述的编辑一般是指按协议规定的标准格式 生成消息。
在本实施例中， 为了完成多媒体消息在不同多媒体消息中心之间进 行信息转发并同时能够完成相应计费功能， 当多媒体消息中心接收到当 前提交的多媒体消息时， 编辑生成含有计费信息的路由前转消息
MM4— forward.REQ。
步骤 402、 发送方多媒体消息中心将步骤 401 中生成的路由前转请 求消息发送到接收方多媒体消息中心。
步驟 403、 接收方多媒体信息中心回复路由前转响应消息 MM4_forward.RES给发送方多媒体消息中心，即接收方多媒体消息中心 接收到发送方多媒体消息中心提交的 MM4_forward.REQ时， 给发送方 多媒体消息中心回一个 MM4— forward.RES作为当前接收情况的回应。
步骤 404、接收方多媒体消息中心根据 MM4_forward.REQ中的多媒 体消息相关信息进行多媒体消息的下发操作。
该步驟中，接收方多媒体消息中心根据接收到的 MM4—forward.REQ 中携带的当前多媒体消息相关信息进行多媒体消息的下发操作。
步骤 405、 接收方多媒体消息中心根据当前下发情况生成发送报告 MM4— delivery— report.REQ并发送给发送方多媒体信息中心。
接收方多媒体消息中心完成多媒体消息的下发以后， 根据当前多媒 体消息的下发情况生成一条相应的 MM4__delivery— report.REQ发送给当 前多媒体消息的发送方多媒体消息中心， 从而能够告知发送方多媒体消 息中心当前多媒体消息下发的状态是成功或者是失败等信息 , 保证发送 方多媒体消息中心完成相应的多媒体消息转发处理流程和完成根据 MM4_forward.REQ消息中的计费信息而进行的计费功能，实现发送方终 端通讯费的收取。
在现有技术中， 接收方多媒体消息中心在完成多媒体消息的下发以 后， 接收方多媒体消息中心会根据接收方终端是否允许生成
MM4_delivery_report.REQ 决定是否给接收方多媒体消息中心生成并下 发表征多媒体消息下发状态的 MM4— delivery— report.REQ,这样就会出现 在接收方终端不允许产生 MM4—delivery__report.REQ的情况下， 发送方 多媒体消 息 中 心接收不到表征多媒体消 息下发情况的 MM4— delivery— report.REQ, 只能根据肯定会收到的路由前转响应消息的 MM4_forward.RES确认多媒体转发成功与否，无法确切知道多媒体消息 是否正确由发送方终端下发到接收方终端的问题， 同时由于接收方终端 可以不产生发送报告， 则接收方多媒体消息中心也就不一定发送发送报 告给接收方多媒体消息中心， 则发送方多媒体消息中心就不能根据多媒 体消息是否下发成功对发送方终端计费， 只能根据 MM4_forward.RES 所携带多媒体转发成功与否来完成对发送方终端的计费操作 , 这样有可 能导致发送方终端提交的多媒体消息没有下发到接收方终端， 却收取了 发送方终端的费用的问题。 本实施例中， 在接收方多媒体消息中心完成 多媒体消息的下发以后 ， 不管接收方终端是否允许产生 MM4_delivery_report.REQ , 接收方多媒体消息中心都会产生一个 MM4_delivery_report.REQ回给发送方多媒体消息中心，表明当前多媒体 消息的下发情况， 从而使发送方多媒体消息中心能够确切的知道当前多 媒体消息的下发情况并正确的完成当前多媒体消息的计费功能。
发送方多媒体消息中心在接收到接收方多媒体消息中心发送的 MM4— delivery— report.REQ以后，会才^据 MM4— delivery— report.REQ的状 态信息和发送方终端对 MM4— delivery— repor REQ的要求生成新的发送 报告发送给发送方终端， 告知用户所提交的多媒体消息的下发情况。 为 了决定是否应该生成一个发送给发送方终端的新的发送报告， 本发明在 MM4接口的发送报告 MM4— delivery— report.REQ中扩展增加一个表明接 收方是否允许生成 MM4__delivery—report.REQ的字段。 如表 4所示， 是 本实施例对发送艮告 MM4_delivery_report.REQ消息的扩展字段：
Figure imgf000013_0001
表 4 步骤 406、 发送方多媒体信息中 心在接收到所述的 MM4— delivery— report.REQ后，根据 MM4— delivery— report.REQ中携带的
MM4— delivery— repor REQ 的信息来决定是否生成发送给发送方终端的 发送报告。
这里， 会有几种情况出现： 当接收方终端不允许产生发送报告时， 不管发送方终端是否要求得到 MM4— delivery—reportJREQ,发送方多媒体 信息中心都不会产生发送给发送方终端的发送报告； 当接受方终端允许 产生发送报告而发送方终端不要求得到 MM4— delivery— reportREQ时， 也不会产生发送给发送方终端的发送报告； 只有当接收方终端允许产生 发送报告， 发送方终端又要求得到 MM4_delivery— reportREQ时， 才会 产生发送给发送方终端的发送报告。 新生成的这个发送报告是提供给发 送方终端的， 与前面所述的接收方多媒体消息中心发送给发送方多媒体 消息中心的 MM4— delivery— reportREQ有一些区别 , 但该发送给发送方 发送终端的报告主要是依据前面所述的 MM4— delivery— reportREQ生成 的， 因为这不是本发明的关键点所在， 所以， 在此并不详细描述。
步骤 407、 判断发送方多媒体消息中心是否生成发送给发送方终端 的发送报告， 如果生成， 则把所生成的发送报告发送到当前多媒体消息 的发送方终端； 否则不作处理。
在本发明中， 不管接收方终端是否允许产生 MM4— delivery—report. REQ , 接收方多媒体消息中心都会产生一个 MM4— delivery— report.REQ 返回给发送方多媒体消息中心， 表明当前多媒体消息的下发情况。 同时 在原有的 MM4接口的发送报告中增加一个表明接收方是否允许生成 MM4_delivery_report.REQ的字段，发送方多媒体消息中心会根据发送报 告中表明的结果和发送方终端是否要求得到 MM4— delivery— report.REQ 来决定是否生成发送给发送方终端的发送 告， 如果生成， 就把该发送 报告发送到当前多媒体消息的发送方终端。 因此， 本发明解决了现有 多媒体消息转发流程中， 接收方终端不产生 MM4— delivery—reportREQ 的情况下，发送方多媒体消息中心只能根据所收到的 MM4— forward.RES 确认多媒体消息转发成功与否， 无法确切知道多媒体消息是否正确由发 送方终端下发到接收方终端的问题。 同时， 本发明还可解决一些因为上 述问题所导致的发送方终端提交的多媒体消息没有下发到接收方终端， 却收取发送方终端费用等实际应用中的问题。
以上所述， 仅为本发明较佳的具体实施方式， 但本发明的保护范围 并不局限于此， 任何熟悉该技术的人在本发明所揭露的技术范围内， 可 轻易想到的变化或替换， 都应涵盖在本发明的保护范围之内。

Claims

权利要求书
1、 一种多媒体消息在不同多媒体消息中心之间转发的方法， 其特 征在于， 该方法包括：
a、发送方多媒体消息中心接收发送方终端提交的多媒体消息，编辑 生成路由前转请求消息；
b、发送方多媒体消息中心将步骤 a中生成的路由前转请求消息发送 到接收方多媒体消息中心；
c、接收方多媒体信息中心收到路由前转请求消息后，发送路由前转 响应消息给发送方多媒体消息中心；
d、 接收方多媒体消息中心根据路由前转请求消息中的多媒体消息 相关信息进行多媒体消息的下发操作；
e、接收方多媒体消息中心根据当前下发情况生成发送报告并发送给 发送方多媒体信息中心。
2、如权利要求 1所述的方法， 其特征在于， 步骤 e中所述的发送报 告中， 进一步包括一个表明接收方是否允许生成发送报告的字段。
3、 如权利要求 2所述的方法， 其特征在于， 该方法还包括步骤： f、发送方多媒体信息中心在接收到所述的发送报告后，根据发送报 告中携带的表明接收方是否允许生成发送报告的字段和发送方终端是 否要求得到发送报告的信息， 决定是否生成发送给发送方终端的发送报 告。
4、 如权利要求 3所述的方法， 其特征在于， 该方法还包括步驟： g、 判断发送方多媒体信息中心是否生成发送给发送方终端的发送 报告， 如果生成， 则把所生成的发送报告发送到当前多媒体消息的发送 方终端； 否则不作处理。
PCT/CN2003/000349 2002-11-12 2003-05-14 Procede de transmission de messages multimedia entre differents centres de messagerie multimedia WO2004045233A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP03729804A EP1562391B1 (en) 2002-11-12 2003-05-14 A method for transmitting a multimedia message between different multimedia message centers
AU2003242100A AU2003242100A1 (en) 2002-11-12 2003-05-14 A method for transmitting multimedia message between different multimedia message center
DE60315697T DE60315697T2 (de) 2002-11-12 2003-05-14 Verfahren zum Senden von Multimedianachrichten zwischen unterschiedlichen Multimedia-Nachrichtendiestzentren
US11/127,759 US7616739B2 (en) 2002-11-12 2005-05-11 Method for forwarding multimedia messages between different multimedia messaging service centers

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN02149290.5 2002-11-12
CN02149290.5A CN1249965C (zh) 2002-11-12 2002-11-12 多媒体消息在不同多媒体消息中心之间转发的方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/127,759 Continuation US7616739B2 (en) 2002-11-12 2005-05-11 Method for forwarding multimedia messages between different multimedia messaging service centers

Publications (1)

Publication Number Publication Date
WO2004045233A1 true WO2004045233A1 (fr) 2004-05-27

Family

ID=32304071

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2003/000349 WO2004045233A1 (fr) 2002-11-12 2003-05-14 Procede de transmission de messages multimedia entre differents centres de messagerie multimedia

Country Status (8)

Country Link
US (1) US7616739B2 (zh)
EP (1) EP1562391B1 (zh)
CN (1) CN1249965C (zh)
AT (1) ATE370630T1 (zh)
AU (1) AU2003242100A1 (zh)
DE (1) DE60315697T2 (zh)
ES (1) ES2291638T3 (zh)
WO (1) WO2004045233A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007000091A1 (fr) * 2005-06-27 2007-01-04 Huawei Technologies Co., Ltd. Procédé et système destinés à limiter les temps de transfert d’un message multimédia pour le centre de service de messagerie multimédia mmsc

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1219081B1 (en) * 1999-10-08 2011-03-30 Nokia Corporation Location sensitive multimedia messaging (mms)
DE10325889A1 (de) * 2003-06-06 2004-12-23 Siemens Ag Verfahren zum Übertragen von Nachrichten
CN1332571C (zh) * 2004-06-28 2007-08-15 华为技术有限公司 在网络间转发多媒体消息的方法
US7876766B1 (en) * 2004-11-22 2011-01-25 Syniverse Icx Corporation Method and apparatus to enable interoperation between multi-media messaging service centers
JP4728348B2 (ja) * 2004-12-28 2011-07-20 サムスン エレクトロニクス カンパニー リミテッド マルチメディアメッセージ管理方法及びシステム
CN101098509B (zh) * 2007-07-17 2013-01-16 中兴通讯股份有限公司 接口递送报告消息的传输方法
WO2009058648A1 (en) * 2007-10-30 2009-05-07 Sybase 365, Inc. System and method for enhanced message delivery
US7746864B1 (en) 2008-04-30 2010-06-29 Cello Partnership System and method for routing inter-carrier short message service or multimedia message service messages
US8515467B2 (en) * 2008-06-25 2013-08-20 Microsoft Corporation Adapter for synchronizing data over different networks
CN101330664B (zh) * 2008-07-21 2012-07-25 华为技术有限公司 多媒体业务的实现方法、系统和装置
US8959232B2 (en) * 2008-12-30 2015-02-17 At&T Mobility Ii Llc IMS and MMS interworking
US8713075B1 (en) * 2009-03-24 2014-04-29 Sprint Communications Company L.P. Inter-carrier communications for multimedia-message delivery
WO2012092679A1 (en) * 2011-01-06 2012-07-12 Research In Motion Limited Delivery and management of status notifications for multiple message formats
CA2823810C (en) 2011-01-06 2016-08-09 Research In Motion Limited Delivery and management of status notifications for group messaging
CN102595348A (zh) * 2012-02-20 2012-07-18 华为技术有限公司 获取消息的转发报告的方法、发送方装置和消息处理系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5497373A (en) * 1994-03-22 1996-03-05 Ericsson Messaging Systems Inc. Multi-media interface
WO1998019438A1 (en) * 1996-10-29 1998-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement for handling of multimedia messages in a telecommunication system
EP1085774A2 (en) * 1999-09-16 2001-03-21 AT&T Corp. H.323 Mobility architecture for terminal user and service mobility

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI104667B (fi) * 1997-07-14 2000-04-14 Nokia Networks Oy Liittymäpalvelun toteuttaminen
FI109067B (fi) * 1999-01-29 2002-05-15 Nokia Corp Maksunosoitus
FI107425B (fi) * 1999-03-16 2001-07-31 Nokia Mobile Phones Ltd Menetelmä ja järjestelmä multimediaan liittyvän informaation välittämiseksi pakettikytkentäisessä solukkoradioverkossa
US6282274B1 (en) * 1999-07-09 2001-08-28 Telcordia Technologies, Inc. Selectable billing options for a single communications account
FI111899B (fi) * 2000-06-16 2003-09-30 Nokia Corp Menetelmä laskutuksen kohdentamiseksi sanomien välitysjärjestelmässä, välitysjärjestelmä, palvelin ja päätelaite
FI114364B (fi) * 2000-11-22 2004-09-30 Nokia Corp Datan siirto
GB0031459D0 (en) * 2000-12-22 2001-02-07 Nokia Networks Oy Charging in a communication system
EP1255416B1 (en) * 2001-05-04 2011-04-06 Siemens Aktiengesellschaft Method and medium for storing and accessing MMS (Multimedia Messaging Service) information
ES2281388T3 (es) * 2001-06-27 2007-10-01 Siemens Aktiengesellschaft Metodos, dispositivos y programa software para procesar y/o evaluar mensajes relacionados con mms (servicio de mensajeria multimedia).
US20030193967A1 (en) * 2001-12-31 2003-10-16 Gregg Fenton Method, apparatus and system for processing multimedia messages
US7327708B2 (en) * 2002-04-25 2008-02-05 Inet Technologies, Inc. Multimedia traffic optimization
US9148216B2 (en) * 2003-07-30 2015-09-29 Globecomm Systems Inc. Distributed satellite-based communications network and method of providing interactive communications services using the same
US20050108417A1 (en) * 2003-11-19 2005-05-19 Serge Haumont System and method for reducing subscriber database loads
GB0402774D0 (en) * 2004-02-09 2004-03-10 Nokia Corp Multimedia message transfer
US7991411B2 (en) * 2004-05-06 2011-08-02 Telecommunication Systems, Inc. Method to qualify multimedia message content to enable use of a single internet address domain to send messages to both short message service centers and multimedia message service centers

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5497373A (en) * 1994-03-22 1996-03-05 Ericsson Messaging Systems Inc. Multi-media interface
WO1998019438A1 (en) * 1996-10-29 1998-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement for handling of multimedia messages in a telecommunication system
EP1085774A2 (en) * 1999-09-16 2001-03-21 AT&T Corp. H.323 Mobility architecture for terminal user and service mobility

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007000091A1 (fr) * 2005-06-27 2007-01-04 Huawei Technologies Co., Ltd. Procédé et système destinés à limiter les temps de transfert d’un message multimédia pour le centre de service de messagerie multimédia mmsc

Also Published As

Publication number Publication date
DE60315697T2 (de) 2008-06-05
EP1562391A4 (en) 2006-09-13
AU2003242100A1 (en) 2004-06-03
US7616739B2 (en) 2009-11-10
CN1249965C (zh) 2006-04-05
EP1562391A1 (en) 2005-08-10
ATE370630T1 (de) 2007-09-15
DE60315697D1 (de) 2007-09-27
CN1501649A (zh) 2004-06-02
EP1562391B1 (en) 2007-08-15
US20050265525A1 (en) 2005-12-01
ES2291638T3 (es) 2008-03-01

Similar Documents

Publication Publication Date Title
US7616739B2 (en) Method for forwarding multimedia messages between different multimedia messaging service centers
JP4334617B2 (ja) 無線装置を介した電子メッセージ通信システム
US7069301B2 (en) Method and apparatus for sending messages from an MMS system
EP2063590B1 (en) A method and system for transmitting email and a push mail server
US20050259652A1 (en) Method for forwarding multimedia messages between multimedia messaging service centers
JP5417438B2 (ja) ショートメッセージ配信に対する課金
WO2010012144A1 (zh) 业务内容信息查询方法、系统和服务提供商平台
EP1804432A1 (en) A method for limiting the forwarding times of the multimedia message for the multimedia messaging service center mmsc and a system thereof
US6980792B2 (en) Billing for replies in a communication system
JP4991772B2 (ja) 伝送方法、交換機
US8300628B2 (en) Method and system for transmitting supplementary data, and communication terminal
WO2007095816A1 (fr) Procédé et système d'acheminement de messages d'un service de messagerie multimédia
TWI241835B (en) Method of transmitting multimedia message in various service environments
EP1750390A1 (en) A method for implementing the charge of the multimedia messaging service
KR101187514B1 (ko) 멀티미디어 메시지 기억 어드레스의 송신 시스템 및 방법
JP5179367B2 (ja) 非同期メッセージの受信通知方法
WO2007033552A1 (fr) Procede pour traiter le message dans le service de message multimedia et systeme y afferant
KR20020072921A (ko) 에스엠에스-엠오를 이용한 무선 단말기와 인스턴트메신저의 메시지 전송 방법
CN100334892C (zh) 一种多媒体消息转发方法
TWI273804B (en) A transforming method of a gateway of the multimedia messaging services inter-exchange between PHS and GPRS network
KR20050122527A (ko) 무선단말기의 멀티미디어 메시지에 대한 회신메시지 전송방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 11127759

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2003729804

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2003729804

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP

WWG Wipo information: grant in national office

Ref document number: 2003729804

Country of ref document: EP