Aspects of the present disclosure involve systems, methods, computer program products, and the like, for correlating information associated with one networking transmission protocol, such as Internet Protocol version 6 (IPv6), to information associated with a different networking transmission protocol, such as Internet Protocol version 6 (IPv4). More specifically, when resolving an Internet Protocol (IP) address associated with a requesting device to a network, the system may base the resolved destination on one or more attributes of a known address to build a network mapping of the received IP address. In one specific example, an IPv6 address is received and associated with a known IPv4 address to map the network.

Disclosed is a mechanism that provides the extensions of PCEP message and the objects to support PCECC with P2MP capability in downloading the labels for branch node of P2MP TE LSPs. In one implementation, various embodiments provide an apparatus, a system, a node and a method that receives a PCLabelUpd message with all the extensions and the objects to support PCECC with P2MP capability, detects the object and identifies that the label download is for P2MP TE LSP and for this LSP. In those embodiments, the apparatus/the system/the node acts as a branch node, and thereby the apparatus/the system/the node downloads all the labels specified in the object to data plane with respect to any existing branch node download mechanism for a P2MP TE LSP.

A system and network devices for packet processing, a network device including a processor and instructions for receiving a first packet sent by a second network node, the first packet including a format of a segment identifier of the second network node describing a length and a location of each field in the segment identifier, obtaining the format based on the first packet, the segment identifier having a first field, and including a determined value of the first field in the segment identifier in a second packet sent to the second network node, the value of the first field in the segment identifier being determined based on a segment routing policy and the format, and the determined value of the first field indicating to the second network node to process the second packet.

An ICN-over-IP architecture, which supports ICN-dependent IP addresses, is provided as an integrated architecture requiring small changes within the network, utilizing the incrementally introduced ICN-enabled IP routers efficiently where ICN-enabled IP routers are distributed within/across domains and are capable of coordinating among others based on domain or ICN imposed policies. System, devices and methods are provided achieving improved performance with the introduction of additional ICN-enabled IP routers within/across domains, and continuing to perform efficiently by relying on the principles of the current IP forwarding and taking advantage of IP's currently available features.

A user plane function (UPF) for use in a mobile network may receive an Internet Protocol version 6 (IPv6) data packet which includes a segment routing header and a payload containing user plane (UP) traffic data associated with a user equipment (UE). The segment routing header may indicate a list of segment identifiers comprising IPv6 addresses. Each first address portion of an IPv6 address may indicate a location of a corresponding UPF in a set of UPFs which define a forwarding path of the IPv6 data packet in the mobile network. Each second address portion of an IPv6 address may indicate one or more rules, actions, or parameters (e.g. forwarding action rules, buffering action rules, etc.) to be applied to the IPv6 data packet at the corresponding UPF in the set of UPFs indicated by the first address portion that is associated with the second address portion.

In one embodiment, a network comprises a first forwarding domain using a first data plane forwarding protocol and a second forwarding domain using a second data plane forwarding protocol different than the first data forwarding plane forwarding protocol. The first forwarding domain includes a first path node and a particular border node. The second forwarding domain includes a second path node and the particular border node. The particular border node performs Segment Routing or other protocol interworking between the different data plane forwarding domains, such as for transporting packets through a different forwarding domain or translating a packet to use a different data forwarding protocol. These forwarding domains typically include Segment Routing (SR) and SR-Multiprotocol Label Switching (SR-MPLS). Paths through the network are determined by a Path Computation Engine and/or based on route advertisements such associated with Binding Segment Identifiers (BSIDs) (e.g., labels, Internet Protocol version 6 addresses).

A server, includes a virtual machine identifier assigning section to assign an identifier of a virtual machine operating on the server; and a network interface to transmit a packet including a Layer 2 header information which includes the identifier of the virtual machine and a first packet field for a VLAN-Tag, wherein the network, interface transmits the packet to a packet encapsulate section which encapsulates a second packet field including the Layer 2 header information with a virtual network identifier representing a virtual network to which the virtual machine belongs.

Some embodiments provide a method of operating several logical networks over a network virtualization infrastructure. The method defines a managed physical switching element (MPSE) that includes several ports for forwarding packets to and from a plurality of virtual machines. Each port is associated with a unique media access control (MAC) address. The method defines several managed physical routing elements (MPREs) for the several different logical networks. Each MPRE is for receiving data packets from a same port of the MPSE. Each MPRE is defined for a different logical network and for routing data packets between different segments of the logical network. The method provides the defined MPSE and the defined plurality of MPREs to a plurality of host machines as configuration data.

A message handler is described. The message handler is configured, in response to receiving a data package which is formatted according to a given communications protocol, such as CAN or Ethernet, and which comprises package-directing data and payload data, to generate package having a predetermined data format, for example a layer-2 or layer-3 package, which comprises a header and payload data. The header comprises an address generated in dependence upon the package-directing data and wherein the payload comprises the data package. The package having a predetermined data format may be an IEEE 1722 frame.

This application provides a method which includes: receiving, by a receiving device from a transport network, a code block stream that is in a first rate mode and that includes a plurality of code blocks; determining a target code block from the code block stream, where the target code block is a code block received by the receiving device in an inter-packet gap of the code block stream, the target code block includes a first target code block, and the first target code block is a code block of a data type, and/or the target code block includes a second target code block, and the second target code block is a code block of a termination type; and modifying the target code block to modify the target code block to a code block, of an ordered set type, that is in a second rate mode.