CN1499802A - Method for realizing reliable transfering transaction by using mechanism of state machine - Google Patents
Method for realizing reliable transfering transaction by using mechanism of state machine Download PDFInfo
- Publication number
- CN1499802A CN1499802A CNA021483671A CN02148367A CN1499802A CN 1499802 A CN1499802 A CN 1499802A CN A021483671 A CNA021483671 A CN A021483671A CN 02148367 A CN02148367 A CN 02148367A CN 1499802 A CN1499802 A CN 1499802A
- Authority
- CN
- China
- Prior art keywords
- state
- transaction
- affairs
- request
- incident
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/90—Buffering arrangements
Abstract
Transaction Request sent by protocol entity to opposite entity is kept in Request queue, and Transaction Reply received from opposite entity for responding Transaction Request is kept in Response queue. Based on event trigging change of state, Transactions in two queues complete corresponding operation and change of state. Thus, reliable transmission of Transactions is realized by using mechanism of state machine. The invention overcomes disadvantages of realizing reliable transmission of Transactions: complicated mechanism and difficult to control testing.
Description
Technical field
The present invention relates to communication technical field, relate in particular to a kind of method that realizes affairs reliable transmission on IP network.
Background technology
In next generation network and in the soft switch networking architecture, Media Gateway Controller (MGC) is controlled media gateway (MG) by MGCP (H.248).H.248 agreement is a kind of principal and subordinate's agreement, based on Media Gateway Controller, media gateway be from, Media Gateway Controller is responsible for the call state relevant with media gateway controlled, media gateway is finished the conversion of media formats between the heterogeneous networks under the control of Media Gateway Controller, if the message that Media Gateway Controller sends can not obtain timely response, may cause repeating sending, will cause can't predicting to the state after the media gateway fill order.
H.248 the protocol message of protocol definition can be gone up transmission in User Datagram Protoco (UDP) (UDP) or transmission control protocol (TCP), when on UDP, transmitting, information drop-out may take place, when on TCP, transmitting, although TCP provides reliable transmission mechanism, but because TCP is a kind of agreement based on stream, for H.248 agreement towards affairs (Transaction), request transaction in the message (Transaction Request) with reply affairs (TransactionReply) and still might lose, so H.248 agreement has been stipulated the requirement transmitted on IP, guarantee the reliable transmission of affairs (Transaction).
At present, H.248 agreement has stipulated that transmission requirement is followed following mechanism on IP:
(1) " once machine-processed at the most "
Require protocol entity in internal memory, to keep two tabulations, one is used for writing down and executes the Transaction Reply that returns behind the Transaction Request that is received recently, another is used for writing down the current Transaction Request that needs processing, when receiving a Transaction Request message, the transaction number (Transaction ID) that receives affairs is compared with the transaction number (Transaction ID) of the Transaction Reply that sends recently, if it is identical, then do not carry out the request transaction Transaction Request that receives, only repeat to send Transaction Reply response message, as inequality, then will receive affairs Transaction ID compares with the Transaction Request tabulation that needs to handle, if in tabulation, find the identical affairs of Transaction ID, then show this TransactionRequest attach most importance to the recurrence give, needn't carry out.
(2) retransmission mechanism
The protocol entity that sends Transaction Request should be all Transaction and specifies a retransmission timer, when timer expiry does not receive response yet, then should repeat to send this Transaction, when the Transaction that repeats repeatedly to send did not meet with a response yet, the entity that sends request should be taked alternative service or remove the existing connection that connects or be about to set up.
(3) three-way handshake mechanism
In the Transaction implementation, some Transaction carries out may need the long time, thereby may cause Transaction to carry out with retransmission mechanism clashes, the re-transmission repeatedly that time of implementation is oversize may to cause Transaction repeatedly perhaps causes retransmission timer numerical value excessive and reduce the efficient of transmission.Need the long time of implementation if protocol entity is predicted a certain Transaction, then can send a Temporary Response message (Transaction Pending) indication Transaction earlier and handle; Receive the TransactionRequest message of repetition when protocol entity, if this Transaction handles, also should send TransactionPending message, the entity that receives Transaction Pending message should be different numerical value of retransmission timer setting of the Transaction Request message of this message correspondence; If receive final Transaction Reply message, then should send an acknowledge message to the opposite end entity immediately, after this, should use common timer.For same TransactionRequest, entity should be ignored the Transaction Pending message of reception after receiving final Transaction Reply.
(4) other
Long timer (LONG-TIMER):
The time that LONG-TIMER sets should be greater than the maximum duration of a Transaction, and this time also should consider the maximum numbers of repetition of Transaction, repeat the maximum of timer and be grouped in maximum transmitted time delay in the network.After protocol entity sent response message, the Transaction ID that protocol entity should be response transactions preserved a backup, and the holding time is the time that LONG-TIMER sets.If LONG-TIMER is overtime, perhaps received the response acknowledgement message that comprises " Response Acknowledgement Parameter " parameter from peer-entities, this parameter has been carried one group of " the Transaction ID scope that has been identified " parameter, then protocol entity will detect Transaction Reply tabulation, abandon those Transaction ID and be included in the interior Transaction Reply of above-mentioned scope.
The mechanism of the realization Transaction reliable transmission of above agreement regulation is complicated, and the test that realizes also is difficult to control.
Summary of the invention
Technical problem to be solved by this invention is: the complicated and unmanageable deficiency of test to realizing of mechanism that overcomes existing realization Transaction reliable transmission, provide a kind of logical relation of the Transaction of making reliable transmission complexity to become simply clear, be convenient to the method that realizes and test.
The present invention solves the problems of the technologies described above the technical scheme that is adopted to be:
This method of utilizing state machine mechanism to realize the affairs reliable transmission, it is characterized in that: with request transaction (Transaction Request) be saved in request (Request) formation of protocol entity to the transmission of opposite end entity, the affairs (Transaction Reply) of replying that will be responded the request transaction (TransactionRequest) that receives from the opposite end entity are saved in and reply (Response) formation, affairs (Transaction) in two formations are finished corresponding operation and state variation according to the incident that triggers state variation respectively, thereby utilize state machine mechanism to realize reliable transmission to affairs (Transaction).
In the described request queue, the state of affairs comprises:
State a: request transaction is sent to the opposite end entity for the first time;
State b: the request transaction that sends to the opposite end entity is not received response in timing, the retransmitted one or many of this request transaction;
State c: after sending request transaction, receive the Temporary Response (Transaction Pending) of opposite end entity to this request transaction to the opposite end entity.
The incident that transaction status changes in the described trigger request formation comprises:
Incident a: receive response to request transaction from the opposite end entity;
Incident b: receive Temporary Response to request transaction from the opposite end entity;
Incident c: the retransmission timer of request transaction is overtime;
Incident d: request transaction has reached maximum retransmission.
In the described request queue, the state of affairs and the operation of incident are changed to:
When receiving incident a, when current state is state a: affairs are abandoned from request queue;
When receiving incident a, when current state is state b: affairs are abandoned from request queue;
When receiving incident a, when current state is state c: affairs are abandoned from request queue, send an acknowledge message to the opposite end entity;
When receiving incident b, when current state was state a: the value of the retransmission timer of affairs was set to Temporary Response timer value, number of retransmissions zero setting, and the state of affairs is adjourned to state c;
When receiving incident b, when current state was state b: the value of the retransmission timer of affairs was set to Temporary Response timer value, number of retransmissions zero setting, and the state of affairs is adjourned to state c;
When receiving incident b, when current state is state c: inoperation;
When receiving incident c, when current state was state a: resend once these affairs, number of retransmissions increased, and the state of affairs is adjourned to state b;
When receiving incident c, when current state was state b: resend once these affairs, number of retransmissions increased;
When receiving incident c, when current state was state c: resend once these affairs, number of retransmissions increased, and the retransmission timer of affairs is reset, and the state of affairs is adjourned to state b;
When receiving incident d, current state can not be state a;
When receiving incident d, when current state is state b: take alternative service or remove the existing connection that connects or be about to set up;
When receiving incident d, current state can not be state c.
Described replying in the formation, the state of affairs comprises:
State A: the request transaction that receives the opposite end entity for the first time;
State B: the response to the request transaction that receives has sent to the opposite end entity;
State C: receive the opposite end entity to replying the affirmation response (ResponseAcknowledgement) of affairs.
Described triggering is replied the incident that transaction status changes in the formation and is comprised:
Incident A: receive request transaction from the opposite end entity;
Incident B: receive replying the affirmation response of affairs from the opposite end entity;
Incident C: transaction number (Transaction ID) holding time that sends response to the opposite end entity is overtime.
Described replying in the formation, the state of affairs and the operation of incident are changed to:
When receiving incident A, when current state is state A: send a Temporary Response to the opposite end entity, do not carry out this request transaction, Temporary Response is retransmitted to reach and will be replied affairs behind certain number of times and delete from reply formation;
When receiving incident A, when current state is state B: resend and once reply affairs and give the opposite end entity, do not carry out this request transaction;
When receiving incident A, when current state is state C: do not carry out this request transaction;
When receiving incident B, when current state is state A: inoperation;
When receiving incident B, when current state was state B: will reply affairs and delete from reply formation, and only preserve transaction number, the state of affairs was adjourned to state C;
When receiving incident B, when current state is state C: inoperation;
When receiving incident C, current state can not be state A;
When receiving incident C, when current state is state B: will reply affairs and from reply formation, delete, and abandon correspondent transaction number;
When receiving incident C, when current state is state C: abandon correspondent transaction number.
Beneficial effect of the present invention is: the present invention utilizes state machine to realize the reliable transmission of Transaction according to the mechanism of the regulation of agreement H.248, utilize state machine mechanism that formation, state and incident are designed, compare with existing implementation, the logical relation that the present invention makes Transaction reliable transmission complexity becomes simply clear by the design of state and incident, is convenient to realize and test.
Embodiment
According to embodiment the present invention is described in further detail below:
The present invention is based on the H.248 regulation of agreement, adopted state machine to realize the reliable transmission of affairs (Transaction), be described in detail as follows on IP, transmitting:
Protocol entity is saved in a request (Request) formation to the request transaction (Transaction Request) that peer-entities sends, the affairs (Transaction Reply) of replying that will be responded the request transaction (Transaction Request) that receives from peer-entities are saved in one and reply (Response) formation, affairs (Transaction) in two formations are finished corresponding operation and state variation according to the incident that triggers state variation respectively, utilize state machine mechanism to realize reliable transmission to affairs (Transaction).
The state of Transaction in the Request formation is as shown in table 1:
Table 1
| State number | Status Name | State description |
| ????a | ?TS_SENT | Transaction is sent to the opposite end entity for the first time |
| ????b | ?TS_RESENT | The Transaction that sends to the opposite end entity does not receive response in timing, the retransmitted one or many of this Transaction |
| ????c | ?TS_PENDING_RECEI ?VED | After sending Transaction, receive the Temporary Response Transaction Pending of opposite end entity to this Transaction to the opposite end entity |
The condition that Transaction enters the Request formation is for the first time after the opposite end entity sends, and initial condition is state a.
The institute that triggers above state variation might incident comprise:
Table 2
| Event number | The incident title | Event description |
| ????a | ?TE_RESPONSE_INCOMING | Receive response from the opposite end entity to Transaction |
| ????b | ?TE_PENDING_ICOMING | Receive Temporary Response from the opposite end entity to Transaction |
| ????c | ?TE_RESEND_TIMEOUT | The retransmission timer of Transaction is overtime |
| ????d | ?TE_MAX_RETRY_ACHIEVED | Transaction has reached maximum retransmission |
Transaction in the current Request formation is as shown in table 3 according to the corresponding operating and the state variation situation of trigger event:
Table 3
| The incident that receives | Current state | Operation and state variation |
| TE_RESPONSE_I ????NCOMING | TS_SENT | Transaction is abandoned from the Request formation |
| TS_RESENT | Transaction is abandoned from the Request formation | |
| TS_PENDING_RE CEIVED | Transaction is abandoned from the Request formation to acknowledge message of opposite end entity transmission |
| TE_PENDING_IN ????COMING | ?TS_SENT | The value of the retransmission timer of Transaction is set to the state of Temporary Response timer value number of retransmissions zero setting Transaction and adjourns to TS_PENDING_RECEIVED |
| ?TS_RESENT | The value of the retransmission timer of Transaction is set to the state of Temporary Response timer value number of retransmissions zero setting Transaction and adjourns to TS_PENDING_RECEIVED | |
| ?TS_PENDING_RE ?CEIVED | Inoperation | |
| TE_RESEND_TI ????MEOUT | ?TS_SENT | The state that resends once this Transaction number of retransmissions increase Transaction is adjourned to TS_RESENT |
| ?TS_RESENT | Resending once this Transaction number of retransmissions increases | |
| ?TS_PENDING_RE ?CEIVED | Resending once this Transaction number of retransmissions increases the state that the retransmission timer of Tramsaction is reset Tramsaction and adjourns to TS_RESENT | |
| ?TE_MAX_RETRY ????ACHIEVED | ?TS_SENT | Can not take place |
| ?TS_RESENT | Take alternative service or remove the existing connection that connects or be about to set up | |
| ?TS_PENDING_RE ?CEIVED | Can not take place |
The state of Transaction in the Response formation is as shown in table 4:
Table 4
| State number | Status Name | State description |
| ????A | ?RS_REQUEST_RECEIVED | Receive for the first time the Transaction Request of opposite end entity |
| ????B | ?RS_SENT | Response Transaction Reply to the Transaction Request that receives has sent to the opposite end entity |
| ????C | ?RS_RESPONSE_ACK_RECEIV ?ED | Receive the affirmation response Response Acknowledgement of opposite end entity to Transaction Reply |
The condition that Transaction enters the Response formation is the Transaction Request that receives the opposite end entity for the first time, initial condition is state A, in case responded TransactionReply, that preserve in the Response formation is Transaction Reply, state is adjourned to state B, and starts long timer LONG_TIMER.
The possible incident of institute that triggers above state variation is as shown in table 5, comprising:
Table 5
| Event number | The incident title | Event description |
| ????A | ?RE_REQUEST_INCOMING | Receive Transaction Request from the opposite end entity |
| ????B | ?RE_RESPONSE_ACK_INCO ?MING | The affirmation that receives Transaction Reply from the opposite end entity responds Response Acknowledgement |
| ????C | ?RE_LONG_TIMEOUT | The Transaction ID holding time that sends response to the opposite end entity is overtime |
Transaction in the current Response formation is as shown in table 6 according to the corresponding operating and the state variation situation of trigger event:
Table 6
| The incident that receives | Current state | Operation and state variation |
| RE_EQUEST_IN ????COMING | ?RS_REQUEST_EC ?EIVED | Send a Transaction Pending Temporary Response and do not carry out this Transaction Request to opposite end entity (Transaction Pending deletes Transaction Reply after retransmitting and reaching certain number of times from the Response formation) |
| ?RS_SENT | Resending a Transaction Reply does not carry out this Transaction Request for the opposite end entity | |
| ?RS_RESPONSE_AC ?K_RECEIVED | Do not carry out this Transaction Request | |
| ?RE_RESPONSE ?ACK_INCOMING | ?RS_REQUEST_REC ?EIVED | Inoperation |
| ?RS_SENT | Transaction Reply is deleted from the Response formation, only preserve the state of Transaction ID Transaction and adjourn to RS_RESPONSE_ACK_RECEIVED | |
| ?RS_RESPONSE_AC ?K_RECEIVED | Inoperation | |
| RE_LONG_TIME ????OUT | ?RS_REQUEST_REC ?EIVED | Can not take place |
| ?RS_SENT | Transaction Reply deleted from the Response formation abandon corresponding Transaction ID | |
| ?RS_RESPONSE_AC ?K_RECEIVED | Abandon corresponding Transaction ID |
Such scheme of the present invention utilizes state machine mechanism that formation, state and event are designed, and compares with existing implementation, makes the logical relation of affairs Transaction transmitting complexity become simply clear, is convenient to realize and test.
Claims (7)
1. one kind is utilized the machine-processed method that realizes the affairs reliable transmission of state machine, it is characterized in that: with request transaction (Transaction Request) be saved in request (Request) formation of protocol entity to the transmission of opposite end entity, the affairs (Transaction Reply) of replying that will be responded the request transaction (Transaction Request) that receives from the opposite end entity are saved in and reply (Response) formation, affairs (Transaction) in two formations are finished corresponding operation and state variation according to the incident that triggers state variation respectively, thereby utilize state machine mechanism to realize reliable transmission to affairs (Transaction).
2. the method for utilizing state machine mechanism to realize the affairs reliable transmission according to claim 1, it is characterized in that: in the described request queue, the state of affairs comprises:
State a: request transaction is sent to the opposite end entity for the first time;
State b: the request transaction that sends to the opposite end entity is not received response in timing, the retransmitted one or many of this request transaction;
State c: after sending request transaction, receive the Temporary Response (Transaction Pending) of opposite end entity to this request transaction to the opposite end entity.
3. the method for utilizing state machine mechanism to realize the affairs reliable transmission according to claim 2,
It is characterized in that: the incident that transaction status changes in the described trigger request formation comprises:
Incident a: receive response to request transaction from the opposite end entity;
Incident b: receive Temporary Response to request transaction from the opposite end entity;
Incident c: the retransmission timer of request transaction is overtime;
Incident d: request transaction has reached maximum retransmission.
4. the method for utilizing state machine mechanism to realize the affairs reliable transmission according to claim 3, it is characterized in that: in the described request queue, the state of affairs and the operation of incident are changed to:
When receiving incident a, when current state is state a: affairs are abandoned from request queue;
When receiving incident a, when current state is state b: affairs are abandoned from request queue;
When receiving incident a, when current state is state c: affairs are abandoned from request queue, send an acknowledge message to the opposite end entity;
When receiving incident b, when current state was state a: the value of the retransmission timer of affairs was set to Temporary Response timer value, number of retransmissions zero setting, and the state of affairs is adjourned to state c;
When receiving incident b, when current state was state b: the value of the retransmission timer of affairs was set to Temporary Response timer value, number of retransmissions zero setting, and the state of affairs is adjourned to state c;
When receiving incident b, when current state is state c: inoperation;
When receiving incident c, when current state was state a: resend once these affairs, number of retransmissions increased, and the state of affairs is adjourned to state b;
When receiving incident c, when current state was state b: resend once these affairs, number of retransmissions increased;
When receiving incident c, when current state was state c: resend once these affairs, number of retransmissions increased, and the retransmission timer of affairs is reset, and the state of affairs is adjourned to state b;
When receiving incident d, current state can not be state a;
When receiving incident d, when current state is state b: take alternative service or remove the existing connection that connects or be about to set up;
When receiving incident d, current state can not be state c.
5. according to claim 1,2, the 3 or 4 described methods of utilizing state machine mechanism to realize the affairs reliable transmission, it is characterized in that: described replying in the formation, the state of affairs comprises:
State A: the request transaction that receives the opposite end entity for the first time;
State B: the response to the request transaction that receives has sent to the opposite end entity;
State C: receive the opposite end entity to replying the affirmation response (ResponseAcknowledgement) of affairs.
6. the method for utilizing state machine mechanism to realize the affairs reliable transmission according to claim 5 is characterized in that: described triggering is replied the incident that transaction status changes in the formation and is comprised:
Incident A: receive request transaction from the opposite end entity;
Incident B: receive replying the affirmation response of affairs from the opposite end entity;
Incident C: transaction number (Transaction ID) holding time that sends response to the opposite end entity is overtime.
7. the method for utilizing state machine mechanism to realize the affairs reliable transmission according to claim 6 is characterized in that: described replying in the formation, and the state of affairs and the operation of incident are changed to:
When receiving incident A, when current state is state A: send a Temporary Response to the opposite end entity, do not carry out this request transaction, Temporary Response is retransmitted to reach and will be replied affairs behind certain number of times and delete from reply formation;
When receiving incident A, when current state is state B: resend and once reply affairs and give the opposite end entity, do not carry out this request transaction;
When receiving incident A, when current state is state C: do not carry out this request transaction;
When receiving incident B, when current state is state A: inoperation;
When receiving incident B, when current state was state B: will reply affairs and delete from reply formation, and only preserve transaction number, the state of affairs was adjourned to state C;
When receiving incident B, when current state is state C: inoperation;
When receiving incident C, current state can not be state A;
When receiving incident C, when current state is state B: will reply affairs and from reply formation, delete, and abandon correspondent transaction number;
When receiving incident C, when current state is state C: abandon correspondent transaction number.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB021483671A CN100417154C (en) | 2002-11-11 | 2002-11-11 | Method for realizing reliable transfering transaction by using mechanism of state machine |
| PCT/CN2003/000788 WO2004045146A1 (en) | 2002-11-11 | 2003-09-17 | A method for realize the reliable transmission of transaction mechanism of state machine |
| AU2003271019A AU2003271019A1 (en) | 2002-11-11 | 2003-09-17 | A method for realize the reliable transmission of transaction mechanism of state machine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB021483671A CN100417154C (en) | 2002-11-11 | 2002-11-11 | Method for realizing reliable transfering transaction by using mechanism of state machine |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1499802A true CN1499802A (en) | 2004-05-26 |
| CN100417154C CN100417154C (en) | 2008-09-03 |
Family
ID=32304066
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB021483671A Expired - Fee Related CN100417154C (en) | 2002-11-11 | 2002-11-11 | Method for realizing reliable transfering transaction by using mechanism of state machine |
Country Status (3)
| Country | Link |
|---|---|
| CN (1) | CN100417154C (en) |
| AU (1) | AU2003271019A1 (en) |
| WO (1) | WO2004045146A1 (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006111091A1 (en) * | 2005-04-20 | 2006-10-26 | Huawei Technologies Co., Ltd. | A method for implementing media gateway report transaction in a next generation network |
| CN100347993C (en) * | 2005-09-27 | 2007-11-07 | 清华大学 | Protocol interoperation characteristic test generating method based on communication multi-port finite state machine |
| CN101179465B (en) * | 2007-12-10 | 2010-12-15 | 中国科学院计算技术研究所 | Wireless network media access control system and service stream dynamic handling method |
| CN101206687B (en) * | 2007-12-18 | 2011-04-06 | 同济大学 | Method for improving dynamic security of distributed dynamoelectric equipment |
| CN1812405B (en) * | 2004-12-10 | 2012-05-23 | 微软公司 | Reliable one-way messaging over request-response transport protocols |
| CN101286862B (en) * | 2007-04-09 | 2012-07-04 | 中兴通讯股份有限公司 | Method for synchronizing and switching multicast service between main and standby in access device |
| CN101447857B (en) * | 2008-05-26 | 2012-07-18 | 中兴通讯股份有限公司 | Method for adjusting time parameter dynamically during message-handling process |
| CN103729259A (en) * | 2012-10-12 | 2014-04-16 | 安凯(广州)微电子技术有限公司 | Verification method and device for AHB read-write burst mutual interruption |
| CN106250250A (en) * | 2016-08-09 | 2016-12-21 | 广州唯品会信息科技有限公司 | Data communications method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5983326A (en) * | 1996-07-01 | 1999-11-09 | Sun Microsystems, Inc. | Multiprocessing system including an enhanced blocking mechanism for read-to-share-transactions in a NUMA mode |
| US5878235A (en) * | 1996-10-03 | 1999-03-02 | Micron Electronics, Inc. | Method and system for concurrent computer transaction processing |
| GT200000127A (en) * | 1999-08-04 | 2002-01-25 | SYSTEM AND METHOD FOR THE FAST AND SECURE ELECTRONIC FUNDS TRANSFER BETWEEN TWO POINTS. | |
| US6405292B1 (en) * | 2000-01-04 | 2002-06-11 | International Business Machines Corp. | Split pending buffer with concurrent access of requests and responses to fully associative and indexed components |
-
2002
- 2002-11-11 CN CNB021483671A patent/CN100417154C/en not_active Expired - Fee Related
-
2003
- 2003-09-17 AU AU2003271019A patent/AU2003271019A1/en not_active Abandoned
- 2003-09-17 WO PCT/CN2003/000788 patent/WO2004045146A1/en not_active Application Discontinuation
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1812405B (en) * | 2004-12-10 | 2012-05-23 | 微软公司 | Reliable one-way messaging over request-response transport protocols |
| WO2006111091A1 (en) * | 2005-04-20 | 2006-10-26 | Huawei Technologies Co., Ltd. | A method for implementing media gateway report transaction in a next generation network |
| US7920582B2 (en) | 2005-04-20 | 2011-04-05 | Huawei Technologies Co., Ltd. | Media gateway for reporting events and method for reporting events by media gateway in a next generation network |
| CN100347993C (en) * | 2005-09-27 | 2007-11-07 | 清华大学 | Protocol interoperation characteristic test generating method based on communication multi-port finite state machine |
| CN101286862B (en) * | 2007-04-09 | 2012-07-04 | 中兴通讯股份有限公司 | Method for synchronizing and switching multicast service between main and standby in access device |
| CN101179465B (en) * | 2007-12-10 | 2010-12-15 | 中国科学院计算技术研究所 | Wireless network media access control system and service stream dynamic handling method |
| CN101206687B (en) * | 2007-12-18 | 2011-04-06 | 同济大学 | Method for improving dynamic security of distributed dynamoelectric equipment |
| CN101447857B (en) * | 2008-05-26 | 2012-07-18 | 中兴通讯股份有限公司 | Method for adjusting time parameter dynamically during message-handling process |
| CN103729259A (en) * | 2012-10-12 | 2014-04-16 | 安凯(广州)微电子技术有限公司 | Verification method and device for AHB read-write burst mutual interruption |
| CN103729259B (en) * | 2012-10-12 | 2017-02-01 | 安凯(广州)微电子技术有限公司 | Verification method and device for AHB read-write burst mutual interruption |
| CN106250250A (en) * | 2016-08-09 | 2016-12-21 | 广州唯品会信息科技有限公司 | Data communications method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| AU2003271019A1 (en) | 2004-06-03 |
| CN100417154C (en) | 2008-09-03 |
| WO2004045146A1 (en) | 2004-05-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1721405B1 (en) | Method for retransmitting packet in mobile communication system and computer-readable medium recorded program thereof | |
| CN1191725C (en) | Method for making data transmission more effective and a data transmission protocol | |
| CN1290286C (en) | Automatic repeat request protocol | |
| JP4981904B2 (en) | Media access control discard notification | |
| TWI330958B (en) | Method of handling packet data in a wireless communications system and related apparatus | |
| CN101030842B (en) | Method and apparatus for rearranging data in mobile telecommunication system | |
| CN1768498A (en) | Avoiding stall conditions and sequence number ambiguity in an automatic repeat request protocol | |
| CN1852076A (en) | Data retransmitting method | |
| CN101068137A (en) | Apparatus and method for operating automatic repeat request in a broadband wireless access communication system | |
| CN101079814A (en) | Method and apparatus for handling packet data in a wireless communications system | |
| CN101047485A (en) | Communication terminal and retransmission control method | |
| CN1700629A (en) | Method for transmitting data in mobile ad hoc network and network apparatus using the same | |
| KR100342122B1 (en) | System and method for medium access control in a wireless data communication | |
| US20060104201A1 (en) | Unit and a method for handling a data object | |
| CN101060386A (en) | Hybrid automatic forward request entity and its data block submission method | |
| CN1951135A (en) | Control station apparatus, base station apparatus, receiving method, transmitting method and communicating method | |
| CN101047481A (en) | Automatic retransmission requiring distribution feedback method in radio communication system | |
| CN101444032A (en) | Retransmission apparatus and method for high-speed data processing | |
| CN1499802A (en) | Method for realizing reliable transfering transaction by using mechanism of state machine | |
| US9306710B2 (en) | RCC connection establishment method and apparatus in communication system background of the invention | |
| CN1977497A (en) | Lossless radio link control entity (RLC) re-establishment avoiding service data unit (SDU) duplication | |
| CN1353510A (en) | Retry control method and device | |
| CN110601799A (en) | Link retransmission method and device based on double sliding windows | |
| CN1298132C (en) | Receiving device, transmitting device, and programs | |
| CN1747568A (en) | Method for base station to transmitting feedback data of multiple clients by sorted combinations |
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 | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080903 Termination date: 20121111 |