An example embodiment may involve a network interface configured to transmit and receive frames. The embodiment may also involve a network protocol stack configured to: (i) perform encapsulation of outgoing messages into outgoing frames for transmission by way of the network interface, or (ii) perform decapsulation of incoming frames received by way of the network interface into incoming messages. The embodiment may also involve a parsing and validation module configured to: (i) receive representations of the incoming or the outgoing messages, and (ii) perform one or more validation checks on the representations, wherein the representations define transactions that are functionally equivalent to corresponding transactions that are defined by the messages, wherein the one or more validation checks are performed in parallel to performance of the encapsulation or decapsulation, and wherein a representation of a message failing the one or more validation checks causes the message to be discarded.

A method for performing vehicle remote diagnosis is provided. A diagnostic device sends a first controller area network (CAN) bus message to a device connector. The device connector encapsulates the first CAN bus message received into a first data packet and sends the first data packet to a vehicle connector through remote communication. The vehicle connector decapsulates the first data packet into the first CAN bus message and sends the first CAN bus message to a target vehicle. The vehicle connector receives second CAN bus messages and filters the second CAN bus messages to obtain a CAN bus diagnostic message, and the second CAN bus messages are sent by the target vehicle in response to the first CAN bus message. The vehicle connector encapsulates the CAN bus diagnostic message into a second data packet and sends the second data packet to the device connector.

A packet can be sent on a VLAN from a first machine that has a first address on the VLAN to a second machine that has a second address on the VLAN and that is located at a remote location associated with a remote location identifier. A network appliance can use the second address to determine the remote location identifier, can encapsulate the packet in a local segment packet that includes a local VNID and the remote location identifier; and can send the local segment packet to a local router. The local router can use the remote location identifier and the local VNID to determine a remote router and a remote VNID, can encapsulate the packet in an outer packet, which can be a VxLAN packet, that includes the remote VNID, and can send the outer packet to the remote router.

A communication apparatus includes: a controller that determines a time stamp as a starting point and a unit period of the time stamp starting from the starting point; an encapsulator that synchronizes, starting from the starting point, a GPIO (General Purpose Input/Output) signal from a Master with the time stamp to generate one of a first GPIO packet including all pieces of sampling data sampled at a constant sampling period and a first GPIO packet including sampling data sampled at a sampling interval according to a frequency of logical changes of the GPIO signal and sampling position information; a LINK that generates an Up link packet including the first GPIO packet; and a PHY that transmits a transmission signal to a communication partner apparatus, the transmission signal conforming to a predetermined communication protocol and including the Up link packet.

In modern networks, RRU and BBU equipment of an access point site typically handles traffic from a single sector. An RRU-BBU pair process that traffic (often limited to a single spectrum from a single sector) according to implemented capabilities and other equipment located further upstream perform functions that rely on information from multiple sectors. An integrated device (e.g., white box) can integrate the functionality of multiple RRU (or NR in 5G) and the functionality of multiple BBU (or DU/CU splits in 5G), which can reduce implementation footprint, costs, and can provide related services more efficiently without going upstream.

A data transmission method includes: a first electronic control unit (ECU) that obtains to-be-sent data. The first ECU determines a protection policy corresponding to the to-be-sent data from a plurality of protection policies, where the protection policies include a plurality of different encapsulation formats for the to-be-sent data and at least two protection policies with different calculation amounts for processing the to-be-sent data. The first ECU encapsulates the to-be-sent data according to the protection policy corresponding to the to-be-sent data to obtain an encapsulated packet. The first ECU sends the encapsulated packet to a second ECU, where the first ECU and the second ECU are any two ECUs in a vehicle.

A disclosed method is performed at a first boundary node bordering a BIER domain. The method includes receiving a message associated with a source and group for multicast from outside the BIER domain. The method further includes generating an encapsulated message based on the message, a metric, and a first proxy address of the first boundary node. The method also includes forwarding the encapsulated message through the BIER domain to at least one second boundary node bordering the BIER domain and connectable to the first boundary node. The first boundary node additionally triggers the at least one second boundary node to decapsulate the encapsulated message for forwarding out of the first domain and store a record including the source, the group, the metric representing the cost of the first boundary node to the source, and the first proxy address on the at least one second boundary node.

Techniques for operating a network device for multiple packet encapsulation for different tunnels are provided. In some embodiments, the network device may receive an original packet on an ingress port, the original packet being received from a first host and addressed to a second host; encapsulate the original packet in a first tunnel packet for a first tunnel; recirculate the first packet through a loopback port; encapsulate the recirculated packet in a second tunnel packet for a second tunnel; and egress the packet encapsulated for the second tunnel. The switch may further add a first tunnel header to the original packet to encapsulate the first packet and add a second tunnel header to the recirculated packet to encapsulate the recirculated packet.

Some embodiments provide a method that allows a first data compute node (DCN) to forward outgoing traffic to a second DCN directly in spite of receiving the incoming traffic from the second DCN through a load balancer. That is, the return traffic's network path from the first DCN (e.g., a server machine) to the second DCN (e.g., a client machine) bypasses the load balancer, even though a request that initiated the return traffic is received through the load balancer. The load balancer receives a connection session request from a client machine to connect to a server. It identifies a set of parameters for the connection session and after selecting a server for the connection, passes the identified set of parameters to a host machine that executes the server. The server establishes the connection session directly with the client machine based on the identified set of parameters.

A forwarding entry generation method includes sending, by a controller, a plurality of resource allocation request messages to a plurality of network devices in a network slice, to trigger the plurality of network devices to allocate resources, where the resource allocation request message includes an identifier of the network slice and a resource that needs to be allocated by a corresponding network device to the network slice; receiving, by the controller, a plurality of resource allocation response messages including the identifier of the network slice and a segment identifier of a corresponding network device, and a resource allocated by each device belongs to the network slice; and generating, by the controller, a forwarding table corresponding to the network slice, where the forwarding table includes a forwarding entry for arriving at a network device in the network slice.