| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear Yan-Xiu, Same problem here J 1. My reply comment on C802.16maint-11/0003: Rejected l AMS can
join more than one multicast group. In that sense, the proposal is increasing
the number of CRC Mask IDs required for AMS’s MAP CRC de-masking at every
subframe. It is more burden to AMS in term of MAP search/detection in PHY level l There is
no CRC Mask ID for broadcast in the proposal. It shows only CRC Mask IDs for
Multicast 2. My reply comment on C802.16maint-11/0005: Accepted-Modified Basically, I am ok with the contributions. But wording needs
to be modified as follows: l In the
remedy #1
l In the
remedy #2
BRs Yeongmoon Son From:
Inuk Jung [mailto:inuk.jung@LGE.COM] Dear Yan-Xiu, I was also not
able to submit reply comments for both cr73-2009 and cr73-m databases. I’ve uploaded
reply contributions on two comments which, refer to contributions 80216maint-11_0001.doc
(Author: Hyunjeong Kang) and C80216maint-11_0002.doc
(Author: Hyunjeong Kang) My reply
recommendation (80216maint-11_0001.doc): Accept-modified. Suggest to review
contribution IEEE C802.16maint-11/0008 including suggested modification. My reply
comment reason: In
perspective of overhead and deployment scenario, we think that providing a zone
switch TLV (Inter-FA) with the carrier information of the 16m carrier is a
simple approach to allow the MS to handover to a 16m only network. My reply
recommendation (80216maint-11_0002.doc): Accept-modified. Suggest to review
contribution IEEE C802.16maint-11/0007 including suggested modification. My reply comment
reason: Including system
information of legacy systems, in the AAI-NBR-ADV message, results in
duplicative information broadcasting. This may incur overhead in case when the
frequency of performing HO to a legacy BS is low. Hence, it may be more efficient
to provided the system information of legacy systems upon request. This contribution
proposes to include DCD/UCD change count information in the AAI-HO-REQ message
to support handover to the legacy BS. Best Regards. Inuk Jung. From: Erik
Colban [mailto:ecolban@HUAWEI.COM] Yan-Xiu, Four calls for comments were issued on 13
April 2011. The comment period for ballots cr73-2009, cr73-m, cr73-j and cr73-h
are closed. No comments were received for cr73-j and cr73-h. The commentary database containing comments
for cr73-m can be found at <802.16maint-11_0009> The commentary database containing comments
for cr73-2009 can be found at <802.16maint-11_0010> 5 comments were received for the ballot
cr73-m. 1 comment was received for the ballot
cr73-2009 This note is a call for reply comments,
with a deadline of Monday 16 May 2011 at 9:00 AM Edmonton time <http://tinyurl.com/277uhde>. To enter reply comment, ,please click the
“Reply” button on the left side under Member view Use the "Submit Reply Comments"
tab in the upper right corner to export your replies to a file for
uploading, per the embedded instructions. Reply comments, in "cmtr"
format, need to be uploaded to the “cr_comments” upload directory <cr_comments
>. For the current database
“80216maint-09_0007r14”, I would like to separate into two parts: 1. the
comments marked by “ready for ballot” in 80216maint-09_2007r12; 2. the rest
comments in 80216maint-09_0007r14. During the maintenance task group opening,
we will discuss how to maintain the database. For the first part, I would also
like to make a motion to accept these comments and incorporate them into
cr73-2009 or reversely as resolution during the maintenance opening since IEEE
std. 802.16m has been approved. For the second part, we will also review during
this meeting. Thanks for your contributions and looking
forward to see you in Lake Louise. Best regards, Zheng Yan-Xiu 802.16 Maintenance Task Group Chair No virus found in this message. 本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。 --
CONFIDENTIAL: The information in this message is confidential and
may be legally privileged. It is intended solely for the addressee(s). Access
to this message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful. Please immediately contact the sender if
you have received this message in error. Thank you. |