IEEE P802 Media Independent Handover Services

Media Independent Handover Services
Meeting Minutes of the IEEE P802.21 Broadcast Handovers Study Group
Chair: Burak Simsek
Secretary: Juan Carlos Zuniga
River Terrace 1: Thursday EST, May 15th, 2008
 Meeting called to order by Burak Simsek, Chair of IEEE 802.21 Broadcast
Handovers Study Group Chair at 08:00AM
 Meeting Agenda
 Kick off speech from Burak Simsek
 Presentation on PSI/SI Tables of DVB for handovers to DVB
 Discussion on the expectations from the study group
 Chair: Any comments or objections for the agenda?
 No response from the floor.
 Burak Simsek: There has been a tremendous support from nearly all the participants.
Therefore many thanks to all of you. Initially the target was directly building a task group
based on the recommendation of Vivek. Although this was possible, due to the need for
synchronization with the DVB technical module and the extension of the initial topic,
which was handovers with DVB, to handovers with broadcasting technologies we had to
build the study group. A successful outcome is only then possible if you and your
colleagues representing different broadcast technologies support us in the future.
 Presentation on PSI/SI tables: Document:
 Discussion:
 Farrokh: is there always an uplink channel?
 Burak: we will assume first that there is none, and second that there will be one.
First one will give a generic look at the differences of broadcast technologies and
the second one reflects the real implementations of DVB.
 Farrokh: Is there a way to identify the user?
 Burak: Basically, multicast/broadcast services cannot identify individual users.
Therefore it is also not possible to talk to only one user directly using multicast
addressing. Normally we would use IP addresses to identify a person or sometimes
MAC addresses. This is not the same for broadcast technologies. Nevertheless,
IPDatacast also makes communicating with individuals possible. Or we are
dealing with all the receivers of a service. So IP represents a service instead of
persons. Uplink address could be the one from the return channel
 Junghoon: Is IP Multicast Leave an IGMP?
 B: No
 Farrokh: how do we determine the address of a stream?
 Burak: Once the IP packet is encapsulated, the PID will become the destination
address. PID “could” change when services are reconfigured.
 Farrokh: I believe that we really need an uplink channel to perform handover.
 Junghoon: Can MIH exist only in X Network and not in DVB network?
 B: There should be no restriction in 802.21
 Burak: Should we define a generic interface or not? (E.g. DVB, MediaFLO, DMB).
Can we have contributions from MediaFLO and DMB?
 Farrokh: We should first answer the question with DVB in mind: can we work
with a FLO scenario (no return channel)?
 Junghoon: Let’s define the scope in this group and leave the generic/specific
interface for the TG phase
 Les: We should do the same as we’ve done for non-broadcast technologies.
Namely, a generic interface and afterwards link specifications…
 The proposal of Les was acceptable also for the others.
 Vivek: You can also prepare more than one PAR.
 Burak: OK. Then this will be our approach in case needed.
 Vivek: Did you arrange the person who will present the tutorial for DVB?
 Burak: I will do it. We should talk on the details of the tutorial.
 Farrokh: There should be some time reserved also for other technologies.
 Burak: Then I will have to find someone other than Prof. Reimers (chair of DVB
technical module). And if this is a person from DVB he won’t be willing to tell
much on other technologies.
 Junghoon, Farrokh, Les, Vivek, Juan Carlos: We can have from each technology
one person. They can prepare slides using the structure of DVB slides.
 Burak: OK. Then I have to be able to determine the slides. In case I am allowed to
combine them in order to make sure that nothing is wrong with the tutorial, this is
not a problem. Then we will prepare a generic broadcasting approach, afterwards
mention about DVB, MediaFLO, DMB and MBMS… For each technology
corresponding tutor will be responsible.
Chan, Anthony
Cheng, Yuu Heng
Cypher, David
Das, Subir
Eastwood, Lester
Han, James Jia
Henderson, Gregory
Jee, Junghoon
Khatibi, Farrokh
Mani, Mahalingam
Ohba, Yoshihiro
Park, Changmin
Sarikaya, Behcet
Simsek, Burak
Singh, Shubhranshu
Suciu, Lucian
Tachikawa, Hitoya
Williams, Michael
Zuniga, Juan
Huawei Technologies
Telcordia Technologies Inc.
Motorola Inc.
Motorola Inc
Research In Motion Ltd.
Avaya Inc.
ETRI - Electronics and Telecommunications Research
Huawei Technologies, USA
Fraunhofer Institute
Samsung Electronics
Orange LAbs
Kyocera Corporation
Nokia Corporation
InterDigital Communications, LLC