| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
9/16/03 Conference call minutes
Attendee’s
Upton, Jerry (Jerry1upton@aol.com)
Chindapol, Aik [Aik.Chindapol@siemens.com]
Tee, Anna [a.tee@samsung.com]
Youssefmir, Mike [mike@arraycomm.com]
Crowley, Steve [scrowley@attglobal.net]
Wieczorek Al-ETMX01 [Al.Wieczorek@motorola.com]
Tomcik, James [jtomcik@qualcomm.com]
Natarajan Nat-ANN004 [Nat.Natarajan@motorola.com]
Ansari, Arif [Arif.Ansari@nextel.com]
Gal, Dan (Dan) [dgal@lucent.com]
Mark Cudak [Mark.Cudak@motorola.com]
John Humbert [ jhumbe01@Sprintspectrum.com]
Khurram Sheikh
Geoff Anderson [meerkats@hvc.rr.com]
Joseph Cleveland [JClevela@sta.samsung.com]
Results
Following is a summary of the discussions that happened on today’s call by section
1) Section 3.1 System Architecture
a. Discussed briefly the contribution made by John Humbert to the CG
i. The intent of the contribution was to allow for the consideration of mesh network solutions , however the actual wording that was proposed requires proposals to support both P-MP and mesh network architecture. A new proposal will be sent out in the next day or two which does a better job of describing the intent.
b. The team agreed to change the wording in the last paragraph in section 3.1.
i. Current Text
1. The AI shall support a layered architecture and separation of functionality between user, data and control planes.
ii. New Text
1. The AI shall support a layered architecture and separation of functionality between user, data and control.
2) Section 3.1.1
a. In some cases the text refers specifically to the MAC and PHY while in others it is more appropriate to use the term layer 1 and layer 2. There maybe circumstances were the 802.20 standard develops unique versions of the interfaces above the MAC and PHY. In cases were there is a possibility that there will be some customization of the interfaces then it is appropriate to reference all of layer 1 and layer 2. The result is a change in the text for 3.1.1 from:
i. Current text
1. To facilitate a layered approach, the 802.20 specification shall incorporate a reference partitioning model consisting of the MAC and PHY.
ii. Proposed Text
1. To facilitate a layered approach, the 802.20 specification shall incorporate a reference partitioning model consisting of layers 1 and 2.
b. Need to add a figure number to the 2nd figure on page 10 and make sure that this is referenced in the index.
3) Section 3.1.2 Layer 1 and 2 inter-working
a. Proposal to delete this sections for the following reasons
i. The interface between layer 1 and layer 2 must be an open standard, consistent with all other IEEE 802 standards and with the text of section 3.1.1 that reads - line 18 in rev 8b - : "The 802.20 standards include PHY and MAC layer specifications with a well-defined service interface between the PHY and MAC layer”.
b. Single vs. multiple MAC'ss for a multiple-PHY 802.20 standard - discussion points
i. Multiple MAC+PHY combinations means multiple 802.20 standards!
ii. A multiple MAC's approach" limits future evolutions of the standard because the PHY and MAC must be changed at the same time.
iii. The MAC needs to be generic (as opposed to "optimized") so that the standard can support both TDD and FDD modes .
4) Section 4.1.1 System Gain
a. This was discussed on last weeks call and subsequently closed on this weeks call.
b. Need to add definition used for system gain into appendix A (John Humbert)
c. Send e-mail to the chair of the Evaluation Committee document making them aware that this issue needs to be addressed.
5) Section 4.1.2 Spectral Efficiency
a. Outlined the current proposal on the reflector with the following action items that need to occur to close this issue out
i. Provide a definition for effective aggregate throughput in appendix A
ii. Are the numbers for the target efficiencies the correct numbers
iii. Need a better definition of sector /Cell (Dan Gal to provide)
iv. There needs to be language on how to incorporate frequency reuse into the determination of Spectral Efficiency.
v. Need to check the entire document to make sure that there is consistency in the objectives set for each section.
6) Section 4.1.3 Frequency Reuse
a. Agreed to drop this section because there is a tradeoff between spectral efficiency and capacity/throughput that various proposals need to optimize.
b. Also there is no need for this section if reuse factors are taken into consideration when calculating spectral efficiency.
c. Move the definition for reuse factor into Appendix A.
7) Section 4.1.3 Support for the use of Repeaters
a. Discussed the proposed new language submitted to the reflector
b. Check with contributors of this section to see if they agree with the proposed text.
Schedule of topics for the next week
1. System Architecture (section 3.1 in rev 8)
2. MWBA System Reference Architecture (section 3.1.1 in rev 8)
3. Spectral Efficiency (Section 4.1.2 in rev 8)
4. Frequency Reuse (Section 4.1.3 in rev 8)
5. Support for Different Block Assignments (Section 4.1.4)
6. Support for the use of Repeaters (section 4.1.13)
7. Duplexing (section 4.1.5, rev 8)
8. Aggregate Data Rates ( section 4.1.7, rev 8)
9. Number of Simultaneous Active Users (section 4.1.8, rev 8)
10. Latency (section 4.1.9, rev 8)
11. Frame Error Rate (section 4.1.10, rev 8)
John J. Humbert
6220 Sprint Parkway
Mailstop KSOPHD0504 - 5D276
Overland Park, KS 66251-6118
PCS (816) 210-9611