CN101175003A - Device for access to multicast service from wireless network controller - Google Patents
Device for access to multicast service from wireless network controller Download PDFInfo
- Publication number
- CN101175003A CN101175003A CNA2006101438589A CN200610143858A CN101175003A CN 101175003 A CN101175003 A CN 101175003A CN A2006101438589 A CNA2006101438589 A CN A2006101438589A CN 200610143858 A CN200610143858 A CN 200610143858A CN 101175003 A CN101175003 A CN 101175003A
- Authority
- CN
- China
- Prior art keywords
- multicast service
- network controller
- radio network
- sgsn
- descendant node
- 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.)
- Withdrawn
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a device to access multicasting businesses from a wireless network controller. The device includes the arranging department of a downlink node list, which is arranged on the lateral side of a core network and is used for arranging the downlink node list in a multicasting business bearing context. The device still includes the recording department of a first descending node list, which is arranged on the lateral side of the core network and responses to multicasting business registration requests from a drifting wireless network controller. The recording department of the first downlink node list records the node information of the drifting wireless network controller in the downlink node list which is arranged by the arranging department of the downlink node list and feeds back the multicasting registration response information to the drifting wireless network controller. The device also includes a session starting request department of the multicasting businesses, which is arranged on the lateral side of the core network and responses to the session starting request from GGSN. The session starting request department of the multicasting businesses starts to send a session starting request message to all wireless network controller and/or all base station controllers which are connected through Iu ports.
Description
Technical field
The present invention relates to the communications field, and more particularly, relate to a kind of device from radio network controller access to multicast service (MBMS, Multimedia Broadcast/Multicast Service).
Background technology
In order to effectively utilize mobile network resource, existing mobile communication system has proposed to use the thought of multicast/broadcast transport service, i.e. MBMS (MultimediaBroadcast/Multicast Service).
MBMS provides the point-to-multipoint service of a data source to a plurality of users send data in the mobile network, realize that Internet resources are shared, raising utilization rate of network resource, the interface resource of especially eating dishes without rice or wine.MBMS provides dual mode: broadcast mode and multicast mode.MBMS 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, multimedia broadcast/multicast service MBMS is based on the WCDMA/GSM Packet Based Network, by increasing some new functional entitys, as broadcast multicast service center BM-SC, existing packet domain functional entity such as SGSN (packet service node), GGSN (packet gateway node), RAN (Radio Access Network) and UE (user terminal) are increased the MBMS function, and defined new logic shared channel and realize that interface-free resources shares.Wherein, the network architecture of using MBMS under the mobile communication system as shown in Figure 1.
Except BM-SC, all be the carrying network element of mobile communication system, finish data-transformation facility.From BM-SC to UE, be called from descending, following node is called the descendant node (downstream node) of the node above the next-door neighbour in the route of down direction.Otherwise be called uply, node is called upstream node (upstream node).Be called the descendant node of GGSN as SGSN, GGSN becomes the upstream node of SGSN.
Realize inserting the MBMS business, need a series of Signalling exchanges to finish the foundation of Data-carrying and signaling bear.Different according to business model (broadcasting and multicast), the content of Signalling exchange is different with mode.
For broadcasting service, comprise following flow process at least: service announcements: inform certain professional relevant information of user by network side by notification message, comprise reproduction time, multicast/broadcast mode, address information etc.; Session begins: before network begins to play related service, can send session from BM-SC and begin message to some GGSN (Gateway GPRSSupport Node, gateway GRPS support node) node, GGSN is handed down to some SGSN (Serving GPRS Support Node again, service GRPS support node), arrive RNC successively, all these nodes are that configured in advance is good, be tree by single to distributing (for broadcasting service more, the effect of this flow process is to set up bearing resource on every link that is issued to RNC), from each network element, this resource comprises a MBMS BearerContext and each information of preserving in it, as QoS information, tunnel information, business information etc.; Conversation end: when a MBMS service ending, the path initiation session end that BM-SC still begins message according to session is to each network element, and purpose is the bearing resource that cancellation is set up.
For multicast service, comprise following flow process at least: service announcements: same broadcasting service; The user activates: the user wants to add some multicast service, need to add multicast group, and the MBMS UE Context that foundation is correlated with on the network element of network side, the information that is used for recording user, trigger register flow path simultaneously, promptly set up MBMS Bearer Context, but do not finish the distribution of concrete resource; Registration: set up MBMS Bearer Context, obtain professional relevant QoS information, but do not finish the distribution of concrete resource, registration can have the activation message trigger, be called implicit registration, also can detect terminal by RNC has the MBMS demand, and oneself does not also have relevant service resources, just initiatively initiate, be called explicit registration; Session begins: finish the distribution of concrete bearing resource; Conversation end: releasing bearing resource; Deexcitation: leave multicast group, discharge MBMS UE context; Nullify: when a node does not have descendant node to need MBMS professional, can discharge the link of this node, initiate to nullify two conditions that need: no descendant node and no MBMS UE context by nullifying to upstream node.
In order to finish the processing of MBMS signaling and MBMS business data transmission, existing MBMS mechanism is to the network element entity of network side: RNC, SGSN, GGSN, and BM-SC, set up a MBMS Service Context at every kind of MBMS business, be used to write down this professional relevant information, and set up the MBMS information that a MBMS User Context is used to write down each user at each user of access to multicast service.
In the MBMS of GGSN and BM-SC Service Context, information such as IP multicast address, APN, TMGI and descendant node tabulation have been comprised.Wherein, IP multicast address, APN and TMGI are MBMS business of sign, the address information of the next network node that downlink data will arrive has been enumerated in descendant node tabulation, thereby makes certain MBMS business datum be orderly unduplicated each node that is issued to of tree.The descendant node tabulation of BM-SC promptly will receive the address information of all GGSN of this business, as the IP address.The descendant node tabulation of GGSN promptly will be accepted the address information of all SGSN of this business.There is not the descendant node tabulation among the MBMS bearer context of SGSN, because SGSN is all coupled RNC at the descendant node of issuing service data.But (promptly a RNC may connect a plurality of SGSN under the situation of Iu-Flex, a SGSN also may connect a plurality of RNC), a RNC may receive that a plurality of SGSN begin message to the session of same business, and at this moment, RNC is as long as select one of them SGSN.But for SGSN, it will write down concrete those RNC need insert this business, because some RNC does not insert from this SGSN.At present, SGSN does not descend row-column list, does not perhaps write down these descendant nodes in the MBMS of SGSN bearer context, and is provided with voluntarily in other places, causes disunity.
The method that in multicast and the broadcasting descendant node is set is different, and in broadcasting service, descendant node is a fixed configurations.And in multicast service, there are two kinds of methods to set up, a kind of SGSN that triggers when initiating activation process by the user initiates registration message and sets up, be that SGSN receives the activation request that the user need add certain multicast service group, and the MBMS Bearer Context of this service groups not also on the SGSN, just set up this context, and to GGSN initiation register requirement, if GGSN does not have MBMS Bearer Context yet, then set up context, and with this SGSN address note in own descendant node tabulation, initiate register requirement to BM-SC simultaneously, BM-SC with GGSN address note in the descendant node of oneself is tabulated.
Another kind method is, when the user who is inserting the multicast service of MBMS moves to a new RNC scope, because the cause of network settings, the reorientation flow process does not also take place, and (effect of this flow process is that original SGSN is rebulid new network element to the link of UE relation, comprise new SGSN, RNC, base station and wireless network cell), the new RNC of this moment is DRNC (after finishing reorientation, DRNC becomes SRNC), DRNC has detected the relevant business of MBMS, just select a default SGSN to initiate register requirement, such registration does not trigger by activating, and is called to show registration.Show what registration was normally initiated by DRNC.
Above-mentioned idiographic flow as shown in Figure 2, wherein, Fig. 2 is the schematic diagram that the explicit register flow path of MBMS is shown.As shown in Figure 2, in step 201, when interesting, RNC SGSN under it sends MBMS login request message (MBMS Registration Request) to the UE that detects its control as RNC to certain MBMS bearer service; In step S202, if the last MBMS bearer context that does not have at this MBMS bearer service of SGSN, SGSN has received the register requirement about this MBMS bearer service from RNC simultaneously, or at this MBMS bearer service, first MBMS UE context is created on SGSN, and also there is not corresponding M BMS bearer context on the SGSN, SGSN will create a MBMS bearer context (placing " Standby " state), and send MBMS login request message (MBMS RegistrationRequest) to GGSN and (carry IP multicast address, APN); In step 203, if the last MBMS bearer context that does not have at this MBMS bearer service of GGSN, GGSN has received the register requirement about this MBMS bearer service from SGSN simultaneously, or at this MBMS bearer service, first MBMS UE context is created on GGSN, and also there is not corresponding M BMS bearer context on the GGSN, GGSN will create a MBMS bearer context (placing " Standby " state), and agency and transfer function transmission MBMS login request message (MBMS Registration Request) to BM-SC (are carried IP multicast address, APN); In step 204, when the MBMS login request message (MBMS Registration Request) received from GGSN, the agency of BM-SC and transfer function add the sign of GGSN in " list of downstream nodes " parameter in its MBMS bearer context, and return MBMS registration reply message (MBMS Registration Response) to GGSN and (carry TMGI, the MBMS bearing capacity that requires), in step 205, if this moment, the MBMS bearer context was a " active " state, BM-SC just begins (Session Start) flow process to the GGSN initiation session; In step 206, if GGSN has received register requirement from SGSN in step 2, GGSN will carry out following operation: the sign of SGSN is added in " the list of downstream nodes " parameter in its MBMS bearer context, return MBMS registration reply message (MBMS Registration Response) (carrying TMGI, the bearing capacity of requirement) to SGSN; In step 207, if this moment, the MBMS bearer context was a " active " state, GGSN just begins (Session Start) flow process to the SGSN initiation session; In step 208, if SGSN has received register requirement from DRNC in step 1, SGSN will carry out following operation: if SGSN has received register requirement from DRNC in step 1, SGSN will carry out following operation; And in step 209, if this moment, the MBMS bearer context was a " active " state, SGSN just begins (Session Start) flow process to the DRNC initiation session.
Finished after the registration, business datum has been sent to DRNC and user from the default SGSN.This moment is not because carry out reorientation, MBMS UE Context of this user not all among default SGSN and the DRNC.The problem that causes like this is that the registration of finishing in the default SGSN is easy to be nullified by SGSN again.Because the condition that SGSN multicast service logout flow path satisfies is: when in SGSN, not having MBMS UE Context (so SGSN does not have descendant node to have only condition of the MBMS UE context of judgement, the initiation condition of GGSN and BM-SC is not have MBMS UE Context and descendant node tabulation for empty).After the cancellation, business datum will no longer be passed through from this node.
In addition, begin in the flow process in the session of setting up the load plane connection, SGSN begins request will for all RNC transmission sessions, in the success response that obtains RNC, there are two types, a kind of is to agree to set up load plane, promptly setting up the Iu carrying connects, another kind is to receive to begin request, but sets up load plane with other SGSN, therefore not SGSN foundation therewith.In this case, SGSN only need be set up the RNC that load plane is connected with it with the MBMS data distributing.Therefore, which RNC has set up to be connected with this SGSN needs record.If but SGSN does not have descendant node tabulation, just can not effectively write down and send with data.
As mentioned above, there are the following problems in the correlation technique, and: SGSN is different with GGSN and BM-SC, and SGSN does not have descendant node tabulation, and whether SGSN can only comprise MBMS UE Context by detection and judge whether to nullify this business like this.And show at DRNC under the situation of registration that it is professional but this user's context not causes very fast cancellation and service disconnection that MBMS need be inserted in the default SGSN.For the situation of Iu-Flex, specifically which RNC need insert the MBMS business from certain SGSN, promptly set up the Iu carrying and connect, this SGSN record to some extent in row-column list down.
Summary of the invention
Consider the problems referred to above and make the present invention, the invention provides for this reason a kind of in mobile communication system the device from the radio network controller access to multicast service.
Main invention thought of the present invention is, at multicast service, at SGSN (ServingGPRS Support Node, service GRPS support node) among the MBMS Bearer Context descendant node tabulation is set, nodal information that is used to write down the DRNC (floating radio network controller) that initiates explicit registration and the nodal information of setting up the RNC (radio network controller) that load plane is connected, make that the cancellation condition of RNC will not be that DRNC can initiate explicit cancellation, the RNC that makes all and SGSN set up load plane can both initiate explicit cancellation; And the cancellation condition of SGSN is the same with GGSN and BM-SC, does not promptly have MBMS UE Context, and the descendant node tabulation is for empty.
According to a first aspect of the invention, provide a kind of method from the radio network controller access to multicast service.
This method may further comprise the steps: the descendant node tabulation is set in the multicast service carrier context; In response to the multicast service registering request from floating radio network controller, SGSN records the nodal information of floating radio network controller in the descendant node tabulation, and returns the multicast service registering response message to floating radio network controller; And begin request message in response to session from GGSN, SGSN begins request message to all radio network controllers that link to each other through the Iu mouth and/or all base station controllers transmission session, afterwards, radio network controller or base station controller send session to SGSN and begin response message, begin response message in response to session, the nodal information that SGSN will need to set up the radio network controller that load plane connects is recorded in the descendant node tabulation.
Wherein, whether need to set up load plane between SGSN and radio network controller or the base station controller, depend on that described radio network controller or base station controller begin indication parameter entrained in the response message to the described session that SGSN sends.
In the multicast service registering step, carry the multicast service carrier ability of TMGI and requirement in the multicast service registering response message.
Base station controller under radio network controller or the Iu pattern begins to carry in the response message TEID (Tunnel Endpoint Identifier, Tunnel End Point Identifier) that is used for the Iu load plane in session, and wherein, SGSN uses TEID to come multicast data forwarding.
Said method further may further comprise the steps: conversation end step, deexcitation step and multicast service are nullified step;
Wherein, multicast service is nullified step and be may further comprise the steps: the de-registration request step: when not had subscriber equipment in the subscriber equipment of radio network controller control when interested in the specific multicast service bearer service, radio network controller sends de-registration request message to SGSN, nullifies from the specific multicast service bearer service with request; And the nodal information of deleting radio network controller in the descendant node tabulation of cancellation response of step: SGSN from specific multicast service bearer service context, and to radio network controller transmission multicast service cancellation response message; Wherein, radio network controller is registered among the SGSN, has perhaps set up load plane with SGSN and has been connected.
When the tabulation of the contextual descendant node of certain bearer service among the SGSN was zero for sky and user's context number, SGSN sent de-registration request to its upstream node.
In nullifying response of step, if set up the Iu load plane for the specific multicast service bearer service between radio network controller and SGSN, then the Iu load plane is released.
To achieve these goals, according to a second aspect of the invention, provide a kind of device from the radio network controller access to multicast service.
This device comprises: the descendant node tabulation is provided with portion, is positioned at core-network side, is used at the multicast service carrier context descendant node tabulation being set; The first descendant node list records portion, be positioned at core-network side, in response to multicast service registering request from floating radio network controller, the first descendant node list records portion records the nodal information of floating radio network controller in the descendant node tabulation that is provided with by the descendant node tabulation portion of setting, and returns the multicast service registering response message to floating radio network controller; Multicast service conversation begins request portion, is positioned at core-network side, begins request in response to the session from GGSN, and multicast service conversation begins portion and begins request message to all radio network controllers that link to each other through the Iu mouth and/or all base station controllers transmission session; Multicast service conversation begins response portion, is positioned at the radio network controller side, asks the session of portion to begin request message in response to beginning from multicast service conversation, sends session to SGSN and begins response message; And the second descendant node list records portion, be positioned at core-network side, begin response message in response to described session, the nodal information of needs being set up the radio network controller that load plane connects is recorded in the described descendant node tabulation.
Wherein, whether need to set up load plane between SGSN and radio network controller or the base station controller, depend on that described radio network controller or base station controller begin indication parameter entrained in the response message to the described session that SGSN sends.
Carry the multicast service carrier ability of TMGI and requirement in the multicast service registering response message.
Preferably, this device further comprises: conversation end portion; Deexcitation portion; Multicast service cancellation portion; And Iu load plane release portion, be used to discharge the Iu load plane of setting up for the multicast service carrier business between radio network controller and the SGSN.
Wherein, session begins to carry in the response message TEID that is used for the Iu load plane, and wherein, SGSN uses TEID to come multicast data forwarding.
Wherein, multicast service cancellation portion comprises: the de-registration request module, when not had subscriber equipment in the subscriber equipment of radio network controller control when interested in the specific multicast service bearer service, the de-registration request module sends de-registration request message to SGSN, nullifies from the specific multicast service bearer service with request; And the cancellation respond module, be used for from the descendant node list message of specific multicast service bearer service context the nodal information of deletion radio network controller, and send multicast service to radio network controller and nullify response message.
Wherein, when the tabulation of the contextual descendant node of certain bearer service among the SGSN was zero for sky and user's context number, SGSN sent de-registration request to its upstream node.
By technique scheme, the present invention has realized following beneficial effect: by setting up the descendant node tabulation, can carry out professional access and cancellation exactly, improve utilization rate of network resource.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the schematic diagram according to the MBMS network architecture of correlation technique;
Fig. 2 is the schematic diagram according to the explicit register flow path of MBMS of correlation technique;
Fig. 3 is the flow chart from the method for radio network controller access to multicast service according to the embodiment of the invention;
Fig. 4 illustrates the schematic diagram that begins flow process according to the multicast service conversation of the embodiment of the invention;
Fig. 5 is the schematic diagram that illustrates according to the multicast service logout flow path of the embodiment of the invention; And
Fig. 6 is the block diagram from the device of radio network controller access to multicast service according to the embodiment of the invention.
Embodiment
Describe the present invention below with reference to the accompanying drawings in detail.
At first, embodiments of the invention provide a kind of method from the radio network controller access to multicast service.
As shown in Figure 3, this method may further comprise the steps:
Step S302, the descendant node tabulation is set in MBMS (multicast service) bearer context, wherein, the descendant node tabulation nodal information that is used to write down the DRNC (floating radio network controller) that initiates explicit registration and the nodal information of setting up the RNC (radio network controller) that load plane is connected;
Step S304, in response to the multicast service registering request from DRNC, SGSN records the nodal information of DRNC in the descendant node tabulation of its MBMS bearer context, and returns the multicast service registering response message to DRNC; Wherein, carry the MBMS bearing capacity of TMGI and requirement in the registration reply message; And
Step S306, begin request message in response to session from GGSN, SGSN begins request message to all radio network controllers that link to each other through the Iu mouth and/or all base station controllers transmission session, afterwards, radio network controller or base station controller send session to SGSN and begin response message, begin response message in response to session, the nodal information that SGSN will need to set up the radio network controller that load plane connects is recorded in the descendant node tabulation.
Wherein, whether need to set up load plane between SGSN and radio network controller or the base station controller, depend on that described radio network controller or base station controller begin indication parameter entrained in the response message to the described session that SGSN sends.
In step S306, SGSN uses 2G/3G to indicate and determines whether that session is begun request message sends to all RNC and/or all BSC; In addition, before the transmission session began response message, for the broadcasting MBMS bearer service, the BSC/ radio network controller was created the multicast service context; And among the BSC under RNC or Iu pattern, store session attribute in the MBMS context, and the status attribute in the multicast service context is set to " Active "; BSC under RNC or the Iu pattern begins to comprise in the response message TEID that is used for the Iu load plane in session, and SGSN uses this TEID to come the transmitting MBMS data, and the BSC under the Gb pattern if not being in the service of MBMS service area, does not just need the store session attribute.If BSC/RNC receives that a plurality of MBMS sessions begin request message, only to set up a loading end with one of them SGSN perhaps.
Step S308: conversation end step;
Step S310: deexcitation step;
Step S312 and step S314: multicast service is nullified step, MBMS nullifies step and is used for downstream node notice upstream node, it no longer needs to receive signaling, session attribute and data at specific MBMS bearer service, and it is removed from corresponding distribution tree, its occurrence condition is: when MBMS bearer context is correlated with in the DRNC deletion of registering in a SGSN, initiated by this DRNC; When setting up the relevant MBMS bearer context of RNC deletion that Iu carrying connects, by this RNC initiation with SGSN.
Wherein, when the tabulation of the contextual descendant node of certain bearer service among the SGSN was zero for sky and user's context number, SGSN sent de-registration request to its upstream node.
As shown in Figure 5, MBMS service cancellation flow process comprises de-registration request and cancellation two stages of response,
Particularly, step S312 (de-registration request step): when RNC (wherein, RNC is registered among the SGSN, perhaps having set up load plane with SGSN is connected) there has not been subscriber equipment in the subscriber equipment of control when interested in specific MBMS bearer service, RNC sends de-registration request message to SGSN, nullifies from specific MBMS bearer service with request;
Alternatively, if RNC might can need to use identical MBMS bearer service again very soon, for fear of unnecessary signaling transmission, RNC can determine not to be to nullify from this MBMS bearer service immediately;
The sign of deletion RNC in the descendant node list message of step S314 (cancellation response of step): SGSN from specific MBMS bearer service context, and to RNC transmission multicast service cancellation response message.
In step S314, if set up the Iu load plane for specific MBMS bearer service between RNC and SGSN, then the Iu load plane is released.
In addition, embodiments of the invention also provide a kind of device from the radio network controller access to multicast service.
As shown in Figure 6, this device comprises:
The descendant node tabulation is provided with portion 602, be positioned at core-network side, be used for the descendant node tabulation being set at the multicast service carrier context, wherein, the descendant node tabulation is used to write down the nodal information and the nodal information of setting up the radio network controller of load plane of the floating radio network controller of initiating explicit registration;
The first descendant node list records portion 604, be positioned at core-network side, in response to multicast service registering request from floating radio network controller, multicast service registering portion records the nodal information of floating radio network controller by the descendant node tabulation and is provided with in the descendant node list parameter of portion's 602 structures, and returns the multicast service registering response message to floating radio network controller; Wherein, carry the multicast service carrier ability of TMGI and requirement in the registration reply message;
Multicast service conversation begins request portion 606, is positioned at core-network side, begins request in response to the session from GGSN, and multicast service conversation begins portion and begins request message to all radio network controllers that link to each other through the Iu mouth and/or all BSC transmission session; Multicast service conversation begins response portion 608, is positioned at the radio network controller side, begins request message in response to the session that begins request portion 606 from multicast service conversation, sends session to SGSN and begins response message; And the second descendant node list records portion 610, be positioned at core-network side, begin response message in response to session, the nodal information of needs being set up the radio network controller that load plane connects is recorded in the descendant node tabulation.
Wherein, whether need to set up load plane between SGSN and radio network controller or the base station controller, depend on that described radio network controller or base station controller begin indication parameter entrained in the response message to the described session that SGSN sends.
Wherein, session begins to carry in the response message TEID that is used for the Iu load plane, and SGSN uses TEID to come multicast data forwarding.
In addition, multicast service conversation begins request portion 606 and uses 2G/3G to indicate to determine whether that session is begun request message sends to all RNC and/or all BSC.
Preferably, the said apparatus according to the embodiment of the invention also comprises: conversation end portion 612; Deexcitation portion 614; Multicast service cancellation portion 616; And Iu load plane release portion 618, be used to discharge the Iu load plane of setting up for the multicast service carrier business between radio network controller and the SGSN.
Wherein, multicast service cancellation portion 616 comprises: de-registration request module 616-2, when not had subscriber equipment in the subscriber equipment of radio network controller control when interested in the specific multicast service bearer service, the de-registration request module sends de-registration request message to SGSN, nullifies from the specific multicast service bearer service with request; And nullify respond module 616-4, be used for the sign of deletion radio network controller from the descendant node list message of specific multicast service bearer service context, and send multicast service cancellation response message to radio network controller.
Wherein, when the tabulation of the contextual descendant node of certain bearer service among the SGSN was zero for sky and user's context number, SGSN sent de-registration request to its upstream node.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.
Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (7)
1. the device from the radio network controller access to multicast service is characterized in that, comprising:
The descendant node tabulation is provided with portion, is positioned at core-network side, is used at the multicast service carrier context descendant node tabulation being set;
The first descendant node list records portion, be positioned at core-network side, in response to multicast service registering request from floating radio network controller, the described first descendant node list records portion records the nodal information of described floating radio network controller in the descendant node tabulation that is provided with by the described descendant node tabulation portion of setting, and returns the multicast service registering response message to described floating radio network controller;
Multicast service conversation begins request portion, be positioned at core-network side, begin request in response to the session from GGSN, described multicast service conversation begins portion and begins request message to all radio network controllers that link to each other through the Iu mouth and/or all base station controllers transmission session;
Multicast service conversation begins response portion, is positioned at the radio network controller side, in response to begin to ask the session of portion to begin request message from described multicast service conversation, sends session to SGSN and begins response message; And
The second descendant node list records portion, be positioned at core-network side, begin response message in response to described session, the nodal information that the described second descendant node list records portion will need to set up the radio network controller that load plane connects is recorded in the described descendant node tabulation.
2. the device from the radio network controller access to multicast service according to claim 1, it is characterized in that, whether need to set up load plane between SGSN and radio network controller or the base station controller, depend on that described radio network controller or base station controller begin indication parameter entrained in the response message to the described session that SGSN sends.
3. the device from the radio network controller access to multicast service according to claim 1 is characterized in that, carries the multicast service carrier ability of TMGI and requirement in the described multicast service registering response message.
4. the device from the radio network controller access to multicast service according to claim 1 is characterized in that, described session begins to carry in the response message TEID that is used for the Iu load plane, and wherein, SGSN uses described TEID to come multicast data forwarding.
5. the device from the floating radio network controller access to multicast service according to claim 1 is characterized in that, further comprises: conversation end portion, deexcitation portion and multicast service cancellation portion; Wherein, described multicast service cancellation portion comprises:
The de-registration request module, when not had subscriber equipment in the subscriber equipment of radio network controller control when interested in the specific multicast service bearer service, described de-registration request module sends de-registration request message to SGSN, nullifies from described specific multicast service bearer service with request; And
Nullify respond module, be used for the nodal information of the described radio network controller of deletion from the descendant node tabulation of described specific multicast service bearer service context, and send multicast service cancellation response message to described radio network controller.
6. the device from the floating radio network controller access to multicast service according to claim 5 is characterized in that, further comprises:
Iu load plane release portion is used to discharge the Iu load plane of setting up for the multicast service carrier business between radio network controller and the SGSN.
7. the device from the radio network controller access to multicast service according to claim 1, it is characterized in that, when the tabulation of the contextual descendant node of certain bearer service among the SGSN was zero for sky and user's context number, SGSN sent de-registration request to its upstream node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101438589A CN101175003A (en) | 2006-11-03 | 2006-11-03 | Device for access to multicast service from wireless network controller |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101438589A CN101175003A (en) | 2006-11-03 | 2006-11-03 | Device for access to multicast service from wireless network controller |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101175003A true CN101175003A (en) | 2008-05-07 |
Family
ID=39423273
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006101438589A Withdrawn CN101175003A (en) | 2006-11-03 | 2006-11-03 | Device for access to multicast service from wireless network controller |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101175003A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102056084A (en) * | 2009-11-04 | 2011-05-11 | 中兴通讯股份有限公司 | Multimedia broadcasting multicast service system and synchronization method thereof |
-
2006
- 2006-11-03 CN CNA2006101438589A patent/CN101175003A/en not_active Withdrawn
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102056084A (en) * | 2009-11-04 | 2011-05-11 | 中兴通讯股份有限公司 | Multimedia broadcasting multicast service system and synchronization method thereof |
| CN102056084B (en) * | 2009-11-04 | 2016-02-10 | 中兴通讯股份有限公司 | Multimedia broadcast multicast service system and synchronous method thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1802049B1 (en) | A method and system for controlling multimedia broadcast/multicast service session | |
| CN1748386B (en) | Method for managing service context of user equipment paging in multimedia broadcast/multicast service | |
| CN101272520B (en) | Method and device for supporting multimedia broadcast multicast service in system structure evolution | |
| US6701155B2 (en) | Network initialized packet data protocol context activation for multicast/broadcast services | |
| CN101267593B (en) | Method and base station for activating multicast and broadcast multimedia service in target cells | |
| US7493108B2 (en) | Provision of a multimedia broadcast/multicast service (MBMS) for a user equipment moving along cells in a cellular mobile communication system | |
| CN100438654C (en) | Press-and-through system and method for realizing same | |
| CN100471323C (en) | Method for acquiring system information as switching residence | |
| CN101132607A (en) | Access gateway, base station and method for evolutionary multimedia broadcast multicast business | |
| CN100394827C (en) | Anti-activating method and related apparatus for multi-media and multiple-broadcasting service | |
| CN100502358C (en) | Method for establishing GTP tunnel in multimedia broadcast/multicast service | |
| CN100473013C (en) | Method for establishing context in multicast service of mobile communication system | |
| CN100502570C (en) | Method for terminal in mobile communication system to obtain APN when joining in multicast service group | |
| TW200808082A (en) | File repair mechanism for MBMS and UMTS network | |
| CN100531137C (en) | Method for establishing control side tunnel in mobile communication system multicast service | |
| CN101094439B (en) | Method and device of assigning resources dynamically for broadcast service in wireless communication system | |
| CN100426886C (en) | Method for realizing stream media service | |
| CN101090327A (en) | Method and system for broadcast/multicase service and supporting IPV4 and IPV6 address at same time | |
| EP1821465B1 (en) | A method for implementing the deactivation of the multimedia broadcast multicast service | |
| CN1307829C (en) | User data message transporting method and device | |
| CN101175003A (en) | Device for access to multicast service from wireless network controller | |
| CN100550865C (en) | The method of multicast user's activating, deactivating in a kind of mobile multicast broadcast service | |
| CN101257397B (en) | Method for accessing multicasting service from wireless network controller | |
| CN100442757C (en) | Method for log-on multimedium broadcast/group broadcast service operation | |
| CN100428860C (en) | Multimedia broadcast/multicast service linking method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C04 | Withdrawal of patent application after publication (patent law 2001) | ||
| WW01 | Invention patent application withdrawn after publication |