JP7119052B2 - Method and device for generating protocol data unit (PDU) packets - Google Patents

Description

TECHNICAL FIELD The present disclosure relates to the field of communication technology, and in particular to methods and devices for generating protocol data unit (PDU) packets. By way of cross-reference to related applications, this application is a continuation of International Application No. PCT/CN2016/104679, filed November 4, 2016, the entire contents of which are incorporated herein by reference.

The Radio Link Control (RLC) layer in Long Term Evolution (LTE) is located between the Packet Data Convergence Protocol (PDCP) layer and the Medium Access Control (MAC) layer. Data packets exchanged between the RLC layer and the PDCP layer are called Service Data Unit (SDU) packets, and data packets exchanged between the RLC layer and the MAC layer are protocol - Referred to as a data unit (PDU) packet.

In actual implementation, the MAC layer can specify the size of the PDU packet, and generally the size of the SDU packet received by the RLC layer is not equal to the size of the PDU packet specified by the MAC layer. . Thus, the RLC layer can process received SDU packets, eg, the SDU packets can be segmented, cascaded, and so on. After processing the SDU packets, the RLC layer can generate PDU packets of the specified size. A PDU packet includes a packet header and a data section, and the packet header includes a data/control (D/C) field, a resegmentation flag (RF) field, a polling bit (P) field, a framing indication (FI ) field, Length Indication (LI) field, Extension Bits (E) field, Sequence Number (SN) field, Last Segment Flag (LSF) field, Segmentation Offset (SO) field, and so on.

In related technical fields, the packet header of a PDU packet occupies a relatively large length, ie the overhead spent by the header is relatively large.

SUMMARY To solve problems in related art, the present disclosure provides a method and device for generating protocol data unit (PDU) packets. Technical solutions are as follows.

According to a first aspect of the present disclosure, a method is provided for generating Protocol Data Unit Packets (PDUs). The method comprises the steps of obtaining a Service Data Unit (SDU) packet, processing the SDU packet according to a preset data packet size, and generating a packet header and data section of the PDU packet according to the processing result. wherein the packet header and the data section constitute a PDU packet, the packet header omitting the framing indication (FI) field and the re-segmentation flag (RF) field, but including preset fields. , if the preset fields include other fields except the FI and RF fields redefined in the common packet header, or newly added target fields, and the field length of the newly added target fields is less than the combined length of the FI and RF fields.

Optionally, the preset field includes other fields, the other fields including a sequence number (SN) field, a last segment flag (LSF) field, and a segmentation offset (SO) field.

If the SDU packets are cascaded, the step of generating the packet header of the PDU packet according to the processing result includes obtaining the SN number to which the first SDU packet of the data section corresponds; obtaining a first indication information used to indicate whether the last byte is the last byte of the last SDU; and the starting byte position of the first byte of the corresponding data section in the SDU packet. and generating a packet header including an SN field, an LSF field, and an SO field, wherein the SN field includes the obtained SN number and the LSF field is the obtained first containing display information, the SO field containing the starting byte position obtained.

Optionally, the preset field includes a newly appended target field, and generating a packet header of the PDU packet according to the processing result is obtaining second display information, wherein the SDU packet is cascaded, the second indication information is used to indicate whether the first SDU in the data section is an SDU segment, and if the SDU packet was not cascaded, the second indication information is used to indicate whether the data section is an SDU segment; and generating a packet header including a target field, the target field being the second including the display information of the step;

Optionally, the step of generating a packet header including a target field includes a common packet header including the target field, if the second indication information is used to indicate that it is not an SDU segment. generating a packet header that omits the SO and LSF fields in .

Optionally, the step of generating a packet header including a target field comprises a previously obtained radio resource control (RRC) configuration message for configuring the packet header to include the target field. If used, generating a packet header containing the target field.

Optionally, the step of generating a packet header for the PDU packet according to the processing result further obtains third indication information used to indicate whether the preset data packet is a small data packet A step wherein the preset data packet is a complete SDU packet to which the first SDU in the data section corresponds if the SDUs are cascaded, and if the SDUs are not cascaded , the preset data packet is a complete SDU packet to which the SDU in the data section corresponds; and third display information to indicate that the preset data packet is a small data packet. is used, generating a packet header including the third indication information and a target SO field, wherein the length of the target SO field is less than the length of the SO field in the common packet header , and steps.

Optionally, generating a packet header including the third indication information and the target SO field configures the packet header such that the previously obtained RRC configuration message includes the third indication information. generating a packet header including the third indication information and the target SO field.

Optionally, generating a packet header for the PDU packet according to the processing result further comprises generating a packet header including an SO field with a target length according to a previously obtained RRC configuration message. wherein the RRC configuration message contains a target length that is less than the length of the SO field in the common packet header.

Optionally, if a cascade function is not included, the method further comprises obtaining an RRC configuration message sent by the receiving end, wherein the RRC configuration message specifies the SDU packet for segmenting the SDU packet. used to disable the segmentation function; and disabling the segmentation function for segmenting the SDU packet after receiving the RRC configuration message.

According to a second aspect of the present disclosure, a device is provided for generating Protocol Data Unit Packets (PDUs). The device includes a first acquisition module configured to acquire service data unit (SDU) packets and a processing module configured to process the SDU packets according to a preset data packet size. and a generation module configured to generate a packet header and data section of a PDU packet according to a processing result of the processing module, wherein the packet header and data section constitute the PDU packet, and the packet header omits the Framing Indication (FI) field and the Re-Segmentation Flag (RF) field, but includes preset fields, excluding the FI and RF fields where the preset fields are redefined in the common packet header or a newly added target field, wherein the field length of the newly added target field is less than the total length of the FI field and the RF field.

Optionally, the preset fields include other fields, the other fields including a sequence number (SN) field, a last segment flag (LSF) field, and a segmentation offset (SO) field, wherein the SDU packet is If cascaded, the generating module further obtains the corresponding SN number of the first SDU packet of the data section, whether the last byte of the data section is the last byte of the last SDU , obtain the starting byte position of the first byte of the corresponding data section in the SDU packet, and obtain the starting byte position of the first byte of the corresponding data section in the SDU packet; configured to generate a header, the SN field containing the obtained SN number, the LSF field containing the obtained first indication information, and the SO field containing the obtained starting byte position; .

Optionally, the preset field includes a newly appended target field, the generating module further obtains a second indication information, and if the SDU packets are cascaded, the second indication information is used to indicate whether the first SDU in the data section is an SDU segment, and if the SDU packets were not cascaded, the second indication information indicates whether the data section is an SDU segment. and is configured to generate a packet header including a target field, the target field including the second indication information.

Optionally, the generating module further includes the target field but omits the SO and LSF fields in the common packet header if the second indication information is used to indicate that it is not an SDU segment configured to generate packet headers;

Optionally, the generating module further comprises a target field if a radio resource control (RRC) configuration message obtained so far is used to configure the packet header to include the target field. It is configured to generate a packet header containing fields.

Optionally, the generating module further obtains third indication information used to indicate whether the preset data packet is a small data packet, and if SDUs are cascaded: If the preset data packet is a complete SDU packet to which the first SDU in the data section corresponds and the SDUs were not cascaded, then the preset data packet corresponds to the SDU in the data section. If the third indication information is used to indicate that the preset data packet is a small data packet, the third indication information and the target SO field are The length of the target SO field is less than the length of the SO field in the common packet header.

Optionally, the generating module further comprises the third indication information if the RRC configuration message obtained so far is used to configure the packet header to include the third indication information. and a target SO field.

Optionally, the generation module is further configured to generate a packet header including an SO field with a target length according to a previously obtained RRC configuration message, the RRC configuration message being a common packet - Contains a target length that is less than the length of the SO field in the header.

Optionally, if the cascade function is not included, the device further obtains the RRC configuration message sent by the receiving end before the generating module generates packet headers of PDU packets according to the processing results. a second acquisition module, wherein the RRC configuration message is used to disable the segment function for segmenting the SDU packet; and after receiving the RRC configuration message, the SDU a disabling module configured to disable a segmentation function for segmenting packets.

According to a third aspect of the present disclosure, a device is provided for generating Protocol Data Unit Packets (PDUs). The device includes a processor and a memory for storing processor-executable instructions, the processor obtaining service data unit (SDU) packets; and generating a packet header and data section of a PDU packet according to the processing result, wherein the packet header and data section constitute a PDU packet, and the packet header is a framing indication (FI) fields and re-segmentation flag (RF) fields are omitted, but contain preset fields, which are redefined in the common packet header Other fields except the FI and RF fields, or newly added and the field length of the newly added target field is smaller than the total length of the FI field and the RF field.

Technical solutions provided by the present disclosure may include the following advantages.
A PDU packet is generated containing a packet header and a data section, the packet header omitting the FI and RF fields but containing preset fields, which are already present in the common packet header. other fields except the existing FI and RF fields, or a target field that is newly added and has a length less than the combined length of the FI and RF fields. In this method, it is possible to solve the problem that the overhead occupied by the packet header of the PDU packet generated in the related technical field is large, and directly omit the FI field and the RF field, or field and RF field while adding a target field with a shorter length, thereby reducing the length of the packet header and saving packet header overhead. It is possible to achieve

It is to be understood that both the foregoing general description and the following detailed description are exemplary only and are not restrictive of the present disclosure.

The drawings herein, which are incorporated in and constitute a part of this disclosure, illustrate embodiments consistent with the disclosure and, together with the description, explain the principles of the disclosure. is doing.
1 is a schematic diagram of an implementation environment according to various embodiments of the present disclosure; FIG.

4 is a method flowchart of a method for generating PDU packets shown in accordance with one exemplary embodiment of the present disclosure;

4 is a method flowchart of a method for generating PDU packets shown in accordance with another exemplary embodiment of the present disclosure;

FIG. 4B is a schematic diagram of processing SDU packets shown in accordance with another exemplary embodiment of the present disclosure;

FIG. 4B is a schematic diagram of the structure of a PDU packet shown in accordance with another exemplary embodiment of the present disclosure;

4 is a method flow chart of a method for generating PDU packets shown in accordance with a further exemplary embodiment of the present disclosure;

4 is a schematic diagram of the structure of a PDU packet shown in accordance with a further exemplary embodiment of the present disclosure; FIG.

4 is a schematic diagram of the structure of a PDU packet shown in accordance with one exemplary embodiment of the present disclosure; FIG.

FIG. 4 is a schematic diagram of obtaining PDU packets after processing SDU packets shown in accordance with one exemplary embodiment of the present disclosure;

FIG. 4 is a schematic diagram of the structure of a device for generating PDU packets shown in accordance with one exemplary embodiment of the present disclosure;

FIG. 4 is a schematic diagram of the structure of a device for generating PDU packets shown in accordance with another exemplary embodiment of the present disclosure;

FIG. 4 is a schematic diagram of the structure of a device for generating PDU packets shown in accordance with one exemplary embodiment of the present disclosure;

Exemplary embodiments are described in detail below. Embodiments thereof are shown in the drawings. In the following description, when referring to the drawings, the same numbers in different drawings identify the same or similar elements unless otherwise indicated. The embodiments described in the exemplary embodiments that follow do not represent all embodiments consistent with the present disclosure. Rather, they are merely examples of devices and methods consistent with some aspects of this disclosure recited in the appended claims.

For ease of understanding, an implementation environment according to various embodiments of the present disclosure is first briefly introduced here.

In LTE, when the sender sends data to the receiver, the RLC layer (see Figure 1) at the sender can receive SDU packets from the PDCP layer. Since the RLC layer interacts with the MAC layer through PDU packets, and the size of a received SDU packet is generally different than the size of a PDU packet specified by the MAC layer, the RLC layer can divide received SDU packets into, e.g., It needs to be processed by segmenting, cascading, etc., then generating PDU packets according to the processing results, and transmitting the generated PDU packets to the receiving end. A PDU packet includes a packet header and a data section. After receiving a PDU packet, the RLC layer at the receiving end decapsulates the SDU according to the packet header of the PDU packet and forwards the SDU to the upper layers.

A transmitting end can be a user equipment (UE) or a base station, and correspondingly a receiving end can also be a base station or a UE, which is not limited herein.

The functions of the RLC layer are performed by an RLC entity, which can be configured as one of the following three modes.

The first mode is transparent mode (TM), which can be considered as empty RLC. This is because this mode only provides data transparent transmission capability.

The second mode is unacknowledged mode (UM), which provides all RLC functionality except retransmission and resegmentation.

The third mode is Acknowledged Mode (AM), which provides full RLC functionality with error detection and retransmission.

Unless otherwise specified, the methods for generating PDU packets provided by various embodiments of the present disclosure are used under UM and AM.

Referring to FIG. 2, which is a method flowchart of a method for generating PDU packets shown in accordance with one exemplary embodiment of the present disclosure, the method for generating PDU packets shown in FIG. , which may include the following steps.

At step 210, an SDU packet is obtained.

At step 220, the SDU packets are processed according to the preset data packet size.

At step 230, a packet header and data section of the PDU packet are generated based on the processing result, and the packet header and data section constitute the PDU packet.

The packet header omits the FI and RF fields, but includes preset fields, which are other fields except the FI and RF fields redefined in the common packet header, or newly added. The field length of the newly added target field is less than the combined length of the FI and RF fields.

In summary, with respect to the method for generating PDU packets provided by this embodiment, a PDU packet is generated that includes a packet header and a data section, the packet header omitting the FI and RF fields. contains a preset field, which is any field other than the already existing FI and RF fields in the common packet header, or a newly added field whose total length is greater than the total length of the FI and RF fields. A target field with a small length. In this method, it is possible to solve the problem that the overhead occupied by the packet header of the PDU packet generated in the related technical field is large, and directly omit the FI field and the RF field, or omitting the field and the RF field while adding a target field with a shorter length, thereby reducing the length of the packet header and achieving the effect of saving the overhead of the packet header It is possible to

The preset fields include fields other than the redefined FI field and RF field in the common packet header, or newly added target fields, and the field length of the newly added target field is , less than the total length of the FI and RF fields.

Therefore, the above two cases are separately described in separate embodiments below.

Referring to FIG. 3A, which is a method flowchart of a method for generating a PDU packet, shown in accordance with one exemplary embodiment of the present disclosure, an example in this embodiment assumes that the preset field is Other fields. As shown in FIG. 3A, a method for generating PDU packets can include the following steps.

At step 310, an SDU packet is obtained.

When the transmitting end needs to send data, the RLC entity can receive SDU packets from the PDCP layer.

At step 320, the SDU packets are processed according to the preset data packet size.

The preset data packet size is the PDU packet size specified by the MAC layer.

In practical implementation, the size of the received SDU packets is generally different from the PDU packet size specified by the MAC layer, so the RLC entity generally needs to process the SDU packets. The processing performed on SDU packets includes one or both of segmentation and cascading, which is not limited in this embodiment.

Optionally, the RLC entity can segment the SDU packet if the size of the SDU packet is larger than the size of the data section in the preset data packet. For example, if the SDU packet size is 100 bytes, the preset data packet size is 60 bytes, and the packet header needs to occupy 10 bytes, the RLC entity splits the SDU packet into two It can be segmented into SDU segments, each SDU segment being 50 bytes. For another example, if the SDU packet size is 100 bytes, the preset data packet size is 70 bytes, and the packet header needs to occupy 10 bytes, then the RLC entity will send the SDU It is possible to segment the packet into two SDU segments as 60 bytes and 40 bytes. The RLC entity then further cascades the 40-byte SDU segment with the 20-byte SDU segment of the next SDU packet, configures the 60 bytes in the next SDU packet to be independent, and It is possible to cascade the last 20 bytes of the SDU segment of one SDU packet with the 40 bytes of the next SDU packet, and so on.

If the size of the SDU packet is smaller than the size of the data section in the preset data packet, the RLC entity can segment and cascade the SDU packet. For example, if the SDU packet size is 30 bytes, the preset data packet size is 120 bytes, and the packet header needs to occupy 10 bytes, referring to FIG. 3B, the RLC entity will: , the cascading of three SDU packets and the first 20 bytes of the fourth SDU packet, the last 10 bytes of the fourth SDU packet, the fifth SDU packet and the sixth SDU packet; It is possible to cascade the 7th SDU packet with the first 10 bytes of the 8th SDU packet, and so on.

No processing is required if the size of the SDU packet is equal to the size of the data section in the preset data packet.

At step 330, data sections are generated based on the processing results.

As can be seen from the processing on SDU packets, data sections can be complete SDUs, SDU segments, or a combination thereof. Additionally, if a data section is a combination of complete SDUs and SDU segments, only the first and last data sections can be SDU segments.

At step 340, the SN number to which the first SDU packet of the data section corresponds is obtained.

If the SDUs are cascaded, the RLC entity can obtain the SN number to which the first SDU packet of the data section corresponds.

For example, if the SDU packet size is 100 bytes and the preset packet size is 120 bytes, then the data section consists of the entire contents of the first SDU packet and the first 10 bytes of the second SDU packet. bytes, so the RLC entity can obtain the SN number of the first SDU packet, eg, SN=0.

At step 350, first indication information is obtained and the first indication information is used to indicate whether the last byte of the data section is the last byte of the last SDU.

The RLC entity can detect whether the last byte of the data section is the last byte of the last SDU. If the detection result is "no", first display information for indicating "no" is generated, for example, "0", and if the detection result is "yes", indicating "yes" A first display information for is generated, for example, "1".

For example, if the SDU packet size is still 100 bytes and the preset packet size is 120 bytes, then the last byte of the data section is the 10th byte of the second SDU packet and the SDU The RLC entity can generate a '0' because it is not the last byte of the packet.

At step 360, the starting byte position of the first byte of the corresponding data section in the SDU packet is obtained.

To enable the receiving end to decapsulate the SDU packet after receiving the PDU packet, the RLC entity can obtain the starting byte position of the first byte of the data section in the SDU packet. be.

At step 370, a packet header is generated that includes SN, LSF, and SO fields, the data section and packet header constitute a PDU packet, the SN field includes the obtained SN number, and the LSF The field contains the first display information obtained and the SO field contains the starting byte position obtained.

The packet header omits the FI and RF fields, but in actual implementation other fields in the common packet header, such as D/C field, E field, LI field, P field, padding field, etc. can further include The padding field is used to allow the data header to be integer bytes when the packet header is non-integer bytes. Optionally, if the method for generating PDU packets is used under UM, the packet header does not contain D/C and P fields, which is not limited by this embodiment.

In actual implementation, referring to FIG. 3C, which is a schematic diagram of the structure of a possible packet header, the packet header can contain a fixed header and an extension header. Additionally, with reference to FIG. 3C, fixed headers start at the beginning of the header and end at the SO field, and extended headers start at the E field and end. The SN field of the fixed header is the SN number to which the first SDU of the data section corresponds, the SO field of the fixed header indicates the starting byte position of the first byte of the corresponding data section in the SDU, and the fixed The LSF field of the header indicates whether the last byte of the data section corresponds to the last byte of the last RLC SDU. The R field is a reserved field, which may or may not exist in the actual implementation, which is not limited by this embodiment. If the extension bit "E" is equal to 1, it indicates that there is an extension header after the fixed header, ie E and LI fields. If the E field of the extension header is equal to 1, it indicates that there is another extension header after the extension header, and so on. The LI field of the first extension header is used to indicate the number of bytes of the first SDU/SDU segment contained in the data section, and the LI field of the second extension header is used to indicate the number of bytes of the second , indicating the number of bytes in the SDU of . . . , and the LI field of the last extension header indicates the number of bytes in the SDU before the last (only the first and last RLC SDUs can possibly be segments). The padding field is used to make the header an integer byte if the size of the entire header is a non-integer byte.

One point to note is that if no cascading is performed when processing an SDU, the RLC entity indicates the segment status of the data section by means of the SO and LSF fields, and the RLC entity at this point can generate the packet header shown in FIG. 3D. In actual implementation, the E field is 0 to indicate that the data section is simply an SDU packet or SDU segment. FIG. 3D takes by way of example only the respective fields of the length shown in the figure and arranged in the order shown in the figure. Optionally, the length and order of each field can be designed according to actual requirements, which is not limited in this embodiment.

Another point to note is that if a PDU packet needs to be re-segmented, only the data section of the PDU packet is re-segmented and the segmented packet header is added according to the above rules. , which will not be described again in this embodiment.

In summary, with respect to the method for generating PDU packets provided by this embodiment, a PDU packet is generated that includes a packet header and a data section, the packet header omitting the FI and RF fields. contains a preset field, which is any field other than the already existing FI and RF fields in the common packet header, or a newly added field whose total length is greater than the total length of the FI and RF fields. A target field with a small length. In this method, it is possible to solve the problem that the overhead occupied by the packet header of the PDU packet generated in the related technical field is large, and directly omit the FI field and the RF field, or omitting the field and the RF field while adding a target field with a shorter length, thereby reducing the length of the packet header and achieving the effect of saving the overhead of the packet header It is possible to

Referring to FIG. 4A, which is a method flowchart of a method for generating a PDU packet shown in accordance with another exemplary embodiment of the present disclosure, in this embodiment, the newly appended target field includes Taking the preset fields as an example, a method for generating the PDU packet shown in FIG. 4A may include the following steps.

At step 410, an SDU packet is obtained.

At step 420, the SDU packets are processed according to the preset data packet size.

At step 430, data sections are generated based on the processing results.

Steps 410 to 430 are similar to steps 310 to 330 in the previous embodiment and will not be described again here.

At step 440, second display information is obtained. If SDU packets are cascaded, the second indication information is used to indicate whether the first SDU in the data section is an SDU segment; , the second indication information is used to indicate whether the data section is an SDU segment.

In actual implementation, if the SDUs are cascaded in step 420, the RLC entity detects whether the first SDU of the data section is an SDU segment, and according to the detection result, the second display information can be generated. For example, if the detection result is "yes", a "0" is generated, and if the detection result is "no", a "1" is generated. For example, with reference to FIG. 3B, the first SDU of the data section for the first PDU is a complete SDU, and the RLC entity generates a '1' at this point, while the second PDU, the first SDU in the data section is the SDU segment, and the RLC entity generates '0' at this point.

If the SDU was not cascaded in step 420, the RLC entity detects whether the data section is an SDU segment and generates second indication information according to the detection result.

At step 450, a packet header is generated that includes a target field. The target field contains secondary display information, and the data section and packet header make up the PDU packet.

In actual implementation, the target field may be a segmentation indication (SI) field. That is, the RLC entity may generate a packet header containing the SI field, the SI field containing the second indication information. The target field is generally of 1 bit.

In actual implementation, if the second indication information is used to indicate that it is not an SDU segment, the RLC entity will include the SI field and omit the SO and LSF fields in the common packet header. It is possible to generate a packet header. Reference is made to FIGS. 4B and 4C, which are schematic diagrams of the structures of PDU packets generated when cascading is performed or not performed, respectively.

However, if the second indication information is used to indicate SDU segments, the RLC entity can generate packet headers that include the SI field. Reference is made to FIGS. 4D and 4E, which are schematic diagrams of the structures of PDU packets generated when cascading is performed or not performed, respectively. Additionally, in cases where cascading is performed, the SN, LSF, and SO fields in the packet header generated by the RLC entity can be similar to the previous embodiment, here will not be described again in

The first point to note is that packet headers that omit the FI and RF fields mentioned in this embodiment will not be described again here. Moreover, unless specified otherwise, packet headers may also include other fields in common packet headers, which are also not described here.

A second point to note is that the base station can configure whether the packet header includes a target field via a radio resource control (RRC) configuration message. Therefore, if the packet header is configured to include a target field via the RRC configuration message, then when generating the packet header, the packet header including the target field is generated and the RRC When generating the packet header, a packet header is generated that does not include the target field if the packet header is configured via the configuration message not to include the target field. This embodiment is not so limited.

A third point to note is that if a PDU packet requires re-segmentation, RLC can perform re-segmentation only on the data section of the PDU packet, and the packet header The encapsulation manner of is similar to that described above and will not be described again in this embodiment.

In summary, with respect to the method for generating PDU packets provided by this embodiment, a PDU packet is generated that includes a packet header and a data section, the packet header omitting the FI and RF fields. contains a preset field, which is any field other than the already existing FI and RF fields in the common packet header, or a newly added field whose total length is greater than the total length of the FI and RF fields. A target field with a small length. In this method, it is possible to solve the problem that the overhead occupied by the packet header of the PDU packet generated in the related technical field is large, and directly omit the FI field and the RF field, or field and RF field while adding a target field with a shorter length, thereby reducing the length of the packet header and saving packet header overhead. It is possible to achieve

In each of the above embodiments, if the packet header contains an SO field, the length of the SO field is generally a preset fixed length, such as 2 bytes. However, for some low-rate services, the size of a PDU packet is often only a few bytes, so a 2-byte SO field is quite large for a PDU packet, thereby reducing the specific overhead of the header. waste. At this point, the SO field can be optimized for length. Optionally, a solution for optimizing the length of the SO field can include the following two modes.

In a first possible mode of implementation, generating the packet header may include:

First, the third indication information used to indicate whether the preset data packet is a small data packet is obtained, and if the SDUs are cascaded, the preset data packet is , the first SDU in the data section is the corresponding complete SDU packet, and the SDUs were not cascaded, then the preset data packet is the complete SDU packet to which the SDU in the data section corresponds. be.

Optionally, the RLC entity can detect if the preset data packet size is smaller than the preset size. If the detection result is "yes", third indication information is generated indicating that the preset data packet is a small data packet, for example "1", and if the detection result is "no". In some cases, third indication information, eg, "0", is generated to indicate that the preset data packet is a large data packet. The preset size can be a default size, such as 100 bytes, or a size configured by the base station via an RRC configuration message if this method is used in the UE, which is The embodiments are not limited. If the preset size is the size configured by the base station, the preset size is the size shared by all data radio bearers (DRBs) or the size used independently by one DRB. There can be, which is not limited in this embodiment.

In actual implementation, when SDU packets are cascaded, the preset data packet is the complete SDU data packet to which the first SDU in the data section corresponds. Optionally, the preset data packet is i.e. the first SDU if the first SDU in the data section is a complete SDU and the first SDU in the data section is an SDU segment In that case, the RLC entity obtains the SDU packet to which the SDU segment belongs and provides the obtained SDU package as a preset data packet.

However, if the SDU packets were not cascaded, the preset data packet is the complete SDU packet to which the SDU in the data section corresponds. Optionally, the preset data packet is i.e. SDU if the content in the data section is a complete SDU, and if the content in the data section is one SDU segment e.g. If the packet is encapsulated in two PDU packets, the RLC entity obtains the SDU packet to which the SDU segment belongs and provides the obtained SDU package as a preset data packet.

Generally, the third indication information is of 1 bit.

Second, when generating the packet header, if the third indication information is used to indicate that the preset data packet is a small data packet, the third indication information and a target SO field, the length of the target SO field being less than the length of the SO field in the common packet header. For example, the length of the target SO field can be 7 bits.

Optionally, the RLC entity can generate a packet header containing a small data (SD) field and a target SO field. The SD field contains third display information.

Optionally, when generating the packet header, if the third indication information is used to indicate that the preset data packet is a large data packet, the SD and SO fields and the length of the SO field is the preset length. This length can be less than the length of the SO field in the common packet header, or it can be equal to the length of the SO field in the common packet header, which in this embodiment is limited to not.

Additionally, in actual implementation, the length of the target SO field and the preset length can be the default length or the length configured by the base station via the RRC configuration message. , which is not limited in this embodiment.

In addition, the base station can configure whether the packet header includes the SD field via the RRC configuration message, and when generating the packet header, the base station can configure via the RRC configuration message. It is possible to generate a packet header containing an SD field only if the existing packet header contains an SD field, which is not limited in this embodiment.

If a small data packet is detected, the overhead occupied by the SO field can be saved by using a target SO field with a length smaller than the length of the SO field in the common packet header. , thereby achieving the effect of further saving the overhead occupied by the packet header.

In a second possible mode of implementation, the step of generating the packet header may include the following.

A packet header containing an SO field with a target length is generated according to the RRC configuration message obtained so far. The RRC configuration message contains a target length, which is less than the length of the SO field in the common packet header.

If the base station performs DRB configuration to the UE via an RRC configuration message, the RRC configuration message contains the target length, such as 7 bits. Of course, in actual implementation, the target length included in the RRC configuration message can be other lengths, which is not limited in this embodiment.

Then, when generating the packet header, the packet header including the SO field with the target length can be generated according to the target length configured in the RRC configuration message.

By configuring a preset length that is smaller than the length of the SO field in the common packet header, the base station allows the RLC entity to generate the SO field with the preset length when generating the packet header. , thereby reducing the overhead occupied by the packet header.

Additionally, if the RLC entity does not have cascading capabilities, the RLC entity may disable the ability to segment small data packets in this embodiment. This is because a certain amount of processing resources are required to segment small data. In actual implementation, it can include the following contents.

First, the RRC configuration message sent by the receiving end is obtained, and the RRC configuration message is used to disable the segmentation function for segmenting the SDU packets.

The base station sends an RRC configuration message to configure the UE DRB and disables the RLC segment function in the DRB's RLC configuration. In actual implementation, the configuration can be performed separately or uniformly for uplink and downlink, and it can be performed under both UM and DM. . Of course, the RRC configuration message can also be configured not to disable segment functionality, which is not limited herein.

Second, the segmentation function for segmenting SDU packets is disabled.

After receiving the RRC configuration message, if the RRC configuration message indicates to disable the segmentation function for the uplink, the RLC entity segments the received SDU packets when transmitting data. 5A, data can be sent using a non-segmented PDU packet format. However, if the RRC configuration message indicates to disable the segment function for the downlink, the RLC entity shall, after receiving the PDU packet sent by the opposite end, wait until the PDU packet is , is an unsegmented SDU packet.

For small data services, the base station may configure the RLC entity to disable segment functionality, which is required by the RLC entity to process small data packets. It reduces the complexity of operations involved and improves the data transmission efficiency of the RLC entity.

In the above embodiments, the SN numbers in the generated PDU packets may not be consecutive after the RLC entity processes the SDU packets. For example, referring to FIG. 5B, the RLC entity receives five SDU packets with SNs of 0, 1, 2, 3, and 4, respectively, then the RLC entity receives the first SDU packet of SN=0. 1 segment into the first PDU packet, the second segment of the SDU packet with SN=0, the SDU packet of SN=1, and the first segment of the SDU packet with SN=2 into the second PDU packet; Encapsulate the second segment of the SN=2 SDU packet and the SN=3 and SN=4 SDU packets into a third PDU packet. Please further refer to FIG. 5B. Apparently, the SN numbers of the three PDU packets obtained by the RLC entity are 0, 0 and 2 in order, which are not consecutive. At this point, in order to check whether each of the captured PDU packets contains repeated content, the RLC entity checks the sequence of SN numbers according to the SN and SO fields in each of the captured PDU packets. It is possible to detect whether or not For example, taking the first PDU packet and the second PDU packet as an example related to FIG. 5B, the RLC entity determines whether the last byte of the first PDU packet is the (LSF-1)th byte That is, it is possible to detect whether it is the 221st byte of the second PDU packet. If the detection result is 'yes', the RLC entity can determine that the SDU packet with SN=0 has no problem in repeating encapsulation. Then, to check whether SDU packet loss occurs in each of the obtained PDU packets, the RLC entity can detect whether n+m is equal to N, where: n is the SN number of the SDU packet corresponding to the last byte contained in the PDU packet where the interrupt starts, m is the SN number of the PDU packet where the interrupt starts, and N is the end of the interrupt. It is the SN number of the PDU packet. If the detection result is "yes", it is determined that no packet loss has occurred, and if the detection result is "no", it is determined that packet loss has occurred. be done. For example, with respect to FIG. 5B, the SN number of the second PDU packet is 0 and the SN number of the third PDU packet is 2. These two are not contiguous, so at this point the RLC entity knows the SN number of the SDU packet to which the last byte of the second PDU packet corresponds (i.e. 2) and the It is possible to calculate the sum (2) with the SN number (i.e. 0) of the , the detection result of the RLC entity is YES, so the RLC entity can determine that no packet loss has occurred.

FIG. 6 is a schematic diagram of the structure of a device for generating PDU packets shown in accordance with one exemplary embodiment of the present disclosure; As shown in FIG. 6, a device for generating PDU packets can include a first acquisition module 610, a processing module 620, and a generation module 630. As shown in FIG.

the first acquisition module 610 is configured to acquire service data unit (SDU) packets;
the processing module 620 is configured to process the SDU packets according to the preset data packet size;
The generating module 630 is configured to generate a packet header and data section of the PDU packet according to the processing result of the processing module 620, the packet header and data section forming the PDU packet, and the packet header , omitting the framing indication (FI) field and the re-segmentation flag (RF) field, but including the preset fields, excluding the FI and RF fields where the preset fields are redefined in the common packet header. field, or a newly appended target field, wherein the field length of the newly appended target field is less than the total length of the FI field and the RF field.

In summary, for the device for generating PDU packets provided by this embodiment, a PDU packet is generated that includes a packet header and a data section, the packet header omitting the FI and RF fields. contains a preset field, which is any field other than the already existing FI and RF fields in the common packet header, or a newly added field whose total length is greater than the total length of the FI and RF fields. A target field with a small length. In this method, it is possible to solve the problem that the overhead occupied by the packet header of the PDU packet generated in the related technical field is large, and directly omit the FI field and the RF field, or field and RF field while adding a target field with a shorter length, thereby reducing the length of the packet header and saving packet header overhead. It is possible to achieve

FIG. 7 is a schematic diagram of the structure of a device for generating PDU packets shown in accordance with one exemplary embodiment of the present disclosure; As shown in FIG. 7, a device for generating PDU packets can include a first acquisition module 710, a processing module 720, and a generation module 730. As shown in FIG.

the first acquisition module 710 is configured to acquire service data unit (SDU) packets;
the processing module 720 is configured to process the SDU packets according to the preset data packet size;
The generating module 730 is configured to generate a packet header and data section of the PDU packet according to the processing result of the processing module 720, the packet header and data section forming the PDU packet, and the packet header , omitting the framing indication (FI) field and the re-segmentation flag (RF) field, but including the preset fields, excluding the FI and RF fields where the preset fields are redefined in the common packet header. field, or a newly appended target field, wherein the field length of the newly appended target field is less than the total length of the FI field and the RF field.

Optionally, the preset field includes other fields, the other fields including a sequence number (SN) field, a last segment flag (LSF) field, and a segmentation offset (SO) field.

If the SDU packets were cascaded, generation module 730 further:
obtaining the SN number to which the first SDU packet of the data section corresponds;
Obtain first indication information used to indicate whether the last byte of the data section is the last byte of the last SDU;
obtain the starting byte position of the first byte of the corresponding data section in the SDU packet;
configured to generate a packet header including an SN field, an LSF field and an SO field, the SN field including the obtained SN number and the LSF field including the obtained first indication information , the SO field contains the starting byte position obtained.

Optionally, the preset fields contain newly added target fields.

The generation module 730 further:
If the second indication information is obtained and the SDU packets are cascaded, the second indication information is used to indicate whether the first SDU in the data section is an SDU segment and the SDU if the packet was not cascaded, the second indication information is used to indicate whether the data section is an SDU segment;
It is configured to generate a packet header including a target field, the target field including second display information.

Optionally, generation module 730 further:
configured to generate a packet header that includes the target field but omits the SO and LSF fields in the common packet header if the second indication information is used to indicate that it is not an SDU segment; It is

Optionally, generation module 730 further:
Generate a packet header containing the target field, if the radio resource control (RRC) configuration message obtained so far is used to configure the packet header to contain the target field. is configured as

Optionally, generation module 730 further:
Obtaining third indication information used to indicate whether the preset data packet is a small data packet, and if the SDUs are cascaded, the preset data packet is a data packet; if the first SDU in the section is the corresponding complete SDU packet and the SDUs were not cascaded, the preset data packet is the complete SDU packet to which the SDU in the data section corresponds;
to generate a packet header including the third indication information and the target SO field, if the third indication information is used to indicate that the preset data packet is a small data packet; and the length of the target SO field is less than the length of the SO field in the common packet header.

Optionally, generation module 730 further:
A packet header containing the tertiary indication information and the target SO field, if the RRC configuration message obtained so far is used to configure the packet header to include the tertiary indication information is configured to generate

Optionally, generation module 730 further generates a packet header including an SO field with a target length according to the RRC configuration message obtained so far, wherein the RRC configuration message includes the SO field in the common packet header. is configured to include a target length that is less than the length of

Optionally, the device further
Obtain the RRC configuration message sent by the receiving end before the generation module 730 generates the packet header of the PDU packet according to the processing result, and the RRC configuration message disables the segment function for segmenting the SDU packet. a second acquisition module 740 configured to be used to
and a disabling module 750 configured to disable the segmentation function for segmenting the SDU packets after receiving the RRC configuration message.

In summary, for the device for generating PDU packets provided by this embodiment, a PDU packet is generated that includes a packet header and a data section, the packet header omitting the FI and RF fields. contains a preset field, which is any field other than the already existing FI and RF fields in the common packet header, or a newly added field whose total length is greater than the total length of the FI and RF fields. A target field with a small length. In this method, it is possible to solve the problem that the overhead occupied by the packet header of the PDU packet generated in the related technical field is large, and directly omit the FI field and the RF field, or field and RF field while adding a target field with a shorter length, thereby reducing the length of the packet header and saving packet header overhead. It is possible to achieve

A device is provided for generating PDU packets according to one exemplary embodiment of the present disclosure, and a method for generating PDU packets provided by the present disclosure may be performed by the device. It is possible. A device for generating PDU packets includes a processor and memory for storing processor-executable instructions;
The processor
obtain a service data unit (SDU) packet;

processing the SDU packets according to the preset data packet size;
configured to generate a packet header and data section of a PDU packet according to a processing result, the packet header and data section constituting the PDU packet, the packet header including a framing indication (FI) field and a Omit the Segmentation Flag (RF) field, but include a preset field, which is redefined in the common packet header Other fields except the FI and RF fields, or a newly added target • The field length of the newly appended target field, including fields, is less than the total length of the FI and RF fields.

FIG. 8 is a schematic diagram of the structure of a device for generating PDU packets shown in accordance with one exemplary embodiment of the present disclosure; Device 800 may be implemented as all or part of a UE.

Referring to FIG. 8, device 800 includes processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and communication One or more of the components named component 816 may be included.

Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. Processing component 802 can include one or more processors 818 for executing instructions to perform all or some of the steps in the methods described above. Moreover, processing component 802 can include one or more modules that facilitate interaction between processing component 802 and other components. For example, processing component 802 can include multimedia modules to facilitate interaction between multimedia component 808 and processing component 802 .

Memory 804 is configured to store various types of data to support the operation of device 800 . Examples of such data include instructions for any application or method operated on device 800, contact data, phonebook data, messages, images, videos, and the like. Memory 804 can be static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only It can be implemented using any type of volatile or non-volatile memory device, such as memory (ROM), magnetic memory, flash memory, magnetic or optical disk, or combinations thereof.

Power component 806 provides power to the various components of device 800 . Power components 806 may include a power management system, one or more power supplies, and any other components associated with power generation, management, and distribution in device 800 .

Multimedia component 808 includes a screen that provides an output interface between device 800 and a user. In some embodiments, the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen for receiving input signals from the user. A touch panel includes one or more touch sensors for sensing touches, swipes, and gestures on the touch panel. A touch sensor not only senses the boundaries of a touch or swipe action, but can also sense the duration and pressure associated with the touch or swipe action. In some embodiments, multimedia component 808 includes a front camera and/or a rear camera. The front and rear cameras are capable of receiving external multimedia data while device 800 is in an operation mode such as photography mode or video mode. Each of the front and rear cameras can be fixed optical lens systems or have focus and optical zoom capabilities.

Audio component 810 is configured to output and/or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals while device 800 is in operating modes such as call mode, recording mode, and speech recognition mode. The received audio signal can also be stored within memory 804 or transmitted via communication component 816 . In some embodiments, audio component 810 further includes speakers for outputting audio signals.

I/O interface 812 provides an interface between processing component 802 and peripheral interface modules such as keyboards, click wheels, buttons, and the like. Buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.

Sensor component 814 includes one or more sensors for providing status assessments of various aspects of device 800 . For example, the sensor component 814 can detect the on/off status of the device 800, the relative placement of components of the device 800 with each other, e.g. 814 can also detect changes in the position of device 800 or components of device 800 , user contact with device 800 , orientation or acceleration/deceleration of device 800 , and changes in temperature of device 800 . Sensor component 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor components 814 may also include optical sensors such as CMOS or CCD image sensors used for imaging applications. In some embodiments, sensor component 814 may also include an accelerometer sensor, gyroscope sensor, magnetic sensor, pressure sensor, or temperature sensor.

Communication component 816 is configured to facilitate wired or wireless communication between apparatus 800 and other devices. Device 800 is capable of accessing wireless networks based on communication standards such as WiFi, 2G, or 3G, or combinations thereof. In an exemplary embodiment, communication component 816 receives broadcast signals or broadcast-related information over broadcast channels from external broadcast management systems. In an exemplary embodiment, communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communication.

In an exemplary embodiment, apparatus 800 includes one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs) for performing the methods described above. , programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components.

In an exemplary embodiment, non-transitory computer readable storage storing instructions, such as memory 804 storing instructions executable by processor 818 in apparatus 800 to perform the methods described above. Media is also provided. For example, the non-transitory computer-readable storage medium can be ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

During actual implementation, the PDU package generation device can be of other structures, which is not limited in this embodiment.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure. This application does not apply to any variations, uses, or adaptations of this disclosure, including common sense or commonly used technical means not disclosed herein, that conform to the general principles of this disclosure. is also intended to cover It is intended that the specification and embodiments be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

The disclosure is not limited to the precise constructions described above and illustrated in the accompanying drawings, and various modifications and changes can be made without departing from the scope of the disclosure. It will be understood that there are It is intended that the scope of the disclosure be limited only by the claims appended hereto.

Claims (8)

A method for generating protocol data unit (PDU) packets , comprising:
obtaining a Service Data Unit (SDU) packet;
processing the SDU packets according to a preset data packet size;
generating a packet header and a data section of the PDU packet according to a processing result, the packet header and the data section forming the PDU packet, the packet header being a framing indication (FI); field and re-segmentation flag (RF) field are omitted, but include a preset field, the preset field includes the newly added target field, and the field length of the newly added target field is less than the combined length of the FI field and the RF field;
generating a packet header and data section of a PDU packet according to the processing result;
determining indication information, wherein the indication information is used to indicate whether the data section is an SDU segment;
generating a packet header including a target field, wherein the target field includes the display information;
Generating a packet header including the target field includes:
if the indication information is used to indicate that the data section is not an SDU segment, including the target field and omitting the segmentation offset (SO) field and the last segment flag (LSF) field; A method comprising generating the packet header. for generating the packet header including the target field, wherein a previously obtained radio resource control (RRC) configuration message configures the packet header to include the target field; 2. The method of claim 1, comprising generating the packet header, if used, including the target field. generating a packet header for the PDU packet according to the processing result, further comprising:
obtaining third indication information used to indicate whether the preset data packet is a small data packet, wherein if the SDU packets are cascaded, the preset - if a data packet is a complete SDU packet to which a first SDU packet in said data section corresponds and said SDU packets were not cascaded, then said preset data packet corresponds to said data packet; the SDU packets in a section are corresponding complete SDU packets, and the packet size of the small data packets is smaller than a preset size;
the packet header including the third indication information and a target SO field, if the third indication information is used to indicate that the preset data packet is a small data packet; , wherein the length of the target SO field is less than the length of the SO field in the packet header. generating the packet header including the third indication information and a target SO field configures the packet header such that a previously obtained RRC configuration message includes the third indication information; 4. The method of claim 3, comprising generating the packet header including the third indication information and the target SO field. generating a packet header of the PDU packet according to the processing result, further comprising generating the packet header including the SO field having a target length according to a previously obtained RRC configuration message. , wherein the RRC configuration message includes the target length less than the length of the SO field in the packet header. If the cascade function is not included,
obtaining an RRC configuration message sent by a receiving end, wherein the RRC configuration message is used to disable a segmentation function for segmenting the SDU packets, and the SDU packets are data packets, wherein the packet size of the small data packets is smaller than a preset size;
and disabling the segmentation function for segmenting the SDU packets after receiving the RRC configuration message. A device for generating protocol data unit (PDU) packets , comprising:
a first acquisition module configured to perform the step of acquiring service data unit (SDU) packets;
a processing module configured to process the SDU packets according to a preset data packet size;
a generation module configured to generate a packet header and a data section of the PDU packet according to a processing result of the processing module, the packet header and the data section forming the PDU packet; If the packet header omits the Framing Indication (FI) field and the Re-Segmentation Flag (RF) field, but contains a preset field, the preset field contains the target field to be newly added, and the newly added a generation module, wherein the field length of the target field to be processed is less than the combined length of the FI field and the RF field;
generating a packet header for a PDU packet according to the processing result;
obtaining indication information, wherein the indication information is used to indicate whether the data section is an SDU segment;
generating a packet header including the target field, wherein the target field includes the display information;
Generating a packet header including the target field includes:
if the indication information is used to indicate that the data section is not an SDU segment, including the target field and omitting the segmentation offset (SO) field and the last segment flag (LSF) field; A device comprising generating the packet header. A device for generating protocol data unit (PDU) packets , comprising:
a processor;
a memory for storing processor-executable instructions;
the processor
obtain a service data unit (SDU) packet;
processing the SDU packets according to a preset data packet size;
configured to generate a packet header and a data section of the PDU packet according to a processing result, the packet header and the data section forming the PDU packet, the packet header being a framing indication ( FI) field and re-segmentation flag (RF) field are omitted, but contain a preset field, the preset field contains the newly added target field, and the field of the newly added target field length is less than the combined length of the FI field and the RF field;
generating a packet header for a PDU packet according to the processing result;
obtaining indication information, wherein the indication information is used to indicate whether the data section is an SDU segment;
generating a packet header including the target field, wherein the target field includes the display information;
Generating a packet header including the target field includes:
if the indication information is used to indicate that the data section is not an SDU segment, including the target field and omitting the segmentation offset (SO) field and the last segment flag (LSF) field; generating the packet header.

Images