CN102427604A - Method and device for confirming delivery of MTC (Machine Type Communication) Device trigger message - Google Patents

Method and device for confirming delivery of MTC (Machine Type Communication) Device trigger message Download PDF

Info

Publication number
CN102427604A
CN102427604A CN2011103976587A CN201110397658A CN102427604A CN 102427604 A CN102427604 A CN 102427604A CN 2011103976587 A CN2011103976587 A CN 2011103976587A CN 201110397658 A CN201110397658 A CN 201110397658A CN 102427604 A CN102427604 A CN 102427604A
Authority
CN
China
Prior art keywords
mtc device
message
trigger messages
device trigger
identification information
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.)
Granted
Application number
CN2011103976587A
Other languages
Chinese (zh)
Other versions
CN102427604B (en
Inventor
王胡成
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Academy of Telecommunications Technology CATT
Datang Mobile Communications Equipment Co Ltd
Original Assignee
China Academy of Telecommunications Technology CATT
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Academy of Telecommunications Technology CATT filed Critical China Academy of Telecommunications Technology CATT
Priority to CN201510883429.4A priority Critical patent/CN105306183B/en
Priority to CN201110397658.7A priority patent/CN102427604B/en
Publication of CN102427604A publication Critical patent/CN102427604A/en
Priority to PCT/CN2012/083457 priority patent/WO2013078928A1/en
Application granted granted Critical
Publication of CN102427604B publication Critical patent/CN102427604B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

The embodiment of the invention discloses a method and device for confirming delivery of an MTC (Machine Type Communication) Device trigger message. The technical scheme provided by the embodiment of the invention is applied; a management server such as an MME (Mobility Management Entity) or an SGSN (Serving General Packet Radio Service Support Node) is adopted as a judging entity; when the MTC Device trigger message is sent to a terminal device, corresponding identification information is carried; and whether the corresponding MTC Device trigger message is delivered successfully or not is confirmed according to whether the confirmed message with the same identification information returned by the terminal device is received or not, so that the problem in the prior art that whether the MTC Device trigger message is delivered successfully or not can not be confirmed is solved, whether the MTC Device trigger message is received successfully or not by the terminal device can be accurately confirmed, and the reliability of an MTC Device trigger message delivery process is improved.

Description

The delivery confirmation method and apparatus of MTC Device trigger messages
Technical field
The present invention relates to communication technical field, particularly a kind of delivery confirmation method and apparatus of MTC Device trigger messages.
Background technology
In the prior art, comprise with MTC (Machine Type Communication, the communication of machine class) the relevant demand of Device Trigger (device fires):
Network should be able to be based on the triggering indication triggering MTC terminal initiation of MTC Server (server) transmission and communicating by letter of MTC Server.
Communicating by letter between indication and foundation and MTC Server should be able to receive be triggered from network in the MTC terminal.Possible situation comprises:
When MTC terminal off-line (offline), receive and trigger indication.
As MTC terminal online (online) but receive when not setting up data and connecting and trigger indication.
When also having set up to receive when data connect, MTC terminal online (online) trigger indication.
Here need to prove; In the prior art; Corresponding to 3GPP (Third Generation Partnership Project, 3G (Third Generation) Moblie gpp) network system, the data connection is meant PDP (the Packet Data Protocol that in the 3GPP network, sets up at the terminal; Packet data protocol) context or PDN (Packet Data Network, packet data network) connect.
And in existing technical scheme; Also propose to support HPLMN (the Home Public Land Mobile Network of MTC Device Trigger characteristic; The home public land mobile network network) being used to of providing transmits Trigger message and must satisfy following requirement to the interface of this PLMN (Public Land Mobile Network, PLMN).
-shall?allow?for?providing?a?validity?or?life?time?that?indicates?how?long?the?network?should?store?the?trigger?request?when?it?cannot?be?delivered?to?the?UE,e.g.when?the?UE?is?not?reachable?or?when?load?control?prevents?immediate?delivery
That is, must consider to provide life cycle indication network (for example UE is unreachable or load control and when causing transmitting at once) in the time can not transmitting Trigger to UE, how long network should preserve this trigger.
In addition, MTC Device Trigger characteristic need satisfy following requirement.
-The?network?shall?be?able?to?report?the?success?or?falure?of?the?trigger(e.g.due?to?network?congestion)to?the?MTC?server,if?so?requested?by?the?MTC?Server.
That is, if MTC Server has asked whether successfully transmission of report Trigger message (for example network congestion and cause bust this), then network need be to MTC Server report relevant information.
On the other hand, in order to realize triggering the demand of MTC Device, proposed use NAS (Non-Access-Stratum, Non-Access Stratum) signaling in the prior art and triggered the method for MTC Device, this method is applicable to successfully the attached UE of (adhering to).
Specifically as shown in Figure 1, for passing through the schematic flow sheet that the NAS signaling triggers the method for MTC Device in the prior art, specifically may further comprise the steps:
Step S101, when MTC Server hopes to get in touch UE, send Trigger message to HSS (Home Subscriber Server, home subscriber server)/HLR (Home Location Register, attaching position register).
Shown in Fig. 1 is UE application trigger request (request of UE applications trigger).
This trigger request of step S102, HSS/HLR checking earlier; Sign with the UE in the trigger message converts the sign that the 3GPP network can be discerned into again, for example IMSI (International Mobile SubscriberIdentification Number, international mobile subscriber identity); Then this request is kept at database; Select current at last just at the MME of service UE (Mobility Management Entity, Mobility Management Entity) or SGSN (Serving GPRS Support Node, GPRS service node; Wherein, GPRS, General Packet Radio Service, GPRS); And trigger message sent to serving MME/SGSN, after receiving, MME/SGSN need return affirmation to HSS/HLR; After MME receives Trigger message, preserve this Trigger.
Step S103, MME/SGSN are encapsulated in trigger message in the NAS signaling, pass to UE.
If trigger message is not urgent, then can when UE and network carry out the NAS Signalling exchange next time, transmit; If trigger message is urgent, network paging UE at once then, and transmit this trigger message.
After step S104, UE received Trigger information, the UE usage counter judged whether to receive the Trigger of repetition; UE sends the NAS signaling to MME/SGSN and confirms; Set up then and the communicating by letter of MTCServer.
After step S105, network are received the affirmation of UE, the Trigger that preserves is deleted, and return Trigger delivered confirmation to HSS/HLR.
In the method, HSS/HLR also can be the intermediate node that can realize above-mentioned functions, for example MTC-IWF (Inter-working Function, interaction function unit).
On the other hand, there is affirmation mechanism in SMS of the prior art (Short Message Service, short message service) mechanism, and MME/SGSN only need transmit the delivery report that UE reports.
Specifically as shown in Figure 2; Schematic flow sheet for the mechanism of the affirmation in the SMS mechanism in the prior art; Step S211 in the figure is to step S212, and MME only is forwarded to GMSC (Gateway Mobile Switching Center after receiving the delivery report that UE uploads; GMSC), control whether retransmit short message by GMSC then.
In realizing process of the present invention, the inventor finds to exist at least in the prior art following problem:
When network is received a plurality of Trigger of certain UE (Trigger that a plurality of MTC Server send and MTC Server send the scene of a plurality of Trigger); If exist the Trigger message dilivery unsuccessful; Then network can not distinguish current which successfully deliver, which is unsuccessful; For example:
According to prior art; When UE is in connected state, network uses Trigger message of DOWNLINK GENERIC NASTRANSPORT message encapsulation, be delivered to UE after; When receiving a new Trigger message from identical or different MTC Server again; This moment, UE can not judge the Trigger message of receiving repetition according to counter, because the content of these two Trigger possibly be different, for example possibly be to trigger to set up different PDN connections; Therefore; If UE only receives a Trigger message, and when using DOWNLINK GENERIC NAS TRANSPORT message to encapsulate acknowledge message to return to network, network does not know that this affirmation is to the Trigger message of which bar.
Summary of the invention
The embodiment of the invention provides a kind of delivery confirmation method and apparatus of MTC Device trigger messages, solves in the existing technical scheme to confirm accurately whether MTC Device trigger messages delivers successful problem.
For achieving the above object, the embodiment of the invention provides a kind of delivery confirmation method of MTC Device trigger messages on the one hand, may further comprise the steps at least:
When management server generates MTC Device trigger messages according to the triggering request that receives; Said management server is said MTC Device trigger messages allocation identification information, and said MTCDevice trigger messages and said identification information are bound storage in this locality;
Said management server sends first message of carrying said identification information and said MTC Device trigger messages to terminal equipment;
When said management server receive that said terminal equipment returns carry identification information and during to second message of the affirmation message of MTCDevice trigger messages, said management server judges whether identification information entrained in said second message and local is bound the said identification information of storage consistent;
If it is consistent; Said management server confirms that affirmation message entrained in said second message is the affirmation message of this locality being bound the said MTC Device trigger messages of storage; The said MTC Device trigger messages and the said identification information of storage are bound in deletion in this locality, and transmit the entrained affirmation message of said second message.
On the other hand, the embodiment of the invention also provides a kind of management server, comprises at least:
Distribution module is used for when generating MTC Device trigger messages according to the triggering request that receives, being said MTC Device trigger messages allocation identification information;
Memory module is used for the identification information that said MTC Device trigger messages and said distribution module are distributed is bound storage;
Sending module is used for sending to terminal equipment and carries identification information that said distribution module distributes and first message of said MTC Device trigger messages;
Receiver module is used to receive the message that said terminal equipment returns;
Judge module; Be used for carrying identification information and during to second message of the affirmation message of MTC Device trigger messages, judging whether identification information entrained in said second message and said memory module are bound the said identification information of storage consistent when what said receiver module received that said terminal equipment returns;
Processing module; Be used for when the judged result of said judge module is unanimity; Confirm that entrained affirmation message is the affirmation message of said memory module being bound the said MTC Device trigger messages of storage in the second received message of said receiver module; Notify said memory module deletion to bind the said MTC Device trigger messages and the said identification information of storage, and notify said sending module to transmit entrained affirmation message in the second received message of said receiver module.
On the other hand, the embodiment of the invention also provides a kind of delivery confirmation method of MTC Device trigger messages, may further comprise the steps at least:
When terminal equipment successfully receive management server and sent carry first message of identification information and MTC Device trigger messages the time, said terminal equipment sends to said management server and carries said identification information and to second message of the affirmation message of said MTC Device trigger messages.
On the other hand, the embodiment of the invention also provides a kind of terminal equipment, comprises at least:
Receiver module is used for the message that the receiving management server is sent;
Sending module; Be used for said receiver module successfully receive said management server and sent carry first message of identification information and MTC Device trigger messages the time, send to said management server and to carry said identification information and second message of the affirmation message of said MTC Device trigger messages.
Compared with prior art, the technical scheme that the embodiment of the invention proposed has the following advantages:
Through using the technical scheme of the embodiment of the invention; With management server (for example MME or SGSN) serves as to judge main body, when sending MTC Device trigger messages to terminal equipment, carries corresponding identification information; And according to whether receiving the affirmation message of carrying same identification information that terminal equipment returns; Confirm whether corresponding M TC Device trigger messages delivers success, thereby, be not sure of MTC Device trigger messages in the solution prior art and whether deliver successful problem; Can confirm accurately whether MTC Device trigger messages is successfully received by terminal equipment, improve the reliability of MTC Device trigger messages delivery process.
Description of drawings
Fig. 1 passes through the schematic flow sheet that the NAS signaling triggers the method for MTC Device in the prior art;
Fig. 2 is the schematic flow sheet of the mechanism of the affirmation in the SMS mechanism in the prior art;
Fig. 3 is the schematic flow sheet of the delivery confirmation method of a kind of MTC Device trigger messages that the embodiment of the invention proposed;
A kind of treatment mechanism of introducing life cycle simultaneously that Fig. 4 proposes for the embodiment of the invention and based on the schematic flow sheet of the delivery confirmation method of the MTC Device trigger messages of the retransmission mechanism of timer;
Fig. 5 is the schematic flow sheet of the delivery confirmation method of the MTC Device trigger messages in a kind of concrete scene that the embodiment of the invention proposed;
Fig. 6 is the structural representation of a kind of management server of embodiment of the invention proposition;
Fig. 7 is the structural representation of a kind of terminal equipment of embodiment of the invention proposition.
Embodiment
Of background technology; The characteristic of MTC Device Triggering has been proposed in the existing technical standard; MTC Server can insert Server through MTC Device Trigger message control terminal; And in order to let MTC Server know whether MTC Device Trigger message transmits success, network need be to the MTC Server report Device Trigger message demand of transmission success whether, but according to the framework of the SAE network of existing 3GPP; Adopt the NAS signaling to trigger under the mode of MTC Device; When handling a plurality of Trigger process at the same time, it specifically is to that network can not be distinguished corresponding message for which Trigger process, also just can not solve network naturally and how report the whether problem of transmission success of Trigger message to MTC Server.
In order to overcome such defective; The embodiment of the invention has proposed a kind of delivery confirmation method of MTC Device trigger messages; Adopting the NAS signaling to trigger under the scene of MTC Device; Through the specific message that terminal equipment fed back, confirm whether MTC Device trigger messages delivers success.
In the corresponding techniques scheme by concrete management server as judging main body, confirm whether the MTCDevice trigger messages delivers success.
In concrete enforcement scene, mentioned here management server can be MME or SGSN, and the variation of concrete physical entity type can't influence protection scope of the present invention.
As shown in Figure 3, be the schematic flow sheet of the delivery confirmation method of a kind of MTC Device trigger messages that the embodiment of the invention proposed, this method specifically may further comprise the steps:
Step S301, when management server generates MTC Device trigger messages according to the triggering request that receives; Said management server is said MTC Device trigger messages allocation identification information, and said MTC Device trigger messages and said identification information are bound storage in this locality.
Step S302, said management server send first message of carrying said identification information and said MTC Device trigger messages to terminal equipment.
When said management server receive that said terminal equipment returns carry identification information and during to second message of the affirmation message of MTCDevice trigger messages, execution in step S303.
Step S303, said management server judge whether identification information entrained in said second message is consistent with the said identification information of local binding storage.
In the technical scheme that the embodiment of the invention proposed; Terminal equipment is after handling the MTCDevice trigger messages in first message; Can the identification information in this first message be carried in second message with corresponding acknowledge message and feed back to management equipment; Thereby management server can come in view of the above recognition and verification message is to be directed against which MTC Device trigger messages on earth.
Based on above-mentioned processing thinking, if the judged result in this step is unanimity, then execution in step S304.
Step S304, said management server confirm that affirmation message entrained in said second message is the affirmation message of this locality being bound the said MTC Device trigger messages of storage; The said MTC Device trigger messages and the said identification information of storage are bound in deletion in this locality, and transmit the entrained affirmation message of said second message.
Through such processing, can accurately recognize affirmation message, and this acknowledge message is reported to corresponding M TC Device trigger messages, thereby, confirm MTC Device trigger messages transmission success.
In above-mentioned processing procedure; If the judged result of step S303 is inconsistent; Show that then the affirmation message in current received second message is not the affirmation message of this locality being bound the said MTC Device trigger messages of storage, therefore, can't carry out concrete processing according to the said MTC Device trigger messages that the second current message is bound storage to this locality; But other second message is waited in continuation; Thereby which MTC Device trigger messages what make that management server can distinguish that acknowledge message is directed against is, and and then confirms the delivery success of which MTC Device trigger messages.
Need be pointed out that further that the delivery report mechanism of applied similar short message is not suitable for using the NAS signaling to carry out the mechanism that Trigger message is transmitted in the prior art, because; The node that does not have similar GMSC in this framework; Simultaneously, Trigger mechanism has ageing characteristics, needs to consider the life cycle of Trigger message; Obviously, existing technical scheme is not considered such problem.
In order to overcome such defective, further introduced the treatment mechanism of life cycle in the technical scheme that the embodiment of the invention proposed, corresponding processing procedure need be adjusted as follows.
In step S301; In order to embody the life cycle characteristic of MTC Device trigger messages; Said management servers process is bound storage with said MTC Device trigger messages and said identification information in this locality, also stored the life cycle of said MTC Device trigger messages in this locality.
Whether the processing of step S302 remains unchanged, and after this, need expire according to life cycle and handle accordingly, specifically is divided into following three kinds of situation.
Situation one, before said life cycle arrives, said management server receives that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages.
In such cases, execution in step S303.
If judged result is consistent; Said management server confirms that affirmation message entrained in said second message is the affirmation message of this locality being bound the said MTC Device trigger messages of storage; The said MTC Device trigger messages and the said identification information of storage are bound in deletion in this locality; And the life cycle of said MTCDevice trigger messages, and transmit the entrained affirmation message of said second message.
If judged result is inconsistent; Show that then the affirmation message in current received second message is not the affirmation message of this locality being bound the said MTC Device trigger messages of storage; Therefore; Can't carry out concrete processing according to the said MTC Device trigger messages that the second current message is bound storage to this locality, but continue to wait for other second message, thereby; Which MTC Device trigger messages what make that management server can distinguish that acknowledge message is directed against is, and and then confirms the delivery success of which MTC Device trigger messages.
Situation two, said management server before said life cycle arrives, do not receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages.
Under this situation, in complete life cycle, management server does not receive any satisfactory second message; Nature; Also just can not receive the affirmation message of this locality being bound the said MTC Device trigger messages of storage, therefore, in the life cycle of this MTC Device trigger messages; This MTC Device trigger messages is not delivered success; The said MTC Device trigger messages and the said identification information of the deletion binding storage of said management server, and the life cycle of said MTC Device trigger messages in this locality, and report said MTC Device trigger messages to trigger failure.
Situation three, said management server did not receive and carry second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing before said life cycle arrives.
This kind situation is equivalent to the repeatedly circulation that a kind of judged result of situation is inconsistent situation; Though be that management server has been received second message in life cycle; But the identification information that wherein carries all is not the local identification information of binding storage, and the affirmation message in promptly current received each second message is not the affirmation message of this locality being bound the said MTC Device trigger messages of storage, therefore; Management server is confirmed in the complete life cycle of the said MTC Device trigger messages of storing is bound in this locality; All do not receive affirmation message to this MTC Device trigger messages, therefore, in the life cycle of this MTC Device trigger messages; This MTC Device trigger messages is not delivered success; The said MTC Device trigger messages and the said identification information of the deletion binding storage of said management server, and the life cycle of said MTC Device trigger messages in this locality, and report said MTC Device trigger messages to trigger failure.
Processing through three kinds of above-mentioned situation; Not only embodied the life cycle characteristic of MTC Device trigger messages; And based on this specific character; Introduced and differentiated that MTC Device trigger messages triggers the mechanism of failure, can in time report the result who triggers failure, avoided unrestrictedly waiting for and deliver the successful wasting of resources that the result brought and the reduction of treatment effeciency.
On the other hand, in the prior art scheme, owing to reasons such as network congestions; MTC Device trigger messages can't in time send to terminal equipment, and management server can not taked other remedial measure yet, only can wait for receiving corresponding acknowledge message always; And owing to reasons such as network congestions, management server may occur also not receiving that terminal equipment returns to the situation of the affirmation message of corresponding MTC Device trigger messages; And under such situation, terminal equipment and management server are understood nature and can be had tangible difference for current triggering result's, on the one hand; Terminal equipment slowly can't be carried out corresponding follow-up business after triggering successfully; And on the other hand, management server can wait for always then and receive corresponding acknowledge message that such result has caused corresponding processing procedure normally not continue; And not corresponding mechanism guarantees delivering success rate, influences the reliability of the transmission course of MTC Device trigger messages.
In order to overcome such defective, further introduced retransmission mechanism in the technical scheme that the embodiment of the invention proposed based on timer, corresponding processing procedure need be adjusted as follows.
The processing of step S301 remains unchanged.
In step S302, said management server sends in the process of first message of carrying said identification information and said MTC Device trigger messages to terminal equipment, and said management server has also started and the corresponding timer of said identification information.
And after this, need handle accordingly according to whether timer overtime, specifically be divided into following three kinds of situation.
Situation one, said management server before said timer expired, receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages.
In such cases, execution in step S303.
If judged result is consistent; Said management server confirms that affirmation message entrained in said second message is the affirmation message of this locality being bound the said MTC Device trigger messages of storage; Then stop and the corresponding timer of said identification information; The said MTC Device trigger messages and the said identification information of storage are bound in deletion in this locality, and transmit the entrained affirmation message of said second message.
If judged result is inconsistent; Show that then the affirmation message in current received second message is not the affirmation message of this locality being bound the said MTC Device trigger messages of storage; Therefore; Can't carry out concrete processing according to the said MTC Device trigger messages that the second current message is bound storage to this locality, but continue to wait for other second message, thereby; Which MTC Device trigger messages what make that management server can distinguish that acknowledge message is directed against is, and and then confirms the delivery success of which MTC Device trigger messages.
Situation two, said management server before said timer expired, do not receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages.
Under this situation, in current complete time-count cycle, management server does not receive any satisfactory second message at timer; Nature also just can not receive the affirmation message of this locality being bound the said MTC Device trigger messages of storage, therefore; At the timer of this MTC Device trigger messages in current complete time-count cycle; This MTC Device trigger messages is not delivered success, thereby, start retransmission mechanism; Said management server sends to terminal equipment again and carries first message of said identification information and said MTC Device trigger messages, and restarts and the corresponding timer of said identification information.
Situation three, said management server did not receive and carry second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing before said timer expired.
This kind situation is equivalent to the repeatedly circulation that a kind of judged result of situation is inconsistent situation; Though be that management server has been received satisfactory second message in this time-count cycle of said timer, the identification information that wherein carries all is not the local identification information of binding storage, and the affirmation message in promptly current received each second message is not the affirmation message of this locality being bound the said MTC Device trigger messages of storage; Therefore; Management server was confirmed in this time-count cycle, did not all receive the affirmation message to this MTC Device trigger messages, therefore; In this this time-count cycle; This MTC Device trigger messages is not delivered success, thereby, start retransmission mechanism; Said management server sends to terminal equipment again and carries first message of said identification information and said MTC Device trigger messages, and restarts and the corresponding timer of said identification information.
Processing through three kinds of above-mentioned situation; Introduced retransmission mechanism based on timer; Management server can unrestrictedly not waited for and deliver successful result; But at timer expired and do not receive under the situation of delivering successful result, directly MTC Device trigger messages is retransmitted, improve the delivery success rate of MTC Device trigger messages as far as possible.
Even based on such processing owing to reasons such as network congestions; Cause the situation that MTC Device trigger messages can't in time be sent to or acknowledge message can't in time be returned; Also can remedy, guarantee that as far as possible MTC Device trigger messages can deliver success through re-transmission.
In order to realize better technique effect; The technical scheme that the embodiment of the invention proposed can also be introduced the treatment mechanism of life cycle and simultaneously based on the retransmission mechanism of timer; In limited life cycle, improve the delivery success rate of MTC Device trigger messages as far as possible through retransmission mechanism.
Based on such technical thought; Further the technical scheme that the aforesaid embodiment of the invention proposed is adjusted; As shown in Figure 4; A kind of treatment mechanism of introducing life cycle simultaneously that proposes for the embodiment of the invention and based on the schematic flow sheet of the delivery confirmation method of the MTC Device trigger messages of the retransmission mechanism of timer, this method specifically may further comprise the steps:
Step S401, when management server generates MTC Device trigger messages according to the triggering request that receives; Said management server is said MTC Device trigger messages allocation identification information; Said MTC Device trigger messages and said identification information are bound storage in this locality, and store the life cycle of said MTC Device trigger messages in this locality.
Step S402, said management server send first message of carrying said identification information and said MTC Device trigger messages to terminal equipment, and startup and the corresponding timer of said identification information.
Wherein, the duration of said life cycle more than or equal to the duration of the time-count cycle of the corresponding timer of said identification information.
Step S403, said management server judged before said timer expired, whether receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages.
If judged result is for being, execution in step S404 then;
If judged result is not, then execution in step S406.
Wherein, judged result comprises two kinds for situation not:
Situation one, before said timer expired, do not receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages.
Situation two, confirm that through subsequent step affirmation message entrained in all received in this time-count cycle of said timer second message all is not the affirmation message of this locality being bound the said MTC Device trigger messages of storage.
Step S404, said management server judge whether identification information entrained in said second message is consistent with the said identification information of local binding storage.
If unanimity, then execution in step S405;
If inconsistent, then return step S403.
Under inconsistent situation, management server thinks that current this second message that receives does not exert an influence to current timer, therefore, need return step S403, proceeds the reception of other second message.
If the especially current a plurality of timers that have corresponding different identification information; The judgement of this step obviously can avoid carrying the interference of second message of different identification information for other timers so, and the delivery process of the MTC Device trigger messages of accurately corresponding identification information being bound is monitored.
Step S405, said management server confirm that affirmation message entrained in said second message is the affirmation message of this locality being bound the said MTC Device trigger messages of storage; Said management server stops and the corresponding timer of said identification information; The said MTC Device trigger messages and the said identification information of storage are bound in deletion in this locality; And the life cycle of said MTC Device trigger messages, and transmit the entrained affirmation message of said second message.
Step S406, said management server judge whether said MTC Device trigger messages satisfies retransmission condition.
If satisfy, return execution in step S402, promptly said management server sends to terminal equipment again and carries first message of said identification information and said MTC Device trigger messages, and restarts and the corresponding timer of said identification information;
If do not satisfy, then execution in step S407.
In concrete processing scene, the judgment processing process of this step specifically can for:
Said management server is confirmed the duration of the life cycle of current residual according to the life cycle of the said MTC Device trigger messages of this locality storage.
If the duration of the life cycle of current residual more than or equal to the duration of the time-count cycle of the corresponding timer of said identification information, then said management server confirms that said MTC Device trigger messages satisfies retransmission condition.
If the duration of the life cycle of current residual less than with the duration of the time-count cycle of the corresponding timer of said identification information, then said management server confirms that the discontented lumping weight of said MTC Device trigger messages passes condition.
The said MTC Device trigger messages and the said identification information of the deletion binding storage of step S407, said management server, and the life cycle of said MTC Device trigger messages in this locality, and report said MTC Device trigger messages to trigger failure.
Need to prove; Whether in the technical scheme that the embodiment of the invention proposed, introduce the treatment mechanism of above-mentioned life cycle and/or can confirm that based on the retransmission mechanism of timer the variation of the corresponding processing scheme that produces therefrom can't influence protection scope of the present invention according to the needs of reality.
No matter adopt which kind of above-mentioned scheme; Said identification information all need satisfy the process of unique identification transmission MTC Device trigger messages that at least can be interim; The requirement of unique identification MTCDevice trigger messages that perhaps at least can be interim, its concrete form can comprise:
Said management server is the Transaction Identifier that the transmission course of this MTC Device trigger messages and subsequent message thereof is distributed; Or,
Said management server is the sequence number that said MTC Device trigger messages is distributed.
In practical application, specifically adopt which kind of above-mentioned form to select as required, such variation does not influence protection scope of the present invention.
Corresponding, for this kind scheme, following in the handled process of terminal equipment side:
When terminal equipment successfully receive management server and sent carry first message of identification information and MTC Device trigger messages the time, said terminal equipment sends to said management server and carries said identification information and to second message of the affirmation message of said MTC Device trigger messages.
Wherein, requirement that said identification information need satisfy and concrete form thereof repeat no more at this referring to above stated specification.
Concrete processing mode is referring to above-mentioned explanation, and is similar with it, at this, and no longer repeat specification.
Compared with prior art, the technical scheme that the embodiment of the invention proposed has the following advantages:
Through using the technical scheme of the embodiment of the invention; With management server (for example MME or SGSN) serves as to judge main body, when sending MTC Device trigger messages to terminal equipment, carries corresponding identification information; And according to whether receiving the affirmation message of carrying same identification information that terminal equipment returns; Confirm whether corresponding M TC Device trigger messages delivers success, thereby, be not sure of MTC Device trigger messages in the solution prior art and whether deliver successful problem; Can confirm accurately whether MTC Device trigger messages is successfully received by terminal equipment, improve the reliability of MTC Device trigger messages delivery process.
Below, the application scenarios in conjunction with concrete describes the technical scheme that the embodiment of the invention proposed.
In the technical scheme that the embodiment of the invention proposed; To prior art problems; Particularly receive the scene of a plurality of MTC Device Trigger to MME/SGSN, provide a kind of MTC DeviceTrigger message the delivery confirmation method, thereby; Can confirm accurately whether MTC Device trigger messages is successfully received by terminal equipment, improve the reliability of MTC Device trigger messages delivery process.
Describe for ease, the embodiment of the invention specifically describes as the concrete example of aforesaid management server with MME/SGSN, and in the application scenarios of reality, the type of concrete management server changes can't influence protection scope of the present invention.
Accordingly, whether transmitting successful determination point with MME/SGSN as Device Trigger, and using under the scene of related Trigger message of identification information and delivery confirmation message, concrete embodiment explains as follows.
As shown in Figure 5, be the schematic flow sheet of the delivery confirmation method of the MTCDevice trigger messages under a kind of concrete application scenarios that the embodiment of the invention proposed, this method specifically may further comprise the steps:
Step S501, MME/SGSN are when encapsulation Trigger message; For each bar Trigger dispensing transaction sign Transaction identifier (Transaction identifier be used for a related message flow), each Trigger message is bound and stored with a Transaction identifier.
Concrete, in the processing procedure of this step shown in Figure 5, Trigger Message is the message that MTCServer issues, encapsulation Transaction Identifier in DOWNLINK GENERIC NAS TRANSPORT message.
In concrete processing scene, the form of DOWNLINK GENERIC NAS TRANSPORT message is as shown in table 1.
The form of table 1DOWNLINK GENERIC NAS TRANSPORT message
Figure BDA0000115561230000151
Figure BDA0000115561230000161
Further, in this step, MME/SGSN is chosen in and inserts Transaction ID among the Additional information, and concrete form is as shown in table 2.
The form of table 2Additional information
Figure BDA0000115561230000162
Concrete, can partly insert Transaction Identifier at the value shown in the table 2, Transaction identifier is provided with according to concrete scene needs, and the variation of concrete form does not influence protection scope of the present invention.
Step S502, MME/SGSN use NAS signaling (if UE at Idle state, then wants earlier paging UE) that Trigger message is passed to UE, start timer T simultaneously.
Wherein, the value of timer T is relevant with concrete realization.
For example, suppose that the Trigger life cycle is 60s, retransmit 5 times, then can T be made as 12s.
After step S503, UE receive the NAS signaling of carrying Trigger message, be each Trigger message transmitting confirmation that successfully receives, in carrying the message of acknowledge message, fill in identical Transaction identifier value equally.
After step S504, MME/SGSN receive the message of carrying Transaction identifier and acknowledge message; What MME/SGSN confirmed to receive through the Transaction identifier in the message is the affirmation message to which bar Trigger message; Thereby this Trigger message that deletion is stored, and stop corresponding timer T.
If step S505 MME/SGSN is after timer T is overtime; Still do not receive certain Trigger acknowledge message; If the residue life cycle of this Trigger message still greater than the time-count cycle of a complete timer T, then realizes according to MME/SGSN, retransmits Trigger message once more.Repeatedly overtime back (realizing being correlated with) is judged and is delivered failure, fails to MTC Server report through HSS/HLR or MTC-IWF.
Compared with prior art, the technical scheme that the embodiment of the invention proposed has the following advantages:
Through using the technical scheme of the embodiment of the invention; With management server (for example MME or SGSN) serves as to judge main body, when sending MTC Device trigger messages to terminal equipment, carries corresponding identification information; And according to whether receiving the affirmation message of carrying same identification information that terminal equipment returns; Confirm whether corresponding M TC Device trigger messages delivers success, thereby, be not sure of MTC Device trigger messages in the solution prior art and whether deliver successful problem; Can confirm accurately whether MTC Device trigger messages is successfully received by terminal equipment, improve the reliability of MTC Device trigger messages delivery process.
In order to realize the technical scheme of the embodiment of the invention, the embodiment of the invention also provides a kind of management server, and its structural representation is as shown in Figure 6, comprises at least:
Distribution module 61 is used for when generating MTC Device trigger messages according to the triggering request that receives, being said MTC Device trigger messages allocation identification information;
Memory module 62 is used for the identification information that said MTC Device trigger messages and said distribution module 61 are distributed is bound storage;
Sending module 63 is used for sending to terminal equipment and carries identification information that said distribution module 61 distributed and first message of said MTC Device trigger messages;
Receiver module 64 is used to receive the message that said terminal equipment returns;
Judge module 65; Be used for carrying identification information and during to second message of the affirmation message of MTC Device trigger messages, judging whether identification information entrained in said second message and said memory module 62 are bound the said identification information of storage consistent when what said receiver module 64 received that said terminal equipment returns;
Processing module 66; Be used for when the judged result of said judge module 65 is unanimity; Confirm that entrained affirmation message is the affirmation message of said memory module 62 being bound the said MTC Device trigger messages of storage in the second received message of said receiver module 64; Notify 62 deletions of said memory module to bind said MTC Device trigger messages and the said identification information of storage, and notify entrained affirmation message in the second received message of the said receiver module of said sending module 63 forwardings 64.
Further, said memory module 62 also is used to store the life cycle of said MTC Device trigger messages.
Accordingly, said processing module 66 specifically is used for:
If before the life cycle that said memory module 62 is stored arrives; Said receiver module 64 receives that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; And confirm that entrained affirmation message is the affirmation message of said memory module 62 being bound the said MTC Device trigger messages of storage in said second message; Then notify said memory module 62 deletions to bind the said MTC Device trigger messages and the said identification information of storage; And the life cycle of said MTC Device trigger messages, and notify said sending module 63 to transmit entrained affirmation message in the second received message of said receiver module 64;
If before the life cycle that said memory module 62 is stored arrives; Said receiver module 64 does not receive that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; Or before the life cycle that said memory module 62 is stored arrives; Said receiver module 64 does not receive and carries second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing; Then notify said memory module 62 deletions to bind the said MTCDevice trigger messages and the said identification information of storage; And the life cycle of said MTC Device trigger messages, and notify said sending module 63 to report said MTC Device trigger messages to trigger failure.
Under the another kind of application scenarios, above-mentioned management server also comprises:
Timing module 67 is used at said sending module 63 when terminal equipment sends first message carry identification information that said distribution module 61 distributed and said MTC Device trigger messages, starting and the corresponding timer of said identification information.
Accordingly, said processing module 66 specifically is used for:
If before the timer expired that said timing module 67 is started; Said receiver module 64 receives that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; And confirm that entrained affirmation message is the affirmation message of said memory module 62 being bound the said MTC Device trigger messages of storage in said second message; Then notify said timing module 67 to stop and the corresponding timer of said identification information; Notify 62 deletions of said memory module to bind said MTC Device trigger messages and the said identification information of storage, and notify entrained affirmation message in the second received message of the said receiver module of said sending module 63 forwardings 64;
If before the timer expired that said timing module 67 is started; Said receiver module 64 does not receive that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; Or before the timer expired that said timing module 67 is started; Said receiver module 64 does not receive and carries second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing; Then notify said sending module 63 to send to terminal equipment again and carry first message of said identification information and said MTC Device trigger messages, and notify said timing module 67 to restart and the corresponding timer of said identification information.
Under the another kind of application scenarios,
Said distribution module 61 specifically is used for when generating the MTCDevice trigger messages according to the triggering request that receives, being said MTC Device trigger messages allocation identification information;
Said memory module 62 specifically is used for the identification information that said MTC Device trigger messages and said distribution module 61 are distributed is bound storage, and stores the life cycle of said MTC Device trigger messages;
Said sending module 63 specifically is used for sending to terminal equipment and carries identification information that said distribution module 61 distributed and first message of said MTC Device trigger messages;
Timing module 67; Be used at said sending module 63 when terminal equipment sends first message carry identification information that said distribution module 61 distributed and said MTC Device trigger messages; Start and the corresponding timer of said identification information; Wherein, the duration of said life cycle more than or equal to the duration of the time-count cycle of the corresponding timer of said identification information;
Said receiver module 64 specifically is used to receive the message that said terminal equipment returns;
Said judge module 65; Specifically be used for before the timer expired that said timing module 67 is started; Said receiver module 64 receives that said terminal equipment returns carries identification information and during to second message of the affirmation message of MTC Device trigger messages, judges whether identification information entrained in said second message and said memory module 62 are bound the said identification information of storage consistent;
Said processing module 66; Specifically be used for when the judged result of said judge module 65 is unanimity; Confirm that affirmation message entrained in said second message is the affirmation message of said memory module 62 being bound the said MTC Device trigger messages of storage; Notify said timing module 67 to stop and the corresponding timer of said identification information; Notify 62 deletions of said memory module to bind said MTC Device trigger messages and the said identification information of storage, and the life cycle of said MTC Device trigger messages, and notify entrained affirmation message in the second received message of the said receiver module of said sending module 63 forwardings 64.
Wherein, said processing module 66 also is used for:
If before the timer expired that said timing module 67 is started; Said receiver module 64 does not receive that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; Or before the timer expired that said timing module 67 is started; Said receiver module 64 does not receive and carries second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing, and notifies said judge module 65 to judge whether said MTC Device trigger messages satisfies retransmission condition;
If judging, said judge module 65 satisfies retransmission condition; Then notify said sending module 63 to send to terminal equipment again and carry first message of said identification information and said MTC Device trigger messages, and notify said timing module 67 to restart and the corresponding timer of said identification information;
If said judge module 65 judges that discontented lumping weight passes condition; Then notify said memory module 62 deletions to bind the said MTC Device trigger messages and the said identification information of storage; And the life cycle of said MTCDevice trigger messages, and notify said sending module 63 to report said MTC Device trigger messages to trigger failure.
Further, said judge module 65 specifically is used for:
According to the life cycle of the said MTC Device trigger messages of said memory module 62 storages, confirm the duration of the life cycle of current residual;
If the duration of the life cycle of current residual more than or equal to the duration of the time-count cycle of the corresponding timer of said identification information, judge that then said MTC Device trigger messages satisfies retransmission condition;
If the duration of the life cycle of current residual less than with the duration of the time-count cycle of the corresponding timer of said identification information, judge that then the discontented lumping weight of said MTC Device trigger messages passes condition.
It is to be noted; Said distribution module 61; Specifically be used to said MTC Device trigger messages and distribute the process of unique identification transmission MTC Device trigger messages that at least can be interim, unique identification MTC Device trigger messages that perhaps at least can be interim is as identification information, wherein; Said identification information specifically comprises:
The Transaction Identifier that distributes for the transmission course of this MTC Device trigger messages and subsequent message thereof; Or,
Sequence number for said MTC Device trigger messages distribution.
In practical application, above-mentioned management server is specially MME or SGSN.
Further, the embodiment of the invention also provides a kind of terminal equipment, and its structural representation is as shown in Figure 7, comprises at least:
Receiver module 71 is used for the message that the receiving management server is sent;
Sending module 72; Be used for said receiver module 71 successfully receive said management server and sent carry first message of identification information and MTC Device trigger messages the time, send to said management server and to carry said identification information and second message of the affirmation message of said MTC Device trigger messages.
Compared with prior art, the technical scheme that the embodiment of the invention proposed has the following advantages:
Through using the technical scheme of the embodiment of the invention; With management server (for example MME or SGSN) serves as to judge main body, when sending MTC Device trigger messages to terminal equipment, carries corresponding identification information; And according to whether receiving the affirmation message of carrying same identification information that terminal equipment returns; Confirm whether corresponding M TC Device trigger messages delivers success, thereby, be not sure of MTC Device trigger messages in the solution prior art and whether deliver successful problem; Can confirm accurately whether MTC Device trigger messages is successfully received by terminal equipment, improve the reliability of MTC Device trigger messages delivery process.
Through the description of above execution mode, those skilled in the art can be well understood to the embodiment of the invention and can realize through hardware, also can realize by the mode that software adds necessary general hardware platform.Based on such understanding; The technical scheme of the embodiment of the invention can be come out with the embodied of software product, this software product can be stored in a non-volatile memory medium (can be CD-ROM, USB flash disk; Portable hard drive etc.) in; Comprise some instructions with so that computer equipment (can be personal computer, server, or network equipment etc.) each implements the described method of scene to carry out the embodiment of the invention.
It will be appreciated by those skilled in the art that accompanying drawing is a preferred sketch map of implementing scene, module in the accompanying drawing or flow process might not be that embodiment of the present invention embodiment is necessary.
It will be appreciated by those skilled in the art that the module in the device of implementing in the scene can be distributed in the device of implementing scene according to implementing scene description, also can carry out respective change and be arranged in the one or more devices that are different from this enforcement scene.The module of above-mentioned enforcement scene can be merged into a module, also can further split into a plurality of submodules.
The invention described above embodiment sequence number is not represented the quality of implementing scene just to description.
More than the disclosed several practical implementation scenes that are merely the embodiment of the invention, still, the embodiment of the invention is not limited thereto, any those skilled in the art can think variation all should fall into the traffic limits scope of the embodiment of the invention.

Claims (23)

1. the delivering method of a machine class communication equipment MTC Device trigger messages is characterized in that, may further comprise the steps at least:
When management server generates MTC Device trigger messages according to the triggering request that receives; Said management server is said MTC Device trigger messages allocation identification information, and said MTCDevice trigger messages and said identification information are bound storage in this locality;
Said management server sends first message of carrying said identification information and said MTC Device trigger messages to terminal equipment;
When said management server receive that said terminal equipment returns carry identification information and during to second message of the affirmation message of MTCDevice trigger messages, said management server judges whether identification information entrained in said second message and local is bound the said identification information of storage consistent;
If it is consistent; Said management server confirms that affirmation message entrained in said second message is the affirmation message of this locality being bound the said MTC Device trigger messages of storage; The said MTC Device trigger messages and the said identification information of storage are bound in deletion in this locality, and transmit the entrained affirmation message of said second message.
2. the method for claim 1 is characterized in that, said management server is said MTCDevice trigger messages allocation identification information, and said MTC Device trigger messages and said identification information are bound storage in this locality, also comprises:
Said management server is stored the life cycle of said MTC Device trigger messages in this locality.
3. method as claimed in claim 2 is characterized in that, said management server is after the life cycle of said MTC Device trigger messages is stored in this locality, and said method also comprises:
If said management server is before said life cycle arrives; Receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages; And confirm that entrained affirmation message is the affirmation message of this locality being bound the said MTC Device trigger messages of storage in said second message; The said MTCDevice trigger messages and the said identification information of the deletion binding storage of then said management server in this locality; And the life cycle of said MTC Device trigger messages, and transmit the entrained affirmation message of said second message;
If said management server is before said life cycle arrives; Do not receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages; Or said management server is before said life cycle arrives; Do not receive and carry second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing; The said MTC Device trigger messages and the said identification information of the deletion binding storage of then said management server, and the life cycle of said MTCDevice trigger messages in this locality, and report said MTC Device trigger messages to trigger failure.
4. the method for claim 1 is characterized in that, said management server sends first message of carrying said identification information and said MTC Device trigger messages to terminal equipment, also comprises:
Said management server starts and the corresponding timer of said identification information.
5. method as claimed in claim 4 is characterized in that, after said management server startup and the corresponding timer of said identification information, said method also comprises:
If said management server is before said timer expired; Receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages; And confirm that entrained affirmation message is the affirmation message of this locality being bound the said MTC Device trigger messages of storage in said second message; Then said management server stops and the corresponding timer of said identification information; The said MTC Device trigger messages and the said identification information of storage are bound in deletion in this locality, and transmit the entrained affirmation message of said second message;
If said management server is before said timer expired; Do not receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages; Or said management server is before said timer expired; Do not receive and carry second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing; Then said management server sends to terminal equipment again and carries first message of said identification information and said MTC Device trigger messages, and restarts and the corresponding timer of said identification information.
6. the method for claim 1 is characterized in that, is specially:
When management server generates MTC Device trigger messages according to the triggering request that receives; Said management server is said MTC Device trigger messages allocation identification information; Said MTCDevice trigger messages and said identification information are bound storage in this locality, and store the life cycle of said MTCDevice trigger messages in this locality;
Said management server sends first message of carrying said identification information and said MTC Device trigger messages to terminal equipment; And startup and the corresponding timer of said identification information; Wherein, the duration of said life cycle more than or equal to the duration of the time-count cycle of the corresponding timer of said identification information;
When said management server before said timer expired; Receive that said terminal equipment returns carry identification information and during to second message of the affirmation message of MTC Device trigger messages, said management server judges whether identification information entrained in said second message and local is bound the said identification information of storage consistent;
If it is consistent; Said management server confirms that affirmation message entrained in said second message is the affirmation message of this locality being bound the said MTC Device trigger messages of storage; Said management server stops and the corresponding timer of said identification information; The said MTC Device trigger messages and the said identification information of storage are bound in deletion in this locality, and the life cycle of said MTC Device trigger messages, and transmit the entrained affirmation message of said second message.
7. method as claimed in claim 6; It is characterized in that; Said management server sends to terminal equipment and carries first message of said identification information and said MTC Device trigger messages, and after startup and the corresponding timer of said identification information, also comprises:
When said management server before said timer expired; Do not receive that said terminal equipment returns carry identification information and to second message of the affirmation message of MTC Device trigger messages; Or said management server is before said timer expired; When not receiving second message of the affirmation message of carrying the said MTC Device trigger messages that this locality binding is stored, said management server judges whether said MTC Device trigger messages satisfies retransmission condition;
If satisfy, said management server sends to terminal equipment again and carries first message of said identification information and said MTC Device trigger messages, and restarts and the corresponding timer of said identification information;
If do not satisfy, the said MTC Device trigger messages and the said identification information of the deletion binding storage of said management server, and the life cycle of said MTC Device trigger messages in this locality, and report said MTC Device trigger messages to trigger failure.
8. method as claimed in claim 7 is characterized in that, said management server judges that whether said MTC Device trigger messages satisfies retransmission condition, specifically comprises:
Said management server is confirmed the duration of the life cycle of current residual according to the life cycle of the said MTC Device trigger messages of this locality storage;
If the duration of the life cycle of current residual more than or equal to the duration of the time-count cycle of the corresponding timer of said identification information, then said management server confirms that said MTC Device trigger messages satisfies retransmission condition;
If the duration of the life cycle of current residual less than with the duration of the time-count cycle of the corresponding timer of said identification information, then said management server confirms that the discontented lumping weight of said MTC Device trigger messages passes condition.
9. like any described method in the claim 1 to 8; It is characterized in that; Said identification information needs the process of unique identification transmission MTC Device trigger messages that at least can be interim, and unique identification MTC Device trigger messages that perhaps at least can be interim specifically comprises:
Said management server is the Transaction Identifier that the transmission course of this MTC Device trigger messages and subsequent message thereof is distributed; Or,
Said management server is the sequence number that said MTC Device trigger messages is distributed.
10. like any described method in the claim 1 to 8, it is characterized in that said management server is specially:
Mobility Management Entity MME or general packet radio service technological service support node SGSN.
11. a management server is characterized in that, comprises at least:
Distribution module is used for when generating MTC Device trigger messages according to the triggering request that receives, being said MTC Device trigger messages allocation identification information;
Memory module is used for the identification information that said MTC Device trigger messages and said distribution module are distributed is bound storage;
Sending module is used for sending to terminal equipment and carries identification information that said distribution module distributes and first message of said MTC Device trigger messages;
Receiver module is used to receive the message that said terminal equipment returns;
Judge module; Be used for carrying identification information and during to second message of the affirmation message of MTC Device trigger messages, judging whether identification information entrained in said second message and said memory module are bound the said identification information of storage consistent when what said receiver module received that said terminal equipment returns;
Processing module; Be used for when the judged result of said judge module is unanimity; Confirm that entrained affirmation message is the affirmation message of said memory module being bound the said MTC Device trigger messages of storage in the second received message of said receiver module; Notify said memory module deletion to bind the said MTC Device trigger messages and the said identification information of storage, and notify said sending module to transmit entrained affirmation message in the second received message of said receiver module.
12. management server as claimed in claim 11 is characterized in that, said memory module also is used for:
Store the life cycle of said MTC Device trigger messages.
13. management server as claimed in claim 12 is characterized in that, said processing module specifically is used for:
If before the life cycle that said memory module is stored arrives; Said receiver module receives that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; And confirm that entrained affirmation message is the affirmation message of said memory module being bound the said MTC Device trigger messages of storage in said second message; Then notify said memory module deletion to bind the said MTC Device trigger messages and the said identification information of storage; And the life cycle of said MTC Device trigger messages, and notify said sending module to transmit entrained affirmation message in the second received message of said receiver module;
If before the life cycle that said memory module is stored arrives; Said receiver module does not receive that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; Or before the life cycle that said memory module is stored arrives; Said receiver module does not receive and carries second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing; Then notify said memory module deletion to bind the said MTC Device trigger messages and the said identification information of storage; And the life cycle of said MTC Device trigger messages, and notify said sending module to report said MTC Device trigger messages to trigger failure.
14. management server as claimed in claim 11 is characterized in that, also comprises:
Timing module is used at said sending module when terminal equipment sends first message carry identification information that said distribution module distributes and said MTC Device trigger messages, starting and the corresponding timer of said identification information.
15. management server as claimed in claim 14 is characterized in that, said processing module specifically is used for:
If before the timer expired that said timing module started; Said receiver module receives that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; And confirm that entrained affirmation message is the affirmation message of said memory module being bound the said MTC Device trigger messages of storage in said second message; Then notify said timing module to stop and the corresponding timer of said identification information; Notify said memory module deletion to bind the said MTCDevice trigger messages and the said identification information of storage, and notify said sending module to transmit entrained affirmation message in the second received message of said receiver module;
If before the timer expired that said timing module started; Said receiver module does not receive that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; Or before the timer expired that said timing module started; Said receiver module does not receive and carries second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing; Then notify said sending module to send to terminal equipment again and carry first message of said identification information and said MTC Device trigger messages, and notify said timing module to restart and the corresponding timer of said identification information.
16. management server as claimed in claim 11 is characterized in that,
Said distribution module specifically is used for when generating MTC Device trigger messages according to the triggering request that receives, being said MTC Device trigger messages allocation identification information;
Said memory module specifically is used for the identification information that said MTC Device trigger messages and said distribution module are distributed is bound storage, and stores the life cycle of said MTC Device trigger messages;
Said sending module specifically is used for sending to terminal equipment and carries identification information that said distribution module distributes and first message of said MTC Device trigger messages;
Timing module; Be used at said sending module when terminal equipment sends first message carry identification information that said distribution module distributes and said MTC Device trigger messages; Start and the corresponding timer of said identification information; Wherein, the duration of said life cycle more than or equal to the duration of the time-count cycle of the corresponding timer of said identification information;
Said receiver module specifically is used to receive the message that said terminal equipment returns;
Said judge module; Specifically be used for before the timer expired that said timing module started; Said receiver module receives that said terminal equipment returns carries identification information and during to second message of the affirmation message of MTC Device trigger messages, judges whether identification information entrained in said second message and said memory module are bound the said identification information of storage consistent;
Said processing module; Specifically be used for when the judged result of said judge module is unanimity; Confirm that affirmation message entrained in said second message is the affirmation message of said memory module being bound the said MTC Device trigger messages of storage; Notify said timing module to stop and the corresponding timer of said identification information; Notify said memory module deletion to bind the said MTC Device trigger messages and the said identification information of storage, and the life cycle of said MTC Device trigger messages, and notify said sending module to transmit entrained affirmation message in the second received message of said receiver module.
17. management server as claimed in claim 16 is characterized in that, said processing module also is used for:
If before the timer expired that said timing module started; Said receiver module does not receive that said terminal equipment returns carries identification information and to second message of the affirmation message of MTC Device trigger messages; Or before the timer expired that said timing module started; Said receiver module does not receive and carries second message of this locality being bound the affirmation message of the said MTC Device trigger messages of storing, and notifies said judge module to judge whether said MTC Device trigger messages satisfies retransmission condition;
If judging, said judge module satisfies retransmission condition; Then notify said sending module to send to terminal equipment again and carry first message of said identification information and said MTC Device trigger messages, and notify said timing module to restart and the corresponding timer of said identification information;
If said judge module is judged discontented lumping weight and is passed condition; Then notify said memory module deletion to bind the said MTC Device trigger messages and the said identification information of storage; And the life cycle of said MTC Device trigger messages, and notify said sending module to report said MTC Device trigger messages to trigger failure.
18. management server as claimed in claim 17 is characterized in that, said judge module specifically is used for:
According to the life cycle of the said MTC Device trigger messages of said memory module storage, confirm the duration of the life cycle of current residual;
If the duration of the life cycle of current residual more than or equal to the duration of the time-count cycle of the corresponding timer of said identification information, judge that then said MTC Device trigger messages satisfies retransmission condition;
If the duration of the life cycle of current residual less than with the duration of the time-count cycle of the corresponding timer of said identification information, judge that then the discontented lumping weight of said MTC Device trigger messages passes condition.
19. like any described management server in the claim 11 to 18; It is characterized in that said distribution module specifically is used to the process that said MTC Device trigger messages is distributed unique identification transmission MTC Device trigger messages that at least can be interim; Unique identification MTCDevice trigger messages that perhaps at least can be interim is as identification information; Wherein, said identification information specifically comprises:
The Transaction Identifier that distributes for the transmission course of this MTC Device trigger messages and subsequent message thereof; Or,
Sequence number for said MTC Device trigger messages distribution.
20. like any described management server in the claim 11 to 18, it is characterized in that, be specially MME or SGSN.
21. the delivery confirmation method of a MTC Device trigger messages is characterized in that, may further comprise the steps at least:
When terminal equipment successfully receive management server and sent carry first message of identification information and MTC Device trigger messages the time, said terminal equipment sends to said management server and carries said identification information and to second message of the affirmation message of said MTC Device trigger messages.
22. method as claimed in claim 21 is characterized in that, said identification information needs the process of unique identification transmission MTC Device trigger messages that at least can be interim, and unique identification MTC Device trigger messages that perhaps at least can be interim specifically comprises:
Said management server is the Transaction Identifier that the transmission course of this MTC Device trigger messages and subsequent message thereof is distributed; Or,
Said management server is the sequence number that said MTC Device trigger messages is distributed.
23. a terminal equipment is characterized in that, comprises at least:
Receiver module is used for the message that the receiving management server is sent;
Sending module; Be used for said receiver module successfully receive said management server and sent carry first message of identification information and MTC Device trigger messages the time, send to said management server and to carry said identification information and second message of the affirmation message of said MTC Device trigger messages.
CN201110397658.7A 2011-12-02 2011-12-02 The delivery confirmation method and apparatus of MTC Device Trigger message Active CN102427604B (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201510883429.4A CN105306183B (en) 2011-12-02 2011-12-02 The delivery confirmation method and apparatus of MTC Device triggering message
CN201110397658.7A CN102427604B (en) 2011-12-02 2011-12-02 The delivery confirmation method and apparatus of MTC Device Trigger message
PCT/CN2012/083457 WO2013078928A1 (en) 2011-12-02 2012-10-24 Method and device for acknowledging delivery of mtc device trigger message

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201110397658.7A CN102427604B (en) 2011-12-02 2011-12-02 The delivery confirmation method and apparatus of MTC Device Trigger message

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN201510883429.4A Division CN105306183B (en) 2011-12-02 2011-12-02 The delivery confirmation method and apparatus of MTC Device triggering message

Publications (2)

Publication Number Publication Date
CN102427604A true CN102427604A (en) 2012-04-25
CN102427604B CN102427604B (en) 2015-11-25

Family

ID=45961536

Family Applications (2)

Application Number Title Priority Date Filing Date
CN201510883429.4A Active CN105306183B (en) 2011-12-02 2011-12-02 The delivery confirmation method and apparatus of MTC Device triggering message
CN201110397658.7A Active CN102427604B (en) 2011-12-02 2011-12-02 The delivery confirmation method and apparatus of MTC Device Trigger message

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN201510883429.4A Active CN105306183B (en) 2011-12-02 2011-12-02 The delivery confirmation method and apparatus of MTC Device triggering message

Country Status (2)

Country Link
CN (2) CN105306183B (en)
WO (1) WO2013078928A1 (en)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013078928A1 (en) * 2011-12-02 2013-06-06 电信科学技术研究院 Method and device for acknowledging delivery of mtc device trigger message
WO2013189222A1 (en) * 2012-06-19 2013-12-27 中兴通讯股份有限公司 Trigger information sending method, protocol conversion method, and system thereof
WO2014029284A1 (en) * 2012-08-20 2014-02-27 中兴通讯股份有限公司 Method and device for congestion control
WO2014067485A1 (en) * 2012-11-05 2014-05-08 华为终端有限公司 Method and core network device for transmitting device trigger message
WO2014071758A1 (en) * 2012-11-06 2014-05-15 中兴通讯股份有限公司 Method for sending information, mtc server, user equipment and mtc system
CN104349373A (en) * 2013-08-07 2015-02-11 华为终端有限公司 Terminal monitoring event posting method, application server and home location equipment
CN104471876A (en) * 2012-08-03 2015-03-25 英特尔公司 Device trigger recall/replace feature for 3gpp/m2m systems
WO2016106561A1 (en) * 2014-12-30 2016-07-07 华为技术有限公司 Message reporting apparatus and method as well as data sending apparatus and method
WO2016177059A1 (en) * 2015-10-20 2016-11-10 中兴通讯股份有限公司 Trigger message processing method, apparatus and system
WO2017071531A1 (en) * 2015-10-30 2017-05-04 阿里巴巴集团控股有限公司 Method and apparatus for sending information
WO2017161995A1 (en) * 2016-03-24 2017-09-28 电信科学技术研究院 Method and device for data transmission launched by terminal
CN107682842A (en) * 2012-06-29 2018-02-09 日本电气株式会社 The optimization that MTC device triggering is transmitted
US10111118B2 (en) 2012-08-03 2018-10-23 Intel Corporation Network assistance for device-to-device discovery
US10390239B2 (en) 2012-08-03 2019-08-20 Intel Corporation Establishing application-based routing policies in multi-mode user equipment using operating system-specific identifiers
US10405211B2 (en) 2012-08-03 2019-09-03 Intel Corporation High efficiency distributed device-to-device (D2D) channel access
CN111858100A (en) * 2020-07-28 2020-10-30 浪潮电子信息产业股份有限公司 BMC message transmission method and related device
US11122647B2 (en) 2012-08-03 2021-09-14 Apple Inc. Enhanced node B, user equipment and methods for discontinuous reception in inter-eNB carrier aggregation

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101267431A (en) * 2007-03-12 2008-09-17 中兴通讯股份有限公司 Matching method of initialization request message in IP multimedia sub-system service trigger
CN102892099A (en) * 2011-07-20 2013-01-23 中兴通讯股份有限公司 Method, system, terminal and network side for responding triggering by terminal

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101064665B (en) * 2006-04-27 2010-06-23 上海无线通信研究中心 Service quality based HARQ method
CN101174930B (en) * 2006-11-03 2012-01-04 华为技术有限公司 Method and apparatus for implementing automatic retransmission request in relay system
CN102045897B (en) * 2009-10-10 2014-08-13 中兴通讯股份有限公司 Group identification reporting method and device
CN102083172B (en) * 2009-12-01 2013-09-11 中兴通讯股份有限公司 Method, device and system for limiting moving times of machine type communication (MTC) equipment by network
CN102215474B (en) * 2010-04-12 2014-11-05 华为技术有限公司 Method and device for carrying out authentication on communication equipment
CN102238477B (en) * 2010-04-30 2014-02-19 华为终端有限公司 Method for triggering group of MTC (Machine Type Communication) devices to communicate with MTC server and MTC device
CN105306183B (en) * 2011-12-02 2019-02-05 电信科学技术研究院 The delivery confirmation method and apparatus of MTC Device triggering message

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101267431A (en) * 2007-03-12 2008-09-17 中兴通讯股份有限公司 Matching method of initialization request message in IP multimedia sub-system service trigger
CN102892099A (en) * 2011-07-20 2013-01-23 中兴通讯股份有限公司 Method, system, terminal and network side for responding triggering by terminal

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP: "《3GPP TR 23.888 V1.6.0》", 30 November 2011 *

Cited By (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013078928A1 (en) * 2011-12-02 2013-06-06 电信科学技术研究院 Method and device for acknowledging delivery of mtc device trigger message
US9204273B2 (en) 2012-06-19 2015-12-01 Zte Corporation Method and system for trigger information transmission and protocol conversion
WO2013189222A1 (en) * 2012-06-19 2013-12-27 中兴通讯股份有限公司 Trigger information sending method, protocol conversion method, and system thereof
CN103517230A (en) * 2012-06-19 2014-01-15 中兴通讯股份有限公司 Method and system for trigger information sending and protocol conversion
CN103517230B (en) * 2012-06-19 2018-05-08 中兴通讯股份有限公司 Trigger the method and system of information transmission and protocol conversion
US11863425B2 (en) 2012-06-29 2024-01-02 Nec Corporation Optimization of MTC device trigger delivery
CN107682842B (en) * 2012-06-29 2020-10-16 日本电气株式会社 Optimization of MTC device trigger delivery
CN107682842A (en) * 2012-06-29 2018-02-09 日本电气株式会社 The optimization that MTC device triggering is transmitted
US11296976B2 (en) 2012-06-29 2022-04-05 Nec Corporation Optimization of MTC device trigger delivery
US10992722B2 (en) 2012-08-03 2021-04-27 Apple Inc. High efficiency distributed device-to-device (D2D) channel access
US10405211B2 (en) 2012-08-03 2019-09-03 Intel Corporation High efficiency distributed device-to-device (D2D) channel access
US10390239B2 (en) 2012-08-03 2019-08-20 Intel Corporation Establishing application-based routing policies in multi-mode user equipment using operating system-specific identifiers
CN104471876A (en) * 2012-08-03 2015-03-25 英特尔公司 Device trigger recall/replace feature for 3gpp/m2m systems
US10425846B2 (en) 2012-08-03 2019-09-24 Intel Corporation Network assistance for device-to-device discovery
US10111118B2 (en) 2012-08-03 2018-10-23 Intel Corporation Network assistance for device-to-device discovery
US11122647B2 (en) 2012-08-03 2021-09-14 Apple Inc. Enhanced node B, user equipment and methods for discontinuous reception in inter-eNB carrier aggregation
CN104471876B (en) * 2012-08-03 2018-08-10 英特尔公司 Include the 3GPP/M2M method and apparatus of equipment triggering recall/replacement feature
WO2014029284A1 (en) * 2012-08-20 2014-02-27 中兴通讯股份有限公司 Method and device for congestion control
CN103634841A (en) * 2012-08-20 2014-03-12 中兴通讯股份有限公司 Congestion control method and device
WO2014067485A1 (en) * 2012-11-05 2014-05-08 华为终端有限公司 Method and core network device for transmitting device trigger message
US9578542B2 (en) 2012-11-05 2017-02-21 Huawei Device Co., Ltd. Method and core network device for transmitting device trigger message
CN103812599B (en) * 2012-11-05 2017-10-17 华为终端有限公司 The method and equipment of the core network of a kind of transmission equipment triggering message
US9706334B2 (en) 2012-11-06 2017-07-11 Zte Corporation Method for sending information, MTC server, user equipment and MTC system
WO2014071758A1 (en) * 2012-11-06 2014-05-15 中兴通讯股份有限公司 Method for sending information, mtc server, user equipment and mtc system
CN103813276A (en) * 2012-11-06 2014-05-21 中兴通讯股份有限公司 Information sending method, MTC server, user equipment, and MTC system
CN104349373A (en) * 2013-08-07 2015-02-11 华为终端有限公司 Terminal monitoring event posting method, application server and home location equipment
WO2016106561A1 (en) * 2014-12-30 2016-07-07 华为技术有限公司 Message reporting apparatus and method as well as data sending apparatus and method
WO2016177059A1 (en) * 2015-10-20 2016-11-10 中兴通讯股份有限公司 Trigger message processing method, apparatus and system
CN106656729B (en) * 2015-10-30 2019-11-22 阿里巴巴集团控股有限公司 A kind of method and device sending information
US10798042B2 (en) 2015-10-30 2020-10-06 Alibaba Group Holding Limited Information sending method and apparatus
CN106656729A (en) * 2015-10-30 2017-05-10 阿里巴巴集团控股有限公司 Method and device for sending information
WO2017071531A1 (en) * 2015-10-30 2017-05-04 阿里巴巴集团控股有限公司 Method and apparatus for sending information
CN107231689B (en) * 2016-03-24 2020-03-24 电信科学技术研究院 Terminal-initiated data transmission method and device
CN107231689A (en) * 2016-03-24 2017-10-03 电信科学技术研究院 Data transmission method and device that a kind of terminal is initiated
TWI738732B (en) * 2016-03-24 2021-09-11 大陸商電信科學技術研究院 Method and device for data transmission initiated by terminal
WO2017161995A1 (en) * 2016-03-24 2017-09-28 电信科学技术研究院 Method and device for data transmission launched by terminal
CN111858100A (en) * 2020-07-28 2020-10-30 浪潮电子信息产业股份有限公司 BMC message transmission method and related device

Also Published As

Publication number Publication date
CN102427604B (en) 2015-11-25
WO2013078928A1 (en) 2013-06-06
CN105306183A (en) 2016-02-03
CN105306183B (en) 2019-02-05

Similar Documents

Publication Publication Date Title
CN102427604B (en) The delivery confirmation method and apparatus of MTC Device Trigger message
CN108370506B (en) Method for serving node relocation in wireless communication system and apparatus therefor
EP3320706B1 (en) Optimized short message transport
CN102340826B (en) A kind of method and apparatus of transfer of data
US11863425B2 (en) Optimization of MTC device trigger delivery
EP2654326B1 (en) Method and apparatus for reliably transmitting group multicast using a cell broadcasting technique in a mobile communication system
US20150181564A1 (en) Device trigger recall/replace feature for 3gpp/m2m systems
US8831650B2 (en) Method of exchanging SMS data in a wireless communications system
JP2015511409A5 (en)
CN105706519A (en) Control of small data transmission in a mobile radio communications network
WO2007078159A1 (en) Method and apparatus for transmitting sip data of idle mode ue in a mobile communication system
CN102340754A (en) Data transmission and receiving methods and equipment
EP2816864B1 (en) Information transmission method, system and device
KR101641518B1 (en) Apparatus and method of the reliable and dynamic group delivery based on multicast or broadcast mobile wireless link
CN104579602A (en) LTE (long term evolution) broadcast multicast repeat method
CN101902732A (en) Method and system for synchronizing EPS (Evolved Packet System) bearer context statuses
CN105450429B (en) Data transmission method, device, system and communication equipment
WO2015103604A1 (en) Techniques for a device trigger recall/replace procedure
CN105792147B (en) Short message delivery failure processing method, device and system
CN101568113B (en) Method, device and system for realizing synchronization of loading state
CN100488292C (en) Mobile short-message system and mailing method
CN103001885A (en) Data message transmission method and system
CN109245816B (en) Link detection method and device
JP5382379B2 (en) SMS transport resource control
US20200374361A1 (en) Apparatus, system and method for mtc

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CP01 Change in the name or title of a patent holder
CP01 Change in the name or title of a patent holder

Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road

Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY

Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road

Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20210607

Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing

Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd.

Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road

Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY