Method and apparatus for transmitting and receiving packet data convergence protocol packet data units in mobile communications

Abstract

Various solutions are described for a device to transmit a Packet Data Convergence Protocol (PDCP) Packet Data Unit (PDU) in mobile communications. The device can determine a PDCP header that includes segmentation information. The device can transmit the PDCP PDU including the PDCP header to another device.

Description

[0001] Cross-referencing

[0002] This disclosure is part of a non-provisional application claiming priority to U.S. Patent Application No. 63 / 680,090 (filed August 7, 2024) and U.S. Patent Application No. 63 / 680,096 (filed August 7, 2024), the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically, to transmitting and receiving Packet Data Units (PDUs) of Packet Data Convergence Protocol (PDCP) in mobile communications. Background Technology

[0004] Unless otherwise stated, the methods described in this section are not prior art to the following claims and are not considered prior art because they are included in this section.

[0005] In Long-Term Evolution (LTE) or New Radio (NR) mobile communications, the data link layer aims to enable reliable, efficient, and structured data transmission between network devices. Specifically, the data link layer comprises the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. Each layer has different functions for processing network packets. In certain scenarios, the PDCP layer can provide specific data processing functions, such as optional compression or transmission-related processing. The RLC layer can be configured to support various forms of data segmentation or transmission control. The MAC layer performs operations related to resource coordination and transmission management. These layers work together to facilitate data transmission over the wireless communication interface.

[0006] However, with multiple protocol layers involved in processing network packets, the overall header overhead can become significant, especially in scenarios where efficiency and latency are critical. Furthermore, maintaining independent functional layers such as PDCP, RLC, and MAC may introduce higher processing complexity, resource usage, and implementation burdens at both the sending and receiving ends. This layered architecture may also limit flexibility in adapting to the evolving needs of next-generation mobile communication systems.

[0007] Therefore, reducing header overhead and processing complexity while maintaining adequate packet transmission capabilities is a crucial consideration in designing next-generation wireless communication networks. Consequently, improved solutions are needed to achieve such efficiency without compromising transmission reliability. Summary of the Invention

[0008] The following abstract is for illustrative purposes only and is not intended to be limiting in any way. That is, the following abstract aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Some embodiments will be further elaborated in the detailed description below. Therefore, the following abstract is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0009] One objective of this disclosure is to provide a solution or approach to address the aforementioned problems related to Packet Data Convergence Protocol (PDCP) Packet Data Units (PDUs) in mobile communications.

[0010] In one aspect, a method may involve an apparatus determining a PDCP header that includes segmentation information. The method may also involve the apparatus sending a PDCP PDU including the PDCP header to another apparatus.

[0011] In one aspect, a method may involve receiving a PDCP PDU including a PDCP header from another device. The PDCP header may include segmentation information. The method may also involve the device processing the PDCP PDU based on the PDCP header including the segmentation information.

[0012] In one aspect, an apparatus may include a transceiver that wirelessly communicates with a wireless network during operation. The apparatus may also include a processor communicatively coupled to the transceiver. During operation, the processor may perform operations including transmitting and receiving a PDCP PDU including a PDCP header with another device via the transceiver. The PDCP header may include segmentation information.

[0013] It is worth noting that although the descriptions herein may be made in the context of certain wireless access technologies, networks, and network topologies, such as Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, 5th Generation (5G), New Radio (NR), Internet-of-Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), and 6th Generation (6G), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, used, and implemented by other types of wireless access technologies, networks, and network topologies. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0014] The accompanying drawings are intended to further understand this disclosure and are incorporated into and constitute a part of this disclosure. The drawings illustrate embodiments of this disclosure and, together with the description, serve to explain the principles of this disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concepts of this disclosure.

[0015] Figure 1 This is a schematic diagram of an example scenario under the scheme described according to the embodiments of this disclosure.

[0016] Figure 2 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0017] Figure 3 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0018] Figure 4 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0019] Figure 5 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0020] Figure 6 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0021] Figure 7 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0022] Figure 8 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0023] Figure 9 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0024] Figure 10 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0025] Figure 11 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0026] Figure 12 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0027] Figure 13 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0028] Figure 14 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0029] Figure 15 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0030] Figure 16 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0031] Figure 17 An example of the PDCP Packet Data Unit (PDU) format according to an embodiment of this disclosure is shown.

[0032] Figure 18 This is a schematic diagram of an example scenario under the scheme described according to the embodiments of this disclosure.

[0033] Figure 19 This is a block diagram of an example communication system according to an embodiment of the present disclosure.

[0034] Figure 20This is a flowchart of an example process according to an implementation of the present disclosure.

[0035] Figure 21 This is a flowchart of an example process according to an implementation of the present disclosure. Detailed Implementation

[0036] Detailed embodiments and implementations of the subject matter of the claims are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are for illustrative purposes only and may be implemented in various forms. This disclosure may take many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are intended to make the description of this disclosure exhaustive and complete, and to adequately convey the scope of this disclosure to those skilled in the art. In the following description, well-known features and technical details may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0037] Overview

[0038] According to the implementation of this disclosure, various technologies, methods, schemes, and / or solutions relate to Packet Data Units (PDUs) of the Packet Data Convergence Protocol (PDCP) associated with devices in mobile communications. According to this disclosure, several possible solutions can be implemented individually or in combination. That is, although these possible solutions are described separately below, two or more of them can be implemented in some combination.

[0039] Regarding this disclosure, an apparatus (i.e., a transceiver (TX)) can determine a PDCP header. The PDCP header may include segmentation information. Subsequently, the apparatus can send a PDCP PDU containing the PDCP header to another apparatus (i.e., a receiver (RX)). Upon receiving the PDCP PDU, the receiver can process the PDCP PDU based on the PDCP header containing the segmentation information.

[0040] Based on the PDCP header containing segmentation information, certain processing steps in the Radio Link Control (RLC) layer can be omitted. When other RLC functions are supported, RLC layer processing can be completely eliminated. Therefore, the inclusion of the RLC header may no longer be necessary, thereby reducing processing complexity. Accordingly, overall header overhead and protocol layer complexity can be reduced while still maintaining adequate packet transmission functionality.

[0041] Figure 1 An example scenario 100 of a scheme according to embodiments of this disclosure is illustrated. Scenario 100 involves at least one network node and at least one user equipment (UE), which may be part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an Internet of Things (IoT) network, or a 6G network). Scenario 100 illustrates a current network framework. The UE may connect to the network side. The network side may include one or more network nodes.

[0042] It should be noted that, for ease of explanation, TX can correspond to a network node and RX can correspond to a UE. However, such a description is merely illustrative and is not intended to limit the scope of this disclosure. Those skilled in the art will recognize that, in alternative embodiments, TX can be implemented by the UE and RX can be implemented by the network node. In other embodiments, TX can be implemented by the UE and RX can be implemented by another UE communicating via a sidelink connection.

[0043] In some embodiments, for the PDCP layer, the network node can determine the PDCP header. This PDCP header may include fragmentation information (e.g., a fragmentation indicator and / or a fragmentation offset). The fragmentation information can be used to support the reassembly of fragmented PDCP PDUs. Subsequently, without processing by the Radio Link Control (RLC) layer (i.e., not associated with an RLC header), the network node can send a network packet carrying the PDCP PDU to the UE. This PDCP PDU includes a PDCP header. Upon receiving the network packet, the UE can process the PDCP PDU based on the PDCP header containing the fragmentation information. For example, the UE can reassemble the PDCP PDU with one or more other PDCP PDUs based on the fragmentation information contained in the PDCP header.

[0044] In some implementations, the segmentation indicator may have a 2-bit field that replaces previously reserved bits. In some implementations, the segmentation indicator may have a value of 0 to 3. When the segmentation indicator is 2 or 3, the PDCP PDU may include a segmentation offset. In some implementations, the PDCP PDU may include a 12-bit sequence number or an 18-bit sequence number. In some implementations, the PDCP header may be associated with a Data Radio Bearer (DRB), a Signaling Radio Bearer (SRB), a Control PDU, or a sidelink.

[0045] Figure 2An example of a PDCP PDU format 200 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a DRB. The PDCP header includes a Data / Control (D / C) field, a segmentation indicator SI, reserved bits R, and a 12-bit sequence number PDCP SN. The D / C field indicates whether the PDCP PDU carries data or control information. The segmentation indicator SI has a 2-bit field that replaces two of the previously reserved bits R (i.e., two of the three reserved bits R are reused as the segmentation indicator SI). The segmentation indicator SI has a value of 0 or 1, indicating whether the PDCP PDU is complete or the beginning of segmented data. The 12-bit sequence number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The PDCP PDU has Data and Message Authentication Code Integrity (MAC-I) for verifying the integrity and authenticity of the transmitted protocol data unit.

[0046] Figure 3 An example of a PDCP PDU format 300 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a DRB. The PDCP header includes a D / C field, a segmentation indicator SI, reserved bits R, and an 18-bit sequence number PDCP SN. The D / C field indicates whether the PDCP PDU carries data or control information. The segmentation indicator SI has a 2-bit field that replaces two of the previously reserved bits R (i.e., two of the five reserved bits R are reused as the segmentation indicator SI). The segmentation indicator SI has a value of 0 or 1, indicating whether the PDCP PDU is a complete data segment or the beginning of a segment. The 18-bit sequence number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The PDCP PDU has data and a MAC-I for verifying the integrity and authenticity of the transmitted protocol data unit.

[0047] Figure 4An example of a PDCP Packet Data Unit (PDU) format 400 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a Data Radio Bearer (DRB). The PDCP header includes a D / C field, a segmentation indicator SI, reserved bits R, a 12-bit sequence number PDCP SN, and a segmentation offset SO. The D / C field indicates whether the PDCP PDU carries data or control information. The segmentation indicator SI has a 2-bit field that replaces two of the previously reserved bits R (i.e., two of the three reserved bits R are reused as the segmentation indicator SI). The value of the segmentation indicator SI is 2 or 3, indicating that the PDCP PDU is a segment of a larger original data unit. The 12-bit sequence number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The segmentation offset SO is used to indicate the position of the segment within the original PDCP PDU. The PDCP PDU has data and a MAC-I for verifying the integrity and authenticity of the transmitted protocol data unit.

[0048] Figure 5 An example of a PDCP Packet Data Unit (PDU) format 500 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a Data Radio Bearer (DRB). The PDCP header includes a D / C field, a segmentation indicator SI, reserved bits R, an 18-bit sequence number PDCP SN, and a segmentation offset SO. The D / C field indicates whether the PDCP PDU carries data or control information. The segmentation indicator SI has a 2-bit field that replaces two of the previously reserved bits R (i.e., two of the five reserved bits R are reused as the segmentation indicator SI). The value of the segmentation indicator SI is 2 or 3, indicating that the PDCP PDU is a segment of a larger original data unit. The 18-bit sequence number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The segmentation offset SO is used to indicate the position of the segment within the original PDCP PDU. The PDCP PDU has data and a MAC-I for verifying the integrity and authenticity of the transmitted protocol data unit.

[0049] Figure 6An example of a PDCP Packet Data Unit (PDU) format 600 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a Signaling Radio Bearer (SRB). The PDCP header includes a segmentation indicator SI, reserved bits R, and a 12-bit sequence number PDCP SN. The segmentation indicator SI has a 2-bit field that replaces 2 bits of the previously reserved bits R (i.e., two of the four reserved bits R are reused as the segmentation indicator SI). The value of the segmentation indicator SI is 0 or 1, indicating whether the PDCP PDU is a complete or the beginning of a segmented data. The 12-bit sequence number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The PDCP PDU has data and a MAC-I for verifying the integrity and authenticity of the transmitted protocol data unit.

[0050] Figure 7 An example of a PDCP Packet Data Unit (PDU) format 700 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a Signaling Radio Bearer (SRB). The PDCP header includes a segmentation indicator SI, reserved bits R, a 12-bit sequence number PDCP SN, and a segmentation offset SO. The segmentation indicator SI has a 2-bit field that replaces 2 bits of the previously reserved bits R (i.e., two of the four reserved bits R are reused as the segmentation indicator SI). The value of the segmentation indicator SI is 2 or 3, indicating that the PDCP PDU is a segment of a larger original data unit. The 12-bit sequence number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The segmentation offset SO is used to indicate the position of the segment within the original PDCP PDU. The PDCP PDU has data and a MAC-I for verifying the integrity and authenticity of the transmitted protocol data unit.

[0051] Figure 8 An example of a PDCP Packet Data Unit (PDU) format 800 according to an embodiment of this disclosure is shown. For example, a PDCP header is associated with a control PDU (i.e., a PDU used for control data). The PDCP header includes a D / C field, a PDU type, a segmentation indicator SI, and reserved bits R. The D / C field indicates whether the PDCP PDU carries data or control information. The PDU type indicates a specific control PDU format or signaling message type. The segmentation indicator SI has a 2-bit field that replaces 2 bits of the previously reserved bits R (i.e., two of the four reserved bits R are reused as the segmentation indicator SI). The value of the segmentation indicator SI is 0 or 1, indicating whether the PDCP PDU is a complete or the beginning of segmented data. The PDCP PDU contains control data.

[0052] Figure 9An example of a PDCP Packet Data Unit (PDU) format 900 according to an embodiment of this disclosure is shown. For example, a PDCP header is associated with a control PDU (i.e., a PDU used for control data). The PDCP header includes a D / C field, a PDU type, a segmentation indicator SI, reserved bits R, and a segmentation offset SO. The D / C field indicates whether the PDCP PDU carries data or control information. The PDU type indicates the specific control PDU format or signaling message type. The segmentation indicator SI has a 2-bit field that replaces 2 bits of the previously reserved bits R (i.e., two of the four reserved bits R are reused as the segmentation indicator SI). The value of the segmentation indicator SI is 2 or 3, indicating that the PDCP PDU is a segment of a larger original data unit. The segmentation offset SO is used to indicate the position of the segment within the original PDCP PDU. The PDCP PDU has data and a MAC-I for verifying the integrity and authenticity of the transmitted protocol data unit.

[0053] Figure 10 An example of a PDCP Packet Data Unit (PDU) format 1000 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a sidelink. This sidelink is associated with a Data Radio Bearer (DRB) for multicast and broadcast, and with a Sidelink Signaling Radio Bearer 0 (SRB0) (i.e., an SRB used for initial signaling messages before the User Equipment (UE) secure activation). The PDCP header includes a Service Data Unit (SDU) type, a Segmentation Indicator (SI), Reserved Bits (R), and a 12-bit Sequence Number (PDCP SN). The SDU type indicates the data type carried in the PDCP PDU. The Segmentation Indicator SI has a 2-bit field that replaces 2 bits of the previously reserved bits R (i.e., two of the nine reserved bits R are reused as the Segmentation Indicator SI). The Segmentation Indicator SI has a value of 0 or 1, indicating that the PDCP PDU is complete data or the beginning of a segmented data. The 12-bit Sequence Number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The PDCP PDU contains data.

[0054] Figure 11An example of a PDCP Packet Data Unit (PDU) format 1100 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a sidelink. This sidelink is associated with a Data Radio Bearer (DRB) for multicast and broadcast, and with a Sidelink Signaling Radio Bearer 0 (SRB0) (i.e., the SRB used for initial signaling messages before the User Equipment (UE) secure activation). The PDCP header includes a Service Data Unit (SDU) type, a Segmentation Indicator (SI), Reserved Bits (R), a 12-bit Sequence Number (PDCP SN), and a Segmentation Offset (SO). The SDU type indicates the data type carried in the PDCP PDU. The Segmentation Indicator SI has a 2-bit field, replacing 2 bits of the previously reserved bits R (i.e., two of the nine reserved bits R are reused as the Segmentation Indicator SI). The Segmentation Indicator SI has a value of 2 or 3, indicating that the PDCP PDU is a segment of a larger original data unit. The 12-bit Sequence Number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The segment offset SO is used to indicate the position of the segment within the original PDCP PDU. The PDCP PDU contains data.

[0055] Figure 12 An example of a PDCP Packet Data Unit (PDU) format 1200 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a side link. This side link is associated with a Signaling Radio Bearer (SRB) for unicast. The PDCP header includes a Segmentation Indicator (SI), Reserved Bits (R), a 12-bit Sequence Number (PDCP SN), and a KNRP Session Identifier (ID). The Segmentation Indicator SI has a 2-bit field, replacing 2 bits of the previously reserved bits R (i.e., two of the nine reserved bits R are reused as the Segmentation Indicator SI). The Segmentation Indicator SI has a value of 0 or 1, indicating that the PDCP PDU is complete data or the beginning of a segmented data. The 12-bit Sequence Number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The KNRP Session ID is used to indicate and distinguish individual side link communication sessions between UEs. The PDCP PDU contains data and a MAC-I, used to verify the integrity and authenticity of the transmitted protocol data unit.

[0056] Figure 13An example of a PDCP Packet Data Unit (PDU) format 1300 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a sidelink. This sidelink is associated with a Signaling Radio Bearer (SRB) for unicast. The PDCP header includes a Segmentation Indicator (SI), Reserved Bits (R), a 12-bit Sequence Number (PDCP SN), a Segment Offset (SO), and a KNRP Session ID. The SDU type indicates the data type carried in the PDCP PDU. The Segmentation Indicator SI has a 2-bit field, replacing 2 bits of the previously reserved bits R (i.e., two of the four reserved bits R are reused as the Segmentation Indicator SI). The Segmentation Indicator SI has a value of 2 or 3, indicating that the PDCP PDU is a segment of a larger original data unit. The 12-bit Sequence Number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The KNRP Session ID is used to indicate and distinguish individual sidelink communication sessions between UEs. The Segment Offset SO is used to indicate the position of the segment within the original PDCP PDU. A PDCP PDU contains data and MAC-I, used to verify the integrity and authenticity of the transmitted protocol data unit.

[0057] Figure 14 An example of a PDCP Packet Data Unit (PDU) format 1400 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a sidelink. This sidelink is associated with a Data Radio Bearer (DRB) for unicast. The PDCP header includes a D / C field, a Serving Data Unit (SDU) type, a Segmentation Indicator (SI), Reserved Bits (R), a 12-bit Sequence Number (PDCPSN), and a KNRP Session ID. The D / C field indicates whether the PDCP PDU carries data or control information. The SDU type indicates the data type carried in the PDCP PDU. The Segmentation Indicator SI has a 2-bit field, replacing 2 bits of the previously reserved bits R (i.e., two of the eight reserved bits R are reused as the Segmentation Indicator SI). The Segmentation Indicator SI has a value of 0 or 1, indicating whether the PDCP PDU is complete data or the beginning of a segmented data. The 12-bit Sequence Number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The KNRP Session ID is used to indicate and distinguish individual sidelink communication sessions between UEs. A PDCP PDU contains data and MAC-I, used to verify the integrity and authenticity of the transmitted protocol data unit.

[0058] Figure 15An example of a PDCP Packet Data Unit (PDU) format 1500 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a side link. This side link is associated with a Data Radio Bearer (DRB) for unicast. The PDCP header includes a D / C field, SDU type, Segmentation Indicator SI, Reserved Bits R, a 12-bit Sequence Number PDCP SN, a Segment Offset SO, and a KNRP Session ID. The D / C field indicates whether the PDCP PDU carries data or control information. The SDU type indicates the data type carried in the PDCP PDU. The Segmentation Indicator SI has a 2-bit field, replacing 2 bits of the previously reserved bits R (i.e., two of the eight reserved bits R are reused as the Segmentation Indicator SI). The value of the Segmentation Indicator SI is 2 or 3, indicating that the PDCP PDU is a segment of a larger original data unit. The 12-bit Sequence Number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The Segment Offset SO is used to indicate the position of the segment within the original PDCP PDU. KNRP session IDs are used to indicate and distinguish between different sidelink communication sessions between UEs. PDCP PDUs contain data and MAC-I, used to verify the integrity and authenticity of transmitted protocol data units.

[0059] Figure 16 An example of a PDCP Packet Data Unit (PDU) format 1600 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a sidelink. This sidelink is associated with a Data Radio Bearer (DRB) for unicast. The PDCP header includes a D / C field, an SDU type, a segmentation indicator SI, an 18-bit sequence number PDCP SN, and a KNRP session ID. The D / C field indicates whether the PDCP PDU carries data or control information. The SDU type indicates the data type carried in the PDCP PDU. The segmentation indicator SI has a 2-bit field, replacing 2 bits of the previously reserved bits R (i.e., all two reserved bits R are reused as the segmentation indicator SI). The value of the segmentation indicator SI is 0 or 1, indicating that the PDCP PDU is either complete or the beginning of a segmented data. The 18-bit sequence number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The KNRP session ID is used to indicate and distinguish individual sidelink communication sessions between UEs. A PDCP PDU contains data and MAC-I, used to verify the integrity and authenticity of the transmitted protocol data unit.

[0060] Figure 17An example of a PDCP Packet Data Unit (PDU) format 1700 according to an embodiment of this disclosure is shown. For example, the PDCP header is associated with a sidelink. This sidelink is associated with a Data Radio Bearer (DRB) for unicast. The PDCP header includes a D / C field, an SDU type, a segmentation indicator SI, an 18-bit sequence number PDCP SN, a segmentation offset SO, and a KNRP session ID. The D / C field indicates whether the PDCP PDU carries data or control information. The SDU type indicates the data type carried in the PDCP PDU. The segmentation indicator SI has a 2-bit field, replacing 2 bits of the previously reserved bits R (i.e., all two reserved bits R are reused as the segmentation indicator SI). The value of the segmentation indicator SI is 2 or 3, indicating that the PDCP PDU is a segment of a larger original data unit. The 18-bit sequence number PDCP SN is used to identify, order, and reassemble the PDCP PDU during data transmission. The segmentation offset SO is used to indicate the position of the segment within the original PDCP PDU. KNRP session IDs are used to indicate and distinguish between different sidelink communication sessions between UEs. PDCP PDUs contain data and MAC-I, used to verify the integrity and authenticity of transmitted protocol data units.

[0061] Figure 18 An example scenario 1800 is illustrated under a scheme according to an embodiment of this disclosure. In some embodiments, at the transmitting end (TX), the transport block (TB) size can be obtained from the received downlink control information (DCI). In the logical channel priority module, data can be filled into one or more PDCP PDUs and segmented into PDCP segments S. The PDCP header of the PDCP segment S can be processed by the MAC layer to write segmentation information. At the receiving end (RX), the PDCP segments S can be reassembled based on the PDCP header containing the segmentation information.

[0062] In some implementations, the receiver (RX) may start a timer associated with the PDCP PDU. In response to the timer expiring, the RX may discard another PDCP PDU associated with that PDCP PDU. More specifically, in the event of a timer expiration, the RX's PDCP entity may forward each complete PDCP PDU to an upper layer (e.g., the IP layer or RRC layer) and discard incomplete segmented packets.

[0063] Example Implementation

[0064] Figure 19An example communication system 1900 according to an embodiment of this disclosure is shown, including an example communication device 1910 and an example network device 1920. Both the communication device 1910 and the network device 1920 can perform various functions to implement the schemes, techniques, processes and methods described herein, relating to the transmission and reception of PDCP PDUs for a UE and a network device in mobile communications, including the above-described scenarios / schemes and processes 2000 and 2100 described below.

[0065] The communication device 1910 may be part of an electronic device, which may be a user equipment (UE), such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 1910 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or mobile phone. The communication device 1910 may also be part of a machine-type device, which may be an Internet of Things (IoT), Narrowband Internet of Things (NB-IoT), or Industrial Internet of Things (IIoT) device, such as a non-movable or fixed device, a home device, a wired communication device, or a computing device. For example, the communication device 1910 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the communication device 1910 may be implemented in the form of one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more Reduced Instruction Set Computing (RISC) processors, or one or more Complex Instruction Set Computing (CISC) processors. The communication device 1910 may include... Figure 19 The communication device 1910 may also include one or more other components unrelated to the present disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, for the sake of brevity, these components of the communication device 1910 are not listed in the present disclosure. Figure 19 It is shown in the text and is not described in the following text.

[0066] Network device 1920 may be part of a network device, which may be a network node such as a satellite, base station, cell, router, or gateway. For example, network device 1920 may be implemented in an eNodeB in an LTE network, a gNB in ​​a 5G / New Radio (NR), Internet of Things (IoT), Narrowband Internet of Things (NB-IoT), or Industrial Internet of Things (IIoT) network, or in a satellite or base station in a 6G network. Alternatively, network device 1920 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more RISC or CISC processors. Network device 1920 may include... Figure 19The network device 1920 may include at least some of the components shown, such as processor 1922. It may also include one or more other components unrelated to this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, for the sake of brevity, these components of the network device 1920 are not listed in the above description. Figure 19 It is shown in the text and is not described in the following text.

[0067] In one aspect, each of processors 1912 and 1922 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processors 1912 and 1922, each of processors 1912 and 1922 may include multiple processors in some implementations and a single processor in others, depending on the different implementations of this disclosure. In another aspect, each of processors 1912 and 1922 may be implemented in hardware (and optionally firmware) comprising, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more transformers, these electronic components being configured and arranged to achieve the specific purposes of this disclosure. In other words, in at least a partial implementation, each of processors 1912 and 1922 is a dedicated machine specifically designed, arranged, and configured to perform a particular task, including transmitting and receiving PDCP packet data units (PDUs) in a device (e.g., represented by communication device 1910) and a network (e.g., represented by network device 1920) to accommodate various implementations of this disclosure.

[0068] In some implementations, the communication device 1910 may further include a transceiver 1916 coupled to the processor 1912 and capable of wirelessly transmitting and receiving data. In other words, the processor 1912 can transmit and receive data, such as configurations, messages, signals, information, indicators, etc., through the transceiver 1916. In some implementations, the communication device 1910 may further include a memory 1914 coupled to the processor 1912 and accessible by the processor 1912 for storing data. In some implementations, the network device 1920 may further include a transceiver 1926 coupled to the processor 1922 and capable of wirelessly transmitting and receiving data. In other words, the processor 1922 can transmit and receive data, such as configurations, messages, signals, information, indicators, etc., through the transceiver 1926. In some implementations, the network device 1920 may further include a memory 1924 coupled to the processor 1922 and accessible by the processor 1922 for storing data. Therefore, the communication device 1910 and the network device 1920 can communicate wirelessly through the transceiver 1916 and transceiver 1926, respectively. For ease of understanding, the following descriptions of the operation, functions and capabilities of the communication device 1910 and the network device 1920 are provided in the context of a mobile communication environment, wherein the communication device 1910 is implemented as a communication device or user equipment (UE), and the network device 1920 is implemented as a network node of a communication network.

[0069] In some implementations, each of memory 1914 and memory 1924 may include a random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitance RAM (Z-RAM). Alternatively, each of memory 1914 and memory 1924 may include a read-only memory (ROM), such as a mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively, each of memory 1914 and memory 1924 may include a non-volatile random access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0070] It is important to note that, in Figure 19 In this embodiment, communication system 1900 may include communication device 1910 (as a transmitter or receiver) and network device 1920 (as a receiver or transmitter). However, this is not intended to limit the scope of this disclosure. In other configurations, communication system 1910 may include communication device 1910 (as a transmitter or receiver) and communication device 1910 (as a receiver or transmitter), or may include network device 1920 (as a transmitter or receiver) and network device 1920 (as a receiver or transmitter).

[0071] Example Process

[0072] Figure 20 An example flow 2000 according to an embodiment of this disclosure is illustrated. Flow 2000 may be an example implementation of the above-described scenario / scheme, whether in part or in whole, for the transmission and reception of Packet Data Convergence Protocol (PDCP) Packet Data Units (PDUs) of this disclosure. Flow 2000 may represent one aspect of the implementation of characteristics of a transmitting end (e.g., communication device 1910 or network device 1920). Flow 2000 may include one or more operations, actions, or functions as shown in blocks 2010 and 2020. Although shown in discrete blocks, the individual blocks of flow 2000 may be divided into more blocks, merged into fewer blocks, or omitted according to desired implementation. Furthermore, each block of flow 2000 may be arranged according to... Figure 20 The process can be executed in the order shown, or in a different order. Process 2000 can be implemented by a sending end (e.g., communication device 1910, network device 1920, or machine-type device). For illustrative purposes only and without limitation, process 2000 is described below in the context of communication device 1910. However, those skilled in the art will understand that network device 1920 can also perform the same or equivalent operations of process 2000. Process 2000 may begin at block 2010.

[0073] In block 2010, process 2000 may involve the processor 1912 of communication device 1910 determining a PDCP header containing segmentation information. Process 2000 may continue from block 2010 to block 2020.

[0074] In block 2020, process 2000 may involve the processor 1912 of communication device 1910 sending a PDCP PDU containing the PDCP header to another device (i.e., the receiving end).

[0075] In some implementations, the segmentation information of the PDCP header may include a segmentation indicator.

[0076] In some implementations, the segmentation indicator may have a value of 0 to 3.

[0077] In some implementations, when the segmentation indicator is 2 or 3, the PDCP header may include a segmentation offset.

[0078] In some implementations, the PDCP header may include a 12-bit sequence number or an 18-bit sequence number.

[0079] In some implementations, the segmentation indicator may have a 2-bit field that replaces the previously reserved bits.

[0080] In some implementations, the PDCP header may be associated with a data radio bearer (DRB), a signaling radio bearer (SRB), a control PDU, or a side link.

[0081] Figure 21 An example flow 2100 according to an embodiment of this disclosure is illustrated. Flow 2100 may be an example implementation of the above-described scenario / solution, whether in part or in whole, for the transmission and reception of a PDCP PDU of this disclosure. Flow 2100 may represent one aspect of the implementation of features of a receiving end (e.g., communication device 1910 or network device 1920). Flow 2100 may include one or more operations, actions, or functions as shown in blocks 2110 and 2120. Although shown as discrete blocks, the individual blocks of flow 2100 may be divided into more blocks, merged into fewer blocks, or omitted according to desired implementation. Furthermore, each block of flow 2100 may be arranged according to… Figure 21 The process can be executed in the order shown, or in a different order. Process 2100 can be implemented by a receiving end (e.g., communication device 1910, network device 1920, or machine-type device). For illustrative purposes only and without limitation, process 2100 is described below in the context of network device 1920. However, those skilled in the art will understand that communication device 1910 can also perform the same or equivalent operations of process 2100. Process 2100 may begin at block 2110.

[0082] In block 2110, process 2100 may involve the processor 1922 of network device 1920 receiving a PDCP PDU containing a PDCP header from another device (e.g., a transmitter). The PDCP header may include segmentation information. Process 2100 may continue from block 2110 to block 2120.

[0083] In block 2120, process 2100 may involve the processor 1922 of network device 1920 processing the PDCP PDU based on the PDCP header containing segmentation information.

[0084] In some implementations, the segmentation information of the PDCP header may include a segmentation indicator.

[0085] In some implementations, the segmentation indicator may have a value of 0 to 3.

[0086] In some implementations, when the segmentation indicator is 2 or 3, the PDCP header may include a segmentation offset.

[0087] In some implementations, the PDCP header may include a 12-bit sequence number or an 18-bit sequence number.

[0088] In some implementations, the segmentation indicator may have a 2-bit field that replaces the previously reserved bits.

[0089] In some implementations, the PDCP header may be associated with a data radio bearer (DRB), a signaling radio bearer (SRB), a control PDU, or a side link.

[0090] In some implementations, process 2100 may also involve the processor 1922 of network device 1920 starting a timer associated with the PDCP PDU. Process 2100 may also involve the processor 1922 of network device 1920 discarding another PDCP PDU associated with the PDCP PDU in response to the expiration of the timer.

[0091] In some implementations, a PDCP PDU containing a PDCP header can be transmitted and received without being associated with an RLC header.

[0092] Additional Notes

[0093] The topics described herein sometimes demonstrate that different components are contained within or connected to other components. It should be understood that the architectures shown are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a specific function can be considered “associated” to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operationally connected” or “operationally coupled” to achieve the desired function, and any two components that can be suchly associated can also be considered “operationally coupled” to achieve the desired function. Specific examples of operational coupling include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.

[0094] Furthermore, regarding the use of almost all plural and / or singular terms in this document, those skilled in the art can appropriately convert plural to singular and / or singular to plural depending on the context and / or application. Various singular / plural arrangements are explicitly listed herein for clarity.

[0095] Furthermore, those skilled in the art will understand that terms commonly used herein, particularly in appended claims, such as the body portion of appended claims, are generally intended as “open-ended” terms. For example, the word “comprising” should be interpreted as “including but not limited to,” the word “having” should be interpreted as “at least having,” and the word “including” should be interpreted as “including but not limited to,” etc. Those skilled in the art will also further understand that if a particular quantity is introduced in a claim intentionally, that intention will be explicitly stated in the claim; if no such statement is made, then that intention does not exist. For example, for ease of understanding, the appended claims described below may contain the use of the introductory phrases “at least one” and “one or more” to introduce the content of the claim. However, the use of such phrases should not be construed as the use of the indefinite article “a” or “one” to introduce the content of the claim limiting any particular claim containing that content to containing only one of that content, even if the same claim contains the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “one,” for example, “a” and / or “one” should be interpreted as “at least one” or “one or more”; the same applies to the use of definite articles to introduce the content of the claim. Furthermore, even if a specific quantity is explicitly stated in the claims, those skilled in the art will recognize that such a statement should be interpreted as at least the stated quantity. For example, stating "two items" alone, without further modification, means at least two items, or two or more items. Additionally, when using conventions such as "at least one A, B, and C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one A, B, and C" includes, but is not limited to, systems with only A, only B, only C, A and B, A and C, B and C, and systems where A, B, and C are present simultaneously. Similarly, when using conventions such as "at least one A, B, or C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one A, B, or C" includes, but is not limited to, systems with only A, only B, only C, A and B, A and C, B and C, and systems where A, B, and C are present simultaneously. Those skilled in the art will further understand that virtually any disjunctive words and / or phrases appearing in the specification, claims, or drawings, when presenting two or more alternative terms, should be understood to include one term, either term, or both terms. For example, the phrase “A or B” should be understood as including the possibility of “A” or “B” or “A and B”.

[0096] As can be seen from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications can be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are defined by the following claims.

Claims

1. A method comprising: The device's processor determines the Packet Data Convergence Protocol (PDCP) header, which includes segmentation information; and The processor sends a PDCP packet data unit (PDU) including the PDCP header to another device.

2. The method of claim 1, wherein the segmentation information of the PDCP header includes a segmentation indicator.

3. The method of claim 2, wherein the segmentation indicator has a value of 0 to 3.

4. The method of claim 3, wherein when the value of the segmentation indicator is 2 or 3, the PDCP header includes a segmentation offset.

5. The method of claim 2, wherein the PDCP header includes a 12-bit sequence number or an 18-bit sequence number.

6. The method of claim 2, wherein the segmentation indicator has a 2-bit field that replaces the previously reserved bits.

7. The method of claim 1, wherein the PDCP header is associated with a Data Radio Bearer (DRB), a Signaling Radio Bearer (SRB), a Control PDU, or a side link.

8. A method comprising: The processor of the device receives a Packet Data Convergence Protocol (PDCP) Packet Data Unit (PDU) from another device, including a PDCP header, wherein the PDCP header includes segmentation information; and The processor processes the PDCP PDU based on the PDCP header, which includes the segmentation information.

9. The method of claim 8, wherein the segmentation information of the PDCP header includes a segmentation indicator.

10. The method of claim 9, wherein the segmentation indicator has a value of 0 to 3.

11. The method of claim 10, wherein when the value of the segmentation indicator is 2 or 3, the PDCP header includes a segmentation offset.

12. The method of claim 9, wherein the PDCP header includes a 12-bit sequence number or an 18-bit sequence number.

13. The method of claim 9, wherein the segmentation indicator has a 2-bit field that replaces previously reserved bits.

14. The method of claim 8, wherein the PDCP header is associated with a data radio bearer (DRB), a signaling radio bearer (SRB), a control PDU, or a side link.

15. The method of claim 8, further comprising: The processor starts the timer associated with the PDCP PDU; as well as The processor discards another PDCP PDU associated with the PDCP PDU in response to the expiration of the timer.

16. An apparatus comprising: A transceiver that communicates wirelessly with a wireless network during operation; as well as A processor, communicatively coupled to the transceiver, enables the processor to perform operations during operation including the following: The transceiver transmits and receives Packet Data Convergence Protocol (PDCP) Packet Data Units (PDUs) including PDCP headers with another device, wherein the PDCP headers include segmentation information.

17. The apparatus of claim 16, wherein the segmentation information of the PDCP header includes a segmentation indicator.

18. The apparatus of claim 17, wherein the segmentation indicator has a 2-bit field that replaces the previously reserved bits.

19. The apparatus of claim 16, wherein the PDCP header is associated with a data radio bearer (DRB), a signaling radio bearer (SRB), a control PDU, or a side link.

20. The apparatus of claim 16, wherein the PDCP PDU of the PDCP header is transmitted and received without being associated with a Radio Link Control (RLC) header.

Images