A method includes determining a delivery performance of a data flow being transmitted from a first network equipment to a second network equipment over a network; determining whether the network is congested based on the determined delivery performance of the data flow being transmitted to the second network equipment; and pacing delivery of the data flow to the second network equipment by reducing a rate at which the data flow is delivered to the second network equipment when the network is determined to be congested.

A method includes determining a delivery performance of a data flow being transmitted from a first network equipment to a second network equipment over a network; determining whether the network is congested based on the determined delivery performance of the data flow being transmitted to the second network equipment; and pacing delivery of the data flow to the second network equipment by reducing a rate at which the data flow is delivered to the second network equipment when the network is determined to be congested.

Embodiments herein provide a method for CLAT Aware Affinity (CAA)-based scheduling by a user equipment (UE) (100) comprising a multi-core processor (120). The method includes a CAA scheduler (180) at the user equipment (100) receiving a packet and determining a path characteristic of the packet. Further, the method includes the CAA scheduler (180) determining, at least one of a IPv4 connection and a IPv6 connection based the path characteristic of the packet; and establishing a connection to at least one of an IPv4 server and an IPv6 server based on the determined at least one of the IPv4 connection and the IPv6 connection. Further, the method includes the CAA scheduler (180) classifying the packet into at least one class and scheduling the packet on at least one core of the multi-core processor (120) based on the at least one class.

Embodiments herein provide a method for CLAT Aware Affinity (CAA)-based scheduling by a user equipment (UE) (100) comprising a multi-core processor (120). The method includes a CAA scheduler (180) at the user equipment (100) receiving a packet and determining a path characteristic of the packet. Further, the method includes the CAA scheduler (180) determining, at least one of a IPv4 connection and a IPv6 connection based the path characteristic of the packet; and establishing a connection to at least one of an IPv4 server and an IPv6 server based on the determined at least one of the IPv4 connection and the IPv6 connection. Further, the method includes the CAA scheduler (180) classifying the packet into at least one class and scheduling the packet on at least one core of the multi-core processor (120) based on the at least one class.

A method for communicating between apparatuses, comprises: in a first apparatus, generating a second packet according to a second protocol, the second packet including a first packet according to a first protocol; in the first apparatus, sending the generated second packet to a second apparatus; in the second apparatus, receiving the second packet; in the second apparatus, determining whether a response to the first packet included in the second packet is possible; and in the second apparatus, in a case where it is determined that a response to the first packet is impossible, including status information corresponding to a cause for the impossibility of the response in a response packet corresponding to the second packet and sending the response packet to the first apparatus.

A method for communicating between apparatuses, comprises: in a first apparatus, generating a second packet according to a second protocol, the second packet including a first packet according to a first protocol; in the first apparatus, sending the generated second packet to a second apparatus; in the second apparatus, receiving the second packet; in the second apparatus, determining whether a response to the first packet included in the second packet is possible; and in the second apparatus, in a case where it is determined that a response to the first packet is impossible, including status information corresponding to a cause for the impossibility of the response in a response packet corresponding to the second packet and sending the response packet to the first apparatus.

An example network device receives an encapsulated network packet via a network tunnel; extracts IPv6 header information from the encapsulated network packet; extracts IPv4 header information from the encapsulated network packet; determines that the encapsulated network packet is a spoofed network packet based on the IPv6 header information and the IPv4 header information; and in response to detecting the spoofed network packet, transmits a message to a Tunnel Entry Point (TEP) device, the message including data representing the IPv6 header information and IPv4 header information. A tunnel entry point (TEP) device may receive the message and use the message to detect spoofed IPv6 traffic, e.g., when an IPv6 header and an IPv4 header of an encapsulated packet matches the IPv6 header and the IPv4 header specified in the message. In this manner, the TEP device may block, rate limit, or redirect spoofed network traffic.

An example network device receives an encapsulated network packet via a network tunnel; extracts IPv6 header information from the encapsulated network packet; extracts IPv4 header information from the encapsulated network packet; determines that the encapsulated network packet is a spoofed network packet based on the IPv6 header information and the IPv4 header information; and in response to detecting the spoofed network packet, transmits a message to a Tunnel Entry Point (TEP) device, the message including data representing the IPv6 header information and IPv4 header information. A tunnel entry point (TEP) device may receive the message and use the message to detect spoofed IPv6 traffic, e.g., when an IPv6 header and an IPv4 header of an encapsulated packet matches the IPv6 header and the IPv4 header specified in the message. In this manner, the TEP device may block, rate limit, or redirect spoofed network traffic.

A system includes a plurality of remote units; a centralized unit communicatively coupled to the plurality of remote units via a fronthaul network; and an entity that performs deep packet inspection. The centralized unit transmits sets of data to the plurality of remote units across the fronthaul network in packets, each of the sets of data mapped to at least one of the plurality of remote units and each of the packets including a respective indicator indicating each remote unit the associated packet is intended for, wherein each indicator comprises a plurality of bit positions where each bit position is mapped to a different one of the plurality of remote units. The entity performs the deep packet inspection on the packets to determine each remote unit the packets are intended for and communicate each packet to each remote unit the packet is intended for over the fronthaul network.

A system includes a plurality of remote units; a centralized unit communicatively coupled to the plurality of remote units via a fronthaul network; and an entity that performs deep packet inspection. The centralized unit transmits sets of data to the plurality of remote units across the fronthaul network in packets, each of the sets of data mapped to at least one of the plurality of remote units and each of the packets including a respective indicator indicating each remote unit the associated packet is intended for, wherein each indicator comprises a plurality of bit positions where each bit position is mapped to a different one of the plurality of remote units. The entity performs the deep packet inspection on the packets to determine each remote unit the packets are intended for and communicate each packet to each remote unit the packet is intended for over the fronthaul network.