Transmission of multicast and broadcast multimedia services via a radio interface

Abstract

The invention relates to a network element (23) for a radio access network (22) of a cellular network supporting the transmission of multicast and broadcast multimedia services via a radio interface Uu to user equipment (25), which network element (23) comprises radio interface protocols associated to different protocol layers including a data link layer (layer 2). In order to enable such transmissions, it is proposed that the data link layer comprises a dedicated multicast broadcast multimedia control sublayer (L2/MBMC) for a multicast broadcast multimedia control protocol (MBMC). The MBMC is to adapt multicast and broadcast multimedia services, originating from a core network of said cellular network, for transmission in the radio interface Uu. The invention equally relates to a corresponding radio access network, to a corresponding cellular network, to a corresponding user equipment, to a corresponding radio access based communication system, and to a corresponding method.

Description

FIELD OF THE INVENTION

[0001] The invention relates to a network element for a radio access network of a cellular network supporting the transmission of multicast and broadcast multimedia services via a radio interface to user equipment, which network element comprises radio interface protocols associated to different protocol layers including a data link layer (layer 2). The invention equally relates to such a radio access network, to such a cellular network, to a corresponding user equipment, to a corresponding radio access based communication system, and to a method for providing multicast broadcast multimedia services to a user equipment.

BACKGROUND OF THE INVENTION

[0002] Broadcast and multicast are methods for transmitting data-grams from a single source to several destinations, i.e. as point-to-multipoint transmissions. As mentioned in the technical specification 3GPP TS 22.146 V5.0.0 (2001-10): “Multimedia Broadcast/Multicast Service; Stage 1 (Release 5)”, currently, two such services are specified, the cell broadcast service (CBS) and the internet protocol (IP) multicast service.

[0003] The CBS allows for low bit-rate data to be transmitted to all subscribers in a set of given cells over a shared broadcast channel. This service offers a message-based service.

[0004] The IP-Multicast service enables mobile subscribers to receive multicast traffic. This service does not allow multiple subscribers to share radio or core network resources. Thus, it does not offer any advantages as far as resource utilization within the public land mobile network (PLMN) and over the radio access network (RAN) is concerned.

[0005] The benefit of multicast and broadcast in the network is that data only has to be sent once on each link, unless a repetition of the data becomes necessary. In UMTS (universal mobile telecommunication services) networks, for example, an SGSN (serving general packet radio system support node) will send data only once to a radio network controller (RNC) regardless of the number of Node Bs and user equipment (UE) that wish to receive it.

[0006] The benefit of multicast and broadcast on the radio interface is that many users can receive the same data over a common down-link (DL) channel, thus avoiding clogging up the radio interface with multiple transmissions of the same data. Therefore, broadcast and multicast are techniques which decrease the amount of data within the network and which use resources more efficiently.

[0007] For illustration, a basic network structure presented for cell broadcast services in the technical specification 3GPP TS 23.041 V4.1.0 (2001-06): “3rd Generation Partnership Project; Technical Specification Group Terminals; Technical realization of Cell Broadcast Service (CBS) (Release 4)” for UMTS is shown in FIG. 1. The network comprises as part of the core network a cell broadcast center CBC 11, which is connected via an Iu-bc interface to an RNC 13 of an UTRAN (UMTS terrestrial radio access network) 12. The CBC 11 may be connected in addition to other RNCs of the same or other UTRANs. Within the UTRAN 12, the RNC 13 is connected via a Iub interface to two Node Bs 14. Each of the Node Bs 14 is further connected via the radio interface Uu to a user equipment 15.

[0008] The CBC 11 is responsible for managing cell broadcast messages and can reach every RNC 13 via the user plane of the Iu interface. Cell broadcast messages are thus distributed by the CBC 11 to each concerned RNC 13. The RNCs 13 are responsible for the control of radio resources. Accordingly, they control the transmission of received broadcast messages via the Node Bs 14 to the UEs 15.

[0009] In the RNC, radio interface protocols are employed in order to be able to set up, reconfigure and release radio bearer services for transmissions like a broadcast transmission on the radio interface. The radio interface protocols are distributed to different layers, more specifically to the physical layer as layer 1, the data link layer as layer 2 and the network layer as layer 3. FIG. 2, which was taken from the technical specification 25.324, illustrates the current broadcast/multicast control protocol model. The figure shows a radio link control protocol (RLC) in a first sublayer L2/RLC and a broadcast/multicast control protocol (BMC) in a second sublayer L2/BMC of the user plane of layer 2. The L2/BMC sublayer is arranged above the L2/RLC sublayer. Further sublayers of layer 2, like a sublayer for the medium access control protocol (MAC) located below the L2/RLC sublayer, are not depicted in the figure. Above the L2/BMC sublayer, a radio resource control protocol (RRC) is depicted, which belongs to the control plane of layer 3. The layers are connected to each other through Service Access Points (SAPs). The BMC is connected to the RRC by a CBMC-SAP and further in unacknowledged mode (UM) via the L2/RLC sublayer and a CTCH-SAP to the MAC sublayer. In addition, the BMC is provided with a BMC-SAP.

[0010] Broadcast and multicast services are received from the core network via the CBC, the Iu-bc interface and the BMC SAP at the L2/BMC sublayer. The BMC adapts the broadcast and multicast services originating from the broadcast domain on the radio interface. To this end, it comprises several functions, which also enable the BMC to interact with the other protocols. The defined functions are storage of cell broadcast messages, traffic volume monitoring and radio resource request for CBS, scheduling of BMC messages, transmission of BMC messages to user equipment and delivery of cell broadcast messages to upper layers (NAS: non access stratum). In accordance with these functions, respective service data and control data is forwarded in unacknowledged mode to the RLC, and further via the CTCH-SAP and the MAC to the physical layer for transmission via the radio interface to the user equipment. The L2/BMC sublayer is transparent for all services except for broadcast/multicast services.

[0011] The above mentioned technical specification 22.146 specifies requirements for a new service called Multicast Broadcast Multimedia Service (MBMS). For the MBMS, two modes of operation are provided, the broadcast mode and the multicast mode. In both modes, the MBMS is to enable unidirectional point-to-multipoint transmissions of multimedia data, like text, audio, picture, or video, from a single source point via a radio interface to a broadcast area or to a multicast group in a multicast area respectively. The transmission of such multimedia services cannot be handled with the current BMC protocol model without changes, since multimedia transmissions require different and additional functions and interactions compared to conventional cell broadcast and IP multicast messages. The realization of the MBMS over the Radio Access Network (RAN) has not been specified yet.

SUMMARY OF THE INVENTION

[0012] It is an object of the invention to enable the transmission of multicast and broadcast multimedia services via a radio access network of a cellular network to user equipment.

[0013] This object is reached with a network element for a radio access network of a cellular network supporting the transmission of multicast and broadcast multimedia services via a radio interface to user equipment, which network element comprises radio interface protocols associated to different protocol layers including a data link layer (layer 2). In the proposed network element, the data link layer comprises a dedicated multicast broadcast multimedia control sublayer for a multicast broadcast multimedia control protocol (MBMC). This MBMC adapts multicast and broadcast multimedia services, which originating from a core network of said cellular network, for transmission on the radio interface.

[0014] The object is equally reached with a cellular network and a radio access network for a cellular network comprising the proposed network element. The object is also reached with a radio access based communication system comprising such a cellular network, and with a user equipment comprising a multicast/broadcast multimedia control entity enabling the handling of multicast and broadcast multimedia services received by such a cellular network.

[0015] Further, the object is reached with a corresponding method.

[0016] The invention proceeds from the idea that instead of adapting the current BMC sublayer to be able to handle the new service, a completely new, additional sublayer could be introduced to layer 2 of the protocol stack. The proposed MBMC sublayer adapts multicast and broadcast multimedia services originating from the broadcast domain on the radio interface. Preferably, this new MBMC sublayer is used in parallel with the existing BMC sublayer.

[0017] It is an advantage of the invention, that it enables the transmission of MBMS messages.

[0018] It is further an advantages of the invention that the introduction of a new, dedicated sublayer for supporting MBMS messages enables an easier implementation than an enhancement of the currently defined BMC.

[0019] It is an additional advantage that with the invention it is not required in the case of UMTS to use the Iubc interface between the core network and UTRAN as with the currently defined BMC, i.e. the Iu-interface could be used, and therefore it is possible to use the functionalities, which are provided by such core network side network elements like SGSN, HLR (home location register), GGSN (gateway general packet radio system support node) etc., in a more flexible way.

[0020] It is still a further advantage of the invention that it enables a system that is backwards compatible with regard to user equipment using earlier releases. User equipment supporting an earlier 3GPP system release would not be able to cooperate with the new functionality of an enhanced BMC, since amendments would have to effect also the existing functionalities.

[0021] Preferred embodiments of the invention become apparent from the subclaims.

[0022] In particular, a variety of advantageous interactions with other layers are proposed, as well as variety of functions which can be provided by the protocol of the new sublayer for enabling these interactions and for enabling the adaptation of MBMS on the radio interface.

[0023] The invention can be employed in particular, though not exclusively, in a UMTS network as cellular network, in which the radio access network is a UTRAN and in which the network element is an RNC for a UTRAN.

[0024] Other objects and features of the present invention will become apparent from the following detailed description considered in conjunction with the accompanying drawings. It is to be understood, however, that the drawings are designed solely for purposes of illustration and not as a definition of the limits of the invention, for which reference should be made to the appended claims. It should be further understood that the drawings are merely intended to conceptually illustrate the structures and procedures described herein.

BRIEF DESCRIPTION OF THE FIGURES

[0025] In the following, the invention is explained in more detail with reference to drawings, of which

[0026] FIG. 1 shows a conventional basic network structure for cell broadcast services;

[0027] FIG. 2 shows a conventional BMC protocol model;

[0028] FIG. 3 shows an embodiment of a basic network structure for MBMSC according to the invention; and

[0029] FIG. 4 shows a MBMC protocol model for an embodiment of an RNC according to the invention.

DETAILED DESCRIPTION OF THE INVENTION

[0030] FIGS. 1 and 2 have already been described in connection with the background of the invention.

[0031] FIGS. 3 and 4 present an embodiment of the invention employed in an UMTS network, in which a new sublayer is introduced for MBMS in an RNC of an UTRAN.

[0032] FIG. 3 presents an embodiment of a basic network structure employed for MBMS in a UMTS network according to the invention. The structure corresponds to the structure presented in FIG. 1, except that instead of a CBC, a multicast broadcast multimedia service center MBMSC 21 is shown. Thus, the network comprises as part of the core network an MBMSC 21, which is connected via an Iu-bc interface with an RNC 23 of an UTRAN 22. Like the CBC, the MBMSC 21 may be connected in addition to other RNCs 23. Within the UTRAN 22, the RNC 23 is connected via a Iub interface to two Node Bs 24. Each of the Node Bs 24 is further connected via the radio interface Uu to a user equipment 25. In the presented embodiment, also a Iu-ps (ps: packet switched) interface or a new Iux interface could be employed instead of a Iu-bc interface for connecting the MBMSC with the UTRAN.

[0033] Analogously to the CBC, the MBMSC 21 is responsible for managing multicast and broadcast multimedia services messages and can reach every RNC 23 via the user plane of the employed interface. Multicast and broadcast multimedia messages are thus distributed by the MBMSC 21 to each concerned RNC 23. The RNCs 23 control the transmission of received multicast and broadcast multimedia messages via the Iub interface, the Node Bs 14 and the radio interface Uu to the UEs 15.

[0034] FIG. 4 shows a MBMC protocol model employed in the RNC 23 of FIG. 3. The MBMC protocol model comprises the same elements as the known BMC protocol model of FIG. 2. In addition, a further sublayer L2/MBMC with an MBMC protocol is introduced, which is integrated in the model in an analogous way as the L2/BMC sublayer. It is thus connected to the RRC by a CMBMC-SAP. Further it is connected in UM via the L2/RLC sublayer to a CTCH-SAP. Alternatively or additionally, the connection to the L2/RLC sublayer could also be in acknowledged mode (AM) and/or transparent mode (TM). Finally, it is connected to a MBMC-SAP. The two sublayers L2/BMC and L2/MBMC are arranged on the same level in the protocol stack.

[0035] The MBMC-SAP provides a broadcast/multicast transmission service in the user plane on the radio interface for common user data in unacknowledged and/or transparent mode. Alternatively or additionally, the acknowledged mode could be employed. MBMS messages and other information required for transmitting the respective service and received at the RNC 23 from the MBMSC 21 are provided to the MBMC via the MBMC-SAP. The MBMC adapts the data for transmission on the radio interface Uu. Then, it forwards the messages and further required information via the RLC, the CTCH-SAP, and the MAC to the physical layer for transmission over the radio interface Uu to the user equipment 25.

[0036] The BMC of the L2/BMC sublayer is maintained as defined by the current specifications. Conventional multicast and broadcast messages received at the RNC 23 e.g. from the CBC 11 of FIG. 1 are transported and processed by the BMC as explained with reference to FIG. 2. Thus, it the BMC is employed in parallel to the new MBMC for dealing with conventional broadcast and multicast messages, which is of particular importance for conventional terminals.

[0037] In the presented embodiment, the new L2/MBMC sublayer is able process received data and to perform different interactions with other layers, in order to enable a required adaptation of MBMS for transmission via the radio interface.

[0038] All interactions are specified in terms of primitives, which constitute a logical exchange of information and control between the L2/MBMC sublayer and higher, lower or parallel layers.

[0039] The L2/MBMC sublayer interacts for example with the RRC for establishing, modifying, and releasing links to the user equipment 25. Further, it interacts with the RRC for carrying out MBMS traffic measurements and traffic control etc.

[0040] The L2/MBMC sublayer moreover also interacts with the IuUP, which is a protocol which takes care of the data transmission on the Iu CS/PS or Iu-x interface, whichever is employed between the RNC and the MBMSC 21, or with the CBC on the user plane. With which one it interacts is dependent on the used protocol on the Iu-interface. This interaction is intended for data transmission, data related control information, flow control information and multicast session related control information. The data related control information may comprise start and/or end of session bits, sequence information, priority information etc. The multicast session related control information may comprise information on data deletion, resets etc.

[0041] Further, the L2/MBMC sublayer interacts with the RLC layer arranged below the L2/MBMC sublayer for the transmission of data, security related information, discard information etc. In addition, some kind of “wake up” message can be transmitted from this RLC layer to all user equipment 25, which is registered and therefore also authorized to receive multicast data. Such a “wake up” message an be considered to constitute some kind of paging without a response requirement.

[0042] The new sublayer also interacts with the MAC layer, which is also arranged below the new L2MBMC sublayer, for coverage and/or congestion issues. In addition, it is also possible that some part of the scheduling is located at the MAC layer e.g. when multicast data is transmitted inside a channel which is not completely dedicated for the transmission of multicast data. Also when there is a need to restrict the data amount on the radio interface, the information to reduce the multicast data rate can be given directly either to the MAC layer or the MBMC layer.

[0043] Finally, the L2/MBMC sublayer interacts with the L2/BMC sublayer. Interactions between these layers concern e.g. scheduling related information etc.

[0044] In the following, the main functions of the MBMC of the L2/MBMC sublayer proposed for the presented embodiment of the invention will be described. These functions are to enable the MBMC to perform all required processing and to perform the mentioned interactions with other protocols.

[0045] A first function provided by the MBMS protocol is a ‘generation of MBMC scheduling messages’. The MBMC receives scheduling information together with each MBMS message over the interface employed between the MBMSC 21 and the RNC 23. Based on this scheduling information, the MBMC generates at the UTRAN side schedule messages, and schedules MBMS message sequences accordingly. At the user equipment side, the MBMC evaluates the scheduled messages and indicates scheduling parameters to the RRC. These parameters are then used by RRC to configure the lower layers for discontinuous receptions of MBMS messages.

[0046] A multicast or broadcast multimedia service can consist of several sessions which shall be send together. One combined multicast session can contain for example sports video clips and second news. This requires a scheduling between the different multicast sessions, which is taken care of by a second function provided by the MBMC called ‘scheduling of MBMC sessions’. The transmission and evaluation of messages and scheduling information is carried out as by the function ‘scheduling of MBMC messages’.

[0047] There are basically two possible ways to implement a scheduling between sessions, which will be explained based on an example for a multicast service. In this example, the multicast service comprises a sports video clips session and a news session. The sports video clips session consists of five parts 1v, 2v, 3v, 4v and 5v, and the news session consists of two part 6n and 7n. In a first alternative, each multicast session will be scheduled independently and sequentially (serially). This means that for example multicast sessions which contain video will be scheduled first and after that multicast sessions which contain news will follow. In this case, parts 1v, 2v, 3v, 4v and 5v will be sent first, and parts 6n and 7n will only be sent after all parts of the video clips session have been transmitted.

[0048] In a second alternative, the multicast sessions will be scheduled simultaneously. In this case, part of the news and sports clips sessions could be sent for instance in the following order: 1v, 6n, 2v, 7n, 3v, 4v and 5v.

[0049] Another function provided by the MBMS protocol is ‘scheduling of MBMC service modes’. A scheduling decisions between the different service modes, i.e. multimedia multicast or multimedia broadcast, has to be carried out in both, the MBMSC 21 and the MBMC layer. The decisions are transmitted through the employed interface between the MBMSC 21 and the RNC 23. The MBMSC 21 is responsible for knowing how many MBMC sessions are currently going on at the UTRAN side. The required service mode scheduling on MBMC should be based on given priorities for sessions corresponding to different modes, indicated by the MBMSC 21 in each MBMSC data frame. In MBMC a session with a higher priority should always get ahead of data with a lower priority. The scheduling decision between the service modes which have the same priority should be based on the arrival of data from the MBMSC 21. How complex the scheduling algorithm for different service modes has to be is also dependent on the selected resource allocation and the channel structure for the multicast/broadcast and MBMC data services.

[0050] The data for both services that can be provided by the MBMSC 21 to the RNC 23, i.e. multicast and broadcast, are transmitted by the MBMC via the RLC and the MAC to the physical layer. The two modes of MBMS will require a prioritization due to the different nature of charging and applications that will run over them. Therefore, a further function provided by the MBMC is a ‘prioritization between MBMS multicast mode messages and MBMS broadcast mode messages’.

[0051] In addition, the two layer 2 sub-layers L2/BMC and L2/MBMC will require a function that co-ordinates the two different enabled services, in particular for scheduling and prioritizing MBMS and CBS messages in a harmonized way. Thus, an interaction is needed with the BMC on how data is forwarded to the RLC etc. A corresponding function ‘scheduling/prioritization between MBMS and CBS message’ is equally provided by the MBMS protocol.

[0052] Moreover, the MBMC provides a function ‘storage of MBM messages’ for storing MBMS messages. This function takes care more specifically of storing MBM messages received over the interface employed between the MBMSC 21 and the RNC 23 until a scheduled transmissions.

[0053] With the aid of yet another function ‘data discard’, the MBMC can discard such multicast related data, which has been considered to be invalid.

[0054] An additional function ‘traffic volume monitoring and radio resource request for MBMS’ is provided by the MBMC for periodically predicting the expected amount of MBMS traffic volume in kbps that is currently needed for the transmission of MBM messages. The function further indicates the expected amount of MBMS traffic to the RRC. Thus, this MBMC function determines at the UTRAN side the required transmission rate for a multicast or broadcast multimedia service based on the messages received over the interface employed between the MBMSC 21 and the RNC 23. Based on this calculation, the function then requests appropriate logical channel and transport channel resources from the RRC. Transport channels that could be the used are DSCH (Downlink Shared Channel) and/or FACH (Forward Access Channel) and/or the HS-DSCH (High Speed-Downlink Shared Channel) of HSDPA (High Speed Downlink Packet Access). Any suitable algorithm which is adapted to the respectively employed algorithm for transmitting MBM messages can be implemented for predicting the amount of MBMS traffic. The algorithm can also include the option that some parameters used in the prediction can be set or changed by the operator of the network.

[0055] The traffic monitoring can also have an impact on the Iu-interface in a form of flow control between the MBMC and a peer entity at the core network side. Such a peer entity can be either SGSN, or CBC, but also some other network element, like a new multicast related network element.

[0056] A further function is provided by the MBMC for the ‘transmission of MBMC messages to UE’. This function transmits the MBMC messages, i.e. equally scheduling and multicast or broadcast multimedia messages, to the user equipment 25 according to a determined schedule. The transmission follows again the protocol stack, thus the transmission takes place first from the MBMC to the RLC, then to the MAC and finally to the physical layer.

[0057] A ‘charging information support’ function interacts with the RLC, in case the latter operates in AM, in order to enable a charging based on the amount of data transmitted to a user equipment 25. This function is used to this end for collecting user equipment information regarding the amount of data, i.e. packets, received by a user equipment 25, based on the amount of acknowledged PDUs. The collected information can then be sent via the interface employed between the RNC 23 and the MBMSC 21 to the core network. The collected information can be transmitted in particular to a corresponding MBMS charging entity in the core network, which charges the user according to the received data.

[0058] For MBMC data transmissions supporting a MBMC PDU (protocol data unit) repetition, a further function called ‘retransmission/repetition’ provided by the MBMC performs the retransmission of data. This means that for instance no RLC level retransmission is introduced and that the UM RLC mode is used.

[0059] Moreover, the L2/MBMC sublayer must be aware of multicast related groups on that level so that it can submit multicast data to the correct cells under one RNC 23. This is taken care of by a ‘multicast group handling’ function provided by the MBMC.

[0060] Finally, a function is provided by the MBMC for identifying MBMS sessions and for initializing links between the MBMSC 21 and the MBMC protocol sublayer L2/MBMC of RNC 23. This function is called ‘identification of MBMS session and initialization of link between MBMSC and L2/MBMC’. Once the MBMSC 21 has received content from the core network, a message has to be sent to the L2/MBMC sublayer via the interface between the MBMSC 21 and the RNC 23 in order to initiate the session and to provide the session details.

[0061] Also on the side of the user equipment 25, a MBMC entity is provided, in order to enable the user equipment 25 to handle multicast/broadcast multimedia services. The MBMC entity of the user equipment 25 comprises a function ‘delivery of MBM messages to upper layer (NAS)’. This functions delivers the multicast or broadcast multimedia messages received from the core network via the interface provided between the MBMSC 21 and the RNC 23 to upper layers (NAS) in the respective user equipment 25. In a possible approach, only non-corrupted MBM messages are delivered. It is also possible, however, that even though the data packet is corrupted the codec supported by application layer may be capable of using these erroneous packets as well. In this case, also corrupted MBM messages should be delivered.

[0062] The MBMC entity of the user equipment 25 may further include a function for determining the amount of MBM data received for charging purposes. The determined amount of data is then forwarded via the radio interface Uu to the cellular network.

[0063] It is to be noted, that this set of functions can be amended in any required or desired way. Moreover, functions that turn out not to be required can be omitted, and additional desired functions can be added.

Claims

1. Network element (23) for a radio access network (22) of a cellular network supporting the transmission of multicast and broadcast multimedia services via a radio interface (Uu) to user equipment (25), which network element (23) comprises radio interface protocols associated to different protocol layers including a data link layer (layer 2), wherein said data link layer comprises a dedicated multicast broadcast multimedia control sublayer (L2/MBMC) for a multicast broadcast multimedia control protocol (MBMC), which MBMC adapts multicast and broadcast multimedia services, originating from a core network of said cellular network, for transmission on said radio interface (Uu).

2. Network element (23) according to claim 1, wherein said dedicated multicast broadcast multimedia control sublayer (L2/MBMC) is transparent for other services than multicast and broadcast multimedia services.

3. Network element (23) according to one of the preceding claims, comprising a radio resource control protocol (RRC) in a network layer (layer 3) situated above said data layer comprising said MBMC, wherein said MBMC interacts with said radio resource control protocol for at least one of the following: establishment of links to user equipment (25) via said radio interface (Uu) for the transmission of MBM data; modifications of links to user equipment (25) established for the transmission of MBM data via said radio interface (Uu); releases of links to user equipment (25) established for the transmission of MBM data via said radio interface (Uu); traffic control of MBM data that is to be transmitted via said radio interface (Uu); and measurements of the traffic amount of MBM data that is to be transmitted via said radio interface (Uu) in at least one direction.

4. Network element (23) according to one of the preceding claims, wherein said MBMC interacts with an Iu-UP (user plane) interface or a cell broadcast center (11) on a user plane for at least one of the following: transmission of MBM data via said radio interface (Uu) on a link established to user equipment (25); transmission of MBM data related control information via said radio interface (Uu) on a link established to user equipment (25); flow control for transmissions of MBM data via said radio interface (Uu) on a link established to user equipment (25); and multicast session related control for the transmission of MBM data via said radio interface (Uu) on a link to user equipment (25).

5. Network element (23) according to one of the preceding claims, wherein said MBMC interacts with a radio link control sublayer (L2/RLC) located below said dedicated sublayer (L2/MBMC) for said MBMC for at least one of the following: transmission of MBM data via said radio interface (Uu) on a link established to user equipment (25); transmission of MBM security related information via said radio interface (Uu) on a link established to user equipment (25); discard MBM information that was destined to be transmitted to user equipment (25); and transmission of a wake up message via said radio interface (Uu) on a link established to user equipment (25);

6. Network element (23) according to one of the preceding claims, wherein said MBMC interacts with a medium access control layer of said data link layer located below said dedicated sublayer (L2/MBMC) for at least one of the following: dealing with at least coverage and/or congestion issues; scheduling at least some specific kind of data; and reduction of the multicast data rate if required.

7. Network element (23) according to one of the preceding claims, wherein said MBMC interacts with a broadcast/multicast control layer. (L2/BMC), in particular for an exchange of scheduling related information.

8. Network element (23) according to one of the preceding claims, wherein any interaction of said dedicated sublayer (L2/MBMC) for said MBMC with other protocol layers (RRC, L2/RLC) is specified in terms of a primitive.

9. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for scheduling messages that are to be transmitted.

10. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for scheduling all sessions belonging to a single MBM service.

11. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function performing a scheduling decision between different MBMC service modes, i.e. multimedia multicast or multimedia broadcast.

12. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for prioritizing between MBMS multicast mode messages and MBMS broadcast mode messages.

13. Network element (23) according to one of the preceding claims, comprising a further dedicated sublayer (L2/BMC) for a broadcast/multicast control protocol (BMC) adapting non-multimedia broadcast/multicast services received from said core network for transmissions on said radio interface (Uu), wherein said MBMC comprises a function for coordinating non-multimedia broadcast/multicast services and multicast/broadcast multimedia services.

14. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for storing MBM messages.

15. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for discarding selected data.

16. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for predicting an expected amount of a traffic volume that is currently needed for the transmission of MBM messages, and for requesting appropriate radio resources for a transmission of said traffic via said radio interface (Uu), and/or for performing an appropriate flow control between said MBMC and a peer entity at the core network side of said cellular network.

17. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for transmitting MBMC messages, including scheduling information and MBM messages, via said radio interface (Uu) to user equipment (25).

18. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for collecting information on the amount of data received by a user equipment (25) and for forwarding said information to a network entity of said cellular network charging said user equipment (25) according to a determined amount of received data.

19. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for repeating a transmission.

20. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for handling the submission of multicast data to selected cells.

21. Network element (23) according to one of the preceding claims, wherein said MBMC comprises a function for identifying a MBMS session and for initializing a link to a multicast broadcast multimedia service center (MBMSC, 21) providing MBMS messages, to which MBMSC (21) said network element (23) is connected via an interface (Iu-bc, Iu-ps, Iux).

22. Network element (23) according to one of the preceding claims, wherein said network element (23) is an RNC (radio network controller) for an UTRAN (UMTS terrestrial radio access network) of a UMTS (universal mobile telecommunication services) network.

23. Radio access network (22) for a cellular network comprising at least one network element (23) according to one of the preceding claims.

24. Radio access network (22) according to claim 23, wherein said radio access network (22) is an UTRAN (UMTS terrestrial radio access network) for a UMTS (universal mobile telecommunication services) network comprising at least one RNC (radio network controller) as at least one network element (23) according to one of claims 1 to 22.

25. Cellular network comprising a multicast broadcast multimedia service center (MBMSC, 21) connected via an interface (Iu-bc, Iu-ps, Iux) to at least one network element (23) according to one of claims 1 to 22.

26. Cellular network according to claim 25, wherein said cellular network is a UMTS (universal mobile telecommunication services) network, comprising at least one RNC (radio network controller) as at least one network element (23) according to one of claims 1 to 22.

27. Cellular network according to claim 26, wherein said interface is one of an Iu-ps, Iu-bc or Iux interface.

28. User equipment (25) comprising a multicast/broadcast multimedia control entity for handling multicast and broadcast multimedia services received via a radio interface (Uu) from a cellular network according to one of claims 25 to 27.

29. User equipment (25) according to claim 28, wherein said multicast/broadcast multimedia control entity includes a function for delivering received MBM messages of a multicast and broadcast multimedia service to an upper layer in said user equipment (25).

30. User equipment (25) according to claim 28 or 29, wherein said multicast/broadcast multimedia control entity includes a function for determining the amount of MBM data received and for forwarding said information via said radio interface (Uu) to said cellular network.

31. Radio access based communications system comprising a cellular network according to one of claims 25 to 27.

32. Radio access based communications system according to claim 29, comprising at least one user equipment (25) according to one of claims 28 to 30.

33. Method for providing multicast broadcast multimedia services from a cellular network via a radio interface (Uu) to user equipment (25), which cellular network comprises a radio access network (22) with a network element (23), which network element (23) comprises radio interface protocols associated to different protocol layers including a data link layer (layer 2), said method comprising adapting multicast and broadcast multimedia services, originating from a core network of said cellular network, for a transmission on said radio interface (Uu) by a multicast broadcast multimedia control protocol (MBMC) of a dedicated multicast broadcast multimedia control sublayer (L2/MBMC), which dedicated sublayer (L2/MBMC) is a sublayer of said data link layer (layer 2) of said network element (23).