fig1 shows a network architecture which is 3gpp compliant and implements the throughput boost via multi - rat parallel data flows proposed here . the network comprises a core network 10 connected through a core packet switching interface 20 , e . g ., iups specified by 3gpp or gb interface of 2g gprs or s1 interface in lte , to a primary network controller 11 which is , in a preferred example , a 3g rnc . the core network 10 serves as gateway to internet , connecting the rnc to a sgsn / ggsn , performs session and paging control , and is in charge of nas signalling . the primary network controller 11 performs radio resource control signalling , radio resource management and mobility management and the functions of radio link control , in order to set up the pdp context connection with the core network 10 . the network further comprises at least one secondary network controller 12 which has the same functionalities as the primary controller 11 aforementioned and connects with the core network 10 through said primary controller 11 , using a lur - like interface 22 defined for signalling and user plane of the , internal or external , communication between the pair of primary 11 and secondary controllers 12 . each primary 11 and secondary 12 controller manages one or more base station , 14 , 14 ′, 15 , with their respective radio access technology , via the corresponding standardized interface 21 , 23 ; e . g ., abis if the base station is 2g bts controlled by a bsc acting as primary or secondary controller , lub for nodeb controlled by 3g rnc or the internal interface of enodeb in lte . for example , the network entities shown in fig1 can be , depending on the supported radio access technologies : the controllers 11 and 12 respectively of primary and secondary radio access technologies : the bsc in 2g , the rnc in 3g and the enodeb in lte ; the base stations 14 , 14 ′, 15 respectively of primary and secondary radio access technologies : the bts in 2g ran , the nodeb in 3g fdd or tdd utran , the enodeb in fdd or tdd lte system . the primary controller 11 is connected to each secondary controller 12 via the interface 22 that carries signalling to establish and control the multi - rat call , as well as provides the user plane data for the secondary flow established trough the secondary rat . the other interfaces , respectively with the core network 10 and the user equipment ( ue ) 13 , are the standard interfaces defined in the 2g or 3g or lte architecture . the ue 13 is a user terminal with simultaneous multi - rat capability , provided with a primary rat receiver / transmitter 13 a and at least one secondary rat receiver / transmitter 13 b . fig2 shows a possible implementation of the protocol stacks in the primary and secondary controllers 11 , 12 for data routing in a network scenario where the primary rat managed by the primary controller 11 is 3g wcdma , the secondary rat provided by the secondary controller 12 is lte and all the ran nodes receive ip packets from the sgsn / ggsn of the core network 10 . in this example , these primary and secondary controllers 11 , 12 have a common protocol layer 30 which is ip layer , so that the incoming ip packets from the core network 10 are sent by the primary controller 11 , i . e ., the rnc , to the nodeb via lub interface and , through the interface 22 , sent to the secondary controller 12 towards the enodeb . the amount of packets to be sent towards the wcdma physical layer 33 of the primary rat or the ofdma physical layer ( 33 ′) of the secondary rat , through the rlc - 3g / mac - 3g and rlc - lte / mac - lte layers 31 , 32 , 31 ′, 32 ′ respectively , is dynamically adjusted by the rnc , for example , according to the flow control information feedback received through the rnc - enodeb interface . whenever erroneous packets remain after rlc retransmission , which is infrequent , those packets are handled by the above application layers , usually triggering tcp retransmissions . packet data convergence protocol — pdcp — can be used to compress the ip headers by the primary controller ( 11 ). as an example , in the case of using 3g as primary rat and lte as secondary rat , it is necessary to perform ip headers compression in the primary rat by the rnc , because this functionality in lte is included in core network nodes but not in the enodeb . thus , the rnc as primary controller 11 acts as a router that receives the ip flow through iups interface and relays the ip packets splitting the data flow into to the rlc - 3g and the rlc - lte to be sent to the nodeb and the enodeb . therefore , in this case , data combination is carried out above the rlc layers . another possible implementation consists of combining the data from ip packets of the same pdp context below the rlc level , as performed by the protocol stacks shown in fig3 . the preferred primary rat is 3g wcdma and the secondary rat is lte . the rnc is the controller node provided with ip layer as common protocol layer 30 between the entities of primary and secondary controllers 11 , 12 and a common protocol for the radio part 31 which is the rlc 3g layer . in this case , the rnc playing the role of primary controller 11 routes but also combines itself the data received from the core network 10 . the rnc is transmitting normally some of the 3g - rlc pdus and other data stream of pdus is then routed to the enodeb , which encapsulates the 3g - rlc pdus over mac - lte layer . then the ue 13 takes all the 3g - rlc pdus as they are numbered and performs reordering in order to rebuild the packets from the two different rats used for data routing into the original ip packet data stream . basically , in this preferred implementation , the rnc maps the rlc 3g channels into the transport channels of lte : in uplink , as shown in fig4 , the uplink shared channel ( ul - sch ) in lte defined by 36 . 300 technical specification of the 3gpp standards can be mapped into the uplink 3g logical channel which carries dedicated traffic channel ( dtch ). fig5 shows mapping in downlink , the dedicated traffic channel ( dtch ) of 3g maps onto downlink shared channel ( dl - sch ) used as transport channel in lte . fig6 shows a diagram of the messages interchanged by the network entities in the call set - up signalling process for the proposed multi - rat transmission . 1 ) call setup 40 and user plane transfer 41 are normally carried out between the primary network controller 11 and the ue 13 . during the rrc connection setup complete of the normal call set - up 40 , the ue 13 sends a signalling message with a 3gpp ue capabilities field which includes new information element ( ie ) indicating the ue ability to support a dual - rat call or multi - mode in general and indicating frequency bands which multi - rat transmitting / receiving is carried over . 2 ) establishment of the call , or call setup 40 , over a primary rat is processed as usual , including pdp context establishment , authentication and the normal procedures executed by the core network 10 nodes that are connected to the primary controller 11 . the primary controller 11 , rnc in the 3g case , also intervenes normally in all the procedures for call setup 40 , including the ciphering , over its primary rat . 3 ) the primary controller 11 seeks info on the cells belonging to other rats that are capable to provide coverage to the ue 13 . this is achieved by using a standard 3gpp measurement control command 42 for requesting the ue 13 to perform radio measurements over the cells of the different rats which are neighbour cells of the one currently providing service to this ue 13 . the ue 13 takes radio signal measurements of neighbouring cells and compares these cell measures to each other and to the radio signal of the current cell in order to determine which cell provides the best signal strength / quality . typical radio measurements can include : in 3g , the energy per chip ( ec ) and the spectral noise power density ( no ) received by the ue 13 to determine the ratio ec / no , also rssi or path loss may be measured ; in 2g , the ue 13 measures the received signal strength ( rxlev ). 4 ) the primary controller 11 retrieves info on the available load 44 in the different - rat cells whose coverage quality is higher than a minimum quality threshold . the information retrieval implies contacting via a set of interfaces the secondary controllers 12 , e . g ., the enodebs in the case of lte and the bscs in the case of 2g / edge , under which the cells with relevant coverage to the ue are handled . 5 ) the primary controller 11 decides , based on the received measurement report 43 from the ue 13 and the load info response 45 from each secondary controller 12 , whether a second — or third . . . — data flow has to be established in basis of all the received info . 6 ) if the primary controller 11 decides to use a secondary or more rats , the ue 13 is notified to activate the second receiver 46 , or the needed receivers , over a specific band , frequency and cell . 7 ) at the same time , the primary controller 11 sends a request to the selected secondary controllers 12 to establish a connection 47 between them for user plane transmission to a specific ue 13 , as well as to send a paging 48 to the paging group which the selected ue 13 belongs to . 8 ) each secondary controller 12 sends a paging to the ue 13 , the ue 13 answers as per a normal call setup procedure 49 defined on the rat used by the secondary controller 12 , and a radio connection is finally established 50 between the ue 13 and each secondary controller 12 selected to carry part of the data flow . transfer of user plane data 51 comes to pass normally between the ue 13 and each secondary controller 12 . the ue 13 receives the information of the channel setup and , as for example of fig3 , this info is directly mapped to the same layer that receives the rlc pdus in the primary controller 11 . also , every secondary controller 12 executes its ciphering procedure . once completed , the secondary controller 12 signals that it is ready to receive data to the primary controller 11 . 9 ) the primary controller 11 starts routing some of the packets received from the core network 10 , by sgsn / ggsn , to each secondary controller 12 which connection is established to , via the established interface between them . 10 ) the packets are combined by the ue 13 once received . note that in this text , the term “ comprises ” and its derivations ( such as “ comprising ”, etc .) should not be understood in an excluding sense , that is , these terms should not be interpreted as excluding the possibility that what is described and defined may include further elements , steps , etc .