Processing method for sending out notice in multimedia message service

Abstract

The invention discloses a method for processing a PUSH notification, including: placing non-compressible fields into the Push notification and placing into the PUSH notification a field signifying message type and a field of internal ID after the fields are compressed; determining whether the PUSH notification may be carried in one short message; if yes, having the PUSH notification carried in one short message; otherwise, having the PUSH notification carried in two short messages; determining whether there are any unoccupied bytes in the short message; if yes, determining whether to place the initiator From field into the PUSH notification according to the number of the unoccupied bytes in the short message, and determining whether to compress Subject field and place the Subject field into the PUSH notification; otherwise, terminating the processing flow of the PUSH notification. The present invention may have the PUSH notifications carried in two short messages at most.

Description

technical field [0001] The invention relates to multimedia information communication technology, in particular to a processing method for push (PUSH) notification in multimedia message service. Background technique [0002] Multimedia Messaging Service (MMS) is a further development of Short Message Service (SMS) and picture information transmission, which enables the transmission of fully functional content and information including images, audio information, video information, data, and text. The multimedia information service can realize real-time mobile phone end-to-end, mobile terminal-to-Internet or Internet-to-mobile terminal multimedia information transmission. A multimedia message service center (MMSC) is a network element responsible for sending multimedia messages on the network. [0003] During the transmission of the multimedia message, when the MMSC receives the multimedia message sent to the MMS terminal by the MMS terminal, the value-added service provider (...

AI Technical Summary

Problems solved by technology

[0061] 1. Since a short message is up to 140 bytes, and the total length of the existing PUSH notification message exceeds 140 bytes, it must be split into multiple messages when sending, and the receiver must wait for the message carrying the same PUSH notification. After all the short messages arrive, they are reassembled into a complete PUSH notification, so the delay in completing the PUSH notification delivery is long and the efficiency is low

[0062] 2. Using multiple short messages to carry a PUSH notification makes the intermediate link of the PUSH notification process more complicated

In addition, when a short message fails to be sent, in the presence of WAPGW, the retransmission mechanisms of MMSC and WAPGW are difficult to coordinate, and it is impossible to accurately determine the short message that should be resent, resulting in a low success rate of PUSH notification, which greatly Affected the quality of service of the multimedia messaging service

[0063] 3. Splitting a PUSH notification into multiple short messages causes too many intermediate links in sending, and the operation cost is relatively high

Images