WO2022042379A1 - 数据处理方法、基站、终端及存储介质 - Google Patents
数据处理方法、基站、终端及存储介质 Download PDFInfo
- Publication number
- WO2022042379A1 WO2022042379A1 PCT/CN2021/113102 CN2021113102W WO2022042379A1 WO 2022042379 A1 WO2022042379 A1 WO 2022042379A1 CN 2021113102 W CN2021113102 W CN 2021113102W WO 2022042379 A1 WO2022042379 A1 WO 2022042379A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- tcp
- sequence number
- message
- packet
- pdcp sdu
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/06—Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless
Definitions
- the present application relates to, but is not limited to, the field of wireless communication technologies, and in particular, relates to a data processing method, a base station, a terminal, and a storage medium.
- the Packet Data Convergence Protocol (PDCP) layer is the protocol layer of the user plane, and the PDCP layer of the data sender parses the data packets from the upper layer and backs them up to the PDCP service data unit (Service Data Unit, SDU), encapsulated into a protocol data unit (Protocol Data Unit, PDU) and distributed to the data receiving end.
- SDU Service Data Unit
- PDU protocol Data Unit
- the PDCP layer will back up the PDCP SDUs and their PDCP sequence numbers corresponding to the unacknowledged PDCP PDUs.
- the PDCP PDUs that are not acknowledged in the source cell need to be back-transmitted to the destination cell with their corresponding PDCP SDUs and PDCP sequence numbers.
- the PDCP SDU backup in the data receiving end will be retransmitted when the PDCP is re-established in the destination cell, and the retransmission process will occupy air interface resources, and when the number of PDCP SDU backups is large, the amount of transmitted packets will be large, which is very difficult. It is easy to cause packet loss and affect business continuity.
- the RLC status report prohibit timer is configured, and the data sender receives the RLC sent by the data receiver. After the status report, delete the PDCP SDU backup that has been confirmed by the UE, thereby reducing the amount of packets during retransmission.
- the RLC status report is usually sent periodically, and unnecessary backup packets are still transmitted when the PDCP is re-established.
- Embodiments of the present application provide a data processing method, a base station, a terminal, and a storage medium.
- an embodiment of the present application provides a data processing method, including: acquiring a transmission control protocol TCP message, backing up a packet data aggregation protocol service data unit PDCP SDU corresponding to the TCP message, generating and saving the The sequence number code corresponding to the PDCP SDU; send the TCP message to the data receiving end; when receiving the confirmation ACK message carrying the confirmation sequence number sent by the data receiving end according to the TCP message, according to the ACK message
- the confirmation sequence number in the text determines the sequence number code that meets the confirmation condition from the stored sequence number code; deletes the PDCP SDU corresponding to the sequence number code that meets the confirmation condition.
- an embodiment of the present application further provides a base station, including: a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor implements the above when executing the computer program the data processing method described.
- an embodiment of the present application further provides a terminal, including: a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor implements the above when executing the computer program the data processing method described.
- embodiments of the present application further provide a computer-readable storage medium storing computer-executable instructions, where the computer-executable instructions are used to execute the above-mentioned method for obtaining preset path information or the above-mentioned data Approach.
- FIG. 1 is a flowchart of a data processing method provided by an embodiment of the present application.
- FIG. 2 is a schematic diagram of data sending and receiving between a data sending end and a data receiving end in a data processing method provided by another embodiment of the present application;
- FIG. 3 is a flowchart of determining that a TCP message is an optimizable message in a data processing method provided by another embodiment of the present application;
- FIG. 4 is a flowchart of determining that a TCP message is an optimizable message in a data processing method provided by another embodiment of the present application;
- FIG. 5 is a flowchart of determining that a TCP message is an optimizable message in a data processing method provided by another embodiment of the present application;
- FIG. 6 is a flowchart of determining that a TCP message is an optimizable message in a data processing method provided by another embodiment of the present application;
- Fig. 7 is a flow chart of determining the serial number code that meets the confirmation condition in a data processing method provided by another embodiment of the present application.
- FIG. 8 is a flowchart of determining the serial number encoding of the PDCP SDU in a data processing method provided by another embodiment of the present application.
- FIG. 9 is a schematic diagram of a base station apparatus for executing a data processing method provided by another embodiment of the present application.
- FIG. 10 is a schematic diagram of a terminal device for executing a data processing method according to another embodiment of the present application.
- the present application provides a data processing method, a base station, a terminal and a storage medium.
- the data processing method includes: acquiring a TCP message, backing up a PDCP SDU corresponding to the TCP message, and generating and saving a sequence number corresponding to the PDCP SDU encoding; sending the TCP message to the data receiving end; when receiving an ACK message carrying an acknowledgment sequence number sent by the data receiving end according to the TCP message, according to the acknowledgment sequence number in the ACK message Determine the sequence number code that meets the confirmation condition from the stored sequence number code; delete the PDCP SDU corresponding to the sequence number code that meets the confirmation condition.
- the sequence number determined according to the ACK message confirmation sequence number is the maximum acknowledgable sequence number code, which will be less than or equal to the maximum sequence number.
- the deletion of the PDCP SDU corresponding to the identifiable serial number code can delete the backup file of the PDCP SDU in a more timely manner, thereby reducing the amount of packets retransmitted by the PDCP.
- FIG. 1 is a flowchart of a data processing method applied to a data sending end provided by an embodiment of the present application.
- the data processing method includes but is not limited to step S110 , step S200 , step S300 and step S400 .
- Step S110 obtaining the TCP message, backing up the PDCP SDU corresponding to the TCP message, and generating and saving the sequence number code corresponding to the PDCP SDU.
- the sequence number code of the PDCP SDU can be stored in any form, such as the attribute information stored in the PDCP SDU, and the mapping relationship between the PDCP SDU and the sequence number code can also be generated. The unique correspondence of the serial number code is sufficient.
- the serial number code may be generated after encapsulating the PDCP SDU, or may be generated directly after being backed up, which is not limited in this embodiment.
- Step S120 sending the TCP packet to the data receiving end.
- PDCP SDUs are also delivered to the upper layer in sequence, so the last PDCP SDU delivered is confirmed, and the previous ones have been received by the higher layer.
- RLC SDUs allow out-of-order delivery
- their corresponding PDCP SDUs will be sorted and delivered to the upper layer in order if out-of-order distribution is not configured, so that the last delivered PDCP SDU is confirmed, then its previous All have been received by the higher layer.
- the sequence number code generated after the backup of the PDCP SDU can substantially reflect the encapsulation sequence of the message, and can more conveniently identify the PDCP SDU backup that can be deleted.
- Step S130 when receiving an ACK message carrying an acknowledgment sequence number sent by the data receiving end according to the TCP message, according to the acknowledgment sequence number in the ACK message, a sequence number code that meets the acknowledgment condition is determined from the stored sequence number codes.
- a bearer, an RLC instance, and a PDCP instance are usually established, and multiple TCP links can be provided in the same bearer at the same time, and data processing is usually performed between each TCP link. It is executed independently, and the link ID can be used to distinguish TCP links. Therefore, after receiving the ACK message, the corresponding link ID can be parsed from the ACK message first, and the ACK message can be used according to the link ID. Confirm the TCP link with the confirmation sequence number, and then perform subsequent operations to avoid mistakenly deleting PDCP SDUs of other TCP links.
- the data receiving end when it receives a TCP packet, it usually sends an ACK packet with an acknowledgment sequence number after determining the entire TCP packet. Therefore, the PDCP SDU determined by the acknowledgment sequence number of the ACK packet can be determined as It is fully confirmed, and there is no situation where the PDCP SDU backup is only partially confirmed.
- the confirmation condition can be specifically set according to the actual situation, for example, it is less than or equal to the determined sequence number code, and the PDCP SDU can be quickly delivered in batches according to the feature of PDCP SDU delivery in sequence, and the PDCP SDUs that can be deleted can be quickly determined in batches according to the sequence number code, so as to improve the PDCP performance. Efficiency of SDU backup deletion.
- the form of the serial number encoding can be a number related to the encapsulation order, or it can be a record of the relevant information of the last encapsulated PDCP SDU, which can realize batch determination of PDCP SDUs according to the encapsulation order, and those skilled in the art can It is motivated to adjust the specific form of serial number coding according to actual needs, and details are not repeated here.
- Step S140 delete the PDCP SDU corresponding to the serial number code that meets the confirmation condition.
- the deletion of the PDCP SDU may be the deletion of the backed up message, or the deletion of the entire PDCP SDU backup, which is not limited in this embodiment.
- the packets received by the data sending end can be of any type, and the sequence number codes are determined according to the encapsulation sequence after parsing. Therefore, after the sequence number codes that meet the conditions are determined, the PDCP corresponding to the deleted sequence code codes that meet the confirmation conditions is deleted.
- SDU can be the backup of any packet, even if the packet corresponding to the PDCP SDU is not a TCP packet, but its encapsulation order determines that its delivery order is before the PDCP SDU determined according to the confirmation sequence number in the ACK packet, so it can be inferred that The outgoing non-TCP packet has also been confirmed, so when the sequence number code meets the confirmation conditions, its PDCP SDU can be deleted together.
- step S140 of this embodiment when step S140 of this embodiment is performed, if an RLC status report is received, the deletion of the PDCP SDU may be completed according to the steps of this embodiment, and then the PDCP SDU in the data transmitting end is deleted according to the RLC status report.
- the steps of this embodiment may also be stopped and executed directly according to the RLC status report. The specific manner may be adjusted according to actual needs, which is not limited in this embodiment. It should be noted that the deletion of the backup of the PDCP SDU according to the RLC status report is a method in some situations in the art, and details are not repeated in this embodiment.
- step S140 of this embodiment when the data receiving end moves to cause cell switching, the data transmitting end no longer retransmits the deleted PDCP SDU backup, which effectively reduces the amount of data during PDCP retransmission. .
- FIG. 2 is a schematic diagram of sending and receiving a data receiving end and a data sending end according to an embodiment of the present application.
- the data sending end in this embodiment of the present application may be a base station or a terminal.
- the base station receives the TCP message sent by the server, parses the message, and encapsulates it.
- the terminal decapsulates it.
- the terminal constructs a TCP ACK packet according to the obtained TCP data packet, encapsulates it into a PDCP PDU and sends it to the base station.
- the base station decapsulates the PDCP and parses it out.
- the link identifier and the confirmation sequence number are determined according to the link identifier to which the TCP link belongs, and then the corresponding sequence number code is determined according to the confirmation sequence number, and the backup of the PDCP SDU less than or equal to the sequence number code in the PDCP retransmission queue is deleted.
- step S100 in the embodiment shown in FIG. 1 includes but is not limited to the following steps:
- Step S210 parsing the TCP message to obtain message information of the TCP message
- Step S220 determining that the TCP packet is an optimizable packet according to the packet information.
- the sequence number occupied by the packet is the length of the payload. For example, if the TCP sequence number of a TCP packet is 2 and the payload length is 2, then In the link, sequence numbers 2 to 4 are all occupied by this packet.
- sequence numbers 2 to 4 are all occupied by this packet.
- Optimized packets are several packets with consecutive sequence numbers in the same TCP link, so the position of an optimizeable packet in the TCP link can be quickly determined, and then encoded according to its sequence number, it can be quickly determined.
- Encapsulated PDCP SDU thus realizing backup deletion of PDCP SDU.
- the determination conditions of the optimizable packets can be adjusted according to actual needs, and there are no restrictions in this embodiment. According to the packet information of the optimizable packets and the acknowledgment sequence number of the ACK packet, the ones that meet the acknowledgment conditions can be determined from the stored sequence number codes.
- the serial number can be encoded.
- the message information may be any information that can be parsed from a TCP message, such as a link identifier, a TCP sequence number, a TCP payload length, etc., which is not limited in this embodiment.
- the message received by the data sender can be any type of message, such as a TCP message, a User Datagram Protocol (UDP) message, etc., and the data sender receives a different type of message.
- the packet After the packet, it can be parsed and encapsulated, and a serial number code can be generated and used for subsequent judgment, which is not limited in this embodiment.
- a serial number code can be generated and used for subsequent judgment, which is not limited in this embodiment.
- it can be set to non-optimized packets by default, and the corresponding PDCP SDUs can be deleted after determining the serial number encoding of the TCP packets.
- the message information includes a message type
- step S120 in the embodiment shown in FIG. 1 includes but is not limited to the following steps:
- Step S310 when determining that the TCP message is a non-retransmitted SYN message or a non-retransmitted SYN ACK message according to the message type, determine that the TCP link to which the TCP message belongs is an optimizable link, and determine that the TCP message to optimize the message.
- the SYN flag of the TCP packet is 1, the payload length of the TCP packet needs to be increased by 1, so the payload length of the SYN packet or the SYN ACK packet is always not zero.
- the non-retransmitted SYN message or the non-retransmitted SYN ACK message is usually the first message in the TCP link, so the sequence numbers of the SYN message or the SYN ACK message itself in the TCP link must be consecutive. Therefore, it can be determined that the packet can be optimized.
- the message information includes a message type, and the message information includes a TCP sequence number, a payload length, and a link identifier.
- Step S120 in the embodiment shown in FIG. 1 includes but is not limited to: The following steps:
- Step S320 when it is determined that the TCP packet is a data packet, the TCP link to which the TCP packet belongs is determined as an optimizable link according to the link identifier, and the TCP packet is determined as an optimizable packet according to the TCP sequence number and payload length.
- the first message of a TCP link is not a non-retransmitted SYN message or a SYN ACK message
- a TCP link is determined to be an optimizeable link
- the sequence number occupied by the packet is the length of the payload. Therefore, according to the TCP sequence number and payload length It can be determined whether the TCP packet is continuous with the sequence number occupied by the last optimizeable packet.
- the next packet can be generated according to its TCP sequence number and payload length.
- the reference sequence number of the message can be selected according to the actual requirement, and the details are not repeated here.
- step S320 in the embodiment shown in FIG. 5 includes but is not limited to the following steps:
- Step S410 when the payload length is greater than zero, and the TCP sequence number is greater than or equal to the sum of the TCP sequence number and the TCP payload length of the last optimizable packet belonging to the same TCP link as the TCP packet, it is determined that the TCP packet is optimizable. message.
- the TCP message when the payload length is zero, the TCP message does not occupy any sequence number, so the ACK message constructed by the data receiving end according to the TCP message will not carry the confirmation sequence number, and the sequence number cannot be encoded. match, so a TCP packet with a zero payload length is determined to be an unoptimizable packet by default.
- the TCP message when it is satisfied that the TCP sequence number is greater than or equal to the sum of the TCP sequence number and the TCP payload length of the last optimizeable message belonging to the same TCP link as the TCP message, the TCP message is determined to be an optimizeable message. Therefore, the sequence numbers of adjacent optimizeable packets must be consecutive. Since TCP packets are delivered in sequence, the TCP packet determined according to the acknowledgment signal in the ACK packet constructed from an optimizeable packet , the optimized packets before it will also be confirmed. At this time, the PDCP SDU backups that can be deleted can be quickly determined in batches, which effectively improves the efficiency of backup deletion.
- the message information further includes a TCP sequence number and a payload length
- step S130 in the embodiment shown in FIG. 4 also includes but is not limited to the following steps:
- Step S510 obtain the maximum acknowledgment information formed by the TCP sequence number and the payload length
- Step S520 when the confirmation sequence number in the ACK message is greater than or equal to the sum of the TCP sequence number and the payload length in the maximum acknowledgment information, confirm the sequence number code that is less than or equal to the sequence number code corresponding to the TCP message as the sequence number that meets the confirmation condition. coding.
- the maximum verifiable information may be information data stored independently in the data sending end, or may be stored in the PDCP instance of the data sending end, and can be used to store the message information of the latest encapsulated optimizable message. .
- the maximum acknowledgment information formed by the TCP sequence number and the payload length may be directly stored in the maximum acknowledgment information, or calculated according to the TCP sequence number and the payload length.
- the specific value is saved, and the specific method is adjusted according to the actual needs.
- the confirmation sequence number meets the conditions, the corresponding PDCP SDU can be matched according to the maximum verifiable information.
- the TCP message corresponding to the TCP sequence number is the maximum TCP sequence number message. Therefore, the TCP message encapsulated before the TCP message must have been confirmed, and the sequence number code of the PDCP SDU corresponding to the maximum TCP sequence number message is obtained as With reference to the code, the serial number code that meets the confirmation conditions can be quickly determined. It should be noted that since the serial number code is obtained according to the encapsulation order, the confirmation condition can be less than or equal to the serial number code.
- the serial number code matched according to the maximum TCP serial number packet is 5, and the backup is currently saved and not deleted.
- the serial number codes of the PDCP SDUs from 1 to 4 can be confirmed as the serial number codes that meet the confirmation conditions, and the backup of the PDCP SDUs corresponding to the serial number codes from 1 to 5 can be deleted.
- step S100 in the embodiment shown in FIG. 1 includes but is not limited to the following steps:
- Step S600 according to the encapsulation sequence of the PDCP SDU in the TCP link, sequence number coding is set for the PDCP SDU and saved.
- the data sending end after parsing the TCP message, the data sending end will encapsulate the TCP message into a PDCP PDU, and backup the PDCP SDU, so the encapsulation order of the TCP message can be followed by PDCP SDU.
- Set the sequence number code so that the sequence number code can reflect the encapsulation order of PDCP SDUs in the TCP link. Since PDCP PDUs are usually delivered in sequence, the data receiving end decapsulates and constructs ACK packets in sequence.
- the serial number code obtained by confirming the serial number is the largest confirmed serial number code, and the PDCP PDU delivered before it must have been confirmed.
- the SDU is determined to be the confirmed PDCP SDU, and the backup is deleted.
- the serial number coding is determined according to the encapsulation order, for non-optimizable packets, although the message information is not updated to the maximum acknowledgment information, it only means that the non-optimizable packets cannot be used for maximum acknowledgment. Determination of the sequence number encoding of the non-optimizable message will still be encapsulated into PDCP PDUs and backup PDCP SDUs. Therefore, in this embodiment, the message information of the optimized message and the determined sequence number of the ACK message are used to determine the sequence number encoding that meets the conditions.
- the corresponding TCP message should also include a non-optimized message, and the sequence number encoding can satisfy the confirmation condition in the above-mentioned embodiment.
- the base station is used as the data sending end, and the terminal is used as the data receiving end, but this does not limit the technical solution of this embodiment.
- the PDCP layer of the base station receives the SYN message sent by the server, and parses the following first message information from the SYN message: the first TCP payload length is 1, the first link identifier (client IP: 1.1.1.1, Server IP: 2.2.2.2, client port: 10000, server port: 20000), since the optimization conditions are met, the message ID is set to be optimized, and the message ID and the first message information are saved to the first backup PDCP SDU attribute information, save the first link identifier, the first TCP sequence number, and the first TCP payload length under the PDCP instance, after the packet is encapsulated into the first PDCP PDU, the first sequence number code is determined to be 1, and then the first The PDCP PDU is delivered to the lower layer and sent to the terminal.
- the TCP/IP layer constructs a SYN ACK message, and the second message information is as follows: the first acknowledgment sequence number is 2, the second link identifier (client IP: 1.1.1.1, server IP: 2.2.2.2, client port: 10000 , server port: 20000); the terminal delivers the SYN ACK message to the PDCP layer, and sends it to the base station through the PDCP, RLC and other protocol layers.
- the second message information is parsed from the TCP message. Since the second link identifier is the same as the first link identifier, it is obtained from the PDCP instance.
- the first packet information matches the first PDCP SDU whose sequence number is 1, then the first PDCP SDU satisfies the condition of being confirmed by the TCP packet sent by the terminal, and the backup packet of the first PDCP SDU is delete.
- the base station receives the first ACK message sent by the server, and parses out the third message information: the second TCP sequence number is 2, the second TCP payload length is 0, and the third link identifier (client IP: 1.1.1.1, Server IP: 2.2.2.2, client port: 10000, server port: 20000), since the length of the second TCP payload is 0, it does not meet the optimization conditions, and the packet identifier is determined to be non-optimizable.
- the third message information is updated to the attribute information of the second backup PDCP SDU. After the message is encapsulated into the second PDCP PDU, the second sequence number code is determined to be 2, and then the second PDCP PDU is delivered to the lower layer and sent to the terminal.
- the base station receives the data message sent by the server, and parses out the fourth message information: the third TCP sequence number is 2, the third TCP payload length is 100, and the fourth link identifier (client IP: 1.1.1.1, server IP : 2.2.2.2, client port: 10000, server port: 20000), the packet satisfies the conditions for optimization, and for the packet to be optimized, update the packet identifier and the fourth packet information to the third backup PDCP SDU , update the third TCP sequence number and the third TCP payload length to the PDCP instance, after the message is encapsulated into the third PDCP PDU, the third sequence number encoding is determined to be 3, and then the third PDCP PDU is delivered to the lower layer and sent to the terminal.
- the third TCP sequence number is 2
- the third TCP payload length is 100
- the fourth link identifier client IP: 1.1.1.1, server IP : 2.2.2.2, client port: 10000, server port: 20000
- the terminal After receiving the third PDCP PDU sent by the base station, the terminal constructs a second ACK message, wherein the second TCP acknowledgment sequence number of the second ACK message is 102, and sends it to the base station; the base station receives and parses the second ACK message.
- the second TCP confirmation sequence number is the sum of the third TCP sequence number and the third TCP payload length
- the third backup PDCP SDU is matched according to the third TCP sequence number and the third TCP payload length in the PDCP instance.
- the third sequence number is encoded as 3, and the second sequence number of the second backup PDCP SDU is encoded as 2. Therefore, the backup messages of the third backup PDCP SDU and the second backup PDCP SDU are deleted together.
- the PDCP layer of the base station receives the SYN message sent by the server, and parses the following first message information from the SYN message: the first TCP payload length is 1, the first link identifier (client IP: 1.1.1.1, Server IP: 2.2.2.2, client port: 10000, server port: 20000), since the optimization conditions are met, the message ID is set to be optimized, and the message ID and the first message information are saved to the first backup PDCP SDU attribute information, save the first link identifier, the first TCP sequence number, and the first TCP payload length under the PDCP instance, after the packet is encapsulated into the first PDCP PDU, the first sequence number code is determined to be 1, and then the first The PDCP PDU is delivered to the lower layer and sent to the terminal.
- the TCP/IP layer constructs a SYN ACK message, and the second message information is as follows: the first acknowledgment sequence number is 2, the second link identifier (client IP: 1.1.1.1, server IP: 2.2.2.2, client port: 10000 , server port: 20000); the terminal delivers the SYN ACK message to the PDCP layer, and sends it to the base station through the PDCP, RLC and other protocol layers.
- the second message information is parsed from the TCP message. Since the second link identifier is the same as the first link identifier, it is obtained from the PDCP instance.
- the first packet information matches the first PDCP SDU whose sequence number is 1, then the first PDCP SDU satisfies the condition of being confirmed by the TCP packet sent by the terminal, and the backup packet of the first PDCP SDU is delete.
- the base station receives the first ACK message sent by the server, and parses out the third message information: the second TCP sequence number is 2, the second TCP payload length is 0, and the third link identifier (client IP: 1.1.1.1, Server IP: 2.2.2.2, client port: 10000, server port: 20000), since the length of the second TCP payload is 0, it does not meet the optimization conditions, and the packet identifier is determined to be non-optimizable.
- the third message information is updated to the attribute information of the second backup PDCP SDU. After the message is encapsulated into the second PDCP PDU, the second sequence number code is determined to be 2, and then the second PDCP PDU is delivered to the lower layer and sent to the terminal.
- the base station receives the first data packet sent by the server, and parses out the fourth packet information: the third TCP sequence number is 102, the third TCP payload length is 100, and the fourth link identifier (client IP: 1.1.1.1, Server IP: 2.2.2.2, client port: 10000, server port: 20000), the first data packet satisfies the optimization conditions, the packet identifier is determined to be optimized, and the packet identifier and the fourth packet information are updated to Under the third backup PDCP SDU, update the third TCP sequence number and the third TCP payload length to the PDCP instance, after the packet is encapsulated into the third PDCP PDU, the third sequence number code is determined to be 3, and then the third PDCP PDU is delivered. to the lower layer and sent to the terminal.
- the third TCP sequence number is 102
- the third TCP payload length 100
- the fourth link identifier client IP: 1.1.1.1, Server IP: 2.2.2.2, client port: 10000, server port: 20000
- the terminal After receiving the first data packet sent by the base station, the terminal constructs a second ACK packet, wherein the second TCP acknowledgement sequence number of the second ACK packet is 2; the base station parses the second ACK packet sent by the terminal after receiving, Since the second confirmation sequence number is smaller than the sum of the third TCP sequence number and the third TCP payload length, the confirmation condition is not satisfied, and the deletion of the backup message is not performed.
- the base station receives the second data packet sent by the server, and parses out the fifth packet information: the fourth TCP sequence number is 2, the fourth TCP payload length is 100, and the fifth link identifier (client IP: 1.1.1.1, Server IP: 2.2.2.2, client port: 10000, server port: 20000), since the TCP sequence number of the current packet is less than the sum of the TCP sequence number and the length of the TCP payload stored in the PDCP instance, the optimization conditions are not met, and the packet The identification is determined to be non-optimizable, and the packet identification is stored under the fourth backup PDCP SDU. After the packet is encapsulated into the fourth PDCP PDU, the fourth sequence number code is determined to be 4, and then the fourth PDCP PDU is delivered to the lower layer and sent to the terminal. .
- the terminal After the terminal receives the second data packet sent by the base station, it constructs a third ACK packet, wherein the third TCP acknowledgment sequence number of the third ACK packet is 202;
- the three TCP confirmation sequence numbers are equal to the sum of the third TCP sequence number and the third TCP payload length, and the confirmation conditions are met.
- the third backup PDCP SDU is the maximum acknowledgable PDCP SDU. Since the third sequence number of the third backup PDCP SDU The code is 3, and the second sequence number of the second backup PDCP SDU is coded as 2, so the backup messages of the third backup PDCP SDU and the second backup PDCP SDU are deleted together.
- the PDCP layer of the base station receives the third data packet sent by the server, and parses out the sixth packet information: the fifth TCP sequence number is 202, the fifth TCP payload length is 100, and the sixth link identifier (client IP: 1.1. 1.1, server IP: 2.2.2.2, client port: 10000, server port: 20000), since the fifth TCP sequence number is equal to the sum of the third TCP sequence number and the third TCP payload length, the optimization conditions are met, and the message identifier is determined For optimization, the message identifier and the sixth message information are stored in the attribute information of the fifth backup PDCP SDU. After the message is encapsulated into the fifth PDCP PDU, the fifth sequence number code is determined to be 5, and then the fourth PDCP PDU is delivered. to the lower layer and sent to the terminal.
- the terminal After the terminal receives the third data packet sent by the base station, it constructs a fourth ACK packet, wherein the fourth TCP acknowledgment sequence number of the fourth data packet is 302; the base station receives the fourth ACK packet sent by the terminal, because the The fourth TCP confirmation sequence number is equal to the sum of the fifth TCP sequence number and the fifth TCP payload length, and the confirmation condition is met, and the fifth backup PDCP SDU is determined to be the largest acknowledgable PDCP SDU. Since the fifth sequence number is coded as 3, the fourth backup PDCP SDU The fourth sequence number is encoded as 4, so the backup messages of the fifth backup PDCP SDU and the fourth backup PDCP SDU are deleted together.
- the PDCP layer of the base station receives the SYN message sent by the server, and parses the following first message information from the SYN message: the first TCP payload length is 1, the first link identifier (client IP: 1.1.1.1, Server IP: 2.2.2.2, client port: 10000, server port: 20000), since the optimization conditions are met, the message ID is set to be optimized, and the message ID and the first message information are saved to the first backup PDCP SDU attribute information, save the first link identifier, the first TCP sequence number, and the first TCP payload length under the PDCP instance, after the packet is encapsulated into the first PDCP PDU, the first sequence number code is determined to be 1, and then the first The PDCP PDU is delivered to the lower layer and sent to the terminal.
- the TCP/IP layer constructs a SYN ACK message, and the second message information is as follows: the first acknowledgment sequence number is 2, the second link identifier (client IP: 1.1.1.1, server IP: 2.2.2.2, client port: 10000 , server port: 20000); the terminal delivers the SYN ACK message to the PDCP layer, and sends it to the base station through the PDCP, RLC and other protocol layers.
- the second message information is parsed from the TCP message. Since the second link identifier is the same as the first link identifier, it is obtained from the PDCP instance.
- the first packet information matches the first PDCP SDU whose sequence number is 1, then the first PDCP SDU satisfies the condition of being confirmed by the TCP packet sent by the terminal, and the backup packet of the first PDCP SDU is delete.
- the base station receives the first ACK message sent by the server, and parses out the third message information: the second TCP sequence number is 2, the second TCP payload length is 0, and the third link identifier (client IP: 1.1.1.1, Server IP: 2.2.2.2, client port: 10000, server port: 20000), since the length of the second TCP payload is 0, it does not meet the optimization conditions, and the packet identifier is determined to be non-optimizable.
- the third message information is updated to the attribute information of the second backup PDCP SDU. After the message is encapsulated into the second PDCP PDU, the second sequence number code is determined to be 2, and then the second PDCP PDU is delivered to the lower layer and sent to the terminal.
- the base station receives the UDP packet sent by the server. Since the UDP packet is not a TCP packet and does not meet the optimization conditions, the packet identifier is determined to be non-optimizable, and the packet identifier is saved to the third backup PDCP SDU, and the packet is encapsulated. After the third PDCP PDU is formed, the third sequence number code is determined to be 3, and then the third PDCP PDU is delivered to the lower layer and sent to the terminal
- the base station receives the data message sent by the server, and parses out the fourth message information: the third TCP sequence number is 2, the third TCP payload length is 100, and the fourth link identifier (client IP: 1.1.1.1, server IP : 2.2.2.2, client port: 10000, server port: 20000), the optimization conditions are met, and the message identifier is determined to be optimizeable.
- This message identifier is saved to the fourth backup PDCP SDU, and the message is encapsulated into the fourth backup PDCP SDU.
- the fourth sequence number code is determined to be 4, and then the fourth PDCP PDU is delivered to the lower layer and sent to the terminal.
- the terminal After the terminal receives the TCP DATA sent by the base station, it constructs a second ACK message, wherein the second TCP confirmation sequence number of the second ACK message is 102; the base station receives the second ACK message sent by the terminal, because the second TCP confirmation The sequence number is equal to the sum of the third TCP sequence number and the length of the third TCP payload, and the confirmation condition is met.
- the fourth backup PDCP SDU is the largest acknowledgable PDCP SDU
- the fourth sequence number of the fourth backup PDCP SDU is encoded as 4
- the second sequence number of the second backup PDCP SDU is coded as 2
- the third sequence number of the third backup PDCP SDU is coded as 3, so the backup messages of the second backup PDCP SDU, the third backup PDCP SDU and the fourth backup PDCP SDU are delete together.
- an embodiment of the present application further provides a base station.
- the base station 900 includes: a memory 920 , a processor 910 , and a computer program stored in the memory 920 and running on the processor 910 .
- the processor 910 and the memory 920 may be connected by a bus or otherwise.
- the non-transitory software programs and instructions required to implement the data processing method of the above embodiment are stored in the memory 920, and when executed by the processor 910, the data processing method in the above embodiment is executed, for example, the above-described FIG. 1 is executed.
- an embodiment of the present application further provides a terminal.
- the terminal 1000 includes: a memory 1020 , a processor 1010 , and a computer program stored in the memory 1020 and running on the processor 1010 .
- the processor 1010 and the memory 1020 may be connected by a bus or other means.
- the non-transitory software programs and instructions required to implement the data processing method of the above embodiment are stored in the memory 1020, and when executed by the processor 1010, the data processing method in the above embodiment is executed, for example, the above-described FIG. 1 is executed.
- an embodiment of the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor or controller, for example, by the above-mentioned
- the execution of a processor in the embodiment can cause the above-mentioned processor to execute the data processing method applied to the data sending end in the above-mentioned embodiment, for example, to execute the above-described method steps S110 to S140 in Method steps S210 to S220, method step S310 in FIG. 4 , method step S320 in FIG. 5 , method step S410 in FIG. 6 , method steps S510 to S520 in FIG. 7 , method step S600 in FIG. 8 .
- the embodiments of the present application include: acquiring a TCP message, backing up the PDCP SDU corresponding to the TCP message, generating and saving a sequence number code corresponding to the PDCP SDU; sending the TCP message to the data receiving end; To the ACK message carrying the acknowledgment sequence number sent by the data receiving end according to the TCP message, and according to the acknowledgment sequence number in the ACK message, determine the sequence number code that meets the acknowledgment condition from the stored sequence number code ; delete the PDCP SDU corresponding to the sequence number code that meets the confirmation condition.
- the sequence number determined according to the ACK message confirmation sequence number is encoded as the maximum acknowledgable sequence number code, which will be less than or equal to the maximum sequence number.
- the deletion of the PDCP SDU corresponding to the identifiable serial number code can delete the backup file of the PDCP SDU in a more timely manner, thereby reducing the amount of packets retransmitted by the PDCP.
- Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer.
- communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery media, as is well known to those of ordinary skill in the art .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
一种数据处理方法、基站、终端及存储介质,数据处理方法包括:获取传输控制协议TCP报文,备份与TCP报文对应的分组数据聚合协议业务数据单元PDCP SDU,生成并保存与PDCP SDU对应的序号编码(S110);将TCP报文发送至数据接收端(S120);当接收到由数据接收端根据TCP报文发送的携带有确认序号的确认ACK报文,根据ACK报文中的确认序号从被保存的序号编码中确定符合确认条件的序号编码(S130);删除与符合确认条件的序号编码对应的PDCP SDU(S140)。
Description
相关申请的交叉引用
本申请基于申请号为202010870213.5、申请日为2020年8月26日的中国专利申请提出,并要求该中国专利申请的优先权,该中国专利申请的全部内容在此引入本申请作为参考。
本申请涉及但不限于无线通信技术领域,尤其涉及一种数据处理方法、基站、终端及存储介质。
在无线通信中,分组数据聚合协议(Packet Data Convergence Protocol,PDCP)层是用户面的协议层,数据发送端的PDCP层将来自高层的数据报文解析后备份到PDCP业务数据单元(Service Data Unit,SDU),封装成协议数据单元(Protocol Data Unit,PDU)后分发至数据接收端。同时,PDCP层会对未被确认的PDCP PDU对应的PDCP SDU及其PDCP序号进行备份。在数据接收端切换场景的情况下,在源小区未被确认的PDCP PDU需要将其对应的PDCP SDU和PDCP序号反传到目的小区。同时,数据接收端内的PDCP SDU备份会在目的小区进行PDCP重建立的时候重传,重传的过程会占用空口资源,而且PDCP SDU备份的数量较多时,传输的报文量较多,很容易引起丢包,影响业务的连续性。
为了解决这个问题,通常在无线链路控制协议(Radio Link Control,RLC)层的确认模式(Acknowledged Mode,AM)下,配置RLC状态报告禁止定时器,数据发送端接收到数据接收端发送的RLC状态报告后,删除已被UE确认的PDCP SDU备份,从而减少重传时的报文量。但是RLC状态报告通常是周期性发送,PDCP重建立时仍然会传输不必要的备份报文。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种数据处理方法、基站、终端及存储介质。
第一方面,本申请实施例提供了一种数据处理方法,包括:获取传输控制协议TCP报文,备份与所述TCP报文对应的分组数据聚合协议业务数据单元PDCP SDU,生成并保存与所述PDCP SDU对应的序号编码;将所述TCP报文发送至数据接收端;当接收到由数据接收端根据所述TCP报文发送的携带有确认序号的确认ACK报文,根据所述ACK报文中的所述确认序号从被保存的所述序号编码中确定符合确认条件的序号编码;删除与所述符合确认条件的序号编码对应的PDCP SDU。
第二方面,本申请实施例还提供了一种基站,包括:存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,所述处理器执行所述计算机程序时实现如上所述的数据处理方法。
第三方面,本申请实施例还提供了一种终端,包括:存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,所述处理器执行所述计算机程序时实现如上所述的数据处理方法。
第四方面,本申请实施例还提供一种计算机可读存储介质,存储有计算机可执行指令, 所述计算机可执行指令用于执行如上所述的预置路径信息获取方法或如上所述的数据处理方法。
本申请的其它特征和优点将在随后的说明书中阐述,并且,部分地从说明书中变得显而易见,或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图用来提供对本申请技术方案的进一步理解,并且构成说明书的一部分,与本申请的实施例一起用于解释本申请的技术方案,并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的一种数据处理方法的流程图;
图2是本申请另一个实施例提供的一种数据处理方法中数据发送端和数据接收端的数据收发示意图;
图3是本申请另一个实施例提供的一种数据处理方法中确定TCP报文为可优化报文的流程图;
图4为是本申请另一个实施例提供的一种数据处理方法中确定TCP报文为可优化报文的流程图;
图5是本申请另一个实施例提供的一种数据处理方法中确定TCP报文为可优化报文的流程图;
图6是本申请另一个实施例提供的一种数据处理方法中确定TCP报文为可优化报文的流程图;
图7是本申请另一个实施例提供的一种数据处理方法中确定符合确认条件的序号编码的流程图;
图8是本申请另一个实施例提供的一种数据处理方法中确定PDCP SDU的序号编码的流程图;
图9是本申请另一个实施例提供的用于执行一种数据处理方法的基站装置示意图;
图10是本申请另一个实施例提供的用于执行一种数据处理方法的终端装置示意图。
为了使本申请的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本申请进行进一步详细说明。应当理解,此处所描述的具体实施例仅用以解释本申请,并不用于限定本申请。
需要说明的是,虽然在装置示意图中进行了功能模块划分,在流程图中示出了逻辑顺序,但是在某些情况下,可以以不同于装置中的模块划分,或流程图中的顺序执行所示出或描述的步骤。说明书、权利要求书或上述附图中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。
本申请提供了一种数据处理方法、基站、终端及存储介质,数据处理方法包括:获取TCP报文,备份与所述TCP报文对应的PDCP SDU,生成并保存与所述PDCP SDU对应的序号编码;将所述TCP报文发送至数据接收端;当接收到由数据接收端根据所述TCP报文发送的携带有确认序号的ACK报文,根据所述ACK报文中的所述确认序号从被保存的所述序号编码中确定符合确认条件的序号编码;删除与所述符合确认条件的序号编码对应的PDCP SDU。根据本申请实施例提供的方案,由于PDCP SDU在数据接收端是按序封装后投递给高层,根据ACK报文确认序号所确定的序号编码为最大可确认的序号编码,将小于或等于该最大可确认的序号编码所对应的PDCP SDU删除,能够更及时地删除PDCP SDU的备份文件,从而减少PDCP重传的报文量。
下面结合附图,对本申请实施例作进一步阐述。
如图1所示,图1是本申请一个实施例提供的应用于数据发送端的数据处理方法的流程图,该数据处理方法包括但不限于有步骤S110、步骤S200、步骤S300和步骤S400。
步骤S110,获取TCP报文,备份与TCP报文对应的PDCP SDU,生成并保存与PDCP SDU对应的序号编码。
在一实施例中,PDCP SDU的序号编码可以通过任意形式保存,例如保存到PDCP SDU的属性信息,也可以生成PDCP SDU与序号编码的映射关系,具体方式根据实际需求选取,能够实现PDCP SDU和序号编码的唯一对应即可。
在一实施例中,序号编码可以是对PDCP SDU进行封装后生成,也可以是在备份后直接生成,本实施例不多作限定。
步骤S120,将TCP报文发送至数据接收端。
需要说明的是,在数据接收端,PDCP SDU也是按序投递给高层的,因此最后投递的PDCP SDU被确认,则其之前的都已被高层接收。而对于5G,虽然RLC SDU允许乱序投递,但是其对应的PDCP SDU在未配置乱序分发的情况下,会排序后按序投递给高层,这样最后投递的PDCP SDU被确认,则其之前的都已被高层接收,基于上述原理,PDCP SDU的备份后生成的序号编码实质上能够体现报文的封装顺序,能够更加便利地识别出可以删除的PDCP SDU备份。
步骤S130,当接收到由数据接收端根据TCP报文发送的携带有确认序号的ACK报文,根据ACK报文中的确认序号从被保存的序号编码中确定符合确认条件的序号编码。
在一实施例中,在数据发送端的初始化阶段,通常会建立承载、RLC实例和PDCP实例,在同一个承载中可以同时具备多个TCP链路,对于数据的处理通常是各TCP链路之间独立执行,而链路标识能够用于区分TCP链路,因此,在接收到ACK报文后,可以先从ACK报文中解析出对应的链路标识,根据链路标识确定使用该ACK报文的确认序号进行确定的TCP链路,再进行后续操作,避免误删其他TCP链路的PDCP SDU。
需要说明的是,数据接收端接收到TCP报文,通常会在确定整段TCP报文后发送携带有确认序号的ACK报文,因此,ACK报文的确认序号所确定的PDCP SDU可以确定为被完全确认,并不会出现PDCP SDU备份只有部分被确认的情况。
在一实施例中,确认条件可以根据实际情况具体设定,例如小于或等于被确定的序号编码,能够利用PDCP SDU按序投递的特性,根据序号编码快速批量确定可删除的PDCP SDU,提高PDCP SDU备份删除的效率。
在一实施例中,序号编码的形式可以是与封装顺序相关的数字,也可以是记录上一个被封装的PDCP SDU的相关信息,能够实现按照封装顺序批量确定PDCP SDU即可,本领域技术人员有动机根据实际需求调整序号编码的具体形式,在此不再赘述。
步骤S140,删除与符合确认条件的序号编码对应的PDCP SDU。
在一实施例中,删除PDCP SDU可以是删除备份的报文,也可以是将整个PDCP SDU备 份进行删除,本实施例不多作限定。
基于上述实施例中,数据发送端接收到的报文可以是任意类型,解析后根据封装顺序确定序号编码,因此,当确定符合条件的序号编码后,删除的符合确认条件的序号编码对应的PDCP SDU可以是任意报文的备份,即使该PDCP SDU对应的报文并非TCP报文,但其封装顺序决定了其投递顺序在根据ACK报文中的确认序号所确定的PDCP SDU之前,因此可以推断出该非TCP报文也已经被确认,因此可以当该序号编码符合确认条件,可以将其PDCP SDU一并删除。
在一实施例中,在执行本实施例的步骤S140时,若接收到RLC状态报告,可以是先根据本实施例步骤完成PDCP SDU的删除,再根据RLC状态报告对数据发送端中的PDCP SDU备份进行处理,也可以停止执行本实施例的步骤,直接根据RLC状态报告执行,具体方式可以根据实际需求调整,本实施例不多作限定。需要说明的是,根据RLC状态报告对PDCP SDU的备份进行删除为本领域一些情形中的方法,本实施例不再过多赘述。
需要说明的是,在执行本实施例的步骤S140后,当数据接收端移动引起小区的切换,数据发送端不再重传已被删除的PDCP SDU备份,有效减少了PDCP重传时的数据量。
另外,在一实施例中,参考图2,图2为本申请实施例的数据接收端和数据发送端的收发示意图。需要说明的是,本申请实施例中的数据发送端可以是基站或者终端,当数据发送端是基站,数据接收端为终端,基站接收服务器发送的TCP报文,对报文进行解析后,封装成PDCP PDU并发送至终端,终端接收到PDCP PDU后进行解封装,终端根据获取的TCP数据报文构造出TCP ACK报文,封装成PDCP PDU并发送至基站,基站将PDCP解封装,解析出链路标识和确认序号,根据链路标识确定所属的TCP链路,再根据确认序号确定对应的序号编码,将PDCP重传队列中小于或等于该序号编码的PDCP SDU的备份删除。当数据发送端是终端,基站为数据接收端,其原理大致相同,在此不再赘述。
另外,参照图3,在一实施例中,图1所示实施例中的步骤S100包括但不限于有以下步骤:
步骤S210,解析TCP报文,得到TCP报文的报文信息;
步骤S220,根据报文信息确定TCP报文为可优化报文。
需要说明的是,根据TCP协议,如果TCP报文携带净荷,该报文占用的序号为净荷的长度,例如,TCP报文的TCP序号为2,净荷长度为2,则在该TCP链路中,序号2至4均被该报文占用,当若干个报文符合序号连续的特性,则在一个TCP报文被确认的情况下,在其之前的所有TCP报文均可以确定被确认,将上述序号可连续的TCP报文定义为可优化报文,反之为不可优化报文。可优化报文为同一TCP链路中所占序号连续的若干个报文,因此能够快速确定一个可优化报文在TCP链路中的位置,进而根据其序号编码,能够快速确定在其之前被封装的PDCP SDU,从而实现PDCP SDU的备份删除。可优化报文的确定条件可以根据实际需求调整,本实施例不多作限制,能够根据可优化报文的报文信息与ACK报文的确认序号从被保存的序号编码中确定符合确认条件的序号编码即可。
在一实施例中,报文信息可以是任意能够从TCP报文中解析得到的信息,例如链路标识,TCP序号、TCP净荷长度等,本实施例不多作限制。
在一实施例中,数据发送端接收到的报文可以是任意类型的报文,例如TCP报文、用户数据报协议(User Datagram Protocol,UDP)报文等,数据发送端接收到不同类型的 报文后均可以进行解析和封装,并生成序号编码并用于后续判断即可,本实施例不多作限定。需要说明的是,对于除TCP报文以外的其他类型的报文,可以默认设置为不可优化报文,通过TCP报文确定出序号编码后一并删除对于的PDCP SDU即可。
另外,参照图4,在一实施例中,报文信息包括报文类型,图1所示实施例中的步骤S120包括但不限于有以下步骤:
步骤S310,当根据报文类型确定TCP报文为非重传的SYN报文或非重传的SYN ACK报文,确定TCP报文所属的TCP链路为可优化链路,并且确定TCP报文为可优化报文。
需要说明的是,根据TCP协议,如果TCP报文的SYN标志为1,则该TCP报文的净荷长度需要加1,因此SYN报文或者SYN ACK报文的净荷长度始终不为零,且非重传的SYN报文或者非重传的SYN ACK报文通常为TCP链路中的第一个报文,因此TCP链路中的SYN报文或者SYN ACK报文本身的序号肯定连续,因此可以确定为可优化报文。
另外,参照图5,在一实施例中,报文信息包括报文类型,报文信息包括TCP序号、净荷长度和链路标识,图1所示实施例中的步骤S120包括但不限于有以下步骤:
步骤S320,当确定TCP报文为数据报文,根据链路标识确定TCP报文所属的TCP链路为可优化链路,根据TCP序号和净荷长度确定TCP报文为可优化报文。
在一实施例中,当一个TCP链路的第一个报文不是非重传的SYN报文或者SYN ACK报文,则无法确保该TCP链路的序号连续,而可优化报文的确定条件需要满足TCP序号的连续,因此,此时不具备确定可优化报文的前提,可以确定该TCP链路的所有报文均为不可优化报文。
需要说明的是,当确定TCP链路为可优化链路,且根据TCP协议,如果TCP报文携带净荷,该报文占用的序号为净荷的长度,因此,根据TCP序号和净荷长度可以确定该TCP报文是否与上一个可优化报文所占用的序号连续。在确定可优化报文时,可以通过TCP序号和净荷长度之和确定,也可以在确定一个报文为可优化报文后,根据其TCP序号和净荷长度生成下一个报文为可优化报文的参考序号,根据实际需求选取具体的方式即可,在此不再赘述。
另外,参照图6,在一实施例中,图5所示实施例中的步骤S320包括但不限于有以下步骤:
步骤S410,当净荷长度大于零,并且TCP序号大于或等于与TCP报文属于同一TCP链路的上一个可优化报文的TCP序号和TCP净荷长度之和,确定TCP报文为可优化报文。
基于上述实施例,当净荷长度为零,该TCP报文并未占据任何序号,因此数据接收端根据该TCP报文所构建出的ACK报文也不会携带确认序号,无法进行序号编码的匹配,因此净荷长度为零的TCP报文默认确定为不可优化报文。
在一实施例中,当满足TCP序号大于或等于与TCP报文属于同一TCP链路的上一个可优化报文的TCP序号和TCP净荷长度之和,将该TCP报文确定为可优化报文,因此,相邻的可优化报文的序号必定是连续的,由于TCP报文按序投递,因此根据一个可优化报文所构造出的ACK报文中的确认信号所确定的TCP报文,在其之前的可优化报文也必定会被确认,此时可以快速批量确定可以删除的PDCP SDU备份,有效提高备份删除的效率。
另外,参照图7,在一实施例中,报文信息还包括TCP序号和净荷长度,图4所示实施例中的步骤S130还包括但不限于有以下步骤:
步骤S510,获取由TCP序号和净荷长度构成的最大可确认信息;
步骤S520,当ACK报文中的确认序号大于或等于最大可确认信息中TCP序号和净荷长度之和,将小于或等于与TCP报文对应的序号编码的序号编码确认为符合确认条件的序号编码。
在一实施例中,最大可确认信息可以是数据发送端中独立保存的信息数据,也可以保存到数据发送端的PDCP实例中,能够用于保存最新封装的可优化报文的报文信息即可。
在一实施例中,TCP序号和净荷长度构成的最大可确认信息,可以是将TCP序号和净荷长度直接保存到最大可确认信息中,也可以是根据TCP序号和净荷长度计算得出具体数值后保存,具体方式根据实际需求调整,能够在确认序号满足条件时,根据最大可确认信息匹配出对应的PDCP SDU即可。
在一实施例中,当ACK报文中的确认序号大于或等于最大可确认信息中的TCP序号和净荷长度之和,则该TCP序号所对应的TCP报文已被全部确认,即该TCP序号所对应的TCP报文为最大TCP序号报文,因此,在该TCP报文之前被封装的TCP报文也必定已经被确认,获取该最大TCP序号报文所对应的PDCP SDU的序号编码作为参考编码,能够快速确定满足确认条件的序号编码。需要说明的是,由于序号编码按照封装顺序得出,因此确认条件可以是小于或等于该序号编码,例如,根据最大TCP序号报文匹配出的序号编码为5,当前被保存且未被删除备份的PDCP SDU的序号编码为1至4的均可以确认为符合确认条件的序号编码,将序号编码为1至5所对应的PDCP SDU的备份删除即可。
另外,参照图8,在一实施例中,图1所示实施例中的步骤S100包括但不限于有以下步骤:
步骤S600,根据PDCP SDU在TCP链路中的封装顺序依次为PDCP SDU设置序号编码并保存。
在一实施例中,根据图2所示,数据发送端在解析TCP报文后,会将该TCP报文封装成PDCP PDU,并备份PDCP SDU,因此TCP报文的封装顺序可以依次为PDCP SDU设置序号编码,使得序号编码能够反映该TCP链路中PDCP SDU的封装顺序,由于PDCP PDU通常按序投递,因此数据接收端解封装和构造ACK报文也是按序,因此,根据ACK报文的确认序号得出的序号编码为最大被确认的序号编码,在其之前投递的PDCP PDU也必然已经被确认,因此可以按照序号编码的排序,将小于或等于该序号编码的序号编码所对应的PDCP SDU确定为已被确认的PDCP SDU,并进行备份删除。
需要说明的是,由于序号编码按照封装顺序确定,对于不可优化报文而言,虽然其报文信息未被更新至最大可确认信息中,但仅意味着不可优化报文不能用于最大被确认的序号编码的确定,该不可优化报文依然会被封装成PDCP PDU并且备份PDCP SDU,因此本实施例通过可优化报文的报文信息和ACK报文的确定序号确定符合条件的序号编码所对应的TCP报文也应当包括不可优化报文,序号编码能够满足上述实施例中的确认条件即可。
为了对本申请实施例的技术方案进行详细阐述,以下以三个具体示例对本申请实施例技术方案进行进一步举例说明。
需要说明的是,为了方案叙述的便利,以下示例场景中以基站作为数据发送端,终端作为数据接收端,但这并不会对本实施例技术方案造成限制。
场景一:TCP流的TCP序号连续
基站的PDCP层收到服务器发送的SYN报文,从SYN报文中解析出如下第一报文信息:第一TCP净荷长度为1,第一链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),由于满足可优化条件,报文标识设置为可优化,将报文标识及第一报文信息保存到第一备份PDCP SDU的属性信息,将第一链路标识、第一TCP序号、第一TCP净荷长度保存到PDCP实例下,报文封装成第一PDCP PDU后,第一序号编码确定为1,再将第一PDCP PDU投递到低层发送给终端。
终端收到PDCP PDU后,解封装RLC协议时,RLC状态报告禁止定时器未超时,不发送RLC状态报告,解封装得出的报文经过RLC、PDCP协议层后,投递给TCP/IP层;TCP/IP层构造SYN ACK报文,第二报文信息如下:第一确认序号为2,第二链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000);终端将SYN ACK报文投递给PDCP层,经过PDCP、RLC等协议层发送给基站。
基站收到SYN ACK报文后,由于报文类型是TCP报文,对该TCP报文解析出第二报文信息,由于第二链路标识与第一链路标识相同,从PDCP实例中获取第一报文信息,根据第一报文信息匹配出序号编码为1的第一PDCP SDU,则第一PDCP SDU满足被终端发送的TCP报文确认的条件,将第一PDCP SDU的备份报文删除。
基站收到服务器发送的第一ACK报文,解析出第三报文信息:第二TCP序号为2,第二TCP净荷长度为0,第三链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),由于第二TCP净荷长度为0,因此不满足可优化条件,报文标识确定为不可优化,将报文标识和第三报文信息更新到第二备份PDCP SDU的属性信息,报文封装成第二PDCP PDU后,第二序号编码确定为2,再将第二PDCP PDU投递到低层发送给终端。
基站收到服务器发送的数据报文,解析出第四报文信息:第三TCP序号为2,第三TCP净荷长度为100,第四链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),该报文满足可优化条件,为可优化报文,将此报文标识及第四报文信息更新至第三备份PDCP SDU下,将第三TCP序号和第三TCP净荷长度更新到PDCP实例,报文封装成第三PDCP PDU后,第三序号编码确定为3,再将第三PDCP PDU投递到低层发送给终端。
终端收到基站发送第三PDCP PDU后,构造第二ACK报文,其中,第二ACK报文的第二TCP确认序号为102,发送给基站;基站接收并解析第二ACK报文,由于第二TCP确认序号为第三TCP序号和第三TCP净荷长度之和,根据PDCP实例中的第三TCP序号和第三TCP净荷长度匹配出第三备份PDCP SDU,由于第三备份PDCP SDU的第三序号编码为3,第二备份PDCP SDU的第二序号编码为2因此将第三备份PDCP SDU和第二备份PDCP SDU的备份报文一并删除。
场景二:TCP流的TCP序号乱序。
基站的PDCP层收到服务器发送的SYN报文,从SYN报文中解析出如下第一报文信息:第一TCP净荷长度为1,第一链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),由于满足可优化条件,报文标识设置为可优化,将报文标识及第一报文信息保存到第一备份PDCP SDU的属性信息,将第一链路标识、第一TCP序号、第一TCP净荷长度保存到PDCP实例下,报文封装成第一PDCP PDU后,第一 序号编码确定为1,再将第一PDCP PDU投递到低层发送给终端。
终端收到PDCP PDU后,解封装RLC协议时,RLC状态报告禁止定时器未超时,不发送RLC状态报告,解封装得出的报文经过RLC、PDCP协议层后,投递给TCP/IP层;TCP/IP层构造SYN ACK报文,第二报文信息如下:第一确认序号为2,第二链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000);终端将SYN ACK报文投递给PDCP层,经过PDCP、RLC等协议层发送给基站。
基站收到SYN ACK报文后,由于报文类型是TCP报文,对该TCP报文解析出第二报文信息,由于第二链路标识与第一链路标识相同,从PDCP实例中获取第一报文信息,根据第一报文信息匹配出序号编码为1的第一PDCP SDU,则第一PDCP SDU满足被终端发送的TCP报文确认的条件,将第一PDCP SDU的备份报文删除。
基站收到服务器发送的第一ACK报文,解析出第三报文信息:第二TCP序号为2,第二TCP净荷长度为0,第三链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),由于第二TCP净荷长度为0,因此不满足可优化条件,报文标识确定为不可优化,将报文标识和第三报文信息更新到第二备份PDCP SDU的属性信息,报文封装成第二PDCP PDU后,第二序号编码确定为2,再将第二PDCP PDU投递到低层发送给终端。
基站收到服务器发送的第一数据报文,解析出第四报文信息:第三TCP序号为102,第三TCP净荷长度为100,第四链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),该第一数据报文足优化条件,报文标识确定为可优化,将此报文标识及第四报文信息更新至到第三备份PDCP SDU下,将第三TCP序号和第三TCP净荷长度更新到PDCP实例,报文封装成第三PDCP PDU后,第三序号编码确定为3,再将第三PDCP PDU投递到低层发送给终端。
终端收到基站发送第一数据报文后,构造第二ACK报文,其中,第二ACK报文的第二TCP确认序号为2;基站收到终端发送的第二ACK报文后进行解析,由于第二确认序号小于第三TCP序号和第三TCP净荷长度之和,不满足确认条件,不执行备份报文的删除。
基站接收到服务器发送的第二数据报文,解析出第五报文信息:第四TCP序号为2,第四TCP净荷长度为100,第五链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),由于当前报文的TCP序号小于PDCP实例下存储的TCP序号与TCP净荷长度之和,不满足可优化条件,报文标识确定为不可优化,将此报文标识保存到第四备份PDCP SDU下,报文封装成第四PDCP PDU后,第四序号编码确定为4,再将第四PDCP PDU投递到低层发送给终端。
终端收到基站发送的第二数据报文后,构造第三ACK报文,其中,第三ACK报文的第三TCP确认序号为202;基站收到终端发送的第三ACK报文,由于第三TCP确认序号等于第三TCP序号和第三TCP净荷长度之和,满足确认条件,参考上述方式确定第三备份PDCP SDU为最大可确认的PDCP SDU,由于第三备份PDCP SDU的第三序号编码为3,第二备份PDCP SDU的第二序号编码为2,因此将第三备份PDCP SDU和第二备份PDCP SDU的备份报文一并删除。
基站PDCP层收到服务器发送的第三数据报文,解析出第六报文信息:第五TCP序号为202,第五TCP净荷长度为100,第六链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2, 客户端端口:10000,服务器端口:20000),由于第五TCP序号等于第三TCP序号和第三TCP净荷长度之和,满足可优化条件,报文标识确定为可优化,将报文标识和第六报文信息保存到第五备份PDCP SDU的属性信息,报文封装成第五PDCP PDU后,第五序号编码确定为5,再将第四PDCP PDU投递到低层发送给终端。
终端收到基站发送的第三数据报文后,构造第四ACK报文,其中,第四数据报文的第四TCP确认序号为302;基站收到终端发送的第四ACK报文,由于第四TCP确认序号等于第五TCP序号和第五TCP净荷长度之和,满足确认条件,确定第五备份PDCP SDU为最大可确认的PDCP SDU,由于第五序号编码为3,第四备份PDCP SDU的第四序号编码为4,因此将第五备份PDCP SDU和第四备份PDCP SDU的备份报文一并删除。
场景三:混合业务场景
基站的PDCP层收到服务器发送的SYN报文,从SYN报文中解析出如下第一报文信息:第一TCP净荷长度为1,第一链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),由于满足可优化条件,报文标识设置为可优化,将报文标识及第一报文信息保存到第一备份PDCP SDU的属性信息,将第一链路标识、第一TCP序号、第一TCP净荷长度保存到PDCP实例下,报文封装成第一PDCP PDU后,第一序号编码确定为1,再将第一PDCP PDU投递到低层发送给终端。
终端收到PDCP PDU后,解封装RLC协议时,RLC状态报告禁止定时器未超时,不发送RLC状态报告,解封装得出的报文经过RLC、PDCP协议层后,投递给TCP/IP层;TCP/IP层构造SYN ACK报文,第二报文信息如下:第一确认序号为2,第二链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000);终端将SYN ACK报文投递给PDCP层,经过PDCP、RLC等协议层发送给基站。
基站收到SYN ACK报文后,由于报文类型是TCP报文,对该TCP报文解析出第二报文信息,由于第二链路标识与第一链路标识相同,从PDCP实例中获取第一报文信息,根据第一报文信息匹配出序号编码为1的第一PDCP SDU,则第一PDCP SDU满足被终端发送的TCP报文确认的条件,将第一PDCP SDU的备份报文删除。
基站收到服务器发送的第一ACK报文,解析出第三报文信息:第二TCP序号为2,第二TCP净荷长度为0,第三链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),由于第二TCP净荷长度为0,因此不满足可优化条件,报文标识确定为不可优化,将报文标识和第三报文信息更新到第二备份PDCP SDU的属性信息,报文封装成第二PDCP PDU后,第二序号编码确定为2,再将第二PDCP PDU投递到低层发送给终端。
基站接收到服务器发送的UDP报文,由于UDP报文不属于TCP报文,不满足优化条件,报文标识确定为不可优化,将此报文标识保存到第三备份PDCP SDU下,报文封装成第三PDCP PDU后,第三序号编码确定为3,再将第三PDCP PDU投递到低层发送给终端
基站接收到服务器发送的数据报文,解析出第四报文信息:第三TCP序号为2,第三TCP净荷长度为100,第四链路标识(客户端IP:1.1.1.1,服务器IP:2.2.2.2,客户端端口:10000,服务器端口:20000),满足可优化条件,报文标识确定为可优化,将此报文标识保存到第四备份PDCP SDU下,报文封装成第四PDCP PDU后,第四序号编码确定为4,再将第四PDCP PDU投递到低层发送给终端。
终端收到基站发送的TCP DATA后,构造第二ACK报文,其中,第二ACK报文的第二TCP确认序号为102;基站收到终端发送的第二ACK报文,由于第二TCP确认序号等于第三TCP序号和第三TCP净荷长度之和,满足确认条件,参考上述方式确定第四备份PDCP SDU为最大可确认的PDCP SDU,由于第四备份PDCP SDU的第四序号编码为4,第二备份PDCP SDU的第二序号编码为2,第三备份PDCP SDU的第三序号编码为3,因此将第二备份PDCP SDU、第三备份PDCP SDU和第四备份PDCP SDU的备份报文一并删除。
另外,参考图9,本申请的一个实施例还提供了一种基站,该基站900包括:存储器920、处理器910及存储在存储器920上并可在处理器910上运行的计算机程序。
处理器910和存储器920可以通过总线或者其他方式连接。
实现上述实施例的数据处理方法所需的非暂态软件程序以及指令存储在存储器920中,当被处理器910执行时,执行上述实施例中的数据处理方法,例如,执行以上描述的图1中的方法步骤S110至步骤S140,图3中的方法步骤S210至步骤S220,图4中的方法步骤S310,图5中的方法步骤S320,图6中的方法步骤S410,图7中的方法步骤S510至步骤S520,图8中的方法步骤S600。
另外,参考图10,本申请的一个实施例还提供了一种终端,该终端1000包括:存储器1020、处理器1010及存储在存储器1020上并可在处理器1010上运行的计算机程序。
处理器1010和存储器1020可以通过总线或者其他方式连接。
实现上述实施例的数据处理方法所需的非暂态软件程序以及指令存储在存储器1020中,当被处理器1010执行时,执行上述实施例中的数据处理方法,例如,执行以上描述的图1中的方法步骤S110至步骤S140,图3中的方法步骤S210至步骤S220,图4中的方法步骤S310,图5中的方法步骤S320,图6中的方法步骤S410,图7中的方法步骤S510至步骤S520,图8中的方法步骤S600。
以上所描述的装置实施例仅仅是示意性的,其中作为分离部件说明的单元可以是或者也可以不是物理上分开的,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
此外,本申请的一个实施例还提供了一种计算机可读存储介质,该计算机可读存储介质存储有计算机可执行指令,该计算机可执行指令被一个处理器或控制器执行,例如,被上述实施例中的一个处理器执行,可使得上述处理器执行上述实施例中的应用于数据发送端的数据处理方法,例如,执行以上描述的图1中的方法步骤S110至步骤S140,图3中的方法步骤S210至步骤S220,图4中的方法步骤S310,图5中的方法步骤S320,图6中的方法步骤S410,图7中的方法步骤S510至步骤S520,图8中的方法步骤S600。
本申请实施例包括:获取TCP报文,备份与所述TCP报文对应的PDCP SDU,生成并保存与所述PDCP SDU对应的序号编码;将所述TCP报文发送至数据接收端;当接收到由数据接收端根据所述TCP报文发送的携带有确认序号的ACK报文,根据所述ACK报文中的所述确认序号从被保存的所述序号编码中确定符合确认条件的序号编码;删除与所述符合确认条件的序号编码对应的PDCP SDU。根据本申请实施例提供的方案,由于PDCP SDU在数据接收端是按序封装后投递给高层,根据ACK报文确认序号所确定的序号编码为最大可确认的序号编码,将小于或等于该最大可确认的序号编码所对应的PDCP SDU删除,能够更及时地删除PDCP SDU的备份文件,从而减少PDCP重传的报文量。
本领域普通技术人员可以理解,上文中所公开方法中的全部或某些步骤可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器,如中央处理器、数字信号处理器或微处理器执行的软件,或者被实施为硬件,或者被实施为集成电路,如专用集成电路。这样的软件可以分布在计算机可读介质上,计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的,术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外,本领域普通技术人员公知的是,通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据,并且可包括任何信息递送介质。
以上是对本申请的一些实施进行了具体说明,但本申请并不局限于上述实施方式,熟悉本领域的技术人员在不违背本申请范围的前提下还可作出种种的等同变形或替换,这些等同的变形或替换均包含在本申请权利要求所限定的范围内。
Claims (10)
- 一种数据处理方法,应用于数据发送端,包括:获取传输控制协议TCP报文,备份与所述TCP报文对应的分组数据聚合协议业务数据单元PDCP SDU,生成并保存与所述PDCP SDU对应的序号编码;将所述TCP报文发送至数据接收端;当接收到由数据接收端根据所述TCP报文发送的携带有确认序号的确认ACK报文,根据所述ACK报文中的所述确认序号从被保存的所述序号编码中确定符合确认条件的序号编码;删除与所述符合确认条件的序号编码对应的PDCP SDU。
- 根据权利要求1所述的数据处理方法,其中,在所述备份与所述TCP报文对应的PDCP SDU之前,还包括:解析所述TCP报文,得到所述TCP报文的报文信息;根据所述报文信息确定所述TCP报文为可优化报文。
- 根据权利要求2所述的数据处理方法,其中,所述报文信息包括报文类型,所述根据所述报文信息确定所述TCP报文为可优化报文,包括:当根据所述报文类型确定所述TCP报文为非重传的同步SYN报文或非重传的同步确认SYN ACK报文,确定所述TCP报文所属的TCP链路为可优化链路,并且确定所述TCP报文为可优化报文。
- 根据权利要求2所述的数据处理方法,其中,所述报文信息包括TCP序号、净荷长度和链路标识,所述根据所述报文信息确定所述TCP报文为可优化报文,包括:当确定所述TCP报文为数据报文,根据所述链路标识确定所述TCP报文所属的TCP链路为可优化链路,根据所述TCP序号和所述净荷长度确定所述TCP报文为可优化报文。
- 根据权利要求4所述的数据处理方法,其中,所述根据所述TCP序号和所述净荷长度确定所述TCP报文为可优化报文,包括:当所述净荷长度大于零,并且所述TCP序号大于或等于与所述TCP报文属于同一TCP链路的上一个可优化报文的TCP序号和TCP净荷长度之和,确定所述TCP报文为可优化报文。
- 根据权利要求2所述的数据处理方法,其中,所述报文信息还包括TCP序号和净荷长度,所述根据所述ACK报文中的所述确认序号从被保存的所述序号编码中确定符合确认条件的序号编码,包括:获取由所述TCP序号和所述净荷长度构成的最大可确认信息;当所述ACK报文中的所述确认序号大于或等于所述最大可确认信息中所述TCP序号和所述净荷长度之和,将小于或等于与所述TCP报文对应的序号编码的序号编码确认为符合确认条件的序号编码。
- 根据权利要求1所述的数据处理方法,其中,所述生成并保存与所述PDCP SDU对应的序号编码,包括:根据所述PDCP SDU在TCP链路中的封装顺序依次为所述PDCP SDU设置所述序号编码并保存。
- 一种基站,包括:存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,其中,所述处理器执行所述计算机程序时实现如权利要求1至7中任意一项所述 的数据处理方法。
- 一种终端,包括:存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,其中,所述处理器执行所述计算机程序时实现如权利要求1至7中任意一项所述的数据处理方法。
- 一种计算机可读存储介质,存储有计算机可执行指令,其中,所述计算机可执行指令用于执行如权利要求1至7中任意一项所述的数据处理方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010870213.5A CN114126084A (zh) | 2020-08-26 | 2020-08-26 | 数据处理方法、基站、终端及存储介质 |
CN202010870213.5 | 2020-08-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022042379A1 true WO2022042379A1 (zh) | 2022-03-03 |
Family
ID=80354578
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/113102 WO2022042379A1 (zh) | 2020-08-26 | 2021-08-17 | 数据处理方法、基站、终端及存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN114126084A (zh) |
WO (1) | WO2022042379A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115695583B (zh) * | 2022-05-08 | 2023-12-01 | 荣耀终端有限公司 | 数据传输方法及电子设备 |
CN115314266A (zh) * | 2022-07-27 | 2022-11-08 | 阿里云计算有限公司 | 访问控制方法、装置、电子设备及可读存储介质 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1437368A (zh) * | 2002-02-08 | 2003-08-20 | 华硕电脑股份有限公司 | 数据传输的确认方法 |
CN101729524A (zh) * | 2008-11-03 | 2010-06-09 | 大唐移动通信设备有限公司 | 一种数据处理方法、装置、rlc实体及pdcp实体 |
CN103888222A (zh) * | 2014-03-21 | 2014-06-25 | 电信科学技术研究院 | 一种数据包处理方法及装置 |
US20170041766A1 (en) * | 2015-08-05 | 2017-02-09 | Qualcomm Incorporated | Media access control segmentation and packet data convergence protocol delivery notification with enhanced component carriers |
WO2018160014A1 (ko) * | 2017-02-28 | 2018-09-07 | 삼성전자 주식회사 | 기지국간 캐리어 집적을 지원하기 위한 패킷 생성 및 분배 방법 및 장치 |
CN109792363A (zh) * | 2016-11-01 | 2019-05-21 | 英特尔Ip公司 | 在lte-wlan聚合中避免通过wlan的上行链路中的hfn去同步 |
-
2020
- 2020-08-26 CN CN202010870213.5A patent/CN114126084A/zh active Pending
-
2021
- 2021-08-17 WO PCT/CN2021/113102 patent/WO2022042379A1/zh active Application Filing
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1437368A (zh) * | 2002-02-08 | 2003-08-20 | 华硕电脑股份有限公司 | 数据传输的确认方法 |
CN101729524A (zh) * | 2008-11-03 | 2010-06-09 | 大唐移动通信设备有限公司 | 一种数据处理方法、装置、rlc实体及pdcp实体 |
CN103888222A (zh) * | 2014-03-21 | 2014-06-25 | 电信科学技术研究院 | 一种数据包处理方法及装置 |
CN108306708A (zh) * | 2014-03-21 | 2018-07-20 | 电信科学技术研究院 | 一种数据包处理方法及装置 |
US20170041766A1 (en) * | 2015-08-05 | 2017-02-09 | Qualcomm Incorporated | Media access control segmentation and packet data convergence protocol delivery notification with enhanced component carriers |
CN109792363A (zh) * | 2016-11-01 | 2019-05-21 | 英特尔Ip公司 | 在lte-wlan聚合中避免通过wlan的上行链路中的hfn去同步 |
WO2018160014A1 (ko) * | 2017-02-28 | 2018-09-07 | 삼성전자 주식회사 | 기지국간 캐리어 집적을 지원하기 위한 패킷 생성 및 분배 방법 및 장치 |
Also Published As
Publication number | Publication date |
---|---|
CN114126084A (zh) | 2022-03-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9860915B2 (en) | Apparatus and method for moving a receive window in a radio access network | |
US6301479B1 (en) | Technique for providing a secure link in a mobile communication system | |
CN110266445B (zh) | 用于重新配置承载的方法及设备 | |
WO2018127238A1 (zh) | 信息处理方法及装置 | |
KR101387537B1 (ko) | 성공적으로 수신했으나 헤더 압축 복원에 실패한 패킷의 처리 방법 | |
EP2168270B1 (en) | A method for handling correctly received but header compression failed packets | |
JP5215413B2 (ja) | 再送プロトコルのためのステータス報告 | |
CN108632229B (zh) | 一种多连接中的头压缩方法、解头压缩方法及装置 | |
CN100391201C (zh) | 一种保持分组数据协议汇聚子层序列号同步的方法 | |
CN109246848B (zh) | 一种rlc实体的重建立方法及装置 | |
WO2017185941A1 (zh) | 一种数据传输方法及相关设备 | |
WO2022042379A1 (zh) | 数据处理方法、基站、终端及存储介质 | |
CN111525989A (zh) | 发送rlc状态报告的方法、设备和存储介质 | |
CN107959554A (zh) | 一种数据的重传方法及装置 | |
CN112351459A (zh) | Pdcp实体发送端/接收端的执行方法、pdcp实体及通信设备 | |
JP2004179917A (ja) | ワイヤレスコミュニケーションシステムにおける不測の伝送中断を処理する方法 | |
WO2023193269A1 (zh) | 数据处理方法、装置、通信设备及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21860217 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 03/07/2023) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21860217 Country of ref document: EP Kind code of ref document: A1 |