1. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Two Methods of Transmit Power Control for Mesh Network] Date Submitted: [10 May, 2006] Source: [Na Shan, Yongjun Liu] Company [Huawei technologies Co., Ltd] Address [No.3 Xinxi Road, Shangdi Information Industry Base, Haidian District, Beijing, P.R.China] Voice: [+86 10 82882921], FAX: [+86 10 82882966], E-Mail:[shanna@huawei.com, yongjunliu@huawei.com] Abstract:[This document provides two methods of TPC combined with the topology of Mesh Network.] Purpose:[Final Proposal for the IEEE802.15.5 Standard.] Notice:This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release:The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

2. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 2 Two Methods of TPC for Mesh Network Na Shan Yongjun Liu Huawei Technologies Co., Ltd.

3. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 3 Contents Overview of the Present TPC TPC issues for Mesh Network Power Table New TPC methods Conclusion

4. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 4 The Present TPC 802.15.3 –Two independent forms of transmit power control (TPC) are available for 802.15.3 systems, a maximum power for the CAP, the beacon and directed MCTAs, and adjustable power in a CTA. –A DEV may also change its transmit power based on its own estimation of the channel. 802.15.4: none

5. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 5 The TPC procedure of 802.15.3 Figure 1

6. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 6 Controlling the PHY power primitives Primitive names ParametersDescriptionsRemarks PHY- PM.request PMLevelNumeric value of one of the supported power management levels of the PHY. These values are implementation dependent. Integer PHY- PM.confirm PMResult -Code Indicates the result of the PHY request. Enumera -tion Table 1 Figure 2

7. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 7 The present TPC issues for Mesh Network It only concerns the communication link between two DEVs Need many TPC commands More power consumption Decrease network capability

8. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 8 Power Table A Power Table is to record the transmitted power levels at which a node transmits signals to neighbor nodes The transmitting node finds the corresponding TP level before it transmits any frames to its neighbor node A Neighbor table which combines a Power table is a Neighbor-Power Table

9. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 9 Neighbor-Power Table The Neighbor-Power Table of Node M: Neighbor nodes TP levels (dBm) A10 B C Table 2 Figure 3 B C D M A

10. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 10 New Neighbor-Power Table According to Two Power Change commands received by node M, the Neighbor-Power Table is changed. The node A TP level is much higher than node B and C. Avoid many TPC commands Neighbor nodes TP levels (dBm) A10 B3 C2 Table 3

11. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 11 Transmit Coverage Figure 4 B C D M A

12. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 12 Issues for present TP levels Power consumption is very high when direct communication between node M and A More interferences from node A when direct communication between node M and A Decrease network capability when direct communication between node M and A

13. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 13 New TPC methods Provide two TPC methods based on the network topology to resolve these issues: –A Centralized TPC method –A Distributed TPC method Principle: the network capability is much better by changing the network topology and transmit power levels

14. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 14 Conditions High layer requirements: power consumption, delay… Frequent Neighbor TPC and power adjust value over a threshold There are at least 2 entries which are much different in the Power Table.

15. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 15 A Centralized TPC method Power Control Server Definition: It is a Functional module that makes a reasonable TP decision. Operation: Topology Server + a specific TPC arithmetic A specific TPC arithmetic is implementation dependent.

16. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 16 The Centralized TPC MAC Primitives Table 4-1 Primitive namesParametersDescriptionsRemarks MLME-TX-POWER.reqReqAddrSpecifies the Device Address of the originating DEV MLME request TPC decision- making. 2octets SrcAddrThe originating Device Address 2octets TgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets LinkRequireInfoDescription of the link service1octet TXPowerReqTimeoutThe time in milliseconds in which the operation initiated by the MLME request needs to be completed before responding with a ResultCode of TIMEOUT. 1octet MLME-TX-POWER.confirmTgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets ResultCodeSpecifies the result of TP request.(0-255) 1 octet TPCResultThe results of TPC decision- making include TPC level. 1 octet

17. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 17 The Centralized TPC MAC Primitives (cont.) Table 4-2 Primitive namesParametersDescriptionsRemarks MLME-TX-POWER.indicationSrcAddrThe originating Device Address 2octets TgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets LinkRequireInfoDescription of the link service1octet TPSetLenThe length of the TP levels Set. 1octet TP levels SetThe neighbor-power table information of the originating DEV variable MLME-TX-POWER.responseSrcAddrThe originating Device Address 2octets TgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets ResultCodeSpecifies the result of TP request.(0-255) TIMEOUT …… 1 octet TPCResultThe results of TPC decision- making include TPC level. 1 octet

18. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 18 The Centralized TPC Commands Table 5 Command namesParametersDescriptionsRemarks Transmitting Power RequestReqAddrSpecifies the Device Address of the originating DEV MLME request TPC decision-making. 2octets SrcAddrThe originating Device Address2octets TgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets LinkRequireInfoDescription of the link service1 octet TPAdjustLevelSpecifies the TP value required, positive value is to increase TP level; otherwise decrease TP level 1 octet TPSetLenThe length of TP levels Set1 octet TP levels SetThe neighbor-power table information of the originating DEV variable Transmitting Power ResponseSrcAddrThe originating Device Address2octets TgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets ResultCodeSpecifies the result of TP request.0-255 1 octet TPCResultThe results of TPC decision- making include TPC level. 1 octet

19. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 19 Figure 5

20. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 20 Before the centralized TPC Figure 6 B C D M A S Node S: (1)Power Control Server (2)It have the whole (or partial) network topology information, such as the network in the yellow background. Node M: Need to change the transmit power level to A.

21. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 21 During the procedure of the centralized TPC (1)Node M sends the Transmit Power Request command to node S. Figure 7 B C D M A S

22. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 22 During the procedure of the centralized TPC (1)Node M sends the Transmit Power Request command to node S. (2)Node S sends the Transmit Power Response command to node M after finishing the TPC decision-making. Figure 8 B C D M A S

23. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 23 After the centralized TPC Figure 9 B C D M A S Node M: (1)Non-communication directly between node A and node M.

24. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 24 After the centralized TPC Figure 10 B C D M A S Node M: (1)Non-communication directly between node A and node M. (2)Routing 1: M-B-A; Routing 2: M-C-D-A; Routing 4: M-C-B-A; Routing 5: M-S-B- A; Routing 6: M-S-D-A; Routing 7: M- S-C-D-A (3)To change the Neighbor-Power table. Node S: Need to change the topology information. Notes: The procedure of increasing TP is similar as this example.

25. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 25 A Distributed TPC method Every node has a Routing Table and a Neighbor-Power Table. Every node makes a TPC decision by itself.

26. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 26 The Distributed TPC MAC primitives Table 6-1 Primitive namesParametersDescriptionsRemarks MLME-TP-RoutingInfo.reqTgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets DEVTypeTRUE-All 1-hop DEVs FALSE-RevAddr designate the DEV 1octet RevAddrSpecifies the Device Address of receiving the RoutingInfo request command. 2octets TPRoutingInfoReqTimeoutThe time in milliseconds in which the operation initiated by the MLME request needs to be completed before responding with a ResultCode of TIMEOUT. 1octet MLME-TP-RoutingInfo.confirmTgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets RevAddrSpecifies the Device Address of receiving the RoutingInfo request command. 2octets ResultCodeSpecifies the result of TP equest.(0-255)1 octet RoutingInfoThe Information is about the TgtAddr and the RevAddr routing. 1octet

27. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 27 The Distributed TPC MAC primitives (cont.) Table 6-2 Primitive namesParametersDescriptionsRemarks MLME-TP-RoutingInfo.indicationTgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets ReqAddrSpecifies the Device Address of requiring routing information 2octets MLME-TP-RoutingInfo.responseTgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets ResultCodeSpecifies the result of TP request.(0- 255) TIMEOUT …… 1 octet RoutingInfoResultThe Information is about the TgtAddr and the RevAddr routing. 1 octet MLME-TP-CHANGE.reqTgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets TPChangeLevelThe requested power change in units of dB 1 octet MLME-TP-CHANGE.confirmResultCodeSpecifies the result of TP Level change. (0-255) 1 octet

28. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 28 The Distributed TPC MAC primitives (cont.) Table 6-3 Primitive namesParametersDescriptionsRemarks MLME-Top-Change.req (optional)TgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets DEVTypeTRUE-All Neighbor DEVs FALSE-RevAddr designate the DEV 1octet RevAddrSpecifies the Device Address of receiving the Top Change request command. 2octets NewNexthopAddrSpecifies the next hop Device Address of the route to TgtAddr. 2octets MLME-Top-Change.confirm (optional)ResultCodeSpecifies the result of transmitting the top change information.(0- 255) 1 octet

29. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 29 The Distributed TPC Commands Table 7 Command namesParametersDescriptionsRemarks RoutingInfo Request CommandTgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets RoutingInfo Response CommandTgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets RevAddrSpecifies the Device Address of receiving the RoutingInfo request command. 2octets ResultCodeSpecifies the result of TP equest.(0-255) 1 octet RoutingInfoThe Information is about the TgtAddr and the RevAddr routing. 1octet Top Change Info indicaton(optional)TgtAddrSpecifies the Device Address of the target of the originating DEV changes TP level 2octets NewNexthopAddrSpecifies the next hop Device Address of the route to TgtAddr. 2octets

30. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 30 Figure 11

31. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 31 Before the Distributed TPC (1)Node M attempts to change Transmit Power level for node A. Figure 12 B C D M A

32. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 32 Figure 13 B C D M A During the procedure of the Distributed TPC (1)Node M attempts to change Transmit Power level for node A. (2)Node M broadcasts the Routing Request information to its 1-hop nodes using the corresponding A TP level. (Parameter: The Target node is Node A.)

33. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 33 Figure 14 B C D M A During the procedure of the Distributed TPC (1)Node M attempts to change Transmit Power level for node A. (2)Node M broadcasts the Routing Request information to its 1-hop nodes using the corresponding A TP level. (Parameter: The Target node is Node A.) (3)All 1-hop nodes send the Routing Response information to Node M. (Parameter: Results of the Target node.)

34. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 34 Figure 15 B C D M A After the Distributed TPC Node M: (1)Non-communication directly between node A and node M.

35. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 35 Figure 16 B C D M A After the Distributed TPC Node M: (1)Non-communication directly between node A and node M. (2)Routing 1: M-B-A (3)Routing 2: M-C-D-A (4)Routing 3: M-C-B-A (5)Routing 4: M-B-C-D-A (6)To change the Neighbor-Power and routing tables.

36. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 36 Distributed TPC -Increasing power The Routing Information Request should be broadcast at the maximum TP level New neighbors are found May change routing table by the Routing Information Responses Others are similar as the procedure of decreasing power

37. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 37 Distributed TPC -Increasing power (Cont.) B C D M A M broadcasts a Routing Information Request at the maximum TP level Node A responses M selects A as its new neighbor M changes its routing table and sends data directly to A, no longer relayed by B

38. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 38 Conclusions Proposed the Power Table –The communication number of TPC commands is reduced. Proposed one new centralized TPC method –Adapted a small network –Power Save –Optimized the network structure and performance Proposed one new distributed TPC method –Adapted a large network –Power Save –Optimized the network structure and performance

39. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 39 Problems???

40. doc.: IEEE 802.15-06-0226-00-0005 Submission May 2006 Na Shan, Yongjun Liu, HuaweiSlide 40 Thank you for your attention!