C802.16gman-10/0057

Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Proposed text for 802.16n System Architecture Reference Model
Date
Submitted
2010-11-05
Source(s)
Eldad Zeira
Eldad.zeira@interdigital.com
InterDigital Communications LLC
Re:
CfC for 802.16n SARM
Abstract
This document proposes text for the 802.16n SARM.
Purpose
To be discussed and decided by GRIDMAN.
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.
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>.
Patent
Policy



C802.16gman-10/0057
Proposed text for 802.16n System Architecture
Reference Model
Eldad Zeira, InterDigital

Discussion
In session #69 in St. Petersburg GRIDMAN has discussed the contents of the 802.16n SARM.
The following content has been agreed (see 80216gman-10_0039r1):
•
•
•
•
•
•
Overall Network architecture model(s) – describing network entities and their links for
e.g.
– MS-MS communications
– Relays
System reference model
Protocol structure e.g. for
– MS-MS communications
– Security
Operational states (if different from current 802.16)
Specific for 2009+802.16j / 802.16m
Specific for feature(s)
This document proposes SARM text for these items.
>>>>>>>>> Proposed Text <<<<<<<<<<<


C802.16gman-10/0057
1 Network reference model
1.1
Over-all Network reference model
The Network Reference Model (NRM) is a logical representation of the network architecture. The NRM
identifies functional entities and reference points over which interoperability is achieved between
functional entities. Error! Reference source not found. illustrates the NRM of HR-Network , consisting
of the following functional entities:
-
Mobile Station (MS) which signifies 802.16m or WirelessMAN-OFDMA compatible subscriber
station
-
HR-MS, HR-RS and HR-BS which are compatible with 802.16n requirements
MS
R1
1
MS
RS
R1
R1
2
MS?
R1'
3
MS?
R1'
4
MS?
HR-MS
HR-BS
operating
as RS
HR-MS
operating
as RS
HR-MS
operating
5 as RS
R1'
R10
R1'
R1'
HR-BS
Backhaul
R1'
HR-RS
R1'
R1
HR-MS
6
HR-MS
HR-MS
R11
7
HR-MS
HR-MS
R11
R11
HR-MS
8

Figure 1: HR-Network Reference Model; Numbers in magenta are referenced in the text
Legend:
R1 refers to "legacy" interface which could be either WirelessMAN-OFDMA (2009) including 802.16j or
802.16m.
Line 5 requires a multi-hop relay. This may change the nature of the interface so it is not strictly R1. Line 5
interfaces are denoted R1’. The support of R1’ for legacy MS is FFS.
Lines 3 & 4 should be same interfaces as line 5.
Line 6 defines a new interface between HR-MS, denoted R10. It is based on HR-MS with limited relaying
functionality. R10 cannot serve legacy MS. The interface between the HR-MS in line 6 and the HR-BS is
legacy.
Lines 7 and 8 represent a new interface, denoted R11, required for HR-MS to HR-MS direct
communications in the absence of infrastructure (single and dual hop cases).


C802.16gman-10/0057
Note that R1’, R10 and R11 should be as close to R1 as possible while fulfilling 802.16n requirements.
1.2
Interoperability table for Multi-mode operation
The HR-Network supports role changes of some network entities to support recovery from network entity
or backhaul failure. Table 1 summarizes the role changes and resulting connectivity.
Table 1: Interoperability Table
e-HR-MS
m-HR-MS
e-HR-MS
m-HR-MS
e-HR-BS
m-HR-BS
New
Roles
Relay
Relay
BS
N/A
Relay
Relay
-
AAI
m-HR-BS
OFDMA
-
e-HR-BS
-
AAI
m-BS
AAI
OFDMA
AAI
OFDMA
OFDMA
(multihop)
OFDMA
OFDMA
(multihop)
OFDMA
OFDMA
e-BS
-
m-HR-RS
OFDMA
(multihop)
e-HR-RS
-
m-RS
OFDMA
(multihop)
e-RS
AAI
OFDMA
OFDMA
OFDMA
AAI
OFDMA
OFDMA
Connected
to…
Original
entities
OFDMA
AAI
m-HR-MS
-
e-HR-MS
AAI
m-MS
e-MS
Legend:
-
OFDMA is shorthand for WirelessMAN-OFDMA (2009) + 802.16j
-
AAI stands for 802.16m
-
An e-HR-xS or m-HR-xS stand for HR-xS node (where xS could be MS, BS or RS) that are based
on WirelessMAN-OFDMA or AAI respectively.


C802.16gman-10/0057
2 IEEE 802.16n System Reference Model
2.1
Multi-mode operation
This section shows the system reference model for HR-BS and HR-MS role changes. An example is given
in Figure 2. The Role Change Management block communicates with other network nodes. It interfaces
with the MAC to request and receive reports of various measurements. Finally it causes the switching of
functionality as specified in the SRD e.g. between HR-MS to HR-RS.
CS SAP
CS SAP
HR-MS Functionality
HR-RS Functionality
Message interface
Management Entity
Service
Specific Entity
Management
Radio Resource
Convergence
Sublayer
Service
Specific
Control
Radio Resource Convergence
andControl
Convergence Sublayer
Sublayer
Convergence
MAC SAP
Sublayer
Management
and
Functions
Management
Functions
MAC SAP
Management Layer
Medium Access Control Functions
Medium Access Control Functions
Security Sublayer
PHY
SAP Sublayer
Security
SAP
PhysicalPHY
Layer
(PHY)
Physical Layer
Management
Common
Part Layer
Management
Sublayer
Common Part
Sublayer
Security Sublayer
MAC
Interface
Security Sublayer
Management Entity
Physical
Layer Entity
Management
(PHY)
Physical Layer
Role Change Management
(RCM)
MAC Common-Part Sublayer
MAC Common-Part Sublayer
Functionality switching mechanism
Figure 2 : System reference model for HR-MS and HR-BS role change
2.2
System reference model for other modes
The System reference model for modes other than multi-mode devices is unchanged from 802.16m system
reference model.


C802.16gman-10/0057
3 HR-MS State Diagrams
3.1
States of HR-MS
Figure 3 depicts the states of an HR-MS. Note the distinct separate states of HR-MS that HR-MS enters
depending if it is associated with an infrastructure node (BS or relay), with another HR-MS without
presence of infrastructure (direct MS-MS) or to infrastructure through a forwarding HR-MS.
Note that direct MS-MS mode does not include Access or Idle states. The former is provided by the HRMS forwarding mode while the other isn't necessary for this mode.
Power
On / Off
Connected
HR-MS to HR-MS (no BS)
Intitialization
Access
HR-MS Forwarding
Access
Fallback
Connected
Idle
Fallback
Connected
Idle
Infrastructure
Fallback
Figure 3: States of an HR-MS
3.2
Initialization State
Figure 4 depicts the initialization stage for an HR-MS. During this stage the HR-MS first attempts to find a
BS or relay in the normal manner (i.e. same as baseline). If one is found, the HR-MS proceeds to the
corresponding access state for the baseline interface.
If none is found, the HR-MS attempts to find another HR-MS to forward its data and proceeds to access
state with that neighbor.


C802.16gman-10/0057
Power On/
Off
Initialization State
Infrastructure
node discovery
From Access, Connected or Idle States
Found?
To access state – Infrastructure node
Neighbor HRMS discovery
To access state – HR-MS forwarding
Found?
Figure 4 : Initialization State
3.3
Access States
Access states are depicted in Figure 5.
Access state with infrastructure nodes is identical to the corresponding legacy mode (WirelessMANOFDMA (2009) or AAI).
Access state to HR-MS connected mode includes:
-
Basic access to an HR-MS found in the initialization state.
-
Network information exchange
-
If the network does not include a BS then HR-MS switches to connected state for MS-MS direct
communication (no BS).
-
Otherwise a link to infrastructure node is established through the forwarding HR-MS.


C802.16gman-10/0057
Access State
From Initialization
State or Idle State
Basic access to forwarding
HR-MS
Network information
exchange
Is BS Present?
N
To Connected –
direct MS-MS
Set up initial link to BS
1) Capability negotiations
2) AMS Authentication,
Authorization, & Key
Exchange
3) Registration with HR-BS
4) Initial service flow
Establishment
To Connected - HRMS forwarding
Figure 5: Access State Procedures for non-infrastructure modes
3.4
Connected States
Connected states for infrastructure and HR-MS forwarding modes are identical to legacy.
There is no connected state for direct communication mode.
3.5
Idle States
Idle states for infrastructure and HR-MS forwarding modes are identical to legacy.
There is no idle state for direct communication mode.
4 IEEE 802.16n High Reliability Network Protocol Structure
4.1
Multi-mode operation
HR-Network stations protocol structure is identical to the baseline protocol.
4.2
MS-MS direct communication and HR-MS forwarding protocol structure
FFS.

