| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear all, I updated the consolidated
contribution as C80216p-rg-11_0032r5 to include the proposed text in
C80216p-rg-11_0035 (submitted by Jaesun) and the updated text in
C80216p-rg-11_0028r1. Regards, Kiseon Ryu PWR RG Chair From: Kiseon Ryu [mailto:kiseon.ryu@LGE.COM]
Dear
16p members, The
meeting minutes for 2nd PWR RG CC are as follows: 1.
Email discussion summary (80216p-rg-11_0041)
was reviewed. 2.
Harmonized contribution on Idle Mode
Operation (C80216p-rg-11_0036r1) was reviewed. A.
Members agreed to the blue text in the
contribution as the consensus text B.
Consensus text will be included without
bracket in the updated document for consolidated contribution. 3.
Harmonized contribution on NE#2
(C80216p-rg-11_0028r1) and NE#1(C80216p-rg-11_0040) were reviewed. A.
Some members raised concern on NE#2
(C80216p-rg-11_0028r1) as follow.
i.
If BS does not know when M2M devices perform network
re-entry, static and periodic assignment of dedicated ranging resource can
increase resource overhead. B.
Some members raised concern on
NE#1(C80216p-rg-11_0040) as follows.
i.
If the M2M device receives multicast traffic
indication in paging message, it does not have to perform network re-entry to
receive the multicast traffic. In this case, access restriction has no meaning.
ii.
Ranging abort in RNG-ACK message can be used
for this kind of access restriction. 4.
Key issues for NE#1 and NE#2 were discussed. A.
Some members shared their views on the issue
of the priority based ranging parameter differentiation
i.
We need to analyze the gain of priority based
ranging parameter differentiation.
ii.
In the case of predictable re-entry of M2M
devices, ranging parameter can be different to M2M devices/groups to distribute
the re-entry load.
iii.
Ranging parameter means not only ranging
parameter values (e.g., opportunity window, backoff window, etc.) but also
assignment of dedicate ranging resource to M2M devices/groups. B.
Members agreed to the high level text for
NE#1 and NE#2 below and it will be included without bracket in the updated
document.
i.
Ranging parameters may be different to M2M
devices or M2M groups. C.
Through the email discussion, detailed text
will be discussed further. 5.
DC#1 (C80216p-rg-11_0037) were reviewed. A.
Some members raised concern on the gain of
device collaboration. I
updated the consolidated contribution C80216p-rg-11_0032r4 based on the 2nd
PWR RG CC result. The
third and final call for PWR RG will be on Thursday, March 24, 2011, 8AM-10AM
US Central Time. Any
comment or question will be welcomed. Regards Kiseon
Ryu PWR
RG Chair |