CN1177434C - Method for realizing multicast business based on universal land radio insertion network interface - Google Patents
Method for realizing multicast business based on universal land radio insertion network interfaceInfo
- Publication number
- CN1177434C CN1177434C CNB021256721A CN02125672A CN1177434C CN 1177434 C CN1177434 C CN 1177434C CN B021256721 A CNB021256721 A CN B021256721A CN 02125672 A CN02125672 A CN 02125672A CN 1177434 C CN1177434 C CN 1177434C
- Authority
- CN
- China
- Prior art keywords
- sgsn
- rnc
- rab
- subordinate
- main
- 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
The present invention discloses a method for realizing a multicast service based on a universal land audio access network interface. An audio network controller (RNC) is simultaneously connected with a plurality of service general grouping radio service supporting nodes (SGSN). The method comprises the following steps that each SGSN establishing the multicast service with the RNC respectively transmits a radio access bearing (RAB) request of the multicast service to the RNC; firstly, whether the RAB corresponding to the same multicast service exists at present is judged after the RNC receives the request; if the RAB does not exist, the RNC directly establishes the corresponding RAB with the SGSN transmitting resquest; if the RAB exists, the RNC establishes the corresponding RAB with the SGSN transmitting request; subsequently, one SGSN from a plurality of service general grouping radio service supporting nodes SGSN at present is selected as a main SGSN, and simultaneously, the RAB is used as a main RAB so that the RNC carries out the multicast service data transmission by the main SGSN; simultaneously, the RNC uses other service general grouping radio service supporting nodes SGSN as an auxiliary SGSN, and the RAB is used as an auxiliary RAB so that the auxiliary SGSN transmits the multicast data to the RNC so as to sustain the auxiliary RAB.
Description
Technical field
The present invention relates to the realization technology of multicast service in the wireless communication system (MBMS), specifically be meant a kind of implementation method of the multicast service based on universal land radio insertion network interface technology (Iu-Flex).
Background technology
Multicast service is a kind of data to be sent to the implementation method of a plurality of destinations from a data source, and by realizing multicast service, identical data content only need transmit once just can send to a plurality of users, thereby has saved Internet resources.
In the standard that the 3rd generation partnership project (3GPP) is formulated, the mobile radio system of realizing multicast service is referring to Fig. 1, and Fig. 1 is the mobile radio system structural representation of existing techniques in realizing multicast service.Among Fig. 1, UE/MS 101 refers to portable terminal, and subscriber equipment (UE, User Equipment) is the general designation of portable terminal in the UMTS network, and travelling carriage (MS, Mobile Station) is the general designation of portable terminal in GPRS (GPRS) network; Similarly, RNS/BSS 102 refers to wireless access network system, Radio Network System (RNS, Radio Network System) and base station system (BSS, Base StationSvstem) be wireless access mesh portions in UMTS network and the GPRS network respectively, the interface of itself and core net is the Iu interface.Core net comprises: attaching position register (HLR, Home Location Register) 103, Serving GPRS Support Node (SGSN) 104, charging gateway 105, Gateway GPRS Support Node (GGSN) 106, inner content provider 107, multicast service center 108, borde gateway 109 and inner multicast service source 110.Packet Data Network comprises: exterior content provider 111 and outside multicast service source 112.
SGSN 104 carries out the miscellaneous service controlled function and the mobile management function of multicast services, transmits cast service data from GGSN 106 to each relevant RNS/BSS 102.GGSN 106 is responsible for and the multicast service source 110,112 of network internal or outside is got in touch, and will give SGSN 104 from the data forwarding of multicast service source 110 or 112.Multicast service center 108 also is a multicast service source, different with other multicast service source is, multicast service center 108 can manage the multi-case data from inside and outside content supplier and arrange, and also will carry out authentication and charging etc. to inner and exterior content provider simultaneously.Borde gateway 109 controls have only the data of certain particular address or some specific fracture can carry out mobile communications network inside from the transfer of data of external network such as regulation.Charging gateway 105 is responsible for collecting the charging data record of multicast service, delivers to the charging center through relevant treatment.Preserve multicast service contracted user's CAMEL-Subscription-Information and routing iinformation among the HLR 103.Network internal and outside content supplier 107,111 send the business datum of BroadCast MultiCast Service to the multicast service center, and are distributed to GGSN106 by multicast service center 109.GGSN 106 sends to SGSN 104 by the multicast link of having set up, and SGSN 104 sends to each relevant RNS/BSS 102 of wireless access network.
In the standard that the 3rd generation partnership project (3GPP) is formulated, the Iu-Flex technology allows the node of a wireless access network to be connected to a plurality of core net nodes, for example the radio network controller (RNC) of the base station controller (BSC) of a General Packet Radio System (GPRS) or universal mobile telecommunications system (UMTS) can be connected to a plurality of service GPRS service support nodes (SGSN) of core net simultaneously, like this, when realizing that in based on the network environment of Iu-Flex technology MBMS is professional, the Business Stream of MBMS may send to same RNC from each SGSN, causes the waste of network bandwidth resources.
Standard according to 3GPP formulates in actual applications, has produced multiple method that can address the above problem, realization multicast service in the network environment of Iu-Flex technology.
First kind of method that is to use the SGSN of acquiescence.Carrying out that multicast service activates or reorientation/during handoff procedure, whether whether the RNC decision set up a multicast service stream or joined in the multicast service stream that has existed.In order to guarantee that RNC only receives multi-case data from a SGSN, RNC at first determines one " acquiescence SGSN ", " acquiescence SGSN " is used for setting up in advance the passage of multicast service stream, set up control RAB (RAB) link between the SGSN of RNC and each user registration simultaneously, the connection that keeps signaling.Because the SGSN of user's registration can't know the data volume that " acquiescence SGSN " transmits, so this method will cause the difficulty based on the traffic carrying capacity charging.
Second kind is the SGSN by-pass method.SGSN participates in the mutual of multicast signaling in this method, but GGSN directly sends cast service data and do not need SGSN to participate in to RNC.Because RNC can directly be connected with GGSN, the internal structure of network will be disclosed when therefore roaming between GGSN and SGSN, and then cause network security problem, because the SGSN of user's registration can't know the data volume of current transmission, the charging based on traffic carrying capacity also can be restricted simultaneously.
The third is that RNC selects one tunnel method from the multichannel multicast service stream.In this method, RNC adheres to receiving the data flow that sends from each SGSN, but only selects one of them data flow to be distributed to multicast users.The shortcoming of this method is that Internet resources can not be fully used.
The 4th kind is the single method of attachment of RNC.In the method, when the MBMS multi-case data begins to transmit, RNC detects the request that a plurality of SGSN send, for same multicast service is established to connection between each SGSN, but RNC only and one of them SGSN set up multicast RAB, and do not set up RAB between other SGSN, but other SGSN can receive multi-case data and produce charge on traffic information for specific user from Gateway GPRS Support Node (GGSN) for this multicast service.In network environment based on the Iu-Flex technology, for a plurality of users that have identical multicast service in the same sub-district, even be connected on the same RNC, also may provide service simultaneously by a plurality of SGSN, each SGSN must be in full accord about the message parameter of MBMS in this case, this will cause between each SGSN about MBMS synchronously and the control complexity of parameter consistency, the implementation efficiency reduction.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of implementation method of the multicast service based on universal land radio insertion network interface, use this method to realize that multicast service is simple, reliable, can save Internet resources, help the safety and the accounting management of network.
For achieving the above object, technical scheme of the present invention specifically is achieved in that
A kind of implementation method of the multicast service based on universal land radio insertion network interface links to each other a radio network controller (RNC) simultaneously with an above service universal grouping wireless business supporting node (SGSN), this method may further comprise the steps:
1) each will send RAB (RAB) request of multicast service with the SGSN that RNC sets up multicast service respectively to RNC, after RNC receives the RAB request of each SGSN, judge earlier that the current RAB that whether has corresponding same multicast service sets up, and enters step 2 then);
2) if do not have, then RNC directly and this SGSN that sends request set up the RAB of corresponding multicast service; Otherwise, the SGSN that RNC and this send request sets up the RAB of corresponding multicast service, from current all SGSN that connect with it, corresponding same multicast service, select a SGSN as main SGSN then, will and this main SGSN between RAB as the main RAB of receiving multicast traffic, RNC carries out the transmission of cast service data by main SGSN, and RNC abandons redundant multi-case data only transmits multi-case data from autonomous SGSN to terminal; Simultaneously RNC with other SGSN as subordinate SGSN, will and subordinate SGSN between RAB as subordinate RAB, subordinate SGSN sends multi-case data to RNC.
It can be the complete cast service data stream or the multicast data stream or the zero business datum flow of compression that subordinate RAB goes up the data flow that transmits.RNC can transmit the multicast data stream or the zero business datum flow of complete cast service data stream or compression according to the indication information that RNC provides on subordinate RAB.
Above-mentioned steps 2) may further include, RNC judges whether more change owner SGSN, if desired, selects a SGSN as main SGSN in subordinate SGSN, then by and new main SGSN between RAB receive multi-case data, continue simultaneously to keep with all subordinate SGSN between be connected.
RNC selects a SGSN as main SGSN, can be selected at random or RNC requires to select to the service quality (QoS) of multicast service according to the load of the quality of the precedence that receives multicast packets, transmission link, transmission link, precedence that transmission link is set up and each SGSN by RNC.
The process of above-mentioned more change owner SGSN further comprises:
A1, RNC select a subordinate RAB as new main RAB, and send recovery request to the SGSN that sets up this new main RAB;
After SGSN described in b1, the step a1 receives recovery request, send complete multi-case data to RNC as new main SGSN;
C1, RNC send standby request to the SGSN that sets up former main RAB;
After SGSN described in d1, the step c1 receives standby request, by send the multi-case data of compression to RNC, keep its with RNC between be connected.
This more the process of change owner SGSN also may further include:
A2, RNC send recovery request to all SGSN that set up subordinate RAB;
After b2, the SGSN that each sets up subordinate RAB receive recovery request, send complete multi-case data to RNC;
C2, RNC select a SGSN among the step b2 as main SGSN, and to set its RAB with RNC foundation be new main RAB;
D2, RNC send standby request to the SGSN that sets up former main RAB and other non-main SGSN;
After each SGSN described in e2, the steps d 2 receives standby request, by send the multi-case data of compression to RNC, keep they with RNC between be connected.
RNC changes or selects main SGSN, can carry out when network need discharge RAB between RNC and the main SGSN; Can not set up yet and carry out when SGSN that RAB is connected initiates the RAB connection request as yet with RNC.
This method further comprises: before RNC selected main SGSN, the qos requirement that RNC and current each SGSN consult multicast RAB respectively was so that the multicast RAB of the main RX path of setting up can satisfy the requirement of all main SGSN and subordinate SGSN.
Subordinate SGSN described in this method sends the multi-case data of compression to RNC, it can be subordinate SGSN sends compressed packet from the cast service data bag to RNC, or subordinate SGSN periodically sends a spot of cast service data bag to RNC, or the cast service data bag of compression, or the RAB state information; Or RNC and restrictive condition of this subordinate SGSN elder generation negotiation, in this restrictive condition, this subordinate SGSN stops to send the cast service data bag to RNC; When surpassing described restrictive condition, subordinate SGSN can send actual cast service data bag to RNC again, and after this RNC and subordinate SGSN can consult new restrictive condition once more; Above-mentioned restrictive condition is meant according to time requirement or data volume scope or service environment requirement and consults.
This method can also comprise: receive the multicast packets of main SGSN transmission as RNC after, RNC can be initiatively report the statistical information of cast service data to main SGSN and current each subordinate SGSN that is attached thereto, or the request of response SGSN reports the statistical information of cast service data to this SGSN.
This statistical information can comprise: the quantity of data packets that RNC receives from main SGSN and/or current SGSN, and the quantity of the multicast packets that RNC has sent to air interface, RNC does not also have the quantity of the multicast packets transmitted etc.
By such scheme as can be seen, key of the present invention is: when the transmission multi-case data, RNC detects a plurality of multicast service stream during corresponding to a multicast service that derive from other SGSN that is attached thereto, select a SGSN as main SGSN by RNC, will and main SGSN between RAB as the main RAB of receiving multicast traffic, RNC carries out the transmission of cast service data by main SGSN; Simultaneously RNC with other SGSN as subordinate SGSN, will and subordinate SGSN between RAB as subordinate RAB, and send multi-case data to RNC by subordinate SGSN, keep RNC and be connected with RAB between the subordinate SGSN.
Therefore, the implementation method of the multicast service based on universal land radio insertion network interface provided by the present invention, owing to adopt RNC to select a SGSN as main SGSN, will and main SGSN between RAB as the main path of receiving multicast traffic, simultaneously RNC with other SGSN as subordinate SGSN, and keep with subordinate SGSN between the method that is connected of RAB realize multicast service, compare with existing method 1, since RNC with other SGSN as subordinate SGSN, and keep with subordinate SGSN between RAB be connected, therefore can not produce the charging problem; Compare with existing method 2,, can not cause network security problem, also help realizing charging simultaneously based on flow because the transmission of multicast service need not disclose the internal structure of network; Compare with existing method 3,, reduced the waste of transfer resource owing to mainly issue multi-case data by main SGSN; Compare with existing method 4, do not have between each SGSN about the parameter information of multicast service the handling problem when inconsistent, it is simple, reliable that system is realized; Therefore adopt the present invention can either save Internet resources, make again and realize that multicast service is simple, reliable, and help the safety and the accounting management of network.In a word, use this method to realize that multicast service is simple, reliable, can save Internet resources, help the safety and the accounting management of network.
Description of drawings
Fig. 1 is the mobile radio system structural representation of existing techniques in realizing multicast service;
Fig. 2 is the schematic diagram of multi-case data transmission path of the present invention;
Fig. 3 is the implementation method flow chart of multicast service of the present invention;
The preferred embodiment flow chart of Fig. 4 new multicast RAB for the present invention sets up;
Another preferred embodiment flow chart of Fig. 5 new multicast RAB for the present invention sets up;
Another preferred embodiment flow chart of Fig. 6 new multicast RAB for the present invention sets up;
Fig. 7 is the more preferred embodiment flow chart of change owner SGSN of the present invention;
Fig. 8 is more another preferred embodiment flow chart of change owner SGSN of the present invention;
Fig. 9 is more another preferred embodiment flow chart of change owner SGSN of the present invention.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, by the following examples, and with reference to accompanying drawing, the present invention is described in more detail.
Fig. 2 is the schematic diagram of multi-case data transmission path, as shown in Figure 2, if have N SGSN to be connected to same RNC and corresponding to same multicast service, then RNC selects one of them SGSN as main SGSN, other SGSN are subordinate SGSN, the RAB link of setting up between RNC and the main SGSN is as main RAB link, and the RAB link of setting up between RNC and the subordinate SGSN is as subordinate RAB link; Be main RAB link with the RAB link of setting up between RNC and the SGSN1 among the figure, with the heavy line signal, other be subordinate RAB link, and with dashed lines is illustrated.
Fig. 3 is the implementation method flow chart of multicast service of the present invention, referring to shown in Figure 3, when realizing multicast service, in step 301, at first set up request to the RAB that RNC sends multicast service by SGSN, RNC sets up the RAB of corresponding multicast service according to request with this SGSN, and receives multicast data stream from this SGSN; In the process of RNC receiving multicast traffic data, with it a plurality of multicast service stream of different SGSN of annexation are arranged in step 302 detection, judge that in step 303 whether above-mentioned multicast service stream is corresponding to same multicast service then, if RNC finds not have the situation of a plurality of multicast service stream corresponding to same multicast service, then change the transmission that step 305 is proceeded multicast service; When if RNC finds to have a plurality of multicast service stream corresponding to same multicast service, then carry out step 304, RNC selects a SGSN as main SGSN, will and main SGSN between RAB as the main path of receiving multicast traffic, simultaneously RNC with other SGSN as subordinate SGSN, and keep with subordinate SGSN between RAB be connected, subordinate SGSN only sends the multi-case data of compression to keep the connection between RNC and the SGSN; Continue step 305 and carry out the transmission of multicast service, carry out the transmission of multicast service by main RAB, the RAB that keeps simultaneously between RNC and the subordinate SGSN connects.
In the transmission course at multicast service of step 305, RNC also will judge whether more change owner SGSN, if desired, in subordinate SGSN, select a SGSN as main SGSN, then by and new main SGSN between RAB receive multi-case data, continue simultaneously to keep with other subordinate SGSN between be connected.RNC can cancel the qualification of main RAB as required at any time and certain subordinate RAB is risen to main RAB, and RNC goes up the receiving multicast traffic data from new main RAB simultaneously.When discharging reasons such as main RAB in multicast users deviated from network or switching or link failure or main SGSN request and causing network need discharge main RAB between RNC and the main SGSN, perhaps initiating to set up the RAB connection request with RNC as new SGSN, when the operation conditions of network may change, for example, the load of former main RAB link may not be optimum, then needs more change owner SGSN and main RAB.The qos requirement that RNC and each SGSN consulted or consulted again multicast RAB respectively is so that the multicast RAB of main RX path can satisfy the requirement of all main SGSN and subordinate SGSN.
It can be the result who selects at random that RNC selects the foundation of new main SGSN, or RNC selects the factors such as qos requirement of multicast service from precedence, the quality of transmission link, the load of transmission link, the precedence of RAB foundation, each SGSN that each paths receives multicast packets.
Subordinate SGSN comprises two kinds of situations to the multi-case data that RNC transmits compression: after a kind of RNC of being and subordinate SGSN consulted a restrictive condition, in this restrictive condition, subordinate SGSN stopped to send the cast service data bag to RNC; To be SGSN send by cast service data bag pressure contract the zero for no traffic amount that message forms or the data traffic of minimum number to RNC another kind.
In actual applications, subordinate SGSN can obtain the multi-case data that compresses in the following ways:
1) RNC and subordinate SGSN consult a restrictive condition.In the scope of this restrictive condition, subordinate SGSN stops to RNC retransmitting multi-casting business data packet, only keeps this subordinate SGSN to be connected with link between the RNC.After surpassing restrictive condition, subordinate SGSN sends actual cast service data bag to RNC again.After this RNC and subordinate SGSN can consult new restrictive condition once more.This restrictive condition can be requirement or the scope of data volume, the requirement (as QoS) of service environment etc. of time, for example in 1 hour and data packet number wrap less than 10,000 IP.When not binding hours and data volume, subordinate SGSN will be to RNC retransmitting multi-casting business data packet.
2) at subordinate SGSN when RNC sends cast service data, subordinate SGSN only sends compressed packet to RNC, RNC receives continuity, integrality and the correctness that can judge multicast data stream behind the compressed packet.
3) RNC and subordinate SGSN consult to determine that regular hour or data packet number are as shaking hands the cycle.The cycle of shaking hands also can be disposed by operator.Do not send cast service data when subordinate SGSN is flat, but every regular hour and/or quantity of data packets, send the multicast packets or the RAB state information of a spot of multicast packets or compression to RNC, to keep the connection of multicast service RAB.
Need explanation, aforesaid way 1) to mode 3) can be used alternatingly or be used in combination.Such as: combination 1) and mode 2), RNC and subordinate SGSN consult a restrictive condition, in the scope of this restrictive condition, subordinate SGSN sends the compressed packet of cast service data bag to RNC.After surpassing restrictive condition, subordinate SGSN sends actual cast service data bag to RNC again.After this RNC and subordinate SGSN can consult new restrictive condition once more.This restrictive condition can be the requirement of time, the scope of data volume, the requirement (as QoS) of service environment etc.
In the cast service data transmission course, when the quantity of the bag that receives from GGSN as subordinate SGSN surpassed the requirement for restriction of RNC, this SGSN did not transmit this packet or only transmits compressed packet to RNC, and acquiescence RNC has received this multi-case data.This SGSN adds up the multicast service flow that SGSN is transmitted to multicast users with this.Compressed packet is meant short infomational message, as the summary info of cast service data bag or IP packet header or the bag sequence number of multicast packets or the bag sequence number tabulation of multicast packets etc. of multicast packets.The purpose that subordinate SGSN continues to RNC transmission compressed packet is to be connected with keeping of RNC, and total data traffic is reduced.When subordinate SGSN not to RNC retransmitting multi-casting packet or when only transmitting compressed packet, the statistical information of the cast service data bag that RNC can receive RNC from main SGSN sends to main SGSN and each subordinate SGSN, as the multicast service flow that receives from main SGSN, the multicast service flow of interface transmission aloft etc.
The preferred embodiment flow chart of Fig. 4 new multicast RAB for the present invention sets up.RNC is connected with the RAB that SGSN1 has set up multicast service A among the figure.This moment, the SGSN2 request was connected with the new RAB that RNC sets up multicast service A.Idiographic flow is as follows:
At first, execution in step 401, SGSN2 initiates RAB to RNC and sets up request, comprises in the request message that the qos parameter of multicast service A requires, the sign of Access Network identification multicast service A, and the Iu interface connects parameter etc.;
Then, execution in step 402, RNC sets up Iu interface transmission link with SGSN2 after receiving that RAB sets up request;
Then, execution in step 403, RNC is according to the sign of multicast service A, judges that RNC is connected with the RAB that SGSN1 has set up multicast service A, follows RNC and judges whether more change owner SGSN, in the present embodiment, judges not more change owner SGSN of needs according to reality;
Execution in step 404 again, and RNC sends RAB to SGSN2 and sets up request responding, and indication multicast RAB sets up, and indication SGSN2 retransmitting multi-casting business datum;
Execution in step 405 again, SGSN1 or SGSN2 can send the statistical information query requests, require RNC to report the state information of multicast service, the state information content comprises: the quantity of data packets that RNC receives from main SGSN and/or current SGSN, the quantity of the multicast packets that RNC has sent to air interface, RNC does not also have the quantity of the multicast packets transmitted etc.;
Execution in step 406 again, and the RNC response request reports statistic behavior information to SGSN1 or SGSN2.The state information content comprises: the quantity of data packets that RNC receives from main SGSN and/or current SGSN, and the quantity of the multicast packets that RNC has sent to air interface, RNC does not also have the quantity of the multicast packets transmitted etc.;
At last, execution in step 407, SGSN1 and SGSN2 add up multicast users respectively according to cast service data flow, QoS or other information or charge.
Wherein, RNC subordinate SGSN1 and SGSN2 receive cast service data, but RNC only transmits the data that main SGSN sends, and are exactly only to transmit the data that SGSN1 sends in the present embodiment, abandon the data that SGSN2 sends.
Another preferred embodiment flow process of Fig. 5 new multicast RAB for the present invention sets up.RNC is connected with the RAB that SGSN1 has set up multicast service A among the figure.This moment, the SGSN2 request was connected with the new RAB that RNC sets up multicast service A.Idiographic flow is as follows:
At first, execution in step 501, SGSN2 initiates RAB to RNC and sets up request, comprises in the request message that the qos parameter of multicast service A requires, the sign of Access Network identification multicast service A, and the Iu interface connects parameter etc.;
Then, execution in step 502, RNC sets up Iu interface transmission link with SGSN2 after receiving that RAB sets up request;
Then, execution in step 503, RNC is according to the sign of multicast service A, judges that RNC is connected with the RAB that SGSN1 has set up multicast service A, follows RNC and judges whether more change owner SGSN, in the present embodiment, judges not more change owner SGSN of needs according to reality;
Execution in step 504 again, and RNC sends RAB to SGSN2 and sets up request responding, and indication multicast RAB sets up, and indication does not need actual retransmitting multi-casting business datum in this Iu connection; Response message comprises: the qos parameter setting of multicast service A, and the Iu interface connects parameter, cast service data forwarding information, as the form of time interval Δ t, compressed packet or the like of shaking hands;
Execution in step 505 again, and to the RNC send state information, the state information content comprises SGSN2 every time Δ t: the bag sequence number that SGSN transmits to RNC less than the quantity of the multicast packets of transmitting to RNC, current wait etc.;
Execution in step 506 again, and RNC checks whether the state information of SGSN2 transmission is consistent with the information of multicast service A; As information inconsistency, then RNC reports the state of current RNC to SGSN2; As the information unanimity, then RNC transmit status indication, notice SGSN2 keeps current state;
Execution in step 507 again, and at set intervals, RNC sends statistical information to SGSN1 and SGSN2, the cast service data flow that report RNC subordinate SGSN1/SGSN2 receives and the cast service data flow of RNC interface transmission aloft;
At last, execution in step 508, SGSN1 and SGSN2 charge to multicast users respectively according to cast service data flow, QoS or other information.
Wherein, RNC subordinate SGSN1 and SGSN2 receive cast service data, but RNC only transmits the data that main SGSN sends, and are exactly only to transmit the data that SGSN1 sends in the present embodiment, abandon the data that SGSN2 sends.
Another preferred embodiment flow process of Fig. 6 new multicast RAB for the present invention sets up.RNC is connected with the RAB that SGSN1 has set up multicast service A among the figure, and this moment, the SGSN2 request was connected with the new RAB that RNC sets up multicast service A.Idiographic flow is as follows:
At first, execution in step 601, SGSN2 initiates RAB to RNC and sets up request, comprises in the request message that the qos parameter of multicast service A requires, the sign of Access Network identification multicast service A, and Iu interface transmission link connects parameter etc.;
Then, execution in step 602, RNC sets up Iu interface transmission link with SGSN2 after receiving that RAB sets up request;
Then, execution in step 603, RNC sends RAB to SGSN2 and sets up request responding, and indication multicast RAB sets up, and response message comprises: the qos parameter setting of multicast service A, the Iu interface connects parameter etc.;
Execution in step 604 again, and RNC is according to the sign of multicast service A, judge that RNC is connected with the RAB that SGSN1 has set up multicast service A, then RNC judges whether more change owner SGSN, in the present embodiment, judge needs selection SGSN2 as main SGSN according to reality, the RAB of RNC and SGSN2 is main RAB;
Execution in step 605 again, and RNC subordinate SGSN2 receives multi-case data, do not need actual retransmitting multi-casting business datum in this Iu connection of the SGSN1 of RNC indication simultaneously; The content of indication information comprises: cast service data forwarding information, as the form of time interval Δ t, compressed packet or the like of shaking hands;
Execution in step 606 again, and SGSN1 sends the compressed packet of current cast service data bag every time Δ t to RNC, and the content of compressed packet comprises: the IP packet header of current IP multicast packets, bag sequence number etc.;
Execution in step 607 again, and RNC checks whether the state information of SGSN1 transmission is consistent with the information of multicast service A, as information inconsistency, then RNC reports the state of current RNC to SGSN1, as the information unanimity, then RNC transmit status indication, notice SGSN1 keeps current state;
Execution in step 608 again, and at set intervals, RNC sends statistical information to SGSN1 and SGSN2, the cast service data flow that report RNC subordinate SGSN1/SGSN2 receives and the cast service data flow of RNC interface transmission aloft;
At last, execution in step 609, SGSN1 and SGSN2 charge to multicast users respectively according to cast service data flow, QoS or other information.
Wherein, RNC subordinate SGSN1 and SGSN2 receive cast service data, but RNC only transmits the data that main SGSN sends, and are exactly only to transmit the data that SGSN2 sends in the present embodiment, abandon the data that SGSN1 sends.
Fig. 7 is the more preferred embodiment flow process of change owner SGSN of the present invention.As shown in Figure 7, idiographic flow is as follows:
At first, execution in step 701, RNC and SGSN1 set up main RAB, set up subordinate RAB with SGSN2 and SGSN3;
Step 702 is when RNC finds that the service quality (QoS) of the main RAB between RNC and the SGSN1 descends;
Execution in step 703, RNC determines that according to the QoS of each subordinate RAB the RAB that RNC and SGSN2 set up is new main RAB;
Then, execution in step 704, RNC sends recovery request to SGSN2, requires SGSN2 to recover to send complete cast service data stream;
Then, execution in step 705 after SGSN2 receives recovery request, stops to send to RNC the cast service data stream of compression, and beginning sends complete cast service data stream to RNC;
Execution in step 706 again, and RNC sends standby request to SGSN1, require SGSN1 to send the cast service data stream of compression;
At last, execution in step 707, after SGSN1 receives standby request, earlier to multicast data stream compress, simplification or discard processing, begin to send the cast service data stream of compression again to RNC, the cast service data stream of compression comprises necessary information or minimum data volume, or carries information such as the disposal ability of SGSN or load, and sending it is the connection that is used for keeping between RNC and the SGSN1;
Wherein, step 706 and step 707 are processes that RNC discharges former main RAB.Thus, finished the once renewal of main SGSN.
Fig. 8 is more another preferred embodiment flow process of change owner SGSN of the present invention.As shown in Figure 8, idiographic flow is as follows:
At first, execution in step 801, RNC and SGSN1 set up main RAB, set up subordinate RAB with SGSN2 and SGSN3;
Step 802 is when SGSN1 request RNC discharges this main RAB;
Execution in step 803, RNC determines that according to the QoS of each subordinate RAB the RAB that RNC and SGSN2 set up is new main RAB;
Then, execution in step 804, RNC sends recovery request to SGSN2, requires SGSN2 to recover to send complete cast service data stream;
Then, execution in step 805 after SGSN2 receives recovery request, stops to send to RNC the cast service data stream of compression, and beginning sends complete cast service data stream to RNC;
Execution in step 806 again, and RNC sends standby request to SGSN1, require SGSN1 to send the cast service data stream of compression;
Last execution in step 807, after SGSN1 receives standby request, earlier to multicast data stream compress, simplification or discard processing, begin to send the cast service data stream of compression again to RNC, the cast service data stream of compression comprises necessary information or minimum data volume, or carry information such as the disposal ability of SGSN or load, sending it is the connection that is used for keeping between RNC and the SGSN1;
Wherein, step 806 and step 807 are processes that RNC discharges former main RAB.Thus, finished the once renewal of main SGSN.
Fig. 9 is more another preferred embodiment flow process of change owner SGSN of the present invention.As shown in Figure 9, idiographic flow is as follows:
At first, execution in step 901, RNC and SGSN1 set up main RAB, set up subordinate RAB with SGSN2 and SGSN3;
Step 902 is when RNC finds main RAB fault between RNC and the SGSN1;
Execution in step 903 and step 904, RNC sends recovery request to each subordinate SGSN, promptly sends recovery request to SGSN2 and SGSN3, requires SGSN2 and SGSN3 to recover to send complete cast service data stream;
Then, execution in step 905 and step 906 after SGSN2 and SGSN3 receive recovery request, stop to send to RNC the cast service data stream of compression, and beginning sends complete cast service data stream to RNC;
Then, execution in step 907, RNC determines that according to the QoS of each subordinate RAB SGSN2 is main SGSN, the RAB that RNC and SGSN2 set up is new main RAB;
Execution in step 908 and step 909 again, RNC sends standby request to SGSN1 and SGSN3, requires SGSN1 and SGSN3 to send the cast service data stream of compression;
Last execution in step 910 and step 911, after SGSN1 and SGSN3 receive standby request, earlier to multicast data stream compress, simplification or discard processing, begin to send the cast service data stream of compression again to RNC, the cast service data stream of compression comprises necessary information or minimum data volume, or carry information such as the disposal ability of SGSN or load, sending it is the connection that is used for keeping between RNC and the SGSN1;
Wherein, step 908 and step 910 are processes that RNC discharges former main RAB.Thus, finished the once renewal of main SGSN.
In the process of the foregoing description transmission compression multicast packets, subordinate SGSN can abandon all or part of multi-case data that will transmit to RNC according to the indication information that RNC provides, and also can transmit whole cast service datas to RNC; RNC abandons redundant multi-case data.
This shows that the implementation method of the multicast service based on universal land radio insertion network interface provided by the present invention uses this method to realize that multicast service is simple, reliable, can save Internet resources, helps the safety and the accounting management of network.
Claims (18)
1, a kind of implementation method of the multicast service based on universal land radio insertion network interface, a radio network controller (RNC) is linked to each other with an above service universal grouping wireless business supporting node (SGSN) simultaneously, it is characterized in that this method may further comprise the steps:
1) each will send RAB (RAB) request of multicast service with the SGSN that RNC sets up multicast service respectively to RNC, after RNC receives the RAB request of each SGSN, judge earlier that the current RAB that whether has corresponding same multicast service sets up, and enters step 2 then);
2) if do not have, then RNC directly and this SGSN that sends request set up the RAB of corresponding multicast service; Otherwise, the SGSN that RNC and this send request sets up the RAB of corresponding multicast service, from current all SGSN that connect with it, corresponding same multicast service, select a SGSN as main SGSN then, will and this main SGSN between RAB as the main RAB of receiving multicast traffic, RNC carries out the transmission of cast service data by main SGSN, and RNC abandons redundant multi-case data only transmits multi-case data from autonomous SGSN to terminal; Simultaneously RNC with other SGSN as subordinate SGSN, will and subordinate SGSN between RAB as subordinate RAB, subordinate SGSN sends multi-case data to RNC.
2, implementation method as claimed in claim 1 is characterized in that: step 2) multi-case data that sends to RNC of described subordinate SGSN is the complete cast service data stream or the multicast data stream or the zero business datum flow of compression.
3, implementation method as claimed in claim 2 is characterized in that: described subordinate SGSN is to send according to the indication information that RNC provides to multicast data stream or the zero business datum flow that RNC sends complete cast service data stream or compression.
4, implementation method as claimed in claim 1, it is characterized in that: described step 2) further comprise, RNC judges whether more change owner SGSN, if desired, in subordinate SGSN, select a SGSN as main SGSN, then by and new main SGSN between RAB receive multi-case data, continue simultaneously to keep with all subordinate SGSN between be connected.
5,, it is characterized in that SGSN of described selection is selected by RNC at random as main SGSN as claim 1 or 4 described implementation methods.
6,, it is characterized in that SGSN of described selection is service quality (QoS) requirement of multicast service to be selected according to the quality of the precedence that receives multicast packets, transmission link, the load of transmission link, precedence and each SGSN that transmission link is set up by RNC as main SGSN as claim 1 or 4 described implementation methods.
7, implementation method as claimed in claim 4 is characterized in that the process of described more change owner SGSN further comprises:
A1, RNC select a subordinate RAB as new main RAB, and send recovery request to the SGSN that sets up this new main RAB;
After SGSN described in b1, the step a1 receives recovery request, send complete multi-case data to RNC as new main SGSN;
C1, RNC send standby request to the SGSN that sets up former main RAB;
After SGSN described in d1, the step c1 receives standby request, by send the multi-case data of compression to RNC.
8, implementation method as claimed in claim 4 is characterized in that the process of described more change owner SGSN further comprises:
A2, RNC send recovery request to all SGSN that set up subordinate RAB;
After b2, the SGSN that each sets up subordinate RAB receive recovery request, send complete multi-case data to RNC;
C2, RNC select a SGSN among the step b2 as main SGSN, and to set its RAB with RNC foundation be new main RAB;
D2, RNC send standby request to the SGSN that sets up former main RAB and other non-main SGSN;
After each SGSN described in e2, the steps d 2 receives standby request, by send the multi-case data of compression to RNC.
9, implementation method as claimed in claim 4 is characterized in that: described RNC is change owner SGSN more, carries out when network need discharge RAB between RNC and the main SGSN.
10, implementation method as claimed in claim 4 is characterized in that: described RNC is change owner SGSN more, does not set up with RNC as yet and carries out when SGSN that RAB is connected initiates the RAB connection request.
11,, it is characterized in that this method also comprises as claim 1,4,7 or 8 described implementation methods: before described RNC selects main SGSN, the qos requirement that RNC and current each SGSN consult multicast RAB respectively.
12, as claim 2,3,7 or 8 described implementation methods, it is characterized in that: described subordinate SGSN is subordinate SGSN sends a compressed packet from the cast service data bag to RNC to the multi-case data that RNC sends compression.
13, as claim 2,3,7 or 8 described implementation methods, it is characterized in that: described subordinate SGSN is that subordinate SGSN periodically sends a spot of cast service data bag to RNC to the multi-case data that RNC sends compression, or the cast service data bag of compression, or RAB state information.
14, as claim 2,3,7 or 8 described implementation methods, it is characterized in that: described subordinate SGSN is that RNC and this subordinate SGSN consult a restrictive condition earlier to the multi-case data that RNC sends compression, in this restrictive condition, this subordinate SGSN stops to send the cast service data bag to RNC.
15, implementation method as claimed in claim 14 is characterized in that: when surpassing described restrictive condition, this subordinate SGSN sends actual cast service data bag to RNC again; After this RNC and this subordinate SGSN consult new restrictive condition once more.
16, implementation method as claimed in claim 15 is characterized in that: described restrictive condition is time requirement or data volume scope or service environment requirement.
17, implementation method as claimed in claim 1, it is characterized in that this method also comprises: RNC initiatively reports the statistical information of cast service data to main SGSN and each subordinate SGSN, or the statistical information request of response SGSN reports the statistical information of cast service data to this SGSN.
18, implementation method as claimed in claim 17, it is characterized in that this statistical information comprises: the quantity of the multicast packets that the quantity of data packets that RNC receives from main SGSN and/or current SGSN, RNC have sent to air interface and RNC also do not have the quantity of the multicast packets transmitted.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB021256721A CN1177434C (en) | 2002-04-09 | 2002-07-26 | Method for realizing multicast business based on universal land radio insertion network interface |
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN02116572.6 | 2002-04-09 | ||
| CN02116572 | 2002-04-09 | ||
| CNB021256721A CN1177434C (en) | 2002-04-09 | 2002-07-26 | Method for realizing multicast business based on universal land radio insertion network interface |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1450752A CN1450752A (en) | 2003-10-22 |
| CN1177434C true CN1177434C (en) | 2004-11-24 |
Family
ID=28792720
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB021256721A Expired - Fee Related CN1177434C (en) | 2002-04-09 | 2002-07-26 | Method for realizing multicast business based on universal land radio insertion network interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1177434C (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7725925B2 (en) * | 2003-10-31 | 2010-05-25 | Juniper Networks, Inc. | Enforcing access control on multicast transmissions |
| CN100456733C (en) * | 2003-11-19 | 2009-01-28 | 华为技术有限公司 | Method of realizing multimedia broadcasting/group broadcasting business deactivation |
| CN100456732C (en) * | 2003-11-19 | 2009-01-28 | 华为技术有限公司 | Method of realizing multimedia broadcasting group broadcnsting business deactivation |
| CN100444650C (en) * | 2004-03-03 | 2008-12-17 | 北京三星通信技术研究有限公司 | Method for introducing MBMS service identification |
| CN100344190C (en) * | 2004-12-14 | 2007-10-17 | 华为技术有限公司 | Base station networking method for wireless access network |
| CN1867022B (en) * | 2005-12-27 | 2010-06-09 | 华为技术有限公司 | Method and apparatus for realizing multicast service diversification charging |
| CN1867023B (en) * | 2005-12-27 | 2010-12-01 | 华为技术有限公司 | Method and apparatus for realizing multicast service pre-payment/later-payment |
| CN100466757C (en) * | 2006-03-22 | 2009-03-04 | 中兴通讯股份有限公司 | System for providing multicasting service in WiWAX mobile communication system |
| WO2008043297A1 (en) * | 2006-09-26 | 2008-04-17 | Huawei Technologies Co., Ltd. | Method, system and network node for bearer control, deletion and data transmission |
| CN101242569B (en) * | 2007-02-05 | 2013-03-20 | 中兴通讯股份有限公司 | A method for preventing or reducing multimedia broadcasting and multicast service interruption |
| CN101925038B (en) * | 2009-06-12 | 2013-01-02 | 华为技术有限公司 | Data transmission method, communication device and network system |
-
2002
- 2002-07-26 CN CNB021256721A patent/CN1177434C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN1450752A (en) | 2003-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1278250C (en) | Technique for providing announcements in mobile-originated calls | |
| JP4327089B2 (en) | Control signal transmission method for MBMS data in a wireless mobile communication system | |
| TWI305471B (en) | Enhanced assisted cell change | |
| AU2005204215B2 (en) | Repairing errors in data of MBMS service | |
| CN1190929C (en) | Allocation of resources in packet-switched data transfer | |
| CN1496138A (en) | Transmitting/receiving controlling information method for mobile communication system | |
| CN1822573A (en) | System and method for controlling data traffic in a wireless communication system | |
| CN1663151A (en) | Multimedia service providing method in a radio mobile communication system | |
| CN1859776A (en) | Roaming user data route optimizing method in 3GPP evolution network | |
| JP2019503142A (en) | Data scheduling method, base station and system | |
| CN1663310A (en) | Selective processing of the common control channel | |
| KR20050019388A (en) | Method of transmitting or receiving packet data and related control information for multimedia broadcasting and multicast service | |
| CN101076979A (en) | System, arrangement and method for providing core network nodes with mobile station related information | |
| CN1943145A (en) | Transmission of control information in wireless communication system | |
| CN1860737A (en) | Access to CDMA/UMTS service over a WLAN access point, using a gateway node between WLAN access point and service providing network | |
| CN1879326A (en) | Discontinuously transmitting and receiving multimedia broadcast/multicast service data in mobile communication system | |
| CN1520203A (en) | Method of simultaneous, accessing circuit sevice and packet service in cellwlar mobile radio system service | |
| CN1736124A (en) | Provision of a multimedia broadcast/multicast service (MBMS) for a user equipment moving along cells in a cellular mobile communication system | |
| CN1636417A (en) | Relocation of serving radio network controller with signaling of linking of transport channels | |
| CN1402949A (en) | Transfer of algorithm parameters during handover of mobile station between radio network subsystems | |
| KR20050073613A (en) | Method for multimedia broadcast/multicast service signaling bearer connection on iu interface | |
| CN1689301A (en) | Header compression method | |
| CN1177434C (en) | Method for realizing multicast business based on universal land radio insertion network interface | |
| CN101064953A (en) | Register method for mobile communication system and the used bimodule terminal | |
| CN101248629A (en) | Reserved bearing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| 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: 20041124 Termination date: 20130726 |