IP Library › Granted Patent US 12,294,499
Granted Patent B1
US 12,294,499 · App. 18/501,305 · Granted May 6, 2025

Pluggable transceiver to facilitate network traffic analysis

Inventors: Jason Curry (Raleigh, NC); Seisaku Nomura (Waynesboro, PA); Mark Gunville (Hampton, NH); Michael Sack (Linden, MI)
Assignee: VIAVI Solutions Inc.
H04L41/12
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 12,294,499
App. No.
18/501,305
Granted
May 6, 2025
Kind
B1
Abstract

A pluggable transceiver receives, from a client, a first message that indicates a first source IP address as being an IP address of a client, a first destination IP address as being an IP address of the pluggable transceiver, a first source port as being a port of the client, and a first destination port as being a port of the pluggable transceiver. The pluggable transceiver updates the first message to indicate the first source IP address as being the IP address of the pluggable transceiver, the first destination IP address as being an IP address of a server, and the first destination port as being a port of the server. The pluggable transceiver sends the updated first message to the server.

Claims (64)

1. A pluggable transceiver, comprising:

one or more hardware processors, configured to:

receive, from a client network device, a first control message that includes a control enablement parameter and a server identifier parameter that indicates an Internet protocol (IP) address of a server network device;

receive, from the client network device and after receiving the first control message, a first message that indicates a first source IP address as being an IP address of the client network device, a first destination IP address as being an IP address of the pluggable transceiver, a first source port as being a port of the client network device, and a first destination port as being a port of the pluggable transceiver;

update the first message to indicate the first source IP address as being the IP address of the pluggable transceiver, the first destination IP address as being the IP address of the server network device, and the first destination port as being a port of the server network device;

send, to the server network device, the updated first message;

receive, from the server network device and after receiving the first control message, a second message that indicates a second source IP address as being an IP address of the server network device, a second destination IP address as being the IP address of the pluggable transceiver, a second source port as being a port of the server network device, and a second destination port as being the port of the client network device;

update the second message to indicate the second source IP address as being the IP address of the pluggable transceiver, the second destination IP address as being the IP address of the client network device, and the second source port as being the port of the pluggable transceiver; and

send, to the client network device, the updated second message.

2. The pluggable transceiver of claim 1 , wherein the pluggable transceiver is configured to be included in another network device, wherein:

the pluggable transceiver is configured to connect to the client network device via a first network segment, and

the pluggable transceiver is configured to connect to the server network device via a second network segment.

3. The pluggable transceiver of claim 1 , wherein updating the first message includes causing at least one of:

a network layer checksum value of the first message to be updated, or

a transport layer checksum value of the first message to be updated.

4. The pluggable transceiver of claim 1 , wherein updating the second message includes causing a network layer checksum value of the second message to be updated.

5. The pluggable transceiver of claim 1 , wherein the first control message further indicates a third source IP address as being the IP address of the client network device and a third destination IP address as being the IP address of the pluggable transceiver, and

wherein the one or more hardware processors are further configured to:

send, based on receiving the control message, a response message that indicates a fourth source IP address as being the IP address of the pluggable transceiver, a fourth destination IP address as being the IP address of the client network device, and a control enablement acknowledgement parameter.

6. The pluggable transceiver of claim 1 , wherein the one or more hardware processors are further configured to:

receive, after sending the first message and sending the second message, a second control message that indicates a third source IP address as being the IP address of the client network device, a third destination IP address as being the IP address of the pluggable transceiver, and a control disablement parameter; and

send, based on receiving the second control message, a response message that indicates a fourth source IP address as being the IP address of the pluggable transceiver, a fourth destination IP address as being the IP address of the client network device, and a control disablement acknowledgement parameter.

7. The pluggable transceiver of claim 1 , wherein at least one of:

the IP address of the client network device, the IP address of the pluggable transceiver, and the IP address of the server network device are different, or

the port of the pluggable transceiver and the port of the server network device are the same.

8. The pluggable transceiver of claim 1 , wherein at least one of:

the IP address of the client network device and the IP address of the server network device are the same, or

the port of the pluggable transceiver and the port of the server network device are the same.

9. A pluggable transceiver, comprising:

one or more hardware processors, configured to:

receive a first message that includes a first network layer header and a first transport layer header,

wherein the first network layer header indicates a first source Internet protocol (IP) address as being an IP address of a client and a first destination IP address as being an IP address of the pluggable transceiver, and

wherein the first transport layer header indicates a first source port as being a port of the client and a first destination port as being a port of the pluggable transceiver;

update the first network layer header and the first transport layer header of the first message to indicate the first source IP address as being the IP address of the pluggable transceiver, the first destination IP address as being an IP address of a server, and the first destination port as being a port of the server;

send, after updating the first network layer header and the first transport layer header of the first message, the first message;

receive a second message that includes a second network layer header and a second transport layer header,

wherein the second network layer header indicates a second source IP address as being an IP address of the server and a second destination IP address as being the IP address of the pluggable transceiver, and

wherein the second transport layer header indicates a second source port as being a port of the server and a second destination port as being the port of the client;

update the second network layer header and the second transport layer header of the second message to indicate the second source IP address as being the IP address of the pluggable transceiver, the second destination IP address as being the IP address of the client, and the second source port as being the port of the pluggable transceiver;

send, after updating the second network layer header of the second message, the second message; and

receive, after sending the first message and sending the second message, a first control message that includes a control disablement parameter.

10. The pluggable transceiver of claim 9 , wherein the pluggable transceiver is configured to be included in a network device.

11. The pluggable transceiver of claim 10 , wherein the client is associated with a first other network device and the server is associated with a second other network device.

12. The pluggable transceiver of claim 10 , wherein the client and the server are each associated with another network device.

13. The pluggable transceiver of claim 10 , wherein the one or more hardware processors are further configured to:

receive, prior to receiving the first message and receiving the second message, a second control message that includes a control enablement parameter and a server identifier parameter that indicates the IP address of the server; and

send, after receiving the second control message, a response message that includes a control enablement acknowledgement parameter.

14. The pluggable transceiver of claim 10 , wherein the one or more hardware processors are further configured to:

send, after receiving the first control message, a response message that includes a control disablement acknowledgement parameter.

15. A method, comprising:

receiving, by a pluggable transceiver, a first message that indicates a first source Internet protocol (IP) address as being an IP address of a client, a first destination IP address as being an IP address of the pluggable transceiver, a first source port as being a port of the client, and a first destination port as being a port of the pluggable transceiver;

sending, by the pluggable transceiver, the first message,

wherein the first message is updated to indicate the first source IP address as being the IP address of the pluggable transceiver, the first destination IP address as being an IP address of a server, and the first destination port as being a port of the server;

receiving, by the pluggable transceiver, a second message that indicates a second source IP address as being an IP address of the server, a second destination IP address as being the IP address of the pluggable transceiver, a second source port as being a port of the server, and a second destination port as being the port of the server;

sending, by the pluggable transceiver, the second message,

wherein the second message is updated to indicate the second source IP address as being the IP address of the pluggable transceiver, the second destination IP address as being the IP address of the client, and the second source port as being the port of the pluggable transceiver; and

receiving, by the pluggable transceiver, at least one of a first control message, before the first message and the second message, or a second control message, after the first message and the second message, wherein at least one of:

the first control message includes a control enablement parameter and a server identifier parameter that indicates the IP address of the server, or

the second control message includes a control disablement parameter.

16. The method of claim 15 , wherein the IP address of the client, the IP address of the pluggable transceiver, and the IP address of the server are different.

17. The method of claim 15 , wherein the IP address of the client and the IP address of the server are the same.

18. The method of claim 15 , wherein the port of the pluggable transceiver and the port of the server are the same.

19. The method of claim 15 , wherein the client is associated with a first network device and the server is associated with a second other network device.

20. The method of claim 15 , wherein the client and the server are each associated with a network device.

Assignments (5)
RELEASE OF SECURITY INTEREST AT REEL/FRAME 73189/0873 Recorded May 28, 2026
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT
To: INERTIAL LABS, INC.; VIAVI SOLUTIONS INC.; VIAVI SOLUTIONS LICENSING LLC
Reel/Frame 075642/0381 →
SECURITY INTEREST Recorded Nov 14, 2025
From: VIAVI SOLUTIONS INC.; VIAVI SOLUTIONS LICENSING LLC; INERTIAL LABS, INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS AGENT
Reel/Frame 073571/0137 →
SECURITY AGREEMENT Recorded Oct 21, 2025
From: INERTIAL LABS, INC.; VIAVI SOLUTIONS INC.; VIAVI SOLUTIONS LICENSING LLC
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT
Reel/Frame 073189/0873 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF ASSIGNOR #3 AND ADDRESS OF ASSIGNEE PREVIOUSLY RECORDED ON REEL 65464 FRAME 228. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jan 10, 2025
From: CURRY, JASON; NOMURA, SEISAKU; GUNVILLE, MARK; SACK, MICHAEL
To: VIAVI SOLUTIONS INC.
Reel/Frame 069871/0009 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 6, 2023
From: CURRY, JASON; NOMURA, SEISAKU; GUNVILLE, MARK RICHARD; SACK, MICHAEL
To: VIAVI SOLUTIONS INC.
Reel/Frame 065464/0228 →
References Cited (7)
US 6415329B1 · Gelman · 2002 [cited by examiner]
US 9118601B2 · Chouinard et al. · 2015 [cited by applicant]
US 9438503B2 · Coomber et al. · 2016 [cited by applicant]
US 10659569B1 · Tourrilhes · 2020 [cited by examiner]
US 20170223151A1 · Brunner · 2017 [cited by examiner]
US 20170251026A1 · Straub · 2017 [cited by examiner]
US 20190104076A1 · Seetharaman · 2019 [cited by examiner]