CN115208521B - Communication guarantee and workflow control method for session layer client and server - Google Patents
Communication guarantee and workflow control method for session layer client and server Download PDFInfo
- Publication number
- CN115208521B CN115208521B CN202211002461.3A CN202211002461A CN115208521B CN 115208521 B CN115208521 B CN 115208521B CN 202211002461 A CN202211002461 A CN 202211002461A CN 115208521 B CN115208521 B CN 115208521B
- Authority
- CN
- China
- Prior art keywords
- data packet
- client
- server
- acknowledgement
- combination
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/188—Time-out mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1806—Go-back-N protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1848—Time-out mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
- Communication Control (AREA)
Abstract
The invention discloses a session layer client-server communication guarantee and workflow control method, and belongs to the field of communication. The method comprises the steps of respectively sending a request data packet part, receiving a feedback data packet (and sending a first acknowledgement data packet) part and receiving a second acknowledgement data packet (and sending a completion data packet) part at a client, respectively sending the request data packet (and sending the feedback data packet) part, receiving the first acknowledgement data packet (and sending the second acknowledgement data packet) part and receiving the completion data packet part at a server, and sequentially and alternately executing the 3 parts of the client and the 3 parts of the server to form a complete communication period. The method can truly play the role of guaranteeing communication and managing and controlling workflow under the severe network environment and complex business logic conditions. Even if the communication is interrupted due to the link breakage of the physical layer, the method can ensure that the communication between the client and the server is continued until the communication is completed as long as the network layer can be recovered.
Description
Technical Field
The invention relates to the field of communication between a client and a server, in particular to a session layer client and server communication guarantee and workflow control method.
Background
The layer 4 transport layer of the OSI (Open System Interconnection) reference model has a TCP protocol widely applied to communication between a client and a server, and has characteristics of repairing data packet transmission errors, such as packet loss retransmission, data packet reordering, and the like, and carries most of internet communication. However, in some circumstances the communication security feature of the transport layer is insufficient to meet the actual requirements, which requires that a set of communication security measures be established at the layer 5 session layer of the OSI reference model.
Meanwhile, we note that the communication between the client and the server is always closely related to the bilateral workflow, generally, only when the client initiates a request, the server receives the request and makes feedback, and then the client receives the feedback, the bilateral workflow can be continued, and when strict, the client is required to confirm the receipt of the feedback to the server. Each of the above steps may fail, blindly defaulting to success and continuing the workflow in some scenarios (e.g., internet of vehicles) may have serious consequences.
In the environment of the internet of things or the internet of vehicles, especially under the wireless or outdoor condition, the common Http protocol is even a professional RPC (Remote Procedure Call) framework, such as Apache thread or Google gRPC, once the physical layer has a connection interruption or other hardware problems, the remote process can not be ensured to be excited each time or the return value of the call can not be obtained 100%, and the communication between the client and the server can not be ensured.
Disclosure of Invention
Aiming at the problem that the communication between a client and a server cannot be ensured once the physical layer is interrupted or other hardware problems occur in the Internet of things or the Internet of vehicles in the prior art, particularly under the wireless or outdoor condition, the invention provides a communication ensuring and workflow control method between the client and the server in a session layer.
The invention adopts the following technical scheme:
a communication guarantee and workflow control method for session layer client and server includes the following steps:
step 1: the client acquires the mutual exclusion lock, and after the acquisition is successful, the client transmits a request data packet to the server, and then starts a request retransmission timer, wherein the request retransmission timer retransmits the request data packet once every fixed time interval;
step 2: after receiving a request data packet, the server acquires a mutual exclusion lock corresponding to the client, processes a service workflow according to the request data packet after the acquisition is successful, and sends a feedback data packet to the client, and then starts a feedback retransmission timer corresponding to the client, wherein the feedback retransmission timer retransmits the feedback data packet once every fixed time interval;
step 3: after receiving the feedback data packet, the client releases the request retransmission timer, then carries out client workflow processing according to the information of the feedback data packet and sends a first acknowledgement data packet to the server, and then starts the first acknowledgement retransmission timer, and the first acknowledgement retransmission timer retransmits the first acknowledgement data packet once every fixed time interval;
step 4: after receiving the first acknowledgement data packet, the service end releases the feedback retransmission timer, then sends a second acknowledgement data packet to the client end, and then starts the second acknowledgement retransmission timer corresponding to the client end, and the second acknowledgement retransmission timer retransmits the second acknowledgement data packet once every fixed time interval;
step 5: after receiving the second acknowledgement data packet, the client releases the first acknowledgement retransmission timer, then sends a completion data packet to the server, and releases the mutual exclusion lock acquired by the client so that other workflow of the client can continue;
step 6: and after receiving the completion data packet, the server releases the second acknowledgement retransmission timer, and then releases the mutual exclusion lock of the client acquired by the server.
Preferably, the start position of the request data packet contains a first flag combination, where the first flag combination includes a code number indicating the client, a serial number of the communication cycle to which the data packet belongs in the client, and a "request" attribute.
Preferably, step 2 specifically includes:
the server side firstly checks a first mark combination in the request data packet after receiving the request data packet, records the first mark combination if the request data packet with the first mark combination is received for the first time, and then acquires the mutual exclusion lock of the client side;
if the record of the first mark combination exists in the local combination mark of the server, not processing;
the starting position of the feedback data packet contains a second mark combination, and the second mark combination comprises a code number indicating the client, a serial number of the communication period of the data packet at the client and a feedback attribute.
Preferably, step 3 specifically includes:
after receiving the feedback data packet, the client firstly checks a second mark combination in the feedback data packet, if the feedback data packet with the second mark combination is received for the first time, the client records the second mark combination, and then releases the request retransmission timer;
if the record of the second mark combination is already in the local combination record of the client, the processing is not performed;
the starting position of the first confirmation data packet contains a third mark combination, and the third mark combination comprises a code number indicating the client, a serial number of the communication period of the data packet at the client and a confirmation attribute.
Preferably, step 4 specifically includes:
after receiving the first acknowledgement data packet, the server side checks a third mark combination in the first acknowledgement data packet, if the first acknowledgement data packet with the third mark combination is received for the first time, the third mark combination is recorded, and then the feedback retransmission timer is released;
if the record of the third mark combination exists in the local combination record of the server side, the processing is not performed;
the starting position of the second confirmation data packet contains a fourth mark combination, and the fourth mark combination comprises a code number indicating the client, a serial number of the communication period of the data packet at the client and a confirmation attribute.
Preferably, step 5 specifically includes:
after receiving the second acknowledgement data packet, the client firstly checks a fourth mark combination in the second acknowledgement data packet, if the second acknowledgement data packet with the fourth mark combination is received for the first time, the fourth mark combination is recorded, and then the first acknowledgement retransmission timer is released;
if the record of the fourth mark combination is already in the local combination record of the client, the client continues to send a completion data packet to the server;
the starting position of the completion data packet contains a fifth mark combination, wherein the fifth mark combination comprises a code number for indicating the client, a serial number of a communication period of the data packet at the client and a 'completion' attribute;
the client deletes all records corresponding to the period before the present communication period from the local mark combination record.
Preferably, step 6 specifically includes:
after receiving the completion data packet, the server side firstly checks a fifth mark combination in the completion data packet, if the completion data packet with the fifth mark combination is received for the first time, the fifth mark combination is recorded, and then the second acknowledgement retransmission timer is released;
if the record of the fifth mark combination exists in the local combination record of the server side, the processing is not performed;
and the server deletes all records corresponding to the communication period of the client in the local mark combination records.
The invention has the beneficial effects that:
the invention provides a session layer client and server communication guarantee and workflow control method, which comprises 3 parts at the client, namely a request packet sending part, a feedback packet receiving part (and a first acknowledgement packet sending part) and a second acknowledgement packet receiving part (and a completion packet sending part), and also comprises 3 parts at the server, namely a request packet receiving part (and a feedback packet sending part), a first acknowledgement packet receiving part (and a second acknowledgement packet sending part) and a completion packet receiving part, wherein the request packet sending part, the feedback packet receiving part (and the first acknowledgement packet sending part), the request packet receiving part (and the feedback packet sending part) and the first acknowledgement packet receiving part (and the second acknowledgement packet sending part) are all implemented by a retransmission mechanism through a timer, and the 3 parts of the client and the 3 parts of the server are sequentially and alternately executed to form a complete communication cycle. The first part of the client and the server can try to acquire a mutual exclusion lock to avoid the next communication between the client and the server before the communication is completed, and the mutual exclusion lock restricts other workflow threads which depend on data exchange or procedure call in the communication, so that the workflows can be suspended to execute before the communication is completed. The last part of both the client and the server releases the previously acquired mutex lock. It should be noted that all request, feedback, acknowledge and complete packets have, in addition to the bytes indicating their own properties ("request", "feedback", "acknowledge" or "complete"), the code number of the client initiating the communication and the byte of the serial number of the client in the communication cycle to which the packet belongs, for example, all acknowledge packets in the 23 rd communication between the C client and the server contain the "C", "23" and "acknowledge" flags, and the receiver of the packet records the combination immediately after the first receipt of the packet with this combination of flags. On the one hand, unnecessary retransmission data packets under the data packet retransmission mechanism can be filtered at the receiving end by comparing the recorded combinations; in both aspects, instead of only one exclusive lock, a exclusive lock (e.g., exclusive lock C) may be set up for each client (e.g., C client) at the server according to the actual situation, so as to increase the throughput of the server.
In summary, the method has a bilateral confirmation mechanism and a retransmission mechanism in the aspect of guaranteeing communication, and can retransmit timely, and also can filter redundant retransmission, and in the aspect of workflow control, the use of the mutual exclusion lock enables other workflow threads which rely on data exchange or procedure call in communication to suspend execution in the whole communication period.
The method can truly play the role of guaranteeing communication and managing and controlling workflow under the severe network environment and complex business logic conditions. Even if the communication is interrupted due to the broken link of the physical layer, the method can ensure that the communication continues until the communication is completed as long as the network layer can recover, and the workflow of the client or the server is not disturbed.
Drawings
FIG. 1 is a flow chart of a portion of a client sending a request packet.
Fig. 2 is a flow chart of a portion of a server receiving a request packet (and transmitting a feedback packet).
Fig. 3 is a flow chart of a portion of a client receiving a feedback data packet (and transmitting a first acknowledgement data packet).
Fig. 4 is a flowchart of a portion of a server receiving a first acknowledgement packet (and transmitting a second acknowledgement packet).
Fig. 5 is a flow chart of a portion of a client receiving a second acknowledgement packet (and transmitting a completion packet).
Fig. 6 is a flowchart of a portion of a reception completion packet in a server.
Detailed Description
The following description of the embodiments of the invention will be given with reference to the accompanying drawings and examples:
example 1
Referring to fig. 1 to 6, a session layer client and server communication guarantee and workflow control method includes that 3 parts are respectively a request packet sending part, a feedback packet receiving part (and first acknowledgement packet sending) part and a second acknowledgement packet receiving part (and completion packet sending) part, 3 parts are respectively a request packet receiving part (and feedback packet sending) part, a first acknowledgement packet receiving part (and second acknowledgement packet sending) part and a completion packet receiving part, a retransmission mechanism is realized by a timer in terms of packet sending, and 3 parts of the client and 3 parts of the server are sequentially and alternately executed to form a complete communication cycle.
The method specifically comprises the following steps:
step 1: c client side obtains mutual exclusion lock, after obtaining success C client side sends request data package to server side, and then starts request resending timer, which resends said request data package to server side once every fixed time interval.
The initial position of the request data packet contains a first mark combination, wherein the first mark combination comprises a code number for indicating the C client, a serial number of the communication period of the data packet in the C client and a request attribute.
Step 2: after receiving the request data packet, the server firstly checks the first mark combination in the request data packet, if the request data packet with the first mark combination is received for the first time, the first mark combination is recorded, then the exclusive lock of the C client is obtained, after the acquisition is successful, the server workflow processing is carried out according to the request data packet, the feedback data packet is sent to the C client, then a feedback retransmission timer corresponding to the C client is started, and the feedback retransmission timer retransmits the feedback data packet to the C client once every fixed time interval.
The starting position of the feedback data packet contains a second mark combination, wherein the second mark combination comprises a code number for indicating the client side C, a serial number of the communication period of the data packet at the client side and a feedback attribute.
If there is already a record of the first combination of marks in the local combination mark of the server, it is proved that the request packet is not transmitted to the server for the first time, which may be the case that the request retransmission timer is not released due to a communication delay or the like, the request packet is always being transmitted to the server, and if there is already a record of the first combination of marks in the local combination mark of the server, the server does not perform any processing.
The mutual exclusion lock prevents the next communication between the client and the server before the communication is completed, and makes the mutual exclusion lock restrict other workflow threads depending on data exchange or procedure call in the communication, so that the workflows can be suspended to execute before the communication is completed.
The mutual exclusion lock acquired before can be released after the communication between the client and the server is completed
Step 3: and C, the client firstly checks the second mark combination in the feedback data packet after receiving the feedback data packet, records the second mark combination if the feedback data packet with the second mark combination is received for the first time, and then releases the request retransmission timer.
The client side C receives the feedback data packet, and the client side C proves that the request data packet service side has received and processed the request data packet, and the request data packet is not required to be sent again by the request retransmission timer, so that the request retransmission timer is required to be released.
And then, carrying out client workflow processing according to the information of the feedback data packet, sending a first acknowledgement data packet to the server, and starting a first acknowledgement retransmission timer, wherein the first acknowledgement retransmission timer retransmits the first acknowledgement data packet to the server once every fixed time interval.
The starting position of the first confirmation data packet contains a third mark combination, wherein the third mark combination comprises a code number for indicating the client side C, a serial number of the communication period of the data packet at the client side and a confirmation attribute.
If there is already a record of the second combination of marks in the local combination record of the C-client, it is proved that the feedback data packet is not sent to the C-client for the first time, which may be the case that the feedback retransmission timer is not released due to a communication delay or the like, the feedback data packet is always being sent to the C-client, and if there is already a record of the second combination of marks in the local combination mark of the C-client, the C-client does not perform any processing.
Step 4: the server side receives the first acknowledgement data packet and checks the third mark combination in the first acknowledgement data packet, if the first acknowledgement data packet with the third mark combination is received for the first time, the third mark combination is recorded, and then the feedback retransmission timer is released.
The server side receives the first confirmation data packet, and then proves that the client side C has received the feedback data packet and has completed processing, and the feedback data packet is not required to be sent again by the feedback retransmission timer at the moment, so that the feedback retransmission timer is required to be released.
And then sending a second acknowledgement data packet to the client, and starting a second acknowledgement retransmission timer corresponding to the client C, wherein the second acknowledgement retransmission timer retransmits the second acknowledgement data packet once every fixed time interval.
The starting position of the second confirmation data packet contains a fourth mark combination, and the fourth mark combination comprises a code number for indicating the client side C, a serial number of the communication period of the data packet at the client side and a confirmation attribute.
If the record of the third mark combination is already in the local combination record of the server, it is proved that the first acknowledgement data packet is not sent to the server for the first time, which may be the case that the first acknowledgement retransmission timer is not released due to communication delay or the like, the first acknowledgement data packet is always sent to the server, and if the record of the third mark combination is already in the local combination mark of the server, the server does not perform any processing.
Step 5: c, the client side checks a fourth mark combination in the second acknowledgement data packet after receiving the second acknowledgement data packet, records the fourth mark combination if the second acknowledgement data packet with the fourth mark combination is received for the first time, and then releases the first acknowledgement retransmission timer;
the client C, after receiving the second acknowledgement packet, proves that the server has received the first acknowledgement packet and completed the processing, and the first acknowledgement retransmission timer is not required to be started again at this time, so that the first acknowledgement retransmission timer needs to be started.
And then sending a completion data packet to the server, and then releasing the mutual exclusion lock acquired by the client so that other workflows of the client can continue.
The start position of the completed data packet contains a fifth mark combination, and the fifth mark combination includes a code number indicating the client of C, a serial number of the communication period to which the data packet belongs in the client, and a 'completion' attribute.
If the record of the fourth mark combination is already in the local combination record of the C client, it is proved that the second acknowledgement data packet is not sent to the C client for the first time, which may be the case because the second acknowledgement retransmission timer is not released due to communication delay or the like, the second acknowledgement data packet is always sent to the C client, and if the record of the fourth mark combination is already in the local combination mark of the C client, the C client only continues to send the completion data packet to the server until the server releases the second acknowledgement retransmission timer after receiving the completion data packet.
In addition, the C client also deletes all records corresponding to the period before the present communication period in the local mark combination record (the record related to the present period cannot be deleted yet because the second acknowledgment retransmission timer of the server has not been released yet).
Step 6: after receiving the completion data packet, the server side firstly checks a fifth mark combination in the completion data packet, if the completion data packet with the fifth mark combination is received for the first time, the fifth mark combination is recorded, and then the second acknowledgement retransmission timer is released;
and then releasing the mutual exclusion lock of the C client acquired by the server.
If the record of the fifth mark combination is already in the local combination record of the server, the completion packet is proved not to be sent to the server for the first time, which may be the case that the second acknowledgement retransmission timer is not timely released due to communication delay or the like, and the second acknowledgement packet is always sent to the C client, the C client will always send the completion packet to the server, and if the record of the fifth mark combination is already in the local combination mark of the server, the server does not perform any processing.
And then, the server deletes all records corresponding to the local communication period of the client in the local mark combination records.
It should be understood that the above description is not intended to limit the invention to the particular embodiments disclosed, but to limit the invention to the particular embodiments disclosed, and that the invention is not limited to the particular embodiments disclosed, but is intended to cover modifications, adaptations, additions and alternatives falling within the spirit and scope of the invention.
Claims (7)
1. A communication guarantee and workflow control method between a session layer client and a server is characterized by comprising the following steps:
step 1: the client acquires the mutual exclusion lock, and after the acquisition is successful, the client transmits a request data packet to the server, and then starts a request retransmission timer, wherein the request retransmission timer retransmits the request data packet once every fixed time interval;
step 2: after receiving a request data packet, the server acquires a mutual exclusion lock corresponding to the client, processes a service workflow according to the request data packet after the acquisition is successful, and sends a feedback data packet to the client, and then starts a feedback retransmission timer corresponding to the client, wherein the feedback retransmission timer retransmits the feedback data packet once every fixed time interval;
step 3: after receiving the feedback data packet, the client releases the request retransmission timer, then carries out client workflow processing according to the information of the feedback data packet and sends a first acknowledgement data packet to the server, and then starts the first acknowledgement retransmission timer, and the first acknowledgement retransmission timer retransmits the first acknowledgement data packet once every fixed time interval;
step 4: after receiving the first acknowledgement data packet, the service end releases the feedback retransmission timer, then sends a second acknowledgement data packet to the client end, and then starts the second acknowledgement retransmission timer corresponding to the client end, and the second acknowledgement retransmission timer retransmits the second acknowledgement data packet once every fixed time interval;
step 5: after receiving the second acknowledgement data packet, the client releases the first acknowledgement retransmission timer, then sends a completion data packet to the server, and releases the mutual exclusion lock acquired by the client so that other workflow of the client can continue;
step 6: and after receiving the completion data packet, the server releases the second acknowledgement retransmission timer, and then releases the mutual exclusion lock of the client acquired by the server.
2. The method for guaranteeing communication between a session layer client and a server and controlling workflow according to claim 1, wherein the start position of the request packet contains a first tag combination, and the first tag combination includes a code number indicating the client, a serial number of a communication cycle to which the packet belongs in the client, and a "request" attribute.
3. The method for guaranteeing communication between a session layer client and a server and controlling workflow according to claim 2, wherein step 2 specifically comprises:
the server side firstly checks a first mark combination in the request data packet after receiving the request data packet, records the first mark combination if the request data packet with the first mark combination is received for the first time, and then acquires the mutual exclusion lock of the client side;
if the record of the first mark combination exists in the local combination mark of the server, not processing;
the starting position of the feedback data packet contains a second mark combination, and the second mark combination comprises a code number indicating the client, a serial number of the communication period of the data packet at the client and a feedback attribute.
4. The method for guaranteeing communication between a session layer client and a server and controlling workflow according to claim 3, wherein step 3 specifically comprises:
after receiving the feedback data packet, the client firstly checks a second mark combination in the feedback data packet, if the feedback data packet with the second mark combination is received for the first time, the client records the second mark combination, and then releases the request retransmission timer;
if the record of the second mark combination is already in the local combination record of the client, the processing is not performed;
the starting position of the first confirmation data packet contains a third mark combination, and the third mark combination comprises a code number indicating the client, a serial number of the communication period of the data packet at the client and a confirmation attribute.
5. The method for guaranteeing communication between a session layer client and a server and controlling workflow according to claim 4, wherein step 4 specifically comprises:
after receiving the first acknowledgement data packet, the server side checks a third mark combination in the first acknowledgement data packet, if the first acknowledgement data packet with the third mark combination is received for the first time, the third mark combination is recorded, and then the feedback retransmission timer is released;
if the record of the third mark combination exists in the local combination record of the server side, the processing is not performed;
the starting position of the second confirmation data packet contains a fourth mark combination, and the fourth mark combination comprises a code number indicating the client, a serial number of the communication period of the data packet at the client and a confirmation attribute.
6. The method for guaranteeing communication between a session layer client and a server and controlling workflow according to claim 5, wherein step 5 specifically comprises:
after receiving the second acknowledgement data packet, the client firstly checks a fourth mark combination in the second acknowledgement data packet, if the second acknowledgement data packet with the fourth mark combination is received for the first time, the fourth mark combination is recorded, and then the first acknowledgement retransmission timer is released;
if the record of the fourth mark combination is already in the local combination record of the client, the client continues to send a completion data packet to the server;
the starting position of the completion data packet contains a fifth mark combination, wherein the fifth mark combination comprises a code number for indicating the client, a serial number of a communication period of the data packet at the client and a 'completion' attribute;
the client deletes all records corresponding to the period before the present communication period from the local mark combination record.
7. The method for guaranteeing communication between a session layer client and a server and controlling workflow according to claim 6, wherein step 6 specifically comprises:
after receiving the completion data packet, the server side firstly checks a fifth mark combination in the completion data packet, if the completion data packet with the fifth mark combination is received for the first time, the fifth mark combination is recorded, and then the second acknowledgement retransmission timer is released;
if the record of the fifth mark combination exists in the local combination record of the server side, the processing is not performed;
and the server deletes all records corresponding to the communication period of the client in the local mark combination records.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211002461.3A CN115208521B (en) | 2022-08-22 | 2022-08-22 | Communication guarantee and workflow control method for session layer client and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211002461.3A CN115208521B (en) | 2022-08-22 | 2022-08-22 | Communication guarantee and workflow control method for session layer client and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115208521A CN115208521A (en) | 2022-10-18 |
| CN115208521B true CN115208521B (en) | 2023-07-04 |
Family
ID=83572019
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211002461.3A Active CN115208521B (en) | 2022-08-22 | 2022-08-22 | Communication guarantee and workflow control method for session layer client and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115208521B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105933242A (en) * | 2016-04-12 | 2016-09-07 | 北京大学深圳研究生院 | Method and system for improving TCP response speed of data center |
| CN106982108A (en) * | 2016-01-18 | 2017-07-25 | 华为技术有限公司 | The method and relevant device of a kind of data transfer |
| CN108616925A (en) * | 2016-12-13 | 2018-10-02 | 中兴通讯股份有限公司 | A kind of processing method and processing device of data flow |
| WO2018189416A1 (en) * | 2017-04-13 | 2018-10-18 | Nokia Solutions And Networks Oy | Backwards feedback bundling |
| CN110213024A (en) * | 2018-04-26 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Data package retransmission method, device and equipment |
| CN110677221A (en) * | 2018-07-02 | 2020-01-10 | 华为技术有限公司 | Retransmission control method, communication interface and electronic equipment |
| CN112367149A (en) * | 2020-10-28 | 2021-02-12 | 百果园技术(新加坡)有限公司 | Message acquisition method, device, equipment and storage medium |
| CN113381920A (en) * | 2020-03-09 | 2021-09-10 | 中国移动通信有限公司研究院 | Data transmission method, node and storage medium |
| WO2021218520A1 (en) * | 2020-04-30 | 2021-11-04 | 北京金山云网络技术有限公司 | Method and apparatus for establishing tcp connection, and server |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2003083679A1 (en) * | 2002-03-25 | 2003-10-09 | Netli, Inc. | System for fast recovery from losses for reliable data communication protocols |
| US9049015B2 (en) * | 2007-09-12 | 2015-06-02 | Cisco Technology, Inc. | Allowing TCP ACK to pass a gateway while queuing data for parsing |
-
2022
- 2022-08-22 CN CN202211002461.3A patent/CN115208521B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106982108A (en) * | 2016-01-18 | 2017-07-25 | 华为技术有限公司 | The method and relevant device of a kind of data transfer |
| CN105933242A (en) * | 2016-04-12 | 2016-09-07 | 北京大学深圳研究生院 | Method and system for improving TCP response speed of data center |
| CN108616925A (en) * | 2016-12-13 | 2018-10-02 | 中兴通讯股份有限公司 | A kind of processing method and processing device of data flow |
| WO2018189416A1 (en) * | 2017-04-13 | 2018-10-18 | Nokia Solutions And Networks Oy | Backwards feedback bundling |
| CN110213024A (en) * | 2018-04-26 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Data package retransmission method, device and equipment |
| CN110677221A (en) * | 2018-07-02 | 2020-01-10 | 华为技术有限公司 | Retransmission control method, communication interface and electronic equipment |
| CN113381920A (en) * | 2020-03-09 | 2021-09-10 | 中国移动通信有限公司研究院 | Data transmission method, node and storage medium |
| WO2021218520A1 (en) * | 2020-04-30 | 2021-11-04 | 北京金山云网络技术有限公司 | Method and apparatus for establishing tcp connection, and server |
| CN112367149A (en) * | 2020-10-28 | 2021-02-12 | 百果园技术(新加坡)有限公司 | Message acquisition method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115208521A (en) | 2022-10-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107204834B (en) | Control method for high-speed network reliable transmission based on UDT protocol | |
| TWI260884B (en) | Method for handling a triggered reset when an RLC is stopped in a wireless communications system | |
| TW477129B (en) | Discard mechanism for selective repeat automatic repeat request | |
| US7359919B2 (en) | Reliable request-response messaging over a request-response transport | |
| US9497779B2 (en) | Enhanced polling method for preventing deadlock in a wireless communications system | |
| JP3744908B2 (en) | Data discard signaling processing in wireless communication systems | |
| JP5192552B2 (en) | Method and transmitter for reducing the risk of transmission stalling | |
| JP2002529010A (en) | Packet discarding method and packet discarding device in data network performing automatic retransmission request | |
| JP2002542662A (en) | Flexible radio link control protocol | |
| US8738984B2 (en) | Apparatus for processing retransmission failure in radio link control (RLC) layer | |
| US20070133414A1 (en) | Method for faster detection and retransmission of lost TCP segments | |
| KR101524029B1 (en) | Link Layer Control Protocol Implementation | |
| TWI435637B (en) | Method and system for handling an error in long term evolution positioning protocol messages exchange | |
| TW200901669A (en) | Congestion reducing reliable transport packet retry engine | |
| WO2013075666A1 (en) | Rlc data packet transmission acknowledgement method and rlc am entity sending party | |
| CN112911638B (en) | Reliable communication method for optimizing wireless network load congestion by using UDP (user Datagram protocol) | |
| CN111147196A (en) | Data transmission method, data sending device and data receiving device | |
| JPWO2008023791A1 (en) | Wireless transmission device, wireless reception device, and wireless communication method | |
| CN115208521B (en) | Communication guarantee and workflow control method for session layer client and server | |
| EP1796301A2 (en) | Method and apparatus for RLC protocol error handling | |
| US20100144364A1 (en) | Retransmission control method and transmitting-side apparatus | |
| KR101611663B1 (en) | Data communications using connectionless-oriented protocol | |
| CN116599953A (en) | File uploading method, device, system, equipment and readable storage medium | |
| JP2006191368A (en) | Network transmission device | |
| WO2018077195A1 (en) | Method and apparatus for data retransmission, and mac device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |