MESH DETERMINISTIC ACCESS (MDA) PROCEDURE IN WIRELESS MESH NETWORK AND WIRELESS DEVICE SUPPORTING THE SAME

• US 20090122774A1
• Filed: 11/06/2008
• Published: 05/14/2009
• Est. Priority Date: 11/09/2007
• Status: Active Grant

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Seok, Yong Ho, Safonov, Alexander A.
• Granted Patent: US 8,310,999 B2
• Time in Patent Office: Days
• US Class Current: 370/338
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/72 using reservation actions during connection setup
• CPC Class Codes: H04L 47/826 Involving periods of time
• CPC Class Codes: H04W 74/002 Transmission of channel access control information
• CPC Class Codes: H04W 74/0833 Random access procedures, e.g. with 4-step access
• CPC Class Codes: H04W 84/12 WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

Provided are a procedure for mesh deterministic access (MDA) in wireless mesh network and a wireless device supporting the procedure. In the method, an intended transmitter transmits an a mesh deterministic access opportunity (MDAOP) setup request message including information for specifying times of a new MDAOP set and information for identifying the new MDAOP set to intended receivers. In this case, the MDAOP setup request message is a setup request message for a broadcast MDAOP. And, the intended transmitter receives an MDAOP setup reply message including a reply code from the intended receivers. The reply code may indicate either accept or refusal of the request for the new MDAOP set.

Claims

1. A mesh deterministic access (MDA) procedure for an intended transmitter in wireless mesh network, the procedure comprising:

transmitting a mesh deterministic access opportunity (MDAOP) setup request message including information for specifying times of a new MDAOP set and information for identifying the new MDAOP set to intended receivers, the MDAOP setup request message being a setup request message for a broadcast MDAOP; and

receiving an MDAOP setup reply message including a reply code from the intended receivers, the reply code indicating either accept or refusal of the request for the new MDAOP set.

2. The procedure as claimed in claim 1,

wherein the method further comprises building a map of neighborhood MDAOP times in a mesh Delivery Traffic Indication Map (DTIM) prior to transmitting the MDAOP request message, the map of neighborhood MDAOP times including neighborhood MDAOP times and neighbor MDAOP interfering times of all neighbor peer mesh points (MPs).

3. The procedure as claimed in claim 2,

wherein the information for specifying times of the new MDAOP set comprises selected MDAOP starting times and durations within the mesh DTIM, and

wherein the MDAOP starting times and durations are chosen so as not to overlap with either the neighborhood MDAOP times or the neighbor MDAOP interfering times.

4. The procedure as claimed in claim 3,

wherein when the neighborhood MDAOP times or the neighbor MDAOP interfering times are the times of another broadcast MDAOP the intended transmitter owns already, the neighborhood MDAOP times or the neighbor MDAOP interfering times may be chosen as the MDAOP starting times and durations.

5. The procedure as claimed in claim 3,

wherein the MDAOP starting times and durations are chosen so as not to overlap with the times that are known to the intended transmitter as being used by itself or its neighbor peer MPs for other activities.

6. The procedure as claimed in claim 1,

wherein MDAOP set ID is used as the information for identifying the new MDAOP set.

7. The procedure as claimed in claim 1,

wherein the MDAOP setup request message is an action frame including an MDAOP request information element,

wherein the information for specifying times of the new MDAOP set and the information for identifying the new MDAOP set are included in the MDAOP request information element, and

wherein a field for the information for identifying the new MDAOP set are set to a value selected among values for a broadcast MDAOP.

8. The procedure as claimed in claim 7,

wherein the MDAOP setup reply message is an action frame including an MDAOP reply information element,

wherein the MDAOP reply information element includes a reply code field for the reply code and a MDAOP set ID field, and

wherein the MDAOP set ID field are set to the same value as that of the MDAOP setup request frame.

9. The procedure as claimed in claim 1,

wherein the method further comprises transmitting an MDAOP advertisement message including information for TX-RX times and information interfering times, and

wherein the TX-RX times includes the times for the setup broadcast MDAOP.

10. The procedure as claimed in claim 1,

wherein the MDAOP setup request message are transmitted to the intended receivers in a unicast, multicast, or multicast manner.

11. A mesh deterministic access (MDA) procedure for intended receivers in wireless mesh network, the procedure comprising:

receiving a mesh deterministic access opportunity (MDAOP) setup request message including information for specifying times of a new MDAOP set and information for identifying the new MDAOP set from an intended transmitters, the MDAOP setup request message being a setup request message for a broadcast MDAOP; and

transmitting an MDAOP setup reply message including a reply code from the intended receivers, the reply code indicating either accept or refusal of the request for the new MDAOP set.

12. The procedure as claimed in claim 11,

wherein the method further comprises checking to see if the times of the new MDAOP set have overlap with its neighborhood times or its neighbor interfering times.

13. The procedure as claimed in claim 12,

wherein if the times of the new MDAOP set do not have overlap with its neighborhood times or its neighbor interfering times or the times of the new MDAOP set have overlap with its neighborhood times or its neighbor interfering times the owner of which is the intended transmitter, the reply code indicates the accept of the request for the new MDAOP set.

14. The procedure as claimed in claim 11,

wherein the information for specifying the times of the new MDAOP set includes selected MDAOP starting times and durations within the mesh DTIM.

15. The procedure as claimed in claim 11,

wherein the method further comprises checking to see if the MDA Access Fraction (MAF) limit of itself or its neighbor peer MPs will be exceed due to the times of the new MDAOP set, and

if so, the reply code indicates the refusal of the request for the new MDAOP set.

16. The procedure as claimed in claim 15,

wherein the method further comprises checking to see if the times of the new MDAOP set have overlap with the times that are known to the intended receiver as being used by itself or its neighbor peer MPs for other activities, and

wherein if so, the reply code indicates the refusal of the request for the new MDAOP set.

17. The procedure as claimed in claim 11,

wherein MDAOP set ID is used as the information for identifying the new MDAOP set.

18. The procedure as claimed in claim 11,

wherein the MDAOP setup request message is an action frame including an MDAOP request information element,

wherein the information for specifying the times of a new MDAOP set and the information for identifying the new MDAOP set are included in the MDAOP request information element, and

wherein a field for the information for identifying the new MDAOP set are set a value selected among values for a broadcast MDAOP.

19. The method as claimed in claim 18,

wherein the MDAOP setup reply message is an action frame including an MDAOP reply information element,

wherein the MDAOP reply information element includes a reply code field for the reply code and a MDAOP set ID field, and

wherein the MDAOP set ID field are set the same value as that of the MDAOP setup request frame.

20. The procedure as claimed in claim 11,

wherein the procedure further comprises:

receiving, from the intended transmitter, first MDAOP advertisement message including information for TX-RX times for the setup broadcast MDAOP; and

transmitting second MDAOP advertisement message including information for TX-RX times for the setup broadcast MDAOP.

21. A mesh deterministic access (MDA) procedure in wireless mesh network,

wherein the procedure is characterized in that an MDA opportunity (MDAOP) for broadcast transmission is allowed.

22. The procedure as claimed in claim 21,

wherein the MDAOP for broadcast transmission is identified by using a value of an MDAOP set ID of a request message for setting up the MDAOP for broadcast transmission.

23. The procedure as claimed in claim 21,

wherein a request message for setting up the MDAOP for broadcast transmission is transmitted from an intended transmitter of the MDAOP to intended receivers of the MDAOP in a unicast, multicast, or broadcast manner.

24. The procedure as claimed in claim 21,

wherein a request message for setting up the MDAOP for broadcast transmission includes MDAOP starting times and durations in a mesh Delivery Traffic Indication Map (DTIM) chosen by an intended transmitter,

wherein if the intended transmitter already owns another MDAOP for broadcast transmission, it is allowed for the intended transmitter to transmit the request message including the same MDAOP set ID and the same MDAOP starting times and durations as those of the another MDAOP.

25. The procedure as claimed in claim 21,

wherein a request message for setting up the MDAOP for broadcast transmission includes MDAOP starting times and durations in a mesh Delivery Traffic Indication Map (DTIM) chosen by an intended transmitter,

wherein if the intended transmitter already owns another MDAOP for broadcast transmission and the MDAOP set ID and the MDAOP starting times and durations of the request message are same as those of the another MDAOP, it is allowed for intended receivers to transmit a reply message including a reply code indicating accept of the request message.

26. The procedure as claimed in claim 21,

wherein if an intended receiver accept a setup request for a broadcast MDAOP from an intended transmitter, the intended receiver includes the related times into its MDAOP advertisement messages only after an MDAOP advertisement message from the intended transmitter is received.

27. A wireless device for supporting a method for mesh deterministic access (MDA) for an intended transmitter in wireless mesh network, the wireless device comprising:

a processor configured to generate and process messages; and

a transceiver operably connected to the processor and configured to transmit and receive the messages for the processor,

wherein the transceiver is configured to;

transmit a mesh deterministic access opportunity (MDAOP) setup request message including information for specifying times of a new MDAOP set and information for identifying the new MDAOP set to intended receivers, the MDAOP setup request message being a setup request message for a broadcast MDAOP; and

receive an MDAOP setup reply message including a reply code from the intended receivers, the reply code indicating either accept or refusal of the request for the new MDAOP set.