CN100421493C - Method for implementing waiting in time delay in conversation procedure for devices connection - Google Patents
Method for implementing waiting in time delay in conversation procedure for devices connection Download PDFInfo
- Publication number
- CN100421493C CN100421493C CNB2005100734129A CN200510073412A CN100421493C CN 100421493 C CN100421493 C CN 100421493C CN B2005100734129 A CNB2005100734129 A CN B2005100734129A CN 200510073412 A CN200510073412 A CN 200510073412A CN 100421493 C CN100421493 C CN 100421493C
- Authority
- CN
- China
- Prior art keywords
- time
- delay
- equipment
- notification message
- executable operations
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Telephonic Communication Services (AREA)
Abstract
The present invention discloses a method for implementing time-delay wait in the process of dialogue connection by devices. The method comprises: a connection is established between a device applying for operation and a device executing operation, and the device applying for operation issues operation to the device executing operation; the device applying for operation waits for operation results returned by the device executing operation according to overtime duration in the process of the operation of the device executing operation, wherein when the device executing operation can not complete the operation in the overtime duration, the device executing operation forwards a time-delay notification message to the device applying for operation; the device applying for operation prolongs time for waiting operation results according to the time-delay notification message.
Description
Technical field
The present invention relates to communication technical field, relate in particular to the implementation method of in conversation procedure for devices connection, prolonging wait.
Background technology
Portable terminal is an important component part in the whole mobile operation service system.Increasingly sophisticated along with termination function, the possibility that terminal software goes wrong significantly increases.Competition between the following operator is growing more intense, and how effectively to guarantee user experience, improves user's loyalty, keeps efficiently service quality and low-cost device to safeguard a significant concern point that has become operator, manufacturer terminal.
Because in the process of carrying out plant maintenance, the duration that different maintenance processes needs is also inequality, therefore, the overtime duration that can't formulate a unification comes the timeout issue of treatment system.Existing open mobile alliance device management (OMADM) standard does not have a kind of effective mechanism yet, is used to handle timeout issue.
In existing technical scheme, because some operations of issuing may consume the unpredictable time, it does not have the state information of assigned operation to return in official hour, and server waits for that always the state information of operating result returns.Shown in Figure 1A, its treatment step is as follows:
Step 1: according to the Setup phase in the OMADM agreement connect (omit connect detailed process);
Step 2: server issues an operation requests;
For example as issuing orders;
<Get>
<CmdID>1</CmdID>
<Item>
<Target>
<LocURI>./Setting_data/set</LocURI>
</Target>
</Item>
</Get>
Step 3: terminal is carried out this operation requests, and server is waited for this operating result simultaneously;
Step 4: terminal return result, server finishes wait state;
<Result>
<MsgRef>5</MsgRef>
<CmdRef>1</CmdRef>
<CmdID>2</CmdID>
<Item>
<Source>
<LocURI>./Setting_data/set</LocURI>
</Source>
<Data>123</Data>
</Item>
</Result>
Step 5: carry out next one operation.
Because the time of some operation is inestimable among the OMA DM, and in case operation side in operating process, fault (operation side cuts off the power supply or do not have network signal etc.) has taken place, causing replying next message gives when applying for operation side, then can make application operation side be in long-term wait state, until last overtime.Consult shown in Figure 1B, its processing procedure is as follows:
Step 1: according to the Setup phase in the OMA DM agreement connect (omit connect detailed process);
Step 2: application operation side issues an operation requests;
Step 3: break down (outage or network signal interrupt) in operation side, causes replying an Alert (1223) message and give application operation side.
Step 4: application operation side waits for the Alert message of operation side or an operating result that returns;
Step 5: application operation side wait timeout;
Step 6: application operation side disconnects and connecting.
Because some operating time in the OMA DM agreement is inestimable, the operating time that has is extremely long, this just possibly can't guarantee to operate consuming time can finishing normally and finish before the opposing party is overtime, when operation side did not finish operation this time, connection was interrupted.Consult shown in Fig. 1 C, its flow process is as follows:
Step 1: according to the Setup Phase in the OMA DM agreement connect (omit connect detailed process);
Step 2: application operation side issues operation requests;
Step 3: the side's of operation executable operations request;
Step 4: application operation side enters the time-delay wait state;
Step 5: application operation side, the time-delay wait timeout sends one and ends connection message Alert (1223);
<Alert>
<CmdID>2</CmdID>
<Data>1223</Data><！--an?unexpected?end-->
<Item></Item>
<Item>
<Data></Data>
</Item>
</Alert>
Step 6: application operation side disconnects this time and connecting, and discharges relevant system resource.
There is following shortcoming in above-mentioned existing scheme:
1, sets unified time-out time for all operations, if the time of the square complete operation of executable operations is greater than time-out time, apply for that then apparatus operating can interrupt connecting, can't guarantee that this operation can normally finish before system is overtime, reduced the reliability of connection session process.
2, in the process of executable operations, the application apparatus operating can not in time be learnt the state of the equipment of executable operations.
Summary of the invention
The invention provides a kind of implementation method that time-delay is waited in conversation procedure for devices connection, in order to solving prior art when the equipment complete operation of the carrying out time-out time that surpasses regulation consuming time, the application apparatus operating disconnects and connects and can't guarantee to operate the problem of normally finishing.
For addressing the above problem, the invention provides following technical scheme:
A kind of implementation method that time-delay is waited in conversation procedure for devices connection, this method connects between the equipment of application apparatus operating and executable operations, issues operation by the application apparatus operating to the equipment of executable operations; Equipment in executable operations carries out in the operating process, and the application apparatus operating is pressed the equipment return result that time-out time is waited for executable operations; Wherein, when the equipment of described executable operations was determined can't finish described operation in described time-out time, to application apparatus operating forward delay interval notification message, the application apparatus operating prolonged the time of waiting for operating result according to this time-delay notification message.
Described time-out time is consulted to determine when connecting by the equipment of application apparatus operating and executable operations; Perhaps, described time-out time adopts the fixed value that can be modified.
The application apparatus operating prolong to wait for that the time of operating result is meant again the equipment return result by executable operations such as time-out times, maybe the time that requires to prolong in remaining time of waiting for and this notification message is added up as time-out time, and press the equipment return result of executable operations such as this time-out time again.
The application apparatus operating after receiving described time-delay notification message also the equipment to executable operations return response message.
The application apparatus operating if receive the operating result that the equipment of executable operations returns before overtime arrival, then finishes to wait for after prolonging the stand-by period.
Described application apparatus operating is the device management server in the equipment management system, and the equipment of executable operations is terminal equipment; Perhaps, the application apparatus operating is a terminal equipment, and the equipment of executable operations is the device management server in the equipment management system.
By the order forward delay interval notification message in the expansion OMADM agreement, perhaps, come the forward delay interval notification message by in the OMADM agreement, increasing order, perhaps, send to the application apparatus operating as notification message by the user-defined identification symbol.
The present invention has following beneficial effect:
1, the present invention is when the duration of the present action need of the device discovery of executable operations may cause the opposite end overtime, make the application apparatus operating prolong the time of waiting for operating result by the forward delay interval notification message, can normally finish to guarantee this time operation, thereby improved the reliability of connection session process, also effectively increased the exploitativeness and the extensibility of service.
2, consult rational time-out time by both sides' equipment, and the application apparatus operating disconnects connection on one's own initiative when the equipment of executable operations breaks down, and can at utmost reduce waste of network resources.
3,, make the application apparatus operating can learn the other side's current state in time by the forward delay interval notification message; By replying the time-delay notification message, can make the device learns application apparatus operating of executable operations and the state of network; Therefore, also can play fault diagnosis functions.
Description of drawings
Figure 1A, Figure 1B, Fig. 1 C are the flow chart that device management server is waited for the terminal equipment operating result in the prior art;
Fig. 2 A consults the schematic diagram of overtime duration at access phase for server among the present invention and terminal equipment;
Fig. 2 B is for preserving the schematic diagram of fixed-timeouts duration on the management tree of equipment among the present invention;
Fig. 3 A, Fig. 3 B server are received the process chart that prolongs time-out time behind the time-delay notification message;
Fig. 4 A is that server is received the flow chart of replying behind the time-delay notification message;
Fig. 4 B is that server is received the flow chart of not replying behind the time-delay notification message;
Fig. 5 A is the time point schematic diagram of terminal equipment forward delay interval notification message;
Fig. 5 B is server is received operating result and finished to wait in delay time a schematic diagram;
Fig. 5 C is that server is received the flow chart that time-delay notification message and time-delay are waited in delay time;
Fig. 5 D is the schematic diagram that server initiatively disconnects connection.
Embodiment
Because after the application apparatus operating issues operation, the duration of finishing different action needs on the equipment of executable operations is also inequality, therefore, the present invention makes the equipment of executable operations can not be in time-out time during complete operation in the overlong time of the action need of carrying out, equipment by executable operations sends a time-delay notification message to the application apparatus operating, after the application apparatus operating receives this time-delay notification message, prolong the delay time of waiting for the operation return results.
Present embodiment is that example describes with device management server in the equipment control (DM) to the management of terminal equipment mainly, and wherein, the application apparatus operating can be a device management server, and the equipment of executable operations is terminal equipment; In like manner, the application apparatus operating can be a terminal equipment, and the equipment of executable operations can be device management server.Terminal equipment includes but not limited to existing portable terminal and fixed terminal.
In order more reasonably to determine to wait for the time-out time of operating result, device management server and terminal equipment can adopt following manner to consult both sides' time-out time:
(1), determines time-out time in the stage of connecting
When device management server after terminal equipment sends an operation requests, enter a time-delay wait state, wait for the return results of terminal equipment, the definite of time-delay stand-by period can be held consultation in being connected establishment stage with device management server by terminal equipment, shown in Fig. 2 A.Negotiation includes but not limited to simply inform, get maximum, gets minimum value, mean value etc.For example, the determined time-delay stand-by period of terminal equipment is 15 seconds, and the determined time-delay stand-by period of device management server is 10 seconds, then may be according to minimum value principle (in order at utmost to reduce the stand-by period of device management server), getting the stand-by period of delaying time in this time connection procedure is 10 seconds.
(2), adopt fixing time-out time value
Set a fixed-timeouts time value, this value can be deposited on the node of management tree, and each the connection after the foundation, the value of getting this node from management tree is with the time-out time value of this value as this connection.Shown in Fig. 2 B, its value can be deposited in below the Operator node.
The time-out time value can be modified, and is made amendment by the Replace order that OMA DM provides by server or terminal.An example of revising the time-out time value is as follows:
<Replace>
<CmdID>3</CmdID>
<Item>
<Source><LocURI>./Operator/Timeout</LocURI></Source>
<Meta>
<Format?xmlns＝′syncml:metinf>Integer</Format>
<Type?xmlns＝′syncml:metinf>text/plain</Type>
</Meta>
<Data>15</Data>
</Item>
</Replace>
Owing to do not stipulate the time-delay notification message in the OMA DM agreement, can adopt following three kinds of modes to realize:
(1), the definition of the Alert order in the expansion OMA DM agreement
In existing OMA DM agreement, different definition has been expanded in order to Alert, and it is mainly used in warning, perhaps reminds purposes; For example Alert (1222) when being used to transmit big file, can send an Alert (1222) by transmitting terminal, represents follow-uply also to be arrived by other message (message); And Alert (1223) expression transmit leg will connect interruption to this.
So realization of the notification message of delaying time, can be on the basis of original OMA DM agreement, Alert order is expanded, an Alert order of waiting for as time-delay, but expansion must be on the basis of the Alert command collision expanded in guaranteeing the original OMADM agreement of discord.For example, can expand time-delay notification message Alert order is 2000 (suppose that 2000 is on the basis that original Alert explosion command conflicts in the discord OMA DM agreement, as long as the numbering that other are random is the conflicts of the original Alert explosion command of discord).The time-delay latency value can be machine-processed through consultation in advance definite by transmitting terminal and receiving terminal, also the time-delay latency value can be positioned in the Alert message.Example is as follows:
<Alert>
<CmdID>2</CmdID>
＜Data〉2000＜/Data〉＜!--time-delay notification message--〉
<Item></Item>
<Item>
＜Data〉15＜/Data〉＜! The time-delay latency value, optional--
</Item>
</Alert>
(2), expansion OMA DM protocol command
Owing to for relevant time-delay waiting mechanism is provided, also can expand in the OMA DM agreement by order to OMADM, for example, provide a Delay order, wait for instruction as a time-delay.Send a Delay instruction from transmitting terminal, receiving terminal receives after the Delay instruction, will start time-delay and wait for that the time value that concrete time-delay is waited for can be by transmitting terminal and receiving terminal as offered, the latency value of perhaps delaying time is by sending in the Delay instruction, and example is as follows:
<Delay>
<CmdID>2</CmdID>
<Item>
＜Data〉15＜/Data〉＜! The time-delay latency value, optional--
</Item>
</Delay>
In the last example, the Delay instruction description receiving terminal wait of delaying time, the time value that its time-delay is waited for is 15 seconds, should value also can be sky certainly, then gets transmitting terminal and receiving terminal and consults the latency value of delaying time in advance.
(3), with the definition of protocol-independent
In order OMA DM agreement not to be changed, the time-delay notification message can not define in the standard of OMA DM agreement yet, by a self-defined identifier, the character (0x0F) that for example is byte is as the time-delay notification message, this identifier and protocol command are irrelevant, the definite of this identifier must be reached an agreement in advance by transmitting terminal and terminal, when each transmitting terminal request delay is waited for, only need to send the message that comprises this byte content, receiving terminal receives this message, identify this time-delay notification message, then enter the time-delay stand-by period.
Device management server can prolong the stand-by period by following mode after receiving the time-delay notification message:
(1) restarts the wait of next time delaying time at every turn
When device management server receives the time-delay notification message, it will restart a new time-delay stand-by period section to the zero clearing of time-delay latency value, consult shown in Fig. 3 A, and its handling process is as follows:
Step 1: device management server issues an operation requests, enters the time-delay wait state;
Step 2: terminal equipment executable operations request;
Step 3: when time-delay notification message point, terminal equipment does not also have complete operation, sends a time-delay notification message to device management server;
Step 4: the device management server latency value zero clearing of will delaying time, carry out the next one time-delay stand-by period;
Step 5: return result is finished in the terminal equipment operation;
Step 6: device management server finishes time-delay to be waited for, carries out next operation requests.
(2) pending adding up such as will delay time
Because when device management server receives the time-delay notification message, the time-delay stand-by period that is not it arrives, may also have the remaining time, can be delayed time last time and wait for remaining time, add up with this terminal equipment time-delay time-delay latency value that notification message comprised, draw device management server with this and enter the time-out time value of waiting for operating result next time.Consult shown in Fig. 3 B, its flow process is as follows:
Step 1: device management server issues operation requests, enters the time-delay wait state;
Step 2: terminal equipment executable operations request;
Step 3: terminal equipment sends point at the time-delay notification message, and operation is not finished, and sends a time-delay notification message;
Step 4: device management server receives the time-delay notification message, will remain the time-delay latency value, with the addition of the desired time-delay latency value of terminal equipment, as the time-delay wait state that enters next time;
Step 5: terminal equipment transmit operation result;
Step 6: device management server receives the operation return results;
Step 7: device management server finishes the time-delay wait state, carries out next operation requests.
Device management server can adopt following dual mode to handle this message after receiving the time-delay notification message of terminal equipment:
(1) the time-delay notification message is replied
Device management server is replied a message and is given terminal equipment after receiving the time-delay notification message of terminal equipment, can include time-delay in this message and wait for value remaining time.Can expand OMA DM agreement, increase a time-delay notice commands in return DelayAck, by answer to the time-delay notification message, terminal equipment can learn that the current device management server still is in the time-delay wait state, can comprise time-delay wait value remaining time in the message owing to reply, terminal equipment can learn that device management server also will continue time-delay and how long wait for.Consult shown in Fig. 4 A, its handling process is as follows:
Step 1: device management server issues an operation requests, and device management server enters the time-delay wait state;
Step 2: terminal equipment is at time-delay notification message point, and operation is not finished, and sends a time-delay notification message to device management server, applies for its further time-delay wait state;
Step 3: device management server enters next step time-delay wait state;
Step 4: device management server sends a DelayAck order,
<DelayAck>
<CmdID>2</CmdID>
<Item>
＜Data〉5＜/Data〉＜! Device management server residue time-delay latency value, optional--
</Item>
</DelayAck>
Step 5: operating result returns;
Step 6: device management server finishes the time-delay wait state, carries out next one operation.
By the answer mode, terminal equipment also can in time be understood the present equipment operation normal condition of device management server, thereby both sides' mutual malfunction monitoring mechanism also is provided.
(2) the time-delay notification message is not replied
Under the situation of the equipment running status that need not at terminal equipment to know that device management server is current, device management server need not the answer of forward delay interval notification message, has so also alleviated the burden of network.Consult shown in Fig. 4 B, its handling process is as follows:
Step 1: device management server issues an operation requests, enters the time-delay wait state simultaneously;
Step 2: before time-delay notification message time point arrived, not complete operation request of terminal equipment sent a time-delay notification message;
Step 3: device management server receives a time-delay notification message, enters next time-delay wait state;
Step 4: the request of terminal equipment complete operation, operating result is returned;
Step 5: device management server receives operating result and returns, and finishes the time-delay wait state;
Step 6: device management server enters next step operation.
Determine the time point of terminal equipment forward delay interval notification message, should consider the time-delay of Network Transmission.Because the time-delay stand-by period of device management server is to send operation requests from it to begin to count, owing to also need the time in the network transmission process, therefore can estimate the time point of terminal equipment forward delay interval notification message, consult shown in Fig. 5 A.
If the time-delay latency value is T, the time point of terminal equipment forward delay interval notification message in time-out time is Ts, and the propagation delay time of network is Tn; Then the time point Ts of the forward delay interval notification message of terminal equipment should satisfy: Ts+Tn＜T; Should guarantee that promptly device management server can receive the time-delay notification message before the time-delay stand-by period arrives.In like manner, if calculate from the N transmitting order to lower levels that begins second with server, to arrive the time of client be N-Tn to the order that sends of server so, therefore, terminal equipment should can be received this message to guarantee device management server at N+T-2*Tn forward delay interval notification message before second.
Below for the delay process in the conversation procedure, for the convenience of describing, all be to describe under the hypothesis device management server situation about need not reply its time-delay notification message that receives, certainly in the actual conditions, device management server may be to reply its time-delay notification message that receives.
(1), the terminal equipment operating time is very short
If the terminal equipment operating time is very short, then before the time point of forward delay interval notification message, operating result is returned to device management server, the notification message of then delaying time needn't send.Shown in Fig. 5 B, its handling process is as follows:
Step 1: device management server transmit operation request enters the time-delay wait state;
Step 2: terminal equipment, operate according to operation requests;
Step 3: before forward delay interval notification message point, return result;
Step 4: because the time-delay stand-by period of device management server, also not arrival will be so device management server will directly carry out next operation.
(2), the terminal equipment operating time is long
The terminal equipment operating time is long, can not one complete operation in the delay time, then terminal equipment should send on the point to device management server forward delay interval notification message at the time-delay notification message, device management server is waited for the return result of terminal equipment, enters the wait state of next time delaying time.Shown in Fig. 5 C, its handling process is as follows:
Step 1: device management server issues an operation requests, enters the time-delay wait state;
Step 2: the terminal equipment operation is not finished, and sends point at first time-delay notification message, sends a time-delay notification message;
Step 3: device management server will carry out the next one time-delay stand-by period;
Step 4: the terminal equipment operation is not finished, and sends point at second time-delay notification message, sends a time-delay notification message again;
Step 5: device management server enters the next time-delay stand-by period;
Step 6: device management server is not finished, and sends point at the 3rd time-delay notification message, sends a time-delay notification message again;
Step 7: device management server enters the next time-delay stand-by period;
Step 8: device management server is not finished, and sends point at the 3rd time-delay notification message, sends a time-delay notification message again;
Step 9: device management server enters the next time-delay stand-by period;
Step 10: the terminal equipment operation is finished, and transmit operation is the result return;
Step 11: device management server finishes time-delay in advance to be waited for;
Step 12: device management server carries out next one operation.
In this handling process, the number of times that the device management server time-delay is waited for is fixed according to the terminal equipment operating time, if the operating time is long, the number of times of the wait of may delaying time is just many; Operating time is short, and might not delay time wait or time-delay wait for that number of times is few.
(3) device management server initiatively disconnects connection
If device management server before wait timeout, does not also receive the operation return results, when also not receiving the time-delay notification message, then device management server initiatively disconnects connection; Consult shown in Fig. 5 D, its handling process is as follows:
Step 1: device management server issues an operation requests, enters the time-delay wait state;
Step 2: the terminal equipment operation is not finished, and at forward delay interval notification message point, sends a time-delay notification message;
Step 3: device management server receives the time-delay notification message, enters the next time-delay stand-by period;
Step 4: the terminal equipment operation is not finished, and at forward delay interval notification message point, sends a time-delay notification message;
Step 5: device management server receives the time-delay notification message, enters the next time-delay stand-by period;
Step 6: terminal equipment breaks down, and can't send abort message, also can't the forward delay interval notification message;
Step 7: the device management server time-delay stand-by period arrives, and does not receive the operation return results, does not receive the time-delay notification message, does not receive abort message;
Step 8: device management server, initiatively disconnect connection this time, discharge related resource.
In this handling process, because the interruption of the connection that the fault of terminal equipment causes, device management server can be at a time-delay notification message in the time, in time learn the fault of operation side, thereby can this time of active break connection, discharge the related resource that this time connects, farthest alleviate waste of network resources.
Though above-mentioned handling process all issues to terminal equipment with device management server and is operating as example, but terminal equipment is to the device management server solicit operation, by the processing procedure of device management server executable operations and in like manner above-mentioned, those of ordinary skill in the art can obtain corresponding handling process apparently according to foregoing description.Equally, technical scheme of the present invention also is applicable to and operates between the communication equipment and need time-delay to wait in other communication systems of operating result.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (11)
1. implementation method that time-delay is waited in conversation procedure for devices connection, this method connects between the equipment of application apparatus operating and executable operations, by applying for that apparatus operating issues operation to the equipment of executable operations; Equipment in executable operations carries out in the operating process, and the application apparatus operating is pressed the equipment return result that time-out time is waited for executable operations; It is characterized in that, when the equipment of described executable operations is determined can't finish described operation in described time-out time, to application apparatus operating forward delay interval notification message, the application apparatus operating prolongs the time of waiting for the return result according to this time-delay notification message.
2. the method for claim 1 is characterized in that, described time-out time is consulted to determine in the process of connecting or in the back that connects by the equipment of application apparatus operating and executable operations; Perhaps, described time-out time adopts the fixed value that can be modified.
3. method as claimed in claim 2 is characterized in that, when time-out time adopts fixed value, this fixed value is kept on the management tree node of equipment.
4. method as claimed in claim 2 is characterized in that, the mode of consulting time-out time comprises: the side in the equipment informs the opposing party by both party, and get both sides' equipment maximum, minimum value or the mean value in definite time-out time.
5. the method for claim 1, it is characterized in that, the time that the application apparatus operating prolongs wait return result is meant the equipment return result who waits for executable operations again by time-out time, or the time that requires in remaining time of waiting in the time-out time and this notification message to prolong added up as time-out time, and wait for the equipment return result of executable operations again by this time-out time.
6. the method for claim 1 is characterized in that, application apparatus operating equipment to executable operations after receiving described time-delay notification message returns response message; Perhaps, the application apparatus operating after receiving described time-delay notification message not the equipment to executable operations return response message.
7. method as claimed in claim 6 is characterized in that, carries the remaining time that time-delay is waited in the response message that the equipment to executable operations returns.
8. the method for claim 1 is characterized in that, the equipment of executable operations sent described time-delay notification message before current delay waits for arriving the time point that is not less than the Network Transmission time-delay overtime remaining time.
9. the method for claim 1 is characterized in that, the application apparatus operating if receive the operating result that the equipment of executable operations returns before overtime arrival, then finishes to wait for after prolonging the stand-by period.
10. as each described method of claim 1 to 9, it is characterized in that described application apparatus operating is the device management server in the equipment management system, the equipment of executable operations is terminal equipment; Perhaps, the application apparatus operating is a terminal equipment, and the equipment of executable operations is the device management server in the equipment management system.
11. method as claimed in claim 10, it is characterized in that, by the order forward delay interval notification message in the expansion OMADM agreement, perhaps, come the forward delay interval notification message by in OMA DM agreement, increasing order, perhaps, send to the application apparatus operating as notification message by the user-defined identification symbol.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100734129A CN100421493C (en) | 2005-05-30 | 2005-05-30 | Method for implementing waiting in time delay in conversation procedure for devices connection |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100734129A CN100421493C (en) | 2005-05-30 | 2005-05-30 | Method for implementing waiting in time delay in conversation procedure for devices connection |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1874581A CN1874581A (en) | 2006-12-06 |
| CN100421493C true CN100421493C (en) | 2008-09-24 |
Family
ID=37484787
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100734129A Expired - Fee Related CN100421493C (en) | 2005-05-30 | 2005-05-30 | Method for implementing waiting in time delay in conversation procedure for devices connection |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100421493C (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101932122B (en) * | 2009-06-26 | 2013-05-08 | 鸿富锦精密工业（深圳）有限公司 | User terminal equipment, base station and method for establishing business flow |
| CN101997858B (en) * | 2009-08-24 | 2013-11-06 | 华为终端有限公司 | Method and device for consumer premises equipment wide area network management protocol (CWMP) conversation interaction |
| CN102156684A (en) * | 2010-12-15 | 2011-08-17 | 成都市华为赛门铁克科技有限公司 | Interface delay protecting method, coprocessor and data processing system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1151551A (en) * | 1995-10-10 | 1997-06-11 | 国际商业机器公司 | System and method for dynamically varying low level file system operation timeout parameters in network systems of variable bandwidth |
| CN1362816A (en) * | 2000-12-28 | 2002-08-07 | Lg电子株式会社 | System and method for processing multi-media information bag in medium access control processor |
| CN1370361A (en) * | 1999-08-17 | 2002-09-18 | 艾利森电话股份有限公司 | Method and device for determining time-parameters |
| CN1520125A (en) * | 2003-01-21 | 2004-08-11 | 华为技术有限公司 | Processing method with maximum matched digit reception in media gateway control protocol |
| CN1551551A (en) * | 2003-02-19 | 2004-12-01 | �ձ�������ʽ���� | Wireless communication system and method which improves reliability and throughput of communication and retransmission timeout determining method |
-
2005
- 2005-05-30 CN CNB2005100734129A patent/CN100421493C/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1151551A (en) * | 1995-10-10 | 1997-06-11 | 国际商业机器公司 | System and method for dynamically varying low level file system operation timeout parameters in network systems of variable bandwidth |
| CN1370361A (en) * | 1999-08-17 | 2002-09-18 | 艾利森电话股份有限公司 | Method and device for determining time-parameters |
| CN1362816A (en) * | 2000-12-28 | 2002-08-07 | Lg电子株式会社 | System and method for processing multi-media information bag in medium access control processor |
| CN1520125A (en) * | 2003-01-21 | 2004-08-11 | 华为技术有限公司 | Processing method with maximum matched digit reception in media gateway control protocol |
| CN1551551A (en) * | 2003-02-19 | 2004-12-01 | �ձ�������ʽ���� | Wireless communication system and method which improves reliability and throughput of communication and retransmission timeout determining method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1874581A (en) | 2006-12-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2713641B1 (en) | Method for receiving data, method for transmitting data, mobile terminal, and server | |
| CN100421389C (en) | Method for processing customized task in equipment management | |
| JP5574544B2 (en) | Unified device management method and system | |
| CN104320425A (en) | Method and device for receiving and sending message | |
| WO2015078341A1 (en) | Method and device for remotely updating application program | |
| CN101902697A (en) | System and method for monitoring and operating service through mobile equipment | |
| US20110047002A1 (en) | Mechanism for multisite service state description | |
| CN108182121A (en) | In a kind of Android control large-size screen monitors system module between communication means and system | |
| CN100421493C (en) | Method for implementing waiting in time delay in conversation procedure for devices connection | |
| CN104463670A (en) | Websocket-based bank preposition transaction system construction method | |
| CN101409654A (en) | Method for processing SNMP information in network management system | |
| CN101729284A (en) | Equipment end initiative based method for realizing link polling in management system | |
| CN104253739A (en) | Implementing method, system and device of always online services | |
| CN101562798B (en) | Method and system for realizing network management by short messages | |
| WO2020098284A1 (en) | Communication method, client device, and server device | |
| CN103501298A (en) | Method and device for ensuring continuous flow in a link circuit during no-break service upgrade process | |
| CN114286431B (en) | Method and device for starting low-power mode, storage medium and electronic device | |
| CN105282235B (en) | A method of solution RPC upgrades unstable in double-PON port ONU | |
| CN105681436A (en) | Communication method between control end and Internet of Things devices based on alljoyn protocol | |
| CN114827303B (en) | Intelligent household product management unit, system, application method and electronic equipment | |
| CN101877862A (en) | Large object transmission method and server | |
| KR100274848B1 (en) | Network management method for network management system | |
| KR20040094139A (en) | Method for instant messaging service by using short message in core network-packet service | |
| CN114285699B (en) | Method and device for realizing uniqueness of terminal in distributed gateway session | |
| WO2024103943A1 (en) | Service processing method and apparatus, storage medium, and device |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080924 Termination date: 20160530 |