1. IEEE 15-15-0335-00-0mag Submission 05 2015 Amarjeet Kumar, Procubed Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [IEEE 802.15.4 MAC Overview] Date Submitted: [06 May, 2015] Source: [Amarjeet Kumar] Company [Procubed Technology Solutions Pvt. Ltd.] Address [A/7, 1 st Floor, KHB Colony, 5 th Block, Koramangala, Bangalore – 560095, INDIA] Voice:[+91-9611-733007], E-Mail:[kumar@procubedinc.com] Re: [Ballot comment submission. References: P802.15.4-REVc-D00.pdf] Abstract:[This document presents an overview for proposed change in LE-RIT in IEEE 802.15.4 MAC sub-layer as currently specified in the “P802.15.4-REVc-D00.pdf” version of the standard.] Purpose:[Proposal for LE-RIT Changes the IEEE 802.15.4 task group.] Notice:This document has been prepared as a proposal to 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. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 2 Content Proposal Summary Proposal Problem Statement Proposed solutions Proposed Change in the specification Amarjeet Kumar, Procubed

3. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 3 Proposal #1: Addition of RIT Passive Scan as a new type of Scan. Proposal #2: Non uses of CSMA-CA while send the data in response to the RIT Data request. Proposal #3: Addition of RIT Data Response Command. Proposal #4: Transmission of RIT data request intermittently. Proposal #5: Addition of Enhanced RIT Data Request. Proposal #6: Addition of new status "FCS_ERROR" in MLME- COMM-STATUS.indication. Amarjeet Kumar, Procubed Proposal Summary

4. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 4 Addition of RIT Passive Scan as a new type of Scan. Amarjeet Kumar, Procubed Proposal #1

5. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 5 Amarjeet Kumar, Procubed Proposal #1: Problem Statement Technical Issues: –As we know Passive or Active Scan is necessary to resolve PAN ID confliction. Coordinators operated in RIT mode don’t send (enhanced) beacon frame because RIT mode is one of the non-beacon-enabled PAN. –Coordinators operated in RIT mode can’t receive (enhanced) beacon request frame because those coordinators wake up intermittently and the reception time is very short ( 1 or 2 ms per 5 seconds).

6. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 6 Amarjeet Kumar, Procubed Proposal #1: Proposed Solution Proposed Solution: –Introduction of a new type Scan Type RIT Passive Scan –Once the Upper Layer sends a MLME-Scan.request with ScanType as “RIT Passive Scan”, the MAC Layer should turn ON its receiver in each channel request for scan and want for the duration configured. It should receive the RIT-Data.request and send it to the upper layer as MLME-Scan.confirm once the Scan is completed. –The device initiating the RIT Passive scan should set the PAN ID as broadcast PAN ID and receive all RIT data request send by the neighbouring nodes. Device supporting RIT Passive scan should send the RIT Data request as a broadcast packet, so that it can be received by all device in neighbourhood.

7. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 7 Amarjeet Kumar, Procubed Proposal #1: Proposed Change in the specification Proposed Solution: –Add Section 6.3.1.4 RIT Passive Scan –MLME-SCAN.request No Change in the primitive –0x08 = RIT passive scan. –Update the table 82 for supporting additional ScanType. MLME-SCAN.confirm (SUCCESS) MLME-SCAN.request (RIT passive) RIT Mode Next Higher layer RIT Mode MLME RIT Data Req Set to first channel RIT Passive Scan RIT Data Req Set to last channel RIT Passive Scan RIT Data Req

8. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 8 Non uses of CSMA-CA while send the data in response to the RIT Data request. Amarjeet Kumar, Procubed Proposal #2

9. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 9 Amarjeet Kumar, Procubed Proposal #2: Problem Statement Technical Issues: –Current specification requires CSMA-CA to be performed during sending of data in response to RIT Data Request. However, in low power devices using RIT feature, device sending data in response to RIT data req. can be avoid CSMA-CA.

10. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 10 Amarjeet Kumar, Procubed Proposal #2: Proposed Solution Proposed Solution: –Page 103, Line number 42-43 –Chapter “ 6.12.3.3 RIT Transmission” Current Text in Specification: Upon reception of RIT Data Request command, the MAC sublayer sends the pending data using unslotted CSMA-CA. Change it to: Upon reception of RIT Data Request command, the MAC sublayer sends the pending data without using unslotted CSMA-CA.

11. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 11 Addition of RIT Data Response Command. Amarjeet Kumar, Procubed Proposal #3

12. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 12 Amarjeet Kumar, Procubed Proposal #3: Problem Statement Technical Issues: –Current specification for LE-RIT Data exchange does not give any flexibility to the sending device to decide on what data to be sent. It has to be pre decided by the upper layer and queued to the MAC layer. This reduces the flexibility to upper layer.

13. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 13 Amarjeet Kumar, Procubed Proposal #3: Proposed Solution Proposed Solution: –Introduction of MLME-RIT-REQ.ind MLME-RIT-RES.req MLME-RIT-RES.conf MLME-RIT-RES.ind –Addition of new MAC Command: RIT Data Response command (0x23) Frame Format Command frame identifierCommand nameRFD TxRFD Rx 0x20LE-RIT data requestXX 0x23LE-RIT data responseXX

14. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 14 Amarjeet Kumar, Procubed Proposal #3: Proposed Change in the specification Proposed Solution: –Modification in Packet exchange process in “6.12.3.2 Periodic RIT data request transmission and reception” MLME-RIT-RES.confirm MLME-SET.request (macRITAutoRequest=FALSE) MLME-RIT-RES.request MLME-RIT- REQ.indication Sender Next Higher layer Sender MLME Receiver Next higher layer Receiver MLME RIT Data Req RIT Data Res (may not be used CSMA-CA) MLME-RIT-RES.indication macRitPeriod macRIT Response WaitTime

15. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 15 Amarjeet Kumar, Procubed Proposal #3: Proposed Change in the specification Proposed Solution: –API definition for MLME-RIT-RES.indication MLME-RIT-RES.indication( SrcAddrMode, SrcPANId, SrcAddr, DstAddrMode, DstPANId, DstAddr, PayloadLength, Payload, LinkQuality, DSN, Timestamp, SecurityLevel, KeyIdMode, KeySource, KeyIndex, ) Information of Source address Information of RIT Data Res’s payload

16. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 16 Amarjeet Kumar, Procubed Proposal #3: Proposed Change in the specification Proposed Solution: –API definition for MLME-RIT-RES.request MLME-RIT-RES.request( SrcAddrMode, DstAddrMode, DstPANId, DstAddr, PayloadLength, Payload, SecurityLevel, KeyIdMode, KeySource, KeyIndex, frameControlOptions, headerIEList, payloadIEList ) Information of Destination address Indication of RIT Data Res’s payload

17. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 17 Amarjeet Kumar, Procubed Proposal #3: Proposed Change in the specification Proposed Solution: –API definition for MLME-RIT-RES.confirm MLME-RIT-RES.confirm ( status )

18. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 18 Amarjeet Kumar, Procubed Proposal #3: Proposed Change in the specification Proposed Solution: –Addition of new PIB’s.

19. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 19 Transmission of RIT data request intermittently. Amarjeet Kumar, Procubed Proposal #4

20. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 20 Amarjeet Kumar, Procubed Proposal #4: Problem Statement Technical Issues: –When two nodes have data to send to each other at same time, both will stop sending RIT Data request at same time and wait for other to send the RIT Data request. In this case both node will be in waiting mode and eventually not be able to send any data to each other.

21. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 21 Amarjeet Kumar, Procubed Proposal #4: Proposed Solution Proposed Solution: –Change the packet exchange sequence in “6.12.3.2 Periodic RIT data request transmission and reception”. Transmission of RIT data request intermittently when it is waiting for an RIT Data Request at arbitrary timing. This will make sure that both node can fetch data from each other. RIT data req. RX RIT data req. RX Data ・・・ RX RIT data req. RX RIT data req. RX Data exchange macRITPeriod macRITData WaitDuraiotn macRITData WaitDuraiotn macRITPeriod macRITTxWaitDuration Data Pending

22. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 22 Addition of Enhanced RIT Data Request. Amarjeet Kumar, Procubed Proposal #5

23. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 23 Amarjeet Kumar, Procubed Proposal #5: Problem Statement Technical Issues: –Current specification does not give flexibility to the Node requesting for data to request any specific data. Node can not request for any specific data from the sending node.

24. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 24 Amarjeet Kumar, Procubed Proposal #5: Proposed Solution Proposed Solution: –Addition of Enhanced RIT Data Request –Here the node sending RIT data request to add an upper layer defined payload to it. The received node upper layer can receive the payload and send back the response required. –Receiving node should support both LE-RIT data request and Enhanced LE-RIT Request. –Addition of MAC Command ID –Frame Format

25. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 25 Amarjeet Kumar, Procubed Proposal #5: Proposed Solution Proposed Solution: –Addition of New PIB’s

26. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 26 Addition of new status "FCS_ERROR" in MLME-COMM- STATUS.indication. Amarjeet Kumar, Procubed Proposal #6

27. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 27 Amarjeet Kumar, Procubed Proposal #6: Problem Statement Technical Issues: –Currently there is no way to indicate the FCS error to the upper layer.

28. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 28 Amarjeet Kumar, Procubed Proposal #6: Proposed Solution Proposed Solution: –Addition of new status code for MLME-COMM-STATUS.indication –The new error code should be reported if the new MAC PIB macIndicateFCSError is set to TRUE. –New error code should be added to the “Table 69—MLME-COMM-STATUS.indication parameters” in page number 218. –New MAC PIB Addition:

29. IEEE 15-15-0335-00-0mag Submission 05 2015 Slide 29 Thank you! Questions Amarjeet Kumar, Procubed