CN114126084A - Data processing method, base station, terminal and storage medium - Google Patents

Data processing method, base station, terminal and storage medium Download PDF

Info

Publication number
CN114126084A
CN114126084A CN202010870213.5A CN202010870213A CN114126084A CN 114126084 A CN114126084 A CN 114126084A CN 202010870213 A CN202010870213 A CN 202010870213A CN 114126084 A CN114126084 A CN 114126084A
Authority
CN
China
Prior art keywords
message
tcp
sequence number
pdcp
packet
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
CN202010870213.5A
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN202010870213.5A priority Critical patent/CN114126084A/en
Priority to PCT/CN2021/113102 priority patent/WO2022042379A1/en
Publication of CN114126084A publication Critical patent/CN114126084A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/12Setup of transport tunnels
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/1607Details of the supervisory signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/06Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/06Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a data processing method, a base station, a terminal and a storage medium, wherein the data processing method comprises the following steps: acquiring a Transmission Control Protocol (TCP) message, backing up a Packet Data Convergence Protocol (PDCP) service data unit (PDCP SDU) corresponding to the TCP message, and generating and storing a sequence number code corresponding to the PDCP SDU; sending the TCP message to a data receiving end; when receiving an acknowledgement ACK message which is sent by a data receiving end according to a TCP message and carries an acknowledgement sequence number, determining a sequence number code which meets the acknowledgement condition from the stored sequence number codes according to the acknowledgement sequence number in the ACK message; and deleting the PDCP SDU corresponding to the sequence number coding which meets the confirmation condition. According to the scheme provided by the embodiment of the invention, the sequence number code determined according to the ACK message confirmation sequence number is the maximum recognizable sequence number code, the PDCP SDU corresponding to the sequence number code less than or equal to the maximum recognizable sequence number code is deleted, the backup file of the PDCP SDU can be deleted more timely, and the message volume of the PDCP retransmission is reduced.

Description

Data processing method, base station, terminal and storage medium
Technical Field
The present invention relates to, but not limited to, the field of wireless communication technologies, and in particular, to a data processing method, a base station, a terminal, and a storage medium.
Background
In wireless communication, a Packet Data Convergence Protocol (PDCP) layer is a Protocol layer of a user plane, and a PDCP layer of a Data transmitting end parses a Data Packet from a higher layer, backs up the Data Packet to a PDCP Service Data Unit (SDU), encapsulates the Data Packet into a Protocol Data Unit (PDU), and distributes the PDU to a Data receiving end. Meanwhile, the PDCP layer backs up PDCP SDUs and PDCP sequence numbers corresponding to unacknowledged PDCP PDUs. Under the condition of switching scenes at a data receiving end, the PDCP PDU which is not confirmed in the source cell needs to reversely transmit the corresponding PDCP SDU and PDCP sequence number to the target cell. Meanwhile, the backup of PDCP SDUs in the data receiving end is retransmitted when the PDCP is re-established in the target cell, the retransmission process occupies the air interface resources, and when the number of the backup of PDCP SDUs is large, the amount of transmitted messages is large, which easily causes packet loss, and affects the continuity of the service.
In order to solve this problem, usually, in an Acknowledgement Mode (AM) of a Radio Link Control (RLC) layer, an RLC status report prohibition timer is configured, and after receiving an RLC status report sent by a data receiving end, a data sending end deletes a PDCP SDU backup that has been Acknowledged by the UE, thereby reducing a packet size during retransmission. However, the RLC status report is usually sent periodically, and unnecessary backup messages are still transmitted when the PDCP is re-established.
Disclosure of Invention
The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.
Compared with deleting the backup file of the PDCP SDU by using the RLC status report, the embodiment of the invention can delete the backup file of the PDCP SDU more timely, thereby reducing the message volume of the PDCP retransmission.
In a first aspect, an embodiment of the present invention provides a data processing method, including:
acquiring a Transmission Control Protocol (TCP) message, backing up a Packet Data Convergence Protocol (PDCP) service data unit (PDCP SDU) corresponding to the TCP message, and generating and storing a sequence number code corresponding to the PDCP SDU;
sending the TCP message to a data receiving end;
when an Acknowledgement (ACK) message which is sent by a data receiving end according to the TCP message and carries an acknowledgement sequence number is received, determining a sequence number code which meets an acknowledgement condition from the stored sequence number codes according to the acknowledgement sequence number in the ACK message;
and deleting the PDCP SDU corresponding to the sequence number coding which meets the confirmation condition.
In a second aspect, an embodiment of the present invention further provides a base station, including: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor implements the data processing method as described above.
In a third aspect, an embodiment of the present invention further provides a terminal, including: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor implements the data processing method as described above.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, which stores computer-executable instructions, where the computer-executable instructions are configured to execute the preset path information obtaining method or the data processing method described above.
The embodiment of the invention comprises the following steps: acquiring a TCP message, backing up a PDCP SDU corresponding to the TCP message, and generating and storing a sequence number code corresponding to the PDCP SDU; sending the TCP message to a data receiving end; when an ACK message which is sent by a data receiving end according to the TCP message and carries an acknowledgement sequence number is received, determining a sequence number code which meets the acknowledgement condition from the stored sequence number codes according to the acknowledgement sequence number in the ACK message; and deleting the PDCP SDU corresponding to the sequence number coding which meets the confirmation condition. According to the scheme provided by the embodiment of the invention, as the PDCP SDU is delivered to the high layer after being encapsulated in sequence at the data receiving end, the sequence number code determined according to the ACK message confirmation sequence number is the maximum recognizable sequence number code, and the PDCP SDU corresponding to the sequence number code less than or equal to the maximum recognizable sequence number code is deleted, the backup file of the PDCP SDU can be deleted more timely, thereby reducing the message volume of the PDCP retransmission.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.
FIG. 1 is a flow chart of a data processing method provided by an embodiment of the invention;
fig. 2 is a schematic diagram of data transceiving of a data transmitting end and a data receiving end in a data processing method according to another embodiment of the present invention;
fig. 3 is a flowchart of determining a TCP packet as an optimizable packet in a data processing method according to another embodiment of the present invention;
fig. 4 is a flowchart illustrating a method for processing data according to another embodiment of the present invention, where the TCP packet is determined to be an optimizable packet;
fig. 5 is a flowchart of determining a TCP packet as an optimizable packet in a data processing method according to another embodiment of the present invention;
fig. 6 is a flowchart of determining a TCP packet as an optimizable packet in a data processing method according to another embodiment of the present invention;
fig. 7 is a flowchart of sequence number encoding for determining whether a validation condition is met in a data processing method according to another embodiment of the present invention;
fig. 8 is a flowchart for determining sequence number coding of PDCP SDUs in a data processing method according to another embodiment of the present invention;
fig. 9 is a schematic diagram of a base station apparatus for performing a data processing method according to another embodiment of the present invention;
fig. 10 is a schematic diagram of a terminal device for executing a data processing method according to another embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
It should be noted that although functional blocks are partitioned in a schematic diagram of an apparatus and a logical order is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the partitioning of blocks in the apparatus or the order in the flowchart. The terms "first," "second," and the like in the description, in the claims, or in the drawings described above, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
The invention provides a data processing method, a base station, a terminal and a storage medium, wherein the data processing method comprises the following steps: acquiring a TCP message, backing up a PDCP SDU corresponding to the TCP message, and generating and storing a sequence number code corresponding to the PDCP SDU; sending the TCP message to a data receiving end; when an ACK message which is sent by a data receiving end according to the TCP message and carries an acknowledgement sequence number is received, determining a sequence number code which meets the acknowledgement condition from the stored sequence number codes according to the acknowledgement sequence number in the ACK message; and deleting the PDCP SDU corresponding to the sequence number coding which meets the confirmation condition. According to the scheme provided by the embodiment of the invention, as the PDCP SDU is delivered to the high layer after being encapsulated in sequence at the data receiving end, the sequence number code determined according to the ACK message confirmation sequence number is the maximum recognizable sequence number code, and the PDCP SDU corresponding to the sequence number code less than or equal to the maximum recognizable sequence number code is deleted, the backup file of the PDCP SDU can be deleted more timely, thereby reducing the message volume of the PDCP retransmission.
The embodiments of the present invention will be further explained with reference to the drawings.
As shown in fig. 1, fig. 1 is a flowchart of a data processing method applied to a data transmitting end according to an embodiment of the present invention, where the data processing method includes, but is not limited to, step S110, step S200, step S300, and step S400.
Step S110, obtaining TCP message, backing up PDCP SDU corresponding to TCP message, generating and storing sequence number code corresponding to PDCP SDU.
In an embodiment, the sequence number coding of the PDCP SDU may be stored in any form, for example, the attribute information of the PDCP SDU may be stored, or a mapping relationship between the PDCP SDU and the sequence number coding may be generated.
In an embodiment, the sequence number coding may be generated after the PDCP SDU is encapsulated, or may be generated directly after backup, which is not limited in this embodiment.
Step S120, the TCP message is sent to the data receiving end.
It should be noted that, at the data receiving end, the PDCP SDUs are also delivered to the higher layer in sequence, so that the last delivered PDCP SDU is acknowledged and all previous PDCP SDUs are received by the higher layer. For 5G, although RLC SDUs are allowed to be delivered out of order, their corresponding PDCP SDUs are delivered to a higher layer in order after being sequenced without being configured for out-of-order delivery, so that the last delivered PDCP SDU is confirmed, and all the previous PDCP SDUs have been received by the higher layer.
Step S130, when receiving the ACK message with the confirmation sequence number sent by the data receiving end according to the TCP message, determining the sequence number code meeting the confirmation condition from the stored sequence number codes according to the confirmation sequence number in the ACK message.
In an embodiment, in an initialization stage of a data sending end, a bearer, an RLC instance, and a PDCP instance are usually established, a plurality of TCP links may be simultaneously provided in the same bearer, data processing is usually performed independently among the TCP links, and a link identifier can be used to distinguish the TCP links, so that after an ACK packet is received, a corresponding link identifier may be analyzed from the ACK packet, a TCP link determined by using an acknowledgement sequence number of the ACK packet is determined according to the link identifier, and then subsequent operations are performed, thereby avoiding mistakenly deleting PDCP SDUs of other TCP links.
It should be noted that, when receiving the TCP packet, the data receiving end usually sends an ACK packet carrying an acknowledgement sequence number after determining the whole segment of the TCP packet, so that the PDCP SDU determined by the acknowledgement sequence number of the ACK packet can be determined as being completely acknowledged, and a situation that only part of the PDCP SDU backup is acknowledged does not occur.
In an embodiment, the confirmation condition may be specifically set according to an actual situation, for example, the confirmation condition is less than or equal to the determined sequence number coding, and the deletable PDCP SDUs can be quickly determined in batches according to the sequence number coding by using the in-sequence delivery characteristic of the PDCP SDUs, so as to improve the efficiency of backup deletion of the PDCP SDUs.
In an embodiment, the form of the sequence number coding may be a number related to the encapsulation sequence, or may be a number related to the last encapsulated PDCP SDU, and it is sufficient to implement batch determination of PDCP SDUs according to the encapsulation sequence.
Step S140, deleting the PDCP SDU corresponding to the sequence number code meeting the confirmation condition.
In an embodiment, deleting the PDCP SDU may be deleting a backup message, or deleting the entire PDCP SDU backup, which is not limited in this embodiment.
Based on the above embodiment, the message received by the data sending end may be of any type, and the sequence number coding is determined according to the encapsulation sequence after parsing, so that, after the sequence number coding meeting the condition is determined, the deleted PDCP SDU corresponding to the sequence number coding meeting the condition can be a backup of any message, even if the message corresponding to the PDCP SDU is not a TCP message, the encapsulation sequence of the PDCP SDU determines that the delivery sequence thereof is before the PDCP SDU determined according to the confirmation sequence number in the ACK message, so that it can be inferred that the non-TCP message is also confirmed, and therefore, when the sequence number coding meets the confirmation condition, the PDCP SDUs can be deleted together.
In an embodiment, when step S140 of this embodiment is executed, if the RLC status report is received, the deleting of the PDCP SDU may be completed according to the step of this embodiment, and then the backup of the PDCP SDU at the data sending end is processed according to the RLC status report, or the step of this embodiment may be stopped, and the step is directly executed according to the RLC status report, and a specific manner may be adjusted according to actual needs, which is not limited in this embodiment. It should be noted that, deleting the backup of the PDCP SDU according to the RLC status report is a method in the prior art, and this embodiment is not described in detail again.
It should be noted that, after step S140 of this embodiment is executed, when the data receiving end moves to cause cell switching, the data sending end does not retransmit the deleted PDCP SDU backup any more, thereby effectively reducing the data amount during PDCP retransmission.
In addition, in an embodiment, referring to fig. 2, fig. 2 is a schematic diagram of transceiving of a data receiving end and a data transmitting end according to an embodiment of the present invention. It should be noted that, the data sending end in the embodiment of the present invention may be a base station or a terminal, where the data sending end is a base station and the data receiving end is a terminal, the base station receives a TCP packet sent by a server, parses the packet, encapsulates the packet into a PDCP PDU and sends the PDCP PDU to the terminal, the terminal decapsulates the PDCP PDU after receiving the PDCP PDU, constructs a TCP ACK packet according to the obtained TCP data packet, encapsulates the TCP ACK packet into a PDCP PDU and sends the PDCP PDU to the base station, the base station decapsulates the PDCP, parses a link identifier and an acknowledgement sequence number, determines a TCP link to which the base station belongs according to the link identifier, determines a corresponding sequence number code according to the acknowledgement sequence number, and deletes a backup of a PDCP SDU smaller than or equal to the sequence number code in a PDCP retransmission queue. When the data sending end is a terminal and the base station is a data receiving end, the principle is substantially the same, and the description is omitted here.
Referring also to fig. 3, in an embodiment, step S100 in the embodiment shown in fig. 1 includes, but is not limited to, the following steps:
step S210, analyzing the TCP message to obtain message information of the TCP message;
step S220, determining the TCP message as an optimized message according to the message information.
It should be noted that, according to the TCP protocol, if a TCP message carries a payload, and a sequence number occupied by the TCP message is a length of the payload, for example, a TCP sequence number of the TCP message is 2, and a length of the payload is 2, then in the TCP link, sequence numbers 2 to 4 are all occupied by the TCP message, when a plurality of messages conform to a characteristic of continuous sequence numbers, all TCP messages before the TCP message can be determined to be confirmed under the condition that one TCP message is confirmed, and the TCP message with a continuous sequence number is defined as an optimizable message, otherwise, the TCP message is an non-optimizable message. The optimized messages are a plurality of messages with continuous sequence numbers occupied in the same TCP link, so that the position of one optimized message in the TCP link can be quickly determined, the PDCP SDU packaged before the optimized message can be quickly determined according to the sequence number coding of the optimized message, and the backup deletion of the PDCP SDU is realized. The determination condition of the optimizable packet can be adjusted according to actual requirements, and this embodiment does not need to be limited much, and only the sequence number code meeting the acknowledgement condition can be determined from the stored sequence number codes according to the packet information of the optimizable packet and the acknowledgement sequence number of the ACK packet.
In an embodiment, the message information may be any information that can be obtained by parsing the TCP message, such as a link identifier, a TCP sequence number, a TCP payload length, and the like, which is not limited in this embodiment.
In an embodiment, the message received by the data sending end may be any type of message, such as a TCP message, a User Datagram Protocol (UDP) message, and the like, and after receiving the different types of messages, the data sending end may analyze and encapsulate the different types of messages, generate a sequence number code, and use the sequence number code for subsequent determination. It should be noted that, for other types of messages except the TCP message, the messages may be set as non-optimizable messages by default, and the PDCP SDU may be deleted after determining the sequence number code through the TCP message.
In addition, referring to fig. 4, in an embodiment, the message information includes a message type, and the step S120 in the embodiment shown in fig. 1 includes, but is not limited to, the following steps:
step S310, when the TCP message is determined to be a non-retransmitted SYN message or a non-retransmitted SYN ACK message according to the message type, the TCP link to which the TCP message belongs is determined to be an optimizable link, and the TCP message is determined to be an optimizable message.
It should be noted that, according to the TCP protocol, if the SYN flag of the TCP message is 1, the payload length of the TCP message needs to be increased by 1, so the payload length of the SYN message or the SYN ACK message is always not zero, and 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 messages or the SYN ACK messages in the TCP link are definitely consecutive, and therefore the TCP message can be determined to be an optimizable message.
In addition, referring to fig. 5, in an embodiment, the message information includes a message type, and the message information includes a TCP sequence number, a payload length, and a link identifier, and step S120 in the embodiment shown in fig. 1 includes, but is not limited to, the following steps:
and step S320, when the TCP message is determined to be a data message, determining the TCP link to which the TCP message belongs as an optimizable link according to the link identifier, and determining the TCP message as an optimizable message according to the TCP serial number and the payload length.
In an embodiment, when a first packet of a TCP link is not a non-retransmitted SYN packet or SYN ACK packet, it is not possible to ensure that sequence numbers of the TCP link are continuous, and a determination condition for an optimizable packet needs to satisfy the continuity of the TCP sequence numbers.
It should be noted that, when it is determined that the TCP link is the optimizable link, and according to the TCP protocol, if the TCP packet carries the payload, the sequence number occupied by the packet is the length of the payload, and therefore, it can be determined whether the TCP packet is consecutive to the sequence number occupied by the last optimizable packet according to the TCP sequence number and the payload length. When determining the message that can be optimized, the determination can be made through the sum of the TCP sequence number and the payload length, or after determining that one message is the message that can be optimized, a reference sequence number that the next message is the message that can be optimized is generated according to the TCP sequence number and the payload length, and a specific manner can be selected according to actual needs, which is not described herein again.
Referring to fig. 6, in an embodiment, step S320 in the embodiment shown in fig. 5 includes, but is not limited to, the following steps:
and step S410, when the payload length is greater than zero and the TCP serial number is greater than or equal to the sum of the TCP serial number of the last optimized message belonging to the same TCP link with the TCP message and the TCP payload length, determining that the TCP message is the optimized message.
Based on the above embodiment, when the payload length is zero, the TCP packet does not occupy any sequence number, so the ACK packet constructed by the data receiving end according to the TCP packet does not carry an acknowledgement sequence number, and matching of sequence number codes cannot be performed, and therefore the TCP packet with the payload length of zero is determined as an unoptimizable packet by default.
In an embodiment, when the TCP serial number is greater than or equal to the sum of the TCP serial number and the TCP payload length of the last optimizable packet belonging to the same TCP link as the TCP packet, the TCP packet is determined as the optimizable packet, so that the serial numbers of adjacent optimizable packets are always continuous, and as the TCP packets are delivered in sequence, the TCP packet determined according to the acknowledgement signal in the ACK packet constructed by one optimizable packet is always acknowledged before the optimizable packet, and then backup of PDCP SDUs capable of being deleted can be quickly determined in batches, so that the efficiency of backup deletion is effectively improved.
In addition, referring to fig. 7, in an embodiment, the message information further includes a TCP sequence number and a payload length, and step S130 in the embodiment shown in fig. 4 further includes, but is not limited to, the following steps:
step S510, obtaining maximum confirmable information composed of TCP sequence number and payload length;
step S520, when the acknowledgement 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 acknowledgement information, confirming the sequence number code less than or equal to the sequence number code corresponding to the TCP message as the sequence number code meeting the acknowledgement condition.
In an embodiment, the maximum confirmable information may be information data independently stored in the data sending end, or may be stored in a PDCP instance of the data sending end, and may be used to store message information of a newly encapsulated optimizable message.
In an embodiment, the maximum confirmable information formed by the TCP sequence number and the payload length may be directly stored in the maximum confirmable information, or may be stored after calculating a specific value according to the TCP sequence number and the payload length, and the specific manner is adjusted according to actual requirements, so that when the confirmation sequence number satisfies a condition, the corresponding PDCP SDU can be matched according to the maximum confirmable information.
In an embodiment, when the acknowledgement sequence number in the ACK packet is greater than or equal to the sum of the TCP sequence number in the maximum acknowledgable message and the payload length, the TCP packet corresponding to the TCP sequence number is already acknowledged completely, that is, the TCP packet corresponding to the TCP sequence number is the maximum TCP sequence number packet, therefore, the TCP packet encapsulated before the TCP packet is also already acknowledged certainly, the sequence number code of the PDCP SDU corresponding to the maximum TCP sequence number packet is obtained as the reference code, and the sequence number code meeting the acknowledgement condition can be determined quickly. It should be noted that, since the sequence number codes are obtained according to the encapsulation sequence, the confirmation condition may be that the sequence number codes are less than or equal to the sequence number codes, for example, the sequence number code matched according to the largest TCP sequence number message is 5, the sequence number codes of the currently stored PDCP SDUs which are not deleted and backed up are 1 to 4, which can be confirmed to be the sequence number codes meeting the confirmation condition, and the sequence number codes are 1 to 5, which correspond to the backup deletion of the PDCP SDUs.
Referring additionally to fig. 8, in one embodiment, step S100 in the embodiment shown in fig. 1 includes, but is not limited to, the following steps:
step S600, setting sequence number codes for the PDCP SDUs in sequence according to the packaging sequence of the PDCP SDUs in the TCP link and saving the sequence numbers.
In an embodiment, as shown in fig. 2, after parsing a TCP packet, a data sending end encapsulates the TCP packet into PDCP PDUs and backs up PDCP SDUs, so that a sequence number code may be sequentially set for the PDCP SDUs by a packaging sequence of the TCP packet, so that the sequence number code can reflect a packaging sequence of the PDCP SDUs in a TCP link, and since the PDCP PDUs are usually delivered in sequence, a data receiving end decapsulates and constructs an ACK packet in sequence, so that a sequence number code obtained according to an acknowledgement sequence number of the ACK packet is a sequence number code that is confirmed to the maximum extent, and a PDCP PDU delivered before the sequence number code is also confirmed, so that a PDCP SDU corresponding to a sequence number code that is smaller than or equal to the sequence number code may be determined as a PDCP SDU that has been confirmed according to a sequence number code ordering of the sequence number code, and backup deletion may be performed.
It should be noted that, since the sequence number coding is determined according to the encapsulation sequence, for the unoptimizable packet, although the packet information is not updated to the maximum acknowledged information, it only means that the unoptimizable packet cannot be used for determining the maximum acknowledged sequence number coding, and the unoptimizable packet is still encapsulated into PDCP PDUs and backup PDCP SDUs, so that the TCP packet corresponding to the sequence number coding that determines the conditions according to the sequence number coding determined by the sequence number of the ACK packet and the packet information of the optimizable packet should also include the unoptimizable packet, and the sequence number coding can satisfy the acknowledgement conditions in the above embodiments.
In order to explain the technical solution of the embodiment of the present invention in detail, the technical solution of the embodiment of the present invention is further illustrated by three specific examples below.
It should be noted that, for convenience of description of the solution, in the following exemplary scenario, the base station is used as a data sending end, and the terminal is used as a data receiving end, but this does not limit the technical solution of this embodiment.
Scene one: TCP sequence number continuation of TCP stream
The PDCP layer of the base station receives the SYN message sent by the server, and analyzes the following first message information from the SYN message: the length of a first TCP payload is 1, a first link identifier (a client IP: 1.1.1.1, a server IP: 2.2.2, a client port: 10000 and a server port: 20000) is set to be optimized because of satisfying the optimization conditions, the message identifier and first message information are stored in the attribute information of a first backup PDCP SDU, the first link identifier, a first TCP serial number and the first TCP payload length are stored in a PDCP instance, after the message is encapsulated into a first PDCP PDU, the first serial number code is determined to be 1, and then the first PDCP PDU is delivered to a lower layer and sent to a terminal.
After receiving the PDCP PDU and de-encapsulating the RLC protocol, the terminal transmits a message obtained by de-encapsulation to a TCP/IP layer after the message passes through the RLC and the PDCP protocol layers without overtime of an RLC status report prohibiting timer and transmitting the RLC status report; the TCP/IP layer constructs a SYN ACK message, and the second message information is as follows: the first confirmation serial number is 2, the second link identification (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 a PDCP layer and sends the SYN ACK message to the base station through protocol layers such as PDCP, RLC and the like.
After receiving the SYN ACK message, the base station analyzes second message information from the TCP message because the message type is the TCP message, acquires first message information from a PDCP example because the second link identification is the same as the first link identification, matches a first PDCP SDU with the sequence number being 1 according to the first message information, and deletes the backup message of the first PDCP SDU when the first PDCP SDU meets the condition of the TCP message confirmation sent by the terminal.
The base station receives the first ACK message sent by the server, and analyzes third message information: the sequence number of the second TCP is 2, the payload length of the second TCP is 0, a third link mark (client IP: 1.1.1.1, server IP: 2.2.2, client port: 10000, server port: 20000) is not satisfied due to the fact that the length of the second TCP payload is 0, the message mark is determined to be not optimized, the message mark and the third message information are updated to the attribute information of the second backup PDCP SDU, after the message is packaged into the second PDCP PDU, the coding of the second sequence number is determined to be 2, and then the second PDCP PDU is delivered to the lower layer to be sent to the terminal.
The base station receives the data message sent by the server, and analyzes fourth message information: the third TCP serial number is 2, the third TCP payload length is 100, the fourth link identification (client IP: 1.1.1.1, server IP: 2.2.2, client port: 10000, server port: 20000) is satisfied, the message identification and the fourth message information are updated to the third backup PDCP SDU as the message which can be optimized, the third TCP serial number and the third TCP payload length are updated to the PDCP example, after the message is encapsulated into the third PDCP PDU, the third serial number code is determined to be 3, and the third PDCP PDU is delivered to the lower layer and sent to the terminal.
After receiving the third PDCP PDU sent by the base station, the terminal constructs a second ACK message, wherein the second TCP acknowledgement sequence number of the second ACK message is 102, and sends the second ACK message to the base station; and the base station receives and analyzes the second ACK message, and a second TCP confirmation sequence number is the sum of the third TCP sequence number and the third TCP payload length, and a third backup PDCP SDU is matched according to the third TCP sequence number and the third TCP payload length in the PDCP example, and the third sequence number of the third backup PDCP SDU is coded into 3, and the second sequence number of the second backup PDCP SDU is coded into 2, so that the backup messages of the third backup PDCP SDU and the second backup PDCP SDU are deleted together.
Scene two: the TCP sequence numbers of the TCP flows are out of order.
The PDCP layer of the base station receives the SYN message sent by the server, and analyzes the following first message information from the SYN message: the length of a first TCP payload is 1, a first link identifier (a client IP: 1.1.1.1, a server IP: 2.2.2, a client port: 10000 and a server port: 20000) is set to be optimized because of satisfying the optimization conditions, the message identifier and first message information are stored in the attribute information of a first backup PDCP SDU, the first link identifier, a first TCP serial number and the first TCP payload length are stored in a PDCP instance, after the message is encapsulated into a first PDCP PDU, the first serial number code is determined to be 1, and then the first PDCP PDU is delivered to a lower layer and sent to a terminal.
After receiving the PDCP PDU and de-encapsulating the RLC protocol, the terminal transmits a message obtained by de-encapsulation to a TCP/IP layer after the message passes through the RLC and the PDCP protocol layers without overtime of an RLC status report prohibiting timer and transmitting the RLC status report; the TCP/IP layer constructs a SYN ACK message, and the second message information is as follows: the first confirmation serial number is 2, the second link identification (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 a PDCP layer and sends the SYN ACK message to the base station through protocol layers such as PDCP, RLC and the like.
After receiving the SYN ACK message, the base station analyzes second message information from the TCP message because the message type is the TCP message, acquires first message information from a PDCP example because the second link identification is the same as the first link identification, matches a first PDCP SDU with the sequence number being 1 according to the first message information, and deletes the backup message of the first PDCP SDU when the first PDCP SDU meets the condition of the TCP message confirmation sent by the terminal.
The base station receives the first ACK message sent by the server, and analyzes third message information: the sequence number of the second TCP is 2, the payload length of the second TCP is 0, a third link mark (client IP: 1.1.1.1, server IP: 2.2.2, client port: 10000, server port: 20000) is not satisfied due to the fact that the length of the second TCP payload is 0, the message mark is determined to be not optimized, the message mark and the third message information are updated to the attribute information of the second backup PDCP SDU, after the message is packaged into the second PDCP PDU, the coding of the second sequence number is determined to be 2, and then the second PDCP PDU is delivered to the lower layer to be sent to the terminal.
The base station receives the first data message sent by the server, and analyzes fourth message information: the third TCP serial number is 102, the third TCP payload length is 100, the fourth link identification (client IP: 1.1.1.1, server IP: 2.2.2, client port: 10000, server port: 20000), the first data message is sufficient for optimization, the message identification is determined to be optimizable, the message identification and the fourth message information are updated to a third backup PDCP SDU, the third TCP serial number and the third TCP payload length are updated to a PDCP example, after the message is encapsulated into a third PDCP PDU, the third serial number code is determined to be 3, and then the third PDCP PDU is delivered to a lower layer to be sent to the terminal.
After receiving the first data message sent by the base station, the terminal constructs a second ACK message, wherein the second TCP acknowledgement sequence number of the second ACK message is 2; and the base station analyzes the second ACK message sent by the terminal after receiving the second ACK message, and does not execute deletion of the backup message because the second confirmation sequence number is smaller than the sum of the third TCP sequence number and the third TCP payload length and does not meet the confirmation condition.
The base station receives the second data message sent by the server, and analyzes fifth message information: the fourth TCP serial number is 2, the length of the fourth TCP payload is 100, a fifth link identifier (client IP: 1.1.1.1, server IP: 2.2.2, client port: 10000, server port: 20000) is provided, because the TCP serial number of the current message is smaller than the sum of the TCP serial number and the TCP payload length stored in the PDCP example and does not satisfy the optimization condition, the message identifier is determined to be not optimized, the message identifier is stored in the fourth backup PDCP SDU, after the message is encapsulated into the fourth PDCP PDU, the fourth serial number code is determined to be 4, and then the fourth PDCP PDU is delivered to the lower layer and sent to the terminal.
After receiving a second data message sent by the base station, the terminal constructs a third ACK message, wherein a third TCP acknowledgement sequence number of the third ACK message is 202; and the base station receives a third ACK message sent by the terminal, and determines that the third backup PDCP SDU is the maximum identifiable PDCP SDU by referring to the mode because the third TCP confirmation sequence number is equal to the sum of the third TCP sequence number and the third TCP payload length and meets the confirmation condition, and deletes the backup message of the third backup PDCP SDU and the second backup PDCP SDU together because the third sequence number of the third backup PDCP SDU is coded as 3 and the second sequence number of the second backup PDCP SDU is coded as 2.
The base station PDCP layer receives the third data message sent by the server, and resolves sixth message information: the fifth TCP serial number is 202, the length of the fifth TCP payload is 100, the sixth link identification (the client IP: 1.1.1, the server IP: 2.2.2, the client port: 10000 and the server port: 20000) meets the optimization condition because the fifth TCP serial number is equal to the sum of the third TCP serial number and the length of the third TCP payload, the message identification is determined to be optimized, the message identification and the sixth message information are stored into the attribute information of the fifth backup PDCP SDU, after the message is encapsulated into the fifth PDCP PDU, the fifth serial number is determined to be 5, and then the fourth PDCP PDU is delivered to the lower layer to be sent to the terminal.
After receiving a third data message sent by the base station, the terminal constructs a fourth ACK message, wherein a fourth TCP acknowledgement sequence number of the fourth data message is 302; and the base station receives a fourth ACK message sent by the terminal, and determines that the fifth backup PDCP SDU is the maximum identifiable PDCP SDU as the fourth TCP confirmation sequence number is equal to the sum of the fifth TCP sequence number and the fifth TCP payload length and meets the confirmation condition, and deletes the backup message of the fifth backup PDCP SDU and the fourth backup PDCP SDU together as the fifth sequence number is coded to be 3 and the fourth sequence number of the fourth backup PDCP SDU is coded to be 4.
Scene three: hybrid service scenarios
The PDCP layer of the base station receives the SYN message sent by the server, and analyzes the following first message information from the SYN message: the length of a first TCP payload is 1, a first link identifier (a client IP: 1.1.1.1, a server IP: 2.2.2, a client port: 10000 and a server port: 20000) is set to be optimized because of satisfying the optimization conditions, the message identifier and first message information are stored in the attribute information of a first backup PDCP SDU, the first link identifier, a first TCP serial number and the first TCP payload length are stored in a PDCP instance, after the message is encapsulated into a first PDCP PDU, the first serial number code is determined to be 1, and then the first PDCP PDU is delivered to a lower layer and sent to a terminal.
After receiving the PDCP PDU and de-encapsulating the RLC protocol, the terminal transmits a message obtained by de-encapsulation to a TCP/IP layer after the message passes through the RLC and the PDCP protocol layers without overtime of an RLC status report prohibiting timer and transmitting the RLC status report; the TCP/IP layer constructs a SYN ACK message, and the second message information is as follows: the first confirmation serial number is 2, the second link identification (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 a PDCP layer and sends the SYN ACK message to the base station through protocol layers such as PDCP, RLC and the like.
After receiving the SYN ACK message, the base station analyzes second message information from the TCP message because the message type is the TCP message, acquires first message information from a PDCP example because the second link identification is the same as the first link identification, matches a first PDCP SDU with the sequence number being 1 according to the first message information, and deletes the backup message of the first PDCP SDU when the first PDCP SDU meets the condition of the TCP message confirmation sent by the terminal.
The base station receives the first ACK message sent by the server, and analyzes third message information: the sequence number of the second TCP is 2, the payload length of the second TCP is 0, a third link mark (client IP: 1.1.1.1, server IP: 2.2.2, client port: 10000, server port: 20000) is not satisfied due to the fact that the length of the second TCP payload is 0, the message mark is determined to be not optimized, the message mark and the third message information are updated to the attribute information of the second backup PDCP SDU, after the message is packaged into the second PDCP PDU, the coding of the second sequence number is determined to be 2, and then the second PDCP PDU is delivered to the lower layer to be sent to the terminal.
The base station receives a UDP message sent by the server, because the UDP message does not belong to a TCP message and does not meet the optimization condition, the message identification is determined to be unoptimizable, the message identification is stored under a third backup PDCP SDU, after the message is encapsulated into a third PDCP PDU, a third sequence number code is determined to be 3, and then the third PDCP PDU is delivered to a lower layer and sent to the terminal
The base station receives the data message sent by the server, and analyzes fourth message information: the sequence number of the third TCP is 2, the length of the payload of the third TCP is 100, a fourth link identifier (client IP: 1.1.1.1, server IP: 2.2.2, client port: 10000, server port: 20000) meets the optimization conditions, the message identifier is determined to be optimized, the message identifier is stored under a fourth backup PDCP SDU, after the message is encapsulated into a fourth PDCP PDU, the code of the fourth sequence number is determined to be 4, and the fourth PDCP PDU is delivered to a lower layer and sent to the terminal.
After receiving the TCP DATA sent by the base station, the terminal constructs a second ACK message, wherein the second TCP acknowledgement sequence number of the second ACK message is 102; and the base station receives a second ACK message sent by the terminal, and determines that the fourth backup PDCP SDU is the maximum identifiable PDCP SDU by referring to the above mode because the second TCP confirmation sequence number is equal to the sum of the third TCP sequence number and the third TCP payload length and meets the confirmation condition, and deletes the backup messages of the second backup PDCP SDU, the third backup PDCP SDU and the fourth backup PDCP SDU together because the fourth sequence number of the fourth backup PDCP SDU is coded as 4, the second sequence number of the second backup PDCP SDU is coded as 2, and the third sequence number of the third backup PDCP SDU is coded as 3.
In addition, referring to fig. 9, an embodiment of the present invention further provides a base station, where the base station 900 includes: memory 920, processor 910, and computer programs stored on memory 920 and operable on processor 910.
The processor 910 and the memory 920 may be connected by a bus or other means.
Non-transitory software programs and instructions necessary to implement the data processing method of the above-described embodiment are stored in the memory 920, and when executed by the processor 910, perform the data processing method of the above-described embodiment, for example, perform the method steps S110 to S140 in fig. 1, the method steps S210 to S220 in fig. 3, the method step S310 in fig. 4, the method step S320 in fig. 5, the method step S410 in fig. 6, the method steps S510 to S520 in fig. 7, and the method step S600 in fig. 8 described above.
In addition, referring to fig. 10, an embodiment of the present invention also provides a terminal, where the terminal 1000 includes: a memory 1020, a processor 1010, and a computer program stored on the memory 1020 and executable 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-described embodiment are stored in the memory 1020, and when executed by the processor 1010, perform the data processing method of the above-described embodiment, for example, the method steps S110 to S140 in fig. 1, the method steps S210 to S220 in fig. 3, the method step S310 in fig. 4, the method step S320 in fig. 5, the method step S410 in fig. 6, the method steps S510 to S520 in fig. 7, and the method step S600 in fig. 8, which are described above, are performed.
The above-described embodiments of the apparatus are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, i.e. may be located in one place, or may also be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
Furthermore, an embodiment of the present invention further provides a computer-readable storage medium, which stores computer-executable instructions, which are executed by a processor or a controller, for example, by a processor in the above-mentioned embodiment, and can enable the processor to execute the data processing method applied to the data transmitting end in the above-mentioned embodiment, for example, execute the above-mentioned method steps S110 to S140 in fig. 1, method steps S210 to S220 in fig. 3, 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, and method step S600 in fig. 8. It will be understood by those of ordinary skill in the art that all or some of the steps of the methods disclosed above may be implemented as software, firmware, hardware, or suitable combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, 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 includes any information delivery media as known to those skilled in the art.
While the preferred embodiments of the present invention have been described in detail, it will be understood by those skilled in the art that the foregoing and various other changes, omissions and deviations in the form and detail thereof may be made without departing from the scope of this invention.

Claims (10)

1. A data processing method is applied to a data sending end and comprises the following steps:
acquiring a Transmission Control Protocol (TCP) message, backing up a Packet Data Convergence Protocol (PDCP) service data unit (PDCP SDU) corresponding to the TCP message, and generating and storing a sequence number code corresponding to the PDCP SDU;
sending the TCP message to a data receiving end;
when an Acknowledgement (ACK) message which is sent by a data receiving end according to the TCP message and carries an acknowledgement sequence number is received, determining a sequence number code which meets an acknowledgement condition from the stored sequence number codes according to the acknowledgement sequence number in the ACK message;
and deleting the PDCP SDU corresponding to the sequence number coding which meets the confirmation condition.
2. The data processing method according to claim 1, wherein before the backing up the PDCP SDU corresponding to the TCP packet, the method further comprises:
analyzing the TCP message to obtain message information of the TCP message;
and determining the TCP message as an optimized message according to the message information.
3. The data processing method according to claim 2, wherein the packet information includes a packet type, and the determining that the TCP packet is the optimizable packet according to the packet information includes:
and when the TCP message is determined to be a non-retransmission synchronous SYN message or a non-retransmission synchronous acknowledgement SYN ACK message according to the message type, determining that a TCP link to which the TCP message belongs is an optimizable link, and determining that the TCP message is an optimizable message.
4. The data processing method according to claim 2, wherein the packet information includes a TCP sequence number, a payload length, and a link identifier, and the determining that the TCP packet is an optimizable packet according to the packet information includes:
and when the TCP message is determined to be a data message, determining that the TCP link to which the TCP message belongs is an optimizable link according to the link identifier, and determining that the TCP message is an optimizable message according to the TCP sequence number and the payload length.
5. The data processing method according to claim 4, wherein said determining that said TCP packet is an optimizable packet according to said TCP sequence number and said payload length comprises:
and when the payload length is greater than zero and the TCP serial number is greater than or equal to the sum of the TCP serial number of the last optimized message belonging to the same TCP link with the TCP message and the TCP payload length, determining that the TCP message is the optimized message.
6. The data processing method according to claim 2, wherein the message information further includes a TCP sequence number and a payload length, and the determining, according to the acknowledgement sequence number in the ACK message, a sequence number code that meets an acknowledgement condition from the stored sequence number codes comprises:
acquiring maximum confirmable information consisting of the TCP sequence number and the payload length;
and when the acknowledgement 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 acknowledgement information, confirming the sequence number code which is less than or equal to the sequence number code corresponding to the TCP message as the sequence number code meeting the acknowledgement condition.
7. The data processing method according to claim 1, wherein the generating and storing sequence number codes corresponding to the PDCP SDUs comprises:
and setting and storing the sequence number codes for the PDCP SDUs in sequence according to the packaging sequence of the PDCP SDUs in the TCP link.
8. A base station, comprising: memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor implements the data processing method according to any one of claims 1 to 7 when executing the computer program.
9. A terminal, comprising: memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor implements the data processing method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium storing computer-executable instructions for performing the data processing method of any one of claims 1 to 7.
CN202010870213.5A 2020-08-26 2020-08-26 Data processing method, base station, terminal and storage medium Pending CN114126084A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010870213.5A CN114126084A (en) 2020-08-26 2020-08-26 Data processing method, base station, terminal and storage medium
PCT/CN2021/113102 WO2022042379A1 (en) 2020-08-26 2021-08-17 Data processing method, base station, terminal, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010870213.5A CN114126084A (en) 2020-08-26 2020-08-26 Data processing method, base station, terminal and storage medium

Publications (1)

Publication Number Publication Date
CN114126084A true CN114126084A (en) 2022-03-01

Family

ID=80354578

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010870213.5A Pending CN114126084A (en) 2020-08-26 2020-08-26 Data processing method, base station, terminal and storage medium

Country Status (2)

Country Link
CN (1) CN114126084A (en)
WO (1) WO2022042379A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115314266A (en) * 2022-07-27 2022-11-08 阿里云计算有限公司 Access control method and device, electronic equipment and readable storage medium
CN115695583A (en) * 2022-05-08 2023-02-03 荣耀终端有限公司 Data transmission method and electronic equipment

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1343267A3 (en) * 2002-02-08 2005-08-03 ASUSTeK Computer Inc. Data transmission confirmation in a wireless communication system
CN101729524B (en) * 2008-11-03 2012-12-12 电信科学技术研究院 Data processing method, data processing device, RLC entity and PDCP entity
CN108306708B (en) * 2014-03-21 2020-07-10 电信科学技术研究院 Data packet processing method and device
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
CN115001639B (en) * 2016-11-01 2023-10-03 苹果公司 Method for avoiding HFN desynchronization in uplink through WLAN in LTE-WLAN aggregation
KR20180099135A (en) * 2017-02-28 2018-09-05 삼성전자주식회사 Method and apparatus of packet generation and distribution for inter-site ca

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115695583A (en) * 2022-05-08 2023-02-03 荣耀终端有限公司 Data transmission method and electronic equipment
CN115695583B (en) * 2022-05-08 2023-12-01 荣耀终端有限公司 Data transmission method and electronic equipment
CN115314266A (en) * 2022-07-27 2022-11-08 阿里云计算有限公司 Access control method and device, electronic equipment and readable storage medium

Also Published As

Publication number Publication date
WO2022042379A1 (en) 2022-03-03

Similar Documents

Publication Publication Date Title
US11490446B2 (en) Method and apparatus for reconfiguring a bearer
WO2018127238A1 (en) Information processing method and apparatus
US9532378B2 (en) Apparatus and method for moving a receive window in a radio access network
RU2461147C2 (en) Method of processing radio protocol in mobile communication system and mobile communication transmitter
KR101387537B1 (en) A method for handling correctly received but header compression failed packets
CN108632229B (en) Header compression method, header decompression method and device in multi-connection
EP2136501B1 (en) Method of delivering a PDCP data unit to an upper layer
US8848583B2 (en) Communication method and apparatus for header compression
EP2168270B1 (en) A method for handling correctly received but header compression failed packets
WO2017185941A1 (en) Data transmission method and relevant device
WO2022042379A1 (en) Data processing method, base station, terminal, and storage medium
US20180007113A1 (en) Apparatus adapted for maintaining receiving data quality and method for receiving data
CN114208137A (en) Method and device for compressing and decompressing Ethernet frame header
CN115022922A (en) Call processing method and device for LTE (Long term evolution) system
CN112118594A (en) Data uploading method, data downloading method, electronic equipment and storage medium
JP2023062123A (en) Wireless communication device, wireless communication method, and wireless communication system
KR101992061B1 (en) Apparatus and method for transmitting file data
TWI473479B (en) Communication system, device and method for preventing data loss

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