Transmission control method and device, equipment, chip and medium

Abstract

The invention provides a transmission control method and device, equipment, a chip and a medium, and the method comprises the steps: transmitting first information which is used for indicating to stop transmitting a heartbeat packet; length change information between first data and second data is obtained, the first data is used for communicating with an application server, and the second data comprises a heartbeat packet; and sending the third data according to the length change information. The technical problem that data transmission performance is affected due to sequence out-of-step of data of an application side and data of a network side in the prior art is solved.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular, to a transmission control method, apparatus, device, chip, and medium. Background Art

[0002] An application processor and a communication processor can be deployed in a terminal. The application processor can execute application functions, while the communication processor can execute communication functions. Some network applications (which can also be referred to as application programs) can maintain a long connection with their application servers by sending periodic heartbeat packets. In the case of no user operation such as late at night or when the screen is blacked out, in order to send heartbeat packets, the network application usually wakes up the application processor periodically and sends heartbeat packets, and finally sends the heartbeat packets to the network side through the communication processor.

[0003] In the related art, the heartbeat packet can be moved to the communication processor, and the communication processor can proxy the application to send the heartbeat packet. That is, the communication processor can directly send the heartbeat to the network side periodically without waking up the application processor, reducing the power consumption of the application processor.

[0004] In this way, when the communication processor sends a heartbeat packet, it will adjust the Transmission Control Protocol (TCP) sequence, which will cause the sequence out-of-sync between the data on the application side and the data on the network side, affecting the data transmission performance. Summary of the Invention

[0005] The present disclosure aims to solve at least one of the technical problems in the related art to some extent.

[0006] To this end, the present disclosure provides a transmission control method, apparatus, communication device, chip, and storage medium, which can synchronize the sequences of the data on the application side and the data on the network side, thereby improving the data transmission performance.

[0007] An embodiment of the first aspect of the present disclosure provides a transmission control method, including: sending a first message, where the first message is used to indicate to stop sending heartbeat packets; obtaining length change information between a first data and a second data, where the first data is used to communicate with an application server, and the second data includes: heartbeat packets; and sending a third data according to the length change information.

[0008] An embodiment of the second aspect of the present disclosure provides a transmission control method, including: receiving a first message, where the first message is used to indicate to stop sending heartbeat packets; stopping sending heartbeat packets according to the first message; and receiving a third data, where the third data is determined based on the length change information between a first data and a second data, the first data is used to communicate with an application server, and the second data includes: heartbeat packets.

[0009] The third - aspect embodiment of the present disclosure provides a transmission control device, including: a first transceiver module, configured to send a first piece of information, where the first piece of information is used to indicate stopping sending heartbeat packets; an acquisition module, configured to acquire the length change information between a first piece of data and a second piece of data, where the first piece of data is used to communicate with an application server, and the second piece of data includes: heartbeat packets; a second transceiver module, configured to send a third piece of data according to the length change information.

[0010] The fourth - aspect embodiment of the present disclosure provides a transmission control device, including: a third transceiver module, configured to receive a first piece of information, where the first piece of information is used to indicate stopping sending heartbeat packets; a control module, configured to stop sending heartbeat packets according to the first piece of information; a fourth transceiver module, configured to receive a third piece of data, where the third piece of data is determined based on the length change information between a first piece of data and a second piece of data, the first piece of data is used to communicate with an application server, and the second piece of data includes: heartbeat packets.

[0011] The fifth - aspect embodiment of the present disclosure provides a communication device, including: a processor, and a memory communicatively connected to the processor; the memory stores computer - executable instructions; the processor executes the computer - executable instructions stored in the memory to implement the transmission control method proposed in the first - aspect embodiment of the present disclosure, or to implement the transmission control method proposed in the second - aspect embodiment of the present disclosure.

[0012] The sixth - aspect embodiment of the present disclosure provides a chip, the chip includes a processing circuit and an interface circuit; wherein, the interface circuit is configured to read instructions, and the interface circuit sends the instructions to the processing circuit, so that the processing circuit executes the transmission control method proposed in the first - aspect embodiment of the present disclosure, or executes the transmission control method proposed in the second - aspect embodiment of the present disclosure.

[0013] The seventh - aspect embodiment of the present disclosure provides a computer - readable storage medium, in which computer - executable instructions are stored, and when the computer - executable instructions are executed by a processor, they are used to implement the transmission control method proposed in the first - aspect embodiment of the present disclosure, or to implement the transmission control method proposed in the second - aspect embodiment of the present disclosure.

[0014] The transmission control method, device, communication device, chip and storage medium provided by the present disclosure send a first message, where the first message is used to indicate to stop sending heartbeat packets, and obtain the length change information between the first data and the second data, where the first data is used to communicate with the application server, and the second data includes: heartbeat packets, and send the third data according to the length change information. Since the first data is the data for communicating with the application server before sending the heartbeat packets, the length change information between the second data and the first data after sending the heartbeat packets is detected, and the third data is sent based on the length change information, thus realizing the sequence synchronization of the data on the application side and the data on the network side, thereby improving the data transmission performance.

[0015] Additional aspects and advantages of the present disclosure will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present disclosure. Description of the Drawings

[0016] The above and / or additional aspects and advantages of the present disclosure will become apparent and be readily understood from the following description of the embodiments in conjunction with the drawings, where:

[0017] Figure 1 is a schematic diagram of the architecture of a communication system shown according to an embodiment of the present disclosure;

[0018] Figure 2 is a schematic flowchart of a transmission control method provided by an embodiment of the present disclosure;

[0019] Figure 3 is a schematic flowchart of another transmission control method provided by an embodiment of the present disclosure;

[0020] Figure 4 is a schematic flowchart of another transmission control method provided by an embodiment of the present disclosure;

[0021] Figure 5 is a schematic flowchart of another transmission control method provided by an embodiment of the present disclosure;

[0022] Figure 6 is a schematic diagram of a heartbeat packet proxy in an embodiment of the present disclosure;

[0023] Figure 7 is a schematic flowchart of a transmission control method in an embodiment of the present disclosure;

[0024] Figure 8 is a schematic diagram of starting to send proxy messages in an embodiment of the present disclosure;

[0025] Figure 9 is a schematic flowchart of a heartbeat packet sending process in an embodiment of the present disclosure;

[0026] Figure 10 Schematic structural diagram of a transmission control device provided by an embodiment of the present disclosure;

[0027] Figure 11 Schematic structural diagram of another transmission control device provided by an embodiment of the present disclosure;

[0028] Figure 12 Block diagram of an exemplary communication device suitable for implementing the embodiments of the present disclosure;

[0029] Figure 13 Schematic structural diagram of a chip proposed by an embodiment of the present disclosure;

[0030] Figure 14 Schematic structural diagram of another chip proposed by an embodiment of the present disclosure. Detailed implementation manners

[0031] The embodiments of the present disclosure will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present disclosure, and should not be construed as a limitation to the present disclosure.

[0032] In the embodiments of the present disclosure, the communication device may be, for example, a terminal or a chip, and there is no limitation thereto.

[0033] In the embodiments of the present disclosure, the chip may be, for example, an application processor or a communication processor, and there is no limitation thereto.

[0034] Figure 1 Schematic architecture diagram of a communication system shown according to an embodiment of the present disclosure. As Figure 1 shown, the communication system 100 may include a terminal 101 and a network device 102. The network device 102 may include at least one of an access network device and a core network device.

[0035] In some embodiments, the terminal 101 includes, for example, at least one of a mobile phone, a wearable device, an Internet of Things device, an automobile with communication function, a smart automobile, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, and a wireless terminal in smart home, but is not limited thereto.

[0036] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of an evolved NodeB (eNB) in a 5G communication system, a next-generation eNB (ng-eNB), a next generation NodeB (gNB), a NodeB (NB), a home NodeB (HNB), a home evolved NodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an Open RAN, a Cloud RAN, a base station in other communication systems, and an access node in a WiFi system, but is not limited thereto.

[0037] In some embodiments, the technical solution of the present disclosure is applicable to the Open RAN architecture. At this time, the interfaces between or within the access network devices involved in the embodiments of the present disclosure may become the internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0038] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). Among them, the CU may also be referred to as a control unit. Adopting the CU-DU architecture can split the protocol layers of the access network device. The functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all protocol layers are distributed in the DU. The CU centrally controls the DU, but it is not limited thereto.

[0039] In some embodiments, the core network device may be a single device including one or more network elements, or may be multiple devices or a group of devices, each including all or part of one or more network elements. The network elements may be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0040] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly explaining the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions proposed in the embodiments of the present disclosure. Those of ordinary skill in the art know that with the evolution of the system architecture and the emergence of new service scenarios, the technical solutions proposed in the embodiments of the present disclosure are equally applicable to similar technical problems.

[0041] The following embodiments of the present disclosure can be applied to Figure 1 the communication system 100 shown, or a part of the main body, but it is not limited thereto. Figure 1 Each main body shown is an illustration. The communication system may include Figure 1 all or part of the main bodies, or may include Figure 1 other main bodies outside. The number and form of each main body are arbitrary. The connection relationships between the main bodies are illustrations. The main bodies may not be connected or may be connected. Their connections may be in any way, either directly or indirectly, either wired or wireless.

[0042] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other communication methods, next-generation systems extended based on them, etc. In addition, combinations of multiple systems (for example, combinations of LTE or LTE-A and 5G, etc.) can also be applied.

[0043] In the related art, the heartbeat packet can be moved to the communication processor, and the communication processor can proxy the application to send the heartbeat packet. That is, the communication processor can directly send the heartbeat to the network side periodically without waking up the application processor, reducing the power consumption of the application processor. In this way, when the communication processor sends the heartbeat packet, it will adjust the TCP sequence, which will cause the sequence of data on the application side and the network side to be out of sync, affecting the data transmission performance.

[0044] In the embodiments of the present disclosure, in order to solve the above technical problems, by sending a first message, where the first message is used to indicate to stop sending the heartbeat packet, and obtaining the length change information between the first data and the second data, where the first data is used to communicate with the application server, and the second data includes: the heartbeat packet, and sending the third data according to the length change information. Since the first data is the data communicated with the application server before sending the heartbeat packet, and the length change information between the second data and the first data after sending the heartbeat packet is detected, and the third data is sent based on the length change information, thus, the sequence synchronization of the data on the application side and the network side is achieved, thereby improving the data transmission performance.

[0045] The data in the embodiments of the present disclosure can be, for example, the Transmission Control Protocol (TCP) sequence.

[0046] The embodiments of the present disclosure can be applied to the scenario where the communication processor proxies the application processor to send the heartbeat packet, and there is no limitation in this regard.

[0047] Figure 2 It is a schematic flow diagram of a transmission control method provided by the embodiments of the present disclosure.

[0048] The execution subject of this embodiment can be, for example, the application processor, and there is no limitation in this regard.

[0049] As Figure 2 shown, the transmission control method includes:

[0050] Step S201: Send a first message, where the first message is used to indicate to stop sending the heartbeat packet.

[0051] Optionally, in some embodiments, before sending the first message, the application processor can enter the sleep state. Before entering the sleep state, in response to the trigger of the application program, it can indicate the communication processor to proxy the sending of the heartbeat packet.

[0052] Optionally, in some embodiments, the application processor may instruct the communication processor to proxy the sending of heartbeat packets by sending second information to the communication processor. After receiving the second information, the communication processor may send at least one heartbeat packet to the application server in response to the second information to support maintaining a long connection between the application and the application server, without limitation thereto.

[0053] Optionally, in some embodiments, if the application processor is awakened, it may send first information to the communication processor to instruct the communication processor to stop proxying the sending of heartbeat packets, and the communication processor may stop sending heartbeat packets in response to the first information.

[0054] Step S202: Obtain the length change information between the first data and the second data, where the first data is used for communication with the application server, and the second data includes: heartbeat packets.

[0055] The application server refers to the server that provides background services for the application. The application server may be deployed on the network side, without limitation thereto.

[0056] The first data refers to the data transmitted during the communication between the application processor and the application server. The communication between the application processor and the application server may specifically refer to: the application processor communicates with the application server through the communication processor in response to the trigger of the application. By way of example, the first data may be, for example, the communication data between the application processor and the application server before sending the heartbeat packet, and this first data may support the application to use the service provided by the application server, without limitation thereto.

[0057] The second data may refer to the data accumulated on the application server side after the communication processor proxies the sending of one or more heartbeat packets. The second data may at least include: one or more heartbeat packets. The one or more heartbeat packets are proxied by the communication processor to be sent, and the second data may also include the first data. That is to say, the second data may be the data received by the application server after accumulating one or more heartbeat packets on the basis of the first data.

[0058] Optionally, in some embodiments, if the first data can be represented as "XXX", then the second data can be represented as "XXX + n * heartbeat packet size", where n * heartbeat packet size may indicate that the second data can carry at least one heartbeat packet.

[0059] Optionally, in some embodiments, the length change information between the first data and the second data may be detected, and the length change information is used to represent the length change of the second data relative to the first data. If the lengths of the second data and the first data are inconsistent, after the communication processor agent sends a heartbeat packet, it will cause the data on the application side and the data on the network side to be out of sequence (i.e., the sequence numbers are not continuous). Therefore, in the embodiments of the present disclosure, after the communication processor agent sends one or more heartbeat packets, the length change information between the second data and the first data may be detected, and the data on the application side and the data on the network side may be sequence synchronized based on the detected length change information.

[0060] Optionally, in some embodiments, in the process of obtaining the length change information between the first data and the second data, the length change information may be received. For example, after the communication processor agent sends one or more heartbeat packets, the length change information may be indicated to the application processor, and then the application processor may receive the length change information sent by the communication processor.

[0061] Optionally, in some embodiments, in the process of obtaining the length change information between the first data and the second data, the number of heartbeat packets sent may be received, and the length change information may be determined according to the number of heartbeat packets sent. For example, after the communication processor agent sends one or more heartbeat packets, the number of heartbeat packets sent may be indicated to the application processor, and then the application processor may receive the number of heartbeat packets sent by the communication processor, and then may combine the heartbeat packet information (such as the heartbeat packet size, the heartbeat packet length) and the number of heartbeat packets sent to determine the length change information. For example, multiplying the heartbeat packet size by the number of heartbeat packets sent to obtain the length change information, and there is no limitation thereto.

[0062] Thus, the length change information between the second data and the first data after sending the heartbeat packet can be detected flexibly, which is effectively applicable to personalized communication scenarios, and can ensure the detection accuracy of the length change information, and support improving the sequence synchronization accuracy of the data.

[0063] Step S203: Send the third data according to the length change information.

[0064] After obtaining the length change information between the first data and the second data as described above, the third data may be sent based on the length change information, wherein the third data sent based on the length change information is used for data sequence synchronization.

[0065] It can be understood that the sequence numbers of data transmitted during the communication between the application processor and the application server are incremented, and the sequence numbers corresponding to each heartbeat packet transmitted by the communication processor to the application server are also incremented. When the communication processor proxy sends each heartbeat packet, the sequence number of the data carrying each heartbeat packet received on the application server side has already changed incrementally. However, due to the "proxy" behavior of the communication processor, the sequence number of the data transmitted again by the application processor does not increment following the increment of the sequence number of the "data carrying each heartbeat packet", resulting in sequence out-of-sync between the data on the application side and the data on the network side. Therefore, in the embodiments of the present disclosure, the application processor can resend the third data based on the length change information. For example, the length of the third data can be configured to be consistent with the length value indicated by the "length change information" to compensate for the aforementioned sequence out-of-sync.

[0066] In this embodiment, by sending the first information, where the first information is used to indicate to stop sending heartbeat packets and obtain the length change information between the first data and the second data, where the first data is used for communication with the application server, and the second data includes: heartbeat packets, and according to the length change information, sending the third data. Since the first data is the data for communication with the application server before sending the heartbeat packets, and the length change information between the second data and the first data after sending the heartbeat packets is detected, and the third data is sent based on the length change information, sequence synchronization between the data on the application side and the data on the network side is achieved, thereby improving the data transmission performance.

[0067] Optionally, in some embodiments, the application processor may send the interface protocol information of the first data to the communication processor, where the first data and the interface protocol information are used to generate heartbeat packets; and / or the application processor may send reference data to the communication processor, where the reference data is used to determine the interface protocol information. Thereby, the communication processor can correctly generate heartbeat packets and effectively implement the proxy sending of heartbeat packets conforming to the interface protocol of the first data.

[0068] Among them, the interface protocol information can be, for example, the socket information of the TCP sequence.

[0069] Optionally, in some embodiments, the interface protocol information includes at least one of the following: address information; port information; the sequence number of the first data; the header information of the first data. Thereby, it can be ensured that accurate heartbeat packets are constructed.

[0070] Among them, the address information may refer to a physical address or an Internet Protocol (IP) address. The IP address is, for example, a source IP address or a destination IP address. The port information is, for example, a source Port or a destination Port. The sequence number of the first data can be expressed as a TCP Seq number. The header information of the first data may refer to the TCP header information and / or the IP header information of the first data.

[0071] Optionally, in some embodiments, heartbeat packet information is sent, where the first data, the interface protocol information, and the heartbeat packet information are jointly used to generate a heartbeat packet. That is to say, the application processor can send the heartbeat packet information to the communication processor, and the heartbeat packet information is used to describe the heartbeat packet, so as to support the communication processor to accurately proxy and send the heartbeat packet as needed.

[0072] Optionally, in some embodiments, the heartbeat packet information includes at least one of the following: the heartbeat packet size; the heartbeat packet data; the heartbeat packet sending period.

[0073] Optionally, in some embodiments, the application processor can indicate a proxy identifier (proxy ID, heartbeat proxy ID) to the communication processor, and the proxy identifier can be used to indicate the proxy process of a heartbeat packet. The proxy identifier can also be referred to as a heartbeat proxy ID.

[0074] Optionally, in some embodiments, the application processor can indicate a protocol type to the communication processor, and the protocol type is, for example, TCP or IP. The application processor can also indicate security information to the communication processor, and the security information can be used for integrity and encryption, which is not limited herein.

[0075] Figure 3 It is a schematic flowchart of another transmission control method provided by an embodiment of the present disclosure.

[0076] The execution subject of this embodiment can be, for example, an application processor, which is not limited herein.

[0077] As Figure 3 shown, the transmission control method includes:

[0078] Step S301: Send first information, where the first information is used to indicate to stop sending heartbeat packets.

[0079] Step S302: Obtain the length change information between the first data and the second data, where the first data is used to communicate with the application server, and the second data includes: heartbeat packets.

[0080] For the descriptions of S301 - S302, reference can be specifically made to the above embodiments, which will not be elaborated herein.

[0081] Step S303: Generate at least one third data according to the length change information and the first data, where the size of the third data is less than or equal to the size of the Maximum Transmission Unit (MTU).

[0082] Optionally, in some embodiments, the MTU can be used to indicate the maximum size of the data service unit that the other party can accept. When implementing the generation of the third data, in order to ensure that each third data can be correctly received, one or more third data can be generated based on the MTU and the length change information. For example, if the length change information is less than or equal to the MTU, one third data that conforms to the length change information can be generated. If the length change information is greater than the MTU, multiple third data are generated, that is, sent in multiple packets, and each third data can carry several data packets for sequence synchronization. In each third data, packet information can also be included, such as the number of data packets for this synchronization and the packet index, which is not limited.

[0083] Step S304: Send at least one third data.

[0084] After generating one or more third data as described above, the third data can be sent or sent sequentially to synchronize the data on the application side and the data on the network side.

[0085] Step S305: Stop sending the third data when the acknowledgment information corresponding to all the third data has been received, where the acknowledgment information is used to indicate that the third data has been received.

[0086] Optionally, in some embodiments, after receiving the third data, if the communication processor confirms that the third data has been correctly received, it can feedback an acknowledgment information to the application processor to notify the application processor that the third data for this synchronization has been received. If the application processor learns that the acknowledgment information corresponding to all the third data has been received, it stops sending the third data, thereby completing the sequence synchronization of the data on the application side and the data on the network side. Then, the application processor can, in response to the trigger of the application program, send the data for communication to the application server again through the communication processor.

[0087] In this embodiment, by sending a first message, where the first message is used to indicate stopping sending heartbeat packets, and obtaining the length change information between the first data and the second data, where the first data is used to communicate with the application server, and the second data includes: heartbeat packets, and according to the length change information, sending third data. Since the first data is the data for communicating with the application server before sending heartbeat packets, and the length change information between the second data and the first data after sending heartbeat packets is detected, and the third data is sent based on the length change information, therefore, sequence synchronization of the data on the application side and the data on the network side is achieved, thereby improving the data transmission performance. By generating at least one third data according to the length change information and the first data, where the size of the third data is less than or equal to the maximum transmission unit (MTU) size, and sending at least one third data. It can effectively ensure that each third data can be correctly received, thereby ensuring the accuracy of sequence synchronization.

[0088] It should be noted that in the following embodiments, the descriptions of the same or corresponding terms and method steps as those in the above embodiments can be referred to the above embodiments together, and will not be repeated here.

[0089] Figure 4 It is a schematic flowchart of another transmission control method provided by an embodiment of the present disclosure.

[0090] The execution subject of this embodiment can be, for example, a communication processor, and there is no limitation thereto.

[0091] As Figure 4 shown, the transmission control method includes:

[0092] Step S401: Receive a first message, where the first message is used to indicate stopping sending heartbeat packets.

[0093] Optionally, in some embodiments, before sending the first message, the application processor can enter the sleep state. Before entering the sleep state, in response to the trigger of the application program, it can instruct the communication processor to proxy the sending of heartbeat packets. The application processor can instruct the communication processor to proxy the sending of heartbeat packets by sending a second message to the communication processor. After receiving the second message, the communication processor can, in response to the second message, send at least one heartbeat packet to the application server to support maintaining the long connection between the application program and the application server, and there is no limitation thereto.

[0094] Step S402: Stop sending heartbeat packets according to the first message.

[0095] Optionally, in some embodiments, if the application processor is awakened, it may send a first message to the communication processor to instruct the communication processor to stop sending proxy heartbeat packets, and the communication processor may respond to the first message and stop sending heartbeat packets.

[0096] Step S403: Receive third data, where the third data is determined based on the length change information between the first data and the second data, the first data is used to communicate with the application server, and the second data includes: heartbeat packets.

[0097] Optionally, in some embodiments, after the communication processor stops sending heartbeat packets, it may receive third data, which is sent by the application processor based on the length change information. The third data can be used for data sequence synchronization. Then the communication processor may receive the third data sent by the application processor.

[0098] It can be understood that the sequence numbers of the data transmitted during the communication between the application processor and the application server are incremented, and the sequence numbers corresponding to each heartbeat packet transmitted by the communication processor to the application server are also incremented. When the communication processor sends each heartbeat packet on behalf of the application processor, the sequence numbers of the data carrying each heartbeat packet received on the application server side have already increased. However, due to the "proxy" behavior of the communication processor, the sequence numbers of the data transmitted by the application processor again do not increase following the increase of the sequence numbers of the data carrying each heartbeat packet, resulting in a sequence out-of-sync between the data on the application side and the data on the network side. Therefore, in the embodiments of the present disclosure, the application processor may resend the third data based on the length change information. For example, the length of the third data may be configured to be consistent with the length value indicated by the "length change information". The communication processor may receive the third data sent by the application processor to cooperate in compensating for the aforementioned sequence out-of-sync.

[0099] In this embodiment, by receiving the first message, where the first message is used to instruct to stop sending heartbeat packets, and according to the first message, stop sending heartbeat packets, and receiving the third data, where the third data is determined based on the length change information between the first data and the second data, the first data is used to communicate with the application server, and the second data includes: heartbeat packets. Thus, sequence synchronization between the data on the application side and the data on the network side is achieved, thereby improving data transmission performance.

[0100] Optionally, in some embodiments, the communication processor may receive the interface protocol information of the first data; and / or receive reference data and parse the interface protocol information from the reference data. Thus, heartbeat packets can be correctly generated, and effectively, proxy sending of heartbeat packets conforming to the interface protocol of the first data can be achieved.

[0101] Optionally, in some embodiments, the interface protocol information includes at least one of the following: address information; port information; sequence number of the first data; header information of the first data.

[0102] Optionally, in some embodiments, the communication processor may receive heartbeat packet information, generate a heartbeat packet based on the first data, the heartbeat packet information, and the interface protocol information, and send the heartbeat packet. Thus, it is possible to accurately proxy and send heartbeat packets as needed.

[0103] Optionally, in some embodiments, the heartbeat packet information includes at least one of the following: heartbeat packet size; heartbeat packet data; heartbeat packet sending period.

[0104] Optionally, in some embodiments, the communication processor may send length change information; and / or send the number of heartbeat packet transmissions, where the number of heartbeat packet transmissions is used to determine the length change information.

[0105] Thus, it is possible to flexibly indicate the length change information between the second data and the first data after sending the heartbeat packet, effectively applicable to personalized communication scenarios, and ensure the indication accuracy of the length change information, supporting the improvement of the accuracy of data sequence synchronization.

[0106] Optionally, in some embodiments, the communication processor may receive at least one third data, where the size of the third data is less than or equal to the maximum transmission unit (MTU) size, and send confirmation information corresponding to the at least one third data, where the confirmation information is used to indicate that the third data has been received. Thus, it is possible to effectively ensure that each third data can be correctly received, thereby ensuring the accuracy of sequence synchronization.

[0107] Figure 5 It is a flowchart of another transmission control method provided by the embodiments of the present disclosure.

[0108] In this embodiment, an interaction diagram between the application processor and the communication processor is shown, which is not limited thereto.

[0109] As Figure 5 shown, the transmission control method includes:

[0110] Step S501: The application processor sends second information, where the second information is used to indicate sending a heartbeat packet.

[0111] Step S502: The application processor sends the interface protocol information of the first data, and / or sends reference data.

[0112] Wherein, the first data is used to communicate with the application server.

[0113] Wherein, the first data and the interface protocol information are used to generate a heartbeat packet.

[0114] Among them, the reference data is used to determine the interface protocol information.

[0115] Step S503: The application processor sends heartbeat packet information.

[0116] Among them, the first data, the interface protocol information, and the heartbeat packet information are jointly used to generate a heartbeat packet.

[0117] Step S504: The communication processor generates a heartbeat packet according to the first data, the heartbeat packet information, and the interface protocol information.

[0118] Step S505: The communication processor sends the heartbeat packet.

[0119] Step S506: The application processor sends the first information, where the first information is used to indicate to stop sending the heartbeat packet.

[0120] Step S507: The communication processor stops sending the heartbeat packet according to the first information.

[0121] Step S508: The application processor obtains the length change information between the first data and the second data, where the first data is used to communicate with the application server, and the second data includes: heartbeat packets.

[0122] Step S509: The application processor sends the third data according to the length change information.

[0123] Step S510: The communication processor receives the third data.

[0124] The following is an example for the above embodiments:

[0125] Taking the data including: TCP sequence and the interface protocol being TCP protocol as an example, there is no limitation to this.

[0126] As Figure 6 shown, Figure 6 is a schematic diagram of a heartbeat packet proxy in an embodiment of the present disclosure. The communication processor can proxy the application program in the application processor to send long connection heartbeat packets. Before the application processor enters sleep, it notifies the communication processor and passes (through IPC) the heartbeat packet and TCP protocol information (an optional example of interface protocol information) to the communication processor. Subsequently, the communication processor proxies to send periodic heartbeat packets. When the application processor wakes up, it notifies the communication processor to stop proxying the heartbeat packet and simultaneously cooperates with the communication processor to complete the sequence synchronization of the TCP stream.

[0127] As Figure 7 shown, Figure 7 is a schematic flowchart of a transmission control method in an embodiment of the present disclosure. Figure 7The interaction schematic between the application processor, communication processor, and application server is shown. It includes:

[0128] S701: The application processor can, in response to the triggering of an application, send first data to the application server through the Socket and the communication processor.

[0129] Among them, the first data sent can be expressed as "TCP Seq = XXX".

[0130] S702: The application processor can, in response to the triggering of an application, obtain interface protocol information through the Socket.

[0131] S703: The application processor sends heartbeat packet information and the interface protocol information of the first data to the communication processor.

[0132] Among them, the heartbeat proxy program in the communication processor can complete the sending proxy of the heartbeat packet.

[0133] S704: The application processor sends reference data to the communication processor so that the communication processor can parse the reference data to obtain interface protocol information.

[0134] The above S704 is an optional step.

[0135] This reference data can also be called a special data packet so that the heartbeat proxy program in the communication processor can obtain TCP and / or IP header information and TCP sequence numbers based on the special data packet.

[0136] S705: The heartbeat proxy program in the communication processor sends n heartbeat packets to the application server.

[0137] S706: The application server receives second data, where the second data includes: heartbeat packets.

[0138] Among them, the second data can be expressed as "TCP Seq = XXX + n * heartbeat packet size".

[0139] S707: Stop the proxy, and the communication processor synchronizes the heartbeat packet sending times to the application processor.

[0140] Among them, the application processor can determine the length change information between the first data and the second data based on the heartbeat packet sending times. The length change information can be expressed as "n * heartbeat packet size".

[0141] S708: The application processor sends third data to the communication processor based on "n * heartbeat packet size".

[0142] After receiving the third data, the communication processor can identify and / or discard it. If it is correctly identified, confirmation information is fed back to the application processor.

[0143] S709: In response to the triggering of the application, the application processor continues to send subsequent data to the application server through the Socket and the communication processor.

[0144] Optionally, in some embodiments, before entering the sleep state, the application processor sends a heartbeat proxy message to notify the communication processor to proxy the sending of the heartbeat packet. The heartbeat proxy message can be an optional example of the above-mentioned second information. The content included in the heartbeat proxy message can be as shown in Table 1 below, and there is no limitation thereto.

[0145] Table 1

[0146]

[0147] The above-mentioned heartbeat interaction information can refer to the interaction information required for the communication processor to proxy the sending of the heartbeat packet. For example, the time information indicating the proxy heartbeat packet, the information of the application program that triggers the proxy heartbeat packet, and so on.

[0148] Optionally, in some embodiments, the application processor can send a start proxy message to the communication processor through a control plane message in response to the triggering of the application program.

[0149] Sending the start proxy message: It is sent to the communication processor through a control plane message, and the communication processor and the application processor can interact through the control plane Inter-Process Communication (IPC). As Figure 8 shown, Figure 8 is a schematic diagram of sending the start proxy message in an embodiment of the present disclosure. The Telephony architecture refers to an operating system architecture. HAL represents the Hardware Abstraction Layer.

[0150] Optionally, in some embodiments, the communication processor can construct an IP data packet, for example, can construct an IP packet according to the TCP protocol and / or the IP protocol, and then send the IP data packet. As shown in Table 2, Table 2 is a schematic diagram of the IP data packet in an embodiment of the present disclosure. Among them, TOS represents the Type of Service field.

[0151] Table 2

[0152]

[0153]

[0154] Optionally, in some embodiments, as Figure 9 shown, Figure 9 is a schematic diagram of the heartbeat packet sending process in an embodiment of the present disclosure. The heartbeat agent program in the communication processor can detect whether the heartbeat packet timer times out. If it times out, a heartbeat packet (IP data packet) is constructed and sent to the application server on the corresponding radio bearer. It is determined whether an acknowledgment message (ACK) is received, or whether the sending of the heartbeat packet (IP data packet) in this cycle reaches the repetition count. If an acknowledgment message (ACK) is received or the sending of the heartbeat packet (IP data packet) in this cycle reaches the repetition count, the sending of the heartbeat packet (IP data packet) in this cycle ends. Otherwise, a heartbeat packet (IP data packet) is constructed again.

[0155] Optionally, in some embodiments, during the process of stopping the heartbeat packet agent, the application processor and the application are awakened. The application processor sends a stop agent message (an optional example of the above first information), and the application processor can wait for a message returned by the heartbeat agent program. The heartbeat agent program receives the stop agent message, stops the timer, and destroys the agent logic. For example, relevant timers can be stopped, the heartbeat agent of this application program can be cancelled, relevant instances can be cleared, and the listening for data on the corresponding IP and / or Port can be registered. The communication processor can send the data length of the total heartbeat packets of this agent to the application processor (which can also be referred to as the TCP Seg growth length, an optional example of the above length change information). The application processor receives the TCP Seg growth length returned by the communication processor, and the application processor receives the TCP Seg growth length for TCP sequence synchronization.

[0156] Optionally, in some embodiments, during the TCP sequence synchronization process, the application processor may, in response to the triggering of an application, send heartbeat packets to synchronize data (an optional example of the above-mentioned third data). The application processor may send heartbeat packets to synchronize data according to the TCP Seg growth length. If the heartbeat packet synchronization data obtained by packet assembly exceeds the MTU, multiple heartbeat packets may be sent to synchronize data, and at least one packet information, such as the total number of synchronization data packets this time and the index of the synchronization data packets this time, may be carried in each heartbeat packet synchronization data. The communication processor may listen for the heartbeat packet synchronization data sent by the application processor. The communication processor may listen for data on the corresponding IP and / or Port, identify the heartbeat packet synchronization data, and feedback an acknowledgment message. In this process, the last data packet of this synchronization may be identified. When all the heartbeat packet synchronization data has been received, the listening for data on the corresponding IP and / or Port is cancelled. If the TCP sequence synchronization is completed, the application processor may, in response to the triggering of an application, continue to send subsequent data. In this process, when the application processor determines that the heartbeat packet synchronization data has been sent and all the acknowledgment messages have been received, the TCP sequence synchronization ends and subsequent data is continued to be sent.

[0157] Figure 10 FIG. is a schematic structural diagram of a transmission control device provided by an embodiment of the present disclosure.

[0158] As Figure 10 shown, the transmission control device 100 includes:

[0159] A first transceiver module 1001, configured to send a first message, where the first message is used to indicate to stop sending heartbeat packets.

[0160] An acquisition module 1002, configured to acquire the length change information between the first data and the second data, where the first data is used to communicate with an application server, and the second data includes: heartbeat packets.

[0161] A second transceiver module 1003, configured to send third data according to the length change information.

[0162] Optionally, in some embodiments of the present disclosure, where

[0163] The first transceiver module 1001 is configured to send a second message, where the second message is used to indicate to send heartbeat packets.

[0164] Optionally, in some embodiments of the present disclosure, where

[0165] The first transceiver module 1001 is configured to send the interface protocol information of the first data, where the first data and the interface protocol information are used to generate heartbeat packets; and / or

[0166] Send reference data, where the reference data is used to determine interface protocol information.

[0167] Optionally, in some embodiments of the present disclosure, the interface protocol information includes at least one of the following:

[0168] Address information;

[0169] Port information;

[0170] The serial number of the first data;

[0171] The header information of the first data.

[0172] Optionally, in some embodiments of the present disclosure, where

[0173] The first transceiver module 1001 is used to send heartbeat packet information, where the first data, the interface protocol information, and the heartbeat packet information are jointly used to generate a heartbeat packet.

[0174] Optionally, in some embodiments of the present disclosure, the heartbeat packet information includes at least one of the following:

[0175] The heartbeat packet size;

[0176] The heartbeat packet data;

[0177] The heartbeat packet sending period.

[0178] Optionally, in some embodiments of the present disclosure, the acquisition module 1002 is used to:

[0179] Receive length change information; and / or

[0180] Receive the number of heartbeat packet transmissions, and determine the length change information according to the number of heartbeat packet transmissions.

[0181] Optionally, in some embodiments of the present disclosure, the second transceiver module 1003 is used to:

[0182] Generate at least one third data according to the length change information and the first data, where the size of the third data is less than or equal to the maximum transmission unit MTU size;

[0183] Send at least one third data.

[0184] Optionally, in some embodiments of the present disclosure, the second transceiver module 1003 is further used to:

[0185] Stop sending the third data when the acknowledgment information corresponding to all the third data has been received, where the acknowledgment information is used to indicate that the third data has been received.

[0186] Optionally, in some embodiments of the present disclosure, the data includes: Transmission Control Protocol (TCP) sequence.

[0187] It should be noted that the foregoing explanation of the embodiments of the transmission control method also applies to the transmission control device of this embodiment, and will not be elaborated here.

[0188] In this embodiment, by sending a first message, where the first message is used to indicate to stop sending heartbeat packets, and obtaining the length change information between the first data and the second data, where the first data is used to communicate with the application server, the second data includes: heartbeat packets, and sending the third data according to the length change information. Since the first data is the data for communicating with the application server before sending the heartbeat packets, and the length change information between the second data and the first data after sending the heartbeat packets is detected, and the third data is sent based on the length change information, sequence synchronization of the data on the application side and the data on the network side is achieved, thereby improving the data transmission performance.

[0189] Figure 11 It is a schematic structural diagram of another transmission control device provided by the embodiments of the present disclosure.

[0190] As Figure 11 shown, the transmission control device 110 includes:

[0191] A third transceiver module 1101, configured to receive a first message, where the first message is used to indicate to stop sending heartbeat packets.

[0192] A control module 1102, configured to stop sending heartbeat packets according to the first message.

[0193] A fourth transceiver module 1103, configured to receive third data, where the third data is determined based on the length change information between the first data and the second data, the first data is used to communicate with the application server, and the second data includes: heartbeat packets.

[0194] Optionally, in some embodiments of the present disclosure, where

[0195] The third transceiver module 1101 is configured to receive a second message, where the second message is used to indicate to send heartbeat packets.

[0196] Optionally, in some embodiments of the present disclosure, where

[0197] The third transceiver module 1101 is configured to receive the interface protocol information of the first data; and / or receive reference data and parse the interface protocol information from the reference data.

[0198] Optionally, in some embodiments of the present disclosure, the interface protocol information includes at least one of the following: address information; port information; the sequence number of the first data; the header information of the first data.

[0199] Optionally, in some embodiments of the present disclosure, wherein

[0200] The third transceiver module 1101 is configured to receive heartbeat packet information, generate a heartbeat packet according to the first data, the heartbeat packet information, and the interface protocol information, and send the heartbeat packet.

[0201] Optionally, in some embodiments of the present disclosure, the heartbeat packet information includes at least one of the following:

[0202] The heartbeat packet size;

[0203] The heartbeat packet data;

[0204] The heartbeat packet sending period.

[0205] Optionally, in some embodiments of the present disclosure, the third transceiver module 1101 is configured to:

[0206] Send length change information; and / or

[0207] Send the number of heartbeat packet transmissions, wherein the number of heartbeat packet transmissions is used to determine the length change information.

[0208] Optionally, in some embodiments of the present disclosure, the fourth transceiver module 1103 is configured to:

[0209] Receive at least one third data, wherein the size of the third data is less than or equal to the maximum transmission unit MTU size;

[0210] Send confirmation information corresponding to at least one third data, wherein the confirmation information is used to indicate that the third data has been received.

[0211] Optionally, in some embodiments of the present disclosure, the data includes: Transmission Control Protocol TCP sequence.

[0212] It should be noted that the foregoing explanation of the embodiments of the transmission control method also applies to the transmission control device of this embodiment, and will not be repeated here.

[0213] In this embodiment, by receiving the first information, wherein the first information is used to indicate to stop sending heartbeat packets, and according to the first information, stop sending heartbeat packets, and receive the third data, wherein the third data is determined based on the length change information between the first data and the second data, the first data is used to communicate with the application server, and the second data includes: heartbeat packets. Thus, sequence synchronization of the data on the application side and the data on the network side is achieved, thereby improving the data transmission performance.

[0214] To implement the above embodiments, the present disclosure also provides a communication device, including: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the methods provided in the foregoing embodiments.

[0215] Figure 12 The block diagram of an exemplary communication device suitable for implementing the embodiments of the present disclosure is shown. Figure 12 The illustrated communication device 12 is merely an example and should not impose any limitation on the functions and usage scope of the embodiments of the present disclosure. The communication device can be, for example, a terminal, and no limitation is imposed thereon.

[0216] As Figure 12 shown, the communication device 12 is presented in the form of a general-purpose computing device. The components of the communication device 12 may include, but are not limited to: one or more processors or processing units 16, a memory 28, and a bus 18 connecting different system components (including the memory 28 and the processing unit 16).

[0217] The bus 18 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the multiple bus structures. For example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnection (PCI) bus.

[0218] The communication device 12 typically includes a variety of computer system-readable media. These media can be any available media accessible by the communication device 12, including volatile and non-volatile media, removable and non-removable media.

[0219] The memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache 32. The communication device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used for reading and writing on non-removable, non-volatile magnetic media ( Figure 12 not shown, commonly referred to as a "hard disk drive").

[0220] Although Figure 12 not shown in the figure, a disk drive for reading and writing on removable non-volatile disks (such as "floppy disks") and an optical disk drive for reading and writing on removable non-volatile optical disks (such as compact disc read only memory (CD-ROM), digital video disc read only memory (DVD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 through one or more data media interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the embodiments of the present disclosure.

[0221] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. The program modules 42 generally perform the functions and / or methods in the embodiments described in the present disclosure.

[0222] The communication device 12 can also communicate with one or more external devices 14 (such as a keyboard, a pointing device, a display 24, etc.), and can also communicate with one or more devices that enable a human body to interact with the communication device 12, and / or communicate with any device that enables the communication device 12 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication can be carried out through an input / output (I / O) interface 22. Moreover, the communication device 12 can also communicate with one or more networks (such as a Local Area Network (LAN), a Wide Area Network (WAN), and / or a public network, such as the Internet) through a network adapter 20. As shown in the figure, the network adapter 20 communicates with other modules of the communication device 12 through a bus 18. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination with the communication device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0223] The processing unit 16 executes various functional applications and data processing by running programs stored in the memory 28, such as implementing the methods mentioned in the foregoing embodiments.

[0224] To implement the foregoing embodiments, the present disclosure also proposes a chip, including: the chip includes a processing circuit, and the processing circuit is configured to execute the method provided in the foregoing embodiments.

[0225] Figure 13 is a schematic structural diagram of a chip proposed by an embodiment of the present disclosure. Reference can be made to Figure 13 the schematic structural diagram of the chip 1300 shown, but not limited thereto.

[0226] The chip 1300 includes a processing circuit 1301 and an interface circuit 1302. The interface circuit 1302 is used to read instructions, and the interface circuit 1302 sends the instructions to the processing circuit 1301 so that the processing circuit 1301 executes the above method.

[0227] Optionally, as Figure 14 shown, Figure 14 is a schematic structural diagram of another chip proposed by an embodiment of the present disclosure. The chip 1300 may further include: a memory 1303 for storing instructions, and the interface circuit 1302 can be used to read the instructions stored in the memory 1303.

[0228] Optionally, the interface circuit 1302 is connected to the memory 1303. The interface circuit 1302 can be used to receive signals from the memory 1303 or other devices, and the interface circuit 1302 can be used to send signals to the memory 1303 or other devices. For example, the interface circuit 1302 can read the instructions stored in the memory 1303 and send the instructions to the processing circuit 1301.

[0229] Optionally, the number of memories 1303 can be one or more. The number of interface circuits 1302 can also be one or more.

[0230] In some embodiments, the interface circuit 1302 executes at least one of the communication steps such as sending and / or receiving in the above method, and the processing circuit 1301 executes other steps.

[0231] In some embodiments, terms such as interface circuit, interface, transceiver pin, transceiver, etc. can be used interchangeably.

[0232] Optionally, all or part of the memory 1303 can also be outside the chip 1300.

[0233] To implement the above embodiments, the present disclosure also proposes a non-transitory computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the method proposed in the foregoing embodiments of the present disclosure.

[0234] To implement the above embodiments, the present disclosure also proposes a computer program product. When the instructions in the computer program product are executed by a processor, the method proposed in the foregoing embodiments of the present disclosure is executed.

[0235] The collection, storage, use, processing, transmission, provision, and disclosure of the user's personal information involved in the present disclosure all comply with the provisions of relevant laws and regulations and do not violate public order and good customs.

[0236] It should be noted that personal information from users should be collected for legal and reasonable purposes and should not be shared or sold outside of these legal uses. In addition, such collection / sharing should be carried out after obtaining the informed consent of the user, including but not limited to notifying the user to read the user agreement / user notice and sign an agreement / authorization including authorizing the relevant user information before the user uses the function. In addition, any necessary steps should be taken to protect and safeguard access to such personal information data and ensure that others with access to the personal information data comply with their privacy policies and procedures.

[0237] The present disclosure anticipates embodiments that can provide users with the option to selectively block the use or access of personal information data. That is, the present disclosure anticipates that hardware and / or software can be provided to prevent or block access to such personal information data. Once personal information data is no longer needed, the risk can be minimized by restricting data collection and deleting the data. In addition, when applicable, personal identifiers are removed from such personal information to protect the privacy of users.

[0238] In the foregoing description of the various embodiments, descriptions with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0239] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present disclosure, the meaning of "a plurality" is at least two, such as two, three, etc., unless otherwise specifically defined.

[0240] Any process or method description shown in a flowchart or described in other ways herein can be understood to represent a module, segment, or portion of code that includes one or more executable instructions for implementing a customized logic function or process. The scope of the preferred embodiments of the present disclosure includes additional implementations, where the functions can be executed in a substantially simultaneous manner or in a reverse order according to the functions involved, rather than in the order shown or discussed, which should be understood by those skilled in the art to which the embodiments of the present disclosure belong.

[0241] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a definable sequence list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device), or used in conjunction with these instruction execution systems, apparatus, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. More specific examples (non-exhaustive list) of computer-readable media include the following: an electrical connection portion with one or more wirings (electronic device), a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpretation, or otherwise appropriately processing it if necessary, and then storing it in a computer memory.

[0242] It should be understood that various parts of the present disclosure can be implemented by hardware, software, firmware, or combinations thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0243] Those of ordinary skill in the art of this technology can understand that all or part of the steps carried by the method of implementing the above embodiments can be completed by a program instructing relevant hardware, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0244] In addition, each functional unit in various embodiments of the present disclosure may be integrated into one processing module, or each unit may exist physically alone, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0245] The above-mentioned storage medium may be a read-only memory, a magnetic disk, an optical disc, etc. Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present disclosure.

Claims

1. A transmission control method, characterized in that, Including: Sending a first message, where the first message is used to indicate to stop sending heartbeat packets; Obtaining length change information between first data and second data, where the first data is used to communicate with an application server, and the second data includes: the heartbeat packets; Sending third data according to the length change information.

2. The method according to claim 1, wherein Before sending the first message, the method further includes: Sending a second message, where the second message is used to indicate to send heartbeat packets.

3. The method according to claim 2, wherein The method further includes: Sending interface protocol information of the first data, where the first data and the interface protocol information are used to generate the heartbeat packets; and / or Sending reference data, where the reference data is used to determine the interface protocol information.

4. The method according to claim 3, wherein The interface protocol information includes at least one of the following: Address information; Port information; The sequence number of the first data; The header information of the first data.

5. The method according to claim 3, wherein The method further includes: Sending heartbeat packet information, where the first data, the interface protocol information, and the heartbeat packet information are jointly used to generate the heartbeat packets.

6. The method according to claim 5, wherein The heartbeat packet information includes at least one of the following: Heartbeat packet size; Heartbeat packet data; Heartbeat packet sending period.

7. The method according to claim 1, wherein The obtaining length change information between first data and second data includes: Receiving the length change information; and / or Receiving the number of heartbeat packet transmissions and determining the length change information according to the number of heartbeat packet transmissions.

8. The method according to claim 1, characterized in that, The sending third data according to the length change information includes: Generating at least one of the third data according to the length change information and the first data, where the size of the third data is less than or equal to the maximum transmission unit (MTU) size; Sending at least one of the third data.

9. The method according to claim 8, wherein The method further includes: Stopping sending the third data when confirmation information corresponding to all the third data has been received, where the confirmation information is used to indicate that the third data has been received.

10. The method according to any one of claims 1-9, characterized in that, The data includes: Transmission Control Protocol (TCP) sequence.

11. A transmission control method, characterized in that, Including: Receiving a first message, where the first message is used to indicate to stop sending heartbeat packets; Stopping sending heartbeat packets according to the first message; Receiving third data, where the third data is determined based on length change information between first data and second data, the first data is used to communicate with an application server, and the second data includes: the heartbeat packets.

12. The method according to claim 11, wherein Before receiving the first message, the method further includes: Receiving a second message, where the second message is used to indicate to send heartbeat packets.

13. The method according to claim 12, wherein The method further includes: Receiving the interface protocol information of the first data; and / or Receiving reference data and parsing the interface protocol information from the reference data.

14. The method according to claim 13, wherein The interface protocol information includes at least one of the following: Address information; Port information; The sequence number of the first data; The header information of the first data.

15. The method according to claim 13, characterized in that, The method further includes: Receiving heartbeat packet information; Generating the heartbeat packets according to the first data, the heartbeat packet information, and the interface protocol information; and Sending the heartbeat packets.

16. The method according to claim 15, wherein The heartbeat packet information includes at least one of the following: Heartbeat packet size; Heartbeat packet data; Heartbeat packet sending period.

17. The method according to claim 11, wherein The method further includes: sending the length change information; and / or sending the number of heartbeat packet transmissions, where the number of heartbeat packet transmissions is used to determine the length change information.

18. The method according to claim 11, wherein The receiving the third data includes: receiving at least one of the third data, where the size of the third data is less than or equal to the maximum transmission unit (MTU) size; sending acknowledgment information corresponding to at least one of the third data, where the acknowledgment information is used to indicate that the third data has been received.

19. The method according to any one of claims 11-18, characterized in that The data includes: Transmission Control Protocol (TCP) sequence.

20. A transmission control device, characterized in that, It includes: a first transceiver module for sending first information, where the first information is used to indicate stopping sending heartbeat packets; an acquisition module for acquiring the length change information between first data and second data, where the first data is used to communicate with an application server, and the second data includes: the heartbeat packets; a second transceiver module for sending third data according to the length change information.

21. A transmission control device, characterized in that, It includes: a third transceiver module for receiving first information, where the first information is used to indicate stopping sending heartbeat packets; a control module for stopping sending heartbeat packets according to the first information; a fourth transceiver module for receiving third data, where the third data is determined based on the length change information between first data and second data, the first data is used to communicate with an application server, and the second data includes: the heartbeat packets.

22. A communication device, characterized in that, It includes: a processor and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1-10 or 11-19.

23. A computer-readable storage medium, characterized in that, Computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the method according to any one of claims 1-10 or 11-19.

24. A computer program product, characterized in that, It includes a computer program, and when the computer program is executed by a processor, it implements the method according to any one of claims 1-10 or 11-19.

25. A chip, characterized in that, The chip includes a processing circuit and an interface circuit; where the interface circuit is used to read instructions, and the interface circuit sends the instructions to the processing circuit so that the processing circuit executes the method according to any one of claims 1-10 or 11-19.

Images