Method for processing push notification in multimedia message service

• US 7,899,476 B2
• Filed: 01/04/2007
• Issued: 03/01/2011
• Est. Priority Date: 07/09/2004
• Status: Expired due to Fees

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Cheng, Weiming, Li, Dawei
• Primary Examiner(s): Hu; Jinsong
• Assistant Examiner(s): Nguyen; Michael
• Application Number:
  US11/619,757
• Publication Number:
  US 20070180037A1
• Time in Patent Office: 1,517 Days
• Field of Search: 455/466, 455/412.1, 455/412.2, 455/414.1, 455/414.2, 455/424, 455/426.1, 455/456.1, 455/456.2, 455/556.1, 455/556.2, 455/414.4, 709/206, 709/207, 370/428, 370/429, 370/522, 370474-477
• US Class Current: 455/466
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

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.

Claims

1. A method for processing a PUSH notification in multimedia message service, comprising:

placing, by a Multimedia Message Service Center, MMSC, non-compressible fields of the PUSH notification into the PUSH notification, compressing a ContentType field signifying message body type and an X-Mms-Transaction ID field of Internal ID, and placing the compressed ContentType field and the compressed X-Mms-Transaction ID field into the PUSH notification;

determining, by the MMSC, 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, by the MMSC, 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 the 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 the 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

wherein, the processes of determining whether to place the initiator From field into the PUSH notification and whether to compress the Subject field and place the Subject field into the PUSH notification comprises;

determining, by the MMSC, whether the unoccupied bytes in the short message are enough to hold the From field, if the unoccupied bytes in the short message are not enough to hold the From field, discarding the From field and the Subject field, and terminating the processes of the PUSH notification;

otherwise placing the From field into the Push notification;

determining, by the MMSC, whether the Subject field may adopt a character set or a coding mode to make a coding length of the Subject field shorter;

if the Subject field may adopt the character set or a coding mode to make the coding length of the Subject field shorter, adopting the character set or the coding mode of shorter coding length to express the Subject field;

otherwise, adopting originally used character set or coding mode;

determining, by the MMSC, whether the unoccupied bytes in the short message, after holding the From field, are enough to hold the character set or the coding mode of the Subject field and codes corresponding to at least one character in a character string code of the Subject field;

if the unoccupied bytes in the short message, after holding the From field, are enough to hold the character set or the coding mode of the Subject field and the codes corresponding to at least one character in the character string code of the Subject field, placing the character set or the coding mode into the PUSH notification, and placing the codes corresponding to an individual character in the character string code into the PUSH notification in sequence according to the unoccupied bytes in the short message;

otherwise, discarding the Subject field and terminating the processes of the PUSH notification.

2. The method according to claim 1, wherein the non-compressible fields of the PUSH notification placed into the PUSH notification comprise 10 fields, the 10 fields not including the ContentType field signifying the message body type, the X-Mms-Transaction-ID field signifying the internal ID, the From field signifying the initiator of the message, and the Subject field signifying a subject of the message.

3. The method according to claim 1, wherein, the process of compressing the ContentType field signifying the message type comprises:

expressing, by the MMSC, the ContentType field signifying the message type with binary codes that takes up 1 byte.

4. The method according to claim 1, wherein, the process of compressing the X-Mms-Transaction-ID field of the internal ID comprises:

discarding, by the MMSC, a central ID of the multimedia message service in the internal ID, and expressing time part in seconds;

discarding, by the MMSC, the central ID in the field of the internal ID, expressing the time part with seconds and converting the field of the internal ID into codes of 64 based number system.

5. The method according to claim 1, wherein, the process of determining whether the PUSH notification can be carried in one short message comprises:

determining, by the MMSC, whether length of the PUSH notification is shorter than 140 bytes;

if length of the PUSH notification is shorter than 140 bytes, the PUSH notification can be carried in one short message;

otherwise, the PUSH notification cannot be carried in one short message.

6. The method according to claim 1, wherein, the process of placing the codes corresponding to the individual characters in the part of the character string codes into the PUSH notification in sequence comprises:

determining, by the MMSC, bytes occupied by the codes to express one displayable character in the existing coding mode;

calculating, by the MMSC, a value m according to the unoccupied bytes of the short message holding the character set coding mode and the coding bytes determined according to the existing coding mode, wherein the value m is the number of displayable characters that the short message holds;

placing, by the MMSC, the codes corresponding to the characters from the first one to m of the character string coding part in the Subject field into the PUSH notification in sequence.