1. Contents p Opportunity for Wireless in 1394 p Proposals p Loose Coupled Bridge p Subnet Architecture p Addressing Scheme p Routing Scheme p Net Management Scheme p Conclusion

2. SONY CORPORATION Wireless - As a New Medium p Cable (Twisted Pair) p POF p Coaxial (?) p Wireless p Implement Wireless Without Significant Impact to the Current Specifications p Need Clear and Neat Solution Possibility in P1394.1 With Minimal Modification Without Describing “Wireless” Specification

3. SONY CORPORATION Wireless System Overview ABCDEFGHIJKLMNOPQ RSTUVWXYZ abcdefghijklmnopq Computer TV Satellite CATV Printer Monitor DVD VCR Audio (CD) Monitor ISDN

4. SONY CORPORATION Hurdles for Wireless p Unexpected Disconnection p Transmission Errors p “Bus” May Not be Achieved p All the Nodes May Not be Seen Directly p Limited Frequency Resources p Bandwidth Limitation p Efficient Use of Frequencies Required

5. SONY CORPORATION IEEE1394 Cable Node Wireless System IEEE1394 Bridge Node IEEE1394 Cable IEEE1394 Cable Portal Bridge has Three Portals In this case Node Implementation Plan p To Guarantee the Transparency to IEEE1394, Wireless System Need to be Defined as 1394-1394 Bridge p Wireless Environment is Bridge Inner Fabric From Cable IEEE1394 Point of View

6. SONY CORPORATION Wireless System 1394 Bus Bridge Architecture 1394 Bus 1394-Wireless Bridge 1394Node Wireless Node 1394-Wireless Bridge 1394Node Wireless Node 1394-Wireless Bridge 1394Node Wireless Node 1394-1394 Bridge ( Logical ) : Expected Hardware

7. SONY CORPORATION Implementation As Bus v.s. Fabric p Bus Causes Discrepancies Such As : p Requires A New Environment Other Than Cable or Backplane p Does Not Allow “Delay” p Bandwidth Acquisition for Isochronous Depends on Wireless Path p Fabric Requires : p To Support Portal Disconnection p Multiportal Bridge Wireless Bridge Wireless

8. SONY CORPORATION Proposal-1: Loose Coupled Bridge p Define Two Type of Bridges p Tight Coupled Bridge : 2-Portal p Conventional Bridge Between Buses p Loose Coupled Bridge : with Multiportal p Supports Disconnected State p Covers Even Distributed Bridge (ex. Located in Separate Room) portal #0portal #1portal (n-1) Fabric Wireless portal #0portal #1 Fabric Tight Loose

9. SONY CORPORATION Why Multiportal ? Wireless System Example Multiportal Solution2-portal Solution Multiportal Solution is Simpler Reduce the Load of : - Isochronous Owner - Bridge Manager Wireless Routing is Concealed in Multiportal Solution

10. SONY CORPORATION Proposal-2 : Subnet Architecture  Hierarchy : Net  Subnet  Bus  Node Net Subnet B Bus Loose Coupled Bridge Tight Coupled Bridge Wireless Subnet ASubnet C

11. SONY CORPORATION Advantages of Subnet Architecture p Localize the Net Configuration with Loose Coupled Bridge Between Subnets 0 1 2 3 0 1 2 3 1414 0505 2626 3737 0 1 2 3 0 1 2 3 Subnet #1 Subnet #2 0 1 2 3 0 1 2 3 Bridge Manager Subnet Manager Subnet #1 Subnet #2 Example : Net Topology Transition 0 1 2 3 5 4 6 7 4141 5050 6262 7373 0 1 2 3 0 1 2 3 Subnet #1 Subnet #2

12. SONY CORPORATION Addressing Scheme Bus 2 Bus 0 Bus 1 Bus 2 Bus 1 Bus 0 Bus 3 Bus 1 Bus 0 Net Subnet 2 Subnet 1 Subnet 3 p subnet_ID : 5bit p Max 31 Subnets in a Net ( 0 - 30 ) p Reserve Subnet_ID=31 for Broadcast p bus_ID : 5bit p Max 31 Buses in a Subnet ( 0 - 30 ) p Reserve bus_ID=31 for Broadcast p physical_ID : 6 bit bus_ID physical_ID bus_IDsubnet_ID

13. SONY CORPORATION Routing Scheme p “Bit Mapped Register” Instead of “Routing Bound Register” p Splitting into Two 5 bit Assignment Enables Sequential Mapping p Routing Bound Need to Consider the Topology p No Need to Reassign the IDs When the Topology is Changed No Interruption When the Topology is Changed Import : 1 Ignore : 0 Bit (bus/subnet_ID ) Bus Routing Subnet Routing 0 1 2 3 4 31 0 0 1 1 0 1 0 1 1 0 0 1 Tight Coupled Bridge Routing Table Loose Coupled Bridge Routing Table Bit (subnet_ID) Import Routing Export Routing 0 1 2 3 4 31 0 0 1 1 0 1 0 1 1 0 0 1 Accept : 1 Ignore : 0

14. SONY CORPORATION Routing Example 0 1 22 0 2 1 0 3 0 1 2 1 0 2 1 (0,0,0) Bus #0 Bus #1 Bus #0 Subnet #0 Subnet #1 Subnet #3 Subnet #2 (3,0,1) Packet Transmission From (0,0,0) To (3,0,1) 0100 0111 ---1 1 0 1 2 3 31 1101 0010 ---1 1 0 1 2 3 31 0111 1000 ---1 1 0 1 2 3 31 1110 0001 ---1 1 0 1 2 3 31 0001 1110 ---1 1 0 1 2 3 31 Bus Rt. Subnet Rt. Import Rt. Export Rt. Tight Coupled Bridge Loose Coupled Bridge ER IR 1010 0101 ---1 1 0 1 2 3 31 ER IR ER IR ER IR (0,0,2) (0,1,1) (1,0,2) (1,0,1) (3,0,2)

15. SONY CORPORATION p Subnet Manager in Every Subnet p Net Manager in the Net Net Management Net Subnet Manager Net Manager

16. SONY CORPORATION Subnet / Net Manager’s Tasks p Subnet Manager’s Tasks p bus_ID Assignment p Routing Configuration in the Subnet p Subnet Cycle Master Selection ( To Be Proposed) p Cycle Transfer Configuration in the Subnet ( To Be Proposed) p Net Manager’ Tasks p subnet_ID Assignment p Inter-Subnet Routing Configuration p Net Cycle Master Selection ( To Be Proposed) p Cycle Transfer Configuration in the Net ( To Be Proposed) p Maximum Number of Nodes Need to be Handled Became 1/32

17. SONY CORPORATION Conclusion p Loose Coupled Bridge p Subnet Architecture p Addressing Scheme p Routing Scheme p Net Management Scheme

18. SONY CORPORATION 8 6 7 5 4 bus_ID Assignment in a Subnet 0 1 3 2 7 6 4 5 0 1 3 2 7 6 4 5 0 1 3 2 7 6 4 5 8 0 1 3 2 new APPENDIX

19. SONY CORPORATION Net Configuration Impact p In a Large Net with Many Buses, Re-configuration May Occur Frequently p Transactions are Interrupted or Some Troubles may happen Configuration Starts （ Bus Addition/Removal ） Configuration Propagates APPENDIX

20. SONY CORPORATION Net Configuration Impact - cont’d p Net Configuration May Causes a System Trouble p Some Systems May Need to be Isolated Configuration PCs and the Peripherals Should be Isolated from Suffering Frequent Configurations APPENDIX