CN102025474A - Network data transmission method - Google Patents
Network data transmission method Download PDFInfo
- Publication number
- CN102025474A CN102025474A CN2010106165368A CN201010616536A CN102025474A CN 102025474 A CN102025474 A CN 102025474A CN 2010106165368 A CN2010106165368 A CN 2010106165368A CN 201010616536 A CN201010616536 A CN 201010616536A CN 102025474 A CN102025474 A CN 102025474A
- Authority
- CN
- China
- Prior art keywords
- message
- client
- server end
- data
- acknowledgement message
- 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
Images
Abstract
The invention discloses a network data transmission method in the technical field of network communication. The method comprises a process of establishment and release of connection, a process of data transmission and a process of regular handshake, wherein the process of establishment and release of connection comprises that: a client initiatively transmits an initial message to a server to request establishment of connection; and the server authenticates and saves the connection information and enters a connection establishing state; the process of data transmission comprises that: the client and the server respectively transmit a data message to each other, and if the opposite side receives the data message, the client or the server continuously transmits the next data message, otherwise, the data message is retransmitted; and the process of regular handshake comprises that: the client and the server respectively transmit a heartbeat message to each other through a first network link and a second network link, if the opposite side receives the heartbeat message, the connection is normal; if the opposite side does not receive the heartbeat message, the heartbeat message is retransmitted; and if the first network link and the second network link are failed, the connection is determined to be interrupted. The invention provides a high-reliability high-real-time network data transmission protocol.
Description
Technical field
The invention belongs to network communications technology field, relate in particular to a kind of network data transmission method.
Background technology
At present, the transportation protocol that uses on the IP network mainly contains UDP, TCP and SCTP etc., and its characteristics are as follows respectively:
(1) UDP: there is not connection, message-oriented (transfer mechanism that transport layer uses when the upper strata provides packet delivery service), unreliable transmission postpones less.
(2) TCP: towards connect (confirmation and affirmation mechanism that transport layer uses) when the upper strata provides reliable the transmission, towards stream (transfer mechanism that transport layer uses when the upper strata provides data flow to transmit service), the reliable transmission postpones uncertain.
(3) SCTP: towards connection, message-oriented, the reliable transmission postpones uncertain.
From the transmission characteristics of above-mentioned UDP, TCP and SCTP as can be seen, udp protocol can not provide reliable transfer mechanism, therefore can not be used for the reliable occasion that transmits of requirement.Transmission Control Protocol does not support to transmit the backup of network, therefore can not be used for the occasion that requirement provides high reliability to transmit by network backup.And Stream Control Transmission Protocol is owing to adopt the confirmation mechanism of overtime repeating transmission, and the calculating of time-out time is subjected to the influence of network average retardation, when network delay increased, the repeating transmission time also can correspondingly increase, and therefore can not be used for some to transmitting the occasion that real-time is had relatively high expectations.In addition,, can not switch fast, also can influence the reliability and the real-time of transmission though Stream Control Transmission Protocol is supported link backup.
In sum, provide in real time in some requirement, authentic data transmits, and the occasion of network redundancy is provided, above agreement all can not meet the demands fully.
Summary of the invention
The objective of the invention is to, a kind of network data transmission method that can in real time, reliably also can realize network redundancy is provided.
Technical scheme is that a kind of network data transmission method transmits by udp protocol, it is characterized in that described method comprises establishment of connection and dispose procedure, data transmission procedure and timing handshake procedure;
Described establishment of connection and dispose procedure comprise:
Step 101: client initiatively sends initial message to server end, and request connects;
Step 102: after server end is received initial message, send initial acknowledgement message to client; Initial acknowledgement message comprises the stored information that write down link information and the initial summary of acknowledgement message;
Step 103: server end discharges agreement control resource;
Step 104: after client is received initial acknowledgement message, the summary of stored information and initial acknowledgement message is taken out, by the stored information response message summary of stored information and initial acknowledgement message is sent to server end then;
Step 105: after server end was received the stored information response message, the summary that takes out stored information and initial acknowledgement message authenticated, and preserves link information in authentication by the back, sends the stored information acknowledgement message to client simultaneously, entered to connect the state of setting up;
Step 106: after client is received the stored information acknowledgement message, enter connection and set up state;
Described data transmission procedure comprises:
Step 201: client end/server end sends data-message to server end/client;
Step 202: after server end/client is received data-message, send data acknowledgement message to client end/server end;
Step 203: client end/server end judges whether to receive data acknowledgement message, if receive, then execution in step 204; Otherwise, execution in step 205;
Step 204: send next data-message;
Step 205: whether the quantity of judging retransmission data message is greater than setting window, if then execution in step 206; Otherwise, return step 201, resend data-message, and make the quantity of retransmission data message add 1;
Step 206: judge to connect and interrupt, close connection;
Described timing handshake procedure comprises:
Step 301: after connecting, client end/server end regularly sends heartbeat message to server end/client by first network link/second network link;
Step 302: after server end/client is received heartbeat message, send the heartbeat acknowledgement message to client end/server end by first network link/second network link;
Step 303: judge whether the client and server end receives the heartbeat acknowledgement message in setting-up time, if then execution in step 304; Otherwise execution in step 305;
Step 304: it is normal to judge that the client and server end connects;
Step 305: client end/server end is not received the heartbeat acknowledgement message in setting-up time, and client end/server end is retransmitted heartbeat message;
Step 306: retransmit number of times above behind the set point number when the client end/server end heartbeat message, judge first network link/second network link failure;
Step 307: if first network link and the second network link simultaneous faults judge that then the client and server end connects interruption.
Described initial message adopts retransmission mechanism, stops to retransmit after client is received initial acknowledgement message; After client is retransmitted first set point number, be judged as connection failure, send the connection abort message to server end.
Described initial acknowledgement message adopts retransmission mechanism, stops to retransmit after server end is received the stored information response message; After server end is retransmitted second set point number, be judged as connection failure, send the connection abort message to client.
Described initial message and stored information response message send simultaneously by two links, and initial acknowledgement message and stored information acknowledgement message send on the link that receives initial message and stored information response message.
Described abort message sends on two links simultaneously.
After described server end/client is received data-message, when client end/server end sends data acknowledgement message, if server end/client also sends another data-message to client end/server end, then this data acknowledgement message is joined in described another data-message and send; If server end/client does not send data-message to client end/server end, then directly send data acknowledgement message.
Effect of the present invention is, by adopt towards connections, dual network redundancy, two twoly receive, timing quick repeats technology, a kind of highly reliable, high real-time network data transportation protocol is provided, can have satisfied the requirement of specific transactions high reliability and the transmission of high real-time data.
Description of drawings
Fig. 1 is establishment of connection and dispose procedure schematic diagram;
Fig. 2 is the message instruction card;
Fig. 3 is the state description table;
Fig. 4 is the data transmission procedure schematic diagram.
Embodiment
Below in conjunction with accompanying drawing, preferred embodiment is elaborated.Should be emphasized that following explanation only is exemplary, rather than in order to limit the scope of the invention and to use.
Fig. 1 is establishment of connection and dispose procedure schematic diagram.Among Fig. 1, a kind of network data transmission method provided by the invention transmits by udp protocol, comprises establishment of connection and dispose procedure, data transmission procedure and timing handshake procedure.
Fig. 2 and Fig. 3 are respectively message instruction card and state description table, and in conjunction with Fig. 2 and Fig. 3, establishment of connection and dispose procedure comprise:
Step 101: client initiatively sends initial message INIT to server end, and request connects.
Step 102: after server end is received initial message INIT, send initial acknowledgement message INIT_ACK to client; Initial acknowledgement message INIT_ACK comprises the stored information that write down link information and the initial summary of acknowledgement message INIT_ACK.In network communications technology field, use COOKIE to write down some information usually, so use the stored information of COOKIE in the present embodiment as the record link information.The summary data that the summary of initial acknowledgement message INIT_ACK adopts the MD5 algorithm to generate is used to carry out the message integrity check, prevents mistake or is distorted.
Step 103: server end discharges agreement control resource.
In general, Connection-oriented Protocol (as TCP) all needs to preserve the information such as state with join dependency, be called PCB (protocol control block), the quantity of PCB resource depends on the number of connection that system can handle, and generally is subject to the factor such as disposal ability, internal memory of system.With the Transmission Control Protocol is example, in case receive connection request message, protocol stack will distribute the PCB resource for connecting, and a large amount of connection requests can cause the PCB resource exhaustion of tcp protocol stack in the short time, can't continue to handle normal connection request, promptly so-called " DOS " attacks.Among the present invention, after handling initial message INIT, just discharged the PCB resource.Receive COOKIE_ACK message, and after authentication passes through, rebuilding PCB according to the data of preserving among the COOKIE again, therefore avoiding the situation that " DOS " attacks among the TCP.
Step 104: after client is received initial acknowledgement message INIT_ACK, the summary of stored information COOKIE and initial acknowledgement message INIT_ACK is taken out, by stored information response message COOKIE_ECHO the summary of stored information COOKIE and initial acknowledgement message INIT_ACK is sent to server end then.
Step 105: after server end is received stored information response message COOKIE_ECHO, the summary that takes out stored information COOKIE and initial acknowledgement message INIT_ACK authenticates, and pass through the back in authentication and preserve link information, send stored information acknowledgement message COOKIE_ACK to client simultaneously, enter connection and set up state.
Step 106: after client is received stored information acknowledgement message COOKIE_ACK, enter connection and set up state.
In addition, in the establishment of connection process, initial message INIT adopts retransmission mechanism, stops to retransmit after client is received initial acknowledgement message INIT_ACK; After client is retransmitted first set point number, be judged as connection failure, send connection abort message ABORT to server end.
Initial acknowledgement message INIT_ACK also can adopt retransmission mechanism, stops to retransmit after server end is received stored information response message COOKIE_ECHO; After server end is retransmitted second set point number, be judged as connection failure, send connection abort message ABORT to client.
Initial message INIT of the present invention and stored information response message COOKIE_ECHO send simultaneously by two links, and initial acknowledgement message INIT_ACK and stored information acknowledgement message COOKIE_ACK send on the link that receives initial message INIT and stored information response message COOKIE_ECHO.
Abort message ABORT sends on two links simultaneously.
Fig. 4 is the data transmission procedure schematic diagram, because data transmission procedure comprises user end to server end transmission data, comprise that also server end is to the client transmissions data, and the principle of two kinds of transmission data is the same, so Fig. 4 is with user end to server end transmission data instance explanation data transmission procedure.Its process comprises:
Step 201: the user end to server end sends data-message DATA.Data-message comprises that forward sequence number FSN and back are to sequence number BSN.
Step 202: after server end is received data-message DATA, send data acknowledgement message SACK to client.
Step 203: client judges whether to receive data acknowledgement message SACK, if receive, then execution in step 204; Otherwise, execution in step 205.
Step 204: send next data-message DATA.
Step 205: judge that whether the quantity of retransmitting (RESEND) data-message DATA is greater than setting window, if then execution in step 206; Otherwise, return step 201, resend data-message DATA, and make the quantity of retransmission data message add 1;
Step 206: judge to connect and interrupt, close connection.
In above-mentioned data transmission procedure, adopt incidentally to confirm mechanism or send independent acknowledgement message mechanism.Detailed process is, after above-mentioned server end is received data-message DATA, when client sends data acknowledgement message SACK, if server end also sends another data-message DATA ' to client, then this data acknowledgement message SACK is joined among described another data-message DATA ' and send; If server end does not send other data-messages to client, then directly send data acknowledgement message SACK.
Among the present invention, regularly handshake procedure comprises:
Step 301: after connecting, client regularly sends heartbeat message to server end by first network link; Server end regularly sends heartbeat message to client by second network link.
Step 302: after server end is received heartbeat message, send the heartbeat acknowledgement message to client by first network link; After client is received heartbeat message, send the heartbeat acknowledgement message to server end by second network link.
Step 303: judge whether the client and server end receives the heartbeat acknowledgement message in setting-up time, if then execution in step 304; Otherwise execution in step 305.
Step 304: it is normal to judge that the client and server end connects.
Step 305: if client is not received the heartbeat acknowledgement message in setting-up time, then server end is retransmitted heartbeat message; If server end is not received the heartbeat acknowledgement message in setting-up time, then client is retransmitted heartbeat message.
Step 306: retransmit number of times above behind the set point number when the client heartbeat message, judge first network link failure; Retransmit number of times above behind the set point number when the server end heartbeat message, judge second network link failure.
Step 307: if first network link and the second network link simultaneous faults judge that then the client and server end connects interruption.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.
Claims (6)
1. a network data transmission method transmits by udp protocol, it is characterized in that described method comprises establishment of connection and dispose procedure, data transmission procedure and timing handshake procedure;
Described establishment of connection and dispose procedure comprise:
Step 101: client initiatively sends initial message to server end, and request connects;
Step 102: after server end is received initial message, send initial acknowledgement message to client; Initial acknowledgement message comprises the stored information that write down link information and the initial summary of acknowledgement message;
Step 103: server end discharges agreement control resource;
Step 104: after client is received initial acknowledgement message, the summary of stored information and initial acknowledgement message is taken out, by the stored information response message summary of stored information and initial acknowledgement message is sent to server end then;
Step 105: after server end was received the stored information response message, the summary that takes out stored information and initial acknowledgement message authenticated, and preserves link information in authentication by the back, sends the stored information acknowledgement message to client simultaneously, entered to connect the state of setting up;
Step 106: after client is received the stored information acknowledgement message, enter connection and set up state;
Described data transmission procedure comprises:
Step 201: client end/server end sends data-message to server end/client;
Step 202: after server end/client is received data-message, send data acknowledgement message to client end/server end;
Step 203: client end/server end judges whether to receive data acknowledgement message, if receive, then execution in step 204; Otherwise, execution in step 205;
Step 204: send next data-message;
Step 205: whether the quantity of judging retransmission data message is greater than setting window, if then execution in step 206; Otherwise, return step 201, resend data-message, and make the quantity of retransmission data message add 1;
Step 206: judge to connect and interrupt, close connection;
Described timing handshake procedure comprises:
Step 301: after connecting, client end/server end regularly sends heartbeat message to server end/client by first network link/second network link;
Step 302: after server end/client is received heartbeat message, send the heartbeat acknowledgement message to client end/server end by first network link/second network link;
Step 303: judge whether the client and server end receives the heartbeat acknowledgement message in setting-up time, if then execution in step 304; Otherwise execution in step 305;
Step 304: it is normal to judge that the client and server end connects;
Step 305: client end/server end is not received the heartbeat acknowledgement message in setting-up time, and client end/server end is retransmitted heartbeat message;
Step 306: retransmit number of times above behind the set point number when the client end/server end heartbeat message, judge first network link/second network link failure;
Step 307: if first network link and the second network link simultaneous faults judge that then the client and server end connects interruption.
2. a kind of network data transmission method according to claim 1 is characterized in that described initial message adopts retransmission mechanism, stops to retransmit after client is received initial acknowledgement message; After client is retransmitted first set point number, be judged as connection failure, send the connection abort message to server end.
3. a kind of network data transmission method according to claim 1 is characterized in that described initial acknowledgement message adopts retransmission mechanism, stops to retransmit after server end is received the stored information response message; After server end is retransmitted second set point number, be judged as connection failure, send the connection abort message to client.
4. a kind of network data transmission method according to claim 1, it is characterized in that described initial message and stored information response message send simultaneously by two links, initial acknowledgement message and stored information acknowledgement message send on the link that receives initial message and stored information response message.
5. according to claim 2 or 3 described a kind of network data transmission methods, it is characterized in that described abort message sends simultaneously on two links.
6. a kind of network data transmission method according to claim 1, after it is characterized in that described server end/client is received data-message, when client end/server end sends data acknowledgement message, if server end/client also sends another data-message to client end/server end, then this data acknowledgement message is joined in described another data-message and send; If server end/client does not send data-message to client end/server end, then directly send data acknowledgement message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201010616536 CN102025474B (en) | 2010-12-30 | 2010-12-30 | Network data transmission method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201010616536 CN102025474B (en) | 2010-12-30 | 2010-12-30 | Network data transmission method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102025474A true CN102025474A (en) | 2011-04-20 |
| CN102025474B CN102025474B (en) | 2013-04-03 |
Family
ID=43866383
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201010616536 Expired - Fee Related CN102025474B (en) | 2010-12-30 | 2010-12-30 | Network data transmission method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102025474B (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102255898A (en) * | 2011-07-05 | 2011-11-23 | 上海悠络客电子科技有限公司 | Method for ensuring stability of large data stream by tcp (Transmission Control Protocol)/udp (User Datagram Protocol) double-mode communication |
| CN102413503A (en) * | 2011-12-27 | 2012-04-11 | 上海海事大学 | Method for adaptively determining packet delayed sending for Semi-TCP (transmission control protocol) |
| CN103036904A (en) * | 2012-12-27 | 2013-04-10 | 东方通信股份有限公司 | Method of data reliable transmission with user datagram protocol (UDP) in communication network |
| CN103901823A (en) * | 2012-12-25 | 2014-07-02 | 联合汽车电子有限公司 | Vehicle-mounted remote terminal |
| CN105306494A (en) * | 2015-11-26 | 2016-02-03 | 上海斐讯数据通信技术有限公司 | Server and method for preventing DOS attacks |
| CN106534331A (en) * | 2016-11-30 | 2017-03-22 | 网宿科技股份有限公司 | Data transmission method and system based on dynamic port switching |
| CN106789696A (en) * | 2016-11-30 | 2017-05-31 | 卡斯柯信号有限公司 | The reliable redundant network transmission method of not face connection based on congestion control |
| CN107071046A (en) * | 2017-05-10 | 2017-08-18 | 武汉票据交易中心有限公司 | The processing method and system of a kind of network interruption |
| CN108134715A (en) * | 2017-12-25 | 2018-06-08 | 浪潮金融信息技术有限公司 | Communication terminal calls processing method based on SCP agreements |
| CN108389241A (en) * | 2018-03-01 | 2018-08-10 | 网易（杭州）网络有限公司 | The methods, devices and systems of textures are generated in scene of game |
| CN109088799A (en) * | 2018-09-28 | 2018-12-25 | 腾讯科技（深圳）有限公司 | A kind of user end inserting method, device, terminal and storage medium |
| CN111193758A (en) * | 2018-11-15 | 2020-05-22 | 西安诺瓦星云科技股份有限公司 | Display management system and maintenance method thereof |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6317831B1 (en) * | 1998-09-21 | 2001-11-13 | Openwave Systems Inc. | Method and apparatus for establishing a secure connection over a one-way data path |
| CN1545294A (en) * | 2003-11-19 | 2004-11-10 | 北京邮电大学 | A realtime data transmission control method for media flow transmission and network measurement |
-
2010
- 2010-12-30 CN CN 201010616536 patent/CN102025474B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6317831B1 (en) * | 1998-09-21 | 2001-11-13 | Openwave Systems Inc. | Method and apparatus for establishing a secure connection over a one-way data path |
| CN1545294A (en) * | 2003-11-19 | 2004-11-10 | 北京邮电大学 | A realtime data transmission control method for media flow transmission and network measurement |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102255898A (en) * | 2011-07-05 | 2011-11-23 | 上海悠络客电子科技有限公司 | Method for ensuring stability of large data stream by tcp (Transmission Control Protocol)/udp (User Datagram Protocol) double-mode communication |
| CN102413503A (en) * | 2011-12-27 | 2012-04-11 | 上海海事大学 | Method for adaptively determining packet delayed sending for Semi-TCP (transmission control protocol) |
| CN102413503B (en) * | 2011-12-27 | 2014-06-25 | 上海海事大学 | Method for adaptively determining packet delayed sending for Semi-TCP (transmission control protocol) |
| CN103901823A (en) * | 2012-12-25 | 2014-07-02 | 联合汽车电子有限公司 | Vehicle-mounted remote terminal |
| CN103036904A (en) * | 2012-12-27 | 2013-04-10 | 东方通信股份有限公司 | Method of data reliable transmission with user datagram protocol (UDP) in communication network |
| CN105306494A (en) * | 2015-11-26 | 2016-02-03 | 上海斐讯数据通信技术有限公司 | Server and method for preventing DOS attacks |
| CN106534331A (en) * | 2016-11-30 | 2017-03-22 | 网宿科技股份有限公司 | Data transmission method and system based on dynamic port switching |
| CN106789696A (en) * | 2016-11-30 | 2017-05-31 | 卡斯柯信号有限公司 | The reliable redundant network transmission method of not face connection based on congestion control |
| CN106534331B (en) * | 2016-11-30 | 2019-10-11 | 网宿科技股份有限公司 | A kind of data transmission method and system based on dynamic port switching |
| CN107071046A (en) * | 2017-05-10 | 2017-08-18 | 武汉票据交易中心有限公司 | The processing method and system of a kind of network interruption |
| CN108134715A (en) * | 2017-12-25 | 2018-06-08 | 浪潮金融信息技术有限公司 | Communication terminal calls processing method based on SCP agreements |
| CN108389241A (en) * | 2018-03-01 | 2018-08-10 | 网易（杭州）网络有限公司 | The methods, devices and systems of textures are generated in scene of game |
| CN109088799A (en) * | 2018-09-28 | 2018-12-25 | 腾讯科技（深圳）有限公司 | A kind of user end inserting method, device, terminal and storage medium |
| CN109088799B (en) * | 2018-09-28 | 2021-09-14 | 腾讯科技（深圳）有限公司 | Client access method, device, terminal and storage medium |
| CN111193758A (en) * | 2018-11-15 | 2020-05-22 | 西安诺瓦星云科技股份有限公司 | Display management system and maintenance method thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102025474B (en) | 2013-04-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102025474B (en) | Network data transmission method | |
| CN103036904B (en) | A kind of udp protocol that uses in a communication network carries out the method for reliable data transmission | |
| CN102368700B (en) | Transmission method of massages in distributed system | |
| KR101159363B1 (en) | Reliable request-response messaging over a request-response transport | |
| US8612617B2 (en) | Reliable multicast transport protocol | |
| EP1909468B1 (en) | Method and apparatus for backing up TCP connection | |
| CN105657646A (en) | Bluetooth 4.0 based device-to-device big data communication method | |
| CN107257270A (en) | Data transmission method and system based on hybrid automatic repeat-request | |
| US8976814B2 (en) | Method of transporting data from sending node to destination node | |
| CN104618007B (en) | A kind of synchronous satellite Transmission Control Protocol segmentation connection optimization method | |
| JP2011518486A (en) | Method for enabling faster recovery of client applications in case of server failure | |
| CN110011967A (en) | A kind of method and system for data transmission | |
| CN105262746A (en) | Method for guaranteeing reliable data transmission on the basis of UDP protocol | |
| CN102111250A (en) | Method for data transmission and network-side equipment | |
| WO2014194493A1 (en) | Method, device and system for reducing confirmation packets at transmission control layer | |
| WO2013123857A1 (en) | File transmission method, instant messaging terminal and system, and computer storage medium | |
| US9510242B2 (en) | Reducing superfluous traffic in a network | |
| KR101953552B1 (en) | Apparatus for one-way transmission, apparatus for one-way reception, and one-way retransmission method for using same | |
| CN103607311A (en) | System and method for reestablishing TCP connection seamlessly | |
| JP2009212796A (en) | Transmitter, data transfer system, data transfer method, and data transfer program | |
| WO2015096089A1 (en) | Fault-tolerance method and device for phich channel transmission information | |
| CN111464514A (en) | TCP hot backup method and system | |
| CN112187408B (en) | Data processing method, system, device, storage medium and processor | |
| JP5665675B2 (en) | Method for operating remote procedure call handler in client and server, and computer system including the client and server | |
| KR20100026721A (en) | Apparatus and method for providing network interface information in stream control transmission protocol |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130403 Termination date: 20201230 |