rs for (i.e. radio access bearer or radio link) in the radio network layer. In the three plane structure the bearer parameters in the application protocol are not directly tied to the user plane tech- nology, but are rather general bearer parameters. The signalling bearer for the application protocol may or may not be of the same type as the signalling protocol for the ALCAP. The signalling bearer is always set up by O&M actions. 3.7.3.2 User Plane The user plane includes the data stream(s) and the data bearer(s) for the data stream(s). The data stream(s) is/are characterized by one or more frame protocols specified for that interface. 3.7.3.3 Transport Network Control Plane The transport network control plane does not include any radio network layer informa- tion, and is completely in the transport layer. It includes the ALCAP protocol(s) that is/are needed to set up the transport bearers (data bearer) for the user plane. It also in- cludes the appropriate signalling bearer(s) needed for the ALCAP protocol(s). The transport network control plane is a plane that acts between the control plane and the user plane. The introduction of transport network control plane makes it possible for the application protocol in the radio network control plane to be completely independent of the technology selected for data bearer in the user plane. When the transport network control plane is used, the transport bearers for the data bearer in the user plane are set up in the following fashion. First there is a signalling transaction by the application protocol in the control plane, which triggers the set up of the data bearer by the ALCAP protocol that is specific for the user plane technology. The independence of control plane and user plane assumes that ALCAP signalling transaction takes place. It should be noted that ALCAP might not be used for all types data bearers. If there is no ALCAP signalling transaction, the transport network control plane is not needed at all. This is the case when pre-configured data bearers are used