Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-16] [802.16n] [MM] Agenda for 16n MM RG 2nd Conference Call - Proposed harmonized text for multi-mode



Thanks Anh Tuan,

 

Please see comments below – hope this helps

 

Eldad

Office   +1 631 622 4134

Mobile +1 631 428 4052

Based in NY area

 

From: Anh Tuan Hoang [mailto:mbox.hoang@GMAIL.COM]
Sent: Tuesday, May 03, 2011 7:39 AM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] [802.16n] [MM] Agenda for 16n MM RG 2nd Conference Call - Proposed harmonized text for multi-mode

 

Hi all,

 

Based on email discussions for multi-mode topic, I would like to propose that the following text to be considered for harmonization. Alina and others, please comment.

 

Proposed text:

 

[Upon loosing backhaul connection, an HR-BS (affected HR-BS) shall be able to operate as a relay station to communicate with another HR-BS (supporting HR-BS) that has connection to backhaul. To the supporting HR-BS, the affected HR-BS is treated as a normal HR-RS. To the subordinate stations of the affected HR-BS, the affected HR-BS may continue to act as an HR-BS or completely operate as a normal HR-RS.

[Eldad] could you clarify – what is the difference between how an ARS and an ABS look to their MS?

 

In the absence of any infrastructure station, an HR-MS may be able to operate as a base station to provide connectivity for itself and other HR-MSs. While doing so, the HR-MS shall maintain the MS and base station functionalities. The mode switch to HR-BS can be initiated by the HR-MS itself or this can be directed by the superordinate station of the HR-MS in response to SPOF (e.g., failure of the superordinate station).

[Eldad] I think we need to define the meaning of “MS functionality”. Part of MS functionality is to be controlled by an ABS. I don’t think we want to retain this part. I think the only part of MS functionality is for local source and sink of data. However we already have a requirement for HR-BS to do that.

In addition, if a super-ordinate node exists and can communicate with the HR-MS why does it need to become an HR-BS?

I would like to suggest therefore:

In the absence of any infrastructure station, an HR-MS may be able to operate as an HR-BS base station to provide connectivity for itself and other HR-MSs. While doing so, the HR-MS shall maintain the MS and base station functionalities. The mode switch to HR-BS can be initiated by the HR-MS itself and can be based on network information previously received from the network. or this can be directed by the superordinate station of the HR-MS in response to SPOF (e.g., failure of the superordinate station).

 

 

In response to SPOF (e.g., HR-BS/RS failure or loss of backhaul) or to support coverage extension, an HR-MS may be able to operate as a relay station to provide connectivity for multiple affected/out-of-coverage HR-MSs. While doing so, the HR-MS shall maintain the MS and relay functionalities. A mode switch to HR-RS shall be initiated by the superordinate station of the HR-MS.]

[Eldad] like the HR-BS, an HR-RS is already required to provide local source – sink. Therefore I would like to suggest the text

In response to SPOF (e.g., HR-BS/RS failure or loss of backhaul) or to support coverage extension, an HR-MS may be able to operate as a relay station to provide connectivity for multiple affected/out-of-coverage HR-MSs. While doing so, the HR-MS shall maintain the MS and relay functionalities. A mode switch to HR-RS shall be initiated by the superordinate station of the HR-MS.]

 

 

Best regards,

Anh Tuan

 

On Mon, May 2, 2011 at 5:36 PM, Hoang Anh Tuan <athoang@i2r.a-star.edu.sg> wrote:

Hi all,

Please be reminded of the coming 2nd Conference Call for MM RG. The details are:
- Time: May 3 2011, 9AM Eastern US, 6AM Pacific, 10PM Japan/Korea
- Duration: 1.5 hours
- Dial in:  +1-866-457-0015; pin 8109
- LiveMeeting:
https://www.livemeeting.com/cc/epripremier/join?id=WMMKF7&role=attend&pw=8f%29K-mM%5Dr
<https://www.livemeeting.com/cc/epripremier/join?id=WMMKF7&role=attend&pw=8f%29K-mM%5Dr> Meeting ID: WMMKF7
Attendee Entry Code: 8f)K-mM]r

We would like to propose the following tentative agenda:
1. Taking attendance
2. Approving agenda
3. Reviewing email discussions on the 4 topics of: Multi-mode, Relay/forwarding, Path Management, Multicast by corresponding leaders (Alina Liru Lu, Zhang Xin, Hoang Vinh Dien, Eunkyung Kim). Each topic will be allocated 20 minutes with the aim of reaching some harmonized text or common understanding
4. Any other business
5. Closing

To facilitate the discussion, we would like to ask the leaders of email discussion topics to prepare consolidated text in advance.

Please comment.

Best regards,
Anh Tuan and Eunkyung
802.16n MM RG Co-chairs