| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Stefano, Thanks for providing your input. I'm addressing your comments below. Regards, Ulises -----Original Message----- Ulises, I have a few additional comments on the slides: - slide 3, "Ensure that 802.21 requirements be considered within
other standard bodies ": this statement presumes that 3GPP has to respect
802.21 requirements. From 3GPP point of view this may be a strong presumption.
Since I think the burden is on 802.21 to get its concepts accepted by 3GPP, we
cannot expect a good reaction to such a statement. (Ulises Olvera) I agree, I will re-state accordingly. - slide 4: The current picture may generate confusion. I think it is
wrong to describe figure 4 as the MIH model, since it represent s only part of
the model. I would show a model where both an MIHF in the terminal and an MIHF
in the network are visible, and keep this slide indicating it is for MIHF in
the terminal. I think we need to keep in mind that large part of the audience
does not know anything about 802.21. The slides (e.g. use of terms) seem
instead to assume that 3GPP has good understanding of 802.21. E.g., by seeing
figure 4 one may think this refers to the function in the network, and by
seeing that the MIH Function is above UTRAN and GERAN "Link Layer" one
may think that there would be a new interface towards WLAN in 3GPP RANs, to
exchange measurement reports and commands between accesses. One may then
conclude this makes no sense for 3GPP, since it would introduce a new interface
in existing RANs that many people in 3GPP think would be practically
impossible. A! gain, my suggestion is to clarify things as much as possible to
avoid confusion. We need to sell these concepts to 3GPP, therefore the burden
is on us to make them understandable and appealing. (Ulises Olvera) Your points are valid. We
need to agree on a model that can satisfy these concerns, yet keeping it
simple. I’ll take a ‘stab’ to a revised model and I will
include it for discussion within tomorrow’s conference. - I think it should be made clearer in the slides that 802.21 focuses
only on inter-technology handoff (e.g. 3GPP-802.11), and is not meant to apply
to mobility within 3GPP-specific access technologies (Ulises Olvera) A statement clarifying
this will be added. - I think that the slides without e.g. a couple of example scenarios
would be very difficult to read and understand by 3GPP people. (Ulises Olvera) Valid point. I propose to
use 3GPP defined scenarios to construct the examples. I will include a couple
of examples for review. Stefano -----Original Message----- From: ext Olvera-Hernandez, Ulises
[mailto:Ulises.Olvera-Hernandez@INTERDIGITAL.COM] Sent: Thursday, August 11, 2005 15:27 To: STDS-802-21@LISTSERV.IEEE.ORG Subject: [802.21] 802.21-3GPP2 Interoperation Telecoference MoM Recorded Participants: Stefan Berg, Kalyan Koora, Subir Das, Ajay Rajkumar, Peretz Feder, Alan
Carlton, Yogesh Bhatt, Vivek Gupta, Xiaoyu Liu, Chris Fitzgerald, Srinivas
Sreemanthula. My apology if I missed someone. General Comments ============== The original agenda suggested to start addressing 802.21 requirements
for 3GPP during the allocated conference call time. The general feeling from
the group however is to take a stage approach whereby general high level
requirements/principles are outlined first and then detail requirements are
addressed. It was generally agreed that a beefed up/improved version of
contribution 21-05-0300-04-0000 (Proposed 802.21 Presentation for 3GPP) can be
used as the basis for a prospective slide package intended for distribution within
relevant 3GPP groups. Staged Approach ============ The group agreed that a staged approach should be taken towards
introducing 802.21 concepts and requirements for 3GPP. The first step should be a presentation package with high level, albeit
clear and concise concepts and principles. This should include problem
statement and how 802.21 principles can be used in 3GPP in order to provide
solutions to this problem. Subsequent steps will include contribution towards relevant 3GPP groups
where requirement should be placed. Note that within the 802.21 group,
development of detailed requirements should proceed in parallel with the
refinement of the 3GPP presentation package. Furthermore it was generally agreed that off line meetings as well as
submission to the 802.21 reflector should be used in order to continue the
refinement of the 3GPP slide package and definition of 3GPP requirements. Short term Goal (September 26th, 2005) ============================ The goal is to develop a complete slide package that can undergo final
review during that 802.21 September meeting and be ready to be submitted to the
3GPP SA group on the week of September 26, Ultimate Goal ========== The ultimate goal is to develop detail requirements that cab realized
through a dedicated WG within 3GPP. Ideally, the slide package should be
completed during the fist two conference calls. The remaining two conference
calls can be used to initiate the definition of details requirements. Impacted 3GPP groups: ================= It is expected that the following 3GPP groups might be impacted with
802.21 requirements: RAN2 RAN3 SA SA2 GERAN GERAN1 Miscellaneous Comments latest 3GPP Slide Package ======================================= - Remove the
title "Motivation" and leave only "Goals" within slide 3. - Improve/beef up
the "Goals" through submissions to the 802.21 reflector. - Define the
problem statement and how 802.21 solves it - Avoid giving an
impression of "incompleteness" or temporary status when referring to
802.21 principles. State 802.21 principles that are solid and well defined. - Find out
whether other groups might also be impacted. (E.g., GERAN WG4 and CT groups). Nest steps ======== Update slide package according to comments Review slide package during next conference call (August 18th,
9:00-11:00 P.M. EST) Start detail requirement process. Please let me know if I missed something. Thanks for your participation. Ulises |