CN101052150B - Control method for multimedia multicast/broadcast business and network node - Google Patents
Control method for multimedia multicast/broadcast business and network node Download PDFInfo
- Publication number
- CN101052150B CN101052150B CN200610072645A CN200610072645A CN101052150B CN 101052150 B CN101052150 B CN 101052150B CN 200610072645 A CN200610072645 A CN 200610072645A CN 200610072645 A CN200610072645 A CN 200610072645A CN 101052150 B CN101052150 B CN 101052150B
- Authority
- CN
- China
- Prior art keywords
- business
- node
- multicast
- network node
- bearer context
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
In invention is used for making MBMS control to inform a failure when having a failure in system so as to save communication bandwidth. It comprise: the middle network node sends a service-starting request to its upper network node, it decides if the service-starting confirmation transmitted from the lower network node is received before the confirmation time is over; if yes, enabling the local broadcast/multicast to bear the context; otherwise, sending the request for stopping the service-starting; if the service-starting requests are simultaneously transmitted to multi network nodes, then after not receiving any service confirmations before being overtime, the request for stopping the transmission of service to upper network node will be transmitted to the upper network node.
Description
Technical field
The present invention relates to mobile communication technology, control method for multimedia multicast/broadcast business and network node in the particularly a kind of WCDMA system.
Background technology
MBMS (Multimedia Broadcast and Multicast Service, multi-medium multi-packet broadcasting and broadcasting service) be a unidirectional multimedia service of a bit arriving multiple spot, it allows data to send to a plurality of recipients from a source entity, and such service will extensive use in wireless network.MBMS utilizes high efficiency wireless forwarding method that identical data are downloaded to a plurality of mobile subscribers, and main contents are the multi-medium data of Media Stream (Streaming) or background Background class.
In 3GPP, defined two kinds of operational modes, be respectively: broadcast mode and multicast (multicast) pattern.Broadcast mode is that a kind of multi-medium data unidirectional from a certain resource entity all Client-initiateds in the broadcast service zone, that put multiple spot transmits.In the multicast pattern, network selectively sends to multi-case data multicast service and receives the sub-district that the user exists.
With the example that is embodied as in WCDMA (Wide-band Code Division Multiple Access, WCDMA access system) system, briefly introduce the flow process of MBMS business below, may further comprise the steps:
1, professional declaration (Service announcement)
BMSC (Broadcast Multicast Service Centre, broadcast/multicast service center) before issuing Streaming Media by the broadcast/multi broadcast mode, by Cell Broadcast CB, way of short messages notice MS (MobileStation), MS begins to monitor these channels such as professional MCCH, MTCH of carrying earlier.
2, session begins (Session Start)
Session begins flow process and is used for the data that BMSC notifies GGSN, SGSN and Access Network to begin to send broadcast/multi broadcast business, needs each network node to set up the service bearer of transmission.
Session begins flow process as shown in Figure 1, comprises the steps:
S101-S101 ', BMSC send Session Start Request (session begins request message) and set up local MBMS bearer context to GGSN, and GGSN returns Session Start Response message to BMSC; Comprise following cell in the Session Start Request message:
TMGI (Temporary Mobile Group Identity), temporary mobile group identity;
QoS (Quality of Service, service quality), the service quality of this session;
MBMS service Area, the service area information of MBMS business;
Session Identifier, the session sign;
Estimated Session Duration estimates the session duration;
Broadcast/Multicast shows that this business is multicast service or broadcasting service;
List of Downstream Nodes for GGSN, the downstream node SGSN tabulation of GGSN etc.
GGSN sets up local MBMS bearer context according to these information.
S102-S102 ', after GGSN receives Session Start Request message, if can set up corresponding M BMS carrying, then return Session Start Response message to BMSC, wherein carry success response information, then according to List of Downstream Nodes for GGSN, send MBMS Session Start Request message and set up the MBMS bearer context to each corresponding SGSN, equally, comprise following cell: TMGI in the MBMS Session Start Request message, QoS, MBMS ServiceArea, Session Identifier, Estimated Session Duration, Broadcast/Multicast......;
If GGSN sets up corresponding M BMS carrying, the Session Start Response message of then carrying failure information to the BMSC news conference inadequately.
When each was received MBMS Session Start Request message and can set up corresponding M BMS carrying, SGSN returned the MBMS Session Start Response message of carrying success response information to GGSN, and created the MBMS bearer context;
Then, set up GTP (GPRS TunnelingProtocol GPRS Tunnel Protocol) tunnel between the SGSN of each success response and the GGSN.
S103-S103 ', same sets up GTP tunnel between the radio network controller (RNC) of SGSN and success response;
Here, the SGSN downstream may connect two or more RNC, and SGSN is respectively with each RNC execution in step S103-S103 ' and set up GTP tunnel.
S104, RNC are that MS distributes wireless access network interface-free resources (RAN (Radio Access Network) Resource Setup).
3, MBMS notice (MBMS Notification)
RNC will send MBMS Notification message at the Uu mouth, at be that all of its control belong to the MS in the sub-district of MBMS Service Area.
4, transfer of data
Be sent in the process of MS in the MBMS data, GGSN finishes data forwarding, and the packet that BMSC is sent is forwarded to the SGSN in downstream by the GTP tunnel of correspondence, and SGSN sends to RNC through the GTP tunnel of correspondence again, and data are transferred to MS through eating dishes without rice or wine.
5, session stops
Session stop procedures is the inverse process that session begins process, and RNC discharges interface-free resources, and RNC, SGSN, GGSN and BMSC remove GTP tunnel step by step.
According to different networking modes, the downstream node of SGSN may be RNC, BSC (Base StationController, base station controller) or MSC (Mobile Service Switch Center, mobile switching centre), wherein, MSC also may connect SGSN by one or more relay nodes.
Regulation according to existing protocol, in broadcast/multi broadcast business, after current node receives that session that the upstream node is sent begins message, create local carrying, the state of carrying is set to activate (Active) state, and send session and begin request message to the downstream node, show that present broadcasting service will begin to have sent data, need the downstream network node to set up the service bearer of transmission.After the downstream network node is created bearer context, reply session and begin success response to current node.
GGSN after receiving that session that BMSC sends begins message, create the MBMS bearer context after, contextual attribute is set to the Active state.Send session to BMSC then and begin success response, show that GGSN is ready.Send session then and begin message, but do not receive that in setting-up time the session of SGSN begins success response to each SGSN.Be the MBMS bearer context on the GGSN, do not create the tunnel with arbitrary SGSN.But BMSC is also unclear, so the back will send data to GGSN as usual.Can't transmit after GGSN receives, can only abandon.The Internet resources between GGSN and the BMSC have not only been wasted in this process, the disposal ability of also having wasted GGSN and BMSC.In addition, the ticket that BMSC produces can show that this GGSN has accepted this service, obviously also is irrational.
By that analogy, when similar above-mentioned abnormal conditions took place, current node may can not receive the response message of all downstream nodes, such as: network congestion, whole unavailable, network configuration mistakes of downstreams node etc.Current device is after creating local bearer context, and just the attribute of local bearer context is set to the Active state, indicates that this context has been in state of activation, and in fact this moment, this bearer context can't be finished the function of transmitting data.But the upstream node is not also known this situation, still can send data to current node, and current node can only discard after receiving data, causes the waste of communication bandwidth resource and device processes ability, also can cause the mistake in the node charging of upstream.The session of this type of MBMS broadcast mode is begun abnormal conditions in the process, and the 3GPP agreement is not carried out standard.
Summary of the invention
The invention provides a kind of control method for multimedia multicast/broadcast business and network node, to solve in the existing multimedia multicast/broadcast business control owing to can't when abnormal conditions occurring, in time carrying out the problem that signalling trouble causes wasting communication bandwidth and processor.
For realizing the technology of the present invention design, the invention provides following technical scheme:
A kind of control method for multimedia multicast/broadcast business, when multicast/broadcast business transmitted by three network nodes at least, in the process of setting up the multimedia multicast/broadcast business carrying, control method of the present invention comprised the steps:
A, go-between node are received when the multicast/broadcast business of upper level network node transmission begins request and can set up the multimedia multicast/broadcast business carrying, upwards the primary network station node returns professional beginning success response, sets up local multicast/broadcast business bearer context and begins request at least one next stage network node transmission business;
B, go-between node judge setting the response time whether receive that the business that at least one next stage network node returns begins success response before overtime, if then activate local multicast/broadcast business bearer context; Otherwise upwards primary network station node transmission business stops request.
Wherein, when multicast/broadcast business that the upper level network node sends to the go-between node began to comprise the tabulation of next stage network node in the request, each next stage network node transmission business that the go-between node comprises in this next stage network node tabulation began request; And the go-between node activates the local service bearer context when receiving before overtime from the professional beginning success response of first of next stage network node in the described setting response time; If the go-between node does not receive that the business that part next stage network node returns begins success response in the described setting response time before overtime, then in the local service bearer context, mark this part next stage network node; If the go-between node does not receive that the business that any one next stage network node returns begins success response in the described setting response time before overtime, then upwards primary network station node transmission business stops request and removes local multicast/broadcast business bearer context.
If the upper level network node is received the business from the go-between node and is stopped request, the go-between node that mark sets out and gives this business to stop to ask in the local service bearer context, and when all go-between nodes all are labeled, stop request and remove local multicast/broadcast business bearer context to multicast/broadcast business service centre transmission business.
Generally speaking, the upper level network node directly connects multicast/broadcast business service centre, and multicast/broadcast business service centre begins back upper level network node transmission business in business and begins request and set up local multicast/broadcast business bearer context; The upper level network node returns professional beginning success response to multicast/broadcast business service centre, sets up local multicast/broadcast business bearer context and begins request to go-between node transmission business; The upper level network node judges in the described setting response time whether receive that the business that the go-between node returns begins success response before overtime, if then activate local multicast/broadcast business bearer context; Otherwise stop request to multicast/broadcast business service centre transmission business.
The business that the primary network station node sends if multicast/broadcast business service centre makes progress begins to comprise in the request tabulation of go-between node, and then each go-between node transmission business of comprising in described go-between node tabulation of upper level network node begins request; And activate the local service bearer context when receiving before overtime in the described setting response time from the professional beginning success response of first of go-between node; If do not receive that the business that part go-between node returns begins success response in the described setting response time before overtime, then in the local service bearer context, mark this part go-between node; If do not receive that the business that any one go-between node returns begins success response before overtime, then stop request and remove local multicast/broadcast business bearer context to multicast/broadcast business service centre transmission business in the described setting response time.
When if multicast/broadcast business service centre stops to ask in the business from the upper level network node received, the upper level network node that mark sets out and gives this business to stop to ask in the local service bearer context, and when all upper level network nodes all are labeled, stop this business and remove local multicast/broadcast business bearer context.
If multicast/broadcast business service centre simultaneously begins request at least two upper level network node transmission business, activate the local service bearer context when then multicast/broadcast business service centre receives before overtime from the professional beginning success response of first of upper level network node in the described setting response time; If do not receive that the business that part upper level network node returns begins success response in the described setting response time before overtime, then in the local service bearer context, mark this part upper level network node; If do not receive that the business that any one upper level network node returns begins success response, then removes local multicast/broadcast business bearer context before overtime in the described setting response time.
The upper level network node that multicast/broadcast business service centre stops to ask to the business that sends returns business and stops response.
After comprising the steps: also between described steps A and the B that the next stage network node receives that business from the go-between node begins request, return professional beginning success response and set up and activate local multicast/broadcast business bearer context to the go-between node.
The present invention also provides a kind of network node of multimedia multicast/broadcast business, comprises the information transmit-receive unit, also comprises:
First module, the link information Transmit-Receive Unit, be used to receive when business that the upper level network node sends begins request and can set up the multicast/broadcast business carrying, return professional beginning success response at least one upper level network node, begin request and set up local multicast/broadcast business bearer context at least one next stage network node transmission business;
Unit second, the link information Transmit-Receive Unit is used to judge setting the response time whether receive that the business that at least one next stage network node returns begins success response before overtime, if then activate local multicast/broadcast business bearer context; Otherwise upwards primary network station node transmission business stops request;
Memory cell, connect described first module and Unit second respectively, be used to preserve local service bearer context and corresponding attribute information thereof, described first module downward primary network station node transmission business begins after the request local multicast/broadcast business bearer context temporarily to be set to established state, described Unit second is received when business that at least one next stage network node returns begins success response, is activated local multicast/broadcast business bearer context.
Beneficial effect of the present invention is as follows:
Technical scheme of the present invention provides the network failure informing mechanism for multicast/broadcast business, each network node can find in time whether downstream network or network node abnormal conditions occur, thereby in time in local bearer context, carry out mark, no longer send the data to the downstream network node that is labeled, to reduce the waste of communication bandwidth and processor; If the whole faults of the downstream network of multicast/broadcast business service centre or network node, can in time stop this business to reduce the waste of communication bandwidth and processor, and high charging precision. all compare in the valuable network in bandwidth and processor, technical solution of the present invention provides the bearing link when abnormal conditions occurring to remove mechanism, help reducing the communication bandwidth under the abnormal conditions and the waste of processor, and improved the accuracy that the upstream node charges, perfect networking plan.
Description of drawings
Fig. 1 is the professional beginning of existing MBMS schematic flow sheet;
Fig. 2 is for realizing a kind of network node structural representation of the method for the invention.
Embodiment
The present invention is directed to the defective of prior art, being given in session begins in the process, if network congestion, all during abnormal conditions such as the unavailable or network configuration mistake of downstreams node, the mechanism of downstream node notice upstream node makes the upstream node can in time stop this session service.
Be example still, comprise following several scene with the WCDMA system:
One, for MBSC
MBSC sets up local MBMS Bear Context and sends session to GGSN (may comprise two or more) and begins request (Session Start Request) message after business begins, the Session Start Response message of the success response information of carrying that judges whether then to receive that at least one GGSN returns, if then continue this business, otherwise stop this professional and timely MBMS of dismounting BearContext;
If MBSC receives the STR Session Termination Request message that downstream GGSN sends, this GGSN of mark in local MBMS Bear Context then, when all GGSN all are labeled, illustrate that downstream node or network are all unavailable, then stop this professional and timely MBMS of dismounting BearContext.
Two, for GGSN
After GGSN receives the Session Start Request that BMSC sends, upstream node BMSC returns Session Start Response message, create local MBMS service bearer context MBMS BearContext, temporarily the attribute of MBMS Bear Context is set to set up (Standby) state of finishing, and each SGSN in List of Downstream Nodes for GGSN tabulation sends MBMS Session Start Request request message then.After receiving first MBMS Session Start Response message from the success response information of carrying of downstream SGSN, the attribute of MBMS Bear Context is set to the Active state again.If do not receive one before GGSN is overtime from SGSN and carry the MBMS Session Start Response message of success response information, then send STRSession Termination Request message and finish this session, and in time remove the MBMS bearer context to reduce the waste of communication bandwidth and processor with notice BMSC to BMSC;
If GGSN receives the transmission MBMS Session Stop Request message of downstream SGSN, this SGSN of mark in local MBMS Bear Context then, when all SGSN all are labeled, illustrate that downstream node or network are all unavailable, then send STR Session Termination Request message and in time remove MBMS Bear Context to BMSC.
Three, for SGSN
SGSN returns MBMSSession Start Response message to GGSN after receiving the Session Start Request message that GGSN sends, send Session StartRequest request message and create local MBMS Bear Context to RNC (may comprise two or more), temporarily the attribute of MBMS BearContext is set to the Standby state.Then, when receive carry the MBMS Session Start Response message of success response information from first of RNC after, the attribute of MBMS Bear Context is set to the Active state again.If SGSN does not receive that before setting-up time is overtime any one is from RNC and carry the MBMS Session Start Response message of success response information, send MBMS Session Stop Request message to GGSN and finish this session, and in time remove local MBMS bearer context to reduce the waste of communication bandwidth and processor with request GGSN;
If SGSN receives the transmission MBMS Session Stop Request message of downstream RNC, this RNC of mark in local MBMS Bear Context then, when all RNC all are labeled, illustrate that downstream node or network are all unavailable, then send MBMS Session Stop Request message and in time remove MBMS Bear Context to GGSN.
Like this, send Session Start Request message to beginning to send in the time period of data from BMSC, report mechanism by fault of the present invention, each network node can find in time whether downstream network or network node abnormal conditions occur, thereby in time in local bearer context, carry out mark, no longer send the data to the downstream network node that is labeled, to reduce the waste of communication bandwidth and processor; If the whole faults of the downstream network of BMSC or network node can in time stop the waste of this business with minimizing communication bandwidth and processor, and improve the charging precision.
Detailed session begins flow process and comprises the steps:
S201, after session begins, BMSC creates local MBMS Bear Context and the Session of node GGSN transmission downstream Start Request message, comprise following cell: TMGI, QoS, MBMS service Area, Session Identifier, Estimated SessionDuration, Broadcast/Multicast and List of Downstream Nodes for GGSN in this Session Start Request message, the downstream node SGSN tabulation of GGSN etc.
After S202, GGSN receive that upstream node BMSC sends Session Start Request message, if could set up corresponding M BMS service bearer upstream node BMSC return the Session Start Response message of carrying success response information, create local MBMS service bearer context MBMS BearContext;
If GGSN can not set up corresponding M BMS service bearer, then upstream node BMSC returns the Session Start Response message of carrying failure response information.
Here, GGSN can also temporarily be set to the Standby state with the attribute of MBMS Bear Context, is used for the state at this locality sign MBMS Bear Context.
S203, GGSN send MBMS Session Start Request message according to from the tabulation of the downstream SGSN in the Session Start Request message of upstream node BMS to each downstream node SGSN; Equally, comprise following cell: TMGI, QoS, MBMS Service Area, Session Identifier, Estimated Session Duration, Broadcast/Multicast...... in the MBMS Session Start Request message;
If downstream node SGSN can set up corresponding M BMS service bearer when receiving the MBMS Session StartRequest message that upstream node GGSN sends, then upstream GGSN returns the MBMS Session Start Response message of carrying success response information, and creates local MBMS BearContext;
If downstream node SGSN can not set up corresponding M BMS service bearer, then upstream node GGSN returns the Session Start Response message of carrying failure response information.
S204, GGSN judge whether to receive that before setting-up time is overtime at least one that return from downstream SGSN carry the MBMS Session Start Response message of success response information, if execution in step S205; Otherwise execution in step S207;
After S205, GGSN received first MBMS Session Start Response message from the success response information of carrying of downstream node SGSN, the attribute of MBMS Bear Context was set to the Active state;
After receiving that all SGSN beam back the MBMS Session StartResponse message (or overtime) of the success response information of carrying of coming, finish the residue work that MBMS Bear Context creates (such as the list item of creating NP etc.); And be marked at the SGSN that setting-up time does not return the MBMS Session Start Response message of carrying success response information before overtime, when transmitting this business datum, do not send data to the SGSN that is labeled;
The SGSN that S206, GGSN and each are returned the MBMS Session StartResponse message of carrying success response information sets up GTP tunnel, and this GTP tunnel is used to carry this business datum;
If abnormal conditions, GGSN does not receive that before setting-up time is overtime any one SGSN beams back the Session Start Response message of the success response information of carrying of coming, then execution in step S207 to S208:
S207, GGSN are before setting-up time is overtime, if do not receive the MBMS Session Start Response message of the success response information of carrying that any one downstream SGSN returns, then send STR Session Termination Request message and finish this session, and in time delete local MBMS Bear Context to reduce the waste of communication bandwidth and processor with notice BMSC to BMSC.
Like this, when appearance was unusual, GGSN can in time notify BMSC to finish this session, after BMSC receives that session stops request message, in bearer context this GGSN is made marks, and no longer sends data to this GGSN.In the descending node tabulation (List of Downstream Nodes) of the ticket that generates, do not comprise this GGSN.
Here, BMSC may send Session StartRequest message to two or more GGSN simultaneously, before setting-up time is overtime, do not receive the Session Start Response message of the success response information of carrying that any one GGSN returns, then stop this business and remove local MBMS BearContext; When receiving the STR Session Termination Request message that one of them GGSN returns, mark the GGSN that sends this STR Session Termination Request message at local MBMS Bear Context, no longer send data to this GGSN, after all GGSN are labeled, then stop this business and remove local MBMS Bear Context.
After S208, BMSC receive STR Session Termination Request message, the session of node GGSN transmission downstream stops response (STR Session Termination Answer) message, but GGSN needn't carry out any processing after receiving STR Session Termination Answer message.
The SGSN that can set up MBMS carrying also needs to continue to carry out following step after receiving MBMS SessionStart Request message from upstream node GGSN:
S209, SGSN according to the local MBMS Bear of the content creating in MBMS Session Start Request message Context after, the attribute of MBMS Bear Context is set to the Standby state, and node RNC/BSC continues to send MBMS Session Start Request message downstream;
If downstream node RNC can set up corresponding M BMS service bearer when receiving the MBMS Session StartRequest message that upstream node SGSN sends, then upstream SGSN returns the MBMS Session Start Response message of carrying success response information, and creates local MBMS BearContext;
If downstream node RNC can not set up corresponding M BMS service bearer, then upstream node SGSN returns the Session Start Response message of carrying failure response information.
S211, SGSN judge the MBMS Session Start Response message whether receive the success response information of carrying that at least one RNC returns before setting-up time is overtime, if execution in step S212 then; Otherwise execution in step S213;
The attribute of S212, SGSN MBMS Bear Context is set to the Active state;
Then, SGSN and return and set up this professional GTP tunnel of carrying between the downstream node RNC of the MBMS Session Start Response message of carrying success response information.So far, the carrying of this service needed is set up and is finished, and the data that BMSC sends are transferred to MS through GGSN, SGSN, RNC successively.
S213, SGSN do not receive the MBMS Session Start Response message of the success response information of carrying that any one downstream node RNC returns before setting-up time is overtime, then the MBMS of node GGSN transmission upstream Session Stop Response message stops this business with notice, and in time deletes local MBMS Bear Context to reduce the waste of communication bandwidth and processor;
After upstream node GGSN receives MBMS Session Stop Response message, in local MBMSBear Context, mark this SGSN, if all SGSN among the local MBMS Bear Context all are labeled, then send STR Session Termination Request message and finish this session, and in time delete local MBMS Bear Context to reduce the waste of communication bandwidth and processor with notice BMSC to BMSC.
Equally, when BMSC receives the STR Session Termination Request message that GGSN returns, mark the GGSN that sends this STR Session Termination Request message at local MBMS Bear Context, no longer send data to this GGSN, after all GGSN are labeled, then stop this business and remove local MBMS Bear Context.
So far, when the network between RNC and the SGSN node occurs unusual or RNC node itself appearance when unusual, SGSN can in time notify BMSC to stop this business by GGSN.
In the WCDMA network, bandwidth and processor all are the comparison preciousnesses, and the bearing link of technical scheme of the present invention under the abnormal conditions mechanism of removing helps reducing the communication bandwidth under the abnormal conditions and the waste of processor, and improve the accuracy that the upstream node charges, improve networking plan.
The foregoing description describes with the example that is embodied as in the WCDMA system, according to different networking modes, the downstream node of SGSN may be RNC, BSC (Base Station Controller, base station controller) or MSC (Mobile Service Switch Center, mobile switching centre), wherein, MSC also may connect SGSN by one or more relay nodes, in the network node of per three connections, can carry out fault of the present invention and report mechanism.
As shown in Figure 2, be used for the WCDMA system, realize the network node 200 of multimedia multicast/broadcast business of the present invention, comprise information transmit-receive unit 201, also comprise:
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (14)
1. by three network nodes transmission, in the process of setting up the multimedia multicast/broadcast business carrying, described control method comprises at least for control method for multimedia multicast/broadcast business, described multimedia multicast/broadcast business:
A, go-between node are received when the multicast/broadcast business of upper level network node transmission begins request and can set up the multimedia multicast/broadcast business carrying, upwards the primary network station node returns professional beginning success response, sets up local multicast/broadcast business bearer context and begins request at least one next stage network node transmission business;
B, go-between node judge setting the response time whether receive that the business that at least one next stage network node returns begins success response before overtime, if then activate local multicast/broadcast business bearer context; Otherwise upwards primary network station node transmission business stops request.
2. control method as claimed in claim 1 is characterized in that:
In the described steps A, the multicast/broadcast business that the upper level network node sends to the go-between node begins to comprise in the request tabulation of next stage network node, and each next stage network node transmission business that the go-between node comprises in this next stage network node tabulation begins request;
Among the described step B, the go-between node activates the local service bearer context when receiving before overtime from the professional beginning success response of first of next stage network node in the described setting response time;
If the go-between node is not received the business that part next stage network node returns and begun success response, then in the local service bearer context, mark this part next stage network node;
If the go-between node does not receive that the business that any one next stage network node returns begins success response in the described setting response time before overtime, then upwards primary network station node transmission business stops request and removes local multicast/broadcast business bearer context.
3. control method as claimed in claim 2 is characterized in that, also comprises before the described steps A:
A01, the multicast/broadcast business service centre primary network station node transmission business that makes progress begins request and sets up local multicast/broadcast business bearer context;
A02, upper level network node are received when the business from multicast/broadcast business service centre begins request and can set up the multimedia multicast/broadcast business carrying, return professional beginning success response to multicast/broadcast business service centre, set up local multicast/broadcast business bearer context and begin request to go-between node transmission business;
A03, upper level network node judge in the described setting response time whether receive that the business that the go-between node returns begins success response before overtime, if then activate local multicast/broadcast business bearer context; Otherwise stop request to multicast/broadcast business service centre transmission business.
4. control method as claimed in claim 3 is characterized in that,
In the described steps A 01, the multicast/broadcast business service centre business that the primary network station node sends that makes progress begins to comprise in the request tabulation of go-between node;
In the described steps A 02, each go-between node transmission business that the upper level network node comprises in described go-between node tabulation begins request;
In the described steps A 03, the upper level network node activates the local service bearer context when receiving before overtime from the professional beginning success response of first of go-between node in the described setting response time;
If the upper level network node does not receive that the business that part go-between node returns begins success response in the described setting response time before overtime, then in the local service bearer context, mark this part go-between node;
If the upper level network node does not receive that the business that any one go-between node returns begins success response in the described setting response time before overtime, then stop request and remove local multicast/broadcast business bearer context to multicast/broadcast business service centre transmission business.
5. control method as claimed in claim 4 is characterized in that, among the described method step A01, multicast/broadcast business service centre begins request at least two upper level network node transmission business simultaneously, and:
Multicast/broadcast business service centre activates the local service bearer context when receiving before overtime from the professional beginning success response of first of upper level network node in the described setting response time;
If multicast/broadcast business service centre does not receive that the business that part upper level network node returns begins success response in the described setting response time before overtime, then in the local service bearer context, mark this part upper level network node;
If multicast/broadcast business service centre does not receive that the business that any one upper level network node returns begins success response, then removes local multicast/broadcast business bearer context in the described setting response time before overtime.
6. control method as claimed in claim 5 is characterized in that, described method also comprises:
When the upper level network node stops to ask in the business from the go-between node received, the go-between node that mark sets out and gives this business to stop to ask in the local service bearer context, and when all go-between nodes all are labeled, stop request and remove local multicast/broadcast business bearer context to multicast/broadcast business service centre transmission business;
When multicast/broadcast business service centre stops to ask in the business from the upper level network node received, the upper level network node that mark sets out and gives this business to stop to ask in the local service bearer context, and when all upper level network nodes all are labeled, stop this business and remove local multicast/broadcast business bearer context.
7. control method as claimed in claim 6 is characterized in that, described method also comprises: the upper level network node that multicast/broadcast business service centre stops to ask to the business that sends returns business and stops response.
8. as claim 5,6 or 7 described control methods, it is characterized in that, comprise the steps: also between described steps A and the B that the next stage network node receives when business from the go-between node begins request and can set up the multimedia multicast/broadcast business carrying, return professional beginning success response to the go-between node, set up and activate local multicast/broadcast business bearer context.
9. control method as claimed in claim 8 is characterized in that, described method also comprises:
The upper level network node that multicast/broadcast business service centre is not labeled in the local service bearer context sends this business datum;
The upper level network is transmitted to this business datum the go-between node that is not labeled in the local service bearer context;
Go-between is transmitted to this business datum the next stage network node that is not labeled in the local service bearer context;
The next stage network node is transmitted to terminal with this business datum.
10. control method as claimed in claim 1 is characterized in that, also comprises in the described steps A: the go-between node temporarily is set to established state with the local service bearer context.
11. control method as claimed in claim 3 is characterized in that,
Also comprise in the described steps A 01: multicast/broadcast business service centre temporarily is set to established state with the local service bearer context;
Also comprise in the described steps A 02: the upper level network node temporarily is set to established state with the local service bearer context.
12. control method as claimed in claim 1 is characterized in that, described upper level network node is that gateway GPRS is supported node GGSN; Described go-between node is that service GPRS is supported node SGSN; Described next stage network node is radio network controller (RNC), base station controller BSC or moving exchanging center MSC.
13. the network node of a multimedia multicast/broadcast business comprises the information transmit-receive unit, it is characterized in that, described network node also comprises:
First module, the link information Transmit-Receive Unit, be used to receive when business that the upper level network node sends begins request and can set up the multimedia multicast/broadcast business carrying, upwards the primary network station node returns professional beginning success response, begins request and sets up local multicast/broadcast business bearer context at least one next stage network node transmission business;
Unit second, the link information Transmit-Receive Unit is used to judge setting the response time whether receive that the business that at least one next stage network node returns begins success response before overtime, if then activate local multicast/broadcast business bearer context; Otherwise upwards primary network station node transmission business stops request.
14. network node as claimed in claim 13 is characterized in that, described network node also comprises:
Memory cell, connect described first module and Unit second respectively, be used to preserve local service bearer context and corresponding attribute information thereof, first module downward primary network station node transmission business begins after the request local multicast/broadcast business bearer context temporarily to be set to established state, and Unit second is received and activated local multicast/broadcast business bearer context when business that the next stage network node returns begins success response.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610072645A CN101052150B (en) | 2006-04-07 | 2006-04-07 | Control method for multimedia multicast/broadcast business and network node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610072645A CN101052150B (en) | 2006-04-07 | 2006-04-07 | Control method for multimedia multicast/broadcast business and network node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101052150A CN101052150A (en) | 2007-10-10 |
| CN101052150B true CN101052150B (en) | 2010-05-12 |
Family
ID=38783311
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200610072645A Expired - Fee Related CN101052150B (en) | 2006-04-07 | 2006-04-07 | Control method for multimedia multicast/broadcast business and network node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101052150B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111866755B (en) * | 2020-07-17 | 2023-03-28 | 腾讯科技（深圳）有限公司 | Communication method, device, medium and electronic equipment for multicast broadcast service |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1163758B1 (en) * | 1999-03-19 | 2003-09-10 | Nokia Corporation | Method and network element for forwarding multicast messages |
| CN1642132A (en) * | 2004-03-29 | 2005-07-20 | 华为技术有限公司 | Method for realizing multimedia broadcast/multi cast service business activation |
| CN1642130A (en) * | 2004-01-08 | 2005-07-20 | 华为技术有限公司 | Multimedia multicast business registration method |
-
2006
- 2006-04-07 CN CN200610072645A patent/CN101052150B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1163758B1 (en) * | 1999-03-19 | 2003-09-10 | Nokia Corporation | Method and network element for forwarding multicast messages |
| CN1642130A (en) * | 2004-01-08 | 2005-07-20 | 华为技术有限公司 | Multimedia multicast business registration method |
| CN1642132A (en) * | 2004-03-29 | 2005-07-20 | 华为技术有限公司 | Method for realizing multimedia broadcast/multi cast service business activation |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101052150A (en) | 2007-10-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2387165B1 (en) | Service transmission method for multimedia broadcast/multicast service | |
| EP1668798B1 (en) | Method for distinguishing mbms service request from other service requests | |
| CN104937963B (en) | Method and apparatus for group communication with robust mobility | |
| KR100943901B1 (en) | Method of Sharing Radio Protocol Entity for Broadcasting and Multicast | |
| EP1796405B1 (en) | Method and apparatus of service identifying and routing in multimedia broadcast/multicast service system | |
| EP1802049B1 (en) | A method and system for controlling multimedia broadcast/multicast service session | |
| US7546108B2 (en) | Method for supporting backward compatibility of MBMS | |
| CN100438654C (en) | Press-and-through system and method for realizing same | |
| US20060107287A1 (en) | Multimedia broadcast/multicast service announcement and notification | |
| CN101009908A (en) | The method for supporting the MBMS service transmission in the LTE system | |
| WO2004071117A1 (en) | Provision of a multimedia broadcast/multicast service (mbms) for a user equipment moving along cells in a cellular mobile communication system | |
| CN101267594A (en) | Method and related apparatus of handling point-to-multipoint MBMS | |
| CN100502358C (en) | Method for establishing GTP tunnel in multimedia broadcast/multicast service | |
| WO2005018116A1 (en) | Method for establishing common transport channel for mbms | |
| CN101212394B (en) | MBMS service activation method and system, multicast data transmission method and system | |
| CN101094439B (en) | Method and device of assigning resources dynamically for broadcast service in wireless communication system | |
| WO2004073272A1 (en) | Method for effectively updating mbms service parameters in ggsn, sgsn and rnc | |
| KR100956817B1 (en) | Method of processing packet data and an apparatus thereof | |
| CN100563384C (en) | A kind of service release method of multimedia broadcast/multi broadcast business | |
| CN1968451B (en) | Method and system for determining to use multicast/broadcast service time | |
| CN102395110A (en) | Method for supporting MBMS service transmission in LTE system | |
| EP2061266B1 (en) | Method, apparatus and system for sending MBMS service in IP load-carrying web | |
| CN101141787B (en) | Method of implementing multicast channel establishment, prelogin, release in broadband access system | |
| CN100444650C (en) | Method for introducing MBMS service identification | |
| CN101052150B (en) | Control method for multimedia multicast/broadcast business and network node |
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 | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100512 Termination date: 20130407 |