WO2017107083A1

WO2017107083A1 - Data sending method and receiving method, apparatus and system

Info

Publication number: WO2017107083A1
Application number: PCT/CN2015/098372
Authority: WO
Inventors: 张鲲鹏; 张金锁; 姚传群
Original assignee: 华为技术有限公司
Priority date: 2015-12-23
Filing date: 2015-12-23
Publication date: 2017-06-29

Abstract

Disclosed are a data sending method, receiving method, apparatus and system, falling within the technical field of networks. The method comprises: acquiring a label from a label resource pool, wherein the label resource pool has a label representing that the sending end currently has the permission to send service data to a receiving end; generating a first data packet according to service data to be sent; and sending the first data packet to the receiving end. In the present invention, by acquiring a label from a label resource pool on the premise that the label resource pool has a label, namely, a sending end currently having the permission to send service data to a receiving end, and then sending a first data packet according to service data to be sent, so that the receiving end can process the service data based on a current service data processing capability, thereby guaranteeing that the sending end can send the service data where the receiving end currently has a service data processing capability, avoiding the problem of transmission failure, improving transmission success rate, and improving the flexibility.

Description

Data transmitting method, receiving method, device and system

Technical field

The present invention relates to the field of network technologies, and in particular, to a data sending method, a receiving method, an apparatus, and a system.

Background technique

In the network system, the sending end often sends service data to the receiving end, and the receiving end caches the service data in the buffer area, and then reads the service data from the buffer area, thereby processing the service data. If the service data sent by the sender exceeds the processing capability of the receiver, the buffer will overflow. The receiver will discard the service data and the service data transmission fails.

In order to avoid the problem of service data transmission failure, the transmitting end may send a status acquisition instruction to the receiving end to request the current state of the receiving end before receiving the service data, and the receiving end receives the status obtaining instruction and determines that the current processing service can be processed. When the data is received, it can return a Ready status response indicating that the service data can be processed. When the sender receives the Ready status response, it calculates the service data sent and received in a unit time, obtains the traffic rate at this time, and determines the traffic rate. If the preset traffic limit is exceeded, if the traffic rate does not exceed the preset traffic limit, the service data is sent to the receiver to implement flow control and backpressure.

In the process of implementing the present invention, the inventors have found that the prior art has at least the following problems:

There is a certain delay between the return of the Ready status response when the receiving end receives the status acquisition command and the service data received by the receiving end, and the Ready status response can only indicate that the receiving end can process the service data when receiving the status acquisition instruction, and It is not possible for the receiving end to process the service data when it receives the service data of the sending end. If the receiving end can not process the service data when receiving the service data of the sending end, the service data will still be discarded, causing the service data transmission to fail. .

Summary of the invention

In order to overcome the problems existing in the prior art, the present invention provides a data transmitting method, a receiving method, an apparatus, and a system. The technical solution is as follows:

In a first aspect, a data sending method is provided, the method comprising:

The sender obtains a label from the label resource pool, where the label resource pool has a label representation The sender currently has the right to send service data to the receiving end;

The sending end generates a first data packet according to the to-be-sent service data of the sending end;

The sending end sends the first data packet to the receiving end.

In conjunction with the first aspect, in a first possible implementation manner of the first aspect, the first data packet includes the acquired label and the service data.

With reference to any of the foregoing possible implementation manners of the foregoing aspect, in a second possible implementation manner of the first aspect, the sending end obtains a label from the label resource pool, including:

And if the sending end determines that at least one label exists in the label resource pool, obtaining a label from the label resource pool.

With reference to any one of the foregoing possible implementation manners of the first aspect, in a third possible implementation manner of the first aspect, before the sending end generates the first data packet according to the to-be-sent service data of the sending end, The method also includes:

Generating the label resource pool according to the service data processing capability of the receiving end.

With the foregoing possible implementation manner of the foregoing aspect, in a fourth possible implementation manner of the foregoing aspect, the generating, by the service data processing capability of the receiving end, the label resource pool includes:

The transmitting end calculates a total processing time of the one data packet according to a transmission delay time between the transmitting end and the receiving end, and a time when the receiving end processes one data packet;

The sending end acquires a service data processing capability of the receiving end, where the service data processing capability is used to indicate a maximum number of data packets processed by the receiving end in a unit time;

The sending end uses the product of the service data processing capability and the total processing time of the one data packet as the total processing capability value of the receiving end;

And generating, by the total processing capability value, the label resource pool, where the label resource pool has a label number equal to the total processing capability value.

With reference to any of the foregoing possible implementations of the first aspect, in a fifth possible implementation manner of the first aspect, the method further includes:

The obtained tag is deleted from the tag resource pool.

With reference to any of the foregoing possible implementations of the first aspect, in a sixth possible implementation manner of the first aspect, the method further includes:

Receiving, by the sending end, the second data packet sent by the receiving end, where the second data packet includes the acquired label and indication data obtained by processing the service data, where the indication data is used to indicate a processing result of the service data by the receiving end;

Retrieving the acquired tag included in the second data packet to the tag resource pool.

With reference to any one of the foregoing possible implementations of the first aspect, in a seventh possible implementation manner of the first aspect, the sending end generates, according to the acquired label and the to-be-sent service data of the terminal, the first After the packet, it also includes:

The sending end stores the detailed information of the service data, where the detailed information includes a memory address of the service data to be sent;

The sending end establishes a correspondence between the label and the detailed information;

After the sending end receives the second data packet sent by the receiving end, the method further includes:

The sending end acquires a memory address corresponding to the label according to the corresponding relationship;

The sending end recovers the memory space indicated by the memory address according to the memory address.

In conjunction with any of the foregoing possible implementations of the first aspect, in an eighth possible implementation manner of the first aspect, the method further includes:

When the sending end performs obtaining a label from the label resource pool, the sending end starts timing;

If the time period reaches a preset duration, and the acquired label is not reclaimed into the label resource pool, the sending end regenerates the label, and regenerates according to the regenerated label and the service data. Transmitting, by the first data packet, the regenerated first data packet to the receiving end.

With reference to any of the foregoing possible implementations of the first aspect, in a ninth possible implementation manner of the first aspect, the method further includes:

When the duration of the statistics reaches a preset duration, it is determined whether the label has been recycled to the label resource pool;

If the label is not returned to the label resource pool, the status of the receiving end is determined to be not in place;

If the tag has been recycled to the tag resource pool, the state of the receiving end is determined to be in place.

With reference to any one of the foregoing possible implementations of the first aspect, in a tenth possible implementation manner of the first aspect, the method further includes:

If the label is not obtained from the label resource pool, the service data is suspended until the label is obtained from the label resource pool, and then the first number is generated according to the obtained label and the service data. According to the packet, the first data packet is sent to the receiving end.

With reference to any of the foregoing possible implementations of the first aspect, in an eleventh possible implementation manner of the first aspect, the method further includes:

If the label is not recovered to the label resource pool, querying the detailed information corresponding to the label according to the correspondence, determining a memory address in the detailed information, and recovering the memory according to the memory address The memory space indicated by the address.

With reference to any of the foregoing possible implementation manners of the first aspect, in a twelfth possible implementation manner of the first aspect, the method is applied to a transmitting end in a distributed system, where the distributed system includes a receiving end and at least A sender.

In a second aspect, a data receiving method is provided, the method comprising:

The receiving end receives the first data packet sent by the sending end, and the first data packet is generated by the sending end by acquiring a label from the label resource pool, and is generated according to the to-be-sent service data, where the label resource pool has a label indicating the sending The terminal currently has the right to send service data to the receiving end;

The receiving end processes the service data based on the current service data processing capability.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the method further includes:

The receiving end sends a second data packet to the sending end, where the second data packet includes a label in the first data packet and indication data obtained by processing the service data in the first data packet, where The indication data is used to indicate a processing result of the service data by the receiving end.

With reference to any of the foregoing possible implementation manners of the second aspect, in a second possible implementation manner of the second aspect, the method is applied to a receiving end in a distributed system, where the distributed system includes a receiving end and at least one The sender.

In a third aspect, a data transmitting apparatus is provided, the apparatus comprising:

a label obtaining module, configured to obtain a label from a label resource pool, where the label in the label resource pool indicates that the sending end currently has the right to send service data to the receiving end;

a data packet generating module, configured to generate a first data packet according to the to-be-sent service data of the sending end;

And a sending module, configured to send, to the receiving end, the first data packet generated by the data packet generating module.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the first data packet The acquired tag and the business data are included.

With reference to any one of the foregoing possible implementations of the third aspect, in a second possible implementation manner of the third aspect, the label obtaining module is further configured to: if it is determined that at least one label exists in the label resource pool, Get a label in the label resource pool.

In conjunction with any of the foregoing possible implementations of the third aspect, in a third possible implementation manner of the third aspect, the device further includes:

The label resource pool generating module is configured to generate the label resource pool according to the service data processing capability of the receiving end.

With the foregoing possible implementation manner of the foregoing aspect, in a fourth possible implementation manner of the third aspect, the label resource pool generating module is further configured to perform transmission according to the sending end and the receiving end a delay time, and a time when the receiving end processes a data packet, calculating a total processing time of the one data packet; acquiring a service data processing capability of the receiving end, where the service data processing capability is used to indicate that the receiving end is The maximum number of data packets processed per unit time; the product of the service data processing capability and the total processing time of the one data packet is used as the total processing capability value of the receiving end; and generated according to the total processing capability value The label resource pool, the label number of the label resource pool is equal to the total processing capability value.

In conjunction with any of the foregoing possible implementations of the third aspect, in a fifth possible implementation manner of the third aspect, the device further includes:

And a deleting module, configured to delete the label acquired by the label obtaining module from the label resource pool.

With reference to any of the foregoing possible implementations of the third aspect, in a sixth possible implementation manner of the third aspect, the device further includes:

a receiving module, configured to receive a second data packet sent by the receiving end, where the second data packet includes the acquired label and indication data obtained by processing the service data, where the indication data is used to indicate Decoding the processing result of the service data by the receiving end;

And a label recycling module, configured to collect the label in the second data packet received by the receiving module into the label resource pool.

With reference to any of the foregoing possible implementations of the third aspect, in a seventh possible implementation manner of the third aspect, the device further includes:

a storage module, configured to store detailed information of the service data, where the detailed information includes a memory address of the service data to be sent;

Establishing a relationship module, configured to establish a correspondence between the label and the detailed information;

a memory address obtaining module, configured to acquire a memory address corresponding to the label according to the correspondence established by the establishing relationship module;

The memory space recovery module is configured to recover the memory space indicated by the memory address according to the memory address obtained by the memory address acquisition module.

In conjunction with any of the foregoing possible implementations of the third aspect, in an eighth possible implementation manner of the third aspect, the device further includes:

a timing module, configured to start timing when the label obtaining module acquires a label from the label resource pool;

a label generating module, configured to regenerate the label if the timing of the timing module reaches a preset duration and the label acquired by the label obtaining module is not recycled to the label resource pool;

The data packet generating module is further configured to regenerate the first data packet according to the label and the service data regenerated by the label generation module;

The sending module is further configured to send, to the receiving end, a first data packet that is regenerated by the data packet generating module.

According to a fourth aspect, a data receiving apparatus is provided, where the data receiving apparatus is applied to a receiving end, and the apparatus includes:

a receiving module, configured to receive a first data packet sent by the sending end, where the first data packet is generated by the sending end from the label resource pool, and is generated according to the service data to be sent, where the label resource pool has a label representation The sending end currently has the right to send service data to the receiving end;

The processing module is configured to process the service data in the first data packet received by the receiving module based on the current service data processing capability.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the device further includes:

a sending module, configured to send a second data packet to the sending end, where the second data packet includes a label in the first data packet and indication data obtained by processing the service data in the first data packet, The indication data is used to indicate a processing result of the service data by the receiving end.

A fifth aspect provides a data transmission system, where the system includes: a receiving end and at least one transmitting end;

Each sender is configured to obtain a label from a label resource pool, where the label resource pool has a label The sign indicates that the sending end currently has the right to send the service data to the receiving end; the first data packet is generated according to the to-be-sent service data of the sending end; and the first data packet is sent to the receiving end.

The receiving end is configured to receive a first data packet sent by any sending end, and process the service data in the received first data packet according to a current service data processing capability.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the sending end that sends the first data packet is further used to delete the acquired label from the label resource pool;

The sending end of the first data packet is further configured to receive the second data packet returned by the receiving end, and collect the label in the second data packet into the label resource pool.

With reference to any one of the foregoing possible implementation manners of the fifth aspect, in a second possible implementation manner of the fifth aspect, the system is a distributed system, where the distributed system includes multiple sending ends and the receiving end.

The beneficial effects of the technical solutions provided by the embodiments of the present invention are:

In the embodiment of the present invention, a label is obtained in the label resource pool, that is, the sender currently has the right to send the service data to the receiving end, and obtains a label from the label resource pool, and sends the first data packet according to the service data to be sent. After receiving the first data packet, the receiving end can process the service data based on the current service data processing capability, and ensure that the sending end can send the service data only when the receiving end currently has the service data processing capability, so as not to exceed The current service data processing capability of the receiving end avoids the problem of transmission failure, improves the transmission success rate, and improves flexibility.

Further, the first data packet is generated according to the acquired label and the to-be-sent service data, and the first data packet is sent to the receiving end, so that the number of labels that have been acquired in the label resource pool is equal to the number of sent data packets, thereby The number of the remaining labels in the label resource pool can accurately indicate the current service data processing capability of the receiving end. That is, the label in the label resource pool can indicate that the sending end currently has the right to send the service data to the receiving end.

Further, when the at least one label in the label resource pool is determined by the sending end, the label is obtained from the label resource pool, which saves the execution step of obtaining the label and improves the success rate of acquiring the label.

Further, the tag resource pool is generated according to the service processing capability of the receiving end, that is, the transmission delay time between the transmitting end and the receiving end, the processing time of the receiving end for one data packet, and the data packet processed by the receiving end in the unit time. The maximum number of the calculation, the total processing capacity value of the receiving end is calculated, and the label resource pool is generated according to the total processing capability value, and the initial number of labels in the label resource pool can be refined. Exactly indicating the total service data processing capability of the receiving end to the transmitting end, so that the transmitting end can indicate the current service data processing capability of the receiving end by the number of initial labels determined by the number of initial labels and the number of transmitted data packets, and the label resources are guaranteed. The presence of a label in the pool indicates that the sender currently has the right to send service data to the receiver, which improves the accuracy and ensures that the sender can send service data only when the receiver has the service data processing capability currently available on the receiver. The problem of failure increases the transmission success rate and increases flexibility.

Further, by deleting the obtained label from the label resource pool, it is ensured that the label in the label resource pool can accurately indicate that the sending end currently has the right to send the service data to the receiving end, and the accuracy of the remaining number of labels is improved.

Further, by recycling the label in the second data packet returned by the receiving end to the label resource pool, when the receiving end processes the first data packet, the number of remaining labels in the label resource pool is increased by the recycling manner, thereby ensuring After the number of labels is increased, the number of remaining labels in the label resource pool can accurately indicate the current service data processing capability of the receiving end. The label in the label resource pool can accurately indicate that the sending end currently has the right to send service data to the receiving end, which improves the Accuracy.

Further, by storing the detailed information of the service data, and establishing a correspondence between the label and the detailed information, when the second data packet is received, the memory address corresponding to the label may be queried according to the corresponding relationship, and the memory is reclaimed according to the memory address. The memory space indicated by the address. By tagging the detailed information of the service data with the tag, it is not necessary to carry the detailed information when the first data packet is sent, and the detailed information of the service data can be determined, which saves bandwidth and improves flexibility. Moreover, when the receiving end completes processing of the first data packet, the memory space indicated by the memory address is recovered in time, thereby saving memory resources.

Further, when the label is obtained from the label resource pool, timing is started. When the timer duration reaches the preset duration, if the label has not been recycled to the label resource pool, the corresponding label is regenerated, and the regenerated label and service are generated according to the label. Data, regenerating the first data packet, and sending the regenerated first data packet to the receiving end, so that the receiving end can re-process the service data, avoiding the problem that the service data processing fails, and avoiding that the receiving end is not correct. The problem of reducing the number of labels in the processing of the service data ensures that the number of remaining labels can accurately indicate the current service data processing capability of the receiving end. The presence of the label in the label resource pool can accurately indicate that the transmitting end currently has the service data to be sent to the receiving end. Permissions, increased accuracy.

Further, by determining whether the receiving end is in position according to whether the label is reclaimed, the current state of the receiving end can be obtained, and the current state of the receiving end can be uploaded to the upper layer software, so that the upper layer software can send the transmitting end according to the current state of the receiving end. Coordinated control for increased flexibility.

Further, when any label is not obtained from the label resource pool, the service data is suspended, and when the label is obtained from the label resource pool, the first data packet is generated according to the obtained label and the service data. The receiving end sends the first data packet, which can ensure that the transmitting end sends the service data only when the receiving end has the service data processing capability, thereby avoiding the problem of the transmission failure and improving the transmission success rate.

Further, when the label recovery timeout is performed, the detailed information corresponding to the label is queried according to the corresponding relationship, the memory address in the detailed information is determined, and the memory space indicated by the memory address is recovered, thereby avoiding memory leakage and improving flexibility.

Further, the transmitting end can be applied to a distributed system, which ensures that multiple transmitting ends in the distributed system can perform flow control by themselves without affecting other transmitting ends, and is convenient for each transmitting end in the distributed system. Order management, with high flexibility.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

1 is a schematic structural diagram of a data transmission system according to an embodiment of the present invention;

2 is a schematic structural diagram of a distributed acceleration system according to an embodiment of the present invention;

3 is a schematic structural diagram of another distributed acceleration system according to an embodiment of the present invention;

4 is a schematic structural diagram of a data sending device according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a data receiving device according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a data sending apparatus according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a data receiving apparatus according to an embodiment of the present invention;

FIG. 8 is a flowchart of a data transmission method according to an embodiment of the present invention;

FIG. 9 is a flowchart of a data sending method according to an embodiment of the present invention;

FIG. 10 is a flowchart of a data receiving method according to an embodiment of the present invention.

detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

FIG. 1 is a schematic structural diagram of a data transmission system according to an embodiment of the present invention. Referring to FIG. 1, the system includes a transmitting end 101 and a receiving end 102.

The sending end 101 is configured to obtain a label from the label resource pool, and the label in the label resource pool indicates that the sending end 101 currently has the right to send the service data to the receiving end; and the first data packet is generated according to the service data to be sent by the sending end 101. Transmitting the first data packet to the receiving end 102;

The receiving end 102 is configured to receive the first data packet sent by the sending end 101, and process the service data in the received first data packet based on the current service data processing capability.

Optionally, the first data packet includes the acquired label and service data.

Optionally, the sending end 101 is further configured to: obtain a label from the label resource pool if it is determined that at least one label exists in the label resource pool.

Optionally, the sending end 101 is further configured to generate a label resource pool according to the service data processing capability of the receiving end 102 before generating the first data packet according to the to-be-sent service data of the sending end 101.

Optionally, the sending end 101 is further configured to: before the first data packet is generated according to the to-be-sent service data of the sending end 101, according to a transmission delay time between the transmitting end 101 and the receiving end 102, and the receiving end 102 processes one The time of the data packet, the total processing time of a data packet is calculated; the service data processing capability of the receiving end 102 is obtained, and the service data processing capability is used to indicate the maximum number of data packets processed by the receiving end in a unit time; The product of the service data processing capability and the total processing time of the one data packet is used as the total processing capability value of the receiving end; according to the total processing capability value, a label resource pool is generated, and the label resource pool has a label number equal to the total processing capability value.

Optionally, the sending end 101 is further configured to delete the obtained label from the label resource pool.

Optionally, the receiving end 102 is further configured to send, to the sending end 101, a second data packet, where the second data packet includes a label in the first data packet, and is processed by processing the service data in the first data packet. The indication data is used to indicate the processing result of the service data by the receiving end; the sending end 101 is further configured to receive the second data packet sent by the receiving end 102, and the label included in the second data packet Recycle to the tag resource pool.

Optionally, the sending end 101 is further configured to: after generating the first data packet according to the acquired label and the to-be-sent service data of the terminal, storing the detailed information of the service data, where the detailed information includes the memory of the service data to be sent. An address; establishing a correspondence between the label and the detailed information; after receiving the second data packet sent by the receiving end 102, acquiring a memory address corresponding to the label according to the corresponding relationship; and recovering the memory according to the memory address The memory space indicated by the address.

Optionally, the sending end 101 is further configured to start timing when acquiring a label from the label resource pool; If the timeout period reaches the preset duration, and the acquired label is not reclaimed into the label resource pool, the sending end 101 regenerates the label, and regenerates the first data packet according to the regenerated label and the service data. Sending the regenerated first data packet to the receiving end 102.

Optionally, the system is a distributed system comprising a receiving end 102 and two or more transmitting ends 101.

Further, the data transmission system may be a distributed acceleration system. Referring to FIG. 2, the distributed acceleration system includes a plurality of local service servers 201 and a plurality of remote acceleration servers 202, wherein each remote acceleration server 202 is configured with Accelerate the engine. Wherein, a plurality of specific references are two or more, and are not described again.

The local service server 201 can apply for the acceleration processing capability of the remote acceleration server 202, and after applying for a certain acceleration processing capability, send the service data that needs to be accelerated to the remote acceleration server 202, and the remote acceleration server 202 can receive the service data. And using the configured acceleration engine to accelerate the service data, and return the instruction data obtained after the acceleration processing to the local service server 201.

The local service server 201 is used as the sending end, and the remote acceleration server 202 is used as the receiving end. When the local service server 201 sends the service data to the remote acceleration server 202, the label can be obtained from the label resource pool. The presence of the label indicates that the local service server 201 currently has the right to send the service data to the remote acceleration server 202, and generates a first data packet according to the service data to be sent by the local service server 201, and sends the first data packet to the remote acceleration server 202. data pack.

The remote acceleration server 202 receives the first data packet sent by the local service server 201, and can accelerate the service data by using the configured acceleration engine based on the currently available acceleration processing capability.

Optionally, the local service server 201 may also delete the obtained label from the label resource pool, and after receiving the second data packet returned by the remote acceleration server 202, the label in the second data packet may be recycled to the label resource. Pool.

Further, in the distributed acceleration system, the local service server 201 and the remote acceleration server 202 can be directly connected through a port or connected through a switch.

For example, referring to FIG. 3, the local service server 201 includes a local processing unit (Central Processing Unit) 301 and a local service board 302, and the remote acceleration server 202 includes a remote end. The CPU 303 and the remote acceleration board 304. The local CPU 301 is connected to the local service board 302, and the remote CPU 303 is connected to the remote acceleration board 304. The local service board 302 and the remote acceleration board 304 can be connected through the switch 305.

In addition, the local service board 302 and the remote acceleration board 304 respectively include a plurality of AE (Accelerate Engine) modules and a plurality of rAE (Remote Accelerate Engine) management modules, wherein the AE module is used for The local service data is accelerated, and the service data sent by other boards is received, and the service data is accelerated, and the instruction data of the processing completion is returned. The rAE management module is configured to configure according to the instructions sent by the processor. The other boards of the AE module send service data, and the other boards accelerate the service data and receive the returned indication data.

The local service board 302 obtains a label from the label resource pool in the process of sending the service data to the remote acceleration board 304 according to the instruction sent by the local CPU 301. The label resource pool has a label indicating the local service board 302. Currently, the user has the right to send the service data to the remote acceleration board 304, and generates the first data packet according to the to-be-sent service data of the local service card 302, and sends the first data packet to the remote acceleration board 304. The remote acceleration board 304 can receive the first service packet sent by the local service board 302, and process the service data based on the current service data processing capability.

The transmitting end and the receiving end shown in the foregoing embodiments may be located in the same device or may be located in different devices. For example, the sender and the receiver can be different modules in the same device, and the two modules can interact with each other. Alternatively, the sending end is located in the data sending device, and the receiving end is located in the data receiving device, and the data sending device and the data receiving device can interact with each other. For details, refer to the following embodiments.

FIG. 4 is a schematic structural diagram of a data sending device according to an embodiment of the present invention. Referring to FIG. 4, the device includes: a receiver 401, a transmitter 402, a memory 404, and a processor 404. The receiver 401, the transmitter 402, and the The memory 404 is respectively connected to the processor 404. The memory 404 stores program code, and the processor 404 is configured to call the program code to perform the following operations:

Obtain a label from the label resource pool. The label in the label resource pool indicates that the sender currently has the right to send service data to the receiver.

Generating a first data packet according to the to-be-sent service data of the sending end;

The first data packet is transmitted to the receiving end by the transmitter 402.

Optionally, the first data packet includes the acquired label and the service data.

Optionally, the processor 404 is configured to invoke the program code to perform the following operations:

If it is determined that at least one tag exists in the tag resource pool, a tag is obtained from the tag resource pool.

The tag resource pool is generated according to the service data processing capability of the receiving end.

Calculating a total processing time of the one data packet according to a transmission delay time between the transmitting end and the receiving end, and a time when the receiving end processes a data packet; acquiring a service data processing capability of the receiving end, the service data processing capability The maximum number of data packets used by the receiving end to process in a unit time; the product of the service data processing capability and the total processing time of the one data packet is used as the total processing capability value of the receiving end; according to the total processing capability The value is generated, and the label resource pool is generated, and the label resource pool has a label number equal to the total processing capability value.

The obtained tag is deleted from the tag resource pool.

Receiving, by the receiver 401, the second data packet sent by the receiving end, where the second data packet includes the acquired label and the indication data obtained by processing the service data, where the indication data is used to indicate that the receiving end is to the service data. The processing result; the acquired label included in the second data packet is recycled to the label resource pool.

Storing the detailed information of the service data, the specific information includes a memory address of the service data to be sent; establishing a correspondence between the tag and the detailed information; and obtaining, according to the correspondence, a memory address corresponding to the tag; according to the memory address, Reclaims the memory space indicated by this memory address.

When a tag is obtained from the tag resource pool, the timer is started; if the timer duration reaches the preset duration, and the acquired tag is not reclaimed into the tag resource pool, the sender regenerates the tag according to the regenerated tag. And the service data, regenerating the first data packet, and sending the regenerated first data packet to the receiving end.

FIG. 5 is a schematic structural diagram of a data receiving device according to an embodiment of the present invention. Referring to FIG. 5, the device includes: a receiver 501, a transmitter 502, a memory 503, and a processor 504. The receiver 501, the The transmitter 502 and the memory 503 are respectively connected to the processor 504. The memory 503 stores program code, and the processor 504 is configured to call the program code to perform the following operations:

Receiving, by the receiver 501, the first data packet sent by the sending end, where the first data packet is generated by the sending end from the label resource pool, and is generated according to the service data to be sent, where the label exists in the label resource pool to indicate the sending end Currently has the right to send business data to the receiving end;

The business data is processed based on current business data processing capabilities.

Optionally, the processor 504 is configured to invoke the program code to perform the following operations:

Transmitting, by the transmitter 502, a second data packet to the transmitting end, where the second data packet includes a label in the first data packet and indication data obtained by processing the service data in the first data packet, where the indication data is used to indicate The result of processing the service data by the receiving end.

FIG. 6 is a schematic structural diagram of a data sending apparatus according to an embodiment of the present invention. The data sending apparatus is applied to a transmitting end. Referring to FIG. 6, the apparatus includes: a label obtaining module 601, a data packet generating module 602, and a sending module 603.

The label obtaining module 601 is configured to obtain a label from the label resource pool, where the label in the label resource pool indicates that the sending end currently has the right to send the service data to the receiving end;

a data packet generating module 602, configured to generate a first data packet according to the to-be-sent service data of the sending end;

The sending module 603 is configured to send the first data packet to the receiving end.

The device provided by the embodiment of the present invention obtains a label from the label resource pool, and sends a label according to the to-be-sent service data, on the premise that the label has a right to send the service data to the receiving end. The first data packet enables the receiving end to process the service data based on the current service data processing capability after receiving the first data packet, thereby ensuring that the transmitting end can send the service only when the receiving end currently has the service data processing capability. Data, so as to avoid exceeding the current service data processing capability of the receiving end, avoiding the problem of transmission failure, improving the transmission success rate and improving flexibility.

Optionally, the label obtaining module 601 is further configured to: obtain a label from the label resource pool if it is determined that at least one label exists in the label resource pool.

Optionally, the device further includes:

a label resource pool generating module 604, configured to generate, according to the service data processing capability of the receiving end, The tag resource pool.

Optionally, the label resource pool generating module 601 is further configured to calculate a total processing time of the one data packet according to a transmission delay time between the sending end and the receiving end, and a time when the receiving end processes a data packet. Obtaining a service data processing capability of the receiving end, where the service data processing capability is used to indicate a maximum number of data packets processed by the receiving end in a unit time; a product of the service data processing capability and the total processing time of the one data packet The total processing capability value of the receiving end is generated according to the total processing capability value, and the label resource pool has a label number equal to the total processing capability value.

Optionally, the device further includes:

The deleting module 605 is configured to delete the label acquired by the label obtaining module from the label resource pool.

Optionally, the device further includes:

The receiving module 606 is configured to receive the second data packet sent by the receiving end, where the second data packet includes the acquired label and the indication data obtained by processing the service data, where the indication data is used to indicate that the receiving end is Processing result of business data;

The label collection module 607 is configured to collect the label in the second data packet received by the receiving module into the label resource pool.

Optionally, the device further includes:

The storage module 608 is configured to store detailed information of the service data, where the detailed information includes a memory address of the service data to be sent;

Establishing a relationship module 609, configured to establish a correspondence between the label and the detailed information;

The memory address obtaining module 610 is configured to obtain a memory address corresponding to the label according to the correspondence established by the establishing relationship module.

The memory space recovery module 611 is configured to recover the memory space indicated by the memory address according to the memory address obtained by the memory address acquisition module.

Optionally, the device further includes:

The timing module 612 is configured to start timing when the label obtaining module acquires a label from the label resource pool;

The label generating module 613 is configured to regenerate the label if the timing of the timing module reaches a preset duration and the label acquired by the label obtaining module is not recycled to the label resource pool;

The data packet generating module 602 is further configured to regenerate the first data packet according to the label and the service data regenerated by the label generation module.

The sending module 603 is further configured to send, to the receiving end, the first data packet that is regenerated by the data packet generating module.

FIG. 7 is a schematic structural diagram of a data receiving apparatus according to an embodiment of the present invention. The data receiving apparatus is applied to a receiving end. Referring to FIG. 7, the apparatus includes: a receiving module 701 and a processing module 702.

The receiving module 701 is configured to receive a first data packet sent by the sending end, where the first data packet is generated by the sending end from the label resource pool, and is generated according to the service data to be sent, where a label exists in the label resource pool to indicate the sending The terminal currently has the right to send service data to the receiving end;

The processing module 702 is configured to process the service data in the first data packet received by the receiving module 701 based on the current service data processing capability.

The apparatus provided by the embodiment of the present invention can receive the first data packet sent to the receiving end on the premise that the transmitting end has the right to send the service data to the receiving end, and can be based on the current service data processing capability in the first data packet. The processing of the service data ensures that the data packet sent by the sender does not exceed the current service data processing capability of the receiving end, avoids the problem of transmission failure, improves the transmission success rate, and improves flexibility.

Optionally, the device further includes:

The sending module 703 is configured to send, to the sending end, a second data packet, where the second data packet includes a label in the first data packet and indication data obtained by processing the service data in the first data packet, where the indication data is It is used to indicate the processing result of the service data by the receiving end.

Based on the data transmission system shown in FIG. 1, an embodiment of the present invention provides a data transmission method applied to the data transmission system. FIG. 8 is a flowchart of a data transmission method according to an embodiment of the present invention. Referring to FIG. 8, the interaction body of the method is a sender and a receiver, and the sender and the receiver may be a terminal, a server, a virtual machine, or a single The device, such as a board, may also be a sending port and a receiving port configured on the device, which are not limited in this embodiment of the present invention. The data transmission method includes the following steps:

801. The sender obtains a label from the label resource pool.

Whether the label exists in the label resource pool can be used to indicate the service data processing capability of the receiving end. If there is a label in the label resource pool, that is, the number of labels in the label resource pool is greater than 0, it indicates that the receiving end currently has the service data processing capability. At this time, if the sending end sends the service data to the receiving end, the receiving end can be based on the current The service data processing capability processes the service data. Therefore, when the label exists in the label resource pool, the sender has the right to send the service data to the receiver. And If there is no label in the label resource pool, that is, the number of labels in the label resource pool is 0, it means that the receiving end does not currently have the service data processing capability. At this time, if the sending end sends the service data to the receiving end, the receiving end cannot The service data is processed, and the service data is discarded. Therefore, when it is determined that the label resource pool does not have a label, the sender does not have the right to send the service data to the receiver.

Specifically, step 801 can be implemented in the following two manners without limitation:

In the first mode, if the sending end determines that at least one label exists in the label resource pool, a label is obtained from the label resource pool.

That is, if there is at least one label in the label resource pool, if it is determined that at least one label exists in the label resource pool, a label is obtained from the label resource pool; if it is determined that the label resource pool has no label, The obtaining step is not performed until the at least one label exists in the label resource pool, and then the action of obtaining the label from the label resource pool is performed.

Method 2: Obtain a label directly from the identity resource pool.

That is, the sender does not determine whether there is at least one label in the label resource pool, but directly attempts to obtain a label from the identifier resource pool. If the label is successfully obtained, the number of remaining labels in the label resource pool is greater than 0, and the receiving end Currently, the ability to process data packets is not available. If the label fails to be obtained, it indicates that there is no label in the label resource pool, and the receiving end does not currently have the ability to process data packets.

802. The sending end generates a first data packet according to the to-be-sent service data of the sending end, and sends the first data packet to the receiving end.

In a first possible implementation, after obtaining a label from the label resource pool, the sending end may encapsulate the service data to be sent into the first data packet, and send the first data packet to the receiving end. That is, the first data packet includes service data to be transmitted.

In a second possible implementation manner, after obtaining a label from the label resource pool, the sending end may encapsulate the obtained label and the service data to be sent into a first data packet, and send the first data packet to the receiving end. A packet of data. That is, the first data packet includes the acquired label and the service data to be sent.

For example, if the tag is in the tag resource pool, the tag is obtained from the tag resource pool, and the tag is configured to obtain the tag 89 from the tag resource pool, and encapsulate the tag 89 and the service data to be sent into the first data packet, and send the packet to the receiving end. A packet of data.

It should be noted that, in this embodiment, each time a service data is to be sent, a label needs to be obtained from the label resource pool, and only after successfully obtaining a label from the label resource pool The obtained label and the service data to be sent are encapsulated into a first data packet, and the first data packet is sent to the receiving end, and if the label is not obtained from the label resource pool, the sending The terminal will suspend the sending of the service data until the tag is successfully obtained from the tag resource pool, and then the obtained tag and the service data to be sent are encapsulated into the first data packet, and the first data is sent to the receiving end. package.

In addition, the number of initial labels in the label resource pool may indicate the total service data processing capability of the receiving end, and each time the transmitting end needs to obtain a label from the label resource pool before sending the service data, the label resource is already obtained from the label resource. The number of tags that are sent out of the pool is the number of packets that have been sent by the sender. It can indicate the number of packets that the receiver is currently processing. It can reflect the service data processing capability currently occupied by the receiver, but in the label resource pool. The number of remaining labels is the number of data packets that the sender can also send, which can indicate the current idle data processing capability of the receiver.

Further, in order to ensure that the number of remaining labels in the label resource pool can accurately indicate the current service data processing capability of the receiving end, the sending end may also acquire the label after obtaining a label from the label resource pool each time. The label is deleted from the label resource pool, so that the number of labels in the label resource pool decreases as the data of the to-be-sent service of the sender decreases. Therefore, the number of data packets sent by the sender can be controlled according to the number of remaining labels. The flow control of the sending end is implemented, thereby ensuring that the number of data packets being processed at any time does not exceed the upper limit of the processing data processing capability of the receiving end, and the flow control is achieved.

In addition, the sending end may use the related protocol between the sending end and the receiving end to send the first data packet to the receiving end, or send the first data packet to the switch, where the first data packet is sent by the switch. The embodiment of the present invention does not limit the forwarding to the receiving end.

803. The receiving end receives the first data packet sent by the sending end, and processes the service data according to the current service data processing capability.

In a first possible implementation, the first data packet sent by the sending end includes service data, and the receiving end may receive the first data packet sent by the sending end, and decapsulate the first data packet to obtain The business data in the first data packet.

In a second possible implementation manner, the first data packet sent by the sending end includes the acquired label and the service data, and the receiving end may receive the first data packet sent by the sending end, and perform the first data packet. Decapsulation, obtaining the label and service data in the first data packet.

Because the current receiving end has the service data processing capability, the receiving end can directly process the service data based on the current service data processing capability, and obtain the processed indication data without discarding the first data packet.

The indication data is used to indicate a processing result of the service data by the receiving end, and the indicator number The data obtained by processing the service data may be included, or the indication data may also include a success response or a failure response generated after the service data is processed, which is not limited by the embodiment of the present invention.

In the actual application, the receiving end may process the service data in different manners, and the specific processing manner may be determined according to the negotiation between the sending end and the receiving end, or determined according to the default processing manner of the receiving end, or according to the first data packet. The processing mode of the carrying is determined, and the processing manner may include acceleration, calculation, analysis, and the like, which are not limited in the embodiment of the present invention. For example, if the transmitting end requests the receiving end to perform acceleration processing on the service data sent by the receiving end, after receiving the first data packet, the receiving end may perform acceleration processing on the service data to obtain accelerated data.

Optionally, in the first implementation scenario of the embodiment shown in FIG. 8, before step 801, the method further includes:

800. The sending end generates a label resource pool according to the service data processing capability of the receiving end.

In the embodiment of the present invention, in order to avoid the problem of service data transmission failure, the maximum number of data packets that the transmitting end can send to the receiving end is determined according to the service processing capability of the receiving end, and the label resource pool is generated according to the maximum number. The number of initial labels of the label resource pool is equal to the maximum number, so that the number of data packets sent is controlled according to the maximum number, so as to ensure that the number of sent data packets does not exceed the service data processing capability of the receiving end.

The service data processing capability of the receiving end may be all the service data processing capability of the receiving end, and may also be the service data processing capability that the sending end applies for from the receiving end, which is not limited in this embodiment of the present invention.

Specifically, the sending end generates a label resource pool according to the service data processing capability of the receiving end, including: the sending end calculates a transmission delay time between the transmitting end and the receiving end, and a time when the receiving end processes a data packet, and calculates a The total processing time of the data packet is obtained, and the service data processing capability of the receiving end is used to indicate the maximum number of data packets processed by the receiving end in a unit time, and the service data processing capability and the one data are calculated. The product of the total processing time of the packet can obtain the maximum number of data packets processed by the receiving end in the total processing time, and the total processing capability value of the receiving end in the total processing time is generated according to the total processing capability value. The tag resource pool is such that the number of tags of the newly generated tag resource pool is equal to the total processing capability value to indicate that the initial tag number in the tag resource pool is equal to the total processing capability value.

The transmission delay time is the time required for the transmitter to transmit a data packet between the sender and the receiver, and the time for processing a data packet is the time elapsed since the receiver starts processing the data to complete the processing. The total processing time of the one packet is to send a packet from the sender. The time required to receive the data packet returned after the receiving end processing is completed is the sum of the transmission delay time and the processing time.

The generating the label resource pool according to the total processing capability value includes: the sending end uses the obtained total processing capability value as the initial label number, generates a label corresponding to the initial label number, and establishes a label resource pool. The established label resource pool includes a label corresponding to the initial number of labels, so that the sending of the data packet is restricted according to the label in the label resource pool in a subsequent process.

For the sake of distinction, the sender can mark multiple tags according to the sequence number. For example, if the number of initial labels is 100, the sender may establish a label resource pool, where the label resource pool includes labels Tag0-Tag99.

In addition, the maximum number of data packets processed by the receiving end per unit time can be determined according to the packet processing rate of the receiving end. Then, the initial number of labels in the label resource pool can be derived from the following formula:

Num=Packet·Rate×(T ₁ +T ₂ );

Among them, Num is the initial number of labels, Packet·Rate is the packet processing rate of the receiving end, T ₁ is the transmission delay time between the transmitting end and the receiving end, and T ₂ is the processing time of the receiving end for one data packet.

Assume that the packet processing rate of the receiving end is 100000 pps (packet per second), indicating that the maximum number of data packets processed in the receiving end 1s is 100000, and the maximum number of data packets processed by the receiving end within 1 ms. The number is 100. Assuming that the receiving end has a processing time of 5 ms for one data packet and a transmission delay time of 5 ms, the total processing time of the receiving end for one data packet is 10 ms. Calculating the product between the maximum number of 100 and the total processing time of 10 ms, the total processing capacity of the receiving end is 1000, and the initial number of labels is determined to be 1000.

The calculated initial number of tags can indicate the maximum number of data packets that the receiving end can process in the total processing time of the transmitting end, that is, the total service data processing capability of the receiving end in the total processing time. During the total processing time, if the number of data packets sent by the sender does not reach the initial number of labels, the total service data processing capability of the receiver is not exceeded.

Optionally, in combination with the first implementation scenario of the embodiment shown in FIG. 8 or the foregoing embodiment shown in FIG. 8, in the second implementation scenario of the embodiment shown in FIG. 8, the method further includes:

804. The receiving end sends a second data packet to the sending end, where the second data packet includes a label in the first data packet and indication data obtained by processing the service data in the first data packet.

After the receiving end processes the service data in the first data packet to obtain the indication data, the label in the first data packet and the indication data may be performed. Encapsulating into a second data packet and transmitting the second data packet to the transmitting end.

Based on the example of step 802, after receiving the first data packet, the receiving end may decapsulate the first data packet to obtain Tag89 and service data, and the receiving end may process the service data to obtain the processed data. Indicating data, and the Tag89 and the indication data are encapsulated into a second data packet, and the second data packet is sent to the transmitting end.

Further, after step 804, the method further includes:

805. The sending end receives the second data packet sent by the receiving end, and collects the label in the second data packet into the label resource pool.

After receiving the second data packet sent by the receiving end, the sending end may decapsulate the second data packet to obtain the label in the second data packet and the processed indication data. After the processing of the service data is completed, the service data processing capability of the service data is released, and the sender reclaims the decapsulated label into the label resource pool, thereby ensuring the label resource. The number of labels in the pool decreases as the data to be sent of the sender decreases, and increases with the label collection. The number of labels in the label resource pool accurately indicates the current service data processing capability of the receiver, and the label resource pool. The presence of a tag can accurately indicate that the sender currently has the right to send service data to the receiver. In addition, the recycling of the label can also ensure that the labels that have been used in the subsequent process can be reused, saving label resources.

In the related art, since the transmitting end may send multiple service data, and the detailed information of different service data is inconvenient to distinguish, the transmitting end needs to carry the detailed information of the service data when transmitting the service data, and the receiving end returns the indication data. It is also necessary to return the detailed information, and the transmitting end can determine which detailed information of the detailed information of the business data is. That is, the transmission information needs to be carried in the transmission process between the transmitting end and the receiving end, which will occupy a certain bandwidth.

In the embodiment of the present invention, in order to avoid occupying bandwidth, the sending end may store the detailed information of the service data after acquiring the label from the label resource pool, and establish a correspondence between the label and the detailed information, and mark the details of the service data by using the label. information. In the subsequent process, after receiving the second data packet returned by the receiving end, and obtaining the label carried in the second data packet, the sending end may query the detailed information corresponding to the label according to the corresponding relationship. In the transmission process between the sender and the receiver, the detailed information does not need to be carried, which saves bandwidth.

The detailed information includes at least a memory address of the service data, and may further include a sender ID (Identification), a queue number of the service data, and the like. The detailed information in the embodiment of the present invention is not limited.

Optionally, after receiving the second data packet, the sending end obtains the label and the indication data carried in the second data packet, and may query the memory address corresponding to the label according to the corresponding relationship, and store the returned data according to the memory address. Indicate the data. In this way, not only the problem of flow control is solved, but also the record of the transmitted service data information can be realized, and the design requirements of the distributed system are satisfied.

Alternatively, after receiving the second data packet and obtaining the label and the indication data carried in the second data packet, the sending end may further query the memory address corresponding to the label according to the corresponding relationship, and recover the memory according to the memory address. The memory space indicated by the address, so that the memory space is applied to other business data to be sent later, which saves memory resources.

For example, after obtaining the tag 89 from the tag resource pool, the sending end may store the detailed information such as the queue number, the memory address, and the sender ID of the service data to be sent, and establish Tag89 and the detailed information. Corresponding relationship, the Tag89 and the service data are encapsulated into a first data packet not including the detailed information, and the first data packet is sent to the receiving end. When the sending end receives the second data packet including the Tag89 and the indication data, the memory address corresponding to the Tag89 may be queried according to the established correspondence relationship, and the memory space indicated by the memory address is recovered according to the queried memory address.

Further, the sending end may start timing when the sending end acquires a label from the label resource pool, and when the timing duration reaches a preset duration, it is determined whether the acquired label has been recycled to the label resource pool. If the obtained label has not been recycled to the label resource pool, it means that the label collection timeout, the first data packet may have been lost, or the receiving end may be abnormal, and the business data cannot be processed or the second data packet cannot be returned. Then, in order to prevent the service data from being processed and to avoid reducing the number of tags when the new service data is not sent, the tag resource pool can regenerate the corresponding tag and regenerate according to the regenerated tag and service data. Transmitting, by the first data packet, the regenerated first data packet to the receiving end, the transmitting end receiving the regenerated first data packet, and reprocessing the service data, and returning the processed indication data and the corresponding label So that the receiver can recycle the label to the label resource pool.

The preset duration may be set by the sending end according to the general duration of obtaining the label from the label resource pool to the label resource pool, or may be based on the transmission delay time between the sending end and the receiving end. The specific setting of the processing time of a data packet is not limited in this embodiment of the present invention.

The sender can also determine whether the receiver is in place according to whether the label is reclaimed. If the label reclaims timeout, it indicates that the receiver may not be started or an abnormality occurs, that is, the receiver cannot work normally. Then, the status of the receiving end can be determined as not being in place. If the label does not have a recovery timeout, it indicates that the receiving end can work normally, and the status of the receiving end can be determined to be in place. The sending end may also collect the actual duration from the time the label is acquired to the collection of the label, and the actual duration is used as a processing delay for processing the corresponding service data by the receiving end, and the receiving is determined according to the processing delay. The current running state of the terminal, and uploading the current running state of the receiving end to the upper layer software, or statistically analyzing the change of the processing delay of the receiving end, uploading to the upper layer software, thereby eliminating the need to send special probe data to the current end of the receiving end. The running status is detected, which saves the detection resources.

In addition, when the timer duration reaches the preset duration, if the label has not been recycled to the label resource pool, the receiver may not regenerate the first data packet, and cancel the processing of the service data again. Moreover, in order to avoid memory leakage, the transmitting end may query the detailed information corresponding to the label according to the correspondence, determine the memory space indicated by the memory address according to the memory address included in the detailed information, and recover the memory space.

In an actual application, the sending end may identify an abnormal condition of the label collection timeout. When the abnormal condition is identified, the retransmission mechanism is directly triggered to resend the first data packet, or the memory is reclaimed according to the memory address in the detailed information. The memory space indicated by the address. Alternatively, when the label collection timeout occurs, the sender may also report an exception to the upper layer software, and the upper layer software determines whether to send the first data packet again or to reclaim the memory space, and the sender may trigger the retransmission mechanism according to the instruction of the upper layer software. Or reclaim the memory space indicated by the memory address.

The above method can ensure that the number of data packets being processed by the receiving end does not exceed the processing upper limit at any time, and achieves the purpose of flow control, ensuring the accuracy and real-time performance of the flow control, and at the same time, the transmitting end can process according to the real-time processing of the receiving end. The result is to decide whether to send the first data packet and implement autonomous flow control. The receiving end does not return the label when the processing is not completed, so that the sending end cannot reclaim the label. If the receiving end does not currently have the service data processing capability, the number of remaining labels of the transmitting end is 0, so that the transmitting end can be controlled to suspend the sending service. Data, the back pressure on the sender is achieved.

It should be noted that the embodiment of the present invention is only an example of performing data packet transmission between a transmitting end and a receiving end. In practical applications, the method can also be applied to a complex system of multiple transmitting ends or multiple receiving ends. And networking environments, such as distributed systems.

In the distributed system, the data provided by the embodiment of the present invention can be used for data transmission between any of the transmitting ends and any receiving end to ensure the flow control of each node in the system, ensuring reliability, and can also be applied to the transmitting end. Specific business data, with high flexibility to meet the diversity needs.

In addition, in a distributed system including a plurality of transmitting ends and a plurality of receiving ends, due to a single receiving end The service data of multiple senders needs to be processed at the same time. If the data traffic between multiple senders and receivers is controlled by backpressure, the service data sent by one sender exceeds the service data of the receiver. When the capability is enabled, the receiving end will backpressure the data channel with all the transmitting ends, causing all the transmitting ends to suspend the transmission of service data, thereby affecting the normal processing of the service data of other transmitting ends.

In the embodiment of the present invention, in a distributed system, multiple senders can perform traffic control by themselves, and each sender can control the number of data packets sent according to the service data processing capability that each party applies to the receiver, It affects other senders and facilitates the orderly management of each sender in a distributed system. It can adapt to complex networking scenarios and has high flexibility.

The method provided by the embodiment of the present invention, after the label is present in the label resource pool, that is, the sender currently has the right to send the service data to the receiving end, and obtains a label from the label resource pool, according to the service data to be sent. Sending the first data packet, so that after receiving the first data packet, the receiving end can process the service data based on the current service data processing capability, and ensure that the sending end can send the service data processing capability if the receiving end currently has the service data processing capability. Business data, so as to avoid exceeding the current business data processing capability of the receiving end, avoiding the problem of transmission failure, improving the transmission success rate and improving flexibility.

In addition, by recycling the label returned by the sender to the label resource pool, the number of remaining labels in the label resource pool can accurately indicate the current service data processing capability of the receiver, and the accuracy is improved; and the service data is marked by the label. The detailed information does not need to carry the detailed information when the first data packet is sent, and can also determine the detailed information of the service data, which saves bandwidth and improves flexibility; if the label recycling timeout, the corresponding label is regenerated, and according to the re The generated label and the service data regenerate the first data packet, and send the regenerated first data packet to the receiving end, thereby avoiding the problem that the service data processing fails, and avoiding reducing when the receiving end does not process the service data. The problem of the number of tags ensures that the number of remaining tags can accurately indicate the current service data processing capability of the receiving end and improve the accuracy.

FIG. 9 is a flowchart of a data sending method according to an embodiment of the present invention. The execution body of the embodiment of the present invention is a transmitting end. Referring to FIG. 9, the method includes the following steps:

901. The sender obtains a label from the label resource pool, and the label in the label resource pool indicates that the sender currently has the right to send service data to the receiver.

902. The sending end generates a first data packet according to the to-be-sent service data of the sending end.

903. The sending end sends the first data packet to the receiving end.

Optionally, the sending end obtains a label from the label resource pool, including:

If the sender determines that at least one tag exists in the tag resource pool, a tag is obtained from the tag resource pool.

Optionally, before the sending end generates the first data packet according to the to-be-sent service data of the sending end, the method further includes:

Optionally, the generating the label resource pool according to the service data processing capability of the receiving end, including:

The sending end acquires the service data processing capability of the receiving end, where the service data processing capability is used to indicate the maximum number of data packets processed by the receiving end in a unit time;

The tag resource pool is generated according to the total processing capability value, and the tag resource pool has a label number equal to the total processing capability value.

Optionally, the method further includes:

The obtained tag is deleted from the tag resource pool.

Optionally, the method further includes:

Receiving, by the sending end, the second data packet sent by the receiving end, where the second data packet includes the acquired label and the indication data obtained by processing the service data, where the indication data is used to indicate that the receiving end is to the service data. process result;

The acquired label included in the second data packet is recycled to the label resource pool.

Optionally, after the sending, by the sending end, the first data packet, according to the acquired label and the to-be-sent service data of the terminal, the method further includes:

The sending end acquires a memory address corresponding to the label according to the correspondence relationship;

The sender reclaims the memory space indicated by the memory address according to the memory address.

Optionally, the method further includes:

When the sender performs a label acquisition from the label resource pool, the sender starts timing;

If the timeout period reaches the preset duration, and the acquired label is not reclaimed into the label resource pool, the sender regenerates the label, and regenerates the first data packet according to the regenerated label and the service data. Sending the regenerated first data packet to the receiving end.

FIG. 10 is a flowchart of a data receiving method according to an embodiment of the present invention. The executor of the embodiment of the present invention may be a receiving end. Referring to FIG. 10, the method includes the following steps:

1001: The receiving end receives the first data packet sent by the sending end, where the first data packet is generated by the sending end from the label resource pool, and is generated according to the service data to be sent, where the label in the label resource pool indicates that the sending end is current. Have the right to send business data to the receiving end;

1002. The receiving end processes the service data based on the current service data processing capability.

The method provided by the embodiment of the present invention can receive the first data packet sent to the receiving end on the premise that the transmitting end has the right to send the service data to the receiving end, and can be based on the current service data processing capability in the first data packet. The processing of the service data ensures that the data packet sent by the sender does not exceed the current service data processing capability of the receiving end, avoids the problem of transmission failure, improves the transmission success rate, and improves flexibility.

Optionally, the method further includes:

The receiving end sends a second data packet to the sending end, where the second data packet includes a label in the first data packet and indication data obtained by processing the service data in the first data packet, where the indication data is used to indicate The result of processing the service data by the receiving end.

Those skilled in the art can understand that all or part of the steps of implementing the above embodiments can be The completion of the hardware may also be performed by a program to instruct related hardware. The program may be stored in a computer readable storage medium. The storage medium mentioned above may be a read only memory, a magnetic disk or an optical disk.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are within the spirit and scope of the present invention, should be included in the scope of the present invention. within.

Claims

A data transmitting method, characterized in that the method comprises:

The sending end obtains a label from the label resource pool, and the label in the label resource pool indicates that the sending end currently has the right to send the service data to the receiving end;

The sending end generates a first data packet according to the to-be-sent service data of the sending end;

The sending end sends the first data packet to the receiving end.
The method of claim 1 wherein said first data packet comprises said acquired tag and said service data.
The method according to claim 1, wherein the sender obtains a label from the label resource pool, including:

And if the sending end determines that at least one label exists in the label resource pool, obtaining a label from the label resource pool.
The method according to claim 1, wherein before the generating end generates the first data packet according to the to-be-sent service data of the sending end, the method further includes:

Generating the label resource pool according to the service data processing capability of the receiving end.
The method according to claim 4, wherein the generating the label resource pool according to the service data processing capability of the receiving end comprises:

The transmitting end calculates a total processing time of the one data packet according to a transmission delay time between the transmitting end and the receiving end, and a time when the receiving end processes one data packet;

The sending end acquires a service data processing capability of the receiving end, where the service data processing capability is used to indicate a maximum number of data packets processed by the receiving end in a unit time;

The sending end uses the product of the service data processing capability and the total processing time of the one data packet as the total processing capability value of the receiving end;

And generating, by the total processing capability value, the label resource pool, where the label resource pool has a label number equal to the total processing capability value.
The method according to any one of claims 1 to 5, wherein the method further comprises:

The obtained tag is deleted from the tag resource pool.
The method of claim 6 wherein the method further comprises:

Receiving, by the sending end, the second data packet sent by the receiving end, where the second data packet includes the acquired label and indication data obtained by processing the service data, where the indication data is used to indicate the The processing result of the service data by the receiving end;

Retrieving the acquired tag included in the second data packet to the tag resource pool.
The method according to claim 7, wherein after the generating, by the sending end, the first data packet, according to the acquired label and the to-be-sent service data of the terminal, the method further includes:

The sending end stores the detailed information of the service data, where the detailed information includes a memory address of the service data to be sent;

The sending end establishes a correspondence between the label and the detailed information;

After the sending end receives the second data packet sent by the receiving end, the method further includes:

The sending end acquires a memory address corresponding to the label according to the corresponding relationship;

The sending end recovers the memory space indicated by the memory address according to the memory address.
The method of any of claims 6-8, wherein the method further comprises:

When the sending end performs obtaining a label from the label resource pool, the sending end starts timing;

If the time period reaches a preset duration, and the acquired label is not reclaimed into the label resource pool, the sending end regenerates the label, and regenerates according to the regenerated label and the service data. Transmitting, by the first data packet, the regenerated first data packet to the receiving end.
A data receiving method, characterized in that the method comprises:

The receiving end receives the first data packet sent by the sending end, and the first data packet is generated by the sending end by acquiring a label from the label resource pool, and is generated according to the to-be-sent service data, where the label resource pool has a label indicating the sending The terminal currently has the right to send service data to the receiving end;

The receiving end processes the service data based on the current service data processing capability.
The method of claim 10, wherein the method further comprises:

The receiving end sends a second data packet to the sending end, where the second data packet includes a label in the first data packet and indication data obtained by processing the service data in the first data packet, where The indication data is used to indicate a processing result of the service data by the receiving end.
A data transmitting apparatus, wherein the data transmitting apparatus is applied to a transmitting end, and the apparatus includes:

a label obtaining module, configured to obtain a label from a label resource pool, where the label in the label resource pool indicates that the sending end currently has the right to send service data to the receiving end;

a data packet generating module, configured to generate a first data packet according to the to-be-sent service data of the sending end;

And a sending module, configured to send, to the receiving end, the first data packet generated by the data packet generating module.
The apparatus of claim 12, wherein the first data packet comprises the acquired tag and the service data.
The device according to claim 12, wherein the tag obtaining module is further configured to: obtain a tag from the tag resource pool if it is determined that at least one tag exists in the tag resource pool.
The device of claim 12, wherein the device further comprises:

The label resource pool generating module is configured to generate the label resource pool according to the service data processing capability of the receiving end.
The device according to claim 15, wherein the tag resource pool generating module is further configured to: according to a transmission delay time between the transmitting end and the receiving end, and the receiving end processing a data packet Time, calculating a total processing time of the one data packet; acquiring a service data processing capability of the receiving end, where the service data processing capability is used to indicate a maximum number of data packets processed by the receiving end in a unit time; a product of the service data processing capability and the total processing time of the one data packet as a total processing capability value of the receiving end; generating, according to the total processing capability value, the label resource pool, the label of the label resource pool The number is equal to the total processing power value.
The device according to any one of claims 12-16, wherein the device further comprises:

And a deleting module, configured to delete the label acquired by the label obtaining module from the label resource pool.
The device according to claim 17, wherein the device further comprises:

a receiving module, configured to receive a second data packet sent by the receiving end, where the second data packet includes the acquired label and indication data obtained by processing the service data, where the indication data is used to indicate Decoding the processing result of the service data by the receiving end;

The label collection module is configured to collect the label acquired by the label acquisition module included in the second data packet received by the receiving module into the label resource pool.
The device of claim 18, wherein the device further comprises:

a storage module, configured to store detailed information of the service data, where the detailed information includes a memory address of the service data to be sent;

Establishing a relationship module, configured to establish a correspondence between the label and the detailed information;

a memory address obtaining module, configured to acquire a memory address corresponding to the label according to the correspondence established by the establishing relationship module;

The memory space recovery module is configured to recover the memory space indicated by the memory address according to the memory address obtained by the memory address acquisition module.
The device according to any one of claims 17 to 19, wherein the device further comprises:

a timing module, configured to start timing when the label obtaining module acquires a label from the label resource pool;

a label generating module, configured to regenerate the label if the timing of the timing module reaches a preset duration and the label acquired by the label obtaining module is not recycled to the label resource pool;

The data packet generating module is further configured to regenerate the first data packet according to the label and the service data regenerated by the label generation module;

The sending module is further configured to send, to the receiving end, a first data packet that is regenerated by the data packet generating module.
A data receiving device, wherein the data receiving device is applied to a receiving end, The device includes:

a receiving module, configured to receive a first data packet sent by the sending end, where the first data packet is generated by the sending end from the label resource pool, and is generated according to the service data to be sent, where the label resource pool has a label representation The sending end currently has the right to send service data to the receiving end;

The processing module is configured to process the service data in the first data packet received by the receiving module based on the current service data processing capability.
The device of claim 21, wherein the device further comprises:

a sending module, configured to send a second data packet to the sending end, where the second data packet includes a label in the first data packet and indication data obtained by processing the service data in the first data packet, The indication data is used to indicate a processing result of the service data by the receiving end.
A data transmission system, characterized in that the system comprises: a receiving end and at least one transmitting end;

Each of the sending ends is configured to obtain a label from the label resource pool, where the label in the label resource pool indicates that the sending end currently has the right to send the service data to the receiving end; and the generating end is generated according to the to-be-sent service data of the sending end. a first data packet; the first data packet is sent to the receiving end.

The receiving end is configured to receive a first data packet sent by any sending end, and process the service data in the received first data packet according to a current service data processing capability.
The system according to claim 23, wherein the sending end of the first data packet is further configured to delete the acquired label from the label resource pool;

The sending end of the first data packet is further configured to receive the second data packet returned by the receiving end, and collect the label in the second data packet into the label resource pool.
The system of claim 23 wherein said system is a distributed system, said distributed system comprising a plurality of transmitting ends and said receiving end.