1. CCN CCN Central Control Network midterm presentation Winter & Spring 2002/03 Student : Kormas Tal Guide : Gerber Alex

2. CCN CCN - motivation Many systems around the world use central computer for security devices (such as entrance and security cameras). Most of the devices are low resource requires and so many could be connected to one computer. We would like to take advantage of the USB port speed and availability, and implement multiple area network (a separate bus for each area) connected to it.

3. 3 CCN - functional Devices Data base Internet Users

4. 4 CCN – project definition This project is mainly about securing a site. It should be designed to work with a large number of devices,both low resource (sensors) and high resource (cameras). It should be hmulti-user (domains), user-friendly and secure software controlling. Data should be inserted/fetched efficiently. Devices could control each other (i.e. if a card reader reads correct user, it should be able to open the door using the door opener).

5. 5 CCN - Interfaces There are 3 main interfaces on this project: 1) devices interface with the network bus using CAN protocol (ISO/IS 11898-2 ) 2) buses interface with the PC using USB protocol. 3) users interface with the PC and data using TCP/IP protocol.

6. CCN CCN – network rates CAN bus : the CAN uses ISO/IS 11898-2 physical layer, so it’s bit rate is up to 125KB/sec. The connection to the computer is USB, and if we assume we use USB 1.1, we could reach up to 12MB/sec (with more then one CAN bus, of course).

7. 7 CNN – spec Since CAN bus can support 1024 devices, and it’s throughput is 1MB/sec. And Since USB 1.1 (slow) can support 12MB/sec. And Since there is no limit to hub usage. We could support up to 12 full buses (or more if it’s not full), or 12K devices. TCP/IP rates are network based (since each user could be connected in a different speed).

8. USB HUB תור FIFO עם זכרון CAN BUS CAN to USB & Can Master CCN CCN – block diagram view אלמנט תקשורת ושליטה

9. 9 CCN – Test Spec The project should be checked using a know working devices. It should have at least 2 device on each bus. It should have at least 2 buses connect. It should have at least 1 user connected. I should check both user connection and data fetch correctness, and admin data fetch correctness.

10. CCN CCN – main idea Each device uses bus interface to connect a CAN bus. Each level/area have it’s own bus. All buses controlled by a master device, which also convert the CAN protocol into USB protocol. All the Can Masters outputs (USB) are connected to a USB Hub (which is power supplied, so the net will keep working when communication to the computer N/A). The hub connected to a memory unit for keeping the data in a FIFO line if the computer is down.

11. 11 CCN – main idea (cont) The data from the devices is inserted to a Database on the computer side. The users connect to the computer and login. Each user have links to is devices. The user can look on the data received from his device and configure them, according to his permissions. As a conclusion : The project is a very interconnected with other devices, both networked (CAN/TCP/USB) and both functionality (door opener/cameras and etc.)

12. 12 CCN – why not… Why not single user? Single user cannot secure a large site, we want to allow more users, each securing a smaller area. Why not single bus? Single bus won’t allow large number of devices, and we’ll be limited by CAN max throughput.

13. 13 CCN – why not…(cont) Why using hub and memory element? since we are limited on the number of USB’s connectors to a single computer -> HUB. Since we would like in order messaging even when the computer is down, we’ll use the memory element to save them.

14. 14 CCN - equipment The PC must have at least USB1.1 free slot. The USB HUB must be Power supplied in case the computer is down. Each CAN bus must have a CAN2USB connector. Each device must have a CAN controller (so it won’t collide with other devices).

15. 15 CCN – Software functionality The software should handle inserting and fetching of data from the Database. The software should handle data from the devices (i.e. if a card reader read a legitimist user, open the connected door). The software should handle user logins (secured). It should show irregularities for the user’s devices. The software should handle users data requests. The software should allow adding devices/users and connect them (devices to devices, and devices to users).

16. 16 CCN – Devices 1.Input : CAN packet p. 2.IF p.data.cont then 3. Act recording to the data(add/remove). 4.ELSE 5. db.(p.dev).data(time) = p.data 6. if(irreg(db.(p.dev))) do db.(p.dev).irlist 7. else if(ok(db.(p.dev))) do db.(p.dev).oklist 8. else do db.(p.dev).failist 9.End if 10.return

17. 17 CCN - Users 1.Inputs : username u, MD5(password) p 2.If(! correct(u,p)) return “incorrect login” 3.Build_page(db.users.u) 4.Return “redirecting to “u” personal page” Build_page: this function gets the user’s line on the DB and build a page out of it (help him look for irregularities and change his devices variables).

18. 18 CCN - Users database Database for users contain the following data for each user: 1.personal details 2.Username 3.MD5(password) 4.list of cams 5.list of sensors 6.Ugroup 7.is_manager

19. 19 CCN – Devices database Database for device contains the following data for each device: 1.device name 2.configures (i.e. good time, legal users list) 3.list of devices for irregularities. 4.list of devices for legal operations 5.list of devices for illegal operations. 6.Actual data from the device (by date and time).

20. 20 CCN – implementation notes The computer OS: windows 2000 I’ll use C# to implement the software, and Microsoft SQL Server for the database. I’m going to use the SQL server to also log the operation made by the users for the administration side. NOTE : there is special user “admin” which will have a different kind of page, and could control all users and devices. He is the manager of the system.

21. 21 CCN – Software checks I shell check my software as follow: 1)Devices work : check that I get the messages on the bus. 2)Database insertion work: check that when a device message receive, it’s inserted to the right place on the database. 3)Users logins : check that the password entered by the user doesn’t leave his computer (on the hash on it does). Then check that he login correctly. Need to check that he receive the right page. 4)Users management : see that only admin users could add/remove devices for there group. See that users can’t use the system to “become” somebody else.

22. 22 CCN – what already done הפרוייקט אופיין הוזמנו חלקים עבור שלב א של הפרוייקט תיאור התוכנה הושלם התחלת צבירת ידע בשפת התכנות ורקע בנושא מסדי נתונים. הוכנו מצבורי ידע בנושאי התוכנה (כמו הגנת אתרים וכו').

23. CCN – part 1 timetable חיבור מחשב ל CAN דרך USB: עד 31.12.02 הקמת רשת בסיסית (Master-Slave) : עד 10.12.02 הקמת רשת : שילוב תוכנה חומרה: עד 24.01.03 הרחבת התוכנה ובדיקת הקמת אלמנט הזיכרון : עד 31.3.03 אם הוחלט על בניית אלמנט זיכרון : איפיונו והכנת סכמה עד 21.4.03, הרכבתו ודיבוגו : עד 31.5.03, חיבור ואינטגרציה : עד ה 25.6.03. אם הוחלט לא להרכיב את אלמנט הזכרון: המשך הרחבת התוכנה עד ה 25.6.03