| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Dear Alina, Anh Tuan, and all, I agree that topology under mode changes is important. However, only 16j compatible RS may make the topology. Thus, I would like to discuss only the general case (2hop case; HR-BS<==>HR-MS(acting as RS)<==>HR-MS) in this moment. Whether more than 3hops in 16m compatible RS is allowable should be discussed further. Thanks & BRs, Eunkyung Kim Electronics & Telecommunications Research Institute (ETRI) From: Lu Liru, Alina [mailto:liru@nict.com.sg] Sorry, there is one typo I would like to correct. Please see the highlighted area. Dear Anh Tuan and Eunkyung, Thank you very much for coordinating the MM RG group. In my opinion, the network nodes after role-changing shall be treated as network stations corresponding to its operating function at the moment. The supported network topology will just follow what it has been defined in the accepted SRD document with agreeable IEEE 802.16n Network Reference Model. For example, for HR-MS operating at RS mode, it should be treated as HR-RS. Hence the topology "HR-BS <=> HR-MS (having changed role to HR-RS) <=> Normal HR-RS <=> Normal HR-MS" shall be supported as it is under the topology " HR-BS <=> HR-RS <=> HR-RS <=> HR-MS ". Thanks and regards, Alina Liru LU (呂 麗茹), Ph.D Research Scientist Wireless Communications Laboratory NICT Asia Research Centre Tel: (65) 6771 1006 Fax: (65) 6779 5753 From: Lu Liru, Alina [mailto:liru@nict.com.sg] Dear Anh Tuan and Eunkyung, Thank you very much for coordinating the MM RG group. In my opinion, the network nodes after role-changing shall be treated as network stations corresponding to its operating function at the moment. The supported network topology will just follow what it has been defined in the accepted SRD document with agreeable IEEE 802.16n Network Reference Model. For example, for HR-MS operating at RS mode, it should be treated as HR-RS. Hence the topology "HR-BS <=> HR-MS (having changed role to HR-RS) <=> Normal HR-RS <=> Normal HR-MS" shall be supported as it is under the topology " HR-BS <=> HR-MS <=> HR-RS <=> HR-MS ". Thanks and regards, Alina Liru LU (呂 麗茹), Ph.D Research Scientist Wireless Communications Laboratory NICT Asia Research Centre Tel: (65) 6771 1006 Fax: (65) 6779 5753 -----Original Message----- Dear Eunkyung and all, First of all, thanks Eunkyung for compiling the useful technical category table. The table captures well different topics and subtopics from the submitted contributions. Based on this, I would like to give the following comments: 1. We can combine relay and forwarding into one category, which gives us in total 4 categories: multimode, path management, relay operation, multicast. 2. Multimode and path management are very closely related, while relay operation is loosely related to these two categories. 3. Multicast is quite independent to the other 3 categories and can be discussed separately (through email, I mean). For multimode, I would like to propose one more sub-topic called "Allowable topologies under mode changes". I am not sure if this issue of which topologies are allowed before/after mode changes is captured under any sub-topic in Eunkyung's table, but this is one of the things we need to agree fist before discussing other details. As an example, do we allow a mode change of an HR-MS into HR-RS which results in the following topology: HR-BS <=> HR-MS (having changed role to HR-RS) <=> Normal HR-RS <=> Normal HR-MS? Btw, Brian and Ron have voiced their opinions that all discussions in RGs should be on the 16 email reflector. So, are we still using this mailing list? Best regards, Anh Tuan ________________________________ From: Eunkyung Kim [mailto:ekkim@etri.re.kr] Sent: Fri 4/8/2011 2:11 PM To: Hoang Anh Tuan; Mar Choong Hock; Joseph Teo Chee Ming; eldad.zeira@interdigital.com; fujimoto.kenichi@jrc.co.jp; gcummings@huawei.com; hvdien@nict.com.sg; Wang Haiguang; liru@nict.com.sg; mingtuo@nict.com.sg; nader.zein@eu.nec.com; rmao@huawei.com; Zheng Shoukang; upkar@ieee.org; Yeow Wai Leong; yihjan@yahoo.com; ym1004.son@samsung.com; zhangxin@nict.com.sg; ???; ???; ??? Cc: Hoang Anh Tuan; 'Eunkyung Kim' Subject: RE: [STDS-802-16] [802.16n] [MM] Work Plan for 802.16n Multi-mode and Multicast (MM) RG Hi all, I would like to initiate email discussion on the technical categorization of MM RG. I have categorized MM RG topic by topic based on the consolidated contributions for MM RG in IEEE 802.16n (C80216n-rg-11_0001.doc <http://dot16.org/ul/upload/gman_rg_db/C80216n-rg-11_0001.doc> ) as shown below Table. The purpose of category is to elevate the email discussion as well as 1st MM RG CC. Any comment is appreciated. Best Regards, Eunkyung Kim MM RG co-chair Table - Technical Category for MM RG in 802.16n category topic sub-topic Related contributions multimode Relay function for HR-BS change from HR-BS to RS rg-11/0026, rg-11/0033, rg-11/0034, rg-11/0036, rg-11/0039r1, n-11/0056r1 return to the HR-BS from RS Relay function for HR-MS capability negotiation rg-11/0026, rg-11/0033, rg-11/0034, rg-11/0036, rg-11/0039r1, n-11/0057r1 change from HR-MS to RS return to the HR-MS from RS replace the RS by other HR-MS(RS) Base Station function for HR-MS capability negotiation rg-11/0026, rg-11/0033, rg-11/0034, rg-11/0039r1 change from HR-MS to BS return to the HR-MS from BS replace the BS by other HR-MS(BS) Base Station function for HR-RS rg-11/0026 relay overall description rg-11/0032r1, rg-11/0055r1 alternative connection rg-11/0038 relay forwarding n-11/0024r2 forwarding relay forwarding n-11/0024r2 forwarding for multicast rg-11/0037 path management alternative path description rg-11/0027, rg-11/0036, rg-11/0039r1 path establishment rg-11/0029, rg-11/0036, rg-11/0039r1, n-11/0050r3 path maintenance rg-11/0029, rg-11/0036, rg-11/0039r1, n-11/0050r3 path selection(change) rg-11/0029 multicast overall description including addressing rg-11/0025, n-11/0045 multicast establishment n-11/0046 multicast operation n-11/0045, n-11/0046 multicast DL control n-11/0047 multicast security rg-11/0012, n-11/0048 local forwarding of multicast rg-11/0037 --------------------------------------------------------------------------------- Eunkyung Kim Electronics & Telecommunications Research Institute (ETRI) From: Eunkyung Kim [mailto:ekkim@etri.re.kr] Sent: Thursday, April 07, 2011 2:14 PM To: STDS-802-16@LISTSERV.IEEE.ORG Cc: 'Hoang Anh Tuan' (athoang@i2r.a-star.edu.sg); 'Eunkyung Kim' Subject: RE: [STDS-802-16] [802.16n] Work Plan for 802.16n Multi-mode and Multicast (MM) RG Dear 16n MM RG fans, Consolidated Contributions for MM RG in IEEE 802.16n (C80216n-rg-11_0001.doc <http://dot16.org/ul/upload/gman_rg_db/C80216n-rg-11_0001.doc> ) is uploaded in the RG upload directory. We encourage you to make an email discussion to accelerate harmonization. Remind you that the submission deadline of comment on the released consolidated MM RG document is noon(AOE), 08 April 2011. If you have any comment, please let Anh and me know. Best Regards, Anh Tuan & Eunkyung MM RG Chairs From: Eunkyung Kim [mailto:ekkim@ETRI.RE.KR] Sent: Friday, April 01, 2011 10:33 AM To: STDS-802-16@LISTSERV.IEEE.ORG Subject: Re: [STDS-802-16] [802.16n] Work Plan for 802.16n Multi-mode and Multicast (MM) RG Dear 802.16n participants, Please read the instruction carefully before uploading any contribution in RG directory. Instruction says "Choose the next available serial number based on the documents in the upload directory and those in the associated file index." Thanks & BRs, Eunkyung --------------------------------------------------------------------------------- Eunkyung Kim Electronics & Telecommunications Research Institute (ETRI) -----Original Message----- From: Hoang Anh Tuan [mailto:athoang@I2R.A-STAR.EDU.SG] Sent: Tuesday, March 29, 2011 5:54 PM To: STDS-802-16@LISTSERV.IEEE.ORG Subject: [STDS-802-16] [802.16n] Work Plan for 802.16n Multi-mode and Multicast (MM) RG Dear 802.16n participants, The Work Plan for 802.16n Multi-mode and Multicast (MM) RG has been uploaded to < http://dot16.org/ul/ul.cgi?command=viewupload&database=gman_db <http://dot16.org/ul/ul.cgi?command=viewupload&database=gman_db> >, document C80216n-11_0062.doc <http://dot16.org/ul//upload/gman_db/C80216n-11_0062.doc <http://dot16.org/ul/upload/gman_db/C80216n-11_0062.doc> > . Please go through and let Eunkyung and I know of any concerns. Best regards, Anh Tuan & Eunkyung MM RG Chairs -----Original Message----- From: Eunkyung Kim [mailto:ekkim@etri.re.kr <mailto:ekkim@etri.re.kr> ] Sent: Tue 3/29/2011 9:52 AM To: STDS-802-16@LISTSERV.IEEE.ORG Subject: Re: [STDS-802-16] [802.16n] 802.16n RG Upload directory Hi Sungcheol and all, Thank you for the announcement. In addition, detailed information of the MM RG discussion will be announced asap. Warm Regards, Anh & Eunkyung MM RG Chairs From: Chang, Sungcheol [mailto:scchang@ETRI.RE.KR <mailto:scchang@ETRI.RE.KR> ] Sent: Tuesday, March 29, 2011 10:35 AM To: STDS-802-16@LISTSERV.IEEE.ORG Subject: [STDS-802-16] [802.16n] 802.16n RG Upload directory Dear 802.16n participants, RG co-chairs are glad to announce 802.16n RG upload directory. The 16n RG upload directory is available at <http://dot16.org/ul/ul.cgi?command=viewupload&database=gman_rg_db <https://owa.i2r.a-star.edu.sg/exchweb/bin/redir.asp?URL="" <http://dot16.org/ul/ul.cgi?command=viewupload&database=gman_rg_db%20%3chttps://owa.i2r.a-star.edu.sg/exchweb/bin/redir.asp?URL="">> > >. Because two RGs, DC and MM, will share one place, please add a RG tag to title of 16n RG contribution as the followings: - "[DC]" prefix for DC RG - "[MM]" prefix for MM RG. Note: See <IEEE C802.16n-11_0061> for more information of DC RG. Best regards, Sungcheol Chang, Ph.D. Mobile Access Technology Research Team, ETRI Sungcheol Chang and Ming-Tuo Zhou, DC RG co-chairs. Anh Tuan and Eunkyung Kim, MM RG co-chairs. |