Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Dear Alex and all
Thank you very much for the fruitful discussion. Here is my view which my colleagues (co-authors) of the document share with me.
-Instead of using the term “802.19 air interface device”, we prefer to use the term “P802.19.1 system”.
The rational is that the guidelines defined in LA require to make system requirements considering 802.19.1 as a single entity.
-Regarding your requirements 1, 2 and 3, we feel that technically they are the same as requirement 4 (slide 6), but they are splitting P802.19.1 system into entities, which contradicts to the guidelines.
-Regarding your requirement 4, it is already covered in requirement 6 (slide 8).
To further improve the clarity, we have reworded our requirement 4 (slide 6) as follows:
P802.19.1 system shall support different architectural options of decision making for TVWS coexistence (e.g. centralized, distributed and autonomous)
Thank you very much
Yohannes
From: Alex Reznik [mailto:alexr.at.ieee@xxxxxxxxx]
Sent: Thursday, February 18, 2010 3:02 AMSubject: [802.19] Fwd: [802.19] Regarding P802.19.1 requirements
Oops, everyone, I forgot to hit "reply all" on my original message. Sorry.
---------- Forwarded message ----------
From: Alex Reznik <alexr.at.ieee@xxxxxxxxx>
Date: Wed, Feb 17, 2010 at 1:01 PM
Subject: Re: [802.19] Regarding P802.19.1 requirements
To: Yohannes <yohannes@xxxxxxxxxx>
Hi, Yohannes,
Thanks for the response and my apologies for the repetitive comment, I could not attend the conference yesterday. At the danger of repeating comments once again, let me then add that it seems to be that these requirement do not translate very well into system requirement and the work that will still need to be done is somewhat more then trivial. As an example, let us consider slide 6 (requirement 4/7). From a system point of view, what you appear to be going for is something like the following set of requirements:
1. Each 802.19 air interface device shall be capable of independent decision making.
2. Each 802.19 air interface device shall be capable of coordinating its decisions with other such device.
3. Each 802.19 air interface device shall be capable of utilizing services provided by a centralized entity in making its decisions.
4. Each 802.19 air interface device shall be capable of implementing decisions (service requests???) of a centralized entity or other 802.19 air interface devices.
I would think that pretty much all the requirements would need to be reworded into something like this...
Thanks,
Alex
On Tue, Feb 16, 2010 at 8:58 PM, Yohannes <yohannes@xxxxxxxxxx> wrote:
Dear Alex
Thank you very much for the remarks. As I tried to explain during the teleconference, the intention is to put high-level requirements on the 802.19.1 system that we specify in the standard. By saying this, we need to ensure the necessary components included in the standard to meet these system requirements.
Regards
Yohannes
From: Alex Reznik [mailto:alexr.at.ieee@xxxxxxxxx]
Sent: Wednesday, February 17, 2010 6:26 AM
To: Yohannes
Cc: STDS-802-19@xxxxxxxxxxxxxxxxx
Subject: Re: [802.19] Regarding P802.19.1 requirements
Hi, Yohannes,
Thank you and your colleagues very much for uploading this presentation, I think it provides an excellent start in this important process.
In addition to seconding Richard's comments on security, I would like to point out that this presentation i somewhat ambiguous about whether these are requirements on us (i.e. 802.19.1 as a group of people) or on the technology we are trying to develop/standardize. Would you please clarify?
Many thanks,
Alex
On Mon, Feb 15, 2010 at 5:25 AM, Yohannes <yohannes@xxxxxxxxxx> wrote:
Dear all
We have uploaded a PDF file with DCN 19-10-0031-00-0001 on the IEEE mentor (https://mentor.ieee.org/802.19/documents) that provides a list of P802.19.1 system requirements. The material is intended for presentation during the Feb 16 telephone conference of the TG to discuss on requirements.
Regards
Yohannes
==================================================
Dr. Yohannes Alemseged Demessie, Expert Researcher
Ubiquitous Mobile Communications GroupNew Generation Wireless Communications Research Center
---------------------------------------------------------------------------------------------------
National Institute of Information and Communications Technology
3-4, Hikarino Oka, Yokosuka, 239-0847, Japan
==================================================