(1,2) O. Boissier (1) , B. Gteau teau (1,2) O. Boissier (1) , B. G - - PowerPoint PPT Presentation

▶
1 2
SMART_READER_LITE
LIVE PREVIEW

(1,2) O. Boissier (1) , B. Gteau teau (1,2) O. Boissier (1) , B. G - - PowerPoint PPT Presentation

Aug 23, 2022 113 likes •423 views

Normative Multi-Agent Normative Multi-Agent Organizations: Organizations: Modeling, Support and Control Modeling, Support and Control MOISE-Inst and SYNAI MOISE-Inst and SYNAI (1,2) O. Boissier (1) , B. Gteau teau (1,2) O. Boissier (1)

slide-1
SLIDE 1

1 1

  • O. Boissier, B. Gateau

19th march 2007

Normative Multi-Agent Normative Multi-Agent Organizations: Organizations: Modeling, Support and Control Modeling, Support and Control

MOISE-Inst and SYNAI MOISE-Inst and SYNAI

  • O. Boissier
  • O. Boissier(1)

(1), B. G

, B. Gâteau âteau(1,2)

(1,2)

(1) MAS/G2I/ENSM.SE Olivier.Boissier@emse.fr (2) CITI/CRP Henri Tudor Benjamin.Gateau@tudor.lu

slide-2
SLIDE 2

2 2

  • O. Boissier, B. Gateau

19th march 2007

Practical Motivations Practical Motivations

  • Context: Interactive TV Games
  • Aim : Development of a generic infrastructure

to support execution of iTV Games

  • Requirements :
  • Roles, Groups and Behavior patterns are important elements of a Game

 Use of an Organizational Model to represent them in an explicit manner

  • Explicit rules and strategies control players in a game (use of penalties and

rewards) Use of Norms to represent them

  • Users may have the possibility to violate the rules

 Use of Avatars controlled by users such that:

Each agent is under the control of its user who decides to violate/respect rules Agents should have autonomy with respect to norms and organization

  • Game must be regulated and controlled

 Use of a normative system  Use of agents/services to enforce the norms, the organization constraints

slide-3
SLIDE 3

Global Picture of Organizations in MAS

MAS MAS

Pattern of Emergent Cooperation Pattern of Predefined Cooperation

MAS MAS

Agents don’t know about organization Agents know about organization

MAS MAS MAS

Pattern of Emergent Organization Pattern of Predefined Organization

slide-4
SLIDE 4

MAS MAS MAS MAS

Organization is Observed. Implicitly programmed in Agents, Interactions, Environment. Organization is a design model. It may be Hard Coded in the Agents. Organization is Observed. Coalition Mechanisms programmed in the Agents. Organization is interpreted/programmed by the Agents, and/or by specialized middleware services.

Agent Centered Point of View Organization Centered Point of View

Global Picture of Organizations in MAS

Agents don’t know about organization Agents know about organization Pattern of Emergent Organization Pattern of Predefined Organization

Our Focus

slide-5
SLIDE 5

5 5

  • O. Boissier, B. Gateau

19th march 2007

Programming Organizations Programming Organizations

Organization Services Interaction Services Environment Services

MAS Services “Multi-Agent Platform” MAS

AMS DF ACC

Organization Specification (OS) defined using an Organization Modeling Language (OML), e.g. AGR, IDL, OMNI, MOISE+ Organization Infrastructure (OI), e.g. Madkit, AMELI, OMNI, S-MOISE+ used to execute and to interpret the OS, building an Organizational Entity (OE), i.e. set of agents executing within an OS

slide-6
SLIDE 6

6 6

  • O. Boissier, B. Gateau

19th march 2007

Research Motivations Research Motivations

Interaction Services Environment Services

MAS Services “Multi-Agent Platform” MAS

AMS DF ACC

Domain Agents: subject to

  • rganization

SS CS FS NS

  • Enrich MOISE+ OML with norms  Moise-Inst OML
  • Define architecture of the Organization Infrastructure (OI)  Synai
  • Define supervisor agents, i.e. agents playing a role in the regulation of the
  • rganization  Regulation OS

Supervisor Agents

slide-7
SLIDE 7

7 7

  • O. Boissier, B. Gateau

19th march 2007

Our Approach Our Approach

Synai Interaction Services Environment Services

MAS Services “Multi-Agent Platform” MAS

AMS DF ACC

Domain Agents

SS CS FS NS

Avatars Organization and Rules of the Game.

slide-8
SLIDE 8

8 8

  • O. Boissier, B. Gateau

19th march 2007

Outline Outline

  • Introduction
  • Motivations
  • Global sketch of our approach
  • Normative Organization Modeling
  • Normative Organization Support
  • Architecture
  • Control
  • Conclusion and perspectives
slide-9
SLIDE 9

9 9

  • O. Boissier, B. Gateau

19th march 2007

 Structural Specification

(SS) structure of the

  • rganization in term of

roles, groups and links

Normative Organisation Normative Organisation Modeling Modeling

SS CS FS NS

 “MOISE Inst” OML to define OS with four independent

dimensions (based on Moise+ [Hübner 02])

slide-10
SLIDE 10

10 10

  • O. Boissier, B. Gateau

19th march 2007

SS CS FS NS

Normative Organisation Normative Organisation Modeling Modeling

  • Functional

Specification (FS) goals to be achieved in the

  • rganization

 “MOISE Inst” OML to define OS with four independent

dimensions (based on Moise+ [Hübner 02])

 Structural Specification (SS)

structure of the organization in term of roles, groups and links

slide-11
SLIDE 11

11 11

  • O. Boissier, B. Gateau

19th march 2007

SS CS FS NS

Normative Organisation Normative Organisation Modeling Modeling

 Contextual

Specification (CS) all possible “a priori” states of the organization

 Functional

Specification (FS) goals to be achieved in the organization

 “MOISE Inst” OML to define OS with four independent

dimensions (based on Moise+ [Hübner 02])

 Structural Specification (SS)

structure of the organization in term of roles, groups and links

slide-12
SLIDE 12

12 12

  • O. Boissier, B. Gateau

19th march 2007

SS CS FS NS

Normative Organisation Normative Organisation Modeling Modeling

  • Normative

Specification (NS) norms gluing all SS, FS and CS together

 “MOISE Inst” OML to define OS with four independent

dimensions (based on Moise+ [Hübner 02])

 Functional

Specification (FS) goals to be achieved in the organization

 Contextual

Specification (CS) all possible “a priori” states of the organization

 Structural Specification (SS)

structure of the organization in term of roles, groups and links

slide-13
SLIDE 13

13 13

  • O. Boissier, B. Gateau

19th march 2007

Team Game Player BasicPlayer Chief History Geo Sport Science OrgCandidate 1..1 1..1 1..1 1..1 1..1 1..1 4..4 *..n GameMaster 1..1

Group Role Abs Role inheritance composition

Links

acq aut com

key

inter-group intra-group

compat

Domain View

Soc

MOISE-Inst Structural Specification MOISE-Inst Structural Specification

slide-14
SLIDE 14

14 14

  • O. Boissier, B. Gateau

19th march 2007

g2m2 Score Scheme g5m4 g4m4 Functional Scheme g412 m5,m16 g44 m4 g421 m4 g43m4 g422 m6,m16 g42 m4 g411 m4 g41 m4 g431 m4g432 m7,m16 g441 m4 g442 m8,m16 goal missions

sequence choice parallelism

key Emotion Scheme g8m13 g82 m15 g81 m14 Score Scheme g7m11 g72 m12 g71 m12 Sanction Scheme g6m9 Score Scheme g62 m10 g61 m10 g3m3 OrgExit Scheme g1m1 OrgEnter Scheme

g41: "History" topic handled g411: "History" question asked g412: "History" question answered g42: "Geo" topic handled g421: "Geo" question asked g422: "Geo" question answered g43: "Sport" topic handled g431: "Sport" question asked g432: "Sport" question answered g44: "Science" topic handled g441: "Science" question asked g442: "Science" question answered g6: Sanction applied g61: Player ejected g62: Team disqualified g7: Score changed g71: Score increased g72: Score decreased g8: Emotion shown g81: Be happy g82: Be sad g1: Team joined g2: X pts scored g4: Topic handled g5: Answer evaluated g3: Team quit

MOISE-Inst Functional Specification MOISE-Inst Functional Specification

slide-15
SLIDE 15

15 15

  • O. Boissier, B. Gateau

19th march 2007

g2m2 Score Scheme g5m4 g4m4 Functional Scheme g412 m5,m16 g44 m4 g421 m4 g43m4 g422 m6,m16 g42 m4 g411 m4 g41 m4 g431 m4g432 m7,m16 g441 m4 g442 m8,m16 goal missions

sequence choice parallelism

key Emotion Scheme g8m13 g82 m15 g81 m14 Score Scheme g7m11 g72 m12 g71 m12 Sanction Scheme g6m9 Score Scheme g62 m10 g61 m10 g3m3 OrgExit Scheme g1m1 OrgEnter Scheme

g41: "History" topic handled g411: "History" question asked g412: "History" question answered g42: "Geo" topic handled g421: "Geo" question asked g422: "Geo" question answered g43: "Sport" topic handled g431: "Sport" question asked g432: "Sport" question answered g44: "Science" topic handled g441: "Science" question asked g442: "Science" question answered g6: Sanction applied g61: Player ejected g62: Team disqualified g7: Score changed g71: Score increased g72: Score decreased g8: Emotion shown g81: Be happy g82: Be sad g1: Team joined g2: X pts scored g4: Topic handled g5: Answer evaluated g3: Team quit

MOISE-Inst Functional Specification MOISE-Inst Functional Specification

slide-16
SLIDE 16

16 16

  • O. Boissier, B. Gateau

19th march 2007

g2m2 Score Scheme g5m4 g4m4 Functional Scheme g412 m5,m16 g44 m4 g421 m4 g43m4 g422 m6,m16 g42 m4 g411 m4 g41 m4 g431 m4g432 m7,m16 g441 m4 g442 m8,m16 goal missions

sequence choice parallelism

key Emotion Scheme g8m13 g82 m15 g81 m14 Score Scheme g7m11 g72 m12 g71 m12 Sanction Scheme g6m9 Score Scheme g62 m10 g61 m10 g3m3 OrgExit Scheme g1m1 OrgEnter Scheme

g41: "History" topic handled g411: "History" question asked g412: "History" question answered g42: "Geo" topic handled g421: "Geo" question asked g422: "Geo" question answered g43: "Sport" topic handled g431: "Sport" question asked g432: "Sport" question answered g44: "Science" topic handled g441: "Science" question asked g442: "Science" question answered g6: Sanction applied g61: Player ejected g62: Team disqualified g7: Score changed g71: Score increased g72: Score decreased g8: Emotion shown g81: Be happy g82: Be sad g1: Team joined g2: X pts scored g4: Topic handled g5: Answer evaluated g3: Team quit

  • Org. Management View

MOISE-Inst Functional Specification MOISE-Inst Functional Specification

slide-17
SLIDE 17

17 17

  • O. Boissier, B. Gateau

19th march 2007

key

transition Event final context initial context Context context Begin MyTurn End NotMyTurn Round3 Round1 Round2 beginG chgRd chgRd endG chgT chgT avT hmT Game endG endG endG

MOISE-Inst Contextual Specification MOISE-Inst Contextual Specification

slide-18
SLIDE 18

18 18

  • O. Boissier, B. Gateau

19th march 2007

  • Norm defines rights and duties for a bearer (role or a group) to

execute a mission in a particular context and during a given time supervised by an issuer which can apply a sanction if the norm is not respected.

<norm> ::= '(':id <normId> :weight <int> '::'

[:conditions <condition>] :context <contextId> :operator <deonticRel> :bearer <sentityId> :issuer <sentityId> :action <deonticAct> [:relation <relation> :deadline <date>] [:sanction <normId>] ')’

  • Conditions are conjonction/disjunction of predicates bearing on:
  • Application, Organization states (e.g. number of agents, cardinalityMax, …),

Status of the norms (violated, respected)

MOISE-Inst Normative Specification

slide-19
SLIDE 19

19 19

  • O. Boissier, B. Gateau

19th march 2007

MOISE-Inst Normative Specification MOISE-Inst Normative Specification

slide-20
SLIDE 20

20 20

  • O. Boissier, B. Gateau

19th march 2007

Functioning of the game:

  • Obligation for the “GameMaster” role to ask questions and to verify answer
  • “m4” mission- during all the game -“Game” context-:

(Norm :id N4 :weight 1 :operator O :issuer Supervisor :bearer GameMaster :context Game :action do(m4))

  • Obligation for the “Chief” role to answer questions -”m16” mission- during the

third round

  • “Round3” context-:

(Norm :id N9 :weight 1 :operator O :issuer GameMaster :bearer Chief :context Round3 :action do(m16) :relation < :deadline answer_delay)

  • ...

MOISE-Inst Normative Specification MOISE-Inst Normative Specification

slide-21
SLIDE 21

21 21

  • O. Boissier, B. Gateau

19th march 2007

Management of the organization:

  • Obligation for the “OrgCandidate” role to join a team -”m1” mission- at the

beginning of the game -”Begin” context- in order to play a role in it: (Norm :id N1 :weight 1 :condition (number(Team)!=cardinalityMax(Team)) :operator O :issuer GameMaster :bearer OrgCandidate :context Begin :action do(m1))

  • Interdiction for an agent playing “OrgCandidate” role to join a team -“m1”

mission- during the game -“Game” context-: (Norm :id N6 :weight 1 :operator F :issuer GameMaster :bearer OrgCandidate :context Game :action do(m1) :sanction N17)

  • …

MOISE-Inst Normative Specification MOISE-Inst Normative Specification

slide-22
SLIDE 22

22 22

  • O. Boissier, B. Gateau

19th march 2007

Regulation of the organization: “Enforcement/reward

Norms” [Lopez y lopez]

  • If N6 is not respected then the “Arbitrator” role has the obligation to eject -“m9”

mission- the agent violating the norm N6 - the one wearing “OrgCandidate” role-: (Norm :id N17 :weight 1 :condition (violated(N6)) :operator O :issuer GameMaster :bearer Arbitrator :context Game :action do(m9))

  • If N8 is not respected then the “Arbitrator” role acts on the score -“m11”

mission- of the team in which the agent violating N8 is wearing the role: (Norm :id N18 :weight 1 :condition (violated(N8)) :operator O :issuer GameMaster :bearer Arbitrator :context Game :action do(m11))

  • …

MOISE-Inst Normative Specification MOISE-Inst Normative Specification

slide-23
SLIDE 23

23 23

  • O. Boissier, B. Gateau

19th march 2007

Outline Outline

  • Introduction
  • Motivations
  • Global sketch of our approach
  • Normative Organization Modeling
  • Normative Organization Support
  • Architecture
  • Control
  • Conclusion and perspectives
slide-24
SLIDE 24

24 24

  • O. Boissier, B. Gateau

19th march 2007

Normative Organization Support Normative Organization Support

  • Domain Agents evolve in an Organizational Entity corresponding

to the current states of:

  • played roles, instances of groups (Sruct. Entity)
  • Committed / executed / pending missions, goals (Func. Entity)
  • inactive / active states (Cont. Entity)
  • active / valid / fulfilled / violated norms (Norm. Entity)
  • Distributed management of the OE:
  • Set of agents for managing the different entities (SEManager, FEManager,

CEManager, NEManager)

  • Indirect/direct enforcement of the Domain Agents to conform to

the OS by applying sanctions

  • OEManager (e.g. action on the score, suspend agents, …)
slide-25
SLIDE 25

25 25

  • O. Boissier, B. Gateau

19th march 2007

SYNAI Architecture SYNAI Architecture

  • Org. Spec.

Functional States Norms Contexts Roles Groups

SS CS FS NS

Domain

FEManager SEManager CEManager NEManager OEManager OrgWrapper

Organization Infrastructure

SE FE CE NE Domain Agents Supervisor Agents

slide-26
SLIDE 26

26 26

  • O. Boissier, B. Gateau

19th march 2007

Supervisor 1..1 Arbitrator Institution 1..1 StructManager NormManager 1..1 1..1 FunctManager ContextManager InstManager ComManager 1..1 0..* 1..1

OrgWrapper Game Soc

SYNAI Regulation Struct. Spec. SYNAI Regulation Struct. Spec.

Domain Struct. Spec.

slide-27
SLIDE 27

27 27

  • O. Boissier, B. Gateau

19th march 2007

SYNAI Regulation FS & CS SYNAI Regulation FS & CS

QuickTime et un d compresseur BMP ﾎ sont requis pour visionner cette image. QuickTime et un d compresseur BMP ﾎ sont requis pour visionner cette image. QuickTime et un d compresseur BMP ﾎ sont requis pour visionner cette image. QuickTime et un d compresseur BMP ﾎ sont requis pour visionner cette image. QuickTime e d compresse ﾎ sont requis pour visionner cette image. QuickTime et un d compresseur BMP ﾎ sont requis pour visionner cette image. QuickTime et un d compresseur BMP ﾎ sont requis pour visionner cette image.

Corrective and Preventive Monitoring Modes

Domain Func. Spec.

slide-28
SLIDE 28

28 28

  • O. Boissier, B. Gateau

19th march 2007

SYNAI Regulation Norm. Spec. SYNAI Regulation Norm. Spec.

QuickTime et un d compresseur BMP ﾎ sont requis pour visionner cette image.

Some kinds of ‘‘Procedural’’ Norms

slide-29
SLIDE 29

29 29

  • O. Boissier, B. Gateau

19th march 2007

Conclusion & Perspectives Conclusion & Perspectives

  • MOISE-Inst extends MOISE+, inspired by other models (e.g.

ISLANDER)

  • Three independent dimensions glued together with a normative dimension
  • Other specifications?
  • Interactions Specification (cf. ISLANDER, OMNI)
  • Ontological Specification (cf. OMNI)
  • Reflective Organization Description
  • SYNAI's structure and functioning specified with MOISE-Inst
  • Next steps
  • Complete implementation of MOÏSEInst model into the iTV Avatars

application

  • Same validation into eCommerce domain with EBSME application
  • Management of norm detection and violation, Use and management of

sanctions, More supervisor agents

slide-30
SLIDE 30

30 30

  • O. Boissier, B. Gateau

19th march 2007

Norm Life Cycle Norm Life Cycle

  • A norm is active as long as its context is active.
  • A norm is valid as long as its condition is

satisfied

  • A norm is considered by the agents when it is

active and valid; it can evolve to fulfilled or violated by taking into account the operator and the time constraint:

  • In case of Obligation, norm is fulfilled if mission

executed in term

  • In case of Prohibition, norm is fulfilled if mission is not

accomplished until the deadline is over