430 likes | 546 Views
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ PicoCast MAC Protocol ] Date Submitted: [8 March 2009]
E N D
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [PicoCast MAC Protocol] Date Submitted: [8 March 2009] Source: [S.M. Ryu, T.H.Kim, J.G.Han, D.Y.Kim, C.S.Eun, & H.S.Lee] Company [Casuh, CNU, PicoCast Forum, ETRI] Address [#813 Leaders B/D, 342-1, Bundang, Seongnam, Kyeonggi, 463-828, Korea] Voice: [+82-31-709-5577,+82-2-2082-1264, +82-42-821-6862], FAX: [+82-31-709-5578] E-Mail:[retaw@casuh.com, jhan@picocast.org, taehyung@casuh.com, dykim@cnu.kr, hsulee@etri.re.kr] Re: [Contribution to IEEE 802.15.6 Meeting, March2009] Abstract: [PicoCast MAC protocol support most of WBAN requirements. Container (Synchronous Frame Set) concept is suitable to support user oriented service convergence and avoid mutual interference. PicoCast single MAC can support multi PHYs and scalable different speed.] Purpose: [Proposal] 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.
PicoCast MAC Protocol March 2009 S. M. Ryu, T. H. Kim CASUH Corp. J. G. Han PicoCast Forum D. Y. Kim, C.S. Eun CNU H. S. Lee ETRI
Mark 4:3~9 (4:3) 『"Listen! A farmer went out to plant some seed.』 (4:4) 『As he scattered it across his field, some seed fell on a footpath, and the birds came and ate it.』 (4:5) 『Other seed fell on shallow soil with underlying rock. The plant sprang up quickly,』 (4:6) 『but it soon wilted beneath the hot sun and died because the roots had no nourishment in the shallow soil.』 (4:7) 『Other seed fell among thorns that shot up and choked out the tender blades so that it produced no grain.』 (4:8) 『Still other seed fell on fertile soil and produced a crop that was thirty, sixty, and even a hundred times as much as had been planted." Then he said,』 (4:9) 『"Anyone who is willing to hear should listen and understand!"』
Spread Spectrum History FH (Frequency Hopping) Bluetooth ECM (Electronic Counter Measure) CDMA ZigBee, GPS DS (Direct Sequence) SS (Spread Spectrum) EW (Electronic War) ECCM (Electronic Counter Counter Measure) Pulsed UWB TH (Time Hopping) AA (Adapted Antenna Array) ESM (Electronic Survailence Measure) 802.15.4a Orthotron Chirp Military : Anti-jamming PicoCast Commercial : High Capacity TDMA , OFDM
PMD: Physical Medium Dependent (radio) MAC_SAP: MAC Service Access Point PHY_SAP: PHY Service Access Point PLCP: PHY Layer Convergence Protocol PicoCast MAC Position
Hybrid Dual MAC Issues in WBAN Work Scope Medical Very high QoS Non-medical High Speed Arrange Requirements • List up user requirements • Check realizability • If no, reduce requirements APP Full Single MAC Challenges & Opportunities • Overcome Near / Far Interference • Single MAC for Multiple PHYs • Compromise power & speed • Medical / Non-medical dual support MAC Independent Multiple MAC 400MHz ~ Kbps 2.4GHz ~Mbps UWB ~10Mbps Choose existing technique • Select good chip • Enhance antenna matching • Reduce system size & Good design PHY • Add process gain for medical use
Solutions for Challenges 1. Near / Far Interference • Chg. : Even though different frequency bands interfere each other • Sol. : Synchronized Framecan 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 so wide user requirements • Sol. : Container Concept accommodates various information Boxes Synchronized Framecan support different PHYs without interference 3. Compromise Power & Speed • Chg. : Low power sensor and High speed multimedia should be supported • Sol.: Multi PHYconcept can support Multi RF Block Sensor use single RF Block, Multimedia use multi RF Block’s 4.Medical / Non-Medical Dual support • Chg.: Medical needs 10-10 BER performance with low speed • Sol.: 128bit Multi preamble provides enough Process Gain We can use 128bit multi preambles as 1 or 4bit data symbols
PicoCast MAC Protocol Features • Single MAC for Multiple PHYs (1,2,3,10,11,12,14) • Open structure for any PHY with the suggested interface. • Support time control for synchronized container concept. • Synchronized Container Concept(7,9,10,11,13,14) • Sensor, data, & multimedia box's can be shipped within a same container • Every same size container should be synchronized to avoid interference • Every container must reserve the first slot for the control box. • 128bit length Multiple Preambles(3,4,5,6,7,9,10,12,13,14) • 127 Preambles(128bits length) are used for different usages. • Emergency, short command, synchronization, priority, hand-over & etc • Support data integrity for important medical information as 1bit symbol • Hierarchical Code structure & Self Frequency Planning (1,6,7,8,9,13,14) • Group Code, Scan Code, & Security Code are used for various applications. • Scan Code supports sounding algorithm to choose the best frequency set. • Adaptive Common Channel Signaling (7,8,9,10,12,13,14) • 16 containers are composed to one vessel(256msec). • Control Boxes are used for adaptive common channel signaling
PHY(RF) independent MAC (Baseband) PicoCast MAC (Baseband) PHY #1 (RF #1) Basic Speed 1Mbps & 125Kbps Basic Container 16msec PHY #2 (RF #2) • • • PHY #N (RF #N) • PHY Type : 2.4G RF, UWB, WMTS, MICS, & etc. • PHY Interface : Synchronized Container Base • Basic Speed : 1Mbps (125Kbps for MICS) • Special Features : • Container Synchronized Interference Rejection • Scalable data rate depend on PHY
Support the operation of Box structure Box Size : 400 μsec ~ 15.2msec Basic Data Rate : 1Mbps Scalable Data Rate : 250K,500K,1M, 2M,4M,8M,16Mbps (option) Lock Time : Less than 500μsec (230μsec recommended) End of Box (EOB) : Less than 300μsec (40μsec recommended) Operation Mode : Tx / Rx / Idle / Sleep / Power-off Write Parameters : Frequency, Power Level Read Parameters : RSSI, Frequency Drift Clock Stability : Less than 20ppm PHY(RF) Requirements • Shall satisfy WBAN Requirement (TG6 Technical Requirements Document) • Special Requirements for low speed MICS Frequency • Basic Data Rate : 125Kbps • Minimum Box Size : 1.3msec (single Command Box) • Linear Modulation to achieve spread spectrum process gain • Control Box slot would be reserved for future usage
Example of PHY Interface with SPI 4 SPI PicoCast MAC (Baseband) PHY#1 (UWB) Command Register Data Buffer #1 Data Buffer SPI PHY#2 (2.4G) Command Register Data Buffer #2 Data Buffer SPI Command Register PHY#3 (MICS) Data Buffer #3 Data Buffer SPI PHY#4 (WMTS) Command Register Data Buffer #4 Data Buffer
Example of Multi RF Application • Frequency Diversity • High speed Tx with narrow band RF • Low Power Sensor uses single RF RF #1 f1 4M Frame Format Mux/ Demux RF #2 f2 4M RF combiner 12Mbps 16M RF #3 f3 4M RF #4 f4 4M 32MHz
Tx : 0dbm I2 Rx : -80dbm I1 Spurious :-60dbm Rx : -80dbm Tx : 0dbm I3 40dB 60dB 80dB UWB fO2 fI2 Near / Far Interference Search Frequency F C A F C M M O1 F C M F C A M M M A C F M C F O2 Shall not receive during other PHY is transmitting Frequency
Mutual Interference of existing solution Rx Rx Rx Rx Tx Tx Tx Tx Tx Rx Rx Rx Tx Tx Tx Rx M S1 S2 S3 S5 S6
Container R R T R R R T T R R R T R R T R T R T T T T T T R R R T T R R T R T R T R T R T How to avoid mutual interference M S1 S2 S3 S5 S6
Body Coordinator Mobile Femto-cell Body Master • Body coordinator is not a suitable concept. • Synchronous frames can reject mutual interference among RFs . • So, Body coordinator should synchronize all of body devices. • Better to rename body coordinator as “Body Master”.
Synchronized Container Concept Tx Rx Idle Rx Idle Rx Idle Idle Tx Idle Idle Idle Rx Idle Tx Tx Idle Rx Idle Rx Tx Rx Rx Rx Tx Tx Rx Rx Tx Rx Rx Rx Tx Rx Rx Tx Rx Rx S4 S1 P1 P2 M S2 P3 S5 S3 Body Master PHY # 1 PHY # 2 PHY # 3 • Avoid mutual interference among PHYs in body master • Shall not receive during other PHY is transmitting. • Transmit together at the same time. • Low speed MICS ignores control box time slot (Non Beacon Mode)
Paradigm Shift : User Oriented WiBro WSD WiBro WSD IPTV WBAN Ubiquitous WBAN IPTV Mobile VoIP RFID USN Infra Mobile VoIP RFID USN Mobile Phone DMB Mobile Phone DMB Provider Oriented User Oriented Users select among services broadcast by providers User terminals should meet provider specifications
Market Initiative WBAN Mobile Mobile Broad- casting Broad- casting Broad- casting IPTV Internet Femto Mobile Broad- casting Int er net Wired Mobile VoIP Wired Wired Home Appliance WLAN Wired Internet Wired Mobile IPTV Femto Mobile VoIP WLAN Body Master Mobile Internet WSD User oriented Ubiquitous Mobile Femto-cell WBAN WBAN
Mobile Femto-cell = Body Master ? Home Appliances PC Body Master IPTV Mobile Femto-cell = User Oriented Service Convergence Mobile Phone Femto-cell Wired
5G : Personal Mobile Space e d h C g A a B c b S f To reduce mutual interference, perfect synchronization is necessary Slide 21
Top level Sync Master 1st Level (GPS ?) White Space Base Station Base Station 2nd Level (Base Station) Fixed AP Fixed AP Fixed AP Mobile AP Mobile AP 3rd Level (AP) Body Master Body Master Body Master Body Master 4th Level (Mobile Femto-cell) Hierarchical Sync Structure HigherID Higher ID
GC8 GC1 GC1 GC2 GC8 GC4 GC26 GC2 GC3 128bit Multi Preambles Ubiquitous Cell Planning • 2-D • 3-D ubiquitous Self Organizing MAC is inevitable
False Alarm & False Dismissal Probability of 128bit preamble 64bit is not enough but 128 bit is high enough ; so we suggest multi Preamble
Sync Aide & Command Preamble Lock time Message EOB Header Suggested Frame Structure Multiple Preamble contains short message Multiple Preamble Structure Fixed Multiple Variable Sync Aide Preamble Lock time Message EOB Header Conventional Frame Structure
Basic Components of PicoCast MAC Vessel (256msec) # 7 # 1 #2 #3 # 4 # 5 # 6 #0 # 8 # 9 # 10 # 11 # 12 # 13 # 14 # 15 Container (16msec) Control Box Payload Box #1 Payload Box #2 Payload Box #n • • • Box Lock (AA) 128bit Preamble 40bit Tag AA Payload EOB Data Encryption PHY dependent constant parameter PHY dependent constant parameter
Example of Box Structure for different PHY 2msec 260μsec (…AA…) 84μ 128μsec 40μ 1480μsec 8μ Lock 128 bit Preamble Tag ‘AA’ Payload (185bytes) EOB 250K ~ 16Mbps 1Mbps Basic data rate for all PHY Scalable data rate 15msec 500μsec (…AA…) 292μ 1024μsec 384μ 12800μsec Lock 128bit Preamble Tag Payload (200bytels) EOB 125Kbps 1Kbps(Medical) / 125Kbps(Nonmedical) Basic data rate for low speed PHY Dual Mode data rate
Example of Control box structure 880 μ sec 128μsec 384μsec 48μsec 245μsec 75μ 1Mbps Basic data rate • Preamble : 128μsec : 128bits • Header : 48μsec : 4Bytes + CRC16 • Payload : 384μsec : 46Bytes + CRC16
Multiple Preamble Generator C0 = all ‘1’ C0 Add ‘0’ C1 1 < C1 (Scan Code) < 127 127bit Gold code Generation and ‘0’ insertion
Code Types Group encryption pattern generator 264 Data In Data Out Secure pattern generator 216
Code application for Box contents Scan Code Lock 128 bit Preamble Tag ‘AA’ Payload EOB 250K ~ 16Mbps 1Mbps Scalable data rate Basic data rate for 2.4GHz & UWB Group Code Security Code • Group Code is used for payload data only. • Different group can not communicate each other • 64bit ID of Master can be used as Group code • Security Code is set as ‘0’ for normal communication
Vessel (256msec) # 6 #0 # 1 #2 # 4 # 5 # 7 #3 # 10 # 11 # 12 # 8 # 13 # 14 # 15 # 9 BB1 BB2 TBD MACB / TBD RCB RACB MCB Control Box for normal Vessel • BB1 : Beacon Box 1, (Master Tx only) • BB2 : Beacon Box 2, (Master Tx, Rx Alternate for Sync Relay) • RCB : Request Control Box ; Contention permitted mode • MCB : Master Control Box • RACB : RCB Acknowledge Control Box • MACB : MCB Acknowledge Control Box
Vessel (256msec) # 1 #2 #3 # 4 # 5 # 10 #0 # 7 # 9 # 11 # 12 # 13 # 15 # 14 # 8 # 6 FBB0 FBB2 FBB4 FBB6 FBB8 FBB10 FBB12 FBB14 FBB3 FBB7 FBB11 FBB15 FBB1 FBB5 FBB9 FBB13 Control Box for fast sync Vessel • FBB : Fast Beacon Box • 16 frequencies are used for synchronization. • FBB use special preamble assigned for fast paring • Normally fast paring is done within 256msec • Within 1sec paring requirement is realizable
Normal Vessel (256msec) Fast Sync Vessel (256msec) # 6 # 7 # 8 # 15 # 10 # 4 # 11 # 13 #2 #0 # 14 # 12 #3 # 5 # 9 # 1 # 11 #2 # 14 #0 # 1 # 12 # 13 # 4 #3 # 6 # 7 # 8 # 9 # 10 # 15 # 5 FBB0 BB1 FBB2 BB2 FBB4 FBB6 FBB8 FBB10 FBB12 FBB14 TBD MACB / TBD Mode Exchange RCB FBB3 FBB7 RACB FBB11 FBB15 MCB FBB1 FBB5 FBB9 FBB13 Vessel Mode Change
MCB MCB MCB # 12 #0 # 1 #2 #3 # 4 # 5 # 6 # 7 # 8 # 9 # 10 # 11 # 13 # 10 # 15 #0 # 1 #2 #3 # 4 # 5 # 6 # 7 # 11 # 8 # 6 # 8 # 4 # 6 # 5 # 1 #3 #2 # 8 #0 # 15 # 14 # 7 # 12 # 9 # 10 # 11 # 12 # 13 # 14 # 15 #0 # 1 #2 #3 # 4 # 5 # 13 # 9 # 14 # 13 # 4 # 11 # 12 # 14 # 15 #0 # 1 #2 #3 # 7 # 6 # 7 # 8 # 9 # 10 # 11 # 12 # 13 # 14 # 15 #0 # 1 #2 #3 # 5 # 5 # 7 # 4 # 15 # 10 #3 # 8 # 9 # 10 # 11 # 12 # 13 # 14 # 15 #0 # 1 # 9 # 4 # 14 # 13 # 12 # 10 # 9 # 11 # 7 # 6 # 5 # 6 # 8 #2 MACB MCB MCB MACB MACB MCB M M P2 P1 MCB Operation Example S4 S1 P1 M S2 P2 S5 S3 MACB MACB S1 S2 S3 S4 S5
M # 14 # 15 # 6 # 7 # 8 # 9 # 10 # 11 # 12 # 13 # 14 # 15 Synchronized Accept Paring Normal Vessel # 11 #0 # 15 # 9 # 12 # 14 # 13 # 10 # 8 # 7 # 6 # 5 # 4 #3 #2 # 1 # 5 #2 #0 #3 # 5 # 6 # 4 #2 #3 # 1 # 1 #0 # 4 # 15 #0 # 1 #2 #3 # 4 # 5 # 6 # 7 # 8 # 9 # 10 # 11 # 12 # 13 # 14 # 15 S1 Scan Scan RCB Request Paring # 14 # 14 RACB RACB BB1 BB2 BB2 BB1 BB2 BB1 BB0 BB1 BB2 BB3 BB4 BB5 BB6 BB7 M # 14 # 15 # 7 # 8 # 9 # 10 # 11 # 12 # 13 # 14 # 15 #0 # 1 #2 #3 # 4 # 5 # 6 # 7 # 8 # 9 # 10 # 11 # 12 # 13 # 14 # 15 Fast Sync Vessel Request Paring Scan # 7 # 8 # 9 # 10 # 11 # 12 # 13 # 15 #0 # 1 #2 #3 # 4 # 5 # 6 # 7 # 8 # 9 # 10 # 11 # 12 # 13 # 14 # 15 S1 RCB Synchronized Accept Paring Paring Process • Full scan time of normal vessel is 2sec. • That of fast sync vessel is only 256msec
M S S Sync Data M Broadcasting Master / Slave S S S S S M S S S S M S S Multicast S S S S S S Direct Multi Channel Protocol Topologies - continued
S S S S M M S S S Convergence of Broadcasting & Communication S S S Broadcast Relay with Single Master S S S S S M S M S S M M S S S S S Sync Relay Protocol Topologies
Additional Considerations for WBAN • Open PHY Interface • Power Control • Smooth Sliding Sync • Role Exchange • QoS Check • Sounding • Emergency Flooding • Roaming / Hand-over • Sensor Mesh Relay Pico 3m 30m Femto Through Body 3m = Forward Body 30m
Conclusion • PicoCast protocol is submitted as asingle MAC for multiple PHYs. • Container concept to reject mutual interference and converge various services • Multi preamble to enhance synchronization probability & for special purposes • Hierarchical sync & code structure for scalable & self organizing system • Common channel signaling based on vessel structure for various service • Welcome Multiple preamble usage for special purpose like medical application • Suggested MAC can be used for 5G mobile communication, too. • WBAN body master & mobile femto-cell have almost same structure • In the future, the cell size of 5G will become femto-cell because of capacity • User oriented broadcasting and communication convergence is possible • White space devise requirements would be satisfied with PicoCast protocol • System evaluation tool and S/W driver can be supplied to PHY partners. • Technical sheet of PHY interface can be supplied to whom want to be partner • Evaluation board to test interoperability can be supplied as project base • Stable & reliable S/W library for single PHY is possible now • S/W library for multiple PHYs will be open within the end of this year
Thank You !!! Q & A Seung Moon Ryu Vice President, PicoCast Forum(www.picocast.org) CEO, Casuh Corp. (www.casuh.com) retaw@picocast.org +82-31-709-5577