Embodiment
As stated in the Background Art, the characteristic of MTCDeviceTriggering is proposed in existing technical standard, MTCServer can by MTCDeviceTrigger Message recover signature terminal equipment access Server, and in order to allow MTCServer know, whether MTCDeviceTrigger message is transmitted successfully, network needs the demand reporting DeviceTrigger message whether transmission success to MTCServer, but the framework of the SAE network according to existing 3GPP, under adopting NAS signaling to trigger the mode of MTCDevice, when processing multiple Trigger process at the same time, network can not distinguish corresponding message specifically for which Trigger process, naturally how network reports problem from Trigger message whether transmission success to MTCServer can not also just be solved.
In order to overcome such defect, the embodiment of the present invention proposes a kind of delivery confirmation method of MTCDevice Trigger message, under employing NAS signaling triggers the scene of MTCDevice, the specific message fed back by terminal equipment, confirms whether MTCDevice Trigger message is delivered successfully.
In corresponding technical scheme by concrete management server as judging main body, confirm whether MTCDevice Trigger message is delivered successfully.
In concrete enforcement scene, management server mentioned here can be MME or SGSN, and the change of concrete physical entity type can't affect protection scope of the present invention.
As shown in Figure 3, the schematic flow sheet of the delivery confirmation method of a kind of MTCDevice Trigger message proposed for the embodiment of the present invention, the method specifically comprises the following steps:
Step S301, when management server generates MTCDevice Trigger message according to the triggering request that receives, described management server is described MTCDevice Trigger message allocation identification information, and described MTCDevice Trigger message and described identification information is bound in this locality and store.
Step S302, described management server send first message of carrying described identification information and described MTCDevice Trigger message to terminal equipment.
When described management server receive that described terminal equipment returns carry identification information and the second message to the acknowledge message of MTCDevice Trigger message time, perform step S303.
Whether step S303, described management server judge that the described identification information stored is bound in identification information entrained in described second message and this locality consistent.
In the technical scheme that the embodiment of the present invention proposes, terminal equipment is after processing the MTCDevice Trigger message in the first message, identification information in this first message can be carried in the second message together with corresponding acknowledge message and feed back to management equipment, thus management server can carry out recognition and verification message accordingly on earth for which MTCDevice Trigger message.
Based on above-mentioned roadmap, if the judged result in this step is consistent, then perform step S304.
Step S304, described management server determine that acknowledge message entrained in described second message is the acknowledge message to the described MTCDevice Trigger message that this locality binding stores, delete the described MTCDevice Trigger message of binding storage and described identification information in this locality, and forward the acknowledge message entrained by described second message.
By such process, accurately can recognize the acknowledge message for corresponding MTCDevice Trigger message, and this acknowledge message is reported, thus, determine MTCDevice Trigger message transmission success.
In above-mentioned processing procedure, if the judged result of step S303 is inconsistent, then show that the acknowledge message in current the second received message is not the acknowledge message of this locality being bound to the described MTCDevice Trigger message stored, therefore, concrete process can't be carried out to the described MTCDevice Trigger message that this locality binding stores according to the second current message, but continue the second message waiting for other, thus, enable management server distinguish acknowledge message for be which MTCDevice Trigger message, and and then determine that the delivery of which MTCDevice Trigger message is successful.
It is further noted that, the delivery report mechanism of the similar short message applied in prior art is not suitable for using NAS signaling to carry out the mechanism of Trigger Message Transmission, because, the node of similar GMSC is not had in this framework, meanwhile, Trigger mechanism has ageing feature, needs the life cycle considering Trigger message, obviously, existing technical scheme does not consider such problem.
In order to overcome such defect, introduce the treatment mechanism of life cycle in the technical scheme that the embodiment of the present invention proposes further, it is as follows that corresponding processing procedure needs to carry out adjustment.
In step S301, in order to embody the life cycle characteristic of MTCDevice Trigger message, described MTCDevice Trigger message and described identification information are bound in this locality and are stored by described management servers process, also store the life cycle of described MTCDevice Trigger message in this locality.
The process of step S302 remains unchanged, and after this, whether needing expires according to life cycle processes accordingly, is specifically divided into following three kinds of situations.
Situation one, before described life cycle arrives, described management server receives second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns.
In such cases, perform step S303.
If judged result is consistent, described management server determines that acknowledge message entrained in described second message is the acknowledge message to the described MTCDevice Trigger message that this locality binding stores, the described MTCDevice Trigger message of binding storage and described identification information is deleted in this locality, and the life cycle of described MTCDevice Trigger message, and forward the acknowledge message entrained by described second message.
If judged result is inconsistent, then show that the acknowledge message in current the second received message is not the acknowledge message of this locality being bound to the described MTCDevice Trigger message stored, therefore, concrete process can't be carried out to the described MTCDevice Trigger message that this locality binding stores according to the second current message, but continue the second message waiting for other, thus, enable management server distinguish acknowledge message for be which MTCDevice Trigger message, and and then determine which MTCDevice Trigger message delivery success.
Situation two, described management server, before described life cycle arrives, do not receive second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns.
In the present case, in complete life cycle, management server does not receive any satisfactory second message, nature, also the acknowledge message to the described MTCDevice Trigger message that this locality binding stores can not just be received, therefore, in the life cycle of this MTCDevice Trigger message, this MTCDevice Trigger message is not delivered successfully, described management server deletes the described MTCDevice Trigger message of binding storage and described identification information in this locality, and the life cycle of described MTCDevice Trigger message, and report described MTCDevice Trigger message to trigger unsuccessfully.
Situation three, described management server, before described life cycle arrives, do not receive the second message of the acknowledge message of carrying the described MTCDevice Trigger message that this locality binding stores.
This kind of situation is equivalent to the repeatedly circulation that a kind of judged result of situation is inconsistent situation, although namely management server have received the second message in life cycle, but the identification information wherein carried is not all the identification information that local binding stores, namely the acknowledge message in current received each second message is not the acknowledge message to the described MTCDevice Trigger message that this locality binding stores, therefore, management server is determined in the complete life cycle of the described MTCDevice Trigger message stored in this locality binding, all do not receive the acknowledge message to this MTCDevice Trigger message, therefore, in the life cycle of this MTCDevice Trigger message, this MTCDevice Trigger message is not delivered successfully, described management server deletes the described MTCDevice Trigger message of binding storage and described identification information in this locality, and the life cycle of described MTCDevice Trigger message, and report described MTCDevice Trigger message to trigger unsuccessfully.
By the process of above-mentioned three kinds of situations, not only embody the life cycle characteristic of MTCDevice Trigger message, and based on this characteristic, introduce and differentiate that MTCDevice Trigger message triggers failed mechanism, can report in time and trigger failed result, avoid the reduction of the wasting of resources and the treatment effeciency unrestrictedly waiting for that the successful result of delivery is brought.
On the other hand, in the prior art scheme, due to reasons such as network congestions, MTCDevice Trigger message cannot send to terminal equipment in time, management server also can not take other remedial measure, only can the corresponding acknowledge message of wait-receiving mode always, and, due to reasons such as network congestions, also may there is the situation not receiving the acknowledge message to corresponding MTCDevice Trigger message that terminal equipment returns in management server, and under such circumstances, obvious difference can be there is in terminal equipment and management server for the understanding nature of current triggering result, on the one hand, terminal equipment slowly cannot carry out corresponding follow-up business triggering successfully, and on the other hand, management server then can the corresponding acknowledge message of wait-receiving mode always, such result result in corresponding processing procedure and can not normally continue, and not corresponding mechanism ensures delivery success rate, affect the reliability of the transmitting procedure of MTCDevice Trigger message.
In order to overcome such defect, introduce the retransmission mechanism based on timer in the technical scheme that the embodiment of the present invention proposes further, it is as follows that corresponding processing procedure needs to carry out adjustment.
The process of step S301 remains unchanged.
In step s 302, described management server sends to terminal equipment and carries in the process of the first message of described identification information and described MTCDevice Trigger message, and described management server also starts the timer corresponding with described identification information.
And after this, need according to timer whether time-out is come to process accordingly, be specifically divided into following three kinds of situations.
Situation one, described management server, before described timer expired, receive second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns.
In such cases, perform step S303.
If judged result is consistent, described management server determines that acknowledge message entrained in described second message is the acknowledge message to the described MTCDevice Trigger message that this locality binding stores, then stop the timer corresponding with described identification information, delete the described MTCDevice Trigger message of binding storage and described identification information in this locality, and forward the acknowledge message entrained by described second message.
If judged result is inconsistent, then show that the acknowledge message in current the second received message is not the acknowledge message of this locality being bound to the described MTCDevice Trigger message stored, therefore, concrete process can't be carried out to the described MTCDevice Trigger message that this locality binding stores according to the second current message, but continue the second message waiting for other, thus, enable management server distinguish acknowledge message for be which MTCDevice Trigger message, and and then determine which MTCDevice Trigger message delivery success.
Situation two, described management server, before described timer expired, do not receive second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns.
In the present case, within the complete time-count cycle that timer is current, management server does not receive any satisfactory second message, nature, also the acknowledge message to the described MTCDevice Trigger message that this locality binding stores can not just be received, therefore, within the complete time-count cycle that the timer of this MTCDevice Trigger message is current, this MTCDevice Trigger message is not delivered successfully, thus, start retransmission mechanism, described management server sends first message of carrying described identification information and described MTCDevice Trigger message again to terminal equipment, and restart the timer corresponding with described identification information.
Situation three, described management server, before described timer expired, do not receive the second message of the acknowledge message of carrying the described MTCDevice Trigger message that this locality binding stores.
This kind of situation is equivalent to the repeatedly circulation that a kind of judged result of situation is inconsistent situation, although namely management server have received satisfactory second message within this time-count cycle of described timer, but the identification information wherein carried is not all the identification information that local binding stores, namely the acknowledge message in current received each second message is not the acknowledge message to the described MTCDevice Trigger message that this locality binding stores, therefore, management server is determined within this time-count cycle, all do not receive the acknowledge message to this MTCDevice Trigger message, therefore, within this this time-count cycle, this MTCDevice Trigger message is not delivered successfully, thus, start retransmission mechanism, described management server sends first message of carrying described identification information and described MTCDevice Trigger message again to terminal equipment, and restart the timer corresponding with described identification information.
By the process of above-mentioned three kinds of situations, introduce the retransmission mechanism based on timer, management server unrestrictedly can not be waited for and deliver successful result, but at timer expired and do not receive deliver successful result, directly MTCDevice Trigger message is retransmitted, improve the delivery success rate of MTCDevice Trigger message as far as possible.
Even if based on such process due to reasons such as network congestions, cause the situation that MTCDevice Trigger message cannot be sent in time or acknowledge message cannot return in time, also can be remedied by re-transmission, ensure that MTCDevice Trigger message can be delivered successfully as far as possible.
In order to realize better technique effect, the technical scheme that the embodiment of the present invention proposes can also introduce the treatment mechanism of life cycle and the retransmission mechanism based on timer simultaneously, in limited life cycle, improved the delivery success rate of MTCDevice Trigger message as far as possible by retransmission mechanism.
Based on such technical thought, further the technical scheme that the aforesaid embodiment of the present invention proposes is adjusted, as shown in Figure 4, for a kind of schematic flow sheet introducing the treatment mechanism of life cycle and the delivery confirmation method based on the MTCDevice Trigger message of the retransmission mechanism of timer that the embodiment of the present invention proposes simultaneously, the method specifically comprises the following steps:
Step S401, when management server generates MTCDevice Trigger message according to the triggering request that receives, described management server is described MTCDevice Trigger message allocation identification information, described MTCDevice Trigger message and described identification information are bound in this locality and stores, and store the life cycle of described MTCDevice Trigger message in this locality.
Step S402, described management server send first message of carrying described identification information and described MTCDevice Trigger message to terminal equipment, and start the timer corresponding with described identification information.
Wherein, the duration of described life cycle is more than or equal to the duration of the time-count cycle of the timer corresponding with described identification information.
Step S403, described management server judge before described timer expired, whether receive second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns.
If judged result is yes, then perform step S404;
If judged result is no, then perform step S406.
Wherein, the situation that judged result is no comprises two kinds:
Situation one, before described timer expired, do not receive second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns.
Situation two, to determine that within this time-count cycle of described timer acknowledge message entrained in received all second message is not all the acknowledge message to the described MTCDevice Trigger message that this locality binding stores by subsequent step.
Whether step S404, described management server judge that the described identification information stored is bound in identification information entrained in described second message and this locality consistent.
If consistent, then perform step S405;
If inconsistent, then return step S403.
In the case of inconsistencies, management server thinks that this second message be currently received does not have an impact to current timer, therefore, needs to return step S403, proceeds the reception of other the second message.
There are multiple timers of corresponding different identification information if especially current, so the judgement of this step obviously can avoid second message of carrying different identification information for the interference of other timers, monitors accurately to the delivery process of the MTCDevice Trigger message that corresponding identification information is bound.
Step S405, described management server determine that acknowledge message entrained in described second message is the acknowledge message to the described MTCDevice Trigger message that this locality binding stores, described management server stops the timer corresponding with described identification information, the described MTCDevice Trigger message of binding storage and described identification information is deleted in this locality, and the life cycle of described MTCDevice Trigger message, and forward the acknowledge message entrained by described second message.
Step S406, described management server judge whether described MTCDevice Trigger message meets retransmission condition.
If met, return and perform step S402, namely described management server sends first message of carrying described identification information and described MTCDevice Trigger message again to terminal equipment, and restarts the timer corresponding with described identification information;
If do not met, then perform step S407.
In concrete process scene, the judgement processing procedure of this step is specifically as follows:
The life cycle of the described MTCDevice Trigger message that described management server stores according to this locality, determines the duration of the life cycle of current residual.
If the duration of the life cycle of current residual is more than or equal to the duration of the time-count cycle of the timer corresponding with described identification information, then described management server determines that described MTCDevice Trigger message meets retransmission condition.
If the duration of the life cycle of current residual is less than the duration of the time-count cycle of the timer corresponding with described identification information, then described management server determines that described MTCDevice Trigger message is discontented with sufficient retransmission condition.
Step S407, described management server delete the described MTCDevice Trigger message of binding storage and described identification information in this locality, and the life cycle of described MTCDevice Trigger message, and report described MTCDevice Trigger message to trigger unsuccessfully.
It should be noted that; introduce the treatment mechanism of above-mentioned life cycle in the technical scheme whether proposed in the embodiment of the present invention and/or can determine according to the actual needs based on the retransmission mechanism of timer, the change of the corresponding processing scheme produced therefrom can't affect protection scope of the present invention.
No matter adopt which kind of above-mentioned scheme, the equal demand fulfillment of described identification information at least can be interim the process of unique identification transmission MTCDevice Trigger message, or the requirement of unique identification MTCDevice Trigger message that at least can be interim, its concrete form can comprise:
Described management server is the Transaction Identifier that the transmitting procedure of this MTCDevice Trigger message and subsequent message thereof is distributed; Or,
Described management server is the sequence number that described MTCDevice Trigger message distributes.
In actual applications, concrete employing can select which kind of above-mentioned form as required, and such change does not affect protection scope of the present invention.
Corresponding, for this kind of scheme, as follows in the respective handling process of terminal equipment side:
When terminal equipment successfully receive that management server sends carry the first message of identification information and MTCDevice Trigger message time, described terminal equipment sends second message of carrying described identification information and the acknowledge message to described MTCDevice Trigger message to described management server.
Wherein, the requirement of described identification information demand fulfillment and concrete form thereof, see aforementioned explanation, do not repeat them here.
Concrete processing mode is see above-mentioned explanation, similar with it, at this, and no longer repeat specification.
Compared with prior art, the technical scheme that the embodiment of the present invention proposes has the following advantages:
By applying the technical scheme of the embodiment of the present invention, with management server (such as MME or SGSN) for judge main body, when sending MTCDevice Trigger message to terminal equipment, carry corresponding identification information, and according to the acknowledge message of carrying same identification information whether receiving terminal equipment and return, determine whether corresponding MTCDevice Trigger message is delivered successfully, thus, solve in prior art and can not determine whether MTCDevice Trigger message delivers successful problem, can determine whether MTCDevice Trigger message is successfully received by terminal equipment accurately, improve the reliability of MTCDevice Trigger message delivery process.
Below, in conjunction with concrete application scenarios, the technical scheme that the embodiment of the present invention proposes is described.
In the technical scheme that the embodiment of the present invention proposes, for the problem of prior art, the scene of multiple MTCDeviceTrigger is particularly received for MME/SGSN, provide a kind of MTCDeviceTrigger message delivery confirmation method, thus, can determine that whether MTCDevice Trigger message is successfully received by terminal equipment, improves the reliability of MTCDevice Trigger message delivery process accurately.
For convenience of description, the embodiment of the present invention is specifically described using MME/SGSN as the concrete example of aforesaid management server, and in the application scenarios of reality, the Change of types of concrete management server can't affect protection scope of the present invention.
Accordingly, whether transmitting successful determination point using MME/SGSN as DeviceTrigger, and using identification information under the scene associating Trigger message and delivery confirmation message, specific embodiment is described as follows.
As shown in Figure 5, be the schematic flow sheet of the delivery confirmation method of the MTCDevice Trigger message under a kind of embody rule scene that the embodiment of the present invention proposes, the method specifically comprises the following steps:
Step S501, MME/SGSN are when encapsulating Trigger message, for each Trigger dispensing transaction mark Transactionidentifier (Transactionidentifier is used to an association message flow), each Trigger message and a Transactionidentifier are bound and stored.
Concrete, in the processing procedure of this step shown in Fig. 5, TriggerMessage is the message that MTCServer issues, in DOWNLINKGENERICNASTRANSPORT message, encapsulate TransactionIdentifier.
In concrete process scene, the form of DOWNLINKGENERICNASTRANSPORT message is as shown in table 1.
The form of table 1DOWNLINKGENERICNASTRANSPORT message
Further, in this step, MME/SGSN selects to insert TransactionID in Additionalinformation, and concrete form is as shown in table 2.
The form of table 2Additionalinformation
Concrete, the value part shown in table 2 can insert TransactionIdentifier, Transactionidentifier needs to arrange according to concrete scene, and the change of concrete form does not affect protection scope of the present invention.
Step S502, MME/SGSN use NAS signaling (if UE is at Idle state, then first wanting paging UE) by Trigger Message Transmission to UE, simultaneously startup timer T.
Wherein, the value of timer T is relevant to concrete realization.
Such as, suppose that Trigger life cycle is 60s, retransmit 5 times, then T can be set to 12s.
After step S503, UE receive the NAS signaling of carrying Trigger message, be the Trigger message transmitting confirmation that each success receives, in the message of carrying acknowledge message, fill in identical Transactionidentifiervalue equally.
After step S504, MME/SGSN receive the message of carrying Transactionidentifier and acknowledge message, what MME/SGSN determined to receive by the Transactionidentifier in message is acknowledge message to which bar Trigger message, thus delete this Trigger message stored, and stop corresponding timer T.
If step S505 MME/SGSN is after timer T time-out, still certain Trigger acknowledge message is not received, if the residue life cycle of this Trigger message is still greater than the time-count cycle of a complete timer T, then realize according to MME/SGSN, again retransmit Trigger message.Repeatedly (realize relevant) after time-out, judge to deliver unsuccessfully, reported unsuccessfully to MTCServer by HSS/HLR or MTC-IWF.
Compared with prior art, the technical scheme that the embodiment of the present invention proposes has the following advantages:
By applying the technical scheme of the embodiment of the present invention, with management server (such as MME or SGSN) for judge main body, when sending MTCDevice Trigger message to terminal equipment, carry corresponding identification information, and according to the acknowledge message of carrying same identification information whether receiving terminal equipment and return, determine whether corresponding MTCDevice Trigger message is delivered successfully, thus, solve in prior art and can not determine whether MTCDevice Trigger message delivers successful problem, can determine whether MTCDevice Trigger message is successfully received by terminal equipment accurately, improve the reliability of MTCDevice Trigger message delivery process.
In order to realize the technical scheme of the embodiment of the present invention, the embodiment of the present invention additionally provides a kind of management server, and its structural representation as shown in Figure 6, at least comprises:
Distribution module 61, for when generating MTCDevice Trigger message according to the triggering request received, is described MTCDevice Trigger message allocation identification information;
Memory module 62, the identification information for described MTCDevice Trigger message and described distribution module 61 being distributed carries out binding and stores;
Sending module 63, for sending first message of carrying identification information that described distribution module 61 distributes and described MTCDevice Trigger message to terminal equipment;
Receiver module 64, for receiving the message that described terminal equipment returns;
Judge module 65, for receive when described receiver module 64 that described terminal equipment returns carry identification information and the second message to the acknowledge message of MTCDevice Trigger message time, whether unanimously judge that identification information entrained in described second message and described memory module 62 bind the described identification information stored;
Processing module 66, for when the judged result of described judge module 65 is consistent, determine that acknowledge message entrained in the second message received by described receiver module 64 is the acknowledge message of described memory module 62 being bound to the described MTCDevice Trigger message stored, notify described MTCDevice Trigger message and described identification information that described memory module 62 is deleted binding and stored, and the acknowledge message entrained by notifying the second message that described sending module 63 forwards received by described receiver module 64.
Further, described memory module 62, also for storing the life cycle of described MTCDevice Trigger message.
Accordingly, described processing module 66, specifically for:
If before the life cycle arrival that described memory module 62 stores, described receiver module 64 receives second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns, and determine that acknowledge message entrained in described second message is the acknowledge message of described memory module 62 being bound to the described MTCDevice Trigger message stored, then notify that described memory module 62 deletes the described MTCDevice Trigger message of binding storage and described identification information, and the life cycle of described MTCDevice Trigger message, and acknowledge message entrained in notifying the second message that described sending module 63 forwards received by described receiver module 64,
If before the life cycle arrival that described memory module 62 stores, described receiver module 64 does not receive second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns, or before the life cycle that described memory module 62 stores arrives, described receiver module 64 does not receive the second message of the acknowledge message of carrying the described MTCDevice Trigger message that this locality binding stores, then notify that described memory module 62 deletes the described MTCDevice Trigger message of binding storage and described identification information, and the life cycle of described MTCDevice Trigger message, and notify that described sending module 63 reports described MTCDevice Trigger message to trigger unsuccessfully.
Under another kind of application scenarios, above-mentioned management server, also comprises:
Timing module 67, for when described sending module 63 sends first message of carrying identification information that described distribution module 61 distributes and described MTCDevice Trigger message to terminal equipment, starts the timer corresponding with described identification information.
Accordingly, described processing module 66, specifically for:
If before the timer expired that described timing module 67 starts, described receiver module 64 receives second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns, and determine that acknowledge message entrained in described second message is the acknowledge message of described memory module 62 being bound to the described MTCDevice Trigger message stored, then notify that described timing module 67 stops the timer corresponding with described identification information, notify that described memory module 62 deletes the described MTCDevice Trigger message of binding storage and described identification information, and acknowledge message entrained in notifying the second message that described sending module 63 forwards received by described receiver module 64,
If before the timer expired that described timing module 67 starts, described receiver module 64 does not receive second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns, or before the timer expired to start at described timing module 67, described receiver module 64 does not receive the second message of the acknowledge message of carrying the described MTCDevice Trigger message that this locality binding stores, then notify that described sending module 63 sends first message of carrying described identification information and described MTCDevice Trigger message again to terminal equipment, and notify that described timing module 67 restarts the timer corresponding with described identification information.
Under another kind of application scenarios,
Described distribution module 61, specifically for when generating MTCDevice Trigger message according to the triggering request received, is described MTCDevice Trigger message allocation identification information;
Described memory module 62, the identification information specifically for described MTCDevice Trigger message and described distribution module 61 being distributed carries out binding and stores, and stores the life cycle of described MTCDevice Trigger message;
Described sending module 63, specifically for sending first message of carrying identification information that described distribution module 61 distributes and described MTCDevice Trigger message to terminal equipment;
Timing module 67, for when described sending module 63 sends first message of carrying identification information that described distribution module 61 distributes and described MTCDevice Trigger message to terminal equipment, start the timer corresponding with described identification information, wherein, the duration of described life cycle is more than or equal to the duration of the time-count cycle of the timer corresponding with described identification information;
Described receiver module 64, specifically for receiving the message that described terminal equipment returns;
Described judge module 65, specifically for before the timer expired that starts when described timing module 67, when what described receiver module 64 received that described terminal equipment returns carries identification information and the second message to the acknowledge message of MTCDevice Trigger message, whether unanimously judge that identification information entrained in described second message and described memory module 62 bind the described identification information stored;
Described processing module 66, specifically for when the judged result of described judge module 65 is consistent, determine that acknowledge message entrained in described second message is the acknowledge message of described memory module 62 being bound to the described MTCDevice Trigger message stored, notify that described timing module 67 stops the timer corresponding with described identification information, notify that described memory module 62 deletes the described MTCDevice Trigger message of binding storage and described identification information, and the life cycle of described MTCDevice Trigger message, and acknowledge message entrained in notifying the second message that described sending module 63 forwards received by described receiver module 64.
Wherein, described processing module 66, also for:
If before the timer expired that described timing module 67 starts, described receiver module 64 does not receive second message of carrying identification information and the acknowledge message to MTCDevice Trigger message that described terminal equipment returns, or before the timer expired to start at described timing module 67, described receiver module 64 does not receive the second message of the acknowledge message of carrying the described MTCDevice Trigger message that this locality binding stores, and notifies that described judge module 65 judges whether described MTCDevice Trigger message meets retransmission condition;
If described judge module 65 judges to meet retransmission condition, then notify that described sending module 63 sends first message of carrying described identification information and described MTCDevice Trigger message again to terminal equipment, and notify that described timing module 67 restarts the timer corresponding with described identification information;
If described judge module 65 judges discontented sufficient retransmission condition, then notify that described memory module 62 deletes the described MTCDevice Trigger message of binding storage and described identification information, and the life cycle of described MTCDevice Trigger message, and notify that described sending module 63 reports described MTCDevice Trigger message to trigger unsuccessfully.
Further, described judge module 65, specifically for:
According to the life cycle of the described MTCDevice Trigger message that described memory module 62 stores, determine the duration of the life cycle of current residual;
If the duration of the life cycle of current residual is more than or equal to the duration of the time-count cycle of the timer corresponding with described identification information, then judge that described MTCDevice Trigger message meets retransmission condition;
If the duration of the life cycle of current residual is less than the duration of the time-count cycle of the timer corresponding with described identification information, then judge that described MTCDevice Trigger message is discontented with sufficient retransmission condition.
It is to be noted, described distribution module 61, specifically for distributing the process of unique identification transmission MTCDevice Trigger message that at least can be interim for described MTCDevice Trigger message, or unique identification MTCDevice Trigger message that at least can be interim is as identification information, wherein, described identification information, specifically comprises:
For the Transaction Identifier that the transmitting procedure of this MTCDevice Trigger message and subsequent message thereof is distributed; Or,
For the sequence number that described MTCDevice Trigger message distributes.
In actual applications, above-mentioned management server, is specially MME or SGSN.
Further, the embodiment of the present invention additionally provides a kind of terminal equipment, and its structural representation as shown in Figure 7, at least comprises:
Receiver module 71, for the message that receiving management server sends;
Sending module 72, for successfully receive at described receiver module 71 that described management server sends carry the first message of identification information and MTCDevice Trigger message time, send second message of carrying described identification information and the acknowledge message to described MTCDevice Trigger message to described management server.
Compared with prior art, the technical scheme that the embodiment of the present invention proposes has the following advantages:
By applying the technical scheme of the embodiment of the present invention, with management server (such as MME or SGSN) for judge main body, when sending MTCDevice Trigger message to terminal equipment, carry corresponding identification information, and according to the acknowledge message of carrying same identification information whether receiving terminal equipment and return, determine whether corresponding MTCDevice Trigger message is delivered successfully, thus, solve in prior art and can not determine whether MTCDevice Trigger message delivers successful problem, can determine whether MTCDevice Trigger message is successfully received by terminal equipment accurately, improve the reliability of MTCDevice Trigger message delivery process.
Through the above description of the embodiments, those skilled in the art can be well understood to the embodiment of the present invention can by hardware implementing, and the mode that also can add necessary general hardware platform by software realizes.Based on such understanding, the technical scheme of the embodiment of the present invention can embody with the form of software product, it (can be CD-ROM that this software product can be stored in a non-volatile memory medium, USB flash disk, portable hard drive etc.) in, comprise some instructions and perform each method implementing described in scene of the embodiment of the present invention in order to make a computer equipment (can be personal computer, server, or network equipment etc.).
It will be appreciated by those skilled in the art that accompanying drawing is a schematic diagram preferably implementing scene, the module in accompanying drawing or flow process might not be that the enforcement embodiment of the present invention is necessary.
It will be appreciated by those skilled in the art that the module in the device implemented in scene can carry out being distributed in the device of enforcement scene according to implementing scene description, also can carry out respective change and being arranged in the one or more devices being different from this enforcement scene.The module of above-mentioned enforcement scene can merge into a module, also can split into multiple submodule further.
The invention described above embodiment sequence number, just to describing, does not represent the quality implementing scene.
Be only the several concrete enforcement scene of the embodiment of the present invention above, but the embodiment of the present invention is not limited thereto, the changes that any person skilled in the art can think of all should fall into the business limited field of the embodiment of the present invention.