Comment Resolution Details

Comment Resolution Details

-

Documents
8 pages
Lire
Le téléchargement nécessite un accès à la bibliothèque YouScribe
Tout savoir sur nos offres

Description

2001-09-13IEEE 802.16.1c-01/36r1Project IEEE 802.16 Broadband Wireless Access Working Group Title Comment Resolution DetailsDate Submitted 2001-09-13Source(s) Carl Eklund Voice: +348504836566Nokia Research Center Fax:+358718036851P.O.BOX 407mailto:carl.eklund@nokia.comFIN-00045 Nokia Group, FinlandRe:IEEE Sponsor Ballot of IEEE P802.16/D4-2001AbstractAdds specific detail to comment resolutionsPurposeFor use in conjunction with comment resolution databaseThis document has been prepared to assist IEEE 802.16. It is offered as a basis for discussion and is not Noticebinding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this Releasecontribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.16.The contributor is familiar with the IEEE 802.16 Patent Policy ...

Sujets

Informations

Publié par
Nombre de visites sur la page 55
Langue English
Signaler un problème
2001-09-1
3
IEEE 802.16.1c-01/36r1
Project
IEEE 802.16 Broadband Wireless Access Working Group <
http://ieee802.org/16
>
Title
Comment Resolution Details
Date Submitted
2001-09-13
Source(s)
Carl Eklund
Voice: +348504836566
Nokia Research Center
Fax:+358718036851
P.O.BOX 40
7
mailto:carl.eklund@nokia.com
FIN-00045 Nokia Group, Finland
Re
:
IEEE Sponsor Ballot of IEEE P802.16/D4-2001
Abstrac
t
Adds specific detail to comment resolutions
Purpos
e
For use in conjunction with comment resolution database
Notice
This document has been prepared to assist IEEE 802.16. It is offered as a basis for discussion and is not
binding on the contributing individual(s) or organization(s). The material in this document is subject to
change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or
withdraw material contained herein.
Release
The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this
contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in
the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution;
and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE
Standards publication. The contributor also acknowledges and accepts that this contribution may be made
public by IEEE 802.16.
Patent Policy
and Procedures
The contributor is familiar with the IEEE 802.16 Patent Policy and Procedures (Version 1.0)
<
http://ieee802.org/16/ipr/patents/policy.html
>, including the statement “IEEE standards may include the
known use of patent(s), including patent applications, if there is technical justification in the opinion of the
standards-developing committee and provided the IEEE receives assurance from the patent holder that it will
license applicants under reasonable terms and conditions for the purpose of implementing the standard.”
Early disclosure to the Working Group of patent information that might be relevant to the standard is essential
to reduce the possibility for delays in the development process and increase the likelihood that the draft
publication will be approved for publication. Please notify the Chair <mailto:r.b.marks@ieee.org> as early as
possible, in written or electronic form, of any patents (granted or under application) that may cover
technology that is under consideration by or has been approved by IEEE 802.16. The Chair will disclose this
notification via the IEEE 802.16 web site <
http://ieee802.org/16/ipr/patents/notices
>.
2001-09-13
Copyright © 2001 IEEE All rights reserved
27
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
Comment: Replace Figure 45 on page 132 with Figure 1 below. Rationale: Figure 45 is incorrect
Comment: Insert figures 2 and 4 into section 6.2.9.2. on page 132. Rationale: The figures clarify the text
Figure 1— SS Initialization Overview
Obtain
Uplink
Parameters
Uplink
Parameters
Acquired
Ranging &
Automatic
Adjustments
Ranging &
Auto Adj
Complete
Establish IP
Connectivity
IP
Complete
Establish
Time of
Day
Time of Day
Established
Transfer
Operational
Parameters
Transfer
Complete
Register
with
BS
Registration
Complete
SS authorization
and
Key Exchnage
SS
Authorization
Complete
Downlink
Synchr.
Established
Scan for
Downlink
Channel
Establish
provisioned
connections
Negotiate
Basic Capabilities
Basic
Capabilities
Negotiated
Operational
2001-09-13
Copyright © 2001 IEEE All rights reserved
28
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
Figure 2— Obtaining Downlink Synchronization
Scan for
Downlink
Channel
Downlink
Synchr.
Established
DL-MAP
Start
Lost DL-MAP
Start
T1
Start
T12
Synchronized
Figure 4— Maintaining Downlink Synchronization
Synchronized
DCD
Reset T1
Synchronized
DL-MAP
Reset Lost
DL-MAP
Timeout
Lost DL-MAP
Timeout
T1
Scan for
Downlink
Channel
2001-09-13
Copyright © 2001 IEEE All rights reserved
29
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
Comment: Replace figure 49 with figure 3 above. Rationale: Diagram in figure 49 lacks an initial state.
Figure 3—Registration — SS
Wait for
REG-RSP
REG-REQ
Register with
BS
2001-09-13
Copyright © 2001 IEEE All rights reserved
30
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
Figure 5— Obtaining Uplink Parameters
Channel
Usable?
Wait
for downlink
synchr.
Downlink
Synchr.
Established
Obtain
Uplink
Parameters
UCD
with descriptor
for ChID=i
Reset T12
Add
channel ChID=i
to channel list
Uplink
parameters
Acquired
Mark
channel ChID=i
usable
Yes
Timeout
T12
Scan for
Downlink
Channel
Mark
downlink
unusable
Maintain
Uplink
No
Start
Lost UL-MAP
Interval
2001-09-13
Copyright © 2001 IEEE All rights reserved
31
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
Comment: Insert figures 5 and 6 of this document into section 6.2.9.3 Rationale: The figures clarify the text
Comment:Create new section H3 between 6.2.12 and 6.2.13 on page 151 with the heading “Assigning SSs to
multicast groups”The content of the section: “ The BS may add an SS to a Multicast polling group by send-
ing a MCA-REQ message with the Join command. Upon receiveing a MCA-REQ the SS shall respond by
Figure 6— Maintain Uplink Parameters, Single Uplink Case, ChID=i
Maintain
Uplink
UCD
with descriptor
for ChID=i
Reset T12
Timeout
T12
Obtain
Uplink
Parameters
Maintain
Uplink
Uplink
Parameters
Invalid
Delete
Ch.Param.
from Ch. List
Timeout
Lost UL-MAP
Interval
UL-MAP
with
ChID=i
Reset
Lost UL-MAP
Interval
2001-09-13
Copyright © 2001 IEEE All rights reserved
32
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
sending a MCA-RSP. The protocol is shown in Figure 7 and Figure 8. “ Add the corresponding figures to this
section.
On page 299 add row to table 118 with the content |BS|T15|Wait for MCA-RSP | 20 ms | 20 ms| |
On page 101 line 46 replace paragraph with ”The Multicast Polling Assignment Request message is sent to
an SS to assign it to or remove it from a multicast polling group. The format of the message is shown in <ref-
erence table 45>.”
Success?
Figure 7— Multicast Polling Assignment, SS
Wait
for
MCA-REQ.
Delete Mulitc
CID from transm.
opportuinities.
Yes
Wait for
MCA-REQ
No
MCA-REQ
Add/
Remove
?
Add Multic.
CID to transm.
opport.
Set
Confition Code =
failed
Set
Confition Code =
Okay
Join
Leave
MCA-RSP
2001-09-13
Copyright © 2001 IEEE All rights reserved
33
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
Rationale for comments: The MCA-XXX protocol is not currently defined. The comment provides a defin-
tion and corrects the description of the message. Sending MCA-REQs to a multicast group was removed as
it would complicate the protocol horribly.
Retries
Available
Figure 8— Multicast Polling Assignment, BS
Wait
Yes
Wait for
MCA-RSP
No
MCA-RSP
Cond,
Code=OK
?
Start
T15
MCA-REQ
Assign
SS to
polling group
Remove
SS from
polling group
Timeout
T15
Wait
Transaction
Failed
Transaction
Successful
Yes
No