TECHNICAL FIELD

The present invention relates to the field of communications technologies, and in particular, to a method, a system and an apparatus for processing notification.

BACKGROUND

Usually in value added service (Value Added Service, VAS), users need to be notified with notifications of subscribed services. For example, while a callee number is not available in a network of global system for mobile communications (Global System for Mobile Communications ,GSM) or code division multiple access (Code Division Multiple Access ,CDMA), the mobile switching center (Mobile Switching Center, MSC) will redirect the call to a voice mail service (Voice Mail Service , VMS) system for further flow to allow a caller number to record voice mail or generate missed call notification to the callee number which will be further sent to a short message service center (Short Message Service Center, SMSC) to notify the callee number when it is reachable in network. While sending a new notification to a user, the VMS system needs to make sure that if the previously submitted short message of a previous notification stored in the SMSC has not been delivered to the user by the SMSC, the previously submitted short message of the previous notification stored in the SMSC should be replaced by the short message of the new notification so that the user always gets the latest short message of the latest notification from the VMS system. When the previously submitted short message of the previous notification should be replaced by the short message of the new notification □ the short message of the new notification carries a replacement flag to indicate the replacement should be performed.

Sometimes, the content of a notification is more than 140 bytes after encoding. For example, Chinese, Russian or Arabic characters are UTF-8 characters not a plain text and the encoded length of the notification content can be easily more than 140 bytes. When the content length is longer than 140 bytes, while a VAS System can use message_payload to transmit the message, however a lot of existing mobile communication networks as well as handsets do not support a message more than 140 bytes. In the case where message_payload is not applicable, the VMS system will split the notification into a plurality of segments each of which is carried by one short message when the notification contains more than 140 bytes, and thus the notification will be sent via a plurality of short messages. If the plurality of short messages of this notification should replace the short message of the previous notification stored in the SMSC, each short message of this notification carries the replacement flag to indicate the replacement should be performed. Then, when the plurality of short messages of this notification are sent to the SMSC, a previously submitted short message of this notification will be replaced by a currently submitted short message of this notification, and eventually only the last submitted short message of this notification will be stored and further send to the user.

SUMMARY

Embodiments of the present invention provide a method, a system and an apparatus for processing notification, to solve the problem that only the last submitted short message can be stored in the SMSC when the content of the notification is more than 140 bytes and carried in multiple short messages. According to a first aspect, a method for processing notification comprises: generating, by a service system, short messages of a notification, wherein each one of the short messages carries a replacement flag and an identification tag which indicates the short messages belong to the notification; sending, by the service system, the generated short messages to a short message service center. In a first possible implementation form of the method for processing notification according to the first aspect, the generating short messages of a notification comprises: splitting the notification into a plurality of segments; generating a plurality of short messages, wherein each one of the plurality of short messages carries one of the plurality of segments and the replacement tag; and assigning an identification tag to each one of the plurality of short messages. In a second possible implementation form of the method for processing notification according to the first aspect as such or according to the first implementation form of the first aspect, the identification tag is carried in a User Data Head of the short message. In a third possible implementation form of the method for processing notification according to the first aspect as such or according to the first implementation form of the first aspect, the identification tag comprises an ID number assigned to the notification and a sequence number of the short message belonging to the notification.

In a fourth possible implementation form of the method for processing notification according to the third implementation form of the first aspect, the ID number assigned to the notification is carried in UDH-Length and/or the sequence number of the short message is carried in UDH-Content.
According to a second aspect, a method for processing notification comprises: receiving, by a short message service center, a currently submitted short message carrying a replacement flag and an identification tag which indicates the short message belongs to a notification; and identifying, based on the identification tag, that the currently submitted short message and a previously submitted short message belong to the same notification, and storing the currently submitted short message without replacing the previously submitted short message. In a first possible implementation form of the method for processing notification according to the second aspect, the identifying, based on the identification tag, that the currently submitted short message and a previously submitted short message belong to the same notification comprises: when the replacement flag indicates to replace a previously submitted short message with the currently submitted short message, determining the previously submitted short message based on a source address, a destination address and a service type carried in the currently submitted short message; determining whether an identification tag of the previous short message matches the identification tag carried in the currently submitted short message; if matching, identifying that the currently submitted short message and the previously submitted short message belong to the same notification.

In a second possible implementation form of the method for processing notification according to the second aspect, the identification tag comprises an ID number assigned to the notification and a sequence number of the short message belonging to the notification. In a third possible implementation form of the method for processing notification according to the second aspect as such, the first possible implementation form of the second aspect, or the second possible implementation form of the second aspect, the identification tag is carried in a User Data Head of the short message. In a fourth possible implementation form of the method for processing notification according to the second possible implementation form of the second aspect, the ID number assigned to the notification is carried in UDH-Length and/or the sequence number of the short message is carried in UDH-Content. According to a third aspect, a service system for processing notifications comprises: a generating unit, configured to generate short messages of a notification, wherein each one of the short messages carries a replacement flag and an identification tag which indicates that the short messages belong to the notification; and a sending unit, configured to send the generated short messages to a short message service center.
In a first possible implementation form of the service system according to the third aspect, the generating unit comprises: a splitting subunit, configured to split the notification into a plurality of segments; a generating subunit, configured to generated a plurality of short messages, wherein each one of the plurality of short messages carries one of the plurality of segments and the replacement tag; and an assigning subunit, configured to assign an identification tag to each one of the plurality of short messages. According to a fourth aspect, a short message service center for processing notification comprises: a receiving unit, configured to receive a currently submitted short message carrying a replacement flag and an identification tag which indicates the currently submitted short message belong to a notification; an identifying unit, configured to identify, based on the identification tag, that the currently submitted short message and a previously submitted short message belong to the same notification, and store the currently submitted short message without replacing the previously submitted short message.

In a first possible implementation form of the short message service center according to the fourth aspect, the identifying unit comprises: a determining subunit, configured to, when the replacement flag indicates to replace a previously submitted short message with the currently submitted short message, determine the previously submitted short message of the currently submitted short message based on a source address, a destination address and a service type carried in the currently submitted short message; an identifying subunit, configured to, if an identification tag of the previously submitted short message matches the identification tag carried in the currently submitted short message, identify that the currently submitted short message and the previously submitted short message belong to the same notification; and a storing subunit, configured to store the currently submitted short message without replacing the previously submitted short message, if the identifying subunit identifies that the currently submitted short message and the previously submitted short message belong to the same notification. In the method, the service system and the short message service center according to embodiments of the present invention, each short message of the notification carries an identification tag to indicate that the short messages belongs to the notification, so that the short messages of the same notification can be identified by the identification tag. The SMSC may determine whether to replace the previously submitted short message with the currently submitted short message by matching the identification tags of the previously submitted short message and the currently submitted short message. If the identification tags of the previously submitted short message and the currently submitted short message match to each other, it means that the previously submitted short message and the currently submitted short message belong to the same notification, the short message service center will not perform replacement, i.e., not replace the previously submitted short message with the currently submitted short message, instead stores both the previously submitted short message with the currently submitted short message. Therefore, the short messages belonging to the same notification will not replace each other in the SMSC and the problem that only the last submitted message can be stored in the SMSC and further sent to the user when the content of the notification is more than 140 bytes and carried by multiple short messages is solved.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

Fig. 1 is a schematic structural diagram of a VMS system integrated with SMSC;

Fig. 2 is a flow chart of the method for processing notification according to an embodiment of the present invention;

Fig.3 is a flow chart of the method for processing notification according to an embodiment of the present invention;

Fig. 4 is an information interaction diagram of the method for processing notification according to an embodiment of the present invention;

Fig. 5 is a schematic structural diagram of the service system for processing notification according to an embodiment of the present invention;

Fig. 6 is a schematic structural diagram of the service system for processing notification according to another embodiment of the present invention;

Fig. 7 is a schematic structural diagram of the short message service center for processing notification according to an embodiment of the present invention;

Fig. 8 is a schematic structural diagram of the short message service center for processing notification according to another embodiment of the present invention;

Fig. 9 is a schematic structural diagram of the service system for processing notification according to another embodiment of the present invention;

Fig. 10 is a schematic structural diagram of the short message service center for processing notification according to another embodiment of the present invention.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present invention are elaborated below with reference to the accompanying drawings. Evidently, the embodiments described below are for an exemplary purpose only, without covering all embodiments of the present invention. Those skilled in the art may derive other embodiments from the embodiments given herein without making creative effort, and all such embodiments are covered in the protection scope of the present invention. Fig. 1 shows a VAS system, e.g. VMS system, which records voice mail or generates missed call notification to voice mail subscriber from caller in case of the subscriber is not available in GSM network. In such process, the VMS system generates short messages of a new voice mail notification for the subscriber, e.g. callee number. After receiving the short message sent from the VMS system, SMSC acquires the mobile station center (Mobile Station Center, MSC) of the subscriber and the status of the subscriber (not in network or available in network) from the MSC via a home location register (Home Location Register, HLR). The SMSC will check callee number status based on the send route information (Send Route Information, SRI) response from the MSC to deliver the latest notification to the callee number, where the latest notification is sent by the VMS system to acknowledge the callee number about detail information of the caller. The SMSC performs replacement based on the caller number, the callee number and the service type of the previously submitted short message and the currently submitted short message, as well as the identification tags carried in the previously submitted short message and the currently submitted short message which indicate the notification the previously submitted short message belongs to and the notification the currently submitted short message belongs to respectively. The SMSC may determine whether the previously submitted short message and the currently submitted short message belong to the same notification by matching the identification tags of them. If the identification tag of the preciously submitted short message matches the identification tag of the currently submitted short message, which means that the previously submitted short message and the currently submitted short message belong to the same notification, the SMSC may save the currently submitted short message without replacing the previously submitted short message.

When the subscriber is available in network, the SMSC sends short messages to the user via the MSC of the subscriber. In embodiments of the present invention, the short messages of the same notification can be identified by the identification tag, therefore, the short messages belonging to the same notification will not replace each other in the SMSC and the problem that only the last submitted message can be stored in the SMSC and further sent to the user when the content of the notification is more than 140 bytes and carried by multiple short messages is solved.
Embodiment 1 As shown in Fig. 2, a method for processing notification according to embodiment 1 includes following steps: Step 101: A service system generates short messages of a notification, where each one of the short messages carries a replacement flag and an identification tag indicating the short messages belong to the notification; The service system can be a value added service system, e.g. a voice mail service system. Generating short messages of a notification can be implemented by splitting the notification into a plurality of segments; generating a plurality of short messages, wherein each one of short messages carries one of the plurality of segments and the replacement tag; and assigning an identification tag to each one of the plurality of short messages. The identification tag of different short messages belonging to the same notification can be the same or different so long as the short message service center can identify that the plurality of short messages belong to the same notification by the identification tag. In order to notify the user of the latest notification, the short message service center replaces a previously submitted short message of the previous notification pending for delivery with the currently submitted short message of the latest notification. For this purpose a replacement flag can be carried in the short messages of the latest notification to indicate that the current submitted short message is the latest and the previous submitted short message of the previous notification should be replaced with it. The replacement flag is, for example, replace_if_present flag in the submit_sm, which is set as 1 when replacement is requested.

If the content of the notification is so long that it cannot be encoded into one short message, the content of the notification can be split into a plurality of segments and each segment is carried by one short message. In such a case, in order to avoid the plurality of short messages of the same notification replacing each other, the plurality of short messages may be identified by carrying an identification tag which indicates that they belong to the same notification. Thereby the short message service center can determine whether the currently submitted short message and the previously submitted short message belong to the same notification by matching the identification tags of the currently submitted short message and the previously submitted short message, and does not replace the previously submitted short message with the currently submitted short message when the currently submitted short message matches the previously submitted short message, which means the currently submitted short message and the previously submitted short message belong to the same notification. Step 102: The service system sends the generated short messages to a short message service center. After generating the short messages of the notification, the service system sends the short messages one by one to the short message service center and the short messages will be further delivered to the user by the short message service center. By using the method provided in this embodiment, the service system can submit a short message carrying an identification tag to the short message service center. By the identification tag, short messages belong to the same notification can be easily identified so as to solve the problem that only the last submitted short message of the notification can be stored in the short message service center when the notification is carried in multiple short messages.

Embodiment 2 As shown in Fig. 3, a method for processing notification according to embodiment 2 includes following steps: Step 201: A short message service center receives a currently submitted short message carrying a replacement flag and an identification tag which indicates the short messages belongs to a notification; Step 202: The short message service center identifies, based on the identification tag, that the currently submitted short message and a previously submitted short message belong to the same notification, and stores the currently submitted short message without replacing the previously submitted short message. After receiving the short message from the service system, the short message service center may determine whether or not to replace the previously submitted short message with the currently submitted short message based on the replacement flag and the identification tag. If the replacement flag indicates to perform replacement, the short message service center determines the previously submitted short message of the currently submitted short message based on the source address, the destination address and the service type carried in the currently submitted short message. And then the short message service center determines whether the identification tag of the previous short message matches the identification tag carried in the currently submitted short message; if matching, the short message service center identifies that the currently submitted short message and the previously submitted short message belong to the same notification and then stores the currently submitted short message without replacing the previously submitted short message; if not matching, the short message service center identifies that the currently submitted short message and the previously submitted short message do not belong to the same notification and then replaces the previously submitted short message with the currently submitted short message. By using the method of this embodiment, the short message service center can identify whether or not the currently submitted short message and the previously submitted short message belong to the same notification by matching the identification tags of the currently submitted short message and the previously submitted short message. If the identification tag of currently submitted short message matches that of the previously submitted short message, which means the currently submitted short message and the previously submitted short message belong to the same notification, the short message service center will not replace the previously submitted short message with the currently submitted short message, instead stores the currently submitted short message so as to solve the problem that only the last submitted short message of the notification can be stored in .the short message service center when the notification is carried in multiple short messages.

Embodiment 3 In this embodiment, the notification is sent from the VAS system to the SMSC via submitsms. The identification tag is carried in User Data Head (UDH) of submitsm by using UDH-Len and UDH-Content, where the value of UDH-Len is the ID number assigned to the notification and the value of UDH-Content indicates the sequence of the submitsms. For the submitsms having the same source address, destination address and service type, if the values of UDH-Len are the same, it means that the submit_sms belong to the same notification and then the submitsms are stored in SMSC without replacement. UDH-Content is used to identify the sequence of the submit_sms. Since a GSM network as well as a handset doesn't support short message with more than 140 bytes, if the content length of a single notification is more than 140 bytes, the VAS system will generate multiple submit_sms to carry the notification.
The replace_if_present flag is set as 1 in each one of the multiple submitsms to enable replacement function. Each one of the multiple submitsms may carry UDH information.
The SMSC may determine whether or not to replace previous submit_sm with the current submitsm according to the value of UDH-Len of the previous submitsm and that of the current submitsm. If the value of UDH-Len of the previous submitsm and that of the current submit_sm are the same, it means that the previous submitsm and the current submitsm belong to the same notification, and the SMSC will not replace the previous submitsm with the current submitsm, instead store the current submit_sm. The following describes this embodiment in more details.
Reference mobile numbers: A-8095197563; C-8095197564. The numbers are short message entity (Short Message Entity, SME) numbers. The notification to be sent is "The below idea will help VAS System to avoid its multiple submitsm requests of same destination and source number to be replaced in SMSC while it's been splitted because of sm content is more than 140 bytes and replace_if_present flag is enabled as l;In this solution, while VAS System has sent multiple submi sm requests of same source and destination with its content length as 140 bytes". The content length of the notification is 391 bytes.

Fig. 3 is an information interaction diagram of the method for processing notification according to an embodiment of the present invention. As shown in Fig. 3, the method comprises following steps. 301. The VAS system generates three submitsms of sender A for corresponding destination C; The length of message content in a submitsm is 140 byte at most and UDH information is 6 bytes in each submit_sm which is included in the message content of submitsm, therefore the length of notification text in each submit_sm is 134 at most. Since the content length of the notification in this embodiment is 391 bytes, longer than 140 bytes, the notification is split into three segments and each one of the three segments is carried by one submitsm. Accordingly, the VAS system frames three submit_sms, i.e. SMI, SM2 and SM3, of sender A for corresponding destination C, where the length of notification text in SMI and the length of notification text in SM2 are 134 bytes while the length of notification text in SM3 is 123 bytes. Both the content length of SMI and SM2 are 140 bytes, and the content length ofSM3 is 129 bytes. An ID number is assigned to the notification, i.e. 5 in this embodiment, and the UDH-Len of each submitsm is set as the ID number assigned to the notification. The UDH-Content of each submit_sm may be in sequential form, as shown in the following real time submitsm protocol data unit (Protocol Data Unit, PDU) to identify the sequence of the multiple submitsms.
Below is the real time submitsm PDU: SUBMIT-SM1:- submit_sm msg-heade commandlength: 0x000000d4 command_id: 0x00000004 command_status: 0x00000000 sequenceno: 0x0000037e msg-body

service_type: VMN

orgaddrton: 0

org_addr_npi: 0

orgaddr: 8095197563

destaddrton: 0

destaddrnpi: 0

destaddr: 8095197564

esm_class: 64

protocoled: 0

priorityflag: 0

schedule_deliveryJime:000000000000000R

validity_period

registereddeliveryflag: 0

replace_if_present flag: 1

data_coding: 0

sm_default_msg_id: 0

sm_length: 140

shortmessage UDH

UDH-Len: 5 UDH-content: 0x0003460301

ASCII-text: The below idea will help VAS System to avoid its multiple submit_sm requests of same destination and source number to be replaced in S SUBMIT-SM2:- submit_sm msg-header commandlength: 0x000000d4 commanded: 0x00000004 command_status: 0x00000000 sequence_no: 0x000004bc msg-body service_type: VMN org_addr_ton: 0 orgaddrnpi: 0
orgaddr: 8095197563 dest_addr_ton: 0 dest_addr_npi: 0 dest_addr: 8095197564 esm_class: 64 protocoled: 0 priority_flag: 0 schedule_delivery_time:000000000005000R validity_period registereddeliveryflag: 0 replace_if_present_flag: 1 data_coding: 0 sm_default_msg_id: 0 srnjengfh: 140 short_message UDH UDH-Len: UDH-content: 0x0003460302 ASCII-text: MSC while it's been splitted because of sm content is more than 140 bytes and replace_if_present flag is enabled as 1 ;In this solution SUBMIT-SM3:- submit_sm msg-header commandjength: 0x000000c9 command_id: 0x00000004 command_status: 0x00000000 sequenceno: 0x000004bd msg-body

servicejype: VMN

org_addr_ton: 0

org_addr_npi: 0

orgaddr: 8095197563

dest_addr_ton: 0

destaddrnpi: 0

dest_addr: 8095197564

esm_class: 64

protocolid: 0

priority_flag: 0

scheduledeliveryjime: 000000000010000R

validity_period

registereddeliveryflag: 0

replace_if_present_flag: 1

data_coding: 0

sm_default_msg_id: 0

smlength: 129 short_message

UDH UDH-Len: 5

UDH-content: 0x0003460303

ASCII-text: , while VAS System has sent multiple submit_sm requests of same source and

destination with its content length as 140 bytes.

302. The VAS system submits 1st short message i.e. SMI to the SMSC to deliver to C with
RIP=1;

303. The VAS system submits 2nd short message i.e. SM2 to the SMSC to deliver to C with
RIP=1;

304. The VAS system submits 3rd short message i.e. SM3 to the SMSC to deliver to C with RIP=1;

305. The SMSC sends SRI request for C to the HLR;

306. The HLR sends SRI response with MSC address as MSC1 and Status as not in network;
HLR acquires the Status of C from MSC1 and sends the MSC address as MSC1 and Status as not in network in SRI response back to SMSC.

307. The SMSC saves SMI in queue associated with C;
In the SMSC, there is no existing SM with same source address, destination address and service type as SMI, so the SMSC saves SMI.

308. The SMSC saves SM2 in queue associated with C without replacing SMI; SMI has been saved in the SMSC. Since replace_if_present flag is 1, the SMSC may replace SMI according to source address, destination address, service type and UDH information. The SMSC identifies that SMI and SM2 have the same source address, destination address and service type and the values of UDH-Len in SMI and SM2 are also the same, so determines that SMI and SM2 belong to the same notification. Therefore the SMSC saves SM2 without replacing SMI.

309. The SMSC saves SM3 in queue associated with C without replacing SMI and SM2;
SMI and SM2 have been saved in the SMSC. Since replace_if_present flag is 1, the SMSC may perform replacement according to source address, destination address, service type and UDH information. The SMSC identifies that SM2 and SM3 have the same source address, destination address and service type and the values of UDH-Len in SM2 and SM3 are also the same, so determines that SM2 and SM3 belong to the same notification. Therefore the SMSC saves SM3 without replacing SM2.

310. The SMSC will be keep on checking status of C with HLR according to SMSC's retry scheduling strategy; or being triggered to retry due to alert from HLR;

311. The SMSC sends SRI request for C to the HLR;

312. The HLR sends SRI response with MSC address as MSC1 and Status as available in network; HLR acquires the Status of C from MSC1 and sends the MSC address as MSC1 and Status as available in network in SRI response back to SMSC.

313. The SMSC sends mobile terminated (Mobile Terminated, MT) request to the MSC1 for C of SM1,SM2 and SM3;

314. The MSC1 tries to send SM1,SM2 and SM3 to C (from sender A) as separate deliversms to C;

315. The MSC1 sends the SMSC MT response as success for C. By using the method provided in this embodiment, when the content of notification is longer than 140 bytes, the VAS system will split the notification into a plurality of segments, each one of the plurality of segments is carried by a submit_sm, each one of the plurality of submit_sms carries an identification tag, i.e. UDH information, to inform SMSC that the plurality of submitsms belong to the same notification. The SMSC validates the source address, the destination address and the service type as well as the UDH information, specifically UDH-Len and UDH-Content, if replace_if_present is enabled. When the source address, destination address and service type of the current submitsm are the same as those of the previous submitsm, if the UDH information of the current submitsm and the UDH information of the previous submitsm are also matching, i.e. UDH-Lens of them are the same and UDH-Contents of them are in same sequence, then the SMSC may identify that the current submit_sm belongs to the same notification as the previous submit_sm saved in the SMSC and thus there is no need to replace the previous submit_sm with the current submitsm; if the UDH information of the current submit_sm and the UDH information of the previous submit_sm are not matching, i.e. the UDH-Len of the current submitsm and that of the previous submit_sm are not the same, the SMSC will identify that the current submitsm and the previous submit_sm do not belong to the same notification and then replace the previous submitsm with the current submitsm. If the SMSC has stored multiple submitsms having the same source address, destination address and service type as the current submit_sm, but UDH information of said multiple submitsms and the UDH information of the current submit_sm are not matching, the SMSC will replace the multiple submitsms with the current submit_sm to store the current submitsm.

The method in this embodiment avoids the previous submit_sm being replaced by the current submit_sm when a notification is sent by a plurality of submit_sms. The submit_sms belonging to the same notification can be easily identified by the identification tag, i.e. UDH information in the embodiment, so as to solve the problem that only the last submitted short message can be stored in the SMSC when the notification is carried in multiple short messages. Embodiment 4 Corresponding to the method for processing notification provided by embodiments of the present invention, a service system is also provided. As shown in Fig. 5, the service system for processing notification in this embodiment includes: a generating unit 510, configured to generate short messages of a notification, where each one of the short messages carries a replacement flag and an identification tag which indicates that the short messages belong to the notification; and a sending unit 520, configured to send the generated short messages to a short message service center. The identification tag of different short messages belonging to the same notification can be the same or different so long as the short message service center can identify that the plurality of short messages belong to the same notification by the identification tag.
The replacement flag can be carried in the short messages to indicate that the current submitted short message is the latest and the previous submitted short message should be replaced with it. The replacement flag is, for example, replace_if_present flag in the submit_sm, which is set as 1 when replacement is requested. The service system in this embodiment can submit a short message carrying an identification tag to the short message service center. By the identification tag, short messages belong to the same notification can be easily identified so as to solve the problem that only the last submitted short message can be stored in the short message service center when the notification is carried in multiple short messages.

Embodiment 5 Fig. 6 shows a schematic structural diagram of the service system for processing notification according to this embodiment of the present invention. On the basis of the service system in Embodiment 4, the generating unit 510 in this embodiment specifically includes:
a splitting subunit 512, configured to split the notification into a plurality of segments a generating subunit 514, configured to generate a plurality of short messages, where each one of the plurality of short messages carries one of the plurality of segments and the replacement tag; and an assigning subunit 516, configured to assign an identification tag to each one of the plurality of short messages. The service system in this embodiment can submit a short message carrying an identification tag to the short message service center. By the identification tag, short messages belong to the same notification can be easily identified so as to solve the problem that only the last submitted short message can be stored in the short message service center when the notification is carried in multiple short messages.

Embodiment 6 As shown in Fig. 7, the short message service center for processing notification in this embodiment includes: a receiving unit 710, configured to receive a currently submitted short message carrying a replacement flag and an identification tag which indicates the short messages belongs to a notification; an identifying unit 720, configured to identify, based on the identification tag, that the currently submitted short message and a previously submitted short message belong to the same notification, and store the currently submitted short message without replacing the previously submitted short message. The short message service center can identify whether or not the currently submitted short message and the previously submitted short message belong to the same notification by matching the identification tags of the currently submitted short message and the previously submitted short message. If the identification tag of currently submitted short message matches that of the previously submitted short message, which means that the currently submitted short message and the previously submitted short message belong to the same notification, the short message service center will not replace the previously submitted short message with the currently submitted short message, instead stores the currently submitted short message so as to solve the problem that only the last submitted short message of the notification can be stored in the short message service center when the notification is carried in multiple short messages.

Embodiment 7 Fig. 8 shows a schematic structural diagram of the short message service center for processing notification according to this embodiment of the present invention. On the basis of the short message service center in Embodiment 6, the identifying unit 720 in this embodiment specifically includes: a determining subunit 722, configured to determine the previously submitted short message of the currently submitted short message based on the source address, the destination address and the service type carried in the currently submitted short message, when the replacement flag indicates to replace the previously submitted short message with the currently submitted short message; an identifying subunit 724, configured to identify that the currently submitted short message and the previously submitted short message belong to the same notification, if an identification tag of the previous short message matches the identification tag carried in the currently submitted short message; and a storing subunit 726, configured to store the currently submitted short message without replacing the previously submitted short message, if the identifying subunit 724 identifies that the currently submitted short message and the previously submitted short message belong to the same notification. The short message service center can identify whether or not the currently submitted short message and the previously submitted short message belong to the same notification by matching the identification tags of the currently submitted short message and the previously submitted short message. If the identification tag of currently submitted short message matches that of the previously submitted short message, which means that the currently submitted short message and the previously submitted short message belong to the same notification, the short message service center will not replace the previously submitted short message with the currently submitted short message, instead stores the currently submitted short message so as to solve the problem that only the last submitted short message of the notification can be stored in the short message service center when the notification is carried in multiple short messages.

Embodiment 8 Fig. 9 shows a schematic structural diagram of the service system for processing notification according to this embodiment of the present invention. As shown in Fig. 9, the service system for processing notification in this embodiment includes a memory 910, a processor 920 and a transmitter 930. The memory 910 is configured to store program. Specifically, the program can include program codes, which can consist of computer operating instructions. The processor 920 is configured to executive the program to generate short messages of a notification, where each one of the short messages carries a replacement flag and an identification tag which indicates the short messages belong to the notification The transmitter 930 is configured to send the generated short messages to a short message service center. The memory 910 can include high speed RAM, and also can include non-volatile memory. The processor 920 can be a central processing unit (Central Processing Unit, CPU), or application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. Further, when generating the short messages of the notification, the processor 910 can be specifically configured to split the notification into a plurality of segments, generate a plurality of short messages, where each one of the plurality of short messages carries one of the plurality of segments and the replacement tag, and assign an identification tag to each one of the plurality of short messages. Alternatively, in specific implementation, if the memory 910, the processor 920, and the transmitter 930 are implemented individually, then the memory 910, the processor 920 and the transmitter 930 can communicate via a bus. The bus can be industry standard architecture (Industry Standard Architecture, ISA) bus, peripheral component interconnect (Peripheral Component Interconnect, PCI) bus or extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus etc. The bus can be divided into address bus, data bus and control bus etc. For convenient representation, the bus is only represented by a single thick line, but does not mean there is only one bus or one kind of bus.

Alternatively, in specific implementation, if the memory 910, the processor 920 and the transmitter 930 are integrated in a single chip, then the memory 910, the processor 920 and the transmitter 930 can communicate via internal interface. The service system in this embodiment can submit a short message carrying an identification tag to the short message service center. By the identification tag, short messages belong to the same notification can be easily identified so as to solve the problem that only the last submitted short message of the notification can be stored in the short message service center when the notification is carried in multiple short messages.
Embodiment 9 Fig. 10 shows a schematic structural diagram of the short message service center for processing notification according to this embodiment of the present invention. As shown in Fig. 10, the short message service system for processing notification in this embodiment includes a memory 1010, a processor 1020, a receiver 1030 and a storage 1040. The receiver 1030 is configured to receive a currently submitted short message carrying a replacement flag and an identification tag which indicates the currently submitted short message belongs to a notification. The memory 1010 is configured to store program. Specifically, the program can include program codes, which can consist of computer operating instructions. The storage 1040 is configured to store the short messages of the notification to be sent to user. The processor 1020 is configured to executive the program stored in the memory 1010 to identify, based on the identification tag, that the currently submitted short message received by the receiver 1030 and a previously submitted short message stored in the storage 1040 belong to the same notification, and store the currently submitted short message into the storage 1040 without replacing the previously submitted short message. The memory 1010 can include high speed RAM, and also can include non-volatile memory. The processor 1020 can be a central processing unit (Central Processing Unit, CPU), or application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.
Further, when identifying, based on the identification tag, that the currently submitted short message received by the receiver 1030 and a previously submitted short message stored in the storage 1040 belong to the same notification, the processor 1020 can be specifically configured to: determine the previously submitted short message of the currently submitted short message based on a source address, a destination address and a service type carried in the currently submitted short message, when the replacement flag indicates to replace the previously submitted short message stored in the storage 1040 with the currently submitted short message received by the receiver 1030; identify that the currently submitted short message and the previously submitted short message belong to the same notification if an identification tag of the previously submitted short message matches the identification tag carried in the currently submitted short message.

Alternatively, in specific implementation, if the memory 1010, the processor 1020, the receiver 1030 and the storage 1040 are implemented individually, then the memory 1010, the processor 1020, the receiver 1030 and the storage 1040 can communicate via a bus. The bus can be industry standard architecture (Industry Standard Architecture, ISA) bus, peripheral component interconnect (Peripheral Component Interconnect, PCI) bus or extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus etc. The bus can be divided into address bus, data bus and control bus etc. For convenient representation, the bus is only represented by a single thick line, but does not mean there is only one bus or one kind of bus. Alternatively, in specific implementation, if the memory 1010, the processor 1020, the receiver 1030 and the storage 1040 are integrated in a single chip, then the memory 1010, the processor 1020, the receiver 1030 and the storage 1040 can communicate via internal interface.
The short message service center in this embodiment can identify whether or not the currently submitted short message and the previously submitted short message belong to the same notification by matching the identification tags of the currently submitted short message and the previously submitted short message. If the identification tag of currently submitted short message matches that of the previously submitted short message, which means that the currently submitted short message and the previously submitted short message belong to the same notification, the short message service center will not replace the previously submitted short message with the currently submitted short message, instead stores the currently submitted short message so as to solve the problem that only the last submitted short message of the notification can be stored in the short message service center when the notification is carried in multiple short messages.

It should be appreciated by persons skilled in the art that, all or a part of the steps in the method of the above embodiments may be completed by relevant hardware under the instruction of a program, and the program may be stored in a computer readable storage medium, when the program is executed, the steps of the above method embodiments are performed. The storage medium may be, such as a read only memory (ROM)/random access memory (RAM), a floppy disk, or an optical disk. It should be noted that the above embodiments are merely provided for describing the technical solutions of the present invention, but not intended to limit the present invention. It should be understood by those of ordinary skill in the art that although the present invention has been described in detail with reference to the foregoing embodiments, modifications can be made to the technical solutions described in the foregoing embodiments, or equivalent replacements can be made to some technical features in the technical solutions, as long as such modifications or replacements do not cause the essence of corresponding technical solutions to depart from the scope of the present invention.

WE CLAIM :

1. A method for processing notification, comprising: generating, by a service system, short messages of a notification, wherein each one of the short messages carries a replacement flag and an identification tag which indicates the short messages belong to the notification; sending, by the service system, the generated short messages to a short message service center.

2. The method as claimed in claim 1, wherein the generating short messages of a notification comprises: splitting the notification into a plurality of segments; generating a plurality of short messages, wherein each one of the plurality of short messages carries one of the plurality of segments and the replacement tag; and assigning an identification tag to each one of the plurality of short messages.

3. The method as claimed in claims 1 or 2, wherein the identification tag is carried in a User Data Head of the short message.

4. The method as claimed in claims 1 or 2, wherein the identification tag comprises: an ID number assigned to the notification and a sequence number of the short message belonging to the notification.

5. The method as claimed in claim 4, wherein the ID number assigned to the notification is carried in UDH-Length and/or the sequence number of the short message is carried in UDH-Content.

6. A method for processing notification, comprising: receiving, by a short message service center, a currently submitted short message carrying a replacement flag and an identification tag which indicates the short message belongs to a notification; identifying, based on the identification tag, that the currently submitted short message and a previously submitted short message belong to the same notification, and storing the currently submitted short message without replacing the previously submitted short message.

7. The method as claimed in claim 6, wherein the identifying, based on the identification tag, that the currently submitted short message and a previously submitted short message belong to the same notification comprises: when the replacement flag indicates to replace a previously submitted short message with the currently submitted short message, determining the previously submitted short message based on a source address, a destination address and a service type carried in the currently submitted short message; determining whether an identification tag of the previous short message matches the identification tag carried in the currently submitted short message; if matching, identifying that the currently submitted short message and the previously submitted short message belong to the same notification.

8. The method as claimed in claim 6, wherein the identification tag comprises: an ID number assigned to the notification and a sequence number of the short message belonging to the notification.

9. The method as claimed in any one of claims 6-8, wherein the identification tag is carried in a User Data Head of the short message.

10. The method as claimed in claim 8, wherein the ID number assigned to the notification is carried in UDH-Length and/or the sequence number of the short message is carried in UDH-Content.

11. A service system for processing notifications, comprising: a generating unit, configured to generate short messages of a notification, wherein each one of the short messages carries a replacement flag and an identification tag which indicates that the short messages belong to the notification; and a sending unit, configured to send the generated short messages to a short message service center.

12. The apparatus as claimed in claim 11, wherein the generating unit comprises: a splitting subunit, configured to split the notification into a plurality of segments; a generating subunit, configured to generated a plurality of short messages, wherein each one of the plurality of short messages carries one of the plurality of segments and the replacement tag; and an assigning subunit, configured to assign an identification tag to each one of the plurality of short messages.

13. A short message service center for processing notification, comprising: a receiving unit, configured to receive a currently submitted short message carrying a replacement flag and an identification tag which indicates the currently submitted short message belongs to a notification; an identifying unit, configured to identify, based on the identification tag, that the currently submitted short message and a previously submitted short message belong to the same notification, and store the currently submitted short message without replacing the previously submitted short message.

14. The short message service center as claimed in claim 13, wherein the identifying unit comprises: a determining subunit, configured to, when the replacement flag indicates to replace a previously submitted short message with the currently submitted short message, determine the previously submitted short message of the currently submitted short message based on a source address, a destination address and a service type carried in the currently submitted short message; an identifying subunit, configured to, if an identification tag of the previously submitted short message matches the identification tag carried in the currently submitted short message, identify that the currently submitted short message and the previously submitted short message belong to the same notification; and a storing subunit, configured to store the currently submitted short message without replacing the previously submitted short message, if the identifying subunit identifies that the currently submitted short message and the previously submitted short message belong to the same notification.