CN101047976A - Authorization failure process method and system in multimedia broadcast/multicast service - Google Patents
Authorization failure process method and system in multimedia broadcast/multicast service Download PDFInfo
- Publication number
- CN101047976A CN101047976A CNA2006100734424A CN200610073442A CN101047976A CN 101047976 A CN101047976 A CN 101047976A CN A2006100734424 A CNA2006100734424 A CN A2006100734424A CN 200610073442 A CN200610073442 A CN 200610073442A CN 101047976 A CN101047976 A CN 101047976A
- Authority
- CN
- China
- Prior art keywords
- network side
- authorization
- mbms
- subscriber equipment
- authorization failure
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a method and system of multi-media broadcast / multicast business when authorization is failed, in which, when the user equipment doesn' t pass the authorization of business management, the network side sends failure information to the user equipment. It makes UE not try to initiate request of activation when MBMS business is not allowed to activate, thereby saving network resources, and reduce the load of network to some extent.
Description
Technical field
The present invention relates to the mobile communication technology field, it is particularly related to the multimedia broadcast/group broadcast service of 3-G (Generation Three mobile communication system), is authorization failure process method and system in a kind of multimedia broadcast/group broadcast service concretely.
Background technology
Along with the development of 3G (Third Generation) Moblie technology, 3G (Third Generation) Moblie can provide than the more service of high data rate of second generation mobile communication, thereby supports the multiple business form.Download, browse at a high speed services such as Internet network such as visual telephone, picture.Wherein have a class business features to be: this business can be simultaneously give subscribed in the wireless network should business the user send.Such as weather forecast, news film, the sports tournament collection of choice specimens or the like.The characteristics of utilizing these business to send simultaneously, 3-G (Generation Three mobile communication system) has been introduced the notion of multicast/broadcast from Rel-6, can more effectively utilize preferential air interface resource, and higher power system capacity is provided.
In the broadcasting/packet service, for an intermediate node, no matter its downstream comprises the node what expectations receive data, and its upstream node always sends a piece of data to this intermediate node; After this intermediate node is received data, the number of nodes that receives data according to its downstream expectation duplicates this data, and distribute this data to the node that each expectation of its downstream receives these data, like this, each bar branch of multicast/broadcast business data transmission tree all has only a piece of data to transmit, take a transfer resource, the transfer of data of root node and its downstream node also is like this.The distinctive points of multicast service and broadcasting service only is: multicast service only sends corresponding information to the user who has subscribed to some information, and the broadcasting service then user of all in wireless network sends information.As seen from the above description, provide identical information to a large number of users simultaneously, can greatly save Internet resources by multicast/broadcast is professional.
Fig. 1 is for supporting the wireless network architecture schematic diagram of broadcasting/packet service.As shown in Figure 1, in the existing third generation partner program (3GPP), support that the wireless network architecture of broadcasting/packet service is broadcasting/packet service server (BM-SC), BM-SC is by Gmb interface or Gi interface and critical point GPRS Support Node (GGSN, Gateway GPRS Support Node) link to each other, a BM-SC can link to each other with a plurality of GGSN; GGSN links to each other by Gn/Gp interface and Serving GPRS Support Node (SGSN, Serving GPRS Support Node), and a GGSN can link to each other with a plurality of SGSN; SGSN can link to each other with universal mobile telecommunications system (UMTS) land radio access web (UTRAN) by the Iu interface, UTRAN links to each other with user terminal (UE) by the Uu interface then, SGSN also can strengthen wireless access network (GERAN) by Iu/Gb interface and global system for mobile communications (GSM) and link to each other, and GERAN links to each other with UE by Um Interface then.Wherein, GGSN and SGSN belong to the node in the core net in the wireless network (CN).
In the prior art, broadcast multicast service center is providing of multimedia broadcast/group broadcast service (MBMS) customer service and transmission provides function.Can be used as one and in public land mobile net (PLMN), be used for the MBMS content delivery, authorize and initiate the access point of MBMS bearer service, and can be used for scheduling and send the MBMS transmission.
Be illustrated in figure 2 as the functional structure of BM-SC, BM-SC is necessary for the MBMS customer service and exists as a functional entity, and it comprises five subdivisions:
1) member's function subdivision;
2) session and sending function subdivision;
3) agency and transfer function subdivision;
4) professional declaration function subdivision;
5) safety function subdivision.
In 3GPP TS 23.246, stipulated MBMS activating multicast service flow process (as shown in Figure 3).This MBMS activating multicast service flow process may further comprise the steps:
Step 1, UE activate packet data protocol (PDP) context;
Wherein, if there is not the PDP Context of activation between UE and the SGSN, then activate a general PDP Context by UE.
Step 2, UE send IGMP (IGMP) to SGSN and add message;
Wherein, UE sends IGMP (IPv4) or multicast audience and finds that (MLD:Multicast Listener Discovery) (IPv6) adds message (Joining message) on the PDP Context of acquiescence, show that its preparation receives specific multicast MBMS bearer service, this bearer service is identified by IP multicast address.
Step 3, GGSN send the MBMS authorization requests to BM-SC;
Wherein, GGSN sends MBMS authorization requests (MBMS Authorization Request) to BM-SC, to obtain making UE receive the mandate of data.The MBMS authorization requests may comprise tracked information (traceinformation).Authorization result (may be based on the CAMEL-Subscription-Information among the BM-SC) and APN (APN) return to GGSN together by member's function in MBMS authorization response (MBMS Authorization Response), be used to create MBMS UE context.Be not authorized to receive the MBMS data if point out UE in authorization response, the entire process flow process finishes, and does not have further message.
Step 4, GGSN send the MBMS notice request to SGSN, and SGSN returns the MBMS push-notification-answer to GGSN;
Wherein:
4a.GGSN send MBMS notice request (MBMS Notification Request) (comprising IP multicast address, APN, the NSAPI of connection) to SGSN.Wherein, the NSAPI of connection (Linked NSAPI) is set to send the pairing NSAPI of PDP Context that adds message; IP multicast address is that IP multicast address that UE asks in joining request; APN may be different from pairing that APN of PDP Context of the acquiescence of activation.Under any circumstance, APN is possible resolved to be a GGSN, and this GGSN may be different from the GGSN that receives that IGMP/MLD joins request.GGSN starts a MBMS Active Timer, because GGSN might can not receive the response from SGSN, for example: SGSN or UE do not support MBMS.
4b.SGSN return MBMS push-notification-answer (reason) (MBMSNotification Response (Cause)) to the GGSN that sends the MBMS notice request, reason wherein points out partly whether the MBMS context activation can be processed.If the reason part authorization by direction that comprises in the response message that GGSN receives is unsuccessful, GGSN just should not send further MBMS notification request message, and whole flow process stops.
Step 5, SGSN send request MBMS context activation message to UE;
Wherein, SGSN sends request MBMS context activation message (Request MBMS ContextActivation) (carrying IP multicast address, APN, the NSAPI of connection, Transaction Identifier TI) to UE, and request UE activates MBMS UE context.The NSAPI that connects makes that UE can be with MBMS UE context and be used for sending the PDP Context that IGMP/MLD adds message associate in step 2.TI is selected by SGSN, comprises the value that can not used by other MBMS UE context of other any PDP Context that has activated and this UE.
Step 6, UE send to SGSN and activate the MBMS context request;
Wherein, UE creates a MBMS UE context, and sends activation MBMS context request (Activate MBMS Context Request) message (carrying IP multicast address, APN, MBMS_NSAPI, MBMS bearing capacity) to SGSN.IP multicast address identification UE wants the MBMS multicast service that adds/activate.APN may specify a specific GGSN.The QoS of the maximum that MBMS bearing capacity indication UE can handle, MBMS_NSAPI is selected by UE, has comprised the value that can not used by other MBMSUE context of other any PDP Context that has activated and this UE.If this moment, SGSN had the pairing MBMS bearer context of this MBMS bearer service information, SGSN just needs the MBMS bearing capacity of checking UE whether to satisfy the requirement of this MBMS bearer service.If SGSN judges the MBMS bearing capacity that the MBMS bearing capacity region of UE requires, SGSN will refuse the request of MBMS context activation, and provides and make cause description.
Step 7, SGSN send the MBMS notice request to GGSN, and GGSN returns the response of MBMS notice refusal to SGSN;
Wherein:
If MBMS UE context is not set up, SGSN returns MBMS notice refusal request (reason) (MBMSNotification Reject Request (Cause)) message to the GGSN that sends MBMS notice request (MBMSNotification Request) message, and wherein what MBMS UE context is reason partly be indicated as being does not have and can be established.
GGSN then returns MBMS notice refusal response (MBMS Notification RejectResponse) message to SGSN.Do like this and just prevent that GGSN from continuing to send MBMS notice request (MBMS NotificationRequest) message.Whole flow process stops.
Carry out safety function between step 8, UE and the SGSN, for example: UE is authenticated.
Step 9, SGSN send to wireless access network (RAN) and call tracking (Invoke Trace) message;
Wherein, under the A/Gb pattern, be activated if the BSS of RAN follows the trail of (BSS trace), SGSN can send to BSS and call tracking (Invoke Trace) message (carry the tracking reference, follow the trail of type, trigger Id and OMC sign).Follow the trail of reference and duplicate from tracked information with the tracking type, tracked information is received from HLR or OMC.
Step 10, SGSN send to GGSN and create the MBMS context request;
Wherein, SGSN creates MBMS UE context, and sends establishment MBMS context request (Create MBMS Context Request) message to GGSN, carry IP multicast address, APN, MBMS_NSAPI, IMSI, MSISDN, RAI, IMEI-SV, RAT Type, MS Time Zone, CGI/SAI, Trace Reference, Trace Type, Trigger Id, OMC Identity, Additional MBMS Trace Info).If GGSN follows the trail of and is activated, SGSN can comprise the tracking reference, follows the trail of type, triggers Id and OMC sign.If BM-SC follows the trail of and is activated, SGSN can comprise additional MBMS tracked information.SGSN can duplicate the tracking reference from tracked information, follow the trail of type and OMC sign, and tracked information is received from HLR or OMC.Whether comprise CGI/SAI, the rule in the 15.1.1a joint that need follow at TS 23.060.
Step 11, GGSN send the MBMS authorization requests to BM-SC, and BM-SC is to GGSN feedback MBMS authorization response;
Wherein:
GGSN sends MBMS authorization requests (MBMS Authorization Request) message to BM-SC and (carries IMSI, MSISDN, RAI, IMEI-SV, RAT Type, MS Time Zone, CGI/SAI, AdditionalMBMS Trace Info), obtain mandate to the UE that is activating.If BM-SC follows the trail of and is activated, GGSN can comprise additional MBMS tracked information.If available, also comprise CGI/SAI.
BM-SC provides in MBMS authorization response (MBMS Authorization Response) message and authorizes decision.BM-SC creates MBMS UE context.
Step 12, GGSN send the MBMS register requirement to BM-SC, and BM-SC is to GGSN feedback MBMS registration response;
Wherein:
If not at the MBMS bearer context of this MBMS bearer service, GGSN just sends MBMS register requirement (MBMS Registration Request) message to BM-SC to GGSN at this moment.
If also be not this MBMS bearer service distribution T MGI this moment, BM-SC will distribute a new TMGI, this TMGI can pass to GGSN and SGSN by MBMS registration response (MBMS Registration Response) message, further, send to UE by activating MBMS context acceptance (Activate MBMS ContextAccept) message.
A MBMS registration of BM-SC response response (MBMS Registration Response) message, comprising at this MBMS bearer service ground MBMS bearer context information, and the sign of initiating the GGSN of register requirement added in " List of downstream nodes " parameter in the MBMS bearer context on the BM-SC.
Step 13, GGSN send to SGSN and create the MBMS context response;
Wherein, GGSN creates MBMS UE context, and sends establishment MBMS context response (Create MBMS Context Response) message to SGSN.
Step 14, SGSN initiate the MBMS register requirement to GGSN, and GGSN is to SGSN feedback MBMS registration response;
Wherein, if SGSN this moment does not also have the MBMS bearer context information at this MBMS bearer service, SGSN just initiates MBMS register requirement (MBMS Registration Request) message to GGSN.
A MBMS registration of GGSN response response (MBMS Registration Response) message, comprising at this MBMS bearer service ground MBMS bearer context information, and the sign of initiating the SGSN of register requirement added in " List of downstrcam nodes " parameter in the MBMS bearer context on the GGSN.
The MBMS context is to the preparation of RAN between step 15, RAN and the SGSN;
Wherein, set up a PS RAB if be at least this UE this moment, SGSN just provides MBMS UE context to the RAN of Iu pattern.
Step 16, SGSN send to RAN and call tracking;
Wherein, under the Iu pattern, be activated if follow the trail of, SGSN will send to RAN and call tracking (InvokeTrace) message (carry the tracking reference, follow the trail of type, trigger Id and OMC sign).Follow the trail of reference and duplicate from tracked information with the tracking type, tracked information is received from HLR or OMC.
Illustrate: when follow the trail of activating is when triggering by signaling method, suitable step 16.Trigger to follow the trail of by OMC during other optional mode and activate.Following the trail of the details of activation describes in TS 32.422.
Step 17, SGSN send to UE and activate the acceptance of MBMS context;
Wherein, SGSN sends to UE and activates MBMS context acceptance (Activate MBMS Context Accept) message (carrying TMGI, the MBMS bearing capacity).The MBMS bearing capacity is indicated the QoS of the maximum of this MBMS bearer service use, and when more MBMS bearer service was activated, the MBMS bearing capacity can be included into the scope of consideration.If do not verify the MBMS bearing capacity of UE, just can verify the MBMS bearing capacity of UE this moment in step 6.If SGSN judges the MBMS bearing capacity of UE and is lower than the MBMS bearing capacity of requirement that SGSN will refuse the request of MBMS context activation, and returns suitable reason.Simultaneously, SGSN can initiate the deexcitation flow process, and the MBMS UE that has set up is carried out deexcitation up and down.
Step by above-mentioned MBMS activating multicast service flow process as can be known, GGSN is when BM-SC initiates authorization requests in the prior art, if the mandate to UE is not passed through in BM-SC, then whole flow process can stop at GGSN, and can not notify UE.If UE can not receive the result of its activation of service in the regular hour, it will constantly send service activation request to network, will increase the weight of the load of core net like this.
Summary of the invention
The objective of the invention is to, authorization failure process method and system in a kind of multimedia broadcast/group broadcast service are provided, make UE when not allowing to activate the MBMS business, do not reattempt and initiate to activate request, thereby the saving Internet resources, and alleviate the load of network to a certain extent.
Technical scheme of the present invention is: authorization failure process method in a kind of multimedia broadcast/group broadcast service, in, when the mandate of subscriber equipment in service management do not passed through, network side sent authorization failure information to described subscriber equipment.
Method of the present invention may further comprise the steps: described subscriber equipment sends multimedia broadcast/group broadcast service (MBMS) to network side and joins request; Network side entity and described service management are carried out alternately user or business being carried out authorisation process; Whether described network side entity is to authorizing by judging, if not, then described network side entity sends authorization failure information to described subscriber equipment.
Described authorization failure information comprises: failure cause information.
Method of the present invention comprises following concrete steps: described subscriber equipment activates packet data protocol (PDP) context, and sends IGMP adding message or MLD adding message (Joining message) in described packet data protocol (PDP) context; Described network side sends multimedia broadcast/group broadcast service (MBMS) authorization requests (MBMS Authorization Request) to described service management; If by authorizing, described service management does not contain the authorization response that the described subscriber equipment of indication is not authorized to the receiving multimedia broadcasting/multicasting service data to described network side feedback packet to described subscriber equipment; Whether to authorizing by judging, if not, described network side sends authorization failure information to described subscriber equipment to described network side according to the authorization response that receives.
Described network side sends authorization failure information to described subscriber equipment and comprises: network side entity directly sends authorization failure information to described user side; Perhaps network side entity sends authorization failure information by the network side intermediate node to described user side.
Described network side entity is critical point GPRS Support Node (GGSN); Described service management is arranged in broadcasting/packet service server (BM-SC), user attaching server (HLR/HSS) or critical point GPRS Support Node; Described network side intermediate node comprises: Serving GPRS Support Node (SGSN), base stations control and/or wireless network control (BSC/RNC).
The present invention also provides authorization failure treatment system in a kind of multimedia broadcast/group broadcast service, comprising: subscriber equipment, network side entity and Service Management Unit; Described Service Management Unit has authorization failure information generating portion, and described network side entity has the authorization failure judgment part; Wherein said authorization failure information generating portion, be used for when described subscriber equipment the mandate of described Service Management Unit not by the time generate authorization failure information, and give described network side entity with described authorization failure feedback information; Whether described authorization failure judgment part is used for according to the authorization failure information that receives authorizing by judging, if not, described network side entity sends authorization failure information to described subscriber equipment.
Described subscriber equipment activates packet data protocol (PDP) context, and sends IGMP adding message or MLD adding message (Joining message) in described packet data protocol (PDP) context; Described critical point GPRS Support Node sends multimedia broadcast/group broadcast service (MBMS) authorization requests (MBMS Authorization Request) to the Service Management Unit that is positioned at the broadcasting/packet service server; The authorization failure information generating portion of described Service Management Unit generates and includes the authorization response that the described subscriber equipment of indication is not authorized to the receiving multimedia broadcasting/multicasting service data; Described broadcasting/packet service server contains the authorization response that the described subscriber equipment of indication is not authorized to the receiving multimedia broadcasting/multicasting service data to described critical point GPRS Support Node feedback packet; The authorization failure judgment part of described critical point GPRS Support Node, according to the authorization response that receives to whether authorizing by judging, if not, described critical point GPRS Support Node sends authorization failure information to described subscriber equipment, and perhaps described critical point GPRS Support Node sends authorization failure information by described Serving GPRS Support Node to described subscriber equipment.
Beneficial effect of the present invention is, make UE network side when carrying out the failure of MBMS service authorization must use clear and definite message informing UE, thereby make UE no longer continue to send MBMS group ripple service activation request, reduced the unnecessary messages expense, saved Internet resources.
Description of drawings
Fig. 1 is a wireless network architecture block diagram of supporting broadcasting/packet service in the prior art;
Fig. 2 is the structured flowchart of prior art BM-SC;
Fig. 3 is a MBMS activating multicast service flow chart in the prior art;
Fig. 4 is the inventive method flow chart;
Fig. 5 is the MBMS activating multicast service flow chart during authorization failure in BM-SC of UE among the present invention;
Fig. 6 be in the embodiment of the invention 1 UE in BM-SC behind the authorization failure GGSN directly send the flow chart of failure notice message to UE;
Fig. 7 be in the embodiment of the invention 2 UE in BM-SC behind the authorization failure GGSN send the flow chart of failure notice message to UE by SGSN;
Fig. 8 is a system architecture diagram of the present invention.
Embodiment
Below in conjunction with description of drawings the specific embodiment of the present invention.The invention provides authorization failure process method and system in a kind of multimedia broadcast/group broadcast service, if the mandate of UE in BM-SC do not passed through, then network side can activate the response of failure to the UE loopback.UE receives that this failure response can select according to the cause value that returns later on---be to initiate to activate request again or stop to initiate to activate request.Like this, when UE learns that it does not allow to activate the MBMS business, will not reattempt and initiate to activate request, thereby save Internet resources, alleviate the load of network to a certain extent.
Key point of the present invention is to add a kind of decision mechanism in GGSN, Fig. 4 shows basic procedure of the present invention, that is: after the authorization requests of finding UE is by the BM-SC refusal, initiate a failure announcement process from the network side to UE, with corresponding failure cause notice UE, make UE can carry out next step processing.
MBMS activating multicast service flow process of the present invention as shown in Figure 5, wherein step comprises:
Step 1 ', UE activates PDP Context;
Wherein, if there is not the PDP Context of activation, UE activates a general PDP Context.
Step 2 ', UE send to add message to GGSN;
Wherein, UE sends IGMP (IPv4) on the PDP Context of acquiescence or MLD (IPv6) adds message (Joining message), shows that its preparation receives specific multicast MBMS bearer service, and this bearer service is identified by IP multicast address.
Step 3 ', GGSN sends the MBMS authorization requests to BM-SC;
Wherein, GGSN sends MBMS authorization requests (MBMS Authorization Request) to BM-SC, to obtain making UE receive the mandate of data.The MBMS authorization requests may comprise tracked information (traceinformation).If UE by authorizing, does not point out in authorization response that then UE is not authorized to receive the MBMS data.
Step 4 ', GGSN initiates the failure announcement process from the network side to UE;
Wherein, GGSN initiates the failure announcement process from the network side to UE, and the message in this process can directly send to UE from GGSN, also can be that GGSN sends to UE by SGSN.The mode of concrete failure announcement can be to use new message, also can be to increase new parameter in original message.For the situation that the mandate of UE is refused by BM-SC, UE will no longer initiate new MBMS activating multicast service request after receiving the failure announcement.
Embodiment one: GGSN directly sends the failure notice message to UE
If GGSN learns UE by authorizing from the authorization response message of BM-SC, GGSN can directly send the failure notice message to UE, and notice UE is the mandate by network not.Then Ci Shi MBMS activating multicast service process as shown in Figure 6, comprising:
1. if there is not the PDP Context of activation, UE activates a general PDP Context;
Add message (Joining message) 2.UE send IGMP (IPv4) or MLD (IPv6) on the PDP Context of acquiescence, show that its preparation receives specific multicast MBMS bearer service, this bearer service is identified by IP multicast address;
3.GGSN send MBMS authorization requests (MBMS Authorization Request) to BM-SC, to obtain to make UE receive the mandate of data.The MBMS authorization requests may comprise tracked information (traceinformation); If UE by authorizing, does not point out in authorization response that then UE is not authorized to receive the MBMS data;
4.GGSN directly send failure notice message (Failure Notification), have the reason of UE authorization failure in this message to UE.For the situation that the mandate of UE is refused by BM-SC, UE will no longer initiate new MBMS activating multicast service request after receiving the failure announcement.
Embodiment two: GGSN sends the failure notice message by SGSN to UE
If GGSN learns UE by authorizing from the authorization response message of BM-SC, GGSN also can send the failure notice message to UE by SGSN, and notice UE is the mandate by network not.Then the MBMS of this moment organizes ripple activation of service process as shown in Figure 7, comprising:
(1) if there is not the PDP Context of activation, UE activates a general PDP Context;
(2) UE sends IGMP (IPv4) or MLD (IPv6) adding message (Joining message) on the PDP Context of acquiescence, shows that its preparation receives specific multicast MBMS bearer service, and this bearer service is identified by IP multicast address;
(3) GGSN sends MBMS authorization requests (MBMS Authorization Request) to BM-SC, to obtain making UE receive the mandate of data.The MBMS authorization requests may comprise tracked information (traceinformation).If UE by authorizing, does not point out in authorization response that then UE is not authorized to receive the MBMS data;
(4) GGSN sends MBMS failure notice message (MBMS Failure Notification) to SGSN, and failure cause wherein indicates UE not by authorizing;
(5) SGSN sends failure notice message (Failure Notification) to UE, and failure cause wherein is for sending the MBMS failure by the cause value the message from GGSN.
Embodiment three: GGSN is authorization failure treatment system in the multimedia broadcast/group broadcast service of UE transmission failure notice message directly
As shown in Figure 8, support that the wireless network architecture of broadcasting/packet service is broadcasting/packet service server (BM-SC), BM-SC passes through Gmb interface or Gi interface and critical point GPRS Support Node (GGSN, GatewayGPRS Support Node) and links to each other, and a BM-SC can link to each other with a plurality of GGSN; GGSN links to each other by Gn/Gp interface and Serving GPRS Support Node (SGSN, Serving GPRS Support Node), and a GGSN can link to each other with a plurality of SGSN; SGSN can link to each other with universal mobile telecommunications system (UMTS) land radio access web (UTRAN) by the Iu interface, UTRAN links to each other with user terminal (UE) by the Uu interface then, SGSN also can strengthen wireless access network (GERAN) by Iu/Gb interface and global system for mobile communications (GSM) and link to each other, and GERAN links to each other with UE by Um Interface then.Wherein, GGSN and SGSN belong to the node in the core net in the wireless network (CN).
If GGSN learns UE by authorizing from the authorization response message of BM-SC, GGSN directly sends the failure notice message to UE, and notice UE is the mandate by network not.Wherein:
The Service Management Unit of BM-SC has authorization failure information generating portion, and described GGSN has the authorization failure judgment part; Wherein
Described authorization failure information generating portion, be used for when UE the mandate of described Service Management Unit not by the time generate authorization failure information, and give GGSN with described authorization failure feedback information;
Described authorization failure judgment part, be used for according to the authorization failure information that receives whether authorizing by judging, if not, GGSN sends authorization failure information to UE, that is: described authorization failure information sends part and directly the authorization failure information that receives sent to UE.
Described network side entity can be critical point GPRS Support Node (GGSN); Described Service Management Unit can be arranged in broadcasting/packet service server (BM-SC), user attaching server (HLR/HSS) or critical point GPRS Support Node.
In specifically implementing, UE activates packet data protocol (PDP) context, and sends IGMP adding message or MLD adding message (Joining message) in described packet data protocol (PDP) context;
GGSN sends multimedia broadcast/group broadcast service (MBMS) authorization requests (MBMS Authorization Request) to the Service Management Unit that is positioned at BM-SC;
The authorization failure information generating portion of described Service Management Unit generates and includes the authorization response that indication UE is not authorized to the receiving multimedia broadcasting/multicasting service data;
BM-SC contains the authorization response that the described subscriber equipment of indication is not authorized to the receiving multimedia broadcasting/multicasting service data to the GGSN feedback packet;
The authorization failure judgment part of GGSN, whether to authorizing by judging, if not, GGSN sends authorization failure information to described subscriber equipment according to the authorization response that receives.
Embodiment four: GGSN is by SGSN (or multistage network side intermediate node) authorization failure treatment system in the multimedia broadcast/group broadcast service of UE transmission failure notice message
As shown in Figure 8, support that the wireless network architecture of broadcasting/packet service is broadcasting/packet service server (BM-SC), BM-SC passes through Gmb interface or Gi interface and critical point GPRS Support Node (GGSN, GatewayGPRS Support Node) and links to each other, and a BM-SC can link to each other with a plurality of GGSN; GGSN links to each other by Gn/Gp interface and Serving GPRS Support Node (SGSN, Serving GPRS Support Node), and a GGSN can link to each other with a plurality of SGSN; SGSN can link to each other with universal mobile telecommunications system (UMTS) land radio access web (UTRAN) by the Iu interface, UTRAN links to each other with user terminal (UE) by the Uu interface then, SGSN also can strengthen wireless access network (GERAN) by Iu/Gb interface and global system for mobile communications (GSM) and link to each other, and GERAN links to each other with UE by Um Interface then.Wherein, GGSN and SGSN belong to the node in the core net in the wireless network (CN).
If GGSN learns UE by authorizing from the authorization response message of BM-SC, GGSN also can send the failure notice message to UE by SGSN, and notice UE is the mandate by network not.Wherein:
The Service Management Unit of BM-SC has authorization failure information generating portion, and described GGSN has the authorization failure judgment part; Wherein
Described authorization failure information generating portion, be used for when UE the mandate of described Service Management Unit not by the time generate authorization failure information, and give GGSN with described authorization failure feedback information;
Whether described authorization failure judgment part is used for according to the authorization failure information that receives authorizing by judging, if not, GGSN sends authorization failure information to SGSN, and SGSN is transmitted to UE with the authorization failure information that receives.
Described network side entity can be critical point GPRS Support Node (GGSN); Described Service Management Unit can be arranged in broadcasting/packet service server (BM-SC), user attaching server (HLR/HSS) or critical point GPRS Support Node; Described network side intermediate node comprises: Serving GPRS Support Node (SGSN), base stations control and/or wireless network control (BSC/RNC).
In specifically implementing, UE activates packet data protocol (PDP) context, and sends IGMP adding message or MLD adding message (Joining message) in described packet data protocol (PDP) context;
GGSN sends multimedia broadcast/group broadcast service (MBMS) authorization requests (MBMS Authorization Request) to the Service Management Unit that is positioned at BM-SC;
The authorization failure information generating portion of described Service Management Unit generates and includes the authorization response that indication UE is not authorized to the receiving multimedia broadcasting/multicasting service data;
BM-SC contains the authorization response that the described subscriber equipment of indication is not authorized to the receiving multimedia broadcasting/multicasting service data to the GGSN feedback packet;
The authorization failure judgment part of GGSN, whether to authorizing by judging, if not, GGSN sends authorization failure information to SGSN according to the authorization response that receives, and SGSN (or multistage network side intermediate node) sends authorization failure information to UE.
The invention enables UE network side when carrying out the failure of MBMS service authorization must use clear and definite message informing UE, thereby make UE no longer continue to send MBMS group ripple service activation request, reduced the unnecessary messages expense, saved Internet resources.
Above embodiment only is used to illustrate the present invention, but not is used to limit the present invention.
Claims (10)
1. authorization failure process method in the multimedia broadcast/group broadcast service is characterized in that, the mandate of subscriber equipment in service management by the time, network side sends authorization failure information to described subscriber equipment.
2. method according to claim 1 is characterized in that, may further comprise the steps:
Described subscriber equipment sends multimedia broadcast/group broadcast service to network side and joins request;
Network side entity and described service management are carried out alternately user or business being carried out authorisation process;
Whether described network side entity is to authorizing by judging, if not, then described network side entity sends authorization failure information to described subscriber equipment.
3. method according to claim 2 is characterized in that, described authorization failure information comprises: failure cause information.
4. method according to claim 1 is characterized in that, comprises following concrete steps:
Described subscriber equipment sends IGMP adding message or the multicast audience finds to add message;
Described network side sends the multimedia broadcast/group broadcast service authorization requests to described service management;
If by authorizing, described service management does not contain the authorization response that the described subscriber equipment of indication is not authorized to the receiving multimedia broadcasting/multicasting service data to described network side feedback packet to described subscriber equipment;
Whether to authorizing by judging, if not, described network side sends authorization failure information to described subscriber equipment to described network side according to the authorization response that receives.
5. method according to claim 4 is characterized in that, described network side sends authorization failure information to described subscriber equipment and comprises:
Network side entity directly sends authorization failure information to described user side; Perhaps
Network side entity sends authorization failure information by the network side intermediate node to described user side.
6. method according to claim 5 is characterized in that,
Described network side entity is the critical point GPRS Support Node;
Described service management is arranged in broadcasting/packet service server, user attaching server or critical point GPRS Support Node;
Described network side intermediate node comprises: Serving GPRS Support Node, base stations control and/or wireless network control.
7. authorization failure treatment system in the multimedia broadcast/group broadcast service comprises: subscriber equipment, network side entity and Service Management Unit; It is characterized in that described Service Management Unit has authorization failure information generating portion, described network side entity has the authorization failure judgment part; Wherein
Described authorization failure information generating portion, be used for when described subscriber equipment the mandate of described Service Management Unit not by the time generate authorization failure information, and give described network side entity with described authorization failure feedback information;
Whether described authorization failure judgment part is used for according to the authorization failure information that receives authorizing by judging, if not, described network side entity sends authorization failure information to described subscriber equipment.
8. system according to claim 7 is characterized in that, also comprises: the network side intermediate node; Described authorization failure information sends part the authorization failure information that receives is sent to described network side intermediate node, and described network side intermediate node is transmitted to described subscriber equipment with the authorization failure information that receives.
9. system according to claim 8 is characterized in that,
Described network side entity is the critical point GPRS Support Node;
Described Service Management Unit is arranged in broadcasting/packet service server, user attaching server or critical point GPRS Support Node;
Described network side intermediate node comprises: Serving GPRS Support Node, base stations control and/or wireless network control.
10. system according to claim 9 is characterized in that,
Described subscriber equipment sends IGMP adding message or multicast audience and finds to add message;
Described critical point GPRS Support Node sends the multimedia broadcast/group broadcast service authorization requests to the Service Management Unit that is positioned at the broadcasting/packet service server;
The authorization failure information generating portion of described Service Management Unit generates and includes the authorization response that the described subscriber equipment of indication is not authorized to the receiving multimedia broadcasting/multicasting service data;
Described broadcasting/packet service server contains the authorization response that the described subscriber equipment of indication is not authorized to the receiving multimedia broadcasting/multicasting service data to described critical point GPRS Support Node feedback packet;
The authorization failure judgment part of described critical point GPRS Support Node, whether to authorizing by judging, if not, described critical point GPRS Support Node sends authorization failure information to described subscriber equipment, perhaps according to the authorization response that receives
Described critical point GPRS Support Node sends authorization failure information by described Serving GPRS Support Node to described subscriber equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100734424A CN101047976A (en) | 2006-03-27 | 2006-03-27 | Authorization failure process method and system in multimedia broadcast/multicast service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100734424A CN101047976A (en) | 2006-03-27 | 2006-03-27 | Authorization failure process method and system in multimedia broadcast/multicast service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101047976A true CN101047976A (en) | 2007-10-03 |
Family
ID=38772097
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006100734424A Pending CN101047976A (en) | 2006-03-27 | 2006-03-27 | Authorization failure process method and system in multimedia broadcast/multicast service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101047976A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102932856A (en) * | 2011-08-08 | 2013-02-13 | 华为技术有限公司 | PLMN (Public Land Mobile Network)-crossed access control method, device and system |
| CN102104633B (en) * | 2009-12-17 | 2015-06-17 | 康佳集团股份有限公司 | IPv6 multicast technology-based method for customizing real time information and system thereof |
| CN106559186A (en) * | 2016-03-21 | 2017-04-05 | 天地融科技股份有限公司 | Data transmission method and system, main communication apparatus and from communication apparatus |
| CN106561014A (en) * | 2015-11-18 | 2017-04-12 | 天地融科技股份有限公司 | Data transmission method and system, main communication equipment, and slave communication equipment |
| CN112333639A (en) * | 2019-08-01 | 2021-02-05 | 苹果公司 | Backup cellular connection for basic services |
| WO2021136467A1 (en) * | 2020-01-02 | 2021-07-08 | 维沃移动通信有限公司 | Multicast service implementing method, device, and communication device |
-
2006
- 2006-03-27 CN CNA2006100734424A patent/CN101047976A/en active Pending
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102104633B (en) * | 2009-12-17 | 2015-06-17 | 康佳集团股份有限公司 | IPv6 multicast technology-based method for customizing real time information and system thereof |
| CN102932856A (en) * | 2011-08-08 | 2013-02-13 | 华为技术有限公司 | PLMN (Public Land Mobile Network)-crossed access control method, device and system |
| CN102932856B (en) * | 2011-08-08 | 2015-09-09 | 华为技术有限公司 | Across the access control processing method of PLMN, equipment and system |
| CN106561014A (en) * | 2015-11-18 | 2017-04-12 | 天地融科技股份有限公司 | Data transmission method and system, main communication equipment, and slave communication equipment |
| CN106559186A (en) * | 2016-03-21 | 2017-04-05 | 天地融科技股份有限公司 | Data transmission method and system, main communication apparatus and from communication apparatus |
| CN112333639A (en) * | 2019-08-01 | 2021-02-05 | 苹果公司 | Backup cellular connection for basic services |
| CN112333639B (en) * | 2019-08-01 | 2023-08-22 | 苹果公司 | Backup cellular connection for basic services |
| US11778472B2 (en) | 2019-08-01 | 2023-10-03 | Apple Inc. | Backup cellular connectivity for essential services |
| WO2021136467A1 (en) * | 2020-01-02 | 2021-07-08 | 维沃移动通信有限公司 | Multicast service implementing method, device, and communication device |
| JP2023510720A (en) * | 2020-01-02 | 2023-03-15 | 維沃移動通信有限公司 | Multicast service realization method and device, communication equipment |
| JP7357797B2 (en) | 2020-01-02 | 2023-10-06 | 維沃移動通信有限公司 | Multicast service implementation method, device, and communication equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1266898C (en) | Method for realizing multimedia broadcast/multi cast service business activation | |
| CN1306766C (en) | Service recognition and route method in multimedia broadcast multicast service system | |
| CN1684414A (en) | Conversation start method for multimedia broadcast/group broadcast service | |
| CN1303799C (en) | Method for controlling multimedia broadcast/multicast service conversation | |
| CN1302686C (en) | Cell information change informing method in multimedia broadcast/multicast service | |
| CN1692578A (en) | An uplink common channel for sending feedback information | |
| CN1836389A (en) | Method for paging a user equipment by using a dedicated channel in a mobile communication system supporting an mbms(multimedia broadcast/multicast service), particularly for informing the user equipme | |
| CN1720678A (en) | Apparatus and method for establishing feedback in a broadcast or multicast service | |
| CN1717880A (en) | RRC connection request method and apparatus for mobile communications | |
| CN1592167A (en) | Method for supporting MBMS backward compatibility | |
| CN101043252A (en) | Method and system for transmitting MBMS mechanism based IMS service | |
| CN1798063A (en) | Method at network side for obtaining situation of receiving multimedia broadcasting / multicasting service by users | |
| CN101056448A (en) | Method for detecting the service quality parameters and network side communication device | |
| CN101039503A (en) | Method for realizing paging in multimedia broadcasting/multicast service | |
| CN101047976A (en) | Authorization failure process method and system in multimedia broadcast/multicast service | |
| CN1859305A (en) | Method for establishing GTP tunnel in multimedia broadcast/multicast service | |
| CN100346596C (en) | Method for activating service of multimedia broadcast/group broadcast service | |
| CN1581744A (en) | Method for providing multiple QOS for MBMS business | |
| CN1735057A (en) | Method for building bearing in multimedia broadcast/multicast service | |
| CN1691676A (en) | Method for determining number of receiving users in multimedia broadcast/multicast service | |
| CN1180639C (en) | Radio channel configuration selecting method in multicast service | |
| CN1677971A (en) | Method for realizing activation of multi-media broadcasting/multicast service | |
| CN1968451A (en) | Method and system for determining to use multicast/broadcast service time | |
| CN1933439A (en) | Realizing method and apparatus for user joining multi casting/broadcasting business | |
| CN1794859A (en) | Method of realizing active in multimedia gooup broadcasting service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |