onnection has terminates Network Connection TE-UDT 1..30 1..30 hasProp o*congState hasProp existsln #*TR-SAPi) *blockingState *) Must be a TR-SAPI to an **) Reflects both CNU and access or an internal route route blocking states Fig. 6.21 The object resource model for TEPC 6.2 A Service Network Modelling Case 6.2.6 Object Behaviour The behaviour of an agent is an object behaviour. By definition, object behaviour is the behaviour that can be observed and specified by an observer that exists inside a service object. The context for object behaviour is described by Fig. 6.22. observer object behaviour Fig. 6.22 How object behaviour is specified Object behaviour is a function of a provider-port behaviour (here the behaviour for service S1) and of a number of user port behaviours (here the behaviours in ports uS2 and uS3). When an object has no user ports (as in case of virtual objects), the object behaviour is therefore equivalent a provider-port behaviour. An effect of placing the observer inside the object is that all object states become reactive states, unless the object handles interrupt states (which requires the definition of some active and interrupt states). Another effect is that an object behaviour description becomes a requirement specification of the behaviour of implementa- tions. Note that a service behaviour defines how users shall behave in the service relations, and it is used for creating object behaviours, but it is not a description of the behaviour of objects to be implemented. The TEPC is an agent. Let's provide a behaviour description for the TEPC, using all information available. We know the object resource model for TEPC (see Fig. 6.21). The behaviour in TEPC's provider port has been discussed, see Fig. 6.16. However, we also need the behaviour in TEPC's user port to CNPC, see Fig. 6.23. In order to give concrete form to the discussion, the state diagram in this fig- ure describes an instance of behaviour, where TEPC uses CNPC to create a connec- tion between CNU1 and CNU5. The operation use