CN108810830A - A kind of short message service center's based reminding method and Short Message Service Gateway - Google Patents
A kind of short message service center's based reminding method and Short Message Service Gateway Download PDFInfo
- Publication number
- CN108810830A CN108810830A CN201710289506.2A CN201710289506A CN108810830A CN 108810830 A CN108810830 A CN 108810830A CN 201710289506 A CN201710289506 A CN 201710289506A CN 108810830 A CN108810830 A CN 108810830A
- Authority
- CN
- China
- Prior art keywords
- short message
- message service
- service gateway
- terminal
- failed delivery
- 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.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/184—Messaging devices, e.g. message centre
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A kind of short message service center's based reminding method of offer of the embodiment of the present invention and Short Message Service Gateway, Short Message Service Gateway determines that reception terminal is reachable based on registration of the terminal in application server is received, and obtain and wait for that throwing the failed delivery that short message is stored again records for reception terminal, then recording triggering short message center according to failed delivery reminds.The characteristics of Short Message Service Gateway can be directly acquainted with the registration known and receive terminal on the application server is utilized, the reachable state for receiving terminal can be directly acquainted in the case where not subscribing to reception terminal accessibility to HLR/HSS.When receive terminal up to when, obtain failed delivery record and triggering short message center remind.Terminal accessibility is provided due to not needing HLR/HSS, so reducing the functional requirement to HLR/HSS, relative to existing scheme, application scenarios are more extensive；Meanwhile because knowing that terminal accessibility does not need HLR/HSS and MME etc. and interacts, coordinates, the communication resource and process resource of system is saved, distributing rationally for resource is conducive to.
Description
Technical field
The present invention relates to the communications field more particularly to a kind of short message service center's based reminding methods and Short Message Service Gateway.
Background technology
It is all the network element that contracted user provides short message service that short messaging gateway, which is one with short message service center, wherein short to disappear
Breath center can realize reception, storage, forwarding, short message report generation, SMS query and short message charging of short message etc.
Function.Short messaging gateway can then provide routing and the interworking function between different short-message systems.The short of traditional circuit domain disappears
Breath is mainly provided by short message service center, using No.7 signaling bears；And IP short messages then use SIP (Session
Initiation Protocol, session initiation protocol) MESSAGE (message) realizations.In order to reduce to existing net circuit domain and IMS
The transformation in domain reuses conventional short message mechanism, IMS (IP Multimedia Subsystem, the subsystem of IP multimedia service)
IP-SM-GW (IP-Short-Message-Gateway, Internet protocol Short Message Service Gateway) is introduced in network, and IP short message industry is provided
Business, system group network structure chart may refer to Fig. 1.
Internet protocol Short Message Service Gateway 11 provides IP-based UE (User Equipment, user equipment) 12 and SMSC
The protocol interaction of short message is received and dispatched between (Short Message Service Center, SMS service center) 13.When with
After family edits short message on sending terminal and selects transmission, short message will be passed to sms center.Sms center receives
The short message will be sent to the Internet protocol Short Message Service Gateway 11 for receiving end side, Internet protocol short message after to the short message
The short message can be passed to corresponding network element to be delivered to reception terminal by gateway 11.When reception terminal is because of factors such as shutdown or signal difference
And when can not receive short message, the delivery for the short message will fail.The case where failure being delivered for short message,
It has formulated to subscribe in 3GPP standards (referring to 3GPP TS 23.204 in detail) and has received the reachable mechanism of terminal：Short message delivers failure
Afterwards, Internet protocol Short Message Service Gateway 11 to HLR/HSS (Home Location Register/Home Subscriber Server,
Home location register/home subscriber server) 14 transmission short message delivery states report (Map-Report-SM-Delivery-
Status), and the accessibility for receiving terminal is subscribed to HSS.Terminal is being received up to after, Internet protocol Short Message Service Gateway 11 will receive
The notice of home location register/home subscriber server 14.After receiving reachability, Internet protocol Short Message Service Gateway 11
To home location register/home subscriber server) 14 transmission MAP-READY-FOR-SM.Home location register/ownership is used
After family server 14 receives message, Alert SC (short message service center's prompting) flow is triggered to sms center, in short message
The heart delivers the short message of failure before retransmitting.Detailed process may refer to interaction figure illustrated in fig. 2：
S202, IP-SM-GW send the reachable notice that short message delivery state is reported and subscribes to reception terminal to HLR/HSS.
Include that short message is delivered as a result, in the example in state report, short message is to deliver failure.IP-
SM-GW subscribes to the accessibility for receiving terminal by sending Map-Any-Time-Modification to HLR/HSS.
S204, HLR/HSS instruction MME (Mobility Management Entity, mobility management entity), which are reported, to be connect
Receive terminal accessibility.
If receiving terminal to register in MME, HLR/HSS can send IDR request messages to MME, and (UE accessibilities are logical
Know), instruction MME reports the accessibility for receiving terminal.If receiving terminal not register in MME, HLR/HSS does not send request
Message.
It is reachable that S206, MME notify that HLR/HSS receives terminal.
When receive terminal up to when, MME notifies the HLR/HSS reception terminals reachable by NOR.
S208, HLR/HSS are sent to IP-SM-GW up to notice.
HLR/HSS notify to determine according to the NOR of MME receive terminal up to when, according to subscription previous IP-SM-GW to IP-
SM-GW is sent up to notice.
S210, IP-SM-GW send MAP-READY-FOR-SM message to HLR/HSS.
IP-SM-GW recognizes reception terminal up to after according to up to notice, and determining that can again throw to the reception terminal
Short message is passed, therefore, can inform that HLR/HSS triggers Alert SC flows to SC by MAP-READY-FOR-SM at this time.
S212, HLR/HSS trigger Alert SC flows to SC.
After HLR/HSS receives MAP-READY-FOR-SM, sms center can be triggered and rearranged for reception end
The delivery of the failure short message at end.
According to above-mentioned introduction, it will be appreciated that the process that existing triggering short message center is reminded depends on HLR/HSS to IP-
SM-GW inform receive terminal accessibility, once HLR/HSS does not support the accessibility of IP-SM-GW to subscribe to, then based on the program without
Method realizes the delivery of failure short message.On the other hand, IP-SM-GW carries out receiving terminal accessibility subscription needs to HLR/HSS
The mutual cooperation of multiple network elements such as HLR/HSS, MME, therefore the processing load of these network elements is increased, it is unfavorable for process resource
It distributes rationally.
Invention content
Short message service center's based reminding method and Short Message Service Gateway provided in an embodiment of the present invention, mainly solving the technical problems that：
A kind of new, independent of the short message service center's prompting for HLR/HSS receive the subscription of terminal accessibility triggering side is provided
Case is necessarily dependent upon HLR/HSS offer accessibility subscription to solve short message service center's prompting in the prior art, is unfavorable for realizing
The problem of process resource is distributed rationally.
In order to solve the above technical problems, the embodiment of the present invention provides a kind of short message service center's based reminding method, including：
Short Message Service Gateway determines that the reception terminal is reachable based on terminal is received in the registration of application server；
The Short Message Service Gateway is obtained waits for that throwing the failed delivery that short message is stored again records for the reception terminal, institute
State failed delivery record from the Short Message Service Gateway to the receptions terminal deliver this when throw again short message failure when generate；
The Short Message Service Gateway records triggering short message center according to the failed delivery and reminds, to indicate short message service center's weight
Newly wait for throwing short message again to described in reception terminal delivery.
The embodiment of the present invention also provides a kind of Short Message Service Gateway, including：
Logging modle, for after receiving terminal delivery short message delivery failure, storage to wait for throwing short message again for this
Failed delivery record；
Determining module, for determining that the reception terminal is reachable in the registration of application server based on reception terminal；
Acquisition module waits for that throwing the failed delivery that short message is stored again records for obtaining for the reception terminal；
Reminding module is reminded for recording triggering short message center according to the failed delivery, to indicate short message service center
Again to the reception terminal deliver described in wait for throwing short message again and lose.
The embodiment of the present invention also provides a kind of computer storage media, and computer is stored in the computer storage media
Executable instruction, the computer executable instructions are used to execute short message service center's based reminding method any one of above-mentioned.
The beneficial effects of the invention are as follows：
Short message service center's based reminding method and Short Message Service Gateway, computer storage media provided in an embodiment of the present invention, short message net
It closes and determines that reception terminal is reachable in the registration of application server based on reception terminal, and obtain and wait for throwing short disappear again for reception terminal
The stored failed delivery record of breath, then records triggering short message center according to failed delivery and reminds, to inform in short message
The heart waits for throwing short message again to reception terminal delivery again.Scheme provided in this embodiment is utilized Short Message Service Gateway and can be directly acquainted with
Know and receive the registration of terminal on the application server, therefore, Short Message Service Gateway is not subscribing to reception terminal accessibility to HLR/HSS
In the case of can be directly acquainted with receive terminal when reachable.When Short Message Service Gateway determine receive terminal up to when, obtain
It takes the failed delivery about the reception terminal of pre-recorded storage to record, and is recorded in triggering short message according to the failed delivery
The heart is reminded.Terminal accessibility is provided due to realizing that process that short message service center reminds does not need HLR/HSS, so reducing pair
The functional requirement of HLR/HSS, relative to existing scheme, application scenarios are more extensive；Meanwhile because knowing that terminal accessibility does not need
HLR/HSS and MME etc. are interacted, are coordinated, and are saved the communication resource and process resource of system, are conducive to distributing rationally for resource.
Description of the drawings
Fig. 1 is a kind of system group network schematic diagram for the note system for including Internet protocol Short Message Service Gateway；
Fig. 2 is a kind of interaction diagrams that the prior art carries out short message service center's prompting；
Fig. 3 is a kind of flow chart for short message service center's based reminding method that the embodiment of the present invention one provides；
Fig. 4 is that the Short Message Service Gateway that the embodiment of the present invention one provides records what triggering short message center was reminded according to failed delivery
A kind of flow chart；
Fig. 5 is a kind of flow chart of short message service center's based reminding method provided by Embodiment 2 of the present invention；
Fig. 6 is a kind of interaction diagrams for the storage failed delivery record that three kinds of the embodiment of the present invention provides；
Fig. 7 is that the reception terminal that three kinds of the embodiment of the present invention provides registers progress short message service center prompting under situation for the first time
A kind of interaction diagrams；
Fig. 8 is that short message service center's prompting is carried out under the reception terminal refresh registration situation that three kinds of the embodiment of the present invention provides
A kind of interaction diagrams；
Fig. 9 is a kind of structural schematic diagram of the Short Message Service Gateway provided in the embodiment of the present invention four；
Figure 10 is a kind of structural schematic diagram of the Short Message Service Gateway provided in the embodiment of the present invention five；
Figure 11 is that a kind of hardware configuration of the server for disposing Short Message Service Gateway provided in the embodiment of the present invention six shows
It is intended to.
Specific implementation mode
The embodiment of the present invention is described in further detail below by specific implementation mode combination attached drawing.
Embodiment one：
Due in the prior art short message deliver failure after carry out short message service center remind dependent on HLR/HSS to
IP-SM-GW, which is provided, receives terminal up to the service subscribed to, and in turn results in short message service center's prompting and requires HLR/HSS that must support
Accessibility is subscribed to, meanwhile, it interacts with MME up to needs when subscribing to because HLR/HSS is provided, coordinate and could realize, need
The a large amount of process resource of the two and the communication resource are occupied, so being unfavorable for distributing rationally for resource.For these problems, this implementation
Example provides a kind of short message service center's based reminding method, refers to the flow chart of short message service center's based reminding method shown in Fig. 3：
S302, Short Message Service Gateway determine that reception terminal is reachable based on registration of the terminal in application server is received.
It is assumed that it is " your Saturday having time to send terminal to receive terminal to have sent a content？" short message, then when
After sending terminal selection transmission, which can be passed to short message service center first, arrange to receive eventually by short message service center
The Short Message Service Gateway of end side delivers the short message.If Short Message Service Gateway delivers short message, receives terminal and be in pass
Machine or the state being not turned on because communication quality is very poor, the then delivery of Short Message Service Gateway will fail.In general, one
Short message means that short message needs are delivered again after delivering failure.
So the Short Message Service Gateway in the present embodiment can be recorded when delivering failure for the failure short message, namely
The failed delivery record for waiting for throwing short message again, so as to it is corresponding receive terminal up to when, carry out this again and wait for throwing short disappear again
The delivery of breath.It is which short message waits for throwing again, and it is short to fail without record that the failed delivery record of Short Message Service Gateway storage, which can characterize,
What the particular content of message is, because the particular content of failure short message is recorded by short message service center.
Although failed delivery record is that Short Message Service Gateway is required when triggering short message center is reminded, that is, unsuccessfully throwing
Passing record is that Short Message Service Gateway itself is required, therefore theoretically, and failed delivery record should be stored on Short Message Service Gateway, but
It, can be to once being registered on AS since a terminal is after off-mode enters open state, which is referred to as
First registration, when terminal is registered for the first time, the data for the terminal that Short Message Service Gateway is locally stored will be disposed of.And
It should be understood that before waiting for that throw short message again delivers successfully again, wait for that the failed delivery for throwing short message again records for this
It is all necessary, so Short Message Service Gateway at least should cannot unsuccessfully be thrown this only by failed delivery record storage in local
Pass the place that record storage will not be arbitrarily eliminated at one.So in the present embodiment, Short Message Service Gateway can record failed delivery
On storage portion to HLR/HSS.It will be understood however, that in addition to HLR/HSS, Short Message Service Gateway can also record failed delivery
It stores on other external memories, as long as the data in the storage location will not be deleted i.e. with the switching on and shutting down of terminal
It can.
In addition, due to the Short Message Service Gateway itself for needing to record using failed delivery, as long as and receiving terminal temporarily less than answering
With being registered for the first time on server, then Short Message Service Gateway can't carry out the data for the reception terminal being locally stored clear
It removes, so, it in the present embodiment, can also be by failed delivery record storage portion in Short Message Service Gateway local, as long as in this way, receiving
Terminal without registering for the first time, and Short Message Service Gateway is when needing to obtain failed delivery record, so that it may to be got from local, phase
For all obtaining the way that failed delivery records from external storage location under any circumstance, can be good at avoiding depositing from outside
It stores up position acquisition failed delivery record and needs time-consuming problem.
It should be understood that it is not by short message that Short Message Service Gateway, which treats the opportunity that throwing short message is delivered again again,
What the heart or Short Message Service Gateway determined at random, but determined by reception terminal.Only when receive terminal up to when, Short Message Service Gateway just meeting
Triggering short message center is reminded, and the delivery to failure short message is rearranged at informing message center.In the present embodiment, short message net
Close directly to obtain from AS (Application Server, application server) and receive the reachable information of terminal, replace to
HLR/HSS carries out receiving the way that terminal accessibility is subscribed to.After reception terminal enters open state from off-mode, it can arrive
It is registered for the first time on AS, at this moment receives terminal and be available.In addition, being carried out for the first time between terminal and application server receiving
After registration, need to carry out a refresh registration to application server at regular intervals, to inform that application server itself is worked as
Before be it is reachable, so Short Message Service Gateway can pass through receive terminal on AS it is first registration with refresh registration understand reception terminal
Reachable information.
S304, Short Message Service Gateway are obtained waits for that throwing the failed delivery that short message is stored again records for the reception terminal.
When Short Message Service Gateway according to receive registration of the terminal on AS recognize the reception terminal up to when, Short Message Service Gateway can be with
It obtains and waits for that throwing the failed delivery that short message is stored again records for the reception terminal.Specifically, if Short Message Service Gateway is only in outside
The failed delivery record of the reception terminal is stored on memory, or the current registration for receiving terminal on AS belongs to first note
Copy, then Short Message Service Gateway can directly arrive the external memory and obtain failed delivery record.If currently receiving note of the terminal on AS
Refresh registration when volume, and terminal not only stores failed delivery record on external memory in advance, but also deposited locally
Failed delivery record is stored up, then Short Message Service Gateway can locally obtain failed delivery record.Failure is being locally stored in Short Message Service Gateway
It can be in the lower progress of at least one of following two situations to deliver record：
The first, whiles Short Message Service Gateway is by failed delivery record storage to external memory, HLR/HSS etc.,
Short Message Service Gateway is also by failed delivery record storage to locally.It is beyond all doubt, if Short Message Service Gateway receive endpoint registration it
The failed delivery record obtained afterwards is that storage then receives terminal and arrived in failed delivery record storage to local in this way
It should not registered after for the first time after local.
Second, Short Message Service Gateway has only arrived the failed delivery record storage external after failed regeneration delivers record
On memory, but after receiving terminal registration for the first time or refresh registration, Short Message Service Gateway gets needle from external memory
After the failed delivery record of the reception terminal, it will the failed delivery record storage portion got to locally.
So when Short Message Service Gateway by any one in above two mode by failed delivery record storage to local
Afterwards, after completing refresh registration on receiving terminal to AS, Short Message Service Gateway can obtain failed delivery record from local.
S306, Short Message Service Gateway record triggering short message center according to failed delivery and remind.
After Short Message Service Gateway gets failed delivery record, triggering short message center will be recorded according to the failed delivery and carried
It wakes up.It is introduced with reference to Fig. 4 processes reminded Short Message Service Gateway triggering short message center in the present embodiment：
S402, Short Message Service Gateway send MAP-Ready-for-SM message to HLR/HSS.
MAP-Ready-for-SM is the message for the related short message service that MAP is defined, and is usually being connect by Short Message Service Gateway
It receives terminal and is sent to HLR when can receive short message.When HLR/HSS receives the MAP-Ready-for-SM of Short Message Service Gateway transmission
After message, usually also a corresponding response message --- " MAP-Ready-for-SM-rsp " can be fed back to Short Message Service Gateway.
S404, HLR/HSS send MAP-Alert-Service-Center message to short message service center.
MAP-Alert-Service-Center, that is, short message service center's reminder message, its essence is for informing in short message
Heart reception terminal is currently reachable, can arrange the delivery again for being waited for throwing short message again to the reception terminal.When in short message
The heart receives MAP-Alert-Service-Center message, also can send " MAP-Alert-Service- to HLR/HSS
Center-rsp " is in response.
In the present embodiment, Short Message Service Gateway generates the failed delivery for the short message after short message delivers failure
Record, and failed delivery record is stored, when it receives the registration understanding of terminal on the application server by corresponding
To the reception terminal up to when, can obtain failed delivery record, and according to failed delivery record triggering to short message service center
It reminds, informs that short message service center arranges to treat the delivery again for throwing short message again.Do not had to by Short Message Service Gateway in this present embodiment logical
Crossing to HLR/HSS subscribe to can be directly acquainted with from application server to the reachable relevant information of terminal is received, so not
With requiring supporting up to property of HLR/HSS to subscribe to, the requirement to HLR/HSS is reduced.Importantly, short message net in the present embodiment
It is simpler to close the reachable mode of understanding reception terminal, does not need HLR/HSS and MME mutual cooperations and can be realized, reduce to being
The requirement of process resource of uniting and the communication resource.
Embodiment two：
The advantages of in order to make short message center based reminding method of the present invention, is clearer with details, and the present embodiment is in embodiment
Continue that short message service center's based reminding method is introduced on the basis of one, refers to Fig. 5：
The storage after short message delivers failure of S502, Short Message Service Gateway is recorded for the failed delivery of the short message.
In the present embodiment, Short Message Service Gateway can be IP-SM-GW, i.e. Internet protocol Short Message Service Gateway.Short Message Service Gateway can incite somebody to action
Failed delivery is recorded while being stored onto local and external memory.It is assumed that external memory is the memory on HLR/HSS, under
The process of failed delivery record storage to HLR/HSS is introduced in face of Short Message Service Gateway：
Since Short Message Service Gateway can send PUR to HLR/HSS, (Profile Update Request, configuration file update are asked
Ask), so, in the present embodiment, Short Message Service Gateway and HLR/HSS make an appointment and a delivery-fail mark are arranged in PUR
Note, i.e., unsuccessfully identify, and is had failed to a certain short message deliveries of Short Message Service Gateway notice HLR/HSS.In the follow-up process, work as short message
When gateway needs to obtain failed delivery record, HLR/HSS can directly carry delivery-fail labels in number of users
According to returning to Short Message Service Gateway in record.
Certainly, since after short message is delivered, Short Message Service Gateway can send MAP-REPORT-SM- to HLR/HSS
DELIVERY-STATUS message, i.e. short message delivery state are reported.After short message, which is delivered, to fail, shape is delivered in short message
Also include the relevant information that short message delivers failure in state report, so, Short Message Service Gateway can also be by sending to HLR/HSS
The report of short message delivery state, will be in failed delivery record storage to HLR/HSS.In the present embodiment, Short Message Service Gateway was both
The PUR for carrying failure mark can be sent to HLR/HSS, and can send the report of short message delivery state.
S504, when monitoring that when throwing the corresponding reception terminal of short message again and being registered on AS, Short Message Service Gateway obtains failure
Deliver record.
After Short Message Service Gateway determines that receive terminal is registered in application server AS, Short Message Service Gateway can obtain in advance
The failed delivery of storage records.If receive that terminal carries out is to register for the first time, Short Message Service Gateway is from external storages such as HLR/HSS
Failed delivery record is obtained on position, and the failed delivery record storage got is thrown to locally to prevent current short message again
It is unsuccessful, can failed delivery record directly be obtained from local when receipt of subsequent terminal carries out refresh registration, to save
Obtain the time of failed delivery record.
If receive that terminal carries out on the application server is refresh registration because in the present embodiment Short Message Service Gateway it
It is preceding that failed delivery record is being locally stored, so, Short Message Service Gateway directly can get failed delivery record from local.
S506, Short Message Service Gateway record triggering short message center according to failed delivery and remind.
Short Message Service Gateway records the process that triggering short message center is reminded according to failed delivery and has been carried out in embodiment one
More detailed introduction, no longer illustrates here.
S508, Short Message Service Gateway judgement wait for throwing whether short message delivers success again.
After short message service center's control Short Message Service Gateway, which is treated, throws short message progress delivery again again, such two kinds are only had
As a result, one is this to wait for that throwing short message again delivers successfully, another kind is to wait for that the delivery again for throwing short message again has failed naturally.
If the determination result is YES, then S510 is executed, otherwise needs to continue to treat again throwing short message to be delivered, therefore go to S504.
S510, Short Message Service Gateway are removed for the failed delivery record for waiting for throwing short message again.
Corresponding failure is carried out since Short Message Service Gateway is just bound to obtain failed delivery record when receiving endpoint registration
The delivery again of short message also will continue to so delivering the Short Message Service Gateway short message to fail is thrown successfully again after in order to avoid script
Short message delivery is carried out, bad user experience is caused to user is received, wastes the communication resource, it is short when waiting for throwing again in the present embodiment
After the success of throwing again of message, Short Message Service Gateway will remove the failed delivery record for the short message.It should be appreciated that short
Letter gateway should be removed including the failed delivery record in local and external memory all storage locations.
The short message service center's based reminding method provided in the present embodiment can unsuccessfully be identified by sending to carry to HLR/HSS
Configuration file update request to will be directed to deliver failure short message failed delivery record storage to HLR/HSS on, profit
It the advantages of failed delivery record will not be removed because of the variation for receiving the SOT state of termination with external memories such as HLR/HSS, allows short
Letter gateway can obtain the failed delivery note for waiting for throwing short message again for the reception terminal even if receiving after terminal registration for the first time
Record, to be thrown failure short message again.In addition short message service center's based reminding method provided in this embodiment can also be short in failure
After the success of throwing again of message, deletes this stored on local and external memory and the failed delivery of the short message is recorded, keep away
Exempt from Short Message Service Gateway to carry out repeating delivery to having delivered successful short message always, wastes the communication resource, reduce user experience.
Embodiment three：
The present embodiment combines specific example to remind short message service center and is described further, and assumes in the present embodiment short
Letter gateway is that IP-SM-GW can also be with other logical ne portions since IP-SM-GW can be disposed as stand-alone network elements
Administration is together.In the present embodiment, IP-SM-GW is disposed on the application server, so, it receives terminal and is noted to application server
Volume is also equivalent to be registered to IP-SM-GW.It is worth noting that " being equivalent to " mentioned here is substantially that station is real in physics
It is said in the angle of body, is to omit this logical ne of application server and interact with IP-SM-GW this logical gateway inside to wait until
, it is not completely equivalent.
Below by the storing of point failed delivery record, register for the first time when short message service center remind and when refresh registration
Short message service center reminds three processes to be illustrated, below referring first to one kind of storage failed delivery record illustrated in fig. 6
Interaction figure：
S601, IP-SM-GW send the report of short message delivery state to HLR/HSS；
S602, IP-SM-GW are locally preserving failed delivery record；
S603, IP-SM-GW send PUR message to HLR/HSS；
S604, HLR/HSS send PUA message to IP-SM-GW.
In the present embodiment, IP-SM-GW sends to HLR/HSS and carries delivery-fail labels in PUR message,
It can indicate that short message delivers failure to HLR/HSS.Certainly, HLR/HSS from short message delivery state report in also be understood that
The delivery result of short message.It is short why IP-SM-GW can understand in HLR/HSS can be reported by short message delivery state
It is also sent to carry the PUR message of failure mark in the case of message dilivery result, this is primarily due to short message and delivers shape
State report is specified in existing communication agreement, no matter the delivery result success or not IP-SM-GW of short message all can be to HLR/
What HSS was sent.And in the present embodiment, when follow-up IP-SM-GW obtains failed delivery record, it is to be understood that only throw
It is which to pass the short message having failed, and is not relevant for delivering successful short message.So if IP-SM-GW is only to HLR/HSS
Send the report of short message delivery state, then HLR/HSS may also need to carry out screening according to the message of reception could be to IP-SM-
GW provides failed delivery record, therefore, in order to avoid HLR/HSS is screened according to the report of short message delivery state, this implementation
IP-SM-GW can deliver the rear of failure in short message and carry the PUR message unsuccessfully identified to HLR/HSS transmissions in example.
It should be understood that these three processes of S601, S602, S603 are there is no the limitation of stringent sequential, Short Message Service Gateway can
To execute sequence according to the actual demand of oneself selection.Since the HLR/HSS PUA message sent to IP-SM-GW is to IP-SM-
The response for the PUR message that GW is sent, so, S604 must be after S603.
It refers to the IP-SM-GW shown in Fig. 7 and carries out short message service center's prompting according to first registration of the terminal on AS is received
A kind of interaction figure：
S701, terminal is received to AS initiation initial registration.
Since AS and IP-SM-GW are disposed together namely IP-SM-GW is deployed on application server, so IP-
The partial function of SM-GW can be undertaken by application server.So when reception terminal is initiated to register to AS, IP-SM-GW
The information can be learnt immediately.
S702, IP-SM-GW send user data requests UDR to HLR/HSS.
S703, HLR/HSS send user data to IP-SM-GW and respond UDA.
UDR (User Data Request, user data requests) can allow HLR/HSS to send the user data of storage
Include that IP-SM-GW is sent to HLR/HSS's in advance in the UDA that HLR/HSS is sent to IP-SM-GW to IP-SM-GW
Delivery-fail is marked.
S704, IP-SM-GW send subscribing notification to HLR/HSS and ask SNR.
S705, HLR/HSS send subscribing notification to IP-SM-GW and ask SNA.
It sends SNR (Subscribe Notification Request, subscribing notification request) and receives SNA
The process of (Subscribe Notification Answer, subscribe-notifications-answer) is that existing terminal is noted on the application server
The process undergone required for volume is not process necessary to realizing short message service center's prompting in the present embodiment.
S706, IP-SM-GW send 200OK message to terminal is received.
After the user data that IP-SM-GW receives HLR/HSS transmissions responds SNA, characterization receives terminal and is taken in application
Initial registration on business device has succeeded, so IP-SM-GW can send a 200OK message as reception to end side is received
Terminal sends the response of registration request.
S707, IP-SM-GW send MAP-Ready-for-SM message to HLR/HSS.
S708, HLR/HSS send MAP-Ready-for-SM-rsp message to IP-SM-GW.
IP-SM-GW is to notify HLR/HSS in short message to HLR/HSS transmissions MAP-Ready-for-SM message
The heart carries out MAP-Alert-Service-Center promptings, and to be then HLR/HSS receiving MAP-Ready-for-SM-rsp
To the response message of IP-SM-GW after MAP-Ready-for-SM.
S709, HLR/HSS send MAP-Alert-Service-Center message to short message service center.
S710, short message service center send MAP-Alert-Service-Center-rsp message to HLR/HSS.
The MAP-Alert-Service-Center message that HLR/HSS is sent to short message service center can be used for reminding short disappear
Breath center currently receives that terminal is reachable, can be delivered again to the short message for delivering failure before again.And in short message
After the heart receives MAP-Alert-Service-Center, MAP-Alert-Service-Center- can be fed back to HLR/HSS
Rsp message is in response.
Assume that short message service center rearranges the short message delivered and failed to script and carries out delivering knot after delivering again below
Fruit is successfully.Then IP-SM-GW can also delete the failed delivery record for the short message：
S711, IP-SM-GW delete the failed delivery record being locally stored.
S712, IP-SM-GW do not carry the PUR message unsuccessfully identified to HLR/HSS transmissions.
S713, HLR/HSS send PUA message to IP-SM-GW.
Obviously, in Fig. 7, S712 and S713 be recorded to remove the failed delivery being stored on HLR/HSS, and
S711 is then to remove the failed delivery record for being stored in the locals IP-SM-GW.But IP-SM-GW can first remove local in fact
The failed delivery of storage records, and can also first remove the failed delivery record being stored on HLR/HSS, so, S711 can be
It, can also be after S713 before S712.
It refers to the IP-SM-GW shown in Fig. 8 and carries out short message service center's prompting according to first registration of the terminal on AS is received
A kind of interaction figure：
S801, terminal is received to AS initiation refresh registrations.
S802, AS return to 200OK message to terminal is received.
Since refresh registration can't make IP-SM-GW remove the data of the reception terminal being locally stored, so in this reality
Apply in example, IP-SM-GW need not after refresh registration to HLR/HSS obtain user data, AS receive refresh registration it
Afterwards, directly 200OK message can be returned to reception terminal to be responded.
S803, IP-SM-GW send MAP-Ready-for-SM message to HLR/HSS.
S804, HLR/HSS send MAP-Ready-for-SM-rsp message to IP-SM-GW.
IP-SM-GW is recorded according to the failed delivery being locally stored to HLR/HSS transmissions MAP-Ready-for-SM message
In order to notify HLR/HSS to carry out MAP-Alert-Service-Center promptings, and MAP-Ready-for- to short message service center
SM-rsp be then HLR/HSS after receiving MAP-Ready-for-SM to the response message of IP-SM-GW.
S805, HLR/HSS send MAP-Alert-Service-Center message to short message service center.
S806, short message service center send MAP-Alert-Service-Center-rsp message to HLR/HSS.
The MAP-Alert-Service-Center message that HLR/HSS is sent to short message service center can be used for reminding short disappear
Breath center currently receives that terminal is reachable, can be delivered again to the short message for delivering failure before again.And in short message
After the heart receives MAP-Alert-Service-Center, MAP-Alert-Service-Center- can be fed back to HLR/HSS
Rsp message is in response.
In the present embodiment, if short message service center arrange IP-SM-GW to failure short message delivered again, and delivery at
After work(, IP-SM-GW is also required to remove the failed delivery record being stored on local and HLR/HSS, process and first registration
Process afterwards is identical, and which is not described herein again.If delivering failure, continue waiting for receiving refresh registration or first of the terminal on AS
Secondary registration.
Short message service center's based reminding method provided in an embodiment of the present invention, IP-SM-GW together with application server deployment,
So the partial function of the two can be with shared, when receiving terminal to application server registers, IP-SM-GW can
To registration message, IP-SM-GW is ordered relative to carrying out receiving terminal accessibility to HLR/HSS it will be appreciated that recognize quick obtaining
The way read can obtain and receive terminal reachable time more quickly, reduce to system processing resources and the communication resource
It occupies, is conducive to distributing rationally for resource.
Example IV：
The present embodiment provides a kind of Short Message Service Gateway, refer to Fig. 9：Short Message Service Gateway 90 includes logging modle 902, determining module
904, acquisition module 906 and reminding module 908.
It is assumed that it is " your Saturday having time to send terminal to receive terminal to have sent a content？" short message, then when
After sending terminal selection transmission, which can be passed to short message service center first, arrange to receive eventually by short message service center
The Short Message Service Gateway 90 of end side delivers the short message.If Short Message Service Gateway 90 delivers short message, receive at terminal
It will fail in shutdown or the state being not turned on because communication quality is very poor, the then delivery of Short Message Service Gateway 90.In usual feelings
Under condition, a short message means that short message needs are delivered again after delivering failure.
So the logging modle 902 in the present embodiment can be recorded when delivering failure for the failure short message,
Namely wait for throwing the failed delivery record of short message again, so as to it is corresponding receive terminal up to when, carry out this again and wait for throwing again
The delivery of short message.It is which short message waits for throwing again, and does not have to record that the failed delivery record that logging modle 902 stores, which can characterize,
What the particular content of failure short message is, because the particular content of failure short message is recorded by short message service center.
Although failed delivery record is that reminding module 908 is required when triggering short message center is reminded, that is, failure
It is that Short Message Service Gateway 90 itself is required, therefore theoretically, failed delivery record should be stored in Short Message Service Gateway to deliver record
It, can be to once being registered on AS on 90, but since a terminal is after off-mode enters open state, the registration process
It is referred to as registering for the first time, when terminal is registered for the first time, data for the terminal that Short Message Service Gateway 90 is locally stored will be by
It disposes.And it should be understood that before waiting for that throw short message again delivers successfully again, wait for throwing the failure of short message again for this
It delivers record to be all necessary, so logging modle 902 cannot at least should only by failed delivery record storage in local
The place that the failed delivery record storage will not be arbitrarily eliminated at one.So in the present embodiment, 902 meeting of logging modle
It will be on failed delivery record storage portion to HLR/HSS.It will be understood however, that in addition to HLR/HSS, logging modle 902 is also
It can be by failed delivery record storage to other external memories, as long as the data in the storage location will not be with terminal
Switching on and shutting down and be deleted.
In addition, due to need using failed delivery record Short Message Service Gateway 90 itself, as long as and reception terminal temporarily less than
Registered for the first time on application server, then Short Message Service Gateway 90 can't by the data for the reception terminal being locally stored into
Row is removed, so, in the present embodiment, logging modle 902 can also be by failed delivery record storage portion in Short Message Service Gateway 90
It is local, as long as in this way, receive terminal without registering for the first time, when needing to obtain failed delivery record, acquisition module 906
It can be got from local, relative to all obtaining the way that failed delivery records from external storage location under any circumstance,
It can be good at avoiding obtaining the time-consuming problem of failed delivery record needs from external storage location.
It should be understood that Short Message Service Gateway 90 is treated, to throw opportunity for being delivered again of short message again be not oneself or short
What message center determined at random, but determined by reception terminal.Only when receive terminal up to when, reminding module 908 just can
Triggering short message center is reminded, and the delivery to failure short message is rearranged at informing message center.In the present embodiment, mould is determined
Block 904 can be obtained directly from AS (Application Server, application server) and receive the reachable information of terminal, replace to
HLR/HSS carries out receiving the way that terminal accessibility is subscribed to.After reception terminal enters open state from off-mode, it can arrive
It is registered for the first time on AS, at this moment receives terminal and be available.In addition, being carried out for the first time between terminal and application server receiving
After registration, need to carry out a refresh registration to application server at regular intervals, to inform that application server itself is worked as
Before be reachable, received so determining module 904 can be registered in refresh registration and understand by receiving first on AS of terminal
The reachable information of terminal.
When determining module 904 according to receive registration of the terminal on AS recognize the reception terminal up to when, acquisition module
906 can obtain and wait for throwing the failed delivery record that short message is stored again for the reception terminal.If specifically, logging modle
902 only store the failed delivery record of the reception terminal, or the current registration for receiving terminal on AS on external memory
Belong to first registration, then acquisition module 906 can directly arrive the external memory and obtain failed delivery record.If current receive eventually
End refresh registration in the registration on AS, and terminal not only stores failed delivery record on external memory in advance, and
And failed delivery record also is being locally stored, then acquisition module 906 can locally obtain failed delivery record.Logging modle
902 be locally stored failed delivery record can carry out in both cases：
The first, when logging modle 902 is by failed delivery record storage to external memory, HLR/HSS's etc. is same
When, also by failed delivery record storage to locally.It is beyond all doubt, if acquisition module 906 is after receiving endpoint registration
The failed delivery record of acquisition is that local is arrived in storage in this way, then receives terminal in failed delivery record storage to originally
It should not registered after for the first time after ground.
Second, logging modle 902 has only arrived the failed delivery record storage outer after failed regeneration delivers record
On portion's memory, but after receiving terminal registration for the first time or refresh registration, acquisition module 906 is obtained from external memory
To after the failed delivery record for the reception terminal, logging modle 902 will be the failed delivery record storage got
Portion is to locally.
So when logging modle 902 by least one of above two mode by failed delivery record storage to this
After ground, after determining module 904 is recognized and receives and complete refresh registration in terminal to AS, acquisition module 906 can be from
It is local to obtain failed delivery record.
After acquisition module 906 gets failed delivery record, it will be recorded in triggering short message according to the failed delivery
The heart is reminded.Reminding module 908 can be reminded by sending MAP-Ready-for-SM triggering short messages center to HLR/HSS,
MAP-Ready-for-SM is the message for the related short message service that MAP is defined, usually by Short Message Service Gateway receive terminal can
HLR is sent to when receiving short message.When HLR/HSS receives the MAP-Ready-for-SM message of the transmission of reminding module 908
Afterwards, usually also a corresponding response message --- " MAP-Ready-for-SM-rsp " can be fed back to reminding module 908.
HLR/HSS can send short message service center's reminder message after receiving MAP-Ready-for-SM to short message service center,
That is MAP-Alert-Service-Center message can arrange pair for informing that it is currently reachable that short message service center receives terminal
The reception terminal is waited for throwing the delivery again of short message again.When short message service center receives MAP-Alert-Service-
Center message also can send " MAP-Alert-Service-Center-rsp " in response to HLR/HSS.
In the present embodiment, Short Message Service Gateway generates the failed delivery for the short message after short message delivers failure
Record, and failed delivery record is stored, when it receives the registration understanding of terminal on the application server by corresponding
To the reception terminal up to when, can obtain failed delivery record, and according to failed delivery record triggering to short message service center
It reminds, informs that short message service center arranges to treat the delivery again for throwing short message again.Do not had to by Short Message Service Gateway in this present embodiment logical
Crossing to HLR/HSS subscribe to can be directly acquainted with from application server to the reachable relevant information of terminal is received, so not
With requiring supporting up to property of HLR/HSS to subscribe to, the requirement to HLR/HSS is reduced.Importantly, short message net in the present embodiment
It is simpler to close the reachable mode of understanding reception terminal, does not need HLR/HSS and MME mutual cooperations and can be realized, reduce to being
The requirement of process resource of uniting and the communication resource.
Embodiment five：
The advantages of in order to make short message center based reminding method of the present invention, is clearer with details, and the present embodiment is in embodiment
Continue that Short Message Service Gateway is introduced on the basis of four, please continue to refer to Figure 10, Short Message Service Gateway 90 further includes removing module 910.
The storage after short message delivers failure of logging modle 902 is recorded for the failed delivery of the short message.In this reality
It applies in example, Short Message Service Gateway 90 can be IP-SM-GW, i.e. Internet protocol Short Message Service Gateway.Logging modle 902 can be by failed delivery
On record while storage to local and external memory.It is assumed that external memory is the memory on HLR/HSS, below to record
The process of failed delivery record storage to HLR/HSS is introduced module 902：
Since Short Message Service Gateway 90 can send PUR (Profile Update Request, configuration file update to HLR/HSS
Request), so, in the present embodiment, logging modle 902 and HLR/HSS make an appointment and a delivery- are arranged in PUR
Fail is marked, i.e., unsuccessfully identifies, and notifies HLR/HSS that a certain short message delivery has failed to logging modle 902.In subsequent process
In, when acquisition module 906 needs to obtain failed delivery record, HLR/HSS can directly mark delivery-fail
It carries and returns to acquisition module 906 in user data record.
Certainly, since after short message is delivered, Short Message Service Gateway 90 can send MAP-REPORT-SM- to HLR/HSS
DELIVERY-STATUS message, i.e. short message delivery state are reported.After short message, which is delivered, to fail, shape is delivered in short message
Also include the relevant information that short message delivers failure in state report, so, logging modle 902 can also be by HLR/HSS
The report of short message delivery state is sent, it will be in failed delivery record storage to HLR/HSS.In the present embodiment, short message net
The PUR for carrying failure mark can not only be sent to HLR/HSS by closing 90, but also can send the report of short message delivery state.
After determining that receive terminal is registered in application server AS, acquisition module 906 can be obtained and be prestored
Failed delivery record.If receive that terminal carries out is to register for the first time, acquisition module 906 is from external storages such as HLR/HSS
Failed delivery record is obtained on position, and the failed delivery record storage got is thrown to locally to prevent current short message again
It is unsuccessful, can failed delivery record directly be obtained from local when receipt of subsequent terminal carries out refresh registration, to save
Obtain the time of failed delivery record.
If what reception terminal carried out on the application server is refresh registration, because of logging modle in the present embodiment
Failed delivery record is being locally stored before 902, so, acquisition module 906 directly can get failed delivery from local
Record.
Reminding module 908 according to failed delivery record process that triggering short message center is reminded in embodiment one into
It has gone more detailed introduction, has no longer illustrated here.
After short message service center's control Short Message Service Gateway 90, which is treated, throws short message progress delivery again again, such two are only had
For kind as a result, one is this to wait for that throwing short message again delivers successfully, another kind is the failure of delivery again for waiting for throwing short message again naturally
?.It successfully removes module 910 if wait for throwing short message and deliver again and needs to remove for the failed delivery note for waiting for throwing short message again
Record.
Since acquisition module 906 is just bound to obtain failed delivery note when receiving terminal to application server registers
Record, and reminder announced module 908 carries out the delivery again of corresponding failure short message, so in order to avoid script delivers the short of failure
Short Message Service Gateway 90 also will continue to carry out short message delivery message is thrown successfully again after, and bad user experience is caused to user is received,
The communication resource is wasted, in the present embodiment, after wait for throwing the success of throwing again of short message again, module 910 is removed and will remove and is directed to
The failed delivery of the short message records.It should be appreciated that including local and external memory should be removed by removing module 910
All storage locations on failed delivery record.
The Short Message Service Gateway provided in the present embodiment can carry the configuration file of failure mark by being sent to HLR/HSS
Update request utilizes HLR/HSS etc. to be directed in the failed delivery record storage to HLR/HSS for the short message for delivering failure
External memory will not remove the advantages of failed delivery record because of the variation for receiving the SOT state of termination, even if Short Message Service Gateway is allowed to exist
The failed delivery record for waiting for throwing short message again for the reception terminal can be also obtained after receiving terminal registration for the first time, to failure
Short message is thrown again.In addition short message service center's based reminding method provided in this embodiment can also be in the success of throwing again of failure short message
Later, it deletes this stored on local and external memory to record the failed delivery of the short message, avoids Short Message Service Gateway always
It carries out repeating delivery to having delivered successful short message, wastes the communication resource, reduce user experience.
Embodiment six：
Short Message Service Gateway in foregoing embodiments can be used as an individual network element deployment on a physical entity, also may be used
To share a physical entity with other logical nes.In the present embodiment on the server by Short Message Service Gateway deployment, with reference to figure
The hardware configuration of Short Message Service Gateway in 11 pairs of various embodiments of the present invention is introduced：
Server 100 includes at least input and output (IO) bus 110, processor 140, memory 130, memory 120 and leads to
T unit 150.
Wherein, input and output (IO) bus 110 respectively with itself belonging to other components of server (processor 140 is deposited
Reservoir 130, memory 120 and communication device 150) connection, and provide transmission lines for other components.
It can be stored in memory 120 for realizing the computer program of short message service center's based reminding method, when server 100 needs
When executing aforementioned short message service center's based reminding method, processor 140 is each from control after code is compiled is read out in memory 120
A component cooperates, and realizes each flow in short message service center's based reminding method.
When Short Message Service Gateway is needed failed delivery record storage to local, memory 130 can be in processor 140
Control under storage failed delivery record.
Processor 140 usually controls the overall operation of the server belonging to itself.For example, processor 140 execute calculate and
The operations such as confirmation.Wherein, processor 140 can be central processing unit (CPU).
Communication device 150, generally includes one or more components, allows the server belonging to itself and wireless communication system
Radio communication between system or network.When Short Message Service Gateway needs are interacted with application server or HLR/HSS, communication device
150 assume responsibility for corresponding communication task under the control of processor 140.
Logging modle, determining module, acquisition module, removing mould in the Short Message Service Gateway that example IV is provided with embodiment five
The function of block can be cooperated and be realized by processor 140 and memory 130, communication device 150.The function of reminding module can be with
It is realized with both processor and communication device.After short message delivers failure, processor 140 can be in local storage
Failed delivery record is stored in 130, while controlling communication device 150 by the failed delivery record storage to external memory,
Such as it stores on HLR/HSS.It is registered in application server AS when receiving terminal or when refresh registration, is led to for the first time
T unit 150 passes through the interaction with application server, it can be realized that the reception terminal is available.If the registration for receiving terminal belongs to
First to register, then processor 140 can control communication device 150 and send request message to external memories such as HLR/HSS, obtain
The failure storage record stored before.After getting failed delivery record, 140 control memory 130 of processor will be got
Failed delivery record stored.And control communication device 150 and HLR/HSS is recorded according to the failed delivery and is interacted,
To allow HLR/HSS to send MAP-Alert-Service-Center message to short message service center.If receiving the registration category of terminal
In refresh registration, then processor 140 can obtain failed delivery record directly from local storage 130, and communication is notified to fill
It sets 150 to interact with HLR/HSS, allows HLR/HSS to send MAP-Alert-Service-Center message to short message service center and complete
Short message service center reminds.
In addition, the Short Message Service Gateway in previous embodiment can also be with application server deployment on same server, at this
Kind in the case of, receive terminal interact with the communication device of application server realization register, substantially namely with Short Message Service Gateway
Interaction saves accessibility and obtains the time so Short Message Service Gateway, which can directly acquire, receives the reachable information of terminal, reduces resource wave
Take.
Obviously, those skilled in the art should be understood that each module of the embodiments of the present invention or each step can be used
General computing device realizes that they can be concentrated on a single computing device, or be distributed in multiple computing device institutes
On the network of composition, optionally, they can be realized with the program code that computing device can perform, it is thus possible to by them
It is stored in computer storage media (ROM/RAM, magnetic disc, CD) and is performed by computing device, and in some cases, it can
With the steps shown or described are performed in an order that is different from the one herein, or they are fabricated to each integrated circuit dies
Block, or by them multiple modules or step be fabricated to single integrated circuit module and realize.So the present invention does not limit
It is combined in any specific hardware and software.
It cannot recognize being further described made by the embodiment of the present invention the above content is specific embodiment is combined
The specific implementation of the fixed present invention is confined to these explanations.For those of ordinary skill in the art to which the present invention belongs,
Without departing from the inventive concept of the premise, a number of simple deductions or replacements can also be made, all shall be regarded as belonging to the present invention
Protection domain.
Claims (10)
1. a kind of short message service center's based reminding method, including：
Short Message Service Gateway determines that the reception terminal is reachable based on terminal is received in the registration of application server；
The Short Message Service Gateway is obtained waits for that throwing the failed delivery that short message is stored again records for the reception terminal, the mistake
Lose delivery record from the Short Message Service Gateway to the receptions terminal deliver this when throw again short message failure when generate；
The Short Message Service Gateway records triggering short message center according to the failed delivery and reminds, with indicate short message service center again to
The reception terminal waits for throwing short message again described in delivering.
2. short message service center's based reminding method as described in claim 1, which is characterized in that further include：
After the success of delivery again for waiting for throwing short message again, removing waits for throwing short message again the Short Message Service Gateway for this
Failed delivery records.
3. short message service center's based reminding method as claimed in claim 1 or 2, which is characterized in that the Short Message Service Gateway is based on receiving
Terminal determines that the reception terminal further includes up to before in the registration of application server：The Short Message Service Gateway is unsuccessfully thrown described
It passs in record storage to external memory.
4. short message service center's based reminding method as claimed in claim 3, which is characterized in that the Short Message Service Gateway is unsuccessfully thrown described
It passs in record storage to external memory and includes：
The Short Message Service Gateway is in the configuration file update request for being sent to home location register/home signature user server
Carrying unsuccessfully identifies, to inform the home location register/home signature user server itself pair and corresponding short message
Failure is delivered, will wait for that the failed delivery record storage for throwing short message again is contracted to the home location register/ownership for this
On client server.
5. short message service center's based reminding method as claimed in claim 3, which is characterized in that the Short Message Service Gateway is based on the reception
The registration of terminal on the application server determine the reception terminal up to when, obtaining failed delivery record includes：
The Short Message Service Gateway determines the reception terminal according to first registration of the reception terminal on the application server
When reachable, the failed delivery record is obtained on the external memory.
6. short message service center's based reminding method as claimed in claim 3, which is characterized in that further include：The Short Message Service Gateway is by institute
State failed delivery record storage to while the external memory by the failed delivery record storage to local；
And/or
After the Short Message Service Gateway obtains failed delivery record from external memory, the failed delivery that will get
Record storage is to locally.
7. short message service center's based reminding method as claimed in claim 6, which is characterized in that the Short Message Service Gateway is based on the reception
The registration of terminal on the application server determine the reception terminal up to when, obtaining failed delivery record includes：
The Short Message Service Gateway determines the reception terminal according to refresh registration of the reception terminal on the application server
When reachable, the Short Message Service Gateway obtains the failed delivery record from local.
8. a kind of Short Message Service Gateway, which is characterized in that including：
Logging modle, for after receiving terminal delivery short message delivery failure, storage to be directed to the mistake for waiting for throwing short message again
Lose delivery record；
Determining module, for determining that the reception terminal is reachable in the registration of application server based on reception terminal；
Acquisition module waits for that throwing the failed delivery that short message is stored again records for obtaining for the reception terminal；
Reminding module is reminded for recording triggering short message center according to the failed delivery, to indicate short message service center again
To the reception terminal deliver described in wait for throwing short message again and lose.
9. Short Message Service Gateway as claimed in claim 8, which is characterized in that the logging modle is for recording the failed delivery
It stores on external memory.
10. Short Message Service Gateway as claimed in claim 9, which is characterized in that the determining module is according to the reception terminal in institute
State first registration on application server determine the reception terminal up to when, the acquisition module is from the external memory
Obtain the failed delivery record.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710289506.2A CN108810830A (en) | 2017-04-27 | 2017-04-27 | A kind of short message service center's based reminding method and Short Message Service Gateway |
| PCT/CN2018/084123 WO2018196715A1 (en) | 2017-04-27 | 2018-04-23 | Short message centre reminding method and short message gateway |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710289506.2A CN108810830A (en) | 2017-04-27 | 2017-04-27 | A kind of short message service center's based reminding method and Short Message Service Gateway |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108810830A true CN108810830A (en) | 2018-11-13 |
Family
ID=63918857
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710289506.2A Withdrawn CN108810830A (en) | 2017-04-27 | 2017-04-27 | A kind of short message service center's based reminding method and Short Message Service Gateway |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108810830A (en) |
| WO (1) | WO2018196715A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022012161A1 (en) * | 2020-07-16 | 2022-01-20 | 中兴通讯股份有限公司 | Method, apparatus and system for processing short message delivery failure |
| WO2022148141A1 (en) * | 2021-01-06 | 2022-07-14 | 中国电信股份有限公司 | Method, apparatus, and system for implementing servitization of short message service center alert information |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1758774A (en) * | 2004-10-10 | 2006-04-12 | 华为技术有限公司 | Method for selecting short message routing at multiple path |
| CN103037328A (en) * | 2011-09-30 | 2013-04-10 | 华为终端有限公司 | Method and device for resending short messages |
| CN105792147A (en) * | 2014-12-24 | 2016-07-20 | 中兴通讯股份有限公司 | Short message delivery failure processing method, device and system |
| CN105827660A (en) * | 2016-05-31 | 2016-08-03 | 浪潮集团有限公司 | IP-SM-GW application and data separation server and realization method |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101998311A (en) * | 2009-08-13 | 2011-03-30 | 中国电信股份有限公司 | Method and device for sending short message |
| WO2015161441A1 (en) * | 2014-04-22 | 2015-10-29 | Qualcomm Incorporated | Receiving embms on a single-radio-multiple-standby user equipment |
| CN106211105B (en) * | 2015-04-30 | 2019-09-06 | 中国电信股份有限公司 | Handle the method and system and application server of short message |
-
2017
- 2017-04-27 CN CN201710289506.2A patent/CN108810830A/en not_active Withdrawn
-
2018
- 2018-04-23 WO PCT/CN2018/084123 patent/WO2018196715A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1758774A (en) * | 2004-10-10 | 2006-04-12 | 华为技术有限公司 | Method for selecting short message routing at multiple path |
| CN103037328A (en) * | 2011-09-30 | 2013-04-10 | 华为终端有限公司 | Method and device for resending short messages |
| CN105792147A (en) * | 2014-12-24 | 2016-07-20 | 中兴通讯股份有限公司 | Short message delivery failure processing method, device and system |
| CN105827660A (en) * | 2016-05-31 | 2016-08-03 | 浪潮集团有限公司 | IP-SM-GW application and data separation server and realization method |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022012161A1 (en) * | 2020-07-16 | 2022-01-20 | 中兴通讯股份有限公司 | Method, apparatus and system for processing short message delivery failure |
| WO2022148141A1 (en) * | 2021-01-06 | 2022-07-14 | 中国电信股份有限公司 | Method, apparatus, and system for implementing servitization of short message service center alert information |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2018196715A1 (en) | 2018-11-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9397968B2 (en) | Method for processing deferred message | |
| CN101189844B (en) | Method, server and system for notification | |
| US9247418B2 (en) | Communication-session termination when subscriber server is unavailable | |
| US9413618B2 (en) | Method, system and devices for managing user provisioning of a service in an IMS network | |
| CN103929730A (en) | Trigger message sending method, device and system | |
| CN100471150C (en) | Method for establishing subscribe communication and method for subscribing user events | |
| EP2007152A2 (en) | Message route method,system and device based on ip transmission | |
| CN103078873B (en) | A kind of asynchronous fault-tolerance approach of message, device and equipment | |
| KR100617775B1 (en) | Method for managing duplicated message notification in multimedia messaging service | |
| CN108810830A (en) | A kind of short message service center's based reminding method and Short Message Service Gateway | |
| US20090248799A1 (en) | Method and server for user identifier update | |
| CN101924737A (en) | Subscribing method and system of user data and related equipment | |
| US20150319588A1 (en) | Method and device for sms processing through ims network | |
| US9332055B2 (en) | Method and apparatus for routing XCAP requests | |
| CN100387014C (en) | Method for treating abnormity of registration in procedure of registering users | |
| CN101384085A (en) | Terminal registration method, apparatus and system | |
| WO2015196809A1 (en) | Message processing method and device | |
| US9596577B1 (en) | Relaying mobile communications | |
| CN108337215B (en) | File transmission method, system and device and electronic equipment | |
| US20080288643A1 (en) | Session Initiation Protocol Signalling | |
| WO2022056931A1 (en) | Methods and devices for performing service subscriptions | |
| US8805346B1 (en) | Caller information retrieval system for unavailable calls | |
| EP2667568A1 (en) | Methods and apparatuses for handling data-related requests | |
| CN105376727A (en) | Data card processing method and device | |
| CN112714430B (en) | Exception handling method and device, storage medium and server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20181113 |
|
| WW01 | Invention patent application withdrawn after publication |