1. IEEE 15-15-0564-00-0mag Submission 07 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: [15 July, 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-0564-00-0mag SubmissionSlide 2 Content Problem Statement Proposed solutions Amarjeet Kumar, Procubed 07 2015

3. IEEE 15-15-0564-00-0mag SubmissionSlide 3 Amarjeet Kumar, Procubed Problem Statement Technical Issues: Current specification –It is assumed that the sending node is aware of its destination. –The upper layer always have data ready to be sent. Use case –The upper layer of the node sending the data needs to decide which receiving device is the correct device to handle its data. – Here the upper layer of the sending node wants to decides on the destination node based on the RIT Data Req it has received. (some Payload on the RIT Data Req Set by upper layer of receiving node) 07 2015

4. IEEE 15-15-0564-00-0mag Submission 07 2015 Slide 4 Amarjeet Kumar, Procubed Proposed Change (i-39/i-391) 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 MLME-RIT-RES.indication macRitPeriod macRIT Response WaitTime

5. IEEE 15-15-0564-00-0mag SubmissionSlide 5 Amarjeet Kumar, Procubed 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 07 2015

6. IEEE 15-15-0564-00-0mag SubmissionSlide 6 Amarjeet Kumar, Procubed 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 07 2015

7. IEEE 15-15-0564-00-0mag SubmissionSlide 7 Amarjeet Kumar, Procubed 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 07 2015

8. IEEE 15-15-0564-00-0mag SubmissionSlide 8 Amarjeet Kumar, Procubed Proposed Solution: –API definition for MLME-RIT-RES.confirm MLME-RIT-RES.confirm ( status ) 07 2015

9. IEEE 15-15-0564-00-0mag SubmissionSlide 9 Amarjeet Kumar, Procubed Proposed Solution: –Addition of new PIB’s. 07 2015

10. IEEE 15-15-0564-00-0mag SubmissionSlide 10 Amarjeet Kumar, Procubed Problem Statement (i-68) 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. 07 2015

11. IEEE 15-15-0564-00-0mag Submission 11 Octets : variable10/4/variable MHR fieldsCommand Frame IdentifierOption command payload Octets : 1Variable 0xffPayload Octets : 112 Time of 1 st Listen (≠0xff) Number of Repeat ListenRepeat Listen Interval - Allowing User to add user defined payload in RIT Data Req. Proposed Solution: 07 2015

12. IEEE 15-15-0564-00-0mag SubmissionSlide 12 Amarjeet Kumar, Procubed Problem Statement (i-41/i-393) 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. 07 2015

13. IEEE 15-15-0564-00-0mag SubmissionSlide 13 Amarjeet Kumar, Procubed 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 07 2015

14. IEEE 15-15-0564-00-0mag SubmissionSlide 14 Amarjeet Kumar, Procubed Proposed Solution: –Addition of New PIB’s AttributeTypeRangeDescriptionDefault aMaxRITPayload Length IntegerConstantMaximum RIT payload length aMax PhyPacketSize – aMaxRITOverhed macRITayloadSet of Octets -RIT payloadNULL macRITPayload Length Integer0 - aMaxRITPayloadLength RIT payload length0 07 2015

15. IEEE 15-15-0564-00-0mag SubmissionSlide 15 Thank you! Questions Amarjeet Kumar, Procubed 07 2015