IEEE 802.19 DCN 19-10-0008-01-0000 Submission TVWS Coexistence Use Cases Notice: This document has been prepared to assist IEEE 802.19. It is offered as.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /90r0 Submission Nov., 2012 NICTSlide b NICT Proposal IEEE P Wireless RANs Date: Authors: Notice: This document.
Advertisements

Doc.: IEEE /0930r0 Submission July 2006 Nancy Cam-Winget, Cisco Slide 1 Editor Updates since Jacksonville Notice: This document has been prepared.
Doc.: IEEE /0024r0 Submission May 2006 Steve Shellhammer, QualcommSlide 1 Discussion of Coexistence Scenarios Notice: This document has been prepared.
Doc.: IEEE /0094r0 Submission November 2009 Steve Shellhammer, QualcommSlide 1 Comments on PAR Notice: This document has been prepared.
Doc.: IEEE /1451r1 Submission September 2006 T. K. Tan, Philips Slide 1 WNG SC Report Notice: This document has been prepared to assist IEEE
Sg-whitespace-09/0029r1 Submission February 2009 Steve Shellhammer, QualcommSlide 1 Coexistence Scenarios Date: Authors: Notice: This document.
Doc.: IEEE /0072r0 SubmissionS. Filin H. Harada, NICTSlide 1 Coexistence algorithms Notice: This document has been prepared to assist IEEE
Doc.: IEEE /0054r0 Submission May 2011 Slide 1Hyunduk Kang, et al, ETRI Discussion on mode of management service Notice: This document has been.
Doc.: IEEE /2237r0 Submission July 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D1.0 Insert and Deletion Notice: This document has been.
Doc.: IEEE /1212r0 Submission TGT and MEF Liaison Notice: This document has been prepared to assist IEEE It is offered as a basis for.
Doc.: IEEE /0028r0 Submission January 2005 Eleanor Hepworth, Siemens Roke ManorSlide 1 Definitions and Terminology Notice: This document has been.
Doc.: IEEE /0197r0 Submission March 2005 Nancy Cam-Winget et alSlide 1 TAP & JIT Merge Process Notice: This document has been prepared to assist.
Doc.: IEEE /0460r1 Submission March 2006 Fujio Watanabe, DoCoMo USA LabsSlide 1 Japanese Emergency Call Regulation Notice: This document has been.
Doc.: IEEE /0652r1 Submission May 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D0.12 Insert and Deletion Notice: This document has been.
[ Interim Meetings 2006] Date: Authors: July 2005
IEEE White Space Radio Contribution Title
LB73 Noise and Location Categories
LB73 Noise and Location Categories
WRAN Protocol Reference Model(PRM)
Waveform Generator Source Code
System Requirements for the RASGCIM Amendment
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
[ Policies and Procedure Summary]
Motion to accept Draft p 2.0
3GPP liaison report July 2006
[place presentation subject title text here]
Descriptive Language Usage in TGv
Decision Topology Definitions
(Presentation name) For (Name of group) (Presenter’s name,title)
On Coexistence Mechanisms
[Comparison between CDMA Code and Contention-based Access]
TGu-changes-from-d0-02-to-d0-03
Contribution on Location Privacy
November Opening Report
On Coexistence Mechanisms
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
Experimental DTV Sensor
July 2012 Opening Report Date: Authors: July 2012
IEEE P Wireless RANs Date:
IEEE P Wireless RANs Date:
Spectrum Sensing Tiger Team
TGu-changes-from-d0-01-to-d0-02
September Opening Report
LB73 Noise and Location Categories
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
November Opening Report
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
System Requirements for the RASGCIM Amendment
Beamforming and Link Adaptation Motions
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
January Opening Report
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
WNG SC Closing Report Date: Authors: November 2005
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
May 2012 Opening Report Date: Authors: May 2012
Presentation transcript:

IEEE DCN Submission TVWS Coexistence Use Cases Notice: This document has been prepared to assist IEEE 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. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the TAG of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE TAG. If you have questions, contact the IEEE Patent Committee Administrator at. January Slide 1Chen Sun et al, NICT

IEEE DCN Submission Abstract This contribution presents an overview of coexistence use cases and classification that can be useful to generate evaluation criteria of coexistence Dependent services and independent services –Dependent services address the situation where LAN provides range extension of RAN for one service. LAN-LAN scenario –LAN-LAN scenario use cases Non-mobile user; Mobile user RAN-RAN scenario –RAN-RAN scenario use cases Non-mobile user; Mobile user LAN-RAN scenario –LAN-RAN scenario use cases Coexistence table of LAN-RAN scenario Classification of devices based on mobility Note: The use cases address the coexistence among heterogeneous networks or networks operated by different operators. LAN and RAN services can be considered of providing coverage extension or of different service purposes. End user devices can have direct access to RAN services instead of using LAN services as a “bridge”. January Slide 2Chen Sun et al, NICT

IEEE DCN Submission use cases classification Slide 3Chen Sun et al, NICT

IEEE DCN Submission LAN-LAN coexistence scenario In a typical LAN service area different LAN of different wireless technologies might exist. For example, in a city business district different service providers might provide LAN access based on different technologies (e.g., , , etc) using TVWS (for example in near by buildings or in same building). Slide 4Chen Sun et al, NICT January

IEEE DCN Submission LAN-LAN coexistence scenario, use cases Use case 1: non-mobile user –TVWS devices such as computers having LAN access –Mode I, Mode II, sensing-only devices Use case 2: mobile user –TVWS devices such as moving pedestrians having LAN access –Mode I, Mode II, sensing-only devices Slide 5Chen Sun et al, NICT January

IEEE DCN Submission RAN-RAN coexistence scenario In a typical RAN service area, different RAN of different wireless technologies might exist. For example, different towns provide different RAN access to residents based on different technologies (e.g., , , etc) using TVWS. At the border area of towns the RAN-RAN coexistence issue arises. Slide 6Chen Sun et al, NICT January

IEEE DCN Submission RAN-RAN coexistence scenario, use cases Use case 1: non-mobile user –TVWS devices such as CPEs having RAN access –fixed; Mode I Use case 2: mobile user –TVWS devices such as pedestrian devices, vehicles, trains having RAN access –Mode I Slide 7Chen Sun et al, NICT January

IEEE DCN Submission LAN-RAN coexistence scenario For coverage extension, RAN services provide connection over large area whereas LAN services provide access for end users. RAN services provide backbone connection to network such as from local base stations/CPEs to backbone internet. LAN services provide connection at end users such as from PCs/PDAs to access points/CPEs Slide 8Chen Sun et al, NICT January

IEEE DCN Submission LAN-RAN coexistence scenario, Use case 1: Vehicle-to- Vehicle communication with internet access Scenario description –TVWS RAN provides internet access to moving vehicles through a local/regional base station. –TVWS LAN/ad hoc network provides communication among vehicles and access to internet Devices –Geolocation information is assumed available at vehicles for Mode II devices –Devices providing LAN/ad hoc network among vehicles (mode I, mode II for AP) –Devices providing access to base station in RAN (Mode I) –Base station is a fixed device Slide 9Chen Sun et al, NICT January

IEEE DCN Submission LAN-RAN coexistence scenario, Use case 2: University campus Scenario description –TVWS RAN provides internet access to university campus through a local/regional base station (for extra capacity or due to infrastructure incapability). –TVWS RAN can also provide end user devices with direct connection to Internet. –TVWS LAN provides internet access to students’ computers and PDAs (notice the transmit power limit of the portable devices). Devices –Base station (fixed; 4w) –CPE (Mode I) –Campus access point in LAN (Mode II) –Campus devices in RAN (mode I) –Sensing-only devices for short range applications Slide 10Chen Sun et al, NICT January

IEEE DCN Submission LAN-RAN coexistence scenario, Use case 3: Internet access in train Scenario description –TVWS RAN provides internet access from moving train to local/regional base station. –TVWS LAN provides internet access to passenger computers Devices –Train position can be determined using railway sensors. –Train device in RAN is in mode I –Train device in LAN is in mode II –Passengers' devices having direction RAN access is in Mode I –Base station is a fixed device Slide 11Chen Sun et al, NICT January

IEEE DCN Submission LAN-RAN coexistence scenario, Use case 4: In- house internet and wireless network Scenario description –TVWS RAN provides access internet to CPE through base station –TVWS LAN/ad hoc provide internet access and wireless networking for in-house devices Devices –Base station (fixed; 4w) –CPE (Mode I) –In house access point (Mode II) –In house devices (mode I, mode II) –In house devices connecting to RAN services Mode I (notice the transmit power limit of the portable devices). –Sensing-only devices for short range applications such as video game devices Slide 12Chen Sun et al, NICT January

IEEE DCN Submission Coexistence table of LAN-RAN coexistence Scenario Slide 13Chen Sun et al, NICT January

IEEE DCN Submission Classification of devices based on mobility Slide 14Chen Sun et al, NICT January