CN101047528A - Processing method and system for information in multi-media broadcast/multicast service - Google Patents
Processing method and system for information in multi-media broadcast/multicast service Download PDFInfo
- Publication number
- CN101047528A CN101047528A CNA2006100347830A CN200610034783A CN101047528A CN 101047528 A CN101047528 A CN 101047528A CN A2006100347830 A CNA2006100347830 A CN A2006100347830A CN 200610034783 A CN200610034783 A CN 200610034783A CN 101047528 A CN101047528 A CN 101047528A
- Authority
- CN
- China
- Prior art keywords
- node
- downstream
- upstream
- intermediate node
- 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.)
- Pending
Links
Images
Abstract
A method for processing information in multimedia broadcast / multicast service includes setting load-carrying judgment unit in intermediate node in order to judge whether MBMS data can be received by downstream node or not, returning message of load being not be able to be used back to upstream node by intermediate node when data can be received by downstream node and carrying out further treatment by upstream node according notification message of downstream node.
Description
Technical field
(Multimedia Broadcast MultipleService, MBMS) realization technology are carried treatment technology in particularly a kind of MBMS business to the present invention relates to multimedia broadcast/group broadcast service.
Background technology
Along with the development of 3G (Third Generation) Moblie technology, 3G (Third Generation) Moblie can provide than the more service of high data rate of second generation mobile communication, thereby supports the multiple business form.Download, browse at a high speed services such as Internet network such as visual telephone, picture.Wherein have a class business features to be: this business can be simultaneously give subscribed in the wireless network should business the user send.Such as weather forecast, news film, the sports tournament collection of choice specimens or the like.The characteristics of utilizing these business to send simultaneously, 3-G (Generation Three mobile communication system) has been introduced the notion of multicast/broadcast from Rel-6, can more effectively utilize preferential air interface resource, and higher power system capacity is provided.
In the broadcasting/packet service, for an intermediate node, no matter its downstream comprises the node what expectations receive data, and its upstream node always sends a piece of data to this intermediate node; After this intermediate node is received data, the number of nodes that receives data according to its downstream expectation duplicates this data, and distribute this data to the node that each expectation of its downstream receives these data, like this, each bar branch of multicast/broadcast business data transmission tree all has only a piece of data to transmit, take a transfer resource, the transfer of data of root node and its downstream node also is like this.The distinctive points of multicast service and broadcasting service only is: multicast service only sends corresponding information to the user who has subscribed to some information, and the broadcasting service then user of all in wireless network sends information.As seen from the above description, provide identical information to a large number of users simultaneously, can greatly save Internet resources by multicast/broadcast is professional.
In order to effectively utilize the mobile communications network resource, 3G (Third Generation) Moblie global standards tissue (3GPP) has proposed the MBMS of mobile communications network, thereby in mobile communications network, provide a data source to send the point-to-multipoint service of data to a plurality of users, the realization Internet resources are shared, improve utilization rate of network resource, the interface resource of especially eating dishes without rice or wine.The MBMS that 3GPP proposes can not only realize the classes of messages multicast and the broadcasting of plain text low rate, and can also realize the multicast and the broadcasting of high-speed multimedia business, and this has complied with the trend of following mobile data development undoubtedly.
Fig. 1 is for supporting the wireless network architecture schematic diagram of broadcasting/packet service, as shown in Figure 1, among the existing 3GPP, support that the wireless network entity of broadcasting/packet service is broadcasting/packet service server (BM-SC), BM-SC is by Gmb interface or Gi interface and critical point GPRS Support Node (GGSN, Gateway GPRSSupport Node) link to each other, a BM-SC can link to each other with a plurality of GGSN; GGSN links to each other by Gn/Gp interface and Serving GPRS Support Node (SGSN, Serving GPRS Support Node), and a GGSN can link to each other with a plurality of SGSN; SGSN can link to each other with universal mobile telecommunications system (UMTS) land radio access web (UTRAN) 104 by the Iu interface, UTRAN 104 links to each other with UE 106 by the Uu interface then, SGSN also can strengthen wireless access network (GERAN) by Iu/Gb interface and global system for mobile communications and link to each other, and GERAN links to each other with UE by Um Interface then.Wherein, GGSN and SGSN belong to the node in the core net in the wireless network (CN).
The network configuration that provides from Fig. 1 as can be seen, in order to support the MBMS business, in 3-G (Generation Three mobile communication system), increased mobile network functional entity--broadcast multicast service center, be BM-SC, described BM-SC is content provider's a inlet, be used for authorizing and initiating the MBMS business, and plan transmits the MBMS content to schedule at mobile network.In addition, on functional entitys such as UE, UTRAN, GERAN, SGSN, GGSN, increased the function relevant with MBMS.
MBMS comprises multicast pattern and broadcast mode, and wherein multicast pattern needs user's corresponding multicast group of contracting, and carries out activation of service, and produces corresponding charge information.Because it is different that multicast pattern and broadcast mode exist on business demand, cause also difference of operation flow separately, as shown in Figures 2 and 3, Fig. 2 is the operation flow schematic diagram of MSMS multicast pattern, Fig. 3 is the operation flow schematic diagram of MSMS broadcast mode.
As shown in Figure 2, the processing procedure that relates to of MBMS multicast service comprises: signatory (Subscription), service declaration (Service announcement), user add that (Joining), session begin (Session Start), MBMS notice (MBMS notification), data transmit (Data transfer), conversation end (SessionStop) and user and withdraw from (Leaving).Wherein, signatory process is used for setting up the relation between user and the service supplier, allows the user subscribe to required MBMS service in advance; Service declaration process is used for promptly notifying user MBMS the relevant information of business by the current service that can provide of BM-SC declaration; User's adition process is a MBMS activation of service process, UE is in adition process, informing network self is ready to become the member of current multicast group, receives the data of corresponding MBMS business, and this adition process can be created the MBMS UE context of record UE information in the UE of network and adding multicast group; Session begins in the process, and BM-SC is ready to transfer of data, and informing network is set up the bearing resource of corresponding core net and Access Network; The MBMS notification procedure is used for being about to begin by RNC notice UE MBMS multicast conversation; In data transfer procedure, BM-SC transfers data to UE by the bearing resource that session begins to set up in the process, the MBMS business has two kinds of patterns when transmitting between UTRAN and UE: point-to-multipoint (PTM) pattern and point-to-point (PTP) pattern, the PTM pattern sends identical data by MBMS point-to-multipoint service channel (MTCH), all add multicast service or can receive the interested UE of broadcasting service, ptp mode sends data by the DTCH logic channel, has only a corresponding UE to receive; The conversation end process is used for the bearing resource that the session process that begins is set up is discharged; The user withdraws from process makes the subscriber in the group leave multicast group, i.e. user's receiving multicast data no longer, and this process can be with corresponding MBMS UE context deletion.
As shown in Figure 3, processing procedure that the MBMS broadcasting service relates to and MBMS multicast service are similar, just before session begins, do not need to carry out signatory process and user's adition process, and, after conversation end, do not need to carry out the user and withdraw from process.
Fig. 4 is for setting up the schematic flow sheet of interactive function in the existing MBMS business.As shown in Figure 4, mainly may further comprise the steps
Step 401:BM-SC session and sending function (Session and Transmission Function) send session and begin request (Session Start Request) message, indicate transfer of data on the horizon, and provide session attribute (TMGI, QoS, the MBMS service area, session identification, the session persistence of estimation, the broadcast/group broadcast pattern is tabulated (only being used for broadcast mode) for the downstream node that GGSN uses) and the 2G/3G indication.This message is sent by BM-SC agency and transfer function (Proxy and Transport Function), sends to all GGSN in " the list of downstream nodes " parameter in the MBMS bearer context.Status attribute in BM-SC agency and the transfer function MBMS bearer context is set to " Active ".For the broadcasting MBMS bearer service, GGSN creates a MBMS bearer context.Downstream node tabulation in GGSN store session attribute and the MBMS bearer context, status attribute in the MBMS bearer context is set to " Active ", and return session to BM-SC agency and transfer function and begin response (Session StartResponse) message, BM-SC acts on behalf of and transfer function will be given to BM-SC session and sending function before it.BM-SC agency and transfer function also can begin session request (Session Start Request) message and be used for billing purpose for BM-SC member's function (Membership Function) transmission portion.
Step 402:GGSN sends session and begins request (Session Start Request) message, and session attribute (TMGI, QoS, MBMS service area, session identification, the session persistence of estimation, broadcast/group broadcast pattern) and 2G/3G are provided indication.This message sends to all SGSN in " list ofdownstream nodes " parameter in the MBMS bearer context among the GGSN.For the broadcasting MBMS bearer service, SGSN creates a MBMS bearer context.2G/3G indication in SGSN store session attribute and the MBMS bearer context, status attribute in the MBMS bearer context is set to " Active ", and return session to GGSN and begin response (Session Start Response) message, be provided for the TEID of load plane, GGSN uses this TEID to come the transmitting MBMS data.For the MBMS bearer service, if SGSN receives that a plurality of MBMS sessions begin request (Session Start Request) message, this SGSN only needs to set up a load plane with one of them GGSN.
Step 403:SGSN sends session and begins request (Session Start Request) message, and session attribute (TMGI, QoS, MBMS service area, session identification, the session persistence of estimation, broadcast/group broadcast pattern) is provided.This message sends to all BSC and/or the RNC that is connected to this SGSN.SGSN uses 2G/3G to indicate to determine that it is only give all BSC that the MBMS session begins request (Session Start Request) message, still only gives all RNC, or gives all RNC and BSC simultaneously.For multicast MBMS bearer service, SGSN may be included in the number that is in the UE of PMM-IDLE state in the route district RA.For the broadcasting MBMS bearer service, BSC/RNC creates the MBMS business contexts.The store session attribute in the MBMS business contexts at BSC under the Iu pattern and RNC, status attribute in the MBMS business contexts is set to " Active ", and return session to SGSN and begin response (Session Start Response) message, BSC under RNC and the Iu pattern can begin to comprise the TEID that is used for load plane in response (Session Start Response) message that SGSN uses this TEID to come the transmitting MBMS data in session.BSC under the Gb pattern if not being the service of MBMS service area, does not then just need the store session attribute.If BSC/RNC receives that a plurality of MBMS sessions begin request (Session Start Request) message, only need to set up a load plane with one of them SGSN.
Step 404:BSC/RNC sets up essential Radio Resource and is used for to interested UE MBMS transmission data.
As can be seen, in existing broadcasting service, when BM-SC after GGSN sends Session StartRequest, GGSN returns Session Start Response to BM-SC, but according to existing procedure, have such problem: GGSN is after BM-SC returns response, BM-SC just thinks that GGSN can receive data, but, after GGSN SGSN downstream sends Session Start Request,, or provided replying of refusal if all SGSN in downstream do not respond to GGSN, BM-SC is ignorant, like this, BM-SC can send data to GGSN, the data and GGSN has no idea to send downwards, GGSN can only abandon data, and being actually has like this wasted the processing of GGSN resource.
SGSN is not to the GGSN response and returned the refusal response, and possible reason comprises: SGSN is restarted or configuration error occurred, does not respond to GGSN; SGSN does not support the MBMS ability; And other a lot of possible reasons, as " Request Accepted ", " Context not found ", " No resourcesavailable ", " No memory is available ", " System failure ", " Mandatory IE incorrect ", " Mandatory IE missing ", " Optional IE incorrect ", " Invalid message format " or the like.
Same, according to existing procedure, SGSN is after GGSN returns response, GGSN just thinks that SGSN can receive data, still, and after SGSN BSC/RNC downstream sends Session Start Request, if all BSC/RNC in downstream do not respond to SGSN, or having provided replying of refusal, GGSN is ignorant, like this, GGSN can send data to SGSN, the data and SGSN has no idea to send downwards, SGSN can only abandon data, has wasted the processing resource of SGSN equally.
Summary of the invention
In view of this, the technical problem to be solved in the present invention is to provide information processing method and system in a kind of realization MBMS business, when it can't receive data in the downstream, notice its carrying of upstream was unavailable, thereby the data of avoiding issuing because of BM-SC can't continue to transmit the wasting of resources that causes.
The another technical problem that the present invention will solve is to provide a kind of intermediate node that is used to realize MBMS operation system kind, unavailable to solve in the prior art because of the intermediate node carrying, and the MBMS business datum that issues can't be received, thereby the problem of the wasting of resources that causes.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention provides a kind of information processing method of realizing multi-medium broadcast/group broadcast MBMS business, it mainly may further comprise the steps:
When intermediate node is received from the service request of upstream node, judge whether its downstream node can receive data, if judged result is a downstream node can not receive data the time, the intermediate node upstream nodes sends the unavailable message of carrying.
Described intermediate node is received when the session from upstream node begins to ask, and sends session to downstream node and begins request message, starts timer simultaneously.
Before the timer expiry, intermediate node does not receive from downstream node response or does not receive that any downstream node response shows and can receive data that then upstream nodes sends the unavailable message of carrying.
If carrying in the unavailable message only is the notice upstream node, current this node is unavailable, after then upstream node is received the unavailable message of carrying of intermediate node transmission, this intermediate node is set to receive the state of data, during this time MBMS session, no longer send any data to this intermediate node, do not reattempt yet and send session to this intermediate node and begin request, perhaps upstream node directly with this intermediate node from its downstream node listing deletion.
Carry in the unavailable message also portability cause description, downstream node can not receive the reason of data.These reasons comprise: do not support the MBMS ability, do not have enough available resources or information word to make mistakes.
If the reason of the unavailable message of described carrying is permanent reason, then upstream node do not reattempt to this intermediate node send that session begins to ask or directly with the downstream node listing of this intermediate node from upstream node in delete; If the reason of the unavailable message of described carrying is interim reason, upstream node adopts regularly or the mode of not timing repeatedly begins request message to this intermediate node transmission session.
Described upstream node does not reattempt and sends session to this intermediate node to begin request be to stop the realization of request/response message by session, describedly directly the process of deleting in the downstream node listing of this intermediate node from upstream node is realized by the MBMS logout flow path.
Described intermediate node comprises Gateway GPRS Support Node GGSN and/or Serving GPRS Support Node SGSN, and when described intermediate node was GGSN, its corresponding upstream node was broadcast/multicast service center BM-SC, and its corresponding downstream node is SGSN; When described intermediate node was SGSN, its corresponding upstream node was GGSN, and its corresponding downstream node is RNC and/or BSC.
The present invention also provides a kind of communication system that realizes multi-medium broadcast/group broadcast MBMS business, comprise root node and at least one intermediate node, wherein have at least an intermediate node to be provided with the carrying judging unit, in order to when the request of upstream node issuing service, judge whether its downstream node can receive data, and can not receive data in the downstream time, upstream nodes sends the unavailable message of carrying.
Described intermediate node sends session to downstream node and begins request message when receiving that the session that sends the upstream begins to ask, and simultaneously described carrying judging unit starts timer event.
Before the timer expiry, intermediate node does not receive from downstream node response or does not receive that any downstream node response shows and can receive data that then upstream nodes sends the unavailable message of carrying.
After upstream node is received the unavailable message of carrying of intermediate node transmission, this intermediate node is set to receive the state of data, during this time MBMS session, no longer send any data to this intermediate node, do not reattempt yet and send session to this intermediate node and begin request, perhaps upstream node directly with this intermediate node from its downstream node listing deletion.
Described intermediate node comprises: Gateway GPRS Support Node GGSN and/or Serving GPRS Support Node SGSN, and when described intermediate node was GGSN, its corresponding upstream node was broadcast/multicast service center BM-SC, its corresponding downstream node is SGSN; When described intermediate node was SGSN, its corresponding upstream node was GGSN, and its corresponding downstream node is RNC and/or BSC.
The present invention also provides a kind of node, be used for realizing the communication system of MBMS business, this node comes bearer service as intermediate node, and this node is provided with the carrying judging unit, in order to when receiving the service request that the upstream sends, judge whether its downstream can receive data.
Described carrying judging unit is realized by timer event, this node is when transmitting service request downstream, start timer, before timer expiry, do not receive the response in any downstream or show that without any response the downstream can receive data and judge that then the downstream cannot receive data.
Described node also comprises the beared information transmitting element, when cannot receive data in carrying judgment unit judges downstream, upstream sends the unavailable message of carrying.
When described carrying judgment unit judges downstream cannot receive data, this node upstream sent the unavailable message of carrying.
Described node is Gateway GPRS Support Node GGSN or Serving GPRS Support Node SGSN.
Compared to prior art, the present invention is provided with the carrying judging unit by the intermediate node in the communication system that realizes the MBMS business, in order to judge whether its downstream node can receive the MBMS data, and return corresponding message informing upstream node, upstream node is done further processing according to the notification message of downstream node, thereby avoided not knowing because of upstream node whether downstream node can receive data, and constantly issued data that downstream node but can't receive and the wasting of resources that causes.
Description of drawings
Fig. 1 is for supporting the wireless network architecture schematic diagram of broadcasting/packet service;
Fig. 2 is the operation flow schematic diagram of MSMS multicast pattern;
Fig. 3 is the operation flow schematic diagram of MSMS broadcast mode;
Fig. 4 is the message processing flow figure of existing MBMS business;
Fig. 5 is the schematic diagram of first better embodiment of information processing method in the MBMS business provided by the invention;
Fig. 6 is the detailed process schematic diagram of Fig. 5;
Fig. 7 is the schematic diagram of second better embodiment of information processing method in the MBMS business provided by the invention;
Fig. 8 is the detailed process schematic diagram of Fig. 7;
Fig. 9 is the schematic diagram of the 3rd better embodiment of information processing method in the MBMS business provided by the invention.
Figure 10 is the communication system schematic block diagram of realization MBMS business provided by the invention.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, be described in further detail below in conjunction with accompanying drawing and better embodiment of the present invention.
First better embodiment provided by the invention as shown in Figure 5, in realizing the MBMS operation system, the carrying judging unit is set in GGSN, in order to when BM-SC issues data, judge follow-uply whether can receive data, if follow-uply cannot receive data, it is unavailable then to send its carrying of message informing BM-SC, and in notification message assignable cause.BM-SC does further processing according to notification message, and avoiding because of not knowing that SGSN can't receive data, and the BM-SC that causes is issued to the problem that the data of GGSN can't continue to transmit.
According to the present invention in the MBMS business of first better embodiment detail flowchart of information processing method as shown in Figure 6, it mainly may further comprise the steps:
Step 601:BM-SC session and sending function send session and begin to ask Session StartRequest message to GGSN, indicate transfer of data on the horizon, and session attribute is provided.GGSN is according to receiving that the session from BM-SC begins request, returns session to BM-SC and begins to respond SessionStart Response.
Step 602:GGSN SGSN downstream sends session and begins request, and the judging unit of GGSN carrying simultaneously starts timer;
If before timer expiry, GGSN does not receive the response of any SGSN, and then execution in step 603;
If GGSN has received response from some SGSN before timer expiry, show to receive the MBMS data that then GGSN does not further carry judgment processing;
If before timer expiry, GGSN does not receive response from any one SGSN, show that it can receive the MBMS data, i.e. all responses that are dealt into GGSN all show, these SGSN can not receive data, and then execution in step 603, and the possible cause that described SGSN can not receive data comprises: do not support the MBMS ability, do not have enough available resources, information word is made mistakes or the like.
This GGSN carrying of step 603:GGSN carrying judgment unit judges is unavailable, and it is unavailable to send the current GGSN of the unavailable message informing of carrying to BM-SC.
If GGSN only notifies BM-SC, current this GGSN is unavailable, and then BM-SC is changed to this GGSN " cannot receive data ", no longer sends any data to GGSN during this time MBMS session, does not also reattempt to this GGSN transmission session to begin request.Perhaps, directly with deletion in " the downstream node listing " of this GGSN from BM-SC.
If GGSN is in the notice disabled while of the current GGSN of BM-SC, in notification message, carry detailed cause description, show that downstream SGSN does not have response or downstream SGSN can not receive the reason of MBMS data, promptly in notice or response, to inform BM-SC, be owing to permanent reason, still interim reason causes GGSN to be in " cannot receive data " state, if interim reason, follow-up BM-SC can adopt regularly or the mode of not timing repeatedly sends Session StartRequest to GGSN, specifically depends on implementation; If permanent reason, then BM-SC then is changed to this GGSN " cannot receive data ", during this time MBMS session, do not send any data to GGSN, do not reattempt to this GGSN yet and send Session Start Request, perhaps, directly with deletion in " the downstream node listing " of this GGSN from BM-SC.
Said process can use STR/STA (session stops asking/replying) message in the Diameter to realize, also can adopt existing MBMS logout flow path to notify BM-SC with deletion in " the downstream node listing " of GGSN from BM-SC.
Second better embodiment provided by the invention as shown in Figure 7, similar and first better embodiment needs also between SGSN and BSC/RNC to confirm whether the downstream can receive the problem of data, when GGSN issues data, the carrying judging unit is set among the SGSN, in order to judge whether BSC/RNC can receive data, if cannot, then SGSN is to the disabled notice of GGSN feedback carrying, and GGSN does corresponding processing according to this notice.
Figure 8 shows that the present invention's second better embodiment detail flowchart, this second better embodiment and first better embodiment are similar, it mainly is at the SGSN place carrying judging unit to be set, after receiving that session from upstream GGSN begins request, when BSC/RNC sent conversation request downstream, SGSN carrying judging unit started timer event, whether can receive data to judge its downstream, if timer expiry, the then unavailable message of the carrying of GGSN report upstream.It specifically may further comprise the steps:
Step 801:SGSN receives that the session from GGSN begins request message, and returns session and begin response message.
Step 802:SGSN BSC/RNC downstream sends session and begins request message, and SGSN carrying judging unit starts timer simultaneously.
If before timer expiry, SGSN does not receive the response of any BSC/RNC, and then execution in step 803;
If SGSN has received response from some BSC/RNC before timer expiry, this response shows can receive the MBMS data, and then SGSN does not further carry judgment processing;
If before timer expiry, SGSN does not receive that from any one BSC/RNC response does not show that it can receive the MBMS data, i.e. all responses that are dealt into SGSN show that all these BSC/RNC can not receive data, and then execution in step 803.
Step 803:SGSN sends the unavailable message of carrying to GGSN, and portability cause description in this message shows that downstream BSC/RNC does not have response or its downstream BSC/RNC can not receive the reason of MBMS data.GGSN then this SGSN is set to " cannot receive data ", then during this time MBMS session, no longer issue any data and give this SGSN, do not reattempt yet and send session to this SGSN and begin request, perhaps will delete in " the downstream node tabulation " of this SGSN from GGSN.
If all SGSN send the unavailable message of carrying to GGSN, then GGSN sends the unavailable message of carrying to BM-SC, and the step 603 in the Xiang Guan handling process and first preferred embodiment is similar thereafter.
The 3rd better embodiment provided by the invention as shown in Figure 9, it all is provided with the carrying judging unit in GGSN and SGSN, in order to judge whether its downstream can receive data, when judging whether the downstream can receive data, also can adopt timer event to realize respectively.
At first, when GGSN receives that session from BM-SC begins request message, return session to BM-SC and begin response message.
Secondly, GGSN sends session to SGSN and begins request message, and the carrying judging unit of GGSN starts timer simultaneously.
Before timer expiry, GGSN has received response from some SGSN, shows to receive the MBMS data, and GGSN does not further carry judgment processing.SGSN continues to send the beginning conversation request to its downstream BSC/RNC, and the carrying judging unit among the SGSN starts timer event, judges further whether its downstream can receive data.It is identical with the present invention's second preferred embodiment to judge among the SGSN whether BSC/RNC can receive the concrete steps of data, does not repeat them here.
Before timer expiry, GGSN does not receive the response of any SGSN, then sends the unavailable message of carrying to BM-SC, and BM-SC does respective handling in detail according to this, and its process and first preferred embodiment are roughly the same, are not described in detail in this.
Before timer expiry, GGSN is not when any one SGSN receives that response shows that it can receive the MBMS data, i.e. all responses that are dealt into GGSN show that all these SGSN can not receive data, and then GGSN sends the unavailable message of carrying to BM-SC.Can carry cause description in this message.BM-SC does further processing according to this message, and its processing method and first preferred embodiment are roughly the same, also repeat no more at this.
Be the communication system schematic diagram of realization MBMS business provided by the invention as shown in figure 10, this system comprises root node and some intermediate nodes, be provided with carrying judging unit and beared information transmitting element in the intermediate node, when root node or upstream node send the conversation request response to downstream node, the intermediate node upstream nodes sends the conversation request response, and send conversation request response to downstream node, whether described carrying judgment unit judges downstream node can receive data simultaneously, when if downstream node can not receive data, described beared information transmitting element upstream nodes sends the unavailable message of carrying.Upstream node is done further processing according to the unavailable message of described carrying.
Concrete, when described intermediate node when receiving that the session that sends the upstream begins to ask, send session to downstream node and begin request message, simultaneously described carrying judging unit starts timer event.Before the timer expiry, intermediate node does not receive from downstream node response or does not receive that any downstream node response shows and can receive data that then upstream nodes sends the unavailable message of carrying.
After upstream node is received the unavailable message of carrying of intermediate node transmission, this intermediate node is set to receive the state of data, during this time MBMS session, no longer send any data to this intermediate node, do not reattempt yet and send session to this intermediate node and begin request, perhaps upstream node directly with this intermediate node from its downstream node listing deletion.
Intermediate node can be GGSN and/or SGSN, if when intermediate node is GGSN, then its corresponding upstream node is BM-SC, and its corresponding downstream node is SGSN.When if intermediate node is SGSN, then its corresponding upstream node is SGSN, and its corresponding downstream node is RNC and/or BSC.
The above only is process of the present invention and method embodiment, in order to restriction the present invention, all any modifications of being made within the spirit and principles in the present invention, is not equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (18)
1, a kind of information processing method of realizing multi-medium broadcast/group broadcast MBMS business is characterized in that may further comprise the steps:
When intermediate node is received from the service request of upstream node, judge whether its downstream node can receive data,
If judged result is a downstream node can not receive data the time, the intermediate node upstream nodes sends the unavailable message of carrying.
2, method according to claim 1 is characterized in that: intermediate node sends session to downstream node and begins request message after receiving that the session from upstream node begins request, starts timer simultaneously.
3, method according to claim 2 is characterized in that: before the timer expiry, intermediate node does not receive from downstream node response or does not receive that any downstream node response shows and can receive data that then upstream nodes sends the unavailable message of carrying.
4, method according to claim 1, it is characterized in that: after upstream node is received the unavailable message of carrying of intermediate node transmission, this intermediate node is set to receive the state of data, during this time MBMS session, no longer send any data to this intermediate node, do not reattempt yet and send session to this intermediate node and begin request, perhaps upstream node directly with this intermediate node from its downstream node listing deletion.
5, method according to claim 1 is characterized in that: carry cause description in the unavailable message of described carrying, can not receive the reason of data in order to show downstream node.
6, method according to claim 5 is characterized in that: described reason comprises: do not support the MBMS ability, do not have enough available resources or information word to make mistakes.
7, method according to claim 5, it is characterized in that: if the reason of the unavailable message of described carrying is permanent reason, then upstream node do not reattempt to this intermediate node send that session begins to ask or directly with the downstream node listing of this intermediate node from upstream node in delete; If the reason of the unavailable message of described carrying is interim reason, upstream node adopts regularly or the mode of not timing repeatedly begins request message to this intermediate node transmission session.
8, according to claim 4 or 7 described methods, it is characterized in that: described upstream node does not reattempt and sends session to this intermediate node to begin request be to stop the realization of request/response message by session, describedly directly the process of deleting in the downstream node listing of this intermediate node from upstream node is realized by the MBMS logout flow path.
9, according to each described method of claim 1 to 7, it is characterized in that: described intermediate node comprises Gateway GPRS Support Node GGSN and/or Serving GPRS Support Node SGSN; When described intermediate node was GGSN, its corresponding upstream node was broadcast/multicast service center BM-SC, and its corresponding downstream node is SGSN; When described intermediate node was SGSN, its corresponding upstream node was GGSN, and its corresponding downstream node is radio network controller (RNC) and/or base station controller BSC.
10, a kind of communication system that realizes multi-medium broadcast/group broadcast MBMS business comprises root node and at least one intermediate node, it is characterized in that:
Have at least an intermediate node to be provided with the carrying judging unit,, judge whether its downstream node can receive data, and when downstream node can not receive data, upstream nodes sent the unavailable message of carrying in order to when the request of upstream node issuing service.
11, system according to claim 10 is characterized in that: described intermediate node sends session to downstream node and begins request message after receiving that the session that sends the upstream begins request, and simultaneously described carrying judging unit starts timer event.
12, system according to claim 11, it is characterized in that: before the timer expiry, intermediate node does not receive from downstream node response or does not receive that any downstream node response shows and can receive data that then upstream nodes sends the unavailable message of carrying.
13, method according to claim 10, it is characterized in that: after upstream node is received the unavailable message of carrying of intermediate node transmission, this intermediate node is set to receive the state of data, during this time MBMS session, no longer send any data to this intermediate node, do not reattempt yet and send session to this intermediate node and begin request, perhaps upstream node directly with this intermediate node from its downstream node listing deletion.
14, according to each described system of claim 10 to 13, it is characterized in that: described intermediate node comprises: Gateway GPRS Support Node GGSN and/or Serving GPRS Support Node SGSN, when described intermediate node is GGSN, its corresponding upstream node is broadcast/multicast service center BM-SC, and its corresponding downstream node is SGSN; When described intermediate node was SGSN, its corresponding upstream node was GGSN, and its corresponding downstream node is RNC and/or BSC.
15, a kind of node, be used for realizing the communication system of MBMS business, it is characterized in that: this node comes bearer service as intermediate node, and this node is provided with the carrying judging unit, in order to when receiving the service request that the upstream sends, judge whether its downstream can receive data.
16, node according to claim 15, it is characterized in that: described carrying judging unit is realized by timer event, this node is when transmitting service request downstream, start timer, before timer expiry, do not receive the response in any downstream or show that without any response the downstream can receive data and judge that then the downstream cannot receive data.
17, according to claim 15 or 16 described nodes, it is characterized in that: described node also comprises the beared information transmitting element, when cannot receive data in carrying judgment unit judges downstream, upstream sends the unavailable message of carrying.
18, node according to claim 17 is characterized in that: described node is Gateway GPRS Support Node GGSN or Serving GPRS Support Node SGSN.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100347830A CN101047528A (en) | 2006-03-28 | 2006-03-28 | Processing method and system for information in multi-media broadcast/multicast service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100347830A CN101047528A (en) | 2006-03-28 | 2006-03-28 | Processing method and system for information in multi-media broadcast/multicast service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101047528A true CN101047528A (en) | 2007-10-03 |
Family
ID=38771780
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006100347830A Pending CN101047528A (en) | 2006-03-28 | 2006-03-28 | Processing method and system for information in multi-media broadcast/multicast service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101047528A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011011946A1 (en) * | 2009-07-28 | 2011-02-03 | 中兴通讯股份有限公司 | Method and device for transmitting multimedia broadcast multicast service notification messages |
| CN102929945A (en) * | 2012-09-28 | 2013-02-13 | 用友软件股份有限公司 | Data distribution device and data distribution method |
| CN105704185A (en) * | 2014-11-27 | 2016-06-22 | 华为软件技术有限公司 | Resource transfer method and apparatus |
| CN106559186A (en) * | 2016-03-21 | 2017-04-05 | 天地融科技股份有限公司 | Data transmission method and system, main communication apparatus and from communication apparatus |
| CN106561014A (en) * | 2015-11-18 | 2017-04-12 | 天地融科技股份有限公司 | Data transmission method and system, main communication equipment, and slave communication equipment |
| CN106919622A (en) * | 2015-12-28 | 2017-07-04 | 伊姆西公司 | For the method and apparatus of distributed data processing |
| CN107580346A (en) * | 2011-03-17 | 2018-01-12 | 高通股份有限公司 | For the successional Target cell selection of multicast broadcast multimedia service |
| CN114071600A (en) * | 2020-08-04 | 2022-02-18 | 大唐移动通信设备有限公司 | Switching method and device based on MBMS service and processor readable storage medium |
-
2006
- 2006-03-28 CN CNA2006100347830A patent/CN101047528A/en active Pending
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9432970B2 (en) | 2009-07-28 | 2016-08-30 | Zte Corporation | Method and device for transmitting multimedia broadcast multicast service notification messages |
| CN101969604B (en) * | 2009-07-28 | 2015-08-12 | 中兴通讯股份有限公司 | The sending method of a kind of multimedia broadcasting and multicast service notice message and device |
| WO2011011946A1 (en) * | 2009-07-28 | 2011-02-03 | 中兴通讯股份有限公司 | Method and device for transmitting multimedia broadcast multicast service notification messages |
| CN107580346B (en) * | 2011-03-17 | 2021-02-02 | 高通股份有限公司 | Target cell selection for multimedia broadcast multicast service continuity |
| CN107580346A (en) * | 2011-03-17 | 2018-01-12 | 高通股份有限公司 | For the successional Target cell selection of multicast broadcast multimedia service |
| CN102929945B (en) * | 2012-09-28 | 2016-03-30 | 用友网络科技股份有限公司 | Data distribution device and data distributing method |
| CN102929945A (en) * | 2012-09-28 | 2013-02-13 | 用友软件股份有限公司 | Data distribution device and data distribution method |
| CN105704185A (en) * | 2014-11-27 | 2016-06-22 | 华为软件技术有限公司 | Resource transfer method and apparatus |
| CN105704185B (en) * | 2014-11-27 | 2019-04-12 | 华为软件技术有限公司 | Resource transfers method and device |
| CN106561014A (en) * | 2015-11-18 | 2017-04-12 | 天地融科技股份有限公司 | Data transmission method and system, main communication equipment, and slave communication equipment |
| CN106919622A (en) * | 2015-12-28 | 2017-07-04 | 伊姆西公司 | For the method and apparatus of distributed data processing |
| CN106919622B (en) * | 2015-12-28 | 2021-10-15 | 伊姆西Ip控股有限责任公司 | Method and apparatus for distributed data processing |
| CN106559186A (en) * | 2016-03-21 | 2017-04-05 | 天地融科技股份有限公司 | Data transmission method and system, main communication apparatus and from communication apparatus |
| CN114071600A (en) * | 2020-08-04 | 2022-02-18 | 大唐移动通信设备有限公司 | Switching method and device based on MBMS service and processor readable storage medium |
| CN114071600B (en) * | 2020-08-04 | 2023-09-05 | 大唐移动通信设备有限公司 | MBMS service based switching method, device and processor readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1306766C (en) | Service recognition and route method in multimedia broadcast multicast service system | |
| CN1297109C (en) | Method for reading multimedia broadcasting/group broadcasting service switch-in information | |
| CN100344181C (en) | Method of simplifying message transmission processing | |
| CN101047528A (en) | Processing method and system for information in multi-media broadcast/multicast service | |
| WO2006015553A1 (en) | The multimedia broadcast / multicasting serve service transmission method | |
| CN1798063A (en) | Method at network side for obtaining situation of receiving multimedia broadcasting / multicasting service by users | |
| CN101039459A (en) | Method and apparatus for multimedia broadcast and multicast service information | |
| CN101039503A (en) | Method for realizing paging in multimedia broadcasting/multicast service | |
| CN100379221C (en) | Multimedia multicast business registration method | |
| CN101039457A (en) | Method and apparatus for acquiring point-to-multipoint multimedia broadcast and multicast service information | |
| CN1774124A (en) | Business control information transmitting method in multimedia broadcasting/group broadcasting service | |
| CN1691676A (en) | Method for determining number of receiving users in multimedia broadcast/multicast service | |
| CN1327742C (en) | Method of realizing active in multimedia gooup broadcasting service | |
| CN100502280C (en) | Method of assuring network side to receive user equipment message | |
| CN1859623A (en) | Method for realizing stream media service | |
| CN1697394A (en) | Method for updating routing area in operation of multimedia broadcast/multicast service | |
| CN1921639A (en) | Method for responding request of MBMS point to point collection building | |
| CN1917485A (en) | Method for responding to request of establishing connection from MBMS point to point | |
| CN100466762C (en) | Method for realizing informing of broadcast multicast service | |
| CN1802010A (en) | Method for realizing multicast broadcast service registration | |
| CN100563361C (en) | The method and apparatus of broadcast multicast service deactivation | |
| CN1960346A (en) | Method for registering multimedia service of broadcast / multicast service | |
| CN1937834A (en) | Broadcasting/multicast business control information transmission method | |
| CN1815995A (en) | Transmission method for controlling access-in information on channel in multi-media broadcasting/organization broadcasting business | |
| CN1620032A (en) | Method of realizing multimedia broadcasting group broadcnsting business deactivation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20071003 |