WO2004045146A1 - Procede de realisation d'une transmission fiable d'un mecanisme de transaction d'un automate fini - Google Patents
Procede de realisation d'une transmission fiable d'un mecanisme de transaction d'un automate fini Download PDFInfo
- Publication number
- WO2004045146A1 WO2004045146A1 PCT/CN2003/000788 CN0300788W WO2004045146A1 WO 2004045146 A1 WO2004045146 A1 WO 2004045146A1 CN 0300788 W CN0300788 W CN 0300788W WO 2004045146 A1 WO2004045146 A1 WO 2004045146A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- transaction
- state
- event
- received
- response
- Prior art date
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
Definitions
- the present invention relates to the field of communication technologies, and in particular, to a method for achieving reliable transmission of transactions on an IP network.
- the MCC controls the media gateway (MG) through the media gateway control protocol (H.248).
- the H. 248 protocol is a master-slave protocol, which is mainly based on the media gateway controller, the media gateway is the slave, and the media.
- the gateway controller is responsible for controlling the call status related to the media gateway, and the media gateway controls the media gateway controller. After completing the conversion of the media format between different networks, if the message sent by the media gateway controller does not get a timely response, it may result in repeated sending, which will cause the state of the media gateway to execute the command unpredictable.
- the protocol messages defined by the H.248 protocol can be transmitted over User Datagram Protocol (UDP) or Transmission Control Protocol (TCP).
- UDP User Datagram Protocol
- TCP Transmission Control Protocol
- message loss may occur.
- TCP Although TCP Provides a reliable transmission mechanism, but because TCP is a stream-based protocol, for the transaction-oriented H.248 protocol, the transaction request and response transactions in the message
- the H.248 protocol specifies that the following mechanisms are required for transmission over IP:
- the protocol entity is required to keep two lists in memory, one is used to record the Transaction Reply returned after the most recently received Transaction Reques t is executed, and the other is used to record the Transaction Request that currently needs to be processed.
- a Transaction Request message is received Comparing the transaction number (Transaction ID) of the received transaction with the transaction number (Transaction ID) of the most recently issued Transaction Reply. If they are the same, the received request transaction is not executed, and the Transact ion Reply response message is sent repeatedly. If they are not the same, compare the Transaction ID of the received transaction with the Transaction Request table to be processed. If a transaction with the same Transaction ID is found in the list, it indicates that the Transaction Request is sent repeatedly and does not need to be executed.
- the protocol entity that issued the Transaction Request should specify a retransmission timer for all transactions. When the timer expires and no response is received, the transaction should be sent repeatedly. When the transaction that has been sent multiple times has not received a response, the request is sent.
- the entity should adopt alternative services or tear down existing or upcoming connections.
- Transact ion some Transaction execution may take a long time, which may cause the Transaction execution to conflict with the retransmission mechanism. If the execution time is too long, it may cause the transaction to be retransmitted multiple times or the retransmission timer. The value is too large to reduce the transmission efficiency. If the protocol entity foresees that a transaction requires a longer execution time, it may first send a temporary response message (Transaction Pending) indicates that the Transaction is being processed. When the protocol entity receives a duplicate Transaction Request message, if the Transaction is being processed, it should also send a Transaction Pending message.
- Transaction Pending temporary response message
- the entity receiving the Transaction Pendin message should be the The retransmission timer is set to a different value; if the final Transaction Reply message is received, an acknowledgement message should be sent immediately to the peer entity, after which the usual timer should be used. For the same Transaction Request, after receiving the final Transaction Reply, the entity shall ignore the received Transaction Pending message.
- the time set by LONG-TIMER should be greater than the maximum duration of a transaction. This time should also take into account the maximum number of transaction repetitions, the maximum value of the repetition timer, and the maximum transmission delay of the packet in the network.
- the protocol entity When the protocol entity sends a response message, the protocol entity should save a backup for the transaction ID of the response transaction, and the save time is the time set by LONG-TIMER. If the LONG-TIMER times out, or has received a response confirmation message from the peer entity containing the "Response Acknowledgement Parameter" parameter, which carries a set of "Confirmed Transact ion ID range" parameters, the protocol entity will detect the Transaction Reply list, discard those Transaction Reply whose transaction ID is in the above range.
- the technical problem to be solved by the present invention is to overcome the disadvantages of the complicated mechanism of realizing reliable transmission of transactions and the difficulty in controlling the implementation of the test, and to provide a simple and clear logical relationship that makes the reliable transmission of transactions complex and easy to implement and test. Methods.
- This method for realizing reliable transmission of transactions by using a state machine mechanism is characterized in that: a request transaction (Transaction Request) sent by a protocol entity to a counterpart entity is stored in a request queue, and a request received from the counterpart entity is stored The transaction (Transaction Reply) responded by the transaction (Transaction Request) is saved to the Response queue, and the transactions in the two queues respectively complete the corresponding operations and state changes according to the event that triggers the state change, thereby using the state Mechanism for reliable transmission of transactions.
- the status of the transaction includes:
- State b The request transaction sent to the peer entity did not receive a response within the time period, and the request transaction was resent one or more times;
- the event that triggers a transaction status change in the request queue includes:
- Event a received a response to the request transaction from the peer entity
- Event b received a temporary response to the request transaction from the peer entity;
- Event C the retransmission timer of the requested transaction expires;
- Event d The request transaction has reached the maximum number of retransmissions.
- the operation state and event change of the transaction are: when event a is received and the current state is state a: the transaction is discarded from the request queue; when event a is received, the current state is state b : Discard the transaction from the request queue; when event a is received and the current state is state c: discard the transaction from the request queue and send a confirmation message to the peer entity;
- the status of the transaction in the response queue includes:
- State A The request transaction of the peer entity is received for the first time
- State B the response to the received request transaction has been sent to the peer entity
- state C the acknowledgement response from the peer entity to the response transaction
- the event that triggers a transaction status change in the response queue includes:
- Event A A request transaction was received from the peer entity
- Event B Acknowledgment response from the correspondent entity to the response transaction
- Event C The transaction ID (Transact ion ID) of the response sent to the peer entity is overtime.
- the change of the status of the transaction and the operation of the event is: when event A is received and the current status is state A: a temporary response is sent to the peer entity, the request transaction is not executed, and the temporary response is resent to Delete the response transaction from the response queue after a certain number of times;
- the present invention uses the state machine to implement reliable transmission of transactions according to the mechanism specified in the H.248 protocol, and uses the state machine mechanism to design queues, states, and events.
- the invention makes the transaction reliably transmit complex logical relationships through the design of states and events to become simple and clear, which is easy to implement and test. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be further described in detail according to the embodiments below.
- the present invention uses the state machine to implement reliable transmission of transactions based on the H.248 protocol's provisions on transmission over IP.
- the detailed description is as follows:
- the request transaction (Transaction Request) sent by the entity to the peer entity is saved to a Request queue, and the response transaction (Transaction Reply) in response to the request transaction (Transaction Request) received from the peer entity is saved to a response (Response) queues, and the transactions in the two queues respectively complete the corresponding operations and state changes according to the events that trigger state changes, and use the state machine mechanism to achieve reliable transmission of transactions.
- Table 1 Status number Status name Status description a TS-SENT Transaction is sent to the peer entity for the first time
- the transaction sent by the TS-RESENT to the peer entity did not receive a response within the time b, and the transaction was resent one or more times.
- TS_PENDING—RECEI receives c VED after sending a transaction to the peer entity to the peer entity's temporary response to the transaction Transaction Pending
- the condition for a Transaction to enter the Request queue is that after it is first sent to the peer entity, the initial state is state a. All possible events that trigger the above state changes include: Table 2 Event number Event name Event description
- TS— PENDING— REC discards the transaction from the request P person ⁇ 'J EIVED and sends a confirmation message to the peer entity
- TS-SENT sets the value of the retransmission timer of the transaction to the value of the temporary response timer
- Transaction's status moves to TS-PENDING— RECEIVED TS-RESENT sets the value of the transaction retransmission timer to the value of the temporary response timer and the number of retransmissions is set to zero
- TS— RESENT takes alternative services or tears down existing connections or
- the condition for the Transact ion to enter the Response queue is that the Transact ion Reques t of the peer entity is received for the first time, and the initial state is State A. Once the Transact ion Reply is responded, the response team ⁇ 'J holds the Transact ion Reply, and the state transitions Go to state B and start the long timer LONG_TIMER. All possible events that trigger the above state changes are shown in Table 5, including:
- the state machine mechanism is used to design the queue, state, and event. Compared with the existing implementation manner, the transaction transact ion reliably transfers complex logical relationships into a single, clear, and easy to implement and test.
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
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 (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB021483671A CN100417154C (zh) | 2002-11-11 | 2002-11-11 | 一种利用状态机机制实现事务可靠传输的方法 |
CN02148367.1 | 2002-11-11 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004045146A1 true WO2004045146A1 (fr) | 2004-05-27 |
Family
ID=32304066
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2003/000788 WO2004045146A1 (fr) | 2002-11-11 | 2003-09-17 | Procede de realisation d'une transmission fiable d'un mecanisme de transaction d'un automate fini |
Country Status (3)
Country | Link |
---|---|
CN (1) | CN100417154C (zh) |
AU (1) | AU2003271019A1 (zh) |
WO (1) | WO2004045146A1 (zh) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7349384B2 (en) * | 2004-12-10 | 2008-03-25 | Microsoft Corporation | Reliable one-way messaging over request-response transport protocols |
CN1855931B (zh) | 2005-04-20 | 2010-08-04 | 华为技术有限公司 | 下一代网络中媒体网关上报事件处理方法 |
CN100347993C (zh) * | 2005-09-27 | 2007-11-07 | 清华大学 | 基于通讯多端口有限状态机的协议互操作性测试生成方法 |
CN101286862B (zh) * | 2007-04-09 | 2012-07-04 | 中兴通讯股份有限公司 | 接入设备中组播业务主备同步和倒换的方法 |
CN101179465B (zh) * | 2007-12-10 | 2010-12-15 | 中国科学院计算技术研究所 | 一种无线网络媒体接入控制系统及其服务流动态处理方法 |
CN101206687B (zh) * | 2007-12-18 | 2011-04-06 | 同济大学 | 一种提高分布式机电装备的动态安全性的方法 |
CN101447857B (zh) * | 2008-05-26 | 2012-07-18 | 中兴通讯股份有限公司 | 一种消息处理过程中动态调整时间参数的方法 |
CN103729259B (zh) * | 2012-10-12 | 2017-02-01 | 安凯(广州)微电子技术有限公司 | 一种AHB总线读写burst相互打断的验证方法及装置 |
CN106250250A (zh) * | 2016-08-09 | 2016-12-21 | 广州唯品会信息科技有限公司 | 数据通信方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0820016A2 (en) * | 1996-07-01 | 1998-01-21 | Sun Microsystems, Inc. | A 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 |
WO2001011524A1 (en) * | 1999-08-04 | 2001-02-15 | Rapidmoney Corporation | System and method for rapidly and securely transferring funds electronically 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/zh 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/zh not_active Application Discontinuation
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0820016A2 (en) * | 1996-07-01 | 1998-01-21 | Sun Microsystems, Inc. | A 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 |
WO2001011524A1 (en) * | 1999-08-04 | 2001-02-15 | Rapidmoney Corporation | System and method for rapidly and securely transferring funds electronically 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 |
Also Published As
Publication number | Publication date |
---|---|
CN100417154C (zh) | 2008-09-03 |
AU2003271019A1 (en) | 2004-06-03 |
CN1499802A (zh) | 2004-05-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107204834B (zh) | 一种基于udt协议的高速网络可靠传输的控制方法 | |
TWI483589B (zh) | 資料傳輸及重新傳輸之方法 | |
JP4414236B2 (ja) | 通信システムにおいてデータの流れを制御する方法および装置 | |
US7031273B2 (en) | Session initiation protocol retransmission method | |
WO2010069206A1 (zh) | 无线链路控制层报文状态报告的发送方法及系统 | |
TW200926721A (en) | Method and apparatus for enhancing various PDCP and layer 2 operations | |
JP4601871B2 (ja) | 通信システムにおけるデータ流れの制御方法 | |
JP2013146068A (ja) | 通信セッション管理におけるトランザクションタイムアウト処理 | |
WO2008041329A1 (en) | Data transfer method | |
WO2013177841A1 (zh) | Ac与ap之间链路保活的检测方法及装置 | |
WO2011100911A2 (zh) | 探测处理方法、数据发送端、数据接收端以及通信系统 | |
WO2004045146A1 (fr) | Procede de realisation d'une transmission fiable d'un mecanisme de transaction d'un automate fini | |
WO2009127112A1 (zh) | 一种流控制传输协议状态迁移的方法 | |
US20030158959A1 (en) | Establishment of communications using point to point protocols such that duplicate negotiations are avoided | |
US20100115102A1 (en) | Method for improving a tcp data transmission in case the physical transmission medium is disconnected | |
WO2007071133A1 (fr) | Procede de mise en oeuvre d'une fonction de commande de processus de protocole iuup/nbup | |
US9794109B2 (en) | Method of maintaining network address translation mapping and client device employing same | |
CN116112128B (zh) | 发送重传请求的方法及装置、数据接收端设备和存储介质 | |
CN101809970A (zh) | 无线链路控制实体的复位方法 | |
WO2007124634A1 (fr) | Procédé de retransmission de données dans le protocole de commande de liaison radio | |
JP4384676B2 (ja) | データ通信装置の制御方法 | |
WO2010130156A1 (zh) | 在双向数据传输中发送ack响应的方法、设备和系统 | |
JP4364763B2 (ja) | データ通信装置 | |
WO2007014525A1 (fr) | Procede d'etablissement d'une liaison entre le dispositif reseau et le terminal de reseau | |
WO2023155690A1 (zh) | 数据传输方法以及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |