Date post: | 11-Jan-2016 |
Category: |
Documents |
Upload: | june-hampton |
View: | 212 times |
Download: | 0 times |
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide1 PicoCast Forum
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Personal Space Communication with WPAN Broadcasting] Date Submitted: [10 March 2010]Source: [S.M. Ryu, J.U.Seo, D.Y. Kim, Y.J.Park, & C.H. Yon] Company [PicoCast Forum, ISO/IEC
JTC1/SC6, IEEE Region 10, LG Telecom]E-Mail:[[email protected], [email protected], [email protected], [email protected],
Re: [In response to 802.15 WNG call for presentations.]
Abstract: [In the future, most users want to maintain their personal space within a fluid, moving environment. Service providers should approach and broadcast their services to these user spaces, allowing users to select service amongst broadcasting services, as if selecting a radio channel. Thus, if service broadcasts within personal spaces became standard, then the Personal Space Communication (PSC) based on WPAN technology will become a leading & killer application for Ubiquitous services in the future. We can ascertain that connections of PSC spaces will represent a large part of future 5G mobile communication.]
Purpose: [Information related to the request for international cooperation]
Notice: This document has been prepared to assist the IEEE P802.15. 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 acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide2 PicoCast Forum
March 2010
S.M. Ryu, J.U. SeoPicoCast Forum
D.Y. KimISO/IEC JTC1/SC6
Y.J. ParkIEEE Region 10
C.H. YonLG Telecom
WPAN Broadcasting for Personal Space Communication
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide3 PicoCast Forum
Contents Congratulatory message for PSC Why PicoCast ? Success stories of new technologies User Oriented Paradigm Shift User Requirements for PSC Technical Requirements for PSC Upgrading PSC standard from ISO/IEC29157 Relationship between PSC and 5GThe value of PSC as mobile carrier
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide4 PicoCast Forum
Part 1 Congratulatory message for PSC
Dr. Park Y.J. Director, IEEE Region 10
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide5 PicoCast Forum
• 1st Step : Personal Terminal Mobility– Basic mobile communication services
Personal Mobile Services
• 2nd Step : Personal Number Mobility– Service provider independent number services
• 3rd Step : Personal Information Mobility– SIM(Subscriber Identification Module) services
• 4th Step : Personal Environment Mobility– Environment follows when a personal space movesEnvironment follows when a personal space moves
Personal Space Communication
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide6 PicoCast Forum
Part 2 Why PicoCast ? Success stories of new technologies
Dr. Seo J.U. Chairman, PicoCast Forum
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide7 PicoCast Forum
How to increase mobile channel capacity ?
Macro Micro Pico Femto
Capacity 1 100 10,000 Low PowerPersonal Space
MobilityTx Power 1 1/1,000 1/1,000,000
3Km
Macro
.
300m
Micro30m
Pico Femto3m
Ubiquitous World Personal Mobile Space (WPAN)
Find new frequencies that haven’t been developed?; no more available Find new signal processing techniques ?; only few times increasable The only way to achieve few thousand times capacity ; reduce cell size
Why PicoCast ? - Capacity
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide8 PicoCast Forum
ChangeMy
Smartphone
ChangeMy
Smartphone
why?why?
Why PicoCast ? - Multi-peer Group Game
Group Game
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide9 PicoCast Forum
EnglishKorean
PSC EarphonePSC Earphone
• Multi-lingual broadcast : Subway lines and Tourist Information
Japanese
Chinese
Why PicoCast? - Select Service as if a radio
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide10 PicoCast Forum
Part 3 User Oriented Paradigm Shift User Requirements for PSC
Dr. Ryu S.M. Vice Chair, PicoCast Forum
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide11 PicoCast Forum
Lazybones want quick & convenient service
PicoCastPersonal Space Communication
Platform Software Internet
BusinessSolution OS Data Center
?Ubiquitous
Standard Exclusive Open, Share
User Convenience
EnvironmentMobility
Paradigm Shift – Invisible World
User-Oriented Mobile SpacePersonal Space Communication
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide12 PicoCast Forum
Wired
Wired
Broad-casting
Mobile
Wired
MobileBroad-casting
Internet
WLAN
FemtoIPTV
Home
Appliance
Mobile VoIP
User Space
WSD
Paradigm Shift – Personal Space Communication
Mobile
Mobile
Wired
Broad-casting
PSCInternet
Internet
Mobile
Wired
Broad-casting
Internet
FemtoIPTV
Mobile VoIP
User oriented Ubiquitous PSC
WLAN
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide13 PicoCast Forum
User terminals should meetprovider I/F specs.
Mobile Phone
WiMAX
IPTV
RFIDUSN
DMB
MobileVoIP
WSD
LTE
Space
User
WiMAX
IPTV
RFIDUSN
MobilePhoneDMB
MobileVoIP
LTE
WSD
Providers should translate their services to user I/F spec.within user mobile space.
Provider-Oriented User-Oriented
Paradigm Shift – User-Oriented Terminal
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide14 PicoCast Forum
HSDPAWiMAX
LTE
PSC = User InterfaceSelect among servicesbroadcast by providers
Mobile service
Wired Service
PC
IPTV
Home Appliances
User Oriented Terminal
Femto-cell
Paradigm Shift – Personal Broadcasting (PicoCast) Service
Option selected by user
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide15 PicoCast Forum
Off-line
IPTV (On-line)
PSC Requirements –Space Secretary
Seeing Hearing Feeling
Space Secretary Mobile video Audio / Voice Sensor Location / Direction Control data
Low power & Medium speed WPAN 2-way Broadcasting
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide16 PicoCast Forum
UWB ?
Bluetooth
Data Transmit Rate
Pow
er
Con
su
mp
tion
WLAN
AudioMobile Video
VideoVoiceSensorRFID
Ultra Low PowerBluetooth
Mobile Phone Power Consumption
ZigBee
PSC needs a single solution for multiple Services
Low power consumption & Medium speed multimedia
Container Concept Based
Sensor & Multimedia ProtocolISO/IEC 29157
PSC
PSC Requirements –Single solution for multiple services
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide17 PicoCast Forum
O1
O2
Frequency
Tx : 0dbm
fI2
Spurious :-60dbm
60dB
fO2
Tx : 0dbm Rx : -80dbm
80dB
Rx : -80dbmSearch Frequency
M
I2
MC
F MCF
MCF
MAC
F
MACF
MA
CF
I1
I3
UWB
40dB
Shall not receive during adjacent PHY is transmitting
PSC Requirements – Avoid mutual interference
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide18 PicoCast Forum
• 2-D • 3-D
GC1
GC2GC4 GC8 GC26
Self Organizing Cell Planning is inevitable
Container Concept is Required to avoid mutual interference in dense environment
GC1
GC2GC3
GC8
PSC Requirements – 3D Cell Planning
increasingMutual
Interference
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide19 PicoCast Forum
PSC Requirements –Container Structure
Video Audio Data Sensor
Higher synchronization performance is required ; 128bits preamble
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide20 PicoCast Forum
30m
Pico
Femto
3m
• Open PHY Interface• Power Control• Smooth Sliding Sync• Role Exchange• QoS Check / Sounding• Location / Direction• Emergency Flooding• Roaming / Hand-over• Sensor Mesh Relay• FCC Regulation
Through Body 3m = Forward Body 30m
PSC Requirements – Futher considerations
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide21 PicoCast Forum
Part 4Technical Requirements for PSC Upgrading ISO/IEC29157 for PSC
Dr. Kim D.Y. Chair, ISO/IEC JTC 1/SC6
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide22 PicoCast Forum
ISM2.4G900M
White Space
~Mbps
mm Wave
~10 cm
Low SpeedUWB
~10Mbps
PHY
MAC
APPHigh QoS
High Speed
Full Single MACHybrid Dual MAC
Arrange Requirements List user requirements Check reliability If no, reduce requirements
Challenges & OpportunitiesOvercome Near / Far Interference Single MAC for Multiple PHYs Tradeoff between power & speed Provide QoS with Low latencyIndependent Multiple MAC
Choose existing technique Select adequate PHY Select good chip solution Enhance antenna matching Reduce system size by good design
Technical Requirements for PSC Solution
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide23 PicoCast Forum
Solutions for Challenges
1. Near / Far Interference Chg. : Shall not receive while adjacent devices are
transmitting, even at different frequencies Sol. : Synchronized Frame can reject mutual interference
among PHYs 128bit multi preamble is necessary to enhance sync. probability 2. Single MAC to support Multi-PHYs
Chg. : Single PHY cannot meet wide user service requirements Sol. : Container Concept accommodates various information
Boxes Synchronized Frame can support different PHYs without interference3. Tradeoff between Power & Speed
Chg. : Low power sensors and Medium speed multimedia should be supported
Sol. : Single MAC for Multi PHY concept can support Multi RF Block
Sensors use single RF Block; Multimedia uses multi RF Blocks4. Provide QoS with Low Latency
Chg. : Ensure broadcasting performance and low latency without ARQ
Sol. : Frequency and Time hybrid diversity algorithm is necessary
Time diversity only cannot overcome multi path fading effect
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide24 PicoCast Forum
Single MAC supporting Multiple PHYs
PHY Type : 900M/2.4G ISM, 700M WS, UWB, mm Wave & etc PHY Interface : Synchronized Container Based multi-PHY support Special Features :
Interference Rejection thru Synchronized Containers Scalable data rate for each PHY Location & Direction reporting
PSCMAC
(Baseband)
PHY #1(RF #1)
PHY #2(RF #2)
PHY #N(RF #N)
Basic Speed~Mbps
Latency< 20msec
Location<10cm
•••
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide25 PicoCast Forum
Idle Idle Idle Idle IdlePHY # 1 Tx
Tx Rx Idle Rx IdlePHY # 2 Idle Rx Idle
Tx
Tx Idle
Rx
Rx
Rx Tx
Rx
Rx
RxPHY # 3
Avoid mutual interference among PHYs in PSC Shall not receive during adjacent PHY is transmitting. Transmit together at the same time.
MP1
P3
S2
S1
S4
S3
S5
P2
Tx
Tx Rx
Rx
Tx
Tx
Rx
Rx
Rx
Rx Tx
Rx
Rx
Rx
PSC Master
Avoid Interference thru Synchronized Containers
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide26 PicoCast Forum
Vessel (256msec)
#0 # 1 #2 #3 # 4 # 5 # 6 # 7 # 8 # 9 # 10 # 11 # 12 # 13 # 14 # 15
Control Box
Payload Box #1 Payload Box #nPayload Box #2 • • •
Container (16msec)
EOBLock(AA)
128bitPreamble
40bitTag
AA Payload
Hard Box
Soft Box
PHY dependent
constantparameter
BB1 BB2
RCB MCB TBD MACB / TBDRACB
Synchronized Container Structure
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide27 PicoCast Forum
70 80 90 100 110 12010
-12
10-10
10-8
10-6
10-4
10-2
100
Decision Threshold
Mis
sed
Det
ecti
on a
nd F
alse
Ala
rm P
roba
bili
ty
-3 dB
-2 dB
-1 dB
0 dB
1 dB
2 dB
3 dB
4 dB
5 dB
6 dB
7 dB
8 dB
9 dB
10 dB
64bit is not enough but 128 bit is high enough ; so we suggest multi Preambles
1.E-07
1.E-06
1.E-05
1.E-04
1.E-03
1.E-02
1.E-01
70 72 74 76 78 80 82 84 86 88 90 92 94Threshold
- 6 dB
- 5 dB
- 4 dB
- 3 dB
- 2 dB
- 1 dB
0 dB
2FAP
2MP
)/(1 0NEM c
)128( 2
1.E-07
1.E-06
1.E-05
1.E-04
1.E-03
1.E-02
1.E-01
35 37 39 41 43 45 47 49 51 53 55Threshold
- 6 dB
- 5 dB
- 4 dB
- 3 dB
- 2 dB
- 1 dB
0 dB
2FAP
2MP
)/(1 0NEM c
)64( 2
N=64 N=128
N=128
128bits preambles for synchronization
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide28 PicoCast Forum
Multiple Preamble Usage
C1 Remarks
1 ~ 8 (8) General Box purpose (Control, Payload)
9 ~ 12 (4) Hierarchy Beacon Box for synchronization
13 ~ 16 (4) Pairing Box (Fast Beacon Box)
17 ~ 18 (2) Sounding Box
19 Secure 1bit/symbol data transmit
20 ~ 35 (16) Reliable 4bit/symbol data transmit ※ would be substituted by the best code set after simulation study.
36 ~ 41 (16) Hands over for the local broadcasting
42 ~ 49 (8) Define Multi-RF to indicate sequence order
50 ~ 127 (except 119) TBD ; for special PHY applications
119 Emergency
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide29 PicoCast Forum
TestPath
DiversityMode
Diversity Number
1 2 3 4 5
Case A
1 soft wall~30m
Freq / Time 2700 / 329 106 / 2 9 / 0 1 / 0 0 / 0
Time with f1 3601 / 601 2487 / 303 2136 / 254 1945 / 237 1816 / 229
Time with f2 2361 / 422 1706 / 185 1457 / 135 1310 / 125 1215 / 111
Case B
2 soft wall~30m
Freq / Time 8264 / 1272 3545 / 101 1536 / 8 637 / 0 480 / 0
Time with f1 4648 / 724 3416 / 424 2976 / 363 2750 / 332 2580 / 309
Time with f2 5640 / 961 4287 / 614 3749 / 514 3461 / 460 3280 / 418
# of frame error / # of Sync loss
Receive sensitivity in multi path fading environment
Ensure broadcasting performance without ARQ
Should use frequency / Time hybrid diversity algorithm ; Frequency Hopping
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide30 PicoCast Forum
Master / Slave
M
S
Sync
Data M
S
S
S
SStar
M
SS
SS
MS
S
S
MS
S
S
MS
S
S
Sync Relay - Mesh - Ad-hoc - Hand-over
Add to IEEE802.15.psc
Possible by Existing Solutions
PSC Solution – Protocols
Multicast
MS
S
S
S S
S
S
M
S
S
S
SConvergence ofBroadcasting & Communication
M
S
S
S S
S
SBroadcast Relay with Single Master
Possible by ISO/IEC 29157
Group Multi Channel
M
S
S
S
S
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide31 PicoCast Forum
Overview of ISO/IEC 29157
Proposal February 5, 2008
NP Ballot: February 5, 2008 – May 5, 2008Meeting: Geneva, Swiss, April 6 – 11, 2008Meeting: Montreux, Swiss, November 3 – 7, 2008
CD Ballot: November 18, 2008 – February 18, 2009Meeting: Tokyo, Japan, June 1 – June 5, 2009
FCD Ballot: July 14, 2009 – November 14, 2009Meeting: Barcelona, Spain, January 18 – 22, 2010
Why ISO/IEC29157(PicoCast) is suitable for PSC service ? Container concept supports both low-power sensor & medium-speed multimedia. Abundant channel capacity due to avoidance of mutual interference. Provides broadcast, multicast & communication convergence protocol. Local broadcasting gives an additional business model such as advertisement. Adaptive common channel signaling supports mobile communication protocols.
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide32 PicoCast Forum
Upgrading Points for PSC Standard
ISO/IEC 29157 IEEE802.15.PSC
PHY
media 2.4G ISM, all ISM, low speed UWB, mm Wave
speed 1Mbps ~ 4Mbps (~ 16Mbps)
MAC
protocolP-P, Star, broadcast,
Multicast, multi-direct, broadcast relay
Sync relay, Mesh
PHY interface
Single Multiple
Container Hard Box,128bit preamble
Hard & Soft Box0 ~ 128bit preamble
APP
Message Sensor, Voice, Audio , Mobile Video
Location X ~ 10 cm
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide33 PicoCast Forum
Part 5Relationship between PSC and 5GThe value of PSC as mobile carrier
Dr. Yon C.H. Vice President of LG Telecom
doc.: IEEE 802. 15-10-0156-00-0psc
Submission
<March 2010>
Slide34 PicoCast Forum
Part 6 PSC Interest Group Schedule for PSC IG & SG Q & A
Mr. Murray P. Chairman PSC Interest Group