1. Application parameters definition for usage models
Hervé Bonneville, Bruno Jechoux
H.Bonneville, B.Jechoux, Mitsubishi ITE

2. Application vs MAC requirements
Month 2003
doc.: IEEE /xxxr0
Application vs MAC requirements
2 possible reference points for traffic parameters in Usage Model document:
At application’s output
At MAC SAP
In any case: Traffic parameters shall be consistent
H.Bonneville, B.Jechoux, Mitsubishi ITE
H.Bonneville, B.Jechoux, Mitsubishi ITE

3. Application vs MAC requirements
Application requirements
Aggregation sub-layer
Aggregation
RTP
RTP overhead S
UDP / TCP
UDP/TCP overhead IP
IP overhead
System requirements
MAC
TGn scope
PHY
H.Bonneville, B.Jechoux, Mitsubishi ITE

4. Reference at application’s output
User’s point of view
Application constraints:
Bit rate, packet size, Packet Error Rate, packet inter-arrival delay and maximum delay at application’s output,
Protocol stack independent (from application to MAC).
H.Bonneville, B.Jechoux, Mitsubishi ITE

5. Reference at MAC SAP MAC designer point of view
Bit rate, packet size, Packet Error Rate and packet inter-arrival delay shall take into account:
Application’s output
Packet aggregation rules and set up
Protocol stack overhead
Maximum delay:
Direct constraint from application
H.Bonneville, B.Jechoux, Mitsubishi ITE

6. Examples: Voice service
At application’s output
Bit rate: 6.3 kbit/s, packet size: 20 octets, inter-arrival delay: 30 ms, PER: 5% and maximum delay: 100 ms
At MAC SAP
Aggregation: 60 octets (3 voice packets)
IP+UDP+RTP header: 40 octets ( )
Bit rate: 10.5 kbit/s, packet size: 100 octets, inter-arrival delay: 90 ms, PER: 1.7% (roughly)
Maximum delay: 100 ms
H.Bonneville, B.Jechoux, Mitsubishi ITE

7. Conclusion 2 possible references, with both pros and cons Select one
And remain consistent
H.Bonneville, B.Jechoux, Mitsubishi ITE