REVd Sponsor Ballot Comment Addendum

Robert Nelson

Description

2004-03-18 IEEE C802.16d-04/42r11 REVd/D3 Sponsor Ballot Comment Addendum234 Bob Nelson56 MacPhy Technologies 78==========================================================================9The current document text is inconsistent regarding system scheduling. Although the parameters defined in1011 clause 11 are specified as being equally applicable to uplink and downlink, the only discussion of scheduling12 in clause 6.4.5 specifically addresses only uplink operation. Similarly, the reference to 6.4.5 on page 35, line13 6 implies that 6.4.5 describes scheduling options for all connections. 1415Current specification of rtPS service for uplink is incomplete in that there is no way for the scheduler to1617 know the interval at which it should issue unicast grant request IEs for the rtPS service flow.1819 To remedy these issues, the following text is proposed as replacement for the current contents of clause 6.4.5.20216.4.5 Scheduling services222324 Scheduling services represent the data handling mechanisms supported by the MAC scheduler for data25 transport on a connection. Each connection is associated with a single data service. Each data service is asso-26ciated with a set of QoS parameters which quantify aspects of its behavior. These parameters are managed27using the DSA and DSC message dialogs. Four services (11.13.13) are supported: Unsolicited Grant Service2829 (UGS), Real-time Polling Service (rtPS), Non-real-time Polling Service (nrtPS), ...

Informations

• Publié par: Shean
• Nombre de lectures: 9
• Langue: English

Extrait

2004-03-18

IEEE C802.16d-04/42r1

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

1

REVd/D3 Sponsor Ballot Comment Addendum

Bob Nelson

MacPhy Technologies

==========================================================================

The current document text is inconsistent regarding system scheduling. Although the parameters defined in

clause 11 are specified as being equally applicable to uplink and downlink, the only discussion of scheduling

in clause 6.4.5 specifically addresses only uplink operation. Similarly, the reference to 6.4.5 on page 35, line

6 implies that 6.4.5 describes scheduling options for all connections.

Current specification of rtPS service for uplink is incomplete in that there is no way for the scheduler to

know the interval at which it should issue unicast grant request IEs for the rtPS service flow.

To remedy these issues, the following text is proposed as replacement for the current contents of clause 6.4.5.

6.4.5 Scheduling services

Scheduling services represent the data handling mechanisms supported by the MAC scheduler for data

transport on a connection. Each connection is associated with a single data service. Each data service is asso-

ciated with a set of QoS parameters which quantify aspects of its behavior. These parameters are managed

using the DSA and DSC message dialogs. Four services (11.13.13) are supported: Unsolicited Grant Service

(UGS), Real-time Polling Service (rtPS), Non-real-time Polling Service (nrtPS), and Best Effort (BE). The

following text provides a brief description of each of the supported scheduling services, including the man-

datory QoS parameters that shall be included in the service flow definition when the scheduling service is

enabled for a service flow. A detailed description of each QoS parameter is provided in 11.13.

The UGS is designed to support real-time data streams consisting of fixed-size data packet transmitted at

periodic intervals, such as T1/E1 and Voice over IP without silence suppression. The mandatory QoS service

flow parameters for this scheduling service are Minimum Reserved Traffic Rate (11.13.10), Maximum Sus-

tained Traffic Rate (11.13.8), Maximum Latency (11.13.16), SDU Size (11.13.18), Tolerated Jitter

(11.13.15), and Request/Transmission Policy (11.13.14).

The rtPS is designed to support data streams consisting of variable-sized data packets that are transmitted at

fixed intervals, such as moving pictures experts group (MPEG) video. The mandatory QoS service flow

parameters for this scheduling service are Minimum Reserved Traffic Rate (11.13.10), Maximum Sustained

Traffic Rate (11.13.8), Maximum Latency (11.13.16), Nominal Service Interval (11.13.19), Tolerated Jitter

(11.13.15), and Request/Transmission Policy (11.13.14).

The nrtPS is designed to support delay-tolerant data streams consisting of variable-sized data packets for

which a minimum data rate is required, such as FTP. The mandatory QoS service flow parameters for this

scheduling service are Minimum Reserved Traffic Rate (11.13.10), Maximum Sustained Traffic Rate

(11.13.8), Traffic Priority (11.13.7), and Request/Transmission Policy (11.13.14).

The BE service is designed to support data streams for which no minimum service level is required and

therefore may be handled on an a space-available basis. The mandatory QoS service flow parameters for this

scheduling service are Maximum Sustained Traffic Rate (11.13.8), Traffic Priority (11.13.7), and Request/

Transmission Policy (11.13.14).