29 results about "Peering" patented technology

Methods and apparatus to decrease DNS lookup times for mobile clients are disclosed. An example DNS cache peering system includes a mobile DNS cache; a mobile DNS server configured to, when an IP address for a URL is not found in the DNS cache, send a DNS lookup request for the URL; a ground-based DNS server to receive the DNS lookup request from the mobile DNS server, and send, in response, a DNS lookup response including the IP address for the URL to the mobile DNS server; and a ground-based DNS peer engine server configured to capture the DNS lookup response, and multicast DNS information from the DNS lookup response to a plurality of mobile DNS peer engine clients, wherein the plurality of mobile DNS peer engine clients are configured to store the DNS information in respective ones of a plurality of mobile DNS caches.

A method of configuring a multiple Access Points (M-AP) set includes transmitting, by an access point (AP) initiating a new M-AP set, an information element including a plurality of octets. One of the plurality of octets indicates the presence of an extended capabilities octet of the plurality of octets. A bit of the extended capabilities octet indicates if an M-AP Coordinated Transmissions (CT) Basic Service Set (BSS) is enabled for this AP. A method of establishing a multiple Access Points (M-AP) set between APs includes transmitting, by a first AP, a first message advertising an M-AP Coordinated Transmission (CT) Basic Service Set (BSS), receiving, by the first AP, from a second AP, a second message advertising a second M-AP CT BSS, and initiate peering, in response to receiving the first message or the second message, used by an M-AP set including the first AP and the second AP.

In some implementations, a routing device may indicate, to a direct connect gateway in a cloud computing system, a default route, wherein the default route is propagated to a virtual network function (VNF) running in the cloud computing system. The routing device may create a generic routing encapsulation (GRE) tunnel between the VNF and the routing device based on the default route, wherein the GRE tunnel permits a direct peering between the VNF and a private network outside of the cloud computing system. The routing device may perform a routing between the VNF and the private network using the GRE tunnel.

In one embodiment, a device determines a mapping between a network destination and Border Gateway Protocol (BGP) peers located across a plurality of autonomous systems for which the network destination is reachable. The device causes, based on the mapping, performance of probing tests along a plurality of paths to the network destination and via the BGP peers, to obtain path performance measurements for the plurality of paths. The device uses a prediction model to generate predicted performance metrics for the plurality of paths based on the path performance measurements. The device configures, based on the predicted performance metrics for the plurality of paths, the BGP peers with BGP peering policies to convey application traffic associated with the network destination via particular path from among the plurality of paths.

Establishing proxy-less connectivity from logically isolated virtual private clouds (VPC)within a cloud environment without the use of VPN or VPC peering is provided. Establishing a service attachment in one VPC, related to a service which is to be accessed, and a service endpoint in another VPC allows for private communication between the two networks without exposing the service to other VPCs in the cloud environment.

The present application relates to a system for ingress traffic management. The system includes a collection system within a network configured to collect traffic arrival information for peering links of the network. The system includes a training system configured to train a model based on the traffic arrival information to predict a probability of a traffic flow arriving on a peering link. The system includes a congestion mitigation system configured to predict based on the model, for traffic flows arriving on one or more peering links, other peering links to which the traffic flows would be shifted due to a condition affecting the one or more peering links. The congestion mitigation system may determine, in response to the condition, a set of prefixes to withdraw based on the other peering links to which traffic would be shifted.

Techniques for implementing Border Gateway Protocol (BGP) peering status-aware hitless reboot on a network device are provided. In one set of embodiments, at the time of shutting down for a hitless reboot, the network device can collect status information regarding its BGP peerings and can write this information to a file on non-volatile storage. Then, upon booting up after the hitless reboot, the network device can retrieve the file from the non-volatile storage and use the status information included therein to restore the BGP peerings as they existed prior to the hitless reboot.

The present invention relates to a method, device, terminal and medium for avoiding data loss in a peering process. Before an OSD in a down state in a placement group starts up and enters the peering process, a historical epoch sequence is calculated, and by judging whether the historical epoch sequence contains an abandoned OSDmap version, it is determined whether data writing occurs in the placement group during the period of the historical epoch sequence, thereby avoiding the situation where data writing cannot be judged when data is written to the abandoned OSDmap version. The analyzed historical epoch sequence of data writing is not less than the actual situation, thereby avoiding missing data writing of the placement group. When an OSD in the placement group that has data writing during the down state starts up and enters the peering process, the status of the remaining OSDs in the placement group is detected. If the remaining OSDs are all in the down state, the peering process of the OSD is suspended, and the peering process is completed only after the remaining OSDs are started up, thereby avoiding data loss caused by the OSD completing the peering process alone when data is written to the placement group during the down state.

A system executes a process for establishing a peering connection between (a) a first customer resource located in a first customer tenancy of a first cloud environment and (b) a second customer resource located in a second customer tenancy of a second cloud environment. The process includes transmitting a first peering request from the first customer tenancy to the second customer tenancy. The first peering request includes a service key that uniquely identifies the first customer resource. The process includes receiving, from the second customer tenancy, a second peering request that includes the service key transmitted in the first peering request. The process includes, responsive to verifying that the service key of the second peering request uniquely identifies the first customer resource, transmitting a control dataset to the second customer tenancy for configuring the peering connection.

The application discloses a VPC peer-to-peer connection method and system, and belongs to the technical field of cloud computing, which comprises the following steps: configuring a local VPP in a local VPC, wherein the local VPP comprises a local subnet IpTable, a local subnet BridgeDomain, a local subnet VxlanTunnel, a local subnet LOOP, a local interconnection BridgeDomain, a local interconnection IpTable, a local interconnection LOOP and a local interconnection VxlanTunnel; configuring a peer VPP in the local VPC, wherein the peer VPP comprises a peer subnet IpTable, a peer subnet BridgeDomain, a peer subnet VxlanTunnel, a peer subnet LOOP, a peer interconnection BridgeDomain, a peer interconnection IpTable, a peer interconnection LOOP and a peer interconnection VxlanTunnel; transmitting a data packet to the local VPP by a local cloud host; transmitting the data packet to the peer VPP by the local VPP; and transmitting the data packet to a peer cloud host by the peer VPP, so as to establish a peer-to-peer connection between the local cloud host and the peer cloud host. The VPC peer-to-peer connection method provided by the application can realize data intercommunication between cloud hosts in different VPCs, and is convenient for system management and data delivery.

Methods and apparatus for interfaces to manage direct network peerings. A system may include a data center, endpoint routers and a connectivity coordinator. The coordinator implements a programmatic interface defining connectivity operations. The coordinator receives a request for dedicated connectivity to data center resources, formatted according to the interface. The coordinator selects a target endpoint router at which to establish a physical link to implement the dedicated connectivity, and transmits a response identifying the target endpoint router and including configuration instructions for setting up a physical link for the dedicated connectivity.

Methods and apparatus to decrease DNS lookup times for mobile clients are disclosed. An example DNS cache peering system includes a mobile DNS cache; a mobile DNS server configured to, when an IP address for a URL is not found in the DNS cache, send a DNS lookup request for the URL; a ground-based DNS server to receive the DNS lookup request from the mobile DNS server, and send, in response, a DNS lookup response including the IP address for the URL to the mobile DNS server; and a ground-based DNS peer engine server configured to capture the DNS lookup response, and multicast DNS information from the DNS lookup response to a plurality of mobile DNS peer engine clients, wherein the plurality of mobile DNS peer engine clients are configured to store the DNS information in respective ones of a plurality of mobile DNS caches.

Techniques for a license manager service of a cloud system to activate and run licensed applications in VPCs with peering connections (or “peered VPCs”) established with configured VPCs. The license manager service may provide users with the ability to select a particular VPC to be configured to use licensed applications, and may further allow users to enable peered VPCs of the configured VPC to use licensed applications. The license manager service may provide a managed experience for activating the licenses for the applications running on computing resources in the configured VPCs and peered VPCs. The license manager service may launch licensed applications on virtual resources in a user's configured VPC and peered VPCs, manage the process for activating the licensed applications with third-party providers, and provide the user with access to licensed applications that have been activated and configured by the license manager service in configured and peered VPCs.

Techniques for making the state of a peering connections or routes between SD-WAN routers of an SD-WAN fabric and external routers dependent on the state of a local instance of a service chain of redundant service chains in the SD-WAN fabric. In examples, an SD-WAN router may determine that a local instance of a service chain is unavailable for inspecting network traffic, and terminate a peering session with an external router such that routes through the SD-WAN router are no longer available to the external router. In other examples where the SD-WAN router determines that the local instance of the service chain is unavailable, the SD-WAN router may use an update message to notify the external router that certain routes are not available through the SD-WAN router for network traffic that needs to be service-chained.

Techniques for making the state of a peering connections or routes between SD-WAN routers of an SD-WAN fabric and external routers dependent on the state of a local instance of a service chain of redundant service chains in the SD-WAN fabric. In examples, an SD-WAN router may determine that a local instance of a service chain is unavailable for inspecting network traffic, and terminate a peering session with an external router such that routes through the SD-WAN router are no longer available to the external router. In other examples where the SD-WAN router determines that the local instance of the service chain is unavailable, the SD-WAN router may use an update message to notify the external router that certain routes are not available through the SD-WAN router for network traffic that needs to be service-chained.

A method of peering in a wireless mesh network, the method comprising: peering of a first mesh device with a second mesh device, wherein the first mesh device is either a first peer mesh multi-link device, MLD, and the second mesh device is a second peer mesh MLD wherein each of the first and the second peer mesh MLDs comprise one or more affiliated mesh stations, STAs; or a mesh STA affiliated with a mesh MLD, and the second mesh device is a mesh STA; wherein peering is initiated after a discovery procedure is completed between the first mesh device and the second mesh device.

This application provides a communication method and apparatus applied to a first network device. The method includes: obtaining at least one first address, each first address being the address of a second network device and each second network device being a network device that has performed capability negotiation with the first network device; and, based on each first address, performing dynamic capability negotiation for a first service with the corresponding second network device; wherein the at least one first address is an address of the first network device under the enabled dynamic peering function.

This invention relates to a method and apparatus for identifying billing anomalies. The method includes: assigning a billing account and creating computing nodes when a new computing task is created, configuring timers, billing accounts, timer rates, and event lists for each node, and establishing a user-task-node binding relationship; performing a corresponding operation on the timer's timing action when each node is subjected to a certain type of operation (start, pause, resume, or end computing operation), and adding a corresponding record to the event list; periodically updating the billing account during the start-up-end process of each node, and updating it again at the end; synchronously updating the billing account of its parent task when any node's billing account is updated; and identifying billing anomalies for all tasks / nodes bound to the user specified in the request when the billing anomaly check interface receives a check request. This invention can enhance platform user stickiness.

In one embodiment, a device identifies available resources of a tunnel in a first software defined network. The device provides, based on the available resources, an indication that the tunnel is available to convey traffic sent by a second software defined network. The device receives, based on the indication, a request to convey traffic sent by the second software defined network via the tunnel in the first software defined network. The device configures a peering node in the first software defined network to connect the second software defined network to the tunnel to allow the traffic sent by the second software defined network to be conveyed via the tunnel.

A conditional high availability peering among all members of an all-active NGFW cluster is established. Data paths are monitored via a dynamic routing protocol capable of conditional advertisement, such as BGP, to detect network isolation failures. Peering can be temporarily suspended with the remote NGFWs by withdrawing the local IP address used for high availability peering to the remote NGFWs, responsive to the detected data path failure. Responsive to detecting a cure of the failed data path using said dynamic routing protocol, the high availability peering to remote NGFW nodes is automatically restored by resuming advertisement of the local peering IP address of the NGFW, wherein the high availability peering is reactivated for all remote NGFW nodes.

In one embodiment, a method includes onboarding, by an edge router, a first tenant from a network management system and determining, by the edge router, a mapping of a tenant identifier associated with the first tenant to a controller identifier associated with a controller. The method also includes reserving, by the edge router, a port number in a kernel for the first tenant and inserting, by the edge router, the tenant identifier into a first control packet. The method further includes communicating, by the edge router, the first control packet to the controller via an encrypted control connection during a first peering session. The first peering session shares the encrypted control connection with a second peering session.

An access point (AP) is configured for trigger-based peer-to-peer (TB P2P) operation with at least two peer stations (P2P1) and (P2P2) in which the AP (API) is operating as a coordinator. The AP may be configured to encode a trigger frame (AP TF) for transmission to reserve channel resources for two or more P2P transfers and identify times for each of the P2P transfers and may indicate an allocation of channel resources to a first of the peer stations (P2P1) for a first of the P2P transfers and to a second of the peer stations (P2P2) for a second of the P2P transfers. During the allocation for the first P2P transfer, the AP may decode a null data packet (NDP) frame for channel sounding received from the first peer station (P2P1). The AP may also encode a TB physical layer protocol data unit (PPDU) in accordance with a multi-user orthogonal frequency division multiple access (MU OFDMA) frame format a transmission to the first peer station (P2P1) in accordance with an uplink multi-user multiple-input multiple output (UL MU MIMO) technique.

Methods are provided for ensuring that a service node selects a local leaf node to reach remote destinations by leveraging reverse metric to inform the active service node of the topology of the leaf nodes. The methods involve obtaining connection information about a service node. The connection information indicates whether the service node is locally connected or connected via a virtual private network (VPN) tunnel. The methods further involve generating a reverse metric signaling based on the connection information. The reverse metric signaling includes a different metric value for the service node when the service node is locally connected than when the service node is connected via the VPN tunnel. The methods further involve providing the reverse metric signaling to the service node to cause the service node to select an intermediate network device from among a plurality of intermediate network devices to forward data traffic to a destination.

A conditional high availability peering among all members of an all-active NGFW cluster is established. Data paths are monitored via a dynamic routing protocol capable of conditional advertisement, such as BGP, to detect network isolation failures. Peering can be temporarily suspended with the remote NGFWs by withdrawing the local IP address used for high availability peering to the remote NGFWs, responsive to the detected data path failure. Responsive to detecting a cure of the failed data path using said dynamic routing protocol, the high availability peering to remote NGFW nodes is automatically restored by resuming advertisement of the local peering IP address of the NGFW, wherein the high availability peering is reactivated for all remote NGFW nodes.

Methods, systems, and devices for wireless communications are described. Described techniques relate to a soft access point (AP) in a multi-link operation including a first radio frequency link for control communications and a second radio frequency link for data communications. Described techniques further relate to a transfer of an AP role in a wireless local area network operating in accordance with an multi-link operation. Described techniques further provide for assisting, at an AP (which may be a soft AP), peer to peer communications between non-AP multi-link devices (MLDs) in a WLAN operating in accordance with an MLO.

A station (STA) may operate as a first peer-to-peer (P2P) client (P2P1) for P2P operations with dual-stage triggering. The STA may decode a primary frame trigger frame (TF) from an access point (AP) operating as a coordinator. The primary TF may allocate resources in an initial portion of a time-duration allocation to the P2P1 for the P2P operations with one or more other peer stations, including a second P2P client (P2P2) and a third P2P client (P2P3). The primary TF may further allocate resources in a subsequent portion of the time-duration allocation to the P2P2 for the P2P operations. The STA may also encode a first secondary TF for transmission within the initial portion of the time-duration allocation. The first secondary TF may allocate specific resource units (RUs) to the one or more other peer stations. The STA may also decode a TB physical layer protocol data unit (TB PPDU) encoded in accordance with a multi-user orthogonal frequency division multiple access (MU OFDMA) frame format. The TB PPDU may be received concurrently within the initial portion of the time-duration allocation from the one or more other peer stations in accordance with an uplink OFDMA technique.

In one embodiment, a method includes onboarding, by an edge router, a first tenant from a network management system and determining, by the edge router, a mapping of a tenant identifier associated with the first tenant to a controller identifier associated with a controller. The method also includes reserving, by the edge router, a port number in a kernel for the first tenant and inserting, by the edge router, the tenant identifier into a first control packet. The method further includes communicating, by the edge router, the first control packet to the controller via an encrypted control connection during a first peering session. The first peering session shares the encrypted control connection with a second peering session.