1. FBMS Termination Date: 2007-1-15 Name Compay Address Phone E-mail
Jiyoung Huh
LG Electronics
Donghee Shim
Yongho Seok
Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Jiyoung et al.

2. Abstract
This document proposes the efficient FBMS termination mechanism for both non-AP STA and AP
The first part is to provide the FBMS update or termination capability of a non-AP STA for a specific FBMS service
The second part is to provide the FBMS termination capability of an AP STA
At the end of the presentation, there will be a motion to include normative text of this proposal in v draft.
Jiyoung et al.

3. Current FBMS mechanism
FBMS Element termination by non-AP STA
A non-AP STA may transmit a FBMS Request frame without the FBMS Element contained in it.
The existing FBMS operation (update and termination from a non AP STA) seems to be inefficient as follows:
Non-AP STA shall transmit FBMS Request including all FBMS Elements to update just one FBMS Element
Non-AP STA shall transmit FBMS Request including all FBMS Elements except particular FBMS Element to terminate that FBMS Element.
There is no FBMS termination mechanism from AP STA
There is a possibility that an AP STA continues to provide a FBMS service for disconnected or moved non-AP STAs (since non-AP STAs disconnected or moved without any specific termination of FMBS elements.
Jiyoung et al.

4. FBMS termination by non-AP STA
Non-AP STA indicates that it is not using FBMS Element any more by setting delivery interval of specific FBMS Element to 0.
Non-AP STAs can send FBMS Request including only particular FBMS Element in order to update or terminate that FBMS Element.
<Scenario>
1. STA1 uses 4 FBMS Elements.
2. STA1 updates 1 FBMS Element.
3. STA1 terminates 1 FBMS Element.
STA1 AP
2. FBMS Request Message with all 4 FBMS Elements
3. FBMS Request Message with all FBMS Elements except terminating FBMS Element
FBMS Response Message
STA1 AP
2. FBMS Request Message with only updating FBMS Element
3. FBMS Request Message with only terminating FBMS Element
FBMS Response Message
<The exsiting termination>
<The proposed termination>
Jiyoung et al.

5. FBMS termination by AP STA
AP STA indicates that it would not provide particular FBMS service for that FBMS group members by sending unsolicited FBMS response with “Terminate” status and the corresponding reason code.
Value
Description 1
Accept 2
Deny 3
Override 4
Terminate
5-255
Reserved
Field Value
Description … 9
Terminated due to AP policy change 10
Terminated in order to support other services with priority 11
Terminated due to lack of network resources
12-255
Reserved
< Element Status Definition>
< Element Reason Code>
Jiyoung et al.

6. FBMS Stream Duration
FBMS Status Element in FBMS Response Element includes the Duration field in order to inform the FBMS Element service period of non-AP STAs.
Non-AP STAs shall update the FBMS Element service period by sending FBMS Request before the Duration is expired.
<Scenario>
AP provides FBMS service for STA1,2,3, and 4 in the same Multicast Group.
1. STA1, which supports the lowest multicast rate, became disconnected.
 Other STAs except STA1 send FBMS Request to update the service period before the duration is expired.
 After that, AP considers STA1 was out of FBMS service with a FBMS ID
AP can update the multicast rate for three remaining STAs with a FBMS ID.
2. All Stations become disconnected.
 No STAs send FBMS Request to update the service period before the duration is expired
 AP can release a FBMS ID and Counter
Jiyoung et al.

7. Conclusion
This document proposes the efficient FBMS termination mechanism for both non-AP STA and AP
Jiyoung et al.

8. Motion
Move to include normative text in document v-normative-text-fbms-termination.doc into the TGv draft.
Mover:
Seconder:
Result:
Jiyoung et al.