doc.: ieee 802.19-10/0165r0 submissionpäivi ruuska, nokiaslide 1 implementation aspects of a...

doc.: IEEE 802.19-10/0165r0

Submission Päivi Ruuska, NokiaSlide 1

Implementation aspects of a 802.19.1 coexistence system

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-10

Name Company Address Phone email Jari Junell Nokia Research Center

Itämerenkatu 11-13, 00180 Helsinki, Finland

+358-718036575 [email protected]

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

Helsinki, Finland +358-718036294 [email protected]

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

Finland +358-718035433 [email protected]

Juha Salokannel Nokia Research Center Visiokatu 1, 33720 Tampere,

Finland +358-718035494 [email protected]

Authors:

November 2010

doc.: IEEE 802.19-10/0165r0

Submission Päivi Ruuska, NokiaSlide 2

Abstract

CE, CM, and CDIS may be implemented by different parties. This presentation presents how the system looks from a TVBD/CE perspective and on the other hand from a CM perspective.

We hope this presentation to be helpful in understanding the design behind our proposal (19-10/156).

November 2010

doc.: IEEE 802.19-10/0165r0

Submission

Acronyms used in this presentation

• CDIS – Coexistence discovery and information server

• CE – Coexistence enabler

• CM – Coexistence manager

• CMIS – Coexistence management and information system

• TVBD – TV band device

• TVWS DB – TV white space database

Päivi Ruuska, NokiaSlide 3

November 2010November 2010

doc.: IEEE 802.19-10/0165r0

Submission

Outline

• What does a CE do?– How does it get connected to a coexistence management and

information system (CMIS)?

– How does it use the services provided by the CMIS?

• What does a CM do?– How does it get connected with a CDIS?

– How does it serve TVBDs?

– How does it communicate with peer CMs?


November 2010

doc.: IEEE 802.19-10/0165r0

Submission

CE operation

• The next slides present the TVBD/CE operation when it decides to register to CMIS and subscribe to a coexistence service, and while it is using the services.

• CE is associated to a TVBD and responsible of providing coexistence information to and from TVBD and coexistence management to TVBD. In this presentation the interface between TVBD and CE is not considered. – The CE doesn’t have to be collocated with a TVBD but may be

also e.g. implemented as a part of a server controlling operations of a TVBD

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

CE – Before registration• A TVBD may be operating before registering to a CMIS, and

subscribing coexistence services.– TVBD selects own operating parameters based on TVWS DB information on

available channels and possibly channel measurements.

• A TVBD may register to a CMIS, and subscribe services before starting operation.– TVBD gets operating parameters from CMIS, or information it can use to select

parameters.

• A TVBD may access to some information provided by a CMIS before registration. – Basic regulatory environment in area.

– Possibly some information to decide whether to start operating in TVWS at all, and whether to register.

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

CE - Registration decision

• TVBD decides to register to CMIS if it has a need for coexistence services.

– May, as an example, need assistance in selecting operating parameters.– TVBD may also register automatically when switched (e.g. if TVBD does not

support channels selection algorithms itself).

• To register the CE sends a Register_req• A registered TVBD is able to subscribe to coexistence information or

management services. • A TVBD which is only registered to CMIS does not get any coexistence

support from CMIS.– A registered TVBD may provide basic TVBD information (geo-location,

capabilities) to the CMIS in TVBD_Information_rsp. Alternatively all the information is provided only upon service subscription. More on these options in the CM slides.

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

CE - Service subscription decision(in registered state)

• A registered TVBD decides to subscribe to a service when it needs assistance in selecting operating parameters.

• Which service to subscribe to, depends on the TVBD capabilities, and possibly on the spectrum environment.– Coexistence management service

• TVBD without advanced channel/resource selection capabilities

• Congested environment.

– Coexistence information service

• TVBD with advanced channel/resource selection capabilities

• To subscribe to a service CE sends a Service_subsribe_req

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

CE – TVBD information provision(in subscribed state) (cont.)

• A TVBD which is subscribed to a service shall provide TVBD information to the CMIS.– Automatically – when information changes, CE sends a

TVBD_Information_rsp

– Upon request from CMIS, CE sends a TVBD_Information_rsp

– May receive a message filtering configuration request from the CMIS – the CE sends TVBD_Info_Update_Config_rsp and configures TVBD_information_rsp message sending rules.

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

CE – TVBD information provision (in subscribed state) (cont.)

• TVBD Information a CE provides to the CMIS if the TVBD is subscribed to information or management service– Geo-location, capabilities

– Coexistence value – The CE calculates CV from the number of nodes in the TVBD network, and possibly TVBD flexibility to use resources and coexist with other systems.

• TVBD Information a CE provides to the CMIS if the TVBD is subscribed to coexistence information service– Resource use – operating parameters (e.g. frequency, bandwidth,

utilization, power)

– Satisfaction value – indication if the TVBD is planning to change operating parameters.

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

CE –TVBD measurements provision(in subscribed state)

• A TVBD which is subscribed to a service should provide TVBD measurements to the CMIS.– Automatically – when changed/new measurement information

available, CE sends a TVBD_measurement_rsp

– Upon request from CMIS, CE sends a TVBD_measurement_rsp which includes stored measurement information.

– CMIS may configure message filtering, or give guidance to the measurements. - Upon receiving a TVBD_Measurement_Config _req, the CE responds with a TVBD_Measurement_Config_rsp and depending on parameters in request configures the automatic measurement information sending rules or tries to configure measurement according the received guidance.

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

CE – Obeying management(in management subscribed state)

• A TVBD subscribed to the management service shall obey the resource allocations received from CMIS.

• Upon receiving a TVBD_coexistence_management_rsp from the CMIS, the CE shall configure the TVBD operating parameters according to the given resource allocation.

• The CE may request new resource allocation from the CMIS, by sending a TVBD_coexistence_management_req which includes the resource need.– The CE shall wait at least TimeX after receiving resource allocation,

before it may send new request.

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

CE – Information service use (in management subscribed state)

• A TVBD subscribed to the information service shall provide own operating parameters to the CMIS. – CE sends updates on changed TVBD operating parameters in TVBD_Information_rsp.

• The CE receives information on spectrum environment changes from the CMIS in a TVBD_Coexistence_information_rsp– CE may use the information to when selecting own operating

parameters.

• The CE may request information of spectrum environment from the CMIS with a TVBD_Coexistence_information_req

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

What if I want to implement a CM, not a CE?

• In the next few slides we describe what it takes from a CM to be part of a CMIS– How does a CM get into the CMIS?

– How does it process messages from TVBDs?

– How does it serve TVBDs?

– How does it use CDIS for neighbor discovery?

– How does it serve peer CMs?

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Assumed CM design

• The CM is assumed to have the following service processes– Basic/Support service process

– TVBD service process

– Neighbor management process

• In the following slides it is assumed that the processes issue requests to each other and provide relevant information

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Joining a CMIS

• The first thing a CM needs to do in order to become a part of a CMIS is to register to a CDIS– With the registration the CM becomes discoverable to other CMs

– The CM issues a registration request message to a CDIS and waits for a response from the CDIS• Ask the CDIS to serve the CM with neighbor discovery service

– Once the CM has successfully registered to a CDIS, it starts providing the Basic/Support service to TVBDs

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Basic/Support service to TVBDs

• Provide basic information to any TVBDs on request and processes registration and service subscription requests from them

– Provide information about regulatory environment upon receiving a request message

• If needed, there could be similar information requests in the spec for unregistered TVBD/CEs

– Process registration request message from a TVBD and check if you can serve the TVBD

• Issue a response message to the TVBD indicating whether the registration succeeded

– Process service subscription message from a TVBD and check if you can provide the service as requested

• The TVBD needs to be at least registered

• Issue a response message to the TVBD indicating whether the subscription succeeded

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Serving a registered TVBD

• Currently it is assumed in the proposal that no information is provided by the TVBD before service subscription

• Note– Alternatively, a CM could obtain basic TVBD information from

the TVBD already before service subscription

– These decisions have an impact on the neighbor discovery service use as discussed in the following slide

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Subscribing services to a TVBD

• The CM processes a service subscription request and the default response is to accept the request from a registered TVBD

• Before accepting the request the CM should have determined neighbors for the TVBD– More on this in the following few slides

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Neighbor discovery

• The CM uses the CDIS to which it has registered to find out potential neighbors of a TVBD it serves

• Before the CM can issue a neighbor discovery request message to the CDIS, it needs to have received basic information of the TVBD from the TVBD

– Currently it is assumed that the information is obtained from the TVBD only upon the TVBD has subscribed to a service

– Alternatively the information could be obtained before service subscription from a registered TVBD

– All this is very much related to the overall design of the procedures and what is possible at what time

• Now the CM invokes neighbor management process for a selected set of candidate neighbors (some or all the potential neighbors)

– More on that in the next slides

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Neighbor management

• The CM has a process that takes care of neighbor management service– Neighbor inquiry

– Neighbor set

– Information and command exchange

– Neighbor remove

• The CM runs the neighbor inquiry function with the candidate neighbors to find out whether the two TVBDs are really neighbors or something else

• The CM proceeds to the neighbor set handshake to establish neighbor or one-sided interferer relationship

• Once the CM has completed the neighbor set on all the neighbors / one-sided interferers, the CM is ready to really start providing coexistence information or coexistence management service

– Should this be the time to provide the response to the service subscription request?

– Or is there some other notification to the TVBD that the services are available?

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Neighbor management (cont.)

• The CM uses the information and command exchange function with all the TVBD pairs for which it has established a neighbor or one-sided interferer relationship. In other words, neighborhood / interferer relationship obligates a CM to provide information or management commands.

– In the case of neighbors the CM shall issue updates to the other CM on any changes in TVBD parameter values (e.g. capabilities, service subscription status, spectrum environment report)

– Updates issued also on changes in operating parameters and satisfaction value if the CM’s own TVBD is subscribed only to the coexistence information service

– New operating parameters shall be issued to the peer CM if the peer CM’s TVBD is subscribed to the coexistence management service

– The CM may also request information from the peer CM– Issue internal requests to other processes as required to forward the information to the TVBD or

for further internal processing

• Neighbor remove handshake is used to remove neighbor or one-sided interferer relationship

– The CM can either initiate the function or be requested to tear down the relationship

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Providing coexistence information service to a TVBD

• Processing autonomous TVBD information updates from the TVBD– Issue an internal request to the neighbor management process to

forward the information to the peer CMs as applicable and needed

• Configuring rules for autonomous information reports• Issuing TVBD information requests to the TVBD• Processing autonomous TVBD measurement reports

from the TVBD• Configuring rules for autonomous measurement reports• Configuring measurements

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Providing coexistence management service to a TVBD

• Processing management requests– Initiate the resource allocation process

– Reply with a allocation response to the requesting TVBD

– Issue an internal request to the neighbor management process to forward the information to the peer CMs as applicable and needed

• Upon receiving an internal request on a management decision made by a peer CM, issue a management response to one’s own TVBD

November 2010


doc.: IEEE 802.19-10/0165r0

Submission

Summary

• In this presentation we went through what’s inside of a CE and a CM

• The intention was to give some insight to the design behind our proposal (19-10/156)

November 2010


doc.: ieee 802.19-10/0165r0 submissionpäivi ruuska, nokiaslide 1 implementation aspects of a...

Documents

tvbd capabilities

registered tvbd

service ce

information system cmis

information changes

abstract ce

ce doesnt

tvws db information