outing tables), IPCP (an Internet function that assigns IP addresses to hosts), the TEI assignment function in LAPD (that assigns terminal identifiers to ISDN terminals), and all functions which auton- omously monitor and maintain the traffic system's behaviour and performance. Figure 5.5 shows the addition of such a management function in a traffic node. e.g. IP Remote machine *) This is the symbol used for denoting management relations between layer elements IPR, RNC, LE, GSN, etc. Fig. 5.5 Traffic nodes and the management system in the N dimension. AMF=autonomous man- agement function; GSN=GPRS support node; IPR=IP router; LE=local exchange; MS=manage- ment system; NE=network element; RNC=radio network controller 5 Management and Traffic Systems Note that we use different symbols for denoting management relations in layer- structure models and in LSM models. In the former, all relations between layers are some kind of layer interfaces, the latter defines no layer interface at all. Instead all interfaces are interfaces between abstract machines, either of a user-provider type (as in Fig. 5.5) or of a peer type (you can read more about this in Appendix D). The AMF element in Fig. 5.5 manages a resource of a traffic system layer ele- ment over an mrCP. It is assumed to do that in collaboration with AMF elements in other traffic system nodes, which is why it uses a traffic system SAG. Once and a while, or upon request of the AF, an AMF may deliver information ("INFO" in the model) to the management system (MS) over an mrCP between the AMF and the AF. This may be performance information, data for charging, or for statistics analy- sis in the MS. AMFs may also spontaneously report alarming conditions to the AF. The AF will define MOs for covering all this kind of information as well. Since the model in Fig. 5.5. shows nodes, it allows us to analyze the distinction between planes and network systems in this context. The M dimension is realized inside traffic system nodes since it is defined by mrCPs. Thus, the bounda