doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 1 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Bridge-node Aided Universal Relay (BAUR) ] Date Submitted: [12 March, 2004] Source: [Po-Ning Chen, Cheng-En Hsieh, Hsung-Pin Chang (presentator), David Chang,Ping-Nan Wu, Ming-Chieh Chang, Ting-Chang Huang] Company [Notional Chiao Tung University] Address [1001 Ta Hsueh Road, Hsinchu, Taiwan 300, ROC ] Voice:[ ext:56656], FAX: [ ], Re: [] Abstract:[The document suggests some enhancement points about the inter- and intra-piconet relaying for 15.3b.] Purpose:[For discussion to add universal relay across the piconets.] Notice:This document has been prepared to assist the IEEE P 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 P

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 2 Bridge-node Aided Universal Relay [BAUR] March, 2004

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 3 Abstract We propose a universal approach that can simultaneously achieve both inter- and intra- piconet relaying. Our scheme can inter-relay packets across piconets without knowing the locations of the devices. Our scheme is backwardly compatible to IEEE draft standard.

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 4 DD Global topology The blue color represents the packets existing in 15.3 The brown color represents the packets proposed to be modified The red color represents the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 5 Global topology PP The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 6 Global topology PP The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 7 Global topology PP D D D The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 8 Global topology PP D D D Remote scan request 2 Command type 2 Length (=n) 1 Channel 1 1 Channel 2 … … octets:1 Channel n The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 9 Global topology PP D D D Remote scan request Remote scan response 2 Command type 2 Length (=6+m) 1 Reason code 1 Number of channels m Channel rating list 1 Number of piconets 2 Remote piconet description set Octets:1 Optional IE The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 10 Global topology PP D D D Register other piconet request Register other piconet request command 2 Command type 2 Length (=4) 1 PNID 1 Channel index The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 11 Global topology PP D D D Register other piconet request Association Request Association request 2 Command type 2 Length (=20) 8 DEV address 7 Overall capabilities 2 ATP 1 DEV utility octets:2 Life time The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 12 Global topology PP D D D Register other piconet request Association Request Association Response Association response 2 Command type 2 Length (=12 or 12+L n ) 8 DEV address 1 DEVID 2 ATP 1 Reason code octets: 0 or L n Vendor specific IE The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 13 Global topology PP D D D Register other piconet request Association Request Association Response Register other piconet response 2 Command type 2 Length (=4) 1 Reason Code The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 14 R Global topology PP D D The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 15 R Global topology PP D D Broadcast Piconet info Broadcast piconet info 2 Command type 2 Length (=10n+8+1) 8 DEV1 address 8 DEV2 address 8 DEVn address … … 2 DEV1 life time 2 DEV2 life time 2 DEVn life time The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 16 R Global topology PP D D Broadcast Piconet info Broadcast piconet info 8 Relay address octets:1 Hop no. count 1 Max hop no. 2 Relays min life time The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 17 R Global topology PP D D Broadcast Piconet info The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 18 R Global topology PP D D Relay _addressDEV_addressHop number Relay1_addrPNC2_DEV1_addr3 Relay1_addrPNC2_DEV2_addr3 Relay1_addrPNC2_DEV3_addr4 Relay2_addrPNC3_DEV1_addr2 Relay2_addrPNC3_DEV2_addr3 Relay2_addrPNC3_DEV3_addr1 Relay3_addrPNC4_DEV2_addr2 ……… Life time … Relay _addressDEV_addressHop number Relay1_addrPNC2_DEV1_addr3 Relay1_addrPNC2_DEV2_addr3 Relay1_addrPNC2_DEV3_addr4 Relay2_addrPNC3_DEV1_addr2 Relay2_addrPNC3_DEV2_addr3 Relay2_addrPNC3_DEV3_addr1 Relay3_addrPNC4_DEV2_addr2 ……… Life time … Relay _addressDEV_addressHop number Relay1_addrPNC2_DEV1_addr3 Relay1_addrPNC2_DEV2_addr3 Relay1_addrPNC2_DEV3_addr4 Relay2_addrPNC3_DEV1_addr2 Relay2_addrPNC3_DEV2_addr3 Relay2_addrPNC3_DEV3_addr1 Relay3_addrPNC4_DEV2_addr2 ……… Life time …

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 19 Local topology P D D D The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 20 Local topology P D D D association request The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 21 Local topology P D D D association request Association response The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 22 Local topology P D D D beacon The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 23 Local topology P D D D probe request Probe request 2 Command type 2 Length (=6) 4 Information requested octets:2 Request index The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 24 Local topology P D D D probe request ACK The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 25 Local topology P D D D D1 The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 26 Local topology P D D D D1 probe request The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 27 Local topology P D D D D1 probe request ACK The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 28 Local topology P D D D D1D2 The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 29 Local topology P D D D D1D2 Local topology info 2 Command type 2 Length (=n) 1 DEV1 1 DEV2 … … 1 DEVn Local topology info The blue color = the packets existing in 15.3 The brown color = the packets proposed to be modified The red color = the newly added packets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 30 Local topology P D D D dev1dev2dev3dev4dev5dev6 dev1-xxxox dev2o-xxxx dev3xx-xox dev4xxx-xx dev5xoox-x dev6oxxxx- dev1dev2dev3dev4dev5dev6 dev1-xxxox dev2o-xxxx dev3xx-xox dev4xxx-xx dev5xoox-x dev6oxxxx-

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 31 Intra-Piconet Relay PNC Src DEV Imm DEV Target DEV Universal CTRq Universal channel time request 2 Command type 2 Length(=sum of n Remote CTRqBs) 18 Universal CTRqB-1 18 Universal CTRqB-2 … … 18 Universal CTRqB-n

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 32 Intra-Piconet Relay PNC Src DEV Imm DEV Target DEV Universal CTRq Universal CTRqB 8 Target Address 1 DSPS set index 1 Stream Request ID 1 Stream index 1 CTRq control 2 CTA rate factor 2 CTRq TU 1 Min no. of TUs Octets:1 Desired no. of TUs

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 33 Intra-Piconet Relay PNC Src DEV Imm DEV Target DEV Universal CTRq IntraPico Relaying request InraPico Relaying Request 2 Command type 2 Length (=4) 1 Source stream index 1 Relaying stream index

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 34 Intra-Piconet Relay PNC Src DEV Imm DEV Target DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response IntraPico Relaying Response 2 Command type 2 Length (=4) 1 Reason code

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 35 Intra-Piconet Relay PNC Src DEV Imm DEV Target DEV Universal CTRq IntraPico Relaying request Universal CTRp response IntraPico Relaying response Universal Channel time response 2 Command type 2 Length (=4) 1 Stream Request ID 1 Stream index 1 Available number of TUs octets:1 Reason code

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 36 Intra-Piconet Relay PNC Src DEV Imm DEV Target DEV Universal CTRq IntraPico Relaying request Universal CTRp response IntraPico Relaying response

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 37 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV PNC Imm DEV

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 38 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq PNC Imm DEV

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 39 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq IntraPico Relaying request PNC Imm DEV InterPico Relaying request InterPico Relaying Request 2 Command type 2 Length (=17) 8 Target Address 2 Source Stream index 1 CTRq control 2 CTA rate factor 2 CTRq TU 1 Min no. of TUs Octets:1 Desired no. of TUs

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 40 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response PNC Imm DEV InterPico Relaying request

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 41 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response PNC Imm DEV Universal CTRq InterPico Relaying request

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 42 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response PNC Imm DEV Universal CTRq IntraPico Relaying request InterPico Relaying request

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 43 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response PNC Imm DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response InterPico Relaying request

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 44 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response PNC Imm DEV Universal CTRq IntraPico Relaying request Universal CTRp IntraPico Relaying response InterPico Relaying request

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 45 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response PNC Imm DEV Universal CTRq IntraPico Relaying request Universal CTRp IntraPico Relaying response InterPico Relaying request InterPico Relaying response InterPico Relaying Response 2 Command type 2 Length (=4) 1 Reason code

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 46 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response PNC Imm DEV Universal CTRq IntraPico Relaying request Universal CTRp IntraPico Relaying response InterPico Relaying request InterPico Relaying response Universal CTRp response

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 47 Inter-Piconet Relay Src DEV Target DEV PNC Imm DEV Relay DEV Universal CTRq IntraPico Relaying request IntraPico Relaying response PNC Imm DEV Universal CTRq IntraPico Relaying request Universal CTRp IntraPico Relaying response InterPico Relaying request InterPico Relaying response Universal CTRp response

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide On Demand Relay Route Discovery command 2 Command type 2 Length (=8n+27) 8 Sour Address 1 Time to live 2 Seq. no. 8 Relay1 address 8 Relay2 address … … 8 RelayN address 8 Des. Address

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide On Demand Relay Route Discovery command 2 Command type 2 Length (=8n+27) 8 Sour Address 1 Time to live 2 Seq. no. 8 Relay1 address 8 Relay2 address … … 8 RelayN address 8 Des. Address

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide On Demand Relay Route Discovery command 2 Command type 2 Length (=8n+27) 8 Sour Address 1 Time to live 2 Seq. no. 8 Relay1 address 8 Relay2 address … … 8 RelayN address 8 Des. Address

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide On Demand Relay Route Discovery command 2 Command type 2 Length (=8n+27) 8 Sour Address 1 Time to live 2 Seq. no. 8 Relay1 address 8 Relay2 address … … 8 RelayN address 8 Des. Address

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide On Demand Relay Route Response command 2 Command type 2 Length (=25+8n) 8 Update Address 8 Relay1 address 8 Relay2 address … … 8 Relay1 address

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide On Demand Relay Route Response command 2 Command type 2 Length (=25+8n) 8 Update Address 8 Relay1 address Update table

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide On Demand Relay Route Response command 2 Command type 2 Length (=25+8n) 8 Update Address Update table

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 55 New Packets: Register other piconet request command Sent by a PNC to indicate a DEV to register other piconets PNID field – PNC ask DEV to register the other piconet with this PNID Channel index field – the channel in which the other piconet resides in. 2 Command type 2 Length (=4) 1 PNID 1 Channel index

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 56 New Packets: Register other piconet response command Sent by a DEV to indicate the result of the registration Reason Code –0->success –1->channel index failure –2->PNID not find –3->no relaying capability –4~255->Reserve. 2 Command type 2 Length (=4) 1 Reason Code

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 57 New Packets: Broadcast piconet info Sent by a PNC to the relaying DEVs to inform other PNCs about the DEVs under its converage Relay address : once a intermediate relaying node receive this packet, it overwrite its address onto this field. Max hop no. : the maximum number of hops allowable. Hop no. count : the number of hops the packet experienced. DEVn life time : the time that the relay node is anticipated to stay in his piconets

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 58 New Packets: Broadcast piconet info (Cont.) 2 Command type 2 Length (=10n+8+1) 8 DEV1 address 8 DEV2 address 8 DEVn address … … 2 DEV1 life time 2 DEV2 life time 2 DEVn life time 8 Relay address octets:1 Hop no. count 1 Max hop no. 2 Relays min life time

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 59 New Packets: Local topology info Sent by a DEV to a PNC to tell its neighbor DEVs DEVn – the device that is in range of the sending device. 2 Command type 2 Length (=n) 1 DEV1 1 DEV2 … … 1 DEVn

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 60 New Packets: Universal channel time request Sent by a DEV to a PNC to ask for channel time allocation The same as the CTRq command except that –Target Address:change from device ID to its physical address 2 Command type 2 Length(=sum of n Remote CTRqBs) 18 Universal CTRqB-1 18 Universal CTRqB-2 … … 18 Universal CTRqB-n

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 61 New Packets: Universal channel time response Sent by a PNC to a DEV to indicate the result of universal channel time request Universal channel time response packet is as same as Channel time response in 15.3 draft.

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 62 New Packets: IntraPico relaying request Sent by a PNC to a DEV to ask it for intrapico relaying Source Stream index Relaying Stream index 2 Command type 2 Length (=4) 1 Source stream index 1 Relaying stream index

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 63 New Packets: IntraPico Relaying Response Sent by a relaying DEV to a PNC Reason code –0->success –1->failure –2~255->Reserved 2 Command type 2 Length (=4) 1 Reason code

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 64 New Packets: InterPico relaying request Sent by a PNC to a DEV to ask it for interpico relaying Target Address Source stream index CTRq control : remove PM CTRq type, CTA type, Target ID list type CTA rate factor CTRq TU Minimum number of TUs Desired number of TUs 2 Command type 2 Length (=17) 8 Target Address 2 Source Stream index 1 CTRq control 2 CTA rate factor 2 CTRq TU 1 Min no. of TUs Octets:1 Desired no. of TUs

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 65 New Packets: InterPico relaying response Reason Code –0->success (packet switch) –1->success (circuit switch) –2->Cannot request channel time –3~255->Reserve

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 66 New Packets: Route discovery Sent by a PNC to a relay DEV to find a routing path Source Address the address of the device who intends to send packets Destination Address the address of the target device that the source-address device wishes to locate. Time to live how long does the packet live in the network. Sequence number a unique number Relayn address Relay node appends its address to this packet. 2 Command type 2 Length (=8n+27) 8 Sour Address 1 Time to live 2 Seq. no. 8 Relay1 address 8 Relay2 address … … 8 RelayN address 8 Des. Address

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 67 New Packets: Route response Sent by a DEV to a PNC Update address equal to the destination address in the Route request packet RelayN response path 2 Command type 2 Length (=25+8n) 8 Update Address 8 Relay1 address 8 Relay2 address … … 8 Relay1 address

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 68 Packets Modified Association request 2 Command type 2 Length (=18) 8 DEV address 7 Overall capability 2 ATP 1 DEV utility Overall capability 4 PNC capabilities 3 DEV capabilities DEV capability octets:2 Life time b4-b0 Supported data rates b7-b5 Preferred fragment size b8 Always AWAKE b9 Listen to Source b10 Listen to Multicast b11-b13 Total relay no. b14-b16 Current relay no. b23-b17 Reserved

doc.: IEEE b Submission March, 2004 Po-Ning Chen et al, NCTUSlide 69 Packets modified Association request –Life time the time that the DEV is anticipated to stay in his piconets –Total relay number the most allowable registration times –Current relay number the current registered number of times