KR20030080946A - Apparatus for transmitting control information for multimedia broadcast/multicast service in mobile communication system and method thereof - Google Patents

Abstract

The present invention provides a multicast multimedia broadcasting service (MBMS) having a plurality of types in a mobile communication system, comprising: requesting a service provision request for a first MBMS, which is any one of the plurality of types, from user terminals; If detected, determining a wireless channel to which the first MBMS data is to be transmitted, generating wireless channel information related to the determined wireless channel, and including the wireless channel information and a service identifier indicating the first MBMS. Generating information and transmitting the generated information to the user terminals through a common control channel.

Description

Apparatus and method for transmitting control information for multicast multimedia broadcasting service in mobile communication system {APPARATUS FOR TRANSMITTING CONTROL INFORMATION FOR MULTIMEDIA BROADCAST / MULTICAST SERVICE IN MOBILE COMMUNICATION SYSTEM AND METHOD THEREOF}

The present invention relates to a mobile communication system, and more particularly, to an apparatus and method for transmitting radio channel configuration information for providing a multicast multimedia broadcasting service through a common channel.

Today, due to the development of the telecommunications industry, the services provided by the code division multiple access (CDMA) mobile communication system are not only voice services but also large data such as packet data and circuit data. It is evolving into a multicasting multimedia communication that transmits. Accordingly, there is a broadcast / multicast service that provides a service from one data source to a plurality of user equipments (hereinafter referred to as UEs) in order to support the multicasting multimedia communication. . The broadcast / multicast service is a cell broadcast service (hereinafter, referred to as a "CBS service"), a message-oriented service, and a multicast multimedia broadcast service supporting multimedia forms such as real-time video, voice, still image, and text ( Multimedia Broadcast / Multicast Service, hereinafter referred to as "MBMS".

Next, a network structure for providing the MBMS service in the mobile communication system will be described with reference to FIG. 1.

1 is a diagram schematically illustrating a network structure for providing an MBMS service in a mobile communication system.

Referring to FIG. 1, first, a multicast / broadcast-service center (MB-SC) hereinafter referred to as a “MB-SC” 110 may be a source for providing an MBMS stream. source), the MB-SC 110 schedules a stream for the MBMS service and transmits the stream to the transport network 111. The transport network 111 refers to a network existing between the MB-SC 110 and a service packet radio service support node (SGSN) 100. In addition, the stream for the MBMS service received from the MB-SC 110 is transferred to the SGSN 100. Here, the SGSN 100 may be configured with a Gateway Packet Radio Service Support Node (GGSN) (hereinafter referred to as "GGSN"), an external network, and the like and receive a plurality of MBMS services at any time. UEs, for example, UE1 104, UE2 105, UE3 106 belonging to Node B 1 102, and UE4 107, UE5 108 belonging to Node B2 103 exist. Let's assume. The SGSN 100 receiving the stream for the MBMS service in the transmission network 111 controls the MBMS-related services of subscribers, ie, UEs, that want to receive the MBMS service. And control MBMS related services such as selectively transmitting MBMS service data to a specific Radio Network Controller (RNC) 101. In addition, the SGSN 100 configures and manages an SGSN service context regarding the MBMS service X, and transfers the stream for the MBMS service to the RNC 101 again. The RNC 101 controls a plurality of Node Bs, transmits MBMS service data to a Node B in which a UE requesting MBMS service among Node Bs managed by the RNC 101 exists, and also provides the MBMS service. The RNC service context is configured and managed with respect to the MBMS service X by controlling a radio channel to be set and having a stream for the MBMS service received from the SGSN 100. As shown in FIG. 1, an MBMS service is provided between a Node B 102, for example, a Node B 102 and UEs 104, 105, and 106 belonging to the Node B 102. Only one radio channel is configured for this purpose. Although not shown in FIG. 1, a Home Location Register (HLR) is connected to the SGSN 100 to perform subscriber authentication for an MBMS service.

Next, a signal flow for initiating MBMS service in the mobile communication system will be described with reference to FIG. 2.

2 is a signal flow diagram illustrating a procedure for initiating an MBMS service in a mobile communication system.

Referring to FIG. 2, first, the MB-SC 110 notifies UEs of the MBMS service subscribers of menu information on MBMS services that can be provided (step 201). Here, the menu information is information indicating at what time a specific MBMS service is provided, and the MB-SC 110 broadcasts the menu information to a predetermined service area or MBMS. It can only transmit to UEs with a service request. MB-SC informs the MBMS service identifier for differentiating and distinguishing each MBMS service through the menu information. In FIG. 2, the MBMS service subscriber is assumed to be the UE 104 for convenience of description. The UE 104 notified of the menu information selects a specific MBMS service to be serviced from the menu information, and transmits a service request for the selected MBMS service to the MB-SC 110. In requesting an MBMS service, an identifier of a service to be received by the UE is selected from among MBMS service identifiers received through the menu information, and information of the UE to receive the MBMS service is transmitted together. Of course, the service request is performed through the paths described in FIG. 1, that is, the MB-SC via the Node B 102, the RNC 101, the SGSN 100, and the transport network 111 in the UE 104. Forwarded to 110. Then, the MB-SC 110 that receives the service request for the specific MBMS service of the UE 104 transmits a response to the service request to the UE 104 (step 201). At this time, as in the case of the service request, the response to the service request is transmitted from the MB-SC 110 to the UE 104 through the transmission network 111, the SGSN 100, and the RNC 101. Delivered. Here, the transmission network 111, the SGSN 100, and the RNC 101 store a UE identifier indicating the UE 104 requesting the specific MBMS service, and actually start the specific MBMS service. When the stored UE identifier is used. In this way, the network, that is, the MB-SC 110, the transmission network 111, the SGSN 100, and the RNC 101 determine the identifiers and the number of UEs to receive the specific MBMS service. .

In this state of completing a request and response for a specific MBMS service, the MB-SC 110 transmits a SERVICE ANNOUNCEMENT message to the UE 104 indicating that the specific MBMS service is to be started in the near future (203). step). In the description of FIG. 2, the UE 104 has been described on the assumption that there is one UE that wants to receive a specific MBMS service. ), The transport network 111, the SGSN 100, and the RNC 101 determine the number of UEs and an identifier indicating each when there are service requests and responses for a specific MBMS service from multiple UEs. Therefore, the service guide message may be delivered to each of the plurality of UEs. In addition, the service announcement message is transmitted to the UE 104 through the transport network 111, the SGSN 100, and the RNC 101, wherein a paging procedure defined in the UMTS standard is performed. process can be used. Here, the reason why the MB-SC 110 transmits the service guide message is that the transmission network 111 on the network, the SGSN 100, and the RNC 101 can set a transmission path for providing the MBMS service. It is to allow for a certain amount of time, and also to identify the UEs to receive the MBMS service.

Upon receiving the service announcement message, the UE 104 transmits a SERVICE CONFIRM message to the MB-SC 110 confirming the fact that it wants to receive the specific MBMS service (step 204). The service confirmation message is also transmitted to the MB-SC 110 through the transport network 111, the SGSN 100, and the RNC 101. In this process, the transport network 111 and the SGSN 100 are transmitted. And, the RNC 101 can identify the service area and the UE to be provided with the specific MBMS service, and actually configures a transmission path for providing the specific MBMS service. In this state in which a transmission path is configured on the network, the RNC 101 configures a radio channel, that is, a radio bearer, for transmitting a stream for the MBMS service with the UE 104 (step 205). The SGSN 100 configures a transmission path for transmitting a stream for the MBMS service with the RNC 101, that is, an MBMS bearer (step 206). Here, the RNC 101 configures a radio bearer only with Node Bs in which UEs that make a service request for the MBMS service exist. Likewise, the SGSN 101 includes UEs that make a service request for the MBMS service. Configure the MBMS bearer only with the RNC. As such, the MB-SC 110 transmits a stream for an MBMS service at a corresponding point in time with a transmission path established on a network, and the stream for the MBMS service is transmitted to the UE 104 through the configured transmission paths. ) And the actual MBMS service is started (step 207).

As described above, in order to provide the MBMS service, a plurality of control information is required, and in order to transmit such control information to each of the corresponding UEs, a plurality of message transmission and reception processes are required. Therefore, in providing an MBMS service, there is a need for a method of transmitting control information, such as control information such as radio channel configuration information, to a plurality of UEs through a control message.

Accordingly, an object of the present invention is to provide an apparatus and method for common transmission of control information for each MBMS type to UEs providing the same MBMS in a mobile communication system.

Another object of the present invention is to provide an apparatus and method for transmitting radio channel configuration information through a common channel to UEs providing the same MBMS in a mobile communication system.

Another object of the present invention is to provide an apparatus and method for transmitting radio channel configuration information through a common control channel to UEs providing the same MBMS in a mobile communication system.

The transmission method of the present invention for achieving the above objects; A method for providing a multicast multimedia broadcasting service (MBMS) having a plurality of types in a mobile communication system, the method comprising: detecting a request for providing a service for a first MBMS, which is any one of the plurality of types, from user terminals; Determining a wireless channel to transmit the first MBMS data, generating wireless channel information related to the determined wireless channel, and generating wireless channel related information including the wireless channel information and a service identifier indicating the first MBMS; And transmitting to the user terminals through a common control channel.

The receiving method of the present invention for achieving the above objects; The wireless network controller provides a multicast multimedia broadcasting service (MBMS) having a plurality of types in a mobile communication system, and a user terminal requesting to receive an MBMS of any one of the plurality of types provides the specific MBMS. A method for receiving, the method comprising: receiving wireless channel related information through a common control channel, detecting a service identifier included in the received wireless channel related information, and a service in which the detected service identifier indicates the specific MBMS; If the identifier is characterized in that it comprises the step of setting up or release the radio channel to correspond to the radio channel information included in the radio channel related information.

The transmitting device of the present invention for achieving the above objects; The wireless network controller provides at least two or more multicast multimedia broadcast services (MBMSs) received from a multicast / broadcasting-service center, wherein at least two or more user terminals belonging to a base station connected with the wireless network controller are the MBMSs. An apparatus for transmitting radio channel information for providing an MBMS to the user terminals in a mobile communication system requiring the same particular MBMS to be provided, the request to receive the specific MBMS from the user terminals. Is detected, configure a service context including a service identifier indicating the specific MBMS, and radio resource control for generating radio channel information required for radio channel setting for providing a specific MBMS to the user terminals existing in the service context Layer and the wireless stay A radio link control layer for segmenting null information in accordance with a preset size and assigning a serial number to the segmented data; and designating a user terminal to receive the segmented data in the serialized segmented data. And a medium access control layer for generating wireless channel related information by inserting a user terminal identifier and channel type information indicating a type of a channel to which the segmented data is to be transmitted.

The receiving device of the present invention for achieving the above objects; The wireless network controller provides at least two or more multicast multimedia broadcast services (MBMSs) received from a multicast / broadcasting-service center, wherein at least two or more user terminals belonging to a base station connected with the wireless network controller are the MBMSs. An apparatus for receiving radio channel information for providing an MBMS transmitted by the radio network controller in a mobile communication system requiring a specific MBMS to be provided, wherein the transport blocks are received from a physical layer. For each of the port blocks, channel type information indicating a type of a channel on which the transport block is transmitted is read, and when the channel type information is a common control channel, the transport is transmitted to a radio link control layer that is in charge of the common control channel. Medium that delivers blocks A radio link control layer configured to generate radio channel related information by using additional information of transport blocks received from the media access control layer, and transmit the generated radio channel related information to a radio resource control layer; Examine the service identifier of the service and, if the service identifier is a service identifier indicating the requested specific MBMS, control to set a wireless channel for receiving the specific MBMS stream according to the wireless channel information included in the wireless channel related information. It characterized in that it comprises a radio resource control layer.

1 schematically illustrates a network structure for providing an MBMS service in a mobile communication system;

2 is a signal flow diagram illustrating a procedure for initiating an MBMS service in a mobile communication system.

3 is a signal flow diagram illustrating an MBMS service providing process according to an embodiment of the present invention.

4 is a diagram schematically illustrating transmission of radio channel configuration information for an MBMS service according to another embodiment of the present invention.

5 is a diagram schematically illustrating wireless channel configuration information transmission for an MBMS service according to another embodiment of the present invention.

6 illustrates a structure of a user terminal for performing a function in an embodiment of the present invention.

7 is a flowchart illustrating a process of operating a user terminal according to another embodiment of the present invention.

8 illustrates a UTRAN structure for performing a function in an embodiment of the present invention.

9 is a flowchart showing the operation of the UTRAN according to another embodiment of the present invention

10 is a diagram schematically illustrating wireless channel configuration information transmission for an MBMS service through a common control channel according to another embodiment of the present invention.

11 is a diagram schematically showing a protocol structure of a UMTS communication system performing a function in an embodiment of the present invention.

12 is a flowchart illustrating a process of operating a user terminal according to another embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that in the following description, only parts necessary for understanding the operation according to the present invention will be described, and descriptions of other parts will be omitted so as not to distract from the gist of the present invention.

3 is a signal flow diagram illustrating an MBMS service providing process according to an embodiment of the present invention.

Before describing FIG. 3, it is assumed that the structure of the mobile communication system is the same as the structure of the mobile communication system described with reference to FIG. 1. Before describing FIG. 3, an RNC service context (SERVICE CONTEXT) and a service managed by a Radio Network Controller (RNC) 101 are first managed. The SGSN SERVICE CONTEXT managed by the Packet Radio Service Supporting Node (SGSN) (hereinafter referred to as "SGSN") 100 will be described. The RNC 101 and the SGSN 100 manage service related information for each multicast multimedia broadcast service (hereinafter referred to as "MBMS") service, and manage related information managed for each MBMS service. SERVICE CONTEXT ", and the related information managed for each MBMS service is a list of UEs (UE: User Equipment, hereinafter referred to as" UE ") that want to provide MBMS service, that is, want to receive MBMS service. UE identifiers of the UEs, information such as a service area where the UEs are located and information such as a quality of service (QoS) hereinafter required to provide MBMS service, and the like. have.

The RNC service context and the information included in the SGSN service context will be described in more detail as follows.

First, the information included in the RNC SERVICE CONTEXT is as follows.

RNC SERVICE CONTEXT = {Multicast / Broadcast-Service Center (MB-SC) (MB-SC) (cell) identifier [identifiers of UE located in that cell], QoS required to provide MBMS service}

As described above, one RNC service context is composed of one service identifier, a plurality of cell identifiers, and a plurality of UE identifiers. In addition, a service identifier includes an MB-SC service identifier and an RNC service identifier. The MB-SC service identifier is a unique identifier assigned to the MBMS service provided by the MB-SC 110. The RNC service identifier is an MBMS service in the RNC. Identifier given to. In this case, the RNC service identifier recognizes only the UE 104 and the RNC 101, and transmits a signal between the RNC 101 and the UE 104 including a radio channel, that is, in a radio bearer. It can be given to recognize the service more efficiently.

Secondly, the information included in the SGSN SERVICE CONTEXT is as follows.

SGSN SERVICE CONTEXT = {MB-SC Service Identifier, SGSN Service Identifier, Identifier of RNC to receive or receive MBMS service [list of UEs located in that RNC], QoS required to provide MBMS service}

The SGSN service identifier in the SGSN SERVICE CONTEXT is an identifier assigned by the SGSN 100 and is used to efficiently recognize the MBMS service between the UE 104 and the SGSN 100. In addition, other information may be used instead of an identifier of an RNC in the SGSN SERVICE CONTEXT. For example, several RNCs may be preset in one service area, and then the RNC identifier may be replaced with a service area identifier corresponding one-to-one to the service area.

The RNC SERVICE CONTEXT and SGSN SERVICE CONTEXT are continuously updated during the MBMS service providing process to be described below, and the RNC 101 and the SGNS 100 may randomly set the RNC SERVICE CONTEXT and SGSN SERVICE CONTEXT. It is used to determine the cell to transmit the stream for the service, i.e., the base station and the RNC, and to identify the UEs receiving the service. Next, a process of providing an actual MBMS service will be described with reference to FIG. 3.

First, the UE 104 transmits a first MBMS service request message to the RNC 101 to request service provision for an arbitrary MBMS service “X” (step 301). Here, the first MBMS service request message includes an MB-SC service identifier, which is a service identifier indicating an MBMS service that the UE 104 wants to receive, and a user identifier for identifying a UE that transmits the first MBMS service request message. Included. Receiving the first MBMS service request message, the RNC 101 updates the configured RNC SERVICE CONTEXT, that is, adds the user identifier of the UE 104 to the receiver related information of the configured RNC SERVICE CONTEXT, A second MBMS service request (MBMS SERVICE REQUEST 2) that adds a cell identifier of the cell to which the UE 104 belongs, that is, a cell B of the Node B 2 102 to the service area related information, and requests to provide a service for the MBMS service X. The message is sent to the SGSN 100 (step 302). The generation and update of the RNC service identifier may be performed when the MBMS SERVICE REQUEST1 message is received (step 301), or when the MBMS SERVICE RESPONSE2 message is received (305). Step). . Here, in the above description, the case where the RNC 101 updates the RNC SERVICE CONTEXT has been described. However, when the MBMS service X requested to provide the service is a new MBMS service, the RNC 101 performs an operation on the MBMS service X. After newly configuring the RNC service context, the information is managed in the newly configured RNC service context. In addition, the second MBMS service request message includes an MB-SC service identifier that designates the MBMS service that the UE 104 wishes to receive, and a user identifier that transmits the second MBMS service request message. That is, if there is a new UE that wants to receive the MBMS service, if there is a UE that wants to receive the service in the past, when the MBMS service is performed later, it has the same RNC service identifier to send control information on the Radio Link afterwards. If the control information is informed and the service requested by the new UE to receive the MBMS service is new, an RNC service identifier for the new MBMS service is generated and managed. In this case, the allocation of the RNC service identifier may be sequentially generated according to the service type, or may be efficiently allocated and managed by a certain formula. That is, in more detail, generating or updating the RNC service identifier updates or adds an RNC Servic Context when the RNC receives MBMS Service Request1 from the UE, and if it is determined that a new RNC service identifier is needed, the MBMS service. The RNC service identifier may be generated when the MBMS Service Response 2 message is received, or the RNC service identifier may be generated together with the MBMS Service Request message. Since this is an implementation problem, of course, it can be sufficiently modified.

The SGSN 100 updates the configured SGSN SERVICE CONTEXT in response to receiving the second MBMS service request message from the RNC 101, that is, the UE 104 is stored in the receiver related information of the configured SGSN SERVICE CONTEXT. A third MBMS service request (RNC) to which the UE 104 belongs, i.e., an identifier of the RNC 101, to request service provision for the MBMS service X; MBMS SERVICE REQUEST 3) message is transmitted to the MB-SC 110 (step 303). Here, in the above description, although the SGSN 1400 updates the SGSN SERVICE CONTEXT, when the MBMS service X requested to provide the service is a new MBMS service, the SGSN 100 is configured for the MBMS service X. After newly configuring the SGSN SERVICE CONTEXT, the information is managed in the newly configured SGSN SERVICE CONTEXT. In addition, the third MBMS service request message includes an MB-SC service identifier. Upon receiving the third MBMS service request message, the MB-SC 110 adds the SGSN 100 that has transmitted the third MBMS service request message to the MBMS service X service providing list and adds the third MBMS service request message. In step 304, a third MBMS SERVICE RESPONSE 3 message indicating normal reception is transmitted to the SGSN 100. In this case, the third MBMS service response message includes an MB-SC service identifier.

Upon receiving the third MBMS service response message, the SGSN 100 updates the service identifier for the MBMS service X, that is, the SGSN service identifier to the service identifier related information of the SGSN SERVICE CONTEXT and updates the third MBMS service. In step 305, a second MBMS SERVICE RESPONSE 2 message indicating that a service request message has been successfully received is transmitted to the RNC 101. Here, the SGSN 100 allocates the SGSN service identifier in response to receiving the third MBMS service request message, which is a service identifier managed by the SGSN 100 in response to the MBMS service X. After receiving the second MBMS service response message, the RNC 101 allocates an RNC service identifier, updates the allocated RNC service identifier to the service identifier related information of the RNC SERVICE CONTEXT, and updates the second MBMS. In step 306, a first MBMS SERVICE RESPONSE 1 message indicating that a service request message has been successfully received is transmitted to the UE 1404. Here, the information about the RNC service identifier may be included in an MBMS service response message and transmitted to the UE. Here, the RNC 101 allocates an RNC service identifier upon receiving the second MBMS service response message, which is a service identifier managed by the RNC 101 corresponding to the MBMS service X. Here, the first MBMS service request message includes an MB-SC service identifier, an SGSN service identifier, and an RNC service identifier. Upon receiving the first MBMS service response message, the UE 104 waits after storing the SGSN service identifier and the RNC service identifier.

On the other hand, the MB-SC 1410 notifies that the MBMS service X will start within a short time, and further, a third MBMS service for identifying a list of UEs, i.e., identifiers of UEs, to be actually provided with the MBMS service X. A MBMS SERVICE NOTIFY 3 message is transmitted to the SGSN 110 (step 307). Here, the third MBMS service notification message includes an MB-SC service identifier, a service start time at which the MBMS service X actually starts, and QoS related information. Upon receiving the third MBMS service notification message, the SGSN 100 sets up a radio bearer for providing the MBMS service X on the transmission network 111, and also establishes an Iu connection for the MBMS service X. UE that wants to receive MBMS service X in real time after setting and updating QoS related information and Iu connection related information among service area related information to SGSN SERVICE CONTEXT. A second MBMS SERVICE NOTIFY 2 message is sent to the RNC 101 to determine the list of users (step 308). Here, the second MBMS service notification message includes an MB-SC service identifier, an SGSN service identifier, service start time, and QoS related information. Receiving the second MBMS service notification message, the RNC 101 checks the UEs identifiers present in the managed RNC SERVICE CONTEXT and the cells to which the UEs belong, and starts the MBMS service X in a short time to the UEs. In step 309, a first MBMS SERVICE NOTIFY 1 message is sent to the UE 104. Here, the first MBMS service notification message includes an MB-SC service identifier, an RNC service identifier, service start time, and QoS related information.

Upon receiving the first MBMS service notification message, the UE 104 determines whether the MBMS service X is actually provided, stores the received QoS related information, and then normally receives the first MBMS service notification message. A first MBMS NOTIFY RESPONSE 1 message is transmitted to the RNC 101 (step 310). Here, the first MBMS notification response message includes an RNC service identifier and a UE identifier. The RNC 101 receiving the first MBMS notification response message is updated to add a UE identifier of the UE that has transmitted the first MBMS notification response message and an identifier of a cell to which the UE belongs to the RNC service context. In operation 311, a second MBMS NOTIFY RESPONSE 2 message indicating that the second MBMS service notification message is normally received is transmitted to the SGSN 100. In step 310, it is assumed that the RNC 1401 receives a first MBMS notification response message only from the UE 104, but it is also possible to receive the first MBMS notification message from a plurality of UEs. In this case, a UE identifier for each of the plurality of UEs and a cell identifier of cells to which the UEs belong are updated to be added to the RNC service context.

Meanwhile, the second MBMS notification response message includes an MB-SC service identifier and a UE identifier. Upon receiving the second MBMS notification response message, the SGSN 100 updates the managed SGSN SERVICE CONTEXT in the form of adding the identifiers and RNC identifiers of the UEs included in the second MBMS notification response message. The SGSN 100 transmits a stream for transmitting the stream for the MBMS service X to the RNC 101 that has transmitted the second MBMS notification response message, that is, a Radio Access Bearer (RAB). A RAB ASSIGNMENT REAUEST message for setting RAB "is transmitted to the RNC 101 (step 312). Here, the RAB assignment request message includes an MB-SC service identifier and QoS information. Receiving the RAB assignment request message, the RNC 101 identifies a cell and a UE having an identifier in the managed RNC service context, and wirelessly links the cell, that is, the Node B 102, according to the received QoS information. Prepare to set (Radio Link), and at this time, by sending the information on the RNC service identifier to send the information about the Radio Link that had previously been sent to each UE for the service through the RNC service identifier collectively Will be. In this case, when the UE is Cell_FACH, the control information is collectively transmitted through the FACH. When the UEs are Cell_DCH, the control information is transmitted in the same manner as in the conventional art, or the UEs are transferred to the Cell_FACH state. It sends a control information on the channel to send the MBMS service through the FACH by receiving the request, and receives the information to form a Radio Link for the channel to receive the actual MBMS service data. The UE, i.e., the UE 104, prepares to establish a radio bearer. The RNC 101 then sends an MBMS RADIO LINK SETUP REQUEST message to the Node B 102 requesting to establish the radio link for transmitting the stream for the MBMS service X. (Step 313). Here, the MBMS radio link setup request message includes channelization code information and scrambling code information to be applied to a radio link for transmitting the stream for the MBMS service X. Receiving the radio link setup request message, the Node B 102 sets up the radio link using the channelization code information and the scrambling code information included in the radio link setup request message and then sets up the RNC 101. In step 314, a RADIO LINK SETUP RESPONSE message indicating that a radio link setup has been performed is performed.

The RNC 101 receives the radio link setup response message and transmits the radio bearer to UEs located in a cell belonging to the Node B 102 that transmits the radio link setup response message, that is, the UE 104. In step 315, a RADIO BEARER SETUP message is transmitted requesting that the R2 be set up. Here, the radio bearer setup message includes an RNC service identifier, service start time, channelization code information, and scrambling code information. Upon receiving the radio bearer setup message, the Node B 102 sets up a radio bearer with the information included in the received radio bearer setup message and then indicates that the radio bearer setup is completed to the RNC 101. The RADIO BEARER SETUP COMPLETE message is transmitted (step 316). In this case, the radio bearer setup complete message includes an RNC service identifier and a user identifier. After receiving the radio bearer setup complete message, the RNC 101 updates the RNC service context to add the identifier of the UE 104 that has transmitted the radio bearer setup complete message, and then transmits the MBMS service X. The MBMS RAB Assignment Response message indicating that the configuration is completed is transmitted to the SGSN 100 (step 317). In this case, the MBMS RAB assignment response message includes an MB-SC service identifier and a plurality of UE identifiers. Upon receiving the MBMS RAB assignment response message, SGSN 100 updates the managed SGSN SERVICE CONTEXT to add identifiers of UEs included in the MBMS RAB assignment response message and then prepares to receive the MBMS service X. A third MBMS NOTIFY RESPONSE 3 message is transmitted to the MB-SC 110 indicating that the service is completed (step 318). The third MBMS notification response message includes an IP multicast address. As such, when the MB-SC 110 receives the third MBMS notification response message, a stream for MBMS service X is provided between the MB-SC 1110 and the UE 104 (step 319).

Message types and operations in the respective components for initiating any of the MBMS service X described above are shown in Tables 1 and 2 below. Of course.

Among the above-mentioned messages, the MBMS RAB assignment request message, the MBMS RAB assignment response message, the MBMS radio link setup request message, the MBMS radio link setup response message, the MBMS radio bearer setup message, and the MBMS radio bearer setup complete message are new. Message, or modify the RAB assignment request message, RAB assignment response message, radio link setup request message, radio link setup response message, radio bearer setup message, and radio bearer setup complete message that are currently used in the UMTS system. It can be defined in one form. However, it is a matter of course that the messages contain various types of information for the MBMS service.

Meanwhile, when there are a plurality of UEs to be provided with the MBMS service in the MBMS service providing process described with reference to FIG. 3, the MBMS such as channelization code information and scrambling code information to each of the plurality of UEs through an MBMS RADIO BEARER SETUP message. Information for configuring a wireless channel for receiving a stream for a service must be conveyed. Here, a method of transmitting the radio channel configuration information to each of the plurality of UEs firstly transmits an MBMS RADIO BEARER SETUP message to each of the UEs, and secondly, the same one to the UEs belonging to one cell. There is a way to send MBMS RADIO BEARER SETUP message. Here, the first method is to apply the method applied in the general UMTS as it is, that is to transmit the radio channel configuration information for each of the UEs one-to-one, the second method to the radio channel configuration information proposed by the present invention It is a transmission method.

Next, a method of transmitting radio channel configuration information to a plurality of UEs through one control message will be described with reference to FIGS. 4 and 5.

First, FIG. 4 is a diagram schematically illustrating transmission of radio channel configuration information for an MBMS service according to another embodiment of the present invention.

First, before describing FIG. 4, first, UE1 421, UE2 422, UE3 423, UE4 431, and UE5 432 have requested the first MBMS service, which is an optional MBMS service. According to the 1MBMS service request, it will be assumed that the process is completed until step 314, that is, the radio link setup, as described with reference to FIG. 3. In addition, the UE1 421, the UE2 422, the UE3 423, and the UE4 425 may receive a forward access channel (FACH) and receive random information (RACH). Access Channel (hereinafter referred to as "RACH") information, the UE1 (421), UE2 (422), UE3 (423), UE4 (425) is in a state that can receive messages transmitted through the FACH (Hereinafter referred to as "Cell_FACH state"), UE5 431 is assumed to be in a state of setting a dedicated channel (DCH: Dedicated CHannel, hereinafter referred to as "DCH") (hereinafter referred to as "Cell_DCH state") do.

First, the RNC 410 transmits one MBMS RADIO BEARER SETUP message for each of the UEs, and the UEs transmit an MBMS RADIO BEARER SETUP COMPLETE message to the RNC 410 in response to an MBMS RADIO BEARER SETUP message. do. The RNC 410 transmits an MBMS RADIO BEARER SETUP message to the UEs in the Cell_FACH state through the FACH configured in each cell, and the configuration of the message transmitted through the FACH is shown in FIG. 4. That is, since the FACH is a channel shared by a plurality of UEs, it is necessary to designate a receiving UE to receive the FACH in messages transmitted through the FACH, but the UE indicating the UE to receive the FACH in UE identifier information 440. Identifier is included. Here, the UE identifier information is allocated for each UE when the UE first accesses the system, and is composed of 16 bits or 32 bits. The other control information 450 means control information other than the UE identifier information 440, and the like includes multiplexed information. Also, the payload 460 includes information actually included in the MBMS RADIO BEARER SETUP message. Are present.

Meanwhile, the RNC 410 transmits an MBMS RADIO BEARER SETUP message to the UE5 431 in the Cell_DCH state through the DCH. Since the DCH is a channel whose characteristic is exclusively assigned to a specific UE, the MBMS RADIO BEARER SETUP message format transmitted through the DCH does not need UE identifier information, but other control information 470 and the actual It has a payload 460 in which the information included in the MBMS RADIO BEARER SETUP message is present. Meanwhile, in FIG. 4, since the FACH is transmitted to the cell boundary region as a common channel, the MBMS RADIO BEARER SETUP message through the FACH is indicated (dotted) to the cell boundary region, and the DCH is a dedicated channel corresponding to the corresponding UE, that is, UE5 ( Since the transmission power control is performed with the 432, only the UE5 432 is transmitted, and the MBMS RADIO BEARER SETUP message through the DCH is displayed (solid line) to the UE5 432.

Next, FIG. 5 schematically illustrates transmission of radio channel configuration information for an MBMS service according to another embodiment of the present invention.

First, prior to the description of FIG. 5, the UE1 521, the UE2 522, the UE3 523, the UE4 531, and the UE5 532 have requested a first MBMS service, which is an arbitrary MBMS service. According to the 1MBMS service request, it is assumed that the process is completed until step 314, that is, the radio link setup, as described with reference to FIG. 3. The UE1 521, the UE2 522, the UE3 523, and the UE4 525 recognize the FACH reception information and the RACH information. The UE1 521, the UE2 522, the UE3 523, It is assumed that UE4 525 is in a Cell_FACH state capable of receiving messages transmitted through the FACH, and UE5 531 is in a Cell_DCH state in which a DCH is configured.

First, the RNC 510 transmits an MBMS RADIO BEARER SETUP message by using the FACH to the UE1 521, the UE2 522, and the UE3 523 which are located in the same cell and are in the Cell_FACH state. The configuration of is as shown in FIG. That is, since the FACH is a channel shared by a plurality of UEs, the RNC indicating which MBMS RADIO BEARER SETUP message is the MBMS RADIO BEARER SETUP message for the UEs receiving the FACH in the messages transmitted through the FACH. Service identifier information 540 is included. That is, since RNC service identifier information is provided to UEs that want to receive the same MBMS service instead of the identifiers of the UEs transmitted through the FACH, unnecessary radio reception information is transmitted by transmitting control information previously transmitted to individual UEs. And, as described above, if the UEs intended to receive the service are in the Cell_DCH state, the UE may transition to the Cell_FACH state for a while to receive control information about the channel for the MBMS service. . In this case, the RNC service identifier information may be sequentially assigned according to the MBMS service that the UE wants to receive, or an efficient equation may be defined to allocate a service identifier according to the equation. Here, the RNC service identifier information 540 is information that the RNC 510 determines to correspond to the first MBMS service and announces to the corresponding UEs through a first MBMS service response message as described with reference to FIG. 3. The other control information 550 means other control information except for the RNC service identifier information 540, and information including the MBMS RADIO BEARER SETUP message is present in the payload 560. . In addition, since the UE4 531 is also in the Cell_FACH state, the RNC 510 transmits an MBMS RADIO BEARER SETUP message using the corresponding FACH, and transmits the MBMS RADIO BEARER SETUP message to the UE5 532 using a DCH.

Next, a UE structure for performing a function in an embodiment of the present invention will be described with reference to FIG. 6.

6 illustrates a structure of a user terminal for performing a function in an embodiment of the present invention.

First, a radio frequency (RF) signal received through an antenna 600 is transmitted to the receiver 610. The receiving unit 610 may control a signal received through the antenna 600 under the control of a radio resource control (RRC) layer 640-1, which is an upper layer. Know the channelization code to apply. The receiver 610 despreads the signal output from the antenna 600 with the recognized channelization code, and then performs a segmentation and a Cyclick Redundancy Check (CRC) operation with a predetermined size. It processes the MBMS RADIO BEARER SETUP message as described in FIG. 4 and FIG. 5 and outputs the same to the UE identifier reading unit 620 and the demultiplexer 630. The RRC layer 640-1 controls to receive the FACH signal to the receiver 610 when the UE is in the Cell_FACH state, and to receive the DCH to the receiver 610 when the UE is in the Cell_DCH state. Command When the UE is in the Cell_FACH state, the receiver 610 transmits the received message to the UE identifier reader 620. When the UE is in the Cell_DCH state, the receiver 610 receives the processed message. To pass to the demultiplexer 630. The UE identifier reading unit 620 knows a UE identifier indicating the UE, and compares the UE identifier of the message transmitted by the receiving unit 610 with the UE identifier previously known. As a result of the comparison, when the UE identifier of the received message and the previously known UE identifier match, the UE identifier reading unit 620 outputs the received message to the demultiplexer 630. In addition, the UE identifier reading unit 620 may know the RNC service identifier in advance. As a result, the UE identifier reading unit 620 demultiplexes the received message only when the identifier information included in the message output from the receiving unit 610 matches the UE identifier indicating the UE or the RNC service identifier. 630, otherwise, discard the received message. That is, the UE identifier reading unit 620 of the UE which has read the individual identifier of the UE reads the RNC service identifier for the MBMS service that it wants to receive. Accordingly, the UE identifier reading unit sees the RNC service identifier and The control information for the MBMS service channel to be received is received, thereby preparing for reception of the actual MBMS service. The demultiplexer 630 may be other control information of a message transmitted by the receiver 610 or the UE identifier reader 620, for example, when the UE receives a message through the FACH, the other described in FIG. 5. When the control information 550 or the message received by the UE through the DCH, the received message is transferred to the upper layer with the other control information 570 described with reference to FIG. 5 to process the received message. Done.

7 is a flowchart illustrating a process of operating a user terminal according to another embodiment of the present invention.

Referring to FIG. 7, first, in step 701, the UE receiving menu information proceeds to step 702. In step 702, if the UE wants to receive a service for a specific MBMS, the UE proceeds to step 703. In step 703, the UE transmits a first MBMS service request message and proceeds to step 704. Here, the first MBMS service request message includes an MB-SC SERVICE identifier indicating a specific MBMS that wants to receive the service. The identifier of the MB-SC is a service identifier assigned to discriminate each MBMS service from the MB-SC. That is, it can be interpreted in the same meaning as the MBMS service identifier described above. In step 704, the UE monitors an appropriate channel according to the state. That is, the FACH is monitored in the Cell_FACH state and the DCH is monitored in the Cell_DCH state. When the first MBMS service response message is received from the RNC through the monitored channel, the RNC service identifier included in the first MBMS service response message is transmitted to the UE. The identifier is transmitted to the reading unit 620 and the flow proceeds to step 705. That is, the UE which has applied for the MBMS service afterwards configures a channel to receive the actual MBMS service according to the RNC service identifier of the control information sent down through the FACH. In addition, the UE monitors an appropriate channel according to the state, and when the UE receives the first MBMS service notification message from the RNC in step 705, it proceeds to step 706. In step 706, the UE detects the service identifier included in the received first MBMS service notification message and once again determines whether to receive the MBMS service corresponding to the service identifier. In step 707, since the UE determines to receive a specific MBMS service corresponding to the service identifier, the UE proceeds to step 708 after transmitting a first MBMS notification response message to the RNC. In step 708, when the UE monitors an appropriate channel according to the state and receives an MBMS radio bearer setup message from the RNC, the UE transmits to the specific MBMS service according to the radio channel configuration information included in the received MBMS radio bearer setup message. Configure a radio bearer for receiving data for the receiver; and the UE stores the service start time included in the received MBMS radio bearer setup message to receive the MBMS data in accordance with the service start time. ). In this case, when the UE is in the Cell_FACH state, an RNC service identifier is inserted as an identifier in the MBMS radio bearer setup message, and the UE identifier reading unit 620 uses the received RNC service identifier in step 704. It is determined whether the MBMS radio bearer setup message is a message corresponding to the UE itself. If the received MBMS radio bearer setup message is a message corresponding to the UE itself, the UE determines a radio bearer as described above. If the radio bearer configuration is completed, the UE proceeds to step 709. In step 709, the UE transmits an MBMS radio bearer setup complete message to the RNC as the radio bearer configuration is completed, and proceeds to step 710. In step 710, the UE receives, starts and ends the MBMS data through the configured radio bearer from the stored service start time.

8 is a diagram illustrating a UTRAN structure for performing a function in an embodiment of the present invention. Here, the UTRAN is a term that collectively refers to Node B and RNC.

Referring to FIG. 8, the RNC that receives the second MBMS service response message first allocates an RNC service identifier for the MBMS service and then transfers the allocated RNC service identifier to the UE identifier inserter 820. The upper layers (RRCs) 840-1,..., 840-n transfer the data to be transmitted to the multiplexer 830 when there is data to be transmitted. Although not shown in FIG. 8, between the upper layers 840-1,..., 840-n and the multiplexer 830, the upper layers 840-1,. Of course, the data output in n) may be segmented into a predetermined predetermined size and a separate element for data processing may be configured, such as assigning a serial number to the segmented data. The multiplexer 830 multiplexes data output from the upper layers 840-1,..., 840-n with multiplexing information, and when the multiplexed signal is transmitted through a DCH, the transmitter 810. When the multiplexed signal is transmitted through the FACH, the multiplexed signal is transmitted to the UE identifier inserter 820. The UE identifier inserter 820 inserts the identifier into the signal received from the multiplexer 830 and outputs the identifier to the transmitter 810. In this case, the UE identifier inserter 820 inserts in the multiplexer 830 which identifier to insert into the signal output from the multiplexer 830, that is, which of RNC service identifiers and UE identifiers to insert. The decision is made according to the control of the multiplexing information or the higher layers 840-1,. For example, when the multiplexing information is 0 or 1, the RNC service identifier may be inserted, and in other cases, the RNC service identifier may be inserted. Alternatively, when data that needs to insert the RNC service identifier is transmitted to the UE identifier inserter 820, the upper layers 840-1,..., 840-n control to insert the RNC service identifier. Can be controlled. The data output from the UE identifier inserter 820 or the multiplexer 830 is converted into a radio frequency (RF) signal by the transmitter 810 and transmitted through the antenna 800.

9 is a flowchart illustrating the operation of the UTRAN according to another embodiment of the present invention.

Referring to FIG. 9, in step 901, the RNC proceeds to step 902 upon receiving the first MBMS service request message. In step 902, the RNC checks whether an RNC service context corresponding to the MB-SC service identifier included in the first MBMS service request message already exists. If the RNC service context corresponding to the MB-SC service identifier does not exist, the RNC proceeds to step 903. In step 903, the RNC generates a new RNC service context corresponding to the MB-SC service identifier and proceeds to step 904. If the RNC service context corresponding to the MB-SC service identifier already exists in step 902, the RNC proceeds to step 904. In step 904, the RNC adds and updates a UE identifier indicating a UE that has transmitted the first MBMS service request message to the generated RNC service context and a cell identifier indicating a cell where the UE is located. Proceed to

In step 905, the RNC transmits a second MBMS service request message including the UE identifier to the SGSN and proceeds to step 906. Then, the SGNS may identify UEs to receive MBMS service and RNCs that manage the UEs using the second MBMS service request message. In step 906, the RNC receives a second MBMS service response message corresponding to the second MBMS service request message from the SGSN and proceeds to step 907. When the RNC receives the second MBMS service response message in step 907, the RNC determines an RNC service identifier, transfers the determined RNC service identifier to the UE identifier inserter 820, and proceeds to step 908. Here, the RNC service identifier is determined by selecting one of the identifiers not assigned to other MBMS services. Of course, when the RNC service context already exists as described in step 902, since the RNC service identifier is already allocated, in this case, there is no need to reassign the RNC service identifier.

In step 908, the RNC transmits a first MBMS service response message including an RNC service identifier to the UE, and proceeds to step 909. In step 909, the UE receives a second MBMS service notification message from the SGSN and proceeds to step 910. In step 910, when the UE receives the received second MBMS service notification message, the UE transmits a first MBMS service notification message to UEs corresponding to UE identifiers registered in the corresponding RNC service context, and proceeds to step 911. do. In step 911, the RNC receives a first MBMS notification response message from the corresponding UEs and proceeds to step 912. In step 912, the RNC updates UE identifiers for UEs that have transmitted the first MBMS notification response messages and identifiers of cells to which the UEs belong to the RNC service context, and then updates the UE identifiers. In step 913, the RNC transmits a second MBMS notification response message to the SGSN. In step 914, the RNC receives an MBMS RAB allocation request message from the SGSN.

In step 915, the RNC prepares a radio channel configuration based on QoS information included in the MBMS RAB allocation request message. That is, the RNC transmits an MBMS radio link setup request message to Node Bs that manage cells registered in the RNC SERVICE CONTEXT and proceeds to step 916. Here, the MBMS radio link setup request message includes radio channel configuration information regarding a radio channel to which MBMS data is to be transmitted, and the Node B controls the transmitter 810 based on the radio channel configuration information. When control of the transmitter 810 is complete, the Node B sends an MBMS radio link setup response message to the RNC. After receiving the MBMS radio link setup response message from the Node B in step 916, the RNC proceeds to step 917 to transmit an MBMS radio bearer setup message to the corresponding UEs, and proceeds to step 919. Here, for the UEs in the Cell_DCH state among the corresponding UEs, the RNC proceeds to step 918 to transmit an MBMS radio bearer setup message through the DCH, and then proceeds to step 919 and the Cell_FACH state among the corresponding UEs. For the UEs, the RNC transmits the information through the FACH in step 917 and then proceeds to step 919. In step 919, the RNC receives an MBMS radio bearer setup complete message from corresponding UEs, and proceeds to step 920. In step 920, the RNC informs SGSN that a radio channel configuration for MBMS data transmission is completed using an MBMS RAB assignment response message and proceeds to step 921. FIG. In step 921, the RNC transmits and terminates MBMS data, that is, MBMS multimedia stream, through the configured wireless channel.

Hereinafter, a second embodiment of the present invention provides a method of transmitting the MBMS RADIO BEARER SETUP message through a common control channel (CCCH: hereinafter referred to as "CCCH"), the second embodiment of the present invention MBMS RADIO BEARER SETUP message transmission using the CCCH according to the description will be described with reference to FIG.

10 is a diagram schematically illustrating transmission of radio channel configuration information for an MBMS service through a common control channel according to another embodiment of the present invention.

Referring to FIG. 10, first, in the description of FIG. 10, the conversations described with reference to FIG. 5, that is, the UE1 521, the UE2 522, the UE3 523, the UE4 531, and the UE5 532 are described. It is assumed that has requested a first MBMS service, which is an arbitrary MBMS service, and has been completed up to step 314, ie, radio link setup, as described with reference to FIG. 3 according to the first MBMS service request. The UE1 521, the UE2 522, the UE3 523, and the UE4 525 recognize the FACH reception information and the RACH information. The UE1 521, the UE2 522, the UE3 523, It is assumed that UE4 525 is in a Cell_FACH state capable of receiving messages transmitted through the FACH, and UE5 531 is in a Cell_DCH state in which a DCH is configured.

First, the RNC 510 transmits an MBMS RADIO BEARER SETUP message using FACH and CCCH to UE1 521, UE2 522, and UE3 523 located in the same cell and in the Cell_FACH state. The configuration of the message transmitted through is as shown in FIG. Here, the MBMS RADIO BEARER SETUP message format transmitted through the CCCH is the same as the MBMS RADIO BEARER SETUP message format described with reference to FIG. 5. However, the headers 540 and 550 do not include a UE identifier for identifying each of the UEs, and the payload 560 includes a UE identifier for identifying each of the UEs. Therefore, UEs in Cell_FACH state receive an MBMS RADIO BEARER SETUP message on the CCCH, and each of the UEs directly transfers an MBMS RADIO BEARER SETUP message received on the CCCH to an RRC layer, and the MBMS at the RRC layer. RADIO BEARER SETUP Message It is determined whether the message is UE's own message. Meanwhile, in the second embodiment of the present invention, a message including information commonly transmitted to a plurality of UEs, such as an MBMS RADIO BEARER SETUP message, is transmitted through the CCCH, and at this time, a message including the information that is commonly transmitted. M-RNTI (MBMS-Radio Network Temporary Identitifier) is used as UE identifier information.

Referring to FIG. 10, a UE 531 in a Cell_FACH state and a UE 532 in a Cell_DCH state exist in the Cell 530, and control messages for the UE 531 are transmitted through the CCCH and the FACH 539. And control messages for the UE 532 over the DPCH 538. The UE 531 in the Cell_FACH state processes and transmits all transport blocks (TBs) received through the FACH to the MAC layer, and the MAC layer transmits the header part of the TBs. The Target Channel Type Field (TCTF) field 1050 is used to determine whether to transmit the received TBs to the UE identifier reader or to the RLC layer connected to the RRC. Here, the TCTF field 1050 is a field added to all TBs transmitted through the FACH, and includes information indicating how to process the corresponding TBs in the receiving MAC layer. For example, when the TCTF field 1050 is coded as '11', the TBs are Dedicated Traffic Channels (DTCHs) or Dedicated Control Channels (DCCHs). UE identifier information and multiplexing information in a field consecutive to the TCTF field 1050, that is, in the payload 1060 field. Therefore, the TCTF field coded as '11' exists in the front of the other control information 550 of the first embodiment of the present invention, but the description thereof is omitted for convenience.

On the other hand, if the TCTF field 1050 is coded as '01000000', it means that the received TBs are data transmitted through the CCCH, so that the receiving MAC layer delivers the corresponding TBs to the RLC layer connected to the RRC. . The RRC layer decodes UE identifier information included in the payload 1060 field of TBs transmitted through the CCCH from the RLC layer to determine whether the TBs are their TBs. Next, a protocol structure configured between the UE and the UTRAN of the UMTS communication system will be described with reference to FIG. 11.

11 is a diagram schematically showing a protocol structure of a UMTS communication system that performs a function in an embodiment of the present invention.

Although FIG. 11 illustrates only the case where the transmitting side 1500 is the UTRAN and the receiving side 1550 is the UE, that is, the case of forward communication, the protocol structure of the FIG. 11 is the forward and reverse communication. Of course it applies to all. CCCH, DCCH, DTCH, etc. are configured between the UE 1550 and the UTRAN 1500 through an RRC CONNNECTION SETUP process after the UE 1550 is first powered on. Here, the CCCH and the DCCH is a path for sending and receiving an RRC message between the UTRAN 1500 and the UE 1550, and the DTCH is a channel for transmitting and receiving user data. Only one CCCH may be configured between the UTRAN 1500 and the UE 1550, and a plurality of DCCHs and DTCHs may be configured. The DCCH, DTCH, and CCCH are collectively called a logical channel. One or two RLC layers may be configured in the logical channel. For convenience of description, FIG. 11 assumes that only one RLC layer is configured in one logical channel. The transmitting side, that is, the UTRAN 1500 RLC layers 1520-1 through 1520-N, are upper layers connected to the RLC layers 1520-1 through 1520-N, that is, RRC layers 1510-1. Segmentation of the data delivered from the 1510-N-1 and the application layer 1510-N to an appropriate size, and additional information such as a serial number (SN) in the segmented data Role to grant them.

The receiving side, that is, the UE 1550 RLC layers 1580-1 through 1580 -N, assembles the transmitted data segmented with reference to a serial number of data transmitted from the MAC layer 1570 and the RLC layer. To the upper layer, that is, the RRC layers 1590-1 to 1590-N-1 and the application layer 1159-N, connected to the fields 1580-1 to 1580-N. Meanwhile, the UTRAN 1500 MAC layer 1530 multiplexes the multiplexing information. The multiplexed information inserter 1530-1 of the MAC layer 1530 inserts an identifier of a corresponding logical channel into data transmitted through a DTCH or a DCCH. On the other hand, multiplexing information is not inserted into the CCCH. Correspondingly, the multiplexed information reader 1570-1 of the MAC layer 1570 of the UE 1550 uses the logical channel identifier inserted by the multiplexed information inserter 1530-1 of the MAC layer 1530 of the UTRAN 1500. The received data is transmitted to the corresponding RLC layer using the read logical channel identifier.

In addition, the UE identifier inserter 1530-2 of the MAC layer 1530 of the UTRAN 1500 inserts an identifier of a receiver to receive the data into data transmitted from the multiplexed information inserter 1530-1. Here, the UE identifier inserter 1530-2 inserts a different identifier as a receiver side identifier according to each of the embodiments of the present invention described above. In the first embodiment of the present invention, the RNC service identifier is It is performed by the UE identifier inserter 1530-2 located in the MAC layer. In the second embodiment of the present invention, the RNC service identifier is inserted in the RRC layer. Also, in the first embodiment of the present invention, as described above, the multiplexed information is inserted in the multiplexed information insertion unit 1530-1 located in the MAC layer. However, in the second embodiment of the present invention, the multiplexed information is inserted in the MAC layer. The operation of the unit 1530-1 is not performed. However, in the first and second embodiments of the present invention, the TCTF field insertion operation of the TCTF insertion unit 1530-3 of the MAC layer is performed in the same manner. Therefore, the receiving side of the first embodiment of the present invention identifies the UE receiving the MBMS service by reading the inserted RNC service identifier in the MAC layer 1570 of the receiving side. In addition, in the case of the receiver of the second embodiment of the present invention, the inserted RNC service identifier is read by the RRC layer of the receiver. In more detail, the UE identifier reading unit 1570-2 of the MAC layer 1570 of the UE 1550 may include a UE identifier of data transmitted by the physical layer 1560 or the TCTF reading unit 1570-3. Checks whether is equal to its UE identifier. The UE identifier reading unit 1570-2 reads the data when the physical identifier 1560 or the UE identifier of the data transmitted by the TCTF reading unit 1570-3 is the same as the UE own identifier. The UE identifier of the message is transmitted to the multiplexed information reader 1570-3.

In addition, the TCTF inserter 1530-3 of the MAC layer 1530 of the UTRAN 1500 inserts a TCTF into data transmitted by the RLC layer 1520-1 or the UE identifier inserter 1530-2. As described above, the data transmitted through the CCCH does not go through the multiplexed information inserter 1530-1 and the UE identifier inserter 1530-2, and the TCTF inserter 1530-1 at the RLC layer 1520-1. 3) is delivered immediately. The TCTF insertion unit 1530-3 codes a TCTF of '01000000' in data transmitted through the CCCH. Meanwhile, the data transmitted through the DCCH or the DTCH is transferred to the TCTF insertion unit 1530-3 through the multiplexing information insertion unit 1530-1 and the UE identifier insertion unit 1530-2, and the TCTF insertion unit 1530-3 codes a TCTF of '11' in data transmitted through the DCCH or DTCH. Correspondingly, if the first 2 bits of the received data received from the physical layer 1560 is 01, the TCTF reading unit 1570-3 of the UE 1550 MAC layer 1570 removes the remaining 6 bits, that is, Remove '01000000' and transfer to RLC 1590-1 connected with CCCH. In addition, when the first two bits of the received data is 11, the TCTF reading unit 1570-3 removes the first two bits, that is, '11', and transmits the first two bits to the UE identifier reading unit 1570-2.

Here, the TCTF reading unit 1570-3 and the TCTF inserting unit 1530-3, the UE identifier reading unit 1570-2, and the UE identifier inserting unit 1530-2 are transmitted and received through the FACH in the forward direction. It is configured only for logical channels. That is, if any DTCH x is transmitted and received on the DPCH, the TCTF reader 1570-3 and TCTF inserter 1530-3 and the UE identifier reader 1570-2 for the logical channel DTCH x. And the UE identifier inserter 1530-2 is not configured. In addition, after segmented to an appropriate size in the RLC layer and additional information is inserted, data transmitted from the MAC layer to the physical layer is called TB. For example, 500 bits of data transmitted from an upper layer, for example, an RRC layer, are segmented into five 100 bits of data in an RLC layer, and then each of the segmented five 100 bits data includes 16 bits of RLC side information and MAC. If 8 bits of additional information is inserted, the MAC layer delivers five 124 bits of data to the physical layer, where each of the 124 bits is TB.

Next, the second embodiment of the present invention will be described in more detail with reference to FIG. 11 as follows.

Referring to FIG. 11, first, the RNC 510 that wants to transmit common information about an MBMS service includes a message including common information about the MBMS service, for example, an MBMS RADIO BEARER SETUP message or an MBMS RADIO BEARER RELEASE message. Configure In this case, RNC service identifier information is inserted into the MBMS RADIO BEARER SETUP message or MBMS RADIO BEARERRELEASE message instead of UE identifier information. The MBMS RADIO BEARER SETUP message or MBMS RADIO BEARER RELEASE message is delivered to the RLC layer 1520-1, and the RLC layer 1520-1 is data included in the MBMS RADIO BEARER SETUP message or MBMS RADIO BEARER RELEASE message. Segmented to a predetermined size and forwarded to the TCTF insertion unit 1530 of the MAC layer 1530. The MBMS RADIO BEARER SETUP message or MBMS RADIO BEARER RELEASE message is transmitted to the RLC layer 1520-1 because the MBMS RADIO BEARER SETUP message or MBMS RADIO BEARER RELEASE message is transmitted through CCCH. In addition, since the MBMS RADIO BEARER SETUP message or MBMS RADIO BEARER RELEASE message is transmitted through CCCH, the above messages are transmitted from the RLC layer 1520-1 to the multiplex information insertion unit 1530-1 of the MAC layer 1530. And outputting the segmented data to the TCTF insertion unit 1530-3 of the MAC layer without going through a special operation of the UE identifier insertion unit 1530-2.

The TCTF inserter 1530-3 inserts a TCTF coded as '01000000' into the data output from the RLC layer 1520-1, and then, cells 1, 520, in which UEs in a Cell_FACH state are located. ) And the physical layer 1540 of the cell 2 530. The operation of the TCTF inserter is to be applied to both the operation through the first embodiment of the present invention or the operation through the second embodiment of the present invention. The data output from the TCTF insertion unit 1530-3 eventually becomes TB. The physical layer 1540 performs FACH after performing a series of transmission signal processing processes such as channel coding, spreading, and modulation of the TBs received from the TCTF insertion unit 1530-3. Send it through. Here, the physical layer 1560 of the UEs 521, 522, 523, and 531 in the Cell_FACH state transfers TBs transmitted through the FACH to the MAC layer 1570. The MAC layer 1570 then outputs the TBs received from the physical layer 1560 to the TCTF reader 1570-3, and the TCTF reader 1570-3 reads the TCTFs of the TBs to determine the TCTF. If is coded as '01000000', it passes to the RLC layer 1580-1. Here, when the TCTF reader 1570-3 of the TBs is coded as '01000000', the TBs are transmitted to the RLC layer 1580-1 because the TBs are transmitted through a CCCH. .

The RLC layer 1580-1 is assembled into an original message, that is, an MBMS RADIO BEARER SETUP message or an MBMS RADIO BEARER RELEASE message, using additional information such as serial numbers of TBs transmitted from the TCTF reader 1570-3. Afterward, it transfers to the corresponding RRC layer 1590-1. The RRC layer 1590-1 is a message in which the MBMS RADIO BEARER SETUP message or MBMS RADIO BEARER RELEASE message is transmitted through CCCH, and thus the UE identifier information included in the MBMS RADIO BEARER SETUP message or MBMS RADIO BEARER RELEASE message. Check it. That is, when transmitted through the CCCH, the RNC service identifier inserted in the RRC layer of the transmitting side is read by the RRC layer 1590-1. In the present invention, since the RNC service identifier is included instead of the UE identifier, it is checked whether the RNC service identifier is the same as the RNC service identifier received in step 306 of FIG. If the received RNC service identifier is the same as the RNC service identifier received in step 306, the required operation is performed based on the information included in the MBMS RADIO BEARER SETUP message or MBMS RADIO BEARER RELEASE message. Here, the necessary operation may be different according to the message type. For example, when the received message is an MBMS RADIO BEARER SETUP message, the RRC layer 1590-1 configures a corresponding physical layer using MBMS channel related information included in the MBMS RADIO BEARER SETUP message. That is, the RRC layer 1590-1 configures a de-spreader of a physical layer to be suitable for a spreading code to be applied to an MBMS channel, and applies a demodulator to a MBMS channel. A channel decoder is configured to suit the channel coding parameter to be used for the MBMS channel. As another example, if the received message is an MBMS RADIO BEARER RELEASE message, the RRC layer 1590-1 instructs the physical layer to stop receiving through the MBMS channel.

Here, the MBMS RADIO BEARER SETUP message or MBMS RADIO BEARER RELEASE message may include the following information.

(1) Message type: Information indicating the type of the message, which is determined in advance as an arbitrary integer value.

(2) UE identifier information: Refers to an identifier of a UE that should receive a message, and in the second embodiment of the present invention, an RNC service identifier may be used as UE identifier information, and is composed of a bit stream of 16 bits or 32 bits. do.

(3) Other control information: Appropriate information is included according to the message type, and MBMS RADIO BEARER SETUP message may include channel related information provided with MBMS service, and MBMS RADIO BEARER RELEASE information includes time information such as MBMS service interruption. This may be included.

Next, an operation of the UE supporting the second embodiment of the present invention will be described with reference to FIG. 12.

12 is a flowchart illustrating a process of operating a user terminal according to another embodiment of the present invention. Prior to the description of FIG. 12, only the case of receiving the MBMS RADIO BEARER SETUP message will be described first for convenience of description, and the same processes as those of the first embodiment of the present invention will be described with the same reference numerals as in FIG. 7. Note the use of symbols.

First, in step 701, the UE having received the menu information proceeds to step 702. In step 702, if the UE wants to receive a service for a specific MBMS, the UE proceeds to step 703. In step 703, the UE transmits a first MBMS service request message requesting to receive the specific MBMS service, and proceeds to step 704. Here, the first MBMS service request message includes an MB-SC SERVICE identifier indicating a specific MBMS that wants to receive the service. In step 1204, the UE monitors an appropriate channel according to the state. That is, the FACH is monitored in the Cell_FACH state and the DCH is monitored in the Cell_DCH state. When the first MBMS service response message is received through the corresponding channel in step 1204 while monitoring the corresponding channel, the UE, that is, the RRC layer of the UE, stores the RNC service identifier included in the first MBMS service response message. Proceed to step 705. In step 705, the UE monitors an appropriate channel according to the state, receives a first MBMS service notification message from the RNC, detects service identifier information included in the received first MBMS service notification message, and proceeds to step 706. Proceed. In step 706, the UE once again confirms whether to receive the MBMS service using the service identifier information detected in the first MBMS service notification message. If the UE determines to receive the MBMS service, the UE proceeds to step 707. In step 707, the UE transmits a first MBMS notification response message to the RNC and proceeds to step 1208. In step 1208, the UE monitors the channel according to the state thereof, receives a MBMS radio bearer setup message from the RNC, and proceeds to step 1209. In step 1209, the UE, that is, the MAC layer of the UE examines TCTF fields of TBs received through a corresponding channel, that is, FACH, and delivers TBs having a TCTF field of '01000000' to the RLC layer 1580-1. The RLC layer 1580-1 configures TBs received from the MAC layer into one message and delivers the TBs to the RRC layer. The RRC layer detects that the message includes MBMS radio bearer setup information by using message type information of the message received from the RLC layer 1580-1, and proceeds to step 1209. In step 1209, the UE checks UE identifier information included in the MBMS radio bearer setup message because the MBMS radio bearer setup message has been delivered through CCCH. If the RNC service identifier is coded in the UE identifier information, the RRC layer of the UE configures a physical layer using MBMS channel related information included in the MBMS radio bearer setup message and proceeds to step 1211. On the other hand, if none of the RNC service identifier and its UE identifier is coded in the UE identifier information as a result of the check in step 1209, the RRC layer of the UE waits until the RLC layer delivers data again. In addition, if the UE identifier of the UE that received the message is coded in the UE identifier information in step 1209, an appropriate operation is performed by using the information included in the MBMS radio bearer setup message. The case where the UE's own identifier is coded in the UE identifier information is not related to the embodiment of the present invention, and thus the detailed description thereof will be omitted.

In step 1211, the UE transmits an MBMS radio bearer setup complete message to the RNC indicating that the operation corresponding to the MBMS radio bearer setup message has been completed, and proceeds to step 1212. In step 1212, the UE starts receiving and ends the corresponding MBMS stream at the service start time included in the MBMS radio bearer setup message.

Next, an operation process of the UTRAN, that is, RNC, for performing a function in the second embodiment of the present invention will be described with reference to FIG. 13.

13 is a flowchart illustrating an operation process of the UTRAN according to another embodiment of the present invention. Before describing FIG. 13, it should be noted that the same reference numerals as those of FIG. 9 are used for the same processes as the first embodiment of the present invention.

First, in step 901, the RNC receives a first MBMS service request message from a UE and proceeds to step 902. In step 902, the RNC checks whether an RNC service context corresponding to the MB-SC service identifier included in the first MBMS service request message already exists. If the RNC service context corresponding to the MB-SC service identifier does not exist, the RNC proceeds to step 903.

In step 903, the RNC generates a new RNC service context corresponding to the MB-SC service identifier and proceeds to step 904. If the RNC service context corresponding to the MB-SC service identifier already exists in step 902, the RNC proceeds to step 904. In step 904, the RNC adds and updates a UE identifier indicating a UE that has transmitted the first MBMS service request message to the generated RNC service context and a cell identifier indicating a cell where the UE is located. Proceed to In step 905, the RNC transmits a second MBMS service request message including the UE identifier to the SGSN and proceeds to step 906. Then, the SGNS may identify UEs to receive MBMS service and RNCs that manage the UEs using the second MBMS service request message. In step 906, the RNC receives a second MBMS service response message corresponding to the second MBMS service request message from the SGSN and proceeds to step 1407. In step 1407, the RNC determines the RNC service identifier and adds it to the RNC service context. Here, the RNC service identifier may be selected as one of RNC service identifiers not assigned to other MBMS services. In addition, if the RNC service context already exists in step 902, the RNC service identifier is already allocated, and in this case, it is not necessary to reassign the RNC service identifier.

In step 908, the RNC transmits a first MBMS service response message including an RNC service identifier to the UE and in step 909. In step 909, the RNC receives a second MBMS service notification message from SGSN and proceeds to step 910. In step 910, the RNC transmits a first MBMS service notification message to UEs registered in a corresponding RNC service context and proceeds to step 911. FIG. In step 911, the RNC receives a first MBMS notification response message corresponding to the first MBMS service notification message from the corresponding UEs and proceeds to step 912. In step 912, the RNC updates a UE identifier of each of the UEs that have transmitted the first MBMS notification response message and an identifier of cells to which the UEs belong to the RNC service context and proceeds to step 913.

In step 913, the RNC sends a second MBMS notification response message to the SGSN and proceeds to step 914. In step 914, the RNC receives an MBMS radio bearer allocation request message from the SGSN and proceeds to step 915. In step 915, when the RNC receives the MBMS radio bearer assignment request message, the RNC prepares a radio channel configuration based on QoS information included in the MBMS radio bearer assignment request message. That is, the RNC transmits an MBMS radio link setup request message to Node Bs managing cells registered in the RNC SERVICE CONTEXT and proceeds to step 916. Here, the MBMS radio link setup request message includes information on a radio channel to which an MBMS service is to be provided, that is, an MBMS stream is to be transmitted, and corresponding Node Bs receiving the MBMS radio link setup request message may configure the MBMS radio link setup. The transmitter 810 or the physical layer 1540 is configured with the radio channel related information included in the request message. When the configuration of the transmitter 810 is completed, the corresponding Node Bs transmit an MBMS radio link setup response message to the RNC. The RNC then receives the MBMS radio link setup response message transmitted by the Node Bs in step 916 and proceeds to steps 1417 and 918. In step 1417, the RNC sends a MBMS radio bearer setup message through FACH and CCCH to UEs belonging to Node Bs, which informs that the transmitter 810 or the physical layer 1540 configuration is completed through the MBMS radio link setup response message. Send to and proceed to step 919. In this case, when the UEs are in the Cell_FACH state, the UE is transmitted through the FACH and the CCCH as in step 1417, and only one message is transmitted to all UEs. As described above, an RNC service identifier is coded in a UE identifier information field of the MBMS radio bearer setup message, and the MBMS radio bearer setup message is transmitted through an RLC layer 1520-1 and a TCTF insertion unit 1530-3. It is transmitted through the FACH and CCCH. Meanwhile, when the UE is in the Cell_DCH state instead of the Cell_FACH state, the RNC proceeds to step 918 to transmit the MBMS radio bearer setup message through the DCH and proceeds to step 919.

In step 919, the RNC receives an MBMS radio bearer setup complete message from corresponding UEs, and proceeds to step 920. In step 920, the RNC notifies SGSN by using an MBMS RAB assignment response message that the radio channel configuration for the MBMS data transmission is completed, and proceeds to step 921. In step 921, the RNC transmits and terminates MBMS data, that is, MBMS multimedia stream, through the configured wireless channel.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by the equivalents of the claims.

As described above, the present invention provides a load of a message transmission / reception process due to transmission and reception of radio channel configuration information by transmitting radio channel configuration information corresponding to UEs requesting the same MBMS service through a common channel when providing an MBMS service in a mobile communication system. Has the advantage of eliminating it. In addition, the present invention is to remove the load of the message transmission and reception process due to the transmission and reception of the radio channel configuration information by transmitting only the radio channel configuration information corresponding to the UEs requesting the same MBMS service by different identifiers when providing the MBMS service Has

Claims (23)

A method for providing a multicast multimedia broadcasting service (MBMS) having a plurality of types in a mobile communication system, When a plurality of radio network controllers (RNCs) detect a service provision request for a first MBMS, which is any one of the plurality of types, from a user terminal (UE), a service identifier indicating the first MBMS and the UEs Configure a first service context including UE identifiers indicating each and cell identifiers indicating cells to which each of the UEs belongs, and providing service for the first MBMS to a service packet radio service support node (SGSN); The request process, The SGSN configures a second service context including the service identifier and RNC identifiers representing each of the plurality of RNCs to receive the first MBMS data according to the service provision request for the first MBMS, and multicast / Requesting to provide a service for the first MBMS to a broadcast-service center (MB-SC); The MB-SC notifies the SGSN of the time when the first MBMS is to be started, and the SGSN wirelessly transmits the first MBMS data to each of the RNCs corresponding to each of the RNC identifiers stored in the second service context. The process of requiring a channel to be configured, Each of the RNCs transmits radio channel configuration information to be used for the radio channel configuration according to the radio channel configuration request through a common channel along with UE identifiers stored in the first service context, and corresponds to the UE identifiers. And controlling UEs to receive the first MBMS data by configuring a radio channel corresponding to the radio channel configuration information. The method of claim 1, The common channel is a forward access channel. The method of claim 1, The wireless channel configuration information is channelization code information and scrambling code information to be applied when transmitting the first MBMS data. A method for providing a multicast multimedia broadcasting service (MBMS) having a plurality of types in a mobile communication system, When a plurality of radio network controllers (RNCs) detect a service provision request for a first MBMS, which is any one of the plurality of types, from a user terminal (UE), a service identifier indicating the first MBMS and the UEs Configure a first service context including UE identifiers indicating each and cell identifiers indicating cells to which each of the UEs belongs, and providing a service packet service for the first MBMS to a service packet radio service support node (SGSN); The request process, The SGSN configures a second service context including the service identifier and RNC identifiers representing each of the plurality of RNCs to receive the first MBMS data according to the service provision request for the first MBMS, and multicast / Requesting to provide a service for the first MBMS to a broadcast-service center (MB-SC); The MB-SC notifies the SGSN of the time when the first MBMS is to be started, and the SGSN wirelessly transmits the first MBMS data to each of the RNCs corresponding to each of the RNC identifiers stored in the second service context. The process of requiring a channel to be configured, Each of the RNCs transmits radio channel configuration information to be used for the radio channel configuration together with the service identifier through a common channel according to the radio channel configuration request, so that the UEs requesting to provide the first MBMS service corresponding to the service identifier are And configuring the radio channel to correspond to radio channel configuration information so as to receive the first MBMS data. The method of claim 4, wherein The common channel is a forward access channel. The method of claim 4, wherein The wireless channel configuration information is channelization code information and scrambling code information to be applied when transmitting the first MBMS data. An apparatus for providing a multicast multimedia broadcasting service (MBMS) having a plurality of types in a mobile communication system, Detecting a service provision request for a first MBMS, which is any one of the plurality of types, from user terminals (UE), a service identifier indicating the first MBMS, UE identifiers indicating each of the UEs, and Configure a first service context including cell identifiers indicating cells to which each of the UEs belong, request a service packet radio service support node (SGSN) to provide service for the first MBMS, and service for the first MBMS A wireless network for receiving a radio channel configuration request for transmitting the first MBMS data in response to the provision request, and transmitting the radio channel configuration information and the UE identifiers together to be used for the radio channel configuration according to the radio channel configuration request through a common channel. Controllers (RNC), Configure a second service context including the service identifier and RNC identifiers representing each of a plurality of RNCs to receive the first MBMS data according to a service provision request for the first MBMS from the RNC, and multicast / broadcast Request a service to the first MBMS to a service center (MB-SC), and establish a radio channel for transmitting the first MBMS data to each of the RNCs corresponding to each of the RNC identifiers stored in the second service context. With SGSN, which requires constructing A UE receiving the common channel signal and configuring a radio channel corresponding to the radio channel configuration information when a UE identifier indicating itself among the UE identifiers of the received common channel signal exists; Said device comprising: a. The method of claim 7, wherein The common channel is a forward access channel. The method of claim 7, wherein The wireless channel configuration information is channelization code information and scrambling code information to be applied when the first MBMS data transmission. An apparatus for providing a multicast multimedia broadcasting service (MBMS) having a plurality of types in a mobile communication system, Detecting a service provision request for a first MBMS, which is any one of the plurality of types, from user terminals (UE), a service identifier indicating the first MBMS, UE identifiers indicating each of the UEs, and Configure a first service context including cell identifiers indicating cells to which each of the UEs belong, request a service packet radio service support node (SGSN) to provide service for the first MBMS, and service for the first MBMS A wireless network configured to receive a radio channel configuration request for transmitting the first MBMS data in response to a provision request and to transmit radio channel configuration information and the service identifier together through a common channel to be used for the radio channel configuration according to the radio channel configuration request; Controllers (RNC), Configure a second service context including the service identifier and RNC identifiers representing each of a plurality of RNCs to receive the first MBMS data according to a service provision request for the first MBMS from the RNC, and multicast / broadcast Request a service to the first MBMS to a service center (MB-SC), and establish a radio channel for transmitting the first MBMS data to each of the RNCs corresponding to each of the RNC identifiers stored in the second service context. With SGSN, which requires constructing And receiving the common channel signal, and if the service identifier of the received common channel signal is the same as the service requested by the user, configures a wireless channel according to radio channel configuration information to receive the first MBMS data. The device, characterized in that. The method of claim 10, The common channel is a forward access channel. The method of claim 10, The wireless channel configuration information is channelization code information and scrambling code information to be applied when the first MBMS data transmission. A method for providing a multicast multimedia broadcasting service (MBMS) having a plurality of types in a mobile communication system, When detecting a service provision request for a first MBMS, which is any one of the plurality of types, from user terminals, a wireless channel for transmitting the first MBMS data is determined, and wireless channel information related to the determined wireless channel is generated. Process, And generating the radio channel related information including the radio channel information and a service identifier indicating the first MBMS and transmitting the radio channel related information to the user terminals through a common control channel. The method of claim 13, And the channel type information indicating that the radio channel information transmits the common control channel to the radio related channel information. The method of claim 13, And generating the radio channel related information including the radio channel information and the user terminal identifiers indicating the user terminals and transmitting the radio channel related information to the user terminals through the common control channel. The method of claim 15, And the user terminal identifier is an MBMS-wireless network temporary identifier. The wireless network controller provides a multicast multimedia broadcasting service (MBMS) having a plurality of types in a mobile communication system, and a user terminal requesting to receive an MBMS of any one of the plurality of types provides the specific MBMS. In a method for receiving, Receiving wireless channel related information through a common control channel and detecting a service identifier included in the received wireless channel related information; And setting up or releasing a wireless channel so as to correspond to wireless channel information included in the wireless channel related information when the detected service identifier is a service identifier indicating the specific MBMS. The method of claim 17, The wireless channel related information may further include channel type information indicating that the wireless channel information is transmitted through the common control channel. The wireless network controller provides at least two or more multicast multimedia broadcast services (MBMSs) received from a multicast / broadcasting-service center, wherein at least two or more user terminals belonging to a base station connected with the wireless network controller are the MBMSs. An apparatus for transmitting radio channel information for providing an MBMS to the user terminals in a mobile communication system requiring the same specific MBMS to be provided, When a request for receiving the specific MBMS is detected from the user terminals, a service context including a service identifier indicating the specific MBMS is configured, and for providing the specific MBMS to the user terminals existing in the service context. A radio resource control layer for generating radio channel information required for radio channel setting; A radio link control layer segmenting the radio channel information according to a preset size and assigning a serial number to the segmented data; Wireless channel related information is inserted into the serialized segmented data by inserting a user terminal identifier designating a user terminal to receive the segmented data and channel type information indicating a type of a channel to which the segmented data is to be transmitted. And a medium access control layer for generating. The method of claim 19, And the user terminal identifier is the service identifier. The method of claim 19, And the user terminal identifier is an MBMS-Wireless Network Temporary Identifier. The method of claim 19, And the channel to which the segmented data is to be transmitted is a common control channel. The wireless network controller provides at least two or more multicast multimedia broadcast services (MBMSs) received from a multicast / broadcasting-service center, wherein at least two or more user terminals belonging to a base station connected with the wireless network controller are the MBMSs. An apparatus for receiving radio channel information for providing an MBMS transmitted by the radio network controller in a mobile communication system requiring a same MBMS to be provided, When transport blocks are received from a physical layer, channel type information indicating a type of a channel on which the transport block is transmitted is read for each of the transport blocks, and the common control when the channel type information is a common control channel. A media access control layer for delivering the transport blocks to a radio link control layer in charge of a channel; A radio link control layer configured to generate radio channel related information by using additional information of transport blocks received from the media access control layer and to transmit the radio channel related information to a radio resource control layer; Examine the service identifier included in the radio channel related information, and if the service identifier is a service identifier indicating the requested specific MBMS, receive the specific MBMS stream according to the radio channel information included in the radio channel related information. And a radio resource control layer for controlling to establish a radio channel for the purpose of communication.