Method and apparatus for f1u and GTP enhancements for beyond 5g and 6g systems
By implementing prioritization and enhanced reporting mechanisms through new TEIDs and IE fields within the GTP header, the F1-U interface addresses packet prioritization and loss reporting issues, enhancing the efficiency and reliability of data transfer in beyond 5G and 6G wireless communication systems.
Patent Information
- Application Number
- PCT/KR2024/006963
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-29
- Filing Date
- 2024-05-23
- Publication Date
- 2024-12-05
AI Technical Summary
Current F1-U interface protocols in beyond 5G and 6G wireless communication systems lack prioritization of data packets, leading to issues like head-of-line blocking, increased jitter, and latency, and do not efficiently handle packet segmentation and loss reporting, which are critical for high-speed and low-latency applications.
The introduction of new Tunnel Endpoint Identifiers (TEIDs) and modified Information Elements (IEs) within the GTP header to prioritize packets, concatenate or segment data units based on MTU size, and enhance loss reporting, allowing for efficient prioritization, packaging, and error recovery across the CU-DU interface.
This solution enables prioritization of packets, reduces latency and jitter, improves data transfer efficiency, and facilitates effective error handling, ensuring better network performance for high-speed and low-latency applications in beyond 5G and 6G systems.
Smart Images

Figure KR2024006963_05122024_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS FOR F1U AND GTP ENHANCEMENTS FOR BEYOND 5G AND 6G SYSTEMS
[0001] The present invention generally relates to wireless communication networking and more particularly relates to a system and method for an interface processing between a centralized unit (CU) and a distributed unit (DU) architecture corresponding to beyond 5G / 6G communication networks.
[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.
[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.
[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.
[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.
[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.
[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
[0008] The present invention has been made to address at least the above problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a method and apparatus for F1-U and GTP enhancements for beyond 5G and 6G systems.
[0009] In one embodiment, a method performed by a centralized unit (CU) of a base station is provided. The method comprising: receiving, from an upper layer at a converged layer 2 (CL2) of the CU (210), at least one service data unit (SDU); generating at least one protocol data unit (PDU) using the at least one received SDU; encapsulating each of the at least one PDU with a general packet radio service (GPRS) tunnelling protocol (GTP) header, wherein each of the at least one encapsulated PDU includes header information including at least one tunnel endpoint identifier (TEID) in the GTP header; assigning a priority to each PDU among the at least one PDU by allocating a value to a TEID among the at least one TEID; and transmitting, to the DU of the base station via the F1-U interface, each PDU among the at least one PDU in an order of the assigned priority.
[0010] In one embodiment, a method performed by a centralized unit (CU) of a base station is provided. The method comprising: receiving, from the upper layer at the CL2 of the CU, a service data unit (SDU) at a converged layer 2 (CL2) of the CU; based on the received SDU, generating, a downlink user data (DUD) including an F1-U header corresponding to a protocol data unit (PDU), wherein the F1-U header includes at least one of information element (IE); adding a payload type flag and a PDU size flag to the at least one IE within the F1-U header; assigning a priority to each PDU among the at least one PDU based on a type of each PDU by allocating a value in the payload type flag; storing a size of each PDU in the PDU size flag upon assigning the priority of each PDU; and transmitting, to the DU of the base station via the F1-U interface, each PDU of the DUD including the PDU size flag in the F1-U header in an order of the assigned priority.
[0011] In one embodiment, a method performed by a centralized unit (CU) of a base station is provided. The method comprising: receiving, from an upper layer at a converged layer 2 (CL2) of the CU, a service data unit (SDU); based on the received SDU, generating a downlink user data (DUD) including an F1-U header corresponding to a protocol data unit (PDU), wherein the F1-U header includes at least one information element (IE); adding each of a multiple PDU exist flag, a number of PDUs field, and an individual PDU size field to the at least one IE within the F1-U header; concatenating (808) at least one PDU into the DUD along with the F1-U header upon a determination that a combined size of the at least one PDU is less than a size of a maximum transfer unit (MTU), wherein the MTU corresponds to a maximum size of the DUD that is being transmitted via the IP layer over the F1-U interface; assigning, upon concatenating the at least one PDU into the DUD, a value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field, respectively, within the F1-U header; and transmitting the DUD including the at least one concatenated PDU along with the F1-U header to the DU of the base station via the F1-U interface.
[0012] In one embodiment, a method performed by a distributed unit (DU) of a base station is provided. The method comprising: receiving, from an upper layer at the DU, downlink user data (DUD); based on the received DUD, generating a downlink data delivery status (DDDS) including a F1-U header corresponding to at least one protocol data unit (PDU), wherein the F1-U header includes at least one Information Element (IE); based on a determination of receiving the DDDS, adding to the at least one IE within the F1-U header each of a CL2-U Sequence Number (SN) Ind flag, a number of lost CL2-U SN range field, a start of lost CL2-U SN range field, an end of lost CL2-U SN range field, and a CL2-U SN of a polling frame field; determining whether a set of PDU among the at least one PDU is lost during PDU transmission from the CU to the DU, based on the received CL2-U SN and segment offset of the at least one PDU via the F1-U interface; assigning, upon a determination that the set of PDU is lost during the PDU transmission, a value for each of the CL2-U SN ID flag, the number of lost CL2-U SN range field, the start of lost CL2-U SN range field, the end of lost CL2-SN range field, and the CL2-U SN of polling frame field, respectively, within the F1-U header; and transmitting, to the CU of the base station via the F1-U interface, the DDDS along with the F1-U header after including the assigned value within the F1-U header.
[0013] In one embodiment, a centralized unit (CU) of a base station is provided. The CU compirises a transceiver and a controller. The controller is configured to: receive, from an upper layer at a converged layer 2 (CL2) of the CU (210), at least one service data unit (SDU), generate at least one protocol data unit (PDU) using the at least one received SDU, encapsulate each of the at least one PDU with a general packet radio service (GPRS) tunnelling protocol (GTP) header, wherein each of the at least one encapsulated PDU includes header information including at least one tunnel endpoint identifier (TEID) in the GTP header, assign a priority to each PDU among the at least one PDU by allocating a value to a TEID among the at least one TEID, and transmit, to the DU of the base station via the F1-U interface, each PDU among the at least one PDU in an order of the assigned priority.
[0014] In one embodiment, a centralized unit (CU) of a base station is provided. The CU compirises a transceiver and a controller. The controller is configured to: receive, from the upper layer at the CL2 of the CU, a service data unit (SDU) at a converged layer 2 (CL2) of the CU, based on the received SDU, generate, a downlink user data (DUD) including an F1-U header corresponding to a protocol data unit (PDU), wherein the F1-U header includes at least one of information element (IE), add a payload type flag and a PDU size flag to the at least one IE within the F1-U header, assign a priority to each PDU among the at least one PDU based on a type of each PDU by allocating a value in the payload type flag, store a size of each PDU in the PDU size flag upon assigning the priority of each PDU, and transmit, to the DU of the base station via the F1-U interface, each PDU of the DUD including the PDU size flag in the F1-U header in an order of the assigned priority.
[0015] In one embodiment, a centralized unit (CU) of a base station is provided. The CU compirises a transceiver and a controller. The controller is configured to: receive, from an upper layer at a converged layer 2 (CL2) of the CU, a service data unit (SDU), based on the received SDU, generate a downlink user data (DUD) including an F1-U header corresponding to a protocol data unit (PDU), wherein the F1-U header includes at least one information element (IE), add each of a multiple PDU exist flag, a number of PDUs field, and an individual PDU size field to the at least one IE within the F1-U header, concatenate at least one PDU into the DUD along with the F1-U header upon a determination that a combined size of the at least one PDU is less than a size of a maximum transfer unit (MTU), wherein the MTU corresponds to a maximum size of the DUD that is being transmitted via the IP layer over the F1-U interface, assign, upon concatenating the at least one PDU into the DUD, a value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field, respectively, within the F1-U header, and transmit, to the DU of the base station via the F1-U interface, the DUD including the at least one concatenated PDU along with the F1-U header.
[0016] In one embodiment, a distribured unit (DU) of a base station is provided. The CU compirises a transceiver and a controller. The controller is configured to: receive, from an upper layer at the DU, downlink user data (DUD), based on the received DUD, generate a downlink data delivery status (DDDS) including a F1-U header corresponding to at least one protocol data unit (PDU), wherein the F1-U header includes at least one Information Element (IE); based on a determination of receiving the DDDS, add to the at least one IE within the F1-U header each of a CL2-U Sequence Number (SN) Ind flag, a number of lost CL2-U SN range field, a start of lost CL2-U SN range field, an end of lost CL2-U SN range field, and a CL2-U SN of a polling frame field, determine whether a set of PDU among the at least one PDU is lost during PDU transmission from the CU to the DU, based on the received CL2-U SN and segment offset of the at least one PDU via the F1-U interface, assign, upon a determination that the set of PDU is lost during the PDU transmission, a value for each of the CL2-U SN ID flag, the number of lost CL2-U SN range field, the start of lost CL2-U SN range field, the end of lost CL2-SN range field, and the CL2-U SN of polling frame field, respectively, within the F1-U header, and transmit, to the CU of the base station via the F1-U interface, the DDDS along with the F1-U header after including the assigned value within the F1-U header.
[0017] Advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. For more enhanced communication system, there is a need for method and apparatus for F1-U and GTP enhancements.
[0018] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
[0019] FIG. 1a illustrates a NG-RAN architecture, in accordance with an existing arts;
[0020] FIG. 1b illustrates a NG-RAN architecture, in accordance with an existing arts;
[0021] FIG. 1c illustrates various PDU types in F1-U, in accordance with existing arts;
[0022] FIG. 1d illustrates various PDU types in F1-U, in accordance with existing arts;
[0023] FIG. 1e illustrates various PDU types in F1-U, in accordance with existing arts;
[0024] FIG. 1f illustrates structures of packets transported over the GTP Tunnel between CU and DU, in accordance with existing arts;
[0025] FIG. 1g illustrates structures of packets transported over the GTP Tunnel between CU and DU, in accordance with existing arts;
[0026] FIG. 2 illustrates a wireless communication environment comprising a Centralized Unit (CU) and a Distributed Unit (DU), in accordance with an embodiment of the present disclosure;
[0027] FIG. 3a illustrates a representation of Tunnel Endpoint Identifier (TEID) of the GPRS Tunnelling Protocol (GTP) header carrying the CL2 PDUs), in accordance with one aspect of the present disclosure;
[0028] FIG. 3b illustrates a modified Downlink User Data (DUD) which allows to specify the Payload Type, in accordance with another aspect of the present disclosure;
[0029] FIG. 3c illustrates a modified Downlink User Data (DUD) to specify length indicators, in accordance with another aspect of the present disclosure;
[0030] FIG. 4a illustrates a modified DUD for scenario where each CL2 PDU is smaller than the MTU size in accordance with an aspect of the present disclosure;
[0031] FIG. 4b illustrates a modified DUD for scenario where the MTU size is smaller than PDU size; in accordance with another aspect of the present disclosure;
[0032] FIG. 5a illustrates modified DDDS which can be used over the CL2-MAC interface, in accordance with various aspects of the present disclosure;
[0033] FIG. 5b illustrates modified DDDS which can be used over the CL2-MAC interface, in accordance with various aspects of the present disclosure;
[0034] FIG. 6a illustrates a UUD PDU frame having F1-U header, in accordance with an aspect of the present disclosure;
[0035] FIG. 6b illustrates an UDDS PDU frame having F1-U header in accordance with an aspect of the present disclosure;
[0036] FIG. 7a illustrates a method for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in a wireless communication network, in accordance with an aspect of the present disclosure;
[0037] FIG. 7b illustrates another method for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in a wireless communication network, in accordance with an aspect of the present disclosure;
[0038] FIG. 8 illustrates yet another method for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in a wireless communication network, in accordance with an aspect of the present disclosure;
[0039] FIG. 9 illustrates yet another method for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in a wireless communication network, in accordance with an aspect of the present disclosure;
[0040] FIG. 10 illustrates yet another method for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in a wireless communication network, in accordance with an aspect of the present disclosure;
[0041] FIG. 11 illustrates yet another method for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in a wireless communication network, in accordance with an aspect of the present disclosure; and
[0042] FIG. 12 illustrates yet another method for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in a wireless communication network, in accordance with an aspect of the present disclosure.
[0043] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
[0044] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.
[0045] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.
[0046] Reference throughout this specification to "an aspect", "another aspect" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
[0047] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.
[0048] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skilled in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.
[0049] It is appreciated that the terms "field", "flag", and "Information Element (IE)" may be used interchangeably. Further, "CL2-MAC interface", "CU-DU interface", and "F1-U interface" may be used interchangeably in some embodiments.
[0050] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the disclosure. This summary is neither intended to identify key or essential inventive concepts of the invention nor is it intended to determine the scope of the disclosure.
[0051] In an embodiment of the present disclosure, a method for F1-U interface processing between a Centralized Unit (CU) and a Distributed Unit (DU) in a wireless communication network, is disclosed. The method includes receiving, at a Converged Layer 2 (CL2) of the CU, a plurality of Service Data Units (SDUs) from an upper layer. The method includes generate a plurality of Protocol Data Units (PDUs) using the received SDUs. The method includes encapsulating each of the plurality of PDUs with a GPRS Tunnelling Protocol (GTP) header, wherein each of the encapsulated plurality of PDUs includes header information including a plurality of Tunnel Endpoint Identifiers (TEIDs) in the GTP header. The method includes assigning a priority to each PDU among the plurality of PDUs by allocating a value to a TEID among the plurality of TEIDs indicating a payload type flag. Lastly, the method includes transmitting, to the DU via an F1-U interface, each PDU among the plurality of PDUs in an order of the assigned priority.
[0052] In another embodiment, a method for F1-U interface processing between a Centralized Unit (CU) and a Distributed Unit (DU) in a wireless communication network, is disclosed. The method includes receiving, from an upper layer, a Service Data Unit (SDU) at a Converged Layer 2 (CL2) of the CU. The method includes generating, based on the received SDU, a Downlink User Data (DUD) including a F1-U header corresponding to a Protocol Data unit (PDU), the F1-U header includes a plurality of Information Elements (IEs). The method includes adding a payload type flag and a PDU size flag to the plurality of IEs within the F1-U header. The method includes assigning a priority to each PDU among the plurality of the PDUs based on a type of each PDU by allocating a value in the payload type flag. The method includes storing a size of each PDU in the PDU size flag upon assigning the priority of each PDU. Lastly, the method includes transmitting, to the DU via an F1-U interface, each PDU of the DUD including the PDU size flag in the F1-U header in an order of the assigned priority.
[0053] In yet another embodiment, a method for F1-U interface processing between a Centralized Unit (CU) and a Distributed Unit (DU) in a wireless communication network, is disclosed. The method includes receiving, from an upper layer, a Service Data Unit (SDU) at a Converged Layer 2 (CL2) of the CU. The method includes generating, based on the received SDU, a Downlink User Data (DUD) including a F1-U header corresponding to a Protocol Data unit (PDU), the F1-U header includes a plurality of Information Elements (IEs). The method includes adding each of a multiple PDU exist flag, a number of PDUs field, and an individual PDU size field to the plurality of IEs within the F1-U header. The method includes concatenating a plurality of PDUs into the DUD along with the F1-U header upon a determination that a combined size of the plurality of PDUs is less than a size of a Maximum Transfer Unit (MTU), wherein the MTU corresponds to a maximum size of the DUD that is being transmitted via the IP layer over F1-U interface. The method includes assigning, upon concatenating the plurality of PDUs into the DUD, a value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field, respectively, within the F1-U header. Lastly, the method includes transmitting, after including the assigned value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field within the F1-U header, the DUD including the concatenated plurality of PDUs along with the F1-U header to the DU via the F1-U interface.
[0054] In yet another embodiment, a method for F1-U interface processing between a Centralized Unit (CU) and a Distributed Unit (DU) in a wireless communication network, is disclosed. The method includes receiving, from an upper layer, a Downlink User Data (DUD) at the DU. The method includes generating, based on the received DUD, a Downlink Data Delivery Status (DDDS) including a F1-U header corresponding to a plurality of Protocol Data units (PDUs), the F1-U header includes a plurality of Information Elements (IEs). The method includes adding, to the plurality of IEs within the F1-U header based on a determination of receiving the DDDS, each of a CL2-U Sequence Number (SN) Ind flag, a number of lost CL2-U SN range field, a start of lost CL2-U SN range field, an end of lost CL2-U SN range field, and a CL2-U SN of a polling frame field. The method includes determining whether a set of PDUs among the plurality of PDUs are lost during PDU transmission from the CU to the DU based on the received CL2-U SN and Segment Offset of the plurality of PDUs via an F1-U interface. The method includes assigning, upon a determination that the set of PDUs are lost during the PDU transmission, a value for each of the CL2-U SN ID flag, the number of lost CL2-U SN range field, the start of lost CL2-U SN range field, the end of lost CL2-SN range field, and the CL2-U SN of polling frame field, respectively, within the F1-U header. Lastly, the method includes transmitting, from the DU to the CU via the F1-U interface, the DDDS along with the F1-U header after including the assigned value within the F1-U header.
[0055] In yet another embodiment, a method for F1-interface processing between a Distributed Unit (DU) and a Centralized Unit (CU) in a wireless communication network, is disclosed. The method includes receiving, from an upper layer, at DU, a Downlink User Data (DUD) frame with Assistance Information Reporting Flag set to true. The method includes generating, an Assistance Information Report (AIR) including a F1-U header, the F1-U header includes an Information Element (IE) indicating an average grant size flag corresponding to the MAC in DU. The method includes determining a value assigned to the average grant size flag. The method includes adding, within the F1-U header, the value of average grant size flag in AIR. Lastly, the method includes transmitting the generated AIR to the CU via an F1-U interface.
[0056] In yet another embodiment, a method for F1-interface processing between a Distributed Unit (DU) and a Centralized Unit (CU) in a wireless communication network, is disclosed. The method includes receiving a plurality of Protocol Data Units (PDU). The method includes generating, based on the received PDUs, an Upstream / Uplink User Data (UUD) including an F1-U header and a plurality of Service Data units (SDUs), the F1-U header includes a plurality of Information Elements (IEs). The method includes adding, within the F1-U header, each of a PDU type flag, a Retransmission (ReTx) flag, a Report Polling flag, and a MAC-U = Sequence Number (SN) flag to the plurality of IEs. The method includes assigning, based on the UUD, a value to each of the PDU type flag, the ReTx flag, the Report Polling flag, and the MAC-U SN flag, respectively, within the F1-U header. The method includes sending, via an F1-U interface, the UUD including the assigned value to an upper layer at CU.
[0057] In yet another embodiment, a method for F1-U interface processing between a Centralized Unit (CU) and a Distributed Unit (DU) in a wireless communication network. The method includes receiving a Upstream User Data (UUD) from a lower layer. The method includes generating, based on the received UUD, an Upstream Data Delivery Status (UDDS) including an F1-U header and a plurality of Protocol Data units (PDUs), the F1-U header includes a plurality of Information Elements (IEs). The method includes adding, within the F1-U header, each of a the PDU type flag, a desired data rate flag, a desired buffer size flag, a lost MAC-U flag to the plurality of IEs. The method includes assigning a value to each of the PDU type flag, the desired data rate flag, the desired buffer size flag, and the lost MAC-U flag, respectively, within the F1-U header. Lastly, the method includes sending, via an F1-U interface, the UDDS including the assigned value to a Medium Access Control (MAC) layer of the DU.
[0058] In yet another embodiment, a system for F1-U interface processing between a Centralized Unit (CU) and a Distributed Unit (DU) in a wireless communication network, is disclosed. The system includes at least one processor in the CU and a memory of the CU communicatively coupled with the at least one processor in the CU. The at least one processor is configured to receive, at a Converged layer 2(CL2), a plurality of Service Data Units (SDUs) from an upper layer. The at least one processor is configured to generate a plurality of Protocol Data Units (PDUs) using the received SDUs. The at least one processor is configured to encapsulate each of the plurality of PDUs with a GPRS Tunnelling Protocol (GTP) header, where each of the encapsulated plurality of PDUs includes header information including a plurality of Tunnel Endpoint Identifiers (TEIDs) in the GTP header. The at least one processor is configured to assign a priority to each PDU among the plurality of PDUs by allocating a value to a TEID among the plurality of TEIDs indicating a payload type flag. The at least one processor is configured to transmit, to the DU via an F1-U interface, each PDU among the plurality of PDUs in an order of the assigned priority.
[0059] In yet another embodiment, a system for F1-U interface processing between a Centralized Unit (CU) and a Distributed Unit (DU) in a wireless communication network, is disclosed. The system includes at least one processor in the CU and a memory of the CU communicatively coupled with the at least one processor in the CU. The at least one processor is configured to receive, from an upper layer, a Service Data Unit (SDU) at a Converged Layer 2 (CL2). The at least one processor is configured to generate, based on the received SDU, a Downlink User Data (DUD) including a F1-U header corresponding to a Protocol Data unit (PDU), the F1-U header includes a plurality of Information Elements (IEs). The at least one processor is configured to add a payload type flag and a PDU size flag to the plurality of IEs within the F1-U header. The at least one processor is configured to assign a priority to each PDU among the plurality of the PDUs based on a type of each PDU by allocating a value in the payload type flag. The at least one processor is configured to store a size of each PDU in the PDU size flag upon assigning the priority of each PDU. The at least one processor is configured to transmit, to the DU via an F1-U interface, each PDU of the DUD including the PDU size flag in the F1-U header in an order of the assigned priority.
[0060] In yet another embodiment, a system for F1-U interface processing between a Centralized Unit (CU) and a Distributed Unit (DU) in a wireless communication network, is disclosed. The system includes at least one processor in the CU and a memory of the CU communicatively coupled with the at least one processor in the CU. The at least one processor is configured to receive, from an upper layer, a Service Data Unit (SDU) at a Converged Layer 2 (CL2) of the CU. The at least one processor is configured to generate, based on the received SDU, a Downlink User Data (DUD) including a F1-U header corresponding to a Protocol Data unit (PDU), the F1-U header includes a plurality of Information Elements (IEs). The at least one processor is configured to add each of a multiple PDU exist flag, a number of PDUs field, and an individual PDU size field to the plurality of IEs within the F1-U header. The at least one processor is configured to concatenate a plurality of PDUs into the DUD along with the F1-U header upon a determination that a combined size of the plurality of PDUs is less than a size of a Maximum Transfer Unit (MTU), wherein the MTU corresponds to a maximum size of the DUD that is being transmitted via the IP layer over F1-U interface. The at least one processor is configured to assign, upon concatenating the plurality of PDUs into the DUD, a value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field, respectively, within the F1-U header. The at least one processor is configured to transmit, after including the assigned value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field within the F1-U header, the DUD including the concatenated plurality of PDUs along with the F1-U header to the DU via the F1-U interface.
[0061] In yet another embodiment, a system for F1-U interface processing between a Distributed Unit (DU) and a Centralized Unit (CU) in a wireless communication network, is disclosed. The system includes at least one processor in the DU and a memory of the DU communicatively coupled with the at least one processor in the DU. The at least one processor is configured to receive, from an upper layer, at the DU, a Downlink User Data Frame. The at least one processor is configured to generate, a Downlink Data Delivery Status (DDDS) including a F1-U header corresponding to a plurality of Protocol Data units (PDUs), the F1-U header includes a plurality of Information Elements (IEs). The at least one processor is configured to add, to the plurality of IEs within the F1-U header based on a determination of receiving the DDDS, each of a CL2-U Sequence Number (SN) Ind flag, a number of lost CL2-U SN range field, a start of lost CL2-U SN range field, an end of lost CL2-U SN range field, and a CL2-U SN of a polling frame field. The at least one processor is configured to determine whether a set of PDUs among the plurality of PDUs are lost during PDU transmission from the CU to the DU based on the received CL2-U SN of the plurality of PDUs via an F1-U interface. The at least one processor is configured to assign, upon a determination that the set of PDUs are lost during the PDU transmission, a value for each of the CL2-U SN ID flag, the number of lost CL2-U SN range field, the start of lost CL2-U SN range field, the end of lost CL2-U SN range field, and the CL2-U SN of polling frame field, respectively, within the F1-U header. The at least one processor is configured to transmit, from the DU to the CU via the F1-U interface, the DDDS along with the F1-U header after including the assigned value within the F1-U header.
[0062] In yet another embodiment, a system for F1-U interface processing between a Distributed Unit (DU) and a Centralized Unit (CU) in a wireless communication network, is disclosed. The system includes at least one processor in the DU and a memory of the DU communicatively coupled with the at least one processor in the DU. The at least one processor is configured to receive, from an upper layer, a Downlink User Data (DUD) frame with Assistance Information Reporting Flag set to true. The at least one processor is configured to generate, an Assistance Information Report (AIR) including a F1-U header, the F1-U header includes an Information Element (IE) indicating an average grant size flag corresponding to the MAC in DU. The at least one processor is configured to determine a value assigned to the average grant size flag. The at least one processor is configured to add, within the F1-U header, the value of average grant size flag in AIR. The at least one processor is configured to transmit the generated AIR to the CU via an F1-U interface.
[0063] In yet another embodiment, a system for F1-U interface processing between a Distributed Unit (DU) and a Centralized Unit (CU) in a wireless communication network, is disclosed. The system includes at least one processor in the DU and a memory of the DU communicatively coupled with the at least one processor in the DU. The at least one processor is configured to receive a plurality of Protocol Data Units (PDUs). The at least one processor is configured to generate, based on the received PDUs, an Upstream / Uplink User Data (UUD) including an F1-U header and a plurality of Service Data units (SDUs), the F1-U header includes a plurality of Information Elements (IEs). The at least one processor is configured to add, within the F1-U header, each of a PDU type flag, a Retransmission (ReTx) flag, a Report Polling flag, and a MAC-U Sequence Number (SN) flag to the plurality of IEs. The at least one processor is configured to assign, based on the UUD, a value to each of the PDU type flag, the ReTx flag, the Report Polling flag, and the MAC-U SN flag, respectively, within the F1-U header. The at least one processor is configured to send, via an F1-U interface, the UUD including the assigned value to an upper layer at CU.
[0064] In yet another embodiment, a system for F1-U interface processing between a Centralized Unit (DU) and a Distributed Unit (CU) in a wireless communication network, is disclosed. The system includes at least one processor in the CU and a memory of the CU communicatively coupled with the at least one processor in the CU. The at least one processor is configured to receive from lower layer, a Upstream User Data (UUD) at CU. The at least one processor is configured to generate, based on the received UUD, an Upstream Data Delivery Status (UDDS) including an F1-U header and a plurality of Protocol Data units (PDUs), the F1-U header includes a plurality of Information Elements (IEs). The at least one processor is configured to add, within the F1-U header, each of a PDU type flag, a desired data rate flag, a desired buffer size flag, a lost MAC-U flag to the plurality of IEs. The at least one processor is configured to assign a value to each of a PDU type flag, the desired data rate flag, the desired buffer size flag, and the lost MAC-U flag, respectively, within the F1-U header. The at least one processor is configured to send, via an F1-U interface, the UDDS including the assigned value to a Medium Access Control (MAC) layer of the DU.
[0065] To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail with the accompanying drawings.
[0066] In recent years several broadband wireless technologies have been developed to meet the requirement of the growing number of broadband subscribers for providing better applications and services. Second generation wireless communication systems have been developed to provide voice services while ensuring the mobility of users. Third generation wireless communication system supports voice services along with a data service. In recent years, a fourth wireless communication system has been developed to provide high-speed data service to cater to the requirement for high-speed and low-latency data services. However, currently, the fourth generation (4G) or Long Term Evolution (LTE) wireless communication system suffers from a lack of resources to meet the growing demand for high-speed data services. The problem is solved by the deployment of a fifth generation wireless communication system to meet the ever-growing demand for high-speed data services. Furthermore, the fifth generation (5G) or New Radio (NR) wireless communication system provides ultra-reliability and supports low latency applications.
[0067] With the advent of further increase in data demand, high bandwidth, and processing capability, the next-generation wireless communication systems i.e., beyond 5G and sixth generation (6G) should be capable to meet such ever-increasing requirements. To meet the requirements, the communication protocol should be capable of processing high-speed data. In LTE, the protocol that exists for a user plane stack includes a Packet Data Convergence Protocol (PDCP), a Radio Link Control (RLC), a Medium Access Control (MAC), and a Physical (PHY) protocol. Additionally, the protocol that exists for a control plane stack includes the Radio Resource Control (RRC) and Non-Access Stratum (NAS).
[0068] As per the 3rd Generation Partnership Project (3GPP), a Next Generation Radio Access Network (NG-RAN) protocol stack that is split across Centralized Unit (CU) and Distributed Unit (DU) is shown in FIG. 1a and FIG. 1b, in accordance with existing art. In general, telecommunication network includes Radio Access Network and Core network. The Radio Access Network may be further divided into multiple entities as split option defined in specification. The conventional split option is split into two entities, i.e., a gNB-Centralized Unit (CU) and a gNB-Distributed Unit (DU). Additionally, NR protocol option for deployment are split across the CU and the DU. The CU provides support for higher layers of the protocol stack like Service Data Adaption Protocol (SDAP), PDCP, and RRC while the DU provides support to the lower layers such as Radio Link Control (RLC), MAC, and PHY layer. Accordingly, the CU performs higher-layer operations like radio resource management, and mobility management, whereas the DU engages in the lower-layer functions like radio signal processing, modulation, error detection, and recovery. As per the architecture, multiple DUs are interfaced to one CU, and the communication between the CU and DUs is carried over a F1-AP interface. The F1 interface further divides into F1-C and F1-U dedicated to the control plane message exchange and the user plane data operation transfers respectively. The CU and DU exchange F1-U packets over GPRS Tunnelling Protocol (GTP) tunnels wherein the GTP extension headers are used for carrying F1-U Protocol Data Unit (PDU) information. In the NR protocol, the F1-U is defined between the PDCP and the RLC interface. Further, a GTP encapsulation allows a placeholder in the form of GTP extension header to send metadata of payload along with the payload. The F1-U interface allows CU to deliver data to the DU as an GTP encapsulated payload. Further, the F1-U interface allows exchange of multiple PDU Types viz. F1U-PDU Type 0-Downlink User Data (DUD), F1U-PDU Type 1- Downlink Data Delivery Status (DDDS), and F1U-PDU Type 2-Assistance Information Report (AIR) as per 3GPP NR Release 15 and onwards protocol. The DUD frame format is defined to allow the DU to perform lossless transmission of NR-U packets and is associated with the transfer of a Downlink NR PDCP PDU from the CU to the DU as shown in FIG. 1c.
[0069] The DDDS allows the DU to deliver feedback of receipt of the DUD and flow control related information as shown in FIG. 1d. The DDDS is also packaged inside the GTP extension header. Further, the AIR allows the DU to share information related to wireless channel to provide assistance in packet formation at the CU as shown in FIG. 1e. Further, the multiple PDUs allow flow control, delay reporting, and recovery of lost packets over the interface with an exchange of radio-related information to enhance the efficiency of the operations of the network.
[0070] Further, with the advent of a further increase in data demand, high bandwidth, and processing capability, it is very much viable that a future modem communication protocol system, particularly in systems beyond 5G / 6G, would be having a huge requirement for high-speed data processing. All applications like high-definition video streaming, AR / VR, holography, and digital Twin require dedicated processing and stringent Key Performance Index (KPI) requirements related to high throughput, low latency, and zero jitters, and all requirements should be met simultaneously. This requires a stricter and simpler packer processing in order to increase desired user experience. In such highly interactive immersive applications, the difference between a lost packet and a late packet is not practically present because of the synchronization required for multiple streams of the applications. All the legacy protocol stack design is focused on lossless data delivery which makes the legacy protocol stack design unsuitable for such highly interactive immersive applications. Furthermore, legacy protocols have layered processing which involves significant processing at each layer. At adjacent layers like PDCP and RLC, duplicate functionalities like windowing, reordering, status report, etc. are present which makes a few functionalities redundant in some scenarios. Thus, there is a need to simplify the processing by removing the redundancies across the complete protocol stack. Also, with an increased number of packets needs to be processed in a shortened Transmission Time Interval (TTI). Thus, there is also a need to improve the data plane processing capability in various aspects in order to achieve extremely fast processing.
[0071] Recently, there have been many approaches to improve multi-core architecture designs. However, the current state-of-the-art techniques need to be simplified and fasten the overhead of processing functionalities for future generation protocol by providing a reliable communication mechanism for the application and transport layers as well. Further, the current functionality of recovery at the RLC layer is typically to overcome a portion of residual loss from the MAC layer. The MAC layer also has a Hybrid Automatic Repeat Request (HARQ) procedure to attempt recovery at subsequent retransmissions. The higher protocol layers in 4G or 5G focus on lossless in-order packet delivery to overcome a residual MAC PDU loss, but at the cost of processing for recovery and subsequent round-trip delays added for recoveries. Simplifying the procedure is necessary to achieve the next-generation application performance without complicating the existing procedures. Simplification, optimization, and convergence are a necessity for ensuring a very lean and agile protocol stack for modem processing, that the Converged Layer 2 (CL2) achieves with a single unified layer for data plane operations.
[0072] Under such scenarios, the simplified design and clean segregation between non-real-time and real-time functionalities introduced by CL2 proved useful. The performance of CL2 increases due to the elimination of duplicate functionalities like sequence numbering, windowing mechanism, reordering, and packet discard present at both PDCP and RLC. As per the prior art, the CL2 is located along with RRC and optionally, with SDAP in CU while MAC and PHY layers are supported by DU. The CL2 provides smart header processing, i.e., header preparation / parsing, fast transfer of data, single window mechanism, soft real time processing, non-real time processing, recovery mechanism and retransmissions for AM mode, efficient reassembly in case of segmentation, duplicate detection, data security enhancements, and header compression / decompression. As per the CL2, the new Interface is required to work between Layer 2 and the MAC. However, the introduction of CL2 leads to a major change in the network architecture as the architecture requires communication between the CL2 located at the CU and the MAC located at the DU instead of the PDCP at the CU and the RLC at the DU, in comparison to the NR. However, as per the possible future option for having a Lean Protocol Stack for Next Generation immersive applications, the Layer 2 might get simplified and merged to improve performance, while MAC being real time remain closer to the Radio Unit for wireless access. This brings a requirement for new interface to be defined between Layer 2 and MAC for standardized deployment. Further, a different magnitude of packets is going to be handled over this interface requiring a need to segregate as per the priorities. However, the conventional configuration has problems, for example, there is no provision to support new functionalities, with new split options possible between CL2-MAC for next generation CU-DU option. Further, new standard interface headers for DU-CU (UL handling) are not present in the existing NR. Further, the present configuration, has the following problems as mentioned below:
[0073] Problem 1: Absence of handling of packets based on priority over F1-U interface: Existing configuration only took care of reordering or lost packet over wired interface between CU-DU (whose possibility was very low being a wired network). The CL2 performs transmission of three different types of packets, that are, Status PDUs, Retransmit PDUs, and Data PDUs, over new interface. The Status PDUs defines PDU to report the ACK and NACK to transmitting CL2 entity. The Retransmit PDUs are sent again upon receiving the NACK in Status PDU. Further, the Data PDUs are sent first time. Among the different type of packets, the order of priority goes as Status PDU > Retransmit PDU > Data PDU as shown in FIG. 1f, and an appropriate priority handling should be ensured at every level in the network to ensure proper functioning of the network. The conventional F1-U interface doesn't support prioritising one packet over another thus would lead to head-of-line blocking of high priority PDUs like Status PDUs resulting in repercussions like temporary window stall, increased jitter & latency and drop in throughput. According to yet another embodiment, FIG. 1g illustrates a structure of packets transported over the GTP Tunnel between CU and DU, in accordance with an existing art. The GTP tunnel is configured to transmit GTP extension header, GTP header, UDP header, and IP header.
[0074] Problem 2: Segmentation / fragmentation of PDUs while packaging payloads inside the Downlink User Data (DUD), in case if the packet size is different than the MTU (Maximum Transfer Unit) of the interface.
[0075] Problem 3: Absence of provision to report lost DUD Packets and Segments: There is a possibility that there could be drop of packets over the CL2-MAC interface due to congestion or TTL expiry. Further, for the case when DUD packets are segmented by CL2-MAC interface (Problem 2) there could be loss of segments over the interface. Moreover, the DDDS cannot support the segmented variant of the DUD and reports the lost packet completely on the DUD.
[0076] Problem 4: Absence of recent grant size reporting to CU entity: Furthermore, CU (CL2) is unaware of recent grant sizes. This may lead to preparation of Status PDU which is relatively larger than the recent grant sizes. Thus, either segmentation of the Status PDU happens or the Status PDU delays for unknown amount of time. The segmentation of the Status PDU is not defined in standards. Thus. the transmission of Status PDU delays till sufficient grant is received. This causes the problem of throughput drop, increased jitter and latency because of window stall. Further, this may also lead to poor performance of the network.
[0077] Problem 5: The absence of standard DU-CU interface in the receiver side. Conventionally, the DU-CU interface in receiver side is not explicitly defined. In UE complete protocol, stack (PHY, MAC, CL2) are placed together. However, in network side, the CU and DU are still placed apart but since uplink traffic is significantly lower than downlink, it was not explored further. Further, in the receiver side there is no standardised interface protocol between the DU and the CU exists. Thus, the reliable message transfer over the present interface cannot be carried out.
[0078] Additionally, multiple technical solutions have been proposed for reducing header processing overhead. In a known art, a Lean User Protocol Stack" introduced by highlighting that the "Packet Jitter", "Packet Loss" and "Data Rate fluctuations" are primary cause for disruption factors for extreme 6G user experiences. Other known arts discussed about simplifying protocol Stack for better and improved performance. However, none of the technical solutions as proposed above discloses about merging the functionalities at RAN into a single layer.
[0079] Therefore, in view of the above-mentioned problem scenarios, there lies a need to design a communication protocol for providing an interface between the CU and DU for a future-generation network with a requirement to interface CL2 with MAC.
[0080] FIG. 2 illustrates a wireless communication environment 200 comprising a Centralized Unit (CU) 210 and a Distributed Unit (DU) 220. The CU 210 and the DU 220 may be associated with a gNB within the wireless communication environment 200. The wireless communication environment 200 may be 5G or 6G network. In some embodiments, the CU 210 and the DU 220 may be functional hardware and / or software implementations within the gNB.
[0081] The CU 210 and DU 220 may exchange data over F1-U interface. Further, GPRS Tunnelling Protocol (GTP) tunnels may be utilized for exchange of data. The CU 210 may include an upper layer 212, a Converged Layer 2 (CL2) 214, and a system 218 for F1-U interface processing between the CU 210 and the DU 220. The DU 220 may include lower layers including a Medium Access Control (MAC) layer 224, and a system 228 for F1-U interface processing between the CU 210 and the DU 220.
[0082] It is appreciated that the CU 210 and the DU 220 may include additional components required for standard-based functionalities, however, the same have not be reproduced herein for sake of brevity. In some embodiments, the CU 210 and the DU 220 may be implemented as dedicated hardware units. In some embodiments, the CU 210 and the DU 220 may be implemented in the form of virtualized software units in hardware or cloud environments.
[0083] FIG. 2 further illustrates a configuration of the system 218 of the CU 210, according to one or more embodiments disclosed herein. Hereinafter, it is understood that terms including "unit" or "module" at the end may refer to the unit for processing at least one function or operation and may be implemented in hardware, software, or a combination of hardware and software.
[0084] The system 218 may include one or more processor(s) 218A (also, referred to as processor 218A), a communication unit 218B (e.g., communicator or communication interface), and a storage unit (e.g., memory 218C). The system 218 may perform functions for transmitting and receiving signals. The memory 218C may include executable instructions that, when executed by the processor, cause the system to perform the functions as described in the present disclosure. As an example, the processor 218A may be a single processing unit or a number of units, all of which could include multiple computing units. The processor 218A may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 218A is configured to fetch and execute computer-readable instructions and data stored in the memory. The processor 218A may include one or a plurality of processors. At this time, one or a plurality of processors 218A may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, and an AI-dedicated processor such as a neural processing unit (NPU). The processor 218A may control the processing of input data in accordance with a predefined operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory, i.e., the memory 218C. The predefined operating rule or artificial intelligence model is provided through training or learning.
[0085] The memory 218C may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as static random-access memory (SRAM) and dynamic random-access memory (DRAM), and / or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[0086] Further, the system 228 of the DU 220 may also include one or more processor(s) 228A (also, referred to as processor 228A), a communication unit 228B (e.g., communicator or communication interface), and a storage unit (e.g., memory 228C). The communication unit 228B may perform functions for transmitting and receiving signals. The functionalities and features of the processor 228A, communication unit 228B, and memory 228C may be similar to those of the processor 218A, communication unit 218B, and memory 218C, respectively. Therefore, a detailed explanation of the same is omitted herein for the sake of brevity of the present disclosure.
[0087] Features of the invention will not be described with reference to FIG. 2 in conjunction with the other figures.
[0088] As described above, a communication protocol for providing an interface between the CU 210 and DU is required as existing F1-U interface does not allow prioritization of one data packet over another. Further, a new method to handling concatenation and fragmentation over CU-DU interface is required. Further, a method to report loss of DUD packets and segments over the interface is required. Furthermore, a method to exchange the information related to recent average grant size to the CU over CU-DU interface is required. Moreover, a new interface protocol between DU and CU at receiver side is required.
[0089] Solution for Problem 1 - Reference is made to the solution for absence of handling of packets based on priority over F1-U interface.
[0090] According to a first aspect of the solution for problem 1, new sub-tunnels between the CU 210 and the DU 220, in particular between the CL2 layer 214 and the MAC layer 224 can be provided by having new Tunnel Endpoint Identifiers (TEIDs). This will facilitate the exchange of information on different Tunnel IDs based on Protocol Data Unit (PDU) Type.
[0091] As describe above, CL2 layer 214 may transmit three different types of packets, namely, status PDUs (PDU to report the ACK and NACK to transmitting CL2 layer), Retransmit PDUs (PDUs which are sent again upon receiving the NACK), and Data PDUs (PDUs which are sent first time). In some embodiments, the DUD may be modified by introducing a 2-bit new Information Element (IE) "Payload Type" which would allow for priority handling at both CU 210 and DU 220. The IE "Payload Type" can have the following values depending on the type of PDU packaged in the DUD:
[0092] 00 : Status PDU
[0093] 01 : Retx PDU
[0094] 10 : Data PDU
[0095] 11 : Reserved
[0096] FIG. 3a illustrates a representation of Tunnel Endpoint Identifier (TEID) of the GPRS Tunnelling Protocol (GTP) header 300 carrying the CL2 PDUs. All the messages exchanged between CU 210 and DU 220 are GTP encapsulated. In some embodiments, the system 218, in particular the processor 218A, may be configured to receive a plurality of Service Data Units (SDUs) at the CL2 layer 214 of the CU 210 from the upper layer 212. A plurality of PDUs may be generated using the received plurality of SDUs by the system 218. Each of the plurality of PDUs may be encapsulated with a GTP header. The encapsulated plurality of PDUs may include header information including a plurality of TEIDs in the GTP header.
[0097] The GTP header 300 contains a 32 byte field TEID. In some embodiments, the GTP tunnel between the CU 210 and the DU 220 remains the same for each PDU type. Priority handling at both CU 210 and DU 220 would recover for the loss. The priority would be handled in the order - Status PDU > ReTx PDU > Data PDU. As there are multiple tunnels between the CU 210 and the DU 220, the priority handling of different PDUs (Status PDU, ReTx PDU, and Data PDU) can be readily performed.
[0098] The system 218 may be configured to assign a priority to each PDU among the plurality of PDUs by allocating a value to a TEID among the plurality of TEIDs indicating a payload type flag. As seen in FIG. 3, the field UEID stands for User Equipment Identifier (UEID), RBID stands for Radio Bearer ID which uniquely specifies the Data Radio Bearer (DRB), and Payload Type specifies the type of PDU which will be carried on the particular tunnel. The Payload Type (payload type flag) may take the following values depending on type of PDU:
[0099] Status PDU - 00
[0100] ReTx PDU - 01
[0101] Data PDU - 10
[0102] In some embodiments, the value allocated to the payload type flag indicates a type of PDU being carried on a specific tunnel. The system 218 may further be configured to transmit, to the DU 220 via the F1-U interface, each PDU in an order of the assigned priority. The TEID of the GTP header 300 allows CU 210 to deliver the CL2 PDUs over the respective CL2-MAC sub-interface.
[0103] According to a second aspect of the solution for problem 1, PDU type information can be sent in Downlink User Data (DUD) from the CU 210 to the DU 220 to facilitate be prioritization. FIG. 3b illustrates a modified Downlink User Data (DUD) 310 which allows to specify the Payload Type. The system 218, in particular the processor 218A, may be configured to receive a plurality of SDUs at the CL2 layer 214 of the CU 210 from the upper layer 212. The system 218 may be configured to generate, based on the received SDUs, a DUD (say, DUD 310) including a F1-U header corresponding to a PDU. The F1-U header includes a plurality of Information Elements (IEs). The system 218 may be configured to adding a payload type flag and a PDU size flag to the plurality of IEs within the F1-U header.
[0104] As seen in FIG. 3b, the DUD 310 may include a Payload Type IE (payload type flag) and a PDU Size IE (PDU size flag) among other IEs. The modified DUD may be transmitted inside the GTP Extension header.
[0105] The Payload Type IE is a 2-bit field in which 00 corresponds to Status PDUs, 01 corresponds to ReTx PDUs, 10 corresponds to Data PDUs, and 11 is reserved. The PDU Size IE may be of 16 bit and represents the total size of PDU packed inside the DUD 310. The system 218 may be configured to assign a priority to each PDU among the plurality of the PDUs based on a type of each PDU by allocating a value in the payload type flag. The system 218 may further be configured to store a size of each PDU in the PDU size flag upon assigning the priority of each PDU. Further, the system 218 may be configured to transmit, to the DU 220 via the F1-U interface, each PDU of the DUD including the PDU size flag in the F1-U header in an order of the assigned priority.
[0106] This allows MAC layer 224 to perform packaging of PDUs to transport block efficiently by allowing MAC layer 224 to carry out prioritization of packets as well as easily figure out the packets which can be packaged and the packet which needs to be segmented. In particular, the Payload Type IE enables the MAC layer 224 to differentiate the PDUs (Status / ReTx / Data) and treat the PDUs as per their respective priority (Status PDU > ReTx PDU > Data PDU). Further, the PDU Size IE allows the MAC layer 224 to interpret the total size of the PDU.
[0107] According to a third aspect of the solution for problem 1, L1 fields of SDUs packed inside PDU to be sent in DUD header from CU to DU in DL, so that segmentation can be performed at MAC. FIG. 3c illustrates a modified Downlink User Data (DUD) 320 to specify length indicators. The system 218 may be configured to add at the CL2 layer 214 of the CU 210, a Length Indicator (LI) exist flag to the plurality of IEs within the F1-U header.
[0108] The DUD 320 may include a Payload Type IE (2 bit), a LI exist flag (1 bit), a Length IE (16 bit), a number of LI fields IE (8 bit), and a PDU Size IE (16 bit) among other IEs. The Payload Type IE is a 2-bit field in which 00 corresponds to Status PDUs, 01 corresponds to ReTx PDUs, 10 corresponds to Data PDUs, and 11 is reserved. The value of LI exist flag indicates a presence of LI fields and a number of the LI fields within the F1-U header. The PDU size IE defines the size of the whole PDU and the Length IE defines size of each SDUs packed inside the PDU. In particular, the number of LI fields IE specifies the number of SDUs (say N) packed inside the CL2 PDU and their corresponding SDU size is mentioned in Length IE, where ith SDU length is specified in ith Length IE where 1 <= i <= N.
[0109] The system 218 may be configured to assign, based on a value of the LI exist flag, corresponding values of the number of LI fields, the PDU size flag, and a length of the PDU within the F1-U header. The Length IE contains the length information of the SDUs packaged inside the PDU. the SDUs may be concatenated to form the PDUs packed inside the DUD 320. Further, the system 218 may be configured to transmit, to the DU 220 via the F1-U interface, each PDU of the plurality of PDUs after including the assigned corresponding values within the F1-U header. This information helps the MAC layer 224 in performing segmentation during grant handling and packaging the SDUs in transport block. The overhead of MAC in the evaluation of parameters like segment offset and SDU lengths in segmented packets during segmentation of the CL2 PDUs can thus be reduced.
[0110] Solution for Problem 2 - Reference is now made to the solution for handling concatenation and fragmentation over CU-DU interface based on Maximum Transfer Unit (MTU) size.
[0111] According to a first aspect of the solution for problem 2, concatenation of existing DUD into a single DUD may be performed. This may be done for the scenario where MTU sizes are larger than CL2 PDU sizes. Packaging of multiple PDUs inside single DUD will lead to reduced number of headers and would lead to fast and efficient data transfer over the interface. The MTU corresponds to a maximum size of the DUD that is being transmitted via the IP layer over F1-U interface.
[0112] The system 218, in particular the processor 218A, may be configured to receive a SDU at the CL2 layer 214 of the CU 210 from the upper layer 212. The system 218 may be configured to generate, based on the received SDU, a DUD including the F1-U header corresponding to a PDU. The F1-U header includes a plurality of IEs. The system 218 may be configured to add each of a multiple PDU exist flag, a number of PDUs field, and an individual PDU size field to the plurality of IEs within the F1-U header.
[0113] FIG. 4a illustrates a modified DUD 410 for scenario where each CL2 PDU is much smaller than the MTU size. Multiple PDUs may then be concatenated inside a single DUD Header. The modified DUD 410 may include Multiple PDUs Exist IE (1 bit), number of PDUs IE (8 bit), and Individual PDU size IE (16 bit per PDU) among other IEs. The Multiple PDUs Exist IE (multiple PDU exist flag) represents the flag whether more than 1 PDUs are packet or not in a given F1-U header. The number of PDUs IE (a number of PDUs field) represents the total number of PDUs in the header, given the Exist flag is true. The Individual PDU size IE (individual PDU size field) represents the size of each PDU in the F1-U header.
[0114] The system 218 may be configured to concatenate a plurality of PDUs into the DUD along with the F1-U header upon a determination that a combined size of the plurality of PDUs is less than a size of a MTU. The system 218 may further be configured to assign, upon concatenating the plurality of PDUs into the DUD (say, DUD 410), a value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field, respectively, within the F1-U header.
[0115] The system 218 may further be configured to transmit, after including the assigned value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field within the F1-U header, the DUD 410 including the concatenated plurality of PDUs along with the F1-U header to the DU 220 via the F1-U interface.
[0116] The concatenated header reduces the number of IP packets flowing through the network and hence the reduction in required IP processing. In other words, more data transfer with a lesser number of IP headers is possible. Thus, resulting in lower processing overhead and reduced latency.
[0117] As an example, the MTU size may be 9000 bytes and three CL2 PDUs of 3000 bytes size may be ready to be transmitted over CL2-MAC (CU-DU) interface. As per existing techniques, each of the three PDUs will be packaged inside three different DUD headers and will be sent over the interface as three different IP packets. However, as per the first aspect of the solution for problem 2, all the three CL2 PDUs can be packed inside a single DUD header and can be sent as a single IP packet. This reduces the header processing of both CL2-MAC interface and IP layer as the number of IP headers and IP processing is reduced.
[0118] According to a second aspect of the solution for problem 2, segmentation of existing DUD into a multiple DUDs may be performed. This may be done for the scenario where MTU sizes are smaller than CL2 PDU sizes. Segmentation and reassembly may be performed as part of CU-DU interface protocol. The processing overhead caused on IP layer due to fragmentation and reassembly can thus be eliminated.
[0119] The system 218 may be configured to generate a DUD including the F1-U header corresponding to a PDU. The F1-U header may include a plurality of IEs. The system 218 may be configured to add each of a Segment Offset (SO) exist flag, a last segment flag, and a SO flag to the plurality of IEs within the F1-U header.
[0120] FIG. 4b illustrates a modified DUD 420 for scenario where CL2 PDU is greater than the MTU size. The modified DUD 420 may include a Segment Offset (SO) Exist Flag IE, a Last Segment Flag (LSF) IE, a SO IE among other IEs. The SO Exist Flag IE may represent the presence of segment offset. The LSF IE may represent if a given segment is last segment. In case of first segment being last segment, the value may be True. In case of complete PDU packed inside DUD frame, LSF IE should be made true while SO Exist Flag should be set to false. In case of segmentation, SO Exist Flag is set to 0 and LSF IE is set to 0, meaning that the payload attached is segmented one and is the first segment. Further, SO Exist Flag set to 1 and LSF IE set to 0 represents a middle segment whereas SO Exist Flag set to 1 and LSF IE set to 1 represents last segment.
[0121] The system 218 may be configured to segment the DUD payload into the plurality of PDUs based on a size of the MTU. The system 218 may be configured to assign, upon segmenting the DUD into the plurality of PDUs, a value for each of the SO exist flag, the last segment flag, and the SO flag, respectively, within the F1-U header.
[0122] The system 218 may be configured to transmit, to the DU 220 via the F1-U interface, the plurality of PDUs after including the assigned value for each of the SO exist flag, the last segment flag, and the SO flag within the F1-U header.
[0123] As an example, the MTU size may be 9000 bytes and the CL2 PDU size may be 27000 bytes. The CL2 PDU may be segmented in to three smaller PDUs of 9000 bytes each. The segmented PDUs can then be sent to the DU 220 without any intermediate fragmentation by the IP layer. Moreover, performing fragmentation and reassembly by means of interface processing allows for multiple optimization during packaging of incomplete segmented PDUs at MAC layer 224.
[0124] Solution for Problem 3 - Reference is now made to the solution for reporting loss of DUD packets and segments over the CU-DU interface.
[0125] As mentioned previously, the DDDS may be utilized by the DU 220 to report the lost packets or reordered packets received on the DUD from the CU 210. In order to be compatible with modified DUDs being sent by the CU 210 (as mentioned above with respect to solutions for problems 1 and 2), the DDDS may also be modified.
[0126] According to a first aspect of the solution for problem 3, a modified DDDS is provided which is compatible with modified DUDs as per second and third aspects of solution of problem 1 and first aspect of solution for problem 2, i.e., FIGS. 3b, 3c, and 4a. The modified DDDS may support functionalities such as buffer size reporting, desired data rate, lost CL2-DUD SN report, feedback delay result, cause report and DUD SN of polling frame.
[0127] The system 228 at the DU 220 may be configured to receive a DUD at the DU 220 from the upper layer 222. The system 228 may be configured to generate a DDDS based on the received SDU. The DDDS may include a F1-U header corresponding to a plurality of PDUs. The F1-U header may include a plurality of IEs. The system 228 may be configured to add each of a CL2-U Sequence Number (SN) Ind flag, a Number of lost CL2-U SN range field, a start of lost CL2-U SN range field, an end of lost CL2-U SN range field, and a CL2-U SN of a polling frame field to the plurality of IEs.
[0128] FIG. 5a illustrates a modified DDDS 510 which can be used over the CL2-MAC interface, as per the first aspect of the solution for problem 3. The modified DDDS 510 may include CL2-U SN Ind IE, a Number of lost CL2-U SN ranges reported IE, Start of lost CL2-U SN range IE, an End of lost CL2-U SN range IE, and a CL2-U SN of Polling frame IE, among other IEs. The CL2-U SN Ind IE is a 1 bit flag that represents the SN of polling DUD frame is present in the DDDS. The Number of Lost CL2-U SN ranges reported IE represents the number of ranges of lost packets and is used when Lost Packet Report is sent. The Start of lost CL2-U SN range IE represents the first SN in the range of lost packet. The End of lost CL2-U SN range represents the last SN in the range of lost packet. The CL2-U SN of Polling frame IE represents the SN of the DUD frame which triggered DDDS through polling bit.
[0129] The system 228 may be configured to determine whether a set of PDUs among the plurality of PDUs are lost during PDU transmission from the CU 210 to the DU 220 based on the received CL2-U SN and Segment Offset of the plurality of PDUs via the F1-U interface. Further, the system 228 may be configured to assign a value for each of the CL2-U SN ID flag, the number of lost CL2-U SN range field, the start of lost CL2-U SN range field, the end of lost CL2-SN range field, and the CL2-U SN of polling frame field, respectively, within the F1-U header. After including the assigned value within the F1-U header, the DDDS along with the F1-U header may then be transmitted from the DU 220 to the CU 210 via the F1-U interface.
[0130] According to a second aspect of the solution for problem 3, a modified DDDS is provided which is compatible with modified DUDs as per second aspect of solution for problem 2, i.e., FIGS. 4b. The modified DDDS may support functionalities of the modified DDDS as per first aspect of solution for problem 3 described above. In addition, the modified DDDS may also allow reporting information on lost segments over CL2-MAC interface. That is, along with ranges of lost SNs, the modified DDDS can also specify the Segment Offsets of particular SNs to avoid retransmission of the whole PDU.
[0131] The system 228 at the DU 220 may be configured to receive a DUD at the DU 220 and generate a DDDS. The DDDS may include a F1-U header corresponding to a plurality of PDUs. The F1-U header may include a plurality of IEs. The system 228 may be configured to add a segment offset start flag and a segment offset end flag to the plurality of IEs.
[0132] FIG. 5b illustrates a modified DDDS 520 which can be used over the CL2-MAC interface, as per the second aspect of the solution for problem 3. The modified DDDS 510 may include a Segment Offset Start IE and a Segment Offset End IE among other IEs. The Segment Offset Start IE may be a 16 bit field representing the start offset of the CL2-DUD PDU. The Segment Offset End IE may be a 16 bit field to represent the end of the segment offset of the CL2-DUD PDU. Additional IEs may include CL2-U Seg Ind flag IE to indicate the presence of segment offsets in the DDDS and Lost CL2-U Sequence Number IE to represent the sequence number of the segment.
[0133] The system 228 may be configured to determine a range of the set of segmented PDUs that are lost during the PDU transmission. The system 228 may further be configured to assign a value to each of the segment offset start flag and the segment offset end flag based on the determined range of the set of segmented PDUs. After including the assigned value corresponding to each of the segment offset start flag and the segment offset end flag within the F1-U header, the DDDS 520 may be transmitted along with the F1-U header to the CU 210 via the F1-U interface.
[0134] The modified DDDS allows to report segment offset of the each lost NR-U SN packet in addition to the ranges. The SNs which are reported through segment field need not be reported as part of the range. In some embodiments, the IEs may be reported for each segment individually. That is, if the Number of Lost CL2-U Segments is 'S' then the above IEs will be written for all 'S' separately in increasing order of SN, and in case SNs are the same, the order should be based on SO.
[0135] Solution for Problem 4 - Reference is now made to the solution for exchanging the information related to recent average grant size to the CU over CU-DU interface.
[0136] According to an aspect of the solution for problem 4, Status PDU size can be generated based on average grant size received from DU 220 as Assistance Information. An Assistance Information Report can be generated and sent to the CU 210, thereby allowing exchange of channel related information between the DU 220 and the CU 210.
[0137] The system 228 at the DU 220 may be configured to receive a DUD frame with Assistance Information Reporting Flag set to true. Further, the system 228 may be configured to generate an Assistance Information Report (AIR) including a F1-U header. The F1-U header includes an IE indicating an average grant size flag corresponding to the MAC in the DU 220. In some embodiments, the F1-U header may also include an Assistance Information Type IE which is a 1 byte field representing the radio quality assistance information.
[0138] The system 228 may be configured to determine a value assigned to the average grant size flag and add, within the F1-U header, the value of average grant size flag in the AIR. The average grant size may correspond to the recent average grant sizes allocated. The system 228 may be configured to transmit the generated AIR to the CU 210 via an F1-U interface. The reporting of average grant size would allow the CU 210 having the CL2 layer 214 to prepare Status PDUs of the appropriate size. Additionally, the Concatenation Index value can be determined while preparing the PDUs.
[0139] Solution for Problem 5 - Reference is now made to the solution for a new interface protocol between the DU and the CU at receiver side.
[0140] According to an aspect of the solution for problem 5, an interface is defined for receiver side where the DU 220 is the transmitter and the CU 210 is the receiver. The synchronization between the DU 220 (MAC) and the CU 210 (CL2) may be increased. Further, two PDU may be defined for transmitting over the interface. The PDU may include Upstream User Data (UUD) and Upstream Data Delivery Status (UDDS).
[0141] The system 228 at the DU 220 may be configured to receive a plurality of PDUs and generate an UUD including F1-U header and a plurality of SDUs. The F1-U header includes a plurality of IEs and the system 228 may be configured to add each of a PDU type flag, a Retransmission (ReTx) flag, a Report Polling flag, and a MAC-U Sequence Number (SN) flag to the plurality of IEs within the F1-U header.
[0142] FIG. 6a illustrates a UUD PDU frame 610 having F1-U header. The UUD PDU 610 may include PDU Type IE, ReTx Flag IE, Report Polling Flag IE, and MAC-U SN among other IEs. The PDU Type IE may be a single-bit field, where 0 represents the UUD frame. The ReTx Flag IE may be a single-bit field representing whether the current UUD is a retransmission of a previously sent UUD or not. If the Flag is set to 1 then it means the attached payload to the UUD frame is a retransmission. The Report Polling Flag IE may be a single-bit flag to request receiving entity (CL2) to reply with UDDS. The MAC-U SN IE may be a 16 bit field to assign each DUD with a SN.
[0143] The system 228 may be configured to assign, based on the UUD, a value to each of the PDU type flag, the ReTx flag, the Report Polling flag, and the MAC-U SN flag, respectively, within the F1-U header. The system 228 may be configured to send, via the F1-U interface, the UUD including the assigned value to the upper layer 212 at the CU 210. The UUD 610 allows carrying data from MAC to CL2 over standard MAC-CL2 interface and ensure lossless delivery over the MAC-CL2 interface, at least f or Status PDUs.
[0144] The system 218 at the CU 210 may be configured to receive the UUD from the lower layer. The system 218 may be configured to generate an UDDS based on the received UUD. The UDDS may include an F1-U header and a plurality of PDUs. The F1-U header includes a plurality of IEs. The system 218 may be configured to add each of a PDU type flag, a desired data rate flag, a desired buffer size flag, a lost MAC-U flag to the plurality of IEs within the F1-U header.
[0145] FIG. 6b illustrates an UDDS PDU frame 620 having F1-U header. The UDDS PDU 620 may include PDU Type IE, Desired Data Rate IE, Desired Buffer Size IE, and Lost MAC-U IE among other IEs. The PDU type IE is a 1 bit flag representing the PDU type, in this case. Type 1 in the flag may correspond to UDDS. The Desired Data Rate IE is used for flow control. The Desired Buffer Size IE is used to report the buffer size. The Lost MAC-U IE may be used to report SN ranges.
[0146] The system 218 may be configured to assign a value to each of the PDU type flag, the desired data rate flag, the desired buffer size flag, and the lost MAC-U flag, respectively, within the F1-U header. The system 218 may be configured to sending, via the F1-U interface, the UDDS including the assigned value to a MAC layer 224 of the DU 220. The UDDS 620 may be used for acknowledgement of the received PDU as well as reporting the Lost PDUs over MAC-CL2 interface. The UDDS 620 may also be useful for performing flow control over the interface.
[0147] Thus, lossless transfer of the PDUs over the interface can be achieved, particularly for the case of buffer overflow and the interface being lossy (air interface). Further, the interface would enable recovery of packets.
[0148] FIG. 7a illustrates a method 700 for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in a wireless communication network, in accordance with an embodiment of the present disclosure. The method 700 may be performed by the system 218 at the CU 210. The method 700 may correspond to the first aspect of the solution for problem 1.
[0149] The method 700 includes a series of operations shown at step 702 through step 710 of FIG. 7a. The method 700 begins at step 702 where the method includes receiving, at the Converged Layer 2 (CL2) of the CU, the plurality of Service Data Units (SDUs) from the upper layer. At step 704, the method includes generating the plurality of Protocol Data Units (PDUs) using the received SDUs.
[0150] At step 706, the method 700 includes encapsulating each of the plurality of PDUs with a GPRS Tunnelling Protocol (GTP) header. Each of the encapsulated plurality of PDUs includes the header information including the plurality of Tunnel Endpoint Identifiers (TEIDs) in the GTP header.
[0151] At step 708, the method 700 includes assigning the priority to each PDU among the plurality of PDUs by allocating the value to the TEID among the plurality of TEIDs indicating the payload type flag. The TEID include the plurality of User Entity IDs (UEIDs), a Radio Bearer ID (RBID), and the payload type flag. The value allocated to the payload type flag indicates a type for PDU being carried on a specific tunnel.
[0152] Further, at step 710, the method 700 includes transmitting, to the DU via the F1-U interface, each PDU among the plurality of PDUs in an order of the assigned priority.
[0153] FIG. 7b illustrates a method 720 performed for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in the wireless communication network, in accordance with an embodiment of the present disclosure. The method 720 may be performed by the system 218 at the CU 210. The method 720 may correspond to the second aspect of the solution for problem 1.
[0154] The method 720 includes a series of operations shown at step 722 through step 732 of FIG. 7b. The method 720 begins at step 722 and includes receiving, from the upper layer, a Service Data Unit (SDU) at the Converged Layer 2 (CL2) of the CU. At step 724, the method 720 includes generating, based on the received SDU, the Downlink User Data (DUD) including the F1-U header corresponding to the Protocol Data unit (PDU), the F1-U header includes the plurality of Information Elements (IEs).
[0155] At step 726, the method 720 includes adding the payload type flag and the PDU size flag to the plurality of IEs within the F1-U header. At step 728, the method 720 includes assigning the priority to each PDU among the plurality of the PDUs based on the type of each PDU by allocating the value in the payload type flag.
[0156] At step 730, the method 720 includes storing the size of each PDU in the PDU size flag upon assigning the priority of each PDU. Further, at step 732, the method 720 includes transmitting, to the DU via the F1-U interface, each PDU of the DUD including the PDU size flag in the F1-U header in an order of the assigned priority.
[0157] With respect to the third aspect of the solution for problem 1, for each PDU among the plurality of PDUs, the method 720 includes adding, at the CL2 of the CU, the Length Indicator (LI) exist flag to the plurality of IEs within the F1-U header, where the value of LI exist flag indicates the presence of LI fields and the number of the LI fields within the F1-U header. The method 720 includes assigning, based on the value of the LI exist flag, corresponding values of the number of LI fields, the PDU size flag, and the length of the PDU within the F1-U header. The method 720 further includes transmitting, to the DU via the F1-U interface, each PDU of the plurality of PDUs after including the assigned corresponding values within the F1-U header.
[0158] FIG. 8 illustrates a method 800 performed for F1-U interface processing between the Centralized Unit (CU) and the Distributed Unit (DU) in the wireless communication network, in accordance with an embodiment of the present disclosure. The method 800 may be performed by the system 218 at the CU 210. The method 800 may correspond to the first aspect of the solution for problem 2.
[0159] The method 800 includes a series of operations shown at step 802 through step 812. The method 800 begins at step 802 that includes receiving, from the upper layer, a Service Data Unit (SDU) at the Converged Layer 2 (CL2) of the CU. At step 804, the method 800 includes generating, based on the received SDU, the Downlink User Data (DUD) including the F1-U header corresponding to the Protocol Data unit (PDU), the F1-U header includes a plurality of Information Elements (IEs).
[0160] At step 806, the method 800 includes adding each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field to the plurality of IEs within the F1-U header. At step 808, the method 800 includes concatenating the plurality of PDUs into the DUD along with the F1-U header upon the determination that the combined size of the plurality of PDUs is less than the size of the Maximum Transfer Unit (MTU), where the MTU corresponds to the maximum size of the DUD that is being transmitted via the IP layer over F1-U interface.
[0161] At step 810, the method 800 includes assigning, upon concatenating the plurality of PDUs into the DUD, the value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field, respectively, within the F1-U header. Further, at step 812, the method 800 includes transmitting, after including the assigned value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field within the F1-U header, the DUD including the concatenated plurality of PDUs along with the F1-U header to the DU via the F1-U interface.
[0162] With respect to the second aspect of the solution for problem 2, the method 800 includes adding each of a Segment Offset (SO) exist flag, a last segment flag, and a SO flag to the plurality of IEs within the F1-U header. The method 800 includes segmenting the DUD payload into the plurality of PDUs based on the size of the MTU, where the size of each of the plurality of PDUs is less than the size of the MTU. The method 800 includes assigning, upon segmenting the DUD into the plurality of PDUs, the value for each of the SO exist flag, the last segment flag, and the SO flag, respectively, within the F1-U header. The method 800 includes transmitting, to the DU via the F1-U interface, the plurality of PDUs after including the assigned value for each of the SO exist flag, the last segment flag, and the SO flag within the F1-U header.
[0163] FIG. 9 illustrates a method 900 for F1-U interface processing between the Distributed Unit (DU) and the Centralized Unit (CU) in the wireless communication network, in accordance with an embodiment of the present disclosure. The method 900 may be performed by the system 228 at the DU 220. The method 900 may correspond to the first aspect of the solution for problem 3.
[0164] The method 900 includes a series of operations shown at step 902 through step 912. The method 900 begins at step 902 and includes receiving, from the upper layer, the Downlink User Data (DUD) at the DU. At step 904, the method 900 includes generating, based on the received SDU, the Downlink Data Delivery Status (DDDS) including the F1-U header corresponding to the plurality of Protocol Data units (PDUs), the F1-U header includes the plurality of Information Elements (IEs).
[0165] At step 906, the method 900 includes adding, to the plurality of IEs within the F1-U header based on the determination of receiving the DDDS, each of the CL2-U Sequence Number (SN) Ind flag, the number of lost CL2-U SN range field, the start of lost CL2-U SN range field, the end of lost CL2-U SN range field, and the CL2-U SN of the polling frame field. At step 908, the method 900 includes determining whether the set of PDUs among the plurality of PDUs are lost during PDU transmission from the CU to the DU based on the received CL2-U SN and Segment Offset of the plurality of PDUs via the F1-U interface.
[0166] At step 910, the method 900 includes assigning, upon the determination that the set of PDUs are lost during the PDU transmission, the value for each of the CL2-U SN ID flag, the number of lost CL2-U SN range field, the start of lost CL2-U SN range field, the end of lost CL2-SN range field, and the CL2-U SN of polling frame field, respectively, within the F1-U header. At step 912, the method 900 includes transmitting, from the DU to the CU via the F1-U interface, the DDDS along with the F1-U header after including the assigned value within the F1-U header.
[0167] With respect to the second aspect of the solution for problem 3, the method 900 includes determining a range of the set of segmented PDUs that are lost during the PDU transmission. The method includes adding, within the F1-U header, a segment offset start flag and the segment offset end flag to the plurality of IEs. The method 900 includes assigning, based on the determined range of the set of segmented PDUs, a value to each of the segment offset start flag and the segment offset end flag. The method 900 includes transmitting, to the CU via the F1-U interface, the DDDS along with the F1-U header after including the assigned value corresponding to each of the segment offset start flag and the segment offset end flag within the F1-U header.
[0168] FIG. 10 illustrates a method 1000 for F1-U interface processing between the Distributed Unit (DU) and the Centralized Unit (CU) in the wireless communication network, in accordance with an embodiment of the present disclosure. The method 1000 may be performed by the system 228 at the DU 220. The method 1000 may correspond to the solution for problem 4.
[0169] The method 1000 includes a series of operations shown at step 1002 through step 1010. The method 1000 begins at step 1002 and includes receiving, from the upper layer, at the DU, the Downlink User Data (DUD) frame with the Assistance Information Reporting Flag set to true. At step 1004, the method 1000 includes generating, the Assistance Information Report (AIR) including the F1-U header, the F1-U header includes an Information Element (IE) indicating an average grant size flag corresponding to the MAC in DU.
[0170] At step 1006, the method 1000 include determining a value assigned to the average grant size flag. At step 1008, the method 1000 includes adding, within the F1-U header, the value of average grant size flag in AIR. At step 1010, the method 1000 includes transmitting the generated AIR to the CU via the F1-U interface.
[0171] FIG. 11 illustrates a method 1100 for F1-U interface processing between the Distributed Unit (DU) and the Centralized Unit (CU) in the wireless communication network, in accordance with an embodiment of the present disclosure. The method 1100 may be performed by the system 228 at the DU 220. The method 1100 may correspond to the first aspect of the solution for problem 5.
[0172] The method 1100 includes a series of operations shown at step 1102 through step 1110. The method 1100 begins at step 1102 and includes receiving the plurality of Protocol Data Units (PDU). At step 1104, the method 1100 includes generating, based on the received PDUs, the Upstream / Uplink User Data (UUD) including the F1-U header and the plurality of Service Data units (SDUs), the F1-U header includes a plurality of Information Elements (IEs).
[0173] At step 1106, the method 1100 includes adding, within the F1-U header, each of the PDU type flag, the Retransmission (ReTx) flag, the Report Polling flag, and the MAC-U Sequence Number (SN) flag to the plurality of IEs. At step 1108, the method 1100 includes assigning, based on the UUD, a value to each of the PDU type flag, the ReTx flag, the Report Polling flag, and the MAC-U SN flag, respectively, within the F1-U header. At step 1110, the method 1100 includes sending, via the F1-U interface, the UUD including the assigned value to the upper layer at CU.
[0174] FIG. 12 illustrates a method 1200 for F1-U interface processing between the Centralized Unit (DU) and the Distributed Unit (CU) in the wireless communication network, in accordance with an embodiment of the present disclosure. The method 1200 may be performed by the system 218 at the CU 210. The method 1200 may correspond to the second aspect of the solution for problem 5.
[0175] The method 1200 includes a series of operations shown at step 1202 through step 1210. The method 1200 begins at step 1202 and includes receiving the Upstream User Data (UUD) from the lower layer. At step 1204, the method 1200 generating, based on the received UUD, the Upstream Data Delivery Status (UDDS) including the F1-U header and the plurality of Protocol Data units (PDUs), the F1-U header includes the plurality of Information Elements (IEs).
[0176] At step 1206, the method 1200 includes adding, within the F1-U header, each of the PDU type flag, the desired data rate flag, the desired buffer size flag, the lost MAC-U flag to the plurality of IEs. At step 1208, the method 1200 includes assigning the value to each of the PDU type flag, the desired data rate flag, the desired buffer size flag, and the lost MAC-U flag, respectively, within the F1-U header. At step 1210, the method 1200 includes sending, via the F1-U interface, the UDDS including the assigned value to the Medium Access Control (MAC) layer of the DU.
[0177] The methods describe above can be performed by programmed computing devices, for example, based on instructions retrieved from non-transitory computer readable media. The computer readable media can include machine-executable or computer-executable instructions to perform all or portions of the described method. The computer readable media may be, for example, digital memories, magnetic storage media, such as magnetic disks and magnetic tapes, hard drives, or optically readable data storage media.
[0178] While the above discussed steps in FIGS. 7a-12 are shown and described in a particular sequence, the steps may occur in variations to the sequence in accordance with various embodiments. Further, a detailed description related to the various steps of FIGS. 7a-12 is already covered in the description related to FIGS. 2-6b and is omitted herein for the sake of brevity.
[0179] The present disclosure thus provides the following:
[0180] ● The new fields which are introduced to handle the packet types related to Status PDU, Retransmission PDU and New Transmission PDU on an interface which is managing data exchange between CL2 layer and MAC layer in order to avoid head of line blocking issues, in case if priority is not applied.
[0181] ● New functionality to support concatenation as well as segmentation in case if the MTU size is different than the PDU size being sent from CL2 to MAC, such that new additional fields are required to be captured to inform about the number of packets which are packed in case of concatenation, whereas the segmented information in case if the packet is segmented.
[0182] ● New additional Assistance Information report like Average Grant Size to be added in the Assistance Information Report over F1-U interface.
[0183] ● New recovery procedures in place in case if the recovery of the concatenated packets or segments need to be performed and its impact on the reporting procedure.
[0184] ● New header structures defined for supporting data exchange and account for ordering between MAC-CL2 in UL direction at the NW deployment to handle better packet management.
[0185] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device, or a combination of hardware device and software module.
[0186] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.
[0187] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.
[0188] Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.
[0189] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.
[0190] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
Claims
1.A method performed by a centralized unit (CU) of a base station in a wireless communication network, the method comprising:receiving, from an upper layer, at least one service data unit (SDU);generating at least one protocol data unit (PDU) based on the at least one received SDU;encapsulating the at least one PDU with a general packet radio service (GPRS) tunneling protocol (GTP) header, wherein the at least one encapsulated PDU includes header information associated with at least one tunnel endpoint identifier (TEID) in the GTP header;assigning a priority to each PDU among the at least one PDU by allocating a value to a TEID among the at least one TEID; andtransmitting, to a distributed unit (DU) of the base station via an F1-U interface, each PDU among the at least one PDU based on the priority to each PDU.2.The method of claim 1,wherein the TEID includes at least one an user entity ID (UEID), a radio bearer ID (RBID), or a payload type flag, andwherein the value allocated to the payload type flag indicates a type of PDU being carried on a tunnel.3.The method of claim 1,wherein the type of PDU indicates at least one of a status PDU, a retransmit PDU, or a data PDU,wherein the status PDU is a PDU for reporting an acknowledgement (ACK) or a negative acknowledgement (NACK) to a converged layer 2 (CL2) of the CU,wherein the retransmit PDU is a PDU retransmitted based on the NACK, andwherein the data PDU is a PDU transmitted at a first time.4.A method performed by a centralized unit (CU) of a base station in a wireless communication network, the method comprising:receiving, from an upper layer, at least one service data unit (SDU);based on the at least one received SDU, generating, at least one downlink user data (DUD) including an F1-U header corresponding to each protocol data unit (PDU) among the at least one PDU, wherein each PDU among the at least one PDU is generated based on the at least one received SDU;adding a payload type flag and a PDU size flag to the F1-U header corresponding to each PDU;assigning a priority to each PDU among the at least one PDU based on a type of each PDU by allocating a value to the payload type flag;storing a size of each PDU in the PDU size flag based on the priority of each PDU; andtransmitting, to a distributed unit (DU) of the base station via an F1-U interface, each PDU of the DUD including the PDU size flag in the F1-U header based on the priority of each PDU.5.The method of claim 4, the method further comprising:adding, a length indicator (LI) exist flag to the F1-U header, wherein a value of the LI exist flag is associated with a presence of LI fields and a number of the LI fields in the F1-U header;based on the value of the L1 exist flag, assigning a value for each of the number of LI fields, the PDU size flag, and a length of the PDU in the F1-U header; andtransmitting, to the DU of the base station via the F1-U interface, each PDU of the DUD.6.The method of claim 5,wherein the number of LI fields is associated with a number of SDU in the PDU corresponding to the F1-U header,wherein the PDU size flag is associated with a size of a whole PDU corresponding to the F1-U header, andwherein the length of the PDU is associated with a size of each SDU in the PDU corresponding to the F1-U header.7.A method performed by a centralized unit (CU) of a base station in a wireless communication network, the method comprising:generating downlink user data (DUD) including an F1-U header corresponding to a protocol data unit (PDU);adding a multiple PDU exist flag, a number of PDUs field, and an individual PDU size field to the F1-U header;concatenating at least one PDU into the DUD with the F1-U header based on a combined size of the at least one PDU;based on the concatenation, assigning a value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field in the F1-U header; andtransmitting, to a distributed unit (DU) of the base station via an F1-U interface, the DUD including the at least one concatenated PDU with the F1-U header.8.The method of claim 7,wherein the at least one PDU is concatenated into the DUD with the F1-U header, in case that the combination size of the at least one PDU is less than a size of a maximum transfer unit (MTU), andwherein the MTU is associated with a maximum size of the DUD being transmitted via an internet protocol (IP) layer over the F1-U interface.9.The method of claim 7, further comprising:adding each of a segment offset (SO) exist flag, a last segment flag, and a SO flag to the F1-U header;segmenting a DUD payload into the at least one PDU based on a size of a MTU, wherein a size of each of the at least one PDU is less than the size of the MTU;based on the segmentation, assigning a value for each of the SO exist flag, the last segment flag, and the SO flag in the F1-U header; andtransmitting, to the DU of the base station via the F1-U interface, the at least one PDU.10.A centralized unit (CU) of a base station in a wireless communication network, the CU comprising:a transceiver; anda controller configured to:receive, from an upper layer, at least one service data unit (SDU),generate at least one protocol data unit (PDU) based on the at least one received SDU,encapsulate the at least one PDU with a general packet radio service (GPRS) tunneling protocol (GTP) header, wherein the at least one encapsulated PDU includes header information associated with at least one tunnel endpoint identifier (TEID) in the GTP header,assign a priority to each PDU among the at least one PDU by allocating a value to a TEID among the at least one TEID, andtransmit, to a distributed unit (DU) of the base station via an F1-U interface, each PDU among the at least one PDU based on the priority to each PDU.11.The CU of claim 10,wherein the TEID includes at least one an user entity ID (UEID), a radio bearer ID (RBID), or a payload type flag, andwherein the value allocated to the payload type flag indicates a type of PDU being carried on a tunnel,wherein the type of PDU indicates at least one of a status PDU, a retransmit PDU, or a data PDU,wherein the status PDU is a PDU for reporting an acknowledgement (ACK) or a negative acknowledgement (NACK) to a converged layer 2 (CL2) of the CU,wherein the retransmit PDU is a PDU retransmitted based on the NACK, andwherein the data PDU is a PDU transmitted at a first time.12.A centralized unit (CU) of a base station in a wireless communication network, the CU comprising:a transceiver; anda controller configured to:receive, from an upper layer, at least one service data unit (SDU),based on the at least one received SDU, generate, at least one downlink user data (DUD) including an F1-U header corresponding to each protocol data unit (PDU) among the at least one PDU, wherein each PDU among the at least one PDU is generated based on the at least one received SDU,add a payload type flag and a PDU size flag to the F1-U header corresponding to each PDU,assign a priority to each PDU among the at least one PDU based on a type of each PDU by allocating a value to the payload type flag,store a size of each PDU in the PDU size flag based on the priority of each PDU; andtransmit, to a distributed unit (DU) of the base station via an F1-U interface, each PDU of the DUD including the PDU size flag in the F1-U header based on the priority of each PDU.13.The CU of claim 12, wherein the controller is further configured to:add, a length indicator (LI) exist flag to the F1-U header, wherein a value of the LI exist flag is associated with a presence of LI fields and a number of the LI fields in the F1-U header,based on the value of the L1 exist flag, assign a value for each of the number of LI fields, the PDU size flag, and a length of the PDU in the F1-U header, andtransmit, to the DU of the base station via the F1-U interface, each PDU of the DUD,wherein the number of LI fields is associated with a number of SDU in the PDU corresponding to the F1-U header,wherein the PDU size flag is associated with a size of a whole PDU corresponding to the F1-U header, andwherein the length of the PDU is associated with a size of each SDU in the PDU corresponding to the F1-U header.14.A centralized unit (CU) of a base station in a wireless communication network, the CU comprising:a transceiver; anda controller configured to:generate downlink user data (DUD) including an F1-U header corresponding to a protocol data unit (PDU),add a multiple PDU exist flag, a number of PDUs field, and an individual PDU size field to the F1-U header,concatenate at least one PDU into the DUD with the F1-U header based on a combined size of the at least one PDU,based on the concatenation, assign a value for each of the multiple PDU exist flag, the number of PDUs field, and the individual PDU size field in the F1-U header, andtransmit, to a distributed unit (DU) of the base station via an F1-U interface, the DUD including the at least one concatenated PDU with the F1-U header.15.The CU of claim 14, wherein the controller is further configured to:add each of a segment offset (SO) exist flag, a last segment flag, and a SO flag to the F1-U header,segment a DUD payload into the at least one PDU based on a size of a MTU, wherein a size of each of the at least one PDU is less than the size of the MTU,based on the segmentation, assign a value for each of the SO exist flag, the last segment flag, and the SO flag in the F1-U header, andtransmit, to the DU of the base station via the F1-U interface, the at least one PDU,wherein the at least one PDU is concatenated into the DUD with the F1-U header, in case that the combination size of the at least one PDU is less than a size of a maximum transfer unit (MTU), andwherein the MTU is associated with a maximum size of the DUD being transmitted via an internet protocol (IP) layer over the F1-U interface.
Citation Information
Patent Citations
PDCP Packet-Based DDDS Frame Transmission
US20210266779A1
Preventing / mitigating packet loss in integrated access backhaul (IAB) networks
US20210274381A1
