CN1638493A - Method of distinguishing MBMS service request from other service request - Google Patents

Abstract

A method for distinguishing MBMS service requests from other service requests, comprising steps: RNC sends a message to UE, indicating that UE needs RRC connection; UE sends a message to SGSN, indicating whether it is MBMS service or dedicated service; SGSN according to different service types or message , sending different messages to the RNC. The present invention enables the SGSN to correctly distinguish the service requests caused by different services, so as to take different operations for different service requests. This differentiated operation enables the SGSN to send different signaling to the RNC, so that the RNC can accurately count the number of users, and Avoid wasting wireless resources.

Description

Method for Distinguishing MBMS Service Requests from Other Service Requests

technical field

The present invention relates to the third generation mobile communication system, in particular to a method for SGSN to distinguish MBMS service requests from other service requests.

Background technique

MBMS is a new service for which relevant standards are being formulated in the third generation mobile communication system partnership project for standardization. The MBMS service is a one-way point-to-multipoint service (that is, multimedia data broadcast from a single data source is sent to multiple users for reception through network transmission). The biggest feature of this kind of business is that it can effectively utilize wireless resources and network resources. MBMS services are mainly used in wireless communication network systems, such as wideband code division multiple access communication systems and global mobile communication systems. The transmission of business data in MBMS basically goes through several processes: data source transmission, intermediate network transmission, destination cell air transmission, and user reception. Fig. 3 is a logical network equipment diagram of a wireless communication system capable of providing MBMS services. In this figure, MBMS actually utilizes a General Packet Radio Service (hereinafter referred to as GPRS) network as a core transmission network. As shown in Figure 3, the broadcast and multicast service center (hereinafter referred to as BM-SC) is the data source for sending MBMS service data; the gateway GPRS support node (hereinafter referred to as GGSN) is used for the communication between the GRPS network and the external network (such as the Internet network) Connection; in the MBMS business, the gateway GPRS support node connects to BM-SC and sends MBMS data to a specific serving GPRS support node (hereinafter referred to as SGSN); the cell broadcast center is the data source of the cell broadcast, and in MBMS, the cell broadcast center Interconnected with BM-SC, so that the cell broadcast center can provide MBMS service announcement function; SGSN is used for UE access control and mobility management, and at the same time sends MBMS data from GGSN to a specific radio unit controller (hereinafter referred to as RNC) ); RNC is used to control a group of base stations and transmit multimedia data to a specific base station; the base station establishes an air physical channel for the MBMS service of a certain cell under the control of RNC; user terminal equipment (hereinafter referred to as UE) is Terminal equipment that receives MBMS data.

Figure 4 shows the entire process of the MBMS service from service announcement, user joining, service notification, radio bearer establishment to the final user leaving.

401 Subscription establishes the connection between the user and the service provider, and the authorized user can receive related MBMS services.

402 Service announcement notifies the user of the MBMS service to be provided. For example, the system wants to broadcast a football match in downtown Beijing at 7:00 pm.

403 Join means that the user joins a group, that is, the user tells the network that he or she is willing to receive this multicast service.

404 MBMS session start indicates establishment of network resources for MBMS data transmission.

405 The MBMS notification informs the user of the upcoming MBMS data transmission.

406 Data transmission indicates the process of transmitting MBMS service data to the user.

407 MBMS session end indicates that the network resources are released after the MBMS service data transmission is completed.

408 Leaving is corresponding to 403 Joining, indicating that the user wants to leave a group, that is, no longer wants to receive data of a certain service.

In the WCDMA system, when the system provides traditional packet services for user equipment, each UE is required to enter the PMM_CONNECTED connection state. This state means that there is a radio resource control RRC connection between the UE and the UTRAN, and there is a signaling connection between the UE and the SGSN. The signaling exchanged between the UE and the SGSN belongs to non-access stratum signaling, that is, NAS signaling. This signaling is transparent to the RNC, that is, the RNC does not care about the content of the message transmitted between the UE and the SGSN. When the UE wants to enter the PMM_CONNECTED state to establish a signaling connection, the necessary message sent by the UE to the SGSN is a service request (SERVICE REQEUST) or a routing area update request (ROUTING AREA UPDATE REQUEST). The Routing Area Update Request message is only required when the UE wants to update its routing area. The service request message is used by the UE in the PMM_IDLE idle state to establish a signaling connection with the SGSN, and tell the SGSN that the purpose of sending this message is to transmit uplink signaling messages, and the uplink data is also a response to paging initiated by the CN. If the service type in the service request is signaling, then after the signaling exchange is completed, the SGSN will release the signaling connection between the RNC and the SGSN; if the service type in the service request is data, then the SGSN will be in an active state The service establishes a radio access bearer RAB, thereby establishing a radio bearer RB for transmitting data for the service; if the service type in the service request is a paging response, the SGSN itself knows whether the paging response is for data transmission or signaling interaction, and thus Make correct processing, send relevant signaling to the user equipment or establish a radio access bearer. When MBMS service is provided in WCDMA, due to the large number of users using MBMS, if all users listening to MBMS service are in the PMM_CONNECTED state, the radio resources consumed on the air interface may be large and wasteful. Therefore, in the UTRAN, some user equipments are in the PMM_CONNECTED state, and the other part of the user equipments are in the PMM_IDLE state. The radio unit controller RNC only counts the number of users in the PMM_CONNECTED state contained in the cells under its control. The user equipment is in the PMM_CONNECTED state, which may be because the user equipment is receiving other proprietary services, or it may be in the connected mode only for MBMS user number statistics. When the RNC finds that the number of UEs receiving MBMS in a certain cell is lower than the transition threshold between point-to-point and point-to-multipoint, the RNC will re-count the number of users in the cell in case there are still users in the cell The user equipment in the idle state is receiving MBMS data. This process can refer to Figure 5. 501 indicates that the RNC receives a "session start indication" from the SGSN, indicating that the MBMS session starts, and the message usually includes service identifiers, service quality parameters and other service parameters related to the service. RNC counts the number of user equipments subscribing to the service in each cell. This process is necessary at the beginning of the session. During the session, if the number of users is lower than the critical value of point-to-point channel and point-to-multipoint channel conversion, then The RNC also starts the process of counting the number of users. The process continues from 502 to 512 . If the RNC finds that the number of users is lower than the critical value, the RNC sends an "MBMS notification" to the user equipment in the idle state in the cell or possibly including the user equipment in CELL_PCH and URA_PCH, and the message includes the notification reason (MBMS called call ), access probability, service identifier and other parameters. After receiving the message, the user equipment in the idle state first establishes an RRC connection with the RNC. 504-506 The UE establishes the RRC connection with the RNC, which is basically the same as the process described in the existing specification, and the only difference may be that the reasons for establishing the RRC connection are different. The cause may be "MBMS Called Call". The NAS layer of the UE sends a "service request" to the SGSN, and the service request message is included in the 507 RRC message "initial direct transfer" and the 508 Iu signaling "initial UE message" and delivered to the SGSN. After the SGSN receives the message, it sends 509 "MBMS UE Connection Request" to the RNC, and delivers all MBMS service identifiers subscribed by the UE to the RNC. RNC returns 510 "MBMS UE Connection Response" to SGSN. 511 RNC adds the UE identity to each service context of the cell where the UE is located. 512 The RNC counts the number of users of each service in each cell. So far, the process of counting the number of users by the RNC ends.

In the service request message sent by the UE to the SGSN, if the service type in the service request is data, the SGSN shall establish a radio access bearer for the activated PDP context, so as to allocate resources for data transmission on the Iu and Uu interfaces. During the process of counting users by MBMS, when the UE receives the "MBMS Notification" from the RNC, if the message indicates that it needs to count the number of users, the UE will enter the connection mode. The idle UE will send a service request message to the SGSN to enter the connection mode. If the service type in the service request is also data at this time, then according to the prior art, the SGSN needs to establish a radio access bearer for the activated PDP context. However, the service request is actually for the MBMS service, and the UE does not request the data transmission of the proprietary service. It can be seen that this will cause wrong operation of the SGSN. Therefore, in order to avoid the wrong operation of SGSN, we suggest adding a new service type in the service request: MBMS service. Or we can also use a new message "MBMS service notification" to report to the SGSN that the MBMS service subscribed by the user equipment needs to be known to the RNC, that is, the UE connection request in Fig. 1 .

In the WCDMA system, there is another case where the UE enters the PMM_CONNECTED state without sending a service request message, that is, when the UE wants to enter the routing area update. At this time, if we also need to let the SGSN notify the RNC UE of the MBMS service, then we can add a message unit: MBMS indication to the message "routing area update request". Or in this process, we can also use a new message "MBMS service notification" to request the SGSN to transmit the MBMS service subscribed by the user equipment to the SRNC of the user equipment.

Contents of the invention

The purpose of the present invention is to provide a method for distinguishing MBMS service requests from other service requests.

In order to achieve the above object, a method for distinguishing MBMS service requests and user-specific service requests comprises steps:

RNC sends a message to UE, indicating that UE needs RRC or PS domain connection

The UE sends a message to the SGSN, indicating whether it is an MBMS service or a dedicated service, or tells the SGSN to notify the RNC of the MBMS service that the UE has joined.

SGSN sends different messages to RNC according to different service types or messages

The invention provides a method for distinguishing MBMS service request and UE's special service request. Through this method, the SGSN can distinguish different services, thereby executing different processing procedures, avoiding the establishment of unnecessary user planes and causing waste of resources.

Description of drawings

Figure 1: The process of distinguishing MBMS services from other dedicated services

Figure 2: UE node action behavior

Figure 3: Schematic diagram of MBMS system structure

Figure 4: MBMS multicast service flow

Figure 5: Flow chart of the process of counting the number of users

Figure 6: SGSN node action behavior

Detailed ways

Next, correct examples of the present invention will be described in detail with reference to the attached drawings. In the following, only the parts necessary to understand this description are described, and other parts will be omitted for the sake of highlighting the key points. Figure 2 describes the service request process between MBMS user equipment and SGSN.

The present invention adds a service type for MBMS in the service request: MBMS service, so that it can distinguish whether the service request sent by the user equipment is only for MBMS service, or for dedicated service, or for both MBMS service and dedicated service. This method can also add a new message "MBMS service notification" transmitted between the user equipment and SGSN. This message informs the SGSN that the UE enters the PMM_CONNECTED state because of the needs of the MBMS service, and the SGSN will send the MBMS UE to the RNC. The connection message informs the RNC of all MBMS services subscribed by the UE. Or the present invention can add the "MBMS indication" information element in the routing area update, inform the SGSN to send the MBMS UE connection message to the RNC, and inform the RNC of all MBMS services subscribed by the UE. Through this distinction, the SGSN can correctly send related messages to the RNC, thereby avoiding service confusion and waste of user plane resources.

At 101 in FIG. 1 , the SGSN notifies the RNC when the MBMS session starts, and the message includes service identifiers, service quality parameters, and user plane information. If there may be a user equipment in PMM_IDLE in the cell under the control of the RNC, the message also includes a notification area, and the RNC will send the MBMS notification in the cell corresponding to the notification area.

At 102 in FIG. 1 above, the RNC counts the number of user equipments in connected mode in each cell of the service. If the number of users is greater than the critical value of point-to-point and point-to-multipoint channels, RNC sends "MBMS Notification" to all or some cells according to the instructions of SGSN, and indicates that the number of users does not need to be counted, and idle UEs do not need to enter connected mode. If the number of users in some cells is less than or equal to the critical value of point-to-point and point-to-multipoint channels, RNC sends "MBMS Notification" to all or some cells according to the instructions of SGSN, and indicates that the number of users needs to be counted, and some idle UEs Need to enter connect mode.

In step 103 in FIG. 1, the RNC sends "MBMS Notification" to the cells under its control according to the instruction of the SGSN. Set "RRC connection needs identification" to true or false according to whether the number of users needs to be counted. The MBMS notification also includes service identifier, notification reason, and access probability. The notification reason is "the called MBMS call". During the business process, the RNC will periodically broadcast the channel type in the cell. When an idle UE moves to the cell, if the channel type is point-to-point or the cell does not provide radio bearers for the service at all, the RRC of the UE will report the information to the upper layers.

In step 104 in FIG. 1 above, the RRC layer of the UE receives the "MBMS Notification" message, submits the reason for the notification and the service identifier to the upper layer, and notifies the upper layer of the arrival of MBMS service data. If the message indicates that an RRC connection is required, that is, the "RRC connection needs flag" is true, the RRC layer will notify the upper layer if the UE is allowed to enter the connected state after performing relevant access probability calculations, and the signaling connection indication is true. This process can be realized through RRC and high-level primitives. This primitive notifies the high-level MBMS service identifier, notification reason and signaling connection indication. If the UE learns at 103 that the channel type in the cell is point-to-point, or the cell does not provide a radio bearer for the service at all, then the RRC of the UE will report to the high layer. The primitives of the report include the service identifier, and the signaling connection indication is true.

In step 105 in FIG. 1, the upper layer processes the MBMS call according to the information transmitted by the RRC. The upper layer associates the MBMS service identifier with the corresponding MBMS context. If the signaling connection indicates that an RRC connection is required, the higher layer informs the RRC layer through a primitive, establishes an RRC connection, and includes the "service request" message between the upper and lower layer primitives and passes it to RRC. Otherwise, higher layers do not need to instruct RRC to perform any operations.

From 106 to 108 in the above-mentioned FIG. 1, RRC establishes an RRC connection according to the instructions of the high layer. The reason for establishing the RRC connection is: the MBMS called party. Other operations of the RNC are the same as specified in the existing specifications.

In steps 109 and 110 in FIG. 1 above, after the RRC connection is established, the UE transmits the message "service request" from the upper layer to the SGSN.

The service type in the service request in 109 should indicate "MBMS service" in this case. This process is completed in two steps: 109 UE submits the message to RNC through RRC signaling "initial direct transmission"; 110 RNC transmits the message to SGSN through Iu signaling "initial UE message". The process of 109 may also occur when the user equipment is updating the routing area. In this case, the message sent from the user equipment to the SGSN is "routing area update request". This process is completed in two steps: 109 UE submits the message to RNC through RRC signaling "initial direct transmission"; 110 RNC transmits the message to SGSN through Iu signaling "initial UE message". If the user equipment has obtained the information about the MBMS service in the cell from the MCCH before performing the routing area update, and the new cell has not provided the MBMS service, then the user can include "MBMS indication" in the routing area update request; or if not The "MBMS indication" is not included in the routing area update request, and after the user equipment establishes a signaling connection, it can send a new message "MBMS service notification" to the SGSN.

In 109a in the above-mentioned figure 1, after the UE establishes a signaling connection with the SGSN (through the service request process), it sends a "MBMS service notification" to the SGSN to notify the SGSN that the UE has joined some MBMS services, and the SGSN is required to send the MBMS service notification to the SGSN. This information informs the SRNC of the UE. The signaling connection between UE and SGSN can be established according to conventional methods. I won't go into details here. In 109a, the UE submits the message to the RNC through the RRC signaling "uplink direct transmission"; 110 the RNC transmits the message to the SGSN through the Iu signaling "direct transmission" message. 109a in FIG. 1 above can also be used to establish a signaling connection between the UE and the SGSN, but the establishment of the signaling connection is caused by the start of the MBMS service. That is to say, this message can completely replace the "service request" message of 109 . The UE sends the "MBMS Service Notification" message to the SGSN, and the message is sent to the SGSN through the RRC signaling "Initial Direct Transfer" and the Iu signaling "Initial UE Message".

111 in the above-mentioned figure 1, after receiving 110, the SGSN finds that the service type of the service request is "MBMS service" or receives the message "MBMS service notification", or receives the message "routing area update request" containing "MBMS indication ", the SGSN checks the MBMS services that the UE has joined saved in the UE context. SGSN sends "MBMS UE connection request" message to RNC, and notifies RNC of the MBMS service identifier that this UE joins. The MBMS service identifier can be an IP multicast address and APN, or a temporary mobile group identifier TMGI.

112 in above-mentioned Fig. 1, RNC confirms to SGSN to receive " MBMS UE connection request " message, and returns " MBMS UE connection response " message.

In step 113 in FIG. 1, the RNC adds the UE identity to the context of the corresponding cell and service.

This process from 102 to 114 does not necessarily only occur at the beginning of the session. During the session, if the RNC finds that the number of users is lower than the critical value for point-to-point and point-to-multipoint channel switching, the RNC can initiate the process of counting the number of users. At this time, the "MBMS notification" in 103 contains the service identifier, and the RRC connection needs to be indicated (set to be true). And set the service type in the service request as "MBMS service", or decide to send a new message "MBMS service notification".

If the UE moves to a new cell, the UE first needs to read the system information to obtain the routing area to which the current cell belongs, and the UE can also obtain information about the MBMS control channel from the system information. Next, the UE receives the MBMS control signaling transmitted on the channel according to the channel configuration. If the UE finds that the current cell's support type for the service is point-to-point or no bearer, then the UE also needs to perform the procedures from 105 to 109 . Next, the UE can send a "routing area update request message", which contains "MBMS indication" or after establishing a signaling connection, send a "MBMS service notification" message, or the user equipment sends a "service request" message, which contains The service type of the service is set to "MBMS service". At the same time, if the routing area where the UE is located changes, and the upper layers of the UE want to send signaling to perform functions such as routing area update, the UE can send a "routing area update request" message, which contains "MBMS indication" or After the signaling is connected, the "MBMS service notification" message is sent. Next, the UE also needs to perform the procedures from 105 to 109 . Of course, if only the routing area of the UE has changed, and the service channel type supported by the current cell is point-to-multipoint, then the UE does not need to include "MBMS indication" or send "MBMS service information" in the "routing area update request" message. Notification" message.

And if the user equipment finds that the routing area has changed when moving the new cell, but at this time the user equipment has not learned any information about the MBMS service in the new cell, then it can only send the "routing area update request" message to the SGSN . During the process of updating the routing area, the user equipment can read the configuration information about the MCCH in the system information. Then read information such as the channel type of the MBMS service according to the configuration information of the MCCH. If the channel type of the MBMS service is point-to-point, then the user equipment sends a "MBMS service notification" message to the SGSN, requesting the SGSN to send the list of MBMS services subscribed by the user equipment to the RNC.

In step 115 in FIG. 1 above, the high layer of the UE decides to receive the dedicated service in the packet domain, and the UE is in an idle state at this time. The higher layer notifies the RRC layer to establish the RRC connection, and sends the NAS message "Service Request" to the SGSN.

From 116 to 118 in FIG. 1 above, the RRC establishes the RRC connection according to the instructions of the high layer, and the reason for establishing the RRC connection is the existing reason value. Other operations of the RNC are the same as specified in the existing specifications.

In 119 and 120 in FIG. 1 above, after the RRC connection is established, the UE transmits the message "service request" from the upper layer to the SGSN. The service type in this service request is set to "data". This process is completed through two steps: 119 UE submits the message to RNC through RRC signaling "initial direct transmission"; 120 RNC transmits the message to SGSN through Iu signaling "initial UE message".

Or in 119a and 120 in FIG. 1, the UE may send the message "MBMS Service Notification" to the SGSN. This process is completed in two steps: 119a UE submits the message to RNC through RRC signaling "uplink direct transmission"; 120 RNC transmits the message to SGSN through Iu signaling "direct transmission". In step 121 in the above-mentioned Figure 1, the SGSN finds that the service type requested by the UE is data, so it checks the MM context of the UE to see which services have PDPs that are activated. SGSN establishes radio access bearers for these services. The SGSN sends a "RAB Assignment Request" message to the RNC, which contains not only parameters such as service quality parameters supporting the service, but also contains a list of MBMS service identifiers that the UE has joined if the SGSN finds that the UE has also joined some MBMS services .

At 122 in the above Figure 1, the RNC returns a "RAB assignment response" to the SGSN, establishes its Iu user plane, and provides a data transmission channel for the service.

In 121a in FIG. 1 above, after receiving 120, the SGSN finds that the service type of the service request is "MBMS service" or receives the message "MBMS service notification", and the SGSN checks the MBMS service that the UE has joined saved in the UE context. SGSN sends "MBMS UE connection request" message to RNC, and notifies RNC of the MBMS service identifier that this UE joins. The MBMS service identifier can be an IP multicast address and APN, or a temporary mobile group identifier TMGI.

122a in above-mentioned Fig. 1, RNC confirms to SGSN to receive " MBMS UE connection request " message, and returns " MBMS UE connection response " message.

In step 123 in FIG. 1, the RNC adds the UE identity to the context of the corresponding cell and service.

In step 124 in FIG. 1, the RNC counts the number of users of each service in the cell, so as to determine whether the channel type is point-to-point or point-to-multipoint. The process from step 115 to step 124 can occur before the session starts, and can also occur during the session.

There is another situation that is not described in Figure 1, that is, when the user equipment is in the RRC connection state and the PMM_IDLE state, when the session starts, the SRNC will send a message to the UE to let the UE enter the PMM_CONNECTED state. The UE enters the PMM_CONNECTED state for MBMS, so we can also use the three methods described in Figure 1: the service type in the service request is "MBMS service", or a new message "MBMS service notification" or in the routing area Add "MBMS indication" in the update request message. After receiving the message, the SGSN also sends a UE connection message to the UE. This process is basically the same as 115-124 in FIG. 1, the only difference is that the RRC connection establishment process 116-118 is not required.

The listed embodiments of the present invention are only to illustrate some specific ways of implementing the present invention, but this is not all the generalized embodiments of the present invention. Any scenario sent by the UE to the CN to allow the CN to perform the UE connection procedure falls within the scope of the present invention.

Example

1) Node processing flow of UE

FIG. 2 describes the node processing flow of the UE. Stage 201 indicates that the UE receives a message from the RNC side. In stage 202, it is judged whether the message received by UE is "MBMS Notification", and if so, it turns to 203, otherwise, it turns to 201. In stage 203, the RRC layer of UE submits the service identification and notification reason obtained from the "MBMS Notification" message to the upper layer. If the "RRC connection needs flag" in the message is true, then the signaling connection flag is true. Otherwise, the signaling connection flag is No. The RRC layer of the UE tells the upper layer whether to establish a signaling connection through the signaling connection indication in the primitive. If the RRC of the UE knows that the channel type of the target cell is point-to-point or the target cell does not provide a radio bearer for the MBMS service that the UE is receiving at all, then the RRC of the UE tells the upper layer that a signaling connection needs to be established through a primitive, that is, a signaling connection indication is true. In stage 204, the high layer judges whether a signaling connection is needed. If necessary, it turns to 205, otherwise it turns to 207. In stage 205, the high layer instructs the RRC layer to establish an RRC connection, and then turns to 206. In stage 206, UE sends a message "service request" to SGSN, the The service type in the message is "MBMS service", or the UE sends a "MBMS service notification" message to the SGSN, or the UE sends a "routing area update" message to the SGSN, and the message carries "MBMS indication". In stage 207, the high level does not perform any further operations. In stage 208, judge whether the received message is "MBMS channel type indication", if so, turn to 209, otherwise turn to 210. In stage 209, judge whether the channel type of the target cell is point-to-point, if so, turn to 203, otherwise turn to 201 . At stage 210, if the target cell does not provide a radio bearer for the MBMS service being received by the UE at all, then go to step 203.

2) Node processing flow of SGSN

Figure 6 is the node action behavior of SGSN.

Stage 601 indicates that the SGSN receives a message from the UE side.

In stage 602, judge whether the message received by the SGSN is a "service request", if so, turn to 603, otherwise turn to 601.

In stage 603, it is judged whether the service type is "MBMS service", if so, turn to 604, otherwise turn to 605.

At stage 604, the SGSN checks its UE context, and sends a "MBMS UE connection request" message to the RNC, which contains the MBMS service ID that the UE has joined.

In stage 605, the SGSN checks the UE context, and establishes a RAB for the PDP already in the active state. The SGSN sends a "RAB Assignment Request" message to the RNC, which carries the ID of the MBMS service that the UE has joined in addition to the parameters for establishing the user plane and the quality of the service.

In stage 606, it is judged whether the message received by the SGSN is a "routing area update request" message, if so, turn to 607, otherwise turn to 608.

In stage 607, it is judged whether the received message contains "MBMS indication", if so, turn to 604, otherwise turn to 601.

In stage 608, it is judged whether the received message is "MBMS service notification", if so, turn to 604, otherwise turn to 601.

Claims (7)

1, a kind of method of distinguishing MBMS service request and the request of user's dedicated service, this method may further comprise the steps:

RNC sends message to UE, and indicating UE needs RRC to connect;

UE sends out message and gives SGSN, indicates MBMS business or dedicated service;

SGSN sends different message according to different types of service or message to RNC.

2, method according to claim 1 is characterized in that: the type of service that UE issues in " service request " of SGSN is " a MBMS business ".

3, method according to claim 1 is characterized in that comprising: the rrc layer of UE sends indication to its high-rise NAS layer.

4, method according to claim 3 is characterized in that: indication notifying MBMS service sign, and the notice reason, signaling connects indication.

5, method according to claim 1 is characterized in that: UE sends to " the routing region updating message " of SGSN, wherein comprises the service apprized RNC of MBMS that parameter indication SGSN should add this UE.

6, method according to claim 1 is characterized in that: UE is a new information to the message that SGSN sends, and this message indication SGSN will inform the MBMS service identification that this UE of RNC adds.

7. method according to claim 6 is characterized in that: described new information is used for setting up subscriber equipment and is connected with signaling between the SGSN.

Images