[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
stds-802-16: SUB11 COMMENT

To: <stds-802-16@ieee.org>
Subject: stds-802-16: SUB11 COMMENT
From: "Marianna Goldhammer" <mariannag@breezecom.co.il>
Date: Thu, 20 Apr 2000 20:13:36 +0300
Organization: BreezeCOM
Sender: owner-stds-802-16@ieee.org


[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
1

[Starting Line #]
5

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert "data" after "packet"

[Reason for Edit]
clarification

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
3

[Starting Line #]
38

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert "telecommuters" after "SOHO"

[Reason for Edit]
To add this market segment

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
6

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change" voice, data and video" to "packet data, voice and in some cases
video"

[Reason for Edit]
Make a correlation between the market size for each service and the order

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
6

[Starting Line #]
fig.2-2

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "voice, data and video" to "data, voice and video"

[Reason for Edit]
Consistence throughout the document

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
7

[Starting Line #]
10

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change the phrase starting with "The MAC and PHY protocols" with:"The MAC
and PHY protocols will not have explicit support for each and every service,
due to the fact that generic data streams SHALL be used for transport. The
MAC and PHY protocols SHALL provide for QoS service specific support.
Service specific QoS meaning is very low BER for data services, delay for
real time services, etc.

[Reason for Edit]
Clarification

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
7

[Starting Line #]
32

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert after business). "The required bandwidth is minimized
with VoIP, the associated codecs providing a very good
 compression: 8kb/s for G.729, 6.3kb/s for G.723. The
 compression result is the increase of the delay.

[Reason for Edit]
To make clear what is VoIP rate

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
7

[Starting Line #]
34

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Delete"low"

[Reason for Edit]
The VoIP delay is not low

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
7

[Starting Line #]
34
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "MUST" with "SHOULD"

[Reason for Edit]
The delay amount is depending on many factors, the MAC being
 only one of them.The delay amount, due to echo cancellers used
 with VoIP, is not extremly critical.

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
7

[Starting Line #]
36

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert after the conversation. "The QoS requiremets should take
 into account the characteristics of the VoIP technology: codec
 end-to-end delay of 50ms for 10ms frame (G.729), 120ms for
30ms frame (G.723), the possibility to transmit concatenated
voice packets, the mandatory use of echo cancellers.

[Reason for Edit]
Give a feeling of what VoIP delay is

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
7

[Starting Line #]
39

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert new paragraph with bullet: BER level The MAC and PHY
 protocols SHOULD provide for a reasonable BER Level for
 voice services. BER of 10-4 is sufficient for voice services
and 10-5 for FAX.

[Reason for Edit]
Make clear the BER issue

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
8

[Starting Line #]
6

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert new numbered paragraph: Internet protocol properties
 Bullet: Packet length - the IP datagrams are characterized by
variable length. The MAC protocols MUST support efficiently
 variable length packets.
Bullet: Bit Error Rate - the TCP/IP protocol, as known from
 literature, drops its performance by 90% when the packet error
 rate reaches 10%. The MAC and PHY protocols MUST provide
 means for realible data transport, the BER target for cellular
 deployment SHELL be 10-9, equivalent to the performance of
 wired networks.

[Reason for Edit]
important issue

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
9

[Starting Line #]
fig 4-1

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Delete right column, avoiding the MAC layer for DAVIC

[Reason for Edit]
Video is a service that should be supported exactly in the same
 way as other services

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
9

[Starting Line #]
45

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert: The IEEE 802.16.3 protocol stack SHALL be the same for
 all the supported services.

[Reason for Edit]
It is no reason to provide special means to the VIDEO service, which is not
the main application and generally the allocated bandwidth size will not
permit video service offering

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
10

[Starting Line #]
30

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Replace "Bandwidth" with "Capacity"

[Reason for Edit]
Bandwidth is measured in Hz, not bit/s

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
10

[Starting Line #]
16

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert paragraph 6 Wireless media characteristics
Sub-paragraph 6.1 Duplex model
Paragraph start The radio regulations permit two access modes:
Frequency Division Duplex - FDD and Time Division Duplex -
 TDD. The MAC and PHY protocol MUST support both FDD
 and TDD duplex modes. Spectral efficiency is maximized in
FDD with full-duplex operation, while in TDD with means to
avoid collocation problems and more complex interference
scenarios. The PHY and MAC protocols MUST provide for full
duplex operation, while preserving the QoS, BER and spectral
 efficiency requirements for data and voice traffic. The MAC and
 PHY protocols MUST provide means to resolve the collocation
 and interference problems in TDD deployment.

[Reason for Edit]
Missing paragraph

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
10

[Starting Line #]
16

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert paragraph 6.2 Channelization
New paragraph The standardization bodies providing channelization
 recommendations are ITU-R, CEPT and FCC. The allocated
bandwidth per operator varies between 5MHz and 120MHz.
 In Europe, the typical allocated bandwidth is 14MHz. The
operators target a good frequency reuse factor, using 4-6 sectors
 for Base Stations.The Base Station bandwidth per sector can be
 between 1.75MHz and 7MHz in in CEPT countries and between
2MHz and 6MHz in MMDS. The MAC and PHY protocols MUST
 permit the operation with channel spacing per sector of 1.75, 3.5
 and 7MHz when using ETSI masks and 2, 3, 5 and 6MHz when
 using other masks. The typical value for performance analysis
SHOULD be 3.5MHz for ETSI mask and 3MHz for MMDS mask.

[Reason for Edit]
Missing paragraph

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
10

[Starting Line #]
16

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert paragraph 6.3 Cellular deployment
New paragraph In cellular deployment, due to interference, the
 system spectral efficiency can be considerably lowered. The
 PHY and MAC protocols SHOULD permit good frequency reuse
 factors, providing at least 2bit/s/cell.In order to reduce the
 interference level, the PHY and MAC protocols MUST permit
power control per subscriber up-link and SHOULD permit
power control per subscriber down-link. The PHY and MAC
 protocols SHALL permit real-time changing of power levels,
as function of propagation conditions, in order to use the
minimum power needed for the target BER.

[Reason for Edit]
Missing paragraph

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
12

[Starting Line #]
4

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Delete from row 4 to row 14

[Reason for Edit]
Telephony will be delivered using VoIP, and the requirements
here are relevant only for classic 64kb/s voice.

[Submitter's Last Name]
Goldhammer

[Submitter's First Name]
Marianna

[Starting Page #]
13

[Starting Line #]
21

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change from table the 10ms in row 7 to "1/4 of the VoIP codec
 end-to-end delay"

[Reason for Edit]
Requirements non consistent with VoIP






      Marianna Goldhammer
      Director - Product Management - Access


       BreezeCOM Ltd.
       Atidim Technology Park, Building 1
       P.O.Box 13139, Tel Aviv 61131, Israel
       Tel: (972)- 3 -6456241/6262
       Fax: (972) -3 -6456290

      Email: mariannag@breezecom.co.il

            http://www.breezecom.com
Prev by Date: stds-802-16: new patent notice filed
Next by Date: stds-802-16: SUB11: Reminder: comment deadline is one week from today
Prev by thread: stds-802-16: new patent notice filed
Next by thread: stds-802-16: SUB11 COMMENT
Index(es):
- Date
- Thread