IP Library Granted Patent US 8,949,391
Granted Patent B2
US 8,949,391 · App. 10/911,378 · Granted Feb 3, 2015

Network management across a NAT or firewall

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,949,391
App. No.
10/911,378
Granted
Feb 3, 2015
Kind
B2
Abstract

The present invention relates to methods of, computer software for and apparatus for enabling network management in a network arrangement in which a first network is separated from a second network by a network address translator or firewall. More particularly, but not exclusively, the present invention enables, in a carrier hosted solution, a) operational information relating to a device or equipment in a customer network and for use in a network management system of a carrier network and b) control information to be provided to the device or equipment by the network management system to traverse the network address translator or firewall separating the carrier and customer networks. The traversal of the network address translator or firewall is achieved by inserting the operational or control information in keep alive signalling used maintain the NAT bind or firewall pinhole.

Claims (50)

1. A method of communicating operational information for use in a network management system across a NAT or firewall connecting a first and a second network, the method comprising the steps of:

generating information indicating a detected operational condition of a device or equipment in the first network;

inserting the generated information in a keep alive message for maintaining a NAT bind or firewall pinhole in the NAT or firewall; and

sending the keep alive message across the NAT or firewall to an entity in the second network.

2. A method according to claim 1 , wherein the keep alive message is a call control protocol message.

3. A method according to claim 1 , wherein the entity in the second network is a call control entity.

4. Apparatus for communicating operational information for use in a network management system across a NAT or firewall connecting a first and a second network, the apparatus comprising:

an information generator arranged to generate information indicating a detected operational condition of a device or equipment in the first network;

an inserter arranged to insert the generated information in a keep alive message for maintaining a NAT bind or firewall pinhole in the NAT or firewall; and

an output interface arranged to send the keep alive message across the NAT or firewall from the first network to an entity in the second network.

5. An apparatus according to claim 4 , wherein the keep alive message is a call control protocol message.

6. An apparatus according to claim 4 , wherein the entity in the second network is a call control entity.

7. A method of communicating operational information for use in a network management system across a NAT or firewall connecting a first and a second network, the method comprising the steps of:

an entity in the second network receiving a keep alive message for maintaining a NAT bind or firewall pinhole in the NAT or firewall, the keep alive message comprising information indicating a detected operational condition of a device or equipment in the first network; and

the entity forwarding the information or the keep alive message to the network management system.

8. A method according to claim 7 , wherein the forwarding step is selectively performed in dependence on the entity detecting that the information is new.

9. A method according to claim 7 , wherein the entity in the second network is a call control entity.

10. A method according to claim 7 , wherein the keep alive message is a call control protocol message.

11. A server for communicating operational information for use in a network management system across a NAT or firewall connecting a first and a second network, the server comprising:

an input interface arranged to receive a keep alive message for maintaining a NAT bind or firewall pinhole in the NAT or firewall from a device, the keep alive message comprising information indicating a detected operational condition of a device or equipment in the first network; and

a forwarder arranged to forward the information or the keep alive message to the network management system via an output interface.

12. A server according to claim 11 , wherein the server comprises a detector arranged to detect whether the information is new and wherein the forwarder is arranged to selectively forward the information in dependence on the detector detecting that the information is new.

13. A server according to claim 11 , wherein the server is a call control entity.

14. A server according to claim 11 , wherein the keep alive message is a call control protocol message.

15. A method of communicating network management control commands across a NAT or firewall connecting a first and a second network, the method comprising the steps of:

an entity in the second network receiving a network management control command for a device in the first network;

the entity inserting the control command in a keep alive message for maintaining a NAT bind or firewall pinhole in the NAT or firewall; and

the entity sending the keep alive message across the NAT or firewall to the device.

16. A method according to claim 15 , wherein the keep alive message is a call control protocol message.

17. A method according to claim 15 , wherein the entity in the second network is a call control entity.

18. A method according to claim 15 , wherein the entity stores the received network management control command until the keep alive message is ready to be sent.

19. A method according to claim 15 , wherein receipt of the network management control command triggers sending of the keep alive message.

20. A hardware device for communicating network management control commands across a NAT or firewall connecting a first and a second network, the server comprising:

an input interface arranged to receive a network management control command for a device in the first network;

an inserter arranged to insert the control command in a keep alive message for maintaining a NAT bind or firewall pinhole in the NAT or firewall; and

an output interface arranged to send the keep alive message across the NAT or firewall from the first network to the second network.

21. A hardware device according to claim 20 , wherein the keep alive message is a call control protocol message.

22. A hardware device according to claim 20 , wherein the apparatus is a call control entity.

23. A method of communicating network management control commands across a NAT or firewall connecting a first and a second network, the method comprising the steps of:

a device in the first network receiving a keep alive message from an entity in the second network, the keep alive message being for maintaining a NAT bind or firewall pinhole in the NAT or firewall;

the device detecting that the received keep alive message comprises a network management control command for the device or for another device or equipment in the first network; and

the device initiating execution of the network management control command in response to the detecting.

24. A method according to claim 23 , wherein the keep alive message is a call control protocol message.

25. A method according to claim 23 , wherein the entity in the second network is a call control entity.

26. A server for communicating network management control commands across a NAT or firewall connecting a first and a second network, the server comprising:

an input interface arranged to receive a keep alive message from an entity in the second network, the keep alive message being for maintaining a NAT bind or firewall pinhole in the NAT or firewall;

a command detector arranged to detect if the received keep alive message comprises a network management control command for the device or for another device or equipment in the first network; and

a command executor arranged to initiate execution of the network management control command in response to the detecting.

27. A server according to claim 26 , wherein the keep alive message is a call control protocol message.

28. A server according to claim 26 , wherein the entity in the second network is a call control entity.

Assignments (8)
RELEASE OF SECURITY INTEREST Recorded Oct 26, 2020
From: JEFFERIES FINANCE LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 054305/0505 →
SECURITY INTEREST Recorded Jun 29, 2018
From: RPX CLEARINGHOUSE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 046485/0644 →
RELEASE (REEL 038041 / FRAME 0001) Recorded Jan 2, 2018
From: JPMORGAN CHASE BANK, N.A.
To: RPX CORPORATION; RPX CLEARINGHOUSE LLC
Reel/Frame 044970/0030 →
SECURITY AGREEMENT Recorded Mar 9, 2016
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 038041/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2015
From: ROCKSTAR CONSORTIUM US LP; ROCKSTAR CONSORTIUM LLC; BOCKSTAR TECHNOLOGIES LLC; CONSTELLATION TECHNOLOGIES LLC; MOBILESTAR TECHNOLOGIES LLC; NETSTAR TECHNOLOGIES LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 034924/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2014
From: ROCKSTAR BIDCO, LP
To: ROCKSTAR CONSORTIUM US LP
Reel/Frame 032425/0867 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2011
From: NORTEL NETWORKS LIMITED
To: ROCKSTAR BIDCO, LP
Reel/Frame 027143/0717 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 4, 2004
From: KETTLEWELL, PAUL; MITCHELL, JULIAN; ARAMBEPOLA, SUJATA
To: NORTEL NETWORKS LIMITED
Reel/Frame 015668/0373 →