CN1960301A

CN1960301A - Method for activating multicast service

Info

Publication number: CN1960301A
Application number: CNA2005101183922A
Authority: CN
Inventors: 张鹏; 段昌
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2005-10-31
Filing date: 2005-10-31
Publication date: 2007-05-09
Anticipated expiration: 2025-10-31
Also published as: CN100411377C

Abstract

The method comprises: adding communication interface between PDG and BM-SC, and sending the request of enabling the multicast service to PDG in order to inform that the PDG itself wants to participate the multicast service; the PDG sends MBMS authorization request to BM-SC; after BM-SC receives the MBMS authorization request, it put the success or failure message of authorization into the MBMS authorization response message that is returned to the PDG; after PDG receives the MBMS authorization response message, if detecting the success authorization indication from the MBMS authorization response message, it sends the multicast service enable acceptance message; otherwise, it send the multicast service reject enable message to UE. The invention implements the enable of IWLAM-based multicast service.

Description

A kind of method for activating multicast service

Technical field

The present invention relates to the activation of service technical field, be specifically related to the method for activating multicast service under a kind of intercommunicated wireless local area network framework.

Background technology

Development along with mobile communication technology, 3G (Third Generation) Moblie can provide the data, services than second generation mobile communication higher rate, thereby can support the multiple business form, as services such as visual telephone, picture download, high speed browsing internet can be provided, and wherein have a class business features to be: such business can have been subscribed to such business in wireless network all users send simultaneously, as: weather forecast, news film, the sports tournament collection of choice specimens etc.The characteristics of utilizing such business to send simultaneously, 3-G (Generation Three mobile communication system) has been introduced the notion of broadcast/group broadcast from Re1-6, more effectively utilizing limited air interface resource, thereby provides higher power system capacity.

In the system architecture of broadcasting/packet service, for an intermediate node, no matter this intermediate node comprises the downstream site what expectations receive data, and the superior node of this intermediate node always sends a piece of data to this intermediate node; After this intermediate node is received data, the quantity that receives the downstream site of data according to expectation is duplicated this data, and distribute this data to downstream site that each expectation receives these data, like this, all have only a piece of data to transmit in each bar branch of broadcasting/packet service transfer of data tree, take a transfer resource, the transfer of data of root node and its downstream site also is like this.The distinctive points of multicast service transmission and broadcast traffic transmissions only is: multicast service only sends to subscribing to this professional user, and the broadcasting service then user of all in wireless network sends.As seen, can provide identical services to a plurality of users simultaneously by broadcast/multicast service system, thereby can greatly save Internet resources.

Third generation partner program (3GPP) has provided the block architecture diagram of the wireless network of support multimedia broadcast/group broadcast service (MBMS), as shown in Figure 1, support the wireless network of MBMS to comprise: broadcast/multicast service center (BM-SC), Gateway GPRS Support Node (GGSN), Serving GPRS Support Node (SGSN), universal mobile telecommunications system land radio access web (UTRAN) and/or global system for mobile communications strengthen wireless access network (GERAN), user terminal (UE), and GGSN and SGSN belong to the interior node of core net (CN) of wireless network.Wherein, BM-SC links to each other with GGSN by Gmb interface or Gi interface, and a BM-SC can link to each other with a plurality of GGSN; GGSN links to each other with SGSN by the Gn/Gp interface, and a GGSN can link to each other with a plurality of SGSN; SGSN links to each other with UTRAN by the Iu interface, and UTRAN links to each other with UE by the Uu interface; In addition, SGSN also can link to each other with GERAN by the Iu/Gb interface, and GERAN links to each other with UE by Um Interface again.

BM-SC is used to MBMS user to provide service concurrence to send business, can be used as the access point that MBMS content delivery, the mandate of MBMS content and MBMS bearer service are initiated in the public land mobile net (PLMN), and can be used for the scheduling of MBMS transmission and the transmission of MBMS.

BM-SC is a necessary functional entity realizing the MBMS business, and its function mainly comprises: member's function, session and sending function, agency and transfer function, professional declaration function and safety function.

Under the MBMS wireless network architecture of 3GPP definition, the flow process of activating multicast service as shown in Figure 2, its concrete steps are as follows:

Step 201:UE sends the multicast service that multicast listener discovery (MLD) agreement of the Internet Group Management Protocol (IGMP) of IPv4 definition or IPv6 definition supports by packet data protocol (PDP) context that activated, acquiescence to GGSN and adds message, and this multicast service adds message and carries the multicast service identifier that will add as IP multicast address etc.

Step 202:GGSN sends MBMS authorization requests (MBMS Authorization Request) message to BM-SC after receiving that multicast service adds message, and BM-SC self will obtain the mandate that makes the UE receiving multicast business with notice.

After step 203:BM-SC receives the MBMS authorization request message, return MBMS authorization response (the MBMS Authorization Response) message of carrying mandate success or failure information to GGSN.

BM-SC can be according to the CAMEL-Subscription-Information of the UE that self preserves, and whether decision authorizes to UE.

Member's function will authorize success or failure information and APN (APN) information to be included in the MBMS authorization response message, calculate the MBMS authorization response message is returned to GGSN, create MBMS UE context to be used for GGSN.

After step 204:GGSN receives the MBMS authorization response message of authorization by direction success, send MBMS notice request (MBMS Notification Request) message to SGSN, this MBMS notification request message comprises the Netscape Internet Server Application Programming Interface Internet (NSAPI) of IP multicast address, APN, connection etc.

Wherein, the NSAPI of connection is for sending the pairing NSAPI of PDP Context that multicast service adds message; The APN possibility is resolved to be a GGSN.

When GGSN sends the MBMS notification request message, start a MBMS Active Timer.If this Active Timer is overtime, do not receive response yet from SGSN, then send refusal and add message to UE, this flow process finishes.

If the MBMS authorization response message authorization by direction that GGSN receives failure, then GGSN sends refusal adding message to UE, and this flow process finishes.

After step 205:SGSN receives the MBMS notification request message, return MBMS push-notification-answer (MBMS Notification Response) message to GGSN, wherein whether indication MBMS context activation can be processed in the cause parameter of this MBMS push-notification-answer message.

If the failure of the cause parameter authorization by direction in the MBMS push-notification-answer message, then GGSN no longer sends the MBMS notification request message to SGSN, and adds message to UE transmission refusal, and this flow process finishes.

Step 206:SGSN sends request MBMS context activation (Request MBMSContext Activation) message to UE, activates MBMS UE context with request UE.

This request MBMS context activation message is carried NSAPI, Transaction Identifier (TI) of IP multicast address, APN, connection etc.

Step 207:UE creates a MBMS UE context after receiving request MBMS context activation message, and sends activation MBMS context request (Activate MBMS ContextRequest) message to SGSN.

After step 208:SGSN receives and activates the MBMS context request message, to UE carry out safety function as: UE is authenticated.Afterwards, SGSN creates MBMS UE context, and sends establishment MBMS context request (Create MBMS Context Request) message to GGSN.

This activation MBMS context request message is carried IP multicast address, APN, MBMS bearing capacity.Wherein, the MBMS bearing capacity that MBMS bearing capacity indication UE supports, if this moment, SGSN has preserved the pairing MBMS bearer context of multicast service that UE will add, then whether the MBMS bearing capacity supported of the SGSN MBMS bearing capacity checking UE that just can require according to the multicast service that the UE that comprises in this MBMS bearer context information will add meets the demands, if do not satisfy, then return MBMS notice refusal request (MBMS Notification Reject Request) message to the GGSN that sends the MBMS notification request message, to prevent that GGSN from continuing to send the MBMS notification request message, after GGSN receives MBMS notice refusal request message, return MBMS notice refusal response (MBMS Notification Reject Response) message to SGSN, SGSN returns to UE and activates MBMS context refuse information simultaneously, and this flow process finishes.

Create the MBMS context request message and carry IP multicast address, APN, international mobile subscriber identifier (IMSI) etc.

Step 209:GGSN sends the MBMS authorization request message to BM-SC, to obtain the mandate to the UE that is activating after receiving and creating the MBMS context request message.

The MBMS authorization request message is carried IMSI etc.

After step 210:BM-SC receives the MBMS authorization request message, return the MBMS authorization response message of carrying mandate success or failure information to GGSN, simultaneously, if authorize successfully, BM-SC creates MBMS UE context.

After step 211:GGSN receives the MBMS authorization response message of authorization by direction success, create MBMS UE context, and send establishment MBMS context response (Create MBMSContext Response) message to SGSN.

After GGSN receives the MBMS authorization response message of authorization by direction success, the MBMS bearer context of not preserving the multicast service that will add if detect self at UE, then send MBMS register requirement (MBMS Registration Request) message to BM-SC, after BM-SC receives the MBMS login request message, also do not distribute interim horde group id (TMGI) if detect self for this multicast service, then distribute a new TMGI for this multicast service, and this TMGI can be sent to GGSN and SGSN by MBMS registration response (MBMS Registration Response) message, further, this TMGI is sent to UE by activating MBMS context acceptance (Activate MBMS ContextAccept) message.

The MBMS registration reply message also comprises the MBMS bearer context at this multicast service, the sign that comprises the GGSN that initiates the MBMS register requirement in this MBMS bearer context, and the BM-SC GGSN that will initiate the MBMS register requirement identifies in the downstream node list parameter of the MBMS bearer context that joins self preservation.After GGSN receives the MBMS registration reply message, create MBMS UE context.

After step 212:SGSN receives and creates the MBMS context response information, send activation MBMS context to UE and accept (Activate MBMS Context Accept) message.

After SGSN receives the MBMS context response information, the MBMS bearer context of not preserving the multicast service that will add if detect self at UE, then initiate the MBMS login request message to GGSN, after GGSN receives the MBMS login request message, return the MBMS registration reply message to SGSN, this MBMS registration reply message comprises the MBMS bearer context at this multicast service, the sign that comprises the SGSN that initiates register requirement in this MBMS bearer context, simultaneously, the GGSN SGSN sign that will initiate register requirement joins in the downstream node list parameter of the MBMS bearer context of self preserving.After SGSN receives the MBMS registration reply message, self be at least this UE and set up a packet domain (PS) RAB (RAB) if detect this moment, then the wireless access network (RAN) to the Iu pattern provides MBMS UE context.

The MBMS context is accepted message and is carried TMGI, MBMS bearing capacity.The MBMS bearing capacity that the multicast service that MBMS bearing capacity indication carrying UE will add requires, when UE had activated more MBMS bearer service, the MBMS bearing capacity can be included into the scope of consideration.If in step 208, do not verify the MBMS bearing capacity of UE, just can verify the MBMS bearing capacity of UE this moment.If SGSN judges MBMS bearing capacity that UE supports and is lower than the MBMS bearing capacity that multicast service that carrying UE will add requires, SGSN sends to UE and activates MBMS context refuse information, and return Reason For Denial, SGSN initiates the deexcitation flow process simultaneously, the MBMS UE context of having set up is carried out deexcitation, and this flow process finishes.

From the above mentioned, the activating multicast service flow process in the existing MBMS system, all at the GPRS/UMTS system design, the Access Network of consideration is GERAN/UTRAN, operation flow also relates at GERAN/UTRAN and SGSN-GGSN framework.

Along with the user is more and more higher to the requirement of wireless access rate, wireless lan (wlan) arises at the historic moment, and it can provide wireless data access at a high speed in more among a small circle.Its basic structure all is to utilize access point (AP) to finish the wireless access of UE, connects to form transmission network by network control and connection device.Along with the rise and the development of WLAN technology, WLAN and various wireless mobile communication network as: the intercommunication of GSM, code division multiple access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) (WCDMA) system, time division duplex-S-CDMA (TD-SCDMA) system, CDMA2000 system is just becoming the emphasis of current research.

In 3GPP standardization body, UE can link to each other with internet (Internet), Intranet (Intranet) by the access network of WLAN, also can be connected with the home network of 3GPP system or the visit net of 3GPP system via the WLAN Access Network.As shown in Figure 3, WLAN UE is under non-roaming situation, as follows with the intercommunication framework of 3GPP home network: WLAN UE links to each other with WLAN IAD (WAG), authentication and authorization charging (AAA) server in the 3GPP home network via WLAN Access Network (AN), and WLAN UE directly links to each other with packet data gateway (PDG) in the 3GPP home network.Shown in Fig. 4 a, WLAN UE is when roaming, WAG, the AAA agency who visits in the net via WLAN AN and 3GPP links to each other, and the part entity in the 3GPP visit net again respectively with the 3GPP home network in the corresponding entity interconnection, as AAA agency and the aaa server in the 3GPP home network in: the 3GPP visit net link to each other, the WAG of 3GPP visit in netting links to each other with PDG in the 3GPP home network etc., while WLAN UE directly links to each other with PDG in the 3GPP home network; Shown in Fig. 4 b, WLAN UE is when roaming, also can link to each other via WAG, the AAA agency in WLAN AN and the 3GPP visit net, and directly link to each other with PDG in the 3GPP visit net, the AAA during 3GPP visit is simultaneously netted acts on behalf of with aaa server in the 3GPP home network and links to each other.Network after WLAN and the intercommunication of 3GPP system is called interworking WLAN (I-WLAN).

As can be seen, as a kind of broadband access technology, WLAN can provide the data, services of higher rate, shows the advantage of MBMS better to the user, and therefore, it is very necessary that MBMS is introduced WLAN.In the prior art, do not provide with WLAN, under the I-WLAN framework, how to realize the solution of the activating multicast service among the MBMS as Access Network.

Summary of the invention

In view of this, main purpose of the present invention is to provide a kind of method for activating multicast service, to realize the activating multicast service under the I-WLAN framework.

For achieving the above object, technical scheme of the present invention is achieved in that

A kind of method for activating multicast service is provided with communication interface between PDG and BM-SC, this method comprises:

A, UE send the message of requesting activation multicast service to PDG;

After B, PDG receive the message of requesting activation multicast service, send the MBMS authorization request message to BM-SC;

After C, BM-SC receive the MBMS authorization request message, the multicast service identifier that gets access to according to self will be authorized success or failure information to be carried in the MBMS authorization response message and returned to PDG;

After D, PDG receive the MBMS authorization response message, judge whether this MBMS authorization response message carries the mandate successful information, if send activating multicast service to UE and accept message; Otherwise, send the activating multicast service refuse information to UE.

The described PDG of step D judges that this MBMS authorization response message is carried and authorizes after the successful information, further comprises before creating MBMS UE context:

PDG sends request MBMS context activation message to UE, and UE creates MBMS UE context after receiving request MBMS context activation message, returns to PDG afterwards and activates the MBMS context request message.

Between BM-SC and aaa server, communication interface is set,

And the described PDG of step B sends the MBMS authorization request message to BM-SC and is specially: PDG is sent to aaa server with the MBMS authorization request message earlier, and aaa server is sent to BM-SC with the MBMS authorization request message by described interface afterwards;

And the described BM-SC of step C returns to PDG with the MBMS authorization response message and is specially: BM-SC is back to aaa server with the MBMS authorization response message by described interface earlier, and aaa server is back to PDG with the MBMS authorization response message afterwards.

Described BM-SC with the MBMS authorization response message be back to after the aaa server, aaa server further comprises before the MBMS authorization response message is back to PDG:

Aaa server judges whether the MBMS authorization response message carries the mandate successful information, if, create MBMS UE context according to the MBMS bearer context of self preserving, simultaneously the MBMS authorization response message is back to PDG; Otherwise, directly authorization response message is back to PDG.

The MBMS bearer context that described aaa server self is preserved is that BM-SC is deployed on the aaa server in advance.

Described aaa server is judged that the MBMS authorization response message is carried and is authorized after the successful information, further comprises before creating MBMS UE context:

Aaa server judges whether self preserves the MBMS bearer context, if preserve, then creates MBMS UE context according to this MBMS bearer context; Otherwise, obtain the MBMS bearer context to BM-SC, and create MBMS UE context according to the MBMS bearer context that gets access to.

Described aaa server obtains the MBMS bearer context to BM-SC and is specially:

Aaa server sends login request message to BM-SC, after BM-SC receives this login request message, the MBMS bearer context is carried at returns to aaa server in the registration reply message.

Aaa server preserves WLAN AN in advance and/or WAG is used to create the contextual information indication of MBMS UE,

Described BM-SC further comprises after the MBMS authorization response message is back to aaa server:

Aaa server detects the MBMS authorization response message and carries the mandate successful information, then be used to create the contextual information indication of MBMS UE, the WLAN AN of the correspondence of self preserving and/or WAG be used to create the contextual information of MBMS UE send to WLAN AN and/or WAG according to described WLAN AN and/or WAG.

Described UE roams,

And described aaa server is used for WLAN AN and/or WAG to create, and the contextual information of MBMS UE sends to WLAN AN and/or WAG is specially: aaa server is used to create the AAA agency that the contextual information of MBMS UE is sent to place, UE roaming back accesses network with WLAN AN and/or WAG, and the AAA agency is used to create the contextual information of MBMS UE with this WLAN AN and/or WAG and sends to WLAN AN and/or WAG afterwards.

Described aaa server receives after the MBMS authorization response message, further comprise before the MBMS authorization response message is back to PDG:

Aaa server judges whether the MBMS authorization response message carries the mandate successful information, if carry, continue to judge whether MBMS bearing capacity that the UE that self preserves supports satisfies the MBMS bearing capacity that multicast service that UE that the MBMS bearer context of self preservation comprised will add requires, if satisfy, directly will carry and authorize the MBMS authorization response message of successful information to be back to PDG; If do not satisfy, the not enough information of UE bearing capacity is back to PDG with authorizing successful information to be carried in the MBMS authorization response message; If do not carry, the MBMS authorization response message that directly will carry authorization failure information is back to PDG;

And the described PDG of step D judges that the MBMS authorization response message is carried and authorizes after the successful information, further comprises before creating MBMS UE context: PDG judges whether authorization response message comprises UE bearing capacity deficiency information, if comprise, then judge whether proceed activating multicast service according to pre-defined rule, if should, then send activating multicast service and accept message to UE; If not should, then send the activating multicast service refuse information to UE.

The described UE of steps A further comprises after PDG sends the message of carrying multicast service identifier: UE sends the MBMS bearing capacity of self supporting to aaa server.

Described aaa server is judged when the MBMS authorization response message is carried the mandate successful information, is further comprised:

Aaa server sends the MBMS bearing capacity message that acquisition request UE supports to UE, and afterwards, UE is back to aaa server with the MBMS bearing capacity of self supporting, aaa server receives and preserve the MBMS bearing capacity that this UE supports afterwards.

Further comprise between described step B and the C:

After B1, BM-SC receive the MBMS authorization request message,, determine a wireless local network connecting point title W-APN simultaneously, this W-APN is returned to steps A and the described PDG of B with authorizing successful information to be carried in the MBMS authorization response message if authorize successfully; If authorization failure returns to steps A and the described PDG of B with the MBMS authorization response message of carrying authorization failure information,

Described W-APN points to the PDG that handles follow-up activation process, and the PDG of the follow-up activation process of described processing is different with the described PDG of B with steps A;

The described PDG of B2, steps A and B receives the MBMS authorization response message, judges whether this authorization response message carries the mandate successful information, if send the request MBMS context activation message of carrying W-APN to UE; Otherwise, send the activating multicast service refuse information to UE;

After B3, UE receive request MBMS context activation message, the PDG of the follow-up activation process of described processing that the WANP that carries to this request MBMS context activation message points to sends and activates the MBMS context request message, after the PDG of the follow-up activation process of described processing receives this activation MBMS context request message, send the MBMS authorization request message to BM-SC;

And the described PDG of step C and D is the PDG of the follow-up activation process of described processing.

The described PDG of step D judges that the MBMS authorization response message is carried and authorizes after the successful information, further comprises before creating MBMS UE context:

Whether the MBMS bearing capacity that the UE that self preserves supports of judging PDG satisfies the bearing capacity that multicast service that the UE that comprised in the MBMS bearer context of self preserving will add requires, if satisfy, creates MBMS UE context; If do not satisfy, then judge whether proceed activating multicast service according to pre-defined rule, if should, then send activating multicast service and accept message to UE; If not should, then send the activating multicast service refuse information to UE.

The described UE of steps A further comprises after PDG sends the message of carrying multicast service identifier: UE sends the MBMS bearing capacity of self supporting to PDG, and PDG receives and preserve the MBMS bearing capacity that this UE supports afterwards.

The message of carrying multicast service identifier that the described UE of steps A sends to PDG is further carried the MBMS bearing capacity that self supports, and PDG receives and preserve the MBMS bearing capacity that described UE supports.

The described PDG of step D judges when the MBMS authorization response message is carried the mandate successful information, further comprise: PDG sends the MBMS bearing capacity message that acquisition request UE supports to UE, afterwards, UE is back to PDG with the MBMS bearing capacity of self supporting, PDG receives and preserve the MBMS bearing capacity that described UE supports.

The described BM-SC of step C will authorize successful information be carried in the MBMS authorization response message after, return to PDG and further to comprise before this MBMS authorization response message:

Whether the MBMS bearing capacity that the UE that self preserves supports of judging BM-SC satisfies the bearing capacity that multicast service that the UE that comprised in the MBMS bearer context of self preserving will add requires, if satisfy, authorize the MBMS authorization response message of successful information to be back to PDG with carrying; If do not satisfy, the not enough information of UE bearing capacity is back to PDG with authorizing successful information to be carried in the MBMS authorization response message,

And the described PDG of step D judges that the MBMS authorization response message is carried and authorizes after the successful information, creates MBMS UE context and send activating multicast service to UE and accept further to comprise before the message: PDG judges whether authorization response message comprises UE bearing capacity deficiency information, if comprise, then judge whether proceed activating multicast service according to pre-defined rule, if should, then send activating multicast service and accept message to UE; If not should, then send the activating multicast service refuse information to UE.

The described MBMS authorization request message of step B is carried the MBMS bearing capacity that UE supports,

When the described BM-SC of step C receives the MBMS authorization request message, further comprise: BM-SC preserves the MBMS bearing capacity that UE that this MBMS authorization request message carries supports.

The described UE of steps A further comprises after PDG sends the message of carrying multicast service identifier: UE sends the MBMS bearing capacity of self supporting to BM-SC, and BM-SC receives and preserve the MBMS bearing capacity that this UE supports afterwards.

Further comprise before the described steps A:

The tunnel that UE detects between self and the PDG is set up, and creates MBMS UE context.

Further comprise before the described steps A: the tunnel between UE foundation and the PDG;

And the described UE of steps A further comprises after the message of PDG transmission requesting activation multicast service: UE creates MBMS UE context.

The message that the steps A described request activates multicast service is that request message is set up in the tunnel, and this tunnel sets up request message and carry multicast service identifier or activating multicast service indication information,

And the described UE of steps A sends described tunnel to PDG and further comprises after setting up request message: UE creates MBMS UE context.

The described PDG of step D judges that the MBMS authorization response message is carried and authorizes after the successful information, returns before activating multicast service accepts message to UE, further comprises:

PDG judges whether tunnel foundation is successful, if success is returned activating multicast service to UE and accepted message; If unsuccessful, return activation multicast service failed message to UE.

Described activating multicast service is accepted message and is further carried the tunnel and set up object information.

The described UE of steps A to PDG send described tunnel set up request message after, UE further comprises before creating MBMS UE context: UE receives that PDG sends carries the tunnel and sets up the tunnel of successful information and set up response message.

The described UE of steps A sends described tunnel to PDG and further comprises after setting up request message: UE sets and also starts a timer,

And described UE further comprises before creating MBMS UE context:

UE detects described timer expiry, then judges whether the activating multicast service refuse information of receiving that PDG sends, if receive, this flow process finishes; If confiscate, create MBMS UE context.

The described multicast service of step D is accepted message and is carried the MBMS UE context that PDG creates,

And described step D further comprises: after UE receives that this multicast service is accepted message, accept the MBMS UE context that MBMS UE updating context self that message carries is created according to this multicast service.

The described PDG of step D judges that authorization response message is carried and authorizes after the successful information, sends activating multicast service to UE and accept further to comprise before the message:

PDG creates MBMS UE context according to the MBMS bearer context of self preserving.

The described PDG of step D judges that authorization response message is carried and authorizes after the successful information, further comprises before creating MBMS UE context:

PDG judges whether self preserves the MBMS bearer context, if preserve, then creates MBMS UE context according to this MBMS bearer context; Otherwise, obtain the MBMS bearer context to BM-SC, and create MBMS UE context according to the MBMS UE bearer context that gets access to.

The MBMS bearer context that described PDG self preserves is: BM-SC is deployed on the PDG in advance.

Described PDG obtains MBMS UE bearer context to BM-SC and is specially:

PDG sends login request message to BM-SC, after BM-SC receives this login request message, returns the registration reply message that carries MBMS UE bearer context to PDG;

Perhaps, PDG sends login request message to the authentication and authorization charging aaa server, after aaa server is received this login request message, returns the registration reply message that carries MBMS UE bearer context to PDG.

PDG preserves WLAN AN in advance and/or WAG is used to create the contextual information indication of MBMS UE,

The described PDG of step D judges that the MBMS authorization response message is carried and further comprises after authorizing successful information: PDG is used to create the contextual information indication of MBMS UE according to described WLAN AN and/or WAG, the WLAN AN of the correspondence of self preserving and/or WAG is used to create the contextual information of MBMSUE sends to WLAN AN and/or WAG.

Described PDG is used to WLAN AN and/or WAG to create that the contextual information of MBMS UE sends to WLAN AN and/or WAG is specially:

PDG earlier is used to create the contextual information of MBMS UE with WLAN AN and/or WAG and is sent to aaa server, and aaa server is used to create the contextual information of MBMS UE with this WLAN AN and/or WAG and sends to WLAN AN and/or WAG afterwards.

Described UE roams,

And described aaa server is used to WLAN AN and/or WAG to create, and the contextual information of MBMS UE sends to WLAN AN and/or WAG is specially:

Aaa server earlier is used for creating the AAA agency that the contextual information of MBMS UE is sent to place, UE roaming back accesses network with WLAN AN and/or WAG, and the AAA agency is used to create the contextual information of MBMS UE with this WLAN AN and/or WAG and sends to WLAN AN and/or WAG afterwards.

Communication interface between described PDG of steps A and the BM-SC is supported Diameter or remote dial-in user's authentication service radius protocol or Session initiation protocol SIP.

Communication interface between described BM-SC and the aaa server is supported Diameter or radius protocol or SIP.

The message that the steps A described request activates multicast service is: the multicast service among the Internet Group Management Protocol IGMP of IPv4 definition adds message, or be: the multicast service in the multicast listener discovery MLD agreement of IPv6 definition adds message, or be: the message of SIP carrying, or be: HTML (Hypertext Markup Language) HTTP carrying, or be the message of WAP (wireless access protocol) WAP carrying, or the message of carrying for custom protocol.

The steps A described request activates the message of multicast service and carries multicast service identifier,

And the described MBMS authorization request message of step B is carried multicast service identifier,

And the multicast service identifier that the described BM-SC of step C gets access to is specially: BM-SC gets access to from described MBMS authorization request message.

Described multicast service identifier is an IP multicast address, or W-APN, or the combination of IP multicast address and W-APN.

Described UE reports the multicast service identifier that self will add of acquiescence when BM-SC is signatory, and BM-SC is saved in the multicast service identifier that this UE acquiescence will add in the CAMEL-Subscription-Information of UE,

And the multicast service identifier that the described BM-SC of step C gets access to is specially: the multicast service identifier that the UE acquiescence that is comprised in the CAMEL-Subscription-Information of the UE that BM-SC preserves by self will add gets access to.

The described BM-SC of step C will authorize after successful information is carried in the MBMS authorization response message, further comprise:

BM-SC creates MBMS UE context.

Compared with prior art, method provided by the present invention is by increasing communication interface between PDG and BM-SC, and by UE the message of requesting activation multicast service is sent to PDG, and PDG self wants to add multicast service with notice; PDG sends the MBMS authorization request message to BM-SC afterwards; After BM-SC receives the MBMS authorization request message, will authorize success or failure information to be carried in the MBMS authorization response message and return to PDG; After PDG receives the MBMS authorization response message,, then send activating multicast service and accept message to UE if detect this MBMS authorization response message authorization by direction success; Otherwise, send the activating multicast service refuse information to UE, realized the activating multicast service under the I-WLAN framework.

Description of drawings

The wireless network architecture figure of the support MBMS that Fig. 1 provides for 3GPP;

Fig. 2 is under the MBMS wireless network architecture of 3GPP definition, the flow chart of activating multicast service;

Fig. 3 is that WLAN UE is under non-roaming situation, with the intercommunication configuration diagram of 3GPP home network;

Fig. 4 a is that WLAN UE is under roaming condition, with the intercommunication configuration diagram one of 3GPP visit net;

Fig. 4 b is that WLAN UE is under roaming condition, with the intercommunication configuration diagram two of 3GPP visit net;

Fig. 5 is the flow chart of activating multicast service provided by the invention;

Fig. 6 is the flow chart of the specific embodiment one of activating multicast service provided by the invention;

Fig. 7 is the flow chart of the specific embodiment two of activating multicast service provided by the invention;

Fig. 8 is the flow chart of the specific embodiment three of activating multicast service provided by the invention;

Fig. 9 is the flow chart of the specific embodiment four of activating multicast service provided by the invention;

Figure 10 is the flow chart of the specific embodiment five of activating multicast service provided by the invention;

Figure 11 is the flow chart of the specific embodiment six of activating multicast service provided by the invention;

Figure 12 is the flow chart of the specific embodiment seven of activating multicast service provided by the invention;

Figure 13 is the flow chart of the specific embodiment eight of activating multicast service provided by the invention;

Figure 14 is the flow chart of the specific embodiment nine of activating multicast service provided by the invention;

Figure 15 is the flow chart of the specific embodiment ten of activating multicast service provided by the invention.

Embodiment

The present invention is further described in more detail below in conjunction with drawings and the specific embodiments.

Fig. 5 is the flow chart of activating multicast service provided by the invention, and as shown in Figure 5, its concrete steps are as follows:

Step 501:UE wants to add multicast service to the message that PDG sends the requesting activation multicast service to notify PDG self.

The message of requesting activation multicast service is that the multicast service in the IGMP agreement of IPv4 definition adds message, or be that the multicast service in the MLD agreement of IPv6 definition adds message, or for setting up request message in the tunnel, or be the message of conversation initialized protocol (SIP) or HTTP(Hypertext Transport Protocol) or WAP (wireless access protocol) (WAP) or custom protocol equivalent-load.It must be noted that, because UE is when BM-SC is signatory, may report the sign of the multicast service that self will add of acquiescence, therefore, the message of the requesting activation multicast service that UE sends can be carried multicast service identifier, can not carry yet, if do not carry, after then PDG receives the message of this requesting activation multicast service, send the MBMS authorization request message of not carrying multicast service identifier to BM-SC, after BM-SC receives this MBMS authorization request message, detect this MBMS authorization request message and do not carry multicast service identifier, then in the CAMEL-Subscription-Information of the UE that self preserves, find the multicast service identifier that the acquiescence of this UE will add.

Multicast service identifier can be an IP multicast address, or W-APN, or the combination of IP multicast address and W-APN, or the like.

After step 502:PDG receives the message of requesting activation multicast service, send the MBMS authorization request message to BM-SC.

Interface protocol between PDG and the BM-SC can adopt Diameter or remote dial-in user's authentication service (RADIUS) agreement or Session Initiation Protocol etc.

After step 503:BM-SC receives the MBMS authorization request message, will authorize success or failure information to be carried in the MBMS authorization response message and return to PDG; Simultaneously, if authorize successfully, BM-SC creates MBMS UE context according to the MBMS bearer context.

In addition, the MBMS authorization response message is also carried multicast service identifier and W-APN, and wherein W-APN points to the group that comprises PDG.

Particularly, if this MBMS authorization request message is carried multicast service identifier, then BM-SC searches the CAMEL-Subscription-Information of this UE according to the UE sign, thereby determines whether to authorize the multicast service that receives this MBMS authorization request message indication to UE; If this MBMS authorization request message is not carried multicast service identifier, then BM-SC inquires the multicast service identifier that the UE acquiescence will add in the CAMEL-Subscription-Information of UE, and determines whether to receive the multicast service that this acquiescence will add to the UE mandate.

In addition, BM-SC also can be when receiving the MBMS authorization request message, creates MBMS UE context, if authorization failure is after this then deleted this MBMS UE context.

After step 504:PDG receives authorization response message, judge whether this authorization response message carries the mandate successful information, if, execution in step 505; Otherwise, return the activating multicast service refuse information to UE, this activating multicast service refuse information may also can provide Reason For Denial as authorization failure etc., and this flow process finishes.

Step 505:PDG creates MBMS UE context according to the MBMS bearer context, and accepts message to UE transmission activating multicast service, activates successfully.

In addition, PDG also can be after the message of receiving the requesting activation multicast service, before BM-SC sends the MBMS authorization request message, create MBMS UE context, carry authorization failure information, then delete this MBMS UE context if after this receive the MBMS authorization response message that BM-SC sends.

Among the present invention, PDG need preserve the corresponding relation of UE sign, Tunnel Identifier and multicast service identifier, so that when after this receiving the multicast service of BM-SC transmission, can find the UE that adds this multicast service according to this multicast service identifier, send the used tunnel of this multicast service thereby further find to this UE.Wherein, the UE sign can be IMSI etc., Tunnel Identifier can be the IP address, this locality (Local) of IP security protocol security association (IPsecSA) or internet key exchange security association (IKE SA) or UE or far-end (Remote) the IP address of UE etc., and multicast service identifier can be TMGI or IP multicast address or W-APN etc.

Further, all message and/or business mutual between PDG and BM-SC all can be through the forwardings of aaa server, at this moment, aaa server also need be preserved the corresponding relation that the WLAN sign of UE sign, Tunnel Identifier, multicast service identifier, the current access of UE, current WAG for the UE service identify etc., so that after this need be when entities such as WLAN AN, WAG send message or business at BM-SC, aaa server can send to entities such as corresponding WLAN AN, WAG according to described corresponding relation.

MBMS UE context among the present invention comprises at least: multicast service identifier, point to comprise at least and send activating multicast service to UE and accept Tunnel Identifier between W-APN (W-APN), UE and the PDG of PDG group of PDG of message, further can comprise: any one among the NSAPI of the WAG sign of tunnel process, the WLAN AN sign of tunnel process, APN, GGSN address, PDG address, SGSN address, TMGI, connection, Transaction Identifier, the MBMS_NSAPI etc. or combination in any.

MBMS bearer context among the present invention comprises: any one in the number of the bearing capacity that multicast/broadcast mode, multicast service identifier, W-APN, MBMS require, the tabulation of downstream node, APN, TMGI, bearing bed state of resources, MBMS service area, UE, the RA tabulation etc. or combination.

Embodiment one:

Fig. 6 is the flow chart of the specific embodiment one of activating multicast service provided by the invention, and as shown in Figure 6, its concrete steps are as follows:

Set up requests/response messages by the tunnel between step 601:UE and the PDG and create the MBMS service tunnel, and the Tunnel Identifier of UE and PDG preservation foundation.

This tunnel can be the special tunnel of only supporting the professional transmission of MBMS, also can be both to have supported the professional transmission of MBMS also to support the general tunnel of other professional transmission.

Step 602:UE initiates to carry the multicast service adding message of self identification to PDG.

This multicast service adds the IGMP message that message can be the IPv4 definition, also can be the MLD protocol message of IPv6 definition, can also be the message of SIP, HTTP, WAP, custom protocol equivalent-load.

This multicast service adds message portability multicast service identifier, also can not carry.Multicast service identifier is as IP multicast address, APN or the like.

After step 603:PDG receives that multicast service adds message, send the MBMS authorization request message of carrying the UE sign to BM-SC.

The MBMS authorization request message is portability W-APN also.

After step 604:BM-SC receives the MBMS authorization request message, will authorize success or failure information to be carried in the MBMS authorization response message and return to PDG; Simultaneously, if authorizes successfully, BM-SC is according to the MBMS bearer context of self preservation and the relevant information establishment MBMS UE context that the MBMS authorization request message is carried.

In addition, the MBMS authorization response message is also carried multicast service identifier, W-APN etc.

Particularly, BM-SC can identify according to the UE that this MBMS authorization request message is carried, at the CAMEL-Subscription-Information that self finds this UE, and the multicast service identifier that carries according to this CAMEL-Subscription-Information and authorization request message or the UE acquiescence that in the CAMEL-Subscription-Information of UE, the inquires multicast service identifier that will add, whether decision authorizes to UE.

The relevant information that the MBMS authorization request message is carried specifically can refer to: multicast service identifier, UE identify as IMSI, W-APN etc.

Particularly, authorizing success or failure information is to be carried in the MBMS authorization response message by BM-SC, and sends to PDG's.

The MBMS UE context that BM-SC creates comprises at least: W-APN, the UE of UE sign, multicast service identifier, PDG correspondence and the Tunnel Identifier between the PDG, further comprise: the sign of the WAG of the tunnel process between sign, UE and the PDG of the WLAN of the tunnel process between UE and the PDG etc.

After step 605:PDG received the MBMS authorization response message, whether authorization by direction was successful to judge this MBMS authorization response message, if, execution in step 606; Otherwise, returning refusal to UE and add message, this refusal adds message can comprise reason that refusal adds as authorization failure etc., the end of this flow process.

Step 606:PDG sends request MBMS context activation message to UE, activates MBMS UE context with request UE.

Step 607:UE creates MBMS UE context after receiving request MBMS context activation message, and returns activation MBMS context request message to PDG.

Activate the MBMS bearing capacity of MBMS context request message portability multicast service identifier, UE sign, UE support etc., wherein, the maximum service quality (QoS) that the MBMS bearing capacity that UE supports has indicated UE to provide.

The MBMS UE context that UE creates comprises at least: the W-APN of multicast service identifier, PDG correspondence and the Tunnel Identifier between the PDG, and the WAG of the sign of the WLAN of the tunnel process between the PDG and the tunnel process between PDG sign.

Step 608:PDG detects self and whether preserves the MBMS bearer context after receiving and activating the MBMS context request message, if, execution in step 609; Otherwise, obtain the MBMS bearer context from BM-SC, execution in step 609 then.

PDG can obtain the MBMS bearer context from BM-SC by dual mode: a kind of be by and aaa server or BM-SC between message such as register requirement/response message etc. obtain the MBMS bearer context alternately, another kind is that BM-SC is deployed to MBMS bearer context stationary part on the PDG.

Further, if comprise the bearing capacity that multicast service that UE will add requires in the MBMS bearer context, then PDG can judge whether MBMS bearing capacity that the UE that self obtains supports satisfies the bearing capacity that multicast service that UE will add requires, if continue to detect self whether to preserve the MBMS bearer context; Otherwise, judge whether proceed activating multicast service according to pre-defined rule, if should, then continue to detect self whether to preserve the MBMS bearer context; If not should, then send to activate MBMS context refuse information to UE, this flow process finishes.

The information of whether proceeding activation of service when particularly, operator is can be with the UE bearing capacity not enough is pre-configured on the PDG; Perhaps at UE when aaa server or BM-SC are signatory, the information of whether proceeding activation of service during with UE bearing capacity deficiency is kept in the CAMEL-Subscription-Information of UE, PDG is after receiving the MBMS authorization response message of carrying the not enough information of UE bearing capacity then, to the CAMEL-Subscription-Information of aaa server or BM-SC inquiry UE, can learn and whether should proceed activation of service.

The MBMS bearing capacity that UE supports can be that UE initiatively reports PDG, or PDG by the MBMS bearing capacity message that sends acquisition request UE and support etc. to the UE active request; Also can be UE to BM-SC initiatively report or BM-SC by the MBMS bearing capacity message that sends acquisition request UE and support etc. to the UE active request obtain the back, PDG obtains from BM-SC again.Wherein, UE initiatively reports the moment of MBMS bearing capacity to preestablish, and sends multicast service and adds particular moment after the message or UE and send multicast service and add message constantly and any time between certain particular moment etc. as being set at UE; PDG or BM-SC also can preestablish to the moment of UE active request MBMS bearing capacity, as being set at the particular moment of receiving after multicast service adds message, or receive particular moment after the MBMS authorization request message, or receive that multicast service adds the moment of message and any time between certain particular moment, or receive the moment of MBMS authorization request message and any time between certain particular moment etc., in addition, the MBMS bearing capacity that UE can support self send to PDG or BM-SC separately, also the MBMS bearing capacity of self supporting can be carried at other message and add in message or the requesting activation MBMS context message etc. as: multicast service and send to PDG or BM-SC.

Step 609:PDG creates MBMS UE context according to the MBMS bearer context, and returns activation MBMS context to UE and accept message, and activating multicast service is finished.

The MBMS UE context that PDG creates comprises at least: the W-APN of UE sign, multicast service identifier, self correspondence and the Tunnel Identifier between the UE, and the WAG of the sign of the WLAN of the tunnel process between the UE and the tunnel process between UE sign.

Embodiment two:

Fig. 7 is the flow chart of the specific embodiment two of activating multicast service provided by the invention, and as shown in Figure 7, flow process shown in this figure is compared with flow process shown in Figure 6:

Step 701～702 are identical with step 601～602.

Step 703 is with the difference of step 603: PDG is sent to aaa server earlier with the MBMS authorization request message after receiving that multicast service adds message, and afterwards, aaa server is transmitted to BM-SC with this MBMS authorization request message.

Can strengthen the Wm interface of definition among the 3GPP TS 23.234 as: make this interface support the transmission of authorization requests/response message and relevant parameter etc., as the interface between PDG and the aaa server, interface protocol can adopt Diameter with the Wm interface after this enhancing.

Step 704 is with the difference of step 604: after BM-SC receives the MBMS authorization request message, authorize the MBMS authorization response message of success or failure information to be back to aaa server with carrying, simultaneously, if authorize successfully, BM-SC creates MBMS UE context; Afterwards, aaa server returns to PDG with the MBMS authorization response message.

Further, after aaa server is received the MBMS authorization response message of authorization by direction success, can detect self and whether preserve the MBMS bearer context, if create MBMS UE context according to the relevant information that this MBMS bearer context and MBMS authorization request message are carried; Otherwise, obtain the MBMS bearer context from BM-SC, the relevant information of carrying according to this MBMS bearer context and MBMS authorization request message is created MBMS UE context then.

Aaa server also can obtain the MBMS bearer context from BM-SC by dual mode: a kind of be by and BM-SC between message such as register requirement/response message etc. obtain the MBMS bearer context alternately, another kind is that BM-SC is deployed to MBMS bearer context stationary part on the aaa server.Particularly, carry multicast service identifier in the login request message, after BM-SC receives this login request message, self finding this multicast service identifier, this MBMS bearer context is being carried at sends to aaa server in the registration reply message afterwards deserved MBMS bearer context.

Interface between BM-SC and the aaa server can be supported Diameter or radius protocol or Session Initiation Protocol etc.

Step 705 is with the difference of step 605: " execution in step 606 " that occur in the step 605 replaced with " execution in step 706 ".

Step 706～707 are identical with step 606～607.

Step 708 is with the difference of step 608: " execution in step 609 " of twice appearance in the step 608 all replaced with " execution in step 709 ".

Step 709 is identical with step 609.

Embodiment three:

Fig. 8 is the flow chart of the specific embodiment three of activating multicast service provided by the invention, and as shown in Figure 8, flow process shown in this figure is compared with flow process shown in Figure 6:

Step 801～603 are identical with step 601～603.

Step 804 is with the difference of step 604: BM-SC further carries W-APN in the authorization response message of the authorization by direction success that PDG returns, and this W-APN points to PDG2; And BM-SC does not create MBMS UE context in step 804.

BM-SC receive simultaneously that a plurality of PDG send at the MBMS authorization request message of same multicast service the time, for simplicity, BM-SC can specify among these a plurality of PDG to carry out follow-up business activation, and the W-APN of the PDG correspondence of this appointment is returned to other PDG except that this appointment PDG.

Step 805 is with the difference of step 605: " execution in step 606 " that occur in the step 605 replaced with " execution in step 806 ".

Step 806 is with the difference of step 606: PDG further carries W-APN to the request MBMS context activation message that UE sends.

Step 807 is: after UE receives request MBMS context activation message, create MBMS UE context, and detect this request MBMS context activation message and carry W-APN, then set up the tunnel between self and the PDG2, the PDG2 that points to this W-APN sends and activates the MBMS context request message then.

Step 808 is: after PDG2 receives and activates the MBMS context request message, send the MBMS authorization request message of carrying multicast service identifier and UE sign to BM-SC.

Step 809 is: after BM-SC receives the MBMS authorization request message, will authorize success or failure information to be carried in the MBMS authorization response message and return to PDG2; Simultaneously, if authorizes successfully, BM-SC is according to the MBMS bearer context of self preservation and the relevant information establishment MBMS UE context that the MBMS authorization request message is carried.

The relevant information that the MBMS authorization request message is carried can comprise: multicast service identifier, UE sign, W-APN etc.

Step 810 is: after PDG2 received the MBMS authorization response message, whether authorization by direction was successful to judge this MBMS authorization response message, if, execution in step 811; Otherwise, to return to UE and to activate MBMS context refuse information, this activations MBMS context refuse information can comprise Reason For Denial as authorization failure etc., the end of this flow process.

Step 811 is with the difference of step 608: PDG2 detects self whether to preserve the MBMS bearer context, if, execution in step 812; Otherwise, obtain the MBMS bearer context from BM-SC, execution in step 812 then.

Here, whether the MBMS bearing capacity that the UE that self obtains supports of judging mode, the PDG2 that PDG2 obtains the MBMS bearer context from BM-SC satisfy the process of the bearing capacity that multicast service that UE will add requires, whether PDG2 proceeded the process that the process of activation of service and PDG2 obtain the MBMS bearing capacity that UE supports when the UE bearing capacity was not enough, describes identical with PDG in the step 608 corresponding.

Step 812 is: PDG2 creates MBMS UE context according to the MBMS bearer context, and returns activation MBMS context to UE and accept message, and activating multicast service is finished.

The MBMS UE context that PDG2 creates is identical with the MBMS UE context of PDG establishment in the step 609.

Embodiment four:

Fig. 9 is the flow chart of the specific embodiment four of activating multicast service provided by the invention, and as shown in Figure 9, flow process shown in this figure is compared with flow process shown in Figure 8:

Step 901～902 are identical with step 801～802.

Step 903 is with the difference of step 803: PDG is sent to aaa server earlier with the MBMS authorization request message after receiving that multicast service adds message, and afterwards, aaa server is transmitted to BM-SC with this MBMS authorization request message.

Step 904 is with the difference of step 804: after BM-SC receives the MBMS authorization request message, authorize the MBMS authorization response message of success or failure information to be back to aaa server with carrying; Afterwards, aaa server returns to PDG with the MBMS authorization response message.

Step 905 is with the difference of step 605: " execution in step 606 " that occur in the step 605 replaced with " execution in step 906 ".

Step 906～907 are identical with step 806～807.

Step 908 is with the difference of step 808: PDG2 is sent to aaa server earlier with the MBMS authorization request message after receiving and activating the MBMS context request message, and afterwards, aaa server is transmitted to BM-SC with this MBMS authorization request message.

Step 909 is with the difference of step 809: after BM-SC receives the MBMS authorization request message, earlier the MBMS authorization response message is back to aaa server, simultaneously, if authorize successfully, BM-SC creates MBMS UE context; Afterwards, aaa server returns to PDG2 with the MBMS authorization response message.

Step 910 is with the difference of step 810: " execution in step 811 " that occur in the step 810 replaced with " execution in step 911 ".

Step 911～912 are identical with step 811～812.

Embodiment five:

Figure 10 is the flow chart of the specific embodiment five of activating multicast service provided by the invention, and as shown in figure 10, flow process shown in this figure is compared with flow process shown in Figure 6:

Step 1001～1004 are identical with step 601～604.

Step 1005 is with the difference of step 605: " execution in step 606 " that occur in the step 605 replaced with " execution in step 1006 ".

Step 1006 is identical with step 606.

Step 1007 is with the difference of step 607: activate the MBMS bearing capacity that MBMS context request message portability has UE to support.

Step 1008 is: PDG sends the MBMS authorization request message to BM-SC after receiving and activating the MBMS context request message, the MBMS bearing capacity that this MBMS authorization request message portability UE supports.

Step 1009 is: after BM-SC receives the MBMS authorization request message, to authorize success or failure information to be carried in the MBMS authorization response message, simultaneously, if authorize successfully, create MBMS UE context, and judge whether MBMS bearing capacity that UE supports satisfies the bearing capacity that multicast service that UE will add requires, if satisfy, return to PDG and to carry the MBMS authorization response message of authorizing successful information; If do not satisfy, then the not enough information of UE bearing capacity is returned to PDG together with authorizing successful information to be carried in the MBMS authorization response message.

BM-SC also can also can obtain by the alternate manner of describing in the step 608 initiatively to the PDG request except obtaining the MBMS bearing capacity of UE support by the MBMS authorization request message.

Step 1010 is: after PDG received the MBMS authorization response message, if detect this MBMS authorization response message authorization by direction success and do not indicate UE bearing capacity deficiency, then execution in step 1011; If detect the failure of this MBMS authorization response message authorization by direction, then to return and activate MBMS context refuse information to UE, this activations MBMS context refuse information can comprise Reason For Denial as authorization failure etc., the end of this flow process; If detect this MBMS authorization response message indication UE bearing capacity deficiency, then PDG determines whether to proceed activation of service according to pre-defined rule, if continue then execution in step 1011; Otherwise, to return to UE and to activate MBMS context refuse information, this activations MBMS context refuse information can comprise Reason For Denial as UE bearing capacity deficiency, the end of this flow process.

Step 1011 is with the difference of step 608: " after the receiving activation MBMS context request message " that occurs in the deletion step 608, and in step 1011, whether the MBMS bearing capacity that UE supports of not judging PDG satisfies the bearing capacity that multicast service that UE will add requires, and " execution in step 609 " with twice appearance in the step 608 all replaces with " execution in step 1012 " simultaneously.

Step 1012 is identical with step 609.

It is to be noted, in the flow process shown in Fig. 7～9, also can be when will authorizing successful information to be carried at the MBMS authorization response message by BM-SC, judge whether MBMS bearing capacity that UE supports satisfies the process of the bearing capacity that multicast service that UE will add requires, and detailed process is identical with this flow process; Simultaneously, PDG does not judge whether MBMS bearing capacity that UE supports satisfies the bearing capacity that multicast service that UE will add requires in step 708,811,911.

Embodiment six:

Figure 11 is the flow chart of the specific embodiment six of activating multicast service provided by the invention, and as shown in figure 11, flow process shown in this figure is compared with flow process shown in Figure 10:

Step 1101～1102 are identical with step 1001～1002.

Step 1103 is with the difference of step 1003: PDG is sent to aaa server earlier with the MBMS authorization request message after receiving that multicast service adds message, and afterwards, aaa server is transmitted to BM-SC with this MBMS authorization request message.

Step 1104 is with the difference of step 1004: after BM-SC receives the MBMS authorization request message, will carry earlier and authorize the MBMS authorization response message of success or failure information to be back to aaa server, simultaneously, if authorize successfully, BM-SC creates MBMS UE context; Afterwards, aaa server returns to PDG with the MBMS authorization response message.

Step 1105 is with the difference of step 1005: " execution in step 1006 " that occur in the step 1005 replaced with " execution in step 1106 ".

Step 1106～1107 are identical with step 1006～1007.

Step 1108 is with the difference of step 1008: PDG is sent to aaa server earlier with the MBMS authorization request message after receiving and activating the MBMS context request message, and afterwards, aaa server is transmitted to BM-SC with this MBMS authorization request message.

Step 1109 is: after BM-SC receives the MBMS authorization request message, return the MBMS authorization response message of carrying mandate success or failure information to aaa server.

Step 1110 is: after aaa server was received the MBMS authorization response message, whether authorization by direction was successful to judge this MBMS authorization response message, if, execution in step 1111; Otherwise, this MBMS authorization response message of carrying authorization failure information is returned to PDG, execution in step 1112 then.

Whether the MBMS bearing capacity that UE supports of judging step 1111:AAA server satisfies the bearing capacity that multicast service that UE will add requires, if satisfy, returns to PDG and to carry the MBMS authorization response message of authorizing successful information; If do not satisfy, then the not enough information of UE bearing capacity is returned to PDG together with authorizing successful information to be carried in the MBMS authorization response message.

Aaa server be except can obtaining the MBMS bearing capacity that UE supports by the MBMS authorization request message, also can by with step 608 in the PDG that the describes same way as of obtaining the MBMS bearing capacity that UE supports obtain.

Step 1112 is: after PDG received the MBMS authorization response message, if detect this MBMS authorization response message authorization by direction success and do not indicate UE bearing capacity deficiency, then execution in step 1113; If detect the failure of this MBMS authorization response message authorization by direction, then to return and activate MBMS context refuse information to UE, this activations MBMS context refuse information can comprise Reason For Denial as authorization failure etc., the end of this flow process; If detect this MBMS authorization response message indication UE bearing capacity deficiency, then PDG determines whether to proceed activation of service according to pre-defined rule, if continue then execution in step 1113; Otherwise, to return to UE and to activate MBMS context refuse information, this activations MBMS context refuse information can comprise Reason For Denial as UE bearing capacity deficiency, the end of this flow process.

It is to be noted, in step 1110, after aaa server is received the MBMS authorization response message of the authorization by direction success that BM-SC sends, self do not preserve the bearing capacity that multicast service that UE will add requires if detect, then obtain the bearing capacity that multicast service that this UE will add requires from BM-SC or PDG or UE.

Step 1113 is with the difference of step 1011: " execution in step 1012 " of twice appearance in the step 1011 all replaced with " execution in step 1114 ".

Step 1114 is identical with step 1012.

It is to be noted, identical with this flow process, in flow process shown in Figure 8, also can be after receiving the MBMS authorization response message of authorization by direction success by aaa server, judge whether MBMS bearing capacity that UE supports satisfies the process of the bearing capacity that multicast service that UE will add requires; Simultaneously, PDG does not judge whether MBMS bearing capacity that UE supports satisfies the bearing capacity that multicast service that UE will add requires in step 811.

Embodiment seven:

Figure 12 is the flow chart of the specific embodiment seven of activating multicast service provided by the invention, and as shown in figure 12, flow process shown in this figure is compared with flow process shown in Figure 6:

Step 1201 is identical with step 601.

Step 1202 is: UE creates MBMS UE context after the tunnel is set up.

Step 1203～1205 are identical with step 602～604.

Step 1206 is with the difference of step 605: " execution in step 606 " that occur in the step 605 replaced with " execution in step 1207 ".

Step 1207 is with the difference of step 608: " activating the MBMS context request message " of occurring in the step 608 replaces with " the MBMS authorization response message of authorization by direction success ", and " execution in step 609 " that occurs in the step 608 replaced with " execution in step 1208 ".

Step 1208 is identical with step 609.

Further, this activation MBMS context is accepted message and is carried the MBMS UE context that PDG creates, and after UE receives that message accepted in this activation MBMS context, accept the MBMS UE context that MBMS UE updating context self that message carries is preserved according to this activation MBMS context.

Embodiment eight:

Figure 13 is the flow chart of the specific embodiment eight of activating multicast service provided by the invention, and as shown in figure 13, flow process shown in this figure is compared with flow process shown in Figure 6:

Step 1301～1304 are identical with step 601～604.

Step 1305 is with the difference of step 605: " execution in step 606 " that occur in the step 605 replaced with " execution in step 1306 ".

Step 1306 is: UE creates MBMS UE context, and sends activation MBMS context request message to PDG.

Here, UE is timer of startup when sending multicast service to add message, this timer duration is the duration that mutual MBMS authorization requests/response message is spent between predefined PDG and the BM-SC, when this timer expiry, UE judges whether to receive that the refusal that PDG sends adds message, if receive, this flow process finishes; If do not receive that then UE begins to create MBMS UE context.

Step 1307 is with the difference of step 608: " execution in step 609 " of twice appearance in the step 608 all replaced with " execution in step 1308 ".

Step 1308 is identical with step 609.

Embodiment nine:

Figure 14 is the flow chart of the specific embodiment nine of activating multicast service provided by the invention, and as shown in figure 14, flow process shown in this figure is compared with flow process shown in Figure 6:

Step 1401 is: UE sends the tunnel carry multicast service identifier or to carry the activating multicast service indication information to PDG and sets up request message.

If what the tunnel set up that request message carries is activating multicast service indication information rather than multicast service identifier, after then PDG receives that request message is set up in this tunnel, send the MBMS authorization request message of not carrying multicast service identifier to BM-SC, after BM-SC receives this MBMS authorization request message, detect this MBMS authorization request message and do not carry multicast service identifier, then in the CAMEL-Subscription-Information of the UE that self preserves, find the multicast service identifier that the acquiescence of this UE will add.

Step 1402 is: PDG sends the MBMS authorization request message of carrying the UE sign after receiving that request message is set up in this tunnel that carries multicast service identifier or carry the activating multicast service indication information to BM-SC.

It is pointed out that PDG also can set up in the tunnel after promptly to UE send carry the tunnel and set up the tunnel of successful information and set up response message after, send the MBMS authorization request message to BM-SC.

Step 1403 is identical with step 604.

Step 1404 is with the difference of step 605: " execution in step 606 " that occur in the step 605 replaced with " execution in step 1406 ".

Step 1405 is: UE creates MBMS UE context.

Equally, UE is timer of startup when sending the tunnel to set up request message, this timer duration is the duration that mutual MBMS authorization requests/response message is spent between predefined PDG and the BM-SC, when this timer expiry, UE judges whether to receive that the refusal that PDG sends adds message, if receive, then this flow process finishes; If do not receive that then UE begins to create MBMS UE context.

Step 1406 is with the difference of step 608: " after the receiving activation MBMS context request message " that occurs in the deletion step 608 replaces with " execution in step 1407 " with " execution in step 609 " that occurs in the step 608.

Further, PDG after receiving the MBMS authorization response message of authorization by direction success, inquire about earlier and UE between the tunnel whether set up success, if the success, then execution in step 1406; Otherwise, think that UE returns activation MBMS context refuse information, this flow process finishes.

Step 1407 is identical with step 609.

Further, this activation MBMS context is accepted message and can be carried the relevant information of having set up the tunnel as the QoS attribute in tunnel etc.

Embodiment ten:

Figure 15 is the flow chart of the specific embodiment ten of activating multicast service provided by the invention, and as shown in figure 15, flow process shown in this figure is compared with flow process shown in Figure 6:

Step 1501 is identical with step 601.

Step 1502 is: UE receives promptly after the tunnel is set up that PDG sends carries the tunnel and sets up after the tunnel of successful information sets up response message establishment MBMS UE context.

Step 1503 is identical with step 602.

Step 1504 is: PDG is sent to aaa server earlier with the MBMS authorization request message after receiving that multicast service adds message, and afterwards, aaa server is transmitted to BM-SC with this MBMS authorization request message.

Step 1505 is: after BM-SC receives the MBMS authorization request message, will carry and authorize success or failure information MBMS authorization response message to be back to aaa server, simultaneously, if authorize successfully, BM-SC creates MBMS UE context.

Step 1506 is: after aaa server was received the MBMS authorization response message, whether authorization by direction was successful to judge this MBMS authorization response message, if, this MBMS authorization response message is returned to PDG, simultaneously, execution in step 1507; Otherwise, the MBMS authorization response message is returned to PDG, simultaneously execution in step 1508.

After step 1507:AAA server is received the MBMS authorization response message of authorization by direction success, detect self and whether created MBMS UE context, if this MBMS UE context is sent to WLAN AN and/or WAG; Otherwise, continue to judge whether self preserves the MBMS bearer context, if preserve, the relevant information establishment MBMS UE context that carries according to this MBMS bearer context and MBMS authorization request message; Otherwise, obtain the MBMS bearer context from BM-SC, the relevant information of carrying according to this MBMS bearer context and MBMS authorization request message is created MBMS UE context then.

Further, after aaa server is received the MBMS authorization response message of authorization by direction success, WLAN AN and/or the WAG that self preserves the contextual information of MBMS UE be can be used to create, WLAN AN and/or WAG sent to.

Here, aaa server obtains and preserves WLAN AN and/or WAG is used to create the used information indication of MBMS UE context to WLAN AN and/or WAG in advance.

If roaming has taken place in UE, then aaa server need be used to WLAN AN and/or WAG to create the contextual information of MBMS UE and sends to and act on behalf of AAA, then by acting on behalf of local corresponding WLAN AN of determining of AAA and/or WAG, and WLAN AN and/or WAG are used to create the contextual information of MBMSUE send to WLAN AN and/or WAG.

Step 1508 is with the difference of step 605: " execution in step 606 " that occur in the step 605 replaced with " execution in step 1509 ".

Step 1509 is with the difference of step 608: " activating the MBMS context request message " of occurring in the step 608 replaced with " the MBMS authorization response message of authorization by direction success ", " execution in step 609 " that occurs in the step 608 replaced with " execution in step 1510 ".

Step 1510 is identical with step 609.

Further, in step 1510, activate the MBMS context and accept the MBMS UE context that message is carried the PDG establishment, and after UE receives that message accepted in this activation MBMS context, accept the MBMS UE context that MBMS UE updating context self that message carries is preserved according to this activation MBMS context.

It is to be noted, in flow process shown in Figure 12～15, also can be after BM-SC will authorize successful information to be carried at the MBMS authorization response message, judge by BM-SC whether MBMS bearing capacity that UE supports satisfies the process of the bearing capacity that multicast service that UE will add requires, and detailed process is identical with process shown in Figure 10; Simultaneously PDG does not judge whether MBMS bearing capacity that UE supports satisfies the bearing capacity that multicast service that UE will add requires in step 1207,1307,1406,1509.

In addition, in flow process shown in Figure 15, also can be after receiving the MBMS authorization response message of carrying the mandate successful information by aaa server, judge by aaa server whether MBMS bearing capacity that UE supports satisfies the process of the bearing capacity that multicast service that UE will add requires, and detailed process is identical with process shown in Figure 11; Simultaneously PDG does not judge whether MBMS bearing capacity that UE supports satisfies the bearing capacity that multicast service that UE will add requires in step 1509.

It is to be noted, in the present invention, also can after PDG or PDG2 receive the MBMS authorization response message of authorization by direction success, WLAN AN and/or the WAG that self preserves be used to create the contextual information of MBMS UE, send to WLAN AN and/or WAG by PDG or PDG2.

Here, PDG or PDG2 obtain and preserve WLANAN and/or WAG is used to create the used information indication of MBMS UE context from WLAN AN and/or WAG in advance.

PDG or PDG2 can be used to create the contextual information of MBMS UE with WLAN AN and/or WAG and directly send to WLAN AN and/or WAG, perhaps via aaa server WLAN AN and/or WAG are used to create the contextual information of MBMS UE by PDG or PDG2 and send to WLAN AN and/or WAG.Certainly, if roaming has taken place in UE, after aaa server receives that WLAN AN that PDG or PDG2 send and/or WAG are used to create the contextual information of MBMS UE, will be earlier this WLAN AN and/or WAG be used to create the contextual information of MBMS UE and be sent to the AAA agency, be forwarded to WLAN AN and/or WAG by the AAA agency again.

The above only is process of the present invention and method embodiment, in order to restriction the present invention, all any modifications of being made within the spirit and principles in the present invention, is not equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims

1, a kind of method for activating multicast service is characterized in that, between packet data gateway PDG and broadcast/multicast service center BM-SC communication interface is set, and this method comprises:

A, user terminal UE send the message of requesting activation multicast service to PDG;

After B, PDG receive the message of requesting activation multicast service, send multimedia broadcast/group broadcast service MBMS authorization request message to BM-SC;

2, the method for claim 1 is characterized in that, the described PDG of step D judges that this MBMS authorization response message is carried and authorizes after the successful information, further comprises before creating MBMS UE context:

3, the method for claim 1 is characterized in that, between BM-SC and aaa server communication interface is set,

4, method as claimed in claim 3 is characterized in that, described BM-SC with the MBMS authorization response message be back to after the aaa server, aaa server further comprises before the MBMS authorization response message is back to PDG:

5, method as claimed in claim 4 is characterized in that, the MBMS bearer context that described aaa server self is preserved is that BM-SC is deployed on the aaa server in advance.

6, method as claimed in claim 4 is characterized in that, described aaa server is judged that the MBMS authorization response message is carried and authorized after the successful information, further comprises before creating MBMS UE context:

7, method as claimed in claim 6 is characterized in that, described aaa server obtains the MBMS bearer context to BM-SC and is specially:

8, method as claimed in claim 3 is characterized in that, aaa server preserves WLANAN in advance and/or WAG is used to create the contextual information indication of MBMS UE,

Aaa server detects the MBMS authorization response message and carries the mandate successful information, then be used to create the contextual information indication of MBMS UE, the WLAN AN of the correspondence of self preserving and/or WAG be used to create the contextual information of MBMS UE send to WLAN (wireless local area network) Access Network WLAN AN and/or WLAN (wireless local area network) IAD WAG according to described WLAN AN and/or WAG.

9, method as claimed in claim 8 is characterized in that, described UE roams,

10, method as claimed in claim 3 is characterized in that, described aaa server receives after the MBMS authorization response message, further comprise before the MBMS authorization response message is back to PDG:

11, method as claimed in claim 10 is characterized in that, the described UE of steps A further comprises after PDG sends the message of carrying multicast service identifier: UE sends the MBMS bearing capacity of self supporting to aaa server.

12, method as claimed in claim 10 is characterized in that, described aaa server is judged when the MBMS authorization response message is carried the mandate successful information, further comprised:

13, as claim 1 or 3 described methods, it is characterized in that, further comprise between described step B and the C:

14, the method for claim 1 is characterized in that, the described PDG of step D judges that the MBMS authorization response message is carried and authorizes after the successful information, further comprises before creating MBMS UE context:

15, method as claimed in claim 14, it is characterized in that, the described UE of steps A further comprises after PDG sends the message of carrying multicast service identifier: UE sends the MBMS bearing capacity of self supporting to PDG, and PDG receives and preserve the MBMS bearing capacity that this UE supports afterwards.

16, method as claimed in claim 14 is characterized in that, the message of carrying multicast service identifier that the described UE of steps A sends to PDG is further carried the MBMS bearing capacity that self supports, and PDG receives and preserve the MBMS bearing capacity that described UE supports.

17, method as claimed in claim 14, it is characterized in that, the described PDG of step D judges when the MBMS authorization response message is carried the mandate successful information, further comprise: PDG sends the MBMS bearing capacity message that acquisition request UE supports to UE, afterwards, UE is back to PDG with the MBMS bearing capacity of self supporting, PDG receives and preserve the MBMS bearing capacity that described UE supports.

18, the method for claim 1 is characterized in that, the described BM-SC of step C will authorize successful information be carried in the MBMS authorization response message after, return to PDG and further to comprise before this MBMS authorization response message:

19, method as claimed in claim 18 is characterized in that, the described MBMS authorization request message of step B is carried the MBMS bearing capacity that UE supports,

20, method as claimed in claim 18, it is characterized in that, the described UE of steps A carries multicast to the PDG transmission and already further comprises after the message of sign fully: UE sends the MBMS bearing capacity of self supporting to BM-SC, and the MBMS bearing capacity of this UE support is also preserved in BM-SC reception afterwards.

21, the method for claim 1 is characterized in that, further comprises before the described steps A:

22, the method for claim 1 is characterized in that, further comprises before the described steps A: the tunnel between UE foundation and the PDG;

23, the method for claim 1 is characterized in that, the message that the steps A described request activates multicast service is that request message is set up in the tunnel, and this tunnel sets up request message and carry multicast service identifier or activating multicast service indication information,

24, method as claimed in claim 23 is characterized in that, the described PDG of step D judges that the MBMS authorization response message is carried and authorizes after the successful information, returns before activating multicast service accepts message to UE, further comprises:

25, method as claimed in claim 24 is characterized in that, described activating multicast service is accepted message and further carried the tunnel and set up object information.

26, method as claimed in claim 23, it is characterized in that, the described UE of steps A to PDG send described tunnel set up request message after, UE further comprises before creating MBMS UE context: UE receives that PDG sends carries the tunnel and sets up the tunnel of successful information and set up response message.

27, method as claimed in claim 23 is characterized in that, the described UE of steps A sends described tunnel to PDG and further comprises after setting up request message: UE sets and also starts a timer,

And described UE further comprises before creating MBMS UE context:

28, method as claimed in claim 23 is characterized in that, the described multicast service of step D is accepted message and carried the MBMS UE context that PDG creates,

As claim 1 or 13 described methods, it is characterized in that 29, the described PDG of step D judges that authorization response message is carried and authorizes after the successful information, sends activating multicast service to UE and accept further to comprise before the message:

30, method as claimed in claim 29 is characterized in that, the described PDG of step D judges that authorization response message is carried and authorizes after the successful information, further comprises before creating MBMS UE context:

31, method as claimed in claim 30 is characterized in that, the MBMS bearer context that described PDG self preserves is: BM-SC is deployed on the PDG in advance.

32, method as claimed in claim 30 is characterized in that, described PDG obtains MBMS UE bearer context to BM-SC and is specially:

33, the method for claim 1 is characterized in that, PDG preserves WLAN AN in advance and/or WAG is used to create the contextual information indication of MBMS UE,

34, method as claimed in claim 33 is characterized in that, described PDG is used to WLAN AN and/or WAG to create that the contextual information of MBMS UE sends to WLAN AN and/or WAG is specially:

35, method as claimed in claim 34 is characterized in that, described UE roams,

36, the method for claim 1 is characterized in that, the communication interface between described PDG of steps A and the BM-SC is supported Diameter or remote dial-in user's authentication service radius protocol or Session initiation protocol SIP.

37, method as claimed in claim 3 is characterized in that, the communication interface between described BM-SC and the aaa server is supported Diameter or radius protocol or SIP.

38, the method for claim 1, it is characterized in that, the message that the steps A described request activates multicast service is: the multicast service among the Internet Group Management Protocol IGMP of IPv4 definition adds message, or be: the multicast service in the multicast listener discovery MLD agreement of IPv6 definition adds message, or be: the message of SIP carrying, or be: HTML (Hypertext Markup Language) HTTP carrying, or be the message of WAP (wireless access protocol) WAP carrying, or the message of carrying for custom protocol.

39, the method for claim 1 is characterized in that, the steps A described request activates the message of multicast service and carries multicast service identifier,

As claim 23 or 39 described methods, it is characterized in that 40, described multicast service identifier is an IP multicast address, or W-APN, or the combination of IP multicast address and W-APN.

41, the method for claim 1 is characterized in that, described UE reports the multicast service identifier that self will add of acquiescence when BM-SC is signatory, and BM-SC is saved in the multicast service identifier that this UE acquiescence will add in the CAMEL-Subscription-Information of UE,

42, the method for claim 1 is characterized in that, the described BM-SC of step C will authorize after successful information is carried in the MBMS authorization response message, further comprise:

BM-SC creates MBMS UE context.