Embed Size (px)
Citation preview
IEEE 15-15-0564-00-0mag
Submission
07 2015
Amarjeet Kumar, ProcubedSlide 1
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)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, 1st Floor, KHB Colony, 5th Block, Koramangala, Bangalore – 560095, INDIA]Voice:[+91-9611-733007], E-Mail:[[email protected]]
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.
IEEE 15-15-0564-00-0mag
Submission
Slide 2
Content
• Problem Statement• Proposed solutions
Amarjeet Kumar, Procubed
07 2015
IEEE 15-15-0564-00-0mag
Submission
Slide 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
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 NextHigher layer
SenderMLME
Receiver Next higher layer
ReceiverMLME
RIT Data Req
RIT Data Req
RIT Data Res
MLME-RIT-RES.indication
macRitPeriod
macRITResponseWaitTime
IEEE 15-15-0564-00-0mag
Submission
Slide 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 identifier Command name RFD Tx RFD Rx
0x20 LE-RIT data request X X
0x23 LE-RIT data response X X
07 2015
IEEE 15-15-0564-00-0mag
Submission
Slide 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 ofRIT Data Res’s payload
07 2015
IEEE 15-15-0564-00-0mag
Submission
Slide 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 ofRIT Data Res’s payload
07 2015
IEEE 15-15-0564-00-0mag
Submission
Slide 8 Amarjeet Kumar, Procubed
Proposed Solution:– API definition for MLME-RIT-RES.confirm
MLME-RIT-RES.confirm (
status
)
07 2015
IEEE 15-15-0564-00-0mag
Submission
Slide 9 Amarjeet Kumar, Procubed
Proposed Solution:– Addition of new PIB’s.
07 2015
IEEE 15-15-0564-00-0mag
Submission
Slide 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
IEEE 15-15-0564-00-0mag
Submission
11
Octets : variable 1 0/4/variable
MHR fields Command Frame Identifier
Option command payload
Octets : 1 Variable
0xff Payload
Octets : 1 1 2
Time of 1st Listen(≠0xff)
Number of Repeat Listen Repeat Listen Interval
- Allowing User to add user defined payload in RIT Data Req.
Proposed Solution:
07 2015
IEEE 15-15-0564-00-0mag
Submission
Slide 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
IEEE 15-15-0564-00-0mag
Submission
Slide 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
IEEE 15-15-0564-00-0mag
Submission
Slide 14 Amarjeet Kumar, Procubed
Proposed Solution:– Addition of New PIB’s
Attribute Type Range Description Default
aMaxRITPayloadLength
Integer Constant Maximum RIT payload length
aMax PhyPacketSize – aMaxRITOverhed
macRITayload Set ofOctets
- RIT payload NULL
macRITPayloadLength
Integer 0 - aMaxRITPayloadLength
RIT payload length 0
07 2015
IEEE 15-15-0564-00-0mag
Submission
Slide 15
Thank you!
Questions
Amarjeet Kumar, Procubed
07 2015
