doc.: ieee 802.19-11/0002r1 submission january 2011 päivi ruuska, nokiaslide 1 neighbor setting...

doc.: IEEE 802.19-11/0002r1

Submission

January 2011

Päivi Ruuska, NokiaSlide 1

Neighbor Setting Procedures

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: 2011-01-18

Authors:Name Company Address Phone email

Päivi Ruuska Nokia Research Center Visiokatu 1, 33720 Tampere,

Finland +358-718035433 [email protected]

Mika Kasslin Nokia Research Center Itämerenkatu 11-13, 00180

Helsinki, Finland +358-718036294 [email protected]

Jari Junell Nokia Research Center Itämerenkatu 11-13, 00180

Helsinki, Finland +358-718036575 [email protected]

Juha Salokannel Nokia Research Center Visiokatu 1, 33720 Tampere,

Finland +358-718035494 [email protected]

doc.: IEEE 802.19-11/0002r1

Submission Päivi Ruuska, NokiaSlide 2

Introduction

In order to provide coexistence services to TVBDs, the coexistence system has to define which TVBDs have to coexist. Thus, in this presentation we describe procedures for neighbor setting.

The intention is that a neighbor relationship is created between the TVBDs which cause interference: – neighbors if the interference is bi-directional

– one-sided interferers if the interference is one-directional

Coexistence system services are used for neighbor setting: – Neighbor discovery is provided by CDIS to CMs.

– Neighbor inquiry, set, and remove are inter-CM neighbor management services.

January 2011

doc.: IEEE 802.19-11/0002r1

Submission

Task division between the entities

CDIS – neighbor discovery

• Proposes candidate neighbors for a TVBD.

• Candidate neighbor selection is based on propagation calculations.

• CM is required to provide TVBD information needed for the calculation.

– Geo-location, max TX power, antenna gains, min SNR, out-door/in-door…

– Not actual operating parameters, e.g. frequency, bandwidth, utilization

CM – neighbor management

• Decides neighbors for the TVBDs it serves.

• Decision is based on – CDIS proposed candidates

neighbors

– Capability and operating parameters of TVBDs

– Channel measurements

January 2011


doc.: IEEE 802.19-11/0002r1

Submission

Neighbor setting procedures overview

• Neighbor discovery – CDIS service– TVBDs which interfere each other may be served by different CMs.

– CDIS calculates which TVBDs interfere each other, and provides candidate neighbor lists to the CMs.

• Neighbor inquiry – inter-CM neighbor management service– CMs serving candidate neighbors exchange more TVBD information.

– Information exchanged in neighbor inquiry is used to validate that the TVBDs are capable of interfering, i.e. TVBDs are able to operate on same frequencies.

– CM initiating the neighbor inquiry also uses the candidate neighbor information to evaluate whether candidate neighbor interferes TVBD and shall be set as neighbor/interferer.

• Neighbor set – inter-CM neighbor management service– A neighbor relationship is created between TVBDs which are estimated to interfere.

• Neighbor remove – inter-CM neighbor management service– The neighbor relationship is tear down between neighbors which no longer interfere.


January 2011

doc.: IEEE 802.19-11/0002r1

Submission

Neighbor Discovery• CDIS provides neighbor discovery service to CMs. CMs are required to provide

up to date information of TVBDs to CDIS.• CM sends Neighbor_discovery_req to CDIS to update parameters of a TVBD and

to request candidate neighbor list for the TVBD.– Parameters: geo-location, max TX power, operation environment (indoor/ outdoor), min

SNR, directed antenna gain…

• CDIS calculates the candidate neighbors to the TVBD and provides the candidate neighbor list to the requesting CM in Neighbor_discovery_rsp

– Candidate neighbor: network which causes interference at the location of TVBD, or network at which location TVBD causes interference > noise floor +3dBm (see following pages).

– Candidate neighbors may be reported in calculated interference level order, based on the interference level the candidate neighbors cause at the location of TVBD.

– Interference direction is also indicated to CM: • Mutual neighbor – both cause interference at each other’s location.

• One-sided interferer source – only candidate neighbor causes interference at location of TVBD.

• One-sided interferer victim – only TVBD causes interference at location of candidate neighbor.


January 2011

doc.: IEEE 802.19-11/0002r1

Submission

Neighbor Discovery – interference calculation 1/3

• Target: to calculate a possibility for a mutual neighbor, one-sided interferer source or one-sided interferer victim cases.

• Candidate neighbor calculation parameters:– Minimum SNR of the network for operation: SNRmin

– Maximum transmission power: Ptxmax

– Antenna gains: G(θ), θ is an angle to the direction of other device

– Attenuation according to a propagation model: L(r), r is a distance

– Defined non-aggregated interference level above the noise: Im

– Noise level: N = F+No, F=noise figure, No=ambient noise


January 2011

doc.: IEEE 802.19-11/0002r1

Submission


• Calculation according to the figure on the right• Calculate max distance r1 for communication

within both networks by solving r1 from the equation (units in dB):

L(r1)=Ptxmax+G(θ)-SNRmin-N • Calculate max interfering distance r2 from the

outmost TVBD devices of both networks by solving r2 from the equation (units in dB): L(r2)=Ptxmax+G(θ)-Im-N

• d_locationAB = distance between informed geolocations of networks A and B


Master of netA (location known in CDIS)

Master of netB (location known in CDIS)

Client of netA

Client of netB

r1’

r1’’

r2’ r2’’

January 2011

doc.: IEEE 802.19-11/0002r1

Submission


• Network A is requesting candidate neighbor list

• B is mutual neighbor if– d_locationAB less than r1’+r2’+r1’’ and r1’’+r2’’+r1’

• B is one-sided interferer source if – d_locationAB more than r1’+r2’+r1’’ and less than r1’’+r2’’+r1’

• B is one-sided interferer victim if– d_locationAB less than r1’+r2’+r1’’ and more than r1’’+r2’’+r1’


client

r1’r2’

r2’’r1’’

One-sided interferer example:B (red) network is source.A (green) network is victim.

Here assumed that master has directed antenna, and client has omnidirectional.

January 2011

master Amaster B client

doc.: IEEE 802.19-11/0002r1

Submission

Neighbor Discovery – client locations known?

• There may be TVBD networks from which only master location is known.– E.g. master is mode II and clients are mode I.

– CDIS assumes that clients may reside anywhere in the communication range of the master.

• There may be TVBD networks from which both master and clients locations are known.– E.g. master and clients are fixed and/or mode II devices.

– CDIS does not need to assume client locations if all of them are known. Candidate neighbor calculation can be done using node locations.

January 2011


doc.: IEEE 802.19-11/0002r1

Submission

Neighbor discovery – client locations not known

• CDIS has to assume that clients may reside anywhere in the communication range of master.

• “External TVBD” may interfere communication of the TVBD network if causes interference anywhere in the communication area.

January 2011


C

CM

Interference area

Communication area- Actual communication area is relevant only where the nodes are, but clients may be anywhere

Mutual neighbor

Mutual neighbor

One-sided victim

doc.: IEEE 802.19-11/0002r1

Submission

Neighbor discovery – client locations known

• If CDIS knows where all the clients are, candidate neighbor calculation can be done using node locations.

• “External TVBD” interferes communication of the TVBD network only if causes interference to the links between nodes which locations are known.

January 2011


C

CM

Interference area

Communication area - Actual communication area is relevant only where the nodes are

One-sided victim

Mutual neighbor

One-sided victim

Communication between links

doc.: IEEE 802.19-11/0002r1

Submission

Neighbor Inquiry• After receiving candidate neighbor list from the CDIS, the CM initiates

neighbor inquiry with the CMs serving candidate neighbors.– CM may not have to start neighbor inquiry related to all candidate neighbors.

• Initiating CM sends Neighbor_inquiry_req to CMs serving the candidate neighbors.

– This is to access more information of candidate neighbors, and to filter out candidate neighbors which are not able to operate on same channels.

– TVBD parameters: TVBD frequency capabilities, RAT type, operating parameters (if operating)…

• Target CM responds with Neighbor_inquiry_rsp.– Candidate TVBD parameters: TVBD frequency capabilities, RAT type operating

parameters.

• Both CMs validate whether the TVBDs are capable of interfering.– If they are capable of operating on same frequencies they may interfere, and

capability_to_interfere is set TRUE.


January 2011

doc.: IEEE 802.19-11/0002r1

Submission

Neighbor Setting• After receiving the Neighbor_inquiry_rsp and validating capability_to_

interfere=TRUE, the initiating CM evaluates whether candidate neighbor interferes TVBD.

– CM may request TVBD to provide measurements to support the evaluation.

• Initiating CM shall send Neigbor_set_req to target CM if it has evaluated own TVBD to be interference victim. It may send Neigbor_set_req to target CM if it has evaluated TVBD to be the interference source only.

– The evaluation is based on CDIS interference direction indication, neighbor inquiry based validation of capability_to_interfere, and initiating CM’s own evaluation after neighbor inquiry which may include TVBD measurements.

– Parameter: proposed neighbor relationship type (neighbor/one-sided interferer source/one-sided interferer victim)

• Target CM responds with Neighbor_set_rsp.– Shall reject if TIME_X elapsed between Neighbor_inquiry_req and Neighbor_set_req, or

capability_to_interfere = FALSE. Otherwise:– Shall accept if mutual neighbor relationship is proposed.– May accept if one-sided interferer relationship is proposed.


January 2011

doc.: IEEE 802.19-11/0002r1


Neighbor Remove

• CMs evaluate the neighbor relationships continuously. If CM discovers that TVBD is not interfering neighbor or vice versa it initiates the neighbor relationship teardown with Neighbor_remove_req– CM shall send request if TVBD is switched off, and may send it

because of other reasons.

– Optional parameter: reason (TVBD switch off, TVBD mobility, no interference detected, other)

• CM of neighbor TVBD shall accept the request by sending Neighbor_remove_rsp.

January 2011

doc.: IEEE 802.19-11/0002r1

Submission

Example: Initial set-up


Net1

Net4 Net3CE

CM CE

CM

CE

CDIS

Net2

CE

CM

January 2011

doc.: IEEE 802.19-11/0002r1

Submission

New network (Net5) starts operation


Net1

Net4

Net5

Net3CE

CM CE

CM

CE

CE

CM

CDIS

Net2

CE

CM

January 2011

doc.: IEEE 802.19-11/0002r1

Submission

CM of new network registers to CDIS if the CM is not registered already


Net1

Net4

Net5

Net3CE

CM CE

CM

CE

CE

CM

CDIS

CM=> CDIS: Register req

CDIS: Can I serve the CM?

CDIS => CM: Register rsp

Net2

CE

CM

January 2011

doc.: IEEE 802.19-11/0002r1

Submission

CM requests neighbor discovery for network 5 from CDIS


Net1

Net2

Net4

Net5

Net3CE

CM CE

CM

CE

CM

CE

CE

CM

CDIS

CM => CDIS: Neighbor discovery req

CDIS=> CM: Neighbor discovery rsp

Candidate neighbors to Net5:Net2, mutual neighborNet1, one-directional interferer source

January 2011

doc.: IEEE 802.19-11/0002r1

Submission

CM sends neighbor inquiry request to CMs of candidate neighbors


Net1

Net4

Net5

Net3CE

CM CE

CM

CE

CE

CM

CDIS

Initiating CM => Target CM: Neighbor inquiry req (TVBD capability parameters, optionally TVBD operating parameters)

Target CM => Initiating CM:Neighbor inquiry req (TVBD capability parameters, TVBD operating parameters)

Both CMs validate whether TVBDs are capable of interfering.

Initiating CM evaluates whether candidate neighbor interferes. The CM may request TVBD to perform measurements on operating channel of candidate neighbor.

Net2

CE

CM

Initiating CM

January 2011

doc.: IEEE 802.19-11/0002r1

Submission

CM sends neighbor set request to CMs of estimated neighbors


Net1

Net4

Net5

Net3CE

CM CE

CM

CE

CE

CM

CDIS

Initiating CM => target CM: Neighbor set req-To CM of Net1: one-directional interferer source-To CM of Net2: mutual neighbor

Target CM => initiating CM: Neighbor set rsp (accept/reject)

Net2

CE

CM

Initiating CM

January 2011

doc.: IEEE 802.19-11/0002r1

Submission

TVBD stops operation - CM sends neighbor removal to CMs of neighbors and updates

information to CDIS


Net1

Net4

Net5 => stopped operation

Net3CE

CM CE

CM

CE

CE

CM

CDIS

CM =>CDISUpdate TVBD information (remove TVBD)May deregister if no need to serve other TVBDs.

CM => neighbor CMNeighbor remove req

Neighbor CM => CMNeighbor remove rsp

Both CMs remove the neighbors from neighbor lists

Net2

CE

CM

January 2011

doc.: IEEE 802.19-11/0002r1


Summary

• In order to provide coexistence services to TVBDs, the coexistence system has to define which TVBDs have to coexist.

• This presentation presented the neighbor discovery, neighbor inquiry, set, and remove procedures.

January 2011

doc.: ieee 802.19-11/0002r1 submission january 2011 päivi ruuska, nokiaslide 1 neighbor setting...

Documents