METHOD FOR AVOIDING A LOOP WHEN FORWARDING A MESSAGE, RESPECTIVE COMMUNICATIONS DEVICE AND SYSTEM

• US 20160269276A1
• Filed: 10/17/2014
• Published: 09/15/2016
• Est. Priority Date: 10/24/2013
• Status: Abandoned Application

• Current Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Original Assignee: Tomson Lajsensing S A
• Inventors: GYSELINCK, Luc, VOET, Jan, STES, Bram
• Application Number:
  US15/031,708
• Publication Number:
  US 20160269276A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/2801 Broadband local area networks
• CPC Class Codes: H04L 12/2854 Wide area networks, e.g. public data networks
• CPC Class Codes: H04L 45/18 Loop-free operations
• CPC Class Codes: H04L 65/102 Gateways arrangements for connecting between networks having differing types of switching systems, e.g. gateways, H04L12/66
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]

Abstract

The method for avoiding a loop when forwarding a message from a first participant of a first LAN to a participant of a second LAN via several forwarding servers of a wide area network (WAN) comprises the steps of: including each time an identifying address of the sending forwarding server in the message by the receiving forwarding server, and keeping each identifying address in the message. The message is in particular an RTPS message including an InfoSource submessage, and each added identifying address is stored in the InfoSource submessage.

Claims

1. Method for avoiding a loop when forwarding a message from a first participant of a first Local Area Network to a participant of a second LAN via several forwarding servers of a wide area network, comprising the steps of

including each time an identifying address of the sending forwarding server in the message by the receiving forwarding server, and keeping each identifying address in the message.

2. Method according to claim 1, wherein the forwarding servers are Internet servers forwarding messages in accordance with a Data Distribution Service for Real-Time Systems (DDS) or in accordance with a Real-Time Publish-Subscribe Wire Protocol—

DDS Interoperability Wire Protocol (RTPS).

3. Method according to claim 1, wherein the message is a DDS message.

4. Method according to claim 1, wherein the message is a RTPS message.

5. Method according to claim 4, wherein the identifying address is a GUIDPrefix of the RTPS message.

6. Method according to claim 1, wherein the message includes a submessage.

7. Method according to claim 6, wherein the message includes an InfoSource submessage.

8. Method according to claim 6, wherein each added identifying address is stored in the submessage.

9. Method according to claim 7, wherein each added identifying address is stored in the InfoSource submessage.

10. Method according to claim 9, comprising the step of adding in the InfoSource submessage the entity from which the message was received:

first forwarder;

the GUIDPrefix of the sending participant, second forwarder;

the GUIDPrefix of the first forwarder, and a third forwarder;

the GUIDPrefix of second forwarder.

11. Method according to claim 9, comprising the step of the first forwarder inspecting the InfoSource submessage to detect a loop, and when the InfoSource submessage already contains the GUIDPrefix of the first forwarder, then the first forwarder drops this message to prevent a loop.

12. Communications device utilizing a method according to claim 1.

13. Communications device according to claim 12, wherein the communications device is a customer premises equipment (CPE) device comprising a microprocessor, a non-volatile memory, in which an operating system is stored, and a volatile memory for the operation of the CPE device.

14. System comprising a first participant (A) of a first Local Area Network (LAN), a participant (B) of a second LAN and several forwarding servers (F1-F3) of a wide area network (WAN), the system utilizing a method according to claim 1.