Download presentation
Presentation is loading. Please wait.
Published byEileen Byrd Modified over 6 years ago
1
Radio Resource Measurements MIB – Seattle Ad Hoc and After
November 2003 Radio Resource Measurements MIB – Seattle Ad Hoc and After Tim Olson Cisco Systems Byoung-Jo “J” Kim AT&T Labs-Research And many others listed in doc #837 Tim Olson & "J" Kim
2
Seattle Ad Hoc – Overview
November 2003 Seattle Ad Hoc – Overview Used 03/0666R4 as a base for MIB discussion – Excellent work by J Kim! Debated various MIB options (“bare bones” vs full featured) Provided “bare bones” Beacon Request/Report template version Worked in groups to complete all measurements in D0.7 version Produced 03/809R0 “bare bones” MIB version Tim Olson & "J" Kim
3
03/0666R4 03/0666R4 included the following:
November 2003 03/0666R4 03/0666R4 included the following: Single table for measurement requests with all current request types defined Individual report table for Beacon Report only Full featured implementation including: Dynamic request and report tables Linked request rows to support parallel bit Time aged request and report table rows Measurement report notifications Tim Olson & "J" Kim
4
November 2003 MIB Options Group was concerned that 03/0666R4 dictated to much MIB functionality for a client and possibly APs Several approaches were discussed: Simple no frills version with circular static tables managed by network manager Full blown interface with row management provided by SME (could be the SNMP manager) Split MIB implementation with more functionality required by the AP and only basic access for client Group decided to produce a simple “bare bones” version Tim Olson & "J" Kim
5
03/809R0 Working in groups document 030809R0 was produced
November 2003 03/809R0 Working in groups document R0 was produced 03/809R0 highlights: Circular request and report tables with table size implementation dependent Multiple request rows combined with a request token Measurement report connected to request using token No row management by the SME Row status indicates state of a given row Tim Olson & "J" Kim
6
November 2003 03/0809 MIB Tree Placement New sub-group added under the dot11smt group 3 groups added for RRM dot11RRMRequest dot11RRMReport dot11RRMConfig Tim Olson & "J" Kim
7
03/809 – Measurement Request
November 2003 03/809 – Measurement Request Tim Olson & "J" Kim
8
03/809 – Measurement Reports
November 2003 03/809 – Measurement Reports Tim Olson & "J" Kim
9
November 2003 03/809 – Channel Load Report Tim Olson & "J" Kim
10
03/809 – Noise Histogram Report
November 2003 03/809 – Noise Histogram Report Tim Olson & "J" Kim
11
November 2003 03/809 – Beacon Report Tim Olson & "J" Kim
12
November 2003 03/809 – Frame Report Tim Olson & "J" Kim
13
November 2003 03/809 – Hidden Node Report Tim Olson & "J" Kim
14
03/809 – Media Sense Time Histogram Report
November 2003 03/809 – Media Sense Time Histogram Report Tim Olson & "J" Kim
15
03/809 – STA Statistics Report
November 2003 03/809 – STA Statistics Report Tim Olson & "J" Kim
16
November 2003 03/809 – RRM Configuration Tim Olson & "J" Kim
17
November 2003 Updates on 809r0 809r1 fixes various minor errors, no structural nor technical 837r0 adds one varible needed to enable dynamic row management on the request table Please ignore the comments in 837r0 Clarifying texts in index usage for report tables: Still FIFO circular, but index updated not reused, thus you can choose to make the report table dynamic or fixed size. 837r3 includes a few minor modifications in addition to r0 Tim Olson & "J" Kim
18
837r0 enabling dynamic row management
November 2003 837r0 enabling dynamic row management Fixed-size circular table does not work if the table is used for SNMPv2, especially due to status ambiguity, index collisions, and multiple-manager race conditions. With the addition of nextIndex and read-create access rights Efficient identification of next index No index collision and confusion from reuse No ambiguity in the row status Commonly used for MIBv2, RFC 2479 Actual row management by SNMPv2 agent codes, which already exist widely Does not preclude fixed size table for internal data structure if intended for other usage than SNMP: Additional notes in 837r0 abstract and in attribute descriptions Tim Olson & "J" Kim
19
837r3 mods Some attemps at clarifying texts
November 2003 837r3 mods Some attemps at clarifying texts Request and report bits 837r0 contains some corrections as well Removed max table size for report tables Not needed since they are Read-only tables The size is completely under STA’s control Site report config table is made into a dynamic table For cleaner use with SNMPv2 Variable access limits changed RowStatus added to clarify each rows status nextIndex for size management and efficiency Clarifying text on number of site report per interface Full match as the defaul for match status Tim Olson & "J" Kim
20
Things to discuss (commented in 837r3)
November 2003 Things to discuss (commented in 837r3) Descriptions and naming for request table enable, request & report attributes and corresponding texts One Request table vs Separate Request table Time unit: TU and msec. Options given? Grouping and Parallel bit: search tokens.. Better ways to do this? Grouping is needed for back to back? Don’t do grouping in SNMP? Ok over-the-air Tim Olson & "J" Kim
21
Things to Discuss (commented in 837r3) Contined…
November 2003 Things to Discuss (commented in 837r3) Contined… Noise histogram has fixed number of bins, but not medium sense histograms. Should they? STA statistics potential confusion this statistics can be either cumulative or differential, depending on measurement duration. The text is not very clear on this STA statistics report does not have an indication when the statistics were read Necessary for cumulative, maybe for differential Tim Olson & "J" Kim
22
Things to Discuss (commented in 837r3) Contined… again
November 2003 Things to Discuss (commented in 837r3) Contined… again Time unit: TSF for report actual start time Not useful in MIB for external entities if TSF cannot be converted into absolute time May need explanation or additional information A time stamp per row when created may be just as useful Tim Olson & "J" Kim
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.