WO2009115033A1 - 多媒体消息业务的实现方法、系统及相关设备 - Google Patents
多媒体消息业务的实现方法、系统及相关设备 Download PDFInfo
- Publication number
- WO2009115033A1 WO2009115033A1 PCT/CN2009/070836 CN2009070836W WO2009115033A1 WO 2009115033 A1 WO2009115033 A1 WO 2009115033A1 CN 2009070836 W CN2009070836 W CN 2009070836W WO 2009115033 A1 WO2009115033 A1 WO 2009115033A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- message
- request
- user
- ordering
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a method, system, and related device for implementing a multimedia message service.
- Multimedia Messaging Service is a further development of Short Message Service (SMS) and Enhanced Message Service (EMS), providing a complete end-to-end for personal multimedia mobile communication services. solution.
- SMS Short Message Service
- EMS Enhanced Message Service
- multimedia messages include images, audio, video, and data.
- multimedia messaging services cover end-to-end, terminal-to-application, and application-to-terminal multimedia messaging communications. It not only realizes the information transfer between terminals, terminals and applications, but also realizes the diversity of content, including various combinations of pictures, voice, images, data and text.
- MMS can generate more colorful content business applications under the interaction of mobile users and Internet content providers.
- MMSC Multimedia Messaging Service Center
- operators In practical applications, in addition to using the Multimedia Messaging Service Center (MMSC) to complete the storage and forwarding of multimedia messages, operators generally deploy some value-added services on the MMSC. For example, the operator can provide the user with a signature file service. After the MMSC receives a message submitted by the user, the MMSC automatically adds a pre-set signature to the receiver at the end of the message content, and the carrier can also send the message to the user. The calling receipt service is provided. After the message submitted by the user is delivered, the MMSC notifies the sending result of the message by using a short message or the like.
- MMSC Multimedia Messaging Service Center
- the MMSC itself is a telecommunication network device that requires high reliability, and directly implements the value-added service in the MMSC, which increases on the one hand.
- the complexity of MMSC leads to the difficulty in the development of MMSC, which affects the speed of the introduction of value-added services.
- the performance of MMSC is degraded. This increases the operator's overall operating cost (TCO).
- the technical problem to be solved by the embodiments of the present invention is to provide a method, a system, and a related device for implementing a multimedia message service, which can eliminate the burden that the value-added service directly implements on the MMSC to the MMSC.
- An embodiment of the present invention provides a method for implementing a multimedia message service, including:
- the multimedia message service center receives the message submission request
- the multimedia message service center searches for the service trigger point that the message service control function device subscribes to the user in the existing message subscription information according to the user identifier carried in the message submission request;
- the multimedia message service center initiates a service processing request to the message service control function device, where the service processing request includes the user identifier, so that the message service control function device is configured according to the
- the user identifier carried in the service processing request is used to search for the service subscribed by the user in the existing service subscription information, and perform corresponding service processing.
- the embodiment of the invention further provides a method for implementing a multimedia message service, including:
- the embodiment of the invention further provides a message service control function device, including:
- a service processing request receiving unit configured to receive a service processing request
- a service search unit configured to search for the service ordered by the user in the service order information holding unit according to the user identifier carried in the service processing request
- the service processing unit is configured to perform corresponding service processing according to the service found by the service search unit.
- the embodiment of the invention further provides a multimedia message service center, including:
- a message submission request receiving unit configured to receive a message submission request submitted by the user agent, and a service trigger point searching unit, configured to: according to the user identifier carried in the message submission request, The message ordering information is used to find a service trigger point that the message service control function device subscribes to; the service processing request sending unit is configured to initiate a service processing request to the message service control function device when the service trigger point is reached .
- An embodiment of the present invention further provides a system for implementing a multimedia message service, including: a multimedia message service center, and a message service control device;
- the multimedia message service center is configured to receive a message submission request submitted by the user agent, and search for a service trigger point that the message service control function device subscribes to the user in the existing message subscription information according to the user identifier carried in the message submission request.
- a service processing request is initiated to the message service control function device;
- the message service control function device receives the service processing request initiated by the service request sending unit; searches for the service subscribed by the user in the existing service order information according to the user identifier carried in the service processing request; The service that the unit finds, and performs corresponding business processing.
- the embodiment of the present invention implements multimedia through message interaction between the MMSC and the Messaging Service Control Function (MSCF).
- MSCF Messaging Service Control Function
- FIG. 1 is a flowchart of a method for implementing a multimedia message service according to an embodiment of the present invention
- FIG. 2 is a flowchart of a method for implementing a signature file service according to an embodiment of the present invention
- FIG. 3 is a flowchart of a method for implementing a calling return service according to an embodiment of the present invention
- FIG. 4 is a flowchart of a method for implementing an advertisement volunteer service according to an embodiment of the present invention
- FIG. 5 is a schematic structural diagram of a message service control function device according to an embodiment of the present invention.
- FIG. 6 is a schematic structural diagram of a system for implementing a multimedia message service according to an embodiment of the present invention.
- the MM10 interface is defined in the Third Generation Partnership Project (3GPP) specification 24.140, introducing the concept of the Messaging Service Control Function (MSCF). The interaction process between MMSC and MSCF is clarified.
- 3GPP Third Generation Partnership Project
- MSCF Messaging Service Control Function
- the embodiment of the present invention extends the existing MM10 interface.
- the message included in the extended MM10 interface provided by the embodiment of the present invention indicates the newly extended message:
- the MM10-Subscribe.REQ message is initiated by the MSCF and is used to subscribe to the message from the MMSC.
- MM10 The Interrogation.REQ/.RES message is a message obtained by extending several fields of the MM1 O Interogation.REQ/.RES message specified by the existing 3GPP standard protocol.
- MM1 O Interrogation.REQ is initiated by the MMSC for submitting the user. The message is triggered to the MSCF for corresponding service processing.
- the transaction identifier must have a transaction ID, which is used to identify the corresponding MM10_Subscribe.RES
- the mandatory MMSC forwards the service trigger point of the message to the MSCF.
- Trigger Point Set 4 trigger points for the sender user:
- TPA1 Transmitter Service Trigger Point 1
- TPA2 Sender Service Trigger Point 2
- TPA3 Sender Service Trigger Point 3
- TPA4 Sender Service Trigger Point 4
- Receiver service trigger point 1 (TPB1): Before the MMSC sends a push notification to the receiver, the code is 0xF4.
- the receiver service trigger point 2 (TPB2): The MMSC has successfully sent a push to the receiver. Notification, coded as 0xF5
- Receiver service trigger point 3 (TPB3): MMSC has completed the message delivery process, coded as 0xF6
- the message body identifier (Need can optionally carry the message Body in the message forwarded by the MMSC to the MSCF).
- Waiting for a response identifier (Wait optional MMSC needs to wait for a response after forwarding the message to the MSCF. for Response)
- Transaction ID The required transaction ID, which is used to identify the (Transaction ID) correspondence with MM10_Subscribe.REQ.
- Transaction ID The required transaction ID is used to identify the correspondence with MM10 Interrogation.RES (Transaction ID).
- Trigger event Trigger must trigger the business trigger point for this message.
- Message ID The ID of the Message Prerequisite Multimedia Message (MM).
- Original ID of the message Optional The original ID of the message. If the message is forwarded from another MMSC (the Originator Message is forwarded, the message needs to be placed in the ID of the original MMSC) in this field to be carried to the MSCF.
- Receiver Address Required Address of the recipient of the message There may be multiple addresses. (Recipient(s)
- Sender address (Sender must address sender's address
- Sender presentation ID Optional Sender ID presented to the recipient
- Presentation Content type (Content content type of Content must message content.
- the message class is another J 1 (the category of the Message optional message (for example, personal business, advertising business, and letter class).
- Expiration and time (Date must-have user agent recently processed (ie, submitted or forwarded) MM's and time) time and date.
- the earliest delivery time is optional.
- the earliest delivery time is optional. The earliest delivery time.
- MMSC Whether the sender's MMS center is optional MMSC delivers 4 notification request. For messages that are forwarded from other MMSCs that need to deliver a report, this field indicates whether the sender MMSC requests MM (Europeator R/S delivery report.
- Forward Counter Optional A counter that indicates the number of times a message has been forwarded.
- the originator address is optional. In the case of forwarding, this information device contains the address of one or more MMS user agents that have (ie, forwarded or submitted) messages that precede their The address is included in the MMS User Agent in the "Sender" address information device. Should indicate the place Provide the order of the addresses. The address of the originating party MMS User Agent shall be indicated.
- the content contains a watermark (DEM optional indicates that the content of the MM contains digital iceprint protection information
- Sender System Address Optional The address of the sender MMSC. This field is required for messages that are forwarded from other MMSCs ( Originator-System-).
- Delivery status (Send optional message delivery status, valid only at ⁇ 4, ⁇ 3 points.
- Transaction ID must-have transaction ID for identification and business processing requests Correspondence between (Transaction ID) (MM10 Interrogation.REQ).
- Processing results including: accept, reject, modify messages, normal status
- Receiver Address Required Address of the recipient of the message There may be multiple addresses.
- Message category Optional Category of message for example, personal business, advertising business, and information industry
- the earliest delivery time is optional.
- the earliest delivery time is optional. The earliest delivery time.
- Delivery report optional request to deliver the report
- the forwarding counter is optionally a counter indicating the number of times the message has been forwarded.
- Content category (Content optional MM content included in the media category another j i
- Table 5 Service Processing Response Message MM10 - Interrogation.
- RES defines the MM10 interface provided by the embodiment of the present invention in detail.
- the technician can redefine the names of the extended fields listed in the table as needed.
- the name of the present invention is only a clearer description of the embodiment, and should not be construed as limiting the embodiment of the invention.
- a method for implementing a multimedia message service includes: Step 101: A user agent submits a service subscription request carrying service subscription information to an MSCF; wherein the service subscription information can be used for the MSCF
- the identity of the subscription service user is specified, and the type of the service is ordered. Therefore, the service subscription information may include: a user identifier, a service type identifier.
- the user identifier of the subscription service may be the mobile phone number of the user, and, due to the variety of multimedia message services, including, for example, a signature file service, a calling receipt service, and an advertising volunteer service, etc., the service type identifier Used to identify which service the subscription order is for.
- the service type identifier may be predefined as 00, indicating that the subscription request is a signature file service subscription request; the service type identifier is 01, indicating that the request is a caller receipt service subscription request; and the service type identifier is 11, indicating that the request is an advertisement. Volunteer business ordering request.
- the service subscription information When the subscription request is a signature service subscription request, the service subscription information further carries: a signature file set by the user.
- Step 102 The MSCF saves the service subscription information, and sends a message subscription request (MM10-Subscribe.REQ) carrying the message subscription information to the MMSC.
- MM10-Subscribe.REQ message subscription request
- the message subscription information may include: a user identifier and a service trigger point, configured to indicate to the MMSC that after the MMSC receives the message submitted by the user identifier, the MMSC shall send a service request processing to the MSCF, and indicate that the MMSC should send a service request to the MSCF.
- Processed business trigger point Step 103: The MMSC saves the message subscription information, and returns a message subscription response message (MM10 Subscribe.REQ) to the MSCF.
- the above describes the implementation process of the user to subscribe to the multimedia message service.
- the following describes the process of implementing the multimedia message service subscribed by the user, including:
- Step 104 The sender user agent (Europeator UA) submits a message submission request
- Step 105 The MMSC searches for the service trigger point that the MSCF subscribes to for the user according to the user identifier carried in the message submission request. When the service trigger point is reached, the MMSC sends a service processing request to the MSCF. (MM10—Interrogation.REQ );
- Step 106 The MSCF searches for the service subscribed by the user in the stored service subscription information according to the user identifier carried in the service processing request, performs corresponding service processing, and returns a service processing response message (MMlO Interrogation.RES) to MMSC.
- MMlO Interrogation.RES a service processing response message
- the foregoing is a method for implementing a multimedia message service according to an embodiment of the present invention.
- the foregoing implementation process shows that the message exchange between the MMSC and the MSCF implements the processing of the multimedia message service, and eliminates the direct operation in the MMSC.
- the service processing imposes a burden on the MMSC, and the MMSC only sends the MSCF order message to the MSCF for corresponding service processing, which avoids the MMSC triggering every message sent by the user to the MSCF, which causes the MSCF pressure to be too large.
- the so-called signature file service means For each message (multimedia message or plain text message) submitted by the user who subscribes to the signature file service, the system can automatically add the signature set by the sender at the end of the message content (message body), and A message with a signature added is sent to the recipient.
- a method for implementing a signature file service includes: Step 201: A user agent submits a signature file service subscription request to an MSCF;
- the service subscription information may include: a user identifier, a service type identifier, and a signature file.
- the service triggering point in the message ordering information may be a TPA1 point or a TPA2 point, and the message ordering information may include: a message body identifier and a wait for response identifier,
- the MMSC indicates that the message body in the message submission request (MM1 - Submit.REQ) needs to be carried when sending the service processing request, and waits for the MSCF to respond;
- the Subscriber User (Subscriber) field in the Message Ordering Request (MM10-Subscribe.REQ) message is used to carry the user identifier
- the Trigger Point field is used to carry the service trigger point
- the Need Body field and the Wait for Response field are used.
- the MMSC is indicated to need to carry the message body when sending the service processing request, and waits for the MSCF to respond.
- Step 203 The MMSC saves the message subscription information carried in the message subscription request (MM10_Subscription.REQ), and returns a message order response (MM10_Subscribe.RES) message to the MSCF.
- MM10_Subscription.REQ message subscription information carried in the message subscription request
- MM10_Subscribe.RES message order response
- the above describes the implementation process of the user ordering the signature file service.
- the following describes the process of implementing the signature file service subscribed by the user.
- the method includes:
- Step 204 The sender user agent submits a message submission request (MM1 - Submit.REQ) message to the MMSC;
- the message submission request (MM1 - Submit.REQ) carries the sender identifier, the receiver identifier, and the message body;
- Step 205 The MMSC finds, according to the sender identifier of the message submission request (MM1 - Submit.REQ) message, the service trigger point that the MSCF subscribes to the user in the existing message subscription information is a TPA2 point, and the MMSC sends the message.
- the party user agent returns a message submission response (MMl Submit.RES) message;
- Step 206 The MMSC reaches the TPA2 point, and the MMSC sends a service processing request (MM1 O Interrogation.REQ) to the MSCF, and waits for the response of the MSCF.
- MM1 O Interrogation.REQ MM1 O Interrogation.REQ
- the service processing request (MM10O Interrogation.REQ) message may include a sender address field, a content type field, and a content field, where the content field is used to carry the message body;
- MM10 - Interrogation.RES business process response
- the MSCF returns the message body of the added signature file to the MMSC in the content field of the service processing response (MM10_Interrogation.RES) message, and processes the process status of the message through the service processing (MM10-Interrogation.RES) message.
- the field indicates to the MMSC that the MMSC needs to modify the message.
- the signature file service is implemented after the above steps are performed, but in order to send the message of adding the signature file to the receiver user, the foregoing method may further include:
- Step 208 The MMSC saves the message body of the added signature file according to the indication of the Process Status field, and sends a notification (MM1_Notification.REQ) message to the receiver user agent.
- Step 209 The receiving user agent returns a notification response (MM1 - Notification. RES) message;
- Step 210 The receiving user agent sends a message obtaining request (MM1 - retrieve.REQ);
- Step 212 The Recipient UA sends a Get Successful Acknowledgement (MMl Acknowledge.REQ) message to the MMSC.
- MMl Acknowledge.REQ Get Successful Acknowledgement
- the MMSC further includes:
- Step 213 The MMSC returns a delivery request to the sender user agent.
- Step 214 The sender user agent returns a delivery response (MM1 - DeliveryReport.RES) message to the MMSC.
- the foregoing describes an implementation process of the signature file service provided by the embodiment of the present invention when the service trigger point is the TPA2 point.
- the second implementation process when the service trigger point is the TPA2 point is that the MMSC may first return a message submission response (MM1_Submit.RES) message to the sender user agent in step 205, and then look up the MSCF to subscribe to the user.
- the service trigger point does not affect the implementation of the embodiment of the present invention.
- the implementation process is basically the same as the TPA2 point.
- the MMSC sends a service processing request to the MSCF before returning the message submission response (MM1_Submit.RES) message to the sender user agent.
- the so-called calling receipt service refers to each message submitted by the sender user of the order receipt service, and the system notifies the sending status of the sender message in the form of a short message.
- a method for implementing a callback service is provided according to an embodiment of the present invention, where the method includes:
- Step 301 The user submits a call forwarding service order request for submitting the service order information to the MSCF;
- the service subscription information may include: a user identifier and a service type identifier;
- Step 302 The MSCF saves the service subscription information, and sends a message subscription request (MM10-Subscribe.REQ) carrying the message subscription information to the MMSC.
- MM10-Subscribe.REQ message subscription request
- the service triggering point in the message ordering information may be: a TPA3 and a TPA4 service triggering point, or may be any one of the TPA3 and the TPA4, and the message processing body does not need to carry the message body when sending the service processing request, and No need to wait for the MSCF response;
- the Subscribe field of the message subscription request (MM10-Subscribe.REQ) message is used to carry the user identifier
- the Trigger Point field is used to carry the service trigger point.
- Step 303 The MMSC saves the message subscription information, and returns a message order response.
- the above describes the implementation process of the user ordering the calling receipt service.
- the following describes the process of implementing the calling receipt service subscribed by the user.
- the method includes:
- Step 304 The sender user agent submits a message submission request (MM1 - Submit.REQ) to the MMSC;
- Step 305 The MMSC finds, according to the sender identifier, that the service trigger point that the MSCF subscribes to the user in the existing message subscription information is TPA3 and TPA4, and returns a message to the sender user agent to submit a response (MM1-Submission. RES );
- Step 306 The MMSC sends a notification message (MM1 - Notification.REQ) to the receiver user agent.
- Step 307 The receiver user agent sends a notification response message (MM1 - Notification.RES) to the MMSC;
- Step 308 The MMSC reaches the TPA3 point, and the MMSC sends a service processing request (MM1 O Interrogation.REQ) to the MSCF.
- MM1 O Interrogation.REQ MM1 O Interrogation.REQ
- the field sender address in the service processing request (MM10-Interrogation.REQ) message carries the sender identifier;
- Step 309 The MSCF finds that the user subscribes to the calling receipt service in the stored service subscription information according to the sender identifier, and the MSCF sends a receipt message to the sender user agent, prompting the sender to push the notification. Sent completed;
- Step 310 The receiver user agent sends a message acquisition request (MM1_Retrieve.REQ); Step 311: MMSC returns a message acquisition response (MM1_Retrieve.RES);
- the message content field of the message acquisition response includes a message body. If the sender user also subscribes to the signature file service, the message acquisition response (MM1_Retrieve.RES) carries the message body with the added signature file. .
- Step 312 The receiver user agent sends a Get Successful Acknowledgement (MM1_Acknowledge.REQ) message to the MMSC;
- Step 313 The MMSC reaches the TPA4 point, and the MMSC sends a service processing request (MM1 O Interrogation.REQ) to the MSCF.
- MM1 O Interrogation.REQ MM1 O Interrogation.REQ
- the service processing request may carry a Sender address field and a Send Status field;
- Step 314 After receiving the service processing request (MM10-Interrogation.REQ) message, the MSCF obtains the sender identifier from the sender address field, and obtains the message delivery status according to the Send Status, and then sends a receipt message to the sender user agent, prompting The final result of the user message.
- MM10-Interrogation.REQ service processing request
- the method further includes:
- Step 315 The MMSC returns a delivery request to the sender user agent.
- Step 316 The sender user agent returns a delivery response (MM1 - DeliveryReport.RES) message to the MMSC.
- step 305 may be performed after step 306, or may be performed between step 307 and step 308, without affecting Implementation of an embodiment of the present invention.
- advertising volunteer business means that some users voluntarily add advertising information to the messages they receive, in exchange for the operator's advertising share.
- a method for implementing an advertisement volunteer service includes: Step 401: A user submits an advertisement volunteer service order request carrying service order information to an MSCF;
- the service subscription information may include: a user identifier, a service type identifier; Step 402: The MSCF saves the service subscription information, and sends a message subscription request (MM10-Subscribe.REQ) carrying the message subscription information to the MMSC;
- MM10-Subscribe.REQ message subscription request
- the service triggering point in the message ordering information is: TPB1 point and TPB3 point, and when ordering the TPB1 point, the message ordering information needs to include: a message body identifier and a waiting response identifier, which are used to indicate to the MMSC when sending a service processing request Need to carry the message body and wait for the MSCF response; Order
- the MMSC does not need to carry the message body when initiating a service processing request, and does not need to wait for the MSCF to respond;
- Step 403 The MMSC saves the message subscription information carried in the message subscription request (MM10_Subscription.REQ) message, and returns a message order response message (MM10_Subscribe.RES) to the MSCF.
- MM10_Subscription.REQ message subscription request
- MM10_Subscribe.RES message order response message
- the above describes the implementation process of the user's subscription advertising volunteer business.
- the following describes the process of implementing the advertising volunteer business subscribed by the user.
- the method includes:
- Step 404 The sender user agent submits a message submission request (MM1 - Submit.REQ) to the MMSC;
- the message submission request (MM1 - Submit.REQ) message includes: a sender identifier, a receiver identifier, and a message body;
- Step 405 The MMSC finds, according to the identifier of the receiver, that the service trigger point that the MSCF subscribes to the user in the existing message subscription information is TPB1 and TPB3, and the MMSC returns a message to the sender user agent to submit a response (MM1 - Submit .RES ) message;
- Step 406 The MMSC arrives at the TPB1 point, sends a service processing request (MM1 O Interrogation.REQ) to the MSCF, and waits for a response from the MSCF.
- MM1 O Interrogation.REQ MM1 O Interrogation.REQ
- the Content Type and Content fields may be included in the Service Processing Request (MM10-Interrogation.REQ) message.
- Step 407 After receiving the service processing request (MM10_Interrogation.REQ) message, the MSCF finds in the existing service subscription information that the recipient user subscribes to the advertising volunteer service according to the identifier of the receiver, and then the MSCF analyzes the message. Fields such as Content Type and Content, and add advertisement information after the message body carried in the Content field, and return the message body of the added advertisement information to the MMSC through the service processing response (MM10-Interrogation.RES) message, and in the Process Status field Indicates that the MMSC needs to modify the message.
- MM10-Interrogation.RES Service Processing Response
- Step 408 The MMSC saves the message body that adds the advertisement information according to the requirements of the MSCF, and sends a notification (MMl_Notification.REQ) message to the receiver user.
- Step 409 The receiving user agent returns a notification response (MM1 - Notification. RES) message;
- Step 410 The receiving user agent sends a message obtaining request (MM1 - retrieve.REQ);
- Step 411 MMSC returns a message to obtain a response (MM1 - Retrieve .RES ) message, wherein the message content of the message acquisition response (MM1_Retrieve.RES) carries the message body with the added advertisement information.
- Step 412 The receiving user agent sends a successful acquisition confirmation (MM1 - Acknowledge.REQ) to the MMSC;
- Step 413 The MMSC arrives at the TPB4 point, and sends a service processing request (MM1 O Interrogation.REQ) message to the MSCF, where the service processing request (MM10-Interrogation.REQ) message includes a Send Status field to indicate the result of the message delivery; MSCF After receiving the service processing request (MM10-Interrogation.REQ) message, it decides whether to compensate the user according to the delivery status displayed in the Send Status field.
- MM1 O Interrogation.REQ MM1 O Interrogation.REQ
- the service processing request (MM10-Interrogation.REQ) message includes a Send Status field to indicate the result of the message delivery
- MSCF After receiving the service processing request (MM10-Interrogation.REQ) message, it decides whether to compensate the user according to the delivery status displayed in the Send Status field.
- the method further includes:
- Step 414 The MMSC sends a delivery request to the sender user agent.
- Step 415 The sender user agent returns a delivery response (MM1 - DeliveryReport.RES) message to the MMSC.
- the foregoing provides a method provided by the embodiment of the present invention.
- a technician may implement the foregoing three types of multimedia message services in an MSCF according to the method provided by the embodiment of the present invention, or implement the foregoing three types of multimedia message services in three MSCFs.
- the implementation of the embodiments of the present invention is not affected. It will be understood by those skilled in the art that all or part of the steps of implementing the foregoing embodiments may be performed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium. , including the following steps:
- a method for implementing a multimedia message service comprising: a multimedia message service center receiving a message submission request; the multimedia message service center searching for a message service control in the existing message subscription information according to the user identifier carried in the message submission request
- the function device is a service trigger point subscribed by the user; when the service trigger point is reached, the multimedia message service center sends a service processing request to the message service control function device; the message service control function device is configured according to the The user identifier carried in the service processing request searches for the service subscribed by the user in the existing service subscription information, and performs corresponding service processing.
- the above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
- the embodiment of the present invention further provides a message service control function device.
- the method includes: a service subscription request receiving unit 501, configured to receive a service subscription request that carries service subscription information;
- the service order information holding unit 502 is configured to save the service ordering information, where the service ordering information may include: a user identifier and a service type identifier;
- the message ordering request sending unit 503 is configured to: when the service ordering request receiving unit receives the service ordering request, send a message ordering request carrying the message ordering information to the multimedia message service center, where the message ordering information may include: user identifier and service triggering Point
- the message service control function device further includes: a service processing request receiving unit 504, configured to receive a service processing request, in order to complete the user-initiated service processing;
- the service search unit 505 is configured to search for the service subscribed by the user in the service order information holding unit 502 according to the user identifier carried in the service processing request.
- the service processing unit 506 is configured to perform corresponding service processing according to the service found by the service search unit 505.
- the message service control function device provided by the embodiment of the present invention implements the order message to the MMSC, so that the MMSC only sends the message ordered by the MSCF to the MSCF for corresponding service processing, thereby preventing the MMSC from triggering each message sent by the user to the MSCF. Problems that cause excessive pressure on MSCF
- the embodiment of the present invention further provides a system for implementing a multimedia message service. Referring to FIG. 6, the method includes: a multimedia message service center 601, and a message service control device 602.
- the Multimedia Messaging Service Center 601 includes:
- the message submission request receiving unit 6011 is configured to receive a message submission request submitted by the user agent.
- the service trigger point searching unit 6012 is configured to search for the message service control function in the existing message subscription information according to the user identifier carried in the message submission request.
- the device triggers a service trigger point for the user;
- the service processing request sending unit 6013 is configured to send a service processing request to the message service control function device when the service trigger point is reached;
- the message service control function device 602 includes:
- the service processing request receiving unit 6021 is configured to receive a service processing request sent by the service request sending unit.
- the service search unit 6022 is configured to search for the service subscribed by the user in the stored service subscription information according to the user identifier carried in the service processing request.
- the service processing unit 6023 is configured to perform corresponding service processing according to the service found by the service search unit.
- the method further includes:
- the service subscription request receiving unit is configured to receive a service subscription request that carries the service subscription information
- the service subscription information storage unit is configured to save the service subscription information
- the service subscription information may include: a user identifier and a service type identifier
- the message ordering request sending unit is configured to: when the service ordering request receiving unit receives the service ordering request, send a message ordering request carrying the message ordering information to the multimedia message service center, where the message ordering information may include: a user identifier and a service triggering point ;
- the method further includes:
- a message ordering request receiving unit configured to receive a message ordering request sent by the message ordering request sending unit
- the message ordering information holding unit is configured to save the message ordering information carried in the message ordering request.
- the service ordering request submitted by the user agent is a signature file service ordering request
- the service ordering information saved by the service ordering information saving unit further includes: a signature file
- the message ordering information sent by the message ordering request sending unit further includes: a message body identifier and a wait response identifier;
- the service trigger point sent by the message ordering request sending unit is specifically: TPA1 point or TPA2 point.
- the service processing request sent by the service processing request sending unit 6013 further carries the message body and the sender identifier in the message submission request;
- the service processing unit 6023 is a signature file service processing unit, configured to: when the TPA1 point or the TPA2 point is reached, search for the signature file preset by the sender in the stored service subscription information according to the sender identifier, and add the signature file. In the message body, the message body of the added signature file is returned to the multimedia message service center by the service processing response message.
- the service subscription request submitted by the user is a caller receipt service request, and the service trigger point sent by the message subscription request sending unit is TPA3 point and/or TPA4 point;
- the service processing request sent by the service processing request sending unit 6013 carries the sender identifier
- the service processing unit 6023 includes: a first calling return service processing unit, configured to: send a return receipt message to the sender user agent, prompting the sender user system that the notification message has been sent to the recipient user.
- the service processing request sent by the service processing request sending unit 6013 carries the sender identifier and the message delivery status identifier;
- the service processing unit 6023 further includes: a second calling return service processing unit; the second calling return service processing unit is configured to:
- the service ordering request submitted by the user agent is an advertisement volunteer service ordering request
- the service triggering point sent by the message ordering request sending unit is TPB1 point and TPB3 point
- the message ordering information sent by the message ordering request sending unit further includes: a message body identifier and a waiting response identifier.
- the service processing request sent by the service processing request sending unit 6013 carries the receiver identifier
- the service processing unit 6023 includes: an advertisement volunteer service processing unit:
- the service processing request sent by the service processing request sending unit 6013 carries the receiver identifier and the message delivery status identifier;
- the service processing unit 6023 further includes: a charging compensation unit;
- the billing compensation unit is configured to determine whether to compensate the user for the advertisement according to the status of the message delivery status displayed by the message delivery status indicator.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09722138.6A EP2247124B1 (en) | 2008-03-18 | 2009-03-17 | Method, system and related device for implementing multimedia messaging service |
BRPI0910929-3A BRPI0910929B1 (pt) | 2008-03-18 | 2009-03-17 | Método e sistema para implementar serviço de transmissão de mensagem de multimídia, função de controle de serviço de transmissão de mensagem e centro de serviço de transmissão de mensagem de multimídia |
MX2010010228A MX2010010228A (es) | 2008-03-18 | 2009-03-17 | Metodo, sistema y dispositivo relacionados para implementar servicio de mensajeria multimedia. |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2008100873159A CN101252704B (zh) | 2008-03-18 | 2008-03-18 | 多媒体消息业务的实现方法、系统及相关设备 |
CN200810087315.9 | 2008-03-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009115033A1 true WO2009115033A1 (zh) | 2009-09-24 |
Family
ID=39955860
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/070836 WO2009115033A1 (zh) | 2008-03-18 | 2009-03-17 | 多媒体消息业务的实现方法、系统及相关设备 |
Country Status (6)
Country | Link |
---|---|
EP (1) | EP2247124B1 (zh) |
CN (1) | CN101252704B (zh) |
BR (1) | BRPI0910929B1 (zh) |
MX (1) | MX2010010228A (zh) |
RU (1) | RU2465741C2 (zh) |
WO (1) | WO2009115033A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102098627A (zh) * | 2009-12-14 | 2011-06-15 | 华为技术有限公司 | 一种多媒体消息传送的方法、系统及装置 |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101252704B (zh) * | 2008-03-18 | 2011-11-02 | 华为技术有限公司 | 多媒体消息业务的实现方法、系统及相关设备 |
CN103517225B (zh) * | 2012-06-27 | 2018-01-02 | 中兴通讯股份有限公司 | 彩信重试方法及装置 |
CN102869002A (zh) * | 2012-08-01 | 2013-01-09 | 福建富士通信息软件有限公司 | 增值业务订购关系管理系统 |
CN106254614A (zh) * | 2016-07-26 | 2016-12-21 | 惠州市斯坦利科技有限公司 | 通讯录联系人处理方法和装置 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1424860A2 (en) * | 2002-11-05 | 2004-06-02 | Siemens Aktiengesellschaft | Method for controlling a multimedia messaging service between a telecommunication device and a telecommunication network, respective smart card and telecommunication device |
CN1889718A (zh) * | 2006-07-19 | 2007-01-03 | 中国移动通信集团公司 | 短消息增值业务的控制系统及控制方法 |
CN101068375A (zh) * | 2007-05-29 | 2007-11-07 | 中国网络通信集团公司 | 实现短消息增值业务的系统、平台及方法 |
WO2007134821A1 (de) * | 2006-05-24 | 2007-11-29 | T-Mobile International Ag & Co. Kg | Verfahren zur steuerung und benutzerspezifischen anpassung eines multimedia messaging dienstes |
CN101252704A (zh) * | 2008-03-18 | 2008-08-27 | 华为技术有限公司 | 多媒体消息业务的实现方法、系统及相关设备 |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FI115744B (fi) * | 2001-02-08 | 2005-06-30 | Nokia Corp | Kommunikaatiopalvelu |
WO2003030474A2 (en) * | 2001-09-28 | 2003-04-10 | Markport Limited | Mmsc access control |
EP1555835A3 (en) * | 2001-12-21 | 2007-01-10 | Orange Personal Communications Services Ltd. | Call processing in mobile telecommunications networks |
CN100372391C (zh) * | 2004-08-16 | 2008-02-27 | 华为技术有限公司 | 一种多媒体消息系统及转发多媒体消息的方法 |
DE102004041912B4 (de) * | 2004-08-30 | 2009-11-26 | Infineon Technologies Ag | Kommunikationsendgerät, Verfahren zum postalischen Versenden von Nutzdaten, Kommunikationssystem, Verfahren zum Erzeugen einer Postsendung, Server und Verfahren zum Betreiben eines Servers |
KR100666711B1 (ko) * | 2005-11-09 | 2007-01-11 | 주식회사 케이티프리텔 | 개방형 모바일 비즈니스 지원 시스템에서 메시지 전송 후실시간 리포트 제공 장치 및 방법 |
EP1868125A1 (en) * | 2006-06-16 | 2007-12-19 | Savernova S.A. | Method for identifying a user of a computer system |
-
2008
- 2008-03-18 CN CN2008100873159A patent/CN101252704B/zh active Active
-
2009
- 2009-03-17 EP EP09722138.6A patent/EP2247124B1/en active Active
- 2009-03-17 BR BRPI0910929-3A patent/BRPI0910929B1/pt active IP Right Grant
- 2009-03-17 RU RU2010142385/07A patent/RU2465741C2/ru active
- 2009-03-17 MX MX2010010228A patent/MX2010010228A/es active IP Right Grant
- 2009-03-17 WO PCT/CN2009/070836 patent/WO2009115033A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1424860A2 (en) * | 2002-11-05 | 2004-06-02 | Siemens Aktiengesellschaft | Method for controlling a multimedia messaging service between a telecommunication device and a telecommunication network, respective smart card and telecommunication device |
WO2007134821A1 (de) * | 2006-05-24 | 2007-11-29 | T-Mobile International Ag & Co. Kg | Verfahren zur steuerung und benutzerspezifischen anpassung eines multimedia messaging dienstes |
CN1889718A (zh) * | 2006-07-19 | 2007-01-03 | 中国移动通信集团公司 | 短消息增值业务的控制系统及控制方法 |
CN101068375A (zh) * | 2007-05-29 | 2007-11-07 | 中国网络通信集团公司 | 实现短消息增值业务的系统、平台及方法 |
CN101252704A (zh) * | 2008-03-18 | 2008-08-27 | 华为技术有限公司 | 多媒体消息业务的实现方法、系统及相关设备 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2247124A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102098627A (zh) * | 2009-12-14 | 2011-06-15 | 华为技术有限公司 | 一种多媒体消息传送的方法、系统及装置 |
Also Published As
Publication number | Publication date |
---|---|
EP2247124A4 (en) | 2011-03-23 |
MX2010010228A (es) | 2010-12-20 |
RU2465741C2 (ru) | 2012-10-27 |
EP2247124B1 (en) | 2014-12-03 |
CN101252704A (zh) | 2008-08-27 |
BRPI0910929A8 (pt) | 2018-10-16 |
CN101252704B (zh) | 2011-11-02 |
RU2010142385A (ru) | 2012-04-27 |
EP2247124A1 (en) | 2010-11-03 |
BRPI0910929B1 (pt) | 2020-09-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7269431B1 (en) | System for forwarding SMS messages to other devices | |
US8832204B1 (en) | Text message spam solutions | |
US8326288B2 (en) | Method and apparatus for providing virtual mobile phone number | |
US8406792B2 (en) | Message modification system and method | |
US20070178895A1 (en) | Method, network entity, system, mobile device and computer program product for automatic provisioning of a service | |
JP6000125B2 (ja) | 選択的なメッセージサービスブロッキングに関する方法および装置 | |
EP2184932B1 (en) | method, device and system for interworking between instant message and short message | |
EP1935144A2 (en) | Apparatus and method for providing a context-sensitive multimedia message service response | |
WO2006056791A1 (en) | Telecommunications services apparatus and methods | |
GB2453260A (en) | Processing a message by using the virtual number of a SSMN terminal | |
WO2015176238A1 (zh) | 隐私保护的方法、装置和用户终端 | |
WO2009115033A1 (zh) | 多媒体消息业务的实现方法、系统及相关设备 | |
JP5661107B2 (ja) | 複数の受信機に電子ショートメッセージを送信するための方法およびシステム | |
EP2424279B1 (en) | Method for processing group messages, service delivery platform and associated equipment | |
JP5179367B2 (ja) | 非同期メッセージの受信通知方法 | |
WO2003094553A1 (en) | Method and device for delivering messages to mobile terminal devices in accordance with a user selectable attainability status | |
KR101790896B1 (ko) | 메시지 처리를 위한 장치 및 그 제어방법 | |
GB2439463A (en) | Telecommunications services methods and apparatus | |
EP1557988A1 (en) | Method and device for wireless messaging | |
WO2011032396A1 (zh) | 一种实现免打扰业务的方法及装置 | |
KR100604723B1 (ko) | 데이터 버스트 메시지를 이용한 멀티미디어 데이터 수신확인 및 읽기 확인 서비스 제공 방법 및 시스템 | |
WO2012009895A1 (zh) | 支持非mms终端使用多媒体消息的方法及mmsc | |
EP2034677A1 (en) | A multimedia message group sending system and the method thereof | |
KR100620858B1 (ko) | 외부 단문 메시지를 위한 가상 이동통신 번호 제공 방법및 장치 | |
KR100620855B1 (ko) | 단문 메시지를 위한 가상 이동통신 번호 제공 방법 및 장치 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09722138 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2010/010228 Country of ref document: MX |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009722138 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010142385 Country of ref document: RU |
|
ENP | Entry into the national phase |
Ref document number: PI0910929 Country of ref document: BR Kind code of ref document: A2 Effective date: 20100917 |