Standalone Operation for Direct Communication
IEEE 802.16 Presentation Submission Template (Rev. 9)
Document Number:
IEEE C802.16n-11/0059
Date Submitted:
2011-03-13
Source:
Sungcheol Chang, Eunkyung Kim, Sungkyung Kim, Hyun Lee, Chulsik Yoon
ETRI
E-mail: scchang@etri.re.kr ,
ekkim@etri.re.kr
Venue:
Call for contributions for 802.16n AWD
Base Contribution:
None
Purpose:
To be discussed and adopted by TG802.16n
Notice:
This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It represents only the views of the participants listed in
the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who 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 802.16.
Patent Policy:
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
<http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>.
Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and <http://standards.ieee.org/board/pat >.
Introduction
• Dedicated resources for direct communication
– Related contributions of C802.16n-10/0051 and 10/0052.
• Channel structure and Signaling Procedures
–
–
–
–
–
–
Related contributions of C802.16n-10/0053 and 10/0054
Channel Structure of Direct Communication
Tx and Rx configuration
Unicast and Multicast transmission
Basic Signaling Procedures
Two Hop Operation
Motivation
• How to provide standalone operation using only MAC
layer connectivity without network connection?
– It’s an extension of direct communication between MSs using
BS transmission capability with BS service coverage because
MS interaction to network is not allowed.
Standalone Procedure: Transmission
• No backhaul connectivity
• Only MAC connectivity
between MSs within BS
coverage.
– BS forwards traffic data
between a pair of two MAC
connections.
– BS forwards traffic data from
an MS to the other MS.
Backbone Network
Local
Forwarding
Standalone Procedure: Signaling
• When the backbone connectivity is not available, the
BS triggers and configures standalone function
– To notify MSs of backbone connection disruption and
configuration of standalone operations including local
forwarding function.
• Deactivating infrastructure operation.
• Configuring and Activating local forwarding connectivity.
– Detail parameters depend on local forwarding connectivity.
– (1:1) Backbone Disable Request / Response (BBD-REQ/RSP)
Backbone Network
– (1:N) Backbone Disable Command (BBD-CMD)
Local
Forwarding
CM
D
BB
D-
3
D
CM
BB
D
BB -R
D- E Q
RS
P
4
DBB
2
P
RS
D- Q
BB -RE
D
BB
1
Backbone Network
Local
Forwarding
Standalone Procedure: Signaling
• When the backbone connectivity is available, the BS
goes infrastructure operation back.
– To notify MSs of the availability of backbone connectivity.
• Activating infrastructure operation.
• Controlling local forwarding connectivity.
– (1:1) Backbone Enable Request / Response (BBE-REQ/RSP)
– (1:N) Backbone Enable Command (BBE-CMD)
Backbone Network
Local
Forwarding
BB
E-
2
D
CM
P
RS
E- Q
BB -RE
E
BB
BB
E
BB -RE
E- Q
RS
P
4
3
EBB
1
CM
D
Backbone Network
Local
Forwarding
Proposed text for 16n AWD
• It will be updated.
Conclusion
• Only MAC connectivity between MSs within BS
coverage.
– Local forwarding function at the BS.
• Related signaling
– Relating to Notification of backbone unavailability
and configuration of local forwarding function.