Beacon For A Star Network, Sensor Nodes In A Star Network, Method For Initializing A Gateway In A Star Network And Method For Operating A Star Network

• US 20120051365A1
• Filed: 05/07/2010
• Published: 03/01/2012
• Est. Priority Date: 05/07/2009
• Status: Abandoned Application

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Bahr, Michael, Vicari, Norbert
• Application Number:
  US13/319,253
• Publication Number:
  US 20120051365A1
• Time in Patent Office: Days
• US Class Current: 370/401
• CPC Class Codes: H04W 48/12 using downlink control channel
• CPC Class Codes: H04W 72/543 based on requested quality, e.g. QoS
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

A beacon for a star network comprising a gateway and at least one sensor node, where the beacon includes fields containing information on the length of a base time-slot and information on the number of used base time-slots per management time-slot, where the management time-slots are used at least to transmit configurations for the star network. In addition, the sensor node in the star network includes a data structure for saving a star network configuration, and the data structure includes a configuration gateway ID and a configuration sequence number as attributes.

Claims

1-15. -15. (canceled)

16. A gateway for a star network including at least one sensor node, the gateway transmitting a beacon including:

fields containing information on a length of a base timeslot and information on a number of base timeslots used per management timeslot;

wherein the management timeslots are used to transmit at least configurations for the star network.

17. The gateway as claimed in claim 16, wherein the beacon includes further fields containing a gateway ID comprising an identifier for the gateway of the star network and a configuration sequence number comprising an identifier for a current configuration of the star network.

18. The gateway as claimed in claim 17, wherein the gateway ID is one of:

derived from a Media Access Control (MAC) address of the gateway, or

a random number and predefined by a network management system.

19. A gateway including the beacon of claim 16, wherein the gateway includes a superframe configuration comprising the beacon.

20. The gateway as claimed in claim 19, wherein a management timeslot is available for each transmission direction and the management timeslots are arranged directly after the beacon.

21. The gateway as claimed in claim 19, wherein access to the management timeslots is always performed based on carrier sense multiple access (CSMA).

22. A sensor node in a star network, the sensor node having a data structure for storing a configuration of the star network, the data structure having attributes comprising a gateway ID of the configuration and a configuration sequence number of the configuration.

23. The sensor node as claimed in claim 22, wherein the data structure can store k≧

1 configurations and is organized as a list or a field.

24. A star network comprising a gateway and multiple sensor nodes as claimed in claim 22.

25. A method for initializing a gateway in a star network comprising a gateway and multiple sensor nodes, the method comprising:

detecting a gateway ID; and

determining start values for the gateway ID and a configuration sequence number.

26. The method as claimed in claim 25, wherein a start value for the gateway ID comprises a random value or a final octet of a MAC address of the gateway.

27. The method as claimed in claim 25, wherein a start value for the gateway ID is stipulated by a network management system.

28. The method as claimed in claim 25, wherein a distributed algorithm is used for recognizing gateway ID duplicates or for assigning a duplicate-free gateway ID.

29. A method for operating a star network having a gateway and multiple sensor nodes, the method comprising:

receiving, by the sensor nodes, beacons from the gateway, the beacons comprising a gateway ID and configuration sequence number;

comparing the received gateway ID and configuration sequence number with corresponding values of a current configuration of a respective sensor node; and

if a sensor node establishes that a match has not occurred, searching configurations stored in the respective sensor node to ascertain whether there is an appropriate configuration for the gateway ID and the configuration sequence number and using the appropriate configuration if there is an appropriate configuration for the gateway ID and the configuration sequence number.

30. The method as claimed in claim 29, further comprising:

providing, by a management timeslot, a notification to the gateway of a missing configuration if no match of the received gateway ID and configuration sequence number with the corresponding values of the current configuration of the sensor node is determined and no configuration corresponding to the gateway ID and the configuration sequence number is stored in the sensor node.