CN100473013C - Method for establishing context in multicast service of mobile communication system - Google Patents

Abstract

The invention discloses a method to build context in multicast service of mobile communication system, and it builds the loading context of multimedia broadcast service MBMS and the user context of MBMS by the interactive signal between SGSN and GGSN, the method includes: when the SGSN sends the requirement for building the MBMS context or refreshing MBMS context to GGSN, if itself does not have loading context, and the message will take a parameter information which is used to inform the GGSN to build or refresh the user context, and builds the loading context (if have not built), and responses GGSN to build the parameter of loading context. And the message can contain the loading ability of user device, which is used for GGSN to compare the loading ability of MBMS with required loading ability of MBMS. The invention optimizes the process for building context for multicast service.

Description

Set up contextual method in the mobile communication system multicast service

Technical field

How to the present invention relates in the mobile communication system multimedia broadcast-multicast service (MBMS:MultimediaBroadcast/Multicast Service, multimedia broadcast/multi broadcast service) more effective contextual method of MBMS of setting up.

Background technology

In order to effectively utilize mobile network resource, existing mobile communication system has proposed to use the thought of multicast and broadcast transport service, i.e. MBMS.MBMS provides the point-to-multipoint service of a data source to a plurality of users send data in the mobile network, realize that Internet resources are shared, raising utilization rate of network resource, the interface resource of especially eating dishes without rice or wine.

MBMS provides dual mode: broadcast mode and multicast mode.MBMS can not only realize the classes of messages multicast and the broadcasting of plain text low rate, and can also realize the multicast and the broadcasting of high-speed multimedia business.

Use the network architecture of MBMS under the mobile communication system, as shown in Figure 1.Multimedia broadcast/multicast service MBMS is based on the WCDMA/GSM Packet Based Network, by increasing some new functional entitys, as BM-SC (broadcast multicast service center), to existing packet domain functional entity such as SGSN (Service GSN, the packet service node, be the network element that core-network side is responsible for mobile management), GGSN (Gateway GSN, the packet gateway node, be the network element that core-network side is responsible for being linked into and sending out core net), RAN (Radio Access Network) and UE (user terminal) increase the MBMS function, and defined new logic shared channel and realized that interface-free resources shares.

Except BM-SC, all be the carrying network element of mobile communication system, finish data-transformation facility.Signaling exchange between GGSN and the BM-SC is carried out in the Gmb reference point, realizes the chain of command of MBMS, comprises following signaling:

-GGSN sets up the bearer context of MBMS and registers at BM-SC.

-GGSN or BM-SC discharge the MBMS bearer context, and GGSN goes registration at BM-SC.

-BM-SC begins and finishes to the GGSN announcement session.

In order to realize inserting the MBMS business, need a series of step and Signalling exchange, at least comprise service announcements, the user adds broadcasting or multicast group (comprises activation, registration etc.) access step, and leave and (comprise deactivation, cancellation etc.) step, in order to finish the processing of MBMS signaling and MBMS business data transmission, existing MBMS mechanism is to existing packet domain core network functional entity SGSN and GGSN, MBMS Bearer Context (bearer context) and two kinds of contexts of MBMS UEContext (user's context) have been increased, be respectively applied for record relevant information of some business and user at certain professional contextual information.

In the prior art, the foundation of MBMS UE Context is finished by the MBMS activation process.When the user need add multicast group, initiate the MBMS activation process, finish foundation at network side MBMS user's context.The foundation of MBMS Bearer context is finished by register flow path, and the register flow path trigger condition can be:

(1) RNC (radio network controller) detects the user and need insert certain MBMS business, but current network is not also set up this professional contextual information, initiates register flow path, as shown in Figure 2.

(2) user activates certain MBMS business, but the network element of network side (as SGSN or GGSN) find also not should business information up and down, just to its upstream node initiation registration message, activation process, as shown in Figure 3.

(3) in user's reorientation flow process, new SGSN find also not should business bearer context, just to GGSN initiation registration message, the reorientation flow process, as shown in Figure 4.

With reference to shown in Figure 2, the network element that can send register requirement in the register flow path that RNC initiates comprises RNC, SGSN, GGSN.Concrete steps comprise:

Step 101, the UE that detects its control as RNC are interesting to certain MBMS bearer service, and RNC SGSN under it sends MBMS login request message (MBMS RegistrationRequest).

If step 102 SGSN goes up the MBMS bearer context that does not have at this MBMS bearer service, SGSN will create a MBMS bearer context (placing ＂ Standby ＂ state), and send MBMS login request message (MBMS Registration Request) to GGSN and (carry IP multicast address, APN).

If step 103 GGSN goes up the MBMS bearer context that does not have at this MBMS bearer service, GGSN will create a MBMS bearer context (placing ＂ Standby ＂ state), and agency and transfer function transmission MBMS login request message (MBMSRegistration Request) to BM-SC (are carried IP multicast address, APN).

Step 104, when the MBMS login request message of having received from GGSN (MBMSRegistration Request), the agency of BM-SC and transfer function add the sign of GGSN in the ＂ list of downstream nodes ＂ parameter in its MBMS bearer context, and return MBMS registration reply message (MBMS Registration Response) to GGSN and (carry Temporary Mobile Group Identity TMGI, Temporary Mobile Group Identity, the MBMS bearing capacity of requirement); If this moment, the MBMS bearer context was a ＂ Active ＂ state, BM-SC just begins (Session Start) flow process to the GGSN initiation session.

If step 105 GGSN has received register requirement from SGSN in step 102, GGSN will carry out following operation:

The sign of SGSN is added in the ＂ list ofdownstream nodes ＂ parameter in its MBMS bearer context;

Return MBMS registration reply message (MBMS Registration Response) (carrying TMGI) to SGSN;

If this moment, the MBMS bearer context was a ＂ Active ＂ state, GGSN just begins (Session Start) flow process to the SGSN initiation session.

If step 106 SGSN has received register requirement from RNC in step 101, SGSN will carry out following operation:

The sign of RNC is added in the ＂ list of downstreamnodes ＂ parameter in its MBMS bearer context;

Return MBMS registration reply message (MBMS Registration Response) (carrying TMGI, the MBMS bearing capacity of requirement) to RNC;

If this moment, the MBMS bearer context was a ＂ Active ＂ state, SGSN just begins (Session Start) flow process to the RNC initiation session.

With reference to shown in Figure 3, activation process occurs in the user need add a multicast group.The step of registration in the activation process and establishment context request is finished the foundation of bearer context and user's context.Be described as follows:

If step 201 has not been set up good ground PDP Context, then UE activates a general PDP Context; The GGSN that uses is called default GGSN (Default GGSN).

Step 202, the PDP Context by acquiescence, UE to the default GGSN of network side send IGMP (IPv4) or MLD (IPv6) add message and express willingness and receive certain MBMS multicast bear business by the IP multicast address sign.

Step 203, default GGSN send the MBMS authorization requests to BM-SC, can receive data thereby require UE authorized; If Trace is activated, can comprise Trace information (additional MBMS Trace information) in this request.

Step 204, BM-SC send the MBMS authorization response to default GGSN, comprise authorization decision in the response and are used for setting up the contextual APN of MBMS UE, and authorization decision produces based on the subscription data in BM-SC member's function; If it is unsuccessful that the MBMS authorization response shows that UE authorizes, then process is ended.

Step 205, default GGSN send MBMS notice request (IP multicast address, APN, NSAPI is associated) to SGSN.The NSAPI that wherein is associated is equal with the NSAPI of acquiescence PDP Context, IP multicast address is the IP multicast address of UE when initiating to join request, APN is different from the APN of acquiescence PDP Context correspondence, that is: the GGSN (being SpecificGGSN, special GGSN) of the APN of this moment parsing may be different with the default GGSN that reception joins request; Default GGSN opens the MBMS Active Timer.

Step 206, SGSN send the MBMS push-notification-answer to the default GGSN that sends the MBMS notice request, comprise the reason that whether can carry out the MBMS context activation in the response; If expression can not be carried out the MBMS context activation in the reason, then default GGSN can not continue to send the message of relevant notice request, and process is ended.

Step 207, SGSN send " requesting activation MBMS context " (IP multicast address, APN, the NSAPI that is associated, TI) requesting activation MBMS UE context to UE.UE can be associated MBMS UE context and the acquiescence PDP Context in second step by the NSAPI that is associated; TI is selected by SGSN and its value wants different with all other PDP Contexts and the MBMS UE context of this UE activation.

Step 208, UE set up MBMS UE context and send " activating the MBMS context request " (IP multicast address, APN, MBMS_NSAPI, MBMS bearing capacity) to SGSN.Wherein IP multicast address identifies the MBMS multicast service that UE will add, APN resolves a special GGSN, the maximum QoS that MBMS bearing capacity sign UE can handle, MBMS_NSAPI is different with all other PDP Contexts and MBMS UE context that this UE activates by UE selection and its value; If had among the SGSN contextual information that should the MBMS bearer service, then it will verify the MBMS bearing capacity of UE.If the MBMS bearing capacity of SGSN checking UE is butted on the MBMS bearing capacity of requirement, then refuse request and the assignable cause of UE.

If step 209 SGSN can not set up MBMS UE context, then " the MBMS notice is refused request information, wherein comprises the reason of refusal to default GGSN transmission.

Step 210, default GGSN send response to SGSN after receiving message; Make that default GGSN can not continue to send " MBMS notice request " message, thereby process is ended.

Step 211, safety function, as: authentication UE.

If step 212, BSS race activation under the A/Gb pattern, then SGSN sends " calling Trace message " (Trace reference, Trace type, Trigger sign, OMC identify) to BSS, the Trace information that Trace reference wherein and Trace type are sent from HLR or OMC.

Step 213, after SGSN creates MBMS UE context, send " creating the contextual request of MBMS " (IP multicast address to special GGSN, APN, MBMS_NSAPI, IMSI, MSISDN, RAI, IMEI-SV, the RAT type, MS time district, GGI/SAI, the Trace reference, the Trace type, the Trigger sign, the OMC sign, additional MBMS Trance information), wherein Trace reference, the Trace type, Trigger sign and OMC identify, and to be SGSN duplicate from the Trace information that HLR or OMC send, and only exist under the situation that GGSN Trace activates, additional MBMS Trace information exists under the situation that BM-SC Trace activates.

Step 214, special GGSN send " MBMS authorization requests " (IMSI, MSISDN, RAI, IMEI-SV, RAT type, MS time district, GGI/SAI, additional MBMSTrance information) to BM-SC UE are authorized, and wherein additional MBMS Trace information exists under the situation that BM-SC Trace activates.

Step 215, BM-SC return the MBMS authorization response, have comprised authorization decision information in the MBMS authorization response, and BM-SC creates MBMS UE context.

If not about the MBMS bearer context information of certain MBMS bearer service, then special GGSN sends " MBMS register requirement " to BM-SC, sees " MBMS registration process " among the special GGSN of step 216.If there is not the TMGI that distributes, BM-SC distribution T MGI then, this TMGI passes to special GGSN and SGSN by " MBM register response " message, passes to UE by " acceptance of activation MBMS context " message.

Step 217, BM-SC send " MBMS registers response " message to special GGSN, the MBMS bearer context information that has wherein comprised corresponding certain MBMS bearer service, and increase the sign of special GGSN in " descendant node tabulation " parameter in own contextual information, see " MBMS registration process ".

Step 218, special GGSN create MBMS UE context, and send establishment MBMS context response to SGSN.

If there is not corresponding M BMS bearer context information among step 219 SGSN, then SGSN sends " MBMS register requirement " to special GGSN, sees " MBMS registration process ".

Step 220, special GGSN send " MBMS registers response " message to SGSN, wherein comprise MBMS bearer context information, increase the sign of SGSN simultaneously in GGSN " descendant node tabulation " parameter in own contextual information, see " MBMS registration process ".

If there is a PS RAB at least in step 221, then the RAN of SGSN under the Iu pattern provides MBMS UE context.

If step 222 Trace under the Iu pattern is activated, then SGSN sends " calling Trace information " message (Trace reference, Trace type, Trigger sign, OMC identify) to RAN, the Trace information that Trace reference wherein and Trace type are sent from HLR or OMC.

Step 223, SGSN to UE send " activating the MBMS context accepts " message (TMGI, MBMS bearing capacity) wherein the MBMS bearing capacity identify the maximum Qos that this MBMS bearer service uses, UE can be used as reference when professional activating other MBMS; If in the 6th step, can not verify the MBMS bearing capacity of UE, can verify at this moment; If SGSN confirms the MBMS bearing capacity of UE and is lower than the bearing capacity of requirement that then the SGSN refusal activates the contextual request of MBMS, and deactivates the MBMS UE context of having set up.

With reference to shown in Figure 4, the reorientation flow process occurs in the user and has moved to new lane place, and this lane place belongs to a new SGSN who is different from existing SGSN (abbreviating old SGSN as), in the flow process and to create context-sensitive step be register flow path and upgrade the context flow process.Be described as follows:

The SRNS reorientation is carried out in step 301, source SRNC (Source Rnc) decision.

Step 302, source SRNC send and require reorientation (Reocation Required) message to give old SGSN, initiate the reorientation set-up procedure.

Step 303, old SGSN (old SGSN) determine that from target Rnc ID the SRNS reorientation is the reorientation of SGSN intra-office or the reorientation of SGSN interoffice.If the reorientation between the SGSN SRNS is changeed re-positioning request (Forward Relocation Request) message before SGSN sends and is given new SGSN (New SGSN).In old SGSN, start a timer simultaneously.Preceding commentaries on classics RELOCATION REQUEST message only is applicable to the reorientation situation between the SGSN SRNS.If MS has added multicast service, old SGSN is with MBMS UE context in preceding commentaries on classics RELOCATION REQUEST message (Forward RelocationRequest).

Step 304, new SGSN send RELOCATION REQUEST message asks to set up RAB to Target RNC (Target RNC).

Step 305, Target RNC (Target RNC) should send the re-positioning request acknowledge message to new SGSN.

Step 306, the user data between Target RNC (Target RNC) and new SGSN transmit resource distributes, and the reorientation that new SGSN has been SRNS is ready, changes relocation response message to old SGSN before then new SGSN sends.Preceding commentaries on classics relocation response message only is applicable to the reorientation of SGSN SRNS inside.If new SGSN supports MBMS, then its MBMS of indication supports situation in preceding commentaries on classics relocation response message (Forward Relocation Response).

Step 307, old SGSN send the reorientation order to source SRNC, continue the reorientation of SRNS.

Step 308, source SRNC are subjected to the RAB of data forwarding restriction to begin to transmit data.

Step 309, receive the reorientation command messages from old SGSN after, source RNC answers the log-on data repeating timer.When the reorientation set-up procedure successfully stops, and SRNC is ready, and source SRNC sends repositioning submission information (SRNS context) and gives Target RNC, triggers the execution of SRNS reorientation.

Step 310, when receiving reorientation when carry out triggering, Target RNC should send the reorientation supervisory messages to new SGSN.To the SRNS reorientation type of " not relating to UE ", it is acceptance to from the repositioning submission information of Iur interface that reorientation carry out to trigger; When the reorientation supervisory messages was sent out, Target RNC should start the SRNC operation.

After step 311, the transmission relocation detect-message, target SRNC sends the RAN mobile message to MS.

Step 312, MS return the affirmation of RAN mobile message for target SRNC.

Step 313, target SRNC finish message to new SGSN initiation reorientation complete process by sending reorientation.The purpose of reorientation complete process is to show finishing of SRNS reorientation by target SRNC to CN.

Change reorientation before step 314, new SGSN send for old SGSN and finish message, notify finishing of old SGSN repositioning process.

Change reorientation before step 315, old SGSN return for new SGSN and finish acknowledge message.

Step 316, new SGSN send the request of renewal PDP Context for default GGSN (Default GGSN).

Step 317, default GGSN return renewal PDP Context response message for new SGSN.

If the SGSN that step 318 is new supports MBMS, it detects at each MBMS UE context of receiving whether corresponding MBMS bearer context is arranged.For each MBMS bearer context that does not also exist in SGSN, SGSN creates a MBMS bearer context (placing ＂ Standby ＂ state), and initiates the MBMS register flow path.

Step 319, old SGSN send Iu release request for source Rnc.

Step 320, source Rnc can return the Iu Release complete to SGSN.

If step 321 is not supported MBMS in new SGSN indication, SGSN originally is by initiating all the MBMS UE context deexcitations with UE among SGSN, GGSN and the BM-SC of deexcitation flow process.

If the old SGSN of step 322 no longer includes the ＂ list of downstream nodes ＂ of MBMS UE context and corresponding MBMS bearer context for empty on this MBMS bearer service, then SGSN initiates the MBMS logout flow path.

If the SGSN that step 323 is new supports MBMS, for each MBMS UE context of receiving in step 3, new SGSN sends update MBMS UE context request message to relevant GGSN and (carries service network identification, MS Time Zone, CGI/SAI, RAT Type, additional MBMS tracked information).

Step 324, GGSN upgrade the contextual appropriate section of these MBMS UE, and return update MBMS UE context response information; Service network identification after GGSN will upgrade sends to BM-SC.Whether need to comprise CGI/SAI, then carry out according to the rule that is defined in definition in the 3GPP TS 23.060 15.1.1a joint.

If step 325 GGSN receives additional MBMS tracked information new or that upgrade from new SGSN, GGSN sends one and activates trace message to BM-SC.

After step 326, reorientation flow process were finished, follow-up needs were finished a routing update process.Do not support the SGSN of MBMS to accept not indicate in the message support of MBMS characteristic at routing region updating.On the other hand, if SGSN supports MBMS, accept the message indication network to the routing region updating of UE and support MBMS.

Can see by above-mentioned trigger condition and flowchart process, in SGSN and GGSN, at some MBMS business, in the same flow process, the foundation of MBMS bearer context and MBMS user's context all need to set up, and two contextual foundation are two relatively independent processes, the problem of Cun Zaiing is like this, after a context foundation is finished, when failure set up in another context, will delete that and just set up context well.

Such as in the reorientation flow process, new SGSN sends the update MBMS user's context to special GGSN, if there is not this context in special GGSN, causes upgrading failure, finish the MBMS bearer context if SGSN this moment has just set up, just may cause the deletion of this MBMS bearer context.

Again such as in the MBMS activation process, SGSN has passed through to special GGSN transmission establishment MBMS user's context message establishing the MBMS user's context, if new SGSN does not also have the bearer context of this MBMS business, then need to set up the MBMS bearer context by initiating register flow path, after foundation is finished, SGSN obtains professional needed bearing capacity, compare with the bearing capacity of UE, the bearing capacity of finding UE has problem, will comprise this user's context of GGSN to the MBMS user's context deletion of having set up.If activate this MBMS business and this user is first, might nullify the bearer context of having set up accordingly.

In sum, the bearer context of MBMS is set up by different flow processs respectively with user's context, and relatively independent, the problem that causes like this is:

1, finish a context foundation, another context is set up under the situation of failure, just may delete that and just set up context well;

2, for the inspection of the MBMS bearing capacity of the MBMS bearing capacity of UE and requirement, only be placed on the SGSN and check, may cause the meaningless foundation of context.

Summary of the invention

Above-mentioned technical problem to be solved by this invention is to provide sets up contextual method in a kind of mobile communication system multicast service, avoid finishing a context foundation, and another context is set up when failing, may delete that and just set up good contextual situation, and avoid the meaningless foundation of context.

For solving the problems of the technologies described above, the invention provides and set up contextual method in a kind of mobile communication system multicast service, by the Signalling exchange between packet service node SGSN and the packet gateway node GGSN, set up multimedia broadcast-multicast service MBMS bearer context and MBMS user's context, this method comprises:

When GGSN sends establishment or update MBMS user's context message, if SGSN does not also have relevant bearer context, then increase an indication parameter at SGSN in establishment or updating message, indication does not have the MBMS bearer context at SGSN;

After GGSN receives described establishment or updating message, when finishing establishment or update MBMS user's context, if detect effective described indication parameter, think that then SGSN does not have and need establishment MBMS bearer context, be equal to the register requirement of receiving that SGSN sends to GGSN;

If GGSN does not have corresponding bearer context yet, then described indication parameter triggers GGSN and sends register requirement to broadcast multicast service center BM-SC, finishes the foundation of the bearer context of GGSN and BM-SC;

If GGSN has set up the relevant bearer context, then GGSN, carries SGSN and creates the bearer context parameters needed in the response message of establishment that sends to SGSN or update MBMS user's context according to this indication parameter;

SGSN finishes the foundation of bearer context according to the establishment bearer context parameters needed of carrying in the response message of receiving.

In the said method, described indication parameter comprises a new instruction parameter, perhaps an existing functional parameter with indicative function.

Wherein, indication parameter comprises an existing functional parameter with indicative function, and further, described indication parameter comprises the MBMS bearing capacity parameter of subscriber equipment, is used for bearing capacity and compares and the double action of indicating; After GGSN receives described establishment or updating message, further comprise: if detect the MBMS bearing capacity parameter of the subscriber equipment in this message, then in the MBMS bearer context that GGSN sets up, take out the MBMS bearing capacity that requires, and compare with the MBMS bearing capacity of subscriber equipment, if the MBMS bearing capacity of subscriber equipment is lower than the MBMS bearing capacity of requirement, then GGSN makes the MBMS user's context and creates the failure processing, and by response message notice SGSN.

Further, method of the present invention, its SGSN that carries in the response message of establishment that sends to SGSN or update MBMS user's context creates the bearer context parameters needed, comprises Temporary Mobile Group Identity TMGI.

Further, method of the present invention, its described indication parameter only just is not changed to effectively under SGSN has the situation of MBMS bearer context.

Utilize the present invention, can avoid as much as possible, finished, when failure set up in another context, may delete that and just set up good contextual situation if a context is set up for MBMS user's context and bearer context; Between SGSN and GGSN, the signaling message that activates MBMS user's context and register flow path is united two into one simultaneously, saved the Internet resources between SGSN and the GGSN, also accelerated to activate the process of MBMS user's context, improved user experience.

Description of drawings

Fig. 1 is the network architecture schematic diagram that uses MBMS under the mobile communication system;

Fig. 2 is a register flow path schematic diagram of the prior art;

Fig. 3 is an activation process schematic diagram of the prior art;

Fig. 4 is a reorientation schematic flow sheet of the prior art;

Fig. 5 is according to the activation process schematic diagram after the described improvement of the embodiment of the invention;

Fig. 6 is according to the reorientation schematic flow sheet after the described improvement of the embodiment of the invention.

Embodiment

Be described in further detail below in conjunction with the execution mode of accompanying drawing technical scheme of the present invention:

The present invention is directed to multicast service, propose: send to GGSN at SGSN and create or during update MBMS user's context message, if SGSN does not also have relevant bearer context, will in establishment or updating message, increase an indication parameter, the concrete feature of the effect of this parameter and content comprises:

GGSN detects this indication parameter, is equal to receive SGSN to the register requirement that GGSN sends, and represents that promptly SGSN does not have and needs are created the MBMS bearer context;

If GGSN does not have corresponding bearer context yet, then this parameter triggers GGSN and sends register requirement to BM-SC, finishes the foundation of the bearer context of GGSN and BM-SC;

If GGSN has set up the relevant bearer context, then this parameter indication GGSN carries SGSN and creates the bearer context parameters needed in the response message of establishment that returns to SGSN or update MBMS user's context, as TMGI etc.; Simultaneously the function of other registration aspects is still carried out, and as GGSN the sign of SGSN is added in the ＂ list ofdownstream nodes ＂ parameter in its MBMS bearer context; If this moment, the MBMS bearer context was a ＂ Active ＂ state, GGSN just begins (Session Start) flow process to the SGSN initiation session.

This parameter can be a new instruction parameter, is included in the parameter list of message, or in the extension header of GTP (GPRS Tunnelling Protocol, GPRS Tunnel Protocol) signaling message.

This parameter only just is changed to effective under SGSN does not have the situation of MBMS bearer context.

This parameter has and can be substituted by other existing functional parameter, finishes deixis, is used as the double action that bearing capacity compares and indicates as the MBMS bearing capacity parameter that comprises UE in the message;

If promptly comprised instruction parameter in the message, also comprised other functional parameter, then be as the criterion with instruction parameter.

This parameter can comprise the MBMS bearing capacity parameter of UE.If GGSN detects the MBMS bearing capacity parameter of UE in establishment that receives or updating message, then the step of the comparison of bearing capacity can be placed on the GGSN and finish, promptly after GGSN has set up the MBMS bearer context, from the MBMS bearer context, take out the MBMS bearing capacity that requires, compare with the MBMS bearing capacity of UE, be lower than the MBMS bearing capacity of requirement if find the MBMS bearing capacity of UE, just directly in establishment that returns to SGSN or renewal response message, tell SGSN to do failure and handle.

Particularly, at SGSN when GGSN send to create MBMS context or update MBMS context request message, if self does not have bearer context, parameter information on just in message, being with, when being used to inform GGSN foundation or upgrading user's context, finish the foundation (if also not setting up) of bearer context, and response SGSN sets up the required parameter of bearer context, the bearing capacity that also may comprise UE simultaneously in the message, be used for GGSN and compare the MBMS bearing capacity of UE and the MBMS bearing capacity of requirement, be lower than the MBMS bearing capacity of requirement if find the MBMS bearing capacity of UE, then GGSN makes the MBMS user's context and creates the failure processing, echoes to SGSN simultaneously and answers message to tell the failure of SGSN do to handle.

Further specify the present invention by two specific embodiments:

Specific embodiment one: MBMS activation process

As shown in Figure 5, this flow process occurs in the user need insert certain business based on MBMS, and network side is not also set up the relevant bearer context information of this business, and at this moment the network element SGSN of network side finishes the foundation of bearer context by creating user's context message.

The description of step 201-212 in step 401-412, same " background technology " in Fig. 3 activation process.

After step 413, SGSN create MBMS UE context, send " creating the request of MBMS user's context " to special GGSN (SpecificGGSN), have in the request and create the required parameter of user's context, and create the indication parameter of bearer context and the MBMS bearing capacity parameter of UE.

Step 414, whether special GGSN checks corresponding M BMS bearer context, if the MBMS bearer context is arranged, take out the MBMS bearing capacity that requires, compare with the MBMS bearing capacity of UE, be lower than the MBMS bearing capacity of requirement if find the MBMS bearing capacity of UE, then directly echoing to SGSN answers message to tell SGSN to do the failure processing, if being higher than the MBMS bearing capacity or the special GGSN of requirement, the MBMS bearing capacity of UE do not have corresponding M BMS bearer context, then BM-SC sends " MBMS authorization requests " (IMSI, MSISDN, RAI, IMEI-SV, the RAT type, MS time district, GGI/SAI, additional MBMS Trance information) UE is authorized, wherein additional MBMS Trace information exists under the situation that BM-SC Trace activates.

Step 415, BM-SC respond the GGSN authorization response, have comprised authorization decision information in the response, and BM-SC creates MBMS UE context.

If not about the MBMS bearer context information of certain MBMS bearer service, then GGSN sends " MBMS register requirement " to BM-SC among step 416 GGSN.

Step 417, BM-SC respond " MBMS registers response " message to GGSN, and the MBMS bearer context information such as the bearing capacity that have comprised corresponding certain MBMS bearer service in the message require parameter and TMGI.TMGI will pass to UE by " activating the MBMS context accepts " message.Increase the sign of GGSN in BM-SC " descendant node tabulation " parameter in own contextual information, see " MBMS registration process ".

The bearing capacity of step 418, GGSN comparison terminal and the bearing capacity of business need if the bearing capacity of terminal is enough, are then created MBMS UE context, and send establishment MBMS context response to SGSN.Comprised TMGI in the response, and the information of having finished bearer context is set up in expression.After receiving, finishes SGSN the foundation of the bearer context of self.

If there is a PS RAB at least in step 419, then the RAN of SGSN under the Iu pattern provides MBMS UE context.

If step 420 Trace under the Iu pattern is activated, then SGSN sends " calling Trace information " message (Trace reference, Trace type, Trigger sign, OMC identify) to RAN, the Trace information that Trace reference wherein and Trace type are sent from HLR or OMC.

Step 419, SGSN send " activating the MBMS context accepts " message (TMGI, MBMS bearing capacity) to UE.

Specific embodiment two: MBMS reorientation flow process

As shown in Figure 6, present embodiment has been optimized new SGSN and GGSN sets up the contextual step of MBMS alternately.

Step 501-517, with the description among the step 301-317 among Fig. 4 in the background technology.

If the SGSN that step 518 is new supports MBMS, for each MBMS UE context of receiving in step 3, new SGSN sends update MBMS user's context request message (except that original parameter, adding indication parameter) to relevant special GGSN (Specific GGSN).

Step 519, special GGSN upgrade the appropriate section of these MBMS user's contexts, if detected effective indication parameter, then special GGSN finishes the registering functional of new SGSN node, and in returning update MBMS UE context response information, comprise the needed information of bearer context of creating, as TMGI etc.Service network identification after special GGSN will upgrade sends to BM-SC.Whether need to comprise CGI/SAI, then carry out according to the rule that is defined in definition in the 3GPP TS 23.060 15.1.1a joint.If special GGSN update MBMS user's context failure is perhaps finished the registering functional failure to new SGSN, then special GGSN echoes to SGSN and answers message to tell SGSN to do the failure processing.

Step 520, old SGSN send Iu release request for source Rnc.

Step 521, source Rnc can return the Iu Release complete to SGSN.

If step 522 is indicated at new SGSN of the 3rd step and do not supported MBMS, SGSN originally is by initiating all the MBMS UE context deexcitations with UE among SGSN, GGSN and the BM-SC of deexcitation flow process.

If the original SGSN of step 523 no longer includes the ＂ list of downstream nodes ＂ of MBMSUE context and corresponding MBMS bearer context for empty on this MBMS bearer service, then SGSN initiates the MBMS logout flow path.

If step 524 GGSN receives additional MBMS tracked information new or that upgrade from new SGSN, GGSN sends one and activates trace message to BM-SC.

Step 525, do not support the SGSN of MBMS to accept not indicate in the message support of MBMS characteristic at routing region updating.On the other hand, if SGSN supports MBMS, accept the message indication network to the routing region updating of UE and support MBMS.

Though the present invention discloses as above with preferred embodiment; right its is not in order to limit the present invention; any person skilled in the art; without departing from the spirit and scope of the invention; when can doing a little change and retouching, so the present invention's protection range attached claim person of defining after looking is as the criterion.

Claims (6)

1, sets up contextual method in a kind of mobile communication system multicast service, by the Signalling exchange between packet service node SGSN and the packet gateway node GGSN, set up multimedia broadcast-multicast service MBMS bearer context and MBMS user's context, it is characterized in that, comprising:

When GGSN sends establishment or update MBMS user's context message, if SGSN does not also have relevant bearer context, then increase an indication parameter at SGSN in establishment or updating message, indication does not have the MBMS bearer context at SGSN;

After GGSN receives described establishment or updating message, when finishing establishment or update MBMS user's context, if detect effective described indication parameter, think that then SGSN does not have and need establishment MBMS bearer context, be equal to the register requirement of receiving that SGSN sends to GGSN;

If GGSN does not have corresponding bearer context yet, then described indication parameter triggers GGSN and sends register requirement to broadcast multicast service center BM-SC, finishes the foundation of the bearer context of GGSN and BM-SC;

If GGSN has set up the relevant bearer context, then GGSN, carries SGSN and creates the bearer context parameters needed in the response message of establishment that sends to SGSN or update MBMS user's context according to this indication parameter;

SGSN finishes the foundation of bearer context according to the establishment bearer context parameters needed of carrying in the response message of receiving.

2, the method for claim 1 is characterized in that, described indication parameter comprises an existing functional parameter with indicative function.

3, method as claimed in claim 2 is characterized in that, described indication parameter comprises the MBMS bearing capacity parameter of subscriber equipment, is used for bearing capacity and compares and the double action of indicating.

4, method as claimed in claim 3, it is characterized in that, after GGSN receives described establishment or updating message, further comprise: if detect the MBMS bearing capacity parameter of the subscriber equipment in this message, then in the MBMS bearer context that GGSN sets up, take out the MBMS bearing capacity that requires, and compare with the MBMS bearing capacity of subscriber equipment, if the MBMS bearing capacity of subscriber equipment is lower than the MBMS bearing capacity of requirement, then GGSN makes the MBMS user's context and creates the failure processing, and by response message notice SGSN.

5, the method for claim 1 is characterized in that, the SGSN that carries in the response message of establishment that sends to SGSN or update MBMS user's context creates the bearer context parameters needed, comprises Temporary Mobile Group Identity TMGI.

6, the method for claim 1 is characterized in that, described indication parameter only just is not changed to effectively under SGSN has the situation of MBMS bearer context.

Images