CN1756422A - Method for controlling multimedia broadcast/multicast service conversation start - Google Patents

Method for controlling multimedia broadcast/multicast service conversation start Download PDF

Info

Publication number
CN1756422A
CN1756422A CNA2004100805365A CN200410080536A CN1756422A CN 1756422 A CN1756422 A CN 1756422A CN A2004100805365 A CNA2004100805365 A CN A2004100805365A CN 200410080536 A CN200410080536 A CN 200410080536A CN 1756422 A CN1756422 A CN 1756422A
Authority
CN
China
Prior art keywords
sgsn
mbms
ggsn
node listing
session
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CNA2004100805365A
Other languages
Chinese (zh)
Other versions
CN100366030C (en
Inventor
张海
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CNB2004100805365A priority Critical patent/CN100366030C/en
Publication of CN1756422A publication Critical patent/CN1756422A/en
Application granted granted Critical
Publication of CN100366030C publication Critical patent/CN100366030C/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a method to control dialog starting in MBMS. Wherein, configuring SGSN node list contained all service area to every business; then, GGSN acquires the list and determines whether admits SGSN have a special MBMS dialog in MBMS registration process or MBMS dialog starting process according to said list. This method can decrease unnecessary signaling load and network cost.

Description

A kind ofly control the method that multimedia broadcast/multicast service conversation begins
Technical field
The present invention relates to multi-medium broadcast/group broadcast service (MBMS) session technology, refer to the method that a kind of MBMS of control session begins especially.
Background technology
Development along with the 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 support the multiple business form, such as: services such as Internet network are downloaded, browsed at a high speed to visual telephone, picture.Wherein, have a class business features to be: can be simultaneously give customized in the wireless network should business all users send, such as: send weather forecast, news film, sports tournament collection of choice specimens or the like.So 3G (Third Generation) Moblie has been introduced the notion of broadcast/group broadcast.
Referring to shown in Figure 1, for an intermediate node, such as node 10, 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 was received data, the number of nodes that receives data according to its downstream expectation duplicated this data, and distributed this data to the node of each these data of expectation reception of its downstream.Like this, each bar branch of multicast/broadcast business data transmission tree all has only a piece of data to transmit, and takies a transfer resource, and 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. 2 is for supporting the wireless network architecture schematic diagram of broadcasting/packet service, as shown in Figure 2, in the existing third generation partner program (3GPP), support that the wireless network architecture of broadcasting/packet service is a broadcasting/packet service server (BM-SC) 201, BM-SC 201 is by Gmb interface or Gi interface and TPF critical point GPRS Support Node (GGSN, Gateway GPRS Support Node) 202 link to each other, and a BM-SC201 can link to each other with a plurality of TPF GGSN 202; TPF GGSN 202 links to each other by Gn/Gp interface and Serving GPRS Support Node (SGSN, Serving GPRS Support Node) 203, and a GGSN 202 can link to each other with a plurality of SGSN 203; SGSN 203 can link to each other with universal mobile telecommunications system (UMTS) land radio access web (UTRAN) 204 by the Iu interface, UTRAN 204 links to each other with user terminal (UE) 206 by the Uu interface then, SGSN 203 also can strengthen wireless access network (GERAN) 205 by Iu/Gb interface and global system for mobile communications (GSM) and link to each other, and GERAN 205 links to each other with UE 207 by Um Interface then.Wherein, GGSN and SGSN belong to the node in the core net in the wireless network (CN).
In the MBMS business, what be used to preserve the MBMS bearing capacity is the MBMS bearer context, and this MBMS bearer context comprises all information descriptions that define a MBMS service bearer, and this MBMS bearer context is created at all nodes of carrying MBMS data.Referring to shown in the table one, the MBMS bearer context comprises: IP multicast address, APN (APN), Temporary Mobile Group Identity (TMGI), state (State), the MBMS bearing capacity that requires, QoS, MBMS coverage, downstream node listing, UEs quantity etc.Wherein, the IP multicast address sign is by the MBMS carrying of this MBMS bearer context description; The APN that APN has been defined for this IP multicast address; TMGI is a Temporary Mobile Group Identity of distributing to the MBMS carrying; State is the activity state of MBMS carrying, comprising: inactive state or state of activation, and whether sign requires to set up the load plane resource that is used for the MBMS transfer of data; The MBMS bearing capacity that requires is used to identify the minimum bearing capacity that UE need support; QoS is the service quality of this MBMS load bearing requirements; The zone that the MBMS coverage sends for the MBMS service needed; The downstream node listing is for having asked the MBMS carrying, the downstream node listing that the MBMS data must be issued to; The UE ground quantity that adds this multicast service that UEs quantity has for this node." X " in the table is illustrated on the corresponding network entity and stores this information.
Parameter Describe RAN SGSN GGSN BM-SC
IP multicast address The MBMS carrying that the IP multicast address sign is described by this MBMS bearer context X X X X
APN The APN that this IP multicast address has been defined X X X Wait to study
TMGI Distributing to the interim of MBMS carrying moves X X X X
Group id
State The activity state (' static ' or ' activation ') of MBMS carrying Wait to study X X X
The MBMS bearing capacity that requires The minimum bearing capacity that sign UE need support X X X
QoS The service quality of this MBMS load bearing requirements X X X X
The MBMS coverage The zone that the MBMS service needed sends X X X X
The downstream node listing Asked the MBMS carrying, the downstream node listing that the MBMS data must be issued to X X X
UEs quantity The UE ground quantity that adds this multicast service that this node has Wait to study X X Wait to study
Table one
Trigger the MBMS session and begin process when BM-SC is ready to send data, the session process that begins activates in the network and is used for the bearing resource of all needs of transferring MBMS service data, and notifies interested UE to be about to begin transfer of data.Begin process by this session, BM-SC offers interested relevant network node with the QoS of MBMS, MBMS business domains, the session attributes such as estimation length of session parameter that may exist; Begin process by this session, can cause relevant RNC and carry out work such as conversation informing, community user counting, radio bearer type selection, wireless and wired load plane foundation at Access Network.BM-SC etc. flow after node finishes relevant work to the downstream, the beginning muticast data transmission, and the carrying multicast data transmission that each node begins to set up in the process by session is until UE.
Before existing MBMS multicast conversation begins, the MBMS registration process that SGSN, GGSN node can cause by processes such as MBMS activating multicast service, Routing Area Updates node is at its upstream registered, and finishes among its upstream node GGSN, the BM-SC filling in of downstream node listing in the MBMS bearer context that is:.Here, the upstream node of GGSN is BM-SC, and downstream node is SGSN.
The MBMS registration process comprises the steps: as shown in Figure 3 in the prior art
Step 301: the UE that detects its administration when Drift Radio Network Controller is interested in the MBMS bearer service, and Drift Radio Network Controller is not also registered this MBMS business, Drift Radio Network Controller sends a MBMS login request message to SGSN under self, carry the parameter of this MBMS bearer service of sign in this login request message, i.e. IP multicast address and APN.
Step 302: if SGSN does not have the MBMS bearer context at above-mentioned MBMS bearer service, and this SGSN receives the register requirement of this MBMS bearer service from certain RNC; Perhaps be that a MBMS bearer service is created first MBMS UE context, and there is not corresponding M BMS bearer context among the SGSN, SGSN is according to the IP multicast address and the APN that carry in login request message or the MBMS UE context, create a MBMS bearer context, this bearer context does not comprise information such as TMGI, bearing capacity requirement, and this MBMS bearer context is an armed state, sends a MBMS login request message of carrying IP multicast address and APN again to GGSN.
Step 303: if GGSN does not have the MBMS bearer context at above-mentioned MBMS bearer service, and GGSN receives the register requirement of this MBMS bearer service from a SGSN; Perhaps be that a MBMS bearer service is created first MBMS UE context, and there is not corresponding M BMS bearer context among the GGSN, then GGSN creates a MBMS bearer context, this MBMS bearer context is an armed state, and sends a MBMS login request message of carrying IP multicast address and APN to BM-SC.
Step 304: in case receive the MBMS register requirement from a GGSN, BM-SC just is increased to the sign of this GGSN in " the downstream node listing " of self MBMS bearer context, and respond a MBMS registration reply message, wherein contain parameters such as TMGI, bearing capacity requirement.If the MBMS bearer context of BM-SC is in " activation " state, BM-SC triggers and the session of this GGSN begins process.
Step 305: if GGSN receives a login request message from the described SGSN of step 302, GGSN is increased to the sign of SGSN in " the downstream node listing " of self MBMS bearer context; And return the MBMS registration reply message to SGSN, carry parameters such as TMGI and bearing capacity requirement in this response message; If the MBMS bearer context is in " activation " state, then the GGSN triggering begins process with the session of SGSN.
Step 306: if SGSN receives the MBMS register requirement from the described Drift Radio Network Controller of step 301, SGSN is increased to the sign of RNC in " the downstream stream node listing " of self MBMS bearer context; And return a MBMS registration reply message and give this RNC; If the MBMS bearer context is in " activation " state, then SGSN initiates to begin process with the session of this Drift Radio Network Controller.
MBMS multicast service conversation of the prior art begins flow process as shown in Figure 4, may further comprise the steps:
The GGSN that step 401:BM-SC preserves in " downstream node listing " parameter in its corresponding MBMS bearer context sends session and begins request message Session Start Request, the indication transmission that is about to begin, and the status attribute that the MBMS bearer context is set is " activation ".QoS, MBMS business domains are provided in this request, have estimated the session attributes such as length of this session.
After GGSN receives that session begins request message, the session attribute that provides in this message is provided in the MBMS bearer context, the status attribute that the MBMS bearer context is set is " activation ", and returns session to BM-SC and begin response message Session Start Response.
The SGSN that step 402:GGSN preserves in " downstream node listing " parameter in its corresponding MBMS bearer context sends MBMS session beginning request message MBMS Session Start Request.
After SGSN receives that the MBMS session begins request message, in the MBMS bearer context, preserve session attribute, and the status attribute that the MBMS bearer context is set is " activation ", return the MBMS session to GGSN and begin response message MBMS Session Start Response, the tunnel destination node sign (TEID) that is used for load plane is provided in this message, has been used for GGSN and sends the MBMS business datum.
Step 403:SGSN sends MBMS session beginning request message MBMS Session Start Request to each BSC/RNC that links to each other with self, comprises session attribute in this message.
Whether the BSC/RNC under the Iu pattern has overlapping and other factors according to the MBMS business domains in its overlay area and the session attribute, determines whether activating self MBMS bearer context.If activate, in the MBMS bearer context, preserve session attribute, the status attribute that the MBMS bearer context is set is returned the MBMS session to SGSN then and is begun responding MBMS Session Start Response message for " activation ".And RNC can comprise TEID to begin in the response message in the MBMS session, is used on the Iu load plane SGSN and carries out data and send.If the BSC under the Gb pattern does not serve the MBMS business domains, then session attribute is not preserved in decision, and its MBMS business contexts is not set to " activation ".
In this step, if the MBMS session that BSC/RNC receives a plurality of Iu of carrying load plane parameters begins request message, the MBMS session that BSC/RNC only returns a success begins response message, is used to set up an Iu planes carry that arrives SGSN.
Step 404:BSC/RNC is in the MBMS business domains, and foundation is used for the Radio Resource of transferring MBMS service data to necessity of UE interested.
For some MBMS business, as business such as local news, local weather forecast, local transport information issues, general the partial service zone to whole mobile network provides.By existing scheme, the session of a MBMS bearer service begins message can send to GGSN, the SGSN of all registrations of registering this MBMS bearer service in the all-network and all RNC that link to each other with these registrations SGSN.Wherein, RNC only after receiving that this session begins message, just can compare multicast business domains and the own zone that covers whether have overlapping, thereby determine whether to set up radio bearer.Certainly, the service bearer plane all is established before this.
For a very big network, network as China Mobile, because user's the roaming and the correlation of SGSN node and region, can cause national most SGSN all this MBMS business to be carried out corresponding registration, the session each time of the so a business (as transport information) that provides in Beijing all can relate to all RNC in the whole nation substantially.Because the MBMS business is various, such network design will inevitably cause these otiose sessions to begin message some RNC, SGSN node being caused the impact of signaling, make relevant network node carry out analysis and arrangement to some useless signalings.Simultaneously, can require GGSN, SGSN node to these irrelevant professional supports, take GGSN to SGSN, SGSN to the load plane resource between the RNC, bring the signaling traffic load that there is no need to RNC, SGSN node, increased offered load and cost.
Summary of the invention
In view of this, main purpose of the present invention is the method that provides a kind of MBMS of control session to begin can reduce the unnecessary signaling traffic load of network node, avoids the waste of network carrying resource, reduces offered load and cost.
For achieving the above object, technical scheme of the present invention is achieved in that
A kind ofly control the method that multimedia broadcast/multicast service conversation begins, this method comprises: GGSN is retrieved as the SGSN node listing that comprises professional all coverages of this MBMS of current MBMS business configuration, then according to the SGSN identification information in the SGSN node listing that is obtained, judge whether current SGSN is contained in the described SGSN node listing, if comprise, the session that then allows this SGSN to carry out specific MBMS session begins flow process, otherwise, refuse the session that this SGSN carries out specific MBMS session and begin flow process.
In the MBMS register flow path, described judgement specifically comprises:
After GGSN receives the MBMS register requirement at current MBMS business that SGSN sends, according to the SGSN node listing that is obtained, whether the SGSN that judges current initiation MBMS register requirement is included in the described SGSN node listing, if, then accept the MBMS register requirement of this SGSN, and the session that the SGSN that allows to succeed in registration carries out specific MBMS session begins flow process; Otherwise, refuse the MBMS register requirement of this SGSN.
Wherein, described SGSN node listing is stored among the BM-SC, then described GGSN obtains the SGSN node listing and is specially: after BM-SC receives the MBMS register requirement at current MBMS business that GGSN sends, return the MBMS registration response that comprises the professional pairing SGSN node listing of current MBMS to GGSN; GGSN obtains described SGSN node listing from the MBMS registration response of being received.Here, described SGSN node listing is stored among the BM-SC and is specially: directly the SGSN node listing is disposed among the BM-SC; Or, in BM-SC, preserve the corresponding relation in SGSN and geographical position, region within the jurisdiction thereof, BM-SC obtains to have the geographical SGSN node listing that occurs simultaneously according to the professional total coverage of the MBMS that obtains from content supplier and the SGSN that self preserves and the corresponding relation in geographical position, region within the jurisdiction thereof.
Perhaps, described SGSN node listing is disposed among the GGSN, and then GGSN is from self obtaining the SGSN node listing that is disposed.
Begin in the flow process in the MBMS session, described judgement specifically comprises:
After a11.GGSN receives that the session at specific MBMS session that BM-SC sends begins request, SGSN in the downstream node listing that self obtains by the MBMS registration process and SGSN in the SGSN node listing that is obtained are sought common ground;
The session that SGSN in the common factor that b12.GGSN is obtained in step a11 sends at specific MBMS session begins request, receives that this session of SGSN continuation execution that session begins to ask begins flow process.
Wherein, described SGSN node listing is disposed among the BM-SC, and then GGSN obtains the SGSN node listing that is disposed from BM-SC.Described GGSN obtains the SGSN node listing from BM-SC: BM-SC begins to ask the SGSN node listing with being disposed to send to GGSN by session; Or GGSN obtains the SGSN node listing that is disposed at BM-SC in the MBMS registration process.
Perhaps, described SGSN node listing is disposed among the GGSN, and then GGSN is from self obtaining the SGSN node listing that is disposed.
In BM-SC, preserve the corresponding relation in SGSN and its geographical position, region within the jurisdiction; This method specifically comprises:
A21.BM-SC is according to the business domains of the current MBMS business of obtaining from content supplier and SGSN and geographical position, the region within the jurisdiction corresponding relation of self preserving thereof, acquisition has the geographical SGSN node listing that occurs simultaneously, and resulting SGSN node listing is sent to GGSN;
After a22.GGSN received that the session at specific MBMS session that BM-SC sends begins request, the SGSN that the SGSN in the downstream node listing that self obtains by the MBMS registration process and BM-SC are sent sought common ground;
The session that SGSN in the common factor that a23.GGSN is obtained in step a22 sends at specific MBMS session begins request, receives that this session of SGSN continuation execution that session begins to ask begins flow process.
Wherein, the business domains of the current MBMS business of obtaining from content supplier described in the step a21 is: total coverage of current MBMS business, or be the coverage of current MBMS business at this session.The described BM-SC of step a21 sends to GGSN with the SGSN node listing and is specially: BM-SC begins to ask the SGSN node listing with being disposed to send to GGSN by session; Or GGSN sends out the request of obtaining the SGSN node listing to BM-SC, and BM-SC sends to GGSN with the SGSN node listing.
In the such scheme, described SGSN node listing is by the oam platform configuration.Described SGSN node listing can be configured to sky.
The method that control MBMS provided by the present invention session begins, oam (OAM) by operator, configuration and the professional relevant SGSN node listing of current MBMS in BM-SC or GGSN, or, obtain and the relevant SGSN node listing of current MBMS business by SGSN and the corresponding relation of SGSN management area and the business domains information of current MBMS business that BM-SC preserves according to self.Afterwards, determine whether to allow certain SGSN registration or whether begin request according to the information in the SGSN node listing by GGSN again to certain SGSN transmission session according to the decision of the information in the SGSN node listing.Begin flow process according to the SGSN node listing by GGSN at MBMS register flow path or MBMS session, determine whether to allow SGSN to begin the MBMS session.So, GGSN only can begin to ask to issue the SGSN relevant with professional sending zone to session, or only allow the SGSN relevant to register with professional sending zone, thereby can not set up the user plane carrying of the SGSN from GGSN to other and current MBMS independent of service, can not send current MBMS session yet and begin to ask irrelevant SGSN node, RNC node, can not cause the signaling traffic load that there is no need, simultaneously, also avoid the waste of network carrying resource, reduce offered load and cost.
In addition, the present invention can realize based on different flow process, and multiple implementation is arranged, and has very strong flexibility and practicality.The present invention changes very little to existing handling process, implement simple, convenient.
Description of drawings
Fig. 1 is the transmission principle schematic diagram of multicast service;
Fig. 2 is for supporting the wireless network architecture schematic diagram of broadcasting/packet service;
Fig. 3 is a MBMS multicast/broadcast service log-on schematic flow sheet;
Fig. 4 begins schematic flow sheet for MBMS multicast/broadcast service conversation;
Fig. 5 is the handling process schematic diagram of first kind of implementation of the present invention;
Fig. 6 is the handling process schematic diagram of second kind of implementation of the present invention;
Fig. 7 is the handling process schematic diagram of the third implementation of the present invention.
Embodiment
Core concept of the present invention is: be each corresponding coverage of MBMS service definition, and be the SGSN node listing that each MBMS business configuration comprises professional all coverages of this MBMS, afterwards, GGSN obtains the SGSN node listing, and begin flow process according to the SGSN node listing at MBMS register flow path or MBMS session, determine whether to allow SGSN to begin current MBMS session.
Here, described SGSN node listing can be configured at the MBMS business by the OAM platform of operator, the professional corresponding SGSN node listing of each MBMS, write down the service region information of different MBMS business respectively, special, this SGSN node listing can be configured to sky, the corresponding MBMS business of expression does not have the restriction of coverage.This SGSN node listing can be disposed among the BM-SC, is handed down to GGSN by BM-SC; Also can directly be disposed among the GGSN; Can also obtain professional relevant SGSN node listing by BM-SC according to SGSN and the corresponding relation in this geographical position, SGSN region within the jurisdiction and the business domains information of current MBMS business of self preserving with current MBMS.
GGSN can be in the MBMS registration process, receive the register requirement of SGSN after, according to the sign of the SGSN in the SGSN node listing, the SGSN beyond the refusal SGSN node listing registers; Also can begin in the process in the MBMS session, identify according to the SGSN in the SGSN node listing, do not issue session and begin request to SGSN node listing SGSN in addition, thereby restriction produces impact with the MBMS business that certain network node has nothing to do to this network node, causes the waste of network carrying resource.
With reference to the drawings and specific embodiments every kind of implementation is described in detail respectively below.
First kind of implementation, OAM are determined the SGSN node listing of the professional total coverage of this MBMS of service according to the professional defined total coverage of each MBMS, and this tabulation comprises all signs of serving the SGSN of the professional total coverage of this MBMS.Such as, the MBMS business that the message of transmitting news is arranged, the professional corresponding total coverage of this MBMS is regional N, divide from the geographic area, zone N has covered regional N1, regional N2 and regional N3, three areas are respectively arranged with SGSN_N1, SGSN_N2 and SGSN_N3, and the professional corresponding SGSN node listing of the MBMS of the message of then transmitting news just is made up of SGSN_N1, SGSN_N2 and SGSN_N3.
In MBMS service log-on process, GGSN judges login request message from SGSN according to the SGSN node listing that disposed, if login request message from the SGSN in the tabulation, then GGSN admits the register requirement of this SGSN; Otherwise GGSN refuses the register requirement of this SGSN.This SGSN node listing can be disposed among the BM-SC, also can directly be disposed among the GGSN.
If the SGSN node listing is disposed among the BM-SC, after BM-SC receives the register requirement of GGSN at certain MBMS business, just the professional corresponding SGSN node listing of this MBMS is handed down to the GGSN that initiates register requirement; Afterwards, GGSN judges the register requirement from SGSN, and whether the SGSN that judges current initiation register requirement is contained in the SGSN node listing that BM-SC sends, if then continue normal MBMS register flow path; Otherwise GGSN refuses the register requirement that current SGSN initiates.Concrete handling process may further comprise the steps as shown in Figure 5:
Step 501~503: identical with step 301~303 in the prior art MBMS register flow path.
Step 504: in case receive the MBMS register requirement from a GGSN, BM-SC just is increased to the sign of this GGSN in " the downstream node listing " of self MBMS bearer context, and respond a MBMS registration reply message, the parameters such as SGSN node listing that wherein contain TMGI, bearing capacity requirement and disposed.If the MBMS bearer context of BM-SC is in " activation " state, BM-SC triggers and the session of this GGSN begins process.Wherein, the SGSN node listing is as a parameter, the SGSN that indicates pairing MBMS business can send on the aspect of total coverage.
Step 505: because GGSN receives a login request message from the described SGSN of step 502, so, whether the SGSN that initiates register requirement this moment in the GGSN determining step 502 is present in the SGSN node listing that BM-SC sends, if be present in the SGSN node listing, then GGSN is increased to the sign of SGSN in " the downstream node listing " of self MBMS bearer context; And return the MBMS registration reply message to SGSN, carry parameters such as TMGI and bearing capacity requirement in this response message; If the MBMS bearer context is in " activation " state, then the GGSN triggering begins process with the session of SGSN.If the SGSN that initiates register requirement is not in the SGSN node listing, then GGSN returns refusal MBMS login request message to SGSN, refuses the register requirement of this SGSN.
In this step, describedly judge that actual is exactly to search the sign that whether comprises the SGSN that initiates register requirement in the SGSN node listing that BM-SC sends.
Step 506: identical with the step 306 in the prior art MBMS register flow path.
If the SGSN node listing directly is disposed among the GGSN, then step 504 is also identical with step 304 in the prior art MBMS register flow path, and only step 505 unlike the prior art.
In this implementation, only existing MBMS registration process is changed a little, and the existing MBMS session process that begins is not changed.Like this, begin in second step of process in session, GGSN need send the downstream node listing that session begins to ask, that is: GGSN will send the target SGSN that session begins to ask, and has been the SGSN tabulation of operator's configuration and the common factor of the successful SGSN that applies for the registration of.
Embodiment one:
In the present embodiment, the coverage of supposing the A of operator is an area B, and area B comprise n sub regions B1, B2 ..., Bn, in the network planning, for each subregion Bi is provided with a SGSN.In the present embodiment, the A of operator provides a MBMS multicast service, is only to provide the transport information business in subregion B1 scope, and so, total the coverage of this MBMS multicast service is exactly subregion B1, corresponding SGSN is SGSN_B1.OAM disposes the SGSN node listing in the BM-SC that this MBMS multicast service is provided, owing to this MBMS multicast service only provides in subregion B1 scope, so the SGSN node listing that OAM disposed has only SGSN sign, i.e. a SGSN_B1.
In carrying out the MBMS registration process, in case receive the MBMS register requirement from a GGSN, BM-SC just is increased to the sign of this GGSN in the parameter " downstream node listing " in self MBMS bearer context, respond a MBMS registration reply message, wherein contain parameters such as TMGI, bearing capacity requirement, SGSN node listing.If the MBMS bearer context of BM-SC is in " activation " state, BM-SC triggers and the session of this GGSN begins process.Here, only comprise SGSN_B1 in the SGSN node listing, expression provides the MBMS multicast service of transport information can send to SGSN_B1.
After GGSN receives login request message from certain SGSN, GGSN judges earlier whether the SGSN node listing that obtains from BM-SC limits the SGSN that receives current MBMS multicast service, judge just whether the SGSN node listing is empty, if be not empty, illustrate and limit, whether the sign of then judging the SGSN that initiates register requirement sends in the SGSN node listing of MBMS multicast service in the permission that BM-SC provides, if initiate register requirement SGSN be identified at the SGSN node listing, then GGSN is increased to this SGSN sign in " downstream node listing " parameter of MBMS bearer context, and to SGSN responding MBMS registration reply message, wherein carry parameters such as TMGI and bearing capacity requirement, if the MBMS bearer context is in " activation " state, GGSN triggers and the session of SGSN begins process.If the sign of the SGSN of initiation register requirement is not at the SGSN node listing, then GGSN refuses the register requirement of this SGSN.Here, if BM-SC does not limit the SGSN that sends the MBMS multicast service, GGSN equally normally finishes the MBMS registration operation of SGSN.
Present embodiment comprises following several situation in actual applications:
1) if a user who belongs to subregion B2 activates the MBMS multicast service that transport information is provided in subregion B2 application, this user causes activation, and the SGSN_B2 that causes subregion B2 initiates register requirement to the GGSN that the transport information business is provided, owing in the SGSN node listing that GGSN preserves SGSN_B1 is only arranged, so GGSN finds the sign of SGSN_B2 and not in the SGSN node listing of self preserving, then refuses the register requirement of SGSN_B2.In this case, SGSN_B2 can give the corresponding reason for rejection of user terminal of initiating activation, and indication causes the activation failure of user terminal because having exceeded the coverage of current MBMS business.After the user receives refusal, can forward to and carry out the business reception under the point-to-point repair mode, perhaps after the initiation requesting users is gone to subregion B1, allow this MBMS multicast service of this user applies.
2) if a user who belongs to subregion B1 roams into subregion B3, so, the Serving RNC repositioning process can cause the SGSN B3 of subregion B3 to the GGSN initiation register requirement that the transport information business is provided between this user's inter-SGSN routing area update process or SGSN, owing in the SGSN node listing that GGSN preserves SGSN_B1 is only arranged, so GGSN finds the sign of SGSN_B3 and not in the SGSN node listing of self preserving, then refuses the register requirement of SGSN_B3.In this case, SGSN_B3 can give the corresponding reason for rejection of user terminal of initiating Serving RNC repositioning process between inter-SGSN routing area update process or SGSN, indication causes the user to activate the failure of this MBMS business because roaming has exceeded the service area of current MBMS business, the user can forward to and carry out the business reception under the point-to-point repair mode, perhaps after the initiation requesting users is gone to subregion B1, allow this MBMS multicast service of this user applies.
3) if a user who roams into subregion B1, perhaps local user who belongs to subregion B1, initiate register requirement by SGSN_B1 to the GGSN that the transport information business is provided, owing to preserve SGSN_B1 in the SGSN node listing of GGSN, so GGSN discovery SGSN_B1 is identified in the SGSN tabulation of self preserving, then GGSN admits the register requirement of SGSN_B1.In this case, service request from user can be satisfied.
Through the MBMS registration process, have only SGSN_B1 in the stream node listing of the downstream of GGSN, so, begin in the process in session, GGSN only can begin request to the session of transport information business and send to SGSN_B1.This session process that begins can not set up the user plane carrying of the SGSN from GGSN to other and this independent of service, can not send corresponding session yet and begin to ask irrelevant SGSN node, RNC node, thereby can not cause the signaling traffic load that there is no need.
Embodiment two:
In the present embodiment, the coverage of supposing the A of operator is an area B, and area B comprise n sub regions B1, B2 ..., Bn, in the network planning, for each subregion Bi is provided with a SGSN.In the present embodiment, the A of operator provides a MBMS multicast service, is only to provide the transport information business in subregion B1 scope, and so, total the coverage of this MBMS multicast service is exactly subregion B1, corresponding SGSN is SGSN B1.OAM disposes the SGSN node listing on the GGSN that this MBMS multicast service is provided, owing to this MBMS multicast service only provides in subregion B1 scope, so the SGSN node listing that OAM disposed has only SGSN sign, i.e. a SGSN_B1.
In carrying out the MBMS registration process, if GGSN receives a login request message from SGSN, GGSN judges at first whether the SGSN node listing that obtains by the OAM configuration limits the SGSN that receives this MBMS multicast service, judge just whether the SGSN node listing is empty, if be not empty, illustrate and limit, whether the sign of then judging the SGSN that initiates register requirement sends in the SGSN node listing of MBMS multicast service in the permission that BM-SC provides, if initiate register requirement SGSN be identified at the SGSN node listing, then GGSN is increased to this SGSN sign in " downstream node listing " parameter of MBMS bearer context, and to SGSN responding MBMS registration reply message, wherein carry parameters such as TMGI and bearing capacity requirement, if the MBMS bearer context is in " activation " state, GGSN triggers and the session of SGSN begins process.If the sign of the SGSN of initiation register requirement is not at the SGSN node listing, then GGSN refuses the register requirement of this SGSN.Here, if the OAM configuration does not limit the SGSN that sends the MBMS multicast service, GGSN equally normally finishes the MBMS registration operation of SGSN.
Present embodiment comprises multiple situation in actual applications equally, and concrete condition is described with embodiment one identical.
Based on first kind of implementation, also there is a kind of implementation in the present invention, is exactly: preserve the corresponding relation of SGSN and its geographical position, region within the jurisdiction in the network in BM-SC, the SGSN here is meant all SGSN that this BM-SC coverage is interior.Operator can provide total coverage of each MBMS business when providing MBMS professional; BM-SC obtains serving all SGSN of the professional total coverage of this MBMS just by total coverage and self stored relation are compared, and forms the SGSN node listing with resulting all SGSN signs.In the MBMS registration process, BM-SC is as long as judge whether to allow current SGSN to register according to the current SGSN node listing that obtains.
Embodiment three:
In the present embodiment, the coverage of supposing the A of operator is an area B, and area B comprise n sub regions B1, B2 ..., Bn, in the network planning, for each subregion Bi is provided with a SGSN.The corresponding relation in SGSN and geographical position, overlay area thereof in the BM-SC preservation network.In the present embodiment, the A of operator provides a MBMS multicast service, and this MBMS multicast service is only to provide the transport information business in subregion B1 scope.BM-SC is by the relatively geographical position of the SGSN institute overlay area of self storage and the geographical position of subregion B1, and the SGSN that obtains serving this transport information service area is SGSN_B1, and then the SGSN node listing just only comprises SGSN_B1.
Follow-up MBMS registration process and session begin process and the foregoing description one, embodiment two is identical.
Second kind of implementation, OAM are each corresponding coverage of MBMS service definition, and write down the identification list of the corresponding SGSN in each MBMS business service zone with the SGSN node listing.Begin in the flow process at each MBMS service conversation, GGSN is before SGSN transmission MBMS session beginning request, relatively by the SGSN sign in the SGSN node listing of sign of the SGSN in the downstream node listing of MBMS registration process acquisition and OAM configuration, get both common factors earlier; Afterwards, the SGSN transmission MBMS session of GGSN in occuring simultaneously begins request message.This SGSN node listing can be disposed among the BM-SC, also can directly be disposed among the GGSN.Here, if the SGSN node listing is empty, expression to service area without limits, then seek common ground is all SGSN in the downstream node listing of GGSN acquisition.
If the SGSN node listing is disposed among the GGSN, concrete handling process may further comprise the steps as shown in Figure 6:
Step 601: identical with the step 401 that prior art MBMS session begins in the flow process.
The SGSN node listing of the SGSN sign in step 602:GGSN relatively obtains by the MBMS registration process the downstream node listing of self and self configuration is got both common factors; The SGSN of GGSN in resulting common factor sends MBMS session beginning request message MBMS Session StartRequest.
After SGSN receives that the MBMS session begins request message, in the MBMS bearer context, preserve session attribute, and the status attribute that the MBMS bearer context is set is " activation ", return the MBMS session to GGSN and begin response message MBMS Session Start Response, the tunnel destination node sign (TEID) that is used for load plane is provided in this message, has been used for GGSN and sends the MBMS business datum.
Step 603~604: identical with step 403~404 that prior art MBMS session begins in the flow process.
If the SGSN node listing is disposed among the BM-SC, then BM-SC can be positioned over the MBMS session with the SGSN node listing and begins to send in the request message GGSN in step 601; Perhaps, GGSN also can obtain the SGSN node listing of OAM configuration from BM-SC in the MBMS register flow path.
In this implementation, existing MBMS registration process is not changed substantially, and only the existing MBMS session process that begins is changed a little.
Embodiment four:
In the present embodiment, the coverage of supposing the A of operator is an area B, and area B comprise n sub regions B1, B2 ..., Bn, in the network planning, for each subregion Bi is provided with a SGSN.In the present embodiment, the A of operator provides a MBMS multicast service, is only to provide the transport information business in subregion B1 scope, and so, total the coverage of this MBMS multicast service is exactly subregion B1, corresponding SGSN is SGSN_B1.OAM disposes the SGSN node listing on the GGSN that this MBMS multicast service is provided, owing to this MBMS multicast service only provides in subregion B1 scope, so the SGSN node listing that OAM disposed has only SGSN sign, i.e. a SGSN_B1.
In the MBMS registration process, the MBMS register requirement of sending no matter from the SGSN_Bi of which subregion Bi correspondence, GGSN is kept at its sign in the downstream stream node listing of MBMS bearer context.
Begin in the process at the MBMS service conversation, sign in SGSN sign in the downstream node listing that GGSN relatively obtains by the MBMS registration process and the SGSN node listing of OAM configuration, get both common factors, the SGSN in occuring simultaneously sends MBMS session beginning request message MBMSSession Start Request then.
After SGSN receives that the MBMS session begins request message, in the MBMS bearer context, preserve session attribute, and the status attribute that the MBMS bearer context is set is " activation ", return the MBMS session to GGSN and begin response message MBMS Session Start Response, the tunnel destination node sign (TEID) that is used for load plane is provided in this message, has been used for GGSN and sends the MBMS business datum.
Owing to have only SGSN_B1 in the common factor that GGSN obtains, so, begin in the process in session, GGSN only can begin request to the session of transport information business and send to SGSN_B1.This session process that begins can not set up the user plane carrying of the SGSN from GGSN to other and this independent of service, can not send session yet and begin to ask irrelevant SGSN node, RNC node, thereby can not cause the signaling traffic load that there is no need.
Such as: in the MBMS registration process, GGSN receives the MBMS register requirement from SGSN_B1, SGSN_B3 and SGSN_B8, be designated SGSN_B1 in the SGSN node listing of OAM configuration, then both common factors are SGSN_B1, and GGSN sends MBMS session beginning request message MBMS Session Start Request to SGSN_B1.
For another example: GGSN receives the MBMS register requirement from SGSN_B5 and SGSN_B13, be designated SGSN_B1 in the SGSN node listing of OAM configuration, then both common factors are empty, and GGSN does not send MBMS session beginning request message MBMS Session Start Request to any SGSN.
Embodiment five:
In the present embodiment, the coverage of supposing the A of operator is an area B, and area B comprise n sub regions B1, B2 ..., Bn, in the network planning, for each subregion Bi is provided with a SGSN.In the present embodiment, the A of operator provides a MBMS multicast service, is only to provide the transport information business in subregion B1 scope, and so, total the coverage of this MBMS multicast service is exactly subregion B1, corresponding SGSN is SGSN_B1.OAM disposes the SGSN node listing in the BM-SC that this MBMS multicast service is provided, owing to this MBMS multicast service only provides in subregion B1 scope, so the SGSN node listing that OAM disposed has only SGSN sign, i.e. a SGSN_B1.
The processing procedure of present embodiment and embodiment four are similar substantially, and just GGSN will obtain the SGSN node listing of OAM configuration from BM-SC before beginning request to SGSN transmission session.The SGSN node listing of described OAM configuration can be issued GGSN by BM-SC at BM-SC when GGSN transmission session begins to ask; Also can be in the MBMS register flow path, GGSN obtains from BM-SC; Can also send the opportune moment of session before beginning to ask to SGSN at GGSN, obtain to the BM-SC request by GGSN.
Based on second kind of implementation, also further there is a kind of implementation in the present invention, is exactly: preserve the corresponding relation of all SGSN and its geographical position, region within the jurisdiction in the network in BM-SC, the SGSN here is meant all SGSN that this BM-SC service range is interior.So, before transmission MBMS session began request message, BM-SC compared MBMS business domains and SGSN institute jurisdiction reason position earlier, obtains the geographical SGSN node listing that occurs simultaneously; Afterwards, begin in the process in execution MBMS session, BM-SC will send to GGSN by the SGSN node listing that relatively obtains, GGSN relatively by the sign of the SGSN in the SGSN node listing that the SGSN in the downstream node listing of MBMS registration process acquisition identifies and BM-SC is given, obtains both common factors again; Then, GGSN only the SGSN in occuring simultaneously send the MBMS session and begin request message.
In this scheme, though total coverage of certain MBMS business covers a plurality of geographic areas, but at each MBMS session, the professional final geographic area that sends of this MBMS may be different, and may be in the geographic area that covered of this MBMS business one or several.Such as, the MBMS business that the message of transmitting news is arranged, the professional corresponding total coverage of this MBMS is regional N, divide from the geographic area, regional N has covered regional N1, regional N2 and regional N3, and three areas are respectively arranged with SGSN_N1, SGSN_N2 and SGSN_N3, if only requiring current MBMS session sends at regional N2, then at current MBMS session, the final area that sends has only regional N2, and does not comprise regional N1 and regional N3.Accordingly, at current MBMS session, the professional corresponding SGSN node listing of the MBMS of the message of transmitting news includes only SGSN_N2.Certainly, in order to reduce number of comparisons, content supplier can be in advance offers BM-SC with total coverage of certain MBMS business, and like this, the SGSN node listing just comprises all SGSN that serve total coverage.Such as, total coverage of the MBMS business of the message of transmitting news is regional N, the SGSN node listing just comprises SGSN_N1, SGSN_N2, SGSN_N3.
Usually, in BM-SC, all preserve total coverage of each MBMS business, if the MBMS business domains that current content supplier issues is total coverage of this MBMS business, then directly the SGSN of total service region information and BM-SC self storage and the geographical position of compass of competency thereof are compared, obtain the SGSN node listing.If the MBMS business domains that current content supplier issues is the coverage at certain session, then BM-SC just compares the MBMS business domains of receiving with the SGSN that self stores and the geographical position of compass of competency thereof, obtains the SGSN node listing.Such as: total coverage of certain MBMS business is regional N, divide from the geographic area, zone N has covered regional N1, regional N2 and regional N3, and the MBMS business domains of this session is regional N3, so, BM-SC just compares the SGSN of regional N3 and self storage and the geographical position of compass of competency thereof, and obtaining the SGSN node listing is SGSN_N3.
Concrete processing procedure may further comprise the steps as shown in Figure 7:
The GGSN that step 701:BM-SC preserves in the MBMS bearer context " downstream node listing " of self correspondence sends session and begins request message Session Start Request, the indication transmission that is about to begin, and the status attribute that the MBMS bearer context is set is " activation ".During beginning to ask, this session writes session attributes such as having QoS, MBMS business domains, the length of estimating this session and SGSN node listing.Wherein, the SGSN node listing is exactly that BM-SC compares MBMS business domains and SGSN institute jurisdiction reason position, the tabulation that geographical SGSN sign of occuring simultaneously is arranged of obtaining.
After GGSN receives that session begins request message, the session attribute that provides in this message is provided in the MBMS bearer context, the status attribute that the MBMS bearer context is set is " activation ", and returns session to BM-SC and begin response message Session Start Response.
Certainly, GGSN also can send out the request of obtaining the SGSN node listing to BM-SC separately, and BM-SC sends to GGSN with the SGSN node listing that obtains after receiving request.
Step 702:GGSN is relatively by the sign of the SGSN in the SGSN node listing that the SGSN in the downstream node listing of MBMS registration process acquisition identifies and BM-SC is given, obtain both common factors, the SGSN in occuring simultaneously sends MBMS session beginning request message MBMS Session Start Request.
After SGSN receives that the MBMS session begins request message, in the MBMS bearer context, preserve session attribute, and the status attribute that the MBMS bearer context is set is " activation ", return the MBMS session to GGSN and begin response message MBMS Session Start Response, the tunnel destination node sign (TEID) that is used for load plane is provided in this message, has been used for GGSN and sends the MBMS business datum.
Step 703~704: identical with step 403~404 that prior art MBMS session begins in the flow process.
Embodiment six:
In the present embodiment, the coverage of supposing the A of operator is an area B, and area B comprise n sub regions B1, B2 ..., Bn, in the network planning, for each subregion Bi is provided with a SGSN, simultaneously, each subregion might further comprise littler area, such as: subregion B1 may comprise regional B11, B12 ..., B1n.In the present embodiment, the A of operator provides a MBMS multicast service, is only to provide the transport information business in subregion B1 scope, and so, total the coverage of this MBMS multicast service is exactly subregion B1, corresponding SGSN is SGSN_B1.In addition, in BM-SC, preserve in the network of the A of operator, the corresponding relation in all SGSN and its geographical position, compass of competency, in this example, the corresponding relation among the BM-SC between only in store SGSN_B1 and the subregion B1.
In the MBMS registration process, the MBMS register requirement of sending from the SGSN_Bi of which subregion Bi no matter, GGSN is kept at its sign in the downstream stream node listing of MBMS bearer context.
Before transmission MBMS multicast conversation began request message, BM-SC compared MBMS business domains and SGSN institute jurisdiction reason position, obtains the geographical SGSN node listing that occurs simultaneously.Here, the MBMS business domains is that BM-SC obtains from the content supplier that current MBMS business is provided.
Give an example, certain MBMS session for described transport information business, if the indication of the MBMS business domains of this MBMS session sends to regional B11, BM-SC judges that earlier regional B11 belongs to the compass of competency of which subregion Bi correspondence, promptly ask the common factor of regional B11 and subregion Bi, the SGSN node that obtains administering the B11 zone is exactly SGSN_B1, and so, SGSN_B1 is exactly the SGSN node listing.The GGSN that BM-SC preserves in " downstream node listing " parameter in its corresponding MBMS bearer context sends session and begins request message Session Start Request, the indication transmission that is about to begin, and the status attribute that the MBMS bearer context is set is " activation ".Session attributes such as QoS, MBMS business domains, the length of estimating this session, SGSN node listing are provided in this request.Wherein, the SGSN node listing has only the sign SGSN_B1 of a SGSN.
After GGSN receives that session begins request message, the session attribute that provides in this message is provided in the MBMS bearer context, the status attribute that the MBMS bearer context is set is " activation ", and returns session to BM-SC and begin response message Session Start Response.
Sign in the given SGSN node listing of SGSN sign in the downstream node listing that GGSN relatively obtains by the MBMS registration process and BM-SC, get both common factors, the SGSN in occuring simultaneously sends MBMS session beginning request message MBMS Session Start Request then.Here, that the common factor that is obtained is exactly SGSN_B1.
After SGSN receives that the MBMS session begins request message, in the MBMS bearer context, preserve session attribute, and the status attribute that the MBMS bearer context is set is " activation ", return the MBMS session to GGSN and begin response message MBMS Session Start Response, the tunnel destination node sign (TEID) that is used for load plane is provided in this message, has been used for GGSN and sends the MBMS business datum.
Owing to have only SGSN_B1 in the common factor that GGSN obtains, so, begin in the process in session, GGSN only can begin request to the session of transport information business and send to SGSN_B1.This session process that begins can not set up the user plane carrying of the SGSN from GGSN to other and this independent of service, can not send session yet and begin to ask irrelevant SGSN node, RNC node, thereby can not cause the signaling traffic load that there is no need.
Need to prove that GGSN is relevant with business, but also may certain relation be arranged with the geographic area, is exactly on the geography specifically, and GGSN may need to carry out professional load sharing, perhaps carries out the needs of local service.
In this case, the method for the APN of BM-SC by limiting every kind of IP multicast service limits the influence of corresponding service to GGSN.Particularly be exactly: APN has determined to provide certain professional GGSN, and BM-SC makes APN relevant with the geographic area, and just having limited provides this professional GGSN.
For example: regional A provides professional B, and there is GGSN_1 this area, so, BM-SC is when providing the APN relevant with professional B, the APN that points to GGSN_1 only is provided, thereby makes the SGSN that thinks access service B all need GGSN_1 to come, so just do not influenced GGSN that other is regional.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.

Claims (15)

1, a kind ofly controls the method that multimedia broadcast/multicast service conversation begins, it is characterized in that, this method comprises: GGSN is retrieved as the SGSN node listing that comprises professional all coverages of this MBMS of current MBMS business configuration, then according to the SGSN identification information in the SGSN node listing that is obtained, judge whether current SGSN is contained in the described SGSN node listing, if comprise, the session that then allows this SGSN to carry out specific MBMS session begins flow process, otherwise, refuse the session that this SGSN carries out specific MBMS session and begin flow process.
2, method according to claim 1 is characterized in that, in the MBMS register flow path, described judgement specifically comprises:
After GGSN receives the MBMS register requirement at current MBMS business that SGSN sends, according to the SGSN node listing that is obtained, whether the SGSN that judges current initiation MBMS register requirement is included in the described SGSN node listing, if, then accept the MBMS register requirement of this SGSN, and the session that the SGSN that allows to succeed in registration carries out specific MBMS session begins flow process; Otherwise, refuse the MBMS register requirement of this SGSN.
3, method according to claim 2 is characterized in that, described SGSN node listing is stored among the BM-SC, and then described GGSN obtains the SGSN node listing and is specially:
After BM-SC receives the MBMS register requirement at current MBMS business that GGSN sends, return the MBMS registration response that comprises the professional pairing SGSN node listing of current MBMS to GGSN; GGSN obtains described SGSN node listing from the MBMS registration response of being received.
4, method according to claim 3 is characterized in that, described SGSN node listing is stored among the BM-SC and is specially: directly the SGSN node listing is disposed among the BM-SC.
5, method according to claim 3, it is characterized in that, described SGSN node listing is stored among the BM-SC and is specially: the corresponding relation of preserving SGSN and geographical position, region within the jurisdiction thereof in BM-SC, BM-SC obtains to have the geographical SGSN node listing that occurs simultaneously according to the professional total coverage of the MBMS that obtains from content supplier and the SGSN that self preserves and the corresponding relation in geographical position, region within the jurisdiction thereof.
6, method according to claim 2 is characterized in that, described SGSN node listing is disposed among the GGSN, and then GGSN is from self obtaining the SGSN node listing that is disposed.
7, method according to claim 1 is characterized in that, begins in the flow process in the MBMS session, and described judgement specifically comprises:
After a11.GGSN receives that the session at specific MBMS session that BM-SC sends begins request, SGSN in the downstream node listing that self obtains by the MBMS registration process and SGSN in the SGSN node listing that is obtained are sought common ground;
The session that SGSN in the common factor that b12.GGSN is obtained in step a11 sends at specific MBMS session begins request, receives that this session of SGSN continuation execution that session begins to ask begins flow process.
8, method according to claim 7 is characterized in that, described SGSN node listing is disposed among the BM-SC, and then GGSN obtains the SGSN node listing that is disposed from BM-SC.
9, method according to claim 8 is characterized in that, described GGSN obtains the SGSN node listing from BM-SC and is: BM-SC begins to ask the SGSN node listing with being disposed to send to GGSN by session; Or GGSN obtains the SGSN node listing that is disposed at BM-SC in the MBMS registration process.
10, method according to claim 7 is characterized in that, described SGSN node listing is disposed among the GGSN, and then GGSN is from self obtaining the SGSN node listing that is disposed.
11, method according to claim 1 is characterized in that, preserves the corresponding relation in SGSN and its geographical position, region within the jurisdiction in BM-SC; This method specifically comprises:
A21.BM-SC is according to the business domains of the current MBMS business of obtaining from content supplier and SGSN and geographical position, the region within the jurisdiction corresponding relation of self preserving thereof, acquisition has the geographical SGSN node listing that occurs simultaneously, and resulting SGSN node listing is sent to GGSN;
After a22.GGSN received that the session at specific MBMS session that BM-SC sends begins request, the SGSN that the SGSN in the downstream node listing that self obtains by the MBMS registration process and BM-SC are sent sought common ground;
The session that SGSN in the common factor that a23.GGSN is obtained in step a22 sends at specific MBMS session begins request, receives that this session of SGSN continuation execution that session begins to ask begins flow process.
12, method according to claim 11, it is characterized in that, the business domains of the current MBMS business of obtaining from content supplier described in the step a21 is: total coverage of current MBMS business, or be the coverage of current MBMS business at this session.
13, method according to claim 11 is characterized in that, the described BM-SC of step a21 sends to GGSN with the SGSN node listing and is specially: BM-SC begins to ask the SGSN node listing with being disposed to send to GGSN by session; Or GGSN sends out the request of obtaining the SGSN node listing to BM-SC, and BM-SC sends to GGSN with the SGSN node listing.
According to claim 1,2,3,4,6,7,8,9 or 10 described methods, it is characterized in that 14, described SGSN node listing is by the oam platform configuration.
According to claim 1,2,3,4,6,7,8,9 or 10 described methods, it is characterized in that 15, described SGSN node listing is configured to sky.
CNB2004100805365A 2004-09-28 2004-09-28 Method for controlling multimedia broadcast/multicast service conversation start Expired - Fee Related CN100366030C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB2004100805365A CN100366030C (en) 2004-09-28 2004-09-28 Method for controlling multimedia broadcast/multicast service conversation start

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2004100805365A CN100366030C (en) 2004-09-28 2004-09-28 Method for controlling multimedia broadcast/multicast service conversation start

Publications (2)

Publication Number Publication Date
CN1756422A true CN1756422A (en) 2006-04-05
CN100366030C CN100366030C (en) 2008-01-30

Family

ID=36689279

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2004100805365A Expired - Fee Related CN100366030C (en) 2004-09-28 2004-09-28 Method for controlling multimedia broadcast/multicast service conversation start

Country Status (1)

Country Link
CN (1) CN100366030C (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100440791C (en) * 2006-06-19 2008-12-03 华为技术有限公司 Method for realizing multi-medium multi-packet broadcasting service
CN102057699A (en) * 2008-06-10 2011-05-11 爱立信电话股份有限公司 SAE application for MBMS
WO2012010049A1 (en) * 2010-07-21 2012-01-26 中兴通讯股份有限公司 Mbms service delivery method and system
CN101052166B (en) * 2007-05-23 2013-02-27 中兴通讯股份有限公司 Region control method for multimedia broadcast and multicast business

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002094562A (en) * 2000-09-20 2002-03-29 Nec Corp Ip packet/multicast method
AU2002255193A1 (en) * 2002-04-17 2003-10-27 Nokia Corporation Method and system for setting up a multicast or broadcast transmission
JP3926288B2 (en) * 2002-05-03 2007-06-06 三星電子株式会社 Multicast multimedia broadcast service apparatus and method in mobile communication system
KR100827136B1 (en) * 2002-05-17 2008-05-02 삼성전자주식회사 Method for signaling connection assignment in a mobile communication system
US20040227618A1 (en) * 2002-11-06 2004-11-18 Samsung Electronics Co., Ltd. Paging method in a mobile communication system providing a multimedia broadcast/multicast service
CN102905226B (en) * 2003-02-12 2015-07-29 三星电子株式会社 The equipment of multimedia broadcast/multi broadcast business is provided in mobile communication system
CN1523798A (en) * 2003-02-17 2004-08-25 ��������ͨ�ż����о����޹�˾ Method for effective updating of MBMS business service parameter in GGSN, SGSN and RNC

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100440791C (en) * 2006-06-19 2008-12-03 华为技术有限公司 Method for realizing multi-medium multi-packet broadcasting service
CN101052166B (en) * 2007-05-23 2013-02-27 中兴通讯股份有限公司 Region control method for multimedia broadcast and multicast business
CN102057699A (en) * 2008-06-10 2011-05-11 爱立信电话股份有限公司 SAE application for MBMS
WO2012010049A1 (en) * 2010-07-21 2012-01-26 中兴通讯股份有限公司 Mbms service delivery method and system
CN102340735A (en) * 2010-07-21 2012-02-01 中兴通讯股份有限公司 MBMS (multimedia broadcast multicast service) sending method and system
CN102340735B (en) * 2010-07-21 2016-03-02 中兴通讯股份有限公司 A kind of sending method of MBMS and system

Also Published As

Publication number Publication date
CN100366030C (en) 2008-01-30

Similar Documents

Publication Publication Date Title
CN1303799C (en) Method for controlling multimedia broadcast/multicast service conversation
CN1268089C (en) Method for multi-media broadcasting/grouped player service data transmission
CN1684414A (en) Conversation start method for multimedia broadcast/group broadcast service
CN1302686C (en) Cell information change informing method in multimedia broadcast/multicast service
CN1149867C (en) Location dependent WWW service in digital cellular communication networks
CN1266898C (en) Method for realizing multimedia broadcast/multi cast service business activation
TWI305471B (en) Enhanced assisted cell change
CN1918812A (en) Radio access node registration for multimedia broadcast multicast service
US20070014291A1 (en) Method for multimedia broadcast/multicast service registration
CN1833380A (en) Cell reselecting method for receiving packet data
CN101047950A (en) Method for allocating default load in 3GPP evolution network
CN1913713A (en) Public data networking access method and system
CN1863370A (en) Method for implementing selective in shared network transfer
CN1192576C (en) Multicast business realizing method in mobile network
CN1543152A (en) A multi-protocol data gateway and method for implementing communication thereof
CN100346596C (en) Method for activating service of multimedia broadcast/group broadcast service
CN1691676A (en) Method for determining number of receiving users in multimedia broadcast/multicast service
CN1905569A (en) Method for changing user IP address of mobile communication network
CN101047976A (en) Authorization failure process method and system in multimedia broadcast/multicast service
CN1758644A (en) Method for controlling session start of multi-medium broadcast/group broadcast service
CN1180639C (en) Radio channel configuration selecting method in multicast service
CN1756422A (en) Method for controlling multimedia broadcast/multicast service conversation start
CN1802010A (en) Method for realizing multicast broadcast service registration
CN1794859A (en) Method of realizing active in multimedia gooup broadcasting service
CN1677971A (en) Method for realizing activation of multi-media broadcasting/multicast service

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20080130

Termination date: 20200928

CF01 Termination of patent right due to non-payment of annual fee