1. AGENT SERVICES FRAMEWORK FOR HANDHELD DEVICES SUPERVISOR: DR MUHAMMAD ASLAM Domain: Artificial Intelligence(AI) Muhammad Ali (09-MS-CE-11), Pureali@gmail.com

2. Agenda  Background (Agents, Web Services, SOA, FIPA)  The Problem  Solution(AgentServices)  Conclusion  QA

3. Background 1/2  Agent: Many definitions.  Agreed definition: Autonomous entities working on behalf of users  WebService: Software component available on the web  SOA: web service architecture. When a system is distributed into webservices.  W3C: standards for web services.  FIPA: Standards for agents

4. Background2/2  Web Services are similar to Agent services.  WSDL-No agent equivalent  UDDI –DF  Access Mechanism: SOAP-FIPA ACL  Ontology: is a knowledge represented as Classes, Properties, Domain-Range, Individuals

5. Agent interaction with its environemnt

6. The problem JADE Implemented by Communication Vocabularly Partial Ontology support Problem LanguageProtocol Problem: Closed System Implicit Ontology FIPA Specification Problem zone

7. Most agent implementations are closed systems, and its very difficult for external agents to affectively communicate with them. Problem Statement

8. Motivation  Restaurant Menu on Handheld device  Mosque Handheld device on silent

9. AgentServices  Ideal solution: Open System=Agents of different systems can talk and understand each other  Interpret agent as Web Service and make it self discoverable and self described  Solution: 1. A: Store Ontology within Agent 2. B: Allow transfer of Agent 3. Communication in terms of Individuals and CRM.

10. Integration of Agent-WebService

11. AgentService Context

12. Architecture

13. Software Hierarchy

14. Contributions  Solves the Domain Knowledge Problem  Provide location awareness  Specification: Commands and Interaction protocols  Library: Android API  GUI part: Android client to demonstrate practical aspects

15. Specification Library Android Client AgentServices Composition

16. Specification 1/2  Precise set of technical details that specifies that commands and interaction Protocol  Ontology Transfer: Command: ASRequestOntology Protocol: Request-Inform  Gui Request: Command:AsRequestGui Protocol: Request-Inform

17. Specification 2/2  Location Properties: Used for DF 1. ASlocationCity: Specifies the city 2. ASlocationCountry: Specifies the country 3. ASlocationAddress: Specifie the address 4. ASlocationPhone: Specifies the phone 5. ASlocationLongitude: Specifies the Longitude 6. ASlocationLatitude: Specifies the Latitude

18. Library 1/2  Powerful, Easy to Use  An API implementing the AS specification  Provide classes and wrappers around Jade  Service Creation Directory Facilator (DF) AgentServiceRegistration : Class for registration with location DiscoverLocation : A wrapper over the complex Jade service description

19. Library 2/2  AgentServicesCommands: Provides most common commands  AgentServiceMessageHandler : 1. Event based listeners setOnRequestOntologyListener setMessageListener setOnStartActionListener 2. Allows to reply to messages  AgentServiceMessageCreator: Wrapper for creating messaages

20. Client Application 1/5  Android Application to demonstrate the practical aspects of the research.  Allows 1. Discovery 2. Search 3. Running of nearby services

21. Client Application 2/5

22. Client Application 3/5

23. App Screenshot 4/5

24. App Screenshot 5/5

25. Six easy steps to create an Agent Service Service Creation Steps

26. Create Protégé Ontology 1/6

27. Creation based on CRM

28. Step 2 and 3  Create a new project in eclipse  Add the AgentServices.jar library  Add the ontology file created in step 1 in source

29. Place Ontologies in Source

30. ATM OWL File

31. Step 4: Register with DF

32. Step 5 : Implement Essential Commands

33. Step 6: Implement the Logic  Implement the application specific business logic

34. Conclusion  Existing systems are closed, application specific and platforms like JADE don’t support explicit ontology.  Allows dynamic creation, registration and discovery.  Solves the Domain Knowledge representation problem without using centralized approach or OA  Location awareness  Future: Streaming, Transfer

35. Service Discovery and Usage Location Awareness Demo Demonstration

36. Pureali@Gmail.com QA