The Museum Project The Museum Project Yoav Gvili & Asaf Stein Supervisor : Alexander Arlievsky

Click here to load reader

  • date post

    19-Dec-2015
  • Category

    Documents

  • view

    213
  • download

    1

Embed Size (px)

Transcript of The Museum Project The Museum Project Yoav Gvili & Asaf Stein Supervisor : Alexander Arlievsky

  • Slide 1
  • The Museum Project The Museum Project Yoav Gvili & Asaf Stein Supervisor : Alexander Arlievsky
  • Slide 2
  • Introduction The museum project idea is to supply museum visitors with a private guide to guide them through their museum tour. The museum project idea is to supply museum visitors with a private guide to guide them through their museum tour. Every visitor of the museum will be able to rent a P.D.A at the entrance. Every visitor of the museum will be able to rent a P.D.A at the entrance. From this moment the visitor (our user) can interactively use the P.D.A as his private guide. From this moment the visitor (our user) can interactively use the P.D.A as his private guide.
  • Slide 3
  • Product Advantages A personal guide for each user. Dynamic. Interactive. Modular.
  • Slide 4
  • Project Goals Research - Blue Tooth. Research - Blue Tooth. Is it possible? Is it possible? Implementation of suitable server client & Data Base application. Implementation of suitable server client & Data Base application.
  • Slide 5
  • The Project demands
  • Slide 6
  • Client features: Client features: The client will be able to get the following services: - Map: a map of the museum rooms + The clients current position. Room: subject of room + links to exhibits. Exhibits: picture + text. General information: about the Museum and its facilities. SMS: connections client-to-client, client to group. Tour select: Choose a tour by field of interest.
  • Slide 7
  • Server Features: Server Features: - The server will support all the clients feature. Management & maintenance features: Management & maintenance features: - Map control: maintenance of map feature. - Map control: maintenance of map feature. - Room control: Add Room, Remove Room, Modify Room. - Room control: Add Room, Remove Room, Modify Room. - Exhibit control: Add Exhibit, Remove Exhibit, Modify Exhibit. - Exhibit control: Add Exhibit, Remove Exhibit, Modify Exhibit. - Groups: Add Group, Add Member, Remove Group, Remove Member. - Groups: Add Group, Add Member, Remove Group, Remove Member.
  • Slide 8
  • Project Architecture The way to achieve the needed services is to build a wireless connection between the P.D.As (the Users) and the museum server. The way to achieve the needed services is to build a wireless connection between the P.D.As (the Users) and the museum server. The sever holds a Data Base with all relevant information and manage connection with the P.D.As (the clients). The sever holds a Data Base with all relevant information and manage connection with the P.D.As (the clients).
  • Slide 9
  • Application Server & Http server are needed Every room may contain one or more wireless pico nets. Bluetooth units of all Rooms are connected to LAN Every client has a Bluetooth unit
  • Slide 10
  • Bluetooth
  • Slide 11
  • Research Main Conclusions The piconets will work in the Master Slave format. The static devices will be Masters, the clients will be Slaves. Direct communication between slaves will not be allowed. Each piconet build of one Master & 7 slaves. Each piconet can hold up to ~200 clients in Park Mode (like sleep). It is possible for a few piconets to work in the same room.
  • Slide 12
  • Research Main Conclusions (cont.) Each client will get it's own IP number on the net. The client will get a new IP on each time it will become an active member of a piconet. The static device (Master) will assign the IP for the client. Masters of each Room will have fixed IP numbers that belongs only to the specific Room.
  • Slide 13
  • Research Main Conclusions (cont.) In addition to IP each client will get a static ID (that will stay the same during all the visit). *** It is advisable to have a central unit for every few rooms in order to decrease the transmission over the net. This unit will supply Data that deals with the few neighbor rooms. (We repeatedly supply this data all the time with no changes).
  • Slide 14
  • Ethernet vs. Bluetooth Bluetooth : 1 M bit/sec 1 M bit/sec Wireless connection Wireless connection 7 users per pico net (max). 7 users per pico net (max). P(Error) P(Error) Ethernet : 10 / 100 M bit/sec 10 / 100 M bit/sec Point to point connection Point to point connection Number of clients limited by connection points Number of clients limited by connection points P(Error) P(Error)
  • Slide 15
  • Http Server Since a part of the clients GUI (touring the museum) is a Web Browser - > an Http server is needed to the project. Since a part of the clients GUI (touring the museum) is a Web Browser - > an Http server is needed to the project. The HTTP server is a regular http server that provides data on demand. The HTTP server is a regular http server that provides data on demand. On initialization the server must be set the root path for the museum web pages. On initialization the server must be set the root path for the museum web pages. All the other data is a regular HTTP server data No special attributes. All the other data is a regular HTTP server data No special attributes.
  • Slide 16
  • Application Server Design This Server manages This Server manages communication with all clients. It is basically divided into three layers: It is basically divided into three layers: - Application - Routing - COM
  • Slide 17
  • Data Base bla
  • Slide 18
  • Client Design The client is also divided into three layers: The client is also divided into three layers: - Application - Application - Context - Context - COM - COM
  • Slide 19
  • Connection steps 1. connect to wall. 2. get IP. 3. connect to museum server. 4. Get waiting messages or Group info response. 5. Browsing.
  • Slide 20
  • The Clients Cache The cache is used The cache is used By the clients Browser. It holds the recent HTML files that were visited by the client. It also support the option to browse BACK. It also support the option to browse BACK.
  • Slide 21
  • Communication In our project all the communication works In our project all the communication works threw LAN. The Protocol we use is TCP/IP. The Protocol we use is TCP/IP. In order to make the connection between In order to make the connection between clients and application server possible we had to create a specific protocol for our application.
  • Slide 22
  • The Application Protocol This protocol is a packet protocol. This protocol is a packet protocol. It is used mostly for clients requests from server: It is used mostly for clients requests from server: - Establish client / server connection. - Establish client / server connection. - Close the above connection. - Close the above connection. - Send a text message request. - Send a text message request. - Room information request. - Room information request. - Group information request. - Group information request.
  • Slide 23
  • The Packet Format:
  • Slide 24
  • Project Algorithms Client connection and receive algorithm Client connection and receive algorithm
  • Slide 25
  • Client Send message algorithm Client Send message algorithm
  • Slide 26
  • Client connection to Server Client connection to Server
  • Slide 27
  • Client handler Algorithm Client handler Algorithm
  • Slide 28
  • Message handling Algorithm Message handling Algorithm
  • Slide 29
  • GUI The Administrator manages the adding and removing of groups and single clients, he can add and remove a group, add client to a group, add or remove a single client group. The Administrator cannot change part fo the group after the group is created. The Administrator manages the adding and removing of groups and single clients, he can add and remove a group, add client to a group, add or remove a single client group. The Administrator cannot change part fo the group after the group is created. The Administrator have the following panels to manage group The Administrator have the following panels to manage group
  • Slide 30
  • 1.Activates the Add new group dialog 2.Activates the Add single client dialog 3.Activates the Remove group dialog 4.Activates the Remove single client dialog 5.Quit program application main window application main window 1 2 5 3 4
  • Slide 31
  • Add new group dialog in this dialog you can add a new group to the data base with all its clients
  • Slide 32
  • Add single client dialog Remove group dialog Remove client dialog
  • Slide 33
  • Clients GUI
  • Slide 34
  • Client main screen A link to the tour select page Opens new Messages dialog to write a new message if the client is a single client group this dialog is disabled.
  • Slide 35
  • Clients GUI Opens Read Messages dialog to read new incoming message. if the client is a single client group or no messages to read this dialog is disabled. Quit program. Room Info to get local room info
  • Slide 36
  • In every room the user Will get an over view of the rooms Exhibits + links for more information By his demand. The user will get a few options By links: To see a map Go back to previous page Select a different t