re: *#pathld{1..960} AR1, AR2, AR4: AR3, AR5: Route properties are: Route properties are: #*routeld(AR3,AR5) -64 K #*routeld{AR1,AR2,AR4) *blockingState *blockingState *routeType {dig} *routeType {dig} Channel properties are: Channel properties are: *state #*chld{B1,B2} *state Route properties are: SR1, IR1: Route properties are: #*routeld{AR6} #*routeld{CR1} 3.1 kHz *blockingState *blockingState *routeType {ana} *routeType {dig} Channel properties are: Channel properties are: *state #*chld{1..30} *state * A property (or attribute) # Property used for identification Fig. 6.8 Service resource models for the connection resources, intuitive notation All these resources can be described by two generic resource models, one for switches and one for routes, using the general resource model notation, see Fig. 6.2 A Service Network Modelling Case SWITCH: ROUTE: #*swld Switch *congestionState Route #*routeld {cong,notCong} *blockingState *blockingState {blocked,notBlocked} {block,notBlock} *routeType{ana,dig} 1,2,30 Position #*posld Channel #o*chld *state{idle,busy} terminatesIn #*pathld A property (or attribute) # Property used for identification o Optional property Fig. 6.9 Generic service resource models for the connection resources, general notation The TEPC need not know anything about the structure of the resource system, or properties of routes and switches. TEPC and CNPC must, however, have a com- mon understanding of which connections exist between CNUs, of the state of the connections and of the RS as a whole. The CNW model can therefore be drawn as shown by Fig. 6.10. General notation Intuitive notation and instance This CNW: o*congState Connection Network acronym CNW properties are: o*congState connections #*TR-SAPI' CNU properties are: *blockingState #*TR-SAPI{CNU1..CNU7 *blockingState 1,2,30 Connection properties are: Connection o#*CEI Endpoint *conState number of *conState connection endpoints Connection {pending, connected, suspended} Fig. 6.10 The service resource model for the connection network (CNW) The