November 2010
doc.: IEEE 802.19-10/161r0
Resource management for TVWS network coexistence
Date: 2010-11-08
Authors:
Name
Company
Address
Ryo Sawai
Sony
corporation
Sony
corporation
Sony
corporation
Sony China
5-1-12, Kitashinagawa, Shinagawaku, Tokyo, 141-0001, Japan
Ryota Kimura
Naotaka Sato
Guo Xin
Phone
email
[email protected]
[email protected]
Notice: This document has been prepared to assist IEEE 802.19. 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.
Submission
Slide 1
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Introduction
• Proposed IEEE P802.19.1 service models, mechanisms and its
algorithms(*) on output power management for TVWS network
coexistence are highlighted here.
(*) This part is in section 7.3 of proposal text [1]
Submission
Slide 2
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Proposed service models(*)
(*) This part is in section 7.3.1 of proposal text [1]
• Service model #1: Dynamic frequency channel allocation service
• Service model #2: RAT (Radio Access Technology) selection service
• Service model #3: Wireless network coverage extension service
• Service model #4: Multi-channel operation service
• Service model #5: Resource sharing support service
Submission
Slide 3
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Overall procedure of proposed method (*)
(*) The part is in section 7.3.2.1 of reference [1]
Figure 7.17
•Step 1:
Network coexistence service
Process start
Step 1
Required information collection
Step 2
Estimation of network
configuration
Yes
Request of
service model #3
or service model #4 ?
No
Step 3
Problem estimation
Step 4
Solution analysis
Step 5
Network reconfiguration
parameter selection
for network coexistence
Step 6
Network reconfiguration request
for each network to be
reconfigured
Network coexistence service
Process end
Required information to conduct TVWS network coexistence service for TVDBs is collected in this step. Required
information from the master TVBD(s) are listed as follows:
 Operable TVWS frequency channel list
 Network configuration parameters
•Step 2:
Network configuration estimation using the information from each TVWS network is conducted in this step. The
processing for service model #3 and #4 skips in the step 6 directly from the step 2. On the other hand, the service
model#1, #2 and #5 operation proceed next step.
•Step 3:
Problem estimation, which occurs among neighbor TVWS networks, is conducted in this step.
•Step 4:
Solution analysis based on the problem estimation is conducted in this step.
Method #1 based on a policy which is to avoid the occurrence of the TVWS network coexistence as much as
possible without relying on the coexistence network protocol stack of each RAT in the target TVWS networks
Method #2 based on a policy which is to optimize the efficiency of the TVWS frequency reuse
•Step 5:
Network reconfiguration parameter selection for network coexistence or resource sharing management with
synchronization operation support is conducted in this step. The representative network reconfiguration parameter
candidates are given as follows:
 Recommended TVWS frequency channel(s)
 Recommended RAT
•Step 6:
Network reconfiguration is requested for each network in this step.
Submission
Slide 4
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Check points in finding the coexistence solution
Common parts in both method #1(*1) & method #2(*2)
1.
Possibility check of occurrence of harmful mutual interference problem
between multiple networks according to the coexistence network
(*1) This part is in section 7.3.2.2 of proposal text [1 ] . Please refer to Slides 16
categorization (*3)
(*2) This part is in section 7.3.2.2 of proposal text [1 ] . Please refer to Slides 17.
(*3) This part is in section 7.3.2.2 of proposal text [1 ] . Please refer to Slides 11-14
2.
Resource check whether the target network can change from the current
frequency channel to the others
3.
Activation type check of resource management service

4.
Please see next slide
Capability check whether resource sharing and the synchronized
operation is possible via each backbone

Submission
If there is a problem on its latency and capability of the master TVBD(s)
controlled by IEEE P802.19.1 system for the backbone network connection ,
the resource sharing may not work well for the problem to be solved
Slide 5
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Activation types of resource management
• The following two cases should be considered
–
Activated case from the master TVBD (w/ CE) of each TVWS network which detected the
harmful interference from the other network(s) for a target channel
 In this case, it is obvious that the network coexistence problem is in the current
network configuration, so the 19.1 system only have to report the recommended
network reconfiguration parameter(s) to the target TVBDs
–
Activated case due to autonomous detection of IEEE P802.19.1 system for network
coexistence problem, if there is update on TVWS network registered in the system
 In this case, the potential interference is estimated in 19.1 system, and its potential
problem event is reported to the target TVBDs with the recommended network
reconfiguration parameter(s)
Submission
Slide 6
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Check points in finding the coexistence solution
(Additional parts in the method #2(*))
(*) This part is in section 7.3.2.2 of proposal text [1 ] . Please refer to Slides 17.
1. Current RAT usage check
2. Operable RAT(s) capability check
3. Capability check whether the operable RAT supports
effective coexistence protocol to protect each network
from the harmful mutual interference by themselves

Please see the Slide#10 - Slide#13 in Appendix
Coexistence protocol check of each RAT protocol itself
may be largely effect in being increased frequency reuse ratio
in multiple neighbor TVWS networks
Submission
Slide 7
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Conclusions
• Proposed IEEE P802.19.1 service models, mechanisms
and its algorithms on resource management for TVWS
network coexistence were summarized.
Submission
Slide 8
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
References
[1] “19-10-0145-00-0001-coexistence-mechanism-and-its-algorithm”, IEEE mentor,
October 2010
Submission
Slide 9
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Appendix
Coexistence network categorization
Submission
Slide 10
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Example studies on existing RAT on network
coexistence problem (1)
Class #1
TVBD (master) w/ CE function
19.1 system
TVBD (slave)
CDIS/CM
TVWS network #1
TVWS network #2
Master TVBD #2
Master TVBD #1
Multiple neighbor master
TVBDs exist in a range which
can communicate each other
via wireless
Slave TVBD #1
[Feature]
Slave TVBD #2
Different TVWS network coverage areas are overlapped each other
[Example studies on existing RAT on network coexistence problem]
Coexistence beacon mechanism of IEEE 802.22 will effectively work in this situation. On the other hand, if the
network scheduling information exchange function between the master TVBDs with enough clock offset compensation
method between the networks is supported in IEEE 802.11 based TVBD(s), it will also work in this situation. If not,
any packet transmission from its slave TVBD in non-overlapping area, which received the permission from the master
TVBD before that, cannot stop in the network, although the master TVBD can receive the NAV (Network Allocation
Vector) information from the other network(s).
Submission
Slide 11
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Example studies on existing RAT on network
coexistence problem (2)
Class #2
TVBD (master) w/ CE function
19.1 system
TVBD (slave)
CDIS/CM
TVWS network #1
Master TVBD #1
TVWS network #2
Master TVBD #2
Slave TVBD #1
Slave TVBD #2
[Feature]
Slave TVBD #3
Multiple neighbor master
TVBD and slave TVBD
managed by the other master
TVBD exist in a range which
can communicate each other
via wireless
Different TVWS network coverage areas are overlapped each other, but each master TVBD cannot communicate each
other even if the same RAT and the same operation channel are used
[Example studies on existing RAT on network coexistence problem]
Coexistence beacon mechanism of IEEE 802.22 between the master TVBD and the slave TVBD(s) may not effectively
work in this situation, if the two networks are not synchronized each other. On the other hand, if the network
scheduling information exchange function between the master TVBD and the slave TVBD(s) managed by the other
master TVBD with enough clock offset compensation method between the networks is supported in IEEE 802.11
based TVBD(s), it will also work in this situation. If not, any packet transmission from the TVBD(s) in nonoverlapping area cannot stop in the network, although the slave TVBD(s) in the overlapping area can receive the NAV
(Network Allocation Vector) information from the other network(s).
Submission
Slide 12
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Example studies on existing RAT on network
coexistence problem (3)
Class #3
TVBD (master) w/ CE function
19.1 system
TVBD (slave)
CDIS/CM
Multiple networks cannot
communicate each other
via wireless in this case
I secondary (2, f j )
TVWS network #2
TVWS network #1
Interference
Interference
Master TVBD #1
I acceptable (1, f j )
I secondary (1, f j )
Slave TVBD #1
[Feature]
Master TVBD #2
I acceptable (2, f j )
Slave TVBD #3
I
secondary
(1, f j )  I acceptable (1, f j )  & &  I secondary (2, f j )  I acceptable (2, f j ) 
Different TVWS network coverage areas are not overlapped each other as shown in above figure, and each master/slave
node cannot communicate each other even if the same RAT and the same operation channel is used
[Example studies on existing RAT on network coexistence problem]
None
Submission
Slide 13
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Example studies on existing RAT on network
coexistence problem (4)
Class #4
19.1 system
CDIS/CM
TVBD (master) w/ CE function
TVBD (slave)
TVWS network #1
Master TVBD #1
TVWS network #2
All the master TVBDs and
slave TVBDs in different
neighbor networks exist in
a range which can
communicate each other
via wireless
Master TVBD #2
Slave TVBD #1
Slave TVBD #2
[Feature]
Different TVWS network coverage areas are overlaid each other. The term “overlaid” means here that a smaller network coverage area of
TVWS network #2 is totally covered in a wider network area of TVWS network #1.
[Example studies on existing RAT on network coexistence problem]
Coexistence protocol of IEEE 802.22 can effectively work in this situation. Subsequently, the master/slave TVBD(s) in the overlapping
area can receive the NAV (Network Allocation Vector) information from the other network(s), so it can also work in this situation.
However, if the interference power from network #1 to network #2 is in harmful level for the network #2 operation, it may be unable to
operate network#2.
[Specific feature in comparison with the other Class]
The obligation interference management for the primary protection could be shrunk in the master TVBD#1 in this case. On the other hand,
it shall be in master TVBD of each TVWS network in the other classes.
Submission
Slide 14
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Appendix
Resource management procedures
Submission
Slide 15
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Method #1 based on a policy which is to avoid the occurrence of the
TVWS network coexistence as much as possible without relying on
the coexistence network protocol stack of each RAT in the target
TVWS networks
Figure 7.18
Start
Information collection
#0
Estimation of maximum communication radius of
master TVBD(s)
#1
Is (Are) there any overlapping area(s)
in each network coverage area ?
No
Class #3
#2
Yes
Class #1/#2/#4
No
Interference power level is
accepted in each network ?
Class #3b
Yes
#8
The start trigger of this processing
is activated from TVWS network(s) which
detected interference problem?
No
Yes
Service model #1
#3
#5
Operation channel
change request to the
selected common
frequency channel(s)
usage
Operation channel
change request to the
selected different
frequency channel(s)
usage
Yes
#4
Another channel selection is
possible for the networks ?
No
#6
Resource sharing and the
Yes
synchronized operation is
Class #1b(1)/#2b(1)/#3b(1)/#4b(1) possible for each network ?
Service model #5
#7
Resource sharing and its
synchronized operation support
Class
#1b(2)/#2b(2)/#3b(2)/#4b(2)
No solution
End
Submission
No
Slide 16
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Method #2 based on a policy which is to optimize the
efficiency of the TVWS frequency reuse
Figure 7.17
Start
Information collection
#0
Estimation of maximum communication radius of
master TVBD(s)
#1
No
Is (Are) there any overlapping area(s)
in each network coverage area ?
Class #1/#2/#4
Additional parts in comparison
with proposed procedure #2
Class #3
#2
Yes
#8
Class #3a
Yes
Class #3b
#10
No
Common RAT operation is possible
in the target overlapping networks ?
Coexistence protocol of each RAT
will be effectively worked ?
Class #1a/#2a/#4a
Service model #1
Yes
#9
#3
The start trigger of this processing
is activated from TVWS network(s) which
detected interference problem?
No
Yes
#11
Current operation RAT is
No
Interference power level is
accepted in each network ?
Yes
Yes
#4
#5
Operation channel
change request to the
selected common
frequency channel(s)
usage
No
Operation channel
change request to the
selected different
frequency channel(s)
usage
Yes
Another channel selection is
possible for the networks ?
No
#6
the same RAT each other ?
Resource sharing and the
synchronized operation is
Class #1b(1)/#2b(1)/#3b(1)/#4b(1) possible for each network ?
Yes
No
#12 in operable
Coexistence protocol
common RAT(s) will be effectively utilized ?
Class #1a/#2a#4a
Yes
Service model #2
No
Service model #5
Class #1b/#2b/#4b
#7
Resource sharing and its
synchronized operation support
#13
Reconfiguration request to change a selected RAT
operation for the TVBD(s) of the target network
Class
#1b(2)/#2b(2)/#3b(2)/#4b(2)
No solution
End
Submission
No
Slide 17
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Appendix
Service models
Submission
Slide 18
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #1 (1)
Example case of “Dynamic frequency channel allocation”
• This service provides dynamic frequency channel allocation
for multiple neighbour TVWS networks
– Example case
• TVWS network#1 operates in TVWS channel F1 and RAT(Radio Access
Technology) #1 (R1). TVWS network#2 operates in TVWS channel F1 and
RAT#2 (R2). In this case, each TVWS network may cause harmful
interference each other. This situation will occur in actual TVWS network
operation, if multiple master TVBDs individually select own network
configuration. If IEEE P802.19.1 system offers the operation channel change
request for master TVBD of TVWS network and the master TVBD of TVWS
network #2 accepts the request to change the operation frequency channel to
F2, they will be able to operate without harmful interference each other.
Submission
Slide 19
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #1 (2)
Example case of “Dynamic frequency channel allocation”


This decision will need
the RAT protocol
capability check whether
the coexistence protocol
works well in the
situation.
Operable frequency channels
 #F1 and #F2
Before
 TVWS network #1
 Selected frequency channel: #F1
 RAT: #R1
 TVWS network #2
 Selected frequency channel: #F1
 RAT: #R2
Submission


Slide 20
Operable frequency channels
 #F1 and #F2
After service model #1 operation
 TVWS network #1
 Selected frequency channel: #F1
 RAT: #R1
 TVWS network #2
 Selected frequency channel: #F2
 RAT: #R2
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #2 (1)
Example case of “RAT selection support”
• This service provides RAT selection support for
multiple neighbour TVWS networks
– Example case
• Each TVWS network may cause harmful interference each other. This
situation will occur in actual TVWS network operation, if multiple
master TVBDs individually select own network configuration. In this
case, if IEEE P802.19.1 system offers the operation RAT change
request, and if the master TVBD of TVWS network #1 accepts the
request to change the operation RAT to R2, they will be able to
operate without harmful interference each other, if the information
exchange between the networks is possible using each RAT. This
decision will need the RAT protocol capability check whether the
coexistence protocol works well in the situation.
Submission
Slide 21
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #2 (2)
Example case of “RAT selection support”
TVBD (master) w/ CE function
TVBD (master) w/ CE function
19.1 system
19.1 system
Operable channels: F1
Operable channels: F1
TVBD (slave)
TVBD (slave)
CDIS/CM
CDIS/CM
TVWS network #1
Frequency channel: F1
Radio access technology:
R1(R1,R2)
TVWS network #1
Frequency channel: F1
Radio access technology:
R2(R1,R2)
TVWS network #2
Frequency channel: F1
Radio access technology: R2
Interference !


This decision will need
the RAT protocol
capability check whether
the coexistence protocol
works well in the
situation.

Operable frequency channel
 #F1

Before
 TVWS network #1
 Selected frequency channel: #F1
 Selected RAT: #R1 (R1&R2 dual mode)
 TVWS network #2
 Selected frequency channel: #F1
 Selected RAT: #R2
Submission
Slide 22
Network coordination
via R2 protocol
TVWS network #2
Frequency channel: F1
Radio access technology: R2
Operable frequency channel
 #F1
After service model #2 operation
 TVWS network #1
 Selected frequency channel: #F1
 Selected RAT: #R2 (R1&R2 dual mode)
 TVWS network #2
 Selected frequency channel: #F1
 Selected RAT: #R2
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #3 (1)
Example case of “Wireless network coverage extension support”
• This service provides wireless network coverage
extension support for multiple neighbour TVWS
networks
– Example case
• TVWS network#1 operates in F1 and R2. TVWS network#2 operates
in TVWS channel F2 and R1, although this network can operate using
the different RAT (R2). In this case, each TVWS network cannot
communicate each other via wireless link. In this case, if a master
TVBD requests the wireless network connection with its neighbour
network, and if IEEE P802.19.1 system can support to connect each
network via wireless communication, they will be able to
communicate each other via wireless link. This service model may be
useful in a case where the fixed internet access speed is so slow, but
the application needs low latency connection.
Submission
Slide 23
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #3 (2)
Example case of “Wireless network coverage extension support”
TVBD (master) w/ CE function
TVBD (master) w/ CE function
19.1 system
19.1 system
Operable channels: F1 and F2
Operable channels: F1 and F2
TVBD (slave)
TVBD (slave)
CDIS/CM
CDIS/CM
TVWS network #1
Frequency channel: F1
Radio access technology: R2


TVWS network #1
Frequency channel: F1
Radio access technology: R2
TVWS network #2
Frequency channel: F2
Radio access technology: R1(R1,R2)
TVWS network #2
Frequency channel: F1
Radio access technology: R2(R1,R2
This decision will need
the RAT protocol
capability check whether
the coexistence protocol
works well in the
situation.

Operable frequency channels
 #F1 and #F2

Before
 TVWS network #1
 Selected frequency channel: #F1
 Selected RAT: #R2
 TVWS network #2
 Selected frequency channel: #F1
 Selected RAT: #R1(R1&R2 dual mode)
Submission
Slide 24
Operable frequency channels
 #F1 and #F2
After service model #3 operation
 TVWS network #1
 Selected frequency channel: #F1
 Selected RAT: #R2
 TVWS network #2
 Selected frequency channel: #F1
 Selected RAT: #R2 (R1&R2 dual mode)
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #4 (1)
Example case of “Multi-channel operation support”
• This service provides multi-channel operation support
for multiple neighbour TVWS networks
– Example case
• TVWS network#1 operates in F1 and R1. TVWS network#2 operates
in TVWS channel F2 and R2. In this case, if the TVWS network wants
to expand the operation bandwidth, the master/slave TVBD may need
a large overhead to find operable clean frequency channel. In this case,
if a master TVBD requests multi-channel selection support for IEEE
P802.19.1, IEEE P802.19.1 system may be able to inform the
additional operation channel(s), whose aggregated interference level is
small, for the client master TVBD(s).
Submission
Slide 25
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #4 (2)
Example case of “Multi-channel operation support”
TVBD (master) w/ CE function
TVBD (master) w/ CE function
19.1 system
19.1 system
Operable channels: F1, F2 and F3
Operable channels: F1, F2 and F3
TVBD (slave)
TVBD (slave)
CDIS/CM
TVWS network #1
Frequency channel: F1
Radio access technology: R1
CDIS/CM
TVWS network #1
Frequency channel: F1+F2
Radio access technology: R1
TVWS network #2
Frequency channel: F2
Radio access technology: R2
TVWS network #2
Frequency channel: F3
Radio access technology: R2
If the TVWS network #1
expects contiguous
channels


Operable frequency channels
 #F1, #F2 and #F3
Before
 TVWS network #1
 Selected frequency channel: #F1
 Selected RAT: #R1
 TVWS network #2
 Selected frequency channel: #F2
 Selected RAT: #R2
Submission


Slide 26
Operable frequency channels
 #F1, #F2 and #F3
After service model #4 operation
 TVWS network #1
 Selected frequency channel: #(F1+F2)
 Selected RAT: #R1
 TVWS network #2
 Selected frequency channel: #F3
 Selected RAT: #R2
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #5 (1)
Example case of “Resource sharing support”
• This service provides resources sharing operation support
for multiple neighbour TVWS networks.
– Example case
• TVWS network#1 operates in F1 and R1. TVWS network#2 want to operate
using R2, but this case cannot find any operable frequency channel because of
the harmful interference from the TVWS network#1. In this case, if IEEE
P802.19.1 system supports the both time synchronized operation and the
time/frequency resource sharing to each master TVBD, each network will be
able to coexist in F1 even if each network will operate in different RATs. This
service model can be also adopted for the other network configuration as
shown in the other network topology.
Submission
Slide 27
Ryo SAWAI, Sony Corporation
November 2010
doc.: IEEE 802.19-10/161r0
Service model #5 (2)
Example case of “Resource sharing support”
TVBD (master) w/ CE function
19.1 system
19.1 system
Operable channels: F1
Operable channels: F1
TVBD (slave)
CDIS/CM
CDIS/CM
TVBD (master) w/ CE function
TVWS network #1
Frequency channel: F1
Radio access technology: R1
TVWS network #1
Frequency channel: F1
Radio access technology: R1
TVWS network #2
Frequency channel: none
Radio access technology: R2


This decision will need a
check(*1) whether
resource sharing and
synchronized operation
is possible via backbone
network for each TVWS
network
Operable frequency channels
 #F1
Before
 TVWS network #1
 Selected frequency channel: #F1
 Selected RAT: #R1
 TVWS network #2
 Selected frequency channel: none
 Selected RAT: #R2
Submission
(*1) Please see the other issues in footnote #23 of reference [1]


Slide 28
TVBD (slave)
TVWS network #2
Frequency channel: F1
Radio access technology: R2
Operable frequency channels
 #F1
After service model #5 operation
 TVWS network #1
 Selected frequency channel: #F1
 Selected RAT: #R1
 TVWS network #2
 Selected frequency channel: #F1
 Selected RAT: #R2
Ryo SAWAI, Sony Corporation