IP Library Granted Patent US 8,626,925
Granted Patent B2
US 8,626,925 · App. 11/305,838 · Granted Jan 7, 2014

Systems and methods for providing a selective multicast proxy on a computer network

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,626,925
App. No.
11/305,838
Granted
Jan 7, 2014
Kind
B2
Abstract

A plurality of non-multicast nodes that do not process multicast messages register with a selective multicast proxy. In response to receiving a request for a service from a requestor via multicast, the selective multicast proxy identifies among the plurality of non-multicast nodes one or more providers of the requested service. The selective multicast proxy sends the request to the one or more providers without sending the request to other non-multicast nodes on the computer network. The selective multicast proxy, the requestor of the service, the provider(s) of the service, and the non-multicast nodes may all be located within the same local area network.

Claims (47)

1. A method for processing multicast requests on a computer network, comprising:

receiving, at a proxy server, registration of a plurality of non-multicast nodes that do not process multicast messages, wherein at least one non-multicast node is a multicast node configured to or notified not to process multicast messages;

receiving, at the proxy server, a request for a service from a requestor via multicast;

identifying, at the proxy server, among the plurality of non-multicast nodes one or more providers of the requested service; and

sending the request from the proxy server, not using multicast, to the one or more providers without sending the request to other non-multicast nodes on the computer network, wherein the proxy server sends the request, which was previously multicast, such that at least one of the one or more providers responds to the request although the one or more providers comprise non-multicast nodes that do not process multicast messages.

2. The method of claim 1 , further comprising:

receiving at least one response to the request from the one or more providers; and

sending the at least one response to the requestor.

3. The method of claim 1 , wherein the request is sent to the one or more providers via a connection-based protocol.

4. The method of claim 1 , wherein the request is sent to the one or more providers via a connectionless protocol.

5. The method of claim 1 , wherein identifying the one or more providers comprises:

detecting a service identifier within the request that identifies the requested service; and

searching for the service identifier within a database of registered nodes.

6. The method of claim 1 , further comprising identifying a plurality of potential providers with a same node identifier, and wherein identifying a provider comprises selecting the provider from among the plurality of potential providers with the same node identifier.

7. The method of claim 1 , wherein receiving registration of the multicast node configured to or notified not to process multicast messages comprises periodically sending a proxy announcement message via multicast.

8. The method of claim 7 , wherein sending the proxy announcement is performed by a selective proxy server connected to the multicast node configured to or notified not to process multicast messages, and wherein the receiving of the proxy announcement message by the multicast node configured to or notified not to process multicast messages results in the multicast node configured to or notified not to process multicast messages ceasing to process multicast requests as long as the multicast node configured to or notified not to process multicast messages remains connected to the selective proxy server.

9. The method of claim 1 , wherein the plurality of non-multicast nodes comprises at least one resource constrained node that is not capable of processing multicast messages.

10. The method of claim 1 , wherein the proxy server, the requestor, and the plurality of non-multicast nodes are all located within a same local area network.

11. A computer system that is configured for processing multicast requests on a computer network, the computer system comprising:

a processor;

memory in electronic communication with the processor;

instructions stored in the memory, the instructions being executable to:

receive, at a proxy server, registration of a plurality of non-multicast nodes that do not process multicast messages, wherein at least one non-multicast node is a multicast node configured to or notified not to process multicast messages;

receive, at the proxy server, a request for a service from a requestor via multicast;

identify, at the proxy server, among the plurality of non-multicast nodes one or more providers of the requested service; and

send the request from the proxy server, not using multicast, to the one or more providers without sending the request to other non-multicast nodes on the computer network, wherein the proxy server sends the request, which was previously multicast, such that at least one of the one or more providers responds to the request although the one or more providers comprise non-multicast nodes that do not process multicast messages.

12. The computer system of claim 11 , wherein the instructions are further executable to:

receive at least one response to the request from the one or more providers; and

send the at least one response to the requestor.

13. The computer system of claim 11 , wherein the request is sent to the one or more providers via a connection-based protocol.

14. The computer system of claim 11 , wherein the request is sent to the one or more providers via a connectionless protocol.

15. The computer system of claim 11 , wherein the instructions executable to identify the one or more providers comprise instructions executable to:

detect a service identifier within the request that identifies the requested service; and

search for the service identifier within a database of registered nodes.

16. A non-transitory computer storage medium comprising executable instructions for processing multicast requests on a computer network, the instructions being executable to:

receive, at a proxy server, registration of a plurality of non-multicast nodes that do not process multicast messages, wherein at least one non-multicast node is a multicast node configured to or notified not to process multicast messages;

receive, at the proxy server, a request for a service from a requestor via multicast;

identify, at the proxy server, among the plurality of non-multicast nodes one or more providers of the requested service; and

send the request from the proxy server, not using multicast, to the one or more providers without sending the request to other non-multicast nodes on the computer network, wherein the proxy server sends the request, which was previously multicast, such that at least one of the one or more providers responds to the request although the one or more providers comprise non-multicast nodes that do not process multicast messages.

17. The non-transitory computer storage medium of claim 16 , wherein the instructions are further executable to:

receive at least one response to the request from the one or more providers; and

send the at least one response to the requestor.

18. The non-transitory computer storage medium of claim 16 , wherein the request is sent to the one or more providers via a connection-based protocol.

19. The non-transitory computer storage medium of claim 16 , wherein the request is sent to the one or more providers via a connectionless protocol.

20. The non-transitory computer storage medium of claim 16 , wherein the instructions executable to identify the one or more providers comprise instructions executable to:

detect a service identifier within the request that identifies the requested service; and

search for the service identifier within a database of registered nodes.

Assignments (3)
MERGER Recorded Feb 13, 2012
From: PANASONIC ELECTRIC WORKS CO.,LTD.,
To: PANASONIC CORPORATION
Reel/Frame 027697/0525 →
CHANGE OF NAME Recorded Jan 28, 2009
From: MATSUSHITA ELECTRIC WORKS, LTD.
To: PANASONIC ELECTRIC WORKS CO., LTD.
Reel/Frame 022206/0574 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2006
From: MILLIGAN, THOMAS; EASTHAM, BRYANT
To: MATSUSHITA ELECTRIC WORKS, LTD.
Reel/Frame 017552/0437 →