KR20060026722A - Handover method of multimedia broadcast/multicast service for supporting mobility of user equipment - Google Patents

Abstract

The present invention relates to a multicast multimedia broadcasting service (MBMS service), and more particularly, discloses a method for UE linking and MBMS channel establishment when a UE performs handover between RNCs. In addition, a method of obtaining a channel type in which an SRNC obtains channel type information of an MBMS service being serviced in a cell managed by a DRNC in an Iur interface between RNCs is disclosed. According to the present invention, the UE adds information indicating that it is receiving MBMS service to an uplink RRC message sent to SRNC, and in DRNC, if the UE receives MBMS service according to the information, MBMS service channel in the cell where the UE is located The SRNC is informed of the type through a signaling transmission message, and the SRNC sets up an MBMS channel according to the MBMS service channel type to reduce unnecessary signaling and service delays by shortening the MBMS channel set up in two procedures.

MBMS (Multimedia Multicast / Broadcast Service), UE Linking, RRC message, MBMS service information, MBMS channel type

Description

Handover method of multimedia broadcasting / multicast service considering mobility of user terminal {HANDOVER METHOD OF MULTIMEDIA BROADCAST / MULTICAST SERVICE FOR SUPPORTING MOBILITY OF USER EQUIPMENT}             

1 is a diagram illustrating a network configuration for a general MBMS service.

2 is a diagram illustrating a network configuration when one or more RNCs are associated to ensure the mobility of a UE.

3 is a diagram illustrating a procedure for managing mobility in a UMTS network when a UE in a CELL_FACH, CELL_PCH, or URA_PCH state receiving an MBMS service moves between two RNCs.

4 is a diagram illustrating a message flow occurring between a DRNC, an SRNC, and a UE when a PTP channel is to be established through a radio link establishment procedure according to MBMS service handover between RNCs according to a first embodiment of the present invention. .

FIG. 5 is a diagram illustrating a message flow occurring between DRNC, SRNC, and UE when a PTM channel is set up when a radio link failure occurs during MBMS service handover according to a second preferred embodiment of the present invention.

6 is a diagram illustrating a flow of messages between a UE, SRNC, DRNC, and SGSN when a service desired by a UE is not yet registered with the DRNC during MBMS service handover according to the third embodiment of the present invention.

7 is a diagram illustrating a message flow for establishing a PTM channel by a common transport channel resource initialization procedure during MBMS service handover according to a fourth embodiment of the present invention.

8A to 8B illustrate the operation of the SRNC when receiving a cell update or URA update message from the DRNC according to the present invention.

9A-9B illustrate the operation of a DRNC in accordance with a preferred embodiment of the present invention.

10 is a diagram illustrating operation of a UE according to a preferred embodiment of the present invention.

The present invention relates to a Multimedia Broadcast / Multicast Service (hereinafter referred to as MBMS Service), and in particular, to provide the MBMS service, a Radio Network Controller (hereinafter referred to as 'RNC'). The present invention relates to a method for performing UE linking and configuration of a radio bearer in an Iur interface between the two.

Due to the development of communication technology, the services provided by the mobile communication system using the wideband code division multiple access method are not only a conventional voice service but also a large amount of data such as packet data and circuit data. It is developing into packet service communication and multimedia broadcasting / communication capable of transmitting multimedia service. Accordingly, in order to support the multimedia broadcasting / communication, an MBMS service that provides a service from one or more multimedia data sources to a plurality of user equipments (hereinafter referred to as UEs) has been discussed.

The MBMS service refers to a service for transmitting the same multimedia data to multiple receivers through a wireless network. In this case, by allowing multiple receivers to share one radio channel, it is possible to save radio transmission resources. The MBMS service supports multimedia transmission forms such as real-time video, audio, still images, and text. The MBMS service is a service that can simultaneously provide audio data and video data according to the multimedia transmission format, and requires a large amount of transmission resources. In the case of the MBMS service, since the same data must be transmitted to a plurality of cells in which users are located, one-to-one (Point to Point) or one-to-many depending on the number of users located in each cell. (Hereinafter referred to as 'PTM') connection is made.

1 is a diagram illustrating a network configuration for a general MBMS service.

Referring to FIG. 1, UEs 161, 162, 163, 171, and 172 refer to terminal equipment or subscribers capable of receiving MBMS service, and cell 1 160 and cell 2 170 are subscribers. It is controlled by the base station apparatus, that is, the Node B, which wirelessly transmits MBMS-related data to the base station. The RNC 140 controls the plurality of cells 160 and 170, selectively transmits multimedia data to a specific cell, and controls a radio channel configured to provide an MBMS service. The connection between the RNC 140 and the UEs 161, 162, 163, 171, and 172 is connected to a Radio Resource Control (RRC) interface.

The RNC 140 is a Packet Switched or Packet Service (PS) network such as the Internet by a Serving GPRS Support Node (SGSN) 130. Is connected to. Communication between the RNC 140 and the PS network is made by packet switched signaling (hereinafter referred to as 'PS signaling'). In particular, the connection between the RNC 140 and the SGSN 130 is called an Iu-PS interface. SGSN 130 controls the MBMS-related services of each subscriber. Representative examples of the role played by the SGSN 130 include managing a service related data of each subscriber and selectively transmitting multimedia data to a specific RNC 140.

Transit NW 120 provides a communication path between Broadcast Multicast Service Center (hereinafter referred to as BM-SC) 110 and SGSN 130, and provides a gateway packet radio. It may be connected to an external network through a Gateway GPRS Support Node (hereinafter referred to as 'GGSN') (not shown). The BM-SC 110 is responsible for scheduling MBMS data as a source of MBMS data.

The RNC 140 is connected to a Circuit Switched (CS) network by a Mobile Switching Center (MSC) 150. The CS network refers to a voice-based legacy communication network that is connection-based. Communication between the RNC 140 and the MSC 150 is performed by circuit switched signaling (CS signaling). In particular, the connection between the RNC 140 and the MSC 150 is called an Iu-CS interface.

MBMS data streams are delivered to UEs 161, 162, 163, 171 and 172 via the transport network 120, SGSN 130, RNC 140, Node B and cells 160, 170.

Although not shown in FIG. 1, there may be multiple SGSNs for one MBMS service and multiple RNCs for each SGSN. Each SGSN is an RNC 140, and each RNC performs selective data transmission to each of a plurality of cells, and for this purpose, a list of nodes to which a data stream should be delivered (that is, SGSN is a list of RNCs, and the RNC is a cell). List) and the like and selectively perform MBMS data transmission only to the stored nodes later.

In order for UEs to access a network and receive a service, a context, which is a set of information required to provide a corresponding service between UEs and network nodes, must be created. Typically, the context includes a UE context and a mobility management (hereinafter referred to as 'MM') context.

First, the RNC creates a UE context for UEs after establishing an RRC connection. The UE context is composed of basic information such as UE identifier, location information of the UE, RRC status information of the UE, and radio resource information allocated to the UE, and is managed by the RNC while the RRC connection is active.

The MM context is for managing the location of the UE in the core network (including SGSN 130 and GGSN). In order for the UE to receive the PS service, first, the MM context of the UE must be generated in the SGSN 130 and the GGSN through a GPRS attach procedure. In particular, the MM context of SGSN 130 may include international mobile subscriber identity (hereinafter referred to as IMSI), temporary mobile subscriber identity (hereinafter referred to as P-TMSI), and international mobility. UE identifiers such as device identification (International Mobile Equipment Identity, hereinafter referred to as 'IMEI'), Mobile Subscriber Integrated Switched Data Network (ISDN) Number (hereinafter referred to as MS-ISDN), and routing Location information such as Routing Area (hereinafter referred to as RA) and Service Area Code (hereinafter referred to as "SAC"), authentication / encryption related information, billing information and discontinuous reception parameters (Discontinuous Reception Parameters) , Hereinafter referred to as 'DRX parameter', and the like.

FIG. 2 is a diagram illustrating a network configuration when one or more RNCs are related to guarantee mobility of one UE in FIG. 1. Here, the BM-SC, Transit NW, MSC, SGSN, etc. of FIG. 1 are briefly represented as one central network node (hereinafter referred to as 'CN') node 301. The two RNCs of FIG. 2, RNC1 311 and RNC2 312, are connected to the CN node 301, and at this time, a wired passage connecting the CN 301 and the RNCs 311 and 312. 341 denotes an Iu interface, and a wired path 342 connecting the RNC1 311 and the RNC2 312 is called an Iur interface. Cell1 321 and Cell2 322 are present under the RNC1 311 and the RNC2 312, respectively. Initially, the UE 331 is located in the Cell1 321 and the RNC1 311 as a radio path 351. In the state connected to the Cell2 (322) and shows the state connected to the RNC2 (312) via a new radio path (352). In this figure, Node B, which plays a role of directly managing a cell and exists between the RNC and the UE, is omitted.

FIG. 3 illustrates a case where a UE in a CELL_FACH (Forward Access Channel), CELL_PCH (Paging Channel), or URA_PCH state receiving MBMS service moves from CELL1 managed by RNC1 to CELL2 managed by RNC2 as shown in FIG. A diagram illustrating a procedure for managing mobility in a UMTS network.

 First, in step 410, if the UE 401 in the CELL_FACH or CELL_PCH state detects that the CELL has been changed, in step 411, the UE sets a cell update message, which is an RRC message, to a common control channel (hereinafter referred to as 'CCCH'). Send through The UE in the URA_PCH state sends a UTRAN Registration Area (URA) Update or Cell Update message on the CCCH.

In step 412, the RNC2 402 confirms the SRNC-ID included in the U-RNTI, which is a parameter of the cell update or URA update message, and transmits an NBAP message, uplink signaling, to the SRNC 403 that has previously managed the UE. Uplink Signaling Transfer: (hereinafter referred to as 'UST') transmits a cell update / URA update message.

In step 413, the SRNC 403 confirms that the UE 401 is receiving the MBMS service, and sends the list of services subscribed to by the UE 401 in the MBMS Attach Request message to the DRNC 402. The same process as step 413 is referred to as MBMS Iur linking or UE linking process. In step 414, the DRNC 402 that receives the MBMS Attach Request creates an MBMS UE context corresponding to the UE that has requested the connection, and if any of the services subscribed to the UE are not registered in the DRNC 402, the DRNC 402 requests the SGSN. After registering the service, it decides which channel each MBMS service will serve. In step 415, the channel type information of each service is transmitted to the SRNC 403 in an MBMS attach response message.

In step 416, the SRNC 403 configures each MBMS service as PTP or PTM according to the service channel type information carried in the MBMS access response message to configure a channel necessary for the DRNC 402, Node B (not shown), and the like. do. Although not shown, a radio link setup procedure is performed when a PTP service is set, and a common transport channel initialization procedure is performed when a PTM service is set.

Finally, in step 417, the SRNC 403 sends a cell update confirm or URA update confirm message, which is an RRC message, to the UE through a dedicated control channel (hereinafter referred to as 'DCCH'). If the UE's state changes, the UE changes to a new state, and if it does not change, the UE can continuously receive the MBMS service as it is.

As described above, in order to seamlessly transmit MBMS service when the UE moves from one RNC to another RNC, the MBMS connection procedure corresponding to steps 413 and 415 must be performed on Iur, unlike general service transmission. Channel configuration delay occurs.

Accordingly, an object of the present invention to solve the above problems is to provide a MBMS service, Iur UE linking method of the MBMS service.

Another object of the present invention is to inform the DRNC that the UE is receiving the MBMS service when the UE receiving the MBMS service is moved to a cell managed by another RNC in an RRC message to the Iur UE linking from the SRNC in which the DRNC will be in the future. It provides a way to prepare.

Another object of the present invention is to confirm that the UE is receiving the MBMS service DRNC to inform the SRNC of the channel type of all or some MBMS services transmitted in the cell where the UE is newly located to help the SRNC UE linking and channel configuration Is to provide a way to do this.

It is still another object of the present invention to provide a method for enabling an SRNC, which identifies how each MBMS service is transmitted in a cell in which a UE is located, to simultaneously perform a UE linking process and a channel configuration process through a single procedure. It is.

In order to achieve the above object, an embodiment of the present invention provides a method for handover of a multimedia broadcasting / multicast service (MBMS service) in consideration of mobility of a user terminal (UE). Transmitting service information on the MBMS service subscribed to by the UE in an update message for transmission to a drift radio network controller (DRNC) connected to the UE, and the DRNC transmits an MBMS service list and channel type information of the MBMS service; And transmitting a signaling transmission message including a to a serving radio network controller (SRNC) that controls radio resources of the UE, and the SRNC subscribes to the MBMS service according to the signaling transmission message transmitted from the DRNC. Identifying a service transmission type of the SRNC, and the SRNC transmits an MBMS service to the DRNC including MBMS service lists; It characterized by including the step of passing the radio link setup message including the list.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, if it is determined that a detailed description of a known function or configuration may unnecessarily flow the gist of the present invention, the detailed description thereof will be omitted. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

The present invention aims to reduce unnecessary signaling overhead and transmission delay by simplifying the RNSAP procedure on Iur, which is essential when a UE attempts to provide a seamless MBMS service to a user in a moving situation.

If the user wants to receive the MBMS service on the go, SRNC provides the Iur UE linking process to provide the DRNC with the list of MBMS services subscribed to the UE, and the annoying SRNC can set the correct MBMS channel type for the cell managed by the DRNC. A channel type indication process in which the DRNC informs the SRNC of the MBMS channel type currently being transmitted in the cell where the UE is located is essential.

The present invention allows the DRNC to inform the SRNC of the UE of channel type information of MBMS services being served in the cell when the DRNC first discovers a UE first introduced into a cell managed by the DRNC. The SRNC compares the information and the list of services subscribed to by the UE stored in the UE context to check whether a specific MBMS service is served by PTP or PTM in the cell, and simultaneously performs MBMS channel setup and Iur UE linking to the DRNC. Can be. The present invention can simultaneously perform Iur UE linking and MBMS channel establishment, thereby reducing signaling overhead and channel establishment delay.

At this point, the first message for which the DRNC confirms a UE in a CELL_FACH, CELL_PCH, or URA_PCH state is a cell update or URA update, which is an RRC message. ) To deliver the RRC message received from the UE.

Therefore, in the present invention, as described above, the UST message carries channel type information of the MBMS service served by the target cell.

If the DRNC loads the MBMS channel type information in the UST message for all UEs that have transmitted the cell update or the URA update, unnecessary MBMS information will be displayed in the UST for UEs that do not provide the existing MBMS service, and existing REL99, REL4, and REL5 It does not meet the standards. Accordingly, in the present invention, when the UE informs the DRNC that the UE is receiving the MBMS service, the DRNC delivers the MBMS service channel type in the UST message to the SRNC.

4 is a diagram illustrating a message flow occurring between DRNC, SRNC and UE according to MBMS service handover between RNCs according to the first preferred embodiment of the present invention.

In step 510, a UE in a CELL_FACH, CELL_PCH, or URA_PCH state sends a cell update or URA update message to update a cell or UTRAN registration area (URA) in step 511. At this time, if the UE receives the MBMS service, the cell update or URA update message includes information indicating that the MBMS service.

There are several ways for the UE to inform the RNC whether it is receiving MBMS service, and Table 1 and Table 2 are examples of such methods. Tables described below, including (Table 1) and (Table 2), describe only parameters added according to an embodiment of the present invention without describing the entire parameter of the message.

In Table 1, an MBMS indicator, which is an information element whose value is 0 or 1, is used for the cell update and URA update messages. The MBMS indicator information element may be included in the UE information element group and has a value of 1 if the UE is subscribed to at least one MBMS service, and 0 if the UE is not subscribed to any service. Table 2 above adds the MBMS cause value to the cause of the existing cell update and URA update messages.

The DRNC receiving the cell update or URA update message sent by the UE transmits the cell update or URA update message to the SRNC using UST, which is an RNSAP message, in step 512. At this time, as described above, the channel information of the MBMS service transmitted in the target cell is included in the UST message and transmitted to the SRNC.

Tables 3 and 4 below are examples of how the DRNC, which has received information that the UE has subscribed to the MBMS service from the cell update or URA update message, loads channel information of the MBMS service in the UST message.

In the present invention, as shown in Table 3, the UST message carries channel information of all MBMS services being serviced in the target cell and sends them to the SRNC. Here, TMGI is an ID of MBMS service defined by BM-SC, and all MBMS services can be classified into one unique TMGI. Channel information corresponding to each service may be determined as one of PTP, PTM, or No service. Here, 'No service' indicates that an MBMS service is registered in the DRNC but is not serviced in the destination cell for various reasons such as lack of radio resources.

Unlike Table 3, Table 4 is an example of delivering a list of services, which are being serviced in PTM format, to the SRNC. When using this method, there is an advantage that the amount of information to be transmitted to the SRNC is reduced compared to the method as shown in Table 3, which transmits the entire service list and channel information. In Table 4 above, only the PTM service list is delivered. However, a method of transmitting only the PTP service list is also possible.

In step 513, the SRNC checks how the service subscribed to the UE is served in the destination cell. Based on this result, the next task to be performed is as follows.

First, if it is confirmed that the service is PTM, the SRNC should establish a channel through a common transport resource request message. Second, if it is confirmed that the service is PTP or that the DRNC does not have information about the desired service, the SRNC is likely to perform the PTP service in the future for these services. You will need to set up the channel via a message. Lastly, if no service message is received due to lack of radio resources of the target cell or the like, the UE does not need to configure a channel. Only UE linking to the DRNC is possible through the MBMS access request message.

Therefore, if the channel type of the entire service being served in the target cell is received from the UST as shown in Table 3, all three cases can be distinguished. However, if only the PTM service list is delivered as shown in (Table 4) above, if the UE does not have the desired service in this list, the channel is configured through the radio link establishment message. If only the PTP service list is delivered, the PTM service and the service not registered in the DRNC cannot be distinguished, and when the channel is set through the common transport resource request message, the initial setting fails for a service not yet registered in the DRNC. This can incur the overhead of setting up a new channel.

In the first embodiment, only the operation of the SRNC when confirming that the service subscribed to by the UE is not serviced in the target cell by the No service or the PTM method is described. To deal with it. Lastly, when checking No service, if there is no FACH service other than MBMS in the past, it is obvious that MBMS access procedure should be performed. Therefore, embodiments will not be described separately.

In step 513, the SRNC confirming that the service subscribed to by the UE is not serviced by the target cell in the No service or PTM scheme, attempts to set up the PTP bearer via the DRNC through the radio link establishment request message in step 514. At this time, the UE linking and MBMS bearer setup are simultaneously performed by including the service list subscribed to by the UE in the radio link setup request message.

As described above, the DRNC receiving the service list subscribed to by the UE determines whether to perform the PTP service or the PTM service based on this. If the DRNC decides to perform the PTP service, in step 516 the DRNC prepares the radio link establishment on the Iub and Uu interfaces, and then in step 517 sends a radio link establishment response message to the SRNC.

In step 518, the SRNC confirming that the radio link establishment has been successfully performed sends an RRC message, Cell Update Confirmation or URA Update Confirmation, to the UE. At this time, it is obvious that the information on the radio link set in step 516 is delivered.

Finally, in step 519, the UE receiving the cell update confirmation / URA update confirmation message changes to the CELL_DCH state and receives the MBMS service through the PTP.

FIG. 5 is a diagram illustrating a message flow occurring between DRNC, SRNC and UE when a PTM channel is set up when a radio link failure occurs during MBMS service handover according to the second preferred embodiment of the present invention.

Step 610 to step 614 is the same as the procedure of FIG. However, in step 615, unlike the embodiment of FIG. 4, the DRNC, which finds that the number of UEs which desire a specific MBMS service has increased by one, determines that the MBMS service will be serviced by the PTM.

In the case of the PTM, the dedicated channel for the UE is unnecessary, so in step 616, the DRNC informs the SRNC via a radio link setup failure message. At this time, the cause of RL setting failure can be set to PTM or No service.

If the cause of the RL establishment failure is No service, SRNC sends a cell update confirmation / URA update confirmation message to the UE and terminates the operation. If the cause of the RL establishment failure is not No service, the SRNC requests the PTM service with the common transport channel resource request message in step 617, and in step 618, the DRNC sends a common transport channel resource response message to the SRNC.

Finally, in step 619, the SRNC sends a cell update confirmation / URA update confirmation message to the UE to terminate the operation. In step 620, the UE switches to the CELL_FACH state and receives the MBMS PTM service transmitted on the FACH channel.

FIG. 6 is a diagram illustrating a message flow between a UE, SRNC, DRNC, and SGSN when a service desired by a UE is not registered in the DRNC at the time of MBMS service handover according to the third embodiment of the present invention.

Steps 710 to 714 are the same as step 510 to step 514 of FIG. 4. In step 715, the DRNC confirms that the service desired by the UE is not registered yet. In step 716, the DRNC informs SGSN that the UE wants to receive the service desired by the MBMS registration procedure. In step 717, the SGSN informs the DRNC that the session has been started by the MBMS session start procedure and sets up a Radio Access Bearer (hereinafter referred to as RAB) related to the MBMS service so that the MBMS data can flow to the DRNC. do. For reference, the MBMS session start procedure means a procedure for setting an MBMS RAB.

The DRNC now decides to perform the MBMS service with PTP in step 718. Steps 719 to 722 are performed in the same manner as in step 516 to step 519 of FIG. 4, so that the UE is allocated a dedicated channel to receive the MBMS service.

7 is a diagram illustrating a message flow for establishing a PTM channel by a common transport channel resource initialization procedure during MBMS service handover according to the fourth embodiment of the present invention.

Steps 810 to 812 are the same as those of steps 610 to 612 of FIG. 5. In step 813, the SRNC confirms that the UE wants the service to be serviced by the DRNC in a PTM manner, and in step 814, the SRNC loads a list of services subscribed to by the UE in the common transport channel resource request message and delivers it to the DRNC. In step 815, the DRNC increments a counter of each service subscribed to by the UE received from the SRNC by one, writes that the total number of UEs receiving the corresponding services is added one by one, and decides to continuously perform the corresponding services in the PTM scheme.

In step 816, the DRNC informs the SRNC that the common channel is properly set up through a common transport channel resource response message, and in step 817, the SRNC sends a cell update confirmation / URA update confirmation message to the UE. Finally, in step 818, the UE enters the CELL_FACH state and receives the MBMS service on the shared channel.

8A to 8B illustrate the operation of the SRNC when receiving a cell update or URA update message from the DRNC according to the present invention.

The SRNC, beginning at step 900, which is in its initial state, checks in step 901 whether a cell update or URA update message has been received from the DRNC via a UST message. If the message is not received, it returns to the initial state. Receiving a cell update or URA update message from the DRNC, the SRNC checks in step 910 whether the UE is receiving MBMS service. If the MBMS service is not received, the cell update operation or the URA update operation is defined as shown in step 911. On the other hand, if the UE receiving the MBMS service transmits a cell update or URA update message, the process proceeds to step 920.

In step 920, the SRNC checks the service list provided by the destination cell included in the UST message and the channel type for each service, and if all the services subscribed to the UE are the No service list, that is, the lack of radio resources in the DRNC, etc. For this reason, check whether the list is included in the list of services registered but not transmitted. If all the services subscribed to by the UE are included in the No service list, the SRNC proceeds to step 940 to determine the transition to the CELL_FACH, CELL_PCH, or URA_PCH state, and performs work for each state. In contrast, if any of the services subscribed to by the UE is not included in the No service list, the process proceeds to step 930.

In step 930, as in step 920, the SRNC checks the service list provided by the destination cell included in the UST message and the channel type for each service to find out whether all the services subscribed to by the UE are serviced by the DRNC in the PTM method. see. If it is confirmed that all the services are being serviced by the PTM, go to step 940; otherwise, go to step 931.

In step 931, the SRNC inserts a list of services subscribed to by the UE into a radio link establishment message, transmits the list to the DRNC, and waits for a response from the DRNC.

If the radio link establishment response is received from the DRNC in step 932, the dedicated channel is correctly configured in the DRNC. In step 933, the SRNC transitions the UE to CELL_DCH, and in step 934, the PTP radio bearer in the cell update confirmation / URA update confirmation message. The information is sent to the UE and the operation ends.

If a radio link establishment failure message is received in response to the radio link establishment request message in step 935, since the dedicated channel establishment has failed, the SRNC transitions the UE to a state other than CELL_DCH so that the UE receives the MBMS service using the common channel. Proceed to step 940 to enable.

From step 940 to step 943, from step 950 to 953, and from step 960 to 963, respectively, indicate the operation of the SRNC when the SRNC decides to transition the UE to CELL_FACH, CELL_PCH, URA_PCH states.

First, in step 940, the SRNC decides to maintain the state of the UE in the CELL_FACH state, and in step 941, the SRNC adds the service list subscribed to the UE to the common transport channel resource request message and transmits it to the DRNC, and waits for a response in step 942. Receiving the common transport channel resource response message, the SRNC sends a cell update confirmation / URA update confirmation message including PTM radio bearer information to the UE in step 943 to terminate the operation.

In step 950, the SRNC, which decides to keep the UE in the CELL_PCH state, loads a list of services subscribed to by the UE in the MBMS access request messages in steps 952 and 953, and transmits the list to the DRNC, and waits for an MBMS access response. In response to the response, the SRNC sends a cell update confirmation / URA update confirmation message including PTM radio bearer information to the UE in step 953 to terminate the operation.

Steps 960 through 963 are the same as steps 950 through 953, which are processes for CELL_PCH except that the UE transitions to the URA_PCH state.

9A to 9B illustrate the operation of a DRNC according to a preferred embodiment of the present invention.

When the DRNC receives an RRC message such as a cell update or URA update message from the UE in step 1001, the DRNC checks whether the RRC message includes information indicating that the UE is receiving an MBMS in step 1002. If the above information is not included, the process is performed when an existing cell update or URA update message is received in step 1003, and the operation ends. If the RRC message contains information that the UE is receiving MBMS, in step 1004 the DRNC adds a list of services being serviced in the destination cell and a channel type to the UST message about how each service is being served. Transmit to DRNC of the UE. At this time, the UST message may specify channel types for all registered services as described in Table 3 as described above, or may include only service IDs that are serviced in a PTM or PTP manner as shown in Table 4 below. have.

When waiting for a message from the SRNC in step 1005 and receiving a radio link establishment request message in step 1010, the DRNC checks whether all services desired by the UE are already registered with the DRNC, as shown in step 1011. If all services are registered, proceed to step 1013, otherwise proceed to step 1012. In step 1012, the DRNC performs an MBMS registration procedure with the SGSN to create an MBMS service context in the DRNC, and a user plane through which the MBMS service data can be transmitted between the SGSN and the SGSN through the MBMS session start procedure. After creating the passage, proceed to step 1013.

In step 1013, the DRNC increments the counter value in each MBMS service context requested by the UE by one and determines the channel type of the MBMS services based on this. In step 1014, if one or more services are determined by the PTP method, the process proceeds to step 1015 and the DRNC establishes a dedicated channel between the UE and transmits a radio link establishment response message to the SRNC and completes the operation.

If the channel type cannot provide the PTM or the MBMS service, the DRNC proceeds to step 1016 and writes a cause value in the radio link establishment failure message as a PTM or No service to the SRNC.

If the message received from the SRNC in step 1020 is a common transport channel resource request, the DRNC proceeds to step 1021 to increment a counter value by one in each MBMS service context requested by the UE and determine a channel type of MBMS services based on the counter values. . If the determined channel type is PTM, as shown in step 1023, the common channel is set, and then a common transport channel resource response message is transmitted to the SRNC. If not, proceed to step 1024 and write the cause value in the common transport channel resource failure message to the SRNC with PTP or No service.

Finally, if the message received from the SRNC is an MBMS access request, the process proceeds to steps 1030 to 1031 to update the counter values and then determines the channel type according to the counter values. The DRNC then sends an MBMS Connection Response message to the SRNC at step 1032.

For reference, although not expressly shown in the drawing, the DRNC determines whether the UE sets the response message of steps 1015, 1016, 1023, 1024, 1032, etc. for each service requested by the UE, such as PTP, PTM or No service. You can inform SRNC with information about.

10 is a diagram illustrating the operation of a UE according to a preferred embodiment of the present invention.

In step 1101, the UE that decides to perform the cell update or the URA update first checks whether it is registered in the MBMS service. If it is not registered, the existing cell update / URA update procedure is performed. If there is a registered service, the process proceeds to step 1110.

In step 1110, the UE transmits the information on the Uu interface including the information indicating that it is receiving the MBMS service in the cell update / URA update message and waits for the cell update confirmation / URA update confirmation message in step 1111 to terminate the operation.

In the present invention operating as described in detail above, the effects obtained by the representative ones of the disclosed inventions will be briefly described as follows.

The present invention adds information that the UE is receiving the MBMS service to the uplink RRC message sent to the SRNC by the UE, and if the DRNC checks this and the UE receives the MBMS service, the MBMS service channel in the cell where the UE is located The type is informed to the SRNC through an UL signaling transfer message, and the SRNC checks the message and sets up the MBMS channel. As a result, the MBMS channel setup, which was performed over two procedures, can be shortened to one procedure, thereby reducing unnecessary signaling burden and service delay.

Claims (27)

In the handover method of the multimedia broadcasting / multicast service (MBMS service) in consideration of the mobility of the user terminal (UE), Transmitting, by the UE, service information on the MBMS service subscribed to by the UE in an update message for updating location information, and transmitting the service information to a drift radio network controller (DRNC) connected with the UE; Transmitting, by the DRNC, a signaling transmission message including an MBMS service list and channel type information of the MBMS service to a serving radio network controller (SRNC) controlling radio resources of the UE; Identifying, by the SRNC, a service transmission type of an MBMS service subscribed to by the UE according to the signaling transmission message transmitted from the DRNC; And transmitting, by the SRNC, a radio link establishment message including an MBMS service list to the DRNC including MBMS service lists. In the handover method of the multimedia broadcasting / multicast service (MBMS service) in consideration of the mobility of the user terminal (UE), Transmitting, by the UE, service information on the MBMS service subscribed to by the UE in an update message for updating location information, and transmitting the service information to a drift radio network controller (DRNC) connected with the UE; Transmitting, by the DRNC, a signaling transmission message including the update message and channel type information of the MBMS service to a serving radio network controller (SRNC) that controls radio resources of the UE; Identifying, by the SRNC, a service transmission type of an MBMS service subscribed to by the UE according to the signaling transmission message transmitted from the DRNC; Determining, by the SRNC, that the service type of the MBMS service is not serviceable or one-to-many, and establishing a radio link including a dedicated channel for the MBMS service via the DRNC; When the radio link is successfully established, the SRNC sending an update confirmation message to the UE through a dedicated control channel; And receiving the MBMS service through the dedicated channel after the UE receives the update confirmation message. The method of claim 2, wherein the update message, And a MBMS indicator having a value of 1 if the UE is subscribed to at least one MBMS service and a value of 0 if not subscribed to any service. The method of claim 2, wherein the signaling transmission message, The channel type information of the MBMS service being transmitted in a cell below the DRNC where the UE is located. The method of claim 4, wherein the channel type information of the MBMS service, A service type of the MBMS service determined as one of one-to-one (PTP), one-to-many (PTM) or no service; And a unique ID of the MBMS service. 6. The method as claimed in claim 5, wherein the service unavailable indicates that the MBMS service is registered with the DRNC but is not currently being serviced in the cell. The method of claim 4, wherein the channel type information of the MBMS service, The service list of MBMS services being serviced in a one-to-many manner or a service list of MBMS services being served in a one-to-one manner. The method of claim 2, wherein the establishing of the radio link comprises: And the SRNC transmits a radio link establishment request message including a service list of MBMS services subscribed to by the user terminal to the DRNC. In the handover method of the multimedia broadcasting / multicast service (MBMS service) in consideration of the mobility of the user terminal (UE), Transmitting, by the UE, service information on the MBMS service subscribed to by the UE in an update message for updating location information, and transmitting the service information to a drift radio network controller (DRNC) connected with the UE; Transmitting, by the DRNC, a signaling transmission message including the update message and channel type information of the MBMS service to a serving radio network controller (SRNC) that controls radio resources of the UE; Identifying, by the SRNC, a service transmission type of an MBMS service subscribed to by the UE according to the signaling transmission message transmitted from the DRNC; The SRNC confirming that the service type of the MBMS service is not serviceable or one-to-many, and transmitting a radio link setup request message to the DRNC requesting wireless link setup including a dedicated channel for the MBMS service; and, Transmitting, by the DRNC, a radio link establishment failure message to the SRNC after confirming that the channel type of the MBMS service is one-to-many after receiving the radio link establishment request message; Establishing, by the SRNC, a radio link including a shared channel for the MBMS service via the DRNC; When the radio link including the common channel is successfully established, the SRNC transmitting an update confirmation message to the UE through a dedicated control channel; And receiving the MBMS service through the shared channel after the UE receives the update confirmation message. The method of claim 9, wherein the update message, And a MBMS indicator having a value of 1 if the UE is subscribed to at least one MBMS service and a value of 0 if not subscribed to any service. The method of claim 9, wherein the signaling transmission message, The channel type information of the MBMS service being transmitted in a cell below the DRNC where the UE is located. The method of claim 11, wherein the channel type information of the MBMS service, A service type of the MBMS service determined as one of one-to-one (PTP), one-to-many (PTM) or no service; And a unique ID of the MBMS service. 13. The method as claimed in claim 12, wherein the service unavailable indicates that the MBMS service is registered with the DRNC but is not currently being serviced in the cell. The method of claim 11, wherein the channel information of the MBMS service, The service list of MBMS services being serviced in a one-to-many manner or a service list of MBMS services being served in a one-to-one manner. The method of claim 9, wherein the radio link establishment failure message, And a failure cause value indicating that the MBMS service is one-to-many. In the handover method of the multimedia broadcasting / multicast service (MBMS service) in consideration of the mobility of the user terminal (UE), Transmitting, by the UE, service information on the MBMS service subscribed to by the UE in an update message for updating location information, and transmitting the service information to a drift radio network controller (DRNC) connected with the UE; Transmitting, by the DRNC, a signaling transmission message including the update message and channel type information of the MBMS service to a serving radio network controller (SRNC) that controls radio resources of the UE; The SRNC confirms that the MBMS service subscribed to by the UE is not registered with the DRNC according to the signaling transmission message transmitted from the DRNC, and sets the DRNC to establish a radio link including a dedicated channel for the MBMS service. Transmitting a request for setting a wireless link request message; Registering by the DRNC with the MBMS service and establishing a radio link including a dedicated channel for the MBMS service; When the radio link is successfully established, the SRNC sending an update confirmation message to the UE through a dedicated control channel; And receiving the MBMS service through the dedicated channel after the UE receives the update confirmation message. The method of claim 16, wherein the update message, And a MBMS indicator having a value of 1 if the UE is subscribed to at least one MBMS service and a value of 0 if not subscribed to any service. The method of claim 16, wherein the signaling transmission message, The channel type information of the MBMS service being transmitted in a cell below the DRNC where the UE is located. 19. The method of claim 18, wherein the channel type information of the MBMS service, A service type of the MBMS service determined as one of one-to-one (PTP), one-to-many (PTM) or no service; And a unique ID of the MBMS service. 20. The method as claimed in claim 19, wherein the service unavailable indicates that the MBMS service is registered with the DRNC but is not currently being serviced in the cell. 19. The method of claim 18, wherein the channel type information of the MBMS service, The service list of MBMS services being serviced in a one-to-many manner or a service list of MBMS services being served in a one-to-one manner. In the handover method of the multimedia broadcasting / multicast service (MBMS service) in consideration of the mobility of the user terminal (UE), Transmitting, by the UE, service information on the MBMS service subscribed to by the UE in an update message for updating location information, and transmitting the service information to a drift radio network controller (DRNC) connected with the UE; Transmitting, by the DRNC, a signaling transmission message including the update message and channel type information of the MBMS service to a serving radio network controller (SRNC) that controls radio resources of the UE; Identifying, by the SRNC, a service transmission type of an MBMS service subscribed to by the UE according to the signaling transmission message transmitted from the DRNC; Determining, by the SRNC, that the service type of the MBMS service is one-to-many, and establishing a radio link including a shared channel for the MBMS service via the DRNC; When the radio link including the common channel is successfully established, the SRNC transmitting an update confirmation message to the UE through a dedicated control channel; And receiving the MBMS service through the shared channel after the UE receives the update confirmation message. The method of claim 22, wherein the update message, And a MBMS indicator having a value of 1 if the UE is subscribed to at least one MBMS service and a value of 0 if not subscribed to any service. The method of claim 22, wherein the signaling transmission message, The channel type information of the MBMS service being transmitted in a cell below the DRNC where the UE is located. The method of claim 22, wherein the channel type information of the MBMS service, A service type of the MBMS service determined as one of one-to-one (PTP), one-to-many (PTM) or no service; And a unique ID of the MBMS service. 26. The method of claim 25, wherein the 'service unavailable' indicates that the MBMS service is registered with the DRNC but is not currently being serviced in the cell. The method of claim 24, wherein the channel information of the MBMS service, The service list of MBMS services being serviced in a one-to-many manner or a service list of MBMS services being served in a one-to-one manner.

Images