CN1665318A - Method for introducing MBMS service identification - Google Patents
Method for introducing MBMS service identification Download PDFInfo
- Publication number
- CN1665318A CN1665318A CN 200410070847 CN200410070847A CN1665318A CN 1665318 A CN1665318 A CN 1665318A CN 200410070847 CN200410070847 CN 200410070847 CN 200410070847 A CN200410070847 A CN 200410070847A CN 1665318 A CN1665318 A CN 1665318A
- Authority
- CN
- China
- Prior art keywords
- mbms
- message
- sgsn
- rab
- rnc
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 89
- 230000003213 activating effect Effects 0.000 claims description 14
- 230000004913 activation Effects 0.000 claims description 11
- 230000007246 mechanism Effects 0.000 abstract description 5
- 238000012545 processing Methods 0.000 abstract description 4
- 230000004048 modification Effects 0.000 abstract description 3
- 238000012986 modification Methods 0.000 abstract description 3
- 238000013507 mapping Methods 0.000 abstract description 2
- 238000010960 commercial process Methods 0.000 abstract 1
- 230000005540 biological transmission Effects 0.000 description 31
- 230000008569 process Effects 0.000 description 30
- 230000004044 response Effects 0.000 description 27
- 230000011664 signaling Effects 0.000 description 16
- 238000001994 activation Methods 0.000 description 8
- 230000008859 change Effects 0.000 description 5
- 230000000977 initiatory effect Effects 0.000 description 5
- 238000007726 management method Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
A method for introducing MBMS service identification includes the step: UE distributes the RAB identification used for MBMS business; UE transmits the RAB identification used for MBMS business to SGSN; SGSN notifies the corresponding relation to RNC. The corresponding relation between the MBMS business and RAB identification can be known by UE, RNC and SGSN by the method of the invention that UE distributes the RAB identification used for MBMS business and transmit it to SGSN and the method of transmitting the mapping relation to RNC by SGSN. When the RNC is transmitting the MBMS data by PTP mode, the existing mechanism can be used to simplify the realization of the MBMS in the RNC device of PTP mode and quicken MBMS commercial process. When the RNC is notifying UE, MBMS business by DCCH, the modification for the existing aerial interface message can be avoided or reduced by using the RAB identification, and the unified processing mode of UE can be ensured. When existing RNC can not support the MBMS business, the device can made to have good post toward compatibility by directly using existing mode.
Description
Technical field
The present invention relates to Wideband Code Division Multiple Access (WCDMA) (hereinafter to be referred as WCDMA) mobile communication system, particularly introduce the method for new multimedia broadcasting and multicast service (hereinafter to be referred as MBMS) sign.
Background technology
Multimedia broadcasting and multicast service (hereinafter to be referred as MBMS) are that a standardized new business is being carried out in third generation partner plan (hereinafter to be referred as 3GPP).The MBMS business is a kind of business of unidirectional point-to-multipoint, and the maximum characteristics of this business are that it can effectively utilize Radio Resource and Internet resources.Different with existing business, MBMS business aloft interface can or be put the transmission of multiple spot (hereinafter to be referred as PTM) dual mode by point-to-point (hereinafter to be referred as PTP).
Fig. 1 has described the system configuration of MBMS, and the MBMS network configuration is based on GPRS (be called for short GPRS) core net, and has increased new network element.Be description below to Fig. 1 MBMS system configuration.
101 broadcasting and multicast service center (being called for short BM-SC) are the professional control centres of MBMS system.102 Gateway GPRS Support Nodes (be called for short GGSN) and 103 Serving GPRS Support Nodes (abbreviation SGSN) have constituted the transmission network of MBMS business, for the transmission of data provides route.104UMTS land radio access web (being called for short UTRAN) provides Radio Resource for MBMS serves on the interface aloft.105 subscriber equipmenies (being called for short UE) are the terminal equipments that is used for receiving data.106 attaching position registers (being called for short HLR) are preserved and subscriber-related data, and services such as subscription authentication can be provided.107Uu is a wave point, and 108Iu represents the interface between Access Network and the core net.The professional used Radio Resource of MBMS is not user's special use, but professional thus all users share.
On the Iu interface, for all users that add same MBMS business, user plane is shared, and promptly for a kind of MBMS business, for a radio network controller (hereinafter to be referred as RNC), has only a MBMS data flow.At RNC and SGSN, user plane be with MBMS service identification and MBMS bearer context (MBMS Bearer Context) one to one.
At SGSN, the sign of MBMS business is had: Temporary Mobile Group Identity (hereinafter to be referred as TMGI) and complete multicast sign are Internet protocol (hereinafter to be referred as IP) multicast address and access point name (hereinafter to be referred as APN).At RNC the sign of MBMS business there are TMGI and MBMS sign.MBMS sign be RNC distribute in wireless access network and UE effective.UE then can discern TMGI, IP multicast address and APN, MBMS sign.
In the system of Rel99, Rel4 and Rel5, Network layer Service Access Point Identifier (hereinafter to be referred as NSAPI) and RAB (hereinafter to be referred as RAB) sign have one-to-one relationship, in grouping (hereinafter to be referred as PS) territory, and radio bearer (hereinafter to be referred as RB) sign also has relation one to one.When UE initiation packet data protocol (hereinafter to be referred as PDP) context activation process, UE selects one not have the NSAPI that uses and pass to SGSN.When SGSN initiated the RAB assigning process, SGSN was included in NSAPI in the RAB identification information element.
The process of existing UE adding MBMS business as shown in Figure 2.
201 UE initiate to set up the process of PDP Context.After PDP Context is set up successfully, all preserve this PDP Context in UE, SGSN and GGSN, the signaling of having set up the PS territory simultaneously between UE and GGSN connects, and the intermediate equipment that this signaling connects is wireless access network (hereinafter to be referred as RAN) and SGSN.
202 UE send Internet group management protocol of the multicast group (hereinafter to be referred as IGMP) to GGSN and add message, and this message connects arrival GGSN by the signaling of setting up in the step 201.This message comprises parameter: Internet protocol (hereinafter to be referred as IP) multicast address, this multicast address can indicate a certain multicast service in a certain MBMS multicast service or the external data network.
203 GGSN and BM-SC carry out Signalling exchange so that UE is carried out authentication.
204 GGSN send the MBMS notification request message to SGSN, and this message comprises parameter: UE sign, IP multicast address.
After 205 SGSN receive message in the step 204, send request MBMS context activation message to UE, this message comprises parameter: UE sign, IP multicast address.
After 206 UE receive message in the step 205, send to SGSN and to activate the MBMS context request message, this message comprises IP multicast address and access point name (hereinafter to be referred as APN).
207 SGSN send " MBMS push-notification-answer " message and give GGSN.The MBMS notification response message contains: cause value.It is the also right and wrong success of successful activation MBMS context that cause value indicates reason owing to SGSN or UE.In case receive among the operation of response message indication failure or the GGSN and activate the overtime of clock.GGSN can return the IP multicast and insert (defining) in 3GPP TS29.061.
208 if desired, carries out the safety encipher process between UE and the SGSN.
209 SGSN send to GGSN and set up the MBMS context request message, and this message comprises IP multicast address and APN.
210 GGSN carry out Signalling exchange so that MBMS business and UE are carried out authentication with BM-SC after receiving message in the step 209.
If 211 GGSN do not set up the bearer context information of this MBMS business, GGSN sends and " carries request information and give BM-SC.This message comprises IP multicast address and APN.
BM-SC sends " carrying response " message and gives GGSN, comprises MBMS bearer context information in the message.BM-SC is in the descendant node tabulation in the sign of this GGSN adding BM-SC bearer context.
If also be not this MBMS traffic assignments Temporary Mobile Group Identity (hereinafter to be referred as TMGI), BM-SC distributes a new TMGI.And pass to GGSN by " carrying response " message, SGSN, and further pass to UE by " activating the acceptance of MBMS context " message (215).
If the state of bearer context is for activating, the session between BM-SC initiation and the GGSN begins process.
212 GGSN produce MBMS UE context, and send " producing the MBMS context response " to SGSN.
If 213 SGSN do not set up the bearer context information of this MBMS business, SGSN sends and " carries request information and give GGSN.This message comprises IP multicast address and APN.
BM-SC sends " carrying response " message and gives GGSN, comprises MBMS bearer context information in the message.BM-SC is in the descendant node tabulation in the sign of this GGSN adding BM-SC bearer context.
If the state of bearer context is for activating, the session between BM-SC initiation and the GGSN begins process.
If 214 at least for this reason UE set up the RAB in a PS territory, SGSN offers RAN to MBMS UE contextual information.
215 SGSN send " activating the MBMS context receives " message and give UE.SGSN does not just send this message after not needing by the time 212 to finish.
For the MBMS business, UE is to distinguish MBMS context and notice SGSN with the MBMS service identification when adding MBMS activation of service MBMS UE context, does not select a NSAPI for MBMS.On SGSN, RNC and UE inside and Iu and Uu interface, can only could discern the MBMS business like this with above-mentioned several MBMS service identifications.This can cause following several problems:
(1) aloft on the interface, when RNC notifies UE MBMS professional by Dedicated Control Channel (hereinafter to be referred as DCCH) (when between PTP and PTM, switching) as the transmission mode in certain sub-district, can only be with TMGI or MBMS sign, so proposition need " radio bearer (hereinafter to be referred as RB) is set up increases information element " MBMS service identification " in the request information in existing message among the existing protocol TS25.346 v2.4.0.Similarly message also has " RB discharges request " and " RB reconfiguration request ".Information element in these message " RAB sign " is to exist, and is not MBMS traffic assignments NSAPI and RAB sign at present; Simultaneously, when the MBMS business is transmitted by ptp mode, the processing of the existing UE end of influence.
(2) be to identify according to the RAB in the agreement to discern different business in existing RNC equipment, if the transfer mode of MBMS business is PTP, corresponding MBMS business does not have the RAB sign of corresponding MBMS business, can cause a large amount of changes to existing equipment.
(3) if RNC does not support the MBMS business, SGSN is in the process with Rel99/Rel4 or Rel5 when UE sets up the Iu user plane for this reason, do not have corresponding N SAPI to use, do not have the corresponding relation of NSAPI and RAB sign, UE just can't distinguish from the next data corresponding service of respective carrier.SGSN can not directly replace the RAB sign with the MBMS service identification, because the length of RAB sign is 8 bits, and the MBMS service identification is 32 bit long as TMGI.
Summary of the invention
The method that the purpose of this invention is to provide a kind of MBMS of introducing service identification, having provided UE is MBMS traffic assignments NSAPI, sends to SGSN, and SGSN sends the RAB be used for the MBMS business and identifies method to RNC, make UE, RNC and SGSN know the corresponding relation that MBMS is professional and RAB identifies.Thereby RNC can notify UE MBMS business (when switching between PTP and PTM as the transmission mode of MBMS business in certain sub-district) by DCCH with the existing message that comprises the RAB sign, RNC is inner when ptp mode uses with the identical mechanism of existing system, when RNC did not have the MBMS ability, SGSN can use RAB ID to set up special I u user plane to UE.
For achieving the above object, a kind of method of introducing multimedia broadcasting and multicast service identifier comprises step:
UE divides the RAB that is used in the MBMS business sign;
UE sends the RAB that is used for the MBMS business and identifies to SGSN;
SGSN is this corresponding relation notice RNC.
Method and SGSN that the UE that provides by the present invention distributes the RAB sign of MBMS business and sends SGSN to send the method for these mapping relations to RNC, the RAB sign that UE, RNC and SGSN are known be used for the MBMS business.When RNC transmits the MBMS data by the PTP mode, can maximizedly utilize existing mechanism, MBMS commercialization process is accelerated in the realization of MBMS in the RNC equipment when simplifying ptp mode.RNC when professional (when switching between PTP and PTM as the transmission mode of MBMS business in certain sub-district), utilizes the RAB sign by DCCH notice UE MBMS, avoids or reduces modification to existing air-interface information, guarantees the unified transaction module of UE.When existing RNC does not support that MBMS is professional, can directly adopt the mode of Rel99/Rel4 or Rel5, make equipment that better compatibility backward be arranged.
Description of drawings
Fig. 1 is the logical network equipment drawing of MBMS business;
Fig. 2 is the process that existing UE adds the MBMS business;
Fig. 3 .. provides RAB sign that is used for the MBMS business and the process of notifying SGSN and RNC by UE;
Fig. 4 provides the RAB sign that is used for the MBMS business, the operating process of UE by UE;
Fig. 5 provides RAB sign and notice SGSN and the RNC that is used for the MBMS business, the operating process of SGSN by UE;
Fig. 6 provides RAB sign and notice SGSN and the RNC that is used for the MBMS business, the operating process of RNC by UE;
Fig. 7 is when transmission mode is switched from PTM to PTP in the RNC sub-district, and RNC uses the signaling process of RAB sign;
Fig. 8 is when transmission mode is switched from PTP to PTM in the RNC sub-district, and RNC uses the signaling process of RAB sign;
When Fig. 9 is the transmission mode change of MBMS business in the RNC sub-district, use the operating process of the professional RNC of RAB sign notice UE MBMS;
When Figure 10 is the transmission mode change of MBMS business in the RNC sub-district, use the operating process of the professional UE of RAB sign notice UE MBMS;
Embodiment
Having provided UE among the present invention is MBMS traffic assignments NSAPI, send to SGSN, and SGSN sends the RAB be used for the MBMS business and identifies method to RNC, thereby make RNC to notify UE MBMS business (when between PTP and PTM, switching) by DCCH with the existing message that comprises the RAB sign as the transmission mode of MBMS business in certain sub-district, RNC is inner when ptp mode uses with the identical mechanism of existing system, has reduced the modification to existing interface message and equipment.
Above-mentioned process describes with figure, also with flow chart the node course of work of (comprising UE, RNC, SGSN) is described.
The process of the RAB sign that Fig. 3 is used in the MBMS business for UE divides.When UE added the MBMS business, UE selected one not have the NSAPI that uses and pass to SGSN.When SGSN initiated connection request to this UE, SGSN was included in the RAB sign in " MBMS UE connection request " message, comprises NSAPI in information element RAB sign.UE is that MBMS traffic assignments RAB sign has two kinds of methods: one, UE add each MBMS when professional for this reason one of MBMS traffic assignments not have the NASPI of use, promptly NSAPI and MBMS service identification have one-to-one relationship.Its two, UE is adding first MBMS business, distributes a NSAPI who is used for all MBMS business who does not use when creating MBMS UE context.
301 UE initiate to set up the process of PDP Context.After PDP Context is set up successfully, all preserve this PDP Context in UE, SGSN and GGSN, the signaling of having set up the PS territory simultaneously between UE and GGSN connects, and the intermediate equipment that this signaling connects is RAN and SGSN.
302 UE send IGMP to GGSN and add message, and this message arrives GGSN by the signaling connection of setting up in the step 301.This message comprises parameter: IP multicast address, this multicast address can identify a certain multicast service in a certain MBMS multicast service or the external data network.
303 GGSN and BM-SC carry out Signalling exchange so that UE is carried out authentication.
304 GGSN send the MBMS notification request message to SGSN, and this message comprises parameter: UE sign, IP multicast address.
After 305 SGSN receive message in the step 304, send request MBMS context activation message to UE, this message comprises parameter: UE sign, IP multicast address.
After 306 UE received message in the step 305, corresponding UE was that the method one of MBMS traffic assignments RAB sign: UE selects a NSAPI who not have use, is used for this MBMS business; Corresponding UE is the method one of MBMS traffic assignments RAB sign: when UE is not MBMS traffic assignments NSAPI, UE select a NSAPI who not have to use be used for all MBMS business (if UE as the MBMS traffic assignments NSAPI, just do not reallocated here).Then, UE sends " activating the MBMS context request " message to SGSN, and corresponding UE is the method one of MBMS traffic assignments RAB sign: this message comprises IP multicast address, APN and the UE NSAPI of MBMS service selection for this reason.When corresponding UE is the method two of MBMS traffic assignments RAB sign, only when UE adds first MBMS business, just comprise the NSAPI that is used for all MBMS business in the message.
After 307 SGSN receive 305 message, preserve the NSAPI that this UE in the message is used for professional or all the MBMS business of this MBMS.
308 SGSN send " MBMS push-notification-answer " message and give GGSN.The MBMS notification response message contains: cause value.It is the also right and wrong success of successful activation MBMS context that cause value indicates reason owing to SGSN or UE.In case receive among the operation of response message indication failure or the GGSN and activate the overtime of clock.GGSN can return the IP multicast and insert (defining) in 3GPP TS29.061.
309 if desired, carries out the safety encipher process between UE and the SGSN.
310 SGSN send to GGSN and set up the MBMS context request message, and this message comprises IP multicast address and APN.
311 GGSN carry out Signalling exchange so that MBMS business and UE are carried out authentication with BM-SC after receiving message in the step 310.
If 312 GGSN do not set up the bearer context information of this MBMS business, GGSN sends and " carries request information and give BM-SC.This message comprises IP multicast address and APN.
BM-SC sends " carrying response " message and gives GGSN, comprises MBMS bearer context information in the message.BM-SC is in the descendant node tabulation in the sign of this GGSN adding BM-SC bearer context.
If also be not this MBMS traffic assignments TMGI, BM-SC distributes a new TMGI.And pass to GGSN by " carrying response " message, SGSN, and further pass to UE by " activating the acceptance of MBMS context " message (316).
If the state of bearer context is for activating, the session between BM-SC initiation and the GGSN begins process.
313 GGSN produce MBMS UE context, and send " producing the MBMS context response " to SGSN.
If 314 SGSN do not set up the bearer context information of this MBMS business, SGSN sends and " carries request information and give GGSN.This message comprises IP multicast address and APN.
BM-SC sends " carrying response " message and gives GGSN, comprises MBMS bearer context information in the message.BM-SC is in the descendant node tabulation in the sign of this GGSN adding BM-SC bearer context.
If the state of bearer context is for activating, the session between BM-SC initiation and the GGSN begins process.
If 315 exist a PS territory RAB of UE foundation for this reason at least, SGSN offers RNC to MBMS UE contextual information.SGSN sends " MBMS UE connection request " message and gives RNC, and corresponding UE is the method one of MBMS traffic assignments RAB sign: comprise the corresponding relation of MBMS service identification and RAB sign in this message, comprise NSAPI in information element RAB sign.If this UE has added a plurality of MBMS business, then comprise the corresponding relation tabulation of MBMS service identification and RAB sign in " MBMS UE connection request " message.Corresponding UE is the method two of MBMS traffic assignments RAB sign: only comprise a RAB sign that is used for all MBMS business in " MBMS UE connection request " message.
RNC sets up MBMS UE context after receiving " MBMS UE connection request " message, preserves the RAB sign that is used for the MBMS business, and sends " MBMS UE connection response " message to SGSN.
316 SGSN send " activating the MBMS context receives " message and give UE.SGSN does not just send this message after not needing by the time 313 to finish.
The corresponding UE branch is used in the method for the RAB sign of MBMS business, and promptly UE selects one when adding the MBMS business does not have the NSAPI that uses to send to SGSN, and SGSN preserves this NSAPI.If there is the RAB in the PS territory of corresponding this UE, SGSN sends " MBMS UE connection request " message and gives RNC, comprises in the message to be used for the professional RAB sign of MBMS, and NSAPI is included in the information element RAB sign.
Also have some SGSN need send the situation of MBMS UE connection request message to RNC, for example, when the UE that has added the MBMS business enters packet domain mobile management (hereinafter to be referred as PMM) connection status and set up the RAB in PS territory; Perhaps when the MBMS session begins or carry out, when UE entered the PMM connection mode for MBMS purpose (as counting, counting, PTP carrying again), same, SGSN sent " MBMSUE connection request " message and gives RNC, comprise RAB ID in the message, NSAPI is included in the information element RAB sign.Adding MBMS with UE in Fig. 3 is that example illustrates that SGSN sends the signaling process of RAB ID to RNC when professional.
The method of the RAB sign that Fig. 4 is used in the MBMS business for UE divides, the operating process of UE.
401 UE receive the next message from SGSN;
If 402 UE receive next " request MBMS context activation " message from SGSN, 403 corresponding UE are the method one of MBMS traffic assignments RAB sign: according to the IP multicast address and the APN that receive in the message, UE is otiose NSAPI of MBMS service selection for this reason, and preserves this corresponding relation; Corresponding UE is the method two of MBMS traffic assignments RAB sign: if when this first MBMS that to be this UE add is professional, UE be the NSAPI that one of all MBMS service selection do not have use, and preserves this NSAPI in MBMS UE context.If UE is the NSAPI that has been the MBMS traffic assignments, just do not reallocated here.
404 UE send " activating the MBMS context request " message and give SGSN, and corresponding UE is the method one of MBMS traffic assignments RAB sign: comprise in the message: IP multicast address, APN and UE be the NSAPI of MBMS service selection for this reason.And wait-for-response.When corresponding UE is the method two of MBMS traffic assignments RAB sign, only when UE adds first MBMS business, just comprise the NSAPI that is used for all MBMS business in the message.
RAB sign and notice SGSN and RNC that Fig. 5 is used in the MBMS business for UE divides, the operating process of SGSN.
501 SGSN receive the next message from UE.
If 502 SGSN receive next " activating the MBMS context request " message from UE, 503 SGSN preserve the NSAPI that is used for the MBMS business in the message.Corresponding UE distributes the method one of MBMS RAB sign: SGSN need preserve the corresponding relation of MBMS service identification and RAB sign.
504 SGSN send " MBMS push-notification-answer " message and give GGSN.The MBMS notification response message contains: cause value.Cause value indicates successful activation MBMS context or owing to the reason of SGSN or UE is non-successful.
Safety encipher process between 505 SGSN execution and the UE, SGSN sends the process that " producing the MBMS context request " gives GGSN and wait-for-response, if SGSN receives when SGSN behind the response message does not set up the bearer context information of this MBMS business and sets up the process of bearer context between the GGSN, shown among Fig. 3 309,310,313 and 314, these operations are identical with existing standard, ignore detailed technology contents here.
If 506 MBMS sessions begin, directly carry out 508.Otherwise, 507 SGSN judge whether to exist to should UE at the RAB in PS territory.
If 508 exist to should UE at the RAB in PS territory, SGSN sends " MBMS UE connection request " message and gives RNC, and corresponding UE is the method one of MBMS traffic assignments RAB sign: comprise the corresponding relation that MBMS service identification and this UE are used for the RAB sign of this MBMS business in the message.If this UE has added a plurality of MBMS business, then comprise the corresponding relation tabulation of MBMS service identification and RAB sign in " MBMS UE connection request " message.Corresponding UE is the method two of MBMS traffic assignments RAB sign: only comprise a RAB sign that is used for all MBMS business in " MBMS UE connection request " message.
509 SGSN receive next " response of MBMS UE connection request " message from RNC.510 SGSN send " activating the MBMS context accepts " message and give UE.
Also have some SGSN need send the situation of MBMS UE connection request message to RNC, for example, when the UE that has added the MBMS business enters packet domain mobile management (hereinafter to be referred as PMM) connection status and set up the RAB in PS territory; Perhaps when the MBMS session begins or carry out, when UE enters the PMM connection mode for MBMS purpose (as counting, counting, PTP carrying again), equally, SGSN sends " MBMSUE connection request " message and gives RNC, corresponding UE is the method one of MBMS traffic assignments RAB sign: comprise the corresponding relation of RAB ID and MBMS service identification in the message, NSAPI is included in the information element RAB sign.If this UE has added a plurality of MBMS business, then comprise the corresponding relation tabulation of MBMS service identification and RAB sign in " MBMS UE connection request " message.Corresponding UE is the method two of MBMS traffic assignments RAB sign: only comprise a RAB sign that is used for all MBMS business in " MBMS UE connection request " message.The operation of SGSN is described with top 508 and 509 in these cases.
Fig. 6 be used in the MBMS business for UE divides with RAB sign and notice SGSN and RNC, the operating process of RNC.
601 RNC receive the next message from SGSN;
If 602 RNC receive next " MBMS UE connection request " message from SGSN, the RAB that is used for the MBMS business that 603 RNC preserve in the message is identified to MBMS UE context; The corresponding UE branch is used in the method one of the RAB sign of MBMS business: RNC need preserve the corresponding relation of MBMS service identification and RAB sign.
604 RNC send " MBMS UE connection response " message and give SGSN.
When Fig. 7 switched from PTM to PTP for transmission mode in the RNC sub-district, RNC used the signaling process of RAB sign by DCCH notice UE MBMS business.
701 control radio network controllers (hereinafter to be referred as CRNC) send the MBMS data to UE in certain sub-district by the mode of PTM.
702 variations owing to interested UE number in the sub-district, CRNC determines the transmission mode in this sub-district to change into PTP from PTM." MBMS p-t-m transmission ending request information is given service wireless network controller (hereinafter to be referred as SRNC) in the CRNC transmission.Whether SRNC switches to PTP according to the situation decision of resource, sends " response of MBMS p-t-m transmission ending " then and gives CRNC.
If the PTP resource is set up successfully in 703 Access Networks, the corresponding UE branch is used in the method one of the RAB sign of MBMS business: SRNC sends existing message " RB foundation " and gives UE, and the RAB of this MBMS business of the correspondence of storing in context sign is included in the message.Do not need to add the MBMS service identification in this message.UE just can know the MBMS business of this radio bearer correspondence by the sign of the RAB in this message.The corresponding UE branch is used in the method two of the RAB sign of MBMS business: SRNC sends message " RB foundation " and gives UE, comprises the RAB sign and the MBMS service identification that are used for all MBMS business in the message.
704 UE set up relevant parameter resource allocation in the message according to RB, send " RB sets up and finishes " message then and give RNC.
705 SRNC send the MBMS data to UE by the radio bearer of PTP.
When Fig. 8 switched from PTP to PTM for transmission mode in the RNC sub-district, RNC used the signaling process of RAB sign by DCCH notice UE MBMS business.
801 CRNC are PTP to the transmission mode of a certain MBMS business in the sub-district, and SRNC sends the MBMS data to UE by the mode of PTP.
802 variations owing to interested UE number in the sub-district, CRNC determines the transmission mode of this MBMS business in this sub-district to change into PTM from PTP." MBMS p-t-m transmission beginning request information is given SRNC in the CRNC transmission.Whether the SRNC decision switches to PTM, sends " MBMS p-t-m transmission beginning response " then and gives CRNC.
803 corresponding UE branches are used in the method one of the RAB sign of MBMS business: SRNC sends existing message " RB release " or " RB reshuffles " message is given UE, requires UE to discharge the Radio Resource of PTP.SRNC is included in the RAB of this MBMS business of the correspondence of storing in context sign in the message.Do not need to add the MBMS service identification in this message.UE just can know the MBMS business of this radio bearer correspondence by the sign of the RAB in this message.The corresponding UE branch is used in the method two of the RAB sign of MBMS business: SRNC sends message " RB foundation " and gives UE, comprises the RAB sign and the MBMS service identification that are used for all MBMS business in the message.
804 UE discharge the Radio Resource of PTP according to the relevant parameter in RB release or the RB reconfiguration message, if what receive is the RB reconfiguration message, UE also needs the RB information element according to needs foundation in the reconfiguration message, set up the Radio Resource of PTM, send " RB discharges and finishes " or " RB reshuffles and finishes " message then and give RNC.
805 CRNC send the MBMS data to UE by the radio bearer of PTM.
The UE that provides by Fig. 3, Fig. 4, Fig. 5 and Fig. 6 divides RAB sign that is used in the MBMS business and the method one that offers SGSN and RNC, when using the PTP transmission mode in the sub-district, can use same Rel99, Rel4, mechanism that Rel5 is the same in RNC inside, identify the different business of same UE of distinguishing (the professional and non-MBMS business of different MBMS business and MBMS) with RAB.When RNC need notify UE MBMS professional by DCCH, can use complete existing message, as " RB foundation " among Fig. 7 and Fig. 8, " RB release " and " RB reshuffles " message, need in existing message, not add the MBMS service identification.The UE that is in CELL_DCH or CELL_FACH is in cell change or mobile, in the time of need notifying UE MBMS professional by DCCH, the method that employing is the same with Fig. 8 with Fig. 7 identifies by RAB and to notify UE, rather than increases the MBMS service identification in existing message.
The UE that provides by Fig. 3, Fig. 4, Fig. 5 and Fig. 6 divides RAB sign that is used in the MBMS business and the method two that offers SGSN and RNC, for using in the sub-district when switching between PTP transmission mode or PTP and the PTM, because existing " RB foundation ", " RB release ", RAB sign in " RB reshuffles " message is necessary, make RNC can have the RAB sign available, and in these message, add " MBMS service identification ", UE can know it is the MBMS business by the RAB sign, further distinguishes different MBMS business by the MBMS service identification.
Corresponding RNC is by the method for RAB sign notice UE MBMS business, and Fig. 9 and Figure 10 are the operating process that example also illustrates RNC and UE when switching with channel respectively.
The operating process of RNC is described in detail as follows:
901 RNC receive message;
If 902 RNC receive next " MBMS p-t-m transmission ending request information, execution 903 from an other RNC.Otherwise, skip to 908.
903 RNC send " response of MBMS p-t-m transmission ending " message and give an other RNC who sends a request message.
904 RNC judge whether the transmission mode of MBMS business in this sub-district can be transformed into PTP, for example according to the situation of resource.
If the transmission mode in the 905 RNC sub-districts can be transformed into PTP, RNC is the MBMS business carrying of setting up PTP for this reason in UTRAN.Then, RNC sends " RB foundation " message and gives UE, the corresponding UE branch is used in the method one of the RAB sign of MBMS business: RNC and the RAB sign to should UE MBMS business of preserving in the context is included in RB sets up in the message, need not increase the MBMS service identification in this message.And wait-for-response message; The corresponding UE branch is used in the method two of the RAB sign of MBMS business: RNC and the RAB sign to should UE being used for all MBMS business of preserving in the context is included in RB sets up message, increases the MBMS service identification in this message.
If 906 RNC receive the response message " RB sets up and finishes " of the success from UE,
907 RNC begin to send the MBMS data to UE by the carrying of PTP.
If 908 RNC receive " MBMS p-t-m transmission beginning request " from another one RNC,
909 RNC send " MBMS p-t-m transmission beginning response " message and give an other RNC who sends a request message.
910 RNC send " RB release " or " RB reshuffles " message is given UE, the corresponding UE branch is used in the method one of the RAB sign of MBMS business: these two message are existing message, comprise in the message preserve in the MBMS UE context to RAB sign that should this MBMS business of UE, do not need to increase the MBMS service identification in the message.And wait-for-response; The corresponding UE branch is used in the method two of the RAB sign of MBMS business: RNC the RAB sign to should UE being used for all MBMS business of preserving in the context is included in " RB releases " or " RB reshuffles " message, increase MBMS service identification in this message.
909 and 910 do not have absolute sequencing.
The operating process of UE is described in detail as follows:
1001 UE receive message;
1002 judge the message that UE receives, if RB sets up message or RB release message or RB reconfiguration message, carry out 1003;
1003 UE carry out corresponding RB foundation or RB discharges or the RB reconfiguration course.The corresponding UE branch be used in the MBMS business RAB sign method once: UE can know the MBMS business of correspondence by the RAB sign.The corresponding UE branch is used in the method two of the RAB sign of MBMS business: UE knows it is the MBMS business by the RAB sign, and which MBMS business further distinguishes by the MBMS service identification in the message is.UE has two kinds of methods to the processing of RAB/RB: the first, and for same MBMS business, the Uu resource is for corresponding two the different RAB of PTP and PTM.If UE receives the RB release message, UE discharges corresponding RB, and according to the UE contextual information, UE knows that this carrying is used for the MBMS business, and is professional the same with other, and after all RB of corresponding this RAB discharged, UE notified the release of high-rise RAB.The RAB of corresponding PTM sets up receive common signaling on common signal channel subsequently after.Equally, when receiving that RB sets up message, after UE configures RB, also to notify the foundation of the RAB of high-rise corresponding this PTP RB.The second, for same MBMS business, the Uu resource is for the corresponding different RB of PTP and PTM, same RAB.For example, after UE received the RB release message, UE discharged corresponding RB, and according to the UE contextual information, UE knows that this carrying is used for the MBMS business, and corresponding RAB is not released.Equally, receiving that RB sets up message, after UE configures RB,, just do not needing to rebulid if corresponding RAB exists.When switching from PTP to PTM for the transmission mode of certain MBMS business in the RNC sub-district, it still is that " RB reshuffles " message is given UE that RNC sends " RB release ", depends on that also UE adopts that a kind of method to the processing of RAB/RB.Corresponding first method, RNC sends " RB release " message and gives UE.Two kinds of corresponding methods, RNC sends " RB reshuffles " message and gives UE, after UE receives this message, discharges the RB of PTP, sets up the RB of PTM, and RAB is constant.
1004 according to the type of message of receiving, UE sends response message " RB sets up and finishes " respectively, and perhaps " RB discharges and finishes " or " RB reshuffles and finishes " are given RNC.
Claims (10)
1. method of introducing multimedia broadcasting and multicast service identifier comprises step:
UE divides the RAB that is used in the MBMS business sign;
UE sends the RAB that is used for the MBMS business and identifies to SGSN;
SGSN preserves this corresponding relation;
SGSN is this corresponding relation notice RNC.
2. method according to claim 1 is characterized in that described UE divides the corresponding relation of the RAB sign that is used in the MBMS business to comprise step:
UE receives the next requesting activation MBMS context message from SGSN;
UE one of MBMS traffic assignments does not for this reason have the NSAPI that uses;
UE sends and activates the MBMS context request message to SGSN;
SGSN receives the next activation MBMS context request message from UE;
SGSN preserve receive NSAPI and MBMS service identification in the message corresponding relation in the SGSN contextual information.
3. according to the described method of claim 2, it is characterized in that: comprise information element: the UE NSAPI of MBMS traffic assignments for this reason in described " activating the MBMS context request " message.
4. method according to claim 1 is characterized in that described UE divides the corresponding relation of the RAB sign that is used in the MBMS business to comprise step:
UE receives the next requesting activation MBMS context message from SGSN;
If UE also is not MBMS traffic assignments NSAPI, UE is the NSAPI that one of all MBMS traffic assignments do not have use;
UE sends and activates the MBMS context request message to SGSN;
SGSN receives the next activation MBMS context request message from UE;
SGSN preserves and receives that the NSAPI that is used for all MBMS business in the message is to the SGSN contextual information.
5. according to the described method of claim 4, it is characterized in that: comprise the NSAPI of information element: UE in described " activating the MBMS context request " message for all MBMS traffic assignments.
6. according to claim 2 or 4 described methods, it is characterized in that: after SGSN preserves the RAB sign that is used for the MBMS business, the RAB sign that is used for the MBMS business is notified to RNC, comprises step by sending " MBMS UE connection request " message:
If there be the RAB of this UE in the PS territory, then SGSN sends " MBMS UE connection request " message and gives RNC.
7. according to claim 2 or 4 described methods, it is characterized in that: after SGSN preserves the RAB sign that is used for the MBMS business, the RAB sign that is used for the MBMS business is notified to RNC, comprises step by sending " MBMS UE connection request " message:
The MBMS session begins or when carrying out, UE enters the PMM connection mode for MBMS purpose (as counting, counting, PTP carrying again), and then SGSN sends " MBMS UE connection request " message and gives RNC;
8. method according to claim 4 is characterized in that: after SGSN preserves the RAB sign that is used for the MBMS business, by sending " MBMS UE connection request " message the RAB sign that is used for the MBMS business is notified to RNC, comprises step:
When the UE that has added the MBMS business entered the PMM connection status and set up the RAB in PS territory, SGSN sent " MBMS UE connection request " message and gives RNC.
9. method according to claim 8, it is characterized in that: comprise information element " RAB sign " in described " MBMS UE connection request " message, if comprise the tabulation of MBMS service identification in this message, then the RAB of each MBMS service identification correspondence sign is included in this message, promptly comprises the corresponding relation tabulation of MBMS service identification and RAB sign in " MBMS UE connection request " message.
10. method according to claim 8 is characterized in that: comprise information element " RAB sign " in described " MBMS UE connection request " message, this RAB sign is used for all MBMS business.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100708473A CN100444650C (en) | 2004-03-03 | 2004-07-23 | Method for introducing MBMS service identification |
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200410007871.2 | 2004-03-03 | ||
| CN200410007871 | 2004-03-03 | ||
| CNB2004100708473A CN100444650C (en) | 2004-03-03 | 2004-07-23 | Method for introducing MBMS service identification |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1665318A true CN1665318A (en) | 2005-09-07 |
| CN100444650C CN100444650C (en) | 2008-12-17 |
Family
ID=35036168
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100708473A Expired - Lifetime CN100444650C (en) | 2004-03-03 | 2004-07-23 | Method for introducing MBMS service identification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100444650C (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006034660A1 (en) * | 2004-09-30 | 2006-04-06 | Huawei Technologies Co., Ltd. | Method and apparatus of service identifying and routing in multimedia broadcast/multicast service system |
| WO2008034389A1 (en) * | 2006-09-18 | 2008-03-27 | Huawei Technologies Co., Ltd. | Method, system and terminal for sending and receiving multicast broadcast service |
| WO2008052420A1 (en) * | 2006-10-24 | 2008-05-08 | Zte Corporation | Method for establishing, re-establishing and deleting the radio access bearer of a selected service |
| CN101296396B (en) * | 2007-04-24 | 2010-12-08 | 中兴通讯股份有限公司 | Method for acquiring sustaining power of community multimedia broadcast multicast service |
| CN101272592B (en) * | 2007-03-21 | 2011-01-26 | 上海贝尔阿尔卡特股份有限公司 | Service scheduling device, service scheduling method and multi-community/multimedia cooperation device |
| CN101170796B (en) * | 2006-10-24 | 2011-08-24 | 中兴通讯股份有限公司 | A method for establishing or reconfiguring special radio carrier in service selection |
| CN102264145A (en) * | 2010-05-31 | 2011-11-30 | 中国移动通信集团公司 | Service scheduling method, device and system |
| CN101090392B (en) * | 2006-06-15 | 2011-12-07 | 华为技术有限公司 | Multi-service receiving method |
| CN101166350B (en) * | 2006-10-17 | 2012-07-04 | 中兴通讯股份有限公司 | Method for radio network controller to establish radio carrier for mobile terminal |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1177434C (en) * | 2002-04-09 | 2004-11-24 | 华为技术有限公司 | Method for realizing multicast business based on universal land radio insertion network interface |
| KR100860581B1 (en) * | 2002-05-18 | 2008-09-26 | 엘지전자 주식회사 | Method for transmitting multicast data |
| KR20040014706A (en) * | 2002-08-10 | 2004-02-18 | 삼성전자주식회사 | Method for transmitting/receiving control message in mobile communication system serving multimedia broadcast/multicast service |
-
2004
- 2004-07-23 CN CNB2004100708473A patent/CN100444650C/en not_active Expired - Lifetime
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006034660A1 (en) * | 2004-09-30 | 2006-04-06 | Huawei Technologies Co., Ltd. | Method and apparatus of service identifying and routing in multimedia broadcast/multicast service system |
| US8325641B2 (en) | 2004-09-30 | 2012-12-04 | Huawei Technologies Co., Ltd | Method and apparatus for service identifying and routing in multimedia broadcast/multicast service system |
| CN101090392B (en) * | 2006-06-15 | 2011-12-07 | 华为技术有限公司 | Multi-service receiving method |
| WO2008034389A1 (en) * | 2006-09-18 | 2008-03-27 | Huawei Technologies Co., Ltd. | Method, system and terminal for sending and receiving multicast broadcast service |
| US8391197B2 (en) | 2006-09-18 | 2013-03-05 | Huawei Technologies Co., Ltd. | Method, system, and terminal for sending and receiving multicast broadcast service |
| CN101166350B (en) * | 2006-10-17 | 2012-07-04 | 中兴通讯股份有限公司 | Method for radio network controller to establish radio carrier for mobile terminal |
| WO2008052420A1 (en) * | 2006-10-24 | 2008-05-08 | Zte Corporation | Method for establishing, re-establishing and deleting the radio access bearer of a selected service |
| CN101170796B (en) * | 2006-10-24 | 2011-08-24 | 中兴通讯股份有限公司 | A method for establishing or reconfiguring special radio carrier in service selection |
| CN101272592B (en) * | 2007-03-21 | 2011-01-26 | 上海贝尔阿尔卡特股份有限公司 | Service scheduling device, service scheduling method and multi-community/multimedia cooperation device |
| CN101296396B (en) * | 2007-04-24 | 2010-12-08 | 中兴通讯股份有限公司 | Method for acquiring sustaining power of community multimedia broadcast multicast service |
| CN102264145A (en) * | 2010-05-31 | 2011-11-30 | 中国移动通信集团公司 | Service scheduling method, device and system |
| CN102264145B (en) * | 2010-05-31 | 2014-12-31 | 中国移动通信集团公司 | Service scheduling method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100444650C (en) | 2008-12-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1306766C (en) | Service recognition and route method in multimedia broadcast multicast service system | |
| CN1592167A (en) | Method for supporting MBMS backward compatibility | |
| CN1203695C (en) | Production of temporary mobile group designation and distribution method | |
| CN1836389A (en) | Method for paging a user equipment by using a dedicated channel in a mobile communication system supporting an mbms(multimedia broadcast/multicast service), particularly for informing the user equipme | |
| CN1496138A (en) | Transmitting/receiving controlling information method for mobile communication system | |
| CN1663151A (en) | Multimedia service providing method in a radio mobile communication system | |
| CN1736124A (en) | Provision of a multimedia broadcast/multicast service (MBMS) for a user equipment moving along cells in a cellular mobile communication system | |
| CN1653729A (en) | Method for managing multicast group in mobile communication system | |
| CN1463103A (en) | Appts. and method for transmitting control information of multimedia broadcasting/combined broadcasting affairs | |
| CN1694546A (en) | Apparatus and method for notifying transmission mode in MBMS service | |
| CN1879327A (en) | Method for transmitting messages related to a broadcast or multicast service in a cellular communications system | |
| CN1839596A (en) | Method and apparatus for transmitting and receiving MBMS packet data and control information | |
| CN1910833A (en) | Radio communication system and method | |
| CN1692578A (en) | An uplink common channel for sending feedback information | |
| CN1830162A (en) | Method for retransmitting a radio resource control connection request message in mobile communication system capable of providing a multimedia broadcast/multicast service | |
| CN1518255A (en) | Method for moving UE in RRC connection mole | |
| AU2004306053B2 (en) | Method and apparatus for providing multimedia broadcast/multicast service in mobile communication system | |
| CN1798063A (en) | Method at network side for obtaining situation of receiving multimedia broadcasting / multicasting service by users | |
| CN1536795A (en) | Method for selecting MBMS service by user | |
| CN1499853A (en) | Method for supporting services in multimedia broadcast and multicast by sharing Lu signaling connection | |
| CN1571532A (en) | Method of point-to-point and point-to-multipoint conversion in multimedia broadcasting and multicast service | |
| CN100346596C (en) | Method for activating service of multimedia broadcast/group broadcast service | |
| CN1665318A (en) | Method for introducing MBMS service identification | |
| CN101047976A (en) | Authorization failure process method and system in multimedia broadcast/multicast service | |
| CN1180639C (en) | Radio channel configuration selecting method in multicast service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CX01 | Expiry of patent term |
Granted publication date: 20081217 |
|
| CX01 | Expiry of patent term |