Re: [STDS-802-16] [MMR-AH-UM] Announcing 6/22/06 Meeting of Multihop Relay Usage Model Ad Hoc Group
Hi Jerry and All,
I also agree to remove the sentence of "It should be noted that even
when multiple routes are enabled ...".
Thanks!
Jen-Shun Yang (Tonny Yang)
ITRI/ICL
TEL:+886-3-5914616
email: jsyang@itri.org.tw
---------------- Original Message ----------------
> Joseph Kim <kyeongsoo.kim@GMAIL.COM> 2006-06-22 03:32:47 AM wrote:
收件人: STDS-802-16@listserv.ieee.org
主旨: Re: [STDS-802-16] [MMR-AH-UM] Announcing 6/22/06 Meeting of Multihop
Relay Usage Model Ad Hoc Group
Jerry and All,
Sorry, but I just found out that Jerry already answered the same
questions/comments from J. Kim in another thread. So in that regard, I
would also propose to remove the said sentence from the document.
Regards,
Joseph
On 6/21/06, Joseph Kim <kyeongsoo.kim@gmail.com> wrote:
Hi Jerry,
Additional comments/questions in Sec. 5.3:
I know the 2nd paragraph of Sec. 5.3 has already been extensively discussed
by many, but the very sentence of "It should be noted that even when
multiple routes are enabled ..." seems to me very unclear:
If we (implicitly) assume here asymmetric routes where for a given
direction (either UL or DL) there is only one path between a source and a
destination, we should clarify that. Otherwise we cannot say the overall
topology is still "tree-like", which is simply not the case when there are
multiple & simultaneous paths between a given source and destination.
In 16j PAR, is there any statement limiting or prohibiting the use of
non-tree topology? I couldn't find any mentioning of topology at all in the
approved PAR (dated 3/30/2006).
Again, many thanks in advance!
Joseph
On 6/21/06, Joseph Kim < kyeongsoo.kim@gmail.com> wrote:
Hi Jerry,
I have the same questions as Jen-Shun regarding the figure in Sec. 5. In
fact, I wonder whether the current descriptions on association in Sec. 5.1
include the following cases or not:
An MS can simultaneously(?) be associated with both MMR-BS and RS ( i.e.,
"MS 2" in the figure)
An MS can simultaneously(?) be associated with multiple RSs (i.e., "MS 3");
An RS can simultaneously(?) be associated with multiple RSs (i.e., "RS 4").
Many thanks in advance for your clarification!
Regards,
Joseph
--
Principal Engineer
Advanced System Technology
STMicroelectronics
- Mobile: (408) 621-4913
- kyeongsoo.kim@st.com / kks@stanford.edu
- http://www.stanford.edu/~kks/
On 6/20/06, Jen-Shun Yang <jsyang@itri.org.tw> wrote:
Dear Jerry,
I got two questions about section 5.
1. Are the MS2 and MS3 in Figure 4 describing the cooperative transmission
or the asymmetric routes of uplink and downlink or both? If they are just
meant to the asymmetric routes of uplink and downlink, I would suggest that
you may change the line of one accee link of MS2 and MS3 to be a dot-line.
2. Does the multiple routing path between MMR-BS and RS4 been used
simultaneously? If they are not been used simultaneously, I would suggest
that you may change the line of one access link of RS4 to be a dot-line,
otherwise the figure 4 is not a "tree-like" topology.
Best Regards,
Jen-Shun Yang (Tonny Yang)
ITRI/ICL
TEL: +886-3-5914616
email: jsyang@itri.org.tw
"Sydir, Jerry" <jerry.sydir@INTEL.COM> -
2006/06/16 06:02 AM
請回信 給 "Sydir, Jerry"
收件人： STDS-802-16@listserv.ieee.org ,
副本抄送： ,
主旨： [STDS-802-16] [MMR-AH-UM]
Announcing 6/22/06 Meeting of Multihop Relay Usage Model Ad Hoc Group
Dear Ad Hoc participants,
The next meeting of the Multihop Relay Usage Model Ad Hoc Group will occur
on Thursday June 22, 06:00 – 07:45 PDT (13:00 – 15:00 UTC). (Note that we
will finish 15 minutes earlier due to conflicts).
The bridge for the meeting is 916-356-2663, Bridge: 2, Passcode: 3578218
I have updated the draft to include modifications to the outline that we
agreed to in the June 15 meeting. It can be found in the following
location:
http://dot16.org/CSUpload//upload/temp_db/C80216j%2d06_UMAHtemp_r4.doc
Please review the changes to make sure they are consistent with what we
decided.
The main topics planned for the meeting are:
- Go over any issues identified in the current version of the
document
- Discuss the new usage model proposal put forth by Matt
Sherman (Matt will upload updated version prior to the meeting
Please send comments and issues that we need to discuss to the mail list
prior to Wednesday June 14 8 AM PDT. I will send out a detailed agenda for
the meeting on Wendesday.
Regards,
Jerry Sydir
本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並
請銷毀此信件。
This email may contain confidential information. Please do not use or
disclose it in any way and delete it if you are not the intended recipient.
本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。
This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.