Methods and apparatus, including computer program products, are provided for communications. In one aspect there is provided a method. The method may include sending, by a gateway, an advertisement including an internet protocol version 6 over low power wireless personal area network context option carrying a well-known prefix, the well-known prefix indicating to a node that the gateway provides an uplink in accordance with internet protocol version 4; and receiving, at the gateway, a first packet received via the wireless network in accordance with internet protocol version 6, the first packet including a destination address in accordance with internet protocol version 4. Related apparatus, systems, methods, and articles are also described.

A network device may receive a packet and may determine whether a next header of the packet is an Internet protocol (IP) header, an Internet control message protocol (ICMP) header, or a segment routing header. The network device may determine, when the next header of the packet is the IP header, whether policy processing of the packet is set to ultimate segment decapsulation and may discard the packet when the policy processing of the packet is not set to ultimate segment decapsulation. The network device may decapsulate an outer header of the packet when the policy processing of the packet is set to ultimate segment decapsulation and may process the packet after decapsulating the outer header of the packet, to generate a processed packet. The network device may forward the processed packet toward a destination.

A network device may receive a packet and may determine whether a next header of the packet is an Internet protocol (IP) header, an Internet control message protocol (ICMP) header, or a segment routing header. The network device may determine, when the next header of the packet is the IP header, whether policy processing of the packet is set to ultimate segment decapsulation and may discard the packet when the policy processing of the packet is not set to ultimate segment decapsulation. The network device may decapsulate an outer header of the packet when the policy processing of the packet is set to ultimate segment decapsulation and may process the packet after decapsulating the outer header of the packet, to generate a processed packet. The network device may forward the processed packet toward a destination.

Embodiments herein disclose a method for Device IP Status Checking and Connection Orchestration (DISCCO) by a first electronic device. The method may include receiving a version(s) of an IP address from a backhaul server. The method may include determining an IP stack capability status of a second electronic device using a network protocol(s), where the IP stack capability status indicates whether the received version(s) of the IP address is supported by the second electronic device and the received version(s) of the IP address is enabled on the second electronic device. The method may include storing the IP stack capability status of the second electronic device into a host status database of the first electronic device. The method may include orchestrating the received version(s) of the IP address with the backhaul server and/or the second electronic device based on the stored IP stack capability status.

This application provides a packet processing method, a device, and a system. The method includes a second network device receives an IPv6 packet sent by a first network device, where the IPv6 packet includes an IPv6 header and a first IPv6 extension header, and the first IPv6 extension header indicates that a network device receiving the IPv6 packet is to perform an action in the first IPv6 extension header on a data plane. The second network device performs the action in the first IPv6 extension header on the data plane of the second network device based on the IPv6 header and the first IPv6 extension header. This ensures that the network device receiving the IPv6 packet can normally forward the IPv6 packet.

A network device includes a memory and a processor. The processor implements at least one classifier to provide classification for tunneled IPinIP traffic based on classification parameters provided by Internet Protocol Version 6 (IPv6) classification encoding, Internet Protocol Version 4 (IPv4) classification encoding, and Transport Control Protocol/User Datagram Protocol (TCP/UDP) classification encodings, wherein one of the IPv6 classification encoding and the IPv4 classification encoding is provided by extension information to provide extended classification capabilities. The processor uses the at least one classifier to compare the classification parameters provided by the IPv6 classification encoding, the IPv4 classification encoding, and the TCP/UDP classification encodings to fields in an IPv6 header, an IPv4 header, and a TCP/UDP header of the IPinIP packet. Based on the comparison, the processor maps the IPinIP packet to a service flow identified by the classification parameters.

A network device includes a memory and a processor. The processor implements at least one classifier to provide classification for tunneled IPinIP traffic based on classification parameters provided by Internet Protocol Version 6 (IPv6) classification encoding, Internet Protocol Version 4 (IPv4) classification encoding, and Transport Control Protocol/User Datagram Protocol (TCP/UDP) classification encodings, wherein one of the IPv6 classification encoding and the IPv4 classification encoding is provided by extension information to provide extended classification capabilities. The processor uses the at least one classifier to compare the classification parameters provided by the IPv6 classification encoding, the IPv4 classification encoding, and the TCP/UDP classification encodings to fields in an IPv6 header, an IPv4 header, and a TCP/UDP header of the IPinIP packet. Based on the comparison, the processor maps the IPinIP packet to a service flow identified by the classification parameters.

A MAP-T system that shares an IPv4 address with one or more other MAP-T systems identifies low latency (LL) traffic for an upstream and a downstream perspective by enhancing NAT of ports using MAP-T rules. The MAP-T rules provide a range of transport ports with a transport slice providing for a subdivision of the transports into a subnet range so as to isolate certain ports for mapping LL traffic. An access point device and a cable modem of the MAP-T system are configured so as to appropriately transform any received traffic so as to properly direct the traffic.

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 fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The tunnel device is selected based on an attribute, such as IP Geolocation. A tunnel bank server stores a list of available tunnels that may be used, associated with values of various attribute types. The tunnel devices initiate communication with the tunnel bank server, and stays connected to it, for allowing a communication session initiated by the tunnel bank server. Upon receiving a request from a client to a content and for specific attribute types and values, a tunnel is selected by the tunnel bank server, and is used as a tunnel for retrieving the required content from the web server, using standard protocol such as SOCKS, WebSocket or HTTP Proxy. The client only communicates with a super proxy server that manages the content fetching scheme.