This application discloses a TSN time synchronization method and apparatus. One example method includes: a first apparatus receives a first TSN time synchronization message from a second apparatus; the first apparatus determines that the first TSN time synchronization message does not carry a first time, where the first time is a system time of a wireless communication system when the second apparatus receives the first TSN time synchronization message; and the first apparatus locally obtains a bridge residence time, write the bridge residence time into the first TSN time synchronization message, and send the first TSN time synchronization message.

A first network device may receive an advertisement that includes a prefix for a second network device, wherein the advertisement is destined for a third network device. The first network device may determine, based on a network topology, whether a next hop is one hop away or multiple hops away. The first network device may selectively modify the advertisement to include a first segment identifier, based on the next hop being one hop away and to generate a first modified advertisement, or may modify the advertisement to include a second segment identifier, based on the next hop being multiple hops away and to generate a second modified advertisement. The first network device may forward the first modified advertisement or the second modified advertisement toward the third network device.

Examples disclosed herein relate to a method comprising receiving a data packet originating from a first device and intended for a second device, wherein the first device and the first access device belong to a first branch of a Wide Area Network (WAN) using a MPLS overlay and the second device belongs to a second branch of the WAN. The method includes encapsulating the data packet in VXLAN including a VXLAN label identifying a role type and transmitting the data packet to a first core device. The method includes determining an MPLS label corresponding to the role type and transmitting the data packet over the MPLS overlay to a second core device belonging to the second branch of the WAN. The method includes translating the MPLS label into the VXLAN label and transmitting the data packet including the VXLAN label to a second access device for an enforcement action.

Metadata indicating that a virtual traffic hub enabling connectivity between a plurality of isolated networks has been established is stored. A determination is made that a first entry of a first isolated network attached to the hub is to be represented in a second routing table of a second isolated network attached to the hub, e.g., to enable network packets originating at resources of the second isolated network to be transmitted via the hub to the first isolated network. A new entry corresponding to the first entry is included in the second routing table.

The same test data frame is dispatched from a network interface device a plurality of times so as to test a network. Since the same test data frame is used, it may be unnecessary for a new test data frame to be provided and protocol processed each time one is required to be sent. The protocol processing resources of the network interface device are then available for sending further traffic in parallel with the dispatch of the test data frames. On the receive side, the network interface device collects statistics regarding the reliable receipt of test frames, without requiring the test frames to be further processed and provided to a driver of the network interface device. In this way, the processing and buffering capacity in the network interface device is available for handling further traffic in parallel with the test traffic.

A method performed by a Next Generation Node B (gNB) in a communications system implementing User Datagram Protocol (UDP) comprises indicating that a data packet comprises a multi-transport network context-identifier (MTNC-ID) corresponding to a forwarding path and being associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for traffic forwarding on the forwarding path, inserting the MTNC-ID into a Generic UDP Encapsulation (GUE) header of the data packet, and transmitting the data packet to a network element (NE) in the communications system based on the forwarding path corresponding to the MTNC-ID.

The present disclosure provides methods for shunting clustered gateways, which relate to the field of computer technologies, and in particular, relate to the technical field of data transmission. A specific implementation solution is: in response to receiving a first packet sent by a target internal network machine, a first hash value is acquired, wherein the first hash value is generated by a shunt of a public network gateway cluster, and the shunt is configured to perform a hash calculation on the first packet based on a pre-configured port dictionary; a target gateway machine is selected from the public network gateway cluster according to the first hash value; and the first packet is sent to the target gateway machine.

A virtual firewall configured with two interfaces assigned different security zones switches between Layer 3 routing and bump-in-the-wire (BITW) modes between sessions. After receiving a packet from a one-arm load balancer, an inner header is determined based on decapsulation which removes an outer header. A route lookup is performed based on the inner header to determine whether to communicate packets of the session with Layer 3 routing or according to the BITW model. The result of the route lookup indicates an egress interface. If the ingress and egress interfaces are the same, the firewall operates according to the BITW model for the session. If the egress and ingress interfaces are different, the firewall routes packets of the session with Layer 3 routing. Upon detection of subsequent packets, the firewall operates according to the determined mode for the session without performing additional inner header route lookups for operation mode determination.

In a wireless network, a user equipment (UE) may support reflective quality of service (QoS), where QoS applied to uplink packets is implicitly derived from downlink packets. For example, when the UE receives a downlink packet that includes a reflective QoS (RQoS) indicator and a QoS flow identifier (QFI), the UE may apply the same QoS associated with the downlink packet to an uplink packet with one or more attributes that match the downlink packet. However, for a received downlink encapsulating security payload (ESP) packet that includes an RQoS indicator and a QFI, a modem cannot determine an uplink security parameters index (SPI) and downlink SPI pairing needed to enable RQoS because the uplink/downlink SPI pairing is known only by the upper layer. Accordingly, some aspects described herein enable the modem to learn uplink/downlink SPI pairings for ESP packets and thereby enable RQoS for ESP packets.

A virtual network interface controller (NIC) associated with a virtual machine in a cloud computing network is configured to support one or more network containers that encapsulate networking configuration data and policies that are applicable to a specific discrete computing workload to thereby enable the virtual machine to simultaneously belong to multiple virtual networks using the single NIC. The network containers supported by the NIC can be associated with a single tenant to enable additional flexibility such quickly switching between virtual networks and support pre-provisioning of additional computing resources with associated networking policies for rapid deployment. The network containers can also be respectively associated with different tenants so that the single NIC can support multi-tenant services on the same virtual machine.