CN116033478A - Communication method, communication device, and computer-readable storage medium - Google Patents

Communication method, communication device, and computer-readable storage medium Download PDF

Info

Publication number
CN116033478A
CN116033478A CN202211582473.8A CN202211582473A CN116033478A CN 116033478 A CN116033478 A CN 116033478A CN 202211582473 A CN202211582473 A CN 202211582473A CN 116033478 A CN116033478 A CN 116033478A
Authority
CN
China
Prior art keywords
data packet
emergency
communication method
report
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211582473.8A
Other languages
Chinese (zh)
Inventor
周斌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Spreadtrum Communications Shanghai Co Ltd
Original Assignee
Spreadtrum Communications Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Spreadtrum Communications Shanghai Co Ltd filed Critical Spreadtrum Communications Shanghai Co Ltd
Priority to CN202211582473.8A priority Critical patent/CN116033478A/en
Publication of CN116033478A publication Critical patent/CN116033478A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

A communication method, a communication device, and a computer-readable storage medium, the method comprising: receiving an emergency state report, wherein the emergency state report is used for reporting a cache abnormal event which occurs to receiving equipment, the cache abnormal event is that the first data packet fails to be received and the idle cache capacity is smaller than or equal to a capacity threshold value; and retransmitting the first data packet in response to the emergency report. The communication method provided by the application is beneficial to improving the communication performance.

Description

Communication method, communication device, and computer-readable storage medium
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a communication method, a communication device, and a computer readable storage medium.
Background
With the development of wireless communication technology, the service required to be transmitted in some communication scenarios generally has the characteristics of large data volume, high transmission delay requirement and the like, and the throughput of the communication device is very large, which brings great challenges to the data transmission capability and the like of the communication device, and the problems of data accumulation or data blocking and the like are easy to occur.
Disclosure of Invention
Embodiments of the present application provide a communication method, a communication device, and a computer readable storage medium, which can reduce the problems of data accumulation or data blocking, and are helpful for improving communication performance.
In a first aspect, an embodiment of the present application provides a communication method, including: receiving an emergency state report, wherein the emergency state report is used for reporting a cache abnormal event which occurs to receiving equipment, the cache abnormal event is that the first data packet fails to be received and the idle cache capacity is smaller than or equal to a capacity threshold value; and retransmitting the first data packet in response to the emergency report.
Optionally, the buffering abnormal event is that the radio link control RLC entity of the receiving device does not receive the complete first data packet, and the idle buffering capacity of the packet data convergence protocol PDCP entity is less than or equal to the capacity threshold.
Optionally, retransmitting the first data packet includes: recoding the first data packet, wherein the reliability of a coding mode adopted by recoding is higher than that of an original coding mode; and sending the recoded first data packet.
Optionally, the transmission priority of the first data packet retransmitted is higher than the transmission priority of the other data packets.
Optionally, the method further comprises: and stopping the transmission of other data packets except the first data packet.
Optionally, the method further comprises: in response to the emergency report, starting a first timer; and stopping retransmission of the first data packet and resuming transmission of the other data packets in response to expiration of the first timer or in response to receiving an indication of elimination of the buffering exception event.
Optionally, the retransmitted first data packet carries a poll identifier, and the poll identifier indicates the receiving device to feed back the retransmission.
Optionally, the emergency state report includes category indication information and packet information, where the category indication information is used to indicate that the category of the state report is an emergency state report, and the packet information is used to indicate the first packet.
Optionally, the class indication information is carried in a control protocol data unit type CPT field.
In a second aspect, embodiments of the present application provide a communication device, including: the receiving module is used for receiving an emergency state report, wherein the emergency state report is used for reporting a cache abnormal event which occurs to the receiving equipment, the cache abnormal event is that the first data packet is failed to be received and the idle cache capacity is smaller than or equal to a capacity threshold value; and the sending module is used for retransmitting the first data packet in response to the emergency state report.
In a third aspect, an embodiment of the present application provides a communication method, including: in response to detecting the cache abnormal event, sending an emergency state report; the emergency report is used for reporting the abnormal buffering event so as to trigger retransmission of the first data packet.
Optionally, the buffering abnormal event is that the radio link control RLC entity does not receive the complete first data packet, and the idle buffering capacity of the packet data convergence protocol PDCP entity is less than or equal to the capacity threshold.
Optionally, the method further comprises: and receiving the recoded first data packet, wherein the reliability of the coding mode adopted by the recoding is higher than that of the original coding mode.
Optionally, the transmission priority of the first data packet retransmitted is higher than the transmission priority of the other data packets.
Optionally, the retransmitted first data packet carries a poll identifier, and the poll identifier indicates to feed back the retransmission.
Optionally, the method further comprises: and sending an elimination indication of the cache abnormal event in response to the receiving of the first data packet.
Optionally, the emergency state report includes category indication information and packet information, where the category indication information is used to indicate that the category of the state report is an emergency state report, and the packet information is used to indicate the first packet.
Optionally, the class indication information is carried in a control protocol data unit type CPT field.
Optionally, sending the emergency report includes: the emergency status report is sent periodically.
Optionally, sending the emergency report includes: in response to detecting the cache abnormal event, starting a first counter, wherein the first counter is used for counting other data packets received after the cache abnormal event is detected; and triggering the transmission of the emergency state report and zeroing the first counter every time the value of the first counter reaches a set threshold value.
In a fourth aspect, embodiments of the present application provide a communication device, including: the sending module is used for responding to the detection of the cache abnormal event and sending an emergency state report; the emergency report is used for reporting the abnormal buffering event so as to trigger retransmission of the first data packet.
In a fifth aspect, embodiments of the present application provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes the communication method provided in the first aspect or the third aspect to be performed.
In a sixth aspect, embodiments of the present application provide a communications apparatus comprising a memory and a processor, the memory having stored thereon a computer program executable on the processor, the processor executing the steps of the communications method provided in the first aspect when the computer program is executed.
In a seventh aspect, embodiments of the present application provide a communications apparatus comprising a memory and a processor, the memory having stored thereon a computer program executable on the processor, the processor executing the steps of the communications method provided by the third aspect when the computer program is executed.
Compared with the prior art, the technical scheme of the embodiment of the application has the following beneficial effects:
in the scheme of the embodiment of the application, in response to detection of the buffering abnormal event, the receiving device sends an emergency state report to the sending device so as to report the buffering abnormal event which occurs to the receiving device to the sending device, wherein the buffering abnormal event is that the first data packet fails to be received and the idle buffering capacity is smaller than or equal to the capacity threshold. In response to receiving the emergency report, the transmitting device retransmits the first data packet.
By adopting the scheme, the receiving equipment actively reports the cache abnormal event to the sending equipment under the condition that the cache abnormal event is detected, and the sending equipment can timely retransmit after receiving the emergency state report so as to relieve the situation of data accumulation as soon as possible, thereby ensuring the service quality.
Further, in the scheme of the embodiment of the present application, the transmission priority of the retransmitted first data packet is higher than the transmission priority of the other data packets. By adopting the scheme, the effective transmission of the first data packet is facilitated to be realized as soon as possible.
Further, in the solution of the embodiment of the present application, in response to the received emergency report, transmission of the data packet other than the first data packet is suspended. By adopting the scheme, the transmission of new data is suspended under the condition of occurrence of a buffering abnormal event, and the situation that data accumulation is aggravated to further inform about packet loss is avoided.
Further, in the scheme of the embodiment of the present application, the transmitting device recodes the first data packet, where the reliability of the coding mode adopted in recoding is higher than that of the original coding mode, and then transmits the recoded first data packet, so as to realize retransmission of the first data packet. By adopting the scheme, the reliability of retransmission of the first data packet can be improved, and effective transmission of the first data packet can be realized as soon as possible.
Drawings
FIG. 1 is a schematic flow chart of a communication method in an embodiment of the application;
FIG. 2 is a schematic diagram of a status report format according to an embodiment of the present application;
FIG. 3 is a schematic diagram of another status report format according to an embodiment of the present application;
FIG. 4 is a schematic diagram of data interaction of a communication method according to an embodiment of the present application;
FIG. 5 is a schematic diagram of data interaction of another communication method according to an embodiment of the present application;
Fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of another communication device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of still another communication device in an embodiment of the present application.
Detailed Description
It should be noted that, the communication system applicable to the embodiment of the present application includes, but is not limited to, a third generation system (3 th-generation, abbreviated as 3G), a long term evolution (long term evolution, abbreviated as LTE) system, a fourth generation system (4 th-generation, abbreviated as 4G), a fifth generation (5 th-generation, abbreviated as 5G) system, a New Radio (abbreviated as NR) system, and a future evolution system or a plurality of communication fusion systems. The 5G system may be a non-independent Networking (NSA) 5G system or an independent networking (SA) 5G system. The scheme of the embodiment of the application can be also applied to various new communication systems in the future, such as 6G, 7G and the like.
A terminal in an embodiment of the present application may refer to various forms of User Equipment (UE), an access terminal, a subscriber unit, a subscriber Station, a Mobile Station (MS), a remote Station, a remote terminal, a Mobile device, a User terminal, a terminal device (Terminal Equipment), a wireless communication device, a User agent, or a User apparatus. The terminal may also be a cellular phone, a cordless phone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capability, a computing device or other processing device connected to a wireless modem, a car-mounted device, a wearable device, a terminal in a future 5G network or a terminal in a future evolved public land mobile network (Public Land Mobile Network, PLMN) etc., as examples of which the embodiments are not limited.
The network device in the embodiments of the present application may also be referred to as an access network device, for example, may be a Base Station (BS) (also referred to as a base station device), and the network device is a device deployed in a radio access network (Radio Access Network, RAN) to provide a wireless communication function. For example, the device for providing a base station function in the second generation (2 nd-generation, abbreviated as 2G) network includes a base radio transceiver station (base transceiver station, abbreviated as BTS), the device for providing a base station function in the third generation (3 rd-generation, abbreviated as 3G) network includes a node B (NodeB), the device for providing a base station function in the fourth generation (4 th-generation, abbreviated as 4G) network includes an evolved NodeB (eNB), the device for providing a base station function in the wireless local area network (wireless local area networks, abbreviated as WLAN) is an Access Point (AP), the next generation base station node (nextgeneration node base station, abbreviated as gNB) in NR, and the node B (ng-eNB) continuing to evolve, wherein the gNB and the terminal device communicate using NR technology, and the ng-eNB and the terminal device communicate using evolved universal terrestrial radio access (Evolved Universal Terrestrial Radio Access, abbreviated as E-UTRA) technology, and the gNB and the ng-eNB can be connected to the 5G core network. The network device in the embodiment of the present application further includes a device that provides a base station function in a new communication system in the future, and the like.
As described in the background, in some communication scenarios, throughput of the communication device is large, which presents a great challenge for data transmission capability of the communication device (e.g., terminal, etc.), and problems such as data accumulation or data blocking are likely to occur.
In a communication scenario, both the transmitting device and the receiving device may be configured with a radio link control (Radio link Control, RLC) entity (entity). Specifically, the RLC entity of the transmitting apparatus receives RLC service data units (Service Data Unit, abbreviated SDUs) from an upper layer, then segments the RLC SDUs to obtain RLC PDUs, and transmits RLC protocol data units (Protocol Data Unit, abbreviated PDUs) to the RLC entity of the receiving apparatus through a lower layer. Correspondingly, the RLC entity of the receiving device receives RLC PDUs through the lower layer, reassembles the RLC PDUs to obtain RLC SDUs, and transmits the RLC SDUs to the upper layer.
Further, the RLC entity may operate in acknowledged mode (Acknowledged Mode, AM for short) for data transmission. The acknowledged mode of RLC is adopted by various access technologies and is applied to various scenarios requiring reliable data transmission, such as browsing web pages, file transfer protocol (File Transfer Protocol, abbreviated FTP) transmission, etc.
The RLC acknowledged mode supports retransmission (retransmission) of RLC SDUs based on a feedback mechanism. Specifically, the transmitting apparatus transmits RLC SDUs to the receiving apparatus and instructs the receiving apparatus to feed back the transmission of the RLC SDUs, and the receiving apparatus may transmit Status reports (Status PDUs) to the transmitting apparatus at the end of the transmission time window. If the receiving device receives the RLC SDU, the status report includes an Acknowledgement (ACK) message; if the receiving device does not receive the RLC SDU, the status report includes a negative acknowledgement (Negative Acknowledge, NACK) message.
During data transmission, a short packet loss may cause a receiving device to need to buffer a large amount of data in order to sequentially deliver the data packet to an upper layer. Specifically, during data transmission, a certain RLC SDU may fail to be transmitted due to jitter of a signal, or the like, that is, the receiving apparatus does not receive the RLC SDU or does not receive the complete RLC SDU. The received data are reported to the upper layer in sequence, if the subsequent RLC SDUs of the RLC SDUs with failed reception are successfully received, the subsequent RLC SDUs with failed reception cannot be reported to the upper layer due to the existence of the RLC SDUs with failed reception, so that the data are accumulated and the buffer pressure is formed. For example, in the LTE system, after receiving an RLC SDU, an RLC entity of a transmitting apparatus submits to a packet data convergence protocol (Packet Data Convergence Protocol, abbreviated PDCP) entity in sequence, and if the RLC entity fails to receive a certain RLC SDU and the subsequent data packet is successfully received, the RLC entity generates data accumulation. For another example, in the NR system, after the RLC entity of the transmitting device receives one RLC SDU, the RLC entity reports the RLC SDU to the PDCP entity, and the PDCP entity sequentially submits the RLC SDU to an upper layer (e.g., an application layer), and if the RLC entity fails to receive a certain RLC SDU and the subsequent data packet is successfully received, the PDCP entity accumulates data.
The data accumulation itself means that the data reception delay becomes large. Meanwhile, data accumulation is a serious test for the storage space of the receiving device, and accumulation of data exceeding the buffering capacity can lead to more packet loss. These all affect the quality of service of the service.
In general, a receiving device will actively drop packets after data is accumulated to the upper capacity limit to avoid the occurrence of buffer exhaustion, which is easy to cause various more serious anomalies. However, this direct packet loss scheme may result in a significant degradation of the quality of service of the traffic.
Or, the receiving device delays sending the RLC status report to the sending device to suspend the sending device from sending new data packets, so as to alleviate the situation that the buffer is about to be exhausted. This scheme is not necessarily valid since the transmission timing of the status report is limited by the RLC transmission window status. For example, the RLC transmission window still has more new data to transmit, and even if the transmission of the RLC status report is delayed, the transmitting device still transmits more new data packets to the receiving device during the period, which still aggravates the buffer pressure of the receiving device.
In view of this, in the solution of the embodiment of the present application, in response to detecting a buffering abnormal event, the receiving device sends an emergency status report to the sending device, so as to report, to the sending device, the buffering abnormal event that the receiving device has occurred, where the buffering abnormal event is that the first data packet has failed to be received and the free buffering capacity is less than or equal to the capacity threshold. In response to receiving the emergency report, the transmitting device retransmits the first data packet. By adopting the scheme, the receiving equipment actively reports the cache abnormal event to the sending equipment under the condition that the cache abnormal event is detected, and the sending equipment can timely retransmit after receiving the emergency state report so as to relieve the situation of data accumulation as soon as possible, thereby ensuring the service quality.
In order to make the above objects, features and advantages of the present application more comprehensible, embodiments accompanied with figures are described in detail below.
Referring to fig. 1, fig. 1 is a flow chart of a communication method in an embodiment of the present application. The method shown in fig. 1 may include:
step S11: receiving an emergency state report, wherein the emergency state report is used for reporting a cache abnormal event which occurs to receiving equipment, the cache abnormal event is that the first data packet fails to be received and the idle cache capacity is smaller than or equal to a capacity threshold value;
step S12: and retransmitting the first data packet in response to the emergency report.
The method shown in fig. 1 may be performed by a transmitting device, which may be a sender of a data packet, and the transmitting device may be a terminal or a network device, which is not limited in this embodiment. The data packet in the embodiment of the present application may refer to an RLC SDU, or may refer to other types of data packets.
In addition, the receiving device referred to in the embodiment of the present application refers to a receiving side of the data packet. The transmitting device may transmit the data packet to the receiving device through an Uplink (Uplink), or the transmitting device may transmit the data packet to the receiving device through a Downlink (Downlink), or the transmitting device may transmit the data packet to the receiving device through a side link (sidlink), which is not limited in this embodiment.
In a specific implementation of step S21, the receiving device sends an emergency status report to the sending device, wherein the emergency status report is sent by the receiving device in response to detecting the buffering abnormal event.
Specifically, during data transmission, the receiving device detects a buffering exception event. Specifically, the abnormal buffering event means that the first data packet fails to be received, and the free buffering capacity is less than or equal to the capacity threshold. The first data packet may be any data packet in the data transmission process, and the buffer capacity refers to the capacity of a buffer area for buffering the received data packet, and the capacity threshold may be defined by a protocol, or may be preconfigured by an operator or a terminal manufacturer. It should be noted that, in the embodiment of the present application, the "failure of receiving the first data packet" may refer to that the complete first data packet is not received. For example, the first data packet is not received and the first data packet is not received intact.
As an example, the data packet is an RLC SDU, and the buffer capacity is a capacity of a buffer area for buffering the received RLC SDU. In an implementation, the data packet may be buffered in the PDCP entity, or may be buffered in the RLC entity, or may be buffered in another entity of Layer 2 (Layer 2), which is not limited in this embodiment. Taking the data packet as RLC SDU, and the data packet is buffered in the PDCP entity as an example, the buffering exception event may also be expressed as: the RLC entity does not receive the complete first data packet and the free buffer capacity of the PDCP entity is less than or equal to the capacity threshold.
Further, if the receiving apparatus detects a buffering abnormal event, the receiving apparatus transmits an emergency status report to the transmitting apparatus in response to the detected buffering abnormal event. The emergency report may be an RLC control PDU, among others. Correspondingly, the sending device receives the emergency report.
In a specific implementation, the emergency status report may include category indication information, which may be used to indicate that the category of the status report is the emergency status report, and packet information, which is used to indicate the first packet so that the transmitting device knows which packet transmission failed. More specifically, the category indication information may be used to distinguish between emergency status reports and general status reports. The emergency report is used for reporting the abnormal event of the buffer memory of the receiving device, and the common status report is only used for reporting whether the receiving device receives the data packet.
Furthermore, the emergency status report is actively transmitted by the receiving device, and the normal status report is instructed to be transmitted by the transmitting device, and if the transmitting device does not set the polling flag for a certain data packet, the receiving device does not actively transmit the normal status report for the data packet to the receiving device. And when the abnormal buffering event is detected, the receiving device sends an emergency state report no matter whether the first data packet with failed receiving has a polling identifier or not.
The polling identifier is information for indicating the receiving terminal to feed back the reception of the data packet. For example, a dedicated bit may be reserved in the data packet, and if the value of the bit is 1, it may be indicated that the data packet has a poll flag, and if the value of the bit is 0, it may be indicated that the data packet does not have a poll flag.
Referring to fig. 2 and 3, fig. 2 is a schematic diagram illustrating a format of a status report according to an embodiment of the present application. Fig. 2 shows a format of a status report with a Sequence Number (SN) length of 12 bits. Fig. 3 shows a format of a status report with a Sequence Number (SN) length of 18 bits.
The class indication information may be carried in a Control PDU Type (CPT) field. Illustratively, the CPT field is located at bits 4 through 6 of the first byte of the status report. Table 1 shows a definition of the CPT field.
TABLE 1
Value Description
000 General status reporting
001 Emergency status reporting
As shown in table 1, if the value of the CPT field is 000, the status report may be indicated as a general status report, and if the value of the CPT field is 001, the status report may be indicated as an emergency status report. For a specific description of the status report shown in fig. 2 and 3, reference may be made to the related content of the existing protocol TS138.322 v17.1.0, which is not described herein. For example, the manner of carrying the data packet information in the emergency status report may refer to the manner of carrying the data packet information in the normal status report in the existing protocol, which is not limited in this embodiment.
With continued reference to fig. 1, in step S12, the transmitting apparatus retransmits the first data packet in response to the received emergency status report.
It should be noted that, in the solution of the embodiment of the present application, whether the first data packet has the polling identifier or not, the receiving device sends an emergency report to report the abnormal buffering event. More specifically, in response to detecting a cache exception event, the receiving device may immediately send an emergency status report. In contrast to the scheme where the receiving device sends a normal status report to the sending device only if the first data packet has a poll identity, the scheme of the embodiments of the present application will actively send an RLC status report if a certain level of received data accumulation is encountered, and explicitly inform the sending device on the RLC status report that this is an "urgent" retransmission request. After receiving the urgent retransmission request, the transmitting device can retransmit in time so as to relieve the situation of data accumulation as soon as possible.
In an implementation, the transmission priority of the first data packet of the retransmission may be higher than the transmission priority of the other data packets. Wherein the other data packets may refer to data packets other than the first data packet. For example, other data packets may include: and the data packet to be sent for the first time and/or the data packet to be retransmitted is triggered by the common status report.
More specifically, the transmission priority of the retransmitted first data packet is higher than that of the other data packets, that is, the transmitting device preferentially transmits the first data packet.
Further, in response to the emergency report, the transmitting apparatus may also suspend transmission of other data packets than the first data packet. With such a scheme, further emphasis on data accumulation at the receiving terminal can be avoided.
In one example, in response to the emergency status report, the transmitting device may start a first timer, the duration of which may be preconfigured. When the first timer expires, the transmitting terminal may stop retransmission of the first data packet and resume transmission of other data packets. Alternatively, if the receiving terminal receives the first data packet before the expiration of the first timer, the transmitting apparatus may stop retransmission of the first data packet and resume transmission of other data packets.
In a specific implementation, after the receiving device receives the first data packet, the receiving device may send an indication of elimination of the buffering abnormal event to the sending device, and in response to the received indication of elimination, the sending device stops retransmission of the first data packet and resumes transmission of other data packets.
More specifically, the retransmitted first data packet may have a poll identifier to instruct the receiving device to feed back the retransmission of the first data packet. Thus, after receiving the first data packet, the receiving device may send a general status report to the sending device, with the general status report including an acknowledgement message. The receiving device receives the complete first data packet, so that the first data packet can be submitted to an upper layer, the data packets after the first data packet can be sequentially submitted to the upper layer, and the receiving device can be separated from the condition of data accumulation and buffering urgency. Thus, when the transmitting device receives the normal status report for the retransmitted first data packet, it can be determined that the elimination instruction of the buffering abnormal event is received.
Further, if the number of data packets failed to be received in the emergency report is plural, that is, the number of first data packets is plural, the transmitting apparatus may start retransmission from the first data packet failed to be received. The first data packet with the failed reception may be a data packet with the smallest sequence number in the multiple data packets with the failed reception.
Referring to fig. 4, fig. 4 is a schematic diagram of data interaction of a communication method in an embodiment of the present application. The communication method shown in fig. 4 may include steps S31 to S34. Specifically:
in step S31, the receiving device detects a buffering abnormal event.
In step S32, in response to detecting the buffering abnormal event, the receiving apparatus transmits an emergency status report to the transmitting apparatus.
For more details regarding step S31 and step S32, reference may be made to the relevant details regarding step S11 above, and will not be described here.
In step S33, the transmitting device re-encodes the first data packet.
In step S34, the transmitting device transmits the recoded first data packet.
Specifically, in response to the emergency report, the transmitting device may first recode the first data packet and transmit the recoded first data packet, so as to implement retransmission of the first data packet.
Wherein, the reliability of the coding mode adopted by recoding is higher than that of the original coding mode. For example, the redundancy of the first data packet after re-encoding is greater than the redundancy of the first data packet before re-encoding.
In a specific implementation, the first data packet may be recoded by using a modulation and coding strategy (Modulation and Coding Scheme, abbreviated as MCS) with a smaller order, so as to improve the reliability of retransmission, thereby ensuring that the receiving device can successfully receive the first data packet. It should be noted that, the first data packet may be recoded by other existing methods for improving coding reliability, which is not limited in this embodiment.
In step S34, the transmitting device preferentially transmits the recoded first data packet. For more details regarding step S34, reference is made to the above detailed description regarding step S12, and no further description is given here.
Referring to fig. 5, fig. 5 is a schematic diagram of data interaction of another communication method in an embodiment of the present application. Compared to the steps S31 to S34 shown in fig. 4, the communication method shown in fig. 5 further includes:
in step S35, the receiving device transmits an elimination instruction of the buffering abnormal event. Specifically, in response to receipt of the first data packet, the receiving device transmits an indication of elimination of the buffering exception event.
Step S36, resumes transmission of other data packets.
For more details of step S35 and step S36, reference may be made to the description related to fig. 1 above, and no further description is given here.
From the above, in the solution of the embodiment of the present application, after data accumulation (i.e., buffering an abnormal event) occurs at the receiving device, the receiving device actively transmits an emergency status report, and explicitly buffers an emergency situation of urgency to the transmitting device. After receiving the emergency report, the sending device immediately adopts a more reliable mode to preferentially transmit the data packet with failed reception, such as sending the data packet needing to be retransmitted, because the emergency report is clear that the emergency report is the condition of needing to be retransmitted; suspending the transmission of other data packets; and selecting a more reliable coding mode to send retransmission packets, etc. Thus, the situation of data accumulation at the receiving device is quickly relieved, and packet loss due to exceeding the buffering capacity caused by further aggravation of accumulation is avoided. In addition, as the scheme can more quickly supplement the data packet with failed reception, the time delay of data delivery can be reduced, and the receiving throughput rate of the receiving device becomes smoother. Accordingly, the service quality can be better ensured.
Further, if the service transmitted between the sending device and the receiving device is a service of a transmission control protocol (Transmission Control Protocol, abbreviated as TCP) layer, by adopting the scheme of the embodiment of the application, the throughput rate of the receiving device can be smoother, and the receiving device can also perform feedback of the TCP layer more timely, thereby being beneficial to improving the sending throughput rate of the sending device.
In a first non-limiting example, the receiving device may periodically send an emergency status report after detecting a cache exception event and before the cache exception event is cleared. For example, in response to detecting a cache exception event, the receiving device may start a second timer, the duration of which may be preconfigured. In response to expiration of the second timer, the receiving device transmits an emergency report to the transmitting device and triggers the second timer to restart counting. Further, the transmitting device may transmit a first data packet in response to each received emergency report. That is, the number of repeated transmissions of the first packet at each retransmission is 1.
In a second non-limiting example, the receiving device may send an emergency status report in response to detecting a buffering exception event. In addition, the receiving device may further start a first counter, where the first counter may be configured to count other data packets received after the detection of the buffering abnormal event, trigger the sending of the emergency status report again each time the value of the first counter reaches a set threshold, and return the value of the first counter to zero. Further, the transmitting device may transmit a first data packet in response to each received emergency report.
In a third non-limiting example, in response to detecting a buffering exception, the receiving device sends an emergency status report to the sending device. The transmitting device may repeatedly transmit the first data packet a plurality of times in response to each received emergency report. That is, the number of repeated transmissions of the first packet is a plurality of times at each retransmission.
The number of repeated sending times of the first data packet may be preset or may be determined according to the emergency degree indicated by the emergency state report. More specifically, multiple backups of the first data packet may be stored in the retransmission buffer, the number of backups being equal to the number of repeated transmissions. In response to receiving the emergency report, the transmitting device transmits a plurality of backups to effect repeated transmission of the first data packet.
In a fourth non-limiting example, the emergency status report may also include indication information that may be used to indicate the degree of urgency to cache the abnormal event. For example, indication information for indicating the degree of emergency may be carried in the CPT field. For example, the values of bits 1 and 2 in the CPT field may be used to carry indication information, and the value of bit 3 is used to indicate whether the status report is an emergency status report. Alternatively, the value of bit 1 in the CPT field is used to indicate whether the status report is an emergency status report, and the values of bits 2 and 3 may be used to carry indication information. The smaller the free buffer capacity, the higher the emergency degree.
Further, after receiving the emergency report, the transmitting device may select a retransmission mode according to the emergency degree of the abnormal event.
For example, a mapping relationship between the number of repeated transmissions and the indication information may be preconfigured, and after the transmission apparatus receives the emergency report, the number of repeated transmissions may be determined according to the indication information, where the higher the emergency degree indicated by the indication information, the greater the number of repeated transmissions. The number of repeated transmissions in this embodiment refers to the number of times the first packet is transmitted in one retransmission.
Also for example, after the transmitting apparatus receives the emergency report, the maximum number of retransmissions may be set according to the indication information. The maximum retransmission times are used for limiting retransmission times, and when the retransmission times of the first data packet reach the maximum retransmission times, the sending device does not retransmit the first data packet any more even if the first data packet is not received successfully. Specifically, the sending device may determine the maximum retransmission times according to the indication information in the emergency status report with reference to the maximum retransmission times corresponding to the normal status report, where the higher the emergency degree indicated by the indication information, the greater the maximum retransmission times.
More specifically, the transmitting device may start the second counter for counting the number of retransmissions of the first data packet when the emergency report for the first data packet is received for the first time, and may not retransmit the first data packet after the value of the second counter reaches the maximum number of retransmissions.
For another example, after the transmitting device receives the emergency report, the transmitting device may determine the transmission priority of the retransmitted first data packet according to the indication information, where the higher the emergency degree, the higher the transmission priority of the first data packet.
For another example, considering that the time required for recoding the first data packet is long for notifying other entities, the transmitting device may use a retransmission method for multiple times if the indication information indicates that the situation is urgent, or may use a retransmission method for recoding and performing one retransmission if the indication information indicates that the situation is not urgent.
It will be appreciated that in a specific implementation, the method may be implemented in a software program running on a processor integrated within a chip or a chip module; alternatively, the method may be implemented in hardware or a combination of hardware and software, for example, implemented in a dedicated chip or chip module, or implemented in a dedicated chip or chip module in combination with a software program.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a communication apparatus in an embodiment of the present application, where the communication apparatus shown in fig. 6 may be disposed in the foregoing transmitting device, and the apparatus shown in fig. 6 may include:
a receiving module 51, configured to receive an emergency status report, where the emergency status report is used to report a buffering abnormal event that occurs in a receiving device, where the buffering abnormal event is that a first data packet fails to be received and an idle buffering capacity is less than or equal to a capacity threshold;
a sending module 52, configured to retransmit the first data packet in response to the emergency status report.
In a specific implementation, the communication apparatus shown in fig. 6 may correspond to a chip having a communication function in a transmitting device; or corresponds to a chip or a chip module having a communication function included in the transmitting apparatus, or corresponds to the transmitting apparatus.
Referring to fig. 7, fig. 7 is a schematic structural diagram of another communication apparatus in the embodiment of the present application, where the communication apparatus shown in fig. 7 may be disposed in the foregoing transmitting device, and the apparatus shown in fig. 7 may include:
a transmitting module 61, configured to transmit an emergency status report in response to detecting the buffering abnormal event;
the emergency report is used for reporting the abnormal buffering event so as to trigger retransmission of the first data packet.
In a specific implementation, the communication apparatus shown in fig. 7 may correspond to a chip having a communication function in the receiving device; or corresponds to a chip or a chip module having a communication function included in the receiving apparatus, or corresponds to the receiving apparatus.
For more matters such as the working principle, the working method and the beneficial effects of the communication device in the embodiments of the present application, reference may be made to the above related description about the communication method, which is not repeated here.
The embodiments of the present application also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the above-described communication method. The computer readable storage medium may include ROM, RAM, magnetic or optical disks, and the like. The computer readable storage medium may also include non-volatile memory (non-volatile) or non-transitory memory (non-transitory) or the like.
The embodiment of the application also provides a communication device, which comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor executes the steps of the communication method when running the computer program. The communication device comprises, but is not limited to, a mobile phone, a computer, a tablet computer and other terminals.
Referring to fig. 8, fig. 8 is a schematic structural diagram of still another communication device in an embodiment of the present application. The communication device shown in fig. 8 comprises a memory 71, a processor 72 and a transceiver 73, the processor 72 being coupled to the memory 71 and the transceiver 73, the memory 71 being either located inside the terminal or outside the terminal. The memory 71, the processor 72 and the transceiver 73 may be connected by a communication bus. The transceiver 73 is used to communicate with other devices or communication networks. Alternatively, the transceiver 73 may include a transmitter and a receiver. The memory 71 has stored thereon a computer program executable on the processor 72, which when executed by the processor 72, the transceiver 73 performs the steps of the communication method provided by the above-described embodiments.
The embodiment of the application also provides a communication device, which comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor executes the steps of the communication method when running the computer program. The specific structure of the communication device may refer to the related description of fig. 8, and will not be described herein. The communication device includes, but is not limited to, a network device such as a base station.
It should be appreciated that in the embodiment of the present application, the processor may be a central processing unit (central processing unit, abbreviated as CPU), and the processor may also be other general purpose processors, digital signal processors (digital signal processor, abbreviated as DSP), application specific integrated circuits (application specific integrated circuit, abbreviated as ASIC), field programmable gate arrays (field programmable gate array, abbreviated as FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It should also be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically erasable ROM (electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (random access memory, RAM for short) which acts as an external cache. By way of example but not limitation, many forms of random access memory (random access memory, abbreviated as RAM) are available, such as static random access memory (static RAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, abbreviated as DDR SDRAM), enhanced Synchronous Dynamic Random Access Memory (ESDRAM), synchronous Link DRAM (SLDRAM), and direct memory bus random access memory (direct rambus RAM, abbreviated as DR RAM).
The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the processes or functions described in accordance with the embodiments of the present application are all or partially produced. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer program may be stored in or transmitted from one computer readable storage medium to another, for example, by wired or wireless means from one website, computer, server, or data center.
It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
In the several embodiments provided in the present application, it should be understood that the disclosed method, apparatus, and system may be implemented in other manners. For example, the device embodiments described above are merely illustrative; for example, the division of the units is only one logic function division, and other division modes can be adopted in actual implementation; for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may be physically included separately, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units. For example, for each device or product applied to or integrated on a chip, each module/unit included in the device or product may be implemented in hardware such as a circuit, or at least part of the modules/units may be implemented in software program, where the software program runs on a processor integrated inside the chip, and the rest (if any) of the modules/units may be implemented in hardware such as a circuit; for each device and product applied to or integrated in the chip module, each module/unit contained in the device and product can be realized in a hardware manner such as a circuit, different modules/units can be located in the same component (such as a chip, a circuit module and the like) or different components of the chip module, or at least part of the modules/units can be realized in a software program, the software program runs on a processor integrated in the chip module, and the rest (if any) of the modules/units can be realized in a hardware manner such as a circuit; for each device, product, or application to or integrated with the terminal, each module/unit included in the device, product, or application may be implemented by using hardware such as a circuit, different modules/units may be located in the same component (for example, a chip, a circuit module, or the like) or different components in the terminal, or at least part of the modules/units may be implemented by using a software program, where the software program runs on a processor integrated inside the terminal, and the remaining (if any) part of the modules/units may be implemented by using hardware such as a circuit.
The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In this context, the character "/" indicates that the front and rear associated objects are an "or" relationship.
The term "plurality" as used in the embodiments herein refers to two or more.
The first, second, etc. descriptions in the embodiments of the present application are only used for illustrating and distinguishing the description objects, and no order division is used, nor does it indicate that the number of the devices in the embodiments of the present application is particularly limited, and no limitation on the embodiments of the present application should be construed.
Although the present application is disclosed above, the present application is not limited thereto. Various changes and modifications may be made by one skilled in the art without departing from the spirit and scope of the invention, and the scope of the invention shall be defined by the appended claims.

Claims (24)

1. A method of communication, comprising:
receiving an emergency state report, wherein the emergency state report is used for reporting a cache abnormal event which occurs to receiving equipment, the cache abnormal event is that the first data packet fails to be received and the idle cache capacity is smaller than or equal to a capacity threshold value;
and retransmitting the first data packet in response to the emergency report.
2. The communication method according to claim 1, wherein the buffering exception event is that the radio link control RLC entity of the receiving device does not receive the complete first data packet, and the free buffering capacity of the packet data convergence protocol PDCP entity is less than or equal to the capacity threshold.
3. The communication method of claim 1, wherein retransmitting the first data packet comprises: recoding the first data packet, wherein the reliability of a coding mode adopted by recoding is higher than that of an original coding mode;
And sending the recoded first data packet.
4. The communication method according to claim 1, wherein the transmission priority of the first data packet retransmitted is higher than the transmission priority of the other data packets.
5. The communication method according to claim 1, characterized by further comprising:
and stopping the transmission of other data packets except the first data packet.
6. The communication method according to claim 5, further comprising:
in response to the emergency report, starting a first timer;
and stopping retransmission of the first data packet and resuming transmission of the other data packets in response to expiration of the first timer or in response to receiving an indication of elimination of the buffering exception event.
7. The communication method according to claim 1, characterized in that the retransmitted first data packet carries a poll identity, said poll identity indicating to said receiving device to feed back said retransmission.
8. The communication method according to claim 1, wherein the emergency status report includes category indication information for indicating that the category of the status report is the emergency status report and packet information for indicating the first packet.
9. The communication method according to claim 8, wherein the class indication information is carried in a control protocol data unit type CPT field.
10. A communication device, comprising:
the receiving module is used for receiving an emergency state report, wherein the emergency state report is used for reporting a cache abnormal event which occurs to the receiving equipment, the cache abnormal event is that the first data packet is failed to be received and the idle cache capacity is smaller than or equal to a capacity threshold value;
and the sending module is used for retransmitting the first data packet in response to the emergency state report.
11. A method of communication, comprising:
in response to detecting the cache abnormal event, sending an emergency state report;
the emergency report is used for reporting the abnormal buffering event so as to trigger retransmission of the first data packet.
12. The communication method according to claim 11, wherein the buffering exception is that the radio link control RLC entity does not receive the complete first data packet, and the free buffering capacity of the packet data convergence protocol PDCP entity is less than or equal to the capacity threshold.
13. The communication method according to claim 11, characterized in that the method further comprises:
and receiving the recoded first data packet, wherein the reliability of the coding mode adopted by the recoding is higher than that of the original coding mode.
14. The communication method according to claim 11, wherein the transmission priority of the first data packet retransmitted is higher than the transmission priority of the other data packets.
15. The communication method according to claim 11, characterized in that the retransmitted first data packet carries a poll identity, said poll identity indicating a feedback of said retransmission.
16. The communication method according to claim 11, characterized by further comprising:
and sending an elimination indication of the cache abnormal event in response to the receiving of the first data packet.
17. The communication method according to claim 11, wherein the emergency status report includes category indication information for indicating that the category of the status report is the emergency status report and packet information for indicating the first packet.
18. The communication method according to claim 17, wherein the class indication information is carried in a control protocol data unit type CPT field.
19. The communication method of claim 11, wherein transmitting the emergency status report comprises: the emergency status report is sent periodically.
20. The communication method of claim 11, wherein transmitting the emergency status report comprises: in response to detecting the cache abnormal event, starting a first counter, wherein the first counter is used for counting other data packets received after the cache abnormal event is detected;
and triggering the transmission of the emergency state report and zeroing the first counter every time the value of the first counter reaches a set threshold value.
21. A communication device, comprising:
the sending module is used for responding to the detection of the cache abnormal event and sending an emergency state report;
the emergency report is used for reporting the abnormal buffering event so as to trigger retransmission of the first data packet.
22. A computer readable storage medium having stored thereon a computer program, which, when run by a processor, causes the communication method of any of claims 1 to 9 or 11 to 20 to be performed.
23. A communication device comprising a memory and a processor, the memory having stored thereon a computer program executable on the processor, characterized in that the processor executes the steps of the communication method according to any of claims 1 to 9 when the computer program is executed.
24. A communication device comprising a memory and a processor, the memory having stored thereon a computer program executable on the processor, characterized in that the processor executes the steps of the communication method according to any of claims 11 to 20 when the computer program is executed.
CN202211582473.8A 2022-12-09 2022-12-09 Communication method, communication device, and computer-readable storage medium Pending CN116033478A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211582473.8A CN116033478A (en) 2022-12-09 2022-12-09 Communication method, communication device, and computer-readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211582473.8A CN116033478A (en) 2022-12-09 2022-12-09 Communication method, communication device, and computer-readable storage medium

Publications (1)

Publication Number Publication Date
CN116033478A true CN116033478A (en) 2023-04-28

Family

ID=86090288

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211582473.8A Pending CN116033478A (en) 2022-12-09 2022-12-09 Communication method, communication device, and computer-readable storage medium

Country Status (1)

Country Link
CN (1) CN116033478A (en)

Similar Documents

Publication Publication Date Title
US11133897B2 (en) Data transmission method and apparatus
US9900798B2 (en) Polling and reporting mechanism
US8843175B2 (en) Apparatus and methods for mitigating protocol-induced back-offs in a communication network
EP2811681B1 (en) Method for moving a receive window in a radio access network
US8175014B2 (en) Method and apparatus for using a relay to provide physical and hybrid automatic repeat request functionalities
US8306061B2 (en) Method for retransmitting data unit using delivery status information
EP2238707B1 (en) Method of detecting and handling an endless rlc retransmission
US9461776B2 (en) Selecting a data unit for retransmission
US8565126B2 (en) Method and a transceiver for reducing retransmissions in a telecommunications system
JP2022547110A (en) Data retransmission method and device, data reception response method and device, and storage medium
US9930694B2 (en) Re-transmitting a poll to a peer protocol entity when a timer expires
KR102299792B1 (en) Transmission protection
WO2015192322A1 (en) Radio resource scheduling method and apparatus
WO2020147453A1 (en) Data transmission method and related apparatus
US20090181703A1 (en) Method and Apparatus for Triggering Status Report in a Wireless Communications System
US10470233B2 (en) RLC delivery failure resolution
CN104137507B (en) Feed back the message treatment method and device of packet loss
WO2020010511A1 (en) Data transmission method and base station
CN116033478A (en) Communication method, communication device, and computer-readable storage medium
US20230362721A1 (en) Method and apparatus for multicast and broadcast services
KR20100045860A (en) Method and user equipment of detecting problem of data transmission
KR100912785B1 (en) Method of reporting status report and receiver
WO2023137854A1 (en) Method for enhancing rlc acknowledge mode during retransmission overrun and under dual-no condition, and apparatuses
TW202406397A (en) A method for enhancing rlc and a user equipment thereof
JP2011055435A (en) Apparatus and method for retransmission control

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination