Embodiments herein provide a method and a UE for handling of integrity check failures of Packet Data Convergence Protocol (PDCP) Protocol Data Units (PDUs) in a wireless communication system. The method includes performing an integrity check at a PDCP layer on at least one Radio Bearer based on a Message Authentication Code-Integrity (MAC-I) of the PDCP PDU. The method includes determining a success of integrity check of the PDCP PDU or a failure of integrity check of the PDCP PDU received on the radio bearer. Further, the method includes discarding the PDCP PDU for which integrity is check failed. Furthermore, the method includes indicating a Radio Resource Control (RRC) layer about the integrity check failure on the at least one radio bearer in response to determining a trigger condition.

A device generates a remote direct memory access (RDMA) packet, where a payload part of the RDMA packet includes a plurality of data blocks and protection information (PI) corresponding to each of the plurality data blocks in to-be-sent data; or a payload part of the RDMA packet includes one data unit or a part of data in the data unit of to-be-sent data, the data unit includes one data block and PI corresponding to the data block, and a length of the data unit is equal to an integer multiple of a length of the part of data; and sends the RDMA packet.

A device generates a remote direct memory access (RDMA) packet, where a payload part of the RDMA packet includes a plurality of data blocks and protection information (PI) corresponding to each of the plurality data blocks in to-be-sent data; or a payload part of the RDMA packet includes one data unit or a part of data in the data unit of to-be-sent data, the data unit includes one data block and PI corresponding to the data block, and a length of the data unit is equal to an integer multiple of a length of the part of data; and sends the RDMA packet.

Datalink frames or networking packets contain protocol information in the header and optionally in the trailer of a frame or a packet. We are proposing a method in which part of or all of the protocol information corresponding to a frame or a packet is transmitted separately in another datalink frame. The “Separately Transmitted Protocol Information” is referred to as STPI. The STPI contains enough protocol information to identify the next hop node or port. STPI can be used avoid network congestion and improve link efficiency. Preferably, there will be one datalink frame or network packet corresponding to each STPI, containing the data and the rest of the protocol information and this frame/packet is referred to as DFoNP. The creation of STPI and DFoNP is done by the originator of the frame or packet such as an operating system.

Datalink frames or networking packets contain protocol information in the header and optionally in the trailer of a frame or a packet. We are proposing a method in which part of or all of the protocol information corresponding to a frame or a packet is transmitted separately in another datalink frame. The “Separately Transmitted Protocol Information” is referred to as STPI. The STPI contains enough protocol information to identify the next hop node or port. STPI can be used avoid network congestion and improve link efficiency. Preferably, there will be one datalink frame or network packet corresponding to each STPI, containing the data and the rest of the protocol information and this frame/packet is referred to as DFoNP. The creation of STPI and DFoNP is done by the originator of the frame or packet such as an operating system.

A method is disclosed for the collection of performance metrics by establishing service operations administration and maintenance (OAM) sessions between an actuator and a plurality of reflectors in a communication network. Test packets from an actuator simultaneously reach a plurality of reflectors along a test path. Each single test packet results into a plurality of test results, one per reflector, with quasi-synchronous performance metrics to sectionalize a network and more efficiently isolate fault or performance problems without the need for additional test packets to isolate the issue. Another method is disclosed wherein an actuator generates and transmits a plurality of simultaneous test packets, one per NID device, resulting into a plurality of test results, one per reflector, with quasi-synchronous performance metrics to sectionalize a network and more efficiently isolate fault or performance problems without the need for additional test packets to isolate the issue.

To provide a low latency near RT RIC, some embodiments separate the RIC's functions into several different components that operate on different machines (e.g., execute on VMs or Pods) operating on the same host computer or different host computers. Some embodiments also provide high speed interfaces between these machines. Some or all of these interfaces operate in non-blocking, lockless manner in order to ensure that critical near RT RIC operations (e.g., datapath processes) are not delayed due to multiple requests causing one or more components to stall. In addition, each of these RIC components also has an internal architecture that is designed to operate in a non-blocking manner so that no one process of a component can block the operation of another process of the component. All of these low latency features allow the near RT RIC to serve as a high speed IO between the E2 nodes and the xApps.

To provide a low latency near RT RIC, some embodiments separate the RIC's functions into several different components that operate on different machines (e.g., execute on VMs or Pods) operating on the same host computer or different host computers. Some embodiments also provide high speed interfaces between these machines. Some or all of these interfaces operate in non-blocking, lockless manner in order to ensure that critical near RT RIC operations (e.g., datapath processes) are not delayed due to multiple requests causing one or more components to stall. In addition, each of these RIC components also has an internal architecture that is designed to operate in a non-blocking manner so that no one process of a component can block the operation of another process of the component. All of these low latency features allow the near RT RIC to serve as a high speed IO between the E2 nodes and the xApps.

Embodiments of apparatus and method for data plane management are disclosed. In one example, an apparatus for communication both uplink and downlink can include a plurality of downlink clusters, each downlink cluster including a downlink cluster processor configured to process three or more downlink data layers. The apparatus can also include a plurality of uplink clusters, each uplink cluster including an uplink cluster processor configured to process three or more uplink data layers. The apparatus can further include a controller configured to scale the plurality of downlink clusters and configured to scale the plurality of uplink clusters. Scaling the plurality of downlink clusters and the plurality of uplink clusters can include activating or deactivating one or more clusters of the plurality of downlink clusters, the plurality of uplink clusters, or both the plurality of downlink clusters and the plurality of uplink clusters.

Systems, apparatuses, and methods are described for wireless communications. A base station and wireless device may communicate capability information associated with a wireless device. The capability information may include information indicating support for an Ethernet type packet data unit session or header parameter compression. An Ethernet type packet data unit session may be instantiated based on the capability information.