WO2007000091A1 - 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 - Google Patents

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 Download PDF

Info

Publication number
WO2007000091A1
WO2007000091A1 PCT/CN2006/001087 CN2006001087W WO2007000091A1 WO 2007000091 A1 WO2007000091 A1 WO 2007000091A1 CN 2006001087 W CN2006001087 W CN 2006001087W WO 2007000091 A1 WO2007000091 A1 WO 2007000091A1
Authority
WO
WIPO (PCT)
Prior art keywords
mmsc
multimedia message
message
multimedia
field
Prior art date
Application number
PCT/CN2006/001087
Other languages
English (en)
French (fr)
Inventor
Kehua Chen
Guangchang Bai
Dawei Li
Weiming Cheng
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 CN2006800117150A priority Critical patent/CN101156384B/zh
Priority to EP06741975A priority patent/EP1804432A4/en
Publication of WO2007000091A1 publication Critical patent/WO2007000091A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/10Multimedia information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/20Hop count for routing purposes, e.g. TTL
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21Monitoring or handling of messages
    • H04L51/214Monitoring or handling of messages using selective forwarding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58Message adaptation for wireless communication

Definitions

  • the present invention relates to a message transmission processing technology of a Multimedia Messaging Service (MMS) system, and in particular, to a method and system for limiting the number of times a multimedia message center (MMSC) forwards a multimedia message.
  • MMS Multimedia Messaging Service
  • Multimedia Messaging Service is a further development of Short Message Service (SMS) and Enhanced Messaging (EMS), providing a complete end-to-end solution for personal multimedia mobile communication services.
  • multimedia messages include images, audio, video, and data.
  • multimedia messaging services cover various forms of multimedia messaging from terminal to terminal, terminal to application server, and application server to terminal. . It not only realizes the transfer of information between terminals, terminals and application servers, but also realizes the diversity of content, including various combinations of pictures, voice, images, data and text.
  • the MMS system can generate more colorful content service applications under the interaction of mobile users and Internet content providers. The user is both a consumer of MS and a developer of MMS content, which will undoubtedly increase the interest of the end user in the use of the business.
  • FIG. 1 is an architectural diagram of an existing MMS system.
  • the MMS system can contain many different network types, such as 2G mobile networks, 3G mobile networks, Internet/IP networks, etc.
  • the connections between these different networks are determined by the Internet Protocol and its associated messaging protocols. Set provided.
  • the transmission scheme of multimedia messages in the 2G mobile network and the 3G mobile network can be compatible with the existing multimedia message transmission scheme on the Internet.
  • the main NEs included in the MMS system are described below:
  • the MMS User Agent is installed on the MMS User Terminal to provide multimedia messaging services through the user terminal.
  • the MMS User Agent is an application on the user terminal that provides functions such as browsing, editing, and processing multimedia messages, as well as operations such as sending, receiving, and deleting multimedia messages.
  • the MMS User Agent supports the Multipurpose Sinteraet Mail Extensions (MIME) protocol. Multimedia messages are represented in MIME format. By defining different subtypes in the MME, multimedia messages can contain text, images, sounds, and the like.
  • MIME Multipurpose Sinteraet Mail Extensions
  • a Wired email client that enables multimedia messaging systems to interact with email, such as endpoint-to-email and email-to-terminal processes.
  • MMSE multimedia message service environment
  • MMS repeater/server used for protocol conversion, content adaptation, storage and scheduling of multimedia messages, completes the transfer operation of multimedia messages between different multimedia devices, and also generates billing bills The function.
  • MMS User Databases are used to store user information, personalized information, interface information, and so on. For example: Capability information of the mobile terminal Profiles, user subscription information subscription, user location information HLR.
  • a message store for storing multimedia messages of users. Since the general multimedia message body is relatively large, 'the user terminal has limited storage capacity, and the user can store the message in a special information storage, such as China Mobile's Monternet photo album.
  • MMS repeater/server MMS user database
  • information storage form the MMS system and core: Multimedia Service Center (MMSC).
  • MMSC Multimedia Service Center
  • VAS Applicatons The MMS External Value-Added Application Server (VAS Applicatons), generally abbreviated as SP/CP, is a value-added service provider (VASP) that provides MMS value-added service services.
  • VASP value-added service provider
  • External Server External Server
  • other services related to multimedia messaging services Servers such as prepaid platforms, data service management platforms, etc.
  • FIG. 2 is a schematic diagram of networking communication of each network element of the MMS system in the case of multiple MMSC interconnections. As shown in FIG.
  • the MMSC interacts with the user terminal through the WAP gateway, and the interaction protocol is the MM1 protocol; the MMSC interacts with the mail (email) server in the IP network by using the MM3 protocol, and the bearer protocol is a simple mail transmission protocol (SMTP (Simple Mail Transfer Protocol) protocol; MMSC and SP/CP use MM7 protocol to exchange, the bearer protocol is generally Hypertext Transfer Protocol (HTTP) protocol, and can also be carried by other protocols; MMSC and MMSC The MM4 protocol is used for interaction, and the bearer protocol is SMTP.
  • SMTP Simple Mail Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a server for performing domain name resolution on the E.164 address is further used, and the Enum Server is configured to provide the MMSC with a function of performing route query according to the receiver terminal number to confirm whether the multimedia message is Need to forward and to which MMSC to forward.
  • FIG. 3 is a flow chart of multimedia messages interacting using the existing MM4 interface protocol.
  • the sender MMSC determines the forwarding route through the Enum Server, and passes the multimedia message and its related attribute information through the multimedia message forwarding request (MM4_forward.REQ).
  • MM4_forward.REQ multimedia message forwarding request
  • Message forwarding where forwarding refers to forwarding, after being forwarded by several MMSCs, and transmitted to the receiver MMSC, the receiver MMSC sends the multimedia message to the receiver user terminal, and returns the multimedia message to the sender MMSC.
  • MM4_forward.RES multimedia message delivery report
  • the receiver MMSC After receiving the multimedia confirmation request (MMl_acknowledgementREQ) message of the receiver user terminal, the receiver MMSC sends a multimedia message delivery report (MM4_delivery-report.REQ) message to the sender MMSC. After the sender's MMSC receives, it returns a multimedia message and sends a report response.
  • MM4_delivery_report.RES when the receiver MMSC receives the multimedia message receiver read response (MM1_read_reply_recipient.REQ) message of the receiver user terminal, sends a multimedia message read response report to the sender MMSC
  • the sender MMSC receives the return message of the multimedia message read response (MM4_read_reply_report_report) message, and returns the message to the sender user terminal to return the multimedia message sender.
  • the MM4 message needs to be forwarded.
  • the main object of the present invention is to provide a method for limiting the number of times a multimedia message center MMSC forwards a multimedia message, thereby limiting the number of times that a multi-message message is forwarded between MMSCs, and avoiding waste of resources of the MMS system.
  • Another object of the present invention is to provide a system for limiting the number of times a multimedia message is forwarded by an MMSC, and to limit the number of times a multimedia message is forwarded between MMSCs, thereby avoiding waste of resources of the MMS system.
  • the main technical solutions of the present invention include:
  • a method for limiting the number of times a multimedia message center MMSC forwards a multimedia message the method adding a counting field for calculating a forwarding number in the multimedia message, the multimedia
  • the V1MSC updates the value in the field for marking the number of forwardings.
  • the current MMSC refuses to continue processing the multimedia message.
  • the method specifically includes:
  • next-level MMSC When the sender MMSC forwards the multimedia message to the next-level MMSC, a counting field for calculating the number of forwarding times is added to the forwarded multimedia message, and the counting field is assigned and then forwarded; the next-level MMSC is used as the current MMSC. ;
  • the current MMSC parses the counting field in the multimedia message, determines the number of times the multimedia message is forwarded according to the value of the counting field, and determines whether the forwarding number exceeds a preset maximum number of forwarding times; if yes, rejects the multimedia message. Processing, ending the process; Nobe ij, the current MMSC forwards the multimedia message to the next-level MMSC, first changes the value of the counting field in the multimedia message according to a predetermined rule, and then forwards the multimedia message, and then the next The primary MMSC acts as the current MMSC, and step B is re-executed.
  • step B before the current MMSC parses the counting field in the multimedia message, the method further includes:
  • the multimedia message carries a counting field, if yes, parsing the counting field of the multimedia message, and continuing to perform the subsequent process; otherwise, when the current MMSC forwards the multimedia message to the next-level MMSC, the forwarded multimedia Add a counting field to the message and forward it to the counting field, and forward the next-level MMSC as the current MMSC.
  • the method further comprises: the sender MMSC assigning a value of 1 to the counting field in the forwarded multimedia message;
  • step B before the current MMSC parses the counting field in the multimedia message and determines the forwarding number of the multimedia message according to the value of the counting field, the method further includes: determining whether the value of the counting field is less than or equal to 0, if , the assignment field is assigned a value of 1, Continue the follow-up process; otherwise, execute the subsequent process directly.
  • the method further includes:
  • the sender MMSC determines whether the receiver user terminal that receives the multimedia message belongs to the local MMSC, and if yes, sends the multimedia message to the receiver user terminal, and ends the process; if not, executes the forwarded multimedia message. Add a count field for calculating the number of forwards and subsequent steps.
  • step B before the current MMSC parses the counting field of the multimedia message, the method further includes:
  • the MMSC determines whether the receiving user terminal that receives the multimedia message belongs to the MMSC, and if yes, sends the multimedia message to the receiving user terminal, and ends the process; if not, executes in the forwarded multimedia message. Add a count field for calculating the number of forwards and the next steps.
  • the current MMSC determines that the number of forwarding times does not exceed the preset maximum number of forwardings, and before the current MMSC forwards the multimedia message to the next-stage MMSC, the method further includes: the current MMSC determining to receive the multimedia message. Whether the user terminal belongs to the MMSC, if yes, the multimedia message is sent to the recipient user terminal, and the process ends; if not, the current MMSC continues to change the value of the counting field in the multimedia message according to a predetermined rule and Next steps.
  • the method for changing the value of the counting field in the multimedia message according to a predetermined rule is: incrementing the value of the counting field.
  • the manner of changing the value of the counting field in the multimedia message according to a predetermined rule is: decrementing the value of the counting field.
  • the multimedia message forwarded by the MMSC is an MM4 interface protocol message.
  • the MM4 interface protocol message is a multimedia forwarding request message, where T N2006/001087
  • the counting field added in the media forwarding request message is the forwarding number field.
  • a processing system for limiting the number of times a MMSC forwards a multimedia message comprising: an adding unit for adding a counting field and assigning a value to a multimedia message; for updating the meter every time the multimedia message is forwarded through an MMSC An update unit of the number of forwardings in the secondary field; configured to calculate the number of forwardings, and when the number of forwardings exceeds a predetermined value, triggering a determination unit that the current MMSC refuses to continue processing the multimedia message.
  • the system further includes a determining unit for determining whether the multimedia message carries a counting field, and the determining unit triggers the updating unit to update the counting time when determining that the multimedia field carries the counting field.
  • the number of forwardings in the field triggers the adding unit to add a counting field in the multimedia message when it is determined that the counting field is not carried.
  • the initial value of the multimedia message count field is 1; the determining unit is further configured to trigger the adding unit to assign the counting field to 1 when the value of the counting field is less than or equal to 0.
  • the multimedia message forwarded by the MMSC is an MM4 interface protocol message.
  • the MM4 interface protocol message is a multimedia forwarding request message, and the counting field added in the multimedia forwarding request message is a forwarding number field.
  • the method of the present invention adds a counting field for calculating the number of forwarding times in the MM4 message when the MMSC forwards the MM4 message, and the value of the field is updated every time the MM4 message is forwarded by one MMSC, and is used for marking the number of forwarding times.
  • the present invention can limit the number of times the multimedia message is forwarded between the MMSCs, and prevent the MM4 messages from being forwarded infinitely between the MMSCs. Thereby avoiding waste of resources of the MMS system.
  • the administrator of the MMS system can also determine, according to the result of which MMSC refuses to forward the MM4 message, that a routing configuration error may occur on the MMSC and its neighboring MMSC, so the use of the present invention can also facilitate the exclusion of the system. Routing failure.
  • Figure 1 is an architectural diagram of an existing MMS system
  • FIG. 2 is a schematic diagram of networking of an MMS system in the case of multiple MMSC interconnections
  • FIG. 3 is a flow chart of multimedia messages interacting using an existing MM4 interface protocol
  • FIG. 4 is a flow chart of a sender MMSC processing and transmitting a multicast message
  • FIG. 5 is a relay or receiver MMSC processing and transmitting A flow chart of multimedia messages. Mode for carrying out the invention
  • the core technical solution of the present invention is: adding a counting field for calculating the number of forwardings in the multimedia message, and each time the multimedia message is forwarded by an MMSC, the MMSC updates the value in the field for marking the number of forwarding times, when the number of forwardings When the predetermined value is exceeded, the MMSC refuses to continue processing the multimedia message.
  • the multimedia message is forwarded to the receiver MMSC of the multimedia message by the relay MMSC as an example to explain the present invention.
  • the MMSC After receiving the multimedia message, the MMSC first determines the source of the multimedia message. If the multimedia message is the MM1 message sent by the user terminal, the MMSC is the sender MMSC of the multimedia message, and therefore the process of processing and transmitting the multimedia message by the sender MMSC is performed; If the multimedia message is an MM4 message forwarded by another MMSC, the MMSC is a relay or receiver MMSC of the multimedia message, thus performing a process of processing or transmitting the multimedia message by the relay or receiver MMSC.
  • the MM1 message is an MM1 message sent by the user terminal to the MMSC, for example: a multimedia message submission request (MM1_submit.REQ) message, a multimedia message notification response (MM1 notification.RES) message, a multimedia message reacquisition request (MMl_retrieve.REQ) message, multimedia confirmation request (MMl_acknowledgement.REQ) message, and multimedia message receiver read response (MMl_read-reply-recipient.REQ) message.
  • MM1_submit.REQ multimedia message submission request
  • MM1 notification.RES multimedia message notification response
  • MMl_retrieve.REQ multimedia message reacquisition request
  • MMl_acknowledgement.REQ multimedia confirmation request
  • MMl_read-reply-recipient.REQ multimedia message receiver read response
  • the MM4 message is all messages transmitted between the MMSCs, for example: a multimedia message forwarding request (MM4_forward.REQ) message, a multimedia message forwarding response (MM4_forward.RES) message, and a multimedia message delivery report (MM4- Delivery_reportREQ) message, multimedia message delivery report response (MM4_delivery_report.RES) message, multimedia message read response report (MM4_read_reply_report.REQ) message, and multimedia message read response (MM4_read_reply_repor RES) message .
  • MM4- Delivery_reportREQ multimedia message delivery report
  • MM4_delivery_report.RES multimedia message read response report
  • MM4_read_reply_repor RES multimedia message read response
  • the MMSC receives the MM1 a submit.RE ( ⁇ message and sends it to other MMSCs.
  • the MM4_forward.REQ message is described as an example.
  • Figure 4 is a flow chart of processing and transmitting a multimedia message by the sender MMSC. As shown in Figure 4, the process includes:
  • Step 401 The sender MMSC receives the MM1 message from the sender user terminal of the multimedia message.
  • the multimedia message submission request (MM1_submit.REQ) carries the content of the multimedia message and the identifier of the receiver user terminal.
  • Step 402 to step 403 The Enum Server of the sending MMSC performs a route query according to the received terminal identifier carried in the received MM1 message, and determines, according to the routing query result, whether the receiving user terminal belongs to the MMSC, and if so, directly The corresponding MM1 message is sent to the receiver user terminal, and the process ends.
  • the MM1 message sent by the MMSC is a multimedia notification request (MMl_notification.REQ), to notify the receiving user terminal to obtain the multimedia message on the MMSC; if the MMSC receives The MM1 message is MMl_acknowledgement.REQ, and the MM1 message sent by the local SC to the sender user terminal is a multimedia message delivery report (MMl_delivery_reportREQ);
  • the MM1 message received by the MMSC is MMl_read_reply_recipienLREQ, and the MM1 message sent by the MMSC to the sender user terminal is a multimedia message sender read response message (MM1_read_reply_originator.REQ).
  • the content of the MM1 message needs to be forwarded to the receiver MMSC of the MM1 message by using the MM4 message, so step 404 is performed.
  • the content of the MM1_submitREQ is forwarded through a multimedia forwarding request (MM4_forward.REQ) message.
  • Step 404 The sender MMSC adds a counting field to the MM4 message to be sent, where is the number of forwarding times (MM4_forward_counter) field, and assigns the number of forwarding times, for example, the value is 1 in this embodiment. This assignment is used to mark the number of times the MMSC forwards the multimedia message.
  • MM4_forward_counter the number of forwarding times
  • Step 405 According to the route queried in step 402, the MM4 message with the number of forwarding times added is forwarded to the next-level MMSC through the MM4 interface.
  • Figure 5 is a flow diagram of processing and transmitting a multimedia message by a relay or receiver MMSC. As shown in Figure 5, the process includes:
  • Step 501 The MMSC receives the MM4 message sent by another MMSC.
  • the MM4 message in this embodiment is an MM4_forward.REQ message.
  • Step 502 The MMSC parses the MM4 message, and obtains a value of the forwarding number field. If the MM4 message is from the MMSC that does not support the function of adding the forwarding number field, there is no forwarding number field in the MM4. In this case, the MM4 message needs to be determined whether the forwarding is carried in the MM4 message. The number field, if yes, parses, if not, the MMSC adds a forwarding number field to the MM4 message and assigns the value of the field to 1.
  • the value of the forwarding number field does not appear to be less than 0.
  • the present invention may also be in step 503 ⁇ Before step 504, the method further includes: determining the forward number If the value of the segment is less than or equal to 0, then the value of the field is set to 1, and then steps 503 to 504 are performed. Otherwise, steps 503 to 504 are directly performed.
  • Step 503 The MMSC determines whether the value of the forwarding number field exceeds a preset maximum number of forwarding times. If yes, the service is refused to continue for the MM4 message; otherwise, step 505 is performed.
  • Step 505 - Step 506 The Enum Server of the MMSC performs a route query according to the identifier of the receiver user terminal carried in the received MM4 message, and determines, according to the result of the route query, whether the user terminal of the receiver belongs to the MMSC, and if yes, The MM4 message is forwarded, and the corresponding MM1 message is directly sent to the receiver user terminal.
  • the MM4 message is MM4_forwardJREQ
  • the corresponding MM1 message is a multimedia notification request (MM1_contact.REQ), to notify the receiving user terminal to obtain the multimedia message on the MMSC, and the process ends.
  • step 507 is performed.
  • step 507 the value of the MM4_forward-counter field in the MM4_forward.REQ message is one.
  • the value in the MM4_forward_counter field is changed in an incremental manner to mark the number of times the MMSC forwards the multimedia message.
  • the present invention can also mark the number of forwardings in a decreasing manner.
  • the value assigned by the sender MMSC in the MM4_forward_counter field is the maximum number of forwarding times, and the value in the field is forwarded after each MMSC forwarding. Decrement by one, until the value of this field is zero, it means that the maximum number of forwardings has been reached, and the current MMSC refuses to serve the message.
  • the value of the MM4_forward_counter field may also be changed by using other counting rules, as long as the MMSC can determine the number of times the MMSC forwards the multi-message message according to the value.
  • Step 508 Forward the processed MM4_forward.REQ message to the next-level MMSC through the MM4 interface according to the route queried in step 505.
  • step 505 may be performed after step 501. If the receiving user terminal belongs to the MMSC, step 506 is performed. If the receiving user terminal does not belong to the MMSC, step 502 and subsequent processes are performed, and When step 503 is performed, if the value of the MM4_forward_count does not exceed the preset maximum number of forwardings, step 507 and subsequent steps are performed.
  • the object of the invention can be achieved as well.
  • the present invention also discloses a processing system for limiting the number of times a MMSC forwards a multimedia message, the system comprising: an adding unit for adding a counting field and assigning a value in a multimedia message; An update unit that updates the number of times of forwarding in the counting field every time the multimedia message is forwarded by an MMSC; used to calculate the number of forwarding times, and triggers the MMSC to refuse to continue processing the multimedia message when the number of forwarding exceeds a predetermined value .
  • the system may further include a determining unit configured to determine whether the multimedia message carries a counting field, and the determining unit triggers the updating unit to update the counting when determining that the multimedia field carries the counting field.
  • the number of forwardings in the field triggers the adding unit to add a counting field in the multimedia message when it is determined that the counting field is not carried.
  • the adding unit may set an initial assignment in the multimedia message counting field to 1; the determining unit is further configured to: use a value less than or When it is equal to 0, the trigger adding unit assigns the counting field to 1.
  • the multimedia message forwarded by the MMSC is an MM4 interface protocol message, and the MM4 interface protocol message is a multimedia forwarding request message, and the counting field added in the multimedia forwarding request message is a forwarding number field.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

限制多媒体消息中心对多媒体消息转发次数的方法和系统 技术领域
本发明涉及多媒体消息业务( MMS , Multimedia Messaging Service ) 系统的消息传输处理技术,尤其涉及一种限制多媒体消息中心( MMSC ) 对多媒体消息的转发次数的方法和系统。 发明背景
多媒体消息服务 ( MMS )是短信息服务( SMS )和增强型消息月良务 ( EMS )的进一步发展, 为个人多媒体移动通信服务提供了完整的端到 端解决方案。 从通信内容上讲, 多媒体消息包括图像、 音频、 视频和数 据等; 从功能上讲, 多媒体消息服务涵盖了终端到终端、 终端到应用月 务器、 应用服务器到终端多种形式的多媒体消息通信。 它不仅实现了终 端之间、 终端和应用服务器之间的信息传递, 还实现了内容的多样性, 包括图片、 语音、 图像、 数据和文本的各种组合。 作为一个开放的媒体 接入平台, MMS 系统可以在移动用户和互联网内容提供商的互动下, 衍生出更丰富多彩的内容服务应用。 而用户既是 MS的消费者, 又是 MMS内容的开发者, 这无疑会提高终端用户对业务的使用兴趣。
图 1为现有 MMS系统的体系结构图。如图 1所示, MMS系统可以 包含许多不同的网络类型, 例如 2G移动网络、 3G移动网络、 因特/ IP 网等, 这些不同网络之间的连接^出由因特网协议及其相关的消息协议 集提供。 并且, 2G移动网络和 3G移动网络中的多媒体消息的传输方 案可与因特网上现存的多媒体消息传输方案兼容。 如图 1 所示, MMS 系统包括的主要网元见以下说明:
在终端侧, 主要包括: MMS 用户代理 (User Agent ), 安装在 MMS 用户终端 ( MMS Terminal )上, 通过用户终端提供多媒体消息服务。 MMS用户代理是在 用户终端上的一个应用,提供用户浏覓、编辑、处理多媒体消息等功能, 以及对多媒体消息的发送、 接收和删除等操作。 MMS 用户代理支持多 用途的网际邮件扩充( MIME, Multipurpose SInteraet Mail Extensions ) 协议,多媒体消息采用 MIME格式表示,通过对 MME中不同子类型的 定义, 多媒体消息可包含文本、 图像、 声音等数据。
无线 Email客户端 ( Wired email client ), 用于使多媒体消息系统与 Email进行交互, 比如终端到 Email和 Email到终端流程。
在网络侧, 主要包括多媒体消息业务环境(MMSE ), MMSE是实 现 MMS业务的一套独立的和完整的网络元素的集合, 具体包括:
MMS 中继器 /服务器( Relay/Server ), 用于对多媒体消息进行协议 转换、 内容适配、 存储以及调度, 完成多媒体消息在不同多媒体设备之 间的传递操作, 同时还具有生成计费话单的功能。
MMS用户数据库(User Databases ), 用于存储用户信息、 个性化信 息、 接口信息等。 例如: 手机终端的能力信息 Profiles, 用户订阅信息 subscription, 用户所在位置信息 HLR。
信息存储器(Message Store ), 用于存储用户的多媒体消息。 由于一 般多媒体消息体都比较大, '用户终端存储能力有限, 用户可以将消息存 储在专门的信息存储器上, 比如中国移动的梦网相册。
上述 MMS中继器 /服务器、 MMS用户数据库和信息存储器组成了 MMS系统和核心: 多媒体业务中心(MMSC )。
MMS外部增值应用服务器(VAS Applicatons ),—般缩写为 SP/CP, 属于增值业务提供商 (VASP ), 用于提供 MMS的增值业务服务。
外部服务器(External Server ), 是与多媒体消息业务相关的其他服 务器, 比如预付费平台、 数据业务管理平台等。
在运营商实际开展业务时, 经常需要用多个 MMSC分别向用户提 供 MMS业务,各个 MMSC分别管理部分用户,提供相应用户的接入功 能。图 2为多个 MMSC互连情况下 MMS系统各网元的组网通信示意图。 如图 2所示, MMSC与用户终端之间通过 WAP网关交互, 交互协议为 MM1协议; MMSC与 IP网中的邮件( Email )服务器之间采用 MM3协 议交互, 其承载协议为简单邮件传输协议(SMTP, Simple Mail Transfer Protocol )协议; MMSC与 SP/CP之间采用 MM7协议交互, 其承载协 议一般为超文本传输协议 ( HTTP, Hypertext Transfer Protocol )协议, 也可使用其它协议承载; MMSC与 MMSC之间则采用 MM4协议交互, 其承载协议为 SMTP协议。 在发送多媒体消息的过程中, 还需利用对 E.164地址进行域名解析的服务器(Enum Server ), 该 Enum Server用于 向 MMSC提供根据接收方终端号码进行路由查询的功能, 以确认多媒 体消息是否需要转发及向哪个 MMSC转发。
多个 MMSC之间消息交互是通过 MM4接口完成,图 3是多媒体消 息在利用现有的 MM4接口协议进行交互的一种流程图。 如图 3所示, 发送方 MMSC 收到发送方用户终端提交的多媒体消息后, 通过 Enum Server确定转发路由, 并将多媒体消息及其相关属性信息通过多媒体消 息前转请求(MM4—forward.REQ ) 消息转发, 此处的前转就是指转发, 经过若干个 MMSC转发后, 传送给接收方 MMSC, 由接收方 MMSC将 多媒体消息下发给接收方用户终端, 并向发送方 MMSC返回多媒体消 息前转响应 (MM4—forward.RES ) 消息; 当接收方 MMSC收到接收方 用户终端的多媒体确认请求( MMl_acknowledgementREQ )消息后, 向 发送方 MMSC发送多媒体消息下发报告(MM4— delivery一 report.REQ ) 消息、 发送方 'MMSC 收到后, 返回多媒体消息下发报告响应 ( MM4_delivery_report.RES ) 消息; 当接收方 MMSC收到接收方用户 终端的多媒体消息接收方阅读应答(MM1一 read_reply_recipient.REQ )消 息后, 向发送方 MMSC 发送多媒体消 息阅读应答报告
( MM4_read_reply_report.REQ ) 消息, 发送方 MMSC收到后返回多媒 体消息阅读应答 4艮告响应 (MM4_read— reply— reportRES ) 消息, 并给发 送 方 用 户 终 端 返 回 多 媒 体 消 息 发 送 方 阅 读 应 答
( MM1— read— reply— originator.REQ ) 消息。
上述流程中, 如果发送方 MMSC 和接收方 MMSC 不是同一个 MMSC, 则都需要对 MM4消息进行转发。
但是,上述现有的技术方案中,无法对多媒体消息在多个 MMSC间 转发的次数进行限制, 如果互连的 MMSC 使用静态路由, 其中一个 MMSC对某条路由配直错误,可能会导致多媒体消息一直在两个 MMSC 之间无限制循环转发的问题, 因此会过多地占用 MMS系统的资源, 造 成资源浪费。 发明内容
本发明的主要目的是提供一种限制多媒体消息中心 MMSC对多媒 体消息转发次数的方法, 实现对多某体消息在 MMSC 间转发的次数进 行限制, 避免对 MMS系统资源的浪费。
本发明的另一目的是提供一种限制 MMSC对多媒体消息转发次数 的系统, 实现对多媒体消息在 MMSC 间转发的次数进行限制, 避免对 MMS系统资源的浪费。
为了实现上述发明目的, 本发明的主要技术方案包括:
一种限制多媒体消息中心 MMSC对多媒体消息的转发次数的处理 方法, 该方法在多媒体消息中添加用于计算转发次数的计次字段, 多媒 体消息每经过一 MMSC转发, 该] V1MSC便更新该字段中的值, 用于标 记转发次数, 当转发次数超过预定值时, 当前的 MMSC拒绝继续处理 该多媒体消息。
优选地, 该方法具体包括:
A、 发送方 MMSC向下一级 MMSC转发多媒体消息时, 在所转发 的多媒体消息中添加用于计算转发次数的计次字段, 对计次字段赋值后 转发; 将该下一级 MMSC作为当前 MMSC;
B、 当前 MMSC解析所述多媒体消息中的计次字段, 根据计次字段 的值确定该多媒体消息的转发次数, 判断转发次数是否超过预设的最大 转发次数; 如果是, 则拒绝对该多媒体消息进行处理, 结束流程; 否贝 ij, 当前 MMSC在向下一级 MMSC转发该多媒体消息时 , 先依据预定的规 律改变该多媒体消息中计次字段的值, 再转发该多媒体消息, 并将该下 一级 MMSC作为当前 MMSC, 重新执行步驟 B。
优选地, 步骤 B中, 所述当前 MMSC解析所述多媒体消息中的 计次字段之前, 进一步包括:
判断该多媒体消息中是否携带计次字段, 如果有, 则解析该多媒体 消息的计次字段, 并继续执行后续流程; 否则, 当前 MMSC 向下一级 MMSC转发该多媒体消息时,在所转发的多媒体消息中添加计次字段并 对计次字段赋值后转发, 并将该下一级 MMSC作为当前 MMSC, 重新 执行步骤^
优选地,该方法进一步包括,所述发送方 MMSC对所转发的多媒体 消息中计次字段的赋值为 1;
步骤 B中, 当前 MMSC在解析所述多媒体消息中计次字段并根据 计次字段的值确定该多媒体消息的转发次数之前, 进一步包括: 判断该 计次字段的值是否小于或等于 0, 如果是, 则将该计次字段赋值为 1 , 再继续执行后续流程; 否则, 直接执行后续流程。
优选地, 在发送方 MMSC向下一级 MMSC转发多媒体消息之前, 进一步包括:
发送方 MMSC判断接收所述多媒体消息的接收方用户终端是否归 属于本 MMSC, 如果是, 则向该接收方用户终端下发该多媒体消息, 结 束流程; 如果不是, 则执行在所转发的多媒体消息中添加用于计算转发 次数的计次字段及后续步驟。
优选地, 步骤 B中, 在当前 MMSC解析所述多媒体消息的计次字 段之前, 进一步包括:
当前 MMSC判断接收所述多媒体消息的接收方用户终端是否归属 于本 MMSC, 如果是, 则向该接收方用户终端下发该多媒体消息, 结束 流程; 如果不是, 则执行在所转发的多媒体消息中添加用于计算转发次 数的计次字段及后续步骤。
优选地,当前 MMSC判断所迷转发次数没有超过预设的最大转发次 数时, 则在当前 MMSC向下一级 MMSC转发所述多媒体消息之前, 进 一步包括: 当前 MMSC判断接收所述多媒体消息的接收方用户终端是 否归属于本 MMSC,如果是,则向该接收方用户终端下发该多媒体消息, 结束流程; 如果不是, 则继续执行当前 MMSC依据预定的规律改变该 多媒体消息中计次字段的值及后续步骤。
优选地, 所述依据预定的规律改变多媒体消息中计次字段取值的方 式为: 递增该计次字段的取值。
优选地, 所述依据预定的规律改变多媒体消息中计次字段取值的方 式为: 递减该计次字段的取值。
优选地, 所述 MMSC转发的多媒体消息为 MM4接口协议消息。 优选地, 所述 MM4接口协议消息为多媒体前转请求消息, 在该多 T N2006/001087 媒体前转请求消息中添加的计次字段为前转次数字段。
一种限制 MMSC对多媒体消息的转发次数的处理系统, 该系统包 括: 用于在多媒体消息中添加计次字段并赋值的添加单元; 用于在多媒 体消息每经过一 MMSC转发, 则更新所述计次字段中的转发次数的更 新单元; 用于计算所述转发次数, 当转发次数超过预定值则触发当前的 MMSC拒绝继续处理所述多媒体消息的判断单元。
优选的, 该系统进一步包括用于判断所述多媒体消息中是否携带计 次字段的判断单元, 该判断单元在判定所述多媒体消息中携带所述计次 字段时触发所述更新单元更新该计次字段中的转发次数, 在判定未携带 所述计次字段时触发所述添加单元在所述多媒体消息中添加计次字段。
优选的, 所述多媒体消息计次字段中的最初赋值为 1; 所述判断单 元进一步用于在所述计次字段的取值小于或等于 0时触发添加单元将该 计次字段赋值为 1。
优选的, 所述 MMSC转发的多媒体消息为 MM4接口协议消息。 优选的 , 所述 MM4接口协议消息为多媒体前转请求消息, 在该多 媒体前转请求消息中添加的计次字段为前转次数字段。
由于本发明所述的方法在 MMSC转发 MM4消息时, 在 MM4消息 中添加用于计算转发次数的计次字段, MM4消息每经过一个 MMSC转 发, 便更新该字段中的值, 用于标记转发次数, 当转发次数超过预定的 最大转发次数时, 则拒绝继续转发该 MM4消息, 因此本发明可以实现 对多媒体消息在 MMSC 间转发的次数进行限制, 避免 MM4 消息在 MMSC之间被无限次地转发,从而避免对 MMS系统资源的浪费。另夕卜, MMS系统的管理人员还可以根据由哪个 MMSC拒绝转发 MM4消息的 结果,判断出路由配置错误可能出现在该 MMSC及其相邻的 MMSC上, 因此利用本发明还可有利于排除系统路由故障。 附图简要说明
图 1为现有 MMS系统的体系结构图;
图 2为多个 MMSC互连情况下的 MMS系统组网示意图;
图 3为多媒体消息在利用现有的 MM4接口协议进行交互的流程图; 图 4为发送方 MMSC处理和发送多某体消息的一种流程图; 图 5为中继或接收方 MMSC处理和发送多媒体消息的一种流程图。 实施本发明的方式
下面结合附图以具体实施例对本发明进行说明。
本发明的核心技术方案为: 在多媒体消息中添加用于计算转发次数 的计次字段, 多媒体消息每经过一 MMSC转发, 该 MMSC便更新该字段 中的值, 用于标记转发次数, 当转发次数超过预定值时, 则 MMSC拒绝 继续处理该多媒体消息。
在以下实施例中, 以 MMSC收到来自用户终端的多媒体消息后, 通 过中继 MMSC将该多媒体消息转发给该多媒体消息的接收方 MMSC为 例对本发明进行说明。
MMSC收到多媒体消息后, 首先判断多媒体消息的来源, 如果该多 媒体消息是用户终端发送的 MM1消息,则本 MMSC为多媒体消息的发送 方 MMSC, 因此执行发送方 MMSC处理和发送多媒体消息的流程; 如果 该多媒体消息是其他 MMSC转发过来的 MM4消息,则本 MMSC为多媒体 消息的中继或接收方 MMSC, 因此执行中继或接收方 MMSC处理和发送 多媒体消息的流程。
所述的 MM1消息为用户终端向 MMSC发送的 MM1消息, 例如: 多 媒体消息提交请求 ( MMl_submit.REQ ) 消息、 多媒体消息通知响应 ( MM1 notification.RES ) 消 息 、 多 媒体消 息重获取请求 ( MMl_retrieve.REQ ) 消 息 、 多 媒 体 确 认 倩 求 ( MMl_acknowledgement.REQ ) 消息以及多媒体消息接收方阅读应答 ( MMl_read— reply— recipient.REQ ) 消息。 所述的 MM4消息为 MMSC之 间传送的所有消息, 例如: 多媒体消息前转请求(MM4— forward.REQ ) 消息、 多媒体消息前转响应 (MM4_forward.RES )消息、 多媒体消息下 发报告 ( MM4— delivery— reportREQ ) 消息、 多媒体消息下发报告响应 ( MM4_delivery_report.RES ) 消息、 多媒体消息阅读应答报告 ( MM4_read_reply_report.REQ )消息、 以及多媒体消息阅读应 艮告响 应 ( MM4— read— reply— repor RES ) 消息。
下面以 MMSC接收 MMl一 submit.RE (^消息, 并向其他 MMSC发送
MM4—forward.REQ消息为例进行说明。
图 4为发送方 MMSC的处理和发送多媒体消息的一种流程图。 如图 4 所示, 该流程包括:
步骤 401、 发送方 MMSC接收到来自多媒体消息的发送方用户终端 的 MM1消息, 本实施例为多媒体消息提交请求(MMl— submit.REQ ) , 其中携带多媒体消息的内容和接收方用户终端的标识。
步骤 402〜步骤 403、 发送方 MMSC的 Enum Server根据接收到的 MM1消息中携带的接收方终端标识进行路由查询,根据路由查询结果判 断该接收方用户终端是否归属于本 MMSC, 如果是, 则直接向接收方用 户终端发送对应的 MM1消息, 结束流程。 本实施例中, 由于 MMSC接收 的是 MMl— submit.REQ, 因此 MMSC发送的 MM1消息为多媒体通知请求 ( MMl_notification.REQ ) , 以通知接收方用户终端到本 MMSC上获取 多 媒 体 消 息 ; 如 果 本 MMSC 接 收 的 MM1 消 息 为 MMl_acknowledgement.REQ ,则本固 SC向发送方用户终端对应发送的 MM1消息为多媒体消息交付报告 ( MMl— delivery— reportREQ ) ; 如果 本 MMSC接收的 MM1消息为 MMl—read— reply— recipienLREQ , 则本 MMSC向发送方用户终端对应发送的 MM1消息为多媒体消息发送方阅 读应答消息 ( MM1— read— reply— originator .REQ ) 。
如果接收方用户终端不归属于本 MMSC, 则需要通过 MM4消息将 MM1消息的内容转发给该 MM1消息的接收方 MMSC, 因此执行步骤 404。 本实施例中通过多媒体前转请求( MM4_forward.REQ ) 消息将所 述 MM1— submitREQ的内容转发出去。
步驟 404、 发送方 MMSC将要发出的 MM4消息中添加计次字段, 此 处为前转次数(MM4— forward—counter )字段, 并对该转发次数字段进行 赋值, 例如本实施例中赋值为 1 , 该赋值用于标记 MMSC对多媒体消息 的转发次数。
步骤 405、按照步骤 402查询的路由, 通过 MM4接口将所述添加了转 发次数字段的 MM4消息向下一级 MMSC转发。
图 5为中继或接收方 MMSC的处理和发送多媒体消息的一种流程 图。 如图 5所示, 该流程包括:
步骤 501、 MMSC接收到其他 MMSC发送的 MM4消息。 例如本实施 例中的 MM4消息为 MM4—forward.REQ消息。
步骤 502、 MMSC解析该 MM4消息, 获取其中前转次数字段的取值。 如果所述 MM4消息来自于不支持添加前转次数字段功能的 MMSC, 则 MM4中没有前转次数字段, 这种情况下, 本步骤中还需先判断所述 MM4消息中是否携带所述前转次数字段, 如果是则解析, 如果不是, 则 本 MMSC在该 MM4消息中添加前转次数字段, 并将该字段的值赋为 1。
一般情况下, 所述前转次数字段的取值不会出现小于 0的情况, 但 是为了防止其他 MMSC系统将前转次数字段误填为小于或等于 0的值, 本发明还可在步骤 503 ~步骤 504之前进一步包括: 判断所述前转次数字 段取值是否小于或等于 0, 是则将该字段的值赋为 1, 再执行步骤 503 ~ 步骤 504, 否则, 直接步骤 503 ~步骤 504。
步骤 503 ~步骤 504、 MMSC判断前转次数字段值是否超过预设的最 大转发次数, 如果是, 则拒绝为该 MM4消息继续进行服务; 否则, 执行 步驟 505。
步骤 505 -步骤 506、 MMSC的 Enum Server根据所接收到的 MM4消 息中携带的接收方用户终端标识进行路由查询, 根据路由查询结果判断 该接收方用户终端是否归属于本 MMSC, 如果是, 则不再对该 MM4消息 进行转发, 直接向接收方用户终端发送对应的 MM1消息。 本实施例中, 由于 MM4消息为 MM4— forwardJREQ, 因此其对应的 MM1消息为多媒体 通知请求( MM1— notification.REQ ) , 以通知接收方用户终端到本 MMSC 上获取多媒体消息, 结束流程。
如果所述接收方 ji]户终端不归属本 MMSC, 则执行步驟 507。
步 骤 507 、 对 所 述 MM4— forward.REQ 消 息 中 的 MM4— forward— counter字段值力口一。
本实施例中, 采用递增的方式改变所述 MM4— forward_counter字段 中的取值, 用以标记 MMSC对多媒体消息的转发次数。 很显然, 本发明 也可利用递减的方式标记转发次数, 例如发送方 MMSC在 MM4— forward— counter字段中所赋的值为最大转发次数值, 每经过一个 MMSC转发, 则将该字段中的值减一, 直到该字段的值为零时, 则表示 已经到达最大转发次数,此时当前 MMSC拒绝为该消息进行服务。另夕卜, 也可利用其他计次规律改变该 MM4— forward— counter字段的取值,只要根 据其取值能确定出 MMSC对多 体消息的转发次数即可。
步骤 508、按照步骤 505所述查询的路由,通过 MM4接口将所述加一 处理后的 MM4— forward.REQ消息向下一级 MMSC转发。 上述流程中, 也可在步骤 501之后先执行步骤 505, 如果接收方用户 终端归属本 MMSC , 则执行步驟 506; 如果接收方用户终端不归属本 MMSC , 则再执行步骤 502和后续流程, 并在执行步骤 503时, 如果 MM4_forward— counter取值没有超过预设的最大转发次数, 则执行步驟 507和后续步骤。 这样, 同样可以实现本发明的目的。
与上述公开的方法相对应,本发明还公开了一种限制 MMSC对多媒 体消息的转发次数的处理系统, 该系统包括: 用于在多媒体消息中添加 计次字段并赋值的添加单元; 用于在多媒体消息每经过一 MMSC转发, 则更新所述计次字段中的转发次数的更新单元; 用于计算所述转发次 数, 当转发次数超过预定值则触发 MMSC拒绝继续处理所述多媒体消 息的判断单元。
所述系统还可进一步包括用于判断所述多媒体消息中是否携带计次 字段的判断单元, 该判断单元在判定所述多媒体消息中携带所述计次字 段时触发所述更新单元更新该计次字段中的转发次数, 在判定未携带所 述计次字段时触发所述添加单元在所述多媒体消息中添加计次字段。
在所述系统的一个具体的实施例中所述添加单元可将所述多媒体消 息计次字段中的最初赋值设为 1; 所述判断单元进一步用于在所述计次 字段的取值小于或等于 0时触发添加单元将该计次字段赋值为 1。
与上述方法相同,所述 MMSC转发的多媒体消息为 MM4接口协议 消息, 所述 MM4接口协议消息为多媒体前转请求消息, 在该多媒体前 转请求消息中添加的计次字段为前转次数字段。
以上所述仅为本发明的最佳实施方案 , 但是本发明的保护范围并不 局限于上述方案, 任何熟悉该技术的人在本发明所揭露的技术范围内, 可轻易想到的变化或替换, '都应涵盖在本发明的保护范围之内。

Claims

权利要求书
1、 一种限制多媒体消息中心 MMSC对多媒体消息的转发次数的处 理方法, 其特征在于,
在多媒体消息中添加用于计算转发次数的计次字段, 多媒体消息每 经过一 MMSC转发, 该 MMSC便更新该字段中的值, 用于标记转发次 数, 当转发次数超过预定值时, 当前的 MMSC拒绝继续处理该多媒体 消息。
2、根据权利要求 1 所述的限制 MMSC对多媒体消息的转发次数的 处理方法, 其特征在于, 该方法具体包括:
A、 发送方 MMSC向下一級 MMSC转发多媒体消息时, 在所转发 的多媒体消息中添加用于计算转发次数的计次字段, 对计次字段赋值后 转发; 将该下一级 MMSC作为当前 MMSC;
B、 当前 MMSC解析所述多媒体消息中的计次字段, 根据计次字段 的值确定该多媒体消息的转发次数, 判断转发次数是否超过预设的最大 转发次数; 如果是, 则拒绝对该多媒体消息进行处理, 结束流程; 否贝^ 当前 MMSC在向下一级 MMSC转发该多媒体消息时, 先依据预定的规 律改变该多媒体消息中计次字段的值, 再转发该多媒体消息, 并将该下 一级 MMSC作为当前 MMSC, 重新执行步骤 B。
3、 根据权利要求 2所述的限制 MMSC对多媒体消息的转发次数的 处理方法, 其特征在于, 步骤 B中, 在所述当前 MMSC解析所述多媒 体消息中的计次字段之前, 进一步包括:
判断该多媒体消息中是否携带计次字段, 如果有, 则解析该多媒体 消息的计次字段, 并继续执行后续流程; 否则, 当前 MMSC 向下一级 MMSC转发该多媒体消息时,在所转发的多媒体消息中添加计次字段并 对计次字段赋值后转发, 并将该下一级 MMSC作为当前 MMSC, 重新 执行步骤8。
4、 根据权利要求 2所述限制 MMSC对多媒体消息的转发次数的处 理方法, 其特征在于, 该方法进一步包括, 所述发送方 MMSC对所转 发的多媒体消息中计次字段的赋值为 1;
步骤 B中, 当前 MMSC在解析所述多媒体消息中计次字段并根据 计次字段的值确定该多媒体消息的转发次数之前, 进一步包括: 判断该 计次字段的值是否小于或等于 0, 如果是, 则将该计次字段赋值为 1 , 再继续执行后续流程; 否则, 直接执行后续流程。
5、 根据权利要求 2所述限制 MMSC对多媒体消息的转发次数的处 理方法, 其特征在于, 在发送方 MMSC向下一级 MMSC转发多媒体消 息之前, 进一步包括:
发送方 MMSC判断接收所述多媒体消息的接收方用户终端是否归 属于本 MMSC, 如果是, 则向该接收方用户终端下发该多媒体消息, 结 束流程; 如果不是, 则执行在所转发的多媒体消息中添加用于计算转发 次数的计次字段及后续步骤。
'
6、 根据权利要求 2所^限制 MMSC对多媒体消息的转发次数的处 理方法, 其特征在于, 步骤 B中, 在当前 MMSC解析所述多媒体消息 的计次字段之前, 进一步包括:
当前 MMSC判断接收所述多媒体消息的接收方用户终端是否归属 于本 MMSC, 如果是, 则向该接收方用户终端下发该多媒体消息, 结束 流程; 如果不是, 则执行在所转发的多媒体消息中添加用于计算转发次 数的计次字段及后续步骤。
7、 根据权利要求 2所述限制 MMSC对多媒体消息的转发次数的处 理方法, 其特征在于, 当前 MMSC判断所述转发次数没有超过预设的 最大转发次数时, 则在当前 MMSC向下一级 MMSC转发所述多媒体消 息之前, 进一步包括: 当前 MMSC判断接收所述多媒体消息的接收方 用户终端是否归属于本 MMSC, 如果是, 则向该接收方用户终端下发该 多媒体消息, 结束流程; 如果不是, 则继续执行当前 MMSC依据预定 的规律改变该多媒体消息中计次字段的值及后续步骤。
8、 根据权利要求 2所述限制 MMSC对多媒体消息的转发次数的处 理方法, 其特征在于, 所述依据预定的规律改变多媒体消息中计次字段 取值的方式为: 递增该计次字段的取值。
9、 根据权利要求 2所述限制 MMSC对多媒体消息的转发次数的处 理方法, 其特征在于, 所述依据预定的规律改变多媒体消息中计次字段 取值的方式为: 递减该计次字段的取值。
10、根据权利要求 1至 9任一项所述限制 MMSC对多媒体消息的转 发次数的处理方法,其特征在于,所述 MMSC转发的多媒体消息为 MM4 接口协议消息。
11、根据权利要求 10所述限制 MMSC对多媒体消息的转发次数的 处理方法, 其特征在于, 所述 MM4接口协议消息为多媒体前转请求消 息, 在该多媒体前转请求消息中添加的计次字段为前转次数字段。
12、一种限制 MMSC对多媒体消息的转发次数的处理系统,其特征 在于, 该系统包括: 用于在多媒体消息中添加计次字段并赋值的添加单 元; 用于在多媒体消息每经过一 MMSC转发, 则更新所述计次字段中 的转发次数的更新单元; 用于计算所述转发次数, 当转发次数超过预定 值则触发当前的 MMSC拒绝继续处理所述多媒体消息的判断单元。
13、根据权利要求 12所述的限制 MMSC对多媒体消息的转发次数 的处理系统, 其特征在于, 该系统进一步包括用于判断所述多媒体消息 中是否携带计次字段的判断单元, 该判断单元在判定所述多媒体消息中 携带所述计次字段时触发所述更新单元更新该计次字段中的转发次数, 在判定未携带所述计次字段时触发所述添加单元在所述多媒体消息中 添加计次字段。
14、 根据权利要求 12所述的限制 MMSC对多媒体消息的转发次数 的处理系统, 其特征在于, 所述多媒体消息计次字段中的最初赋值为 1; 所述判断单元进一步用于在所述计次字段的取值小于或等于 0时触发添 加单元将该计次字段赋值为 1。
15、 根据权利要求 12、 13、 或 14所述的限制 MMSC对多媒体消息 的转发次数的处理系统, 其特征在于, 所述 MMSC转发的多媒体消息 为 MM4接口协议消息0
16、 根据权利要求 15所述的限制 MMSC对多媒体消息的转发次数 的处理系统, 其特征在于, 所述] VIM4接口协议消息为多媒体前转请求 消息, 在该多媒体前转请求消息中添加的计次字段为前转次数字段。
PCT/CN2006/001087 2005-06-27 2006-05-24 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 WO2007000091A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2006800117150A CN101156384B (zh) 2005-06-27 2006-05-24 限制多媒体消息中心对多媒体消息转发次数的方法和系统
EP06741975A EP1804432A4 (en) 2005-06-27 2006-05-24 METHOD AND SYSTEM FOR LIMITING THE TIMES OF TRANSFERRING A MULTIMEDIA MESSAGE FOR THE MMSC MULTIMEDIA MESSAGING SERVICE CENTER

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510079988.6 2005-06-27
CNA2005100799886A CN1889536A (zh) 2005-06-27 2005-06-27 限制多媒体消息中心对多媒体消息的转发次数的处理方法

Publications (1)

Publication Number Publication Date
WO2007000091A1 true WO2007000091A1 (fr) 2007-01-04

Family

ID=37578795

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001087 WO2007000091A1 (fr) 2005-06-27 2006-05-24 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

Country Status (4)

Country Link
US (1) US20070088848A1 (zh)
EP (1) EP1804432A4 (zh)
CN (2) CN1889536A (zh)
WO (1) WO2007000091A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10376636B2 (en) 2014-03-28 2019-08-13 Repro-Med Systems, Inc. Compact mechanical pump

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0402774D0 (en) * 2004-02-09 2004-03-10 Nokia Corp Multimedia message transfer
CN101345740B (zh) * 2007-07-09 2011-08-24 华为技术有限公司 一种多媒体数据的数字识别注册、处理方法及系统
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
CN101340634B (zh) * 2008-08-14 2012-12-05 中兴通讯股份有限公司 一种彩信互通前转消息去重保护的实现方法
CN101346004B (zh) * 2008-08-19 2011-12-28 中兴通讯股份有限公司 在回呼过程中防止前转的方法和回呼中心
US8285837B2 (en) * 2008-09-30 2012-10-09 Microsoft Corporation Recording and/or use of generation information
CN101715174B (zh) * 2008-10-08 2012-09-19 中国移动通信集团公司 多媒体消息发送方法、业务中心、wap网关及系统
US20100274858A1 (en) * 2009-04-27 2010-10-28 Nokia Corporation Mid-service sharing
US8782144B2 (en) * 2009-07-29 2014-07-15 Cisco Technology, Inc. Controlling the distribution of messages
CN101674547B (zh) * 2009-10-21 2014-11-05 中兴通讯股份有限公司 一种彩信跟踪的方法和装置
US8687609B2 (en) * 2009-11-04 2014-04-01 Cisco Technology, Inc. Managing router advertisement messages to support roaming of wireless mobile client devices
US8832802B2 (en) 2010-02-01 2014-09-09 Protextion Technologies, Llc System for distribution permissions for network communications

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003084129A1 (fr) * 2002-03-28 2003-10-09 Huawei Technologies Co., Ltd Procede de collecte de donnees de topologie de reseau
WO2004045233A1 (fr) * 2002-11-12 2004-05-27 Huawei Technologies Co., Ltd Procede de transmission de messages multimedia entre differents centres de messagerie multimedia
WO2005013544A1 (en) * 2003-07-30 2005-02-10 Sk Telecom. Co., Ltd. Method of providing multimedia messaging service using unique message identifier

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6181703B1 (en) * 1995-09-08 2001-01-30 Sprint Communications Company L. P. System for managing telecommunications
GB9715857D0 (en) * 1997-07-29 1997-10-01 Philips Electronics Nv Wireless networked message routing
US7190956B2 (en) * 2001-05-15 2007-03-13 Motorola Inc. Instant message proxy for circuit switched mobile environment
CN1145326C (zh) * 2001-05-16 2004-04-07 华为技术有限公司 一种控制短消息转发次数的方法
CN1606887B (zh) * 2001-12-21 2010-08-25 奥林吉个人通讯服务公司 移动电信网络中的呼叫处理
US20030193967A1 (en) * 2001-12-31 2003-10-16 Gregg Fenton Method, apparatus and system for processing multimedia messages
US7366288B1 (en) * 2003-04-10 2008-04-29 At&T Corp. Method and apparatus of detection of inter-carrier looping
JP3668231B2 (ja) * 2003-05-07 2005-07-06 ボーダフォン株式会社 マルチメディア・メッセージサービス装置
US20050091367A1 (en) * 2003-10-23 2005-04-28 Nokia Corporation System and method for tracking content communicated over networks
US7603715B2 (en) * 2004-07-21 2009-10-13 Microsoft Corporation Containment of worms
US7664055B2 (en) * 2005-03-21 2010-02-16 Rf Monolithics, Inc. System and method for synchronizing components in a mesh network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003084129A1 (fr) * 2002-03-28 2003-10-09 Huawei Technologies Co., Ltd Procede de collecte de donnees de topologie de reseau
WO2004045233A1 (fr) * 2002-11-12 2004-05-27 Huawei Technologies Co., Ltd Procede de transmission de messages multimedia entre differents centres de messagerie multimedia
WO2005013544A1 (en) * 2003-07-30 2005-02-10 Sk Telecom. Co., Ltd. Method of providing multimedia messaging service using unique message identifier

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10376636B2 (en) 2014-03-28 2019-08-13 Repro-Med Systems, Inc. Compact mechanical pump

Also Published As

Publication number Publication date
EP1804432A1 (en) 2007-07-04
CN101156384A (zh) 2008-04-02
US20070088848A1 (en) 2007-04-19
EP1804432A4 (en) 2010-01-27
CN1889536A (zh) 2007-01-03
CN101156384B (zh) 2010-08-25

Similar Documents

Publication Publication Date Title
WO2007000091A1 (fr) 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
US7546117B2 (en) Method and apparatus for blocking ID information associated with a sender of a short messaging service (SMS) message
US8005493B2 (en) Messaging system and method
EP1704683B1 (en) Apparatus and method for routing multimedia messages between a user agent and multiple multimedia message service centers
JP2006178999A (ja) スパム対策ブラック・リストの格納
EP2353274B1 (en) Mobile station and application server for providing a service to the mobile station and operation methods for the same
JP2006178996A (ja) スパム防止サーバ
US8341396B1 (en) Dynamic selection and insertion of signature blocks during message transmission
US20080242327A1 (en) System and method for sending sms and text messages
JP4368885B2 (ja) ショートメッセージ再送システム、ショートメッセージ再送方法
US20170142215A1 (en) Relaying mobile communications
CN100455049C (zh) 一种多媒体消息服务系统中对消息的处理方法
WO2003045041A1 (en) Selectively recalling sent messages
EP2371098B1 (en) Subscriber provisioning method and system
CN101262646A (zh) 控制发送多媒体消息的方法和多媒体消息业务中心
US9641646B1 (en) Distributed multimedia system for IP networks
WO2012151811A1 (zh) 多媒体消息的处理方法及装置
KR100604589B1 (ko) 번호 변경된 이동통신 단말기로의 메세지 포워딩 방법 및그 시스템
WO2012139359A1 (zh) 一种实现增值业务的方法、系统及装置
IES84271Y1 (en) A messaging system and method
GB2383229A (en) Preventing the wastage of network resources by preventing delivery of a message to a recipient who is not intended to receive it

Legal Events

Date Code Title Description
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: 2006741975

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2006741975

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 200680011715.0

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE