CN101998305A - Short message scheduling method and system - Google Patents
Short message scheduling method and system Download PDFInfo
- Publication number
- CN101998305A CN101998305A CN2009101664545A CN200910166454A CN101998305A CN 101998305 A CN101998305 A CN 101998305A CN 2009101664545 A CN2009101664545 A CN 2009101664545A CN 200910166454 A CN200910166454 A CN 200910166454A CN 101998305 A CN101998305 A CN 101998305A
- Authority
- CN
- China
- Prior art keywords
- scheduling
- module
- action
- class
- short message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 230000009471 action Effects 0.000 claims description 156
- 230000004044 response Effects 0.000 claims description 9
- 230000002452 interceptive effect Effects 0.000 claims description 7
- 230000005540 biological transmission Effects 0.000 abstract 1
- 230000008569 process Effects 0.000 description 14
- 238000004891 communication Methods 0.000 description 7
- 238000007726 management method Methods 0.000 description 7
- 239000000243 solution Substances 0.000 description 6
- 239000003637 basic solution Substances 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000012360 testing method Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 239000003795 chemical substances by application Substances 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003111 delayed effect Effects 0.000 description 1
- 238000002716 delivery method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses a short message scheduling method. The method comprises the following steps of: setting a scheduling class corresponding to a user for an access module and a transmitting module; transmitting the set scheduling class to the access module, the transmitting module and a core scheduling module; and controlling the access module and the transmitting module to uniformly schedule a short message which is transmitted by the user and corresponds to the scheduling class according to a received scheduling class by using the core scheduling module according to the received scheduling class. The embodiment of the invention also discloses a short message scheduling system. The system comprises a portal module, the core scheduling module, the access module and the transmitting module. By the method and the system, the transmission of the short message of the user can be uniformly scheduled.
Description
Technical Field
The present invention relates to mobile communication technologies, and in particular, to a method and a system for scheduling short messages.
Background
With the rapid development of modern communication technology, the appearance of Short Message Service (SMS) service brings great convenience to people's daily life, and thus, the SMS service has been used by more and more users, and has also become an important service in modern communication networks. Under the existing conditions, the short message service can utilize the existing rapidly developed Internet (Internet) and mobile network resources to provide comprehensive internal and external information services for various enterprises.
In the prior art, a basic solution of the short message service generally adopts a scheme with a four-layer structure. Fig. 1 is a schematic structural diagram of a basic solution of a short message service in the prior art. As shown in fig. 1, the solution described above may include the following four-layer structure:
1) a service application layer;
the service application layer mainly refers to a processing layer under various application environments. The service application layer is mainly used for providing basic service logic and service functions for users. Specifically, the service application layer may be: various industrial Service application systems, corporate clients (ECs), Service Providers (SPs), etc.
2) A network access layer;
the network access layer is mainly used for accessing various industry application systems to an operator network. Specifically, the network access layer may be: an ISMG (Internet Short message gateway), an industry gateway (IAGW) or a service access agent part of the IAGW (IAGW-A, namely an A module of the IAGW). The short message gateway can be a gateway of a dream network in the prior art.
3) A service management layer;
the service management layer (also referred to as a network management layer) is mainly used for the management of service items and subscription relationships by operators. Specifically, the service management layer may be: a Mobile Information Service Center (MISC), a traffic control part of the IAGW (IAGW-M, i.e., an M-module of the IAGW), and the like.
4) A network issuing layer;
the network delivery layer mainly refers to a device for receiving and sending short messages, and specifically, the network delivery layer may be: a Short Message Service Center (SMSC), a wireless network, etc.
As shown in fig. 1, in the basic solution of the short message service, the network access layer and the service management layer may be disposed in different devices, or may be integrated in the same device (e.g., IAGW and/or ISMG). Therefore, the network access layer and the service management layer may be collectively referred to as an access module (e.g., IAGW, ISMG, etc.) in the communication network system, and the network delivery layer may be referred to as a delivery module (e.g., SMSC, etc.) in the communication network system.
In the prior art, the short message gateway/industry gateway (i.e., the short message gateway and/or the industry gateway, the same below) can generally set different priorities for different users according to a preset condition or a preset policy. The short messages submitted by the users with high priority have high priority, so the short messages are preferentially tried to be submitted to the short message center for issuing, and the short messages submitted by the industrial customers with high priority are enabled to obtain differentiated services on the short message gateway/the industrial gateway. However, in the existing technical solution, although the Short Message gateway/industry gateway and the Short Message center can communicate through a standard Peer to Peer Short Message protocol (SMPP), the Short Message gateway/industry gateway and the Short Message center are separated and independent from each other in terms of user priority control, and the Short Message gateway/industry gateway does not send the user priority set by the Short Message gateway/industry gateway to the Short Message center, so that a user with high priority on the Short Message gateway/industry gateway cannot continuously obtain differentiated services on the Short Message center, and when the phenomena that the success rate of Message distribution is low, the current limit of Message and the like affect the normal operation of the network occur in the communication network, the user with high priority cannot be distinguished from the user with low priority on the important indexes such as the success rate of Message distribution and the like, thereby affecting the user experience of the user with high priority, causing the high priority users to be dissatisfied to some extent.
Secondly, the short message gateway, the industry gateway and the short message center generally have corresponding retransmission scheduling mechanisms. The short message gateway and the industry gateway only retransmit a few errors (for example, no response of an interface, an error of the interface and the like); although the retransmission scheduling mechanism of the short message center is relatively perfect, retransmission strategies can be configured for errors from number 1 to number 255, but a space for optimization still exists.
In the prior art, network elements such as a short message gateway, an industry gateway, a short message center and the like all independently provide an error tracking and analyzing mechanism, and error codes of the network elements are also independently defined, so that in the actual maintenance work, it is difficult to clearly locate which link the problem occurs.
In addition, in the prior art, the reports of the network elements such as the short message gateway, the industry gateway, the short message center and the like are also independent and not unified, and the report of each network element can only reflect the message state of the current network element but not the overall operation state, so that the sending speed of the short message in the short message sending process cannot be controlled, and the adjustment and configuration of the sending speed of the test short message cannot be realized, so as to meet the actual test requirements of different services.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and a system for scheduling short messages, so as to uniformly schedule short message delivery of a user.
In order to achieve the above purpose, the technical solution in the embodiment of the present invention is realized as follows:
a method for scheduling short messages comprises the following steps:
setting scheduling classes corresponding to the user for the access module and the issuing module respectively;
respectively sending the set scheduling classes to an access module, a distribution module and a core scheduling module;
and the core scheduling module controls the access module and the issuing module to uniformly schedule the short messages sent by the users corresponding to the scheduling class according to the received scheduling class.
The setting of the scheduling class corresponding to the user for the access module and the issuing module respectively comprises the following steps:
setting an access module scheduling class corresponding to the user for the access module, and setting an issuing module scheduling class corresponding to the user for the issuing module;
the access module scheduling class and the issuing module scheduling class are the same scheduling class or different scheduling classes;
the step of respectively sending the set scheduling classes to the access module, the issuing module and the core scheduling module comprises the following steps:
and sending the access module scheduling class to an access module and a core scheduling module, and sending the issuing module scheduling class to an issuing module and a core scheduling module.
The setting of the scheduling classes corresponding to the users for the access module and the issuing module respectively comprises the following steps:
and respectively setting scheduling classes corresponding to the user for the access module and the issuing module according to the priority of the user.
The setting of the scheduling class corresponding to the user for the access module and the issuing module according to the priority of the user respectively comprises the following steps:
presetting one or more scheduling classes;
determining the corresponding relation between the users with different priorities and the set scheduling classes;
and respectively setting scheduling classes corresponding to the users for the access module and the issuing module according to the corresponding relation.
The scheduling classes include: more than two preset scheduling actions and scheduling strategies related to each scheduling action;
the scheduling policy is execution information of each scheduling action in the scheduling class.
The preset scheduling action is any one of the following scheduling actions:
scheduling action 1: sending the short message by using a conventional short message sending method;
scheduling action 2: issuing an original short message in a lightning short message form;
scheduling action 3: issuing a prompt short message in the form of a lightning short message;
scheduling action 4: actively calling a receiving end user through an interactive voice response system, and reminding the receiving end user to listen to an original short message;
scheduling action 5: actively calling a receiving end user through an interactive voice response system, and reminding the receiving end user to listen to the prompt short message;
scheduling action 6: sending an original short message through a manual seat system;
scheduling action 7: forwarding the original short message through an e-mail system;
scheduling action 8: forwarding the original short message through an instant message system;
scheduling action 9: forwarding the original short message through an office system of a receiving end user;
scheduling action 10: finishing successfully;
scheduling action 11: ending the failure;
and either or both of the scheduling actions 10 and 11 are included in either one of the scheduling classes.
The scheduling actions in the scheduling class include: scheduling action1, scheduling action2, scheduling action4, scheduling action6, scheduling action10, and scheduling action 11;
the scheduling policy in the scheduling class is as follows:
the scheduling action1 is first performed and,
if scheduling action1 is successful, performing scheduling action 10; if the scheduling action1 fails, selecting and executing the next scheduling action according to the reason of the failure of the scheduling action 1;
the selecting and executing the next scheduling action according to the reason for the failure of scheduling action1 comprises:
when the reason for the failure of the scheduling action1 is that the memory of the receiving end is full, executing a scheduling action2 or a scheduling action 4;
when the reason of the failure of the scheduling action1 is that other errors occur at the receiving end, the scheduling action4 is executed;
when the reason for the failure of scheduling action1 is that the network has an error, performing scheduling action 11;
wherein,
if scheduling action2 is successful, performing scheduling action 10; if scheduling action2 fails, scheduling action4 is performed;
if the scheduling action4 is successful, after delaying a predetermined time, performing a scheduling action 1; if scheduling action4 fails, scheduling action6 is performed;
if scheduling action6 is successful, scheduling action10 is performed; if the scheduling action6 fails, a scheduling action11 is performed.
The scheduling actions in the scheduling class include: scheduling action1, scheduling action10, and scheduling action 11;
the scheduling policy in the scheduling class is as follows:
the scheduling action1 is first performed and,
if scheduling action1 is successful, performing scheduling action 10; if the scheduling action1 fails, judging whether a preset termination condition is met, if so, executing a scheduling action 11; if not, after delaying for a predetermined time, scheduling action1 is performed again.
The scheduling actions in the scheduling class include: scheduling action1, scheduling action6, scheduling action10, and scheduling action 11;
the scheduling policy in the scheduling class is as follows:
the scheduling action1 is first performed and,
if scheduling action1 is successful, performing scheduling action 10;
if the scheduling action1 fails, selecting and executing the next scheduling action according to the reason of the failure of the scheduling action 1;
the selecting and executing the next scheduling action according to the reason for the failure of scheduling action1 comprises:
when the reason for the failure of the scheduling action1 is that the receiving end has an error, executing a scheduling action 6;
when the reason of the failure of the scheduling action1 is the reason except that the error occurs in the receiving end, judging whether the preset termination condition is met, if so, executing a scheduling action 11; if not, after delaying for a predetermined time, scheduling action1 is performed again.
The termination conditions are as follows: a limit on the number of repeated executions of scheduling action 1; or a limit on the execution time of the scheduling class.
The core scheduling module controls the access module and the issuing module to uniformly schedule the short messages sent by the users corresponding to the scheduling class according to the received scheduling class, respectively, and the core scheduling module comprises:
the core scheduling module sends a corresponding access instruction to the access module according to the received access module scheduling class, and the access module is controlled to schedule the short message sent by the user corresponding to the scheduling class according to the received access module scheduling class through the access instruction;
and the core scheduling module sends a corresponding issuing instruction to the issuing module according to the received issuing module scheduling class, and controls the issuing module to schedule the short message sent by the user corresponding to the scheduling class according to the received issuing module scheduling class through the issuing instruction.
The method still further comprises:
when the scheduling action in the scheduling class fails, an executor of the scheduling action sends corresponding failure information to the core scheduling module; the failure information at least comprises information related to the scheduling action failure.
The embodiment of the invention also provides a short message scheduling system, which comprises: the system comprises a portal module, a core scheduling module, an access module and a distribution module;
the portal module is used for respectively setting scheduling classes corresponding to the user for the access module and the issuing module; respectively sending the set scheduling classes to the access module, the issuing module and the core scheduling module;
the core scheduling module is used for respectively controlling the access module and the issuing module to uniformly schedule the short messages sent by the users corresponding to the scheduling class according to the received scheduling class through the access instruction and the issuing instruction;
the access module is used for scheduling the short messages sent by the users corresponding to the scheduling class according to the access instruction and the received scheduling class;
and the issuing module is used for scheduling the short messages sent by the users corresponding to the scheduling class according to the issuing instruction and the received scheduling class.
The system still further includes: a standby issuing module;
the core scheduling module is also used for communicating with the standby issuing module through a customized interface and controlling the standby issuing module to schedule the corresponding short message through a standby issuing instruction;
and the standby issuing module is used for scheduling the short message corresponding to the instruction according to the standby issuing instruction.
The standby issuing module comprises:
any one or more of an interactive voice response system, a manual seating system, an email system, an instant messaging system, and a receiving end user's office system.
In summary, the embodiments of the present invention provide a method and a system for scheduling short messages. In the method and the system, the access module scheduling class and the issuing module scheduling class corresponding to the user can be respectively set for the access module and the issuing module, and the core scheduling module can respectively control the access module and the issuing module according to the received access module scheduling class and the received issuing module scheduling class, so that the uniform scheduling of the short message issuing of the same user can be realized.
Drawings
Fig. 1 is a schematic structural diagram of a basic solution of a short message service in the prior art.
Fig. 2 is a schematic structural diagram of a short message scheduling system in an embodiment of the present invention.
Fig. 3 is a flowchart of a short message scheduling method according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail with reference to the accompanying drawings and specific embodiments.
In the embodiment of the invention, a short message scheduling system is provided. Fig. 2 is a schematic structural diagram of a short message scheduling system in an embodiment of the present invention. As shown in fig. 2, the system includes: the system comprises a Portal module, a core scheduling module (kernel-Schedule), an access module and a distribution module.
The portal module is used for respectively setting scheduling classes corresponding to the user for the access module and the issuing module; respectively sending the set scheduling classes to the access module, the issuing module and the core scheduling module;
the core scheduling module is used for respectively controlling the access module and the issuing module to uniformly schedule the short messages sent by the users corresponding to the scheduling class according to the received scheduling class through the access instruction and the issuing instruction;
the access module is used for scheduling the short messages sent by the users corresponding to the scheduling class according to the access instruction and the received scheduling class;
and the issuing module is used for scheduling the short messages sent by the users corresponding to the scheduling class according to the issuing instruction and the received scheduling class.
In addition, the short message scheduling system can also comprise a standby issuing module. The core scheduling module can be communicated with the standby issuing module through a customized interface and controls the standby issuing module to schedule the corresponding short message through a standby issuing instruction;
and the standby issuing module is used for scheduling the short message corresponding to the command according to the standby issuing command.
In the embodiment of the invention, the core scheduling module can communicate with the access module and the issuing module through an SMPP protocol; the standby issuing module may include: any one or more of an Interactive Voice Response (IVR) system, a human agent system, an email system, an instant messaging system, an office system of a receiving end user, and the like. Taking fig. 2 as an example, the standby issuing module in fig. 2 includes an IVR system and a manual seat system.
In addition, the specific implementation manner of respectively setting the scheduling class corresponding to the user for the access module and the delivery module according to the priority of the user, and the specific implementation manner of controlling the access module and the delivery module by the core scheduling module to uniformly schedule the short messages sent by the user corresponding to the scheduling class according to the received scheduling class will be described in detail in the following description of the short message scheduling method provided in the embodiment of the present invention.
Based on the short message scheduling system, in the embodiment of the invention, a short message scheduling method is also provided. In the scheduling method, the scheduling classes corresponding to the user can be firstly respectively set for the access module and the issuing module; then the set scheduling classes are respectively sent to an access module, a distribution module and a core scheduling module; and the core scheduling module controls the access module and the issuing module to uniformly schedule the short messages sent by the users corresponding to the scheduling class according to the received scheduling class.
Fig. 3 is a flowchart of a short message scheduling method according to an embodiment of the present invention. As shown in fig. 3, the method for scheduling short messages in the embodiment of the present invention includes the following steps:
In a common communication network system, a short message channel is generally used to send a short message that a user needs to send, and when sending a short message through the short message channel fails, the system can process the short message that fails to be sent by adopting various technical means according to specific error reasons. For example, the short message gateway and the industry gateway can resend the short message failed in sending according to the error prompts such as no response of an interface, interface error and the like, and the short message center can respectively configure corresponding resending strategies according to errors from number 1 to number 255. Generally, the above various technical means for sending short messages may be collectively referred to as scheduling operation.
In the embodiment of the invention, the scheduling of the short message of the user can be realized by using various preset scheduling actions. For example, for a short message (i.e., an MT service, such as a short message group sending service, etc.) sent by a user (e.g., a group user with a high priority) to a receiving end user, when a short message that the user needs to send fails to be sent in a short message channel, the short message that fails to be sent can be scheduled according to an error reason. In an embodiment of the present invention, the scheduling operation used in performing the scheduling includes:
1) scheduling Action 1(Action 1): and sending the short message by using a conventional short message sending method.
In the scheduling action1, a conventional short message issuing method in the field can be used to directly issue the short message required to be sent by the user to the corresponding receiving end user through the access module and the issuing module.
2) Scheduling Action 2(Action 2): the original short message is issued in the form of lightning short message (i.e. flash message).
The lightning short message is a short message service promoted by China mobile, and is also called a hands-free short message. The difference between the lightning short message and the common short message is that: after receiving the lightning short message, the user directly displays the content of the lightning short message on a screen of a mobile terminal (for example, a mobile phone) of the user, and the user does not need to enter a corresponding menu for reading through operation.
In the scheduling action2, the original short message which is required to be sent by the user is sent to the corresponding receiving terminal in a lightning short message mode. For example, if the access module executes the scheduling action2, the access module issues the original short message to the issuing module in the form of a lightning short message, and then the issuing module issues the lightning short message to a receiving end user of the original short message; if the dispatching action2 is executed by the issuing module, the issuing module directly issues the original short message to a receiving end user of the original short message in the form of a lightning short message.
3) Scheduling Action 3(Action 3): and issuing a prompt short message in a lightning short message mode.
In the scheduling action3, a prompt short message corresponding to the original short message which needs to be sent by the user is sent to the corresponding receiving terminal in a lightning short message mode, so as to prompt the receiving terminal to receive the original short message. The manner of executing the scheduling action3 by the access module and the issue module is similar to the manner of executing the scheduling action2, and is not described herein again.
4) Scheduling Action 4(Action 4): and actively calling the receiving end user through the IVR system to remind the receiving end user to listen to the original short message.
In the scheduling action4, the IVR system actively calls the receiving end user to remind the receiving end user to listen to the original short message, i.e. the IVR system directly plays the content of the original short message in a voice manner, so that the receiving end user can obtain the content of the original short message.
Therefore, in the scheduling action4, the IVR system can actively call the receiving end user, and directly play the original short message content in the form of voice, so that the user can obtain the original information content. For example, if the access module executes the scheduling action4, the access module can send the original short message to the core scheduling module, and the core scheduling module sends the original short message and the related instruction to the IVR system through the customized interface, so that the IVR system actively calls the receiving-end user and directly plays the content of the original short message in a voice manner; similarly, if the dispatching action4 is executed by the issuing module, the issuing module can send the original short message to the core dispatching module, and the core dispatching module sends the original short message and the related instruction to the IVR system through the customized interface, so that the IVR system actively calls the receiving end user and directly plays the content of the original short message in a voice mode.
5) Scheduling Action 5(Action 5): and actively calling the receiving end user through the IVR system to remind the receiving end user to listen to the prompt short message.
In the scheduling action5, the IVR system can actively call the receiving end user to remind the receiving end user to listen to the prompt short message, i.e. the IVR system directly plays the content of the prompt short message in a voice mode to prompt the receiving end user to receive the original short message. The manner of executing the scheduling action5 by the access module and the issue module is similar to the manner of executing the scheduling action4, and is not described herein again.
6) Scheduling Action 6(Action 6): and sending the original short message through the manual seat system.
In the scheduling action6, the original short message may be forwarded to a manual position system, and the manual position system sends the original short message to a receiving end user of the original short message in a manual manner (for example, telephone notification, written notification, manual notification, or the like). The manner of executing the scheduling action6 by the access module and the issue module is similar to the manner of executing the scheduling action4, and is not described herein again.
7) Scheduling Action 7(Action 7): and forwarding the original short message through an electronic Mail (E-Mail) system.
In the scheduling action7, the original short message can be forwarded to an email system, and the email system sends the original short message to a receiving end user of the original short message through an email. The manner of executing the scheduling action7 by the access module and the issue module is similar to the manner of executing the scheduling action4, and is not described herein again.
8) Scheduling Action 8(Action 8): and forwarding the original short message through an Instant Messaging (IM) system.
In the scheduling action8, the original short message can be forwarded to an instant message system, and the instant message system sends the original short message to a receiving end user of the original short message in an instant message manner. The manner of executing the scheduling action8 by the access module and the issue module is similar to the manner of executing the scheduling action4, and is not described herein again.
9) Scheduling Action 9(Action 9): and forwarding the original short message through an Office (OA) system of the receiving end user.
When the receiving end user of the original short message has a corresponding office system, the original short message can be forwarded to the office system of the receiving end user by using the scheduling action9, and the original short message is sent to the receiving end user by the office system through various modes such as instant messages, internal mails and the like. The manner of executing the scheduling action9 by the access module and the issue module is similar to the manner of executing the scheduling action4, and is not described herein again.
10) Scheduling Action10 (Action 10): and finishing successfully.
When the scheduling action10 is executed, a successful charging ticket can be output, and the whole process is ended. The scheduling action10 can be used when the original short message is successfully received by the receiving end user.
11) Scheduling Action11 (Action 11): and ending the failure.
When the scheduling action11 is executed, a failure charging ticket can be output, and the whole process is ended. The scheduling action11 can be used when the original short message is sent in error, so that the original short message is not successfully received by the receiving end user.
The above lists are some scheduling methods commonly used in the embodiments of the present invention. In the technical solution of the present invention, other scheduling actions may also be set according to actual needs, and are not described herein again.
In addition, in the embodiment of the present invention, if a certain scheduling action fails, that is, the scheduling of the short message cannot be completed (for example, the short message retransmission fails), the scheduling action may also return a failure message (for example, information such as a failure reason) to a corresponding module (for example, an access module, a delivery module, a core scheduling module, etc.) in the system according to the needs of the actual situation, so that the system can locate the position and reason of the error.
In the prior art, an access module (e.g., a short message gateway, an industry gateway, etc.) and an issuing module (e.g., a short message center, etc.) in a communication network system are separated and independent from each other in terms of control of user priority, that is, the access module and the issuing module both use independent scheduling actions.
In the embodiment of the invention, various scheduling actions can be preset, and the scheduling classes corresponding to the user are respectively set for the access module and the issuing module, so that the issuing of the short messages of the user is uniformly scheduled. Preferably, in the embodiment of the present invention, a plurality of scheduling actions may be preset, and the scheduling classes corresponding to the user are respectively set for the access module and the delivery module according to the priority of the user, so as to implement uniform scheduling for delivering the short message of the user. The scheduling class may include more than two scheduling actions and a scheduling policy associated with each scheduling action, and the scheduling policy is execution information of each scheduling action in the scheduling class. Wherein the execution information may include: information such as the execution order, execution conditions, and/or execution time of each scheduling action in the scheduling class. Each scheduling action in the scheduling class may be executed according to a corresponding scheduling policy sequence, and therefore, in the embodiment of the present invention, the scheduling class may also be regarded as a scheduling action set formed by a plurality of scheduling actions connected in series (the connection is used to indicate a precedence relationship between the scheduling actions). Wherein, each scheduling action in the scheduling class may be partially the same or all the same, or may be completely different scheduling actions; however, any one scheduling class necessarily includes either or both of scheduling action10 and scheduling action11 to end the entire flow. In the embodiment of the present invention, the same scheduling class may include 255 scheduling actions at most, that is, a concatenation of 255 scheduling actions may be supported at most.
In order to more clearly introduce the technical solution of the present invention, several scheduling classes in the embodiment of the present invention will be described as an example below.
First, first scheduling class.
In the scheduling class, 6 scheduling actions can be included: scheduling action1, scheduling action2, scheduling action4, scheduling action6, scheduling action10, and scheduling action11 described above.
In the scheduling class, the scheduling policy is: scheduling action1 is first performed and the subsequently performed scheduling action is determined based on the subsequently occurring actual situation.
Specifically, the method comprises the following steps:
1. for scheduling action 1:
1.1) if scheduling action1 succeeds, scheduling action10 is performed.
Namely, if the short message is successfully sent by using the conventional short message sending method, the scheduling action10 is executed, the whole process is ended, and the successful charging ticket is output.
1.2) if the scheduling action1 fails, selecting and executing the next scheduling action according to the reason of the failure; specifically, the method comprises the following steps:
1.2.1) when the failure reason is that the memory of the receiving end is full, executing a scheduling action2, namely issuing the original short message to a receiving end user in the form of a lightning short message;
in addition, in another embodiment of the present invention, when the failure cause is that the memory of the receiving end is full, the scheduling action4 can also be executed, that is, the receiving end user is reminded to delete the short message in the memory of the receiving end in an active calling mode in the IVR system, so as to reserve a proper storage space to receive the short message to be sent to the receiving end user;
1.2.2) when the failure reason is that other errors (for example, the signal of the receiving end is poor) occur at the receiving end, executing a scheduling action4, namely reminding the receiving end user to listen to the original short message in an active calling mode in the IVR system;
1.2.3) when the failure reason is that the network sending the short message has an error, executing a scheduling action11, namely ending the whole process, and outputting a failure charging ticket and failure related information;
2. for scheduling action 2:
2.1) if scheduling action2 succeeds, scheduling action10 is performed.
Namely, if the original short message is successfully issued in the form of the lightning short message, the dispatching action10 is executed, the whole process is ended, and a successful charging ticket is output.
2.2) if scheduling action2 fails, performing scheduling action 4;
namely, if the original short message fails to be sent in the form of the lightning short message, the dispatching action4 is executed, namely, the receiving end user is reminded to listen to the original short message in an active calling mode in the IVR system.
3. For scheduling action 4:
3.1) if the scheduling action4 succeeds, after a predetermined time delay, scheduling action1 is performed.
If the scheduling action4 is successful, that is, the receiving end user receives the active call of the IVR system, after delaying for a predetermined time (for example, 5 minutes), the scheduling action1 is executed, that is, the original short message is delivered to the receiving end user again by using a conventional short message delivery method.
3.2) if scheduling action4 fails, performing scheduling action 6;
if the dispatching action4 fails, that is, the active calling of the receiving end user by the IVR system is unsuccessful, the dispatching action6 is executed, that is, the original short message is issued to the receiving end user in a manual seat mode.
4. For scheduling action 6:
4.1) if the scheduling action6 is successful, a scheduling action10 is performed.
If the dispatching action6 is successful, namely the original short message is successfully issued to the receiving end user in an artificial seat mode, the dispatching action10 is executed, namely a successful charging ticket is output, and the whole process is ended.
4.2) if the scheduling action6 fails, a scheduling action11 is performed.
If the dispatching action6 fails, that is, the original short message is unsuccessfully sent to the receiving end user in an artificial seat mode, the dispatching action11 is executed, that is, a failure charging ticket is output, and the whole process is ended.
5. For the scheduling action 10:
according to the content of the scheduling action10, after the scheduling action10 is executed, a successful charging ticket is output, and the whole process is ended.
6. For scheduling action 11:
according to the content of the scheduling action11, after the scheduling action11 is executed, the failed charging ticket is output, and the whole process is ended. In the scheduling action11, information on failure (for example, information on the failure cause) may be output as needed in actual circumstances.
Second, second scheduling class.
In the scheduling class, the following may be included: scheduling action1, scheduling action10, and scheduling action 11; and the scheduling policy in the scheduling class is: firstly, scheduling action1 is executed, and corresponding scheduling action is executed according to the subsequent actual situation. Specifically, the method comprises the following steps:
for scheduling action 1:
1.1) if scheduling action1 succeeds, scheduling action10 is performed.
Namely, if the short message is successfully sent by using the conventional short message sending method, the scheduling action10 is executed, the whole process is ended, and the successful charging ticket is output.
1.2) if the scheduling action1 fails, judging whether a termination condition is met, if so, executing a scheduling action 11; if not, after a predetermined time (e.g., 5 minutes) is delayed, scheduling action1 is performed again.
Wherein, the termination condition can be preset according to the actual application condition. In the embodiment of the present invention, the termination condition may be a limit on the number of times of repeatedly executing the scheduling action1 (for example, when the scheduling action1 has been repeatedly executed 5 times, the termination condition is considered to be satisfied), may also be a limit on the execution time of the scheduling class (for example, when the scheduling action1 is executed for the first time by the scheduling class, and when the timing exceeds a predetermined timing, the termination condition is considered to be satisfied), and may also be another limit condition, which is not described herein again.
Therefore, in the present scheduling class, when scheduling action1 fails and the termination condition is not satisfied, scheduling action1 is repeatedly performed after delaying for a predetermined time; and when the scheduling action1 fails and the termination condition is met, executing a scheduling action11, ending the whole process and outputting a failure charging ticket.
As can be seen from the above, in the scheduling class, when the receiving end user does not successfully receive the original short message, the scheduling action1 may be repeatedly executed after a certain time interval until the receiving end user successfully receives the original short message or the termination condition is met.
And thirdly, scheduling in a third class.
In the scheduling class, the following may be included: scheduling action1, scheduling action6, scheduling action10, and scheduling action 11; and the scheduling policy in the scheduling class is: firstly, scheduling action1 is executed, and corresponding scheduling action is executed according to the subsequent actual situation. Specifically, the method comprises the following steps:
for scheduling action 1:
1.1) if scheduling action1 succeeds, scheduling action10 is performed.
1.2) if the scheduling action1 fails, selecting and executing the next scheduling action according to the failure reason; specifically, the method comprises the following steps:
1.2.1) when the reason of the failure of the scheduling action1 is that the receiving end has errors (for example, the memory of the receiving end is full), executing a scheduling action6, namely directly sending the original short message to a receiving end user in a manual seat mode;
1.2.2) when the reason of the failure of the scheduling action1 is the reason except the error of the receiving end (for example, the error of the network sending the short message), judging whether the preset termination condition is met, if so, executing a scheduling action 11; if not, after delaying the preset time (for example, 5 minutes), executing the scheduling action1 again, namely, sending the original short message to the receiving end user again by using the conventional short message sending method again.
The above description is several scheduling classes that may be used in the specific embodiment of the present invention, and the system may set the scheduling classes corresponding to the users for the access module and the issue module, respectively. For example, the system may set the scheduling classes corresponding to the users for the access module and the delivery module according to the priorities of the users. Specifically, in the embodiment of the present invention, one or more scheduling classes may be preset according to actual requirements, and a correspondence between users with different priorities and the set scheduling classes may be determined, so that scheduling classes corresponding to respective users may be set for the access module and the delivery module according to the correspondence.
Taking the three scheduling classes described above as an example, after the three scheduling classes are preset according to the method, the corresponding relationships between users with different priorities and the three scheduling classes may be preset, for example, the corresponding relationship is: users with high priority correspond to the third scheduling class, users with medium priority correspond to the first scheduling class, and users with low priority correspond to the second scheduling class. Therefore, if the user of the sent short message is a user with high priority, the system respectively sets a third scheduling class corresponding to the user for the access module and the issuing module; if the user of the sent short message is a user with a medium priority, the system respectively sets a first scheduling class corresponding to the user for the access module and the issuing module; if the user of the sent short message is the user with low priority, the system respectively sets a second scheduling class corresponding to the user for the access module and the issuing module.
In addition, in a specific practical application, other types of scheduling classes may also be set according to the requirements of the users and the priorities of the users, and the specific setting manner and the specific contents of the scheduling classes are not described herein again.
In the embodiment of the invention, the scheduling classes corresponding to the user can be respectively set for the access module and the issuing module according to the priority of the user, so that the issuing of the short message of the user can be uniformly scheduled. The scheduling class set for the access module may be referred to as an access module scheduling class, and the scheduling class set for the delivery module may be referred to as a delivery module scheduling class, that is, the access module scheduling class corresponding to the user may be set for the access module according to the priority of the user, and the delivery module scheduling class corresponding to the user may be set for the delivery module according to the priority of the user. The access module scheduling class and the issuing module scheduling class can use the three scheduling classes introduced above, and can also use other scheduling classes set according to actual conditions; in addition, for the same user, the set access module scheduling class and the set delivery module scheduling class may be the same scheduling class or different scheduling classes.
And step 302, respectively sending the set scheduling classes to the access module, the issuing module and the core scheduling module.
In this step, when the access module scheduling class and the delivery module scheduling class are the same scheduling class, the scheduling class can be directly and respectively sent to the access module, the delivery module and the core scheduling module; and when the access module scheduling class and the issuing module scheduling class are different scheduling classes, the access module scheduling class can be sent to the access module and the core scheduling module, and the issuing module scheduling class can be sent to the issuing module and the core scheduling module.
And 303, the core scheduling module controls the access module and the issuing module to uniformly schedule the short messages sent by the users corresponding to the scheduling class according to the received scheduling class.
In the embodiment of the invention, the core scheduling module can be used for respectively controlling the access module and the issuing module according to the received scheduling class, thereby realizing the uniform scheduling of issuing the short messages of the same user.
Specifically, the core scheduling module may communicate with the access module in the SMPP protocol, and send a corresponding access instruction (for example, some existing instructions in the SMPP protocol or newly set instructions corresponding to the access module scheduling class) to the access module according to the received access module scheduling class, so as to control the access module to schedule the short message sent by the user corresponding to the scheduling class according to the received access module scheduling class through the access instruction, that is, the access module executes a corresponding scheduling action in the scheduling class on the short message sent by the user corresponding to the scheduling class according to the received access instruction and the received access module scheduling class; similarly, the core scheduling module may also communicate with the delivery module through the SMPP protocol, and send a corresponding delivery instruction (for example, some existing instructions in the SMPP protocol or newly set instructions corresponding to the delivery module scheduling class) to the delivery module according to the received delivery module scheduling class, so that the delivery module is controlled by the delivery instruction to schedule the short message sent by the user corresponding to the scheduling class according to the received delivery module scheduling class. By the above mode, the core scheduling module can realize the uniform scheduling of the short message issuing of the same user.
In addition, because some scheduling actions in the set scheduling classes may need to schedule the short message through a standby delivery module (e.g., an IVR system, an artificial seat system, etc.), the core scheduling module may further communicate with the standby delivery module through a customized interface according to the scheduling actions in the corresponding scheduling classes, and send corresponding standby delivery instructions (e.g., preset instructions corresponding to the scheduling actions) to the standby delivery module according to the scheduling actions, so as to control the standby delivery module to execute the corresponding scheduling actions through the standby delivery instructions, and send corresponding information (e.g., information of success or failure of the scheduling actions) returned by the standby delivery module to the access module or the delivery module, thereby completing the scheduling of the short message according to the corresponding scheduling classes.
In addition, when the scheduling action in the scheduling class fails, an executor of the scheduling action (e.g., the access module, the delivery module, the standby delivery module, etc.) sends corresponding failure information to the core scheduling module, where the failure information at least includes information related to the scheduling action failure (e.g., information about time, location, reason, etc. of the scheduling failure), and therefore, the core scheduling module can know the location and reason of the error according to the failure information. For example, when a certain scheduling action in the scheduling class executed in the access module fails, the access module sends corresponding failure information to the core scheduling module; similarly, the core scheduling module can also receive failure information sent by other modules such as the issuing module and the standby issuing module, so that the core scheduling module can quickly locate the error link according to actual needs, thereby realizing unified full-flow tracking.
In the above short message scheduling method, because the access module scheduling class and the delivery module scheduling class are respectively set for the access module and the delivery module according to the same user, the short message delivery of the same user can be uniformly scheduled; meanwhile, the system can also carry out different scheduling (namely scheduling by using different scheduling classes) on the short messages which need to be issued by the users according to the priorities of the users, thereby realizing differentiated services, meeting the requirements of the users with high priorities as much as possible and improving the user experience of the users with high priorities; in addition, because the core scheduling module can also obtain the failure information sent by each module (such as an access module, a delivery module, a standby delivery module and the like), the links and reasons of errors can be quickly positioned according to actual needs, thereby realizing uniform full-flow tracking; in addition, as the core scheduling module can be used for uniformly scheduling the issuing of the short message, the core scheduling module can also generate a uniform report according to the scheduling condition of the short message and acquire the running state of the whole system through the uniform report, so that the sending speed of the short message in the short message sending process can be controlled, the adjustment and configuration of the sending speed of the test short message are realized, and the actual test requirements of different services are met.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (15)
1. A method for scheduling short messages is characterized by comprising the following steps:
setting scheduling classes corresponding to users for the access module and the issuing module respectively;
respectively sending the set scheduling classes to an access module, a distribution module and a core scheduling module;
and the core scheduling module controls the access module and the issuing module to uniformly schedule the short messages sent by the users corresponding to the scheduling class according to the received scheduling class.
2. The method of claim 1,
the setting of the scheduling class corresponding to the user for the access module and the issuing module respectively comprises the following steps:
setting an access module scheduling class corresponding to the user for the access module, and setting an issuing module scheduling class corresponding to the user for the issuing module;
the access module scheduling class and the issuing module scheduling class are the same scheduling class or different scheduling classes;
the step of respectively sending the set scheduling classes to the access module, the issuing module and the core scheduling module comprises the following steps:
and sending the access module scheduling class to an access module and a core scheduling module, and sending the issuing module scheduling class to an issuing module and a core scheduling module.
3. The method of claim 1, wherein the setting the scheduling classes corresponding to the users for the access module and the delivery module respectively comprises:
and respectively setting scheduling classes corresponding to the user for the access module and the issuing module according to the priority of the user.
4. The method of claim 3, wherein the setting the scheduling classes corresponding to the user for the access module and the delivery module according to the priority of the user respectively comprises:
presetting one or more scheduling classes;
determining the corresponding relation between the users with different priorities and the set scheduling classes;
and respectively setting scheduling classes corresponding to the users for the access module and the issuing module according to the corresponding relation.
5. The method according to any one of claims 1 to 4,
the scheduling classes include: more than two preset scheduling actions and scheduling strategies related to each scheduling action;
the scheduling policy is execution information of each scheduling action in the scheduling class.
6. The method according to claim 5, wherein the preset scheduling action is any one of the following scheduling actions:
scheduling action 1: sending the short message by using a conventional short message sending method;
scheduling action 2: issuing an original short message in a lightning short message form;
scheduling action 3: issuing a prompt short message in the form of a lightning short message;
scheduling action 4: actively calling a receiving end user through an interactive voice response system, and reminding the receiving end user to listen to an original short message;
scheduling action 5: actively calling a receiving end user through an interactive voice response system, and reminding the receiving end user to listen to the prompt short message;
scheduling action 6: sending an original short message through a manual seat system;
scheduling action 7: forwarding the original short message through an e-mail system;
scheduling action 8: forwarding the original short message through an instant message system;
scheduling action 9: forwarding the original short message through an office system of a receiving end user;
scheduling action 10: finishing successfully;
scheduling action 11: ending the failure;
and either or both of the scheduling actions 10 and 11 are included in either one of the scheduling classes.
7. The method of claim 6,
the scheduling actions in the scheduling class include: scheduling action1, scheduling action2, scheduling action4, scheduling action6, scheduling action10, and scheduling action 11;
the scheduling policy in the scheduling class is as follows:
the scheduling action1 is first performed and,
if scheduling action1 is successful, performing scheduling action 10; if the scheduling action1 fails, selecting and executing the next scheduling action according to the reason of the failure of the scheduling action 1;
the selecting and executing the next scheduling action according to the reason for the failure of scheduling action1 comprises:
when the reason for the failure of the scheduling action1 is that the memory of the receiving end is full, executing a scheduling action2 or a scheduling action 4;
when the reason of the failure of the scheduling action1 is that other errors occur at the receiving end, the scheduling action4 is executed;
when the reason for the failure of scheduling action1 is that the network has an error, performing scheduling action 11;
wherein,
if scheduling action2 is successful, performing scheduling action 10; if scheduling action2 fails, scheduling action4 is performed;
if the scheduling action4 is successful, after delaying a predetermined time, performing a scheduling action 1; if scheduling action4 fails, scheduling action6 is performed;
if scheduling action6 is successful, scheduling action10 is performed; if the scheduling action6 fails, a scheduling action11 is performed.
8. The method of claim 6,
the scheduling actions in the scheduling class include: scheduling action1, scheduling action10, and scheduling action 11;
the scheduling policy in the scheduling class is as follows:
the scheduling action1 is first performed and,
if scheduling action1 is successful, performing scheduling action 10; if the scheduling action1 fails, judging whether a preset termination condition is met, if so, executing a scheduling action 11; if not, after delaying for a predetermined time, scheduling action1 is performed again.
9. The method of claim 6,
the scheduling actions in the scheduling class include: scheduling action1, scheduling action6, scheduling action10, and scheduling action 11;
the scheduling policy in the scheduling class is as follows:
the scheduling action1 is first performed and,
if scheduling action1 is successful, performing scheduling action 10;
if the scheduling action1 fails, selecting and executing the next scheduling action according to the reason of the failure of the scheduling action 1;
the selecting and executing the next scheduling action according to the reason for the failure of scheduling action1 comprises:
when the reason for the failure of the scheduling action1 is that the receiving end has an error, executing a scheduling action 6;
when the reason of the failure of the scheduling action1 is the reason except that the error occurs in the receiving end, judging whether the preset termination condition is met, if so, executing a scheduling action 11; if not, after delaying for a predetermined time, scheduling action1 is performed again.
10. The method according to claim 8 or 9,
the termination conditions are as follows: a limit on the number of repeated executions of scheduling action 1; or a limit on the execution time of the scheduling class.
11. The method of claim 2, wherein the step of the core scheduling module controlling the access module and the delivery module to uniformly schedule the short messages sent by the users corresponding to the scheduling class according to the received scheduling class comprises:
the core scheduling module sends a corresponding access instruction to the access module according to the received access module scheduling class, and the access module is controlled to schedule the short message sent by the user corresponding to the scheduling class according to the received access module scheduling class through the access instruction;
and the core scheduling module sends a corresponding issuing instruction to the issuing module according to the received issuing module scheduling class, and controls the issuing module to schedule the short message sent by the user corresponding to the scheduling class according to the received issuing module scheduling class through the issuing instruction.
12. The method of claim 5, further comprising:
when the scheduling action in the scheduling class fails, an executor of the scheduling action sends corresponding failure information to the core scheduling module; the failure information at least comprises information related to the scheduling action failure.
13. A short message scheduling system is characterized in that the system comprises: the system comprises a portal module, a core scheduling module, an access module and a distribution module;
the portal module is used for respectively setting scheduling classes corresponding to the user for the access module and the issuing module; respectively sending the set scheduling classes to the access module, the issuing module and the core scheduling module;
the core scheduling module is used for respectively controlling the access module and the issuing module to uniformly schedule the short messages sent by the users corresponding to the scheduling class according to the received scheduling class through the access instruction and the issuing instruction;
the access module is used for scheduling the short messages sent by the users corresponding to the scheduling class according to the access instruction and the received scheduling class;
and the issuing module is used for scheduling the short messages sent by the users corresponding to the scheduling class according to the issuing instruction and the received scheduling class.
14. The system of claim 13, further comprising: a standby issuing module;
the core scheduling module is also used for communicating with the standby issuing module through a customized interface and controlling the standby issuing module to schedule the corresponding short message through a standby issuing instruction;
and the standby issuing module is used for scheduling the short message corresponding to the instruction according to the standby issuing instruction.
15. The system of claim 14, wherein the backup issue module comprises:
any one or more of an interactive voice response system, a manual seating system, an email system, an instant messaging system, and a receiving end user's office system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101664545A CN101998305A (en) | 2009-08-19 | 2009-08-19 | Short message scheduling method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101664545A CN101998305A (en) | 2009-08-19 | 2009-08-19 | Short message scheduling method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101998305A true CN101998305A (en) | 2011-03-30 |
Family
ID=43787719
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009101664545A Pending CN101998305A (en) | 2009-08-19 | 2009-08-19 | Short message scheduling method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101998305A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102364967A (en) * | 2011-11-21 | 2012-02-29 | 携程计算机技术（上海）有限公司 | Short message transmission method and system |
| CN103796182A (en) * | 2014-02-28 | 2014-05-14 | 杭州东信北邮信息技术有限公司 | Message sending system and method |
| CN109152061A (en) * | 2018-09-28 | 2019-01-04 | 彩讯科技股份有限公司 | Channel agility method, apparatus, server and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1889711A (en) * | 2005-06-29 | 2007-01-03 | 华为技术有限公司 | Information group transmitting system and method |
| CN1905408A (en) * | 2006-08-04 | 2007-01-31 | 华为技术有限公司 | Method and apparatus for monitoring message |
| CN1949894A (en) * | 2006-11-08 | 2007-04-18 | 华为技术有限公司 | Short message centre and short message for warding method |
| CN101159716A (en) * | 2007-11-16 | 2008-04-09 | 华为技术有限公司 | Gateway system and message service processing method thereof |
-
2009
- 2009-08-19 CN CN2009101664545A patent/CN101998305A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1889711A (en) * | 2005-06-29 | 2007-01-03 | 华为技术有限公司 | Information group transmitting system and method |
| CN1905408A (en) * | 2006-08-04 | 2007-01-31 | 华为技术有限公司 | Method and apparatus for monitoring message |
| CN1949894A (en) * | 2006-11-08 | 2007-04-18 | 华为技术有限公司 | Short message centre and short message for warding method |
| CN101159716A (en) * | 2007-11-16 | 2008-04-09 | 华为技术有限公司 | Gateway system and message service processing method thereof |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102364967A (en) * | 2011-11-21 | 2012-02-29 | 携程计算机技术（上海）有限公司 | Short message transmission method and system |
| CN102364967B (en) * | 2011-11-21 | 2013-11-06 | 携程计算机技术（上海）有限公司 | Short message transmission method and system |
| CN103796182A (en) * | 2014-02-28 | 2014-05-14 | 杭州东信北邮信息技术有限公司 | Message sending system and method |
| CN103796182B (en) * | 2014-02-28 | 2017-02-15 | 杭州东信北邮信息技术有限公司 | Message sending system and method |
| CN109152061A (en) * | 2018-09-28 | 2019-01-04 | 彩讯科技股份有限公司 | Channel agility method, apparatus, server and storage medium |
| CN109152061B (en) * | 2018-09-28 | 2023-05-02 | 彩讯科技股份有限公司 | Channel allocation method, device, server and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3430772B1 (en) | Message transfer system, method of transferring messages and software product | |
| US8635278B2 (en) | System and method for interruption management | |
| US6622021B1 (en) | System and method for implementing an automated communication response service | |
| EP2063590B1 (en) | A method and system for transmitting email and a push mail server | |
| CN100382543C (en) | Messaging systems | |
| US9729336B2 (en) | System and method for delayed phone conferencing | |
| US20060246877A1 (en) | Cellular telephone network with record keeping for missed calls | |
| US20070004383A1 (en) | Method and apparatus for providing a call reminder | |
| US10419371B2 (en) | Methods and systems for delayed notifications in communications networks | |
| CN104410982B (en) | Terminal polymerization and reconstructing method in a kind of Wireless Heterogeneous Networks | |
| US20150381541A1 (en) | Group Messaging Method, and Device | |
| US20120213345A1 (en) | Meeting scheduler sending reminders | |
| CN103686635A (en) | Short message retransmitting method and system | |
| WO2010012221A1 (en) | Method, device and system for sending short message | |
| CN101998305A (en) | Short message scheduling method and system | |
| CN1794832A (en) | Method of transmitting short message | |
| CN101540965A (en) | Method for processing dual-card multimedia message based on Windows Mobile platform | |
| EP1810533B1 (en) | Telecommunications services apparatus and method | |
| CN101815338A (en) | Device and method for controlling concurrent call volume | |
| CN100403818C (en) | Short message retransmitting method and short message retransmitting system | |
| EP1569431A1 (en) | Automatic conferencing service | |
| CN114979982B (en) | Message issuing method and device, electronic equipment and storage medium | |
| CN115866535A (en) | Method and system for realizing 5G message access by multiple protocols | |
| US20090111432A1 (en) | Phone messaging using audio streams | |
| CN101072389A (en) | System and method for prompting user access failure for digital trunking communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20110330 |