Neighbor Setting Procedures

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0165r1 SubmissionPäivi Ruuska, NokiaSlide 1 Implementation aspects of a coexistence system Notice: This document has been.
Advertisements

Submission doc.: IEEE /XXXXr0 Month Year John Doe, Some CompanySlide 1 Insert Presentation Title Here Date: YYYY-MM-DD Authors: Notice: This document.
Doc.: IEEE /160r0 SubmissionSlide 1 Output power management for TVWS network coexistence Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /0262r1 Submission March 2010 Ha-Nguyen Tran et al., NICTSlide 1 Requirements and Amendment Regarding TVWS Database Access Notice:
Doc.: IEEE /0002r1 Submission January 2011 Päivi Ruuska, NokiaSlide 1 Neighbor Setting Procedures Notice: This document has been prepared to assist.
Doc.: IEEE /0118r0 Submission July 2012 Mika Kasslin, NokiaSlide 1 How to run WSO decision making with coexistence report announcements? Notice:
Doc.: IEEE /161r0 SubmissionSlide 1 Resource management for TVWS network coexistence Notice: This document has been prepared to assist IEEE
Doc.: IEEE /0061r0 Submission June 2011 Mika Kasslin, NokiaSlide 1 Discovery system overview Notice: This document has been prepared to assist.
Doc.: IEEE /41r0 SubmissionSlide 1 P System Architecture Notice: This document has been prepared to assist IEEE It is offered.
Doc.: IEEE /0013r0 Submission January 2012 Mika Kasslin, NokiaSlide 1 Motivation for Monitor WSO Notice: This document has been prepared to assist.
Doc.: IEEE /129r0 Submission September 2010 Junho Jo/Jihyun Lee, LG ElectronicsSlide 1 IEEE System description Notice: This document.
Doc.: IEEE COEX-02/004r0 Submission 23 January, 2001 James P. K. Gilb, Appairent Technologies Project: IEEE P Working Group for Wireless Personal.
Doc.: IEEE /0037r0 Submission February 2010 Joe Kwak (InterDigital)Slide 1 TVWS Architecture for SDD Date: Authors: Notice: This document.
Doc.: IEEE /0088r0 Submission September 2011 Jari Junell, NokiaSlide 1 Neighbor discovery simulation summary Notice: This document has been prepared.
Doc.: IEEE /0162r0 Submission November 2010 Jihyun Lee, LG ElectronicsSlide 1 TVWS Coexistence Procedures and Protocols Notice: This document.
Bluetooth and WLAN coexistence in dense deployment scenarios
Requirements and Amendments Regarding TVWS Database Access
Wireless Coexistence in the Automotive Domain – Study group proposal
Submission Title: [Proposal for MAC Peering Procedure]
Month Year doc.: IEEE yy/xxxxr0 Janurary 2016
doc.: IEEE <doc#>
Overview of IEEE Date: Authors: August 2014
Proposal on system description, reference model and draft outline
Submission Title: [Comment resolution for i-31]
<month year> doc.: IEEE <01/137> March 2001
P System Architecture Date: Authors: March 2010
doc.: IEEE <doc#>
<May,2009> doc.: IEEE <doc .....> <July 2009>
Resource allocation principles for coexistence system
Submission Title: [802.11n Liaison Report May 2009]
Submission Title: [Proposal for MAC Peering Procedure]
May 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Input to the TRD of TG3d Date Submitted: 12.
July Tutorial – Possible Solutions
doc.: IEEE <doc#>
FCC Regulations and Multi-band Operation
Possible Effects of FCC rules to design
Design Principles for Entity Responsibilities
doc.: IEEE <doc#>
Month Year doc.: IEEE yy/xxxxr0 July 2015
FCC rules and design Date: Authors: October 2010
AP Location Capability
Submission Title: [Proposal for MAC Peering Procedure]
Coexistence of CMs with different decision making algorithms
Enabling Procedure of Communication in TVWS under FCC rules
P System Architecture Date: Authors: March 2010
Neighbors and Neighbor Discovery
Discussion Topics Date: Authors: March 2011 Month Year
Updates to the Draft Authors:
Updates to the Draft Authors:
Submission Title: [Proposal for MAC Peering Procedure]
March 2016 Election Results
doc.: IEEE yy/xxxxr0 Month Year May 2016
Examples of deployment scenarios
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Consideration of Coexistence Problem]
July Tutorial – Possible Solutions
doc.: IEEE <doc#>
TG1 Draft Topics Date: Authors: September 2012 Month Year
Requirements Date: Authors: March 2010 Month Year
Date Submitted: [29 August 2016]
Procedures Date: Authors: November 2010
Possible Action Items Date: Author:
P System Architecture Date: Authors: March 2010
Coexistence Decision Making Topologies
P System Architecture Date: Authors: March 2010
Interference-free scheduling
Comments to IEEE /68 Date: Authors: September 2009
Enabling Procedure of Communication in TVWS under FCC rules
Month Year doc.: IEEE yy/xxxxr0 August 2019
Month Year doc.: IEEE yy/xxxxr0 January 2016
Presentation transcript:

Neighbor Setting Procedures Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2011 Neighbor Setting Procedures Date: 2011-01-03 Authors: 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. Päivi Ruuska, Nokia John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2011 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. Päivi Ruuska, Nokia John Doe, Some Company

Neighbor setting procedures overview January 2011 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. – CMs are required to provide some TVBD information for this calculation. 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. Päivi Ruuska, Nokia

Neighbor Discovery January 2011 Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2011 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. Päivi Ruuska, Nokia John Doe, Some Company

Neighbor Discovery – interference calculation 1/3 January 2011 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 Päivi Ruuska, Nokia

Neighbor Discovery – interference calculation 2/3 Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2011 Neighbor Discovery – interference calculation 2/3 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’’ Päivi Ruuska, Nokia John Doe, Some Company

Neighbor Discovery – interference calculation 3/3 Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2011 Neighbor Discovery – interference calculation 3/3 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’ 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. r2’ r1’ master B client client master A r1’’ r2’’ Päivi Ruuska, Nokia John Doe, Some Company

Example: Initial set-up January 2011 Example: Initial set-up CDIS CM CE Net1 CE CM CE Net4 Net3 CM CE Net2 Päivi Ruuska, Nokia

New network (Net5) starts operation January 2011 New network (Net5) starts operation CDIS CM CE Net1 CE CM CE Net4 Net3 CM CM CE CE Net2 Net5 Päivi Ruuska, Nokia

January 2011 CM of new network registers to CDIS if the CM is not registered already CDIS CM CE Net1 CM=> CDIS: Register req CDIS: Can I serve the CM? CDIS => CM: Register rsp CE CM CE Net4 Net3 CM CM CE CE Net2 Net5 Päivi Ruuska, Nokia

CM requests neighbor discovery for network 5 from CDIS January 2011 CM requests neighbor discovery for network 5 from CDIS CDIS CM CE CM => CDIS: Neighbor discovery req CDIS=> CM: Neighbor discovery rsp Candidate neighbors to Net5: Net2, mutual neighbor Net1, one-directional interferer source Net1 CE CM CE Net4 Net3 CM CM CE CE Net2 Net5 Päivi Ruuska, Nokia

January 2011 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. Päivi Ruuska, Nokia

CM sends neighbor inquiry request to CMs of candidate neighbors January 2011 CM sends neighbor inquiry request to CMs of candidate neighbors CDIS CM 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. CE Net1 CE CM CE Net4 Net3 CM CM CE CE Net2 Net5 Initiating CM Päivi Ruuska, Nokia

Neighbor Setting Target CM responds with Neighbor_set_rsp. January 2011 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. Päivi Ruuska, Nokia

CM sends neighbor set request to CMs of estimated neighbors January 2011 CM sends neighbor set request to CMs of estimated neighbors CDIS CM CE Net1 CE CM CE Net4 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) Net3 CM CM CE CE Net2 Net5 Initiating CM Päivi Ruuska, Nokia

January 2011 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. Päivi Ruuska, Nokia

January 2011 TVBD stops operation - CM sends neighbor removal to CMs of neighbors and updates information to CDIS CDIS CM CM =>CDIS Update TVBD information (remove TVBD) May deregister if no need to serve other TVBDs. CM => neighbor CM Neighbor remove req Neighbor CM => CM Neighbor remove rsp Both CMs remove the neighbors from neighbor lists CE Net1 CE CM CE Net4 Net3 CM CM CE CE Net2 Net5 => stopped operation Päivi Ruuska, Nokia

January 2011 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. Päivi Ruuska, Nokia