Patent classifications
H04L12/56
Method for Obtaining Port Path and Apparatus
A method for obtaining a port path and an apparatus to improve a network capacity, where the method includes receiving, by a controller, a request message from a first server, where the request message requests port path information, and the port path information includes a port that a logical link from the first server to a second server passes through, obtaining, by the controller, a first absolute port path (APP) and a second APP according to network topology information, where the first APP includes a port that a logical link from a root node to the first server passes through, and the second APP includes a port that a logical link from the root node to the second server passes through, obtaining, by the controller, the port path information according to the first APP and the second APP, and sending the port path information to the first server.
Message Attack Defense Method and Apparatus
The present disclosure discloses a message attack defense method and apparatus. The method includes: receiving, by a controller, a report message sent by at least one switch; respectively storing, by the controller in a switch queue corresponding to each switch, the received report message that is sent by each switch; and performing, by the controller, round-robin scheduling on the switch queue corresponding to each switch.
Load balancer bypass
Redirecting message flows to bypass load balancers. A destination intermediary receives a source-side message that includes a virtual address of a load balancer as a destination, and that is augmented to include a network address of a destination machine as a destination. The destination intermediary determines that a source intermediary should address subsequent network messages that originate from a source machine and that are associated with the same multi-message flow to the destination machine while bypassing the load balancer. The destination intermediary modifies the source-side message so the destination for the source-side message addresses the destination machine, and passes the modified source-side message to the destination machine. The destination intermediary receives a response from the destination machine identifying the source machine as its destination, and modifies the response so a source address identifies the virtual address of the load balancer, and dispatches the modified response to the source machine.
On-demand access to compute resources
Disclosed are systems, methods and computer-readable media for controlling and managing the identification and provisioning of resources within an on-demand center as well as the transfer of workload to the provisioned resources. One aspect involves creating a virtual private cluster within the on-demand center for the particular workload from a local environment. A method of managing resources between a local compute environment and an on-demand environment includes detecting an event associated with a local compute environment and based on the detected event, identifying information about the local environment, establishing communication with an on-demand compute environment and transmitting the information about the local environment to the on-demand compute environment, provisioning resources within the on-demand compute environment to substantially duplicate the local environment and transferring workload from the local-environment to the on-demand compute environment. The event can be a threshold or a triggering event within or outside of the local environment.
Sticky service sessions in a datacenter
Some embodiments provide novel inline switches that distribute data messages from source compute nodes (SCNs) to different groups of destination service compute nodes (DSCNs). In some embodiments, the inline switches are deployed in the source compute nodes datapaths (e.g., egress datapath). The inline switches in some embodiments are service switches that (1) receive data messages from the SCNs, (2) identify service nodes in a service-node cluster for processing the data messages based on service policies that the switches implement, and (3) use tunnels to send the received data messages to their identified service nodes. Alternatively, or conjunctively, the inline service switches of some embodiments (1) identify service-nodes cluster for processing the data messages based on service policies that the switches implement, and (2) use tunnels to send the received data messages to the identified service-node clusters. The service-node clusters can perform the same service or can perform different services in some embodiments. This tunnel-based approach for distributing data messages to service nodes/clusters is advantageous for seamlessly implementing in a datacenter a cloud-based XaaS model (where XaaS stands for X as a service, and X stands for anything), in which any number of services are provided by service providers in the cloud.
Computer system and maintenance method of computer system
A communication system includes a control device configured to calculate a packet forwarding path and set a flow based on the packet forwarding path in a node, and a plurality of nodes configured to forward a received packet based on a flow set by the control device. The control device, when receiving a detour instruction, calculates a new packet forwarding path which detours a detour target node and sets a flow based on the new packet forwarding path in the plurality of nodes on the new packet forwarding path.
Hierarchical quality of service scheduling method and device
Provided are an HQoS scheduling method and device. A received uplink data packet is encapsulated and stored in a queue in uplink direction, and an uplink queue scheduling component is requested to perform scheduling. In this manner, HQoS scheduling in the uplink direction is implemented, and a personalized demand of a user can be met by scheduling uplink data, to carry out more flexible function customization. According to the method and device, the data packet may be further sent to a downlink direction after the HQoS scheduling in the uplink direction is completed, and the HQoS scheduling can be performed on the data in the downlink direction, so that the HQoS scheduling is respectively performed on the data in both the uplink direction and the downlink direction; in this manner, the real bidirectional HQoS scheduling control is implemented, and QoS of the user service can be guaranteed in both directions.
Network Virtualization
A virtualization controller may select a physical device as a root device of a virtual device, and select a physical device as a leaf device of the virtual device. The virtualization controller may obtain a user network interface (UNI) on the leaf device, establish a virtual interface on the root device for the UNI, and record a relation which associates the UNI with the virtual interface. The virtualization controller may control the root device and the leaf device to establish a virtual tunnel between the UNI and the virtual interface through which the root device and the leaf device may exchange data.
DATA CENTER
A data center includes: a server including a control plane; a data plane that is configured to receive network connection information from the control plane; and a storage group including a plurality of first storage devices. The data plane may be configured to set connections between the server and the plurality of first storage devices based on the network connection information corresponding to each first storage device of the plurality of first storage devices.
Multicast and unicast messages in a virtual cell communication system
Reliable multicast delivery in wireless communication, even when a WS doesn't know its AP, is determined at the AP without the sending device. Multicast packets are received at each AP having destinations. Without altering those packets, the AP encapsulates them in an A-MSDU packet. Each A-MSDU packet is sent individually to each destination, and might encapsulate more than one multicast packet. Destinations might receive two streaming messages faster than if sent separately. AP's might choose a 1st multiple of multicast packets from a 1st source, a 2nd, different, multiple of multicast packets from a 2nd source, and a single multicast packet from a 3rd source. Individualized optimization of transmission parameters for each A-MSDU packet and each multicast packet therein. Individualized optimization of transmission parameters for the A-MSDU packet for each destination. The AP collectively optimizes delivery of distinct multicast packets to different destinations.