METHOD FOR ESTABLISHING A SIGNALING BEARER CONNECTION ON Iu INTERFACE FOR MBMS

Description of equivalent WO 2004043021 A1

METHOD FOR MULTIMEDIA BROADCAST/MULTICAST SERVICE SIGNALING BEARER CONNECTION ON IU

INTERFACE

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to Multimedia Broadcast/Multicast Service in Wideband

Code Division Multiple Access (hereinafter referred to as WCDMA) mobile communication system, more specifically, relates to a method for signaling bearer connection of Multimedia Broadcast/Multicast Service on lu interface (the interface between Radio Access Network and Core Network).

2. Description of the Prior Art Multimedia Broadcast and Multicast Service (hereinafter referred to as MBMS) is a new service under standardization by 3^r Generation Partnership Project (hereinafter referred to as 3 GPP). MBMS service is an unidirectional point-to-multipoint (p-t-m) service, whose most remarkable characteristic is that it can make use of radio resources and network resources efficiently.

The architecture of the MBMS system is described in brief in combination with Figure 1.

MBMS network structure adds new network elements based on the core network of General Packet Radio Service (hereinafter referred to as GPRS). Broadcast and Multicast Service center 101 (hereinafter referred to as BM-SC) is the service control center of MBMS system. Gateway GPRS Supporting Node 102 (hereinafter referred to as GGSN) and Service GPRS Supporting Node 103 (hereinafter referred to as SGSN) constitute the transmission network of MBMS service and provide route for data transfer. Home Location Register 106 (hereinafter referred to as HLR) saves the data related to user and can provide services such as user's authentication or the like. UMTS

Terrestrial Radio Access Network 104 (hereinafter referred to as UTRAN) provides radio resources for MBMS service over the air-interface. Iu 107 indicates the interface between Radio Access Network and Core Network. User Equipment 105 (hereinafter referred to as UE) is the terminal device for receiving data. Radio resources used by MBMS service are not dedicated for one user, but are shared by all users using this service. (1) Signaling connection mode of the existing lu interface

In order to transfer message of layer 3 between UE and CN, the existing Radio Access Network Application Part (hereinafter referred to RANAP) establishes a signaling connection for each activated UE. RANAP supports two modes, i.e. connection-oriented and connectionless-oriented.

(2) Signaling connection establishment and release of the existing lu interface

When information of UE and CN needs to be exchanged between Radio Network Controller (hereinafter referred to as RNC) and CN and there is no signaling connection control part (hereinafter referred to as SCCP) for this UE on lu interface, it is started to establish a new SCCP connection. The establishment of SCCP connection is as follows:

I) RNC initiates the establishment of SCCP signaling connection;

When RNC receives a non-MAC (Media Access Control) message from UE for the first time and there is no lu connection for this UE, RNC initiates the procedure of SCCP connection establishment. RNC sends a SCCP Connection Request message to

CN, which includes a RANAP message in its data field.

II) CN initiates the establishment of SCCP signaling connection

CN initiates the establishment of SCCP signaling connection when executing relocation. CN initiates the establishment of lu connection through sending a SCCP Connection Request message to RNC, which includes a RANAP message in its data field (optional).

Situations listed above are only those for SCCP connection establishment having been decided at present. And other situation will be introduced in the future.

On the occasion of normal release, the release of SCCP comiection is initiated by CN. When CN finds that a signaling connection isn't needed any more, the connection will be released and CN sends a SCCP RELEASED message.

On the occasion of abnormal, both CN and RNC can initiate a release procedure.

(3) The existing relocation procedure of Serving Radio Network Subsystem The SRNS relocation procedure is described by 3GPP specification TR 23.846 vl.2.0. Figure 2 shows the corresponding signaling flow. The detailed description for each step in the flow is as follows.

201 Source RNC decides to execute SRNS relocation procedure;

202 Source RNC sends a Relocation Demand message to the old SGSN; 203 The old SGSN forwards the Relocation Demand message to the new SGSN; 204 The new SGSN sends a Relocation Request message to the target RNC and a radio access bearer (hereinafter referred to as RAB) is established between the target RNC and the new SGSN. After the resources needed by RAB including resources of the user plane are successfully allocated, the target RNC sends a Relocation Request Confirmation message to the new SGSN.

205 The new SGSN forwards a Relocation Response message to the old SGSN.

206 The old SGSN sends a Relocation Command message to the source RNC.

207 The source RNC starts to copy data and sends them to the target RNC through network protocol (hereinafter referred to as IP layer). 208 The source RNC sends a Relocation delivery message to the target RNC. This procedure is used to transmit SRNS Context to the target RNC and the role of SRNS converts from the source RNC to the target RNC.

209 When the target RNC receives the trigger message for relocation execution, it sends a Relocation Detecting message to the new SGSN. After ^"that, ^'the target RNC starts to play the role of Serving Radio Network Controller (hereinafter referred to as

SRNC).

210 The UE exchanges mobility related information with the target RNC, such as the new SRNC Identifier, the representation of location area and uplink user data exchanging between UE and the target RNC, etc. 211 If the SRNS relocation is a relocation occurring between different SGSNs, the new SGSN sends a Update PDP Context Request message to the corresponding GGSN after it receives the Relocation Detecting message. GGSN updates Packet Data Protocol (hereinafter referred to as PDP) context and returns back a Update PDP Context Response message. The new SGSN examines respective MBMS services in MBMS Context of UE. IF a certain service is joined by the first UE in SGSN, a GPRS Tunnel Protocol (hereinafter referred to as GTP) tunnel between SGSN and GGSN is established and MBMS Context is created in GGSN.

212 The target SRNC initiates a Relocation completion procedure after receiving a UTRAN Mobility Information Confirmation message. The new SGSN sends a Relocation completion message to notify the old SGSN of the completion of SRNS relocation procedure.

213 Release the lu connection between the source RNC and the source SGSN and the user resources.

214 If the new Route Area Indication (hereinafter referred to as RAI) is different from that of the old, UE initiates a route location update procedure.

Cl, C2 and C3 execute Customized Applications for Mobile network Enhanced Logic (hereinafter referred to as CAMEL). Existing RANAP uses a signaling connection for each activated UE. MBMS service is a new point-to-multipoint service, whose feature is to make use of radio resources and network resources more efficiently through sharing. On lu interface, the user plane of MBMS services is shared. If each UE uses one signaling connection, it will not only increase the traffic of the information on lu interface and the processes on the RNC and SGSN side, but also be unable to solve completely the problem due to user mobility. In order to solve of the problem of user mobility, messages on the existing lu interface need to be modified as well. Thus, a method for lu interface connection oriented to MBMS service shall be proposed, which can not only make reasonable use of network resources, reduce processes on RNC and SGSN side and modifications to the existing message, but also can solve the problem of user mobility.

The existing Relocation Demand message is connection-oriented. If an user does not have other services (e.g. voice) except for receiving MBMS service, the lu connection dedicated to the user has not been established. How to send a relocation demand message or establish lu connection dedicated for the UE is the problem to be solved.

Since the user plane of MBMS service on lu interface is shared, while the user plain and control plane of other services are dedicated, SRNS relocation procedure needs to be modified in this new mode.

Besides the connection method proposed in this invention (shared signaling connection is used on lu for the same kind of MBMS service, and at the same time, dedicated lu connection is established for the case in which other services besides

MBMS service are received and the mobility of the UE occurs), there is another proposal that only shared lu connection exists on lu interface for UEs receiving MBMS. With respect to both these cases in which shared lu connection exists, the method for establishing and releasing MBMS shared connection hasn't been provided in the existing SCCP connection establish procedure, and the situation for establishing shared connection shall be added to the conditions for establishing SCCP connection. Since MBMS is a new-introduced service, when the shared connection used for MBMS service shall be released is a problem unsolved in present specification.

SUMMARY OF THE INVENTION

The object of this invention is to provide a new method for establishing a shared lu signaling connection for the same kind of MBMS service. In order to realize above object, according to one aspect of this invention, a method of signaling bearer connection on lu interface for MBMS service is provided, in which RNC establishes the shared signaling bearer for MBMS service on lu interface, the method includes the following steps:

(a) RNC receives a MBMS Notification message for a certain MBMS service from

SGSN;

(b) RNC constructs a MBMS Service Request message according to the contents of the notification; (c) RNC sends a SCCP Connection Request message to SGSN, requests to establish a

SCCP signaling connection, and then waits for a reply;

RNC receives a SCCP Connection Confirmation message from SGSN, which indicates the success of shared lu signaling connection establishment for this service.

According to another aspect of this invention, a method of signaling bearer connection on lu interface for MBMS service is provided, in which SGSN establishes the shared signaling bearer for MBMS service, the method includes the following steps: a) SGSN sends a MBMS Notification message to Radio Network Controller (RNC) after receiving the data sent from GGSN, notifies of relevant MBMS service information, and then waits for the response message from RNC; b) After receiving a SCCP Connection Request message from RNC, SGSN separates the RANAP message included in the data fields, saves the lu signaling connection ID allocated by RNC for this service; allocates the identifier of the signaling connection in SGSN, and then constructs a SCCP Connection Confirmation message and a MBMS RAB Assignment Request message; c) SGSN sends a SCCP Connection Confirmation message to RNC;

SGSN sends a MBMS RAB Assignment Request message to RNC via the shared lu connection established. If the MBMS RAB Assignment Request message is included in the data field of the SCCP Connection Confirmation message, this step can be omitted.

According to another aspect of this invention, a method of signaling bearer connection on lu interface for MBMS service is provided, in which SGSN establishes the shared signaling bearer for MBMS service on lu interface, the method includes the following steps: a) SGSN receives MBMS data from GGSN; b) SGSN analyzes the service to be performed. If there is no shared lu connection for this service, it organizes a SCCP Connection Request message, whose data fields include a MBMS RAB Assignment Request message. c) SGSN sends a SCCP Connection Request to RNC, requests to establish SCCP signaling connection, and then waits for a reply;

SGSN receives a SCCP Connection Confirmation message from RNC, which indicates the success of the shared lu signaling connection establishment for this service.

According to still another aspect of this invention, a method of signaling bearer connection on lu interface for MBMS service is provided, in which RNC establishes the shared signaling bearer for MBMS service on lu interface, the method includes the following steps: a) After receiving a SCCP Connection Request message from SGSN, RNC separate^'s the RANAP message included in the data fields, saves the lu signaling connection

ID allocated by SGSN for this service; allocates the identifier of the signaling connection in RNC, and then constructs a SCCP Connection Confirmation message and MBMS RAB Assignment Response message; b) RNC sends a SCCP Connection Confirmation message to SGSN; c) RNC sends a MBMS RAB Assignment Response message to SGSN via the shared lu connection established. If the MBMS RAB Assignment Response message is not included in the data field of the SCCP Connection Confirmation message, this step can be omitted;

This invention solves the problem of signaling connection on lu interface after

MBMS service is introduced into the existing mobile communication system.

1. The connection mode given in this invention can reasonably utilize network resources, reduce effectively signaling congestion on lu interface, and reduce modifications to the existing lu interface message. 2. Through modifying the SRNS relocation flow, it solves the problem due to user mobility in the case of introducing the MBMS service. These modifications have no effect on the existing relocation procedure and keep afterward compatibility.

3. It provides an establish and release mechanism for shared lu connection, thereby to guarantee the feasibility of the existence of shared connection. BRIEF DESCRIPTION OF THE DRAWINGS

The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings in which:

Figure 1 schematically illstrates MBMS system configuration;

Figure 2 shows the procedure of the existing SRNS relocation;

Figure 3 shows the flow of the establishment of the shared lu signaling connection for MBMS according to the first method of the invention; Figure 4 shows the flow of the establishment of the shared lu signaling connection for MBMS according to the second method of the invention;

Figure 5 shows the flow of establishing the dedicated lu signaling connection for UE receiving MBMS data;

Figure 6 shows the SRNC relocation procedure (wherein the release of shared lu connection is method 1);

Figure 7 shows the SRNC relocation procedure (wherein the release of shared lu connection is method 2);

Figure 8 shows the SRNC relocation procedure (wherein the release of shared lu connection is method 3).

DETAILED DESCRIPTION OF THE INVENTION

In order to provide a reasonable lu connection mode for MBMS service, this invention makes modification and innovation for the existing technology in follow several aspects:

• The use of a shared lu signaling connection for the same kind of MBMS service is proposed, and a UE dedicated lu signaling connection is established if UE receives other services besides MBMS service or moves. Those messages providing services for MBMS are sent through the shared lu connection. The identical messages for the same kind of service needn't be sent repeatedly at the same time, thereby to make use of network resources reasonably. A dedicated lu connection is used for other non-MBMS service or for a user's mobility, which can reduce modifications to the existing messages. • The problem of how to send a Relocation Demand message on occasion that user only receives MBMS service is solved.

A new situation is added to the trigger conditions of the existing SCCP connection establishment: when RNC sends a Relocation Request message to SGSN, if there is no lu connection for this UE on lu interface, a SCCP connection establishment procedure is initiated.

• Modification to the relocation procedure

In order to solve the problem due to the user mobility after introducing MBMS, some messages are added to the SRNS relocation flow, thereby to solve completely the relocation problem when the user plane is shared and the control plane employs this new lu connection mode.

• Conditions for establishing shared connection for MBMS service are added to the existing SCCJP connection estaonsnment commons.

A new situation is added to the trigger condition of the existing SCCP connection establishment as follows: when RNC sends a MBMS Service Request to SGSN or SGSN sends a MBMS RAB Assignment Request message to RNC, if there is no lu connection used for this UE on lu interface, SCCP connection establishment procedure is initiated. The establishment procedures is applicable not ony to the case of the coexistence of both the shared and dedicated lu connection, but also to the case of the exsistence of only the shared lu connection.

• MBMS shared connection release: when data transmission finishes or no UE uses MBMS service between RNC and SGSN, both RNC and SGSN can initiate an lu connection release procedure.

(1) Signaling connection mode on lu interface

Messages used for MBMS on lu interface are oriented to a service such as MBMS Notification, MBMS Service Request/Deletion, MBMS RAB Establishment, etc, but not to a UE. Thus, it is proposed to use a shared lu connection for the same kind of

MBMS service on lu interface. Messages for the MBMS service can be sent via the shared lu connection. It is unnecessary to send messages for multiple UE repeatedly on lu interface at one time, thereby to reduce information traffic on lu interface and thus to avoid that RNC/SGSN receives multiple the same messages from the connections serving for different UEs at the same time, which can reduce the processing on the RNC and SGSN side. In addition, the user can also receive other services (e.g. voice) while receiving MBMS service, and the mobility of each user is independent. Messages used by the lu interface in the existing SRNS relocation flow are connection-oriented messages for the UE. In order to reduce modifications to the existing messages and to the existing SRNS relocation flow at the same time, which makes the system keep backward compatibility, it is necessary to establish a dedicated lu connection for the UE to control user plane resources of other service or user mobility if the user uses other services (e.g. voice) besides MBMS service or moves.

(2) SRNS relocation procedure

In order to accomplish the SRNS relocation procedure, this invention makes the following modifications and innovations: a) The Relocation Demand message is connection-oriented. If the user who has moved receives no services other -than MBMS -service and~the lu connection dedicated for UE hasn't been established. At this time, a temporary lu dedicated connection needs to be established. So a new situation is added to the trigger conditions of the existing SCCP connection establishment, which is described as follows:

The situations of SCCP connection establishment are as follows:

I) RNC initiates the establishment of SCCP signaling connection When RNC receives a non-MAC (Media Access Control) message from UE for the first time and there is no lu connection for this UE, RNC initiates the procedure of SCCP connection establishment. RNC sends a SCCP Connection Request message which includes a RANAP message in its data field to CN.

When RNC sends a Relocation Demand message to the source SGSN, if there is no lu connection used for this UE on lu interface, RNC initiates a SCCP connection establishment procedure. A RANAP message is included in the data field of the SCCP Connection Establishment Request message.

II) CN initiates the establishment of SCCP signaling connection

CN initiates the establishment of SCCP signaling connection when executing relocation. CN initiates the establishment of lu connection through sending a SCCP

Connection Request message which includes a RANAP message (optional) in its data field to RNC. b) In order to make the target RNC get known the situation of MBMS service used by the UE, an information element, i.e. MBMS Context List, is added to the existing Relocation Request message. MBMS Context mainly includes APN, IP Address and

Qos. c) After the target RNC receives a Relocation Request messge, if it finds that it hasn't received a certain MBMS service that is requested by UE at present, it sends a MBMS Service Request message to the new SGSN. The new SGSN can establish RAB for the corresponding MBMS service at the same time when it establishes RAB, and sends MBMS data to the new RNC. This is a new step added by this invention. d) Functions with 14 steps are added. When RNC receives a lu Release Command message, which indicates the completion of SRNS relocation procedure. If the UE that has moved is the last user of the source RNC, Both the shared connection and the user plane resources corresponding to MBMS service shall be released. Three schemes can be selected for this function. The following schemes are also applicable to the situation that the last user between RNC and SGSN quits the service or other situation that shared lu connection needs to be released.

Scheme 1) The function is initiated by RNC and implemented by the existing messages.

RNC sends a lu Release Request message to SGSN and requests SGSN to release corresponding lu connection and the user plane resources;

SGSN sends a lu Release Command message to the source RNC;

The source RNC releases corresponding resources and sends a lu Release Completion message to SGSN.

Scheme 2) The function is initiated by RNC and implemented by adding a new message.

RNC releases the user plane resources and the lu connection, and then sends a MBMS lu Release Indication message to the old SGSN. This new message is a connection-oriented message, which mainly includes the following several information elements:

> RABs Data Volume Report List It mainly includes two parts:

S RAB Identifier (RAB ID)

^•S RAB data volume report items, e.g. downlink data volume that haven't been successfully sent and data volume reference.

> RABs Released List Main contents include:

✓ RAB Identifier (RAB ID)

^■f The sequence number of downlink Protocol Data Unit (PDU) ^•/ The sequence number of uplink PDU Scheme 3) The function is initiated by SGSN and implemented by the existing messages.

If SGSN finds that the last user between it and RNC leaves or quits a certain MBMS service, it sends a lu Release Command to RNC. RNC releases the corresponding resources and sends a lu Release Completion message to SGSN.

(3) The establishment and release of lu interface shared signaling connection

In order to establish the shared lu connection, two methods can solve this problem.

Method 1 is described as follows:

A new situation is added to the trigger conditions of the existing SCCP connection establishment, which is described as follows:

The situation of the SCCP connection establishment is as follows:

I) RNC initiates the establishment of SCCP signaling connection When RNC receives a non-MAC (Media Access Control) message from UE for the first time and there is no lu connection for this UE, RNC initiates the procedure of SCCP connection establishment. RNC sends a SCCP Connection Request message which includes a RANAP message in its data field to CN.

When RNC sends a Relocation Demand message to the source SGSN, if there is no lu connection used for this UE on lu interface, RNC initiates a SCCP connection establishment procedure. A Relocation Demand message is included in the data field of a SCCP Connection Establishment Request message.

When RNC sends a MBMS Service Request message to SGSN, if there is no lu connection used for this UE on lu interface, RNC initiates a SCCP connection establishment procedure. A RANAP message is included in the data field of the SCCP

Connection Establishment Request message.

II) CN initiates the establishment of SCCP signaling connection

CN initiates the establishment of SCCP signaling connection when executing relocation. CN initiates the establishment of lu connection through sending a SCCP Connection Request message which includes a RANAP message (optional) in its data field to RNC,.

Method 2 is described as follows:

A new situation is added to the trigger condition of the existing SCCP connection establishment, which is described as follows: The situation of SCCP connection establishment is as follows:

III) RNC initiates the establishment of SCCP signaling connection

When RNC receives a non-MAC (Media Access Control) message from UE for the first time and there is no lu connection for this UE, RNC initiates the procedure of SCCP connection establishment. RNC sends a SCCP Connection Request message which includes a RANAP message in its data field to CN.

When RNC sends a Relocation Demand message to the source SGSN, if there is no lu connection used for this UE on lu interface, RNC initiates a SCCP connection establishment procedure. A Relocation Demand message is included in the data field of a SCCP Connection Establishment Request message.

IV) CN initiates the establishment of SCCP signaling connection

CN initiates the establishment of SCCP signaling connection when executing relocation. CN initiates the establishment of lu connection through sending a SCCP Connection Request message which includes a RANAP message (optional) in its data field to RNC.

When SGSN sends a MBMS RAB Assignment Request message to RNC, if there is no lu connection used for this UE on lu interface, SGSN initiates a SCCP connection establishment procedure. A RANAP message is included in the data field of the SCCP Connection Establishment Request message.

On the occasion of normal release, the release of SCCP connection is initiated by CN. When CN finds that a signaling connection isn't needed any more, the connection will be released and CN sends a SCCP RELEASED message. On any abnormal occasion, both CN and RNC can initiate a release procedure. The shared MBMS lu connection can be released in the following two situations:

> When SGSN won't receive MBMS data any more, a signaling connection and RAB release procedure can be initiated.

> When no UE uses MBMS service between RNC and SGSN, both RNC and SGSN can initiate a lu connection release procedure.

In the following, the flow of this invention will be described in detail by referring to attached figures.

(1) The signaling flow of MBMS shared lu connection establishment

Method 1 is described as follows: Figure 3 shows the signaling flow of MBMS shared lu connection establishment initiated by RNC. The detailed description for each operation step is as follows. 301 GGSN sends data to SGSN.

302 SGSN constructs a MBMS Notification message, which is connectionless-oriented, the same as the existing paging message, and belongs to the notification service of RANAP, and send it to RNC. 303 RNC sends a MBMS Notification message to UE to notify UE of incoming

MBMS service.

304 Establish a RRC connection for the UE in idle state.

305 UE sends a MBMS Service Request message to UTRAN.

306 RNC analyzes the on-going service. If there is no lu connection used for this service, RNC constructs a SCCP Connection Request message.

307 RNC sends a SCCP Connection Request message which includes a MBMS Service Request message in its data field to SGSN.

308 SGSN analyzes the SCCP Connection Request message and save the Iu^~ connection ID allocated by RNC; SGSN analyzes the service requested by RNC and constructs a MBMS RAB Assignment Request message and a SCCP Connection

Confirmation message.

309 SGSN sends a SCCP Connection Confirmation message to RNC. SGSN can directly send a MBMS RAB Assignment Request which is a RANAP message to RNC, or make the MBMS RAB Assignment Request message to be included in the data field of SCCP Connection Confirmation. MBMS RAB Assignment Request is a connection-oriented message.

310 RB is established for the UE that receives MBMS service.

311 RNC sends a MBMS RAB Assignment Response message to SGSN via the shared lu connection used for this service. 312 SGSN starts to send downlink data.

Method 2 is described as follows:

Figure 4 shows the signaling flow of the MBMS shared lu connection establishment initiated by SGSN. The detailed description for each operation step is as follows.

401 GGSN sends data to SGSN.

402 SGSN constructs a MBMS Notification message which is connectionless-oriented, the same as the existing paging message, and belongs to the notification service of RANAP to RNC. 403 RNC sends a MBMS Notification message to UE to notify UE of incoming MBMS service.

404 RNC analyzes the on-going service. If there is no lu connection used for this service, RNC constructs a SCCP Connection Request message. 405 SGSN sends a SCCP Connection Request message which includes a MBMS

RAB Assignment Request message in its data field to RNC.

406 RNC analyzes the SCCP Connection Request message, saves the lu connection ID allocated by SGSN, and constructs a MBMS RAB Assignment Response message and a SCCP Connection Confirmation message. 407 RNC sends a SCCP Connection Confirmation message to SGSN. RNC can directly send a MBMS RAB Assignment Response message which is a RANAP message to SGSN, or make the MBMS RAB Assignment Response message to be included in the data field of the SCCP Connection Confirmation message. MBMS RAB Assignment Responseis^~a connection-oriented message.- 408 Establish a RRC connection for the UE in idle state.

409 UE sends a MBMS Service Request message to UTRAN.

410 RB is established for UE that receives MBMS service.

411 SGSN starts to send downlink data.

(2) The signaling flow of MBMS dedicated lu connection establishment

Figure 5 describes the signaling flow for establishing dedicated lu connection when UE needs to receive other services (e.g. voice) when receiving MBMS service. The description for each operation step is as follows.

501 MS receives MBMS service. 502 when there is uplink data for non-MBMS service needed to be sent, and if a

RRC connection has been existed, MS can construct a Service Request message.

503 MS sends a Service Request message to SGSN and requests SGSN to preserve resources. The service type parameter of the Service Request message shall be set as data. When RNC forwards a Service Request message of UE which is a non-MAC message to SGSN, if there is no lu connection for this UE, RNC constructs a SCCP

Connection Request message, initiates a lu connection establishment procedure, and establishes a dedicated lu connection for the UE.

504 After receiving the SCCP Connection Request message, SGSN saves the lu connection ID allocated by RNC, allocates a identifier in SGSN for this connection, and sends a SCCP Connection Confirmation message to RNC.

505 If the service request is accepted, SGSN returns back a Service Acceptance message to MS.

506 SGSN sends a RAB Assignment Request message to RNC and requests to establish RAB.

507 RNC sends a RB Establishment message to MS, notifies MS to re-established RAB ID, and requests to establish radio resources.

508 MS and RNC return a RB Establishment Completion message and a RAB Assignment Response message respectively, which indicate the completion of the bearer establishment on user plane.

509 For each re-established RAB according to modified QoS. SGSN initiates a PDP Context Modification procedure and notifies MS and GGSN of a newly-negotiated QoS corresponding to the PDP context.

510 MS sends uplink data packets.

(4) SRNS relocation procedure Figure 6, Figure 7 and Figure 8 describe the SRNS relocation procedure when

MBMS service is added and the signaling connection mode on lu interface according to this invention is adopted. The difference among Figure 6, Figure 7 and Figure 8 exists in that the messages used for releasing the shared lu connection are different, the message corresponding to three schemes of the invention. Compared to the existing SRNS ^• relocation procedure, it solves: the problem of how to send a Relocation Demand message when user only receives MBMS service;

> If there is no corresponding service added in the target RNC, the corresponding message is added to the flow; If due to the moving of UE, there is no UE that is using MBMS service in the source RNC, the shared connection and user plane resources shall be released.

The detailed description for each step is as follows.

601 Source RNC decides to execute a SRNS relocation procedure; 602 and 603 : The source RNC constructs a Relocation Demand message, and if a lu connection dedicated for UE exists, and the message is directly sent to SGSN. If UE receives no services other than MBMS service and thus no lu connection dedicated for the UE is available, RNC constructs a SCCP Connection Request message which includes a Relocation Demand message in its data field. RNC sends the SCCP Connection Request message to CN.

604 The old SGSN forwards the Relocation Request message which includes MBMS Context to the new SGSN.

605 The new SGSN sends a Relocation Request message to the target RNC, and establishes a dedicated lu connection for UE during the sending of the Relocation Request message. 606 If the target RNC hasn't joined corresponding service, it sends a MBMS

Service Request message to SGSN.

607 Radio access bearer, which includes RABs of MBMS, is established between the target RNC and the new SGSN.

608 After the resources needed by RAB, which include resources on the user plane, are successfully allocated, the target RNC sends a Relocation Request Confirmation message to the new SGSN.

609 The new SGSN forwards the Relocation Response message to the old SGSN.

610 The old SGSN sends a Relocation Command message to the source RNC.

611 The source RNC starts to copy data and sends them to the target RNC through network protocol (hereinafter referred to as IP layer).

612 The source RNC sends a Relocation Delivery message to the target RNC. This procedure is used to transmit SRNS Context to the target RNC, and the role of SRNS is converted from the source RNC to the target RNC.

613 When the target RNC receives the trigger message for relocation execution, it sends a Relocation Detecting message to the new SGSN. After that, the target RNC starts to play the role of Serving Radio Network Controller (hereinafter referred to as SRNC).

614 UE exchanges information on the mobility such as the new SRNC Identifier, the indication of location area and uplink user data, etc. with the target RNC 615 If the SRNS relocation is a relocation occurring between different SGSNs, and when the new SGSN receives a Relocation Detecting message, it sends a Update Packet Data Protocol (hereinafter referred to as PDP) Context Request message to the corresponding GGSN. GGSN updates PDP context and returns back an Update PDP Context Response message. The new SGSN examines each MBMS service in MBMS Context for the UE. IF a certain service is joined by the first UE in SGSN, a GTP tunnel is established between SGSN and GGSN, and MBMS Context is created in GGSN.

616 The target SRNC initiates a Relocation completion procedure after receiving a UTRAN Mobility Information Confirmation message.

617 The new SGSN sends a Relocation completion message to notify the old SGSN of the completion of SRNS relocation procedure, and the old SGSN returns a

Relocation completion Confirmation message. 618 The lu connection between source RNC and source SGSN and the user resources are released. If UE is receiving no services other than MBMS service, it only needs to release the temporary lu connection dedicated for the UE.

619 If the UE is the last one that uses MBMS service in the source RNC, the shared connection and user plane resources for the MBMS service shall be released. RNC sends a lu Release Request message to SGSN and requests SGSN to release the corresponding lu connection and user plane resources; SGSN sends a lu Release Command message to the source RNC; The source RNC releases the corresponding resources and sends a lu Release completion message to SGSN. If the UE is the last user of multiple the services in the source RNC, the above release procedure will be performed for multiple times.

620 If the new Route Area Indication (hereinafter referred to as RAI) is different from the old, UE initiates a route location update procedure.

Each operation step except for 719 in Figure 7 is the same as that in Figure 5.

719 If the UE is the last one that uses MBMS service in the source RNC, the shared connection and user plane resources corresponding to the MBMS service shall be released. RNC releases the user plane resources and lu connection^ and then sends a MBMS lu Release Indication message to the old SGSN. This message includes information on released RAB. If the UE is the last user of multiple MBMS services in the source RNC, the above release procedure will be performed for multiple times.

Each operation step except for 819 in Figure 8 is the same as that in Figure 5.

819 If SGSN finds that the last UE that uses the MBMS service leaves or quits between it and RNC, it sends a lu Release Command to RNC.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the following claims.