80216n-10-0045
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Minutes of GRIDMAN Teleconference 2010-12-07
Date
Submitted
2010-12-07
Source(s)
Tim Godfrey
E-mail: tim.godfrey@ieee.org
EPRI
Re:
Abstract
Teleconference Minutes
Purpose
Notice
Release
Patent
Policy
This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It
represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for
discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material
contained herein.
The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution,
and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name
any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole
discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The
contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.16.
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
<http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and
<http://standards.ieee.org/guides/opman/sect6.html#6.3>.
Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and
<http://standards.ieee.org/board/pat>.
80216n-10-0045
GRIDMAN Teleconference Minutes
7-December-2010
Participants:
Tim Godfrey – EPRI (TG Chair)
DJ Shyy - Mitre
Eldad Zeira - Interdigital
xin zhang - NICT
mingtuo – NICT Singapore
Suncheol Chang, ETRI
Youngbin Chang - Samsung
Eunkyun Kim – ETRI
Topics for 7-December:
Definitions of R1 interface ((Not discussing backward compatibility modes)),
Definition of relation between capability and role.
New Contribution IEEE 802.16n-10/0062, “Mesh Topology for Relays”, from D. J. Shyy, MITRE
Discussion
Which reliability is addressed with mesh topology? DJ says the case of a disappearing relay
would be supported by a mesh, not a tree.
Can multiple paths be accomplished without a mesh? Maybe by role changing MS to RS it would
be possible.
Is a tree limited to a single path or multiple paths? A multi-hop relay can configure different
paths while maintaining a tree topology.
The root of the tree is a BS. Can a MS reach another RS by only passing through RS, and not BS.
Local Forwarding by a relay allows MS to MS via RS without passing through a BS.
To change the SRD requires a CR with 75% vote. This cannot be done on a conference call.
80216n-10-0045
Contribution C80216n-10_0063.doc “Proposed System Architecture Reference Model for IEEE 802.16n”
(Samsung, ETRI)
In the case of row 3, what is the case for RS to RS interface? Does the RS to RS interface require
a different drawing.
There is disagreement on whether we need to show HR-RS to HR-RS in network reference
model. It causes it to become too complex graphically.
Considering C80216n-10_0064, the HR-MS to HR-MS link is designated as R’mm, because the
source and sink relationship is limited to the two HR-MS devices. The Rmm difference is the
source and the network entity.
If the RS can source and sink data, but the partner is still a network entity.
Intention of network reference model is based on WiMAX network document model. We don’t
want to change that model. The interface between entity and entity is describes. It does not
include source and sink.
Youngbin agrees that HR-RS can be source and sink. Also, in the local forwarding case the data
does not go through the network.
We may still need another diagram to describe source and sink relationships.
The network reference model should be simple and define the reference point only.
Eldad thinks this diagram could be much more complicated if we add cases for local forwarding.
Document 0063 shows the interfaces and protocols, but another diagram is needed to show the
source and sink.
Contributions are requested to provide a diagram for the 802.16n Network Reference Model. They will
be discussed in the January meeting.
For next call, we will discuss protocol structure.
January 4 (Time Slot 1) Dial-in Number: 1-270-400-1500
•Topic: Protocol Structure
Participant Access Code 484164