IP Library Granted Patent US 11,064,021
Granted Patent B2
US 11,064,021 · App. 16/403,175 · Granted Jul 13, 2021

Method, device and computer program product for managing network system

Inventors: Fei Chen (Beijing, CN); Fucai Liu (Beijing, CN); Junping Zhao (Beijing, CN)
Assignee: EMC IP Holding Company LLC
H04L67/1014H04L47/125H04L67/327
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,064,021
App. No.
16/403,175
Filed
May 3, 2019
Granted
Jul 13, 2021
Kind
B2
Art Unit
2443
USPC
709/225
Abstract

Techniques for managing a network system are disclosed. For example, a method comprises: receiving, at a network adapter, an access request from a client, the access request including first header information and first payload information; transmitting the first header information to a load balancing server associated with the network adapter; receiving the updated first header information from the load balancing server, wherein the updated first header information is determined by the load balancing server based on the received first header information and an identifier of the load balancing server, and wherein the updated first header information indicates a destination server to which the access request is to be transmitted; and, generating, based on the updated first header information and the first payload information, an updated access request. Accordingly, the processing capability of load balancing servers and the performance of load balancing servers in a network system may be improved effectively.

Claims (76)

1. A method for managing a network system, comprising:

receiving, at a network adapter, an access request from a client, the access request including first header information and first payload information;

transmitting the first header information to a load balancing server associated with the network adapter;

receiving updated first header information from the load balancing server, wherein the updated first header information is determined by the load balancing server based on the received first header information and an identifier of the load balancing server, and wherein the updated first header information indicates a destination server to which the access request is to be transmitted; and

generating, based on the updated first header information and the first payload information, an updated access request;

wherein transmitting the first header information to the load balancing server comprises:

removing the first payload information from the access request to obtain a modified access request, the modified access request including the first header information and an indicator representing the removed first payload information; and

transmitting the modified access request to the load balancing server; and

wherein generating the updated access request comprises:

obtaining, from the load balancing server, a correspondence between the load balancing server and the client; and

determining, from a set of stored payload information and based on the correspondence, the first payload information corresponding to the updated first header information.

2. The method of claim 1 , further comprising:

transmitting the updated access request to the destination server.

3. The method of claim 1 , further comprising:

storing the first payload information in a set of payload information.

4. The method of claim 1 , further comprising:

receiving, at the network adapter, a response to the access request from the destination server, the response including second header information and second payload information;

transmitting the second header information to the load balancing server;

receiving the updated second header information from the load balancing server, wherein the updated second header information is determined by the load balancing server based on the received second header information and the identifier of the load balancing server, and wherein the updated second header information indicates the client to which the response is to be transmitted; and

generating, based on the updated second header information and the second payload information, an updated response.

5. The method of claim 4 , further comprising:

obtaining, from the load balancing server, a correspondence between the load balancing server and the client; and

determining, from a set of stored payload information and based on the correspondence, the second payload information corresponding to the updated second header information.

6. The method of claim 1 , wherein the access request comprises a predefined format; and

wherein generating the updated access request comprises maintaining the predefined format.

7. The method of claim 6 , wherein generating the updated access request comprises setting, by a packet regenerator module, the indicator, the indicator replacing the removed first payload information.

8. The method of claim 7 , wherein setting the indicator includes assigning, by the packet regenerator module, a value corresponding to zero to the indicator representing removal of all data of the first payload information from the modified access request.

9. The method of claim 7 , wherein the access request comprises a packet having a header field with the first header information and a payload field with the first payload information; and

wherein generating the updated access request comprises replacing the payload field with the indicator.

10. A method of managing a network system, comprising:

receiving, from a network adapter, first header information in an access request from a client, the access request comprising the first header information and first payload information;

updating the first header information based on the received first header information and an identifier of a load balancing server associated with the network adapter, the updated first header information indicating a destination server to which the access request is to be transmitted and excluding the first payload information; and

transmitting the updated first header information to the network adapter to enable the network to generate an updated access request based on the updated first header information and the first payload information in the access request.

11. The method of claim 10 , further comprising:

generating a correspondence between the load balancing server and the client; and

transmitting the correspondence to the network adapter.

12. The method of claim 10 , wherein updating the first header information comprises:

obtaining an identifier of the client from the first header information; and

replacing the identifier of the client with the identifier of the load balancing server.

13. The method of claim 10 , further comprising:

receiving, from the network adapter, second header information in a response to the access request from the destination server;

updating the second header information based on the received second header information and the identifier of the load balancing server, the updated second header information indicating the client to which the response is to be transmitted; and

transmitting the updated second header information to the network adapter such that the network adapter generates an updated response based on the updated second header information and second payload information in the response.

14. The method of claim 13 , further comprising:

obtaining a correspondence between the load balancing server and the client; and

transmitting the correspondence to the network adapter such that the network adapter determines, from a set of stored payload information and based on the correspondence, the second payload information corresponding to the updated second header information.

15. The method of claim 10 , wherein transmitting the updated first header information to the network adapter is performed such that the network adapter combines the updated first header information and the first payload information to generate the updated access request.

16. A device for managing a network system, comprising:

one or more processors;

a memory coupled to at least one of the one or more processers; and

computer program instructions stored in the memory that, when executed by the at least one processor, cause the device to execute acts, the acts comprising:

receiving, at a network adapter, an access request from a client, the access request including first header information and first payload information;

transmitting the first header information to a load balancing server associated with the network adapter;

receiving the updated first header information from the load balancing server, wherein the updated first header information is determined by the load balancing server based on the received first header information and an identifier of the load balancing server, and wherein the updated first header information indicates a destination server to which the access request is to be transmitted; and

generating, based on the updated first header information and the first payload information, an updated access request;

wherein transmitting the first header information to the load balancing server comprises:

removing the first payload information from the access request to obtain a modified access request, the modified access request including the first header information and an indicator representing the removed first payload information; and

transmitting the modified access request to the load balancing server; and

wherein generating the updated access request comprises:

obtaining, from the load balancing server, a correspondence between the load balancing server and the client; and

determining, from a set of stored payload information and based on the correspondence, the first payload information corresponding to the updated first header information.

17. The device of claim 16 , wherein the acts further comprise:

transmitting the updated access request to the destination server; and

storing the first payload information in a set of payload information.

18. The device of claim 16 , wherein

generating the updated access request comprises:

obtaining, from the load balancing server, a correspondence between the load balancing server and the client; and

determining, from a set of stored payload information and based on the correspondence, the first payload information corresponding to the updated first header information.

19. The device of claim 16 , wherein the acts further comprise:

receiving, at the network adapter, a response to the access request from the destination server, the response including second header information and second payload information;

transmitting the second header information to the load balancing server;

receiving the updated second header information from the load balancing server, wherein the updated second header information is determined by the load balancing server based on the received second header information and the identifier of the load balancing server, and wherein the updated second header information indicates the client to which the response is to be transmitted; and

generating, based on the updated second header information and the second payload information, an updated response.

20. The device of claim 19 , wherein the acts further comprise:

obtaining, from the load balancing server, a correspondence between the load balancing server and the client; and

determining, from a set of stored payload information and based on the correspondence, the second payload information corresponding to the updated second header information.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (050724/0466) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO WYSE TECHNOLOGY L.L.C.)
Reel/Frame 060753/0486 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 060438/0742 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST AT REEL 050405 FRAME 0534 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058001/0001 →
SECURITY INTEREST Recorded Jun 5, 2020
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 053311/0169 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Oct 15, 2019
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 050724/0466 →
SECURITY AGREEMENT Recorded Sep 17, 2019
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 050405/0534 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 3, 2019
From: CHEN, FEI; LIU, FUCAI; ZHAO, JUNPING
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 049077/0080 →
Priority Claims (1)
CN 201810621512.8 · Jun 15, 2018 · national
Continuity (1)
Related Publication 20190387051A1 · Dec 19, 2019
Cited By (1)
US 12,405,906