A system includes a self-backhauled eNodeB which communicates via a radio interface with an anchor eNodeB, where the self-backhauled eNodeB is made reachable in an operator's network via a serving gateway and where the serving gateway of the self-backhauled eNodeB owns an IP address associated with the self-backhauled eNodeB. The system receives a packet destined for the self-backhauled eNodeB and classifies the packet to a bearer associated with a self-backhauled link to the self-backhauled eNodeB.

Upon receipt of a packet addressed to a virtual IP address assigned to each first device from a second device outside a base network, a processor identifies a base relay apparatus that accommodates the first device, to which the virtual IP address is assigned, on the basis of the virtual address and a protocol type of the received packet, and also identifies a reception port number of the identified base relay apparatus, which corresponds to a combination of the virtual IP address and the protocol type of the received packet, from among reception port numbers each assigned to a combination of the first device accommodated to identify a transfer destination, and a protocol type. Then, the processor relays the received packet to the identified reception port number of the identified base relay apparatus.

Embodiments of the present invention provide a Multiprotocol Label Switching traffic engineering tunnel establishing method and device. A tunnel establishing method includes: receiving, by a second routing device, an identifier, which is sent by a first routing device, of an MPLS TE tunnel from a first VPN instance to a second VPN instance; acquiring, by the second routing device according to the identifier, path information of the MPLS TE tunnel from the first VPN instance to the second VPN instance; and establishing an MPLS TE tunnel from the second VPN instance to the first VPN instance according to the acquired path information. Therefore, forward and reverse bidirectional tunnels are co-routed or partially co-routed, thereby solving a problem caused by non-co-routing during BFD.

An embodiment of a communication circuit for communicating data across an isolation barrier may include an input circuit to receive a plurality of input data channels, a framing circuit to frame an input data packet from the plurality of input data channels, an encoding circuit to select a characteristic of a data symbol to represent a plurality of bits of the framed input data packet, and a driver circuit to drive one or more data symbols representing the framed input data packet onto an isolator configured to communicate data across the isolation barrier. The encoding circuit may select an amplitude, frequency or phase of the data symbol from a plurality of predetermined amplitudes, frequencies or phases, to encode the plurality of bits as the selected amplitude, frequency or phase. The communication circuit also may include a receive circuit to receive one or more second data symbols from the isolator, a decoding circuit to decode a plurality of bits of an output data packet as a function of a characteristic of the second data symbol, and a deframing circuit to deframe the output data packet into output data of a plurality of output data channels.

In one embodiment, an offload platform is an compute platform, adjunct to a router or other packet switching device, that performs packet processing operations including determining an egress forwarding value corresponding to the next-hop node of the packet switching device to which to send an offload-platform processed packet. The offload platform downloads forwarding information from the router, and augments it, such as, but not limited to, representing interfaces of the router as identifiable virtual interface(s) on the offload platform, and including each of one or more next-hop nodes of the router represented as an identifiable virtual adjacency and identifiable tunnel (e.g., identified by the egress forwarding value). In one embodiment, the egress forwarding value is an Multiprotocol Label Switching (MPLS) label or Segment Routing Identifier. The router identifies packets of certain packet flows to send to the adjunct offload platform, rather than processing per its routing information base.

A Cable Modem Termination System (CMTS) having a gateway configured to output signals on over data tunnels for transfer over a cable network to Customer Premises Equipment (CPE). Each data tunnel is preferably characterized as a one-way data stream of out-of-band (OOB) messaging signals.

For traffic exiting a logical network through a particular VTI, some embodiments perform a service classification operation for different data messages to identify different VTIs that connect the edge forwarding element to a service node to provide services required by the data messages. Each data message, in some embodiments, is then forwarded to the identified VTI to receive the required service. The identified VTI does not perform a service classification operation. The service node then returns the serviced data message to the edge forwarding element. In some embodiments, the identified VTI is not configured to perform the service classification operation and is instead configured to mark all traffic directed to the edge forwarding element as having been serviced. The marked serviced data message is received at the edge forwarding element and forwarded to a destination of the data message through the particular VTI.

A cloud extension agent can be provided on a customer premise for interfacing, via an outbound secure connection, cloud based services.

Methods and apparatus for providing L4S support with regard to non-3GPP untrusted/trusted accesses in which a non-3GPP access point, e.g., a WLAN AP or a TNAP, is enabled to monitor for downlink congestion with regard to L4S downlink data traffic flows at the non-3GPP AP, detect congestion and perform explicit congestion notification (ECN) markings are described. In some embodiments an innermost IP header field corresponding to a downlink L4S data packet, which typically conveys ECN information, in unavailable to the non-3GPP AP, due to IPsec encapsulation. The non-3GPP AP indicates detected congestion, at the non-3GPP AP, in an DL traffic flow via setting bits in an outer IP header ECN field. The AP detected DL congestion information is communicated via the outer IP header ECN field to a destination UE or to a core network interface device, e.g., a N3IWF or TNGF.

Systems and methods for managing a global virtual network connection between an endpoint device and an access point server are disclosed. In one embodiment the network system may include an endpoint device, an access point server, and a control server. The endpoint device and the access point server may be connected with a first tunnel. The access point server and the control server may be connected with a second tunnel.