IP Library Granted Patent US 8,700,775
Granted Patent B2
US 8,700,775 · App. 11/903,219 · Granted Apr 15, 2014

Routing of communications to a platform service

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 8,700,775
App. No.
11/903,219
Granted
Apr 15, 2014
Kind
B2
Abstract

Systems and methods for routing communications to a platform service are provided. A message including payload data is received. The information in the payload data of the message is examined in order to determine the type of message. The message is then relayed to an appropriate platform service based on the type of message. Some embodiments assign numbers to the packets that make up the message.

Claims (37)

1. A method for routing a communication to a platform service, the method comprising:

receiving a first message and a second message in a first communication;

sending an acknowledgement message to a source of the first communication in reply to the first message;

analyzing payload data contained in the second message to identify a communication type, wherein the communication type is specific to one of a plurality of platform service types available for routing, the available plurality of platform service types including a virtual private network platform service and an extranet platform service;

sending a first message and a second message in a second communication to a corresponding platform service of the platform service type specific to the communication type indicated by the payload data, wherein the second message in the second communication includes the payload data contained in the second message of the first communication;

receiving an acknowledgement of the first message from the corresponding platform service;

receiving a reply responsive to the second message in the second communication from the corresponding platform service; and

relaying the reply from the corresponding platform service to the source of the first communication.

2. The method of claim 1 , wherein the first and second messages in the first communication are sequentially numbered and the first and second messages in the second communication are sequentially numbered differently from the first and second messages in the first communication; and the method further comprises:

modifying the sequential numbering of the second message in the first communication to correspond with the sequential numbering of the second communication with the corresponding platform service, and

modifying the sequential numbering of the reply to the second message in the second communication to correspond with the sequential numbering of the first communication.

3. A method for routing a first communication to a platform service, the method comprising:

receiving the first communication comprising payload data;

determining a communication type for the first communication based on at least information provided by the payload data, wherein the communication type is specific to one of a plurality of platform service types available for routing, the available plurality of platform service types including a virtual private network platform service and an extranet platform service; and

relaying the first communication to a corresponding platform service being of the platform service type specific to the communication type of the first communication.

4. The method of claim 3 , further comprising receiving a reply from the corresponding platform service and relaying the reply to a source of the first communication.

5. The method of claim 3 , wherein the first communication is transmitted using sequentially numbered packets.

6. The method of claim 3 , further comprising:

receiving a second communication, the second communication directed to a same internet protocol (IP) address and comprising different payload data than the payload data of the first communication; and

determining a communication type for the second communication based on at least information provided by the different payload data, wherein one of the first and second communications is determined to be a communication type specific to a virtual private network platform service and the other of the first and second communications is determined to be a communication type specific to an extranet platform service.

7. The method of claim 3 , wherein the payload data of the first communication includes a virtual private network protocol frame.

8. The method of claim 3 , wherein the payload data of the first communication includes a secure socket layer (SSL) helo message.

9. The method of claim 3 , further comprising sending an acknowledgement to a source of the first communication in response to receiving a portion of the first communication.

10. The method of claim 3 , further comprising receiving a reply from the available platform service in response to the relayed first communication.

11. The method of claim 10 , further comprising forwarding the received reply to a source of the relayed first communication.

12. The method of claim 10 , further comprising sending an acknowledgement to the corresponding platform service in response to the received reply.

13. The method of claim 3 , wherein the virtual private network platform service has a different port number than the extranet platform service.

14. The method of claim 3 , wherein port numbers for the virtual private network platform service and the extranet platform service are set based on user input.

15. The method of claim 14 , wherein the first communication is sent to a port number associated with a transfer protocol and wherein the port number associated with the transfer protocol is different from the port numbers set for the virtual private network platform service and the extranet platform service.

16. A system for routing a communication to a platform service, the system comprising:

an input configured to receive the communication comprising payload data;

a processor configured to execute instructions stored in memory for determining a communication type based on at least information provided by the payload data and received at the input wherein the communication type is specific to one of a plurality of platform service types available for routing, the available plurality of platform service types including a virtual private network platform service and an extranet platform service; and

an output configured to relay the communication received at the input to a corresponding platform service being of the platform service type specific to the communication type of the communication, the corresponding platform service selected from a plurality of platform services.

17. A non-transitory computer-readable storage medium, having embodied thereon a program executable by a processor to perform a method for routing a first communication to a platform service, the method comprising:

receiving the first communication comprising payload data;

determining a communication type for the first communication based on at least information provided by the payload data, wherein the communication type is specific to one of a plurality of platform service types available for routing, the available plurality of platform service types including a virtual private network platform service and an extranet platform service; and

relaying the first communication to a corresponding platform service of the platform service type specific to the communication type of the first communication.

Assignments (20)
FIRST LIEN IP SUPPLEMENT Recorded Jun 30, 2025
From: SONICWALL US HOLDINGS INC.
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 071777/0641 →
RELEASE OF SECOND LIEN SECURITY INTEREST IN PATENTS RECORDED AT RF 046321/0393 Recorded Jun 16, 2025
From: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
To: SONICWALL US HOLDINGS INC.
Reel/Frame 071625/0887 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jun 7, 2018
From: SONICWALL US HOLDINGS INC.
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 046321/0414 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Jun 7, 2018
From: SONICWALL US HOLDINGS INC.
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 046321/0393 →
RELEASE OF FIRST LIEN SECURITY INTEREST IN PATENTS RECORDED AT R/F 040581/0850 Recorded May 22, 2018
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
To: QUEST SOFTWARE INC. (F/K/A DELL SOFTWARE INC.); AVENTAIL LLC
Reel/Frame 046211/0735 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE PREVIOUSLY RECORDED AT REEL: 040587 FRAME: 0624. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Nov 28, 2017
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: QUEST SOFTWARE INC. (F/K/A DELL SOFTWARE INC.); AVENTAIL LLC
Reel/Frame 044811/0598 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NATURE OF CONVEYANCE PREVIOUSLY RECORDED AT REEL: 041072 FRAME: 235. ASSIGNOR(S) HEREBY CONFIRMS THE INTELLECTUAL PROPERTY ASSIGNMENT AGREEMENT. Recorded Apr 5, 2017
From: AVENTAIL LLC
To: SONICWALL US HOLDINGS INC.
Reel/Frame 042245/0523 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Jan 23, 2017
From: AVENTAIL LLC
To: SONICWALL US HOLDINGS, INC.
Reel/Frame 041072/0235 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Nov 10, 2016
From: DELL SOFTWARE INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040587/0624 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Nov 9, 2016
From: DELL SOFTWARE INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040581/0850 →
RELEASE OF SECURITY INTEREST IN CERTAIN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040039/0642) Recorded Oct 31, 2016
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVENTAIL LLC; DELL PRODUCTS L.P.; DELL SOFTWARE INC.
Reel/Frame 040521/0016 →
RELEASE OF SECURITY INTEREST Recorded Oct 31, 2016
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: AVENTAIL LLC; DELL PRODUCTS, L.P.; DELL SOFTWARE INC.
Reel/Frame 040521/0467 →
SECURITY AGREEMENT Recorded Sep 14, 2016
From: AVENTAIL LLC; DELL PRODUCTS L.P.; DELL SOFTWARE INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 040039/0642 →
SECURITY AGREEMENT Recorded Sep 14, 2016
From: AVENTAIL LLC; DELL PRODUCTS, L.P.; DELL SOFTWARE INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040030/0187 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORDED ON REEL/FRAME 024776/0337 Recorded May 8, 2012
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: AVENTAIL LLC; SONICWALL, INC.
Reel/Frame 028177/0115 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORDED ON REEL/FRAME 024823/0280 Recorded May 8, 2012
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: AVENTAIL LLC; SONICWALL, INC.
Reel/Frame 028177/0126 →
SECURITY AGREEMENT Recorded Aug 3, 2010
From: AVENTAIL LLC; SONICWALL, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 024776/0337 →
PATENT SECURITY AGREEMENT (SECOND LIEN) Recorded Aug 3, 2010
From: AVENTAIL LLC; SONICWALL, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 024823/0280 →
MERGER Recorded Feb 4, 2009
From: AVENTAIL CORPORATION
To: AVENTAIL LLC
Reel/Frame 022200/0475 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 21, 2007
From: HOPEN, CHRIS; TOMLINSON, GARY B.; BROOKE, JOHN; BROWN, DEREK W.; BURDGE, JONATHAN; ERICKSON, RODGER D.
To: AVENTAIL CORPORATION
Reel/Frame 019923/0039 →