Method For Processing Push Notification In Multimedia Message Service
First Claim
1. A method for processing a PUSH notification in multimedia message service, comprising:
- placing non-compressible fields of the PUSH notification into the PUSH notification, compressing a Type field signifying message type and a Transaction identification (TID) field of Internal ID, and placing the compressed Type field and the compressed TID field into the PUSH notification;
determining whether the PUSH notification can be carried in one short message;
if the PUSH notification can be carried in one short message, having the PUSH notification carried in one short message;
if the PUSH notification cannot be carried in one short message, having the PUSH notification carried in two short messages;
determining whether there are unoccupied bytes in the short message;
if there are unoccupied bytes in the short message, determining whether placing a From field signifying an initiator of the message into the PUSH notification according to number of the unoccupied bytes in the short message, and determining whether compressing a Subject field as well as placing the Subject field into the PUSH notification according to number of the unoccupied bytes in the short message;
if the From field has already been put into the short message, whereas there are no enough bytes in the short message to hold the Subject field, discarding the Subject field;
if there are unoccupied bytes in the short message, but the From field cannot be hold in the short message, discarding the From field and the Subject field that are not placed into the PUSH notification.
1 Assignment
0 Petitions
Accused Products
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.
26 Citations
7 Claims
-
1. A method for processing a PUSH notification in multimedia message service, comprising:
-
placing non-compressible fields of the PUSH notification into the PUSH notification, compressing a Type field signifying message type and a Transaction identification (TID) field of Internal ID, and placing the compressed Type field and the compressed TID field into the PUSH notification;
determining whether the PUSH notification can be carried in one short message;
if the PUSH notification can be carried in one short message, having the PUSH notification carried in one short message;
if the PUSH notification cannot be carried in one short message, having the PUSH notification carried in two short messages;
determining whether there are unoccupied bytes in the short message;
if there are unoccupied bytes in the short message, determining whether placing a From field signifying an initiator of the message into the PUSH notification according to number of the unoccupied bytes in the short message, and determining whether compressing a Subject field as well as placing the Subject field into the PUSH notification according to number of the unoccupied bytes in the short message;
if the From field has already been put into the short message, whereas there are no enough bytes in the short message to hold the Subject field, discarding the Subject field;
if there are unoccupied bytes in the short message, but the From field cannot be hold in the short message, discarding the From field and the Subject field that are not placed into the PUSH notification. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
Specification