DEVICE AND METHOD FOR EVENT-TRIGGERED COMMUNICATION BETWEEN AND AMONG A PLURALITY OF NODES

• US 20090207005A1
• Filed: 10/27/2005
• Published: 08/20/2009
• Est. Priority Date: 11/11/2004
• Status: Active Grant

• Current Assignee: NXP B.V. (NXP Semiconductors NV)
• Original Assignee: Koninklijke Philips Electronics N.V. (Koninklijke Philips N.V.)
• Inventors: Ruffini, Marco, Habetha, Jorg
• Granted Patent: US 8,144,029 B2
• Time in Patent Office: Days
• US Class Current: 340/435
• CPC Class Codes: G08G 1/162 event-triggered
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support
• CPC Class Codes: H04W 92/18 between terminal devices

Abstract

In order to provide a device (100) as well as a method for event-triggered communication between and among a plurality of nodes (A, B, C, S), in particular between and among a plurality of mobile nodes, for example between and among a plurality of vehicles, where the aspect of acknowledging the messages is taken into consideration, it is proposed to address at least one message (M1, M2, M3), in particular at least one identifying message (IM) and/or at least one acknowledging notification (AM), to at least one specific node (A, B, C, S), in particular by way of unicast transmission.

Claims

1. A device for operating event-triggered communication between and among a plurality of nodes, in particular between and among a plurality of mobile nodes, for example between and among a plurality of vehicles, characterized by at least one transmitting means for addressing at least one message, in particular at least one identifying message and or at least one acknowledging notification, to at least one specific node, in particular by way of unicast transmission.

2. The device according to claim 1, characterized in that the transmitting means is designed for additionally transmitting at least one event notification

by way of unicast transmission, in particular separately for each specific node from which the identifying message had been received, and/or

by way of broadcast transmission to the plurality of nodes.

3. The device according to claim 1, characterized by at least one receiving means

for sensing the message being transmitted by at least one of the nodes and/or

for sensing the event notification being transmitted by at least one of the nodes.

4. The device according to claim 1, characterized in that the acknowledging notification is addressed to the specific node from which the identifying message and/or the event notification had been received.

5. The device according to claim 1, characterized by at least one storing means

for storing the identifying message, in particular for locally storing identifying information of the specific node from which said identifying message had been received, and

for storing the acknowledging notification for each specific node, in particular for locally storing whether an acknowledgement of a certain event notification had been received wherein the device can distinguish between different event notifications.

6. The device according to claim 1, characterized by being designed

for addressing the message periodically,

for repeating the addressing of the message and/or for repeating the transmitting of the event notification in case no acknowledging notification has been received within a certain time-out period, and/or

for deleting the identifying message, in particular deleting the information regarding at least one of the nodes in case no identifying message has been received from this node within a certain time period, in particular within a certain lifetime.

7. The device according to claim 6, characterized in

that the time-out period after which the addressing is repeated is equal to the time period of the addressing of the identifying message by the specific node and/or

that the certain time period, in particular the lifetime, after which the 25 identifying message (IM) regarding the specific node is deleted, is equal to the maximum time period of the addressing of the identifying message by said specific node or a multiple of said maximum time period.

8. Communication network or communication system for event-triggered 30 communication between and among a plurality of nodes, each node comprising at least one device according to claim 1.

17. Communication protocol for at least one communication network according to claim 8.

9. Method for event-triggered communication between and among a plurality of nodes, in particular between and among a plurality of mobile nodes, for example between and among a plurality of vehicles, characterized by addressing at least one message, in particular at least one identifying message and/or at least one acknowledging notification, to at least one specific node, in particular by way of unicast transmission.

10. The method according to claim 9, characterized by the following steps after at 10 least one event notification had been received:

listening to the identifying message of at least one of the nodes;

locally storing the identifying information of at least one specific node from which the identifying message had been received;

transmitting the event notification to at least one of the nodes and waiting for an acknowledging notification;

locally storing for each of the nodes whether an acknowledgement of a certain event notification had been received wherein it can be distinguished between different event notifications;

repeating the transmission in case no acknowledging notification has been received within a certain time-out period; and

deleting the identifying message, in particular deleting the information regarding at least one of the nodes in case no identifying message has been, received from this node within a certain time period, in particular within a certain lifetime.

11. The method according to claim 10, characterized by addressing the acknowledging notification to the specific node from which the identifying message and/or the event notification had been received.

12. The method according to claim 10, characterized in that the event notification is

transmitted by way of unicast transmission, for example separately for each specific node from which the identifying message has been received, and/or

transmitted by way of broadcast transmission to the plurality of nodes, the event notification being triggered in particular by incidents around the node and/or in the node.

13. The method according to claim 10, characterized by sending and/or forwarding the received event notification to a certain number of the 10 nodes.

14. The method according to claim 10, characterized by sending and/or forwarding the received event notification to all nodes for which the reception of an identifying message is still locally stored and an acknowledging notification for the reception of the event notification is not marked, except for the node from which the event notification has been received.

15. The method according to claim 9, characterized in that the identifying message, in particular the local information, of the specific node from which the identifying message had been received

is either built and stored on-demand, in particular once an event has occurred and/or the event notification is received,

or is permanently maintained and updated.

16. The method according to claim 13 characterized in that said number of nodes to which the notification is sent and/or forwarded and/or the frequency of message repetition is depending on the number of identifying messages received from different nodes.

18. (canceled)