CN100464530C - Method for announcing group-playing dialogue begin of multimedia broadcasting - Google Patents

Abstract

A process for notifying start of multimedia televise multicasting session comprises the following steps: a) according to the different types of RNC, parameters in messages sent to RNC by SGSN are different; b) RNC returns a message back to SGSN; or also comprise the steps: a) according to the different types of RNC, SGSN sends different messages to RNC; b) RNC returns a message back to SGSN. By increasing indication bit to messages, the present invention simplifies processing burden at RNC side, shortens the time for building Iu user plane caused by UE movement, and then ensures the minimization of data loss of users.

Description

The method that the session of notice multimedia broadcasting and multicast begins

Technical field

The present invention relates to 3-G (Generation Three mobile communication system), particularly the method that begins in the session of Serving GPRS Support Node notice radio-cell controller.

Background technology

MBMS is formulating relevant criterion for it to carry out a standardized new business in the 3-G (Generation Three mobile communication system) partner program.The MBMS business is a kind of unidirectional point to the business of multipoint system (promptly broadcasting out multi-medium data from single data source is sent to a plurality of users through Network Transmission and receives).The maximum characteristics of this business are that it can effectively utilize Radio Resource and Internet resources.The MBMS business is mainly used in the wireless communication network system, as Wideband Code Division Multiple Access (WCDMA) communication system, and global system for mobile communications etc.The transmission of business datum will be passed through basically among the MBMS: transmission in data source transmission, go-between transmission, the purpose cell null, user receive such plurality of processes.Fig. 3 is a wireless communication system logical network equipment drawing that the MBMS business can be provided, and in fact MBMS has utilized general grouped wireless data service (hereinafter to be referred as GPRS) network as core transport network in the figure.As shown in Figure 3, broadcasting and multicast service center (hereinafter to be referred as BM-SC) are the data sources that sends the MBMS business datum; Gateway GPRS Support Node (hereinafter to be referred as GGSN) is used for being connected of GRPS network and external network (as the INTERNET network); Gateway GPRS Support Node connects BM-SC and the MBMS data is sent to specific Serving GPRS Support Node (hereinafter to be referred as SGSN) in the MBMS business; CBC is the data source of Cell Broadcast CB, by with CBC and BM-SC interconnection, makes CBC that MBMS can be provided professional declaration function in MBMS; SGSN is used for that UE is carried out access control and mobile management and simultaneously the MBMS data of coming from GGSN is sent to specific radio-cell controller (hereinafter to be referred as RNC); RNC is used for controlling one group of base station and multi-medium data is sent to specific base stations; Aerial physical channel is set up for the MBMS business of certain sub-district in the base station under the control of RNC; Subscriber terminal equipment (hereinafter to be referred as UE) is the terminal equipment that receives the MBMS data.

Provided the MBMS business among Fig. 4 and be established to all processes that end user is left from business declaration, user's adding, service announcements, radio bearer.

401 subscribe to the contact of setting up between user and the service provider, and authorized user can receive relevant MBMS service.

The MBMS business that 402 professional declarations notify the user to provide.For example, system in the afternoon 7:00 relay a football match in areas of Beijing.

403 add the expression users adds a group, promptly the user tell network he or she be ready to receive this multicast service.

The 404MBMS session begins to represent that being established as the MBMS transfer of data sets up Internet resources.

The 405MBMS notice is informed the MBMS transfer of data that the user will carry out at once.

406 data transfer representation MBMS business data transmission are to user's process.

The 407MBMS conversation end is represented after the MBMS business data transmission is finished, releasing network resources.

408 leave and add correspondingly with 403, and the expression user will leave a group, does not promptly rethink to receive certain professional data.

In existing MBMS system, when the MBMS session began, SGSN will notify the RNC session to begin, and the professional relevant QoS parameter of this MBMS, the multicast service zone.What Fig. 2 described is how SGSN notifies the RNC session to begin.Three types RNC is arranged below the SGSN in the prior art: the one, be in the RNC of last known Routing Area (RA), the sub-district under this RNC control range comprises the subscriber equipment that is in idle condition (PMM_IDLE); The 2nd, service radio-cell controller (SRNC), the sub-district under the RNC control range comprises the subscriber equipment that is in connection status (PMM_CONNECTED), and this RNC is the SRNC of UE; The 3rd, floating radio-cell controller (DRNC), the sub-district under the RNC control range comprises the subscriber equipment that is in connection status (PMM_CONNECTED), but this RNC is not the SRNC of UE, but the DRNC of UE.For the subscriber equipment that is in the PMM_IDLE state, because SGSN knows the residing Routing Area of subscriber equipment (RA), SGSN is according to the mapping relations between Routing Area and the RNC, thereby learn the residing RNC of these UE, when session begins, send session to these RNC and begin Indication message, as 205 among Fig. 2 (we suppose wherein just include PMM_IDLE UE among the RNC#2), this message comprises service identification, the QoS parameter of this business correspondence, multicast service zone.For the subscriber equipment that is in the PMM_CONNECTED state, because mobility of user equipment, SGSN only knows the SRNC of this UE, and does not know the DRNC of UE.That is to say that DRNC shields SGSN.Therefore SGSN can only begin Indication message to the residing SRNC transmission of this UE session, and as 205 among Fig. 2 (we suppose that RNC#2 is the SRNC of certain user's equipment), this message comprises service identification, the QoS parameter of this business correspondence, multicast service zone.If some UE moves to the sub-district that DRNC controls, just belong to the DRNC of some UE as the RNC#1 among Fig. 2.Because SGSN does not know the existence of this class RNC, therefore will cause SGSN not send session and begin indication to this RNC.There are two kinds of methods to have this class RNC in the prior art so that SGSN knows, thereby notify these RNC sessions to begin: first kind as 201 among Fig. 2, after first UE that activates the MBMS business moves to this RNC, this RNC knows the MBMS service identification that this UE activates, if RNC does not also set up for this professional context, then set up.RNC sends " MBMS RNC register requirement " message to SGSN then.After SGSN receives this message, in its bearer context, preserve the sign of this RNC, so that session can be notified this RNC when beginning.After session began, SGSN checked the RNC sign that comprises in its context, sends 207 to this RNC, notifies this RNC session to begin, and comprises service identification in this message, the QoS parameter of this business correspondence, multicast service zone; Second kind as 206 among Fig. 2, and after session began, the SRNC of UE can receive earlier from SGSN and send " the MBMS session begins indication " message.SRNC is that " MBMS adheres to request information, informs the service identification that these UE of DRNC have added and session has begun in RNC#1 transmission 203 to the residing DRNC of UE.DRNC returns " MBMS adheres to response " message to SRNC, if DRNC does not also set up for this professional context, then sets up.DRNC sends " MBMS RNC register requirement " message to SGSN then.After SGSN receives this message, to in its bearer context, preserve the sign of this RNC, because in this case, session begins, therefore SGSN sends 207 to RNC, notifies this RNC session to begin, and comprises service identification in this message, the QoS parameter of this business correspondence, the multicast service zone.

From the description of Fig. 2 we as can be seen, no matter be for any among three kinds of RNC, it all is that the same, entrained parameter also is the same that the session that SGSN sends to RNC begins Indication message, that is to say that SGSN does not distinguish these three kinds of RNC's.For the RNC that is in last known Routing Area, the position of UE is concerning SGSN, and on the Routing Area rank, a RA can comprise one or more RNC, and a RNC also can comprise a plurality of RA.A RA is corresponding to a plurality of sub-districts.In session at first, guarantee that all subscriber equipmenies know that all session begins, so that knowing, UE monitors multicast control channel (MCCH), particularly for the subscriber equipment that is in the PMM_IDLE state, has only the residing Routing Area of SGSN notice these UE of RNC, just can make RNC send the MBMS notice to the sub-district that RA comprises exactly, make UE know that session begins.This shows that " session the begins indication " message for sending to this class RNC wherein also will comprise the residing positional information of UE.For SRNC and DRNC, because the position of the UE that is controlled is visible, therefore can which sub-district to send the MBMS notice to by the SRNC decision on cell level, SGSN does not need to indicate the residing position of this UE.This shows that for this two class RNC, SGSN does not need to comprise the information of UE present position to " session begins indication " of its transmission.Prior art is not distinguished for these three kinds of different RNC, and this perhaps sends the MBMS notice to the zone at whole RNC place after just meaning that RNC receives " session begins indication " message, does not perhaps send.This unified processing scheme or can increase signaling bear on the air interface perhaps can cause certain customers to can not receive the MBMS notice, therefore is necessary prior art is improved.In addition, if some RNC among RA has subscriber equipment to exist, these subscriber equipmenies are very big from the possibility that these RNC move to other RNC that are in same RA so, therefore, we also can be kept at the session parameter in the business contexts of these RNC, user plane between RNC and the SGSN also can be set up, and uses after waiting until.

In addition, if include the MBMS context of at least one UE among SGSN, because the possibility that UE moves in the SGSN control range is very big, so session begins to be sent to all RNC that SGSN controls.

Because SGSN preserves mobile management (MM) context of each subscriber equipment, so SGSN knows that what UE are arranged in its control range.If SGSN can inform the RNC number of users in advance, if number of users is fewer, RNC just can directly determine point-to-point still to put the multidrop channel type so.

Summary of the invention

The present invention be intended to solve different RNC learn receive that session begins after, the difference of the information content that comprises according to different message or same message, and carry out different operations.

For achieving the above object, a kind of method of notifying the multimedia broadcasting and multicast session to begin comprises step:

Service general grouping service wireless GPRS Support Node SGSN sends " session begins indication " message and gives radio network controller (RNC), and this message comprises " notification area ";

Radio network controller (RNC) sends the MBMS notice in the sub-district that described " notification area " comprises;

Radio network controller (RNC) returns " session begins to confirm " message to SGSN.

The present invention is by increasing indication information in message, thereby simplified the processing burden of RNC side, shortened again because UE moves the time that the Iu user plane that causes is set up, thus the minimizing of assurance user data loss.

Description of drawings

The flow chart that Fig. 1 is to use the session of same message informing different RNCs to begin;

Fig. 2 is the flow chart that notice RNC session begins in the prior art;

Fig. 3 is a MBMS system configuration schematic diagram;

Fig. 4 is a MBMS multicast service flow process;

The flow chart that Fig. 5 is to use the session of different messages notice different RNCs to begin;

Fig. 6 is the topological structure that uses in the example;

The node action of RNC when Fig. 7 is to use identical message;

The node action of SGSN when Fig. 8 is to use identical message;

The node action of RNC when Fig. 9 is to use different messages;

The node action of SGSN when Figure 10 is to use different messages.

Embodiment

Below, the example that present invention will be described in detail with reference to the accompanying. following describes understanding the necessary part of this explanation, can omit to some extent other part in order to give top priority to what is the most important.

The same message that is to use that Fig. 1 describes is carried out the flow process that session begins to notify to different RNCs.

The plot of describing among Fig. 1 is to carry out according to the correlation between each RNC among Fig. 6, according to shown in Figure 6, comprises RNC1 and RNC6 among the RA1, comprises RNC4 among the RA2, comprises RNC5 among the RA3, comprises RNC2 and RNC3 among the RA4.

Before session began, RNC4 was the SRNC of certain user's equipment, and RNC5 is the DRNC of certain user's equipment, and RNC1 comprises the subscriber equipment that activation MBMS business is in the PMM_IDLE state.According to prior art, DRNC may register to SGSN before session begins.

Among above-mentioned Fig. 1 101, DRNC sends " MBMS RNC register requirement " message to SGSN, comprises the service identification tabulation in the message, after SGSN receives this message, this RNC can be joined in one of its bearer context middle and lower reaches node listing.Bearer context about SGSN sees also prior art.Wherein the formation of downstream node tabulation describes in detail later on.

Among above-mentioned Fig. 1 102, SGSN receive " the MBMS session begins " message that GGSN sends, with the service identification that comprises in this message, and QoS parameter, the multicast service zone is included in this professional bearer context.SGSN sends message to the RNC that its bearer context middle and lower reaches node listing comprises, and this MBMS service conversation of notice RNC begins.

Among above-mentioned Fig. 1 103, SGSN sends " session begins indication " message to RNC4, comprising service identification, QoS parameter, multicast service zone, parameters such as Tunnel Identifier.Because RNC4 is the SRNC of some UE, provide professional possibility so oriented these UE of this RNC provide with point-to-point or point-to-multipoint mode, so can also comprise the Tunnel Identifier between SGSN side RNC and the SGSN in this message, be used for transmitting data.

Among above-mentioned Fig. 1 104, SRNC returns " session begins to confirm " message to SGSN, comprises " using indication in the future " in this message, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.If this SRNC will provide point-to-multipoint channel or will be to providing point-to-point channel with its subscriber equipment that has RRC to be connected to its control sub-district down, " use in the future and indicate " so can be set to deny, show that SGSN receives this message after, just can transmit data.Otherwise, if this SRNC neither needs the sub-district under its control that the point-to-multipoint channel is provided, do not need to providing point-to-point channel with its subscriber equipment that has RRC to be connected yet, " using indication in the future " so is set to very, after showing that SGSN receives this message, just do not need to transmit data, but will preserve at this professional user-plane tunnel sign, the transfer of data of this user plane can be recovered afterwards again.

Among above-mentioned Fig. 1 105, SGSN sends " session begins indication " message to RNC1, comprising service identification, QoS parameter, multicast service zone, parameters such as notification area and Tunnel Identifier.After RNC receives this message, notification area is become cell ID, the sub-district under its control sends " MBMS notice " message, and the UE that notice is in the PMM_IDLE state should business begin.RNC can also comprise number of users in this message, so that can directly determine to use point-to-point channel under the fewer situation of number of users.RNC judges whether the sub-district under its control comprises subscriber equipment, if comprise, then showing needs user plane to carry out transfer of data, and " using indication in the future " is set to not, otherwise do not need user plane, and " using indication in the future " is set to true.Yet no matter in the sub-district of its control whether subscriber equipment is arranged, user plane can be set up at this moment, RNC returns 106 " session begins to confirm " message to SGSN, comprises the parameter of using indication and RNC side to set up about user plane in the future in this message, as Tunnel Identifier.

Among above-mentioned Fig. 1 107, " MBMS adheres to request information to SRNC, comprises service identification in the message, UE identification list, cell list, URA tabulation to the DRNC transmission.DRNC just can know among which sub-district of its control or the URA and comprises the subscriber equipment that is in the PMM_CONNECTED state like this.If DRNC does not receive " session begins indication " message from SGSN, then may this RNC neither any SRNC that is in the subscriber equipment of connection mode, RA under it does not comprise the subscriber equipment that activates this MBMS business of any PMM_IDLE of being in yet, and other RNC (if any) of RA did not register to SGSN yet under it.DRNC just to the SGSN registration, sends 109 " MBMSRNC register requirement " message so, comprises in this message " service identification ".

Among above-mentioned Fig. 1 110, SGSN will join this RNC in this professional MBMS bearer context and go, and sends " session begins indication " message to RNC5 then, comprising service identification, QoS parameter, multicast service zone, parameters such as Tunnel Identifier.If this DRNC will provide the point-to-multipoint channel to its control sub-district down, " use indication in the future " so and can be set to and deny, show that SGSN receives this message after, just can transmit data.Otherwise, if this DRNC does not need to provide the point-to-multipoint channel to its control sub-district down, " use indication in the future " so and be set to true, show that SGSN receives this message after, just do not need to transmit data, identify but will preserve at this professional user-plane tunnel.

Among above-mentioned Fig. 1 111, DRNC returns " session begins to confirm " message to SGSN, comprises in this message and uses indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.

Among above-mentioned Fig. 1 112 supposes that a UE is that sub-district under the RNC4 moves to DRNC when being the sub-district of RNC2 control from SRNC, and SRNC sends to DRNC that " MBMS adheres to request information, comprises service identification in the message, customer equipment identification and cell ID.

Among above-mentioned Fig. 1 113, DRNC returns " MBMS adheres to response message " to SRNC.

Among above-mentioned Fig. 1 114 represents that first activates the UE of this MBMS business under this RNC2, and this moment, RNC2 will set up the MBMS business contexts so, sends 115 " MBMS RNC register requirement " message to SGSN then, comprises in this message " service identification ".

Among above-mentioned Fig. 1 116, SGSN will join this RNC in this professional MBMS bearer context middle and lower reaches node listing, send " session begins indication " message to RNC2 then, comprising service identification, QoS parameter, multicast service zone, parameters such as Tunnel Identifier.Owing to be first UE, DRNC does not need to provide the point-to-multipoint channel to its control sub-district down, " uses indication in the future " so and is set to very, show that SGSN receives this message after, just do not need to transmit data, but will preserve at this professional user-plane tunnel sign.

Among above-mentioned Fig. 1 117, DRNC returns " session begins to confirm " message to SGSN, comprises " using indication in the future " in this message, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.Because RNC2 and RNC3 are in RA4 together, therefore also to send " session begins indication " message to RNC3, but owing to do not comprise any UE among this RNC, service parameter is sent to this RNC just in order better to support mobility of user equipment, therefore in 118 message, increase an information unit: the notice indication.This information unit represents that RNC needn't add up the process of number of users at its affiliated area.This RNC does not need to use the user to transmit data yet, therefore is set to true with " use indication in the future ".When system decision when being in same SGSN control all RNC transmission sessions down and beginning, the processing mode of RNC3 be the same now.

Among above-mentioned Fig. 1 119, RNC returns " session begins to confirm " message to SGSN, comprises in this message and uses indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.

Move to the sub-district of RNC2 control as subscriber equipment new user who adds this business or be in idle condition in the sub-district that RNC2 controlled, SGSN sends 120 " MBMS UE connection requests " to RNC2, comprises the MBMS service identification tabulation that UE adds in this message.RNC2 sends 121 " MBMS UE connection response " to SGSN.

Among above-mentioned Fig. 1 122, RNC2 judge whether the ordered business of this UE does not set up context, if then set up.SGSN joins this RNC in this professional MBMS bearer context and goes, and sends 123 " session begins indication " message to RNC2 then, comprising service identification, and QoS parameter, multicast service zone, parameters such as Tunnel Identifier.Owing to be first UE, RNC2 need provide point-to-point channel to its control sub-district down, " uses indication in the future " so and is set to not, show that SGSN receives this message after, just need transmit data.

Among above-mentioned Fig. 1 124, DRNC returns " session begins to confirm " message to SGSN, comprises in this message and uses indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.Because RNC2 and RNC3 are in RA4 together, therefore also to send 125 " session begins indication " message to RNC3, but owing to do not comprise any UE among this RNC, service parameter is sent to this RNC just in order better to support mobility of user equipment, therefore in 125 message, increase an information unit: the notice indication.This information unit represents that RNC need add up the process of number of users at its affiliated area, if this information unit is included in the message, does not then need to add up number of users, otherwise the statistics number of users.This RNC does not need to transmit data for the user yet, therefore " uses indication in the future " and is set to very.When system decision when being in same SGSN control all RNC transmission sessions down and beginning, the processing mode of RNC3 be the same now.

Among above-mentioned Fig. 1 126, RNC returns " session begins to confirm " message to SGSN, comprises in this message and uses indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.

If have other RNC and RNC4 or RNC5 to be in same RA, when business began, SGSN also will send " session begins indication " and give these RNC so.The same in the message content and 125, then the content of RNC return messages also with 126 in the same.When system decision when being in same SGSN control all RNC transmission sessions down and beginning, the processing mode of these RNC be the same now.

The different messages that is to use that Fig. 5 describes carries out the flow process that session begins to notify to different RNCs.

The plot of describing among Fig. 5 is to carry out according to the correlation between each RNC among Fig. 6, according to shown in Figure 6, comprises RNC1 and RNC6 among the RA1, comprises RNC4 among the RA2, comprises RNC5 among the RA3, comprises RNC2 and RNC3 among the RA4.

Before session began, RNC4 was the SRNC of certain user's equipment, and RNC5 is the DRNC of certain user's equipment, and RNC1 comprises the subscriber equipment that activation MBMS business is in the PMM_IDLE state.According to prior art, DRNC may register to SGSN before session begins.

Among above-mentioned Fig. 5 501, DRNC sends " MBMS RNC register requirement " message to SGSN, comprises the service identification tabulation in the message, after SGSN receives this message, this RNC can be joined in the downstream node tabulation in its bearer context.

Among above-mentioned Fig. 5 502, SGSN receive " the MBMS session begins " message that GGSN sends, with the service identification that comprises in this message, and QoS parameter, the multicast service zone is included in this professional bearer context.SGSN sends message according to the relevant RNC in the downstream node tabulation of its bearer context, and this MBMS service conversation of notice RNC begins.

Among above-mentioned Fig. 5 503, SGSN sends " MBMS RAB request for allocation " message to RNC4, comprising service identification, QoS parameter, multicast service zone, parameters such as Tunnel Identifier.Because RNC4 is the SRNC of some UE, so oriented these UE of this RNC provide with point-to-point or point-to-multipoint mode professional possibility are provided, therefore also comprise the Tunnel Identifier of user plane between RNC that the SGSN side distributes and the SGSN in this message, be used for transmitting data.

Among above-mentioned Fig. 5 504, SRNC returns " MBMS RAB assignment response " message to SGSN, comprises in this message to use indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.If this SRNC will provide point-to-multipoint channel or will be to providing point-to-point channel with its subscriber equipment that has RRC to be connected to its control sub-district down, " use in the future and indicate " so can be set to deny, show that SGSN receives this message after, just can transmit data.Otherwise, if this SRNC neither needs the sub-district under its control that the point-to-multipoint channel is provided, do not need to providing point-to-point channel with its subscriber equipment that has RRC to be connected yet, " using indication in the future " so is set to very, after showing that SGSN receives this message, just do not need to transmit data, but will preserve at this professional user-plane tunnel sign.

Among above-mentioned Fig. 5 505, SGSN sends " MBMS RAB request for allocation " message to RNC1, comprising service identification, QoS parameter, multicast service zone, parameters such as notification area and Tunnel Identifier.After RNC receives this message, judge whether the sub-district under its control comprises subscriber equipment, if comprise, then showing needs user plane to carry out transfer of data, and " using indication in the future " is set to not, otherwise do not need user plane, and " using indication in the future " is set to true.Yet no matter in the sub-district of its control whether subscriber equipment is arranged, can set up user plane, RNC returns 506 " MBMSRAB assignment response " message to SGSN, comprises in this message to use indication in the future, the parameter that the RNC side is set up about user plane is as Tunnel Identifier.RNC can also comprise number of users in this message, so that can directly determine to use point-to-point channel under the fewer situation of number of users.

Among above-mentioned Fig. 5 507, " MBMS adheres to request information to SRNC, comprises service identification in the message, UE identification list, cell list, URA tabulation to the DRNC transmission.DRNC just can know among which sub-district of its control or the URA and comprises the subscriber equipment that is in the PMM_CONNECTED state like this.If DRNC does not receive " session begins indication " message from SGSN, then may this RNC neither any SRNC that is in the subscriber equipment of connection mode, RA under it does not comprise the subscriber equipment that activates this MBMS business of any PMM_IDLE of being in yet, and other RNC (if any) of RA did not register to SGSN yet under it.DRNC just to the SGSN registration, sends 509 " MBMS so

The RNC register requirement " message, comprise in this message " service identification ".

Among above-mentioned Fig. 5 510, SGSN will join this RNC in this professional MBMS bearer context and go, and sends " MBMS RAB request for allocation " message to RNC5 then, comprising service identification, QoS parameter, multicast service zone, parameters such as Tunnel Identifier.If this DRNC will provide the point-to-multipoint channel to its control sub-district down, " use indication in the future " so and can be set to and deny, show that SGSN receives this message after, just can transmit data.Otherwise, if this DRNC does not need to provide the point-to-multipoint channel to its control sub-district down, " use indication in the future " so and be set to true, show that SGSN receives this message after, just do not need to transmit data, identify but will preserve at this professional user-plane tunnel.

Among above-mentioned Fig. 5 511, DRNC returns " MBMS RAB assignment response " message to SGSN, comprises in this message to use indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.

Among above-mentioned Fig. 5 512 supposes that a UE is that sub-district under the RNC4 moves to DRNC when being the sub-district of RNC2 control from SRNC, and SRNC sends to DRNC that " MBMS adheres to request information, comprises service identification in the message, customer equipment identification and cell ID.

Among above-mentioned Fig. 5 513, DRNC returns " MBMS adheres to response message " to SRNC.

Among above-mentioned Fig. 5 514, expression is if this UE activates the UE of this MBMS business for first UE, and this moment, RNC2 will set up business contexts so, to SGSN transmission 515 " MBMS RNC register requirement " message, comprised in this message " service identification " then.

Among above-mentioned Fig. 5 516, SGSN will join this RNC in the downstream node tabulation of this professional MBMS bearer context and go, and send " MBMS RAB request for allocation " message to RNC5 then, comprising service identification, QoS parameter, multicast service zone, parameters such as Tunnel Identifier.Owing to be first UE, DRNC does not need to provide the point-to-multipoint channel to its control sub-district down, " uses indication in the future " so and is set to very, show that SGSN receives this message after, just do not need to transmit data, but will preserve at this professional user-plane tunnel sign.

Among above-mentioned Fig. 5 517, DRNC returns " MBMS RAB assignment response " message to SGSN, comprises in this message to use indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.Because RNC2 and RNC3 are in RA4 together, therefore to send " session begins indication " message to RNC3, but, service parameter be sent to this RNC just in order better to support mobility of user equipment owing to do not comprise any UE among this RNC.This message represents that RNC needn't add up the process of number of users at its affiliated area.This RNC does not need to use the user to transmit data yet, therefore is set to true with " use indication in the future ".When system decision when being in same SGSN control all RNC transmission sessions down and beginning, the processing mode of RNC3 be the same now.

Among above-mentioned Fig. 5 519, RNC returns " session begins to confirm " message to SGSN, comprises in this message and uses indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.

Move to the sub-district of RNC2 control as subscriber equipment new user who adds this business or be in idle condition in the sub-district that RNC2 controlled among above-mentioned Fig. 5, SGSN sends 520 " MBMS UE connection requests " to RNC2, comprises the MBMS service identification tabulation that UE adds in this message.RNC2 sends 521 " MBMS UE connection response " to SGSN.

Among above-mentioned Fig. 5 522, RNC2 judge whether the ordered business of this UE does not set up context, if then set up.SGSN joins this RNC in this professional MBMS bearer context and goes, and sends 523 " MBMS RAB request for allocation " message to RNC2 then, comprising service identification, and QoS parameter, multicast service zone, parameters such as Tunnel Identifier.Owing to be first UE, RNC2 need provide point-to-point channel to its control sub-district down, " uses indication in the future " so and is set to not, show that SGSN receives this message after, just need transmit data.

Among above-mentioned Fig. 5 524, DRNC returns " MBMS RAB assignment response " message to SGSN, comprises in this message to use indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.Because RNC2 and RNC3 are in RA4 together, therefore to send 525 " session begins indication " message, but, service parameter be sent to this RNC just in order better to support mobility of user equipment owing to do not comprise any UE among this RNC to RNC3.This message represents that RNC need add up the process of number of users at its affiliated area, if this information unit is true, does not then need to add up number of users, otherwise the statistics number of users.This RNC does not need to transmit data for the user yet, therefore " uses indication in the future " and is set to very.When system decision when being in same SGSN control all RNC transmission sessions down and beginning, the processing mode of RNC3 be the same now.

Among above-mentioned Fig. 5 526, RNC returns " session begins to confirm " message to SGSN, comprises in this message and uses indication in the future, and the parameter that the RNC side is set up about user plane is as Tunnel Identifier.

If have other RNC and RNC4 or RNC5 to be in same RA, when business began, SGSN also will send " session begins indication " and give these RNC so.The same in the message content and 525, then the content of RNC return messages also with 526 in the same.When system decision when being in same SGSN control all RNC transmission sessions down and beginning, the processing mode of these RNC be the same now.

The generation type of the contextual downstream node of MBMS service bearer tabulation among the SGSN: SGSN place is that each it UE that served preserves the MBMS service identification of its subscription.SGSN knows which UE has subscribed to those MBMS business.After UE has subscribed to the MBMS business,, go in the downstream node tabulation of all professional corresponding bearer contexts that the RNC that comprises among the RA of SGSN with this UE place adds that UE subscribes to if UE is in the PMM_IDLE state.If this UE is in the PMM_CONNECTED state, the RNC that SGSN comprises the SRNC at this UE place adds in the downstream node tabulation that UE subscribes to all professional corresponding bearer contexts and goes.If the DRNC at this UE place registers to SGSN, SGSN also will join this RNC UE and subscribe in the downstream node tabulation of all professional corresponding bearer contexts and go.Simultaneously the SGSN every other RNC that also DRNC with arbitrary SRNC and registration will be in same RA also joins in the downstream node tabulation of bearer context of corresponding service and goes.This process can be that UE joins arbitrary MBMS and carries out when professional before session begins, and also can carry out when session begins.

In order to distinguish this four kinds of different RNC, SGSN can increase a sign in its bearer context: the RNC type identification, be used for distinguishing dissimilar RNC, so that decision sends different " session begins indication " message or sends different type of message " MBMS RAB request for allocation " or " session begins indication " message.

Table 1:SGSN bearer context content

Parameter	Describe
		IP multicast address	Service identification
APN	Service identification
		Service quality	The service quality of this MBMS service needed is provided
The multicast services zone	The zone that the MBMS business should be distributed
		The downstream node tabulation	The RNC that needs announcement session to begin may set up the RNC of user plane
The RNC Status Type	Be in the RNC of last known Routing Area (RA), the sub-district under this RNC control range comprises the subscriber equipment that is in idle condition (PMM_IDLE); Service radio-cell controller (SRNC), the sub-district under the RNC control range comprises the subscriber equipment that is in connection status (PMM_CONNECTED), and this RNC is the SRNC of UE; Floating radio-cell controller (DRNC), the sub-district under the RNC control range comprises the subscriber equipment that is in connection status (PMM_CONNECTED), but this RNC is not the SRNC of UE, but the DRNC of UE.Belong to other RNC of a RA with the DRNC of some SRNC or registration

Embodiment

1) the node processing flow process of RNC

Fig. 7 has described the node processing flow process of RNC when using identical message.

701 stage RNC receive message from SGSN.

702 stages judged whether the message of receiving from SGSN is " session begins indication ", if then turn to 703, otherwise turn to 701.In 703 stages, RNC preserves SGSN service specified mass parameter in its business contexts, the multicast service zone, and the Tunnel Identifier of SGSN side, and set up Iu user plane between RNC and the SGSN, and distribute the Tunnel Identifier of RNC side, forward 704 to.In 704 stages, RNC checks in this message whether comprise " notice indication ", if then turn to 705, otherwise turn to 706.In 705 stages, the RNC decision not sub-district under it sends the MBMS notice, does not promptly add up number of users, and RNC stage user plane is waited until use in the future, will " use indication in the future " and be set to really turn to 709.In 706 stages, RNC checks in the message whether comprise " notification area ", if having, then turns to 707, otherwise turns to 708.In 707 stages, RNC will should be mapped to the sub-district according to configuration in the zone, send the MBMS notice in each sub-district, statistics community user number.RNC can use (" using indication in the future " is true) according to whether there being the user to determine whether using immediately the Iu user plane to carry out transfer of data (" using indication in the future " is for denying) in the sub-district after still waiting until, turn to 709 then.In 708 stages, if RNC is SRNC, then judging whether to provide the point-to-multipoint transmission mode for the sub-district under its control, perhaps will be for setting up point-to-point channel with its UE that has RRC to be connected, if " using indication in the future " is set is not, " using indication future " if both are all not, then is set is true.If RNC is DRNC, then judging whether will be for its control sub-district down provide the point-to-multipoint transmission mode, if " using indication in the future " is set for not, otherwise is set to really turn to 709.In 709 stages, RNC sends " session begins to confirm " message to SGSN, wherein comprises the parameter of the Tunnel Identifier etc. of RNC side about user plane, uses indication or the like in the future.

Fig. 9 has described the node processing flow process of RNC when using different messages.

901 stage RNC receive message from SGSN.

902 stages judged whether the message of receiving from SGSN is " MBMS RAB request for allocation ", if then turn to 903, otherwise turn to 908.In 903 stages, RNC preserves SGSN service specified mass parameter in its business contexts, the multicast service zone, and the Tunnel Identifier of SGSN side, and set up the Iu user plane, and distribute the Tunnel Identifier of RNC side, forward 904 to.In 904 stages, RNC checks in the message whether comprise " notification area ", if having, then turns to 905, otherwise turns to 906.In 905 stages, RNC will should be mapped to the sub-district according to configuration in the zone, send the MBMS notice in each sub-district, statistics community user number.RNC can use (" using indication in the future " is true) according to whether there being the user to determine whether using immediately the Iu user plane to carry out transfer of data (" using indication in the future " is for denying) in the sub-district after still waiting until, turn to 906 then.906 stages, if RNC is SRNC, then judging whether to provide the point-to-multipoint transmission mode for the sub-district under its control, perhaps will be for setting up point-to-point channel with its UE that has RRC to be connected, if " using indication in the future " then is set is not, otherwise " using indication in the future " if both are all not, then is set is true.If RNC is DRNC, then judging whether will be for its control sub-district down provide the point-to-multipoint transmission mode, if " using indication in the future " then is set for not, otherwise is set to really turn to 907.In 907 stages, RNC sends " MBMS RAB assignment response " message to SGSN, wherein comprises the parameter of the Tunnel Identifier etc. of RNC side about user plane, uses indication or the like in the future.

2) node processing of SGSN

Fig. 8 has described the node processing flow process of SGSN when using identical message.

801 stage SGSN receive message from GGSN or RNC.

802 stages judged that whether message sends " MBMS session " from GGSN, if then turn to 803, otherwise turned to 810.803 stage SGSN check the RNC type in its bearer context, turn to 804.804 stages were judged RNC if belong to the RA that contains PMM_IDLE UE, then turned to 805, otherwise turned to 806.805 stages, SGSN will comprise " notification area " in " session begins indication " message, this zone is the RA that comprises PMM_IDLE UE, and this RA will comprise this RNC or this RNC comprises a plurality of such RA, so this notification area can be one or more RA, perhaps whole RNC turns to 809 then.806 stages judged that whether this RNC is SRNC or the DRNC that registered, if then turn to 809, otherwise turned to 807.807 stages were judged whether this RNC belongs to SRNC or the DRNC that registered and belong to same RA, if then turn to 808, otherwise turn to 801.In 808 stages, SGSN will comprise " notice indication " in " session begins indication " message, it indicates that RNC does not need to add up number of users, turns to 809.In 809 stages, SGSN sends " session begins indication " message to RNC, removes in the message to comprise possible notification area, outside the notice indication, also needs to comprise this professional QoS parameter, Tunnel Identifier of SGSN side or the like.

In 810 stages, judge whether the message that SGSN receives is " MBMS RNC register requirement ", if then turn to 811, otherwise turns to 813.In 811 stages, SGSN joins the RNC that this RNC and other and this RNC are in a RA together in this professional bearer context, forwards 812 to.812 stages were judged whether well afoot of business, if forward 803 to, otherwise forwarded 801 to.

813 stages judged whether that new RNC need join in the bearer context, this RNC or have the sub-district of UE under its control to join this business, or have idle UE to move to the sub-district under this RNC control and become SRNC, forward 814 to.In 814 stages, SGSN joins the RNC that this RNC and other and this RNC are in a RA together in this professional bearer context, forwards 812 to.

Figure 10 has described the node processing flow process of SGSN when using different messages.

1001 stage SGSN receive message from GGSN or RNC.

1002 stages judged that whether message sends " MBMS session " from GGSN, if then turn to 1003, otherwise turned to 1011.1003 stage SGSN check the RNC type in its bearer context, turn to 1004.1004 stages were judged RNC if belong to the RA that contains PMM_IDLE UE, then turned to 1005, otherwise turned to 1006.1005 stages, SGSN will comprise " notification area " in " session begins indication " message, this zone is the RA that comprises PMM_IDLE UE, and this RA will comprise this RNC or this RNC comprises a plurality of such RA, so this notification area can be one or more RA, perhaps whole RNC turns to 1007 then.1006 stages judged that whether this RNC is SRNC or the DRNC that registered, if then turn to 1007, otherwise turned to 1008.In 1007 stages, SGSN sends " MBMS RAB request for allocation " message to RNC, removes in the message to comprise possible notification area, also needs to comprise this professional QoS parameter, Tunnel Identifier of SGSN side or the like.1008 stages were judged whether this RNC belongs to SRNC or the DRNC that registered and belong to same RA, if then turn to 1009, otherwise turn to 1001.In 1009 stages, SGSN sends " session begins indication " message to RNC, removes in the message to comprise this professional QoS parameter, Tunnel Identifier of SGSN side or the like.

In 1010 stages, judge whether the message that SGSN receives is " MBMS RNC register requirement ", if then turn to 1011, otherwise turns to 1013.In 1011 stages, SGSN joins the RNC that this RNC and other and this RNC are in a RA together in this professional bearer context, forwards 1012 to.1012 stages were judged whether well afoot of business, if forward 1003 to, otherwise forwarded 1001 to.

1013 stages judged whether that new RNC need join in the bearer context, this RNC or have the sub-district of UE under its control to join this business, or have idle UE to move to the sub-district under this RNC control and become SRNC, forward 1014 to.In 1014 stages, SGSN joins the RNC that this RNC and other and this RNC are in a RA together in this professional bearer context, forwards 1012 to.

Claims (2)

1. method of notifying the multimedia broadcasting and multicast session to begin comprises step:

Service general grouping service wireless GPRS Support Node SGSN sends " session begins indication " message and gives radio network controller (RNC), and this message comprises " notification area ";

Radio network controller (RNC) sends the MBMS notice in the sub-district that described " notification area " comprises;

Radio network controller (RNC) returns " session begins to confirm " message to SGSN.

2. method according to claim 1 is characterized in that described " notification area " is one or more Routing Area RA.

Images