Re: [STDS-802-16-MOBILE] [Harmonization] MBS Harmonization
Dear Yong Chang and All,
Hi. I'm Kang il Koh from SKTelecom.
As Dongkie stated below, I also think that the MBS Information Acquisition should
be described more clearly. We had written out a fairly simple contribution concerning
the matter. It's uploaded on the server(H80216e-04_11.doc)
Also, I've uploaded H80216e-04_12.doc. This contribution is taking into account the case
where MSS moves out from the MBS zone but still wants the MBS contents to be delivered
Please take a look at these two contributions.
I'd be glad to discuss with the Ad-hoc on these matters.
Kang il Koh
From: owner-stds-802-16-mobile@LISTSERV.IEEE.ORG [mailto:owner-stds-802-16-mobile@LISTSERV.IEEE.ORG]On Behalf Of galahad
Sent: Wednesday, August 11, 2004 9:36 PM
Subject: Re: [STDS-802-16-MOBILE] [Harmonization] MBS Harmonization
Some comments on the MBS contribution follows(Same text is put in
1. MBS for Sleep Mode
On page 5 (3) MBS_MAP Information Element, Runcom's comment mentions about
MBS service in sleep mode. But Samsung's proposed text only mentions about
idle mode. I'd say MBS service shall be supported in any mode including
sleep mode also.
2. Content Server Acquisition Method
On page 3 MBS Information Acquisition section, how the MSS acquires MBS
content server's IP address is not known. Maybe it's out of scope or maybe
not depending how to do it. If it's address is in the MSS in static manner,
it's out of scope. But if it's address or FQDN is broadcasted via MAC
message, it should be discussed in our TG.
3. Multicast IP Addr/Port in DSX-REQ
On page 3 second figure, DSA-REQ forwards multicast IP addr and port to BS.
I guess multicast IP addr and port should be newly added to the DSX-REQ MAC
message encodings or it utilize IP destination address and Protocol source
port range field. But I prefer the former.
4. Mapping between Muticast IP Addr/Port and Multicast CID
How does the MSS maps Multicast IP Addr/Port to Multicast CID or Broadcast
CID? Is the mapping information comes with the DSA-RSP? If it's true, that
mapping information needs to be coordinated between BS and MBS server. Or by
5. Broadcast versus Multicast
How does the MSS differentiate between broadcast and multicast? Is it purely
depends on CID value range? If it's true, then when MSS gets information
with HTTP Response(MBS Contents List), that means MSS cannot recognize
which content is for broadcast or multicast?
6. MBS Zone Concept
As the author says, " A BS may concurrently support multiple MBS Zones, but
only one MBS zone identifier for one broadcast and multicast service shall
be used in a BS". Like Paging group, one MBS zone might have some geographic
service area and if that multiple MBS zone's geographic service area are not
the same. How does the MSS know the boundary with different value of the
same MBS zone? So I guess MBS zone should be kind of Paging Zone concept.
With that concept, in the same MBS zone area, as the Samsung says, MBS
related parameter does not change. But I think MBS Zone ID should be
advertised in e.g. NBR-ADV.
7. MBS Accounting
Not only MBS Accounting but also 802.16e Accounting is not defined yet.
Where can we discuss and define accounting procedure? In TGg? As with the
802.1X accounting, in 802.16e Accounting has to be defined ASAP from the
operator's perspective. Whether we submit MBS framework to Tge and MBS
accounting to TGg, I'd like to define MBS accounting with Samsung's
contribution at the same time.
----- Original Message -----
From: "Yong Chang" <yongchang@SAMSUNG.COM>
Sent: Wednesday, August 11, 2004 4:44 PM
Subject: [STDS-802-16-MOBILE] [Harmonization] MBS Harmonization
> I have uploaded the initial draft for MBS Harmonization on the upload
> I showed in this draft how many comments on MBS were given.
> For conference call of MBS only, what I heard from the chair of
> Harmonization is that
> Time: August 5(Thursday), 3:30 PM (PST)
> Bridge Information: Chair will give information ASAP.
> If anyone have a contribution with MBS, then please upload it on the
> before the meeting.
> Yong Chang/Ph.D
> Samsung Electronics, LTD