Fipa abstract Architecture Specification

FIPA Abstract Architecture Specification

1 Introduction 3

2 Scope and methodology 5

3 Architectural Overview 12

4 Agent and agent information model 28

5 Architectural elements 35

6 Evolution of the architecture 54

7 Appendix A: Goals of message transport abstractions 55

8 Appendix B: Goals of Directory service abstractions 59

9 Appendix C: Goals for Abstract Agent Communication Language 61

10 Appendix D: Goals for security and identity abstractions 64

Figure 1 - Abstract Architecture mapped to various concrete realizations 9

Figure 2 - Concrete realizations using a shared element realization 10

Figure 3 - An agent registers with a directory service 15

Figure 4 - Directory query 15

Figure 5 - Directory query for a service 16

Figure 6 - A FIPA-message 17

Figure 7 - FIPA-message becomes a transport-message 18

Figure 8 – Communicating using any transport 20

Figure 9 - Two transport-messages to the same agent 21

Figure 10 - Encrypting a message payload 22

Figure 11 - Agent without an agent-platform 23

Figure 12 - Agent using an agent-platform 24

Figure 13 - Transformation of ACL using transform service 25

Figure 14 – Transport-transform-service transforming messages 27

Figure 15 UML: Basic Agent Relationships 29

Figure 16 – UML: Transport Message relationships 30

Figure 17 – UML: Directory-entry and locator relationships 31

Figure 18 – UML: FIPA-message elements 32

Figure 19 - UML: Message Transport Entities 33

Figure 20 - UML: FIPA Entity relationships 34