WO2005109793A1 - Procede de transmission de messages multimedia - Google Patents

Procede de transmission de messages multimedia Download PDF

Info

Publication number
WO2005109793A1
WO2005109793A1 PCT/CN2005/000424 CN2005000424W WO2005109793A1 WO 2005109793 A1 WO2005109793 A1 WO 2005109793A1 CN 2005000424 W CN2005000424 W CN 2005000424W WO 2005109793 A1 WO2005109793 A1 WO 2005109793A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
short message
push notification
mmsc
multimedia
Prior art date
Application number
PCT/CN2005/000424
Other languages
English (en)
French (fr)
Inventor
Fei Tang
Dawei Li
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 JP2007511834A priority Critical patent/JP4628420B2/ja
Priority to BRPI0510018-6A priority patent/BRPI0510018A/pt
Priority to EP05741909A priority patent/EP1747650A4/en
Publication of WO2005109793A1 publication Critical patent/WO2005109793A1/zh
Priority to US11/558,612 priority patent/US7917161B2/en

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/21Monitoring or handling of messages
    • H04L51/224Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • H04W4/14Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/26Network addressing or numbering for mobility support
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation

Definitions

  • the present invention relates to multimedia information communication technology, and in particular, to a method for sending multimedia messages.
  • the Multimedia Message Service Centre (MMSC) is responsible for sending multimedia messages composed of plain text, pictures, video, audio, and other media formats on the network.
  • MMS multimedia message service
  • VASP Value-added service provider
  • the delivery process includes two stages: the PUSH notification process and the message extraction process.
  • the PUSH notification process of the MMS service is mainly that the MMSC sends a PUSH notification to the receiver terminal through one or more short messages, and the PUSH notification includes related information about the multimedia message: for example, the addressing information required by the receiver terminal to extract the multimedia message, Sender identification, multimedia message subject, and receiver terminal address information.
  • the addressing information is the unique identifier of the MMSC address and the multimedia message in the MMSC.
  • FIG. 1 shows the entire sending process of a multimedia message initiator, such as an MMS terminal, a VASP, or a mail server, in the prior art to send a multimedia message to the receiving MSC / MMS terminal, including:
  • Step 11 The initiator of the multimedia message submits the multimedia message to the MMSC.
  • the multimedia message includes the address information of the receiver's MMS terminal, such as a mobile phone number.
  • Step 12 After receiving the multimedia message, the MMSC starts a PUSH notification process, and sends a PUSH notification to the receiving MMS terminal, which specifically includes the following steps:
  • Step 1201 The MMSC sends a PUSH information message push-message to a wireless application gateway (WapGW, Wireless Application Gateway), and records the number of times this step is performed.
  • the PUSH information message push-message includes a PUSH notification, and the PUSH notification further includes content such as addressing information required by the receiver MMS terminal to extract the multimedia message, the identifier of the sender, the subject of the multimedia message, and the address information of the receiver MMS terminal.
  • the addressing information is an MMSC address and a unique identifier of the multimedia message in the MMSC.
  • Step 1202 The WAPGW receives a PUSH information message push-message, and returns a PUSH response message push-response to the MMSC.
  • Step 1203 The WAPGW uses the interface protocol between the WAPGW and the short message center (SMSC), that is, the short message point-to-point protocol (SMPP) to encapsulate the PUSH notification in the PUSH information message push-message with a short message, and sends it to the SMSC using the SMPP protocol.
  • the submit message submit_sm includes a short message containing a PUSH notification, and records the number of times this step is performed.
  • the interface protocol between WAPGW and SMSC can also use User Datagram Protocol (UCP), Computer Interface Information Transmission Protocol (CIMD), or other similar protocols.
  • UCP User Datagram Protocol
  • CIMD Computer Interface Information Transmission Protocol
  • Step 1204 After receiving the submission message submit_sm, the SMSC returns a submission response submit_sm_resp to the WAPGW, and executes step 1205.
  • the SMSC sends a short message to the receiving MMS terminal.
  • Step 1205 The SMSC determines the location register (HLR) address to which the receiver MMS terminal belongs by sending the address information of the receiver MMS terminal included in the PUSH notification in the submission message and sends a routing request message map_sri— for— sm_req to the HLR. , And record the number of times this step is performed. If the current network is a CDMA network, the routing request message is an SMSREQ message.
  • HLR location register
  • Step 1206 After receiving the routing request message map_sri_for_sm_req, the HLR returns a routing response message map_sri_for_sm_resp to the SMSC, and the routing response message map_sri_for__sm_resp includes the receiver MMS. MSC address where the terminal is currently located.
  • the routing response message is an smsreq message. If the current network is a CDMA network, the routing response message is an smsreq message. If the current network is a GPRS and WCDMA network, the routing information included in the routing response message is the MSC or SGSN address where the receiver terminal is currently located.
  • Step 1207 The SMSC reads the routing information in the routing response message map_sri_for_sm_resp, and sends a short message sending request message map_mt_fwd_sm_req to the receiving MMS terminal through the receiving MSC according to the routing information, which includes a PUSH notification. If the current network is a CDMA network, the short message sending request message is a point-to-point short message sending request message (SMDPP).
  • SMSP point-to-point short message sending request message
  • Step 1208 The receiving MMS returns a short message and sends a response message map_mt_wd_sm_resp to the SMSC through the receiving MSC.
  • the short message sending response message map_mt_M_sm_resp includes information that the PUSH notifies whether the delivery is successful.
  • the SMSC judges within a predetermined time whether it received a PUSH notification to send a successful short message sending response message map_mt_fwd_sm_resp, and if so, execute step 1209; otherwise, the SMSC selects whether to resend and resend the time according to the internal retransmission policy. If the retransmission is performed, it is determined whether the number of times of performing step 1205 exceeds the predetermined number. If the number of times is exceeded, the SMSC determines that the PUSH notification fails to be issued, and executes step 1209; if the number of times is not exceeded, the retransmission is taken. Strategy, return to step 1205.
  • the response message returned by the MSC to the SMSC is smdp 0
  • Step 1209 The SMSC sends a delivery report message deliver_sm to the WAPGW, and the delivery report message deliver_sm includes information that the PUSH notifies whether the delivery is successful.
  • Step 1210 After receiving the delivery report message deliver_sm, the WAPGW returns a delivery report response to the SMSC to deliver_sm_resp. And determine whether the PUSH notification is successfully issued according to the content of the delivery report message; if successful, execute step 1211; otherwise, determine whether to retransmit according to the internal retransmission policy; if retransmit, determine whether the number of times to execute step 1203 exceeds a predetermined If the number of times exceeds the predetermined number, the WAPGW determines that the PUSH notification fails to be issued, and executes step 1211. If the number of times does not exceed the predetermined number, the WAPGW adopts a retransmission policy, and returns to step 1203.
  • step 1211 the WAPGW sends a result notification message to the MMSC, resultnotification-message.
  • the resultnotification-message of the result notification message includes information about whether the PUSH notification is successful.
  • Step 1212 After receiving the result notification message, the MMSC returns a result notification response-response-response to the WAPGW, and judges whether the PUSH notification is successfully delivered according to the content of the result notification message result-notification-message. If it is successful, the PUSH notification process ends. Otherwise, according to the internal retransmission policy, the SMSC selects whether to retransmit and the time for retransmission. If it is retransmitted, it determines whether the number of times to execute step 1201 exceeds a predetermined number of times. If it exceeds the predetermined number, the MMSC determines that the PUSH notification has failed to be issued. , End the sending process of the multimedia message, determine that the sending of the multimedia message fails, and execute step 17. If the predetermined number of times is not exceeded, the MMSC adopts a retransmission policy, and returns to step 1201.
  • Step 13 After receiving the short message containing the PUSH notification, the receiver MMS terminal processes it according to its own selection mode: if the receiver MMS terminal chooses to delay the extraction of the multimedia message, the multimedia message is extracted according to the extracted multimedia contained in the PUSH notification information. The addressing information of the message is reported to the MMSC through the notification response MM1_notification.RES, and the PUSH notification has been received, and then step 14 is performed; if the receiver MMS terminal chooses to immediately retrieve the multimedia message, step 14 is directly performed. '
  • Step 14 When the multimedia message retrieval time arrives, the receiving MMS terminal sends a multimedia message retrieval request MMl_retrieve.REQ to the MMSC according to the addressing information of the extracted multimedia message contained in the PUSH notification message.
  • Step 15 The MMSC sends a multimedia message to the receiving MMS terminal through the multimedia message retrieval response MMl_retrieve.RES.
  • Step 16 the receiving MMS terminal confirms the message MM1_acknowledgement.REQ through the multimedia message to the MMSC to receive the status of the multimedia message.
  • the receiver terminal returns the reception status of the multimedia message to the MMSC through a notification response MM1-notification.RES message.
  • Step 17 If the sender requires to know the sending status of the multimedia message, the MMSC returns a multimedia message sending status report to the sender, where the sending status report contains the receiving status information of the receiving multimedia message; if the sender does not require to know the sending of the multimedia message Status, the process ends.
  • the PUSH notification process is very important for the entire MMS service and is a necessary condition to ensure that the receiver can obtain the message normally.
  • the current WAPGW supports interface protocols that can communicate with short message centers, such as SMPP, UCP, and CIMD
  • the current WAPGW can use this interface protocol to encapsulate PUSH notifications with short messages, and use this interface protocol to communicate with short messages.
  • Message center communication and the current MMSC does not support the interface protocol that can communicate with the short message center, because Therefore, in the existing PUSH notification process, the WAPGW must communicate with the short message center.
  • there are many intermediate links in the PUSH notification process it is difficult to coordinate the retransmission mechanisms of MMSC and WAPGW, and the success rate and efficiency of PUSH notifications are relatively low.
  • the main object of the present invention is to provide a method for sending a multimedia message, improve the efficiency and success rate of sending multimedia messages, and reduce costs.
  • a method for sending a multimedia message is characterized in that the method adds an interface protocol module capable of communicating with a short message system to a multimedia message service center MMSC, and includes:
  • the initiator of the multimedia message submits the multimedia message including the address information of the multimedia receiver to the MMSC;
  • the MMSC initiates a PUSH notification process, and sends an PUSH notification to the short message system using an interface protocol that can communicate with the short message system;
  • the short message system obtains routing information of the multimedia message receiver from the home location register HLR of the multimedia message receiver, and sends the PUSH notification to the multimedia message receiver according to the routing information;
  • the multimedia message receiver starts the multimedia message extraction process, and extracts the multimedia message from the MMSC according to the multimedia message addressing information in the PUSH notification.
  • the short message system is a short message center, or a short message gateway and a short message center.
  • the short message system is a short message center, and in step b, the method for the MMSC to send a PUSH notification to the short message center using an interface protocol that can communicate with the short message center is:
  • the MMSC uses an interface protocol that can communicate with the short message center to encapsulate the PUSH notification into a short message containing the PUSH notification, and uses the interface protocol to send the short message containing the PUSH notification to the short message center.
  • the interface protocols that can communicate with the short message center are: short message point-to-point protocol SMPP, user datagram protocol UCP, and computer interface information sending protocol CIMD.
  • the short message system is a short message gateway and a short message center
  • the method for the MMSC in step b to send a PUSH notification to the short message system using an interface protocol that can communicate with the short message system is:
  • the MMSC uses the interface protocol between the MMSC and the short message gateway to encapsulate the PUSH notification into a message containing the PUSH notification, and uses the interface protocol between the MMSC and the short message gateway to send the message containing the PUSH notification to the short message gateway. ;
  • the short message gateway uses the interface protocol between the short message gateway and the short message center to encapsulate the PUSH notification into a short message containing the PUSH notification, and uses the interface protocol between the short message gateway and the short message center to send the short message center Send the short message containing the PUSH notification.
  • the interface protocol between the MMSC and the short message gateway is China Mobile Point-to-Point Protocol CMPP or China Unicom Short Message Gateway Interface Protocol SGIP, and the interface protocol between the short message gateway and the short message center is SMPP, UCP or CIMD.
  • the method for the short message system to obtain the routing information of the multimedia message receiver from the HLR of the multimedia message receiver in step c is:
  • the short message center finds the multimedia message receiver's home HLR through the multimedia message receiver address information in the PUSH notification, and sends a routing request message to the HLR. c 2. After receiving the routing request message, the HLR returns the route to the short message center. Response message, The routing response message includes the routing information of the multimedia message receiver. After receiving the routing response message, the short message center obtains the routing information of the multimedia message receiver.
  • the short message system is a short message center, and after the step C, the method further includes: c3.
  • the multimedia message receiving direction returns a short message sending response message to the short message center.
  • the short message sending response message includes whether the PUSH notification is issued.
  • the short message center determines within a predetermined time whether a short message sending response message containing the PUSH notification and delivery success information is received, and if so, executes c4; otherwise, determines whether the number of times of performing step c exceeds a predetermined number of times, If yes, the short message center determines that the PUSH notification delivery fails, and executes step c4; otherwise, the short message center adopts a retransmission strategy, and returns to step c;
  • the short message center sends a delivery report message to the MMSC, where the delivery report message includes information that the PUSH notifies whether the delivery is successful;
  • the MMSC receives the delivery report message, and judges whether the PUSH notification is successfully delivered according to the content of the delivery report message. If it is successful, the PUSH notification process is ended; otherwise, it is determined whether the number of times of performing the ankle b has exceeded a predetermined number of times, and if so, then The MMSC determines that the PUSH notification delivery fails, and ends the sending process of the multimedia message; otherwise, the MMSC adopts a retransmission strategy, and returns to step 1 ?.
  • step c the method further includes:
  • the multimedia message receiving direction returns a short message sending response message to the short message center.
  • the short message sending response message includes information on whether the PUSH notification is issued successfully, and the short message center determines within a predetermined time whether it has received a PUSH notification.
  • Send a response message with a success message if yes, execute c4 '; otherwise, determine whether the number of times to perform step c exceeds a predetermined number of times, and if so, the short message center determines that the PUSH notification has failed to be issued, and executes step c4' Otherwise, the short message center adopts a retransmission strategy, and returns to step c;
  • the short message center sends a delivery report message to the short message gateway, where the delivery report message includes information that the PUSH notifies whether the delivery is successful; c5 '.
  • the short message gateway receives the delivery report message, and judges whether the PUSH notification is successfully delivered according to the content of the delivery report message. If successful, step c6' is performed. Otherwise, it is determined whether the number of times to perform step b2 'exceeds a predetermined number of times. If yes, the short message gateway determines that the PUSH notification has failed to be issued, and executes step c6; otherwise, the short message gateway adopts a retransmission strategy, and returns to step b2;
  • the short message gateway sends a result notification message to the MMSC, where the result notification message includes information about whether the PUSH notification is issued successfully;
  • the MMSC receives the result notification message, and determines whether the PUSH notification is successfully delivered based on the content of the result notification message. If it is successful, the PUSH notification process ends; otherwise, it determines whether the number of times to perform step b1' exceeds a predetermined number of times. If yes, Then the MMSC determines that the PUSH notification has failed to be delivered, and ends the sending process of the multimedia message; otherwise, the MMSC adopts a retransmission strategy, and returns to step b1 '.
  • the step d specifically includes:
  • the multimedia message receiver sends a multimedia message extraction request to the MMSC according to the addressing information of the multimedia message extraction contained in the PUSH notification information;
  • the MMSC sends the multimedia message to the receiver of the multimedia message through the multimedia message extraction response;
  • the multimedia message receiving direction returns the receiving status of the multimedia message to the MMSC.
  • step dl Before the step dl, it further includes:
  • the multimedia message receiver selects the extraction mode. If the multimedia message receiver chooses to delay the extraction of the multimedia message, it reports to the MMSC through a notification response that a PUSH notification has been received according to the addressing information of the extracted multimedia message contained in the PUSH notification information. Step dl is performed again; if the receiver of the multimedia message chooses to extract the multimedia message immediately, step dl is directly performed.
  • the network to which the short message system belongs is: Global Mobile Communication Network GSM, Universal Wireless Branch Group business network GPRS, Wideband Code Division Multiple Access WCDMA, Code Division Multiple Access CDMA95 network or CDMA2000 network.
  • the method described in the present invention adds an interface protocol module that can communicate with the short message system in the MMSC, and enables the MMSC to communicate directly with the short message system, the participation of the WAPGW in the PUSH notification process can be eliminated and the middle of the PUSH notification process can be reduced. Link to eliminate the dependence of the WAPGW on sending multimedia messages, and further eliminate the inconsistencies between the MMSC and WAPGW retransmission mechanisms.
  • the short message system is an intermediate communication device capable of forwarding short messages.
  • the short message system may be a short message center, or a short message gateway and a short message center.
  • the short message system is a short message center
  • MMSC directly communicates with the short message center, reducing intermediate links, it can improve the efficiency and success rate of sending multimedia messages, improve the quality of service of multimedia message services, and reduce costs; in addition, Since the MMSC in the method of the present invention can directly communicate with short message centers of various networks by using an interface protocol, the flexibility of multimedia message service networking is improved.
  • FIG. 1 is a flowchart of sending a multimedia message in the prior art
  • FIG. 2 is a flowchart of sending a multimedia message when the short message system according to the present invention is a short message center;
  • FIG. 3 is a flowchart of sending a multimedia message when the short message system according to the present invention is a short message gateway and a short message center. Mode for Carrying Out the Invention The implementation method of the present invention is further described below with reference to the drawings and specific embodiments.
  • the core idea of the present invention is: In the PUSH notification process, the participation of WAPGW is eliminated, and the MMSC communicates directly with the short message system to complete the delivery of the PUSH notification.
  • the short message system of the present invention is a short message center, or a short message gateway and a short message center.
  • an interface protocol module capable of communicating with a short message system is added to the MMSC.
  • the short message system is a short message center SMSC
  • an interface protocol module capable of directly communicating with the SMSC is added to the MMSC, such as in a GSM network.
  • the SMPP protocol module is used in other networks, which can be UCP protocol module, CIMD protocol module, or other protocol modules.
  • the short message system is a short message gateway and SMSC
  • Gateway protocol module such as China Mobile Peer to Peer (CMPP), China Unicom Short Message Gateway Interface Protocol (SGIP), or other similar protocol modules.
  • the sender of a multimedia message such as an MMS terminal, a VASP, or a mail server, sends a multimedia message to the receiver's MMS terminal.
  • the entire sending process includes:
  • Step 21 The initiator of the multimedia message submits the multimedia message to the MMSC, and the multimedia message includes address information of the receiver's MMS terminal, such as a mobile phone number;
  • Step 22 After receiving the multimedia message, the MMSC initiates a PUSH notification process, and sends a PUSH notification to the receiving MMS terminal.
  • the PUSH notification includes the receiving MMS terminal extraction. Addressing information required for multimedia messages, identification of sender, subject of multimedia message, and receiver
  • the MMS terminal address information is the unique identifier of the MMSC address and the multimedia message in the MMSC.
  • the PUSH notification process specifically includes the following steps:
  • Step 2201 The MMSC uses an interface protocol for communication with the SMSC, such as the SMPP protocol, to encapsulate the PUSH notification into a short message, and uses the interface protocol to send a submit message to the SMSC, submit—sm, which includes a PUSH notification.
  • the short message records the number of times this step is performed.
  • the interface protocol between MMSC and SMSC can also use the UCP protocol, CIMD protocol, or other similar protocols.
  • the SMPP protocols involved in this article can be replaced by the above UCP protocol, CIMD protocol, or other similar protocols.
  • Step 2202. After receiving the submission message submit_sm, the SMSC returns a submission response submit_sm_resp to the MMSC.
  • the following steps 2203 to 2206 are the procedures for the SMSC to send a short message to the receiving MMS terminal:
  • Step 2203 The SMSC determines the location register (HLR) address to which the receiver MMS terminal belongs by sending the address information of the receiver MMS terminal included in the PUSH notification in the submission message sm, and sends a routing request message map_sri_ to the HLR ⁇ _ — Sm— req, and record the number of times this step is performed.
  • HLR location register
  • Step 2204 After receiving the routing request message map_sri_for_sm_req, the HLR returns a routing response message map_sri_for_sm_resp to the SMSC, and the routing response message map_sri_for_sm_resp includes receiving.
  • the routing information of the remote MMS terminal that is, the MSC address where the receiving MMS terminal is currently located.
  • the routing response message is an smsreq message. If the current network is a CDMA network, the routing response message is an smsreq message. If the current network is a GPRS and WCDMA network, the routing information included in the routing response message is The information is a service general packet service node (SGSN) address.
  • SGSN service general packet service node
  • Step 2205 The SMSC reads the routing information in the routing response message map_sri_for_sm_resp, and sends a short message sending request message map_mt_ ⁇ vd_sm_req through the receiving MSC to the receiving MMS terminal according to the routing information, which contains the required information.
  • Step 2206 The receiver MMS returns a short message and sends a response message map_mt_fwd_sm_resp to the SMSC through the receiver MSC.
  • the short message sending response message map_mt_f_d_smjresp includes information of whether the PUSH notification is successful.
  • the SMSC determines within a predetermined time whether it received a PUSH notification to send a successful short message sending response message map_mt_ wd_sm_resp, and if so, executes the next step; otherwise, the SMSC selects whether to resend and resend according to the internal retransmission policy.
  • Time if it is retransmitted, determine whether the number of times of performing step 2203 exceeds a predetermined number of times, if it exceeds the predetermined number of times, SMSC determines that the PUSH notification fails to be issued, and executes the next step; if it does not exceed the predetermined number of times, SMSC takes a retransmission Send the strategy, and return to step 2203.
  • the response message returned by the MSC to the SMSC is smdpp.
  • Step 2207 The SMSC sends a delivery report message deliver_sm to the MMSC, and the delivery report message deliver_sm includes information that the PUSH notifies whether the delivery is successful.
  • Step 2208 After receiving the delivery report message deliver_sm, the MMSC returns a delivery report response deliver_sm_resp to the SMSC. It then judges whether the PUSH notification is successfully delivered according to the content of the delivery report message. If it is successful, the PUSH notification process is ended; otherwise, the MMSC chooses whether to retransmit and the time for retransmission according to the internal retransmission policy. If it is retransmitted, then It is determined whether the number of times of performing step 2201 exceeds a predetermined number of times.
  • step 2201 determines that the PUSH notification fails to be delivered, ends the sending process of the multimedia message, and determines that the multimedia The message sending fails, and step 17 is performed; if the predetermined number of times is not exceeded, the MMSC adopts a retransmission policy, and returns to step 2201.
  • Step 23 After receiving the PUSH notification, the receiving MMS terminal performs processing according to its own selection mode: If the receiving MMS terminal chooses to extract multimedia messages with a delay, then according to the addressing of the extracted multimedia messages contained in the PUSH notification information Information, notify the MMSC through the notification response MMl_notification.RES that the PUSH notification has been received, and then execute step 24; if the receiver MMS terminal chooses to immediately retrieve the multimedia message, directly perform step 24.
  • Step 24 When the multimedia message retrieval time arrives, the receiving MMS terminal sends a multimedia message retrieval request MMl_retrieve.REQ to the MMSC according to the addressing information of the extracted multimedia message contained in the PUSH notification message.
  • Step 25 The MMSC sends a multimedia message to the receiving MMS terminal through the multimedia message retrieval response MMl_retrieve.RES.
  • Step 26 In the case of delayed extraction, the receiver MMS terminal acknowledges the message MMl—acknowledgement.REQ through the multimedia message to the MMSC to receive the status of the multimedia message. In the case of immediate extraction, the receiver terminal returns the reception status of the multimedia message to the MMSC through a notification response MM1-notification.RES message.
  • Step 27 If the sender requires to know the sending status of the multimedia message, the MMSC returns a multimedia message sending status report to the sender, where the sending status report includes the receiving status information of the receiving multimedia message; if the sender does not require to know the sending of the multimedia message Status, the process ends.
  • the networking method described in the method of the present invention can be used, that is, the MMSC uses the corresponding interface protocol to directly communicate with various mobile networks or fixed networks.
  • Short message system Communication to complete the sending of multimedia messages.
  • the MMSC can directly connect to the CDMA short message center MC to complete the sending of multimedia messages.
  • FIG. 3 shows the whole process of sending a multimedia message to a receiver MMS terminal when the short message system according to the present invention is a short message gateway and an SMSC.
  • the process is similar to the process shown in FIG. 2 except that The interaction process between the MMSC and the short message system is slightly different. Only the interaction process between the MMSC and the short message system is described below.
  • the MMSC After receiving the multimedia message, the MMSC starts a PUSH notification process, including:
  • Step 3201 the MMSC uses an interface protocol between the MMSC and the short message gateway, such as CMPP, to encapsulate the PUSH notification into a message containing the PUSH notification, and use the CMPP to send the PUSH information message containing the PUSH notification to the short message gateway CMPP_SUBMIT, And record the number of times this step was performed.
  • CMPP short message gateway
  • Step 3202. After receiving the CMPP_SUBMIT, the short message gateway returns a PUSH response message CMPP_SUBMIT_RESP to the MMSC.
  • Step 3203 The short message gateway uses an interface protocol between the short message gateway and the SMSC, such as SMPP, to encapsulate the PUSH notification into a short message containing the PUSH notification, and sends the submit message containing the PUSH notification to SMSC using submit-sm, And record the number of times this step was performed.
  • the interface protocol here can also be UCP, CIMD, or other similar protocols.
  • Step 3204 After receiving the submit_sm, the SMSC returns a submit response submit_sm_resp to the short message gateway, and executes step 2203.
  • step 2203 to step 2206 are performed. Please refer to the description of FIG. 2 for the operation process from step 2203 to step 2206. After performing step 2206, perform the following steps:
  • Step 3205 The SMSC sends a delivery report message deliver_sm to the short message gateway, and the deliver_sm includes information that the PUSH notifies whether the delivery is successful.
  • Step 3206 After receiving the deliver_sm, the short message gateway returns deliver_sm_resp to the SMSC, and judges whether the PUSH notification is successfully delivered according to the contents of the deliver_sm. If successful, go to step 3207; otherwise, determine whether the number of times to perform step 3203 exceeds a predetermined number of times. If so, the short message gateway determines that the PUSH notification fails to be issued and executes step 3207; otherwise, the short message gateway adopts a retransmission strategy. Return to step 3203.
  • Step 3207 The short message gateway sends a result notification message to the MMSC.
  • the CMPP_ DELIVER includes a notification that the PUSH notification is issued successfully.
  • Step 3208 The MMSC receives the CMPP_DELIVERS, and returns a result notification response CMPP_DELIVER_RESP to the short message gateway, and judges whether the PUSH notification is successfully issued according to the content of the CMPP_DELIVER. If the PUSH notification is successful, the PUSH notification process is ended; otherwise, the determination is performed in step 3201. Whether the number of times exceeds a predetermined number, if yes, the MMSC determines that the PUSH notification delivery fails, and ends the sending process of the multimedia message; otherwise, the MMSC adopts a retransmission strategy, and returns to step 3201.
  • the multimedia message extraction process is the above steps 23 to 27.

Landscapes

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

Description

一种多媒体消息的发送方法
技术领域
本发明涉及多媒体信息通讯技术, 尤其涉及一种多媒体消息的发送 方法。 发明背景 多媒体消息业务中心 ( MMSC , Multimedia Message Service Centre ) 负责在网络上发送由纯文本、 图片、 视频、 音频及其他媒体格式组成的 多媒体消息。 MMSC收到多媒体消息业务(MMS, Multimedia Message Service )终端、 增值业务提供商 (VASP, Value Added Service Provider )或者邮件服务器发给 MMS终端的多媒体消息时, 启动下发 流程。下发流程包括 PUSH通知流程和消息提取流程两个阶段。目前 MMS 业务的 PUSH通知流程主要是 MMSC通过一条或者多条短消息向接收方 终端发送 PUSH通知, 该 PUSH通知包括有关多媒体消息的相关信息: 例 如接收方终端提取多媒体消息所需的寻址信息、 发送方标识、 多媒体消 息主题和接收方终端地址信息等。 其中寻址信息为 MMSC地址和多媒体 消息在 MMSC中的唯一标识。 接收方终端收到 PUSH通知后, 便启动消 息提取过程, 即根据 PUSH通知中包括的寻址信息, 向存储多媒体消息 的 MMSC发起消息提取请求, 并提取多媒体消息。
多媒体消息在全球移动通信网 (GSM ) 、 通用无线分组业务网 ( GPRS )、宽带码分多址( "WCDMA )、码分多址( CDMA )95^ CDMA2000 和其他网络中的发送过程较类似 , 因此下面以多媒体消息在 GSM网络中 的发送过程为例说明现有技术多媒体消息的发送方案。 如图 1所示为现有技术中多媒体消息发起方,例如 MMS终端、 VASP 或邮件服务器, 向接收方 MSC/MMS终端发送一条多媒体消息的整个发 送过程, 包括:
步骤 11、 多媒体消息的发起方将多媒体消息提交给 MMSC, 该多媒 体消息中包括接收方 MMS终端的地址信息, 例如手机号码;
步骤 12、 MMSC收到多媒体消息后, 启动 PUSH通知流程, 向接收 方 MMS终端下发 PUSH通知, 具体包括以下步骤:
步骤 1201 、 MMSC向无线应用 网关 ( WAPGW , Wireless Application Gateway )发送 PUSH信息消息 push-message, 并记录执行 本步骤的次数.。 所述 PUSH信息消息 push-message中包括 PUSH通知, 该 PUSH通知中又包括接收方 MMS终端提取多媒体消息所需的寻址信息、 发送方的标识、 多媒体消息主题和接收方 MMS终端地址信息等内容, 所 述寻址信息为 MMSC地址和所述多媒体消息在 MMSC中的唯一标识。
步骤 1202、 WAPGW收到 PUSH信息消息 push-message, 向 MMSC返 回 PUSH响应消息 push-response。
步骤 1203、 WAPGW使用 WAPGW与短消息中心(SMSC )之间的接 口协议, 即短消息点对点协议(SMPP )对 PUSH信息消息 push-message 中的 PUSH通知进行短消息封装, 并使用 SMPP协议向 SMSC发送提交消 息 submit— sm, 该提交消息 submit— sm中包括含有 PUSH通知的短消息, 记 录执行本步骤的次数。 在某一运营商的实际网络中 WAPGW与 SMSC之 间的接口协议也可以使用用户数据报协议(UCP ) 、 计算机接口信息发 送协议(CIMD )或其他同类协议。
步骤 1204、 SMSC收到提交消息 submit— sm后, 向 WAPGW返回提交 响应 submit— sm—resp, 并执行步骤 1205。
以下步驟 1205至步骤 1208为 SMSC向接收方 MMS终端下发短消息 的流程:
步骤 1205、 SMSC通过提交消息 submit— sm中 PUSH通知包含的接收 方 MMS终端地址信息确定接收方 MMS终端归属的位置寄存器 ( HLR ) 地址, 并向该 HLR发送路由请求消息 map—sri— for— sm_req, 并记录执行本 步驟的次数。 如果当前网络为 CDMA网络, 则路由请求消息为 SMSREQ 消息。
步驟 1206、 HLR收到路由请求消息 map_sri— for— sm_req后, 向 SMSC 返回路由响应消息 map— sri— for— sm一 resp , 所述的路由响应消息 map—sri—for__sm— resp中包括接收方 MMS终端当前所在的 MSC地址。
如果当前网络为 CDMA网络, 则所述路由响应消息为 smsreq消息, 如果当前网络为 GPRS和 WCDMA网絡,则路由响应消息中包括的路由信 息为接收方终端当前所在 MSC或 SGSN地址。
步骤 1207、 SMSC读取路由响应消息 map— sri_for— sm— resp中的路由信 息,根据该路由信息通过接收方 MSC向接收方 MMS终端下发短消息发送 请求消息 map_mt— fwd_sm_req , 其中包括含有 PUSH通知的短消息; 如果当前网络为 CDMA网络, 则所述的短消息发送请求消息为点对 点短消息发送请求消息 (SMDPP ) 。
步骤 1208、接收方 MMS通过接收方 MSC向 SMSC返回短消息发送响 应 消 息 map— mt— wd—sm— resp 。 该 短 消 息 发 送 响 应 消 息 map_mt_M_sm_resp包括 PUSH通知是否下发成功的信息。 SMSC在预定 时间内判断是否收到 PUSH通知下发成功的短消息发送响应消息 map_mt_fwd_sm_resp, 如果是, 则执行步骤 1209; 否则, SMSC根据内 部重发策略, 选择是否重发和重发^时间, 如果重发, 则判断执行步骤 1205的次数是否超过预定次数, 如果超过预定次数, 则 SMSC认定 PUSH 通知下发失败, 并执行步骤 1209; 如果没有超过预定次数, 则采取重发 策略, 返回步骤 1205。
如果当前网络为 CDMA网絡, 则 MSC向 SMSC返回的响应消息为 smdp 0
步驟 1209、 SMSC向 WAPGW发送递送报告消息 deliver— sm, 该递送 报告消息 deliver— sm包括 PUSH通知是否下发成功的信息。
步驟 1210、 WAPGW收到递送报告消息 deliver— sm后, 向 SMSC返回 递送报告响应 deliver— sm—resp。并根据递送报告消息的内容判断 PUSH通 知是否下发成功, 如果成功, 则执行步驟 1211; 否则, 根据内部重发策 略, 决定是否重发, 如果重发则判断执行步骤 1203的次数是否超过预定 的次数, 如果超过预定次数, 则 WAPGW认定 PUSH通知下发失败, 并执 行步驟 1211 , 如果没有超过预定的次数, 则 WAPGW采取重发策略, 返 回步骤 1203。
步 骤 1211 、 WAPGW 向 MMSC 发 送 结 果 通 知 消 息 resultnotification - message, 该结果通知消息 resultnotification-message中包 括 PUSH通知是否下发成功的信息。
步骤 1212、 MMSC收到结果通知消息后, 向 WAPGW返回结果通知 响 应 resultnotification-response , 并 才艮 据 结 果 通 知 消 息 resultnotification-message的内容判断 PUSH通知是否下发成功, 如果成 功, 则结束 PUSH通知流程; 否则, SMSC根据内部重发策略, 选择是否 重发和重发的时间, 如果重发, 则判断执行步骤 1201的次数是否超过预 定的次数, 如果超过预定的次数, 则 MMSC认定 PUSH通知下发失败, 结束该多媒体消息的发送流程, 认定该多媒体消息发送失败, 并执行步 驟 17, 如果没有超过预定的次数, 则 MMSC采取重发策略, 返回步骤 1201。
以下的步骤 13至步骤 17为多媒体消息的提取流程: 步骤 13、 接收方 MMS终端收到含有 PUSH通知的短消息后, 根据自 身的选择模式进行处理:如果接收方 MMS终端选择延时提取多媒体消息 的情况下, 则根据 PUSH通知信息中包含的提取多媒体消息的寻址信息, 通过通知响应 MMl— notification.RES向 MMSC报告已收到 PUSH通知, 再 执行步驟 14; 如果接收方 MMS终端选择立即提取多媒体消息的情况下, 则直接执行步骤 14。 '
步骤 14、当多媒体消息提取时间到达时,接收方 MMS终端根据 PUSH 通知信息中包含的提取多媒体消息的寻址信息, 向 MMSC发送多媒体消 息提取请求 MMl— retrieve.REQ。
步驟 15、 MMSC通过多媒体消息提取响应 MMl— retrieve.RES向接收 方 MMS终端下发多媒体消息。
步驟 16、在延时提取的情况下,接收方 MMS终端通过多媒体消息确 认消息 MMl_acknowledgement.REQ向 MMSC返回多媒体消息的接收状 态。 在立即提取的情况下 , 接收方终端通过通知响应 MMl— notification.RES消息向 MMSC返回多媒体消息的接收状态。
步骤 17、 如果发送方要求获知多媒体消息的发送状态, 则 MMSC向 发送方返回多媒体消息发送状态报告, 该发送状态报告包含接收方多媒 体消息的接收状态信息; 如果发送方没有要求获知多媒体消息的发送状 态, 则结束流程。
由上述流程可看出 PUSH通知流程对于整个 MMS业务至关重要, 是 保证接收方正常获取消息的必要条件。
但是, 由于当前的 WAPGW支持可与短消息中心进行通讯的接口协 议, 例如 SMPP、 UCP和 CIMD, 因此当前的 WAPGW都可使用该接口 协议对 PUSH通知进行短消息封装, 并利用该接口协议与短消息中心通 讯, 而当前的 MMSC 不支持可与短消息中心进行通讯的接口协议, 因 此,在现有的 PUSH通知流程中, 必须经过 WAPGW才能与短消息中心 进行通讯。 由此导致 PUSH通知流程的中间环节多, MMSC和 WAPGW 的重发机制难以协调一致, PUSH通知的成功率和效率也比较低, 因此 在很大程度上降低了多媒体消息的发送成功率, 大大影响了多媒体短消 息业务的服务质量。 另外, 由于中间环节过多, 运营的成本也比较高。 发明内容 有鉴于此, 本发明的主要目的是提供一种多媒体消息的发送方法, 提高多媒体消息的发送效率和成功率, 降低成本。
为了实现上述目的, 本发明的技术方案是这样实现的:
一种多媒体消息的发送方法, 其特征在于, 所述的方法在多媒体消 息业务中心 MMSC 中加入可与短消息系统进行通讯的接口协议模块, 并包括:
a、 由多媒体消息的发起方向 MMSC提交包括多媒体接收方地址信 息的多媒体消息;
b、 MMSC启动 PUSH通知流程, 使用可与短消息系统进行通讯的 接口协议向短消息系统发送 PUSH通知;
c、 短消息系统向多媒体消息接收方的归属位置寄存器 HLR获取多 媒体消息接收方的路由信息, 并根据该路由信息向多媒体消息接收方下 发所述 PUSH通知;
d、 多媒体消息接收方启动多媒体消息提取流程, 根据 PUSH通知 中多媒体消息寻址信息从 MMSC提取多媒体消息。
优选的, 所述的短消息系统为短消息中心, 或者为短消息网关和短 消息中心。 所述短消息系统为短消息中心, 且所述步骤 b中 MMSC使用可与 短消息中心进行通讯的接口协议向短消息中心发送 PUSH通知的方法 为:
bl、 MMSC使用可与短消息中心进行通讯的接口协议将 PUSH通知 封装成含有 PUSH通知的短消息, 并使用所述接口协议向短消息中心发 送该含有 PUSH通知的短消息。
所述可与短消息中心进行通讯的接口协议为: 短消息点对点协议 SMPP、 用户数据报协议 UCP、 计算机接口信息发送协议 CIMD。
所述短消息系统为短消息网关和短消息中心, 且所述步骤 b中 MMSC使用可与短消息系统进行通讯的接口协议向短消息系统发送 PUSH通知的方法为:
bl'、 MMSC使用 MMSC与短消息网关之间的接口协议将 PUSH通知 封装成含有 PUSH通知的消息, 并使用该 MMSC与短消息网关之间的接 口协议向短消息网关发送该含有 PUSH通知的消息;
b2'、 短消息网关利用短消息网关与短消息中心之间的接口协议将 PUSH通知封装成含有 PUSH通知的短消息, 并使用该短消息网关与短消 息中心之间的接口协议向短消息中心发送该含有 PUSH通知的短消息。
所述 MMSC与短消息网关之间的接口协议为中国移动点对点协议 CMPP或中国联通短消息网关接口协议 SGIP, 所述短消息网关与短消息 中心之间的接口协议为 SMPP、 UCP或 CIMD。
所述步骤 c中短消息系统向多媒体消息接收方的 HLR获取多媒体消 息接收方的路由信息的方法为:
cl、 短消息中心通过 PUSH通知中的多媒体消息接收方地址信息查 找到多媒体消息接收方归属 HLR, 并向该 HLR发送路由请求消息; c2、 HLR收到路由请求消息后, 向短消息中心返回路由响应消息, 该路由响应消息中包括多媒体消息接收方的路由信息, 短消息中心收到 路由响应消息后, 获取多媒体消息接收方的路由信息。
所述短消息系统为短消息中心, 且在所述步骤 C之后, 还包括: c3、 多媒体消息接收方向短消息中心返回短消息发送响应消息, 该 短消息发送响应消息中包括 PUSH通知是否下发成功的信息, 短消息中 心在预定的时间内判断是否收到含有 PUSH通知下发成功信息的短消息 发送响应消息, 如果是, 则执行 c4; 否则, 判断执行步骤 c的次数是否超 过预定次数, 如果是, 则短消息中心认定 PUSH通知下发失败, 并执行 步骤 c4; 否则, 短消息中心采取重发策略, 返回步驟 c;
c4、 短消息中心向 MMSC发送递送报告消息, 该递送报告消息包括 PUSH通知是否下发成功的信息;
c5、 MMSC收到递送报告消息,根据递送报告消息的内容判断 PUSH 通知是否下发成功, 如果成功, 则结束 PUSH通知流程; 否则, 判断执 行步踝 b的次数是否超过预定次数, 如果是, 则 MMSC认定 PUSH通知下 发失败, 结束该多媒体消息的发送流程; 否则, MMSC采取重发策略, 返回步骤1?。
在所述步骤 c之后, 还包括:
c3'、 多媒体消息接收方向短消息中心返回短消息发送响应消息, 该 短消息发送响应消息中包括 PUSH通知是否下发成功的信息, 短消息中 心在预定的时间内判断是否收到含有 PUSH通知下发成功信息的短消息 发送响应消息, 如果是, 则执行 c4'; 否则, 判断执行步驟 c的次数是否 超过预定次数, 如果是, 则短消息中心认定 PUSH通知下发失败, 并执 行步骤 c4'; 否则, 短消息中心采取重发策略, 返回步骤 c;
c4'、 短消息中心向短消息网关发送递送报告消息, 该递送报告消息 包括 PUSH通知是否下发成功的信息; c5'、 短消息网关收到递送报告消息, 根据递送报告消息的内容判断 PUSH通知是否下发成功, 如果成功, 则执行步骤 c6', 否则, 判断执行 步骤 b2'的次数是否超过预定次数, 如果是, 则短消息网关认定 PUSH通 知下发失败, 并执行步骤 c6,; 否则, 短消息网关采取重发策略, 返回步 驟 b2,;
c6'、 短消息网关向 MMSC发送结果通知消息, 该结果通知消息包括 PUSH通知是否下发成功的信息;
c7'、 MMSC收到结果通知消息, 居结果通知消息的内容判断 PUSH 通知是否下发成功, 如果成功, 则结束 PUSH通知流程; 否则, 判断执 行步骤 bl'的次数是否超过预定次数, 如果是, 则 MMSC认定 PUSH通知 下发失败, 结束该多媒体消息的发送流程; 否则, MMSC采取重发策略, 返回步骤 bl'。
优选的, 所述的步骤 d具体包括:
dl、 多媒体消息接收方根据 PUSH通知信息中包含的提取多媒体消 息的寻址信息, 向 MMSC发送多媒体消息提取请求;
d2、 MMSC通过多媒体消息提取响应向多媒体消息接收方下发多媒 . 体消息;
d3、 多媒体消息接收方向 MMSC返回多媒体消息的接收状态。
在所述步驟 dl之前, 进一步包括:
多媒体消息接收方选择提取模式, 如果多媒体消息接收方选择延时 提取多媒体消息, 则根据所述 PUSH通知信息中包含的提取多媒体消息 的寻址信息, 通过通知响应向 MMSC报告已收到 PUSH通知, 再执行步 骤 dl; 如果多媒体消息接收方选择立即提取多媒体消息, 则直接执行步 骤 dl。
所述短消息系统所属的网络为: 全球移动通信网 GSM、 通用无线分 组业务网 GPRS、 宽带码分多址 WCDMA、 码分多址 CDMA95网络或 CDMA2000 网絡。
由于本发明所述的方法在 MMSC 中增加可与短消息系统进行通讯 的接口协议模块, 实现 MMSC直接与短消息系统通讯, 因此在 PUSH 通知流程中可消除 WAPGW的参与, 减少 PUSH通知流程的中间环节, 消除发送多媒体消息对 WAPGW 的依赖, 并进一步消除 MMSC 和 WAPGW重发机制的不一致性。
本发明所述的短消息系统为可转发短消息的中间通讯设备, 短消息 系统可以为短消息中心, 也可以为短消息网关和短消息中心。
如果短消息系统为短消息中心, 则由于 MMSC直接与短消息中心 通讯, 減少了中间环节, 因此可提高多媒体消息的发送效率和成功率, 提高多媒体消息业务的服务质量, 并降低成本; 另外, 由于本发明所述 方法中 MMSC可直接利用接口协议与各种网络的短消息中心进行通讯, 因此提高了多媒体消息业务组网的灵活性。
如果短消息系统为短消息网关和短消息中心, 则由于短消息网关处 理短消息的效率和成功率比 WAPGW处理短消息的效率和成功率高,因 此, 也可以提高多媒体消息的发送效率和成功率。 附图简要说明 图 1为现有技术中多媒体消息的发送流程图;
图 2为当本发明所述的短消息系统为短消息中心时, 多媒体消息的 发送流程图;
图 3为当本发明所述的短消息系统为短消息网关和短消息中心时, 多媒体消息的发送流程图。 实施本发明的方式 下面结合附图和具体实施例进一步说明本发明的实施方法。
本发明的核心思想为: 在 PUSH通知流程中, 消除 WAPGW的 参与, 利用 MMSC直接与短消息系统通讯, 完成 PUSH通知的下发。 本发明的短消息系统为短消息中心, 或者为短消息网关和短消息中 心。
本发明所述方法在 MMSC中加入可与短消息系统进行通讯的接口 协议模块, 当短消息系统为短消息中心 SMSC时, 在 MMSC中加入可与 SMSC直接通讯的接口协议模块, 例如在 GSM网络中为 SMPP协议模块, 在其他网絡中可以为 UCP协议模块、 CIMD协议模块或其他协议模块; 当短消息系统为短消息网关和 SMSC时, 在 MMSC中加入可与短消息网 关直接通讯的短消息网关协议模块, 例如中国移动点对点协议(China Mobile Peer to Peer, CMPP )、 中国联通短消息网关接口协议( SGIP )或 其他同类协议模块。
由于多媒体消息在 GSM、 GPRS, WCDMA、 CDMA95、 CDMA2000 或其他网络中的发送过程较类似, 因此下面以多媒体消息在 GSM网络中 的发送过程为例说明本发明所述方法。
如图 2所示为当本发明所述的短消息系统为 SMSC时, 多媒体消息发 起方, 例如 MMS终端、 VASP或邮件服务器, 向接收方 MMS终端发送多 媒体消息的整个发送过程, 包括:
步骤 21、 多媒体消息的发起方将多媒体消息提交给 MMSC, 该多媒 体消息中包括接收方 MMS终端的地址信息, 例如手机号码;
步驟 22、 MMSC收到多媒体消息后, 启动 PUSH通知流程, 向接收 方 MMS终端下发 PUSH通知, 该 PUSH通知中包括接收方 MMS终端提取 多媒体消息所需的寻址信息、 发送方的标识、 多媒体消息主题和接收方
MMS终端地址信息等内容,所述寻址信息为 MMSC地址和所述多媒体消 息在 MMSC中的唯一标识, PUSH通知流程具体包括以下步驟:
步骤 2201、 MMSC使用与 SMSC进行通讯的接口协议, 例如 SMPP协 议, 将 PUSH通知封装成短消息, 并使用该接口协议向 SMSC发送提交消 息 submit— sm, 该提交消息 submit— sm中包括含有 PUSH通知的短消息,记 录执行本步骤的次数。
如果当前网络为其他网络, 则 MMSC与 SMSC之间的接口协议也可 以使用 UCP协议、 CIMD协议或其他同类协议, 本文中所涉及的 SMPP协 议都可用上述 UCP协议、 CIMD协议或其他同类协议代替。
步骤 2202、 SMSC收到提交消息 submit— sm后, 向 MMSC返回提交响 应 submit— sm— resp。
以下步骤 2203至步骤 2206为 SMSC向接收方 MMS终端下发短消息 的流程:
步骤 2203、 SMSC通过提交消息 submit— sm中 PUSH通知包含的接收 方 MMS终端地址信息确定接收方 MMS终端归属的位置寄存器 (HLR ) 地址, 并向该 HLR^_送路由请求消息 map— sri— for— sm— req , 并记录执行本 步骤的次数。
如果当前网络为 CDMA网络, 则路由请求消息为 SMSREQ消息。 步骤 2204、 HLR收到路由请求消息 map_sri— for— sm— req后, 向 SMSC 返回路由响应消息 map— sri— for— sm_resp , 所述的路由响应消息 map— sri—for— sm— resp中包括接收方 MMS终端的路由信息,即接收方 MMS 终端当前所在的 MSC地址。
如果当前网络为 CDMA网络, 则所述路由响应消息为 smsreq消息 , 如果当前网络为 GPRS和 WCDMA网络,则路由响应消息中包括的路由信 息为服务通用分组业务节点 (SGSN )地址。
步骤 2205、 SMSC读取路由响应消息 map— sri_for一 sm— resp中的路由信 息,根据该路由信息通过接收方 MSC向接收方 MMS终端发送短消息发送 请求消息 map—mt— ^vd_sm_req, 其中包含要发给接收方 MMS终端的含有 PUSH通知的短消息。 如果当前网络为 CDMA网络, 则所述的短消息发 送请求消息为 SMDPP消息。
步骤 2206、接收方 MMS通过接收方 MSC向 SMSC返回短消息发送响 应 消 息 map_mt_fwd_sm_resp 。 该 短 消 息 发 送 响 应 消 息 map— mt一 f d— smjresp包括 PUSH通知是否下发成功的信息。 SMSC在预定 的时间内判断是否收到 PUSH通知下发成功的短消息发送响应消息 map_mt_ wd_sm_resp , 如果是, 则执行下一步骤; 否则, SMSC根据内 部重发策略, 选择是否重发和重发的时间, 如果重发, 则判断执行步骤 2203的次数是否超过预定的次数, 如果超过预定次数, 则 SMSC认定 PUSH通知下发失败, 并执行下一步驟; 如果没有超过预定的次数, 则 SMSC采取重发策略, 返回步驟 2203。
另外, 如果当前网络为 CDMA网络, 则 MSC向 SMSC返回的响应消 息为 smdpp。
步骤 2207、 SMSC向 MMSC发送递送报告消息 deliver— sm, 该递送报 告消息 deliver_sm包括 PUSH通知是否下发成功的信息。
步骤 2208、 MMSC收到递送报告消息 deliver— sm后, 向 SMSC返回递 送报告响应 deliver— sm_resp。并才艮据递送报告消息的内容判断 PUSH通知 是否下发成功, 如果成功, 则结束 PUSH通知流程; 否则, MMSC根据 内部重发策略, 选择是否重发和重发的时间, 如果重发, 则判断执行步 骤 2201的次数是否超过预定的次数, 如果超过预定的次数, 则 MMSC认 定 PUSH通知下发失败, 结束该多媒体消息的发送流程, 认定该多媒体 消息发送失败, 并执行步驟 17; 如果没有超过预定的次数, 则 MMSC采 取重发策略, 返回步骤 2201。
以下的步驟 23至步骤 27为多媒体消息的提取流程:
步骤 23、 接收方 MMS终端收到 PUSH通知后, 根据自身的选择模式 进行处理: 如果接收方 MMS终端选择延时提取多媒体消息的情况下, 则 根据 PUSH通知信息中包含的提取多媒体消息的寻址信息, 通过通知响 应 MMl— notification.RES向 MMSC报告已收到 PUSH通知, 再执行步骤 24; 如果接收方 MMS终端选择立即提取多媒体消息的情况下, 则直接执 行步骤 24。
步骤 24、当多媒体消息提取时间到达时,接收方 MMS终端根据 PUSH 通知信息中包含的提取多媒体消息的寻址信息, 向 MMSC发送多媒体消 息提取请求 MMl— retrieve.REQ。
步骤 25、 MMSC通过多媒体消息提取响应 MMl_retrieve.RES向接收 方 MMS终端下发多媒体消息。
步骤 26、在延时提取的情况下,接收方 MMS终端通过多媒体消息确 认消息 MMl— acknowledgement.REQ向 MMSC返回多媒体消息的接收状 态 。 在立即提取的情况下 , 接收方终端通过通知响应 MMl— notification.RES消息向 MMSC返回多媒体消息的接收状态。
步骤 27、 如果发送方要求获知多媒体消息的发送状态, 则 MMSC向 发送方返回多媒体消息发送状态报告, 该发送状态报告包含接收方多媒 体消息的接收状态信息; 如果发送方没有要求获知多媒体消息的发送状 态, 则结束流程。
在 GSM、 GPRS、 WCDMA、 CDMA95、 CDMA2000或其他各种移 动网络和固定网络中, 均可采用本发明方法所述的组网方式, 即 MMSC 使用相应的接口协议直接与各种移动网络或固定网络的短消息系统进 行通讯, 从而完成多媒体消息的发送。 例如在 CDMA网络中, MMSC可 直接与 CDMA的短消息中心 MC连接, 完成多媒体消息的发送。
图 3所示为当本发明所述的短消息系统为短消息网关和 SMSC时, 多 媒体消息发起方向接收方 MMS终端发送多媒体消息的整个发送过程,该 过程与图 2所示的过程相似, 只是 MMSC与短消息系统间的交互过程稍 有不同, 以下只对 MMSC与短消息系统间的交互过程进行说明。
MMSC收到多媒体消息后, 启动 PUSH通知流程, 包括:
步骤 3201、 MMSC使用 MMSC与短消息网关之间的接口协议, 例如 CMPP,将 PUSH通知封装成含有 PUSH通知的消息,并使用 CMPP向短消 息网关发送该含有 PUSH通知的 PUSH信息消息 CMPP— SUBMIT, 并记录 执行本步骤的次数。
步骤 3202、短消息网关收到 CMPP— SUBMIT后,向 MMSC返回 PUSH 响应消息 CMPP一 SUBMIT— RESP。
步驟 3203、 短消息网关利用短消息网关与 SMSC之间的接口协议, 例如 SMPP, 将 PUSH通知封装成含有 PUSH通知的短消息, 并使用 SMPP 向 SMSC发送该含有 PUSH通知的提交消息 submit— sm, 并记录执行本步 骤的次数。 此处的接口协议也可以是 UCP、 CIMD或其他同类协议。
步驟 3204、 SMSC收到 submit— sm后, 向短消息网关返回提交响应 submit—sm— resp , 并执行步骤 2203。
接着执行步驟 2203到步骤 2206。 所述步骤 2203到步骤 2206的操作过 程请参见图 2的说明。 执行完步驟 2206后, 执行以下步骤:
步骤 3205、 SMSC向短消息网关发送递送报告消息 deliver— sm, 该 deliver— sm包括 PUSH通知是否下发成功的信息。
步骤 3206、 短消息网关收到 deliver— sm后, 向 SMSC返回 deliver_sm_resp , 并根据 deliver— sm的内容判断 PUSH通知是否下发成功, 如果成功, 则执行步骤 3207, 否则, 判断执行步骤 3203的次数是否超过 预定次数, 如果是, 则短消息网关认定 PUSH通知下发失败, 并执行步 骤 3207; 否则, 短消息网关采取重发策略, 返回步骤 3203。
步骤 3207、 短消 息 网 关向 MMSC发送结果通知消 息
CMPP— DELIVER,该 CMPP— DELIVER包括 PUSH通知是否下发成功的信 白
步骤 3208、 MMSC收到 CMPP— DELIVERS , 向短消息网关返回结果 通知响应 CMPP_DELIVER_RESP, 并根据 CMPP— DELIVER的内容判断 PUSH通知是否下发成功, 如果成功, 则结束 PUSH通知流程; 否则, 判 断执行步骤 3201的次数是否超过预定次数,如果是,则 MMSC认定 PUSH 通知下发失败, 结束该多媒体消息的发送流程; 否则, MMSC采取重发 策略, 返回步骤 3201。
多媒体消息的提取流程为上述的步骤 23至步骤 27。
以上所述, 仅为本发明较佳的具体实施方式, 但本发明的保护范围 并不局限于此, 任何熟悉该技术的人在本发明所揭露的技术范围内, 可 轻易想到的变化或替换, 都应涵盖在本发明的保护范围之内。

Claims

权利要求书
1、 一种多媒体消息的发送方法, 其特征在于, 所述的方法在多媒 体消息业务中心 MMSC 中加入可与短消息系统进行通讯的接口协议模 块, 并包括:
a、 由多媒体消息的发起方向 MMSC提交包括多媒体接收方地址信 息的多媒体消息; .
b、 MMSC启动 PUSH通知流程, 使用可与短消息系统进行通讯的 接口协议向短消息系统发送 PUSH通知;
c、 短消息系统向多媒体消息接收方的归属位置寄存器 HLR获取多 媒体消息接收方的路由信息, 并根据该路由信息向多媒体消息接收方下 发所述 PUSH通知;
d、 多媒体消息接收方启动多媒体消息提取流程, 根据 PUSH通知 中多媒体消息寻址信息从 MMSC提取多媒体消息。
2、 如权利要求 1 所述的方法, 其特征在于, 所述的短消息系统为 短消息中心, 或者为短消息网关和短消息中心。
3、 如权利要求 2所述的方法, 其特征在于, 所述短消息系统为短 消息中心, 且所述步骤 b中 MMSC使用可与短消息中心进行通讯的接 口协议向短消息中心发送 PUSH通知的方法为:
M、 MMSC使用可与短消息中心进行通讯的接口协议将 PUSH通知 封装成含有 PUSH通知的短消息, 并使用所述接口协议向短消息中心发 送该含有 PUSH通知的短消息。
4、 如权利要求 3所述的方法, 其特征在于, 所述可与短消息中心进 行通讯的接口协议为: 短消息点对点协议 SMPP、 .用户数据报协议 UCP、 计算机接口信息发送协议 CIMD。
5、 如权利要求 2所述的方法, 其特征在于, 所述短消息系统为短消 息网关和短消息中心 , 且所述步骤 b†MMSC使用可与短消息系统进行 通讯的接口协议向短消息系统发送 PUSH通知的方法为:
bl'、 MMSC使用 MMSC与短消息网关之间的接口协议将 PUSH通知 封装成含有 PUSH通知的消息, 并使用该 MMSC与短消息网关之间的接 口协议向短消息网关发送该含有 PUSH通知的消息;
b2'、 短消息网关利用短消息网关与短消息中心之间的接口协议将 PUSH通知封装成含有 PUSH通知的短消息, 并使用该短消息网关与短消 息中心之间的接口协议向短消息中心发送该含有 PUSH通知的短消息。
6、 如权利要求 5所述的方法, 其特征在于, 所述 MMSC与短消息网 关之间的接口协议为中国移动点对点协议 CMPP或中国联通短消息网关 接口协议 SGIP,所述短消息网关与短消息中心之间的接口协议为 SMPP、 UCP或 CIMD。
7、如权利要求 2所述的方法, 其特征在于, 所述步骤 c中短消息系统 向多媒体消息接收方的 HLR获取多媒体消息接收方的路由信息的方法 为 ··
cl、 短消息中心通过 PUSH通知中的多媒体消息接收方地址信息查 找到多媒体消息接收方归属 HLR, 并向该 HLR发送路由请求消息;
c2、 HLR收到路由请求消息后, 向短消息中心返回路由响应消息, 该路由响应消息中包括多媒体消息接收方的路由信息, 短消息中心收到 路由响应消息后, 获取多媒体消息接收方的路由信息。
8、 如权利要求 2所述的方法, 其特征在于, 所述短消息系统为短消 息中心, 且在所述步驟 c之后, 还包括:
c3、 多媒体消息接收方向短消息中心返回短消息发送响应消息, 该 短消息发 i响应消息中包括 PUSH通知是否下发成功的信息, 短消息中 心在预定的时间内判断是否收到含有 PUSH通知下发成功信息的短消息 发送响应消息, 如果是, 则执行 c4; 否则, 判断执行步骤 c的次数是否超 过预定次数, 如果是, 则短消息中心认定 PUSH通知下发失败, 并执行 步驟 c4; 否则, 短消息中心采取重发策略, 返回步骤 c;
c4、 短消息中心向 MMSC发送递送报告消息, 该递送报告消息包括 PUSH通知是否下发成功的信息;
c5、 MMSC收到递送报告消息,根据递送报告消息的内容判断 PUSH 通知是否下发成功, 如果成功, 则结束 PUSH通知流程; 否则, 判断执 行步骤 b的次数是否超过预定次数, 如果是, 则 MMSC认定 PUSH通知下 发失败, 结束该多媒体消息的发送流程; 否则, MMSC采取重发策略, 返回步骤 。
9、 如权利要求 5所述的方法, 其特征在于, 在所述步驟 c之后, 还包 括:
c3'、 多媒体消息接收方向短消息中心返回短消息发送响应消息, 该 短消息发送响应消息中包括 PUSH通知是否下发成功的信息, 短消息中 心在预定的时间内判断是否收到含有 PUSH通知下发成功信息的短消息 发送响应消息, 如果是, 则执行 c4'; 否则, 判断执行步骤 c的次数是否 超过预定次数, 如果是, 则短消息中心认定 PUSH通知下发失败, 并执 行步骤 c4'; 否则, 短消息中心采取重发策略, 返回步骤 c;
c4'、 短消息中心向短消息网关发送递送报告消息, 该递送报告消息 包括 PUSH通知是否下发成功的信息;
c5'、 短消息网关收到递送报告消息, 根据递送报告消息的内容判断 PUSH通知是否下发成功, 如果成功, 则执行步骤 c6', 否则, 判断执行 步骤 b2'的次数是否超过预定次数, 如果是, 则短消息网关认定 PUSH通 知下发失败, 并执行步骤 c6'; 否则, 短消息网关采取重发策略, 返回步 骤 b2';
c6'、 短消息网关向 MMSC发送结果通知消息, 该结果通知消息包括 PUSH通知是否下发成功的信息;
c7'、 MMSC收到结果通知消息,才艮据结果通知消息的内容判断 PUSH 通知是否下发成功, 如果成功, 则结束 PUSH通知流程; 否则, 判断执 行步骤 bl'的次数是否超过预定次数, 如果是, 则 MMSC认定 PUSH通知 下发失败, 结束该多媒体消息的发送流程; 否则, MMSC采取重发策略, 返回步錄 bl'。
10、如权利要求 1所述的方法, 其特征在于, 所述的步骤 d具体包括: dl、 多媒体消息接收方根据 PUSH通知信息中包含的提取多媒体消 息的寻址信息, 向 MMSC发送多媒体消息提取请求;
d2、 MMSC通过多媒体消息提取响应向多媒体消息接收方下发多媒 体消息;
d3、 多媒体消息接收方向 MMSC返回多媒体消息的接收状态。
11、 如权利要求 10所述的方法, 其特征在于, 在所述步骤 dl之前, 进一步包括:
多媒体消息接收方选择提 莫式, 如果多媒体消息接收方选择延时 提取多媒体消息, 则根据所述 PUSH通知信息中包含的提取多媒体消息 的寻址信息, 通过通知响应向 MMSC报告已收到 PUSH通知, 再执行步 骤 dl; 如果多媒体消息接收方选择立即提取多媒体消息, 则直接执行步 驟 dl。
12、 如权利要求 1所述的方法, 其特征在于, 所述短消息系统所属 的网络为: 全球移动通信网 GSM、 通用无线分组业务网 GPRS、 宽带码 分多址 WCDMA、 码分多址 CDMA95网络或 CDMA2000网络。
PCT/CN2005/000424 2004-05-12 2005-03-31 Procede de transmission de messages multimedia WO2005109793A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2007511834A JP4628420B2 (ja) 2004-05-12 2005-03-31 マルチメディアメッセージの配信方法及びシステム、並びにマルチメディアメッセージサービスセンター
BRPI0510018-6A BRPI0510018A (pt) 2004-05-12 2005-03-31 método e sistema para transmissão de mensagens multimìdia e centro de serviço de mensagem multimìdia
EP05741909A EP1747650A4 (en) 2004-05-12 2005-03-31 METHOD FOR TRANSMITTING MULTIMEDIA MESSAGES
US11/558,612 US7917161B2 (en) 2004-05-12 2006-11-10 Method and system for delivering multimedia messages and multimedia message service center

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200410034765.3 2004-05-12
CNB2004100347653A CN100362873C (zh) 2004-05-12 2004-05-12 一种多媒体消息的发送方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/558,612 Continuation US7917161B2 (en) 2004-05-12 2006-11-10 Method and system for delivering multimedia messages and multimedia message service center

Publications (1)

Publication Number Publication Date
WO2005109793A1 true WO2005109793A1 (fr) 2005-11-17

Family

ID=35320572

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/000424 WO2005109793A1 (fr) 2004-05-12 2005-03-31 Procede de transmission de messages multimedia

Country Status (7)

Country Link
US (1) US7917161B2 (zh)
EP (1) EP1747650A4 (zh)
JP (1) JP4628420B2 (zh)
KR (1) KR100853700B1 (zh)
CN (1) CN100362873C (zh)
BR (1) BRPI0510018A (zh)
WO (1) WO2005109793A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100805056B1 (ko) 2005-12-28 2008-02-20 주식회사 케이티프리텔 멀티미디어 데이터의 재전송을 위한 장치, 방법 및 시스템

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060451B (zh) * 2006-04-18 2012-04-25 华为技术有限公司 多媒体消息传送方法与系统
JP4482545B2 (ja) * 2006-09-20 2010-06-16 日本電信電話株式会社 情報配信装置及び情報配信方法
CN101202944B (zh) * 2006-12-12 2011-01-19 中兴通讯股份有限公司 一种网间传输多媒体消息的系统
US20090239505A1 (en) * 2007-01-30 2009-09-24 Ramakrishnan Thyagarajapuram S Systems and methods for distributing messages to mobile devices
JP5295128B2 (ja) * 2007-01-30 2013-09-18 バブル モーション ピーティーイー,リミテッド モバイル機器にメッセージを配信するためのシステムおよび方法。
CN101150757B (zh) * 2007-06-13 2010-11-03 中兴通讯股份有限公司 一种多媒体消息内容适配的方法和系统
CN101355719B (zh) * 2007-07-26 2011-04-20 中国移动通信集团公司 多媒体消息的处理方法、装置及系统
CN101094455B (zh) * 2007-08-04 2012-05-23 中兴通讯股份有限公司 一种实现移动网络中短消息实时传输的方法
CN101110797B (zh) * 2007-08-29 2013-06-05 中兴通讯股份有限公司 一种多媒体消息业务实现系统及其方法
CN101163276B (zh) * 2007-11-26 2011-02-02 华为技术有限公司 一种下发彩信的方法和系统、及彩信中心
CN101516067A (zh) * 2008-02-21 2009-08-26 中国移动通信集团公司 多媒体消息存储地址发送系统及方法
CN101594582B (zh) * 2008-05-28 2012-02-01 中国移动通信集团公司 消息发送方法、设备及系统
WO2009146442A1 (en) * 2008-05-29 2009-12-03 Bubble Motion Pte., Ltd. Systems, methods and software applications for mobile device menu modification
CN101330664B (zh) * 2008-07-21 2012-07-25 华为技术有限公司 多媒体业务的实现方法、系统和装置
US9135363B2 (en) 2009-06-09 2015-09-15 Gvoto (Hong Kong) Ltd. Methods and systems for automatic content retrieval and organization
US20110082572A1 (en) * 2009-10-06 2011-04-07 Ramakrishnan Thyagarajapuram S Distributing Media By Subscription
CN102045657A (zh) * 2009-10-21 2011-05-04 中国移动通信集团公司 一种多媒体业务承载方法、终端和系统
CN101815265B (zh) * 2010-02-10 2012-09-05 播思通讯技术(北京)有限公司 微技信息传输方法及系统
CN101895838A (zh) * 2010-07-15 2010-11-24 中兴通讯股份有限公司 一种多媒体消息业务中下发消息的方法及系统
CN102739604B (zh) * 2011-03-31 2016-09-28 中兴通讯股份有限公司 媒体消息安全传输的方法和系统
US20140090005A1 (en) * 2011-05-19 2014-03-27 Nippon Hoso Kyokai Integrated broadcasting communications receiver
WO2013052964A2 (en) * 2011-10-07 2013-04-11 Interop Technologies, Llc Non-ims rich communication suite
CN102984669B (zh) * 2012-11-27 2018-06-05 南京工业大学 一种移动通信网络中多媒体消息自动回复的方法
CN103945347A (zh) * 2013-01-23 2014-07-23 苏州市伏泰信息科技有限公司 基于lbs的环卫作业短信调度系统
CN104767650A (zh) * 2014-01-03 2015-07-08 中国移动通信集团广东有限公司 一种消息网络延迟测算方法及装置
US11146923B1 (en) * 2020-04-01 2021-10-12 Sprint Spectrum L.P. Method and system to facilitate media-content delivery

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999066746A2 (en) 1998-06-15 1999-12-23 Nokia Networks Oy A method for delivering messages in a wireless communications system using the same protocol for all types of messages
WO2002056615A1 (en) * 2000-12-20 2002-07-18 Nokia Corporation Arrangement for implementing transmission of multimedia messages
WO2003026138A2 (en) * 2001-09-14 2003-03-27 Nokia Corporation System and method for wireless multimedia communication
WO2003043286A2 (en) * 2001-11-13 2003-05-22 International Business Machines Corporation Wireless messaging services using publish/subscribe systems

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5822700A (en) * 1996-04-18 1998-10-13 Telefonaktiebolaget L M Ericsson Flow control of short message service messages in a cellular telephone network
US5878397A (en) * 1996-07-10 1999-03-02 Telefonaktiebolaget L M Ericsson (Publ) Method for transporting short messages in a wireless telecommunications system
FI109511B (fi) * 1997-06-03 2002-08-15 Nokia Corp Lyhytsanomien reititys
JP3492265B2 (ja) * 1999-10-29 2004-02-03 ボーダフォン株式会社 デジタル無線電話によるメッセージ通信システム
US6947738B2 (en) * 2001-01-18 2005-09-20 Telefonaktiebolaget Lm Ericsson (Publ) Multimedia messaging service routing system and method
DE10117895A1 (de) * 2001-04-10 2002-10-17 Siemens Ag Benachrichtigung im Multimedia Messaging Service (MMS)
JP4213358B2 (ja) * 2001-04-12 2009-01-21 株式会社エヌ・ティ・ティ・ドコモ マルチキャスト情報配信制御方法及びシステム、並びにサーバ及びクライアント
EP1555835A3 (en) * 2001-12-21 2007-01-10 Orange Personal Communications Services Ltd. Call processing in mobile telecommunications networks
US6795541B2 (en) * 2002-03-11 2004-09-21 Ericsson Inc. Method, apparatus and system for completing a call when a called party has not answered the call
EP1361712B1 (en) * 2002-05-07 2006-03-29 Sony Ericsson Mobile Communications AB Method for communicating messages to an electronic communication equipment
US20050038892A1 (en) * 2003-08-13 2005-02-17 Sun Microsystems, Inc. Method for wireless communication and apparatus for conducting the same
US7181538B2 (en) * 2003-11-14 2007-02-20 Sybase 365, Inc. System and method for providing configurable, dynamic multimedia message service pre-transcoding
FI20031871A0 (fi) * 2003-12-19 2003-12-19 Nokia Corp Multimediasanomapalvelujärjestelmä ja menetelmä
US7649895B2 (en) * 2003-12-30 2010-01-19 Airwide Solutions Inc. Apparatus and method for routing multimedia messages between a user agent and multiple multimedia message service centers
US20050278749A1 (en) * 2004-05-14 2005-12-15 Ewert Joerg C System and method for automatic modification of multimedia messages

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999066746A2 (en) 1998-06-15 1999-12-23 Nokia Networks Oy A method for delivering messages in a wireless communications system using the same protocol for all types of messages
WO2002056615A1 (en) * 2000-12-20 2002-07-18 Nokia Corporation Arrangement for implementing transmission of multimedia messages
WO2003026138A2 (en) * 2001-09-14 2003-03-27 Nokia Corporation System and method for wireless multimedia communication
WO2003043286A2 (en) * 2001-11-13 2003-05-22 International Business Machines Corporation Wireless messaging services using publish/subscribe systems

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
RALPH D.; GRAHAM P.: "3 A Standard-based Approach", MMS TECHNOLOGIES, USAGE AND BUSINESS MODELS, pages 63 - 85
See also references of EP1747650A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100805056B1 (ko) 2005-12-28 2008-02-20 주식회사 케이티프리텔 멀티미디어 데이터의 재전송을 위한 장치, 방법 및 시스템

Also Published As

Publication number Publication date
JP2007537632A (ja) 2007-12-20
US7917161B2 (en) 2011-03-29
CN1697531A (zh) 2005-11-16
JP4628420B2 (ja) 2011-02-09
BRPI0510018A (pt) 2007-09-25
KR20070011589A (ko) 2007-01-24
EP1747650A4 (en) 2007-06-13
CN100362873C (zh) 2008-01-16
KR100853700B1 (ko) 2008-08-25
US20070149224A1 (en) 2007-06-28
EP1747650A1 (en) 2007-01-31

Similar Documents

Publication Publication Date Title
WO2005109793A1 (fr) Procede de transmission de messages multimedia
US6928290B2 (en) Method and apparatus for network-assisted automatic confirmation of short message service delivery
JP4448028B2 (ja) 無線通信システムにおいてsmsメッセージに対する報告を伝達するための方法及び装置
KR100492959B1 (ko) 공중 이동통신망과 연동되는 사설 무선망의 단문 메시지서비스 서버 및 방법
WO2006005252A1 (fr) Procede de traitement pour notification de retransmission dans un service de messagerie multimedia
CN100512314C (zh) 一种优化Push通告消息的方法
CA2568599A1 (en) Reporting terminal capabilities for supporting short message service
WO2005114912A1 (en) Message routing method and system
WO2007025432A1 (fr) Procede destine a realiser un service de transfert d'informations, systeme et terminal correspondantsprocede fournissant un service de transfert d'informations, systeme et terminal connexes
WO2008110105A1 (fr) Procédé et dispositif d'envoi d'un message, équipement de centrale de messages
WO2012062070A1 (zh) 反馈接收端状态的方法、系统和服务器
WO2012062051A1 (zh) 一种下发多媒体消息的方法和系统
WO2010009666A1 (zh) 多媒体业务的实现方法、系统和装置
WO2007033552A1 (fr) Procede pour traiter le message dans le service de message multimedia et systeme y afferant
WO2006099812A1 (fr) Procédé de transmission de message
AU2007202041A1 (en) Method and apparatus for conveying reports for SMS messages in wireless communication systems

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 BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG 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 NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY 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): BW GH GM KE LS MW MZ NA 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 IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

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: 11558612

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2007511834

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

WWE Wipo information: entry into national phase

Ref document number: 2005741909

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 1020067025929

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 1020067025929

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 2005741909

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 11558612

Country of ref document: US

ENP Entry into the national phase

Ref document number: PI0510018

Country of ref document: BR