JP7842877B2 - Central unit, distributed unit, user equipment, and method for data transmission based on application data units - Google Patents

Description

The embodiments of this application generally relate to wireless communication technology, and more particularly to a central unit, distributed units, user equipment, and methods for data transmission based on application data units.

Extended reality (XR), including augmented reality (AR) and virtual reality (VR), as well as cloud gaming (CG), present a new and promising category of connected devices, applications, and services. Application and traffic awareness within the radio access network (RAN) is one of the key features for improving the user experience of XR services. XR services require high bitrates with limited latency. Typically, applications require a certain minimum level of application data to be available on the client side before the next level of processing can begin. This minimum level of application data is called an "Application Data Unit" (ADU).

At the NG interface between the base station (BS) and the core network (CN), ADU-related information is likely included in the NG-U header for each QoS flow. However, the information within the NG-U header is either removed by the BS's central unit (CU) or protected by the PDCP layer. Therefore, the BS's distributed units (DUs) cannot access ADU-related information for each DRB after the QoS flow-to-DRB mapping procedure.

Furthermore, the NR-U protocol layer is used for flow control of user data packets transferred from the node hosting NR PDCP to the corresponding node. Existing flow control is primarily based on the delivery status of PDCP PDUs, which is not applicable to ADU-based QoS frameworks. Additionally, the BS's CU may provide information about downlink NR PDCP PDUs that are discarded with respect to user data associated with a specific data radio bearer, which is also not applicable to ADU-based QoS frameworks.

3GPP TS 38.473 3GPP TS 38.425 3GPP TS 38.415

Some embodiments of this application provide a central unit (CU) for a network node. The CU includes a processor and a transceiver coupled to the processor. The processor is configured to receive application data unit (ADU) information related to a plurality of application data units (ADUs) from a core network via the transceiver, determine data radio bearer (DRB) and ADU association information related to one or more of the plurality of ADUs associated with one or more data radio bearers (DRBs) to distributed units (DUs) of the network node via a CU-DU interface, and transmit the DRB and ADU association information, as well as the ADU information, to the DU via the transceiver through the CU-DU interface.

In some embodiments, the processor is further configured to transmit DRB and ADU association information to the DU via transceivers using F1 Application Protocol (F1-AP) signaling.

In some embodiments, the processor is further configured to transmit ADU information to the Packet Data Convergence Protocol (PDCP) protocol data unit (PDU) via a transceiver in the user plane protocol.

In some embodiments, the processor is further configured to add ADU information in the F1 user plane (F1-U) protocol.

In some embodiments, the F1-U protocol is provided by the GPRS tunneling protocol user plane (GTP-U) extension header, and the F1-U protocol is added to the New Radio (NR) Radio Access Network (RAN) container of the GTP-U extension header, to the New Container of the GTP-U extension header, or to the Packet Data Unit Session Container of the GTP-U extension header.

In some embodiments, the processor is further configured to process ADU information before generating the PDCP PDU and to attach the ADU information to the PDCP PDU.

In some embodiments, the processor is further configured to receive flow control information based on the ADU from the DU via a transceiver.

In some embodiments, the processor is further configured to transmit DRB identification information to the DU via a transceiver and to receive ADU-based flow control information from the DU via the transceiver through the DRB corresponding to the DRB identification information.

In some embodiments, ADU-based flow control information includes at least one of the following: one or more ADU sequence numbers of one or more ADUs successfully delivered to the user equipment (UE) with respect to user data via the DRB; one or more ADU sequence numbers of one or more ADUs that were not delivered to the UE or not transmitted to the lower layer of the DU; one or more packet sequence numbers that were not delivered to the UE or not transmitted to the lower layer of the DU; or one or more ADU sequence numbers of one or more ADUs transmitted to the lower layer of the DU with respect to user data related to the DRB.

In some embodiments, the processor is further configured to send an ADU discard indication to the DU via a transceiver.

In some embodiments, the ADU drop indication is included in the F1-U protocol and includes at least one of the indications of a non-critical packet to be dropped, which indicates one or more ADUs to be dropped, or at least one non-critical packet of one or more ADUs to be dropped.

In some embodiments, the DRB and ADU association information indicates that at least one packet transmitted through one or more DRBs corresponds to the same ADU, or that at least one packet of the ADU corresponds to one or more DRBs.

In some embodiments, the ADU information includes at least one of the following: an ADU sequence number, a packet sequence number of the ADU's packets, an indication of the last packet in the ADU's packets, or an indication of the ADU's packet importance.

Some embodiments of this application provide a DU for a network node. The DU includes a processor and a transceiver coupled to the processor. The processor is configured to receive ADU information and DRB and ADU association information from a CU via a CU-DU interface via the transceiver, wherein the ADU information relates to a plurality of ADUs, and the DRB and ADU association information relates to one or more of a plurality of ADUs associated with one or more DRBs to the CU of the network node via the CU-DU interface; to determine ADU-based flow control information according to the ADU information and DRB and ADU association information; and to transmit ADU-based flow control information to the CU via the transceiver.

In some embodiments, the processor is further configured to receive DRB and ADU association information from the CU via transceivers through F1-AP signaling.

In some embodiments, the processor is further configured to receive ADU information from the CU via a transceiver in the PDCP PDU user plane protocol.

In some embodiments, ADU information is added to the F1-U protocol.

In some embodiments, the F1-U protocol is provided by a GTP-U extension header, and the F1-U protocol is added to the NR RAN container of the GTP-U extension header, to a new container of the GTP-U extension header, or to the packet data unit session container of the GTP-U extension header.

In some embodiments, the processor is further configured to retrieve ADU information from the GTP-U extension header, add the ADU information to the header or ADU layer of an existing layer, and transmit the ADU information to the UE via a transceiver.

In some embodiments, the processor is further configured to receive DRB identification information from the CU via a transceiver and to transmit ADU-based flow control information to the CU via the transceiver through the DRB corresponding to the DRB identification information.

In some embodiments, ADU-based flow control information includes at least one of the following: one or more ADU sequence numbers of one or more ADUs successfully delivered to the user equipment (UE) with respect to user data via the DRB; one or more ADU sequence numbers of one or more ADUs that were not delivered to the UE or not transmitted to the lower layer of the DU; one or more packet sequence numbers that were not delivered to the UE or not transmitted to the lower layer of the DU; or one or more ADU sequence numbers of one or more ADUs transmitted to the lower layer of the DU with respect to user data related to the DRB.

In some embodiments, the processor is further configured to receive an ADU discard indication from the CU via a transceiver and, in accordance with the ADU discard indication, discard at least one packet associated with one or more ADUs.

In some embodiments, the discard indication includes at least one of the following: one or more ADUs to be discarded, or an indication of a non-fatal packet to be discarded, which is included in the F1-U protocol and indicates one or more ADUs to be discarded, or at least one non-fatal packet of one or more ADUs to be discarded.

In some embodiments, the DRB and ADU association information indicates that at least one packet transmitted through one or more DRBs corresponds to the same ADU, or that at least one packet of the ADU corresponds to one or more DRBs.

In some embodiments, the ADU information includes at least one of the following: an ADU sequence number, a packet sequence number of the ADU's packets, an indication of the last packet in the ADU's packets, or an indication of the ADU's packet importance.

Some embodiments of this application provide a UE, which includes a processor and a transceiver coupled to the processor. The processor is configured to receive network packets from a DU of a network node via the transceiver and to obtain ADU information from the header of an existing layer of the network packet, from the ADU layer of the network packet, or from the header of the PDCP PDU of the network packet before parsing the PDCP PDU.

In some embodiments, the ADU information includes at least one of the following: an ADU sequence number, a packet sequence number of the ADU's packets, an indication of the last packet in the ADU's packets, or an indication of the ADU's packet importance.

Some embodiments of this application provide a method for a network node. The network node includes a CU and a DU. The method includes the steps of: receiving ADU information related to a plurality of ADUs from a core network by the CU; determining by the CU DRB and ADU association information related to one or more of the plurality of ADUs associated with one or more DRBs to the DU of the network node via a CU-DU interface; and transmitting the DRB and ADU association information, as well as the ADU information related to one or more DRBs, via the CU to the DU via the CU-DU interface.

In some embodiments, the method further includes the steps of: receiving DRB and ADU association information and ADU information associated with one or more DRBs from a CU via a CU-DU interface by the DU; determining ADU-based flow control information by the DU according to the ADU information associated with one or more DRBs and the DRB and ADU association information; and transmitting the ADU-based flow control information to the CU by the DU.

To illustrate how the advantages and features of this application may be obtained, this description is made by reference to the specific embodiments shown in the accompanying drawings. These drawings are merely illustrative of the embodiments of this application and should not be considered to limit its scope.

This is a schematic diagram of a wireless communication system according to some embodiments of this application. This is a block diagram of a wireless communication system according to some embodiments of this application. This is a schematic diagram of message transmission between a CU and a DU according to some embodiments of this application. This is a schematic diagram of a protocol stack between a UE and a BS including a CU and DU according to some embodiments of this application. This is a schematic diagram of a protocol stack between a UE and a BS including a CU and DU according to some embodiments of this application. This is a schematic diagram of message transmission between a CU and a DU according to some embodiments of this application. This is a schematic diagram of message transmission between a CU and a DU according to some embodiments of this application. This is a flowchart of a method for wireless communication according to an embodiment of the present disclosure. This is a block diagram of a CU according to some embodiments of this application. This is a block diagram of a DU according to some embodiments of this application. This is a block diagram of a UE according to some embodiments of this application.

The detailed description of the attached drawings is intended to describe preferred embodiments of this application and is not intended to show only the one form in which this application may be carried out. It should be understood that the same or equivalent functions may be achieved by different embodiments intended to be encompassed within the spirit and scope of this application.

Hereafter, references to some embodiments of this application are made in detail, and examples of those embodiments are shown in the accompanying drawings. Embodiments of this application may be provided in, but are not limited to, network architectures employing various service scenarios, such as 3GPP 3G, Long-Term Evolution (LTE), LTE Advanced (LTE-A), 3GPP 4G, and 3GPP 5G NR (New Radio). It is anticipated that terminology used in this application may change with the development of 3GPP (registered trademark, hereinafter the same) and related communication technologies, but this should not affect the principles of this application.

Referring to Figure 1, the wireless communication system 100 may include user equipment (UE) 101, base station (BS) 102, and core network (CN) 103. While a specific number of UE 101, BS 102, and CN 103 are shown in Figure 1, it is assumed that any number of UE 101, BS 102, and CN 103 may be included in the wireless communication system 100.

CN 103 may include Core Access and Mobility Management Function (AMF) entities. BS 102, which may communicate with CN 103, may operate or function under the control of the AMF entities. CN 103 may further include User Plane Function (UPF) entities coupled to communicate with the AMF entities.

BS 102 may be geographically distributed. In some embodiments of this application, BS 102 may be referred to as an access point, access terminal, base, base unit, macrocell, Node-B, evolved Node-B (eNB), gNB, home Node-B, relay node, or device, or may be described using other terms used in the art. Generally, BS 102 is part of a radio access network that may include one or more controllers coupled to one or more corresponding BS for communication.

UE 101 may include, but is not limited to, computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs), tablet computers, smart televisions (e.g., internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, and modems), and Internet of Things (IoT) devices.

According to some embodiments of this application, UE 101 may include, but is not limited to, portable wireless communication devices, smartphones, cellular phones, foldable mobile phones, devices having subscriber identification modules, personal computers, selective call receivers, wireless sensors, monitoring devices, or any other devices capable of transmitting and receiving communication signals over a wireless network.

In some embodiments of this application, UE 101 may include, but is not limited to, wearable devices such as smartwatches, fitness bands, and optical head-mounted displays. Furthermore, UE 101 may be referred to as a subscriber unit, mobile unit, mobile station, user, terminal, mobile terminal, wireless terminal, fixed terminal, subscriber station, user terminal, or device, or described using other terms used in the art. UE 101 may communicate directly with BS 102 via uplink communication signals.

The wireless communication system 100 may be compatible with any type of network capable of transmitting and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with wireless communication networks, cellular telephone networks, time division multiple access (TDMA) based networks, code division multiple access (CDMA) based networks, orthogonal frequency division multiple access (OFDMA) based networks, long-term evolution (LTE) networks, 3GPP-based networks, 3GPP 5G networks, satellite communication networks, high-altitude platform networks, and/or other communication networks.

In some embodiments of this application, the wireless communication system 100 conforms to the 3GPP protocol 5G New Radio (NR) or the 3GPP protocol 5G NR-light (or reduced capability NR UE), with BS 102 transmitting data on the downlink (DL) using an OFDM modulation scheme, and UE 101 transmitting data on the uplink (UL) using a single-carrier frequency division multiple access (SC-FDMA) or OFDM scheme. However, more broadly, the wireless communication system 100 may implement any other open or proprietary communication protocol, among others, such as WiMAX.

In some embodiments of this application, UE 101 and BS 102 may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Furthermore, in some embodiments of this application, UE 101 and BS 102 may communicate over a licensed spectrum, while in other embodiments, UE 101 and BS 102 may communicate over an unlicensed spectrum. This application is not intended to be limited to any particular wireless communication system architecture or protocol implementation. In several further embodiments of this application, BS 102 may communicate with UE 101 using the 3GPP 5G protocol.

Figure 2 is a block diagram of a wireless communication system 100 according to some embodiments of this application. In some embodiments, BS 102 may include a central unit (CU) 1021 and distributed units (DUs) 1023. CU 1021 may communicate with CN 103 via interface 109 (e.g., NG interface) and with DU 1023 via CU-DU interface 108 (e.g., F1 interface). DU 1023 may communicate with CU 1021 via interface 108 and with UE 101 via interface 107 (e.g., Uu interface).

Figure 3 is a schematic diagram of message transmission in a wireless communication system 100 according to some embodiments of this application. In some embodiments, CU 1021 may receive application data unit (ADU) information 1022 from CN 103. The ADU information 1022 may be related to multiple application data units (ADUs).

In some embodiments, CU 1021 may determine data radio bearer (DRB) and application data unit (ADU) association information 1020 related to one or more ADUs associated with one or more data radio bearers (DRBs) to DU 1023. CU 1021 may transmit the DRB and ADU association information 1020 to DU 1023 via the CU-DU interface 108 between CU 1021 and DU 1023. In other words, DU 1023 may receive the DRB and ADU association information 1020 from CU 1021 via the CU-DU interface 108. In some embodiments, the DRB and ADU association information 1020 may indicate that (1) at least one packet transmitted through one or more DRBs corresponds to the same ADU, or (2) at least one packet of an ADU corresponds to one or more DRBs.

For example, an ADU might represent a Group of Pictures (GOP) for a video service. GOPs are grouped together in a way that enhances the visual outcome of the video sequence. GOPs include various types such as intra-encoded pictures (I-frames), predictively encoded pictures (P-frames), and B-predictively encoded pictures (B-frames). Another example is that an ADU might represent I-frames and P-frames, FOV (Field of View) streams and omnidirectional streams, video/depth and attitude/control, video streams, and audio streams.

In some embodiments, CU 1021 may transmit DRB and ADU association information 1020 to DU 1023 via F1 Application Protocol (F1-AP) signaling during DRB setup-related procedures or DRB modification-related procedures. In particular, the F1-AP signaling containing the DRB and ADU association information 1020 may be a UE CONTEXT SETUP REQUEST message (as defined in 3GPP TS 38.473) or a UE CONTEXT MODIFICATION REQUEST message (as defined in 3GPP TS 38.473).

For example, the DRB and ADU association information 1020 is provided within the DRB to Be Setup List information element (IE) of the DRB to Be Setup List below. In particular, when DRB '#1' is set up, an ADU-associated DRB (i.e., DRB '#2') is also indicated. In other words, DRB '#1' and the DRB associated with at least one ADU (i.e., DRB '#2') correspond to the same ADU.

As another example, DRB and ADU association information 1020 is provided within a separate IE of the ADU-associated DRBs List below. Specifically, the separate IE contains the ADU association ID (i.e., ADU association IDs '#1' and '#2'). In this example, it is shown that DRB '#1' and DRB '#2' are associated with the ADU having ID '#1', and DRB '#3' and DRB '#4' are associated with the ADU having ID '#2'. In other words, DRB '#1' and DRB '#2' correspond to the same ADU, and DRB '#3' and DRB '#4' correspond to the same ADU.

In some embodiments, CU 1021 may transmit ADU information 1022 to DU 1023 via CU-DU interface 108. The ADU information 1022 may be related to one or more DRBs to DU 1023. The ADU information 1022 may include at least one of the following: (1) an ADU sequence number, (2) a packet sequence number of the ADU's packets, (3) an indication of the last packet of the ADU's packets, or (4) an indication of the ADU's packet severity.

The ADU sequence number may be the sequence number of the ADU. The packet sequence number of the ADU packets may be the sequence number of each packet within the ADU. The last packet indication of the ADU packets may indicate the last packet in the ADU. The severity indication of the ADU packets may indicate (a) whether the packet is critical or non-critical, or (b) the severity level of the packet.

In some embodiments, CU 1021 may transmit ADU information 1022 to DU 1023 in the user plane protocol of each Packet Data Convergence Protocol (PDCP) protocol data unit (PDU), and CU may add ADU information 1022 in the F1-U protocol. The F1-U protocol may be provided by the GPRS Tunneling Protocol User Plane (GTP-U) extension header.

In some implementations, the F1-U protocol may be added to the NR Radio Access Network (RAN) container of the GTP-U extension header (as defined in 3GPP TS 38.425). ADU information 1022 may be added after the QoS flow-to-DRB mapping procedure and PDCP layer processing. In other words, ADU information 1022 may be added for each PDCP PDU.

A new frame format carrying ADU information 1022 for each packet may be introduced on the NR user plane protocol. For example, the new frame format USER DATA WITH ADU INFORMATION, which carries ADU information 1022 for each packet, may be introduced on the NR user plane protocol.

In some implementations, the F1-U protocol may be added to a new container in the GTP-U extension header. In some implementations, the F1-U protocol may be added to the PDU session container in the GTP-U extension header (as defined in 3GPP TS 38.415).

In some embodiments, DU 1023 may obtain ADU information 1022 from the GTP-U extension header. DU 1023 may add ADU information 1022 to (1) an existing Layer 2 layer header (e.g., PDCP layer, RLC layer, and MAC layer), or (2) a new Layer 2 layer, which may be the ADU layer. DU 1023 may transmit ADU information 1022 to UE 101 based on the existing Layer 2 layer header or the new Layer 2 layer header. UE 101 may receive a network packet from DU 1023 and obtain ADU information 1022 from the existing Layer 2 layer header of the network packet or from the ADU layer of the network packet.

For example, when DU 1023 adds ADU information 1022 to a new Layer 2 layer (i.e., the ADU layer), the protocol stack 401 between UE 101 and BS 102 (including CU 1021 and DU 1023) is shown in Figure 4. In this example, the ADU layer is located between the RLC layer and the MAC layer. ADU information 1022 is transmitted between CU 1021 and DU 1023 based on the GTP-U layer. ADU information 1022 is also transmitted between DU 1023 and UE 101 based on the ADU layer.

In some embodiments, CU 1021 may process ADU information 1022 before generating a PDCP PDU and attach the ADU information 1022 to the PDCP PDU. UE 101 may obtain the ADU information 1022 from the PDCP PDU of the network packet before processing the PDCP PDU.

For example, based on the protocol stack 402 shown in Figure 5, CU 1021 generates ADU information 1022 after SDAP layer processing and before PDCP layer processing. Then, CU 1021 attaches ADU information 1022 to the PDCP PDU. After packet transmission between CU 1021 and DU 1023, UE 101 retrieves ADU information 1022 before PDCP layer processing. Then, UE 101 processes ADU information 1022 after PDCP layer processing and before SDAP layer processing.

In some embodiments, after the transmission of the DRB and ADU association information 1020 and ADU information 1022, the CU 1021 or DU 1023 may perform ADU-based flow control according to the DRB and ADU association information 1020 and ADU information 1022.

In some embodiments, ADU packets may be served by multiple DRBs between CU 1021 and DU 1023. Therefore, ADU-based flow control information related to ADU-based flow control may be provided via one of the DRB's F1-U protocols (i.e., GTP-U tunnels). In particular, CU 1021 may select one of the DRB's F1-U protocols for providing ADU-based flow control information; therefore, DU 1023 may generate and provide ADU-based flow control information to CU 1021 based on the selected DRB's F1-U protocol.

Figure 6 is a schematic diagram of message transmission between CU 1021 and DU 1023 according to some embodiments of this application. In some embodiments, CU 1021 may select a specific DRB from the DRBs between CU 1021 and DU 1023 for DU 1023 to provide ADU-based flow control information. CU 1021 may transmit DRB identification information 1024 for the specific DRB to DU 1023, and thus DU 1023 may generate and provide ADU-based flow control information via the specific DRB.

In some embodiments, ADU-based flow control information is carried in the user plane protocol of a particular DRB (for example, within the GTP-U extension header of a particular DRB) and may include at least one of the following: (1) information about one or more ADUs successfully delivered to UE 101; (2) information about one or more ADUs sent to the lower layer of DU 1023; (3) information about one or more ADUs not delivered to UE 101; or (4) information about one or more ADUs not sent to the lower layer of DU 1023.

For example, information about one or more ADUs successfully delivered to UE 101 may include one or more ADU sequence numbers of one or more ADUs successfully delivered to UE 101 in relation to user data in the DRB. Information about one or more ADUs transmitted to the lower layer 1023 of the DU may include one or more ADU sequence numbers of one or more ADUs that were not delivered to the UE or not transmitted to the lower layer of the DU. Information about one or more ADUs that were not delivered to UE 101 may include one or more packet sequence numbers that were not delivered to the UE or not transmitted to the lower layer of the DU. Information about one or more ADUs that were not transmitted to the lower layer of DU 1023 may include one or more ADU sequence numbers of one or more ADUs that were transmitted to the lower layer of the DU in relation to user data related to the DRB.

Figure 7 is a schematic diagram of message transmission between CU 1021 and DU 1023 according to some embodiments of this application. In some embodiments, when an IP packet belonging to a particular ADU is too slow (i.e., the IP packet queue time exceeds a threshold), CU 1021 may send an ADU discard indication 1026 to DU 1023. DU 1023 may discard the ADU in accordance with the ADU discard indication 1026.

In particular, the ADU discard indication 1026 may be included in the F1-U protocol and may include at least one of the following: (1) one or more ADUs to be discarded, or (2) an indication of at least one non-fatal packet of one or more ADUs to be discarded. Upon receiving the ADU discard indication 1026, DU 1023 may discard all buffered or available packets of all associated DRBs of the ADU indicated by the sequence number, or DU 1023 may discard all packets of the ADU marked as non-fatal according to the indication of non-fatal packets to be discarded. For example, a new frame format, USER DATA WITH ADU INFORMATION, carrying ADU information 1022 for each packet, is introduced on the NR user plane protocol.

Figure 8 shows a flowchart of a method for wireless communication according to some embodiments of this application. Referring to Figure 8, Method 800 is performed, in some embodiments of this application, by CUs and DUs of a network node (e.g., CU 1021 and DU 1023 of BS 102).

In some embodiments, operation S801 is performed for the CU to receive ADU information related to multiple ADUs from the core network. Operation S802 is performed for the CU to determine DRB and ADU association information related to one or more of the multiple ADUs associated with one or more DRBs to the DU of the network node via the CU-DU interface. Operation S803 is performed for the CU to transmit DRB and ADU association information, as well as ADU information related to one or more DRBs, to the DU via the CU-DU interface.

Operation S804 is performed for the DU to receive DRB and ADU association information, as well as ADU information associated with one or more DRBs, from the CU via the CU-DU interface. Operation S805 is performed for the DU to determine ADU-based flow control information according to the ADU information associated with one or more DRBs and the DRB and ADU association information. Operation S806 is performed for the DU to transmit ADU-based flow control information to the CU via the CU-DU interface.

Figures 9A to 9C show exemplary block diagrams of CU 1021, DU 1023, and UE 101 according to certain embodiments of the present disclosure.

As shown in Figure 9A, CU 1021 may include at least one non-temporary computer-readable medium (not shown in Figure 9A), a processor 10211, and a transceiver 10213. The processor 10211 may be electrically coupled to the non-temporary computer-readable medium (not shown in Figure 9A) and the transceiver 10213.

In this figure, elements such as the processor 10211 and transceiver 10213 are shown singly; however, unless explicitly stated otherwise, there may be multiple such elements. In certain embodiments of this disclosure, CU 1021 may further include input devices, memory, and/or other components.

In some embodiments of this disclosure, a non-temporary computer-readable medium may store computer-executable instructions causing the processor to perform the procedures relating to CU 1021 as described above. For example, when executed, the computer-executable instructions cause the processor 10211 to interact with the transceiver 10213 to perform the operations relating to CU 1021 shown in Figures 2 through 8.

As shown in Figure 9B, DU 1023 may include at least one non-temporary computer-readable medium (not shown in Figure 9B), a processor 10231, and a transceiver 10233. The processor 10231 may be electrically coupled to the non-temporary computer-readable medium (not shown in Figure 9B) and the transceiver 10233.

In this figure, elements such as the processor 10231 and transceiver 10233 are shown singly, but unless explicitly stated otherwise, there may be multiple such elements. In certain embodiments of this disclosure, DU 1023 may further include input devices, memory, and/or other components.

In some embodiments of this disclosure, a non-temporary computer-readable medium may store computer-executable instructions causing the processor to perform the procedures relating to DU 1023 as described above. For example, when executed, the computer-executable instructions cause the processor 10231 to interact with the transceiver 10233 to perform the operations relating to DU 1023 shown in Figures 2 to 8.

As shown in Figure 9C, the UE 101 may include at least one non-transient computer-readable medium (not shown in Figure 9C), a processor 1011, and a transceiver 1013. The processor 1011 may be electrically coupled to the non-transient computer-readable medium (not shown in Figure 9C) and the transceiver 1013.

In this figure, elements such as the processor 1011 and transceiver 1013 are shown singly; however, unless explicitly stated otherwise, there may be multiple such elements. In certain embodiments of this disclosure, the UE 101 may further include input devices, memory, and/or other components.

In some embodiments of this disclosure, a non-temporary computer-readable medium may store computer-executable instructions that cause the processor to perform the procedures relating to UE 101 as described above. For example, when executed, the computer-executable instructions cause the processor 1011 to interact with the transceiver 1013 to perform the operations relating to UE 101 shown in Figures 1, 2, 4, and 5.

Those skilled in the art will understand that the operation of the methods described in relation to the embodiments disclosed herein may be embodied directly in hardware, in software modules executed by a processor, or in a combination of both. The software modules may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. Furthermore, in some embodiments, the steps of the method may exist as one, any combination, or set of code and/or instructions on a non-temporary computer-readable medium, which may be incorporated into a computer program product.

While this disclosure has been described using its specific embodiments, it is evident that many alternatives, modifications, and variations will be apparent to those skilled in the art. For example, various components of the embodiments may be replaced, added, or superseded in other embodiments. Furthermore, not all elements in each figure are necessary for the operation of the disclosed embodiments. For example, those skilled in the art of the disclosed embodiments will be able to create and use the teachings of this disclosure simply by employing the elements of the independent claims. Therefore, the embodiments of this disclosure described herein are intended to be illustrative and not restrictive. Various modifications may be made without departing from the spirit and scope of this disclosure.

In this specification, the words “includes,” “including,” or any other variations thereof are intended to include non-exclusive inclusion, meaning that a process, method, product, or apparatus containing a list of elements may include other elements not expressly enumerated or specific to such process, method, product, or apparatus, rather than containing only those elements. Elements preceded by “a,” “an,” etc., do not, unless further constraints, exclude the existence of additional identical elements in a process, method, product, or apparatus containing the element. Furthermore, the word “another” is defined as at least the second or subsequent element. Words such as “having” as used herein are defined as “including.”

In this specification, the words “comprises,” “comprising,” or any other variations thereof are intended to include non-exclusive inclusion, meaning that a process, method, product, or apparatus containing a list of elements may include other elements not expressly enumerated or specific to such process, method, product, or apparatus, rather than containing only those elements. Elements preceded by “a,” “an,” etc., do not, unless further constraints, exclude the existence of additional identical elements in a process, method, product, or apparatus containing the element. The word “another” is defined as at least the second or subsequent element. As used herein, the words “including,” “having,” etc., are defined as “comprising.”

100 Wireless Communication Systems
101 User Equipment (UE)
1011 processor
1013 Transceiver
102 Base station (BS)
1020 Data Radio Bearer (DRB) and Application Data Unit (ADU) Association Information
1021 Central Unit (CU)
10211 Processor
10213 Transceiver
1022 Application Data Unit (ADU) Information
1023 Distributed Unit (DU)
10231 Processor
10233 Transceiver
1024 DRB identification information
1026 ADU Destruction Indication
103 Core Network (CN)
107 Interfaces
108 CU-DU Interface
109 Interfaces
401 Protocol Stack
402 Protocol Stack
800 ways

Claims (11)

The central unit (CU) of a network node,
Processor and
The processor includes a transceiver coupled to the processor,
The aforementioned processor,
The transceiver receives application data unit (ADU) information related to multiple application data units (ADUs) from the core network.
Determine the data radio bearer (DRB) and ADU association information related to one or more of the plurality of ADUs associated with one or more data radio bearers (DRBs) to the distributed units (DUs) of the network node via the CU-DU interface.
The transceiver is configured to transmit the DRB and ADU association information, as well as ADU information associated with one or more DRBs, to the DU via the CU-DU interface .
The processor is further configured to transmit the ADU information related to the one or more DRBs to the Packet Data Convergence Protocol (PDCP) protocol data unit (PDU) user plane protocol via the transceiver.
CU. The CU according to claim 1, wherein the processor is further configured to transmit the DRB and ADU association information to the DU via the transceiver through F1 application protocol (F1-AP) signaling . The aforementioned processor,
The CU according to claim 1, further configured to receive flow control information based on the ADU from the DU via the transceiver. The aforementioned processor,
The DRB identification information is transmitted to the DU via the transceiver.
The CU according to claim 3 , further configured to receive flow control information based on the ADU from the DU via the transceiver through a DRB corresponding to the DRB identification information. The aforementioned processor,
The CU according to claim 1, further configured to transmit an ADU discard indication to the DU via the transceiver in accordance with the ADU information relating to the one or more DRBs. The CU according to claim 1, which indicates that the DRB and ADU association information indicates that at least one packet transmitted via one or more DRBs corresponds to the same ADU, or that at least one packet of an ADU corresponds to one or more DRBs. A distributed unit (DU) of a network node,
Processor and
The processor includes a transceiver coupled to the processor,
The aforementioned processor,
Receiving data radio bearer (DRB) and application data unit (ADU) association information and ADU information from a central unit (CU) via a CU-DU interface via the transceiver, wherein the DRB and ADU association information relates to one or more of a plurality of ADUs associated with one or more data radio bearers (DRBs) to the CU of the network node via the CU-DU interface, and the ADU information relates to the one or more DRBs to the CU,
The system is configured to determine flow control information based on ADUs according to the ADU information associated with one or more DRBs and the DRB and ADU association information, and to transmit the flow control information based on ADUs to the CU via the transceiver .
The processor is further configured to receive the ADU information related to one or more DRBs from the CU via the transceiver in the user plane protocol of the Packet Data Convergence Protocol (PDCP) protocol data unit (PDU) . The DU according to claim 7 , further configured to receive the DRB and ADU association information from the CU via the transceiver through F1 application protocol (F1-AP) signaling . The aforementioned processor,
The DRB identification information is received from the CU via the transceiver.
The DU according to claim 7 , further configured to transmit flow control information based on the ADU to the CU via the transceiver through a DRB corresponding to the DRB identification information. The aforementioned processor,
The transceiver receives an ADU discard indication from the CU.
The DU according to claim 7 , further configured to discard at least one packet associated with the one or more ADUs in accordance with the ADU discard indication. The aforementioned ADU discard indication is included in the F1 user plane (F1-U) protocol.
A DU according to claim 10 , comprising at least one of one of the following: one or more ADUs to be discarded, or an indication of a noncritical packet to be discarded, which indicates at least one noncritical packet of an ADU to be discarded .