561918 FRAMEWORK FOR MOBILE COLLABORATIVE LEARNING

PHASE-1 PURPOSE: User (Mobile) wants to get synchronization and a synchronization (text, video, audio, graphs and all kind of data). User uses the data for communication with other users, stores onto RSS or use for own information. The approach must have web based because it will be easier for mobile to make real time communication. The real mobile will get unique ID number when they will try to access website. These unique ID numbers can be used as password to obtain the information from websites. The unique ID number will be issued from both types of servers that have to be implemented on website. How these unique ID will be issued? Any mobile user will provide His/ Her name and mobile number, then two types of server one named DHCP server and other is Rogue DHCP server will issue unique ID. You need to set timer for issuance of unique ID (password). If mobile user fill in information means name and mobile number within 15 seconds then DHCP server will issue unique ID (Password). If time is exceeded than 15 seconds, then DHCP ROGUE Server will issue unique ID (Password) to mobile. Note: ID issued by DHCP server will be valid ID and can be used as password and ID issued by Rogue DHCP server will be considered fake ID and cannot get access other server. PHASE-2 The mobile user will use this ID for getting the access of information Mobile supported content server (MSCS) that is implemented as part of website. The function of MSCS is to authenticate the mobile user on the basis of unique ID (Password). This job is done with help of MSCS to verify the status of the users. If illegitimate user sends the request for getting the contents for collaborative learning that request is declined. MSCS is implemented on internet information server (Web server) that also provides the access to legitimate users. MSCS will forward the request of mobile user to authentication server. Valid IDs are stored in authentication server. The validity of mobile users will be identified on the basis of unique ID issued by DHCP server and Rogue DHCP Server. The ID is valid, then request will be processed otherwise Mobile user must get message “Request Declined”. MSCS will also deal three types of services normal, low priority and high priority. If request is about normal service that is handled with file system manager. Low priority services will be dealt with database manager. High priority will be dealt with HTTP client. QUERRY PROCESSOR that will be part of MSCS that will decide where to send request for obtaining the data. Query processor must be smart enough to decide. How Query processor will identify types of services? When validity of users will be determined then two messages should display “Request Accepted” or “Request Declined”. In case of acceptance of request, MSCS will provide three types of options. By clicking the button “Request Accepted” then should appear the following messages. I. Normal Service II. Low priority service III. High Priority service These services will be controlled by Query processor. The Query processor will decide to which component should be used to process the request. Query processor will send Normal type of service to file system manager, Low priority type service to Database manager and High Priority type service to HTTP connection. Note: You have to show little bit delay for normal type of service in order to show real impression on people that service is normal, for low priority service, you have to show little bit less delay than normal type of service but high priority type of services, You do not need to give delay. If you use timer or something else that can make message little bit longer in process. PHASE-3 If you deal with high priority service, you need to introduce Cache server. I suggest to all students, cache some data on cache server for getting the faster contents. Integration of cache server process provides the faster delivery of contents. With introduction of cache server, time can be saved of backups and log monitoring because the substantial time is spent on these activities every day. It improves the performance. If requested data is not cached on cache server, then cache server must be linked with content management system (CMS). If cache server is linked with CMS, CMS can deliver the requested contents to cache server in order to maintain status of high priority service. Low priority service will be dealt with database manager; As database manager will forward request to CMS. Normal types of service will be forwarded through file system manager to CMS. As we already talked about dealing of delay for these types of services. So you have to control through these components. The CMS provides logical storage for different devices. CMS controls four types of databases. One database has only text, second database audio, third database has video and fourth database has pictures, images and graphs etc. All of these databases are connected with central database that will obtain required contents from other database and deliver the contents with help of CMS. You have to implement multiple repositories on CMS; the reason of introducing multiple repositories is to get all types of data with different repository. For instance request for text can be dealt with repository-1, request for video will be dealt with repository-2, request for audio will be dealt with repository-3, request for pictures, images, graphs etc will be dealt with repository-n or repository-4. The repository plays a role as bridge for connecting file system manager and database manager with databases for obtaining the requested contents. The rapid increase in consumption of different media cause of mixing all the contents and resulting loss of data occurs. To control this issue; various repositories are introduced at MSCS for each media that handle the scalability issues and loss of data. The multiple uses of repositories capture and preserve communication process and serve as tangible indicators for improving the quality of mobile learning. Multiple repositories must be part of CMS. CMS will provide requested contents to mobile users, It means mobile user will be able to watch, hear and see the contents to be obtained through request. Phase-4 (Final). This phase is building of Really Simple Syndication (RSS). Mobile users must have access to build RSS and also store information in their own RSS. The all of RSS must have unique password and common password for each RSS. Common password must be known by users only and unique password must be known by teacher. The teacher must be able to access all RSS with help of unique password. In addition, teacher can provide the access of RSS to other users to get knowledge about RSS for [login to view URL] users must be able to read but not be able to modify the contents of other users' RSS. Finally, the passwords of RSS must be changeable if any user wants to change password that must be provided access to change password and obtain new password anytime. Note : If you have any confusion, feel free to contact me for more clarification.