Disclosure of Invention
The invention aims to provide a data transmission processing method, a user terminal, network equipment and a system, which solve the problem of high complexity of a protocol layer.
In order to achieve the above object, an embodiment of the present invention provides a data transmission processing method, including:
when data transmission processing is carried out, a protocol layer of the user terminal carries out segmentation operation on data so as to obtain segmented data;
and generating the acquired segmented data into PDU by another protocol layer of the user terminal based on scheduling information.
Optionally, another protocol layer of the ue generates the obtained segmented data into a PDU based on the scheduling information, including:
for the initial transmission data, another protocol layer of the user terminal directly generates the acquired segmented data into PDU based on scheduling information; or
For retransmission data, another protocol layer of the user terminal generates the acquired segmented data into a PDU based on scheduling information and does not allow re-segmentation of the data.
Optionally, a protocol layer of the ue performs a segmentation operation on the data to obtain segmented data, including:
and the protocol layer of the user terminal performs segmentation operation on the data according to the preset segment length so as to acquire the segment data.
Optionally, a protocol layer of the ue performs a segmentation operation on the data to obtain segmented data, including:
and a protocol layer of the user terminal performs segmentation operation on the data according to the dynamically determined segment length so as to acquire the segment data.
Optionally, the dynamically determined segment length comprises a network device signaled segment length; or
The dynamically determined segment length comprises a dynamically determined segment length for the user terminal, and the method further comprises:
and the user terminal sends the length information of the segment length to network equipment so that a protocol layer of the network equipment executing uplink scheduling allocates initial transmission resources and/or retransmission resources matched with the segment length according to the length information.
Optionally, the segment length is dynamically determined based on one or more of the following information:
segment length indication information desired by the network device;
segment length indication information desired by the user terminal;
uplink channel quality information of the user terminal;
data transmission condition of the user terminal;
and the characteristics of the uplink service corresponding to the user terminal.
Optionally, the data includes uplink SDUs, and the segmenting operation includes:
a segmentation operation according to a segment length.
Optionally, another protocol layer of the ue generates the obtained segmented data into a PDU based on the scheduling information, including:
another protocol layer of the user terminal separately generates a PDU from the segments meeting the segment length in the obtained segment data based on the scheduling information, and when a remaining segment of an SDU does not meet the segment length, concatenates the remaining segment of the SDU with its continuous SDU to generate a PDU meeting the segment length, and allows padding (padding) for the last PDU; or
The other protocol layer of the user terminal generates a PDU separately from the segments meeting the segment length in the acquired segment data based on the scheduling information, and when a remaining segment which does not meet the segment length exists in an SDU, adds padding to the remaining segment to meet the segment length, and generates the PDU; or
Another protocol layer of the user terminal separately generates a PDU from the segments meeting the segment length in the obtained segment data based on scheduling information, and when a remaining segment of an SDU does not meet the segment length, separately generates a PDU for the remaining segment; or
The other protocol layer of the user terminal generates a PDU by the segments meeting the segment length in the obtained segment data based on scheduling information, and when a residual segment which does not meet the segment length exists in an SDU and the length of the residual segment is less than the head overhead of a PDU, the residual segment and the previous segment data are combined to generate a PDU; or
The other protocol layer of the user terminal generates a PDU by the segments meeting the segment length in the obtained segment data based on scheduling information, and when a residual segment which does not meet the segment length exists in an SDU and the length of the residual segment is equal to the head overhead of a PDU, the residual segment and the previous segment data are combined to generate a PDU; or
And the other protocol layer of the user terminal generates one PDU (protocol data Unit) by using the segments meeting the segment length in the acquired segment data based on scheduling information, and generates the PDU for the rest segments when the rest segments meeting the segment length exist in one SDU and the length of the rest segments is equal to the head overhead of one PDU.
Optionally, the header of the PDU includes all or part of the following information:
an indication field of a Sequence Number (SN) corresponding to the data part, an offset and a length of data corresponding to a first SN in an SDU corresponding to the SN, and indication information of data lengths corresponding to other SNs except the first SN, wherein the indication information is used for indicating information of whether the SN is followed by data or a next SN; or
And indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of the next SN.
An embodiment of the present invention further provides a data transmission processing method, including:
when data transmission processing is carried out, a protocol layer of the network equipment carries out segmentation operation on data so as to obtain segmented data;
another protocol layer of the network device generates the acquired segmented data into a PDU based on scheduling information.
Optionally, another protocol layer of the network device generates the obtained segmented data into a PDU based on the scheduling information, where the PDU includes:
for the initial transmission data, another protocol layer of the network equipment directly generates the acquired segmented data into PDU based on scheduling information; or
For retransmission data, another protocol layer of the network device generates the obtained segmented data into a PDU based on scheduling information and does not allow re-segmentation of the data.
Optionally, a protocol layer of the network device performs a segmentation operation on the data to obtain segmented data, including:
and a protocol layer of the network equipment performs segmentation operation on the data according to a preset segment length so as to obtain the segmented data.
Optionally, a protocol layer of the network device performs a segmentation operation on the data to obtain segmented data, including:
a protocol layer of the network device performs a segmentation operation on the data according to the dynamically determined segment length to obtain segmented data.
Optionally, the segment length is dynamically determined based on one or more of the following information:
the network device performs a desired segment length indicated by a protocol layer of a segment;
downlink channel quality information of the user terminal;
characteristics of data corresponding to the user terminal.
Optionally, the method further includes:
the protocol layer of the network device executing the segmentation sends the length information of the segment length to the protocol layer of the network device executing the scheduling, so that the protocol layer of the network device executing the scheduling allocates the initial transmission resource and/or the retransmission resource matched with the segment length according to the length information.
Optionally, the data includes an SDU, and the segmenting operation includes:
a segmentation operation according to a segment length.
Optionally, another protocol layer of the network device generates the obtained segmented data into a PDU based on the scheduling information, where the PDU includes:
another protocol layer of the network device separately generates a PDU from the segments meeting the segment length in the obtained segment data based on the scheduling information, and concatenates the remaining segments of the SDU with its consecutive SDUs to generate a PDU meeting the segment length when there are remaining segments that do not meet the segment length in an SDU, and padding is allowed for the last PDU; or
Another protocol layer of the network device separately generates a PDU from segments of the acquired segment data that satisfy the segment length based on scheduling information, and when a remaining segment of an SDU that does not satisfy the segment length exists, adds padding to the remaining segment to satisfy the segment length, and generates a PDU; or
Another protocol layer of the network device separately generates a PDU from the obtained segment data meeting the segment length based on scheduling information, and when a remaining segment of an SDU does not meet the segment length, separately generates PDUs for the remaining segment; or
Another protocol layer of the network device separately generates a PDU from the segments meeting the segment length in the obtained segment data based on scheduling information, and when a remaining segment which does not meet the segment length exists in an SDU and the length of the remaining segment is smaller than the head overhead of a PDU, combines the remaining segment with the previous segment data to generate a PDU; or
Another protocol layer of the network device separately generates one PDU from the segments meeting the segment length in the obtained segment data based on scheduling information, and when a remaining segment which does not meet the segment length exists in one SDU and the length of the remaining segment is equal to the head overhead of one PDU, combines the remaining segment with the previous segment data to generate one PDU; or
Another protocol layer of the network device separately generates one PDU for segments of the acquired segment data that satisfy the segment length based on scheduling information, and separately generates a PDU for a remaining segment when there is a remaining segment of an SDU that does not satisfy the segment length and the length of the remaining segment is equal to a header overhead of one PDU.
Optionally, the header of the PDU includes all or part of the following information:
the method comprises the following steps of indicating information of SN corresponding to a data part, offset and length of data corresponding to a first SN in SDU corresponding to the SN, and data length corresponding to other SNs except the first SN, wherein the indicating information is used for indicating whether the SN is followed by the data or the next SN; or
The header of the PDU includes all or part of the following information:
the data part comprises an indication field of a sequence number SN corresponding to the data part and indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of a next SN.
An embodiment of the present invention further provides a user terminal, including:
the segmentation module is used for controlling a protocol layer of the user terminal to perform segmentation operation on data to acquire segmented data when data transmission processing is performed;
a generating module, configured to control another protocol layer of the user terminal to generate the obtained segmented data into a PDU based on scheduling information.
Optionally, the generating module is configured to control, for the initial transmission data, another protocol layer of the user terminal to directly generate the obtained segmented data into a PDU based on the scheduling information; or
The generation module is used for controlling another protocol layer of the user terminal to generate the acquired segmented data into PDU (protocol data Unit) based on scheduling information for retransmitted data, and the data is not allowed to be re-segmented.
Optionally, the segmentation module is configured to control a protocol layer of the ue to perform a segmentation operation on data according to a preset segment length, so as to obtain segmented data.
Optionally, the segmentation module is configured to control a protocol layer of the ue to perform a segmentation operation on data according to the dynamically determined segment length to obtain segmented data.
Optionally, the dynamically determined segment length comprises a network device signaled segment length; or
The dynamically determined segment length comprises a dynamically determined segment length for the user terminal, and the user terminal further comprises:
a sending module, configured to send length information of the segment length to a network device, so that a protocol layer, which executes uplink scheduling by the network device, allocates, according to the length information, initial transmission resources and/or retransmission resources that are matched with the segment length.
Optionally, the segment length is dynamically determined based on one or more of the following information:
segment length indication information desired by the network device;
segment length indication information desired by the user terminal;
uplink channel quality information of the user terminal;
data transmission condition of the user terminal;
and the characteristics of the uplink service corresponding to the user terminal.
Optionally, the data includes uplink SDUs, and the segmenting operation includes:
a segmentation operation according to a segment length.
Optionally, the generating module is configured to control another protocol layer of the user terminal to generate a PDU separately for a segment meeting the segment length in the obtained segment data based on scheduling information, and when there is a remaining segment that does not meet the segment length in an SDU, concatenate the remaining segment of the SDU with its consecutive SDUs to generate a PDU meeting the segment length, and allow padding for a last PDU; or
The generation module is used for controlling another protocol layer of the user terminal to generate a PDU from the obtained segment data meeting the segment length based on scheduling information, and when a residual segment which does not meet the segment length exists in an SDU, padding is added to the residual segment to meet the segment length, and the PDU is generated; or
The generation module is used for controlling another protocol layer of the user terminal to generate one PDU from the obtained segmentation data meeting the segmentation length based on scheduling information, and when a residual segmentation of an SDU does not meet the segmentation length exists, generating PDU for the residual segmentation; or
The generation module is used for controlling another protocol layer of the user terminal to generate one PDU by the segments meeting the segment length in the acquired segment data based on scheduling information, and when the remaining segments not meeting the segment length exist in one SDU and the length of the remaining segments is smaller than the head overhead of one PDU, the remaining segments and the previous segment data are merged to generate one PDU; or
The generation module is used for controlling another protocol layer of the user terminal to generate one PDU by the segments meeting the segment length in the acquired segment data based on scheduling information, and when the remaining segments which do not meet the segment length exist in one SDU and the length of the remaining segments is equal to the head overhead of one PDU, the remaining segments and the previous segment data are merged to generate one PDU; or
The generation module is used for controlling another protocol layer of the user terminal to generate one PDU from the obtained segment data meeting the segment length based on scheduling information, and when the remaining segments which do not meet the segment length exist in one SDU and the length of the remaining segments is equal to the head overhead of one PDU, the PDU is generated for the remaining segments.
Optionally, the header of the PDU includes all or part of the following information:
the method comprises the following steps of indicating information of SN corresponding to a data part, offset and length of data corresponding to a first SN in SDU corresponding to the SN, and data length corresponding to other SNs except the first SN, wherein the indicating information is used for indicating whether the SN is followed by the data or the next SN; or
The header of the PDU includes all or part of the following information:
the data part comprises an indication field of a sequence number SN corresponding to the data part and indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of a next SN.
An embodiment of the present invention further provides a network device, which includes:
the segmentation module is used for controlling a protocol layer of the network equipment to perform segmentation operation on data to acquire segmented data when data transmission processing is performed;
a generating module, configured to control another protocol layer of the network device to generate the obtained segmented data into a PDU based on scheduling information.
Optionally, the generating module is configured to control, for the initial transmission data, another protocol layer of the network device to directly generate the obtained segmented data into a PDU based on the scheduling information; or
The generation module is used for controlling another protocol layer of the network equipment to generate the acquired segmented data into PDU (protocol data Unit) based on scheduling information for retransmitted data, and the data is not allowed to be re-segmented.
Optionally, the segmentation module is configured to control a protocol layer of the network device to perform a segmentation operation on the data according to a preset segment length, so as to obtain the segmented data.
Optionally, the segmentation module is configured to control a protocol layer of the network device to perform a segmentation operation on the data according to the dynamically determined segment length to obtain the segmented data.
Optionally, the segment length is dynamically determined based on one or more of the following information:
the network device performs a desired segment length indicated by a protocol layer of a segment;
uplink channel quality information of the user terminal;
characteristics of data corresponding to the user terminal.
Optionally, the network device further includes:
a sending module, configured to control a protocol layer of the network device performing segmentation to send length information of the segment length to a protocol layer of the network device performing scheduling, so that the protocol layer of the network device performing scheduling allocates, according to the length information, an initial transmission resource and/or a retransmission resource that matches the segment length.
Optionally, the data includes an SDU, and the segmenting operation includes:
a segmentation operation according to a segment length.
Optionally, the generating module is configured to control another protocol layer of the network device to generate a PDU separately for a segment meeting the segment length in the obtained segment data based on scheduling information, and when there is a remaining segment that does not meet the segment length in an SDU, concatenate the remaining segment of the SDU with its consecutive SDUs to generate a PDU meeting the segment length, and allow padding for a last PDU; or
The generation module is configured to control another protocol layer of the network device to generate a PDU separately for segments satisfying the segment length in the acquired segment data based on scheduling information, and when there are remaining segments that do not satisfy the segment length in an SDU, add padding to the remaining segments to satisfy the segment length, and generate a PDU; or
The generation module is configured to control another protocol layer of the network device to generate a PDU separately for a segment satisfying the segment length in the acquired segment data based on scheduling information, and when there are remaining segments that do not satisfy the segment length in an SDU, generate PDUs separately for the remaining segments; or
The generation module is used for controlling another protocol layer of the network equipment to generate one PDU by the segments meeting the segment length in the acquired segment data based on scheduling information, and when the remaining segments which do not meet the segment length exist in one SDU and the length of the remaining segments is smaller than the head overhead of one PDU, the remaining segments and the previous segment data are merged to generate one PDU; or
The generation module is used for controlling another protocol layer of the network equipment to generate one PDU by the segments meeting the segment length in the acquired segment data based on scheduling information, and when the remaining segments which do not meet the segment length exist in one SDU and the length of the remaining segments is equal to the head overhead of one PDU, the remaining segments are combined with the previous segment data to generate one PDU; or
The generation module is configured to control another protocol layer of the network device to generate a PDU separately for segments of the acquired segment data that satisfy the segment length based on scheduling information, and to generate a PDU separately for a remaining segment when there is a remaining segment of an SDU that does not satisfy the segment length and the length of the remaining segment is equal to a header overhead of a PDU.
Optionally, the header of the PDU includes all or part of the following information:
the method comprises the following steps of indicating information of SN corresponding to a data part, offset and length of data corresponding to a first SN in SDU corresponding to the SN, and data length corresponding to other SNs except the first SN, wherein the indicating information is used for indicating whether the SN is followed by the data or the next SN; or
The header of the PDU includes all or part of the following information:
the data part comprises an indication field of a sequence number SN corresponding to the data part and indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of a next SN.
The technical scheme of the invention at least has the following beneficial effects:
in the embodiment of the invention, when data transmission processing is carried out, a protocol layer of the user terminal carries out segmentation operation on data so as to obtain segmented data; and generating the acquired segmented data into PDU by another protocol layer of the user terminal based on scheduling information. Therefore, the segmentation of the data and the generation of the PDU are realized by different protocol layers, and the complexity of the protocol layers can be reduced.
Detailed Description
In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments.
Referring to fig. 1, fig. 1 is a schematic diagram of a network structure provided by an embodiment of the present invention, as shown in fig. 1, including a user terminal 11 and a network Device 12, where the user terminal 11 may be a terminal Device such as a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), or a Wearable Device (Wearable Device), and it should be noted that a specific type of the user terminal 11 is not limited in the embodiment of the present invention. The user terminal 11 may establish communication with the network device 12, where the network in the drawing may indicate that the network device 12 establishes communication with the user terminal 11 wirelessly, and the network device 12 may be an evolved Node B (eNB) or other base station, and may also be other network side devices, for example: the access point device, it should be noted that the specific type of the network device 12 is not limited in the embodiment of the present invention.
Referring to fig. 2, an embodiment of the invention provides a data transmission processing method, as shown in fig. 2, including the following steps:
201. when the data transmission processing is performed, a protocol layer of the user terminal performs a segmentation operation on the data to obtain segmented data.
202. And generating the acquired segmented data into PDU by another protocol layer of the user terminal based on scheduling information.
In this embodiment of the present invention, the data may be uplink data, for example: the data may be one or more uplink data, for example: the data may be understood as one or more SDUs, or the data may be higher layer data, such as: a higher layer PDU. In addition, the segmentation may be understood as dividing data into a plurality of segments, that is, after one data performs a segmentation operation, a plurality of segments are obtained.
In addition, the generating of the obtained segmented data into the PDU based on the scheduling information may be understood as generating the PDU from the obtained segmented data in the resource scheduled by the scheduling information, so as to transmit the generated PDU in the resource scheduled by the scheduling information.
In addition, in this embodiment, the generation of the PDU by the acquired segment data may be that each segment data is generated into one PDU alone, or the segment data conforming to the segment length is generated into one PDU alone, and the segment data not conforming to the segment length is concatenated into the generated PDU. Therefore, the short data of each PDU can be realized, and the phenomenon that the PDU is too small to be utilized due to the fact that the PDU is short can be avoided, so that the transmission resources are fully utilized, compromise between head cost and resource utilization rate is realized, and the resource utilization rate of the system is improved.
In addition, in the embodiment of the present invention, the one protocol layer and the other protocol layer may be understood as two adjacent protocol layers. For example: the one protocol layer may be an L3 protocol layer and the other protocol layer may be an L2 protocol layer.
Optionally, another protocol layer of the ue generates the obtained segmented data into a PDU based on the scheduling information, including:
for the initial transmission data, another protocol layer of the user terminal directly generates the acquired segmented data into PDU based on scheduling information; or
For retransmission data, another protocol layer of the user terminal generates the acquired segmented data into a PDU based on scheduling information and does not allow re-segmentation of the data.
In this embodiment, it can be realized that the obtained segmented data is directly generated into PDU for the initial transmission data, and the previous segmented data is generated into PDU for the retransmission data without re-segmentation.
Optionally, a protocol layer of the ue performs a segmentation operation on the data to obtain segmented data, including:
and the protocol layer of the user terminal performs segmentation operation on the data according to the preset segment length so as to acquire the segment data.
In this embodiment, the segmentation may be performed according to a preset segment length, where the preset segment length may be obtained by a user terminal and a network device through negotiation in advance, or may be obtained by default by the user terminal, and the embodiment of the present invention is not limited thereto. In addition, the segmentation can be carried out according to a preset segmentation length in the initial stage, and the segmentation can be carried out according to a dynamic segmentation length in the subsequent process.
Optionally, a protocol layer of the ue performs a segmentation operation on the data to obtain segmented data, including:
and a protocol layer of the user terminal performs segmentation operation on the data according to the dynamically determined segment length so as to acquire the segment data.
In this embodiment, segmentation according to a dynamic segment length can be realized, and the obtained segment data with the dynamic segment length can be more easily suitable for the actual transmission requirement, so as to improve the performance. In addition, the dynamically determined segment length here may be dynamically configured by the network device or dynamically determined by the user terminal.
Optionally, the dynamically determined segment length comprises a segment length notified by the network device.
In this embodiment, it may be achieved that the dynamically determined segment length is informed by the network device, for example: the network device notifies the segment length to the user terminal by means of configuration signaling or broadcast message.
In this embodiment, the segment length may be dynamically determined based on one or more of the following information:
segment length indication information desired by the network device;
segment length indication information desired by the user terminal;
uplink channel quality information of the user terminal;
data transmission condition of the user terminal;
and the characteristics of the uplink service corresponding to the user terminal.
That is, the network device dynamically determines the segment length based on one or more items, where the indication information of the expected segment length of the network device may be understood as the indication information indicating the expected segment length of the network device, and when the indication information exists, the segment length may be the segment length indicated by the indication information. The segment length indication information desired by the ue may be understood as indication information indicating a segment length desired by the ue, and when the indication information exists, the segment length may be a segment length indicated by the indication information. If both the indication information exist, the segmentation can be performed by preferentially using the segment length expected by the network device. In addition, when the above uplink channel quality information exists, the above segment length may be a segment length that is decreased when the user terminal channel quality becomes poor, and a segment length that is increased when the user terminal channel quality becomes good. In addition, when the above-mentioned data transmission situation exists, the above-mentioned segment length may be a length that is decreased when the data transmission situation becomes worse, and a length that is increased when the data transmission situation becomes better. In addition, when the characteristics of the uplink data corresponding to the user terminal exist, when the uplink service characteristics of the user terminal change, for example, the service packet becomes large, the segment length is increased, and otherwise, the segment length can be decreased.
Optionally, the dynamically determined segment length comprises a dynamically determined segment length of the user terminal, and the method further comprises:
and the user terminal sends the length information of the segment length to network equipment so that a protocol layer of the network equipment executing uplink scheduling allocates initial transmission resources and/or retransmission resources matched with the segment length according to the length information.
In this embodiment, it can be realized that the user terminal determines the segment length by itself, and then the protocol layer that executes the uplink scheduling is notified of the segment length, so that the protocol layer that executes the uplink scheduling by the network device can be better matched with the segment length when allocating the initial transmission and/or retransmission resources, thereby reducing padding and improving the resource utilization rate.
In this embodiment, the segment length may be dynamically determined based on one or more of the following information:
segment length indication information desired by the network device;
segment length indication information desired by the user terminal;
uplink channel quality information of the user terminal;
data transmission condition of the user terminal;
and the characteristics of the uplink service corresponding to the user terminal.
That is, the user terminal dynamically determines the segment length based on one or more items, where in this embodiment, reference may be made to an embodiment in which the network device dynamically determines the segment length, and details are not described here.
Optionally, the data includes uplink SDUs, and the segmenting operation includes:
a segmentation operation according to a segment length.
In this embodiment, segmentation of SDUs may be implemented, for example: one or more SDUs are segmented. In addition, the segment length here may be a preset segment length described in the foregoing embodiment, or a dynamically determined segment length determined by the network device or the user terminal. And since the segment length is determined before the segmentation operation is performed, the segment length in the embodiment of the present invention may be understood as a pre-segment length.
In this embodiment, the generating, by another protocol layer of the ue, the PDU from the acquired segmented data based on the scheduling information may include:
and the other protocol layer of the user terminal independently generates a PDU (protocol data Unit) by the segments meeting the segment length in the acquired segment data based on the scheduling information, and when the remaining segments not meeting the segment length exist in one SDU, concatenates the remaining segments of the SDU with the continuous SDU thereof to generate the PDU meeting the segment length, and allows padding for the last PDU.
In this embodiment, it is possible to generate a PDU for each segment satisfying the segment length, which is understood to be segment data having a length equal to the segment length. Since there may exist an SDU not equal to an integer multiple of the segmentation length in practical applications, there may exist segments that do not satisfy the segmentation length after the segmentation. In this embodiment, it may be implemented to concatenate segments that do not satisfy the segment length, so as to generate a PDU that satisfies the segment length. That is, the data of the previous SDU and the next SDU are allowed to be concatenated, and a PDU meeting the length requirement of the pre-segmentation segment is generated. In addition, the above-mentioned concatenating the remaining segment of the SDU with its consecutive SDU may be, but is not limited to, concatenating the remaining segment of the SDU with its consecutive remaining segment of the SDU, or concatenating the remaining segment of the SDU with its consecutive segment of the SDU satisfying the segment length, and so on. A PDU satisfying the segment length may be understood as a PDU having a data portion equal to the segment length, i.e. a PDU comprising a plurality of segments whose sum is equal to the segment length. In addition, by allowing padding to the latest PDU, the data part of the PDU is equal to the fragment length, so that all PDUs are generated according to the fragment length strictly. Therefore, the waste of transmission resources is avoided, and the utilization rate of the transmission resources is improved.
In this embodiment, the header of the PDU may include all or part of the following information:
the SN corresponding to the data part comprises an indication field of the SN corresponding to the data part, the offset and the length of the data corresponding to the first SN in the SDU corresponding to the SN, and indication information of the data lengths corresponding to other SNs except the first SN, wherein the indication information is used for indicating whether the SN is followed by the data or the next SN.
The head can indicate each SDU corresponding to the PDU generated by concatenation, the offset and the length of the data corresponding to the first SN in the corresponding SDU, and the data length corresponding to other SNs.
In the foregoing embodiment, another protocol layer of the ue generates the obtained segmented data into a PDU based on scheduling information, including:
and the other protocol layer of the user terminal generates a PDU (protocol data Unit) by using the segments meeting the segment length in the acquired segment data based on scheduling information, and when the remaining segments not meeting the segment length exist in an SDU (service data Unit), adds padding to the remaining segments to meet the segment length and generates the PDU.
In this embodiment, the concatenation of data of a previous SDU and a next SDU is not allowed, but padding is added to the remaining segments to satisfy the segment length, so that a PDU is generated for each segment individually, and each PDU is generated exactly according to the segment length. Therefore, the waste of transmission resources is avoided, and the utilization rate of the transmission resources is improved.
In the foregoing embodiment, another protocol layer of the ue generates the obtained segmented data into a PDU based on scheduling information, including:
and the other protocol layer of the user terminal generates one PDU (protocol data Unit) by using the segments meeting the segment length in the acquired segment data based on scheduling information, and generates the PDU for the rest segments when the rest segments meeting the segment length exist in one SDU.
In this embodiment, it is achieved that segments satisfying the segment length generate one PDU alone, i.e. PDUs are generated strictly according to the segment length in normal cases, while PDUs can be generated alone for the remaining segments, i.e. in some special cases PDUs are allowed to be generated not strictly according to the segment length, i.e. smaller than the segment length. In addition, in this embodiment, when the overhead of the header of one PDU separately generated for the remaining segments is smaller than the overhead of the data part, the PDU may be separately generated for the remaining segments.
In the foregoing embodiment, another protocol layer of the ue generates the obtained segmented data into a PDU based on scheduling information, including:
and the other protocol layer of the user terminal generates one PDU (protocol data Unit) by separately using the segments meeting the segment length in the acquired segment data based on scheduling information, and when the remaining segments meeting the segment length exist in one SDU and the length of the remaining segments is less than the head overhead of one PDU, the remaining segments and the previous segment data are combined to generate one PDU.
In this embodiment, it can be realized that the segments meeting the segment length generate one PDU alone, that is, the PDU is generated strictly according to the segment length under normal conditions, and for the remaining segments, when the length of the remaining segments is smaller than the header overhead of one PDU, that is, when the header overhead of one PDU generated for the remaining segments alone is larger than the data part overhead of the PDU, the remaining segments and the previous segment data are merged to generate one PDU, so that it is possible to avoid generating a PDU with an excessively small data part, and reduce the header overhead.
Optionally, another protocol layer of the ue generates the obtained segmented data into a PDU based on the scheduling information, including:
the other protocol layer of the user terminal generates a PDU by the segments meeting the segment length in the obtained segment data based on scheduling information, and when a residual segment which does not meet the segment length exists in an SDU and the length of the residual segment is equal to the head overhead of a PDU, the residual segment and the previous segment data are combined to generate a PDU; or
And the other protocol layer of the user terminal generates one PDU (protocol data Unit) by using the segments meeting the segment length in the acquired segment data based on scheduling information, and generates the PDU for the rest segments when the rest segments meeting the segment length exist in one SDU and the length of the rest segments is equal to the head overhead of one PDU.
In this embodiment, when the length of the remaining segment is equal to the header overhead of one PDU, one PDU may be generated for the remaining segment alone or for data combination of the previous segment. Specifically, the selection may be performed according to actual transmission, for example: in order to reduce the overhead, the data of the previous segment of the remaining segments may be combined to generate one PDU, whereas the PDU may be generated separately for the remaining segments.
In the embodiment without concatenation, the header of the PDU includes the following information:
and indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of the next SN.
Since no concatenation is done, the header only needs to indicate its SN, and information indicating whether the SN is followed by data or the next SN, thereby reducing header overhead.
In the embodiment of the invention, when data transmission processing is carried out, a protocol layer of the user terminal carries out segmentation operation on data so as to obtain segmented data; and generating the acquired segmented data into PDU by another protocol layer of the user terminal based on scheduling information. Therefore, the segmentation of the data and the generation of the PDU are realized by different protocol layers, and the complexity of the protocol layers can be reduced.
Referring to fig. 3, an embodiment of the invention provides another data transmission processing method, as shown in fig. 3, including the following steps:
301. when data transmission processing is carried out, a protocol layer of the network equipment carries out segmentation operation on data so as to obtain segmented data;
302. and generating the acquired segmented data into a PDU by another protocol layer of the network equipment based on the scheduling information.
For the description of the data, the segmentation operation, and the PDU generation, reference may be made to the description of the data, the segmentation operation, and the PDU generation in the embodiment shown in fig. 2, which is not described herein again. In addition, the data may be downlink data.
Optionally, another protocol layer of the network device generates the obtained segmented data into a PDU based on the scheduling information, where the PDU includes:
for the initial transmission data, another protocol layer of the network equipment directly generates the acquired segmented data into PDU based on scheduling information; or
For retransmission data, another protocol layer of the network device generates the obtained segmented data into a PDU based on scheduling information and does not allow re-segmentation of the data.
Optionally, a protocol layer of the network device performs a segmentation operation on the data to obtain segmented data, including:
and a protocol layer of the network equipment performs segmentation operation on the data according to a preset segment length so as to obtain the segmented data.
Optionally, a protocol layer of the network device performs a segmentation operation on the data to obtain segmented data, including:
a protocol layer of the network device performs a segmentation operation on the data according to the dynamically determined segment length to obtain segmented data.
Optionally, the segment length is dynamically determined based on one or more of the following information:
the network device performs a desired segment length indicated by a protocol layer of a segment;
downlink channel quality information of the user terminal;
characteristics of data corresponding to the user terminal.
The dynamic determining method of the segment length may refer to the implementation of dynamically determining the segment length described in the embodiment shown in fig. 2, and is not described herein again.
Optionally, the method further includes:
the protocol layer of the network device executing the segmentation sends the length information of the segment length to the protocol layer of the network device executing the scheduling, so that the protocol layer of the network device executing the scheduling allocates the initial transmission resource and/or the retransmission resource matched with the segment length according to the length information.
In this embodiment, it can be realized that the protocol layer that can notify the network device of the segment length to execute the scheduling can be better matched with the segment length when the protocol layer that the network device executes the scheduling allocates the initial transmission and/or retransmission resources, thereby reducing padding and improving the resource utilization rate. The protocol layer for performing scheduling may be a protocol layer for performing downlink scheduling.
Optionally, the data includes an SDU, and the segmenting operation includes:
a segmentation operation according to a segment length.
Optionally, another protocol layer of the network device generates the obtained segmented data into a PDU based on the scheduling information, where the PDU includes:
another protocol layer of the network device separately generates a PDU from the segments meeting the segment length in the obtained segment data based on the scheduling information, and concatenates the remaining segments of the SDU with its consecutive SDUs to generate a PDU meeting the segment length when there are remaining segments that do not meet the segment length in an SDU, and padding is allowed for the last PDU; or
Another protocol layer of the network device separately generates a PDU from segments of the acquired segment data that satisfy the segment length based on scheduling information, and when a remaining segment of an SDU that does not satisfy the segment length exists, adds padding to the remaining segment to satisfy the segment length, and generates a PDU; or
Another protocol layer of the network device separately generates a PDU from the obtained segment data meeting the segment length based on scheduling information, and when a remaining segment of an SDU does not meet the segment length, separately generates PDUs for the remaining segment; or
Another protocol layer of the network device separately generates a PDU from the segments meeting the segment length in the obtained segment data based on scheduling information, and when a remaining segment which does not meet the segment length exists in an SDU and the length of the remaining segment is smaller than the head overhead of a PDU, combines the remaining segment with the previous segment data to generate a PDU; or
Another protocol layer of the network device separately generates one PDU from the segments meeting the segment length in the obtained segment data based on scheduling information, and when a remaining segment which does not meet the segment length exists in one SDU and the length of the remaining segment is equal to the head overhead of one PDU, combines the remaining segment with the previous segment data to generate one PDU; or
Another protocol layer of the network device separately generates one PDU for segments of the acquired segment data that satisfy the segment length based on scheduling information, and separately generates a PDU for a remaining segment when there is a remaining segment of an SDU that does not satisfy the segment length and the length of the remaining segment is equal to a header overhead of one PDU.
In this embodiment, the header of the PDU may include all or part of the following information:
the method comprises the following steps of indicating information of SN corresponding to a data part, offset and length of data corresponding to a first SN in SDU corresponding to the SN, and data length corresponding to other SNs except the first SN, wherein the indicating information is used for indicating whether the SN is followed by the data or the next SN; or
The header of the PDU may include the following information:
the data part comprises an indication field of a sequence number SN corresponding to the data part and indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of a next SN.
The embodiments of generating PDUs through concatenation and not allowing to generate PDUs through concatenation described above may refer to the embodiments shown in fig. 2, and are not described herein again.
It should be noted that, this embodiment is used as an implementation of data on the network device side corresponding to the embodiment shown in fig. 2, and for avoiding repeated description, reference may be made to the relevant description of the embodiment shown in fig. 2 for a specific implementation of this embodiment, which is not described again in this embodiment. In this embodiment, the complexity of the protocol layer can be reduced as well.
The embodiments described in the above examples are illustrated below by way of a number of examples:
example 1:
this example is illustrated by the following data transmission process:
as shown in fig. 4, a three-layer protocol stack structure is taken as an example for explanation. The L3 protocol layer under the three-layer protocol stack structure has the pre-segmentation function and can also have the functions of header compression, safety and the like. Of course, header compression and security related functions can be extracted separately to generate a protocol layer L4 above L3, so that the protocol stack structure becomes a four-layer protocol stack. Since whether the four-layer protocol stack or the three-layer protocol stack does not affect the content to be protected in this patent, only the three-layer protocol stack structure is taken as an example for description here. The following description applies equally under the four-layer protocol layer structure.
In fig. 4, the L3 protocol layer of the network device is a protocol layer that performs downlink pre-segmentation, and the L2 protocol layer of the network device is a protocol layer that performs downlink scheduling.
The downlink data transmission process under the protocol stack structure is as follows:
the L3 protocol layer of the network device determines the segment length and notifies the L2 protocol layer of the network device;
the L3 protocol layer of the network device first determines the downstream fragment length. The initial downlink segment length may be a default value, such as agreed upon or based on a default configuration. The subsequent downstream segment length may be dynamically adjusted. The dynamic adjustment of the segment length may be based on one or a combination of the following information:
the network equipment indicates the expected pre-segmentation length to a protocol layer for executing the pre-segmentation of the user terminal;
the physical layer of the user terminal feeds back the uplink channel quality information of the terminal to a protocol layer which executes the segmentation operation of the user terminal;
characteristics of a downlink service corresponding to the user terminal, such as a packet size;
such as reducing the segment length when the user terminal channel quality becomes poor; when the downlink service characteristics of the terminal change, for example, the service packet becomes larger, the segment length is increased.
The L3 protocol layer of the user terminal informs the L2 protocol layer of the network device of the determined segment length, so that when the L2 protocol layer scheduler of the network device performs resource allocation, the allocated resource can be better matched with the segment length, thereby reducing the padding size and improving the resource utilization rate.
The L3 protocol layer of the network device performs the segmentation operation, wherein the L3 protocol layer of the network device performs the segmentation operation in the following three ways:
firstly, segmenting strictly according to a segment length, allowing data of a previous SDU and a next SDU to be concatenated, and generating a PDU meeting the requirement of a pre-segment length. Padding is allowed for the last PDU.
And secondly, segmenting strictly according to the segment length, and not allowing the data of the previous SDU and the next SDU to be concatenated. Padding is added to complement the pre-segment length when the last segment of an SDU does not satisfy the pre-segment length.
Normally, pre-segmenting according to the segment length, but in some special cases, the length of the real segment is allowed to be larger or smaller than the predetermined segment length, and the specific case includes one or all of the following cases:
concatenation of SDUs is not allowed, so that a PDU can be generated separately if the length of the tail remaining portion of an SDU after segmentation is smaller than a predetermined pre-segmentation length.
SDU concatenation is not allowed, so that when an SDU is segmented, if the head cost of a PDU generated by the tail part of the SDU is larger than that of a data part, the data part and the previous segmented data are allowed to be combined to generate a PDU.
For the first mode, since segmentation and concatenation are supported, the header design thereof may include at least the following indication fields. Of course, if the middle contains a plurality of consecutive SNs, the indication to the middle SN may be omitted, and only the number and length of the middle SNs may be indicated. For example: the header may include the following:
a SN indication field (SN) corresponding to the data portion;
the offset (SO) and the length (L) of the data corresponding to the first SN in the SDU corresponding to the SN;
data length (L) corresponding to other SNs;
indication information (E) for indicating whether the SN is followed by data or information of a next SN.
For the second and third modes, since only segmentation is supported and concatenation is not supported, the situation design is simple, and only the following contents are included:
SN indication field (SN) corresponding to data portion
Indication information (E) for indicating whether the SN is followed by data or SN length indication information.
After the L3 protocol layer of the network device completes segmentation, the segmented data may be cached in the L3 protocol layer of the network device, or may be sent to the L2 protocol layer of the network device.
And the L2 protocol layer of the network equipment executes downlink scheduling operation, wherein the L2 protocol layer of the network equipment can execute downlink scheduling after the segment length indication information is acquired from the L3 protocol layer of the network equipment, and the resource allocation is matched with the integer number of pre-segment lengths as much as possible during scheduling, so that the size of padding resources can be reduced as much as possible, and the resource utilization rate is improved.
The L2 protocol layer of the network device organizes the PDUs, i.e., the segmented data into PDUs. For example: after the L2 protocol layer of the network device determines the scheduling information, segmented data is selected from the buffer of the L3 protocol layer of the network device or the L2 protocol layer of the network device to be concatenated and multiplexed, and PDU is generated.
The network device performs downlink data transmission, for example: and the L2 protocol layer of the network equipment transmits the organized L2PDU to the L1 protocol layer of the network equipment for downlink data transmission.
The network device performs automatic Repeat reQuest (ARQ) retransmission of downlink data. If the terminal still cannot correctly receive the downlink data sent to the terminal by the network after Hybrid Automatic Repeat reQuest (HARQ) retransmission, ARQ retransmission of the downlink data needs to be performed, the L2 layer of the network device allocates resources for the downlink retransmission data based on the segmentation size of the L3 protocol layer of the network device, and the ARQ retransmission data is not allowed to be re-segmented.
Example 2:
this example is illustrated in the context of an uplink data transmission process
As shown in fig. 5, a three-layer protocol stack structure is taken as an example for explanation. The L3 layer has a segmentation function under the three-layer protocol stack structure, and can also have the functions of header compression, safety and the like. Of course, header compression and security related functions can be extracted separately to generate a protocol layer L4 above the L3 protocol layer, so that the protocol stack structure becomes a four-layer protocol stack. Since whether the four-layer protocol stack or the three-layer protocol stack does not affect the content to be protected in this patent, only the three-layer protocol stack structure is taken as an example for description here. The following description applies equally under the four-layer protocol layer structure.
In fig. 5, the L3 protocol layer of the user terminal performs uplink fragmentation, and the L2 protocol layer of the network device is a protocol layer that performs uplink scheduling.
The uplink data transmission process under the protocol stack structure is as follows:
the L3 protocol layer of the user terminal determines the fragment length and informs the L2 protocol layer of the network device.
The L3 protocol layer of the user terminal first determines the upstream fragment length. The initial upstream pre-partition length may be a default value, such as a protocol agreement or based on a default configuration. The length of the subsequent uplink pre-partition can be dynamically adjusted. The length of the pre-partition can be determined by the network to inform the terminal, or can be determined by the terminal. Determining the length of the pre-partition may be based on one or a combination of the following information:
the length indication information of the pre-partition expected by the network equipment;
the length indication information of the pre-segment expected by the user terminal;
uplink channel quality information of the terminal;
characteristics of an uplink service corresponding to the terminal, such as a packet size;
such as reducing the length of the pre-segment when the channel quality of the terminal becomes poor; when the downlink service characteristics of the terminal change, for example, the service packet becomes larger, the length of the pre-segment is increased.
In addition, the pre-segmentation length of the L3 protocol layer of the user terminal needs to notify the L2 protocol layer of the network device, so that when the L2 protocol layer scheduler of the network device performs resource allocation, the allocated resources can be better matched with the pre-segmentation length, thereby reducing the padding size and improving the resource utilization rate.
If the segment length of the L3 protocol layer of the user terminal is determined by the network device, informing the L2 protocol layer of the network device by the network device through an internal interaction mode; if the segment length of the L3 protocol layer of the user terminal is determined by the user terminal, the L2 protocol layer of the network device is signaled by the user terminal.
The L3 protocol layer of the ue performs segmentation, wherein the L3 protocol layer of the ue performs pre-segmentation, specifically, the following three methods are used:
firstly, segmenting strictly according to the length of the pre-segmentation segment, allowing the data of the previous SDU and the data of the next SDU to be concatenated, and generating a PDU meeting the length requirement of the pre-segmentation segment.
And secondly, segmenting strictly according to the segment length, and not allowing the data of the previous SDU and the next SDU to be concatenated. Padding is added to complement the pre-segment length when the last segment of an SDU does not satisfy the pre-segment length.
Normally, pre-segmenting according to the segment length, but in some special cases, the length of the real segment is allowed to be larger or smaller than the predetermined segment length, and the specific case includes one or all of the following cases:
concatenation of SDUs is not allowed, so that a PDU can be generated separately if the length of the tail remaining portion of an SDU after segmentation is smaller than a predetermined pre-segmentation length.
SDU concatenation is not allowed, so that when an SDU is segmented, if the head cost of a PDU generated by the tail part of the SDU is larger than that of a data part, the data part and the previous segmented data are allowed to be combined to generate a PDU.
For the first mode, since segmentation and concatenation are supported, the header design thereof may include at least the following indication fields. Of course, if the middle contains a plurality of consecutive SNs, the indication to the middle SN may be omitted, and only the number and length of the middle SNs may be indicated. For example: the header may include the following:
a SN indication field (SN) corresponding to the data portion;
the offset (SO) and the length (L) of the data corresponding to the first SN in the SDU corresponding to the SN;
data length (L) corresponding to other SNs;
indication information (E) for indicating whether the SN is followed by data or information of a next SN.
For the second and third modes, since only segmentation is supported and concatenation is not supported, the situation design is simple, and only the following contents are included:
SN indication field (SN) corresponding to data portion
Indication information (E) for indicating whether the SN is followed by data or SN length indication information.
After the L3 protocol layer of the ue completes segmentation, the segmented data may be buffered in the L3 protocol layer of the ue, or may be sent to the L2 protocol layer of the ue.
And the L2 protocol layer of the network equipment executes downlink scheduling operation, wherein the L2 protocol layer of the network equipment executes downlink scheduling after being based on the segment length indication information of the L3 protocol layer of the user terminal, and the resource allocation is matched with the integer number of pre-segment lengths as much as possible during scheduling, so that the size of padding resources can be reduced as much as possible, and the resource utilization rate is improved. The allocated resources are then signalled to the user terminal via the physical layer.
The L2 protocol layer of the user terminal organizes PDUs, for example: after the L2 protocol layer of the user terminal determines the scheduling information, segmented data is selected from the buffer of the L3 protocol layer of the user terminal or the L2 protocol layer of the user terminal for concatenation and multiplexing, and PDU is generated.
The user terminal performs uplink data transmission, for example: and the L2 protocol layer of the user terminal transmits the organized L2PDU to the L1 protocol layer of the user terminal for uplink data transmission.
And the user terminal uplink data ARQ is retransmitted. If the uplink data of the user terminal still cannot be successfully received by the network device through the HARQ retransmission, the ARQ retransmission of the uplink data is required, and the L2 protocol layer of the network device allocates resources for the uplink retransmission data based on the segment size of the L3 protocol layer of the user terminal, wherein the ARQ retransmission data is not allowed to be re-segmented.
Referring to fig. 6, an embodiment of the present invention provides a ue, as shown in fig. 6, a ue 60 includes:
a segmenting module 61, configured to control a protocol layer of the ue to perform a segmenting operation on data to obtain segmented data when performing data transmission processing;
a generating module 62, configured to control another protocol layer of the user terminal to generate the obtained segmented data into a PDU based on scheduling information.
Optionally, the generating module 62 is configured to control, for the initial transmission data, another protocol layer of the user terminal to directly generate the obtained segmented data into a PDU based on the scheduling information; or
The generating module 62 is configured to, for retransmission data, control another protocol layer of the user terminal to generate the acquired segmented data into a PDU based on scheduling information, and not allow re-segmentation of the data.
Optionally, the segmenting module 61 is configured to control a protocol layer of the ue to perform a segmentation operation on data according to a preset segment length, so as to obtain segmented data.
Optionally, the segmentation module 61 is configured to control a protocol layer of the ue to perform a segmentation operation on the data according to the dynamically determined segment length to obtain the segmented data.
Optionally, the dynamically determined segment length comprises a network device signaled segment length; or
The dynamically determined segment length comprises a dynamically determined segment length for the user terminal, and as shown in fig. 7, the user terminal further comprises:
a sending module 63, configured to send the length information of the segment length to a network device, so that a protocol layer that executes uplink scheduling by the network device allocates, according to the length information, initial transmission resources and/or retransmission resources that are matched with the segment length.
Optionally, the segment length is dynamically determined based on one or more of the following information:
segment length indication information desired by the network device;
segment length indication information desired by the user terminal;
uplink channel quality information of the user terminal;
data transmission condition of the user terminal;
and the characteristics of the uplink service corresponding to the user terminal.
Optionally, the data includes uplink SDUs, and the segmenting operation includes:
a segmentation operation according to a segment length.
Optionally, the generating module 62 is configured to control another protocol layer of the user terminal to generate a PDU separately for a segment meeting the segment length in the obtained segment data based on the scheduling information, and when there is a remaining segment that does not meet the segment length in an SDU, concatenate the remaining segment of the SDU with its consecutive SDUs to generate a PDU meeting the segment length, and allow padding for a last PDU; or
The generating module 62 is configured to control another protocol layer of the user terminal to generate a PDU separately for segments satisfying the segment length in the acquired segment data based on scheduling information, and when there are remaining segments that do not satisfy the segment length in an SDU, add padding to the remaining segments to satisfy the segment length, and generate a PDU; or
The generating module 62 is configured to control another protocol layer of the ue to generate a PDU separately for segments of the acquired segment data that satisfy the segment length based on scheduling information, and when there are remaining segments of an SDU that do not satisfy the segment length, generate PDUs separately for the remaining segments; or
The generating module 62 is configured to control another protocol layer of the ue to generate a PDU separately from segments of the acquired segment data that satisfy the segment length based on scheduling information, and when there is a remaining segment of an SDU that does not satisfy the segment length and the length of the remaining segment is smaller than a header overhead of a PDU, merge the remaining segment with its previous segment data to generate a PDU; or
The generating module 62 is configured to control another protocol layer of the ue to generate a PDU separately from segments of the acquired segment data that satisfy the segment length based on scheduling information, and when there is a remaining segment of an SDU that does not satisfy the segment length and the length of the remaining segment is equal to a header overhead of a PDU, merge the remaining segment with its previous segment data to generate a PDU; or
The generating module 62 is configured to control another protocol layer of the user terminal to generate a PDU separately for segments of the acquired segment data that satisfy the segment length based on scheduling information, and to generate a PDU separately for a remaining segment when there is a remaining segment of an SDU that does not satisfy the segment length and the length of the remaining segment is equal to a header overhead of the PDU.
Optionally, the header of the PDU includes all or part of the following information:
the method comprises the following steps of indicating information of SN corresponding to a data part, offset and length of data corresponding to a first SN in SDU corresponding to the SN, and data length corresponding to other SNs except the first SN, wherein the indicating information is used for indicating whether the SN is followed by the data or the next SN; or
The header of the PDU includes all or part of the following information:
and indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of the next SN.
It should be noted that, in this embodiment, the user terminal 60 may be a terminal in the embodiment shown in fig. 1 to fig. 5, and any implementation of the user terminal in the embodiment shown in fig. 1 to fig. 5 may be implemented by the user terminal 60 in this embodiment, and the same beneficial effects are achieved, which is not described herein again.
Referring to fig. 8, an embodiment of the present invention provides a network device, as shown in fig. 8, a network device 80 includes:
a segmenting module 81, configured to control a protocol layer of the network device to perform a segmenting operation on data to obtain segmented data when data transmission processing is performed;
a generating module 82, configured to control another protocol layer of the network device to generate the obtained segmented data into a PDU based on scheduling information.
Optionally, the generating module 82 is configured to control, for the initial transmission data, another protocol layer of the network device to directly generate the obtained segmented data into a PDU based on the scheduling information; or
The generating module 82 is configured to, for retransmission data, control another protocol layer of the network device to generate the acquired segmented data into a PDU based on scheduling information, and not allow re-segmentation of the data.
Optionally, the segmenting module 81 is configured to control a protocol layer of the network device to perform a segmentation operation on the data according to a preset segment length, so as to obtain the segmented data.
Optionally, the segmenting module 81 is configured to control a protocol layer of the network device to perform a segmentation operation on the data according to the dynamically determined segment length, so as to obtain the segmented data.
Optionally, the segment length is dynamically determined based on one or more of the following information:
the network device performs a desired segment length indicated by a protocol layer of a segment;
downlink channel quality information of the user terminal;
characteristics of data corresponding to the user terminal.
Optionally, as shown in fig. 9, the network device further includes:
a sending module 83, configured to control the protocol layer that performs segmentation by the network device to send length information of the segment length to the protocol layer that performs scheduling by the network device, so that the protocol layer that performs scheduling by the network device allocates, according to the length information, initial transmission resources and/or retransmission resources that match the segment length.
Optionally, the data includes an SDU, and the segmenting operation includes:
a segmentation operation according to a segment length.
Optionally, the generating module 82 is configured to control another protocol layer of the network device to generate a PDU separately for a segment meeting the segment length in the obtained segment data based on the scheduling information, and when there is a remaining segment that does not meet the segment length in an SDU, concatenate the remaining segment of the SDU with its consecutive SDUs to generate a PDU meeting the segment length, and allow padding for a last PDU; or
The generating module 82 is configured to control another protocol layer of the network device to generate a PDU separately for segments satisfying the segment length in the acquired segment data based on scheduling information, and when there are remaining segments that do not satisfy the segment length in an SDU, add padding to the remaining segments to satisfy the segment length, and generate a PDU; or
The generating module 82 is configured to control another protocol layer of the network device to generate, based on the scheduling information, one PDU separately for segments of the acquired segment data that satisfy the segment length, and to generate, when there are remaining segments of an SDU that do not satisfy the segment length, PDUs separately for the remaining segments; or
The generating module 82 is configured to control another protocol layer of the network device to generate a PDU separately from segments of the acquired segment data that satisfy the segment length based on scheduling information, and when there are remaining segments of an SDU that do not satisfy the segment length and the length of the remaining segments is smaller than a header overhead of a PDU, merge the remaining segments with the previous segment data to generate a PDU; or
The generating module 82 is configured to control another protocol layer of the network device to generate a PDU separately from segments of the acquired segment data that satisfy the segment length based on scheduling information, and when there are remaining segments of an SDU that do not satisfy the segment length and the length of the remaining segments is equal to a header overhead of a PDU, merge the remaining segments with the previous segment data to generate a PDU; or
The generating module 82 is configured to control another protocol layer of the network device to generate a PDU separately for segments of the acquired segment data that satisfy the segment length based on scheduling information, and to generate a PDU separately for a remaining segment when there is a remaining segment of an SDU that does not satisfy the segment length and the length of the remaining segment is equal to a header overhead of the PDU.
Optionally, the header of the PDU includes all or part of the following information:
the method comprises the following steps of indicating information of SN corresponding to a data part, offset and length of data corresponding to a first SN in SDU corresponding to the SN, and data length corresponding to other SNs except the first SN, wherein the indicating information is used for indicating whether the SN is followed by the data or the next SN; or
The header of the PDU includes all or part of the following information:
the data part comprises an indication field of a sequence number SN corresponding to the data part and indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of a next SN.
It should be noted that the network device 80 in this embodiment may be the network device in the embodiment shown in fig. 1 to fig. 5, and any implementation of the network device in the embodiment shown in fig. 1 to fig. 5 may be implemented by the network device 80 in this embodiment to achieve the same beneficial effects, which is not described herein again.
Referring to fig. 10, there is shown a structure of a user terminal, the terminal including: a processor 1000, a transceiver 1010, a memory 1020, a user interface 1030, and a bus interface, wherein:
the processor 1000, which is used to read the program in the memory 1020, executes the following processes:
when data transmission processing is carried out, a protocol layer of a user terminal is controlled to execute segmentation operation on data so as to obtain segmented data;
controlling another protocol layer of the user terminal to generate the acquired segmented data into a PDU based on scheduling information.
Among other things, a transceiver 1010 for receiving and transmitting data under the control of the processor 1000.
In fig. 10, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 1000 and memory represented by memory 1020. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1010 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The user interface 1030 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 may store data used by the processor 1000 in performing operations.
Optionally, another protocol layer of the ue generates the obtained segmented data into a PDU based on the scheduling information, including:
for the initial transmission data, another protocol layer of the user terminal directly generates the acquired segmented data into PDU based on scheduling information; or
For retransmission data, another protocol layer of the user terminal generates the acquired segmented data into a PDU based on scheduling information and does not allow re-segmentation of the data.
Optionally, a protocol layer of the ue performs a segmentation operation on the data to obtain segmented data, including:
and the protocol layer of the user terminal performs segmentation operation on the data according to the preset segment length so as to acquire the segment data.
Optionally, a protocol layer of the ue performs a segmentation operation on the data to obtain segmented data, including:
and a protocol layer of the user terminal performs segmentation operation on the data according to the dynamically determined segment length so as to acquire the segment data.
Optionally, the dynamically determined segment length comprises a network device signaled segment length; or
The dynamically determined segment length comprises a dynamically determined segment length for the user terminal, and the processor 1000 is also for:
sending the length information of the segment length to a network device through a transceiver 1010, so that a protocol layer of the network device executing uplink scheduling allocates initial transmission resources and/or retransmission resources matched with the segment length according to the length information.
Optionally, the segment length is dynamically determined based on one or more of the following information:
segment length indication information desired by the network device;
segment length indication information desired by the user terminal;
uplink channel quality information of the user terminal;
data transmission condition of the user terminal;
and the characteristics of the uplink service corresponding to the user terminal.
Optionally, the data includes uplink SDUs, and the segmenting operation includes:
a segmentation operation according to a segment length.
Optionally, another protocol layer of the ue generates the obtained segmented data into a PDU based on the scheduling information, including:
the other protocol layer of the user terminal generates a PDU by the segments meeting the segment length in the obtained segment data based on the scheduling information, and when a residual segment which does not meet the segment length exists in an SDU, the residual segment of the SDU is concatenated with the continuous SDU thereof to generate the PDU meeting the segment length, and padding is allowed for the last PDU; or
The other protocol layer of the user terminal generates a PDU separately from the segments meeting the segment length in the acquired segment data based on the scheduling information, and when a remaining segment which does not meet the segment length exists in an SDU, adds padding to the remaining segment to meet the segment length, and generates the PDU; or
Another protocol layer of the user terminal separately generates a PDU from the segments meeting the segment length in the obtained segment data based on scheduling information, and when a remaining segment of an SDU does not meet the segment length, separately generates a PDU for the remaining segment; or
The other protocol layer of the user terminal generates a PDU by the segments meeting the segment length in the obtained segment data based on scheduling information, and when a residual segment which does not meet the segment length exists in an SDU and the length of the residual segment is less than the head overhead of a PDU, the residual segment and the previous segment data are combined to generate a PDU; or
The other protocol layer of the user terminal generates a PDU by the segments meeting the segment length in the obtained segment data based on scheduling information, and when a residual segment which does not meet the segment length exists in an SDU and the length of the residual segment is equal to the head overhead of a PDU, the residual segment and the previous segment data are combined to generate a PDU; or
And the other protocol layer of the user terminal generates one PDU (protocol data Unit) by using the segments meeting the segment length in the acquired segment data based on scheduling information, and generates the PDU for the rest segments when the rest segments meeting the segment length exist in one SDU and the length of the rest segments is equal to the head overhead of one PDU.
Optionally, the header of the PDU includes all or part of the following information:
the method comprises the following steps of indicating a domain of a sequence number SN corresponding to a data part, an offset and a length of data corresponding to a first SN in an SDU corresponding to the SN, and indicating information of data lengths corresponding to other SNs except the first SN, wherein the indicating information is used for indicating whether the SN is followed by the data or the next SN; or
The header of the PDU includes all or part of the following information:
and indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of the next SN.
It should be noted that the user terminal in this embodiment may be the user terminal in the embodiment shown in fig. 1 to 5, and any implementation of the user terminal in the embodiment shown in fig. 1 to 5 may be implemented by the user terminal in this embodiment, and the same beneficial effects are achieved, which is not described herein again.
Referring to fig. 11, a structure of a network device is shown, the network device including: a processor 1100, a transceiver 1110, a memory 1120, a user interface 1130, and a bus interface, wherein:
the processor 1100, which reads the program in the memory 1120, performs the following processes:
when data transmission processing is carried out, a protocol layer of the network equipment is controlled to execute segmentation operation on data so as to obtain segmented data;
controlling another protocol layer of the network device to generate the acquired segmented data into a PDU based on scheduling information.
Among other things, the transceiver 1110 is used for receiving and transmitting data under the control of the processor 1100.
In FIG. 11, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1100, and various circuits of memory, represented by memory 1120, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1110 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 1130 may also be an interface capable of interfacing with a desired device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 may store data used by the processor 1100 in performing operations.
Optionally, another protocol layer of the network device generates the obtained segmented data into a PDU based on the scheduling information, where the PDU includes:
for the initial transmission data, another protocol layer of the network equipment directly generates the acquired segmented data into PDU based on scheduling information; or
For retransmission data, another protocol layer of the network device generates the obtained segmented data into a PDU based on scheduling information and does not allow re-segmentation of the data.
Optionally, a protocol layer of the network device performs a segmentation operation on the data to obtain segmented data, including:
and a protocol layer of the network equipment performs segmentation operation on the data according to a preset segment length so as to obtain the segmented data.
Optionally, a protocol layer of the network device performs a segmentation operation on the data to obtain segmented data, including:
a protocol layer of the network device performs a segmentation operation on the data according to the dynamically determined segment length to obtain segmented data.
Optionally, the segment length is dynamically determined based on one or more of the following information:
the network device performs a desired segment length indicated by a protocol layer of a segment;
downlink channel quality information of the user terminal;
characteristics of data corresponding to the user terminal.
Optionally, the processor 1100 is further configured to control a protocol layer of the network device performing segmentation to send length information of the segment length to a protocol layer of the network device performing scheduling, so that the protocol layer of the network device performing scheduling allocates, according to the length information, an initial transmission resource and/or a retransmission resource that matches the segment length.
Optionally, the data includes an SDU, and the segmenting operation includes:
a segmentation operation according to a segment length.
Optionally, another protocol layer of the network device generates the obtained segmented data into a PDU based on the scheduling information, where the PDU includes:
another protocol layer of the network device separately generates a PDU from the segments meeting the segment length in the obtained segment data based on the scheduling information, and concatenates the remaining segments of the SDU with its consecutive SDUs to generate a PDU meeting the segment length when there are remaining segments that do not meet the segment length in an SDU, and padding is allowed for the last PDU; or
Another protocol layer of the network device separately generates a PDU from segments of the acquired segment data that satisfy the segment length based on scheduling information, and when a remaining segment of an SDU that does not satisfy the segment length exists, adds padding to the remaining segment to satisfy the segment length, and generates a PDU; or
Another protocol layer of the network device separately generates a PDU from the obtained segment data meeting the segment length based on scheduling information, and when a remaining segment of an SDU does not meet the segment length, separately generates PDUs for the remaining segment; or
Another protocol layer of the network device separately generates a PDU from the segments meeting the segment length in the obtained segment data based on scheduling information, and when a remaining segment which does not meet the segment length exists in an SDU and the length of the remaining segment is smaller than the head overhead of a PDU, combines the remaining segment with the previous segment data to generate a PDU; or
Another protocol layer of the network device separately generates one PDU from the segments meeting the segment length in the obtained segment data based on scheduling information, and when a remaining segment which does not meet the segment length exists in one SDU and the length of the remaining segment is equal to the head overhead of one PDU, combines the remaining segment with the previous segment data to generate one PDU; or
Another protocol layer of the network device separately generates one PDU for segments of the acquired segment data that satisfy the segment length based on scheduling information, and separately generates a PDU for a remaining segment when there is a remaining segment of an SDU that does not satisfy the segment length and the length of the remaining segment is equal to a header overhead of one PDU.
Optionally, the header of the PDU includes all or part of the following information:
the method comprises the following steps of indicating information of SN corresponding to a data part, offset and length of data corresponding to a first SN in SDU corresponding to the SN, and data length corresponding to other SNs except the first SN, wherein the indicating information is used for indicating whether the SN is followed by the data or the next SN; or
The header of the PDU includes all or part of the following information:
the data part comprises an indication field of a sequence number SN corresponding to the data part and indication information, wherein the indication information is used for indicating whether the SN is followed by data or information of a next SN.
It should be noted that the network device in this embodiment may be the network device in the embodiment shown in fig. 1 to 5, and any implementation of the network device in the embodiment shown in fig. 1 to 5 may be implemented by the network device in this embodiment to achieve the same beneficial effects, which is not described herein again.
Referring to fig. 12, there is shown a structure of a data transmission processing system, which includes:
the ue 121, configured to perform a segmentation operation on data by a protocol layer of the ue 121 to obtain segmented data when performing data transmission processing;
another protocol layer of the ue 121 generates PDU from the acquired segmented data based on scheduling information;
the network device 122 is configured to, when performing data transmission processing, perform a segmentation operation on data by a protocol layer of the network device 122 to obtain segmented data;
another protocol layer of the network device 122 generates the acquired segmented data into PDUs based on scheduling information.
In this embodiment, the network device 122 and the terminal 121 may be the network device and the terminal introduced in the embodiments shown in fig. 1 to 11, and the embodiments thereof may refer to the embodiments shown in fig. 1 to 11, and the same technical effect may also be achieved, which is not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the transceiving method according to various embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.