Doc.: IEEE 802.19-10/161r0 SubmissionSlide 1 Resource management for TVWS network coexistence Notice: This document has been prepared to assist IEEE 802.19.

doc.: IEEE 802.19-10/161r0

Submission Slide 1

Resource management for TVWS network coexistence

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.

Date: 2010-11-08Authors:

Name Company Address Phone email

Ryo Sawai Sony corporation

5-1-12, Kitashinagawa, Shinagawa-ku, Tokyo, 141-0001, Japan

[email protected]

Ryota Kimura Sony corporation

Naotaka Sato Sony corporation

[email protected]

Guo Xin Sony China

Ryo SAWAI, Sony Corporation

November 2010

doc.: IEEE 802.19-10/161r0

Submission

Introduction

• Proposed IEEE P802.19.1 service models, mechanisms and its algorithms(*) on output power management for TVWS network coexistence are highlighted here.

November 2010

Ryo SAWAI, Sony CorporationSlide 2

(*) This part is in section 7.3 of proposal text [1]

doc.: IEEE 802.19-10/161r0

Submission

Proposed service models(*)

November 2010


Slide 3

• 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

(*) This part is in section 7.3.1 of proposal text [1]

doc.: IEEE 802.19-10/161r0

Submission

Overall procedure of proposed method (*)

November 2010


Slide 4

Step 1Required information collection

Network coexistence serviceProcess start

Step 2Estimation of network

configuration

Step 3Problem estimation

Step 4Solution analysis

Step 5Network reconfiguration

parameter selection for network coexistence

Step 6Network reconfiguration request

for each network to be reconfigured

Network coexistence serviceProcess end

Request of service model #3

or service model #4 ?

No

Yes

•Step 1: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 networksMethod #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.

Figure 7.17 (*) The part is in section 7.3.2.1 of reference [1]

doc.: IEEE 802.19-10/161r0

Submission

Check points in finding the coexistence solutionCommon 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 categorization (*3)

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 Please see next slide

4. Capability check whether resource sharing and the synchronized operation is possible via each backbone

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

November 2010


Slide 5

(*1) This part is in section 7.3.2.2 of proposal text [1 ] . Please refer to Slides 16

(*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

doc.: IEEE 802.19-10/161r0

Submission

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)

November 2010


Slide 6

doc.: IEEE 802.19-10/161r0

Submission

Check points in finding the coexistence solution(Additional parts in the method #2(*))

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

November 2010


Slide 7

Coexistence protocol check of each RAT protocol itself may be largely effect in being increased frequency reuse ratio in multiple neighbor TVWS networks

(*) This part is in section 7.3.2.2 of proposal text [1 ] . Please refer to Slides 17.

doc.: IEEE 802.19-10/161r0

Submission

Conclusions

• Proposed IEEE P802.19.1 service models, mechanisms and its algorithms on resource management for TVWS network coexistence were summarized.

November 2010

Ryo SAWAI, Sony CorporationSlide 8

doc.: IEEE 802.19-10/161r0

Submission

References


Slide 9

[1] “19-10-0145-00-0001-coexistence-mechanism-and-its-algorithm”, IEEE mentor, October 2010

November 2010

doc.: IEEE 802.19-10/161r0

Submission

AppendixCoexistence network categorization

November 2010


Slide 10

doc.: IEEE 802.19-10/161r0

Submission

Example studies on existing RAT on network coexistence problem (1)

Class #1

November 2010


Slide 11

19.1 system

TVWS network #1 TVWS network #2

TVBD (slave)

TVBD (master) w/ CE function

CDIS/CM

Slave TVBD #1

Master TVBD #1

Master TVBD #2

Slave TVBD #2[Feature] 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).

Multiple neighbor master TVBDs exist in a range which can communicate each other via wireless

doc.: IEEE 802.19-10/161r0

Submission


Class #2

November 2010


Slide 12

19.1 system

TVWS network #1TVWS network #2

TVBD (slave)


CDIS/CM

Slave TVBD #1

Master TVBD #1

Master TVBD #2

Slave TVBD #2

Slave TVBD #3[Feature] 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 non-overlapping 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).

Multiple neighbor master TVBD and slave TVBD managed by the other master TVBD exist in a range which can communicate each other via wireless

doc.: IEEE 802.19-10/161r0

Submission


Class #3

November 2010


Slide 13

19.1 system

TVWS network #1 TVWS network #2

TVBD (slave)


CDIS/CM

Slave TVBD #1

Master TVBD #1Master TVBD #2

Slave TVBD #3

secondary (2, )jI f

secondary secondary(1, ) (1, ) & & (2, ) (2, )j acceptable j j acceptable jI f I f I f I f

(2, )acceptable jI fsecondary (1, )jI f

(1, )acceptable jI f

[Feature] 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

Multiple networks cannot communicate each other via wireless in this case

doc.: IEEE 802.19-10/161r0

Submission


Class #4

November 2010


Slide 14

19.1 system

TVWS network #1

TVWS network #2

TVBD (slave)


CDIS/CM

Slave TVBD #1

Master TVBD #1

Master TVBD #2

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.

All the master TVBDs and slave TVBDs in different neighbor networks exist in a range which can communicate each other via wireless

doc.: IEEE 802.19-10/161r0

Submission

AppendixResource management procedures

November 2010


Slide 15

doc.: IEEE 802.19-10/161r0

Submission

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

November 2010


Slide 16

No

Estimation of maximum communication radius of master TVBD(s)

Is (Are) there any overlapping area(s) in each network coverage area ?

Yes

Information collection

End

Start

Another channel selection is possible for the networks ?

Yes

Resource sharing and the synchronized operation is possible for each network ?

Yes

No

No

Interference power level is accepted in each network ?

Yes

No

Service model #1

Resource sharing and its synchronized operation support

No solution

Operation channel change request to the

selected common frequency channel(s)

usage


selected different frequency channel(s)

usage

Service model #5

Class #1/#2/#4 Class #3b

Class #1b(1)/#2b(1)/#3b(1)/#4b(1)

Class #1b(2)/#2b(2)/#3b(2)/#4b(2)

Class #3#1

#2

#3

#4

#6

#7

#5

#0

The start trigger of this processing is activated from TVWS network(s) which

detected interference problem?

No

Yes#8

Figure 7.18

doc.: IEEE 802.19-10/161r0

Submission

Method #2 based on a policy which is to optimize the efficiency of the TVWS frequency reuse

November 2010


Slide 17

No

Estimation of maximum communication radius of master TVBD(s)

Is (Are) there any overlapping area(s) in each network coverage area ?

Yes

Information collection

Common RAT operation is possible in the target overlapping networks ?

Yes

Yes

End

Start

Another channel selection is possible for the networks ?Yes

Resource sharing and the synchronized operation is possible for each network ?

Yes

No

No

Interference power level is accepted in each network ?

Yes

No

Service model #1

Resource sharing and its synchronized operation support

No solution


selected common frequency channel(s)

usage


selected different frequency channel(s)

usage

Reconfiguration request to change a selected RAT operation for the TVBD(s) of the target network

Service model #2

Service model #5

Class #1/#2/#4

Class #3a

Class #3b

The start trigger of this processing is activated from TVWS network(s) which

detected interference problem?

No

No

Class #1a/#2a#4aClass #1b/#2b/#4b

Class #1b(1)/#2b(1)/#3b(1)/#4b(1)

Class #1b(2)/#2b(2)/#3b(2)/#4b(2)

Class #3

Coexistence protocol of each RAT will be effectively worked ?

Yes

No

Current operation RAT is the same RAT each other ?

Yes

NoCoexistence protocol in operable

common RAT(s) will be effectively utilized ?

Yes

No

Class #1a/#2a/#4a

#1

#2

#3

#4

#13

#6

#7

#8#10

#9

#11

#12

#5

#0

Additional parts in comparison with proposed procedure #2

Figure 7.17

doc.: IEEE 802.19-10/161r0

Submission

AppendixService models

November 2010


Slide 18

doc.: IEEE 802.19-10/161r0

Submission

Service model #1 (1)Example case of “Dynamic frequency channel allocation”

November 2010


Slide 19

• 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.

doc.: IEEE 802.19-10/161r0

Submission

Service model #1 (2)Example case of “Dynamic frequency channel allocation”

November 2010


Slide 20

Operable frequency channels#F1 and #F2

BeforeTVWS network #1

Selected frequency channel: #F1RAT: #R1

TVWS network #2 Selected frequency channel: #F1RAT: #R2


After service model #1 operationTVWS network #1

Selected frequency channel: #F1RAT: #R1

TVWS network #2 Selected frequency channel: #F2RAT: #R2

This decision will need the RAT protocol capability check whether the coexistence protocol works well in the situation.

doc.: IEEE 802.19-10/161r0

Submission

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.

November 2010


Slide 21

doc.: IEEE 802.19-10/161r0

Submission


Example case of “RAT selection support”

November 2010


Slide 22

19.1 systemOperable channels: F1

TVWS network #1Frequency channel: F1

Radio access technology: R1(R1,R2)


Radio access technology: R2Interference !

TVBD (slave)


CDIS/CM





Radio access technology: R2

TVBD (slave)


CDIS/CM

Network coordination via R2 protocol

This decision will need the RAT protocol capability check whether the coexistence protocol works well in the situation.Operable frequency channel

#F1Before

TVWS network #1Selected frequency channel: #F1Selected RAT: #R1 (R1&R2 dual

mode)TVWS network #2

Selected frequency channel: #F1Selected RAT: #R2

Operable frequency channel#F1


Selected frequency channel: #F1Selected RAT: #R2 (R1&R2 dual

mode)TVWS network #2


doc.: IEEE 802.19-10/161r0

Submission


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.

November 2010


Slide 23

doc.: IEEE 802.19-10/161r0

Submission


Example case of “Wireless network coverage extension support”

November 2010


Slide 24

19.1 systemOperable channels: F1 and F2





TVBD (slave)


CDIS/CM

19.1 systemOperable channels: F1 and F2





TVBD (slave)


CDIS/CM

This decision will need the RAT protocol capability check whether the coexistence protocol works well in the situation.Operable frequency channels

#F1 and #F2Before

TVWS network #1Selected frequency channel: #F1Selected RAT: #R2

TVWS network #2 Selected frequency channel: #F1Selected RAT: #R1(R1&R2 dual mode)




TVWS network #2 Selected frequency channel: #F1Selected RAT: #R2 (R1&R2 dual

mode)

doc.: IEEE 802.19-10/161r0

Submission


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).

November 2010


Slide 25

doc.: IEEE 802.19-10/161r0

Submission


Example case of “Multi-channel operation support”

November 2010


Slide 26

19.1 systemOperable channels: F1, F2 and F3





TVBD (slave)


CDIS/CM

19.1 systemOperable channels: F1, F2 and F3

TVWS network #1Frequency channel: F1+F2




TVBD (slave)


CDIS/CM

Operable frequency channels#F1, #F2 and #F3



TVWS network #2 Selected frequency channel: #F2Selected RAT: #R2

Operable frequency channels#F1, #F2 and #F3


Selected frequency channel: #(F1+F2)Selected RAT: #R1


If the TVWS network #1 expects contiguous channels

doc.: IEEE 802.19-10/161r0

Submission


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.

November 2010


Slide 27

doc.: IEEE 802.19-10/161r0

Submission


Example case of “Resource sharing support”

November 2010


Slide 28




TVWS network #2Frequency channel: none


TVBD (slave)


CDIS/CM






TVBD (slave)


CDIS/CM

Operable frequency channels#F1



TVWS network #2 Selected frequency channel: noneSelected RAT: #R2

Operable frequency channels#F1




This decision will need a check(*1) whether resource sharing and synchronized operation is possible via backbone network for each TVWS network

(*1) Please see the other issues in footnote #23 of reference [1]

Doc.: IEEE 802.19-10/161r0 SubmissionSlide 1 Resource management for TVWS network coexistence Notice: This document has been prepared to assist IEEE 802.19.

Documents

rat step

tvws network coexistencenotice

sony corporationpage

sony corporationslide

yyxxxxr020101110ryo

tvws frequency reusestep

sony corporationnovember

sony proposal slide